# OBD1 vs OBD2: reference scope

Source: https://obdlens.com/compare/obd1-vs-obd2/
Last built: 941ad311c197960f285f

[Diagnostic knowledge](https://obdlens.com/knowledge/)

OBD Lens publishes generic OBD2 and manufacturer reference families. Use the reference namespace and vehicle profile to establish the scope of a definition.

| Reference | What OBD Lens publishes |
| --- | --- |
| OBD-I | No separate OBD-I reference directory is published here. |
| OBD-II | [Generic OBD2 definitions](https://obdlens.com/knowledge/?kind=codes&namespace=obd2) |
| Manufacturer references | [Separate reference families and vehicle relationships](https://obdlens.com/brands/) |

[P0420](https://obdlens.com/codes/p0420/) · [P0430](https://obdlens.com/codes/p0430/) · [P0135](https://obdlens.com/codes/p0135/) · [P0141](https://obdlens.com/codes/p0141/) · [Brand references](https://obdlens.com/brands/) · [Pending, stored and permanent codes](https://obdlens.com/knowledge/pending-stored-permanent-codes/)

## What is the scope of OBD Lens?

OBD-II and enhanced manufacturer references.

## Where are generic OBD2 definitions?

The knowledge search provides a generic OBD2 namespace filter.

## Does a reference family prove applicability?

Reference-family membership is not proof that a code applies to every listed ECU or vehicle. Runtime-ready definitions are not physical-vehicle validation. Unavailable readings must not be treated as zero. App and hardware sale availability must be checked separately.

Reference-family membership is not proof that a code applies to every listed ECU or vehicle. Runtime-ready definitions are not physical-vehicle validation. Unavailable readings must not be treated as zero. App and hardware sale availability must be checked separately.

---

Reference-family membership is not proof that a code applies to every listed ECU or vehicle. Runtime-ready definitions are not physical-vehicle validation. Unavailable readings must not be treated as zero. App and hardware sale availability must be checked separately.