I believe it will work for most codes. I don't think it will work though for the land rover specific stuff like the drive train stuff, wheel speed sensors etc. I will verify in about 2 weeks and let you know when my new bluetooth adapter gets here.

Chris

Only a few functions work on my 97 Land Rover Range Rover. The one i really wanted to work, the L/100km does not. Anyone got any ideas? I have entered the engine size etc..

Works reasonably with a Discovery 3, though not getting quite a few PIDs to display any data. This could be either because of the adapter (I have a cheapo one at the moment), the software (doubt it), or, more likely, the fact that the D3 has (I think) around 6 ECUs and Torque interfaces only with the engine one?

Ian, any thoughts on this?

My Australian V8 Rangovery (Discovery/Range Rover hybrid but has the mechanicals/electronics of a 06/2000 Discovery II) works just great for all the engine stuff with a chinese bluetooth adapter and HTC Desire.

Torque reports that there are issues with the BT adapter but it seems to work OK.

However it can't access any of the Land Rover specific stuff (ABS, HDC, TCL, ACE, SRS etc)

It's down to the adapter (if the app has said it's faulty, you really ought to get the seller to replace it!) and the ECU

All ECU's are not equal - each one will allow slightly different sensors to be read (for example, diesels have fuel rail pressure, petrol engines usually don't), and also what the manufacturer has decided to allow to be read. - another example would be that you might have a mass airflow sensor and no manifold pressure sensor (quite a few engines usually have one *or* the other, apart from some german built engines which have both)

Also, some really early implementations of OBD only allowed a couple of sensors to be read, but as the standard has matured, more manufacturers are allowing access to more sensors.

It's highly unlikely you will ever get all the sensors being accessible in the standard OBD2 block as they simply are not all implemented depending on the engine type, haven't been required by the legislation of the country the vehicle is sold in, or some other reason best known to the manufactuer why the sensor wasn't included as being readable as part of the OBD2 standard 'list'. Torque knows which ones that the ECU does allow to be read, so when adding a display, they will show up in green.

There is a facility in the app that allows you to add your own sensors to poll, so if for example you had something like the service manuals for your vehicle which had the PIDs listed in them (commonly known as Extended or Mode 21 / 22 PIDs) then you can add these yourself and get extra information from (any) vehicle ECU - the app allows you to address whatever ECU you need to talk to using the custom PID entry(accessible via the main settings)

Hi, great app!

I've tested it with an EML 237 with a Ford Mondeo, a Citroen Picasso, a Renault Clio and a Renault Laguna. Works great!

Unfortunately, it doesn't work with my 2004 Land Rover Discovery II TD5.

Any help, please?
Thanks

Hi!

You'll need to find out if your disco is OBD2 compliant - (it's 2004 so I would expect it to be, so it could be an adapter issue on the protocol it uses). Unfortunately I don't have a definitive list for landrover so you may be better off asking if it's OBD2 compliant on a dedicated landrover/discovery forum. This can also be country-specific if you are outside the EU/US

If it's OBD2 compliant, then Torque will work with it.

Thanks, I'll try to find out!

I have the fantastic Torque app running on my Skoda Tdi and have used it on many other vehicles. I bought a slightly more expensive bluetooth device as the first was a bit "flakey". The current device and phone combo run the app in a really reliable/robust way on the above vehicle, however I can't get it to read my 2003 Landrover Defender Td5 ECU? Having read the above thread I've looked into it and I think from Landrover Forums it is OBDII and runs the protocol ISO9141-2. I have tried letting it search in the Thorough Auto mode and also tried selecting ISO9141-2 manually and tried combinations of the faster comms and disable ELM327 auto timing options and basically I'm stumped. There must be a way to get this to connect as it seems really close but so far no joy? As I said, I'm fairly confident the hardware and bluetooth link are good (let's not rule out finger trouble though)

Help Please :o)

Hi!

If the Landrover is * definitely* OBD2 compliant, then it should work with the app without any issues. So the issue will be one of the following:

* Check the diagnostic connector for damage (sometimes something silly like a pin that has been pushed back in the socket that no longer makes contact, etc)

* The adapter may not function for ISO9141 protocols (similar to the Ford issue on the clone adapers). Different protocols use different signalling standards (and wires) to communicate with the ECU. If the adapter is faulty on one of those protocols (ie: missing component, or dry-joint on the PCB) then the adapter may work fine for some protocols, but not others (it would appear to work in vehicle X, but not in vehicle Y, even if both were OBD2 compliant)

* or the vehicle isn't OBD2 compliant. If it is, then Torque will work with it (it's a common standard between manufacturers). So if you are absolutely certain it's compliant, (just having the correct shaped connector won't be a guarantee) then it should work with the app. Bear in mind, that the same model/year of vehicle can be disabled for OBD2 if it is sold outside of the EU / US (this is largely dependant on the manufacturer though, as they are not obliged to provide OBD2 support for some countries)

Thanks for a really quick response! I'll have another poke about over the weekend.

Step one, I will assume that just about every wire/pin on a Defender 90 might be broken as it's basically a tractor :o)

Step two, You're right I'm not "totally certain" of the OBD protocol just because some bloke on some random forum said so. (Needs a bit more research than 2 min on google)

Thanks, if I can crack it I know loads of people that will want this given that the stock Defender doesn't even come with a Rev counter!

So step 1 and 2 this weekend.

1. Plugged in a Snap_On diag unit and it worked and so that confirms the wiring/pins are all in good order.

2. Doing the above seemed to suggest the Td5 is EOBD but the protocol shown was E_KW2000 ? Does that mean anything to anyone?

Unclear if that means Torque will never talk to it or not. Also unclear if Defender was light comercial and therefore not subject to OBD II until as late as 2007? i.e. when it became the Tdci

I'm guessing that I won't be able to use this to enable bluetooth on my 09 RR sport.?

@kiwiandy At the moment, the app doesn't enable/disable features in vehicles (though this may change for VW's as a separate part of the app in the near future)

@defenderist Hm, that means that the adapter isn't able to talk to the ECU - if the snap on tool says EOBD (then it's OBD2 compliant) and should be working. It may be just that protocol on the adapter itself that isn't functional

Things to do:

Enable debugging in the app (Settings -> General Settings)

Restart the app

Let it try to connect to the vehicle for a couple of minutes. Then go to the realtime information screen and press menu->more->send debug info

In the box that pops up, type 'defender 90' and press send, wait for the 'sent ok' message. I will then have a look at it and confirm if it's a bug (or what I suspect, the adapter not talking on that paticualr protocol)

As above, followed the instructions and I think it sent the message with debug. Title Defender 90 Td5

None of the TD5 engined vehicles are EOBD compliant as they use mode 27 (or is 23?) secure comms to transmit fault codes. A generic code reader, or software such as Torque will simply show no codes present, however you should be able to display data from several sensors. Unfortunately you can't even rely on the MIL as the only faults which will turn that on are a bad or disconnected throttle pot.

Hawkeye, distributed by Bearmach, can read TD5 fault codes, as well as talking to all the other ECUs in the vehicle and letting you set options and test actuators. Mind you, it's about £250 and it still won't do everything Testbook can..

i have that OBD2 for my yr08 defender also but it always telling i don't have any fault codes but once i pulg-in nano com it shows me at least two+ fault codes.. what i can do on my OBD2??

Looking for help!!

Have a landrover doscovery 5 MY21 , Looking for software to activate service mode to release the brake caliper? Thanks