Works With Your Vehicle

OBDAI connects to any OBD2-compliant vehicle worldwide. That’s nearly three decades of cars, trucks, and SUVs from every major manufacturer.

Vehicle Compatibility

The Simple Truth

If your vehicle has an OBD2 port, OBDAI works with it (mostly)

In the United States, that means every gasoline and diesel car, truck, and SUV from 1996 to today. No compatibility guessing. No model-specific limitations. No “check if your car is on our list” anxiety.

OBDAI is built around the SAE J1979 / OBD-II standard — the universal diagnostic language that every compliant vehicle speaks. Whether you drive a Ford F-150, a BMW 3 Series, a Toyota Camry, or a Jeep Wrangler, ARIA connects and diagnoses.

Global Coverage

Worldwide OBD2 Coverage

Region	Standard	Gasoline/Petrol	Diesel	Notes
United States	OBD-II (SAE J1979)	1996+	1996+	All U.S. light-duty cars and trucks from 1996 onward are fully supported.
Canada	OBD-II (SAE J1979)	1998+ (most 1996-97 work)	1998+	Treat 1998+ as fully supported; many 1996-1997 vehicles also work.
European Union / UK	EOBD	2001+ petrol	2004+ diesel	2001+ petrol and 2004+ diesel have full EOBD support; earlier Euro cars may have 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	Most late-model imports fully supported.

Diagnostic Data

WHAT OBDAI READS

Standard OBD2 Data (All Compliant Vehicles)

Every OBD2-compliant vehicle provides this core diagnostic data:

Trouble Codes (DTCs) — Current, pending, and permanent diagnostic trouble codes
Freeze Frame Data — Snapshot of sensor readings when a code was triggered
I/M Readiness Monitors — Emissions system status for inspection/maintenance tests
Live Sensor Data — Real-time readings from 150+ parameters (RPM, coolant temp, vehicle speed, oxygen sensors, fuel trim, and more)
Vehicle Identifier Data — VIN decoding, Calibration ID, CVN, ECU names, trip counters, time since MIL cleared, and more

Enhanced Diagnostics Coming Soon

Manufacturer-Specific PIDs — Extended sensor data beyond standard OBD2 (requires OBDAI branded adapter)

Connection Types

RECOMMENDED HARDWARE

For the best experience with ARIA, we recommend our purpose-built diagnostic devices.

OBDAI Gen 2 BLE Device — Premium Choice

Custom-branded professional hardware
Bluetooth Low Energy 4.0+ for reliable wireless connection
Optimized for ARIA’s continuous monitoring features
Works with iOS, Android, and Windows

OBDAI Gen 1 BLE Device — Great Value

Reliable BLE connectivity tested with OBDAI
Same protocol support as Gen 2
Works with iOS, Android, and Windows

Your Hardware

Already Have Hardware?

OBDAI works with a variety of ELM327-based adapters across all connection types. These are devices we’ve specifically tested:

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

Note: For the full ARIA experience — including manufacturer-specific parameters and Agent-controlled sensor selection — we recommend OBDAI hardware. Third-party adapters may have connection limitations or slower response times.

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:

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

If your car is 1996+ (US), 2001+ petrol (EU), or 2004+ diesel (EU), you’re covered. ARIA will connect, read codes, pull live data, and provide AI-powered diagnostics.

For everything else, try connecting — you might be surprised. ARIA will automatically discover what data your vehicle makes available.

Works With Your Vehicle

Vehicle Compatibility

The Simple Truth

If your vehicle has an OBD2 port, OBDAI works with it (mostly)

Global Coverage

Worldwide OBD2 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