Hi!

If your vehicle is definitely OBD2 compliant then the app will work with it (however, just having the correct shaped socket does not automatically mean it’s OBD2 compliant)

If the vehicle is compliant, and you have the app connected to the adapter ok, then it can only be an issue with the adapter not functioning correctly

Ah!

The legislation for OBD2 is very different in japan – this affects imported vehicles that were originally sold in japans domestic market – they’re not required to support OBD2.

You will need to double-check that the vehicle is really OBD2 compliant, as you may find that it is not – Usually the ECU firmware determines if the vehicle is OBD2 capable or not (so you may find that a UK firmware would enable support, though you would need to speak to some honda experts to see if that’s possible first)

Hi

It’s the adapter that does the searching for the correct protocol and does the hard work of talking to the ECU, Torque merely asks the adapter for various readings once it has connected to the ECU

If the adapter can’t find a protocol to talk to the ECU, then Torque won’t be able to talk to it – whether that is the free or pro versions. This could mean (that if you definately absolutely know the vehicle is OBD2 compliant) that it could be the adapter

Ah

J1850-PWM is a problem protocol on some adapters – there is a note on it on the http://torque-bhp.com/wiki/Bluetooth_Adapters page due to the number of adapters with issues with that protocol (usually it only affects ford vehicles though)

Yes, you can enable ‘debugging’ in the general settings, and then restart the app

Let the app try to connect for a minute, then go to the realtime information screen->menu->more->send debugging info.

Type your forum name in and ‘toyota’ in (so I know what it’s about when I see it) then press ‘send’. I’ll have a look and confirm what is going on for you

Hi!

Sorry – in the settings from the main screen (press menu when you start torque), then go to ‘General Settings->{scroll down}->Enable debugging

Hi

Check that the Honda supports OBD2 – if it does then it should definitely work with Torque.

Which would mean that you are unlucky and have a defective clone adapter (that works on one manufacturers protocols, but not another manufacturers different protocols) – they should work on all protocols, but due to build quality and testing issues means that your adapter likely is defective on the protocol your honda uses (it’s the adapter that does the job of talking the correct protocol to the ECU)

You may need to get the adapter replaced (after you have checked the honda supports OBD2) – if it’s a petrol based engine then it should support it if you’re in the EU/US (diesels support OBD2 from 2004 onwards)

Ok my adapter used to work on my car. Loaned to friend, upgraded phone, now phone connects to adapter but no communication with the ecu.

Cars are identical in every way, year make model. Heck even the same color.

According to a chart of protocols by vehicle that I found (which listed the correct protocol for my Dodge Durango) the protocol for my
2007 Chrysler Town and Country is “VPN”. This protocol is not listed among the ELM37/Torque protocols, and it does not fond a correct protocol when doing an auto search. Will this protocol become available, or is there some other way to communicate with the OBD?