Peugeot AdBlue Fault Solution: EDC17C60 and DCM6.2 on 3008, 5008, Rifter 1.6 / 2.0 BlueHDi
On Peugeot BlueHDi diesels the most common complaint is AdBlue: the “AdBlue fault, engine will not start in X km” warning and countdown. The cause is often the AdBlue tank and pump unit or the NOx sensor. The 1.6 and 2.0 BlueHDi use the Bosch EDC17C60 or the Delphi DCM6.2 / DCM7.1 family, and AdBlue solutions are available at ECU Prime on these ECUs.
Which BlueHDi, which ECU?
- Bosch EDC17C60: Stage 1, AdBlue / SCR, NOx, DPF, EGR, swirl (TVA), emission package; combined Stage 1 + AdBlue, start-stop off.
- Delphi DCM6.2A, DCM6.2C and DCM6.2: Stage 1, AdBlue / SCR, DPF, EGR, lambda and emission package; combined Stage 1 + AdBlue.
- Delphi DCM7.1A and DCM7.1B: Stage 1, AdBlue / SCR, DPF, EGR and emission package.
When a reset is not enough
Clearing the fault code only hides the warning for a while; if the sensor or pump fault remains, the countdown starts again. A lasting fix means reading the ECU and preparing a file for it. For the 1.5 BlueHDi see our MD1CS003 article. Models: 3008, 5008, 508, Rifter, Partner and Expert.
The ECU type depends on model year and engine. The exact type is confirmed from the ECU label or by reading it with a diagnostic tool; send a photo of the label on WhatsApp and we will tell you which file applies.
Service pages: Peugeot AdBlue fault solution, DPF fault solution, EGR fault solution.
How it works
- Reading: upload the original file read with your tool, or visit one of our locations.
- Calibration: the file is prepared for the exact engine and ECU software version, checksum corrected; the original is archived.
- Application and check: fault scan and run / road test after writing.
Workshops get the same solutions through the ECU Prime file service.
Emission-related software is offered only for uses permitted by applicable law (off-road / closed-site use, racing, export, diagnostics); road use and inspection compliance are the owner’s responsibility.