OBD-II is the diagnostic interface that lets scan tools communicate with a vehicle's onboard control systems.
Where the OBD-II port is
The OBD-II connector is usually under the dashboard near the driver's side. A scan tool plugs into this port to request standardized diagnostic information from the vehicle.
Exact location can vary by model, and some vehicles also expose manufacturer-specific data that basic scan tools cannot fully interpret.
What OBD-II can read
OBD-II can read many diagnostic trouble codes, emissions readiness monitors, basic sensor values and vehicle data used for inspection and maintenance.
It is especially associated with the check-engine light, but modern vehicles may have many systems that also store proprietary codes outside generic OBD-II access.
OBD-II on hybrids and EVs
Hybrids and EVs can still use the OBD-II connector for diagnostics, but battery, charging and high-voltage data may require manufacturer-specific tools or enhanced scan-tool support.
Do not assume every app or Bluetooth dongle can read the same information from every vehicle.
What OBD-II cannot tell you
OBD-II data is a starting point, not a complete diagnosis. A code can identify a system or circuit, but the root cause may be wiring, software, sensor behavior, a mechanical issue or a related system.
Practical owner notes
- Cheap code readers can help identify basic check-engine codes.
- Clearing a code without fixing the cause can hide symptoms temporarily.
- Readiness monitors may need drive cycles before an emissions test.
- ADAS, TPMS and body-system codes may need enhanced scan tools.
Related terms
Sources
- eCFR - 40 CFR 86.1806-17 Onboard diagnostics
- California Air Resources Board - OBD program
- SAE J1962 - Diagnostic connector standard
Feature names, connector support, diagnostic behavior and EV specifications can vary by model year, trim, software version and market. Always verify the exact vehicle documentation before buying, repairing or relying on a feature.