AutoLogicTools

OBD-II trouble code

P22A2: NOx Sensor Circuit Intermittent (Bank 1 Sensor 2)

The downstream NOx value keeps disappearing and coming back. On a device that reports over a data link this is a node leaving the network, not a signal flickering — and that distinction gives you a timestamp to chase.

Medium severityPowertrainAuxiliary Emissions ControlsDrivable short-term

Quick facts

System
Powertrain
Category
Auxiliary Emissions Controls
Severity
Medium severity
Drivable
Usually safe to drive short-term
Repair cost range
$80$1,100
DIY difficulty
Intermediate DIY

Browse every code in P2200–P22A8, or start from the full code library.

What does P22A2 mean?

An intermittent fault on an ordinary analogue sensor is frustrating because there is nothing to see: a voltage wobbles, the module notices, and the only record is the code. This code behaves differently, and the difference is worth understanding before you start wiggling wires.

The downstream NOx sensor does not send a voltage that the module interprets. It is a small self-contained device with its own processor that measures, calculates and then transmits a finished number as a message on a data link. When the connection to it degrades, the device does not produce a slightly wrong number — it stops appearing on the link altogether, and then reappears. That is a dropout, not a glitch, and the vehicle keeps a record of it in a way an analogue intermittent never leaves behind. Somewhere in the network module's memory there is very often a lost-communication entry for that specific node, and its freeze frame carries a timestamp, an engine run time and a coolant temperature.

Use that. Read every module the tool can reach, not just the engine controller, and write down the stored conditions from both the P22A2 and any communication fault that names the same device. When they agree — same run time, same coolant temperature, same road speed — you have a repeatable condition to reproduce, and reproducing an intermittent is the entire job. When the recorded conditions cluster around a cold engine, suspect the supply and the connector. When they cluster around a particular speed or a rough surface, suspect the harness where it is routed along the underside of the vehicle. When they cluster around nothing at all, look at the link itself.

That last case deserves a note. This sensor generally sits at the far end of the aftertreatment harness — physically the most distant device in that group from the controller that talks to it. A data link degrades from the ends inward, so a splice, a terminal or a connection that has gone marginal anywhere along that run will take out the furthest device first while every nearer one keeps working. A single device dropping out while the rest of the network is untouched is normal and points at that device and its own connector. Several aftertreatment devices dropping out together points at the shared part of the run and means replacing this sensor would fix nothing.

Finally, be suspicious of a repair that has already been attempted. A sensor of this type that has been unplugged and reconnected several times during previous diagnosis can end up with spread terminals that grip loosely, and a loose terminal in a connector exposed to vibration and heat is the most ordinary cause of a dropout there is.

Common causes

  • Loose or spread terminals in the downstream sensor connector, often after previous disconnection
  • Chafed or heat-damaged harness along the underside routing to the rear sensor position
  • Degraded splice or connection in the shared aftertreatment data link run
  • Moisture in the connector creating an intermittent path that clears as the area warms
  • Intermittent supply or ground causing the sensor's controller to reset and rejoin the link
  • Failing sensor controller that drops off the network under heat
  • Corrosion at a connector on a vehicle used on salted roads
  • Harness pulled tight or re-routed incorrectly after exhaust or driveline work

Symptoms

  • Check engine light that comes on, clears itself and returns days later
  • Post-SCR NOx value in live data vanishing and reappearing rather than reading wrong
  • A lost-communication fault stored against the same device in another module
  • Emissions or exhaust fluid warnings that appear and disappear
  • Fault that seems tied to rough roads or to a particular part of a familiar journey
  • Other aftertreatment devices dropping out at the same instant when a shared run is at fault
  • No detectable change in how the engine runs

Diagnostic steps

  1. 1.Scan every module the tool can reach, not only the engine controller, and note any lost-communication fault naming this sensor. That entry is the evidence an analogue intermittent would never leave.
  2. 2.Compare the freeze frame conditions stored with each related code. Matching run time, coolant temperature and road speed give you a condition you can deliberately reproduce.
  3. 3.Establish whether this device alone drops out or whether other aftertreatment devices go with it. One device points at that device and its connector; several point at the shared harness run.
  4. 4.Inspect the connector at the sensor for terminal tension using a drag test on a matching pin rather than a continuity check. Continuity passes on a terminal that is too loose to stay connected over a bump.
  5. 5.Follow the harness along its underbody route looking for chafe points, heat contact against the exhaust, and any section pulled tight by a previous repair.
  6. 6.Reproduce the fault with the scan tool recording — a firm hand on the harness, a controlled drive over a rough surface, or a heat gun on a suspect section while watching the value.
  7. 7.Check supply and ground stability at the sensor during the drop-out rather than at rest. A controller that momentarily loses supply will rejoin the link and look identical to a data fault.
  8. 8.Repair the connection or harness section found, then drive the recorded fault condition deliberately and confirm the value holds continuously before calling it fixed.

Repair cost

$80$1,100

Most of these end cheaply once the dropout is located. Re-terminating a connector or repairing a short harness section is $80 to $350. A larger harness repair along the underbody run is $200 to $600. A downstream NOx sensor assembly is $400 to $900 fitted, plus $80 to $180 where initialisation is required. Diagnostic time on an intermittent is realistically $120 to $260 because reproducing it is the work, and it is money well spent — replacing the sensor on an unreproduced dropout is the classic way to pay full price and keep the fault.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with wiring harness repair preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

This is an intermediate DIY job. It usually involves diagnostic steps, specialty parts, and some careful work in tight spaces. If you have the tools and a service manual or trustworthy video for your specific vehicle, it is achievable in a weekend. Otherwise, a competent independent shop will be faster.

Related codes

Frequently asked questions

Can I keep driving with P22A2?

Yes for the short term. The engine runs normally and nothing about the fault affects control of the vehicle. The reason not to leave it indefinitely is that exhaust-fluid systems commonly escalate to a reduced power strategy once emissions monitoring has been unreliable across enough drive cycles, and an intermittent fault will eventually accumulate those cycles even though it feels like it is coming and going harmlessly.

Why does another module have a code for the same sensor?

Because this sensor communicates on a data link rather than sending a plain voltage, so when it drops out the module that was listening for it records a lost-communication fault against that specific node. That entry is genuinely useful — it carries its own freeze frame, and comparing its stored conditions with the ones saved against P22A2 usually gives you a repeatable set of circumstances to chase.

Should I replace the sensor if I cannot reproduce the fault?

Not yet. An unreproduced dropout is as likely to be a loose terminal or a chafed section of harness as a failed device, and those cost a fraction of the part. Spend the time on reproduction instead: drive with the value recording, work the harness by hand, warm a suspect section. If the value holds solid while the connector is being stressed and drops when it is not touched at all, the device becomes the reasonable conclusion.

Why this sensor and not the others?

Position. The downstream sensor generally sits at the far end of the aftertreatment harness, furthest from the controller that talks to it, and a marginal connection anywhere along that shared run takes out the most distant device first while nearer ones carry on working. That is also the check worth making early: if several aftertreatment devices drop out together, the shared section is at fault and replacing this one sensor would change nothing.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.