Determining whether your vehicle is OBD2 (On-Board Diagnostics II) or EOBD (European On-Board Diagnostics) compliant is crucial for using automotive scan tools effectively. It’s important to understand that OBD-II and EOBD compliance is primarily determined by where the vehicle was originally sold and its model year, not necessarily where it was manufactured. This guide will help you understand compatibility and how to verify if your vehicle is OBD2 eobd compliant.
Understanding OBD-II and EOBD Compliance
OBD-II is a standard mandated in the United States for all cars and light trucks, model year 1996 and newer. This standardization was driven by environmental regulations to monitor vehicle emissions and ensure proper functioning of emission control systems. EOBD is the European equivalent of OBD-II, with similar objectives for emission control and diagnostics. While both systems are very similar and share many diagnostic protocols, understanding the nuances of compliance based on geographical markets is essential.
It’s vital to note that hybrid and electric vehicles, being low or zero emission vehicles, might not fully support or require OBD-II/EOBD in the same way as internal combustion engine vehicles. Always consult your vehicle manual or dealership for specific compatibility information regarding these vehicle types.
Vehicle Compatibility Chart: By Country of Sale and Model Year
The following chart provides a general guideline for OBD-II and EOBD compliance based on the country where your vehicle was initially sold. If your country is not listed, please refer to your vehicle’s owner’s manual or consult with a dealership to confirm compatibility.
Country of Sale | Model Years | Notes |
---|---|---|
United States | 1996 | |
European Union (Diesel) | Full OBD-II Compliance for 2007 and onward | Limited Compliance from 2004-06 |
European Union(Petrol) | Full OBD-II Compliance for 2002 and onward | Limited Compliance from 2001 |
Canada | 1998 | |
Algeria | 2014 | |
Argentina (Domestic) | 2008 | |
Argentina (Imports) | 2009 | |
Australia (Diesel) | 2007 | |
Australia (Petrol) | 2006 | |
Bahrain | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |
Brazil (Petrol) | Full OBD-II Compliance for 2007 and onward | Limited Compliance from 2005-06 |
Brazil (Diesel) | Full OBD-II Compliance for 2015 and onward | Limited Compliance from 2013-14 |
Chile (Diesel) | 2013 | |
Chile (Petrol) | 2014 | |
China (Beijing – Petrol) | 2008 | |
China (Country – Diesel) | 2011 | |
China (Country – Petrol) | 2010 | |
Costa Rica | Limited Compliance from 2017 onward | |
Hong Kong | 2006 | |
India | Full OBD-II Compliance for 2017 and onward | Limited Compliance from 2013-16 |
Iran | 2012 | |
Israel | 2003 | |
Japan | Full OBD-II Compliance for 2008 and onward | Limited Compliance from 2003-07 |
Kuwait | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |
Mexico | 2007 | |
Morocco | 2010 | |
New Zealand (Diesel) | 2007 | |
New Zealand (Petrol) | 2006 | |
Nigeria | 2015 | |
Oman | Full OBD-II compliance for 2018 and onward | Limited Compliance from 2017-18 |
Peru | 2003 | |
Peru | 2017 | |
Philippines | 2016 | |
Qatar | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |
Russia | Full OBD-II Compliance for 2012 and onward | Limited Compliance from 2010-11 |
Saudi Arabia | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |
Singapore | 2014 | |
South Korea | Full OBD-II Compliance for 2010 and onward | Limited Compliance from 2005-09 |
Taiwan | 2008 | |
Thailand | 2013 | |
Turkey | 2013 | |
United Arab Emirates | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |
Vietnam | 2017 | |
Yemen | Full OBD-II Compliance for 2018 and onward | Limited Compliance from 2017-18 |


This table offers a quick reference, but let’s delve into more detail for key regions.
OBD2 Compliance in the United States
In the United States, the Environmental Protection Agency (EPA) mandated OBD-II compliance for all cars and light trucks starting from model year 1996. This means if your vehicle was sold new in the US and is a 1996 model year or newer, it is highly likely to be OBD-II compliant. You can find more information on the EPA’s website.
OBD-II compliant vehicles in the US encompass a wide range of makes and models, including vehicles from manufacturers such as: Acura, BMW, Chevrolet, Ford, Honda, Toyota, and many more.
EOBD Compliance in the European Union
The European Union introduced EOBD regulations in stages. For gasoline (petrol) vehicles, mandatory EOBD compliance began on January 1, 2001, for all new types and January 1, 2002, for all types of passenger cars (category M1) and light commercial vehicles (category N1 class I) not exceeding 2500 kg.
For diesel vehicles in the EU, EOBD compliance became mandatory from January 1, 2003, for new types and January 1, 2004, for all types within the same vehicle categories (M1 excluding vehicles designed to carry more than six occupants or exceeding 2500 kg, and N1 class I).
It’s important to note that “European Union” in these directives refers to the member states at the time of implementation (early 2000s). Full OBD-II compliance (EOBD) for diesel vehicles in the EU was more comprehensively enforced from 2007 onwards.
Determining OBD2 EOBD Compliance Beyond the Chart
If your vehicle’s origin or model year is not clearly defined in the chart, or for further verification, you can physically check your vehicle for an emission control information label. This label is typically found under the hood, often on the underside of the hood itself or on the engine compartment’s firewall.
Fig. 1 – Vehicle Emission Control Information Label
This label (Fig. 1) may explicitly state that the vehicle is designed to comply with OBD II, EOBD, or JOBD (Japanese OBD) legislation. In this context, OBD-II is often used as a general term encompassing these various standards.
Consulting your vehicle’s owner’s manual can also provide information about OBD-II or EOBD compliance. While dealerships might be able to assist, be aware that not all service personnel may be fully informed about the nuances between OBD and OBD-II/EOBD.
If your vehicle is not OBD-II or EOBD compliant, generic OBD-II scan tools may not function correctly or provide accurate diagnostic information.
The 16-Pin OBD Connector: Not a Guarantee of Compliance
Many vehicles, especially from European and Asian manufacturers, adopted the 16-pin Diagnostic Link Connector (DLC) long before implementing full OBD-II or EOBD systems. Therefore, the presence of a 16-pin connector does not automatically mean your vehicle is OBD2 eobd compliant.
A subtle but sometimes noticeable difference can be found in the DLC shape itself. Non-EOBD compliant vehicles may have a DLC that does not fully conform to the SAE J1979 standard, exhibiting slight variations in shape.
For example, comparing the DLC of a non-EOBD compliant Ford Escort (Fig. 2) with a standard J1962 Type A connector (Fig. 3) reveals these subtle differences, particularly in the “ears” of the connector.
Fig. 2 – Ford Escort DLC (non-EOBD compliant)
Fig. 3 – J1962 Vehicle Connector, Type A (OBD2/EOBD compliant)
These visual cues, while not definitive, can sometimes offer hints about potential non-compliance.
Conclusion: Verifying OBD2 EOBD Compliance for Effective Diagnostics
Understanding OBD2 eobd compliance is essential for anyone using scan tools for vehicle diagnostics. While the compatibility chart provides a solid starting point, always verify compliance through the emission control label, owner’s manual, and by understanding that the 16-pin connector is not a foolproof indicator. By taking these steps, you can ensure you are using your OBD-II or EOBD scan tool on a compatible vehicle, leading to accurate and reliable diagnostic results.