Capture DTC context
Document the code, operating condition and timing together.
UNDERSTAND THE FAULT CODE
P2002 after chiptuning: check DPF efficiency and calibration context
Review the fault code, operating condition, hardware and calibration together—not isolated map values.
TECHNICAL CONTEXT
What matters for this topic.
P2002 means diesel particulate filter efficiency below threshold on bank 1. The ECU believes the DPF is not filtering as expected or that the sensor/model data suggests reduced filter efficiency.
The cause can be a loaded or damaged DPF, pressure sensor problems, blocked lines, exhaust leaks, temperature issues or implausible DPF modelling. After tuning, it is important to separate true hardware issues from calibration or model conflicts.
A poor tune can increase soot production when injected quantity, air mass and smoke limitation are not balanced. Changed exhaust temperature behavior or poor regeneration logic can also make P2002 more likely.
Good files keep combustion, air path, smoke limiters and protection functions coherent. They do not blindly alter emission-related strategies and avoid unnecessary DPF stress.
ECU-JOBS SUITE
How the Suite supports the workflow.
Review calibration
Compare relevant maps and changes with the original.
Separate causes
Do not prematurely mix software logic, sensors and mechanical causes.
NEXT STEPS
Put technical knowledge into practice.
Create a project from the original, check available detection and Solutions, and edit changes as a separate version.