Check engine light on a VW or Audi: what to do first

Look at the light itself first. If it is flashing, stop driving as soon as you safely can, switch the engine off and get the car recovered — a flashing engine light means the engine is misfiring badly enough to damage the catalytic converter, and that damage builds the longer you drive. If it is steady amber and the car drives, sounds and smells normal, you are not in an emergency: drive gently, keep the load light, avoid hard acceleration and towing, and get the fault codes read in the next day or two. The light on its own tells you almost nothing about what is actually wrong — only reading the stored codes does that, and the order below is how to work through it without paying for the wrong part.

Steady or flashing: the one thing to check before anything else

VW, Audi, Skoda and SEAT follow the same engine management light convention as other makes built to modern OBD standards — the amber engine outline, usually called the MIL. Steady means the engine control unit has stored a fault it treats as emissions-relevant. Flashing means it is detecting a misfire severe enough to risk damaging the catalytic converter. If your car's handbook describes its lamps differently, the handbook wins.

The difference matters because the consequences are so different. A steady light might be a sensor that has drifted out of tolerance, and the car may run for weeks without getting worse. A flashing light is an active, ongoing event: unburnt fuel is passing into the exhaust and burning in the catalyst, where temperatures can climb well beyond what it was designed for. Catalytic converters are expensive, and a melted one can restrict the exhaust and cause further damage on top.

If it flashes, treat it as a stop-driving instruction. Pull over somewhere safe, switch off, and call for recovery. If it flashes only under load — accelerating, pulling a hill — and then settles to steady, the misfire is still happening; the car simply is not misfiring badly enough at idle to keep the lamp blinking. Do not carry on and hope.

What the light actually tells you, and what it doesn't

The engine management light is a single lamp reporting on a system with a great many monitored parameters. It tells you that the engine ECU has logged at least one fault. It does not tell you which fault, how serious it is, how long it has been there, whether it is one fault or six, or whether the part named in the code is the part that has failed.

That last point is what costs people the most money. A code is a description of a symptom the ECU noticed, not a parts order. A code pointing at a lambda sensor can be caused by an exhaust leak upstream of it. A lean-mixture code on a turbocharged petrol engine is very often a split hose or a failed seal letting unmetered air in, rather than the air mass sensor the code appears to blame. Fitting the part the code names, without working out why the ECU saw what it saw, is guesswork with a receipt attached.

The light also has a blind spot: it covers engine and emissions faults. VAG cars carry many other control modules — ABS, airbags, gearbox, power steering, climate, comfort and more — and a fault in those will not usually light the engine lamp. Those modules store their own codes, and a fault can sit in one of them for a long time, invisible, while the dashboard looks perfectly happy.

The other lights that turn up alongside it on a VAG

VAG dashboards use a few lamps that owners of other makes will not recognise, and they change what the engine light means.

EPC (Electronic Power Control) normally appears as the letters EPC in amber; some models use an engine-outline symbol instead, so check your handbook for the exact icon on your car. It relates to the drive-by-wire throttle and torque management side of things — throttle body, accelerator pedal sensor, brake light switch and similar. Seen together with the engine light it often comes with reduced power or limp mode: the ECU has deliberately capped power to protect the car, or because it no longer trusts a sensor. The car will feel gutless and may refuse to rev past a certain point. That is usually the car protecting itself rather than a second, separate fault appearing.

On many VAG diesels, a flashing glow plug light means an engine management fault has been stored rather than that the glow plugs themselves have failed — the lamp is reused as a general warning. Many diesels also have a separate DPF light, which normally asks you to drive steadily at speed so the filter can regenerate, rather than to stop. Your handbook sets out the procedure for your car; and if the DPF light shows up alongside other warnings, or with lost power, treat that as a fault to be read rather than something to drive off.

Red lights are a different category entirely. Oil pressure, coolant temperature and charging warnings mean stop now, whatever the amber engine light is doing. Amber says investigate; red says the engine may be being damaged as you read this.

The two-minute look before you spend anything

Before booking anything, do a short check on the driveway with the engine off and cool. You are not diagnosing; you are ruling out the cheap and obvious. Check the coolant level and the oil level. Look for anything clearly disconnected, split or hanging loose in the engine bay — on turbocharged petrol engines the plastic and rubber pipework between turbo, intercooler and inlet is a known weak point, and a split is often visible. Smell for fuel or hot coolant.

