Connected to Bluetooth but not to ECU
by Frodus (and Piemmm)

I’m going to document this here, since a lot of people ask and I’ll try to make it more searchable.

If you’re having an issue where the bluetooth adapter will connect to torque, but torque is having issues connecting to the ECU, its usually because either the protocol isn’t being detected by the adapter correctly, or the protocol hardware (CAN, K-line, etc) is faulty.

So here are some things to try first:

– Check the vehicle profile. Make sure the protocol is set to ‘Automatic (Fast)’ and the OBD2 adapter is set to ‘As defined in Global OBD2 settings’. Then check that you have told Torque to use that vehicle profile.

– If that doesn’t work, then Set the protocol to “Automatic – Thorough protocol scan” and wait. It might take a few minutes connect the first time.

If neither of those work:
– Google the protocol for your year/make/model of vehicle. Enter that protocol into the vehicle profile manually and then try to connect.

If nothing works:
– The adapter likely has faulty hardware on the protocol the vehicle uses. This is unfortunately fairly common on some of clone adapters commonly found on E-Bay/Amazon. It usually manifests as working on one manufacturers vehicle, but not a different manufactures (different manufacturers use different wires/protocols in the adapter, and sometimes they’re not all working due to a fault). Unfortunately this will need you to get a replacement adapter

I can confirm that one of the ones I got on ebay did not have k-line and I couldn’t talk to my Girlfriend’s vehicle.

Corolla Fielder 2006 – not supported.
I bought this software to add some external gauges from my car to phone, trace trip and make diagnostic. Was surprised, that program can’t find ECU, even if I add init string from other program (HobDrive in this case). I drive JDM Toyota Corolla nze144, phone – LG G Flex. (my comment from Google play).

Sorry for my English, also, I can add that I have one more device connected to phone – Sony SmartWatch2. Can’t believe that this one can effect, cause different software is working. It shows me init string

ATSP6\nATAL\nATSH7E0\nATCRA7E8\nATST32\nATSW00

I really confused in this string only in ATCRA7E8…
Any Ideas why I have problem whis connection to ECU

Quote from Capp777 on August 5, 2014
Have you tried adding your init
string to the custom init string field
in the vehicle profile?

of course i have. First of all, a put string from HobDrive to vehicle profile, Torque found correct protocol (that is also mansioned in init string), but anyway, can’t connect to ECU.

Thank you so much I was about to give up on Torque because it would take forever to detect the ECU! I’m really happy its all working properly and connecting re connecting without issue!

Thanks,

Charlie

BUMP.
Can someone tell me if manual selection for the protocol is not shown in Torque Lite edition ? I assume Profile creation is the same deal ?

i have some problem with the connection to ecu with my infiniti g35 2006 , i have tried all the setting and i dont find the protocol k1297-g35 in the app .. i dont know if is in there on other app
can u help me pls
sorry for bad english

Hi

I am new to this site. I bought a Vgate obd scan and downloaded the torque pro app on my phone. Everything comes up with a tick except connection to ECU i have tried the suggestions as above but still not working.I don’t know how to manually put in my protocol for my car. Has anyone else had the same problem with a Holden? I have a 1999 VT Equipe or is it a faulty obd? I live in New Zealand and bought mine off trade me.

Any help would be much appreciated