'03 D2 Td5 ECU faults cannot be cleared

[catch-22]

Have tried with 2 nanocoms and an autologic. ECU has a power upgrade. Here are the codes -

The TD5 ecu contain the following faults:

FAULT 08-01 air conditioning fan drive over temperature (CURRENT)
FAULT 08-02 fuel pump drive over temperature (CURRENT)
FAULT 08-03 tacho drive over temperature (CURRENT)
FAULT 08-04 gearbox/abs drive overtemperature (CURRENT)
FAULT 08-05 air conditioning clutch over temperature (CURRENT)
FAULT 08-06 mil lamp drive over temperature (CURRENT)
FAULT 08-07 glowplug relay drive overtemperature (CURRENT)
FAULT 10-01 air conditioning fan drive open load (CURRENT)
FAULT 10-02 fuel pump drive open load (CURRENT)
FAULT 10-03 tachometer open load (CURRENT)
FAULT 10-04 gearbox/abs drive open load (CURRENT)
FAULT 10-05 air conditioning clutch open load (CURRENT)
FAULT 10-06 mil lamp drive open load (CURRENT)
FAULT 10-07 glowplug lamp drive open load (CURRENT)
FAULT 10-08 glowplug relay drive open load (CURRENT)
FAULT 12-01 air conditioning fan drive open load (INTERMIT.)
FAULT 12-02 fuel pump drive open load (INTERMIT.)
FAULT 12-03 tachometer open load (INTERMIT.)
FAULT 12-04 gearbox/abs drive open load (INTERMIT.)
FAULT 12-05 air conditioning clutch open load (INTERMIT.)
FAULT 12-06 mil lamp drive open load (INTERMIT.)
FAULT 12-07 glowplug lamp drive open load (INTERMIT.)
FAULT 14-01 air conditioning fan drive open load (INTERMIT.)
FAULT 14-02 fuel pump drive open load (INTERMIT.)
FAULT 14-03 tachometer open load (INTERMIT.)
FAULT 14-04 gearbox/abs drive open load (INTERMIT.)
FAULT 14-05 air conditioning clutch open load (INTERMIT.)
FAULT 14-06 mil lamp drive open load (INTERMIT.)
FAULT 14-07 glowplug lamp drive open load (INTERMIT.)


The SLABS ecu contain the following faults:

FAULT 29-05 engine speed input signal intermittent or missing (LOGGED) 254 times



The Disco seems fine. Average fuel consumption is 12.1. Have removed the ECU and left it out for a while in an attempt to flush to no avail. I am going to reseat all fuses and check all earths this weekend. Have recently replaced MAF and CAS with OEM (the issue existed prior to this).

I have considered putting on a standard map and trying to clear them again but figured the logging component has nothing to do with the fuel map....would this be correct?

But whatelse could it be?

[Tombie]

On your ECU can you check the part number and if anything the version..

NNNxxxxx <- The one on the end
NNWxxxxx <- this ones on top of the ECU usually

I'll investigate if the mapping is wrong for the unit and causing the errors, but we'll solve it...

[Redback]

Hi Kelvin, Phil told me of your drama.

We had a similar problem, what we did was reload a standard file over the one with the faults, clear the faults on that file go for a drive to make sure it drove OK, CHECK FOR FAULTS, all OK, then reload the upgrade over the standard file, seems to have worked so far, maybe try a different file, Phil has a couple I think.

edit, disregard my ramblings, Phil said he tried all that:rolleyes:

Baz.

[catch-22]

Thanks Baz. I don't think we loaded a standard map file....just loaded another that he had. The map that was on there had a weird name for the fuel map (from memory) and Phil recons it may have been corrupt.

Cheers
Caine :)

[Redback]

Thanks Baz. I don't think we loaded a standard map file....just loaded another that he had. The map that was on there had a weird name for the fuel map (from memory) and Phil recons it may have been corrupt.

Cheers
Caine :)

Sorry Caine, no idea where I got Kelvin from:eek:

I can't help with my standard file as my D2 is manual.

Baz.

[catch-22]

Hi Kelvin, Phil told me of your drama.

We had a similar problem, what we did was reload a standard file over the one with the faults, clear the faults on that file go for a drive to make sure it drove OK, CHECK FOR FAULTS, all OK, then reload the upgrade over the standard file, seems to have worked so far, maybe try a different file, Phil has a couple I think.

edit, disregard my ramblings, Phil said he tried all that:rolleyes:

Baz.

Hi Baz,

I was just checking if this thread had any updates and re-read. Are you saying above that the faults are associated with the file?

[Blknight.aus]

seen this on the busmasters....

if you have a fault in active memory when you write in the new map you may not be able to remove the fault codes. Reinstall the original map, clear the faults and then re-install the new map.

Dont know why, the techs cant explain why, it shouldnt do it but it does and just to make matters extra funky some readers will pick up the errors and some wont..

[LOVEMYRANGIE]

IIRC, the faults are registered into the memory and align themselves with the map. If the map is changed, the association with that map also changes and is not recognized by the new map either.
The new map won't overwrite this internal register as they aren't associated with the new map and as the faults are logged in order, it will only see the first visible faults from the old map first.

It may be worthwhile trying to get a fault to occur with the new map and see if it registers differently or actually logs the fault as the reader may only be programmed to look for one particular register set and not a secondary set from the new map. Kind of like a PC when it files things under say ***.reg and a previous as ***.old, but it only sees the .old file.

If not, reload the original, reset and reflash as per other posts.

Cheers

Andrew

[LandyAndy]

All of those faults normally indicate "oil in the harness"
You stated that you removed the ECU to flush it.
If you have oil at the red plug on the ECU you need to fit a new injector harness to start with,then look at flushing the oil from the main harness(metho spirits is good).EASY DIY JOB!!!!
The faults will go away as the oil goes.
GOODLUCK
Andrew

[harlie]

I remember something very similar to this... I'm going to agree with Tombie, if you reload the standard file and all is good, it can be a case of the ECU not liking an upgrade. The faults are cleared but instantly logged again with the ignition on.

[catch-22]

On your ECU can you check the part number and if anything the version..

NNNxxxxx <- The one on the end
NNWxxxxx <- this ones on top of the ECU usually

I'll investigate if the mapping is wrong for the unit and causing the errors, but we'll solve it...

So is the mapping wrong for the unit? Rem this is the second map we have tried

[disco_thrasher]

Sorry Caine, no idea where I got Kelvin from:eek:

I can't help with my standard file as my D2 is manual.

Baz.

i was thinking there where far too many Kelvins going around here LOL
Cheers Kelvin

[catch-22]

On your ECU can you check the part number and if anything the version..

NNNxxxxx <- The one on the end
NNWxxxxx <- this ones on top of the ECU usually

I'll investigate if the mapping is wrong for the unit and causing the errors, but we'll solve it...

Mike, can you please let me know if you have given me the correct map. The one you initially put on has been replaced with the one Phil put on.

It has been near two months and I would appreciate a response. I have pm'd and sent multiple emails providing the information you require and I have not had a single response.

[catch-22]

Well, standard map was loaded the codes did not clear.