P200200 on an Audi: how to read the VAG six-character code

Why VAG tools show six characters, not five

A normal OBD-II code has five characters. A letter for the system, then four digits. Your cheap code reader shows P2002. A VAG tool shows P200200. It looks like a different code, but it is not.

Modern VAG control units follow a diagnostic standard that lets a code carry a third part. That part is called the fault-type byte, or failure type. It is written as two extra characters on the end. The first five characters say what is wrong. The last two can say how it is wrong.

This is why you may see a fault listed twice in a long scan, once as a five-character code in the generic list and once as a six-character code in the manufacturer list. Treat them as one fault. Do not pay for two repairs because a report prints two lines.

What the extra byte actually tells you

Most Audi owners only ever see 00 on the end. That is normal for P200200, but it helps to know the other values exist.

• 00 means no sub-type is given

  On P200200 the byte is 00. The control unit is reporting the base fault only. It is not hiding a second problem. The useful detail lives in the status bits and the freeze frame, not in the byte.

• Other values narrow the failure mode

  On some codes the byte reads 01, 11, 1C or similar. These can mean signal too high, signal too low, a circuit fault or a plausibility failure. The meaning depends on the code family, so always read it against the code it sits on.

• Do not search for a different fix by byte

  A forum post about P200200 is about the same fault as one about P2002. If the byte differs from yours, check you are reading about the same sensor or system before copying a repair.

• Older tools may show a five-digit VAG number

  Very old VCDS and VAG-COM sessions list a number such as 16394 beside the P code. That is the older internal fault number for the same fault. It is not a separate problem.

The same code on VW, Skoda and SEAT

P200200 reads the same on a Golf, Octavia, Leon or Passat as on an A3 or A4. The group shares engines, particulate filters and the differential pressure sensor, so the code means the same thing across the badges.

What changes is the exact part and the engine family. A 2.0 TDI EA288 in an Audi A4 has the same style of filter control as a Skoda Superb with that engine. A repair worked out on one often carries across to the other. We still check each car on its own live data, because pipe routing and sensor position differ by model.

Our focus here is the Audi, but if you drive a VW, Skoda or SEAT, the steps on this page apply to you too.

Companion codes you will see next to P200200 in VAG format

A single P200200 on its own is useful. P200200 with company tells us far more. These are the ones we meet most often.

• P246300: soot accumulation too high

  The ECU thinks the filter holds more soot than it should. It often comes first, then a failed regeneration, then P200200 after a repair attempt. It points to a loaded filter, a short-trip pattern or an EGR that makes too much soot.

• P245300: DPF pressure sensor range or performance

  The differential pressure sensor signal looks wrong. A sensor fault, a split pipe or a blocked pipe can all do this. Together with P200200 it makes the sensor side the first place to look.

• P040100: EGR flow insufficient

  The EGR is not moving the gas the ECU asked for. A carboned valve is the usual cause. Extra soot from a poor EGR is a common route to P200200 a few weeks later.

• P242F00: ash accumulation too high

  A different life-limit warning. The filter is full of ash, which does not burn. Regeneration cannot clear it. The fix is cleaning or replacement, not software.

Static, intermittent and what the status bits say

Next to each stored code, VAG tools show a status. The two words you will meet most are static and intermittent (VCDS calls it sporadic). They matter more than most owners expect.

Static means the fault was present on the last check. It is active now. That tends to point at a real, ongoing cause, such as a failed sensor, a split pipe or a cracked core.

Intermittent means the fault was logged but is not present right now. It may need heat, load or a certain engine speed to show. A pipe that opens up when hot, or an EGR that sticks only on a cold start, are classic examples.

Clearing an intermittent code and hoping is a common mistake. The ECU resets its counters, the car feels fine for a week, and the fault returns. We read the status first, then try to recreate the conditions.

How to read freeze frame on a P200200

Freeze frame is a snapshot of the engine at the moment the fault was stored. It is the closest thing to a witness statement.

• Mileage and time since the fault

  Tells you whether the fault is new or has been stored for months. An old fault with a fresh light often means a second problem has arrived.

• Engine speed, load and coolant temperature

  A fault stored at idle with a cold engine points somewhere different from one stored at motorway speed when hot.

• Exhaust gas temperatures

  If the temperatures were high, a regeneration was probably running. A fault logged during a burn suggests a cracked core or a leak, not a simple sensor drift.

