Hi!

You likely need to set the protocol in the vehicle profile to the specific protocol for your vehicle - Torque asks the adapter to locate the protocol itself when it starts, and the adapter will cycle through several protocols.

Selecting the correct protocol for your vehicle in the vehicle profile will stop the adapter trying to select the wrong protocol (and it's a timing thing)

Hi,

Thanks for your reply. I did pre-select the protocol. I remember the post you mentioned. I select CAN 54bit protocol in toreque pro application, but still the same issue. My car is 2017 toyota camry 4cylinder 2.5Lite LE. Still same problem. On that post it tell me to choose right protocol for my toyota and that CAN 54bit is the right one as I know. Any other ideas you have?

Anyway, same thing works fine on old toyota. I should say that new torque pro application does not work well with new toyota cars.

Hi!

Nothing has changed in the initial OBD connection code between the old and new versions, that code is still the same

You'll want CAN 11 it or 29 bit (there is no 54bit option) in the settings. I would suggest leaving it on (Automatic - Fast protocol scan) which also may work around the issue

@hover:

try to enable the use of alternative OBD header on vehicle profile.

not sure it fix the issue for you, but in my case (2010 Mazda 3) using alternative obd header I fixed the error warning light of Blind Spot Assist.