P2059 – Reductant Injection Air Pump Control Circuit/Open

P2059 is a powertrain diagnostic trouble code that, in SAE J2012-style terms, points you toward a circuit-level signal plausibility problem in an emissions-related system, most often within the reductant (Diesel Exhaust Fluid) control strategy on diesel applications. The exact component and monitoring logic can vary by make, model, and year, so you should confirm the definition in service information and then prove the fault with basic electrical testing. Treat it as a “signal doesn’t make sense” problem until measurements show a clear wiring, sensor, or actuator issue.

What Does P2059 Mean?

SAE J2012 defines the DTC structure and general formatting, and standardized DTC descriptions are published in the SAE J2012-DA digital annex; however, many manufacturer implementations—especially emissions sub-monitors—can vary in the exact component-level interpretation. For P2059, the consistent, safe takeaway is that the Powertrain Control Module (PCM) is seeing a reductant/emissions-related circuit signal that fails a plausibility check against expected operating conditions.

This code is shown without an FTB (Failure Type Byte) suffix. If your scan tool or OEM software shows P2059 with a hyphenated suffix, that suffix is an FTB identifying a subtype (for example, a specific signal behavior such as plausibility, range/performance, or correlation) while the base code remains P2059. What makes P2059 distinct is that it’s typically not a simple “voltage high/low” detection; it’s often set when the PCM can’t reconcile an input or commanded output with what it expects to see on that circuit in real time.

Quick Reference

• Code: P2059 (shown without an FTB; an FTB, if present, is a subtype)
• System: Powertrain, emissions / reductant management (vehicle-dependent)
• What it means: Circuit signal plausibility fault detected by the PCM
• Commonly associated with: DEF dosing/quality/temperature/pressure-related circuits, harness/connectors, power/ground integrity (varies by vehicle)
• Typical driver notice: Check Engine light, possible emissions warnings or reduced power depending on strategy
• Best first action: Confirm OEM definition, pull freeze-frame data, then verify power/ground/reference and signal behavior with a meter or scope

Real-World Example / Field Notes

In the bay, P2059 commonly shows up after a DEF event: the tank was run low, fluid was contaminated, the vehicle sat through a freeze/thaw cycle, or the harness got tugged during unrelated work. One pattern I see is a “good part” getting replaced because the symptom feels like a component problem, but the root cause ends up being voltage drop on a shared ground, moisture in a connector, or a rubbed-through section of loom near the exhaust/underbody. Another frequent scenario is a plausibility mismatch during a commanded test: the PCM commands a reductant-related actuator, but the feedback circuit doesn’t respond as expected, so proving command, power/ground, and signal integrity becomes the fastest path to the real fix.

Symptoms of P2059

• Check Engine Light illuminated (may be intermittent at first).
• Emissions readiness monitors not completing, causing an inspection failure.
• Reduced power or torque limitation when the Engine Control Module (ECM) protects the aftertreatment system.
• Increased fuel use due to altered aftertreatment strategy or repeated regeneration attempts (application dependent).
• Regeneration behavior more frequent or abnormal (for vehicles equipped with Diesel Particulate Filter (DPF) or similar aftertreatment).
• Rough running or drivability complaints during certain operating conditions if fueling/airflow is adjusted to manage aftertreatment temperatures.
• Burning odor or higher exhaust heat noticed during attempted aftertreatment events (not always present).

Common Causes of P2059

Most Common Causes

• Wiring/connector issues in an aftertreatment-related harness: chafing, water intrusion, backed-out terminals, corrosion, or poor pin fit causing signal plausibility errors.
• Power or ground instability feeding an aftertreatment component or sensor circuit (shared grounds are common); confirmed by voltage drop under load.
• Signal integrity faults such as high resistance in a signal return, intermittent opens, or unintended contact to another circuit that makes the ECM see an implausible signal relationship.
• Sensor performance drift in a commonly associated aftertreatment sensor (exact sensor varies by make/model/year), where the value is electrically “in range” but fails plausibility versus operating conditions.
• Aftertreatment actuator response issues (application dependent) where commanded change does not produce the expected feedback, pointing to circuit or actuator problems rather than a single guaranteed part.

Less Common Causes

