OBD-I: why a very old car will not connect at all
The adapter is plugged in, the app is open, and there is no link — and it is not the adapter's fault. Cars older than a certain age simply do not have the protocol the app can read.
OBD-II is a single standard, mandatory for cars newer than a particular model year (covered in broad terms in what OBD-II actually is). Before that standard there was OBD-I — or more precisely, every manufacturer had its own version of diagnostics, not agreed with anyone else's.
What actually differs about OBD-I
- Its own connector. Not the 16-pin trapezoid, but whatever the maker chose — often not even under the wheel, but under the bonnet.
- Its own protocol. Even if you can physically plug an adapter in, the car «speaks» a language a standard OBD-II adapter does not understand.
- Its own codes. Even where something does read, the code numbers do not match the familiar P0xxx — it is a different, manufacturer-specific numbering system.
The practical upshot: an ordinary OBD-II adapter and an ordinary OBD-II app simply cannot work with such a car, and that is not a fault of the adapter, the phone or the app.
How to tell this is actually the reason
Before going further, rule out the ordinary causes of «silence» that show up on newer cars too: is the ignition on, is the adapter running unusually hot, is it the right connector. The order is covered in ELM327 will not connect — if none of that fits and the car is noticeably old, age is the likely cause.
What to do if the car really predates the standard
Our app and this site are built specifically for OBD-II — for older cars, diagnostics goes through the manufacturer's own proprietary tool or through workshops that specialise in such cars. That is an honest limit, not a reason to suggest something that will not work.
To see what the app's screen looks like at all, without a real car, there is a demo mode on a made-up vehicle — so you can see the interface in advance, before deciding what to do with your particular car.
