AutoLogicTools

OBD-II trouble code

P2221: NOx Sensor Heater Sense Circuit (Bank 2)

A fault in the heater feedback path at the second nitrogen oxide sensor address. The useful thing about this address specifically is that the vehicle carries another one of these sensors, so you have a free reference: whether the other heater behaved the same way at the same moment narrows this to a shared cause or a single sensor before you touch a tool.

Low severityPowertrainAuxiliary Emissions ControlsDrivable short-term

Quick facts

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

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

What does P2221 mean?

Any code stored against the second of two identical devices comes with an advantage the first one does not have, and on this one it is worth using before anything else. The vehicle has another nitrogen oxide sensor with its own heater, its own feedback and its own set of codes, running through the same drive cycle on the same supply from the same controller. That makes it a reference sample. Look at what it did at the same moment this fault was recorded, and the answer usually points somewhere useful in under five minutes.

If both heaters struggled together, the cause is something they share: the supply fuse or relay, the common ground, the controller itself, or nothing wrong at all because the journey never met the conditions the monitor needed. If only this one reported a problem, the shared parts are exonerated in a single step and the investigation belongs to this sensor, its connector, and the length of harness that serves it alone. Very few circuit codes hand you that much for free, and it is the reason to read data from both addresses before deciding anything.

The second thing this address brings is a matter of geography rather than electronics, and it changes where the odds sit. On a typical aftertreatment harness the second sensor is the furthest device from the controller — it sits at the tail of the system, at the end of the longest run of wire, behind more inline connectors, more splices and more chassis tie points than any other sensor in the group. Every one of those interfaces is a place a low-current feedback line can fail, and the count of them, not the length of the wire, is what raises the failure rate at this address. So the fault is more often out along the route than at either end of it, and the inspection ought to follow the route rather than start at the sensor and stop.

It is also worth understanding what this circuit is for, because it explains why the severity is genuinely low. On most systems the second sensor is not what tells the controller how much to dose. It is what tells the controller whether the dosing worked — it grades the finished result. So a fault here degrades the vehicle's ability to assess its own aftertreatment performance rather than its ability to run it. That is a real loss for an inspection and a real loss for the diagnostic information the next technician will want, but it is not a loss of function, and nobody driving the vehicle will detect it.

One caution on cost, because it is the standard way this code gets expensive. The part named on the code is one of the pricier sensors fitted under a vehicle, and the feedback circuit is one of the cheapest things on it to break. Those two facts pull in opposite directions, and the resolution is to establish whether the heater actually failed before buying the thing that heats. Where the other sensor's data is available, that comparison is usually enough on its own.

Finally, on timing. The monitor that produces this code typically runs once per cold start, so a repair cannot be judged on a warm restart or a lap of the car park. Clear the code, leave the vehicle overnight, and drive it properly. A vehicle that has been sitting on a workshop lift for two days has not tested anything.

Common causes

  • Corroded, spread or backed-out terminal in one of the inline connectors between the controller and the sensor at the tail of the harness
  • High-resistance splice in the feedback conductor, common on a run that includes several joints
  • Water and salt intrusion at a connector sitting low in the road spray
  • Shared supply or ground fault, identifiable because the other nitrogen oxide sensor reports a problem in the same drive
  • Damaged or chafed section of the aftertreatment harness where it runs exposed under the vehicle
  • Internal fault in the sensor's own electronics, which generate the heater status the controller reads
  • Harness disturbed or a connector left unlatched during exhaust, suspension or driveline work
  • Controller input fault, which is uncommon and should only be suspected after the harness is proven
  • Calibration mismatch after a controller replacement or reflash, where the expected heater reporting behaviour changed

Symptoms

  • Check engine light with no perceptible change in performance, fuel use or exhaust fluid consumption
  • Emissions readiness monitors that stay incomplete through repeated drive cycles
  • Normal dosing behaviour and normal nitrogen oxide data from the other sensor address
  • The equivalent code at the other sensor address stored at the same time, which points at something the two share
  • Aftertreatment conversion efficiency data that is missing or flagged invalid on a scan tool
  • No symptom at all until an inspection or a routine scan finds the code
  • On diesels, the eventual staged inducement warnings if the fault is left in place long enough

Diagnostic steps

  1. 1.Read live data from both nitrogen oxide sensor addresses before anything else, and compare what their heaters did during the drive that set this code.
  2. 2.If both struggled, investigate what they share first — the supply fuse and relay, the common ground point, and the controller — rather than either sensor.
  3. 3.If only this address reported a fault, the shared parts are cleared and the work is confined to this sensor, its connector and the harness serving it alone.
  4. 4.Check whether any heater control code is stored alongside. If one is, diagnose that fault and expect this feedback code to clear with it.
  5. 5.Follow the harness route rather than inspecting only the ends. Open every inline connector between the controller and this sensor and check each for corrosion, spread terminals and water.
  6. 6.Test the feedback conductor end to end for resistance, and wiggle-test it at each connector while watching the reading.
  7. 7.Measure voltage drop across any splices found in the run, since a high-resistance joint reads acceptable on a static continuity check.
  8. 8.Establish whether the heater genuinely failed before pricing a sensor, using the comparison with the other address as the primary evidence.
  9. 9.Clear the code, leave the vehicle to cool overnight, then drive a full warm-up cycle. This monitor generally runs once per cold start and cannot be tested any other way.

Repair cost

$100$950

Diagnostic time is $100 to $250, and the comparison against the other sensor address usually resolves the direction of the fault inside the first half hour. Repairing a corroded terminal, a bad splice or a damaged section of the aftertreatment harness runs $80 to $400, and the majority of these end there because this address sits behind the most connectors. A shared supply or ground fault is $120 to $450. Replacing the sensor assembly is $250 to $900 fitted and should be the last conclusion rather than the first, since the heater is often working correctly while this code is stored.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with wiring harness / circuit 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

How does the other NOx sensor help me diagnose this one?

The two run on the same supply, the same ground and the same controller through the same drive cycle, so the second one is a reference sample. If both heaters misbehaved at the same moment, look at what they share. If only this one did, everything shared is ruled out and the fault is in this sensor, its connector or the harness serving it alone. That is a five-minute check with a scan tool and it usually decides where to spend the next hour.

Why is the failure rate higher at this address than at the other sensor?

Position, not quality. On most aftertreatment harnesses this is the furthest device from the controller, which means it sits behind more inline connectors, splices and tie points than anything else in the group. Each of those is a place a low-current feedback line can go high-resistance, and it is the number of interfaces rather than the length of the wire that drives the odds.

Do I need a new NOx sensor?

Often not, and this is the code where assuming so costs the most, because the sensor is one of the more expensive parts under the vehicle while the feedback circuit is one of the cheapest things on it to break. Establish whether the heater actually failed first — comparing against the other sensor address is usually enough — and buy the part only if the evidence says the part is at fault.

Can I keep driving with P2221?

Yes. On most systems this sensor reports on whether the exhaust treatment worked rather than commanding it, so a fault here costs the vehicle its ability to grade itself, not its ability to run. Nothing about driving becomes unsafe. The reasons to fix it are that emissions monitors will not complete, and on a diesel the aftertreatment inducement sequence eventually starts counting regardless of how the vehicle feels.

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.