Hi

This usually happens on vehicles that are not OBD2 compliant. Are you absolutely certain your vehicle is OBD2 compliant? (Quite a few diesels are not compliant until after 2004 in the U.S.)

It sounds very much like your vehicle is OBD1 and not OBD2. Torque will sometimes work with OBD1 (as the protocols are basically the same) however the wiring in the diagnostic socket *will* include special pins, one of which will be the one that is shutting down your ECU when the adapter does a protocol scan to find the correct protocol to talk to the ECU with.

Ian

Well now, that makes perfect sense. Soooooo back to the drawing board. Thanks for the quick reply. Any chance someone will do a add on to Torque to solve the problem ? Or is it even possible ????

Er, well in the case of OBD1, it's not really a workaroundable problem - it's a different standard which does different things compared to what you throw at it. plus you get the bonus of not having an OBD1 adapter (and I don't think you can get bluetooth ones of those)

Ian

I have a 2011 Subaru WRX and I also had a weird issue where I left my ScanLink dongle plugged in for several hours while at work and when I started it when preparing to head home I had a CEL thrown. I didn't record the code, I apologize for that, but I checked it out online and wasn't too concerned initially. I cleared the codes and went on my way.

When I got home I had a few things take place and I went back out and attempted to start my car and it wouldn't turn over right away for whatever reason. I unplugged my dongle and the car started up...

With the limited information I do have, is this something you've heard about before? I'd have to imagine the issue with the gentleman above is probably not the case with me, so I'm hoping you may have something to check.

Ian I was doing some reading and it's very possible that the PID's I have setup for logging could be a potential issue... If I recall correctly the CEL explanation had something to do with "General Use and Mazda" (words to that effect)...

I have a 2008 Volvo xc70 and a 2005 Honda civic ex. I have a plx kiwi bluetooth adapter. I use torque on a daily basis on my Honda and it works great. Thought I would try it on my Volvo. After driving about a mile, the car went into a cycle of stalling and running every second or 2. I quickly pulled over, disconnected the adapter, started the car and it runs fine. I have driven the volvo 1000's of miles before and after the incident without issue, but have not dared connect the adapter again. I continue to use the adapter and torque on my Honda without issue. Is there a possible compatibility issue with the Volvo?

Quote from emcdonough on April 27, 2011
I have a 2008 Volvo xc70 and a 2005 Honda civic ex. I have a plx kiwi bluetooth adapter. I use torque on a daily basis on my Honda and it works great. Thought I would try it on my Volvo. After driving about a mile, the car went into a cycle of stalling and running every second or 2. I quickly pulled over, disconnected the adapter, started the car and it runs fine. I have driven the volvo 1000's of miles before and after the incident without issue, but have not dared connect the adapter again. I continue to use the adapter and torque on my Honda without issue. Is there a possible compatibility issue with the Volvo?

I have a 95 855 T5 and it works ok, some PIDs will stall my car tho. I think it was the trans temp reading. As soon as it tries to probe that sensor the engine will stumble and usually stall. Starts back up just fine. I'm sure it might be the crappy $12 adapter i got from eBay.