Nanocom or ECU????

[Basil135]

Ok, so like 20 others, I have a new Nano Evo to play with.

I have gone thru, and cleared a stack of weird faults, only to have them re-appear virtually straight away. I saved them to a text file, and they are below:

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


The above was recorded after this mornings drive into work. I cleared all the faults before leaving home, and 20 mins and a fairly good run in, they had come back.

Now, the car is running like it always has. So, I am down to 2 options.

1) The ECU is sending out some very strange signals.
2) The Nano is reading some weird stuff, and making it up as it goes along.

Just for interests sake, the ac faults are really weird, as I didnt have it on at all this morning. And if the fuel pump was open load, then I doubt if it would be running.

I guess there is always a third option, and that is I am driving a ticking time-bomb around, but I am not too worried about that - so long as it is quick...:eek:


So, thoughts, ideas, opinions????

[Basil135]

So, no-one has ANY idea??? :o

Do you mean to tell me that I might have found the ONE Land Rover problem that hasn't been brought up before? :angel:

[crossy999]

Oil in the wiring harness ? (check the red plug on the ecu for contamination) - this can cause some whacky problems.

crossy

[brookvale]

As they say - "you are not alone"...
I have similar faults logged on my 04 90 and three diagnostic boxes cannot clear them; my new nano evo (repaired by BBS within 1 week and back in full working order!), an Autoblogic box and a Faultmate.
Mine are similar in that they are Air con stuff (haven't got the complete list at the mo - sorry).

The boxes all say "faults cleared" then, without engine running and going back to read faults, they show again.

I've had the oily loom issue (No.4 injector fault) and have just had the rocker harness replaced. Injector fault and rough running gone but air con faults still show.

The seller did not advertise my vehicle as re-mapped but it has been - enough people have driven it to say it goes way better than standard.
Can't imagine a remap would somehow alter the way faults are monitored.

BTW: I have other errors showing: (am I the only one? :) )
Brake pedal down, Evo reports "brake switch off" and vice versa
Gearbox in high range, Evo reports "Low".

Another thread starter maybe - the Nano documentation shows:
• Fuel used: The TD5 ECU has been designed to work with a wide range of possible fitments and options. Many of the input sensors and output controls can be omitted giving many vehicle option, model or market variants. This value indicates if this TD5 ECU has its fuel used output for trip computers and econometers enabled or not.

Anyone set this to ON and hooked up a trip computer?

Neil

[brookvale]

just checked my Evo;
Same list of faults as Basil's...
Feeling spooked now :)

[LOVEMYRANGIE]

How many of you have chipped or flashed ECU's??
There has been odd errors popping up after chips have been done and not being able to be cleared.
Tombie is a bit more in the know on this and has dealt with issues relating to errors after a remap.

Andrew


I am not a moderator, I am a human being!!!

[Redback]

Basil, do you have a power upgrade on your ECU, or is yours standard??

OK, just noticed you do, if you still have the standard file and the upgrade file available.

Replace the power upgraded file with the standard file and see if the fault still appear, if they don't then it's something with the upgrade file, now replace the standard file with the upgraded file and see what happens, if they reappear then this will confirm the upgrade file is corrupt and you may need a new file from Tombie.

Baz.

[Tombie]

Upgrade file won't be corrupt.
Just a different revision number ECU causing a few 'ghost' errors.

Nothing to worry about....

[brookvale]

There's no extra chippery/wires, externally on/near my ECU box.
Should we be differentiating between "chipped" (bolt-on goodie) as opposed to "re-mapped"?
How would we tell?
Am guessing that Basil's system has been re-mapped in a way that's similar to mine, given that we are getting similar fault codes.

[Redback]

Upgrade file won't be corrupt.
Just a different revision number ECU causing a few 'ghost' errors.

Nothing to worry about....

The issue I see Mike with these ghost faults is how do you determin the ghost faults from the actual faults the car may have.

Baz.

[brookvale]

'Ghost' errors - possibly the same as those 'features' which enhance the Microsloft and Apple experiences we have...

All the same not very useful to have an aircon problem and tell the mechanic "that fault code showing now? - yes it's there all the time".

[Basil135]

Mike did my upgrade, so I am fairly confident in what he says.

There are no issues with the car that I can tell, and the only thing that has changed is that i now have the ability to read some of the info.

What is also interesting, is that if I look at the recorded maximums during a trip, I have set a top speed of over 200 km/h, and the temp hit a high of over 170 degrees. Not bad considering the trip was during peak hour, and thru the suburbs...

I recorded the trip home last night, and in over 1700 lines of data, there were two peaks of 136 km/h & 162 km/h. They only lasted for 1 line and are obviously these magical ghost errors. Its more intriguing than annoying - for the moment anyway

[Tombie]

The issue I see Mike with these ghost faults is how do you determin the ghost faults from the actual faults the car may have.

Baz.

In the coming financial year I am looking to put in place new mapping based on a database of all previous clients vehicles...

Those who need new mapping to clear these ghost faults will get an upgrade done gratis.

I have some issues to work through at my end financially at the moment before I can move forward with my business ventures. Will then be working harder on the tuning side.

[Tombie]

Whats even funnier is an un-modified Defender TD5 will show "Can Bus Errors - Automatic transmission"


Driver demand errors are common on all TD5s mapped or stock...
A/C errors and EGR also common...
Injector faults are common...

To log a fault only requires a "blip" in the data, not long and often not noticed either.

[Michael2]

Why not find someone with a Hawkeye, and plug that in for a 2nd opinion?

If the faults are Nanocom specific, then you could disregard them with a higher degree of confidence.