P2002 – Particulate Trap Efficiency Below Threshold Bank 1

P2002 is a powertrain Diagnostic Trouble Code (DTC) that points to a diesel emissions control efficiency problem detected by the engine controller. In SAE J2012-DA wording, it’s associated with Diesel Particulate Filter (DPF) efficiency being below an expected threshold, based on how the system’s sensors and calculated soot loading behave. The exact enable criteria and which sensor signals are used can vary by make, model, and year, so you confirm the root cause with basic electrical checks and plausibility testing of the pressure/temperature signals and exhaust flow conditions.

What Does P2002 Mean?

P2002 is commonly defined in SAE-style terms as Diesel Particulate Filter efficiency below threshold. SAE J2012 defines the DTC structure and many standardized descriptions, and the standardized wording is published in the SAE J2012-DA digital annex. Even with that standardized description, how a specific vehicle decides the threshold is met (or not met) varies by calibration and hardware, so diagnosis must be test-driven.

This code is shown without an FTB (Failure Type Byte) suffix. If an FTB were present (for example, a hyphen and extra characters), it would further classify the failure mode as a subtype defined by the vehicle manufacturer or the applicable standard, but the base meaning of P2002 would remain centered on DPF efficiency being below the expected threshold.

Quick Reference

• Code: P2002
• SAE-style meaning: Diesel Particulate Filter efficiency below threshold
• System: Powertrain / diesel aftertreatment (emissions control)
• What it really indicates: The controller calculated DPF performance/soot loading isn’t matching expected values
• Commonly associated with: Differential pressure sensor signal plausibility, exhaust temperature sensing, regeneration frequency/completion, exhaust leaks/restrictions
• Typical drivability impact: Reduced power or limited regeneration capability depending on strategy
• Basic confirmation approach: Verify sensor power/ground/reference, compare pressure/temperature signals to operating conditions, check for leaks and restriction, confirm regen results with scan data/Mode $06 where available

Real-World Example / Field Notes

A common shop scenario is a diesel truck that mostly does short trips: the customer notices the cooling fans running more often, a warning message about emissions, and eventually a power reduction. P2002 sets after several drive cycles because the controller keeps seeing DPF loading climb faster than expected or sees too little change during attempted regeneration. In the bay, you might find a differential pressure reading that looks high at idle, but the fix isn’t automatic: the cause could be a restricted DPF, a biased pressure sensor or plugged sensor hoses, an exhaust leak ahead of the DPF changing the pressure/flow relationship, or a regeneration that never completes due to temperature signal plausibility issues. The fastest path is verifying the sensor’s 5V reference, ground integrity, and signal behavior under known conditions (key on/engine off, idle, snap throttle, and a controlled road test), then matching those measurements to scan tool data before replacing anything.

P2002 is a powertrain diagnostic trouble code that, under SAE J2012-DA wording, points to a Diesel Particulate Filter (DPF) efficiency condition below an expected threshold. The exact enable criteria and which sensors the Engine Control Module (ECM) uses to judge “efficiency” can vary by make, model, and year, so you confirm the root cause with basic tests: scan data plausibility, differential pressure behavior, exhaust temperature response, and electrical checks on power/ground/reference and signal integrity. Don’t assume a clogged filter or a specific sensor has failed until the numbers prove it.

Symptoms of P2002

• Check engine light Malfunction Indicator Lamp (MIL) on, sometimes after extended highway driving or repeated short trips.
• Reduced power Noticeable limp/derate, especially under load or during acceleration.
• Poor fuel economy Increased fuel consumption due to frequent regeneration attempts or altered fueling strategy.
• Regeneration concerns Regens occurring very often, taking longer than normal, or not completing.
• Exhaust odor/heat Hot exhaust smell or elevated underbody heat during attempted regenerations.
• Rough running Slight surging or unstable idle on some platforms during active regen events.
• Hard start after shutdown Occasional extended crank after a hot soak if regen-related strategies were active.

Common Causes of P2002

Most Common Causes

• DPF soot loading high enough that the calculated/observed filtration efficiency falls below threshold (often from repeated short trips or interrupted regenerations).
• Exhaust leaks (commonly associated with joints, flex sections, clamps, or gaskets) upstream or near the DPF that skew pressure/flow readings and efficiency calculations.
• Differential pressure sensor bias or slow response (sensor or hoses/lines restricted, cracked, melted, or water/condensate affected), causing implausible DPF pressure drop.
• Exhaust Gas Temperature (EGT) sensor drift (commonly associated with pre/post DPF sensors) leading to incorrect regen control and efficiency evaluation.
• Regeneration not occurring when commanded due to operating conditions (low fuel, wrong drive cycle, excessive idling) or frequent key-off events.

Less Common Causes

• Aftermarket exhaust/DPF modifications or incorrect replacement parts changing backpressure and modeled efficiency.
• Engine-out soot higher than normal from underlying issues (air intake restriction, boost leaks, injector imbalance, EGR system faults) that overload the DPF.
• Electrical issues: poor sensor power/ground, shared reference voltage problems, corrosion in connectors, harness chafing near hot exhaust.
• DPF substrate damage (cracked/melted) causing abnormal flow paths and misleading pressure/temperature behavior.
• Engine Control Module (ECM) possible internal processing or input-stage issue, considered only after all external wiring and sensor signals test good.

