Saab 9-5 2005 with OBDkey pro and a Samsung Galaxy S3
I downloaded torque (the free version) and it worked well enough for me to buy the full version. It worked mostly (not all data was easily accessible but it worked). i then played around to set it up like I wanted it and now it won't work. The adapter is connected (most of the time), but the car ECU is no longer contactable. I have tried it in two cars, and it still doesn't connect. However, torque lite will still work, as will the OBDkey supplied software, so I know it's a Torque issue somewhere.
I have tried uninstalling and reinstalling Torque pro, unpairing and re-pairing the OBDkey and deleting the program data in apps manager. Nothing makes any difference and as it still knows my two profiles I assume I am not resetting it in any way.
How can I get out of thsi mess I have got myself into?
Ian
Tried it with Torque Free - it works fine. Tried it with the OBDkey software - it works fine. Tried it on a different device (an S2) it works fine. On the S3 it won't now even connect to the OBDkey, though every other bit of software doesn't have a problem.
Something I have done on the original S3 has broken it. Anyone any ideas what?
Ian
I have the same issue. Torque worked fine for about 2 months then a month or so ago it stopped. First it would not connect to the ECU and now it will not connect to the adapter either. 2 other pieces of OBD software work fine. What's up with that?
Update to my post. Found that my connection problems were to do with having that particular vehicle profile connect using the "thorough scan" method for OBD protocol, was not working (perhaps due to my impatience). I found the exact protocol for my vehicle and voila no more problems.
I shall try that. It would fit with my symptoms I guess, because it works until I create a profile and once you have created a profile I can't find a way to delete them. The second device stopped working once I created a profile for my car. I have switched it to Automatic Fast Scan instead of Thorough Scan and will see what that does. If no change I will have to try each of the individual selections.
I have a third device with it installed now (Nexus 7) so I shall test the profile creation theory with that.
Anyone know what protocol a 2005 Saab 9-5 and 2003 Ford Galaxy might use?
Ian
That got it working again, thanks. It would have been nice if the programs authors could have pointed us in the right direction but we got there in the end.
Now to have a play with the settings...
Ian
Hi!
Thanks for the feedback on your experience - this is something I've had a couple of people ask about and it's mainly a 'patience' thing when the app scans the vehicle for the first time ever
Torque can take up to a minute (with the OBDKey adpater) to connect the first time you start it (using the thorough protocol scan). If you use the 'fast' protocol scan (which doesn't work on 100% of vehicles) then it will be faster. The thorough protocol scan will be faster at selecting the correct protocol the next time you connect to it however
You can delete profiles (scroll to the bottom of the profile edit screen and you'll see the delete button). I may change this to a 'swipe' action in an update to better follow the android ui guidelines (though I have to keep android 2.2 compatibility)
In addition, I'm not 100% sure (I haven't got my notes with me at the moment) but the 9-5 may talk multiple OBD2 protocols (this may be a factor if the adapter sees the wrong one first)
Now I have set it to Fast Scan it connects pretty quickly. And as it works reliably so I am not going to play any further unless I find out for certain exactly what protocol the 9-5 uses. What I have works and that's enough.
Thanks for the response though - more information is good 🙂
Ian