Bolt Remaps

Call 0203 038 8555 · WhatsApp 07719 156806 · 4.8 ★★★★★ 283 Google reviews · 6am–9pm, 7 days, including bank holidays

Using a Fault Code Reader on a Diesel Van: What It Can and Can't Tell You

Fault codes · Published

By the Bolt Remaps technical team · Last updated:

A cheap code reader is worth having: it shows the generic engine codes and points you at the right system. What it usually can't do is see the separate AdBlue module, show live data or reset a countdown.

Bolt Remaps technician using a diagnostic tablet in the engine bay, next to the AdBlue filler
Live data on the SCR system before any part is quoted.

In short

  • A basic reader shows generic P-codes from the engine computer. That is a useful starting point.
  • Many cannot see the separate SCR (AdBlue) module, manufacturer codes, live data or the countdown.
  • Clearing a code does not fix the fault, and on most vans it will not reset an AdBlue countdown.
  • Write down the exact code, the mileage, when it appeared and the countdown miles before you call anyone.

What a cheap reader does well

A plug-in reader from a motor factor or online shop connects to the diagnostic socket under the dash and asks the engine computer for stored faults. On a diesel van that is genuinely useful. It turns a vague warning light into a code such as P20EE or P2BAD, which tells you which system to look at.

Most will also show whether the code is current or stored, and many can read the freeze frame: a snapshot of engine speed, temperature and load at the moment the fault was logged. That snapshot often explains when and why the fault appears.

For a quick check of whether a light is something serious, and for having a sensible conversation with a technician, a basic reader earns its money.

Generic codes and manufacturer codes

Codes that start P0 and P2 are defined by a common standard. P20EE means SCR efficiency below threshold on every make, and our list of AdBlue fault codes covers the common ones. Any reader will show those.

Codes that start P1, and many U and B codes, are manufacturer-specific. The same code can mean different things on different makes, and some cheap readers either do not show them or show them with the wrong description.

The Peugeot and Citroën additive codes are a good example. P1435, P1434 and P15B3 relate to the Eolys additive that helps the particle filter burn off soot. They are not AdBlue codes at all, but a reader with a generic library may label them wrongly or not at all.

What cheap readers usually miss

These are the gaps we see most when an owner shows us what their reader found.

  • The SCR or DCU module

    On many vans the AdBlue system has its own control unit. Its pump, heater and pressure codes live there, not in the engine computer. A reader that only talks to the engine can say "no faults" while the AdBlue module has several.

  • Network codes

    Codes such as U029D, lost communication with the NOx sensor point at wiring or a sensor that has stopped talking. Some readers do not report U codes at all.

  • Live data

    Diagnosing an SCR fault means watching NOx readings, dosing pressure demanded against actual, fluid temperature and quality while the engine runs. Basic readers either do not show this or only show a few generic engine values.

  • The countdown counter

    The miles remaining before a no-start are held in the SCR or engine module. Basic readers rarely display it, and cannot reset it. Our page on the AdBlue countdown explains how it works.

  • Tests and adaptations

    Running the AdBlue pump, doing a dosing quantity test, resetting adaptations after a new part or forcing a DPF regeneration all need a tool that can command the modules, not just read them.

Why clearing codes doesn't fix it

Clearing a code removes the record. It does not change anything on the van. If the NOx sensor is still reading wrong or the pump still cannot make pressure, the computer will see the problem again, often within a single drive, and the light will be back.

On most vans, clearing the code also has no effect on the AdBlue countdown. That counter is designed to resist casual resets so that the fault has to be repaired. Some owners clear codes repeatedly in the hope of buying time and lose the freeze frame that would have helped find the fault.

Clearing a code before getting it diagnosed makes the job slower, not quicker. Leave it stored and let the technician see it.

When the reader is right and the job is simple

Sometimes the code tells you the whole story. A loose or damaged AdBlue cap, a tank that is genuinely low, or a recent top-up from an open or old container can all trigger warnings that clear once the cause is dealt with.

If you have just put the wrong fluid in the AdBlue tank, do not drive further and read our guide to wrong fluid in the AdBlue tank. That one is urgent, but the fix starts with draining, not with parts.

If the code is a single, simple one and it does not come back after the obvious fix, you may not need us at all. The AdBlue symptom checker helps you decide.

What to write down before you call

This saves time on the phone and on the driveway.

  • The exact code

    All five characters, for example P20EE, not "an AdBlue code". If there are several, list them all and note which appeared first.

  • The mileage

    The odometer reading now and, if you know it, when the light first came on.

  • The countdown

    If the dash shows miles remaining, note the figure and the date. It tells us how urgent the job is.

  • What changed

    A recent top-up, a cold night, a service, a new part, or a long run on the motorway. Small details often point straight at the cause.

When to call us

Mobile AdBlue diagnosis and repair from £249. No fix, no fee. 6am to 9pm, 7 days, across London and the South East. We are IMI affiliated, have 7+ years of experience, and bring dealer-level diagnostic equipment to your driveway, yard or roadside.

If your reader shows P20EE or P2BAD, the next step is a full scan with live data. See our AdBlue repair prices, read about the MOT and the law, or get a fixed price.

Common questions

Can a cheap OBD reader diagnose AdBlue faults?

It can show generic AdBlue codes stored in the engine computer, such as P20EE or P2BAD, which is a good start. Most cannot read the separate SCR module, show live data, run the pump or reset the countdown. That means they can point you at the system, but they cannot prove which part has failed.

Will clearing the code reset my AdBlue countdown?

On most vans, no. The countdown is held in the SCR or engine module and is designed not to reset just because a code is cleared. It stops once the fault is repaired and the system confirms it is working again. Clearing codes early also wipes the freeze frame data that helps a technician find the fault.

Why does my reader say no faults when the AdBlue light is on?

The AdBlue fault is probably stored in a separate SCR or DCU module that your reader cannot talk to. Many vans split the AdBlue system onto its own control unit. A tool with full manufacturer coverage will read that module and show the codes behind the warning.

What is a manufacturer-specific code?

Codes starting P1, and many U and B codes, are defined by each car maker rather than the common standard. The same code can mean different things on different makes. For example, Peugeot and Citroën use P1435, P1434 and P15B3 for their Eolys additive system, which has nothing to do with AdBlue.

What should I tell a technician about my fault code?

Give the exact code, every other code that is stored, the current mileage, when the light first came on, and the countdown figure if one is showing. Mention anything that changed just before, such as a top-up, a cold night or a recent service. It helps the technician bring the right parts and plan the tests.