OBDAI 3.1: Standard OBD2 stops here. ARIA keeps going.

OBDAI 3.1: ARIA Reads the Rest of the Car, Beyond Standard OBD2

Standard OBD2 tells you how the engine and emissions system are doing. That’s it. The tire pressures, the transmission fluid temperature, the battery state, the door switches, the mileage the computers are keeping: all of that lives in the car’s other modules, in each manufacturer’s own language. OBDAI 3.1 is the release where ARIA learned to speak it.

There’s never a good time to record a demo. I shot this one in my 2017 Explorer between school pickups, phone on the dash, no script. I asked ARIA questions the way I’d ask the tech in the next bay, and she answered straight from the Explorer’s own modules. Then she kept watching the transmission and checked back in on her own while I drove.

Bringing in manufacturer-specific parameters has been the plan since the beginning. It’s the next logical step after full standard OBD2 and OBDonUDS, and it’s the part of diagnostics the big scan tool companies have always kept behind their own hardware. This post explains what manufacturer-specific data actually is, how it differs from standard OBD2 and OBDonUDS, and what ARIA did with it on a real drive.

Three kinds of diagnostic data, explained

Most people say “OBD2” to mean anything you can pull off the diagnostic port. Under the dash, there are really three different things going on.

1. Standard OBD2 (SAE J1979): the emissions basics

Standard OBD2 is the common language every car sold in the U.S. since 1996 has to speak. It exists because of emissions law, so it covers what emissions regulators care about: engine speed, load, coolant temperature, fuel trims, oxygen sensors, readiness monitors, Mode 6 self-tests, freeze frame and the check engine codes. The parameter list is published by SAE (J1979DA defines about 220 live parameters), and it means the same thing on a Ford as it does on a Toyota. That’s why a $20 code reader can read it.

The catch: it stops at the engine and emissions system. Standard OBD2 has nothing to say about your tires, your doors, your seats or how hot your transmission fluid is, unless the automaker chooses to put it there.

2. OBDonUDS (SAE J1979-2): the same rules, a newer protocol

OBDonUDS is the next generation of standard OBD2. It moves the same emissions diagnostics onto UDS (Unified Diagnostic Services, ISO 14229), the protocol engineers already use inside the car. Some 2025 and 2026 vehicles use it already, and it’s required for 2027 models.

It still covers emissions, but it reports a lot more about them: readiness by group with the individual tests inside each group, test results tied to specific trouble codes, first and latest fault snapshots, and how often each monitor gets a chance to run. We covered that in How OBDonUDS Helps You Diagnose Faults and Resolve Readiness. What matters here is that OBDonUDS is still a published standard with a defined scope. It doesn’t open up the rest of the car.

3. Manufacturer-specific data: the rest of the car

Manufacturer-specific data, also called OEM data or enhanced diagnostics, is everything each automaker defines for itself. Every module in the car (body control, transmission, brakes, airbags, parking aid, battery energy control, climate, infotainment) has its own list of readings, identified by codes the manufacturer assigns. On many newer vehicles those readings travel over the same UDS protocol OBDonUDS uses, but the dictionary is private. A reading’s ID, its scaling and which module holds it can change by make, model, year and module version.

That’s why most generic scanners can’t show it, and why the dealer tools and the big scan tool brands charge what they do. Somebody has to build and maintain that dictionary, car by car.

ARIA lists the five Ford modules she can reach and explains the difference between standard OBD2 and manufacturer-specific diagnostics
I asked ARIA to explain the difference herself. Her answer: “the difference between a basic health check and talking directly to the car’s individual departments.”

Side by side

Standard OBD2OBDonUDSManufacturer-specific
Defined bySAE J1979, publishedSAE J1979-2, publishedEach automaker, private
CoversEngine and emissionsEngine and emissions, in more depthBody, transmission, chassis, battery, comfort and more
Same on every car?YesYes, on vehicles that use itNo. Varies by make, model, year and module
Example readingsRPM, coolant temp, fuel trims, readinessReadiness group tests, fault snapshots, monitor activityTire pressures, transmission fluid temp, gear ratio, battery charge, door switches
In OBDAIAll tiersPRO and UltraNew in 3.1: PRO and Ultra

What ARIA read on my Explorer

