#CAN
6 posts in Car Diagnostics blog about "CAN" — OBD-II diagnostics, DTC codes, repair. ← All posts
-
ISO-TP (ISO 15765-2): how long diagnostic messages travel on CAN
A CAN frame carries eight bytes. A VIN is seventeen. ISO-TP is the layer that solves that, and understanding it explains several otherwise baffling adapter behaviours.
-
Car cybersecurity: why modern cars are stolen through electronics, and what an owner can do
Locks and alarms are no longer the main barrier. Modern theft is work on the vehicle network rather than on the doors. How the risk is structured, and which countermeasures genuinely work.
-
The LIN bus: half the car that never appears at the diagnostic port
Window motors, mirrors, the rain sensor, the alternator, the climate system — all of it lives on a second network, cheaper and slower than CAN. The OBD port cannot see it at all, which is why some faults "cannot be diagnosed".
-
U0100: lost communication with the engine module — and why the car still drives
The most common network code. Somebody on the bus stopped hearing the engine control module — and that almost never means the module itself has died. Causes from a voltage sag to a broken bus wire.
-
Odometer fraud: how OBD-II reveals rolled-back mileage when buying used
What OBD-II shows when the odometer says 50 000 mi but the real number is 150 000: ECU log audit, mismatch between ABS, ECM and cluster, motohours vs mileage, DTC history analysis.
-
5 OBD-II Protocols Explained in Plain English
ISO 9141-2, KWP2000, J1850 PWM, J1850 VPW, CAN — how they work, which cars use them, and why protocol support matters when choosing an adapter.