Introduction
A modern car contains several electronic control units. They control the engine, transmission, brake system, airbags, climate, body electronics and other systems. When a unit detects a value or event outside the intended limits, it can store a diagnostic trouble code.
Diagnostic equipment reads these codes and helps identify which system to inspect. It significantly reduces search time, but the code itself does not always point to a single faulty part.
What the code means
The code shows which unit registered the problem and which circuit, sensor, actuator or parameter it relates to. For example, a sensor fault code may be caused not only by the sensor itself, but also by damaged wiring, a poor contact, missing power, a mechanical fault or incorrect values from another related system.
Correct diagnostics therefore starts with reading the code and the stored freeze-frame conditions, and continues with checking live parameters and the physical condition of the vehicle.
Why some codes are intermittent
Some codes appear once and never come back after clearing. Possible causes:
- discharged or weak battery
- brief voltage drop during cranking
- disconnecting or reconnecting the battery terminal
- temporary loss of communication between units
- unplugging a connector during a repair
- a single sensor reading outside the allowed range
Such a code does not always mean that a part has to be replaced immediately. It is important to check whether the code is active, when it appeared and whether it returns after clearing.
Recurring and permanent codes
A recurring or intermittent code may appear only under specific conditions: with a cold engine, under load, while driving, when moisture is present, or with temperature changes. Finding such a fault often requires observing Live Data and re-testing the vehicle.
A permanent code usually returns immediately or shortly after clearing. If the root cause has not been fixed, simply clearing the code does not repair anything. Wiring, a sensor, an actuator, the control unit itself or the mechanical part of the system has to be checked.
Clearing a code is not a repair
Clearing wipes the record from the unit's memory but does not remove the physical cause of the fault. It is recommended to write down the code and its related data before clearing, especially if the fault appears rarely.
After a repair, the codes are cleared again and the system is checked to see whether they come back. If the code does not return and the parameters are normal, this helps to confirm the outcome of the work.
Which equipment to choose
A simple OBD2 adapter is often enough for basic engine and emissions code reading. Actual capabilities depend on the car and on the software used.
Access to AT, ABS, SRS, climate, body electronics and other units usually requires a brand-specific interface or a multi-brand scanner with extended support for the particular vehicle.
Before buying, decide whether you need to read only the engine unit or all available units of the car.