I ended up buying a BT OBD device from Amazon because I had read about all the issues with the Chinese units. While I am sure that is where mine comes from I figured I had a better return policy. So when it arrived I quickly popped it in my 2011 Audi A4 and our 2011 Ford Edge. I had no problems pairing with the device and in both vehicles the Torque app shows an ECU connection.
I played around a bit in the Audi and was surprised that requesting codes shows nothing. I had cleared codes previously with VCDS-Lite but it claims there is no historic data. Also while it was plugged in the ABS warning came on but it never sees a code for that. Though I did read somewhere that ABS systems are not well supported. Beyond that I noticed that while it does seem to read back a lot of data there are some things that seem suspicious. Like the throttle position...every now and then it will seem to really overshoot the actual position. Also the boost doesn't have any data. Based on what I read it seems like this is a calculated value using the MAF (working) and engine size (input). So am I doing something wrong or is this device a little quirky? Or is this vehicle just one of the protocols that isn't well supported so some issues are normal? If this is a device issue is there a way to really confirm it is working correctly?
Hi!
Throttle position isn't what you think it is - it's a relative reading (per the SAE specification) not an absolute reading, http://torque-bhp.com/wiki/Throttle_Position has more information on this
VCDS isn't OBD2 - it's VW's native protocol that talks to different systems other than the engine ECU, and also has a different fault code reporting system
OBD2 historic faults are not required to be supported by vehicles which is why you don't see them (however the CARB (us thing) is trying to mandate the use of this field i believe for newer vehicles)
OBD2 fault code reporting primarily coveres the engine, powertrain and emissions systems (abs isn't part of that spec) which is why you're not seeing fault codes for it but may be in VW's native protocol - Torque does support VW's native protocol using a paticular adapter (a recent addition) and will be able to read VW's native fault codes soon, using that adapter
Thanks for the link on the throttle. What I am seeing is slightly different but suspect it has something to do with how inputs to the throttle are handled. Meaning if it sees a quick increase in throttle % it jumps to 100% assuming you will need full acceleration. Then when it sees the input stopped increasing it back way down.
As for the VCDS...I should state I was not intending on this being a complete replacement to that system. Just a quick and dirty way to check codes on the go. The car has over 200k so things are likely to start crapping out and want to be able to tell the difference between a post cat O2 sensor and something much worse. Just to verify, maybe this weekend I will disconnect the post cat O2 just to make sure this does read the code appropriately.
Any reason I wouldn't be seeing the calculated version of boost? I do have MAF, RPM and intake temp readings and engine displacement has been set. Is this a paid version thing only? All the videos I have see with it working appears to be paid.
But even though I said I never intended on this being a complete replacement to VCDS...can you elaborate more on the adapter that would be needed?
WBH BT4 – Bluetooth VAG vehicle diagnostic interface with WBH-diag Pro
The http://www.obd2-shop.eu/wbhbt4-p-213.html web page is in German so do a Google or Bing search for WBH BT4 and use the translate this page link to change to English or whatever.
Hi
Boost (using maf) is the full version only at the moment (I should roll this in to the lite version now to be honest so might do that in it's next update)
On the VW Fox I used to have access to, the throttle used to go quite high when you floored it, but would then drop back (I think it was about 60 to 75% after the engine went above a certain RPM) - not seen that behaviour on the fords I've tested on though
Quote from admin on August 9, 2012
Hi!
Throttle position isn't what you think it is - it's a relative reading (per the SAE specification) not an absolute reading, http://torque-bhp.com/wiki/Throttle_Position has more information on this
VCDS isn't OBD2 - it's VW's native protocol that talks to different systems other than the engine ECU, and also has a different fault code reporting system
OBD2 historic faults are not required to be supported by vehicles which is why you don't see them (however the CARB (us thing) is trying to mandate the use of this field i believe for newer vehicles)
OBD2 fault code reporting primarily coveres the engine, powertrain and emissions systems (abs isn't part of that spec) which is why you're not seeing fault codes for it but may be in VW's native protocol - Torque does support VW's native protocol using a paticular adapter (a recent addition) and will be able to read VW's native fault codes soon, using that adapter
Which adapter are you talking about ?