Strange goings on with auto

I actually flushed the cooler as well as swapping out the crap fittings for screw ons when the front end was out. Soaked both coolers in assorted solvents, HINT, don't forget to drain and flush before giving it to the welder to TIG up. Apparently the apprentice doesn't like the explosion when it goes up.

I'm waiting on approval but the specialist reporting on the damage from the lack of filling and subsequent failure of one way clutch will read "economically viable to replace with imported unit".

Thanks for the input :) So you had yours mucked up by installer so you going to replace with an Ashcroft, Like the plan! :D What is the customs on it I wonder? Its given me some idea any way as what to do now.
Cheers Scott

Quote:

---

Originally Posted by schuy1

There is a fault code showing up now regarding a read timeout in the auto faults so I assume it is going down hill!

---

Scott, what is the code you are getting?

Quote:

---

Originally Posted by OffTrack

Scott, what is the code you are getting?

---

Yes I havent looked it up yet, I am assuming it is something to do with the time the box is taking to engage once I select "D" or any other position. The code is P1843 read timeout

Chers Scott

Just to add I have only seen it the once and it has not reappeared since I cleared it 600kms ago.
And I just looked it up and its a limp home mode fault,How ever I did not notice any Limping at any time :o Apart from the takeoffs and the odd hard kick down it seems to work ok.

Quote:

---

Originally Posted by schuy1

Yes I havent looked it up yet, I am assuming it is something to do with the time the box is taking to engage once I select "D" or any other position. The code is P1843 read timeout

Chers Scott

---

It's related to loss of canbus communication between the EAT ECU and the Td5 ECU, rather than any internal issue with the Auto, and should trigger M&S.

http://www.aulro.com/afvb/attachment...1&d=1374374577

cheers
Paul

This page, When buying over the internet , should help with calculating costs at customs level.

Thanks Paul. Interesting because I have not seen M&S lights . and they both do work when I select the appropriate modes . Looks like it could possibly have been a bad connection in the auto harness which I have recently disconnected and cleaned the plugs. Looks like it is not related to the auto problems.If so I'm sure it would have reappeared.


Clubagreenie, you sure know how to supply some heavy reading! :D Gonna take a little wading through maybe, Funny Last night I googled customs and their site did not appear on my search page!?

Cheers Scott

Quote:

---

Originally Posted by schuy1

Thanks Paul. Interesting because I have not seen M&S lights . and they both do work when I select the appropriate modes . Looks like it could possibly have been a bad connection in the auto harness which I have recently disconnected and cleaned the plugs. Looks like it is not related to the auto problems.If so I'm sure it would have reappeared.

Cheers Scott

---

Scott,

The canbus timeout has a couple of common causes - remapping the ECU logs this fault code. What happens the EAT ECU is powered on and can't establish a connection to the engine ECU so logs a timeout fault. The other cause is the battery voltage dropping below something like 11.2V (can't find the post but an AULROian did some testing and posted up the exact voltage).

If the Nanocom was able to report the "ambient conditions" which the EAT ECU stores you would have been able see whether this was the case or not...

Otherwise it is a connectivity issue between the EAT ECU and the engine ECU. There are connections at the EAT ECU, behind the window switch panel and at the ECU.

One thing I'd note is that the fault condition has to exist for 1 second before a fault code is logged. It may be possible that a marginal connection could cause interruptions to communications of less than one second but still not log a fault. Seems reasonably unlikely but not impossible.

Anyway the fault isn't directly related to the Auto itself, but can impact performance.

cheers
Paul

Just to confirm, Canbus timeout errors can be just plain voltage related,like Paul says. I have had them appear sometimes after ignition on and testing other things etc etc, they start flashing, then I run the engine for 5 or 10 minutes, then switch off, and on, and they are gone. Fault code logged.

JC

Thanks for that Paul , I now have a much clearer idea of how that occurs. I think I may have been the fella who did the battery level test as to when the M&S lights start flashing :) and yes it was dead on 11.2 volts . At the time I did not have the Nanacom, so it is possible the code was stored then? Although I am sure I have looked in the faults since I had the Nanacom.

Cheers Scott