AutoLogicTools

OBD-II trouble code

P229E: NOx Sensor Circuit (Bank 1 Sensor 2)

The module cannot get a valid signal from the downstream NOx sensor. The thing most people get wrong about this code is that a modern NOx sensor is not a sensor on a wire — it is a small networked module, and a continuity test proves almost nothing.

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
$150$1,200
DIY difficulty
Intermediate DIY

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

What does P229E mean?

Start with what makes this component unlike almost everything else on the vehicle. A NOx sensor is not a two-wire element producing a voltage that the engine module interprets. The sensing element is far too delicate and its output far too small to survive that arrangement, so every production NOx sensor is sold as an assembly: a probe in the exhaust, a short length of dedicated harness, and a sealed electronic control box part-way along it. That box conditions the signal, manages the heater, runs its own diagnostics and reports finished values onto a serial data bus. The engine module never sees the raw element at all — it sees messages.

That single fact rewrites the diagnosis. When this code sets, the complaint is usually that the sensor's controller has stopped reporting on the bus, or is reporting a fault about itself. Reaching for a multimeter and testing continuity between the engine module and the sensor is therefore close to useless, because the wires being tested do not carry the measurement. The right first tool is a scan tool that can show whether the sensor module is present and communicating, and what it is saying about itself. A sensor that is electrically intact and has simply dropped off the bus looks identical, on a meter, to a sensor that is working perfectly.

The second fact concerns where the thing lives. This sensor's controller box is bolted to or hung near the exhaust system, making it the most hostile mounting location of any electronics on the vehicle. It endures the heat of the aftertreatment system, the vibration of the exhaust, and everything the road throws at it, including winter salt. On the downstream position in particular — after the diesel particulate filter and the selective catalytic reduction catalyst — the thermal event that shortens its life is regeneration, where exhaust temperatures are driven deliberately high and held there. A sensor that has been through hundreds of regeneration cycles has had its controller and its connector cooked hundreds of times. Failures here are usually the box or the connector, not the probe, and because the box and the probe are almost never sold separately, 'just replacing the wiring' is rarely an available repair.

The third thing to know before ordering a part is that fitting it is often not the end of the job. Many systems require the new sensor to be recognised, initialised or have its identifier written before it will report properly, and a sensor that never comes online produces precisely the original symptom. Verify the repair by confirming the sensor is present on the bus and returning live values, not by watching whether the warning light goes out, because a light that has not yet re-run its monitor tells you nothing either way.

Common causes

  • Failed sensor control module in the sealed box on the sensor harness
  • Connector corrosion or heat damage where the sensor plugs into the vehicle harness
  • Open or shorted bus wiring between the sensor module and the engine control module
  • Heat damage to the harness section routed near the exhaust or the particulate filter
  • Supply or ground fault preventing the sensor module from powering up at all
  • Road salt and moisture intrusion into the connector on the downstream position
  • A replacement sensor fitted but never initialised, so it never reports on the bus
  • Rarely, an engine control module or aftertreatment controller fault

Symptoms

  • Check engine light with an emissions or exhaust system message
  • Diesel exhaust fluid or SCR related warnings displayed alongside
  • Reduced power inducement if the emissions fault persists across drive cycles
  • Missing or obviously implausible NOx readings in live data
  • Regeneration cycles behaving unpredictably or being suppressed
  • Failed emissions test with the engine running normally
  • No drivability complaint at all in the early stages

Diagnostic steps

  1. 1.Connect a scan tool and establish first whether the sensor module is communicating at all. Present but reporting a fault, and completely absent from the bus, are two different problems with two different causes.
  2. 2.Read codes from the aftertreatment controller as well as the engine module. These sensors report through more than one path on many systems and the more specific fault is often stored elsewhere.
  3. 3.Locate the sensor's control box physically and inspect it. It is a sealed unit mounted near the exhaust, and heat damage, cracking or corrosion there is visible without any test equipment.
  4. 4.Unplug and examine the connector carefully for green corrosion, melted pins and spread terminals. On the downstream position this connector sits where salt and water collect.
  5. 5.Confirm supply voltage and ground at the sensor module before assuming the module itself has failed. A sensor that cannot power up cannot report, and the fault looks identical to a dead sensor.
  6. 6.Check bus continuity and integrity between the sensor and the module only after the communication status is known, and understand that a continuity test on these wires does not verify the measurement path.
  7. 7.Inspect the harness along its full route, concentrating on the sections that run closest to the exhaust and the particulate filter. Repeated regeneration heat is what kills wiring in this position.
  8. 8.After fitting a replacement, confirm the new sensor appears on the bus and returns live values. Many systems require an initialisation step, and a sensor that never comes online reproduces the original code exactly.

Repair cost

$150$1,200

A downstream NOx sensor assembly is typically $400 to $900 fitted, and the price reflects that you are buying a small electronic control module with a probe attached rather than a simple sensor. Connector or harness repair, where the damage is genuinely outside the sealed assembly, runs $150 to $450. Some vehicles require the replacement to be initialised or coded, adding $80 to $180. Diagnostic time is $100 to $220. Because the probe and the controller are almost always one non-separable part, repairing a damaged sensor lead is rarely an option.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with nox sensor replacement 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 P229E?

In the short term yes, since the engine itself is unaffected and the vehicle will drive normally at first. The reason not to leave it is specific to diesels: when the module cannot verify emissions performance, many manufacturers escalate through warnings to a reduced power inducement strategy, sometimes with a countdown of remaining miles or engine starts. That escalation can be abrupt and is not something you want to discover on a long journey. Have it looked at before the system starts limiting the vehicle.

Why will a multimeter not find this fault?

Because the wires you would be testing are not carrying the measurement. A modern NOx sensor has its own electronic controller built into the harness, and that controller sends finished values to the engine module over a data bus. So the connection can be electrically perfect while the sensor's controller has failed, dropped off the bus or never powered up — and continuity would read fine in every one of those cases. Start with a scan tool that can show whether the sensor module is communicating, then use a meter to investigate what you find.

Why do these sensors fail so often?

Location. The controller is a sealed electronic module mounted on or beside the exhaust, which is the harshest place on the vehicle to put electronics — constant heat, constant vibration, and full exposure to road salt and water. The downstream position is worse again, because every regeneration cycle drives exhaust temperature deliberately high and holds it there, and a sensor that has done a hundred thousand miles has been through that hundreds of times. The box and the connector usually give out well before the probe does.

Is the code always the sensor, or could it be wiring?

Wiring and connectors are genuinely common causes, particularly on the downstream position where salt collects, so they are worth inspecting properly before ordering anything. The awkward part is that it rarely changes the repair. The probe, its lead and the controller box are sold as one assembly on almost every application, so damage anywhere inside that assembly means a complete sensor. Only damage to the vehicle-side harness and connector — outside the sealed unit — can be repaired on its own.

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.