SCR diagnostics • Fault code list • Updated for 2026
AdBlue Fault Codes Master List: Complete Diagnostic Guide 2026
Your van rarely stops without warning.
It starts with a code, a light, or a countdown.
This guide helps you understand the code and choose the right next step.
Mobile across Leicester, Loughborough & surrounding Midlands • Mon–Sun 09:00–20:00
If you searched for an AdBlue fault codes list, you probably want one of two things.
You either want to keep driving without the van dropping into limp mode, or you need to stop a countdown before it hits zero.
The hard bit is not the code itself.
The hard bit is working out whether you have a fluid problem, a pressure problem, a sensor problem, or an electrical problem.
That is where this guide helps.
Table of contents
- How AdBlue fault codes work
- What to do first (and what not to do)
- Master fault code list table
- The “big four” codes you’ll see most
- Live data checks that prevent wrong repairs
- No-start countdown logic and why it returns
- Transit vs Sprinter vs Boxer patterns
- Repair vs delete decision framework
- Next steps
What this guide is not
It is not a parts list.
It will not tell you to buy a pump just because you saw “pressure” in a code description.
It is a diagnostic guide written for real-world van owners and fleets.
The goal is simple: stop repeat faults and stop no-start countdowns.
How AdBlue fault codes work
Your SCR system uses a few key inputs to decide whether it is reducing NOx properly:
- NOx sensor readings (upstream and downstream)
- AdBlue dosing commands (what the ECU asks for)
- Pressure and flow feedback (what actually happens)
- Temperature and heater circuits (to prevent crystallisation and freezing)
When one input looks wrong for long enough, the ECU stores a fault.
If the fault repeats across drive cycles, it usually escalates to warnings, limp mode, or a countdown.
Pending vs stored vs permanent
- Pending means it failed once but has not repeated enough times yet.
- Stored means it has repeated and the ECU now treats it as a real issue.
- Permanent means the ECU expects proof of a fix before it will clear it.
What to do first (and what not to do)
If your warning just appeared, you have a short window where good choices save money.
Bad choices turn it into a repeat issue.
Do this first
- Take a photo of the dashboard message and remaining miles if a countdown shows.
- Scan for codes and write them down before you clear anything.
- Check your AdBlue level and confirm you used correct fluid from a sealed container.
- If the fault appeared after refilling, note how long after the refill it triggered.
Avoid these common mistakes
- Clearing codes repeatedly without fixing the cause. It often speeds up countdown logic.
- Pouring in “cheap” fluid from an open container that has been sat in a garage.
- Assuming a new NOx sensor fixes everything. It depends on what the ECU sees.
- Ignoring the first warning because the van still drives. Many systems lock later.
A lot of vans come to us after someone cleared the code, the warning returned, and the next step was a countdown.
That is why the first scan matters.
Master fault code list table
This table covers the core SCR and AdBlue codes that turn up most in UK diesel vans.
Use it to understand the direction, then use the diagnostic sections below to confirm the cause.
| Code | Category | What it usually means | Common triggers | What to check next |
|---|---|---|---|---|
| P20EE | Efficiency | SCR NOx efficiency below threshold | NOx sensor drift, injector blockage, crystallisation, calibration/adaptation | Upstream vs downstream NOx readings, dosing command vs response, injector condition |
| P204F | Performance | Reductant system performance issue | Pressure stability, electrical supply, pump wear, sensor deviation | Pressure under load, wiring supply/earth, freeze frame conditions |
| P20E8 | Pressure | Reductant pressure too low | Weak pump, blocked filter, line restriction, winter issues | Pressure build time, stable pressure level, leaks, filter condition |
| P207F | Quality | Reductant quality below standard | Contaminated fluid, old stored fluid, sensor misread | Recent refill history, fluid source, quality sensor plausibility, tank contamination |
| P202A | Electrical / heater | Reductant heater performance | Heater element, wiring, control module, cold weather stress | Heater current draw, wiring continuity, temperature rise vs time |
| P202B | Electrical / heater | Heater control circuit low | Short to ground, damaged wiring, connector corrosion | Wiring checks, connector pins, voltage drop tests |
| P202C | Electrical / heater | Heater control circuit high | Open circuit, broken wire, relay/control issue | Continuity, actuator tests, module output checks |
| P2202 | Electrical / NOx | NOx sensor circuit low input | Wiring fault, sensor fault, connector water ingress | Wiring integrity, reference voltage, sensor communication |
| P2203 | Electrical / NOx | NOx sensor circuit high input | Open circuit, sensor internal fault, harness damage | Harness inspection, plug pin tension, sensor plausibility checks |
A code description is not a diagnosis.
It is a clue.
The “big four” codes you’ll see most
If we had to pick four codes that cause the most stress in the real world, it would be these.
They are the codes that most often lead to repeat warnings or a countdown.
P20EE – SCR efficiency below threshold
P20EE is the classic “it drives fine, then suddenly it doesn’t” code.
In plain terms, the ECU believes the SCR system is not cleaning emissions enough.
Common real causes behind P20EE
- NOx sensor drift causing false efficiency failure
- Injector dosing issue from crystallisation
- AdBlue pressure instability under load
- Adaptation values out after repeated resets
If you only change one part without confirming the data, P20EE often comes back.
Deep dive: P20EE meaning, causes and fixes
P204F – reductant system performance
P204F is the system saying, “I cannot operate normally.”
It is broad on purpose, so you need to anchor it to freeze frame and live data.
What usually sits behind P204F
- Pressure takes too long to build
- Pressure drops when dosing is commanded
- Electrical supply issue to pump or module
- Sensor signal inconsistent with operating conditions
Deep dive: P204F mobile fix guide
P20E8 – AdBlue pressure too low
P20E8 is one of the more direct codes.
It means the system cannot reach or hold target pressure.
That can be the pump, but it can also be restriction, leakage, or winter-related line issues.
Signs it is a pressure supply issue
- Pressure builds slowly from cold
- Pressure drops when dosing is requested
- The fault appears after cold starts or short trips
Deep dive: P20E8 causes and diagnosis
P207F – reductant quality below standard
P207F often appears after a refill.
That does not automatically mean the fluid is wrong, but it does mean the system believes quality is not within expected range.
Common causes behind P207F
- Contamination from old containers or dirty funnels
- Fluid stored too long in heat
- Sensor plausibility issue that flags false quality failure
- Tank contamination from crystallised residue
Deep dive: P207F contamination guide
Live data checks that prevent wrong repairs
The reason AdBlue faults return is simple.
People fix the code, not the cause.
Live data is what reveals the cause.
AdBlue pressure: what you are looking for
You want stability.
A system that spikes, drops, or takes too long to build pressure will trigger pressure and performance faults.
- How quickly pressure rises after start
- Whether pressure holds steady at idle
- What happens to pressure when dosing occurs
NOx sensors: why “two sensors” causes confusion
Many vans have upstream and downstream NOx sensors.
P20EE often shows when the ECU sees poor reduction between the two.
- Upstream reading should respond to engine load changes
- Downstream should show reduction after SCR dosing
- If either sensor is drifting, efficiency can look “bad” even when the catalyst is fine
Heaters: the hidden winter trigger
Heater faults do not always show on mild days.
They appear when temperatures drop and the system cannot bring fluid lines and tank to working condition.
- Check heater circuit codes (P202A–P202C)
- Check wiring and connector condition
- Check whether faults appear mainly after overnight cold starts
If you want one practical tip: record live data before clearing anything.
Once you clear it, you lose the story.
No-start countdown logic and why it returns
Most no-start countdowns do not begin after one fault.
They begin after repeated failure cycles.
The ECU is basically saying: “I tried to reduce emissions, it failed enough times, so I will restrict the vehicle.”
Why the countdown comes back after a reset
- The underlying fault never cleared, so the ECU logs it again on the next drive cycle.
- The reset tool cleared the warning but not the conditions that triggered it.
- The system needs a proof-of-fix cycle (some vans will not clear “permanent” faults without it).
If you want the full explanation of how it triggers and what to do, read:
Transit vs Sprinter vs Boxer: common patterns
Different vans fail in different ways.
The codes can look similar, but the patterns behind them vary.
Ford Transit patterns
- P20EE paired with NOx sensor circuit faults shows up regularly.
- Pressure issues can present as P20E8 first, then evolve into P204F if ignored.
- Repeated resets can lead to recurring warnings even when the van feels fine.
Start point: Ford Transit AdBlue problems guide
Mercedes Sprinter patterns
- Countdown issues are common, especially when the underlying fault is left too long.
- Heater and temperature-related faults show up more in winter.
- “Refill” messages can remain even after topping up if the system needs a proper reset cycle.
Start point: Mercedes Sprinter AdBlue problems guide
Peugeot Boxer patterns
- Crystallisation and dosing issues can drive efficiency faults.
- P207F after refill is seen when fluid quality or tank condition is questionable.
- Warnings can return quickly if the same underlying condition remains.
Start point: Peugeot Boxer AdBlue problems guide
Repair vs delete decision framework
People often ask, “Should I repair it or should I delete it?”
The right answer depends on repeat failure risk, cost, and downtime.
The wrong answer is making the decision without diagnosis.
Repair makes sense when
- You have a single clear failure (one sensor, one wiring fault, one heater issue).
- The vehicle is low mileage and you want to keep it standard.
- The fault history is short, not months of repeat warnings.
Delete is often considered when
- You have repeated failures and the same code keeps returning.
- Repair costs keep stacking up across multiple components.
- Downtime costs you money and the van cannot afford another “countdown” week.
Read: AdBlue delete vs repair
Next steps if you have a fault code today
- Record the code list and dashboard message.
- Stop clearing codes repeatedly.
- Use the code category to guide checks (pressure, quality, electrical, efficiency).
- If a countdown shows, act early before it reaches zero.
Want it diagnosed properly?
We carry out mobile AdBlue diagnostics across Leicester, Loughborough and nearby counties.
You get a clear answer and the right fix route.
Need the warning gone before it turns into a no-start?
We diagnose first, then fix the root cause. Mobile across Leicestershire and nearby counties.
