The Connector Still Fits. The Protocol Changed.

OBDAI supports nearly three decades of classic OBD-II—and OBD BLE GEN2 is built for the SAE J1979-2 OBDonUDS transition already reaching late-model vehicles.

Vehicle Compatibility

The New Compatibility Question

Does your adapter speak the standardized protocol the vehicle actually uses?

For most of the OBD-II fleet, the answer is the familiar SAE J1979-1 path—the standardized emissions-diagnostic language mechanics have relied on for decades.

But some 2023–2026 vehicles already use SAE J1979-2 OBDonUDS instead. The connector looks the same. The adapter may power up. Yet a legacy-only tool can ask the old question and receive nothing useful back.

OBDAI has implemented both generations of the standardized conversation. Classic vehicles continue through J1979-1. OBDonUDS requires OBD BLE GEN2 and rolls out first to qualifying GEN2 PRO customers: field beta in September 2026, followed quickly by the full PRO release. Qualifying GEN2 Premium customers receive OBDonUDS in 2027.

The business question is no longer just “Does the car have an OBD-II port?”
It is “Can my hardware ask the question this vehicle expects?”

See Which New Cars Changed →Watch OBDonUDS Work →

Global Coverage

Worldwide Standards Coverage

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 a qualifying rollout tier.
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.

Standards dates describe what the vehicle is required to expose—not a guarantee that every adapter can speak every generation. OBD BLE GEN2 is the required OBDAI hardware for J1979-2 OBDonUDS.

Diagnostic Data

TWO GENERATIONS. ONE ARIA WORKFLOW.

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.

Choose Your Hardware

THE PROTOCOL LIVES IN THE ADAPTER

For the widest standardized coverage, choose the adapter built for the fleet transition.

OBD BLE GEN2 — Required for OBDonUDS

Supports the classic SAE J1979-1 fleet
Required for the SAE J1979-2 OBDonUDS path
Bluetooth Low Energy for iOS, Android, and Windows
Built for ARIA’s evidence collection, continuous monitoring, and staged OBDonUDS rollout

GEN2 PRO goes first: field beta launches September 2026 and the full PRO release follows quickly. Qualifying GEN2 Premium customers receive OBDonUDS in 2027.

Two deadlines. Two reasons to act.

September 30: Already purchased? Redeem your qualifying GEN2 Premium or PRO licence to enter the activated cohort. New GEN2 PRO customers must also purchase and redeem by then to be considered for the field beta.

October 31: Purchase an eligible GEN2 Premium or PRO package at current pricing and qualify for the included update when your tier reaches rollout. The offer may be extended.

Choose GEN2 + PRO →Choose GEN2 + Premium →Already Bought? Redeem →

OBDAI GEN1 — Classic OBD-II Coverage

Reliable BLE hardware for SAE J1979-1 vehicles
Works with iOS, Android, and Windows
Does not provide OBDonUDS support

GEN1 and GEN2 no longer have the same protocol coverage. If late-model compatibility matters to your work, GEN2 is the future-proof choice.

Existing Adapters

What Your Current Adapter Can—and Cannot—Do

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. OBD BLE GEN2 is required for OBDAI’s OBDonUDS rollout.

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.

Summary

The Bottom Line

The port tells you standardized diagnostics should be available. The protocol and adapter determine whether your tool can reach them.

OBDAI supports the classic standardized fleet today. Choose OBD BLE GEN2 for the new OBDonUDS path and the widest late-model coverage as the transition reaches independent shops.

See eligibility, rollout timing, and current-price deadlines →

The Connector Still Fits. The Protocol Changed.

Vehicle Compatibility

The New Compatibility Question

Does your adapter speak the standardized protocol the vehicle actually uses?

Global Coverage

Worldwide Standards Coverage

GM (Chevrolet, GMC, Cadillac, Buick)

Mercedes-Benz

Toyota/Lexus

Volkswagen/Audi

Honda/Acura

Ford/Lincoln

Hyundai/Kia

BMW

Nissan/Infiniti

Stellantis (Chrysler, Dodge, Jeep, RAM)

Mazda

Subaru