Vehicle compatibility · More evidence for ARIA
Newer car.
OBDAI is ready.
Standard OBD-II, OBDonUDS and manufacturer-specific data in one ARIA-led diagnostic workflow. Connect wirelessly with GEN2 and Pro, or use your J2534 interface on Windows with Ultra.
Use the current OBDAI app. OBDonUDS requires a compatible vehicle and either GEN2 with PRO or Ultra, or a compatible Windows J2534 interface with Ultra. Coverage and available data depend on the vehicle and interface. Classic OBD-II remains supported.
Three generations. One ARIA.
From classic OBD-II and newer OBDonUDS to manufacturer-specific data, give ARIA the evidence your vehicle can provide.
Manufacturer-specific data
NEW Pro + GEN2 · Ultra + J2534ARIA goes past the engine computer into modules like body control, brakes, airbags, power steering, parking aid, trailer brake, transfer case, climate, seats and EV battery. Available modules and readings vary by vehicle and adapter type.
Growing production library: 67,000+ parameter entries across 1,600+ make/model/year combinations and 300+ models.
Catalog totals, not readings available on one car. The same signal in two modules counts twice.
OBDonUDS
SAE J1979-2 · GEN2 + PRO, or Windows J2534 + UltraThe 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-1The established standard across decades of vehicles. Use OBDAI GEN1, GEN2, or a compatible J2534 interface on Windows with Ultra.
EOBD & regional equivalents
Standardized emissions diagnosticsCoverage follows the vehicle’s original-market specification. See regional guidance below for common starting years.
JOBD / Japanese imports
Partial supportConnection 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
Standardized emissions diagnostics are not universal access to manufacturer-specific modules or service functions.
Choose your connection: GEN1, GEN2 or J2534
GEN1: classic OBD-II
Use OBDAI GEN1 for classic OBD-II diagnostics: live readings, trouble codes, readiness and recorded data for ARIA to investigate. GEN1 does not provide the supported OBDonUDS connection.
GEN2: wireless diagnostics and manufacturer-specific data
OBDAI GEN2 works with iOS, Android and Windows. It supports classic OBD-II, plus OBDonUDS and supported manufacturer-specific data with Pro or Ultra. Choose GEN2 for wireless work on your phone, tablet or Windows PC.
J2534: use your existing interface on Windows
OBDAI Ultra lets you use a compatible J2534 pass-through interface with the Windows app. Install the interface manufacturer’s Windows J2534 driver, then select J2534 in OBDAI. OBDAI implements J2534 04.04 and 05.00 and supports classic OBD-II, OBDonUDS and manufacturer-specific data through this connection, where supported by the vehicle and interface.
Ultra includes a GEN2 wireless adapter; bring your own J2534 interface and Windows PC. J2534 support provides diagnostics and ARIA analysis. Module programming and reflashing use your OEM programming software.
See J2534 interface examples and Ultra details →
Set up your J2534 connection →
Available readings and functions depend on the vehicle, interface and plan. A connection does not guarantee access to every manufacturer-specific module or service function.
Not sure about your vehicle? Ask us before you buy. Or read why the standard is changing.