Check engine lights + fault codes

[Liner]

Hi All,

I was driving my 1.6tdci focus this morning and there was a slight shimmy- I thought it was in my mind. During the next run the check engine light came on.

I got home and hooked up to forscan to get these codes:

PCM P2002

FACM P2409-60

 

I cleared the modules, tried again and they came up again.

So I read up on both and ran through a few of the self tests... Usually this helped a lot, but then on two tests the tests were aborted and I was told to contact the developer. Can anti-spyware cause this issue?

This also gave me two new U codes I can't erase...

My next step was to do the forced Particle filter regen- this did not remove the code, but did upset the neighbours!

Below is the full log (faults) followed by the individual fault logs (fault1 through to fault4)

 

Help!

 

Johnna

[Tdci-Peter]

5 hours ago, Liner said:

Usually this helped a lot, but then on two tests the tests were aborted and I was told to contact the developer. Can anti-spyware cause this issue?

This also gave me two new U codes I can't erase...

Usually those U1900 codes are not important, they can happen when connecting up the diagnostics. But if they can not be cleared, or perhaps it is they keep occurring, then it does indicate a bus problem, with a failure to communicate between modules. That would also explain the failure to do the self tests.

The Dosing Module, or FACM, is on the HS-CAN bus. There is a connector on this bus that sometimes gives trouble, low down in front of the passenger front door, behind the trim panel.

Keep on checking, and see if new codes appear. Bus problems can have a wide range of symptoms.

Not sure about the spyware bit, is that some software on the laptop? If so, it seems unlikely to have that sort of effect.

If your version of Forscan has been on your computer for some time, go to the Forscan site and download the latest version.

 

[Liner]

Thank you Peter, I had downloaded the newest forscan to use too and got the same results. 

Yeah, spyware and malware can sometimes block certain software functions, which may be an issue with the inoperative forscan functions.

 

However, I have a resolution to the original issue. On inspection of the two tubes between the EGR and the DPFE sensor this morning the wider bore tube was totally ruptured. I had some correct bore braided hose in store, so I sleeved it with the insulating matting and refitted that. The CEL disappeared and using forscan I was able to remove all of the fault codes.

On two self-tests, no DTCs were generated at all.

 

Happy days!