OBD and troubleshooting on the modern car
From error code to cause — how you work systematically
Modern cars are filled with control units and sensors that constantly monitor engine, exhaust and safety systems. As a car mechanic, your task is not just to read an error code but to understand what the code tells you — and what it doesn't tell you. The error code is a clue, not a solution manual.
§What is OBD?
OBD stands for On-Board Diagnostics—the car's built-in self-diagnosis. When a control unit registers a value outside the expected range, it stores a fault code (DTC, Diagnostic Trouble Code) and often lights the engine control light. With a diagnostic tool connected to the car's socket, you can read the codes, see current measured values (live data), and in many cases activate components to test them.
§The error code is a symptom, not a diagnosis
A classic error is going directly to product presentation without first uncovering the customer's real needs.
Systematic procedure
- 01Listen to the customer's description — when does the fault occur, cold or warm, under low or high load?
- 02Read off all stored codes and note them down before you delete anything.
- 03Look at live data and freeze frame data showing the car's condition when the error occurred.
- 04Make a full run-through of the entire process, preferably with a model, before the actual test day.
- 05Confirm the repair by deleting the code, test drive and check that it does not return.
§Measure rather than guess
A multimeter an oscilloscope and the diagnostic tool's live data are your most important tools. When you measure voltage resistance and signals directly on the component and its connector you can determine whether the fault is in the component in the wiring network or in the control unit. This is the difference between a mechanic who repairs and one who replaces on chance.
“The one who does not measure guesses — and guessing costs the customer money.”
— Workshop principle