mondeo mk3 tdci crank sync

[oldbod]

Hi. Have a user on our uk talkford forum using forscan to troubleshoot a non-starting mondeo mk3 tdci car. He currently reports cps-state as showing alternately sync and error. My own car using forscan 2.2.3 windows switches between sync, synching, wait and error , at various times. My car (2002 build tdci , separate icu ) also cuts out when I attempt to drive it whilst monitoring cps_state though it appears to allow me to mildly increase engine rpm while stationary.

I have previously seen reports of cps_state showing error when monitored, possIbly again entirely correctly.

Obviously all of these could be down to genuine error states - flaky sensors, dual mass flywheels, etc., but i was wondering if it might be possible to clarify if cps_state is a value directly monitored from within icu/pcm or if forscan derives it from a combination of other inputs, and if any more was known about its impact on engine operation.

anyinput gratefully recieved...

[FORScan]

My car (2002 build tdci , separate icu ) also cuts out when I attempt to drive it whilst monitoring cps_state though it appears to allow me to mildly increase engine rpm while stationary.

This is correct PCM behaviour - in order to read data from ICU/FIP, FORScan has to switch module to special diagnostic mode. In this mode, engine stalls if you try to drive.

FORScan reads PID value from PCM, then converts it according to the formula in the database. State PIDs are displayed in a textual format, so FORScan has to decode it using some conversion table. For example, 0 means SYNCHED, 1 means WAITING etc. For ths CPS_STATE PID on Mondeo Mk3 FORScan knows only 3 states:

SYNCHED
WAITING
SYNCHING

If it says Error, it means some error occured while reading or calculating the PID. This may be either adapter problem (so FORScan was unable to get the data) or calculation problem (so if FORScan knows only 3 states above encoded as 0, 1 and 2 correspondingly, and receves value=3 that is missing in the table, it will shows Error). Specific reason can be found out by analysing internal FORScan logs as described on Contact Us page.

Also from exeprience, often Mondeo Mk3 TDCi engine non-starting problems are caused by fuel system.