If you want to listen for a hiss or a change in engine note with the engine running, keep hands, clothing, hair and tools well clear of belts and cooling fans, which can start without warning. Check the fuel filler cap is properly seated and clicked home: on petrol cars a loose or perished cap can set an evaporative-emissions code and bring the engine light on with it. Diesels have no evaporative system, so that particular cause does not apply to them.

If any of that turns something up, note it — but do not clear the light yet. The stored data is worth more to you than a tidy dashboard.

Why a code reader is the only real way to know

There is no way to work out what the light means by looking at it, by how the car drives, or by matching symptoms online. You have to read the codes.

A cheap generic OBD reader will get you started, and it is far better than nothing. Its limits are worth understanding, though. It generally talks only to the engine module. It reads the standardised generic codes rather than the manufacturer-specific ones VAG relies on for detail. And while most readers will show some standardised live data, that is not the same as the VAG measuring blocks — the group readings — which are what tell you whether a sensor is genuinely faulty or is honestly reporting a problem somewhere else. A basic reader can come back with little or nothing to report while a VAG-aware tool finds manufacturer-specific codes, or codes sitting in modules the basic tool never speaks to at all.

That gap is what we built VAGPULSE for: Windows software and a cable that scan the other modules as well as the engine, and show live measuring blocks while the car runs. Whatever you use, the aim is identical — get the actual codes, in full, with their freeze-frame data, before anyone picks up a spanner.

The order to work through it

Work through it in this order. Each step is cheap, and each one narrows what the next step has to consider.

• Check whether the light is flashing. If it is, stop and get the car recovered. If not, drive gently and briefly.
• Rule out the red warnings — oil pressure, coolant temperature, charging. Those override everything else.
• Do the two-minute look: fluids, obvious splits or disconnections, fuel filler cap.
• Read the codes across every module, and save the freeze-frame data alongside them. That records the conditions at the moment the fault was logged — engine speed, load, temperature — and it is often the most useful clue you will get.
• Write down every code exactly as it appears, including the manufacturer-specific description, before clearing anything.
• Look at live data with the engine running, if your tool can. Compare what the suspect sensor reports against what the rest of the engine is doing.
• Fix the most likely root cause, not the part named in the code, where the two differ.
• Only then clear the codes, and drive the car in the way that would provoke the fault. If the code comes straight back, it is not fixed.

Clearing the code: when it's fine, and when it isn't

Clearing a code is a diagnostic step, not a repair. It is exactly the right thing to do after a fix, so you can see whether the fault returns. It is the wrong thing to do as a way of making a warning go away.

Be straight with yourself about that line. Clearing codes to make a car look healthy before selling it, or to slip a known fault past an emissions test, is deception — you are hiding a defect you know about from a buyer or a tester, and on a safety- or emissions-related fault that can be an offence as well as dishonest. It also rarely works. Clearing resets the car's internal self-check monitors, and until the car has completed enough driving for those checks to run again, the not-ready status is plain to see. In the UK, an illuminated engine management light is itself checked at MOT on the vehicles the rule applies to, so the honest route and the practical route point the same way. The scope depends on the vehicle, so check the current rules or ask your tester.

Resist the old trick of disconnecting the battery, too. On modern VAG cars it generally does not clear stored fault memory anyway, so it fixes nothing while potentially costing you freeze-frame detail and learned adaptations, along with throttle, window and stored convenience or radio settings. Clear codes deliberately, with a proper tool, once you know what they said.

When to stop and hand it over

Get the car to a garage rather than pressing on if any of these apply: the light is flashing; the car is in limp mode or has clearly lost power; there is a knocking, rattling or grinding noise; there is smoke, a strong fuel smell or steam; the temperature gauge is climbing; or the fault appeared immediately after work was done on the car.

There is also a set of jobs that is simply not owner territory, even with a good tool in hand. Anything touching airbags and seat-belt pretensioners can deploy them and cause serious injury. Anything touching ABS or the brake system affects whether the car stops — brake-system basic settings and bleeding routines belong with someone qualified to check the result. Steering angle and assistance systems affect whether the car goes where you point it. Immobiliser and key work, even on your own vehicle and with proof that it is yours, needs the correct equipment and in most cases an auto-locksmith or a dealer; get it wrong and the car will not start at all.

Reading codes from any of those systems to understand what is happening is fine and genuinely useful. Running actuator tests, basic settings or adaptations on them is not the same thing, and that is where you want somebody qualified, with the right kit and the right insurance.

Common questions