How to clear a fault code properly (and when not to)

Clearing a fault code deletes the record of a problem. It does not fix the problem. So the honest answer is: fix the fault first, then clear the code, then drive the car and re-scan to confirm it stays gone. If you clear before you've fixed anything, one of three things happens - the light comes straight back, the light stays off for a few days and then returns, or the module simply refuses to clear because the fault is happening right now. And before you clear anything, write down what the code was: the moment you erase it, you also erase the stored conditions that would have told you what went wrong.

What clearing actually does

Every control module in a VW, Audi, Skoda or SEAT - engine, gearbox, ABS, airbag, climate, gateway, and a couple of dozen others depending on the car - keeps its own small fault memory. When a module's self-tests spot something outside the expected range, it writes an entry into that memory and, if the fault affects emissions or safety, lights a lamp on the dash.

Sending an erase command wipes those stored entries. That is all it does. It does not repair a wire, reseat a connector, replace a sensor or regenerate a diesel particulate filter. The module carries on running exactly the same self-tests it was running a minute ago, and if the condition is still there it writes the entry back - sometimes within the same key cycle, sometimes within seconds.

This is worth being blunt about because a cleared code is often read as good news. It isn't news at all. The only informative moment is the re-scan after the car has been driven: if the fault is genuinely gone, that scan comes back clean; if it isn't, the same entry reappears, and on modules that report fault status it will usually show as present rather than historic - which tells you the condition is live right now.

Read and save everything before you clear

A VAG fault entry is usually richer than the short code number most people quote. Depending on the age of the car and the module, you may also get a description, status information (whether the fault is present now or was present in the past), a counter showing how many times it has occurred since the memory was last emptied, a mileage or time stamp for when it was last seen, and a set of environmental conditions captured at the moment of the fault - things like coolant temperature, engine speed, load and vehicle speed. On emissions faults this is the freeze frame, and it is often the single most useful thing on the screen. Older modules store much less than newer ones, so take what the car gives you.

Clearing throws all of that away. If you clear first and diagnose second, you have just deleted the evidence and you will be waiting for the fault to happen again before you can look at it properly. Save a full scan report - every module, not just the engine - before you touch the erase button. A photograph of the screen is better than nothing; an exported report is better still.

This is also where tool choice matters, because a generic code reader only sees the emissions-related engine codes and will happily tell you the car is fine while the ABS and airbag modules are both storing faults. VAGPULSE scans every module and lets you clear one module at a time rather than wiping everything at once, which is what you want when you are trying to work out which faults were knock-on effects of the one you just fixed.

Why some modules refuse to clear

It is very common to send an erase command, watch the tool report success, and find the fault still sitting there on the next read. That is usually not a tool problem. Most VAG modules distinguish between a fault that is present right now and one that has been recorded in the past, and while the condition is live the module re-registers it immediately after the memory is emptied. From the outside it looks like the clear failed. In practice it worked, and then the fault came back before you could blink.

Some modules go further and decline the request outright while the fault is active, particularly on safety systems. Others will only accept an erase under specific conditions - ignition on with the engine not running, or after the tool has completed a security handshake with the module. And some entries are not really fault codes at all: crash data in an airbag module, for example, is held deliberately, and after an actual deployment the control unit and the deployed components normally have to be replaced rather than reset.

On cars new enough to support them, there is also a category of emissions fault that cannot be cleared by any tool at all. These permanent codes are erased only by the car itself, once the engine management has re-run the relevant self-test and genuinely passed it. They exist precisely to stop a fault being hidden with a scan tool before a test. If one is present, no amount of clearing will move it - only a real repair will.

Where clearing is the wrong move entirely

Some warnings should not be cleared and forgotten, because the system behind them may be partly or wholly disabled while the fault is stored.

With any of these, the code is a symptom. Clearing it changes the dashboard and nothing else.

• Airbag and seatbelt pretensioner faults. An SRS light usually means the system has taken itself out of service - it may not deploy in a crash. Get the cause diagnosed. Work on pyrotechnic components needs the battery disconnected and a proper stand-down period before anything is unplugged, and airbag circuits must never be probed with a multimeter. After a deployment, the affected parts are replaced, not cleared. This is not a place to experiment.
• ABS, ESP and brake-related faults. Clearing does not restore anti-lock or stability control, and after work on the hydraulic system many VAG cars need a guided bleed or basic-setting routine rather than a simple erase.
• Steering angle, level and calibration faults. These generally need a calibration procedure carried out properly, often with the car set up in a specific way. Clearing them alone achieves nothing and the fault returns on the next self-test.
• Immobiliser and key faults. Anything involving the immobiliser is legitimate work on your own vehicle, but it needs a franchised dealer or a reputable auto locksmith with the right credentials and proof of ownership. It is not a clear-the-code job.
• Diesel particulate filter and emissions warnings. Soot loading and adaptation values are calculated by the ECU; erasing a fault does not reset them, and a filter that needs regenerating or replacing still does.

