ELM327 will not connect: a checklist in order
Nine causes, most common first. Eight of them are fixed without buying another adapter.
"The adapter will not connect" is really three different problems: the phone does not see the adapter, the phone sees it but will not pair, or the link is up and the car stays silent. Here they are in order, most common first.
1. The ignition is off
The OBD-II socket is not always live. On most cars the adapter only wakes up with the ignition on — the engine need not be running, but the key must be in the ignition position. If no light shows on the adapter at all, start here.
2. The adapter is not fully seated
The socket is stiff, and in the dark under the dashboard it is easy to decide it is in. The sign is a light that blinks and dies when you touch it. Push until it clicks.
3. Classic Bluetooth instead of BLE (or the other way round)
This is the most common cause among people who "did everything right".
- Bluetooth 2.x (classic) must first be paired in the phone settings, usually with PIN
1234or0000, and only then opened in the app. - BLE (Bluetooth 4.0 and newer), on the contrary, must not be paired in settings: it is found from inside the app. Look for it in the phone's Bluetooth list and you will not find it at all.
4. Wi-Fi adapter: the phone went back to mobile data
A Wi-Fi adapter creates its own network (usually WiFi_OBDII or V-LINK, at 192.168.0.10, port 35000). The phone notices there is no internet on it and quietly switches back to mobile data. Turn off "switch to mobile data" for that network.
5. The adapter is busy with another phone
An ELM327 holds one connection. A tablet left in the glovebox and paired to the same adapter is a perfectly good reason for "it will not connect".
6. The adapter has locked up
Cheap adapters hang, especially after living in the socket for days. Pull it out, wait ten seconds, plug it back in — not a joke, but a working move.
7. A weak battery
Below roughly 11.5 V control units start behaving oddly: the adapter connects and the car does not answer. Check the voltage — if the app got that far, it is the first thing to look at.
8. A clone with a reduced command set
The link works, codes are read, but service operations fail or some readings stay empty. That is not a fault — it is a cheap copy where part of the command set was never implemented.
9. The car does not speak OBD-II
The same-shaped socket is fitted to cars that do not use the protocol: petrol cars before 2001 in Europe, diesels before 2004, plus particular markets and models. The socket is there, the protocol is not.
If nothing helped
Before buying another adapter, try it on a different car, or with a different phone. It takes thirty seconds and splits every possible cause exactly in half: the adapter or the car.
