Abs lights are turning on but only when I use Torque

Jimbo69ny:

This may seem odd, but try unhooking the bluetooth cable when you shut the car off and don't plug it in until after you start the car. Try this for the next few days and see if you stop getting the lights coming on after the first couple of miles.

BTW - assume you also leave the device the you are running torque on in the car when its off?

 

I actually meant the Android device, not the adaptor. Does it stay in the car also?

 

The adapter runs off the 12v auxiliary battery, you could be running in to a low battery situation.

http://priuschat.com/forums/newbie-forum/73400-weird-stuff-happening-mpgs-dropping-test-battery.html

 

Well, I have this same problem in my car that I have narrowed it down to specific conditions that will reliably cause this condition.

If I leave the bluetooth turned on on my Android device (that stays in the car) the ABS and related lights will come on reliably after I drive a few miles. They will go back off only if I shut off the car, unplug the bluethooth adaptor and then restart the car before I plug it back in. Of course if the lights are on, regenerative braking is disabled.

If I make sure that I either turn the Android device off completely, or simply disable bluetooth on the device until after the car is made Ready, I have no problems with the ABS etc lights. This is easy for me to do as Torque has a setting to turn bluetooth off when it quits. That is not something you would likely want, however, if you are using the bluetooth for other things with the phone (like hands free calling).

In your case I suspect that as you get close to the car and get in, the phone and the adaptor start communicating some before you make the car ready, and on come the lights after a few miles. Somehow I think you need to keep the phone and the adaptor from communicating when the car is not Ready. Likely the easiest way to do that, is keep the adaptor unplugged until after you start the Prius.

 

Pin 16 on the OBDII port is power. I am adding a switch to it! Since my surgery I have not been driving as much as I want, but the battery is getting low. I dropped the maintenance charger on it to keep it topped off.
A relay that comes on when you power up will be added to my setup.

 

I experienced the same thing as the OP when I would stop for gas without turning off Torque or the kiwi bluetooth adapter. The car would come on fine but within a minute three yellow lights would come on ( (!), ABS, VSC) and regenerative braking was disabled. I described my issue here: http://priuschat.com/forums/gen-ii-...-brake-brake-warning-abs-vsc.html#post1392900

A bit later I ran across the suggestion that if your specific protocol wasn't selected Torque might be spamming the OBDII port with other protocols in its search for an ECU.

This spamming could potentially stomp on or interfere with some ECU-ECU traffic and trip the warning lights. I decided that was a plausible explanation, selected the protocol my prius uses (ISO 15765-4 CAN 11bit 500k baud) in Torque's vehicle profile, and the problem has not reproduced itself since.

 

I'll try it too! Thanks for the thought...

 

Could you call my wife and let her know that? That would really help me out

Not really a guess, you can confirm it yourself with one of usbseawolf2000's custom PID "Brake - Regenerative Torque (lbs-ft)." That one and "Brake - Friction Pad Torque (lbs-ft)" are two of my standard gauges as I like to monitor just how often the crappy roads in this town kick me out of regenerative braking to friction braking whenever the road has some ripples or potholes in it. I should really stop monitoring it as it just makes my driving here an even less pleasant experience.

 

holy crap i just typed up a whole post explaining what happened to me and here someone beat me to it. Pretty much the same thing happened to me. I'm just glad this has happened to others as i feel very relieved now...

 

I never had that issue, probably because I selected ISO 15765-4 CAN 11bit 500k baud. Auto detecting every time take longer so I just selected that.

 

Setting the default protocol worked for me as well. I never noticed it was a settable thing. Good tip! Thanks. I still find myself turning the program off when I stop as I am used to doing that.

I really should take some time to learn more about the Torque program itself. I have learned just enough to get usbseawolf2000's custom PIDs working. There are probably many useful controls and features I know nothing about.

Which makes me think maybe usbseawolf2000 would want to consider adding that setting to Post #1 so people in the future don't experience this problem.

 

I was having this issue with my Gen III and what I found worked was not to go into the Realtime Info (gauges) screen until the 2 ODB blue symbols had stopped flashing on the upper left of the Torque home screen (takes about 20 seconds for me). Again set ISO 157-4 CAN (11bit 500k baud) as the Preferred OBD2 Protocol (last line in the Vehicle Profile Editor.) Perhaps the "Traction control Disable" PID in the custom PIDs I added may be the issue, as it may scan through all of these when first connecting, can't say for sure.