After you clear: drive cycles and readiness

Once a genuine repair is done and the codes are cleared, the car does not immediately declare itself healthy. The engine management runs a series of self-tests - catalyst efficiency, oxygen sensor operation and heating, evaporative emissions on petrol cars, EGR and particulate systems on diesels - and each has its own conditions before it will run. Some need a proper cold start after the car has stood long enough to cool right down. Some need a steady cruise at a settled speed. Some need a period of overrun with your foot off the throttle. The evaporative test on petrol cars typically won't run unless the fuel level sits within a particular window, which is why a car that lives on a quarter tank or is always brimmed can take a long time to complete it.

Until each of those tests has actually run, its readiness status stays incomplete. Clearing codes resets all of them to not-yet-run. That is the real cost of an unnecessary clear: you have blanked the car's own record of what it has verified about itself, and it takes a mixture of driving - town, open road, cold starts, a few days rather than a few miles - to build it back up.

If the warning lamp was lit, it also does not go out the instant you clear. On an emissions fault the lamp normally extinguishes by itself after several consecutive fault-free drive cycles, and the stored code self-erases after a few dozen warm-up cycles even if nobody touches it. A lamp that goes out on its own after a repair is a much stronger signal than one you turned off with a tool.

Battery disconnection and other shortcuts

Disconnecting the battery to clear fault codes is a habit left over from much older cars, and on a modern VAG vehicle it mostly doesn't work. Fault memories are held in non-volatile storage and survive the power cut, as do most learned adaptations - throttle and transmission values are generally retained too, so the old advice about 'resetting the ECU' no longer applies the way it once did. What you can lose is clock and radio settings, one-touch window operation and other convenience functions that need re-initialising, and on some cars specific adaptations that then have to be re-learned or re-set with a tool. Dropping the voltage across the whole car can also set fresh undervoltage faults in modules that didn't have any, so you may end up with more entries than you started with. And a battery disconnect is not a trivial operation in its own right on a car with airbags: it needs a stand-down period before anything else is disturbed.

The other shortcut worth naming is clearing repeatedly and hoping. If the same code comes back three times, the third clear tells you nothing the first two didn't - and each clear destroys the status, counter and stored conditions that would have made the fault easier to pin down. It also leaves a recognisable trace: a scan showing no stored faults but every readiness monitor incomplete is the classic signature of a car that was cleared very recently, and an experienced buyer or garage will read it that way.

There is nothing wrong with clearing as a diagnostic step, though - it is standard practice. Clear, drive under the conditions where the problem shows up, re-scan, and see exactly what returns and what doesn't. That turns a pile of historic entries into a short list of live ones, which is genuinely useful.

Before a sale or a test: the honest bit

Clearing codes so a warning light stays off long enough to sell a car, or long enough to get through an MOT or emissions test, is deception. It is worth saying plainly rather than dressing up. If you know the car has a fault and you present it to a buyer as fault-free, you are misrepresenting it - and 'sold as seen' does not protect a seller who has actively hidden something. In most jurisdictions it is unlawful for a trader under consumer protection law, and for a private seller it is still a misrepresentation the buyer can pursue you over.

The same applies to a test. On most cars of testable age the tester checks that the engine management lamp works and is not indicating a fault. Turning that lamp off on the morning of the test is not preparing the car; it is concealing a defect from the person whose job is to find it. Practically, it also tends not to work: some testing regimes check readiness monitors and will reject a car whose monitors are incomplete after a recent clear, permanent emissions codes on cars that support them cannot be cleared at all, and a fault serious enough to light the lamp usually lights it again quickly.

What is completely legitimate is clearing historic entries that you know are already resolved - codes logged during a battery change, a repair you have just completed, or a sensor that has been replaced. If you are selling, the genuinely strong move is the opposite of hiding: fix what you can, then hand the buyer a full scan report showing every module clean. That is far more persuasive than a dashboard with no lights on, and it costs you nothing but honesty.

A sequence that actually works

Put together, the whole thing is short:

• Scan every module and save the report - codes, status, any occurrence counts and stored conditions, not just the code number.
• Diagnose using that information. Freeze frame conditions, where the module stores them, usually point at when and where the fault happens.
• Fix the cause. If it is airbag, brake, steering or immobiliser related, or you are not sure, get it looked at properly.
• Clear the codes, starting with the module that holds the root fault. Knock-on faults in other modules often disappear once the source is cured.
• Drive the car normally for a few days, including at least one proper cold start and a mix of town and open-road driving.
• Re-scan. A clean scan after real driving is the only version of 'it's fixed' worth trusting.

Common questions