WWH-OBD: the world harmonised standard replacing classic OBD-II

OBD-II was designed in the United States in the early 1990s, primarily around petrol passenger cars and a specific set of emissions concerns. Europe adopted a variant called EOBD, Japan another called JOBD, and heavy vehicles were largely outside the whole framework.

WWH-OBD — World Wide Harmonised On-Board Diagnostics — is the effort to unify all of that.

Related: OBD-II vs EOBD vs JOBD differences and OBD-II protocols explained.

What it changes

It is built on UDS

Classic OBD-II uses its own set of numbered modes: Mode 01 for live data, Mode 03 for codes, and so on.

WWH-OBD uses Unified Diagnostic Services, the same protocol manufacturers already use for their own deep diagnostics. That means one protocol for both the legislated data and the manufacturer data, rather than two.

UDS mode 22, what manufacturers hide.

Codes get longer

Classic DTCs are two bytes: P0420, U0100. WWH-OBD uses three-byte codes, where the third byte is a failure type — telling you not just which circuit but how it failed: short to ground, open circuit, signal implausible.

That is genuinely more informative. “P0420 with failure type: efficiency below threshold” carries more than “P0420”.

More data, more classes

WWH-OBD extends coverage to heavy-duty vehicles and adds data classes that classic OBD-II never defined.

More granular readiness

Rather than the classic fixed set of monitors, WWH-OBD reports readiness in a more detailed structure.

OBD readiness monitors explained.

What it means for a generic adapter

Here is the practical part, and it is worth being honest about.

Most vehicles still support classic OBD-II alongside anything newer. Manufacturers implement the legacy modes because inspection equipment worldwide expects them.

But the direction of travel is clear, and two related developments matter more day to day:

SAE J1979-2, OBDonUDS, which moves the legislated data onto UDS services. Some newer vehicles expose less through the classic modes as a result: SAE J1979-2 explained.

DoIP, diagnostics over Ethernet, which changes the physical connection for manufacturer-level access: DoIP explained.

The practical answer for owners

On the vast majority of vehicles on the road today, a Bluetooth Classic ELM327-class adapter reads codes, live data, freeze frame and readiness normally.

Where you will notice a difference:

• Very new vehicles may expose fewer parameters through classic modes.
• Some manufacturers have moved specific data to UDS-only access.
• Heavy vehicles have always had their own standards: truck OBD J1939.

Check the supported PID list on any unfamiliar vehicle — it tells you exactly what is available rather than leaving you to guess: supported PIDs and why parameters are missing.

The wider trend

Diagnostics is moving toward authenticated, manufacturer-controlled access. The reasons are partly security — a vehicle network reachable by anyone is reachable by attackers — and partly commercial.

Security gateway modules and OBD access, UN R155 and R156 vehicle cybersecurity and right to repair and diagnostic data access.

Whether the legislated minimum stays genuinely open is an ongoing policy question, and one worth following if you intend to keep diagnosing your own cars.

What to take away

1. Classic OBD-II still works on most of the fleet, and will for years.
2. The replacement is UDS-based, with longer, more descriptive codes.
3. Newer vehicles may expose less through the classic modes.
4. Check supported PIDs rather than assuming.

Pair an ELM327 adapter, open the free tier of the app and read the supported PID list on your vehicle. That list is the honest answer to what your car will and will not tell a generic tool.