#live data
8 posts in Car Diagnostics blog about "live data" — OBD-II diagnostics, DTC codes, repair. ← All posts
-
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.
-
From raw bytes to readable numbers: how PID formulas work
Your app shows 87 °C. The car sent the byte 0x7B. The conversion between them is defined by the standard, and knowing it explains some odd readings.
-
Freeze frame or live data: which one answers your question
One is a photograph of the moment a fault occurred, the other is a film of what is happening now. Choosing the wrong one is why people stare at healthy numbers for an hour.
-
OBD-II Mode 01: current data and the PIDs that matter
Mode 01 is the live feed every OBD-II car supports. Knowing which of its hundred-odd parameters are worth watching turns a list of numbers into a diagnostic method.
-
Reading live data as graphs: spotting the fault in the shape
A number tells you a value; a graph tells you a behaviour. Most sensor faults are visible in the shape of the trace long before the value goes out of range.
-
Live data: five parameters worth learning to read
Codes tell you the system noticed a deviation. Live data tells you what is happening now. Five parameters to start with.
-
Why your scanner shows fewer parameters than the next car: how supported PIDs work
Somebody else sees boost pressure and oil temperature; you see RPM and speed. That is not an app limitation — the car itself declares which parameters it will hand over, and the list differs from vehicle to vehicle.
-
MAF and MAP Sensor OBD-II Diagnostics: P0100, P0105, P0171 via Live Data
How to distinguish MAF sensor fault from MAP, vacuum leak, or clogged air filter via OBD-II Live Data: P0100, P0101, P0105, P0171 — step-by-step algorithm without blind replacement.