Thread: Anyone tried this OBD Scanner?

Craig

I have one similar, works fine on my V8 - but I couldnt get it to work on several defenders

Me. It will only work from 2003 for diesels and I think it was 2000 for petrol.
OBD2 was phased in from 1996 but LR didn't comply till the 11th hour.

My son bought me one but it wouldn't work on my MY2002 Td5 Defender but would on his WRX Subaru.
I think it also worked on his '96 Rangie but I wouldn't swear to that.
Alan.

Had this last week Craig.
Sketcy but I said from memory dont work on D2s,but ok on Defender.
Now Ladas says it works on his V8 D2 I recall that it only workd on the D1/D2 V8 management.
No good for D2/Defender TD5 motor or D2 SLABS/Body ECUs.
Andrew

Originally Posted by LandyAndy

Had this last week Craig.
Sketcy but I said from memory dont work on D2s,but ok on Defender.
Now Ladas says it works on his V8 D2 I recall that it only workd on the D1/D2 V8 management.
No good for D2/Defender TD5 motor or D2 SLABS/Body ECUs.
Andrew

LandyAndy if it works on OBD1 Disco 1's if only just V8 engine management that is a pretty rare and good find at thay money is it not???

At that price they are great.
They suit LOTs of vehicles,just not the stuff we have trouble with on the D2s that stealers charge $100 or more to reset!!!
Andrew

I bought an OBD-II to RS232 interface from Check Engine Light OBD2 OBDII scan tool OBD just before Xmas after Ron referred to it in a post, and, full of anticipation, I got it working with my USB to RS-232 adaptor with my (company-supplied) Toshiba Tecra notebook.

Unfortunately, when I plugged it in to the (looks like) OBD-II connector on my 1996 V8 Series I Disco, I couldn't get it to establish communications with the engine ECU. As far as I can make out, the 96 Disco has a connector which is normally used for OBD-II but it actually uses a LandRover bastardised form of OBD-I protocol (presumably to make it unreadable with anything but LR Testbook) and I don't believe I'm ever going to talk to the Disco at this point although I'd love for someone to tell me it is possible and offer a solution (oh - I don't think I can justify the expense of Rovacom Lite though).

The interface is a neat little unit and it only cost $155 so I'm not going to slash my wrists over it, and I'm sure I'll own a car in the future which I'll be able to talk to (although interestingly it won't talk to my wife's 2003 Corolla either) so I'll just put it away in the box of bits to play with later.

It was a good find, Ron, just a shame it won't work with my car. And there's heaps of freebie software out there to display the sensor readings and codes too. It uses the ELM327 OBD-II interpreter which supports multiple versions of the OBD-II protocol including CAN (ISO 15765-4), SAE J1850 PWM, SAE J1850 VPW, ISO 9141-2, ISO 14230-4, and J1939 CAN.

If anyone here in Adelaide would like to try it on their car, let me know and we can set up a trial sometime.

GrahamH you say "...on my 1996 V8 Series I Disco, I couldn't get it to establish communications with the engine ECU"

If that the case this reader is probably a dud for D1's or LR's pre 1996 version of OBD-1 protocol and not surprising.

As you say using some freeware (and a RS-232 or USB connector between PC and ECU) is all you need to access ECU/engine data. In LR's it is only with testbook and rovacom you will ever get to next step of accessing fault codes and non engine/ECU data (as opposed to just ECU data).

That closed source/electronic access exclusivity was a stupid "protect the stealer at any lengths strategy" by LR starting some 20 years ago that did nothing to enhance their reputation when things went wrong and or people wanted flexibility about non stealers servicing their rig.