LSDroid time out issue

[The_Big_Swedish]

Not sure what the issue is, it worked flawlessly on first read and write execution. Now when I try to read or write I get a time out alarm every time.

Im using an OBDLink MX+ it will connect and work with their software but times out with LSDroid. Different PCM same issue, different harness (stand alone vs. bench) same issue.

I've exhausted every idea I could come up with short of buying a new OBDLink.

I would really appreciate some insight into this.

Thanks, James.

[B52Bombardier1]

What is the PCM voltage while having this problem?

Rick

[The_Big_Swedish]

What is the PCM voltage while having this problem?

Rick

I'm not sure if it is a voltage issue. Just tried it now and voltage is 12.44

[The_Big_Swedish]

What is the PCM voltage while having this problem?

Rick

12.44 battery voltage, PCM shows 12.2v

[B52Bombardier1]

Try using the MX+ on a completely different vehicle. Stream a lot of PIDS while the vehicle is running. This will tell you if the MX+ is healthy, at least for reading.

What version of LS Droid? I'm at 2.2 Beta. You might try reloading LS Droid.

Rick

[The_Big_Swedish]

Try using the MX+ on a completely different vehicle. Stream a lot of PIDS while the vehicle is running. This will tell you if the MX+ is healthy, at least for reading.

What version of LS Droid? I'm at 2.2 Beta. You might try reloading LS Droid.

Rick

I connected the OBDLink MX+ to a 2016 Hyundai Santa Fe and went for a test drive with live readings active. Everything works as it should via OBDLink software.

It originally worked with LSDroid v0.2.1 before the time out issue. I uninstalled the app then reinstalled same version, no change. V0.2.2 same result. V0.2.2B same result.

I first noticed the issue after using the OBDLink software, they require you to register the device before using it. Could there be some kind of licensing issue where OBDLink blocks out other software?

[B52Bombardier1]

Are you flashing the PCM while the PCM is installed in the vehicle or with the PCM removed and supported on a bench harness? The LS Droid documentation mentions that other modules on the data bus can interfere with LS Droid communication to / from the PCM.

I have an MX+ and I'm happy with it on a bench harness and I never do flashing to a PCM while its in the vehicle. The Droid documentation also mentions that the MX "+" device is strictly speaking, NOT a supported device. Pete mentions that firmware could be the cause here with the MX+ device but again, I have great luck with it on a bench harness using the latest firmware.

Lots of stuff in that LS Droid app documentation.

Edit: your 12.2 VDC level noted above is the absolute ragged lower limit for LS Droid.

Rick