Stahlcar diagnostic guide
What is OBD2?
The standard that lets a scan tool read engine and emissions fault information from most modern vehicles.
OBD2 is useful, but it is often misunderstood. A vehicle can have the familiar 16-pin socket without giving a basic code reader access to ABS, airbags, transmission or every other control module.
In plain language
OBD2 gives vehicles and scan tools a common way to communicate.
When the engine computer detects a problem that can affect engine operation or emissions, it stores a Diagnostic Trouble Code, usually shortened to DTC. An OBD2 reader plugs into the vehicle and asks the computer for that information.
This can help identify why the check-engine light is on, show live engine data and clear supported codes after a fault has been repaired.
Before OBD2, manufacturers used a mixture of their own connectors, codes and communication systems. Those earlier systems are commonly grouped together under the name OBD1.
The important distinction
OBD2 access and full vehicle diagnostics are not the same thing.
This is the part that causes most scan-tool buying mistakes.
Engine and emissions information
A normal OBD2 code reader is intended for standardised engine-related diagnostics.
- Check-engine fault codes
- Supported live engine data
- Readiness monitor information
- Clearing supported engine codes
Manufacturer-level vehicle systems
A single-make or all-makes scanner can communicate with additional modules when supported.
- ABS and airbag systems
- Transmission and body modules
- Service and relearn functions
- Supported active tests and coding
A 16-pin socket does not prove full compatibility. Some older vehicles use the same style of connector with manufacturer-specific communication, and even a fully OBD2-compliant car will not give a basic reader access to every system.
The New Zealand reality
Compatibility depends on the vehicle's market, not just its model year.
New Zealand has a mixed vehicle fleet, including NZ-new cars, Japanese imports, Australian-market models and European vehicles. Advice written for a US-market vehicle may not apply to the version sold here.
Use 2006 onward as the safer general starting point
For generic OBD2 reader compatibility in New Zealand, later vehicles are much more consistent. Earlier vehicles need closer checking.
Japanese imports can vary
The make, model, engine, year and original market can all affect whether a generic OBD2 reader will communicate.
The connector shape is not enough
Some pre-OBD2 vehicles have a 16-pin socket but still use manufacturer-specific diagnostic protocols.
Check the job as well as the vehicle
A car may work perfectly with an OBD2 reader for engine codes but still require a different scanner for ABS, airbags or service functions.
Quick compatibility reference
Typical OBD2 starting dates.
These are useful first-check dates based on the standards and the vehicles commonly seen in New Zealand. They are a guide rather than a guarantee, especially for Japanese imports and earlier Australian-market vehicles.
American vehicles
1996 onwardUS-market passenger vehicles generally adopted OBD2 from the 1996 model year.
European vehicles
Petrol 2001Diesel 2004
European-market vehicles generally use the related EOBD standard from these dates.
Australian vehicles
Around 2006 onwardCompatibility becomes far more consistent from about 2006, although earlier Holden and Ford models can vary by engine and model.
Common Japanese and Korean starting points
Useful rough dates for vehicles and imports frequently encountered in New Zealand.
Diesel from about 2008
More consistent from 2008
Important: An earlier model may still work, and a later import can still differ. The vehicle's engine, original market and the system you want to diagnose all matter.
OBD1 compared with OBD2
The change was standardisation.
OBD2 did not make every vehicle identical. It created a common minimum standard for engine and emissions diagnostics.
Earlier systems
OBD1
A broad name for manufacturer-specific diagnostic systems used before OBD2 became widespread. Plugs, procedures and code formats varied heavily between brands and models.
Standardised diagnostics
OBD2
A common 16-pin connector and standardised engine or emissions information that compatible scan tools can access across many different vehicle makes.
Diagnostic Trouble Codes
What does an OBD2 code mean?
A code such as P0301 is a clue recorded by the vehicle computer. It identifies the area in which a fault was detected, but it does not automatically tell you which part to replace.
The code needs to be considered alongside symptoms, live data and proper testing. Clearing a code removes the stored information; it does not repair the cause.
A little more technical
What are OBD2 protocols?
Protocols are the communication methods used between the vehicle and the scan tool. You may see names such as CAN, ISO 9141-2, KWP2000 or J1850 in product specifications.
Most current multi-protocol OBD2 readers handle the common standards automatically, so the average buyer does not need to select a tool by protocol alone.
Common questions
What OBD2 does and does not mean.
Will any OBD2 reader work on any car?
No. Compatibility depends on the vehicle's year, market and protocol. Earlier vehicles and imports are the most likely to need checking.
Can OBD2 read ABS and airbag codes?
Generic OBD2 access is engine and emissions focused. ABS, airbags and other modules usually require a full-system scanner with suitable vehicle coverage.
Does clearing a code fix the problem?
No. It only clears the stored code and warning light. If the fault remains, the code will normally return.
Choosing a scan tool
Need engine codes only, or access to more of the vehicle?
Start with the scan-tool guide or use the Product Selector to narrow the range by vehicle, systems and the jobs you need to carry out.