P226D 'Damaged or Substrate Missing' 2016 T6 Shuttle - Is the DPF for the bin?

Robert Hallyburton

322,000 miler
VIP Member
T6 Pro
Evening everyone,

My T6 was in for an issue relating to the EGR which ended up getting replaced. As part of the work completed the Garage recommend getting at DPF flush done at the same time by a third party. Vehcile back now but getting a P226D Fault code 'Damaged or Substrate Missing' which eventually brings the EML on

Does this mean the DPF is toast now and needs replaced or is it there anything else we should consider.

Thanks in advance

Robert
 

Attachments

  • Like
Reactions: mmi
It is not necessarily a toast DPF, but could be that the sensors are a bit "confused" after the clean.
If you clear the fault code does it come back on?
Further diagnostics can be done by running continuous block map of the DPF sensor info to see what they are reporting.
 
It is not necessarily a toast DPF, but could be that the sensors are a bit "confused" after the clean.
If you clear the fault code does it come back on?
Further diagnostics can be done by running continuous block map of the DPF sensor info to see what they are reporting.
Yes, fault code comes back on.
 
Dont you have to reset the DPF values after a clean or replacement? Maybe the ECU expects a high soot level but the sensor is contradicting that.
 
DPF flush done at the same time by a third party. Vehcile back now but getting a P226D Fault code 'Damaged or Substrate Missing' which eventually brings the EML on
Possibly the filter substrate was damaged?
Is the exhaust sooty now?


Would be interested to get a couple of engine blockmap files.
1) ignition ON, engine OFF (preferably cold engine)​
2) engine idling (preferably cold engine)​
3) hot engine idling (after a 20 (minimum) driving​



How-to create a blockmap file:

Ignition ON
[VCDS]
[Applications]
[Controller Channel Map]
- Single Controller Address = 01
- Login or security access code: Leave blank
- Function: Measuring values
- Output: CSV file
[Go]


The result files (.csv) are saved into directory C:\Ross-Tech\VCDS\Logs



PS. Ideally would be nice to capture a log as below:
 
You could just put some smoke through it and see what comes out of the tail pipe, if it’s holed smoke will emit and it’s stuffed.
 
Back
Top