I’m having a frustrating problem with this application.

I have a nexus 5, and a cheap USB ELM 327 1.4 device. I’m using the latest version of the torque pro software as far as I know.

Torque ‘sees’ the ELM device, and will start the lights TX/RX lights blinking at 38400 baud. It will not connect to the ECU on my 2004 dodge durango, the ECU lights never blink either.

On the main screen of the app, the connect icon will go green for some time, and the car icon will blink, then the connect icon will go yellow, and the app will say that it cant talk to the OBD adapter. I never connects to the ECU.

I can use a terminal app on my phone, and connect the ELM adapter at 38400 baud and the durango ECU using the 11bit 500K protocol, with no problem.

I have turned on ‘debugging’ in the app, but it never shows me anything, or offer up any type of file to look at.

It fails on my Nexus 5 phone, and a fresh install on my Nexus 10 tablet. Both devices can talk to the ELM adapter using a simple rs232 terminal. The adapter is FTDI -> ELM 1.4

Anybody have an idea how to debug/fix this? Seems like it should be a simple error…

Thanks in advance.

> Have you tried setting your specific protocol
> in the vehicle profile?

Yes, ISO 15765-4 CAN (11bit 500k baud)
I can use this protocol to connect to the vehicle using this adapter and a terminal program.

> re errors being reported under Adapter Status
> icon functions? (normal is no errors). When errors
> are present there may be issues with your adapter.

Sometimes it reports 1 error, then it clears back to 0, The little usb stick icon blinks blue, then solid blue, then goes yellow. Torque is never able to connect to the ECU.

I will get “No response from OBD adapter, did you select the right baud rate?” The lights on the adapter are blinking the whole time. I can set the baud to AUTO, or 38400 and I get the same result.

Is it possible to see what error is being generated? Where is the debug information kept?

Seems like it is real close to working, and is possibly a simple communication/parsing error.

Again, I can connect to the adapter at 38400 baud from both my devices using a simple terminal program. I set the adapter to protocol 6, and I can talk to my ECU and send/receive data just fine.

Thanks for trying to assist!

Hi!

This should simply work – it doesn’t matter on the type of adapter as Torque doesn’t care if the manufacturer id/ version/etc is present or not

What does matter is the ECU responses and that the adapter sends them back in the correct format.

It could also be an erroneous setting in the vehicle profile causing the issue. Make sure you’re using a default vehicle profile (dont change any of the settings in it) for any testing – Torque will always be able to connect to OBD2 compliant vehicles with a default vehicle profile

When you do it manually, out of interest, what is the response the adapter sends back to the 0100 command when you send it to the ECU?

defaults did not work. Still the same condition.

To let you know, I tried OBD Fusion, and it worked right away, with both of my vehicles.

Would really like to get this app to work, so any other diagnostic information I can give you, please let me know.