• Exhaust leaks upstream of aftertreatment sensors affecting measured oxygen/temperature/pressure relationships and triggering plausibility faults.
• Contamination (oil, soot, coolant, fuel additives) impacting sensor ports or reference passages, skewing readings without an obvious electrical failure.
• Mechanical restriction in the aftertreatment path (application dependent) that makes pressures/temperatures behave abnormally and appear “implausible” to the ECM.
• Control module input-stage issue possible internal processing or input conditioning concern, but only considered after all external wiring, power, grounds, and signals test good.
• Calibration/updates where an OEM software revision changes plausibility thresholds; confirm with service information rather than guessing.

Diagnosis: Step-by-Step Guide

Tools you’ll use: scan tool with live data and Mode $06 (if supported), digital multimeter (DVOM), back-probe pins or pierce probes, wiring diagram/service information, smoke machine (or regulated low-pressure leak tester), basic hand tools for connector inspection, infrared thermometer or thermal camera (helpful), and a test light or fused jumper for load-testing power/grounds.

1. Verify the complaint: record freeze-frame data, fuel level, temperatures, and operating mode when P2059 set. Clear the code and see if it returns on a short road test under similar conditions.
2. Confirm system context: because P2059 can be manufacturer-defined at the component level, use service information to identify which aftertreatment signal/circuit the ECM is flagging. Don’t assume a specific sensor or actuator.
3. Visual inspection first: inspect the relevant harness routing near the exhaust/aftertreatment hardware for heat damage, abrasion, or melted conduit. Unplug connectors and check for corrosion, spread terminals, or moisture.
4. Check power and ground under load: with the circuit powered, perform voltage-drop tests on the suspect component’s ground and power feeds. Look for excessive drop that indicates resistance, not just “continuity.”
5. Reference voltage checks: if the circuit uses a 5V reference, verify the reference is stable (not sagging) and that sensor ground is near 0V relative to battery negative.
6. Signal plausibility: watch the signal PID(s) on live data. Compare the value against expected behavior during controlled conditions (idle, steady cruise, snap throttle) and against related PIDs (temperature/pressure/airflow) for logical correlation.
7. Wiggle and heat test: gently wiggle the harness and connectors while monitoring the signal on the scan tool and/or DVOM. If heat-related, warm the connector area carefully and look for dropouts or spikes.
8. Network and sensor sanity: if data appears erratic, verify the sensor is not “floating” by checking for intermittent opens/shorts to power/ground with key on/engine off and key off resistance tests per service info.
9. Mechanical influence checks: if electrical tests pass, check for exhaust leaks and restrictions that could create implausible pressure/temperature relationships. Use smoke testing and temperature mapping before condemning electronics.

Professional tip: when P2059 is a plausibility-type fault, the fastest path is usually proving the circuit’s power, ground, and signal are stable under the exact conditions when the code sets—use freeze-frame to recreate those conditions, then load-test the feeds and log the PID for dropouts instead of replacing parts based on a “looks good” continuity check.

Possible Fixes & Repair Costs

Costs depend on what your tests prove. A good shop will confirm the circuit and signal behavior first, because P2059 can be set by different subsystems depending on make/model/year, and SAE J2012 structure doesn’t guarantee a single component-level definition.

• Repair damaged wiring/connector (justified by visible corrosion, loose terminals, failed wiggle test, or excessive voltage drop on power/ground): low $0–$80 DIY materials; typical $120–$350 shop.
• Clean/secure grounds and power feeds (justified by >0.1V drop on grounds under load or unstable supply voltage during actuation): low $0–$40; typical $100–$250.
• Replace a commonly associated sensor/actuator (only after confirming incorrect resistance/current draw, out-of-spec output, or poor plausibility versus command): typical $200–$700; high $800–$1,500+ if access is difficult.
• Control module issue (only after all external wiring, power, ground, and signal integrity tests pass; possible internal processing or input-stage issue): high $900–$2,500+ including setup and configuration where required.

Labor and access drive the range most: exhaust-area components, heat shielding, and seized fasteners can turn a straightforward electrical fix into a longer job.

Can I Still Drive With P2059?

