P2AEC

NOx Sensor Circuit Intermittent Bank 1 Sensor 2

P2AEC is a generic OBD-II powertrain diagnostic trouble code: NOx Sensor Circuit Intermittent Bank 1 Sensor 2. It is logged by the engine control unit when the powertrain monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

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

What P2AEC means

P2AEC is set when the PCM detects an intermittent signal from the downstream NOx sensor on Bank 1 (Sensor 2). Unlike continuous circuit high or low faults, an intermittent fault means the sensor signal drops out or spikes unexpectedly at irregular intervals, making it difficult to capture with a simple static measurement. The PCM monitors for signal dropouts, sudden jumps, or loss of communication with the sensor over a defined monitoring window.

Intermittent faults are frequently caused by loose or corroded connector terminals, hairline cracks in the sensor pigtail wiring that open under vibration or thermal cycling, or a marginally failing sensor that functions correctly when cold but drops out as temperatures rise. Chafed wiring that intermittently contacts ground or a voltage rail can also produce this pattern.

Diagnosing intermittent codes requires dynamic testing: monitoring live NOx data over a road test while manipulating the harness, or using a data logger to capture the moment the signal is lost. Because the fault may not be present during a workshop inspection, careful attention to connector condition and harness routing is essential before condemning the sensor itself.

Common causes

Most-frequently reported root causes when P2AEC is logged.

  • 1
    Loose or intermittently contacting NOx sensor connector terminal.
  • 2
    Hairline crack or break in sensor pigtail wiring that opens under vibration.
  • 3
    Chafed harness intermittently shorting to ground or voltage.
  • 4
    Marginally failing NOx sensor element that drops out at operating temperature.
  • 5
    Corroded terminal causing high resistance that increases with heat.
  • 6
    Sensor heater intermittent fault causing temporary loss of operating temperature.
  • 7
    PCM connector pin intermittent contact.

Symptoms drivers notice

MIL illuminated, potentially with a history of self-clearing.
NOx sensor live data showing occasional dropouts or spikes during a road test.
Inconsistent DEF dosing behavior noticed as varying fuel economy.
Fault may not be present during a cold workshop inspection.
Multiple related NOx or SCR codes stored in history.

How to diagnose P2AEC

A typical diagnostic flow when this code is present.

  1. 1
    Retrieve all current and historical DTCs; note freeze frame conditions when the fault was captured.
  2. 2
    Perform a thorough visual inspection of the NOx sensor connector, pigtail, and harness routing.
  3. 3
    Conduct a wiggle test on the harness while monitoring NOx sensor live data for signal interruptions.
  4. 4
    Road test the vehicle with a live data recorder active to capture the signal at operating temperature.
  5. 5
    Clean and reseat the sensor connector; apply dielectric grease to protect terminals.
  6. 6
    If no harness fault is found and the fault recurs, replace the NOx sensor.
  7. 7
    Clear codes and perform a monitored drive cycle to verify repair.

Vehicles where we've handled P2AEC

Platforms in our catalogue with confirmed P2AEC coverage.

BMW 320D
2016

Related powertrain codes

Frequently asked questions

Why does P2AEC appear and disappear on its own?

Intermittent faults often correlate with temperature or vibration. The connection may be adequate when cold or stationary but fail under heat expansion or road vibration.

Is it safe to ignore an intermittent NOx sensor fault?

No. Intermittent faults tend to become permanent over time and cause emissions non-compliance in the meantime. Diagnose and repair promptly.

How do I capture an intermittent fault?

Use a scan tool with data logging capability and monitor the downstream NOx sensor channel over a road test that replicates the conditions when the fault was first noted.

Can a loose battery connection cause this code?

Unlikely to cause this specific code directly, but a weak power supply can affect sensor heater operation and contribute to marginal sensor behavior.

Disabling P2AEC in software

RaceTune can permanently disable P2AEC — 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 P2AEC 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

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 P2AEC 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