sierrafery
Well-Known Member
MJI
Well-Known Member
MJI
Well-Known Member
Elm327 scanners work OK with the D2 port, gives you real-time monitoring of the engine and some codes.
ELM327 - Wikipedia, the free encyclopedia
On ebay by the hundred, software is a rip-off of another company in most cases, but for the basics they are fine.
MaxiScan MS509 OBDII reader is 2001-onwards for petrol ans 2004-onwards for diesel according to this spec:
http://www.amazon.co.uk/BW-MS509-Autel-Maxiscan/dp/B001LHXTO0
Peter
ELM327 - Wikipedia, the free encyclopedia
On ebay by the hundred, software is a rip-off of another company in most cases, but for the basics they are fine.
MaxiScan MS509 OBDII reader is 2001-onwards for petrol ans 2004-onwards for diesel according to this spec:
http://www.amazon.co.uk/BW-MS509-Autel-Maxiscan/dp/B001LHXTO0
Peter
Last edited:
sierrafery
Well-Known Member
the Td5 is not OBDII compliant, only the V8 engine management...if in the unlikely case that an OBDII reader will comunicate with the Td5 engine ECU is completely unreliable anyway as it picks up some signals from a diesel ECU(IF it does) and corroborates it with petrol/OBDII protocol... OBDII protocols were built in the disesel ECUs only from 2006 on....there are cheaper multivehicle scanners(not generic OBDII) like e.g. the Autocom CDP or VDM Ucandas where you can select the vehicle type and these have limited coverage for land rover various ECUs but not with programming capabilities...an example attached
Attachments
Last edited:
sierrafery
Well-Known Member
no, it's not
I've got a cheap (under £10) device off eBay...VgateScan OBD Scan ..interfaces via Bluetooth to a free app on my Android phone. I'm pretty sure that it works with my Disco 2. I'll check later on.
EDIT: Well, it says it is connected to the ECU and that there are no faults,. However, looking at the reading such as rpm seems to bear no relationship to actual revs and so maybe when it says 'connected to ECU' it is only at some very primitive handshaking level. Mine is a Td5, btw.
Worked fine on the Mazda RX-8 as I was able to reset an anomalous Check Engine warning light ( and get SWMBO off my case!)
EDIT: Well, it says it is connected to the ECU and that there are no faults,. However, looking at the reading such as rpm seems to bear no relationship to actual revs and so maybe when it says 'connected to ECU' it is only at some very primitive handshaking level. Mine is a Td5, btw.
Worked fine on the Mazda RX-8 as I was able to reset an anomalous Check Engine warning light ( and get SWMBO off my case!)
Last edited:
sierrafery
Well-Known Member
maybe you missed that post of mine^^^... i say again, for everybody... An OBDII reader even if it connects and pics up signals from the Td5 ECU it will interpret the signals according to the OBDII protocol and gives various and unrelated readings cos the Td5 is not OBDII compliant so the outputs for diagnostics are different than the OBDII is conceived to read and ''translate"
Just echoing what sierrafery has said, you need a Hawkeye or Nanocom if you want to get inside the D2 systems, the basic readers are fine but very limited.
Peter
Peter
sierrafery
Well-Known Member
there is not such thing as exclusively OBDII port, it's a ISO - J1962 16 pin DLC(diagnostic link connector)...and the OBD II protocol was compulsory for diesel cars only for MY 2004 onwards in Europe
I'm confused now ! Do you mean May = MY ? If so does that mean that if my Disco 2 was made (or registered?) in June 2004 that it should have ODB?
sierrafery
Well-Known Member
MY = make year, and as it was a tranzition year the last D2's were allowed with the original protocol ... don;t be confused just take it as it is: D2 Td5 is not OBDII compliant ... period, so who can't accept that and has a 2004 Td5 bring LR to trial for that...anyway even if it was OBDII would not be perfect as OBDII must cover only the engine management/emission controll, not all the systems
