OBDLink MX Bluetooth with Torque Pro Android app
 

I recently purchased the Scantool OBDlink MX Bluetooth OBD2 adapter for my 05 RX8. ( ScanTool.net LLC - OBDLink MX Scan Tool | OBD Interface | App Accelerator - ScanTool.net)

& Also got the Torque Pro android app for my tablet while operating in the car. (which is pretty sweet; real-time gauges, info & check fault codes)

Is there anyone else running this setup & having any electrical issues with it?

I put in a new redtop battery @ the same time I plugged the OBDLink MX into my OBD2 port.
Another mod i did was 25mm wheel spacers.

& I have been getting CAM communication error codes ever since.
U1900
U0073
U0155

Also to add my power steering stopped working. & going bonkers trying to figure that out.
Im thinking this might be related.

Im thinking maybe having this constantly plugged into the OBD2 port is causing the CAM communications to fault.

Any help with past experience & any input would be appreciated.
Thanks.

Wow, $149 bucks. I bought the cheap chinese knock off on Amazon for $15. I've been using it with Torque Pro without any issues. I leave mine plugged in 24x7 too.

Not all bluetooth OBD2 adapters are created equal, and not all cars are created equal too. My bluetooth adapter (OBD+Key from the UK) has worked without a single blip on my 99 Miata then 05 MSM, wife's 06 Mazda5 then her 12 Mazda2.

Different story with my RX-8. Plug it in, don't connect to it and everything is fine. Fire up Torque, as soon as Torque connects to the adapter, my DSC/TCS is immediately disabled and I get the communication errors. If the adapter is already plugged in, Torque running and connected, and THEN I start the car, no errors or issues. I think this indicates that it's a command from Torque that the ECU doesn't like and causes a fault, but it's only sent when first connecting to the adapter or ECU.

Since it doesn't happen the same on every RX-8 with any adapter, the adapter plays a part.
Since it doesn't happen on every car with the same adapter, the car ECU plays a part.

It's not just Torque doing it, and it's not just the adapter, and it's not just the car. It's something that is playing with all three that causes stuff like this.



There isn't any real long-term study on comparing adapters though, so it's still largely a crapshoot with decent, but not perfect, odds.

hmm, interesting so maybe ill start up torque app before i turn the key to ignite the motor & see if this still occurs.
Is it possible my power steering issue could be tied to this at all?

Might be, might not be. Our ECU does have power steering maps in it, so a communication error could possibly be affecting it.

Or you might just have a dirty PS connector as well :)

yeah; i ruled out that ps harness yesterday. Hard wired everything with new wires like MM did. Also greased the knuckle like u did.
But thanks for the input.

price difference is based on the technology used in the package. Most cheaper devices are using the dated ELM chipset. ELM has been around for quite some time and only supports one bus (which is generally all that is needed when doing OBD2 sniffing). ELM chipsets do not have any power saving features. This supports up to 500kbps UART transfer rates

Newer devices like the obdlink use the newer STN chipset. Supporting multiple highspeed and lowspeed busses is one of the best features of this chipset, as well as integrated power saving features which allow you to keep it plugged in 24/7 without draining the battery. Supports 38bps to 10MBps which is awesome if you would like to design your own software and monitor like 20 PIDs at once.

On top of that the STN chips are 10x faster than the ELM chips, have 4 times more ROM, 8 times more RAM, a lower input voltage, have upgradable firmware, and can access more advanced ("ST") bus commands.

Thanks Paimon, removed my prior statement. Thanks for schooling a noob :)

updated my post to reflect the changes you made lover :)

I found a solution that is holding up true.
RIWWP is correct that you need to connect the software after the engine has started.
here is a very helpful link.

Forums — » Torque OBD ECU Scanner » Torque Discussion / Ideas » Help: all engine lights on after connecting!Torque

So my solution is to disable bluetooth on the tablet as shut-down.
Once vehicle is running. Enable bluetooth on the tablet.

as for my PS problem; disconnected negative terminal, 10 break pedal stomps within 5 seconds.
& it worked!

Actually, the problem I had was the reverse. It only worked fine if I was already connected before starting the engine. If I connect after the engine is running, I get the TCS disabled. While driving, leaving it in gear, and quickly cycling the key off then on (restarts smoothly as if pull started), the light clears and TCS works again.

Looking at the link, it does look like it's a combination of the adapter I have plus Torque plus how the RX-8 doesn't like what it sees. Change the car, no problem, change the app, no problem. I don't have another adapter, but I've considered getting a 2nd for my wife to keep with her, just in case.

No issues on mine
 

FWIW, this is the adapter I use with my Torque app for my HTC DINC2 (sorry for small image, I bought on Amazon and it's an ELM 327 BT adapter). It will not connect unless I've already started the car. Doesn't work otherwise. Although I don't get near as much info as I'd like, it doesn't cause any issues so far. Knock on wood! ;)

EDIT: After owning this adapter a little over a year now it is what I suspect to be broken. :wallbash: The screenshot doesn't show it but it says "Faulty Adapter" at the bottom of the screen while the Torque app is in use. It still clears CEL's and reads information correctly as far as I can tell. I'll keep it for the cool display options with Torque app. I believe I'll purchase an actual scan tool for proper diagnosing.