Karrier-Bag said:

I don't have much dosh and need to get an obd reader for my disco auto, the three amegos have sprung up just before replacing front disks and pads, I hoped it was the thin disks that had caused them to come on, I tried a 30 quid reader and also one a local motor factor had but neither showed any fault codes, I tried removing battery to see if that would work but now off to pay 35 quid to have them cleared and to find out what is wrong, maybe a sensor or bearing....... any ideas what's cheapest and best?

Click to expand...

Karrier-Bag said:

Ive just had it put on a snap on gadget and it shows a 117 front right abs sensor problem, but it is a new hub and sensor so that is a bit weird

Click to expand...

Karrier-Bag said:

Have cleared the lights, there was one other code which is135 amd said speed input sensor or something, i wonder if that is the problem i sometimes have, as i pull away it is like in limp mode for 10 seconds then kicks in properly, only a problem when 8n heavy traffic and needing to pull out fast

Click to expand...

brian47 said:

Where did you purchase the new hub from and what quality was it?

There have been reports of faults in the past when new hubs have been fitted. There is a risk that some of the cheaper replacement hubs can give problems, sometimes due to the reluctor ring which is sensed by the speed sensor having the wrong number of segments and therefore sending a different speed signal when compared with the other wheels.
Other times it could just be something as simple as the speed sensor not being seated correctly.
@sierrafery is the top man on the ABS/speed sensing system.

Regarding a fault code reader for the diesel Disco 2, many will claim to work on the Disco 2, without specifying which type, petrol or diesel. The diesel Disco only became compatible with the release of the Disco 3 in mid-2004. Proir to that the diesel D2 was not compatible. The only code readers known to work on the D2 are Nanocom, Hawkeye and Lynx. Testbook T4 is the professional kit used by the main dealer.

Click to expand...

ozzyboydeano said:

I always thought the discoverys use the obd2
I have the 2002 d2 and I have 3 obd2 scan tools from other previous cars I have owned ..all I can do is read codes with them and some slight live data like engine load throttle position rpm and road speed on my disco
these are only for engine ecu only

I also have the rsw http://www.rswsolutions.com/index.php/discovery-ii/abs-amigo-v1-usb back when I got mine it was allot cheaper
this is the version 1 but tells you to plug into the obd2 port ?

Click to expand...

brian47 said:

The development of diagnostics compatible with OBDII protocols moved at different urgencies at Land Rover. The petrol Discoverys were compatible by the mid to late 1990's, probably to meet some obscure EU ruling. The diesel Discoverys, including all diesel Discovery 2 models were equipped with on board diagnostics which were peculiar to the Disco. Some of the interchange of data between control unit and diagnostics; the protocol, was for no other reason than convenience or "no other way to do it", compatible with OBDII, but most of it was not. The hardware, including the connection socket was the easy bit but the software, the language was the sticking point.

Land Rover probably decided to no longer pursue diagnostics compatibility on the diesel Disco 2 because of the impending release of the Discovery 3 in mid-2004 which was fully compatible with OBDII. Consequently petrol Dicsoverys are compatible with OBDII but diesel Discoverys are not. This is the condition that creates the confusion in the adverts for code readers. Those adverts almost never differentiate between petrol and diesel models, just listing "Discovery 2".

Having said that, even even with the Disco 3, some code readers are of more use to the owner than others. Many owners will recommend the IID scanner, but the Nanocom for instance, can also be unlocked for the later Discos as well.

Click to expand...