Hi!

Is torque still functioning when it ‘freezes’? (ie: can you still navigate around the screen) – if you can, then it usually means that the adapter is freezing up or there is something intefering with bluetooth (in other cases, a damaged OBD socket has caused the adapter to restart/reset, so check that the OBD2 socket looks ok physically)

I am having the same problem. Just got a osblink mx . When I first started it there were all the readings on the dials I wanted. Then after about a minute it dropped the bluetooth and had to reconnect and barely any pids.

I have tried over and over it work with the extended pids after resting everything then nothing. What gives?

Are you using a vehicle profile with the protocol
set specific to your vehicle eliminating the auto
search?

Just another user.

When you were using the auto search
for protocol did it ever connect to the
ECU?

If it did you can look under the adapter
status icon functions to see which protocol
was used.

VPW or 11-Bit CAN has been typical for
most Ford 6.0 users here.

J1939 is typically for commercial vehicles
which like you said Torque doesn’t
support yet …but I could be wrong.

Just went one a great run maybe twenty minutes. It was reading the extended pids I wanted beautifully. Then Bamm nothing no bluetooth connection. This was after about a 15 mile cruise up the freeway. All the way home it wouldn’t connect, i even tried to shutting off the truck and restarting it, nothing Then in my driveway I reset the mX and resycned it. Turn it on everything on. 5 seconds later not connected.

A couple of times I noticed it was connected , but not to the ecu. It would be in this state for a few minutes or so. I am starting to think its the bluetooth adapter MX

How much voltage does it need ? I think i remember seeing it and it was 13.7 or 14. I will have to look again to be exact.

Although from reading another post I don’t think this mix adapter is comparable. I think the lx would solve the problem.

Yes I believe it said 13.7.

So today the LX came and I put it in. First start , had trouble reading the extended pids. It showed like 46 errors in other faults under adapter.

Then I restarted everything and perfect was reading all extended pids and maybe even some I dint see before. Then after 2 minutes same thing, nothing.

It still showed bt connected and ecu connected. Also there were no error counts either. That was funny when this would happen on the mx it would always show other error counts. I waited a second the it came back , ten after 45 seconds gone.

Then I had trouble even reconnecting back to blue tooth and ecu. I think Im done. I just wished it would have worked.

Did you ever get this solved? I have the OBDLink MX Bluetooth and after about 3-5 minutes most of the PID Displays freeze. Those that remain active are the SAE PIDs typically.

Hi!

This is usually if something consistently replies ‘NO DATA’ to a pid request meaning that you likely have a problematic OBD adapter or the connection to the ECU is causing repeating NO DATA replies

I’ll see if I can do something with this in one of the updates soon, though it’s not a bug, the ECU is saying there’s ‘no data’ at some point for your PID requests and that usually means a connection or adapter problem. The app does this because of another problematic vehicle (which is still within the sae spec, just) to work around issues there