Petes Posted November 19, 2008 Share Posted November 19, 2008 Does anyone know what this means. 23-04 Unable to detect remote CAN mode error logged on a 2000 td5 D2. Rgds Pete Quote Link to comment Share on other sites More sharing options...
cipx2 Posted November 19, 2008 Share Posted November 19, 2008 ...... 2000 td5 D2........ Auto or manual? My guess is auto. Quote Link to comment Share on other sites More sharing options...
Petes Posted November 19, 2008 Author Share Posted November 19, 2008 Auto or manual? My guess is auto. Yep Auto. Its not mine. I am just trying to help someone out. Quote Link to comment Share on other sites More sharing options...
cipx2 Posted November 19, 2008 Share Posted November 19, 2008 The ECM ecu and the EAT ecu (electronic auto transmisssion) are communicating via a CAN (control area network) bus. These are the only 2 devices using the CAN bus on D2.. In order for one device, say the ECM, to send something to the other, say the EAT, it must first make sure the other is listening and the bus is in receive (listen) mode. The CAN bus can have different states called modes (listen mode, loopback mode, disabled mode, normal mode - I think these are all). Basically, the fault code says that the ECM can't determine what mode/state is the controller connected at the other end in. Simply said, there's a communication error between the ECM and the EAT. I'm guessing again. I think this fault is CURRENT and the auto box might be in limp mode. Is this right? Quote Link to comment Share on other sites More sharing options...
Ally V8 Posted November 20, 2008 Share Posted November 20, 2008 As said the DII only uses the CAN for 2 ECU's,the engine ecu and the autobox one. It is just a twisted pair of wires,usually yellow/white or white yellow.Rarely is there a fault with these,but its easy to check continuity/short to earth etc to confirm their condition.Most often its a sensor failure or wiring fault elsewhere,once the can wires have been checked the first thing to do is get the computer on the car and view ALL live data you can from both ECU's.Something will be missing or implausible.With implausible or missing data the ECU's do not even try to communicate and just log faults. Often its fairly obvious where the fault lies - esp if you have access to Testbook which shows out of range values in grey instead of black.If you are using a generic scanner then it could be more difficult. 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.
Note: Your post will require moderator approval before it will be visible.