Does AutoScan Work With My Car? A Compatibility Guide
The short answer is three dates. European petrol vehicles from 2001, European diesel from 2004, and non-European vehicles from 1996. If your car falls after the relevant date it almost certainly supports OBD2 diagnostics, and AutoScan will talk to it through an ELM327 adapter on a Windows laptop. The longer answer is about what “works” means, because reading a fault code and accessing every module in the car are two different things.

Why those particular dates
They are not arbitrary and they are not AutoScan’s dates. They are when on-board diagnostics became a legal requirement in each market.
The United States mandated OBD2 for cars from the 1996 model year, which is why non-European vehicles built for export tend to follow that date. Europe introduced its own version, usually called EOBD, for petrol cars from 2001 and extended it to diesels from 2004. The requirement brought with it a standard connector, a standard set of requests, and a standard list of fault codes — which is precisely what makes generic diagnostic software possible.
| Vehicle | Supported from |
|---|---|
| European petrol | 2001 |
| European diesel | 2004 |
| Non-European (US, Japanese, Korean built to the US standard) | 1996 |
The awkward cases either side of the line
Two things happen around a mandate date.
Some manufacturers implemented the standard before they had to, so a late-1990s European car occasionally has full support. Others fitted the physical connector ahead of the deadline without implementing the full protocol behind it, which gives you the frustrating situation where the adapter powers up, the software finds the port, and the car simply does not answer. If you have a car built within a year or two either side of your market’s date, the only way to know is to try it.
Diesels are the more common source of confusion in the UK. A 2002 diesel is before the European diesel date even though a 2002 petrol of the same model is comfortably after the petrol one. Same car, same year, different answer.
The two-minute check
Look under the dashboard on the driver’s side for a trapezoidal 16-pin socket. If it is there, look at pin 6 and pin 14 — if those two positions have metal pins fitted, the car uses CAN, which effectively guarantees OBD2 support. A socket with those positions empty is likely to use one of the older protocols, which is fine but makes adapter choice matter more.
What generic OBD2 reaches, and what it does not
This is the part worth being precise about, because it is where expectations go wrong.
What is standardised across all makes
- Emissions-related fault codes from the engine and, on most cars, the transmission — stored, pending and permanent.
- Clearing those codes.
- Freeze frame data captured when a code was stored.
- Live sensor values from the engine control unit.
- Readiness monitor status.
- The vehicle identification number, on most cars.
What is manufacturer territory
Anything outside the emissions remit was never standardised. Body control modules, infotainment, comfort electronics, adaptive suspension, coding and adaptation, key programming, service interval resets on many cars — these use manufacturer-specific protocols that generic OBD2 does not define. Some are reachable with the right software, many are not without dealer-level equipment.
ABS and airbag modules sit in between. They are outside the generic OBD2 remit, but a lot of manufacturers expose them in a way that diagnostic software can read. AutoScan supports ABS and SRS from the Enhanced edition upward, which is the practical reason to step up from Standard if your warning light is not an engine light.
Petrol, diesel, hybrid and electric
Petrol and diesel are both fully covered, with the caveat about the different start dates. What differs is the data: a diesel has no lambda-based closed-loop fuelling in the way a petrol engine does, so the parameters worth watching are different — rail pressure, boost, EGR position, particulate filter differential pressure and regeneration status rather than lambda voltage and short-term fuel trim.
Hybrids have a conventional engine control unit and report engine fault codes normally. What you will not see through generic OBD2 is the high-voltage battery management system, which is manufacturer-specific on every hybrid.
Fully electric vehicles are the genuine gap. They still have an OBD2 socket, because the connector requirement remains, but the standardised OBD2 data set was designed around combustion engine emissions. There is very little of it that applies to a car with no engine, and almost everything interesting on an EV sits behind manufacturer-specific protocols. Generic diagnostic software is not the right tool for an electric car.
What you need on the computer side
AutoScan is Windows software. It needs a Windows PC or laptop, a free USB port for a wired ELM327 adapter, and enough battery to sit in the car for a while — or a power lead, if you are going to be watching live data through a long drive.
There is no Mac or Linux version. If your household is Mac-only, that is a genuine reason to look elsewhere rather than something to work around. The Enhanced PLUS edition adds Bluetooth adapter support and a mobile app, but the core application is a Windows program and it is honest to buy it on that basis.
Vans and light commercials
The same dates apply. A light commercial vehicle built to the relevant standard supports OBD2 in the same way a car does. Heavy commercial vehicles use different diagnostic standards entirely and are outside the scope of consumer OBD2 tools.
How to confirm it yourself before buying
The most reliable check is the physical one, and it costs nothing.
- Find the socket. It has to be within reach of the driver’s seat by regulation. Under the dash on the driver’s side is the usual place; also check behind small trim panels, in the centre console, the glovebox, or under an ashtray lid.
- Check the date. Your V5C registration document gives the date of first registration. Compare it with the table above, being careful to use the diesel date if it is a diesel.
- Look at the pins. Pin 4 and pin 5 are grounds, pin 16 is battery positive, and those three are always populated. Pins 6 and 14 populated means CAN. Pin 7 populated points at one of the ISO protocols. That tells you what your adapter needs to support.
- Plug in and see. The free download lets you install the software and confirm it launches and finds your adapter. It is a limited version — it will not read fault codes or show live data until licensed — so treat it as an installation and connection check, not a working trial.
What to do if the car does not answer
Before concluding your car is unsupported, rule out the ordinary causes. The ignition needs to be on. The OBD2 socket has its own fuse on many cars, and a blown one gives you a dead socket — on some models it takes out the cigarette lighter at the same time, which is a useful clue. And a cheap ELM327 clone that only implements CAN will find nothing at all on a car using an older protocol, which looks identical to an unsupported vehicle from the driver’s seat.
Testing the same adapter on a different car separates the two possibilities faster than anything else.
One licence, any number of cars
Worth knowing if you are weighing this up for a household rather than a single vehicle: the licence key is bought once, does not expire, and is not tied to a particular car. There is no per-vehicle charge and no subscription. What is time-limited is access to new update releases — one year with Standard, two with Enhanced, three with Enhanced PLUS — after which the software continues to work with the database you already have.
Check your car before you spend anything
Find the socket, check the date on your V5C, and if both look right, install the download and see whether the software finds your adapter.
Read it yourself
Stop guessing at the code
AutoScan reads the fault straight out of your car and tells you what it means in plain English, on your own Windows laptop. The trial reads real codes before you pay anything.
Keep reading
Related guides
AutoScan vs Other OBD2 Software: An Honest Comparison
Where AutoScan fits among free apps, brand-specific tools and handheld scanners, including a straight section on when you should buy something else…
Do You Need to Pay for OBD2 Software? Free vs Paid
Free OBD2 apps are genuinely good for some jobs and genuinely useless for others. A straight look at where the free tier…
Which ELM327 Adapter to Buy, and Why Cheap Ones Fail
Most OBD2 connection problems are the adapter, not the software. What the ELM327 chipset actually is, how the clones differ, and what…