Usually you can drive short distances, but you should treat P2059 as a “confirm-and-fix soon” powertrain fault. Depending on how your vehicle defines P2059, the Engine Control Module (ECM) may limit certain functions, reduce power, or disable a readiness monitor. If you notice reduced power, harsh operation, stalling risk, or an overheating smell, stop and diagnose. If it’s only a light with normal drivability, drive gently and avoid towing until testing confirms what system is involved.

What Happens If You Ignore P2059?

Ignoring P2059 can lead to worsening wiring damage (heat, vibration, corrosion), repeated monitor failures, reduced fuel economy, and failed emissions inspection. If the fault is in a control circuit that commands an actuator, prolonged incorrect operation can also stress the actuator or related components, turning a small electrical problem into a more expensive repair.

Related Pump Reductant Codes

Compare nearby pump reductant trouble codes with similar definitions, fault patterns, and diagnostic paths.

• P2061 – Reductant Injection Air Pump Control Circuit High
• P2060 – Reductant Injection Air Pump Control Circuit Low
• P2448 – Secondary Air Injection System Switching Valve Control Circuit/Open
• P2062 – Reductant Supply Control Circuit/Open
• P2056 – Reductant Injector Circuit/Open Bank 2 Unit 2
• P2053 – Reductant Injector Circuit/Open Bank 1 Unit 2

Key Takeaways

• SAE structure, variable meaning: P2059 is a powertrain DTC by format, but the exact component-level interpretation can vary by make/model/year; confirm using scan data and circuit tests.
• Test before replacing: Verify power, ground, and signal integrity (including voltage drop and load testing) before condemning sensors, actuators, or modules.
• Plausibility matters: Compare commanded states to feedback and look for intermittent opens/high resistance with wiggle and heat/vibration checks.
• Modules are last: Consider an ECM issue only after external wiring and inputs test good and the fault can be reproduced.

Vehicles Commonly Affected by P2059

P2059 is commonly seen on vehicles with more complex emissions and powertrain control strategies, where multiple sensors and actuators are monitored for plausibility. It’s often reported on some Ford, Volkswagen/Audi, and GM applications, plus certain light-duty diesel platforms, because these architectures may monitor additional exhaust or emissions-related actuators and their circuits. The key is that the same code can map to different monitored circuits depending on the manufacturer’s implementation and calibration.

FAQ

Can I clear P2059 and see if it comes back?

You can, but do it in a controlled way. Clear the code, then run a short drive while watching live data and readiness status. If P2059 returns quickly, that usually points to an electrical integrity issue you can reproduce (power/ground drop, connector pin fit, or signal plausibility). If it takes days, focus on intermittent conditions: harness movement, moisture intrusion, and heat-related resistance changes.

Is P2059 an emissions-related code?

Often it is, but not always. The “P” format indicates a powertrain fault, and many P2059 definitions in OEM literature relate to monitored emissions hardware or control circuits. However, SAE J2012 describes structure and standardized formatting, and the exact monitored component may vary by application. Confirm by checking the scan tool’s DTC description for your VIN and identifying which monitor or actuator test fails.

Can a weak battery or charging problem trigger P2059?

Yes. Low system voltage or unstable charging can cause control modules to see implausible signals or actuator current that doesn’t match commands, especially during cold starts or high electrical loads. Test battery state of charge, alternator output, and voltage drop on main grounds. If you see voltage sag during actuator commands or cranking, address the supply issue first, then re-test to confirm P2059 does not return.

What tests should a shop perform before replacing parts for P2059?

Expect basic electrical and plausibility testing: confirm the DTC sets, pull freeze-frame, and watch live data for the affected input/output while commanding tests if supported. Then check power, ground, and reference voltage (if used), measure voltage drop under load, and perform a wiggle test on connectors and harness routing. If it’s a controlled actuator, measure current draw and compare command versus feedback.

Can an Engine Control Module cause P2059?

It can, but it’s not the first suspect. An ECM can set P2059 if an input stage or driver circuit behaves incorrectly, but you only go there after proving external wiring, grounds, power feeds, and the sensor/actuator itself are within spec and the signal remains incorrect at the module connector. If all external tests pass and the fault is repeatable, a possible internal processing or input-stage issue becomes more likely.