Here’s what came off the car in about ten minutes of normal driving, all by asking.

  • Tire pressures, all four corners. 35.6 PSI front left, 35.4 front right, 35.6 rear left and 37.6 rear right, from the body control module. She compared them to the 35 PSI placard and reminded me not to let air out of warm tires.
  • The modules that answered. OBDAI confirmed five: powertrain, body control, battery energy control, parking aid and the infotainment interface. It listed 33 more that sit on a network my adapter can’t reach, and noted the headlamp module didn’t respond.
  • Total vehicle distance. About 151,304 miles from the powertrain module. She noted it can differ slightly from the dash odometer. Then she pulled yesterday’s recorded reading from history (151,283.1) and did the math: 21.1 miles since.
  • Transmission data. Sixth gear in drive, commanded and measured ratio matched at 0.742, torque converter slip 1.75 RPM against zero requested, fluid at 142°F and climbing, no sensor errors.
  • Battery and body. 14 volts, an estimated 77% battery charge, both front doors closed, ignition in run.
Following ARIA tab showing manufacturer readings: tire pressures, total vehicle distance and gear ratios from the Ford body control and powertrain modulesFollowing ARIA tab showing transmission fluid temperature, transmission range, battery state of charge, door switches and ignition from the Ford modules
The new Following ARIA tab on my Explorer. Every reading is labeled with the module it came from, body control or powertrain.

None of that is standard OBD2. It’s the Explorer’s own data, read from its own modules.

Standard and manufacturer data in the same session

You don’t switch modes. ARIA reads standard OBD2 and manufacturer-specific data together, so she can put engine speed and coolant temperature next to tire pressures from the body module, or watch transmission temperature while she reads fuel trims. The adapter takes them one after another, not all at the exact same instant, but they all land in the same conversation and the same recording.

She keeps watching and reports back

I asked whether the transmission was warmed up, and if not, to keep an eye on it. ARIA set up a 15-minute watch, picked about 167°F as a practical warm-up target, and checked every two minutes. Then she came back on her own while I drove: 152°F, then 157°F, then 162°F, “just five degrees below our warm check target.”

ARIA reads the Explorer transmission data and schedules a temperature check-in every two minutesARIA reports a scheduled transmission temperature check-in on her own during the drive
Left: ARIA reads the transmission and sets up the watch. Right: one of her automatic check-ins, no tapping required.

She also stayed honest. After reading the transmission, she said a snapshot “isn’t a complete transmission health verdict.” I told her she was supposed to be helping me sell it. She was right, though. That’s the job: tell you what the car actually reported, not what you want to hear.

Everything she reads goes on the new Following ARIA tab, a live list of the manufacturer values she’s tracking in that session. The readings are saved with the session, so she can pick up the investigation later in the app or on the web. And she shows her work: you see each step on screen as she finds a module, looks up a reading and reads it.

ARIA shows her steps on screen while she looks up and reads manufacturer data
ARIA shows each step while she works: reviewing the session, looking up manufacturer data, reading it.

Tens of thousands of parameters, and you never scroll through them

OBDAI’s manufacturer catalog spans tens of thousands of manufacturer-specific parameters across thousands of vehicle applications, and it grows every week. A list that size would be useless on a phone screen. So there is no list. You ask for what you want (“what’s the transmission temperature?”, “what can the body module see?”) and ARIA searches the catalog for your car, finds the module that holds it, reads it, and can keep following it.

When you connect, OBDAI checks which modules on your car actually answer. Those totals are what’s in the catalog, not what every car will report. Your vehicle, its modules and your adapter decide what’s available, and ARIA tells you what she can and can’t reach.

Here’s the part I’m most excited about: new vehicles and corrections are added on our service, not in the app. For most parameters there’s no app update. They show up, and the next time you ask, ARIA has them.

J2534 on Windows: every module on the vehicle

The drive in the video used the OBD BLE GEN2 adapter on a phone. GEN2 talks to the car over CAN on the standard OBD2 pins, the main diagnostic network, which is where the engine computer and a handful of other modules live. On my Explorer, OBDAI confirmed five modules that way and listed 33 more on networks the adapter couldn’t reach. On the same Explorer simulator on my bench, GEN2 on an Android phone sees four.

