Hi is anyone using the OBDLINK LX reliably in RealDash CAN mode over Bluetooth. I am using this with my Samsung S8 which I had previously used with MeatPi and Vlink OBD adapters for years without any problems. Now I am trying to use this adapter for CAN and it just seems to drop the connection repeatedly with nothing to indicate the likely cause. I have disabled all the wakeup and sleep parameters using the config software and the problem persists. Any ideas or experience most welcome
Got the log, unfortunately it does not show any other reason for reconnecting than timeout- meaning that data stops coming in.
one reason might be it being accessed by a different device. Make sure nothing else is paired to it.
Thanks for the suggestion, but likelihood is low as I have no other devices in the vicinity, and I have renamed the device using the OBDLink utility and re-flashed the firmware even though it was already current, and the problem persists
Im have one and used it some days ,the devas obdlink lx not stability in contacts same time lost
the connection . Now i used obdlink cx and v link
Hello
I’m having the same recurring disconnection issue with my OBDLink LX dongle. Have you found a solution?
Henri
Hi
I use both the LX and MX models.
In terms of OBD2 communication (11-bit/29-bit CAN), the LX doesn’t seem stable, whereas the MX is stable.
I initialized the LX using the following procedure and tried manually sending a command via OBD2MONITOR to see if it could transmit a custom CAN message.
Initialization works fine, but when sending CAN (ATSH18DA3AF1), it returns a CAN error.
I checked with another device to see if the CAN was actually being output to the bus, but it wasn’t being sent.
I tried the same code on the MX, and it was able to send CAN reliably.
I suspect this is not an error with RealDash-OBDLink, but rather an internal error with the OBDLink LX.
init code
ATD
ATZ
ATE0
ATL0
ATS0
ATSP7
ATH0
ATAL
ATSH18DA3AF1
It could be that LX has some limited CAN functionality over MX. Not sure though.