OBD2 Connection Issues

I’m a new user. Hardware is Raspberry Pi 3. I first tried an OBD2 to USB cable…the connection would last a few minutes, but then just stop working, i.e., just driving a short distance and the gauges would stop working…as if there was no longer data being received.

Now I am trying the OBDLink LX bluetooth device. The Raspberry bluetooth would never detect it, but inside RealDash it was detected and I selected it. In the OBD2 Monitor screen there were two errors. At >0100 BUS INIT: …ERROR and at >0900 BUS INIT: …ERROR. Everything else looked okay, it detected the protocol, I selected the file, and returned to the gauge display.

Then none of the gauges worked and in the bottom right corner a small message kept popping up “Connecting… OBDLink LX”. I waited several minutes to see if it would eventually connect, but it just kept popping up.

I then went back into the Garage and Connections to check on the connection. Selected the connection, then into OBD2 Monitor, but this time it just kept repeating “Connecting” and “Not Connected” over and over.

EDIT 01: I tried using the Bluetooth device with a Windows tablet. It did find the device and connect. Inside Realdash I was able to connect to the device and the connection was more reliable, however, there were still a few times within an hour that I had to return to the connection settings in Realdash, run the OBD2 Monitor, and the connection resumed.

I’m assuming the raspberry pi is running Android? Possibly Linux? And Windows is obviously running Windows

I’m thinking most likely it’s a bad Bluetooth device. Try it with your phone on Android if you have one and see if you have any issues staying connected.

For me, this sounds like there could be a PID request that your vehicle does not respond to. Some adapters/vehicles also need some extra delay between requests for not to get stuck.

Please send a debug log, I can take a look:

How to send a debug log - General / Frequently Asked Questions - RealDash Forum