Clearing codes: when it helps and when it hurts

“Clear faults” is the most tempting function on any scanner: the lamp goes out and the car looks healthy. The problem is that the code takes information with it that is worth more than the lamp.

What disappears with the code

The freeze frame — a snapshot of conditions when the fault set: revs, load, temperature, speed, trims. The most valuable thing in diagnostics, and it is erased with the code; covered in the freeze frame article.

Readiness monitors. Clearing resets them all, and they need several complete drive cycles to return; covered in the readiness monitors article.

History. How many cycles the code was active and whether it repeated — the context that says whether this was a one-off event or a process.

Adaptations — on some cars clearing codes also resets learned corrections, after which the car drives worse for a while than it did before.

When clearing is appropriate

After a repair — to check whether the code returns. That is the verification itself.

After eliminating a one-off cause — for instance a tank of bad fuel, where the cause is understood and gone.

During swap-based diagnosis — swap the coils, clear, drive, and see whether the code moved. Here clearing is part of the method; covered in the ignition coil article.

To check whether a code is currently active — clear it and see whether it returns immediately.

When not to clear

Before recording the code and freeze frame. The main rule: save first, clear second.

Before a workshop visit. You will arrive with a car showing no symptom, and the mechanic will have to wait for it to recur. That lengthens the repair and increases the bill.

Instead of a repair. The lamp goes out, the cause remains, and with active misfires the catalyst carries on destroying itself.

Before selling. The worst practical case: a buyer with an adapter sees reset monitors in a second and draws the obvious conclusion; covered in the selling preparation article.

Before an annual test. The monitors will not have time to return, and the test fails for exactly that reason; covered in the test preparation article.

What to do instead

1. Record every code — including pending ones.
2. Save the freeze frame — a screenshot or a written record.
3. Note the symptom — when, under what conditions, how often.
4. Read live data in the regime where the symptom appears.
5. Fix it.
6. Then clear — to verify the result.

About permanent codes

Modern cars have a category of codes that a scanner cannot clear at all. They disappear on their own once the system is satisfied the fault is gone — after several successful cycles.

That exists precisely to defeat clearing before an inspection. So “preparing” a modern car by clearing does not work, by design.

In short

• The freeze frame disappears with the code — the most valuable part of the information.
• Record first, clear second; never the reverse.
• Clearing before a workshop visit lengthens the repair and raises the bill.
• Reset monitors are visible to a buyer or an inspector in a second.
• Permanent codes cannot be cleared by a scanner — deliberately.

Download the app — codes, freeze frames, and monitors are read with an ELM327 adapter over Bluetooth SPP on Android.