P2B69
NOx Sensor Circuit Intermittent Bank 1 Sensor 2P2B69 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.
What P2B69 means
P2B69 is stored when the aftertreatment or engine control module detects an intermittent signal fault in the downstream NOx sensor circuit on Bank 1 (Sensor 2, post-SCR catalyst). Unlike a continuous circuit high or low fault, an intermittent fault means the sensor signal drops out, spikes, or becomes erratic at irregular intervals rather than remaining consistently out of range. The module detects signal plausibility violations that are transient in nature, often associated with vibration, thermal cycling, or moisture-related connector issues.
Common causes include loose or corroded connector pins that make intermittent contact, a wire harness with a partial break (especially at high-flex areas or near heat sources), or a sensor with an internally degrading sense cell that fails unpredictably under certain temperature or exhaust flow conditions. Intermittent faults are among the most difficult to diagnose because symptoms may not be present at the time of inspection.
Because the fault is intermittent, the SCR feedback loop may function normally much of the time but will be disrupted during dropout events. NOx emissions compliance can be compromised during fault episodes. The MIL is illuminated and the fault is stored with freeze-frame data capturing the conditions at the time of each dropout. Careful connector inspection, harness flex testing, and sensor substitution under load are the most effective diagnostic approaches.
Common causes
Most-frequently reported root causes when P2B69 is logged.
-
1
Loose or corroded connector pins at the NOx sensor harness connector.
-
2
Partial wire break in the sensor harness at a flex point or near a heat source.
-
3
Sensor element degrading internally and failing intermittently under heat or vibration.
-
4
Reductant or moisture ingress into the connector causing intermittent contact resistance.
-
5
Harness routing allowing chafing or vibration-induced contact with chassis or exhaust.
-
6
Failed sensor controller integrated into the sensor body producing intermittent output dropouts.
-
7
Loose sensor mounting allowing vibration to disrupt the electrical connection.
Symptoms drivers notice
How to diagnose P2B69
A typical diagnostic flow when this code is present.
-
1
Connect a scan tool and review all DTCs and all stored freeze-frames to identify patterns (speed, temperature, engine load) correlated with the fault.
-
2
Inspect the NOx sensor harness connector for corrosion, loose pins, or moisture contamination.
-
3
Wiggle the harness and connector while monitoring the live NOx signal on a scan tool to reproduce the dropout.
-
4
Inspect the harness routing for chafing against exhaust components or chassis members.
-
5
Check the sensor mounting torque to ensure it is not vibrating loose.
-
6
If no wiring fault is found, perform a road test monitoring live data; a dropout confirms the sensor or harness is intermittently failing.
-
7
Replace the sensor if wiggle testing or a road test reproduces the dropout without finding a wiring fault.
Related powertrain codes
Frequently asked questions
Why is an intermittent fault harder to diagnose than a continuous one?
The fault may not be present during inspection. The circuit appears normal when the fault is not active, so reproduction under specific conditions (vibration, heat, moisture) is essential.
Should I replace the sensor immediately if I find P2B69?
Not without first performing a thorough connector and harness inspection. Many intermittent faults are caused by corroded connector pins that can be cleaned or repaired for a fraction of the sensor replacement cost.
Can this fault cause the SCR system to misfire DEF?
During a signal dropout event, the control module may briefly revert to open-loop dosing or suspend dosing, which can cause momentary over- or under-delivery of reductant.
How many occurrences does it take to set P2B69?
The exact threshold varies by manufacturer, but typically the fault must occur a minimum number of times across a defined drive window before the MIL is illuminated and the code is confirmed.
Disabling P2B69 in software
RaceTune can permanently disable P2B69 — 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.
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 P2B69 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