P2BAD

NOx Exceedance — Root Cause Unknown

P2BAD is a generic OBD-II powertrain diagnostic trouble code: NOx Exceedance — Root Cause Unknown. It is logged by the engine control unit when the scr/adblue monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

Code
P2BAD
Group
Powertrain
System
SCR/AdBlue
Severity
Warning (MIL on, possible limp mode)
Need P2BAD disabled?
RaceTune permanently disables any OBD-II trouble code on supported ECUs — for motorsport, off-road, and export use.
→

What P2BAD means

P2BAD — NOx Exceedance — Root Cause Unknown — is an SAE generic code set when the SCR control system detects that actual NOx conversion efficiency has fallen below the required threshold but cannot attribute the failure to any single specific subsystem fault. It is, in a sense, a catch-all NOx efficiency fault that appears when no single component (reagent quality, dosing injector, pump, level, heater, or NOx sensor) has triggered its own specific fault code, yet the overall system is failing to meet its NOx conversion target. The ECM typically arrives at P2BAD after ruling out the more specific causes through its internal diagnostic tree.

Common scenarios that lead to P2BAD include a SCR catalyst that has been chemically poisoned (by sulphur, phosphorus from oil additives, or coolant contamination), a catalyst that has undergone thermal de-activation from repeated high-temperature events, or a subtle system-wide degradation where no single component has crossed its individual fault threshold but the combination of marginal performance results in overall NOx exceedance. It can also appear transiently when a new SCR catalyst has not yet reached its light-off temperature conditioning, or immediately after an AdBlue tank drain-and-refill before the quality re-evaluation has completed.

On Euro 5b/6 platforms P2BAD is treated the same as any other NOx exceedance code from a regulatory countermeasure perspective: it contributes to the fault accumulation counter and triggers the progressive torque derate if unresolved.

Common causes

Most-frequently reported root causes when P2BAD is logged.

  • 1
    Thermally de-activated SCR catalyst substrate from repeated high-temperature exposure
  • 2
    SCR catalyst chemically poisoned by sulphur compounds (high-sulphur fuel), phosphorus (oil additives), or coolant contamination
  • 3
    Marginal combined degradation across multiple SCR subsystems — each component within individual fault thresholds but collectively failing
  • 4
    Upstream NOx sensor drift or contamination causing inaccurate SCR efficiency calculation
  • 5
    Downstream NOx sensor fouling leading to inaccurate conversion efficiency measurement
  • 6
    AdBlue dosing calibration drift — pump delivering slightly low volumes without triggering a circuit fault
  • 7
    Recent AdBlue fluid change or quality variation before re-evaluation cycle completes

Symptoms drivers notice

MIL and NOx/SCR warning illuminated
Elevated NOx output detectable on emissions test
No single obvious component failure visible on scan tool live data
Progressive torque derate if fault persists across the countermeasure fault accumulation limit
Possible ammonia slip odour if catalyst has aged and AdBlue overdosing relative to remaining activity

How to diagnose P2BAD

A typical diagnostic flow when this code is present.

  1. 1
    Connect a scan tool and read NOx sensor upstream and downstream values at steady-state operation — calculate actual conversion efficiency and compare to the expected minimum (typically above 85% on Euro 6 platforms)
  2. 2
    Check all related fault codes in history — P2BAD appearing alone without any companion SCR fault codes points to catalyst degradation or sensor inaccuracy; companion codes suggest a multi-system fault
  3. 3
    Verify AdBlue fluid quality by refractometer — confirm concentration is within specification before investigating further
  4. 4
    Command a dosing actuator test and verify correct pump current and injector operation to rule out subtle mechanical dosing faults
  5. 5
    Inspect upstream and downstream NOx sensors for contamination or heat damage; replace any NOx sensor whose reading appears implausible relative to engine load conditions
  6. 6
    If catalyst poisoning is suspected (high-mileage vehicle, known oil consumption or coolant loss), assess catalyst condition by comparing NOx conversion efficiency cold vs. hot — a poisoned catalyst shows poor conversion even when fully warmed
  7. 7
    If no specific fault is found and P2BAD persists, SCR catalyst replacement is the most likely remaining corrective action after all sensors and dosing components have been verified

Vehicles where we've handled P2BAD

Platforms in our catalogue with confirmed P2BAD coverage.

BMW 530XD
2017
BMW X5
2018–2019
BMW 320D
2016
MB GLE350 30D
BMW 530XD 30D
MB GLC220 21D
2017

Related powertrain codes

Frequently asked questions

Why does P2BAD appear instead of a more specific code?

P2BAD is set when the root-cause diagnostic tree cannot isolate the failure to a single component. The NOx conversion failure is real, but no individual sensor, pump, injector, or quality monitor has exceeded its individual fault threshold. This most often points to gradual catalyst degradation.

Is P2BAD a sign that the SCR catalyst needs replacing?

Not always, but it is the most common conclusion after all other components have been verified. If AdBlue quality, dosing function, and NOx sensor accuracy are all confirmed correct and P2BAD persists, the SCR catalyst is the next component to replace.

Can high-sulphur diesel cause P2BAD?

Yes. Sulphur compounds from non-compliant fuel bind to SCR catalyst active sites, temporarily reducing conversion efficiency in a process called sulphur poisoning. A desulphation cycle (high exhaust temperature run) can partially recover a sulphur-poisoned catalyst. Permanent deactivation occurs with severe or repeated sulphur exposure.

Is P2BAD the same fault as P2BA9?

No. P2BA9 specifically identifies insufficient reagent quality as the root cause of NOx exceedance. P2BAD means NOx exceedance has occurred but the root cause cannot be determined from available sensor data. P2BA9 is resolved by replacing the AdBlue; P2BAD requires a broader investigation.

Disabling P2BAD in software

RaceTune can permanently disable P2BAD — and any other OBD-II diagnostic trouble code — on every ECU family we support. The monitor is disabled inside the ECU itself, so the fault stops being logged: the warning light stays off and the engine never enters limp mode for this code. The change is tied to your exact software version.

Permanent
The monitor is disabled in the ECU itself — not just cleared. It cannot return.
Tailored to your file
Each patch is matched to your specific software version — never a one-size-fits-all file.
Reversible
The original file is always preserved. Reflash the stock to return the ECU to factory state.

ECUs with a P2BAD disable in our catalogue

Confirmed coverage from our recipe database — we support many more families. Upload your file and our identifier will match it automatically.

  • Bosch EDC17CP57 verified 2 software versions
  • Bosch EDC17C50 verified 1 software version
  • Bosch EDC17C56 verified 1 software version
  • Bosch EDC17C66 verified 1 software version
  • Bosch MD1CP002 verified 1 software version
  • Bosch MD1CS001 verified 1 software version

Software modifications affect emissions compliance and are not road-legal in many jurisdictions. RaceTune service files are intended for motorsport, off-road, and export use.

Got P2BAD in your scan?

Upload your ECU file — we'll identify the exact software version and confirm whether a disable is available for your car.

Upload your file