obd2 & Torque issues

I've read on here about it causing delays/confusion if OB2 is plugged in when the car boots up / goes into ready mode. Something about the OBD2 interfering with Prius system scan to make sure all the electronics are up and running. Perhaps you could figure out a way to put a switch in the system and set it up so it doesn't get turned on till after the vehicle is up and running?

 

The issue I have seen posted was due to the protocol auto detect.

To resolve it, go to Vehicle Profile and set it to CAN 11 bit 500 baud. It will also speed up the process.

 

nice to know, thanks

 

So far, so good with me. Though, I did find it disturbing when I plugged in my BT adapter for the first time and connected to the Torque app, my reverse beep came back. How could that have happened without actually issuing the command? For that matter, I haven't even brought that display to the dashboard.

Anywho, I've been toying with the app itself, the layout, and the downloaded data. It takes awhile to get a feel for it all... especially when comparing differences between Android versions and screen resolutions.

I just got an ODB splitter yesterday. So, now I have both my ScanGauge and Torque available at the same time. That setup is working well too. I was a bit worried about having so much cabling to deal with. Turns out, all that can be secured tight and tucked in without getting in the way of anything. Phew!

Thanks to all the advice those have shared so far. That's been really helpful.

 

Where did you get the splitter?

As for the beep, just previewing the settings used to trigger these settings, but this was recently addressed in the latest pid list.

 

Which OBDII dongle did you get?

When you browse the list to pick, Torque actually sends the command to display the data as you scroll. A cool feature but the PIDs that changes the configuration got sent as well.

For that reason, I have separated out those config PIDs into different csv file.

 

OBDII Splitter Y Cable, J1962M to 2-J1962F, 1ft (145802) : Amazon.com : Automotive

Yup. And I wondered if that would do it, as I was scrolling to watch each of the values fill in.

 

I discovered a new issue tonight:

DON'T LEAVE THE APP CONNECTED TO THE PRIUS WHEN YOU POWER OFF THEN POWER BACK ON!

I was just going to run into the house for a few quick things. Why bother shutting off or disconnecting the phone? It became obviously about 100 feet from my house. Warning lights starting illuminating and the screen displayed a "CHECK PCS SYSTEM" message. Needless to say, I quickly figured out what had happening. And yes, I took the extra step to confirm my theory. Powering off then on again brought back the same condition.

Powering off again, killing the phone, then powering on again, all returned to normal. Phew!

 

so you narrowed that down to Torque as opposed to the OBD2 scanner? I read on Amazon that the "cheap" scanner do sometimes weird things whereas the primo ones behave much better...?

For those who have issues, what scanner are you using?

I am using a Kiwi Bluetooth and never had any of these issues, but again I have a TCH 2012.

 

Confirmed from my side as well on TCH 2012: When I leave Torque running and I power off and on again the engine, I have weird stuff happening, last time I had the airbag light and another one that were on.

Switching off the car, the application then starting on the car then switching on the application fixed it all.

 

Someone should report this "bug" to Torque app author on their forum. Ian is quick to fix things.

 

Can someone share some screenshots of the Torque app? Especially features related to PIP.

 

This is my setup. For a full list of available PIDs, go here.

 

Anyone have any issues with the adapter draining battery?

 

Not yet, have it in my pip for about 2 weeks running, all the time, no issue yet!