The check engine light and OBD fault codes

The check engine light, properly the malfunction indicator lamp, is the most misunderstood signal on a dashboard. Owners treat it as either an emergency or as background noise, and it is neither. It means the car has stored a fault code that it considers relevant to emissions or engine management. It does not tell you how serious that is, and it does not tell you what is broken.

When the light comes on

The engine controller constantly compares sensor readings against expected ranges. When something sits outside its range for long enough, or fails a self-test twice, a code is stored and the lamp is lit. That covers a very wide span of seriousness, from a fuel cap that was not tightened properly to a failing catalytic converter.

The distinction that actually matters is how the lamp behaves. A steady lamp is a stored fault you should investigate without panic. A flashing lamp normally indicates misfire severe enough to send unburnt fuel into the exhaust, which can destroy the catalytic converter quickly. That one is not a next-week job.

What a scan gives you

Plugging into the diagnostic port gives more than a code list, and the extras are the useful part:

• Stored codes, both confirmed and pending.
• Freeze frame data, a snapshot of conditions at the moment the fault was recorded, such as engine speed, load and coolant temperature. This tells you whether the fault happens cold, hot, at idle or under load.
• Live readings, which let a technician watch a sensor behave rather than infer from a code.
• Readiness monitors, the self-tests described below.

How to read a code

Codes follow a standard shape: a letter for the area, then digits. P is powertrain, B is body, C is chassis and U is network or communication. So a code beginning with P relates to engine or transmission, and the digits narrow it to a subsystem and a specific condition.

The important discipline is not to translate a code straight into a part. A code describing an oxygen sensor circuit does not mean the sensor has failed. It means the reading was implausible, and the cause is frequently an unmetered air leak, an exhaust leak or a fuelling problem that the sensor is correctly reporting. Replacing the named part is the most common way to spend money without fixing anything.

Active against pending

A pending code means the fault was seen once and not yet confirmed by a second identical test. An active or confirmed code has failed twice and usually lights the lamp.

For a buyer, pending codes are quietly valuable. A car can show a clean dashboard and still be carrying pending codes for a fault that is developing. Ask for the full scan output rather than a verbal summary, and look at that section specifically.

Readiness monitors, and the seller who cleared the codes

This is the part worth understanding properly, because it turns a common seller tactic into a finding.

Cars run periodic self-tests on emissions-related systems: the catalytic converter, the oxygen sensors, the evaporative system and others. Each of those is a readiness monitor, and each reports either complete or not complete. Completing them requires a mix of driving conditions over time, which is why a car cannot finish them in a five minute drive around the block.

Clearing stored codes resets those monitors. So the combination of zero stored codes and several monitors reading not ready is a strong indication that somebody cleared the memory shortly before you arrived. That is more useful to you than the code would have been, because it tells you both that there was a fault and that the seller preferred you not to see it. It is also worth knowing that a periodic roadworthiness test will typically not accept a car whose monitors have not completed, for the same reason.

What a service record adds

A code tells you what the car thinks right now. A record tells you whether this has happened before, which is often the more valuable question. The same fault appearing three times across two years, with a part replaced each time, describes a problem that was never actually diagnosed.

Where a workshop documented the job, that record is signed by the shop that issued it, and a shared snapshot can be checked to confirm it has not been altered since it was generated. Where work was done informally with nothing written down, there is no record to find, and the scan is all you have. That is a real limit rather than a detail. Check a report tests a snapshot you have been given, and finding a car's service history covers where records actually live.

What to do with all this

If you own the car: get it read rather than guessing, treat a flashing lamp as urgent, and keep the diagnosis rather than only the receipt, so the next fault can be read against it.

If you are buying: insist on a scan across modules rather than the engine alone, ask for the printout, read the pending codes, and check the readiness monitors before you accept that a clean dashboard means a clean car. The full pre-purchase sequence places this alongside the physical checks.