Ziggemby Posted September 19, 2016 Share Posted September 19, 2016 I have got now several times same issue that Focus 2006 1.8TDCi informs me about Engine System Fault and then Acceleration reduced. This usually within a minute after I start the engine. I replaced the battery already but no help. After cleaning the errors from ECU I can restart the engine and continue driving normally without any issues. Could this be caused by the common instrument cluster issue mentioned in many forums? If so what is the correct (low budget) fix for that? Thanks! When I scan the error codes I will get the lists below Current Fault Log ------------------ ECU reports no current faults Pending Fault Log ------------------ U0001: null U0073: null U0121: null U0131: null U0140: null U0155: null U2197: null Historic Fault Log ------------------ ECU reports no historic faults Other discovered fault codes (possibly pending, current or manufacturer specific) ---------------------------------------------------- P0571: Cruise Control/Brake Switch A Circuit U1900: null U2012: null U2200: null End of report. Current Fault Log ------------------ECU reports no current faults Pending Fault Log ------------------ U0001: null U0001: null U0073: null U0073: null U0121: null U0121: null U0131: null U0131: null U0140: null U0155: null U2197: null U2197: null Historic Fault Log ------------------ECU reports no historic faults Other discovered fault codes (possibly pending, current or manufacturer specific) ---------------------------------------------------- P0571: Cruise Control/Brake Switch A Circuit P1622: null U1900: null U2200: null End of report. Current Fault Log ------------------ECU reports no current faults Pending Fault Log ------------------ U0001: Unknown code - More information may be available on the web U0073: Unknown code - More information may be available on the web U0121: Unknown code - More information may be available on the web U0131: Unknown code - More information may be available on the web U0140: Unknown code - More information may be available on the web U0155: Unknown code - More information may be available on the web U2197: Unknown code - More information may be available on the web Historic Fault Log ------------------ECU reports no historic faults Other discovered fault codes (possibly pending, current or manufacturer specific) ---------------------------------------------------- U1900: Unknown code - More information may be available on the web U2012: Unknown code - More information may be available on the web U2200: Unknown code - More information may be available on the web U2510: Unknown code - More information may be available on the web End of report. Quote Link to comment Share on other sites More sharing options...
Ziggemby Posted September 21, 2016 Author Share Posted September 21, 2016 Any views should I start to disassemble instrument cluster to see if there are cold joints? Quote Link to comment Share on other sites More sharing options...
Ziggemby Posted September 22, 2016 Author Share Posted September 22, 2016 Guys please provide your view of the root cause for this fault Quote Link to comment Share on other sites More sharing options...
Tdci-Peter Posted September 22, 2016 Share Posted September 22, 2016 On 19/09/2016 at 10:11 PM, Ziggemby said: Could this be caused by the common instrument cluster issue mentioned in many forums? If so what is the correct (low budget) fix for that? At a guess, yes! I fixed one for £0.00 (though I had to splash out £10 on an ELM327 to use with Forscan, but that was a very worthwhile investment. Forscan would provide more info on all those DTCs. But the common 2006 fault mode generates lots of U codes. For my fix, see: http://www.fordownersclub.com/forums/applications/core/interface/file/attachment.php?id=40491 Any questions, post here. Quote Link to comment Share on other sites More sharing options...
Ziggemby Posted September 23, 2016 Author Share Posted September 23, 2016 Thanks for great instructions! I will try first by cleaning the connector if it does not help then some soldering action. 1 Quote Link to comment Share on other sites More sharing options...
Ziggemby Posted September 25, 2016 Author Share Posted September 25, 2016 Connector cleaning was enough for one day / ~6 engine starts but now below codes appeared again. I think I must proceed to soldering phase... Current Fault Log ------------------ ECU reports no current faults Pending Fault Log ------------------ U0001: null U0001: null U0073: null U0073: null U0121: null U0121: null U0140: null U2197: null Historic Fault Log ------------------ ECU reports no historic faults Other discovered fault codes (possibly pending, current or manufacturer specific) ---------------------------------------------------- U1900: null U2012: null End of report. Quote Link to comment Share on other sites More sharing options...
Tdci-Peter Posted September 26, 2016 Share Posted September 26, 2016 7 hours ago, Ziggemby said: Connector cleaning was enough for one day / ~6 engine starts but now below codes appeared again. I think I must proceed to soldering phase... If moving the connector produced a temporary change, then at least that does point to where the fault is likely to be. I measured the resistance across the CAN bus connection (using the diagnostic connector first, then the pins on the IC when I had access to them.) It should be very close to 60ohms while connected. The IC on its own should read 120 ohms, stable & reliable, on the HS-CAN bus pins on its connector. pin nos in the pdf. (17-18). The MS-CAN bus is on pins 22 & 23, and should read the same. It is useful to keep testing for the fault, soldering more connections than needed may cause more problems than it solves. Good light & a magnifying glass is highly recommended. I had to clear various DTCs after re-fitting it, I used Forscan for this, as it can access all modules. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.