I cannot seem to link my vehicle via OBD. What can I do?

In this article, we'll discuss the most common reasons connecting via OBD fails and how to resolve these situations.

Written By Katya S.

Last updated 9 months ago

Common reasons for connection failure

  • The OBD device does not support a BLE connection

    → Ensure that the device model does support a BLE (Bluetooth Low Energy) connection

  • The vehicle model isn’t yet supported for being linked via OBD

    → ABRP needs to know how to interpret data communicated via OBD in order to make use of it. This is done with OBD commands / PIDs and these can differ depending on vehicle manufacturer and model. You can check all supported vehicle models here in our Live Data Comparison, and if your vehicle isn’t yet supported you can start a ticket in this board; https://abrp.featurebase.app/?b=6724bd07ae5c63c8a1acf5d4

  • The ABRP app hasn’t been permitted to use Bluetooth

    → Ensure the ABRP app is permitted to use Bluetooth in your iOS or Android device settings.

  • Another app is connected to the OBD device

    → Disconnect any other app before attempting to link to ABRP.

  • The OBD device isn’t properly plugged in

    → Make sure the OBD device is properly plugged in. Plugging it out and back in may help.

  • The OBD device’s firmware isn’t up to date

    → Check with the manufacturer of the OBD device if there are new firmware versions to update the device with.

  • The vehicle isn’t turned on

    → Make sure the car is turned on when attempting to link.

Other recommendations

  • Try it again a few times; sometimes, it takes a moment for initial data to be transferred.

  • Make sure to click 'save' once the device has been found and connected successfully.