New DPF fitted, malfunction and limp mode still on

[MicktheDee]

Hi, I’m hoping someone can help as I’ve almost gave up! My  2013 titanium x went into limp mode due to dpf and wouldn’t regen, so I fitted a new dpf, disconnected battery to clear computer and the thing is still in limp mode with exact same fault code..

Is there anyway to sort this???

thank you

[TomsFocus]

Hi, we're gonna need some more info...  Which engine size?  Which model even!?  Ford make a few!

What is the exact fault code you're getting?  It's much more likely to be a faulty sensor or vaporizer than the actual DPF at fault.

[MicktheDee]

Sorry 😐 It’s the mondeo 2,0l tdi, tit x. These are the codes that came up and also when I got forscan to try and regen myself it said it was completely blocked so couldn’t. I fitted a new dpf myself(which might not have been wise) nothing changed 😫😂

[MicktheDee]

P246c

p2463

p246b

also saying 300% soot accumulation 

[Frembrit]

Yeah, I wouldn't drive that any more for now...Mine went in to limp mode at around 180% soot load.

Although if you've only just fitted the new DPF then it shouldn't be that high...Did you reset the DPF learned value? I wouldn't have thought that disconnecting the battery would do this, I used a laptop, a modified ELM327 lead and Forscan software. Try that but I suspect that the fuel Vaporiser in the exhaust is blocked and therefore it won't ever do a regen.

It blocks up due to the build up of carbon inside the vaporiser unit, and to clean it would involve removing it from the exhaust pipe and spending time trying to scrape it clean internally through a tiny hole (which won't work)  or by removing the glow plug which is possible and this is what I did when I tried to clean mine, however it didn't work. It's also possible that the glow plug could be on it's way out too. Changed mine 3 years ago and it's been fine since, though I regularly use premium diesel now.

Have a read here too https://talkford.com/community/topic/314066-dpf-error-code-p2463/?st=0

 

[Tizer]

You could try the trick of disconnecting the MAF Sensor, starting the engine to induce a new fault code, stopping and reconnecting the MAF again and clearing all the fault codes with FORScan as per this sticky thread in the FORScan Forum https://forscan.org/forum/viewtopic.php?f=6&t=247#p630  

It is for the 1.6 engine though and an earlier build than yours so it may not be applicable to your 2.0 engine.