Quote:
Originally Posted by SonicVQ
Well, since you asked
If that was my car, I would use a good/fast wireless OBD scanner (OBDLink MX+, VeePeak BLE) and a good OBD app, like OBDFusion (or OBDLInk) and datalog:
Cylinder #1 ignition timing
Engine RPM
Vehicle speed
Short term and long term fuel trims for each bank
Engine coolant temp
Intake air temp
Absolute engine load
*O2 sensor lambda bank 1/2
Mass air flow A/B (Bank 1/2)
(Note: OBDLink MX+ can read about 40 PIDs/second, which results in about 4 samples per second per PID)
Log the data on different days and make of note of when you think the issue is happening.
Then, post your log file here and I will have a look. As a VQ specialist, I have been reviewing data logs for the last 5 years and have a good idea of what the "expected" values should be, for different driving conditions.
If the above is not too much effort or cost, it might shed some light on what is going on.
|
SonicVQ... that is amazing from you. Id certainly appreciate it.
I'll give it another go at the stealership... which isn't paying off, but given that I'm under warranty - warranty that they haven't so far neither honoured nor respected -... if not, I'll do what you suggested and I'll send you the data logs for the info above. Sounds very thorough.
I appreciate your time.
Sorry for the delay.
Hadn't logged in until now.
Cheers!
Gesendet von meinem SM-G985F mit Tapatalk