Thread: 99MY TD5 Defender Diagnostic Socket Problem

Originally Posted by OffTrack

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)

So you have used a Kiwi ODB2 connector to get error codes? To be honest, getting and clearing the engine codes would probably be the primary use I would put it to anyway.

I tried my cheap bluetooth connector on a 2001 Suzuki Grand Vitara yesterday, with exactly the same result, so I'm suspecting it's dodgy.

Yes. The kiwi worked fine with several iPhone apps I tried. I was also able to access the ELM command line interface via wifi. At the time I was trying to find out if the iPhone software was ignoring PID's but it became apparent they simply werent accessible via the standard ODBII protocol.

I'm surprised an elm interface won't work. If you want to really investigate have a look at the elm documentation PDFs. The is enough detail to let you connect with a terminal app and issue commands directly to the elm chip. They are very similar to the old AT modem commands and not difficult to use. It could be a good way to narrow down the issue.

Good night.
You could solve your problem? I'm going through the same situation. I appreciate if you help me.

Originally Posted by HowardSmall

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

Originally Posted by sidarta

Good night.
You could solve your problem? I'm going through the same situation. I appreciate if you help me.

No, never got it to work so gave up in the end.
Howard

I can't get mine to work either (just bought it ) , I found the following on the net, does anyone know how to connect to the defender another way?

-----------------------------------------------------

Iain W:
I'm having problems connecting my ELMscan5 interface to a 2005 Land Rover Defender Td5. I'm confident the ELMscan5 is functional as I've been able to connect to other cars, however this is the first I've tried with ISO9141. I've followed the troubleshooting flow chart elsewhere on this website, and still get the error message about initialising the bus.

Has anyone else successfully connected to a Td5 engined vehicle?

Iain


Hi, I just purchased an Elmscan 5 for my 2003 TD5 Defender, it did not work,
after searching the net I found the following, does anyone know if the reader reads the protocol properly and if new software would work or is the reader not capable of reading the TD5 protocol?

---------------------------------------

CanDoo:
Try forcing the ISO protocol manually with the command ( using the hyperterminal ) at sp 3 . If the vehicle is CAN equipped then you will need to try sp 4 to 9, trying each number in turn until the unit responds.

Iain W:
I've just been talking to the technical people at Land Rover. They've confirmed that the interface to the Td5 ECU is via ISO9141, however the Defender is not classed as a car, and so does not need to be OBD2/EOBD compliant. Which explains why the ELMscan5 is unable to establish a connection to the ECU. Apparantly Defenders will be OBD2/EOBD compliant from 2007.

Iain