Possible OBDLink MX Issue?
- Thread starter Bigjht
- Start date
firewater88
New member
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?
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?
firewater88
New member
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.SHOdded said:
AT warning happens once started to drive away but torque hasn't fully connected to ECU yet.
ecoboostsho
New member
You could try obdfusion and see if that still causes the issue. Would potentially rule out torque Pro..
Sent from my XT1096 using Tapatalk
Sent from my XT1096 using Tapatalk
firewater88
New member
Thanks, will give it a try.
firewater88
New member
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
Thanks for the advice
firewater88
New member
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.
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.