Diagnosis: Step-by-Step Guide

Tools you’ll want: a bidirectional scan tool with live data and service functions, a Digital Multimeter (DMM), a vacuum/pressure hand pump (as applicable), a low-pressure gauge or manometer, smoke machine (intake/exhaust capable), infrared thermometer or thermocouples, basic hand tools for hose inspection, and wiring back-probe pins.

1. Verify the code and capture freeze-frame data. Note coolant temp, vehicle speed, calculated soot load (if available), regen status, and any “time since last regen” style parameters.
2. Check service information for your exact vehicle because P2002 thresholds and monitored sensors vary by make/model/year. Confirm what the ECM uses (differential pressure, EGTs, calculated soot/ash model).
3. Do a visual inspection of the exhaust from turbo/downpipe area through the DPF. Look for soot trails, loose clamps, cracked flex sections, or missing gaskets that can affect flow and sensor readings.
4. Inspect DPF differential pressure sensor hoses/lines (if equipped): confirm they are not melted, kinked, restricted with soot/condensate, or swapped. Any restriction can create a false high/low pressure drop.
5. Use live data to compare differential pressure at idle versus a steady elevated rpm (for example, a held rpm in park per OEM guidance). Readings should change smoothly with airflow; a flatline, jumpy, or implausible signal points to sensor/line issues.
6. Check EGT sensor plausibility. During a commanded or active regeneration (if conditions allow), you should see predictable temperature rise and reasonable correlation between upstream/downstream sensors, not a stuck value or erratic spikes.
7. Electrical checks: with key on, verify sensor supply voltage (often 5V reference for pressure sensors), good ground (low voltage drop under load), and signal voltage within expected range. Wiggle-test harnesses near heat sources while watching live data for dropouts.
8. If exhaust leaks are suspected but not visible, smoke-test the exhaust (or use soapy water on cold joints with low pressure) and repair leaks before judging DPF efficiency.
9. If sensors and wiring pass, evaluate soot/ash loading evidence: frequent regens, high calculated soot, or high measured pressure drop under load. Confirm the engine is not producing excess soot (air filter restriction, boost leaks, fuel quality, injector balance per scan data where available).
10. After repairs or corrections, clear the code and perform the OEM drive cycle/regen verification. Recheck live data and confirm the monitor completes without returning P2002.

Professional tip: Don’t condemn the DPF based on one pressure reading. Validate differential pressure against airflow (idle vs elevated rpm vs loaded road test) and cross-check with temperature behavior during regen; a biased sensor, restricted hoses, or an exhaust leak can mimic “low efficiency” and will fail a replaced DPF just as quickly.

Possible Fixes & Repair Costs

Costs depend on what your test results show, because P2002 is typically set when the Powertrain Control Module (PCM) calculates a particulate filter efficiency value that doesn’t meet its expected threshold under specific operating conditions. Do not replace parts until you confirm the inputs used for that calculation.

• Low ($0–$180): If inspection and scan data show normal differential pressure readings but poor recent drive cycles, a correct regeneration/drive cycle, exhaust leak repair at joints, or cleaning carbon-loaded sensor tubes/hoses may be justified. You’re paying mostly for diagnosis time and small parts.
• Typical ($250–$1,200): If measured sensor signals are biased or unstable (verified by KOEO/idle/load tests), replacing a commonly associated differential pressure sensor, repairing wiring/connectors, or servicing plugged pressure lines is justified. Labor varies with access and corrosion.
• High ($1,200–$4,000+): If differential pressure is truly high under controlled load and temperature conditions and regeneration cannot reduce it, particulate filter service/replacement (and addressing the root cause of soot/ash loading) is justified. Costs swing with vehicle type, sensor count, and whether the filter is serviceable.

Only consider a PCM “possible internal processing or input-stage issue” after power/ground integrity, sensor reference/return, and signal plausibility all test good.

Can I Still Drive With P2002?

You can sometimes drive short distances with P2002, but you should treat it as a “limited time” situation. If the calculated particulate filter efficiency is below threshold, exhaust backpressure may be rising even if the vehicle still feels normal. Watch for reduced power, higher fuel use, frequent fan operation, or a regeneration request. If you notice heavy smoke, strong exhaust smell, abnormal heat near the exhaust, or the vehicle enters a reduced-power mode, stop driving and diagnose it.

What Happens If You Ignore P2002?

Ignoring P2002 can allow soot/ash loading to increase until regeneration is no longer effective, raising exhaust backpressure and temperatures. That can trigger reduced power, damage sensors, stress the turbocharger, and in worst cases overheat exhaust components. It can also prevent emissions monitors from running, leading to an inspection failure.

Last updated: March 1, 2026

Vehicles Commonly Affected by P2002

P2002 is commonly seen on diesel passenger vehicles and light trucks that use a particulate filter and differential pressure-based monitoring. It’s often reported on Volkswagen/Audi TDI applications, Ford Power Stroke light-duty diesels, and Mercedes-Benz/other European diesels, mainly because these platforms rely heavily on calculated efficiency using multiple sensor inputs and strict regeneration strategies. The exact threshold logic, sensor layout, and confirmation criteria vary by make, model, and year, so always confirm with scan data and basic electrical tests.