OBDonUDS · Vehicle compatibility

Newer car.
OBDAI is ready.

OBDonUDS support for newer vehicles. ARIA to explain what the evidence means. Get both with OBDAI PRO + GEN2.

Get PRO + GEN2 →See supported standards ↓

OBDonUDS requires OBDAI 2.7 or later, PRO, and the OBDAI GEN2 adapter. Coverage and available data depend on the vehicle. Classic OBD-II remains supported.

Two generations. One ARIA.

From familiar OBD-II vehicles to the newer OBDonUDS standard, choose the connection your vehicle uses.

OBDonUDS
SAE J1979-2 · PRO + GEN2
The newer standardized diagnostic path already used by some late-model vehicles. Read faults, readiness, live data and supporting evidence where the vehicle provides them.
Classic OBD-II
SAE J1979-1
The established standard across decades of vehicles. Use OBDAI GEN1, GEN2, or a supported third-party adapter.
EOBD & regional equivalents
Standardized emissions diagnostics
Coverage follows the vehicle’s original-market specification. See regional guidance below for common starting years.
JOBD / Japanese imports
Partial support
Connection does not guarantee complete sensor data or readiness. Check the vehicle’s implementation before choosing hardware.

Need the details?

Check regional coverage, available data, or the adapter you already own.

Regional coverage and model years

Region	Standard	Gasoline/Petrol	Diesel	Notes
United States	OBD-II (SAE J1979-1 / J1979-2)	1996+	1996+	Standardized OBD is required from 1996 onward. Most vehicles use J1979-1; some 2023–2026 transition vehicles use J1979-2 OBDonUDS. OBDonUDS requires OBD BLE GEN2 and PRO.
Canada	OBD-II (SAE J1979)	1998+ (most 1996-97 work)	1998+	1998+ follows standardized OBD requirements; many 1996–1997 vehicles also work. Exact late-model protocol support depends on the vehicle specification and adapter.
European Union / UK	EOBD	2001+ petrol	2004+ diesel	Standardized EOBD applies from 2001 for petrol and 2004 for diesel; earlier vehicles and market-specific implementations may provide partial coverage.
Australia	ADR 79/01 (OBD-II equivalent)	2006+	2007+	OBD-II-style diagnostics mandatory from 2006 (petrol) and 2007 (diesel).
Russia & Eastern Europe	EOBD / OBD-II	~2001+ petrol	~2004+ diesel	Most modern vehicles follow Euro EOBD standards.
Japan (Domestic)	JOBD	Early 2000s+	Early 2000s+	Partial support only — see notes below.
South Africa	Mixed EU/US spec	2001+ (EU spec)	2004+ (EU spec)	Coverage depends on whether vehicle was built to EU or US standards.
Latin America	Mostly US/EU spec	1996+ (US) or 2001+ (EU)	1996+ (US) or 2004+ (EU)	Locally built non-OBD vehicles may have limited functionality.
Middle East	US/EU import specs	Varies by import origin	Varies by import origin	Compatibility follows the vehicle’s original-market standard, gateway, and implementation.

Model-year guidance is not a guarantee for every vehicle or adapter. Original market, protocol and implementation matter.

What ARIA can read and explain

Classic OBD-II — SAE J1979-1

OBDAI reads the standardized evidence your vehicle already provides and carries it into the same ARIA workflow:

Trouble Codes — confirmed, pending, and permanent emissions-related DTCs
Freeze Frames — the operating conditions captured when the fault set
I/M Readiness — monitor status for inspection and repair verification
Live Data — current sensor values, graphing, recording, and cross-drive evidence
Monitor Tests — the vehicle’s own measured test results and pass/fail limits
Vehicle Information — VIN, calibration IDs, CVNs, ECU identities, and standardized counters

Next-Generation OBD-II — SAE J1979-2 OBDonUDS GEN2

OBDonUDS carries that standardized diagnostic mission through UDS services and data identifiers—and adds evidence the classic workflow never had:

Automatic J1979-1 / J1979-2 detection when a late-model vehicle does not answer the legacy request
Standardized UDS DTC workflows for confirmed, pending, and permanent faults
Extended fault records and multiple snapshots that preserve more context around a failure
DTC-level readiness groups that help ARIA explain what is preventing a monitor from completing
Monitor tests, vehicle information, live parameters, and multi-ECU evidence through the new path

Same ARIA. More modern conversation. The protocol changes underneath; the technician still gets evidence, reasoning, and a professional result.

Standardized emissions diagnostics are not universal access to manufacturer-specific modules or service functions.

Adapters, platforms and edge cases

Choose GEN2 for OBDonUDS

OBDAI GEN2 works with iOS, Android and Windows. Pair it with PRO and OBDAI 2.7 or later for OBDonUDS on supported vehicles. GEN1 and supported third-party adapters remain options for classic OBD-II; they do not provide the supported OBDonUDS path.

OBDAI can use several tested ELM327-based adapters for the classic J1979-1 path. These devices do not qualify for OBDonUDS:

Device	Connection	Platforms	Status
Vgate iCar Pro BLE 4.0	Bluetooth LE	iOS, Android, Windows	✓ Tested
VEEPEAK OBDCheck BLE+	Bluetooth LE	iOS, Android, Windows	✓ Tested

Important: Third-party adapters and OBD BLE GEN1 remain useful for classic J1979-1 diagnostics, but OBDonUDS requires OBD BLE GEN2. Adapter speed, firmware, cloning, and protocol handling can also limit otherwise compatible vehicles.

Platform Support

Connection Methods by Platform

Platform	Supported Connections
Android	Bluetooth LE (4.0+), Classic Bluetooth, WiFi
iOS	Bluetooth LE (4.0+), WiFi, MFi-certified adapters
Windows	Bluetooth LE (4.0+), Classic Bluetooth, WiFi, USB Serial

Edge Cases

Partial Support & Edge Cases

What "Partial Support" Means

Some vehicles connect to OBDAI but may not provide complete diagnostic data:

Late-Model OBDonUDS Vehicles

Some 2023–2026 vehicles already use SAE J1979-2 instead of answering the legacy standardized request. A legacy-only adapter may connect electrically and still produce a no-communication result. OBDAI PRO and OBD BLE GEN2 are required for OBDonUDS support.

Japanese Domestic Market (JDM) Vehicles

Japan uses JOBD, which is conceptually similar to OBD-II but doesn't guarantee the same PID (parameter ID) coverage. If you have a gray-market Japanese import, expect:

Basic connection and some trouble code reading
Incomplete or missing live sensor data
Readiness monitor status may not be available

Pre-OBD2 Vehicles

Vehicles manufactured before OBD2 requirements (pre-1996 US, pre-2001 EU petrol, pre-2004 EU diesel) may have:

Proprietary diagnostic protocols
No standardized trouble codes
Limited or no J1979 data

Locally-Built Non-OBD Vehicles

Some vehicles built for local markets (particularly in developing regions) may not include full OBD2 compliance, even on recent models.

Not sure about your vehicle? Ask us before you buy. Or read why the standard is changing.

Newer car.OBDAI is ready.