Check pins 4 & 5 against ground.
Let know if you need the appropriate electrical diagram. There's only (5) conductors total.
I have now tried three different OBDII devices without any success linking to the ECU. They scan for protocols but never find anything.
I am thinking it is the connector on the Defender and have checked that the correct wires are on the correct pins of the OBDII socket. I have not traced them back to the ECU at this stage but am wondering if anyone has had a similar problem?
By the way there is power on pin 16 so that is not the problem.
Thanks, Howard
Check pins 4 & 5 against ground.
Let know if you need the appropriate electrical diagram. There's only (5) conductors total.
What devices have you tried? The generic code readers wont work on a td5
That was what I understood but another post in this forum stated that the user had success reading the ODBII with an ELM327 Bluetooth device. On checking the RAVE documentation re the Diagnostic Socket it states:
"The socket is constructed to ISO standard and allows attachment of TestBook or any other ISO standard scantool."
I tried an ELM327 with USB interface, ELM327 with Bluetooth interface and Maxiscan MS509. None of these could find the protocol and the Maxiscan certainly has many in its firmware.
Given the RAVE document and the comments by a user having success I have concluded that there must be an error in the circuit on my Defender. I will check the earth (as per another post's suggestion) - I had assumed that was OK as the ELM327 powers up but of course it could be that the signal earth is faulty...
Otherwise I am at a loss.
Regards, Howard
As far as I know, but I am happy to be proven wrong, none of those readers will read the td5 ecu.
The wording could well be ambiguos. It may allow the connection of an iso standard scan tool, it doesnt say they will read.
good luck!
Pin 4 is 0 ohms to chassis but pin 5 is about 1K ohms to chassis. My reading of the circuit diagram tells me that pin 5 is the signal ground and should be connected to the header earth. In that case it should be 0 ohms to chassis.
Would you agree? If that is the case earthing pin 5 to chassis might bring the OBDII to lilfe...
Howard
I'm no help to your problem, but I also have no success with an ELM327 Bluetooth adapter reading the ECU on an '02 Defender 110. No problems connecting on the Bluetooth side, just unable to get anything from the ECU.
I might try the ELM327 on a different vehicle this afternoon, to try and eliminate it as faulty.
I would love to hear from anybody who has successfully had one working.
The elm scan tools should connect to the EMS. I've used a Kiwi Wifi which is elm based on a TD5 D2 and as able to connect, and scan/clear engine codes. You can't do very much else apart from read rpm, water temp and a couple of other useless bits of information.
LUCAS TD5 DIAGNOSTIC (LAND ROVER) (SM010)
Although the ECU is OBD compliant, It's compliant diagnostic capabilities represent only a small fraction of its total.
It is not your connector.
I am yet to hear a genuine report of diagniostic/ communication capability with any of the claimed OBD universal interface devices with a TD5 ECU.
These devices will plug in and many will connect to the SLABS and BCU, but will not communicate with a TD5 ECU.
The Td5 runs unique protocols/code/programming and will only interface with devices capable of such. OBD compliant is irrelevent in most cases.
I wouldnt be chasing any of the outputs until you know the device you have will actually interface with the TD5.
i.e if it worked before, go ahead and check the wiring. If it never worked before dont waste your time and send it back for a refund and get a device that is known to work with a TD5
cheers
| Search AULRO.com ONLY! |
Search All the Web! |
|---|
|
|
|
Bookmarks