OBD2 adapter connects but shows no data? How to fix it

When an OBD2 adapter connects but no data appears, the problem is almost always one of a handful of things: the car isn't awake, iOS has grabbed the adapter, the adapter itself is stuck, or the car limits what third-party scanners can read. Work through these in order.

1. The car isn't fully awake

Some cars only answer once the engine is running and their self-tests have finished. Start the engine, wait about 15 seconds, and try again. Electric vehicles need to be in Ready. Subaru models with EyeSight keep the data bus quiet for 5 to 10 seconds after ignition while the camera self-tests; that's normal.

2. iOS has paired the adapter

Bluetooth LE adapters should connect only from inside the app. If the adapter was paired in iOS Settings, often by a firmware-update tool, iOS can grab its classic Bluetooth side every time the car starts and block the connection Odo needs. The giveaway: it only works after you turn Bluetooth off and on.

1. 1

   Forget it in iOS

   Open iOS Settings → Bluetooth, tap (i) next to the adapter and choose Forget This Device.

2. 2

   Reconnect from Odo

   Connect only from Garage → OBD II in the app. If a later firmware update pairs it again, repeat the Forget step.

3. The adapter is stuck

Some adapters, especially inexpensive clones, freeze after an irregular disconnect. Unplug the adapter, wait 30 seconds so it fully loses power, and plug it back in. For a brand-new adapter that never responds, confirm it's Bluetooth LE and ELM327-compatible, then long-press it in the scan list and try Minimal Init, which skips setup commands a few firmware versions mishandle.

4. Data stops updating after a while

If readings freeze after the car was parked or the ignition cycled, the car's computer has likely gone into low-power mode. Odo notices and reconnects on its own within about 30 to 45 seconds. To skip the wait, tap Disconnect on the adapter card and connect again.

5. It keeps disconnecting

• Push the adapter firmly into the port; a loose fit is the most common cause.
• Move your phone closer, and reduce other Bluetooth devices nearby if you can.
• Try a different, known-good adapter. If that also drops, the car's OBD2 port may need attention.

6. Your car limits third-party access

• Jeep, RAM, Dodge, Chrysler and Fiat from 2018 use a security gateway that blocks third-party scanners unless a bypass module is fitted at the port.
• Tesla doesn't provide standard OBD2 vehicle data.
• Volkswagen Group cars from 2020 and Mercedes-Benz from 2018 give standard engine data but block enhanced diagnostics.
• Older cars in some markets use protocols generic adapters can't read: US vehicles from 1996 are usually fine, but cars outside the US built before 2001 (petrol) or 2004 (diesel) may not be.

7. Some readings are missing

Odo shows only what your car reports. Each car declares its supported readings when you connect. A tile that shows a dash is supported but currently zero or unavailable; a reading that doesn't appear at all isn't offered by your car. If the VIN shows only partly, some older cars and basic clone chips can't assemble the longer reply, but live data, codes and readiness still work.

Still not working?

Email [email protected] with your car's make, model and year, your adapter, and the debug log from the Adapter tab in Garage → OBD II. That log shows exactly where the conversation with your car stopped.