I got a couple of bluetooth ODB2 readers that talk to my android phone (torque). They work fine, but in my 2006 F430 spyder, it puts the car in traction control disabled mode (I get the sideways triangle and the green LED on the maneto does not follow where I turn the selector). Apart from that the adapter works, but obviously the car is a bit pissed and I'm wondering if it's designed to get in some kind of half limp mode when you don't use a fancy ferrari only odb2 adapter. Does anyone else have experience with this either way? Thanks, Marc
Thanks, so it is adapter dependent. I tried the kiwi on another car, but I returned it because it's huge (big box with a cable) when most competing adapters are small enough to fit in the plug. At least it means I might get more lucky with another adapter, but the kiwi one is just too big for my taste. Thanks much.
I have an ELM327 coupled to laptop. I can see DTC - p codes. However the other info is very limited. Like I can see throttle position (but not accelerator pedal). Also can only see the O2 sensor on bank1. Nothing on bank2. What do you get with the bluetooth OBD2 tools
I use a "Scantool" (BT) on a 360. When I first connect I get no choice and the system connects to ECU11 which is one or other of the two (don't recall which off hand). If I tell the unit to disconnect and reconnect I get an option to connect to ECU11 or ECU14. Only on the second connect do I get the option for the second ECU. Also, I cannot connect to the second ECU if the Immobiliser is armed. Maybe this will help you with your O2 issue on bank 2.