A J2534 pass-through interface is a different class of tool. It’s the hardware dealer and shop software is built on, and it exposes a lot more of the vehicle. With OBDAI Ultra on Windows, ARIA uses it the same way she uses GEN2: you ask, she finds the module, she reads it.

Here’s ARIA on a Windows tablet, connected through a VXDIAG VCX SE J2534 interface to that 2017 Ford Explorer simulator. Same plain-English conversation, start to finish.

ARIA on Windows reports 25 responding Ford control modules on a 2017 Explorer simulator through a J2534 interface, broken down by vehicle area
“How many systems do you see on this Ford?” Through J2534, 25 control modules answered: powertrain, ABS and power steering, airbags, body, climate, seats, audio, instrument cluster and parking aid.

Then I asked her to grab three parameters from each one. She went module by module and came back with a table of live readings:

  • Powertrain (PCM): fuel pump ON
  • Power steering (PSCM): EPAS motor current 1 A
  • Restraints (RCM): belt tension sensor O.K.
  • Instrument cluster: supply voltage 13.837 V
  • Liftgate (RGTM): handle and latch switch states
  • Body and battery control: horn relay, reverse lamp and battery voltage
ARIA's table of readings grabbed from all 25 Ford modules, starting with ABS, audio, infotainment, body control, battery control and door modules
Three readings from each module, collected in about 28 seconds.
End of ARIA's module table with powertrain, power steering, restraints, liftgate, climate and seat readings, her interpretation cautions and her bottom line: all 25 modules returned data, 74 readable parameters
Her bottom line: all 25 modules returned data, 74 readable parameters in total.

She was just as careful as she was on the road. She called the readings one-time snapshots, not continuous monitoring, and said outright that this isn’t a full system health check. She also flagged which labels need context before anyone calls them a fault. That’s what you want from a diagnostic partner: read everything, then tell you what it does and doesn’t prove.

That’s manufacturer-level access. Not just the engine. Every module on the vehicle that answers.

Questions to ask ARIA

  • “How many manufacturer modules can you see on this car?”
  • “What’s the current tire pressure?”
  • “Is the transmission warmed up? If not, let me know when it is.”
  • “What can the body module tell you right now?”
  • “What was the mileage last time, and what’s the difference?”
  • “Compare coolant temperature with transmission temperature on this drive.”

You don’t need module names, parameter IDs or a wiring diagram. Describe what you want and ARIA works out where to find it.

What you need

Manufacturer-specific data comes with OBDAI PRO and the OBD BLE GEN2 adapter on iPhone, iPad, Android and Windows, or OBDAI Ultra with a supported J2534 interface on Windows. It’s read-only: ARIA reads values, she doesn’t write, reset or program anything. OBDAI 3.1 is live now on iOS, Android and Windows, so update the app and ask ARIA what she can see on your car.

See PRO and Ultra Watch the full drive

Frequently asked questions

What is manufacturer-specific OBD2 data?

It’s diagnostic data each automaker defines for its own vehicles, beyond the standard OBD2 emissions set. It covers modules like body control, transmission, battery management and parking aid, with readings such as tire pressures, transmission fluid temperature and battery charge. It’s also called OEM data or enhanced diagnostics.

Is OBDonUDS the same as manufacturer-specific data?

No. OBDonUDS (SAE J1979-2) is the new standard for emissions diagnostics, required on 2027 models. Manufacturer-specific data is the automaker’s own data for the rest of the car. On many newer vehicles both use the UDS protocol, but OBDonUDS is a published standard and manufacturer data is not.

Can a regular OBD2 scanner read manufacturer-specific parameters?

A basic code reader only reads standard OBD2. Reading manufacturer data takes a definition for each make, model and module, plus hardware that can make the requests. OBDAI uses its own catalog, the OBD BLE GEN2 adapter or a supported J2534 interface, and ARIA to find what you ask for. A J2534 interface on Windows reaches more of the vehicle’s modules than a Bluetooth adapter on the standard pins.

Does every car get manufacturer data in OBDAI 3.1?

Not yet. The catalog grows on our service without app updates. When you connect, OBDAI checks which modules your car answers, and ARIA tells you what’s available.

If you try it, tell me what you asked her and what she found. I read these myself, and they decide which vehicles we add next.

– Daniel
Founder, OBDAI

author avatar
Daniel-Blackmon Founder

Share: