Possible OBDLink MX Issue?

ecoboostsho · August 08, 2014, 11:34:25 AM

Its not a guaranteed it will happen. Just not recommended...at least by me. I used to have a cheap adapter and this would happen all the time to me...I would be driving around and the dash lights would literally freak out. Very disconcerting although the car performed fine the whole time. Hasn't happened since I switched to the MX but I suppose its still possible it could be causing everyone issues.

Sent from my XT1060 using Tapatalk

SHOdded · August 08, 2014, 12:21:55 PM

Darn those ACKs and NACKs

Larrylu · August 08, 2014, 01:00:34 PM

Quote from: FoMoCoSHO on August 08, 2014, 11:21:31 AM
Weird, I never have any issues like that. Unplug one device, plug in another....no issues.

Me too! I Leave mine plugged in all the time but also have had no issues unplugging the my tuner (MyCal) and plugging the MX in with the car running or not. It's never been squirrelly or fussy.

ZSHO · August 08, 2014, 01:14:22 PM

It could be a 2013 PP issue like the wheel hubs LOL.

Bigjht · August 08, 2014, 01:15:41 PM

The issue I was having is on my truck not my SHO.

ShoBoat · August 08, 2014, 01:53:30 PM

Quote from: Bigjht on August 08, 2014, 01:15:41 PM
The issue I was having is on my truck not my SHO.

Maybe you have an F150 SHO

firewater88 · December 06, 2016, 09:19:04 AM

Sorry to dig up an old thread, but searched and found this.
I switched to the MX adapter for my Nexus 7 from a cheap one and now get service Advanced Trac error while torque opens and seems to be polling sensors before it says connected to ECU. Goes away and never comes on once connected. Does not happen all the time and never had it with the cheap one, only issue I had with it was torque would show it as a faulty adapter.
Did anyone figure out the issue with thiers? Bad adapter? Just the way it checks sensors?

SHOdded · December 06, 2016, 10:07:17 AM

Did you connect it before the car was started and all the warning lights went out? Try connecting it just before you are ready to drive away.

firewater88 · December 06, 2016, 10:19:52 AM

Quote from: SHOdded on December 06, 2016, 10:07:17 AM
Did you connect it before the car was started and all the warning lights went out? Try connecting it just before you are ready to drive away.

It is always plugged in to port. I have the Nexus7 set to power on when car starts and shut down 5min after car off (all through Tasker and switched power) so it gets a fresh boot every time I start car.
AT warning happens once started to drive away but torque hasn't fully connected to ECU yet.

ecoboostsho · December 06, 2016, 10:45:52 AM

You could try obdfusion and see if that still causes the issue. Would potentially rule out torque Pro..

Sent from my XT1096 using Tapatalk

firewater88 · December 06, 2016, 10:57:05 AM

Thanks, will give it a try.

firewater88 · December 13, 2016, 01:43:41 PM

Running a different app than Torque and I have not had that AT error or any other errors upon startup. Although, it is getting cold and have been remote starting the Flex and by the time I get in, the tablet has booted and connected up already. May try to do a full wipe on Torque and see if it still continues.

Thanks for the advice

SHOdded · December 13, 2016, 01:56:29 PM

We shall overcome

firewater88 · January 31, 2017, 07:05:00 PM

Found the fix for this on the apps forum:

It's an issue with the adapter searching for the protocol when the vehicle is starting the ECUs up and checking comms (should not cause any permanent issues as an ignition reset should clear them)

Go into the vehicle profile, then select the advanced settings and in the protocol selection, choose "Automatic – Fast" as the protocol selection (this will scan for protocols in a different mode that will cause the issue to not happen anymore, though it may work on older vehicles (pre 2004))

Has worked for me since, connects in faster too.