On-Board Diagnostics (OBD-II) Design Information
OBD-II is used by scan tool or other hardware to communicate with a vehicle’s on-board computer through an OBD-II connector located under the dash. The information contained here provides information related to designing custom hardware and software to communicate with any OBD-II equipped vehicles, such as:
- OBD-II automotive standards
- Enhanced OBD-II (manufacturer specific)
- PIDs (Parameter IDs)
- Diagnostic Trouble Codes (DTC)
- Software design
- Software implementation
- Protocol implementation
- Legacy OBD-II protocols
- Hardware design
On-Board Diagnostics (OBD) II is a group of automotive diagnostic protocol standards used by a scan tool. OBD-II was mandated on most gas powered vehicles in 1996. The 16-pin OBD-II connector used to connect the scan tool is located inside the vehicle typically under the driver’s side dashboard.
European on-board diagnostics (EOBD) is essentially the same as the US-based OBD-II and was mandated in 2000 for gas powered vehicles and 2003 for diesel powered vehicles.
JOBD is OBD-II for vehicles sold in Japan.
A scan tool communicates with one or more vehicle computers to send and retrieve diagnostic data. The diagnostic data varies widely depending on the vehicle make, model and year. In general, newer vehicles provide more diagnostic data.
Common features on OBD II equipped vehicles include:
- Read diagnostics trouble codes
- Clear diagnostic trouble codes (DTCs)
- Turn off the check engine light
- Read live real-time sensor data
- Command on-board self-diagnostic tests (bi-directional commands)
- Read readiness monitors
Wikipedia provides an in-depth history of on-board diagnostics.
Auterra OBD-II OEM License
Do you have a product idea that requires communication using a vehicle's OBD-II diagnostic port? Need software source code and hardware schematics to get your project jumpstarted? If so, see the link below.
OBD-II Adapter Software Source Code
OBD-II Adapter Design