Some links on this page are affiliate links. If you buy through them, OBD Dynamics may earn a commission at no extra cost to you. It helps keep the lights on and the advice honest.
“Will it work on my car?” is the question we are asked most, and it deserves a proper answer rather than a yes. The honest answer has two parts, because the port on your dashboard guarantees far less than most people assume.
What the port itself guarantees
The standard sixteen-pin diagnostic connector is a physical and electrical standard. If a vehicle has one, a compliant tool can plug in and, in principle, talk to it. The connector is normally within reach of the driver’s seat — under the dash, near the steering column, sometimes behind a small panel or inside the fusebox cover. If you cannot find it, it is almost always hiding behind a trim piece rather than absent.
Generic versus manufacturer-level
This is the distinction that matters, and it is where expectations go wrong.
- Generic OBD2 is the standardised layer. It covers emissions-related engine data: generic fault codes, freeze frame, live sensor data and readiness monitors. Any compliant tool can read this on any compliant vehicle.
- Manufacturer-level diagnostics is everything else — ABS, airbag, transmission, body modules, climate, immobiliser, plus manufacturer-specific codes and all the service and coding functions. None of this is standardised. Each manufacturer implements it their own way, and a tool can only access it if its software specifically supports that make.
So a cheap reader will show an engine code on almost anything with the port. It will not touch your ABS light. That is not a fault in the tool; it is the boundary of the standard.
Protocols under the connector
Behind the same physical plug sit several different communication protocols, used across different eras and manufacturers — the various ISO and SAE standards, and CAN on more recent vehicles. A good tool handles all of them automatically and you never think about it. A very cheap adapter may support only some, which is exactly how people end up with a tool that connects to one car in the family and not the other.
Why South Africa needs extra care
Our vehicle parc is unusually varied, and that has practical consequences for coverage.
- Grey and used imports. A vehicle brought in from another market may run software, and occasionally an entire electrical architecture, that differs from the model sold locally under the same name. Tool coverage lists are usually organised by market.
- Japanese domestic market vehicles in particular can require specific software support, and a badge that looks familiar is not a guarantee.
- Older bakkies and commercial vehicles stay in service here far longer than in many markets. Some pre-date full standardisation, and some use manufacturer connectors and protocols requiring an adapter.
- Heavy vehicles and light commercials often use different diagnostic standards to passenger cars entirely.
- Model years differ by market. A feature introduced in Europe in one year may have arrived here later, or not at all.
How to check properly before you buy
- Get the full vehicle details: make, model, exact year, engine and where the vehicle was originally sold. The VIN is the definitive answer and is worth quoting.
- Look at the tool’s coverage list for that specific combination, not just the make.
- Check coverage per function, not just per vehicle. A tool may support your car for engine and ABS but not for the one service function you actually bought it for.
- Ask specifically about the job you need done — electronic parking brake retraction, battery registration, injector coding, steering angle calibration. These are the functions people assume are included and discover are not.
- Ask whether coverage improves with updates, since newer vehicles are added over time.
If a tool will not connect
- Check the ignition position. Most tools need ignition on, engine off, and some need the engine running.
- Check the fuse. The diagnostic port is fused, and a blown fuse is a very common and very simple cause of “no communication”.
- Check the battery. A weak battery causes communication faults that look like tool faults.
- Check the connector itself for bent or pushed-back pins, which happens after a previous tool was removed carelessly.
- Try another vehicle. If it connects there, the tool is fine and the problem is on the car.
If you are unsure whether a tool covers what you need, send us the vehicle details and the functions you want to perform and we will check the coverage before you buy rather than after. Please make sure you are on our official website when you send an enquiry.
Tools mentioned in this guide
Brand-specific tools go deeper than generic OBD2. Check the coverage list for your exact car, or ask us first.
OBDeleven Bluetooth diagnostics
Best for: VW, Audi, Skoda, SEAT, BMW and Toyota owners who want app-based coding
A Bluetooth dongle and phone app with one-click coding apps for supported brands.
- Phone app (Android and iOS)
- One-click apps for common coding changes
- Full scans on supported makes