PDA

View Full Version : TD5 ECU Fuel Used Function



djam1
13th September 2012, 05:40 PM
Has anyone ever successfully used the Fuel Used function in the TD5 ECU?
Nanocom documentation says

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.

Not sure where it feeds off of the ECU or what is compatible with the output?

jakeslouw
13th September 2012, 08:38 PM
Logic indicates that it needs the following:

- an accurate fuel level measurement input
- an accurate odo signal input
- accurate fuel flow input

JayBoRover
13th September 2012, 08:41 PM
Logic indicates that it needs the following:

- an accurate fuel level measurement input
- an accurate odo signal input
- accurate fuel flow input
It's a Land Rover ... what the 'eck does logic have to do with it?:wasntme: (Sorry - I couldn't resist:D)

jakeslouw
13th September 2012, 08:43 PM
It's a Land Rover ... what the 'eck does logic have to do with it?:wasntme: (Sorry - I couldn't resist:D)
Yes, true, was just mentioning what REAL vehicle manufacturers use! :o

djam1
13th September 2012, 09:16 PM
Logic indicates that it needs the following:

- an accurate fuel level measurement input
- an accurate odo signal input
- accurate fuel flow input

MMM not sure you got the question

"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."

As indicated in the description the output from the ECU can be interpreted by some device that can make sense of the output data.

The question was has anyone ever used this and if so how I am assuming that one of the unused pins can be tapped and the output interpreted into useful information.
I thought that it was quite logical

jakeslouw
13th September 2012, 09:58 PM
I reckon that the output from the ECU would have gone to a BCM (body control module) of some type and then onto an LCD display.

Was a BCM ever used on the Disco 2, because that would be the place to start.

petmic
26th January 2013, 05:28 AM
My theory is that enabling Fuel used output in Td5 ECU will enable some PWM signal on one of the not used pins on the ECU connector block. Since this signal was never connected anywhere in Disco and Defender the wiring diagram shows some pins as Not connected. It shouldn't be that hard to find out which pin it is (about 5 pins are not used). My guess is that the signal will have 12V logic levels, it will be PWM, giving ms/l of fuel.

Slunnie
26th January 2013, 10:03 AM
The Scangauge will show the instant and average consumption for the OBD2 compatible TD5's.

djam1
26th January 2013, 11:00 AM
The Scangauge will show the instant and average consumption for the OBD2 compatible TD5's.

Simon Thanks that is interesting I didn't think the Scangauge worked on TD5 s because of a non true OBD2 compatibility?

Slunnie
26th January 2013, 11:50 AM
Simon Thanks that is interesting I didn't think the Scangauge worked on TD5 s because of a non true OBD2 compatibility?
I'm not definate, but I think the early ones were not OBD2 and the later ones are. I would definately check its compatibility before buying though, because I think you may be right too.

OffTrack
30th January 2013, 03:21 PM
I'm not definate, but I think the early ones were not OBD2 and the later ones are. I would definately check its compatibility before buying though, because I think you may be right too.

None of them were fully OBDII compatible. Requirement for OBDII on diesel passenger vehicles didn't come into effect until 2005.

All the Td5 Disco 2's have a small number of PID's available via OBD-II, with no appreciable difference between 1999 and 2004:

Mode 1
- Trouble codes and on board test information
- Calculated Load Value
- Engine RPM
- Vehicle Speed
- Absolute Throttle Sensor position

Mode 2
- Freeze frame trouble code

That's it.

Based on posts on OBDII tools in the Diagnostic forum, Defender Td5 owners have little success with accessing fault codes using OBD-II tools, so it's unlikely you'll get any PID's either.

cheers
Paul

technophile
2nd February 2013, 01:21 AM
None of them were fully OBDII compatible. Requirement for OBDII on diesel passenger vehicles didn't come into effect until 2005.




So defenders up to 2005 were not OBD II compliant? Does this mean that my 2006 td5 will be, and that I will be able to get various other readings?


Thanks