• Differential pressure reading

  A very low figure at high load is the classic sign of gas escaping around the filter or a false signal from the sensor.

P200200 sits in the DPF, but the EGR often starts it

The code belongs to the DPF. It judges the filter's efficiency. But the EGR sits earlier in the chain and decides how much soot reaches the filter, so an EGR fault can bring the DPF code on.

AdBlue is a third, separate system for NOx. P200200 is not an AdBlue fault. If your dash also shows an AdBlue warning, that is a different job, and we can handle it in the same visit.

How we handle a P200200 on site

We work from the code outward. The code tells us where to start. The data tells us where it ends.

• Full-system scan in VAG format

  We pull all modules, not only the engine. Faults in other units, such as a low voltage event, can explain odd sensor behaviour.

• Record status and freeze frame first

  We save the screen before touching anything. This is the evidence the rest of the job is judged against.

• Check companion codes as a group

  P246300, P245300 and P040100 each tell a different story. Seen together they usually point to one cause.

• Live data against known good values

  Pressure across the filter, exhaust temperatures, soot mass and EGR position, compared with what a healthy engine shows.

• Retest after the repair

  We clear the fault and drive until the ECU runs its own monitor again. A code that stays away through that cycle is a fixed code.

What happens after we read your P200200

You get a fixed price before work starts. We are mobile, so the whole job happens where the car is parked.

Reading the code is the easy part. Most of the value is in the order we test. Pipes and sensor first, EGR second, filter last. That order keeps the bill low and avoids replacing a good filter.

• Pipes and sensor

  Replace split or swapped pipes and fit a new sensor if it fails the bench-style checks we run on the car.

• EGR and soot source

  Clean or replace the valve, fix the cause of the soot, then reset the counters.

• Service regeneration

  A controlled burn when the filter is healthy but loaded.

• Filter replacement

  Only when the core fails tests. We adapt the new part and reset the ash and soot values.

• Mobile code read, diagnosis and simple fix: From £249 Full VAG scan, status and freeze frame review, and fixes such as a pipe or forced regeneration.
• Sensor or EGR repair: Fixed price after diagnosis Quoted once live data proves which part has failed.
• Filter replacement: Fixed price after diagnosis Offered only after every cheaper cause is ruled out.

Software and P200200

Software can help with a P200200, but only some kinds are suitable for the road.

• Dealer updates and adaptations (road legal)

  After a new sensor or filter, VAG needs a basic setting and a reset of the stored values. Without it the code can return straight away. We run these on every job.

• Service regeneration (road legal)

  Run from the tool with the car stationary and watched on temperature. It clears a loaded filter but cannot repair a damaged one.

• Off-road DPF and EGR software

  For vehicles that will never use UK public roads, such as competition or export cars, we can supply off-road DPF and EGR software. It is for off-road, competition or export use only, and it is never a road-legal fix.

The legal position on DPF and EGR software, plainly

Since February 2014 the MOT tester checks that a diesel which left the factory with a particulate filter still has one. Since May 2018, visible smoke of any colour from a DPF-equipped diesel is a major fault.

Using a vehicle on a UK public road with its emissions controls switched off or altered is a separate legal issue under the Road Vehicles (Construction and Use) Regulations. Passing an MOT does not make it lawful, and insurers may treat an undeclared change as a modification.

So we repair the fault first and we say this before any software work is discussed. Software that changes DPF or EGR operation is only for vehicles that will not be used on UK roads.

P200200 questions

Why does my scanner say P2002 but the garage says P200200?

Both describe one fault. The garage tool shows the VAG six-character form, where the last two characters are the fault-type byte.

What does the 00 at the end of P200200 mean?

It is the fault-type byte. A value of 00 means the unit gives no extra sub-type. The detail you need is in the status and freeze frame.

Is a static P200200 worse than an intermittent one?

A static fault is active now, so the cause is usually present and easy to find. An intermittent one needs conditions to recreate it, which can take more testing.

Can I clear P200200 myself and carry on?

You can, but if the cause is still there the code returns, and you lose the stored freeze frame we would use to find it. Read it first.

Does P246300 with P200200 mean a blocked filter?

Not always. It means the ECU believes soot is high. A false pressure signal can cause that, so we confirm with live data before blaming the filter.

Is P200200 an AdBlue code?

No. It belongs to the particulate filter. AdBlue faults use different codes and a different system, though we can check both on one mobile visit.