FORScan forum

Hi
I have a 2008 Focus 1.6 TDCI thats had the missfortune of running on its own engine oil and wrecking the engine.
I have found a replacement engine from a 2010 model but it has a different part no on the injectors.

The original engine has injector Part No 0445110259. When i have previously recoded these I have used the first 8 digits of the injector code.

The new Injectors are part No 0445110353. The style of the coding looks different.

I have spoken to Bosch technical who confirm that the coding is indeed different and requires 9 digits instead of 8.
Is this functionality to add 9 digit codes avalible within Forscan? Or is it he cas that my ECU willnot accept 9 digit codes?

Thanks in advance

Carl

The new engine has another PCM. At least calibration file is different (may be hardware is different as well, we don't know). If you solve this problem somehow, FORScan will be able to re-program the 9-digit injector codes on your new engine.

The engine is in and running well without putting in the correct codes,just around the 1800rpm range i feel could be improved maybe by using thr correct codes. How do i input the 9 digit codes as forscan appears only to request 8

carlb wrote:The engine is in and running well without putting in the correct codes,just around the 1800rpm range i feel could be improved maybe by using thr correct codes. How do i input the 9 digit codes as forscan appears only to request 8

It is not possible with FORScan (as well as with majority other software), because your old PCM is programmed for 8-digit codes. FORScan detects type of PCM, it will not allow to enter 9 digit codes in PCM that is designed for 8 digit codes etc. Even if you find a software that can do it, and even if your PCM will accept the 9-digit code (what we seriously doubt in), the PCM itself will not work with this code correctly.

We do not think the high RPM problem is related to injectors. Most likely, it is related to the calibration. New engine requlires new calibration file.

Hi Thanks for the reply, it makes perfect sense. I will not worry too much as the car is running well enough.
Do you have any plans to add a dpf delete function to Forscan in the future? as it was the DPF that caused my original problem.

carlb wrote:Do you have any plans to add a dpf delete function to Forscan in the future? as it was the DPF that caused my original problem.

This function requires at least reprogramming PCM that is not implemented yet. It is planned to implement the re-flashing in the future versions.