P2BAC

Exceedence - Deactivation of EGR

P2BAC is a generic OBD-II powertrain diagnostic trouble code: Exceedence - Deactivation of EGR. It is logged by the engine control unit when the egr monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

Code
P2BAC
Group
Powertrain
System
EGR
Severity
Warning (MIL on)
Need P2BAC disabled?
RaceTune permanently disables any OBD-II trouble code on supported ECUs — for motorsport, off-road, and export use.
→

What P2BAC means

P2BAC is stored when the powertrain control module (PCM) or diesel control module detects that the signal voltage from the downstream NOx sensor (Bank 1, Sensor 2) is above the expected operating range for a defined period. The downstream NOx sensor is located after the selective catalytic reduction (SCR) catalyst and is used to monitor SCR conversion efficiency and closed-loop DEF dosing control.

A high-circuit fault can originate from a sensor supply voltage fault, a shorted signal wire, an internal sensor failure, or a wiring harness issue causing the signal line to be pulled high. The module compares the sensor output against calibrated limits; when the signal remains above the high threshold continuously, this code is triggered and the NOx sensor monitoring function is suspended.

Leaving this fault unaddressed can degrade SCR efficiency monitoring, potentially causing the system to under-dose or over-dose reductant. Extended operation with a faulty downstream NOx sensor may eventually lead to tailpipe NOx exceedance and could trigger additional SCR-related fault codes or a torque derate on some platforms.

Common causes

Most-frequently reported root causes when P2BAC is logged.

  • 1
    Failed downstream NOx sensor with internally shorted signal cell.
  • 2
    Chafed or pinched wiring harness creating a short to voltage on the NOx sensor signal circuit.
  • 3
    Corroded or spread connector pins at the NOx sensor harness connector.
  • 4
    Faulty NOx sensor control module or sensor heater driver circuit affecting signal reference.
  • 5
    Contaminated NOx sensor element caused by excessive sulfur or oil exposure.
  • 6
    Open or high-resistance ground circuit for the NOx sensor.

Symptoms drivers notice

Malfunction indicator lamp (MIL) illuminated.
SCR system operating in open-loop or reduced-efficiency mode.
Possible increase in DEF consumption or dosing irregularities.
Additional SCR or emission-related DTCs stored alongside P2BAC.
Possible mild torque reduction on vehicles with strict NOx monitoring enforcement.

How to diagnose P2BAC

A typical diagnostic flow when this code is present.

  1. 1
    Connect a scan tool and record all stored and pending DTCs along with freeze-frame data.
  2. 2
    Check live data for the downstream NOx sensor signal voltage and compare against specification.
  3. 3
    Perform a visual inspection of the NOx sensor connector and wiring harness for chafing, corrosion, or damage.
  4. 4
    Measure sensor signal circuit voltage at the harness connector with the sensor disconnected to check for a short to voltage.
  5. 5
    Verify sensor heater circuit resistance and supply voltage are within manufacturer specification.
  6. 6
    If wiring checks pass, replace the downstream NOx sensor and retest.
  7. 7
    Clear codes, perform a complete drive cycle, and confirm the fault does not return.

Vehicles where we've handled P2BAC

Platforms in our catalogue with confirmed P2BAC coverage.

BMW 320D
2016
MB GLE350 30D

Related powertrain codes

Frequently asked questions

Can I drive with P2BAC active?

Short-term driving is generally possible, but SCR efficiency monitoring is compromised. Have the fault diagnosed promptly to avoid cascading emission system faults or a torque derate.

Is P2BAC always a failed sensor?

Not always. A short to voltage in the wiring harness or a faulty connector can produce the same high-circuit code without the sensor itself being defective.

Will P2BAC clear itself?

If the root cause is intermittent (e.g., a loose connector), the code may clear after a drive cycle, but it will return until the underlying fault is repaired.

Does P2BAC affect DEF dosing?

Yes. When the downstream NOx sensor signal is invalid, the SCR closed-loop dosing strategy falls back to open-loop, which can degrade reductant efficiency.

Disabling P2BAC in software

RaceTune can permanently disable P2BAC — 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 P2BAC 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 EDC17C50 verified 1 software version
  • Bosch EDC17CP57 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 P2BAC 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