Audi fault codes explained: what your engine warning light is telling you

If the engine warning light has appeared on your Audi and a scanner has handed you a code, the obvious next question is what that code means and how much it is going to cost. Audi fault codes are genuinely useful, but they describe a symptom rather than a failed part. This article covers what the codes are, how the car decides to store one, what two real codes from our Audi list actually point to, and when it is worth having the car tested properly rather than guessing.

What an Audi fault code actually is

Every modern Audi runs a set of self checks in the background while you drive. Control units monitor sensors, actuators and system outputs against the values the software expects to see. When a reading sits outside that expected range, and stays there long enough to rule out a one off glitch, the control unit stores a diagnostic trouble code and usually illuminates the engine warning light.

Codes beginning with P relate to the powertrain, which covers the engine, fuel system, emissions control and gearbox. The code itself is a reference number tied to a description, such as an oxygen sensor circuit reporting low voltage. Alongside the code, the control unit stores a snapshot of running conditions at the moment the fault was logged. That snapshot, often called freeze frame data, records things like engine speed, coolant temperature and load. It frequently tells a technician more than the code does.

Audi also stores manufacturer specific codes that a basic scanner cannot see. A generic reader plugged into the diagnostic port will show standard emissions related faults, but it will not show most gearbox, chassis or comfort system faults, and it will not show the extended data that dealer level software reads.

Why the code is a starting point and not an answer

A fault code names the circuit or the monitor that reported a problem. It does not name the component that failed. This distinction is where most wasted money goes.

Take a mixture fault as an example. The engine can report a lean condition because of a split intake hose, a leaking crankcase ventilation system, an injector not delivering correctly, a failing high pressure fuel pump, or a mass airflow sensor reading low. Every one of those produces a similar stored code. Fitting the part named in the code description is a coin toss, and on an Audi it is an expensive one.

Structured diagnostics closes that gap. Live data shows what the sensors are reporting while the engine runs. Comparing those readings against known good values, checking wiring and connectors, and looking at how the fault behaves under load is what turns a code into an actual diagnosis.

Two examples from our Audi fault code list

Two codes from our list show how much interpretation sits behind a single number. Audi fault code P013100 refers to the oxygen sensor circuit on bank 1, sensor 1, reporting low voltage. The pre catalyst sensor is the one the engine uses to trim fuelling, so a fault here affects running quality and emissions. The sensor itself is one possible cause. So is damaged wiring, a poor earth, a connector that has taken heat from the exhaust, an exhaust leak upstream of the sensor drawing in air, or a genuinely rich mixture caused by something else entirely. The code tells you where to look, not what to buy.

Audi fault code P00C600 refers to fuel rail pressure being too low while the engine is cranking. Drivers usually notice this one as a long crank before the engine catches, particularly first thing in the morning. Possible causes include a weak low pressure supply from the in tank pump, wear in the high pressure pump drive, a leaking injector bleeding rail pressure back overnight, or a fuel pressure regulator not holding. Those repairs vary enormously in cost, which is exactly why pressure testing matters before anything is replaced.

What happens if you just clear the code

Clearing a code with a scanner switches the light off. It does not repair anything. The control unit reruns its monitors, and if the underlying fault is still present the code returns, usually within a few drive cycles.

Clearing also wipes the freeze frame data. That is the part people underestimate. You have removed the evidence of the conditions the fault occurred under, which makes the next diagnosis harder and often slower. If the light comes on, it is worth having the codes read and recorded before anything is erased.

There is also the MOT to think about. An engine warning light that is illuminated and indicating a fault counts as a failure item under the current MOT rules, so an ignored light tends to catch up with you eventually.

When to keep driving and when to stop

A steady engine warning light generally means the car has logged a fault worth investigating soon, and in most cases the vehicle can be driven carefully to a garage. A flashing engine warning light is different. It usually indicates a misfire severe enough to risk damaging the catalytic converter, and continuing to drive can turn a coil pack into a catalyst replacement. Pull over safely and arrange recovery.

Red warning lights are a separate matter entirely. Oil pressure and coolant temperature warnings mean stop as soon as it is safe to do so, regardless of what any fault code says.

How we diagnose Audi faults at VGS Performance

We use dealer level diagnostic platforms including ODIS and VCDS, which read the full range of control units on an Audi rather than the limited emissions set a generic reader picks up. That means we can see stored codes across the engine, gearbox, ABS, electronics and comfort systems, along with measured value blocks and adaptation data.

From there the process is structured rather than speculative. We read and record all stored codes and freeze frame data, check live values against expected ranges, test the wiring and connectors in the affected circuit where the readings suggest it, and confirm the cause before quoting for any repair. You can read more about how we approach this on our dealer level diagnostics page, and our full Audi OBD fault code list covers the individual codes in more detail.

Frequently asked questions

Will an Audi fault code clear itself?

Some will. If the fault was a one off and the control unit runs its monitor successfully over several drive cycles without seeing the problem again, the light can go out on its own and the code becomes a stored historic fault. A code that returns after clearing points to a live fault that needs testing.

Can I drive my Audi with the engine warning light on?

A steady light usually means you can drive to a garage, keeping the revs and load sensible. A flashing light means stop and arrange recovery, because it normally indicates a misfire that can damage the catalytic converter within a short distance.

Does a fault code mean I need a new part?

Not necessarily. A code identifies the circuit or system reporting a problem, not the component that failed. Wiring damage, connector corrosion, air leaks and software issues all produce codes that name a sensor. Testing before replacing avoids paying for parts that were never faulty.

Getting your Audi checked in Swindon

If your Audi has an engine warning light on, or a scanner has given you a code you want interpreting properly, we can test it and tell you what is actually wrong.