Clearing a fault code yourself

Clearing a code takes ten seconds with an OBD2 adapter. Doing it at the right moment takes a little more thought: clearing repairs nothing, and it also erases things you may want to keep.

What clearing really does

The OBD2 clear command deletes the stored codes, the pending codes and the freeze frame — the snapshot of engine conditions at the moment of the fault. It switches the light off.

It also resets the diagnostic monitors: the self-tests the control unit runs while driving on the converter, the sensors, the evaporative system, the EGR. They go back to “not ready” and only revalidate after a certain distance under specific conditions.

It does not erase everything: on recent vehicles, a “permanent” code stays recorded until the control unit has rerun the test itself and found the fault gone. That is deliberate: it stops a fault being hidden with a single tap.

When it is justified

After a repair. You have changed the spark plug, the sensor, the fuel cap: the light stays on until someone switches it off, or for several drive cycles before it goes off by itself. Clearing confirms the repair holds: if the code does not return, it is fixed.

As a diagnostic method. An old code, which may or may not still apply, gets cleared to see whether it returns — and under what conditions. Note it first.

After a false alarm. Fuel cap left off at the station (P0455), battery disconnected, sensor plugged back in: the fault no longer exists, the light just does not know yet.

When not to

Right before the roadworthiness test. The reset monitors are read by the inspector; depending on the country, a vehicle whose monitors are not ready is failed or sent back. Allow several dozen kilometres of varied driving — town, open road, cold then warm — for them to revalidate, sometimes several days.

Before reading and noting. The code and its freeze frame are the information; the light is only the messenger.

When the light is flashing. A misfire in progress is not cleared, it is repaired — see Check engine light on: what to do.

To sell. The code returns at the first opportunity, and a buyer with an adapter will see “not ready” monitors that betray a recent clear.

How to do it

Ignition on, engine off, unless the manufacturer says otherwise. Plug in the adapter, open the app, read the codes first and note them — Klaro lets you share a code's page in one gesture.

Run the clear. The light goes off immediately, or on the next start. Then drive normally: if the code returns in the following days, the fault was not the one you thought, or not repaired.

In Klaro, clearing is the Pro version's feature; reading codes and live data stays free.

The code comes back

That is the useful information. Either the repair did not address the real cause — a P0420 returning on a new converter often has a sensor or a misfire behind it —, or the fault is intermittent and waiting for its conditions.

Look at the pending codes: they appear before the light comes back on, and say which of the faults is recurring.

How long before the monitors are ready

A complete “drive cycle” starts with a cold engine, includes idling, town driving and a stretch at steady speed, and ends with the engine warm. Some monitors revalidate in one cycle; others — evaporative, converter — need several, with constraints on fuel level or outside temperature.

In practice: 50 to 150 km of varied driving over two or three days. If you cleared by mistake before a test, drive, then check with the inspector's tool or a workshop that the monitors are ready.

What you need

An OBD2 adapter — see Which adapter to choose — and Klaro. Read, note, repair, then clear. In that order.