Was this article helpful?
Exporting OBD logs: turning a CSV into an actual answer
A log is only useful if you can compare it against something. Here is what to record, how to structure it, and which comparisons find faults.
Watching live data on a phone while driving is unsafe and ineffective. Logging it and looking afterwards is neither, and it makes comparisons possible that no amount of real-time watching can.
Related: reading live data graphs properly and OBD data logging for track days.
Fewer parameters, faster sampling
The most important decision, and most people get it wrong in the same direction.
An adapter polls parameters one at a time. Ten parameters means each is sampled a tenth as often as one would be.
Log four or five parameters relevant to your specific question, not everything available. A high sample rate on the right values beats a low rate on all of them.
Parameter sets by question
Mixture fault: short-term fuel trim, long-term fuel trim, MAF, engine RPM, calculated load.
Misfire: misfire counters per cylinder, RPM, load, coolant temperature.
Diesel power loss: rail pressure commanded and actual, boost commanded and actual, RPM, load.
Overheating: coolant temperature, RPM, vehicle speed, ambient temperature.
Transmission slip: RPM, vehicle speed, gear commanded and actual, fluid temperature.
Charging: control module voltage, RPM, electrical load.
Structuring the drive
A log of aimless driving is hard to interpret. A log of a defined sequence is not.
A useful standard sequence:
- Ignition on, engine off, thirty seconds. Establishes key-off reference values — this is where a sensor reading something impossible reveals itself.
- Cold start, then idle for two minutes. Warm-up behaviour.
- Gentle drive to full operating temperature.
- Steady cruise, two minutes. The most comparable condition.
- Full-throttle acceleration in a high gear. Load-dependent faults appear here and nowhere else.
- Overrun deceleration.
- Return to idle, warm.
Repeat the same sequence when comparing before and after a repair. Comparability is the whole point.
What the key-off segment catches
Worth its own note, because it is the cheapest diagnostic in this article.
With the engine off, several values have known correct answers:
| Parameter | Must read |
|---|---|
| Fuel rail pressure | Zero |
| Oil pressure | Zero |
| Transmission line pressure | Zero |
| MAP | Atmospheric |
| MAF | Zero |
| All temperature sensors | Approximately the same, after a soak |
Anything that disagrees has been caught lying before the engine even started.
P0520 to P0523 oil pressure sensor and P0191 to P0193 fuel rail pressure sensor.
Reading a CSV without special tools
Any spreadsheet will do.
Plot against time, not against row number, so gaps in sampling are visible.
Plot related values on the same chart. Commanded against actual is the single most informative pairing in diagnostics — rail pressure, boost, camshaft position, EGR position, gear.
Look for shape, not absolute values. A curve with steps, a value that plateaus when it should climb, two traces that diverge under load — those are faults. Individual numbers rarely are.
The comparisons that find things
| Comparison | Reveals |
|---|---|
| Commanded vs actual | Whether an actuator obeyed |
| Idle vs 2500 rpm trims | Vacuum leak versus metering error |
| Cold vs warm, same route | Temperature-dependent faults |
| Before vs after repair | Whether it worked |
| Bank 1 vs bank 2 | Which half of a V-engine |
| This month vs six months ago | Drift, and developing faults |
That last row is the one owners skip and shouldn’t. A baseline recorded when everything is fine is what makes every later log interpretable.
Fuel trim STFT and LTFT explained and the first OBD scan after buying a used car.
Doing it safely
Do not operate a phone while driving. Start the log before setting off, put the phone down, drive, and stop before looking at anything.
For anything requiring full-throttle work, use a road where that is legal and safe, or bring a passenger to handle the device.
What a log is worth at a workshop
A great deal, and more than a description.
“It hesitates sometimes” is a starting point. “Here is a log where rail pressure falls from 1400 to 900 bar under full load at 3200 rpm, repeatable” is a diagnosis someone can act on.
How to read a workshop quote and walking into a workshop with your own data.
You can check this yourself. Pair an ELM327 adapter, open the free tier of the app and record one baseline drive while the car is healthy. That file is worth more than any log you take after something goes wrong.
Comments …
Loading…