Short answer: Yes — OBDAI fully supports hybrid and electric vehicles through the complete SAE J1979DA parameter set, current through the April 2024 specification. ARIA decodes battery pack health, charging state, motor data, fuel cell systems, and more. Your vehicle determines what data is available — not OBDAI.
What Hybrid and EV Data Can OBDAI Read?
OBDAI decodes the complete J1979DA hybrid/EV parameter set. All parameters below are captured second-by-second in ARIA’s time-series analysis — not just snapshot values.
Battery State and Charge
| PID | Display Label | Description |
|---|---|---|
| 0x5B | BAT_SOC | Hybrid Battery Pack Remaining Charge (%) |
| 0xB2 | BAT_SOH | Traction Battery Pack State of Health (%) |
| 0xBE | HVESS_SOH / HVESPA–H_SOH | HVESS State of Health, per pack A through H (%) |
| 0xBF | HVESS_MIN_SOC / HVESPA–H_MIN_SOC | Recommended Minimum State of Charge per pack (%) |
| 0xC1 | HVESS_MAX_SOC / HVESPA–H_MAX_SOC | Recommended Maximum State of Charge per pack (%) |
| 0xD2 | SOCE / SOCR | State of Certified Energy / State of Certified Range (%) |
| 0xD8 | BCAP_R | Battery Capacity Calculation Ready (Not Ready / Ready) |
| 0xD9 | CALCULATED_ESS_CAP | Calculated Energy Storage System Energy (kWh) |
Battery Temperature
| PID | Display Label | Description |
|---|---|---|
| 0xB4 | HVESS_Temp | HVESS Temperature (°C) |
| 0xB7 | HEV Batt Min Cell Temp | Minimum cell temperature (°C/°F) |
| 0xB7 | HEV Batt Max Cell Temp | Maximum cell temperature (°C/°F) |
| 0xB7 | HEV Batt Ave Cell Temp | Average cell temperature (°C/°F) |
| 0xB7 | HEV Batt Bus Bar Temp | Bus bar temperature (°C/°F) |
| 0xB7 | HEV Batt Coolant Temp | Coolant temperature (°C/°F) |
| 0xB7 | HEV_Batt_Therm_Mode | Thermal management state (Active / Passive / Off) |
Battery Voltage and Current
| PID | Display Label | Description |
|---|---|---|
| 0x9A | HEV_BATT_V | Hybrid/EV Battery System Voltage (V) |
| 0x9A | HEV_BATT_A | Hybrid/EV Battery System Current (A) |
| 0xB5 | HVESS_Cur | HVESS Current (A) |
| 0xB6 | HVESS_Volt | HVESS Voltage (V) |
| 0xB9 | HEV Batt Min Cell Voltage | Minimum cell voltage (V) |
| 0xB9 | HEV Batt Max Cell Voltage | Maximum cell voltage (V) |
| 0xBA | HEV Batt PWR Available | Continuous rated power available (%) |
| 0xBA | HEV Batt Charge Current Limit | Continuous charge current limit (A) |
| 0xBA | HEV Batt Discharge Current Limit | Continuous discharge current limit (A) |
Charging Rate and Power
| PID | Display Label | Description |
|---|---|---|
| 0xB3 | HVESS_ACR / HVESPA–H_ACR | Actual charge rate, system and per pack A–H (kW) |
| 0xD1 | HVESS_CHARGE_LIM | Energy Storage System actual charging limit (kW) |
| 0xD1 | HVESS_CHARGE_ACT | Energy Storage System actual charging power (kW) |
| 0xD4 | HVESS_ENER | Battery pack cumulative energy per second (Wh/s) |
| 0xDA | HVESS_ENER | Battery pack cumulative current per second (Ah/s) |
Energy Throughput (Lifetime)
| PID | Display Label | Description |
|---|---|---|
| 0xBB | HVESS_Enrg_In / HVESPA–H_Enrg_In | Cumulative energy into the HVESS system and per pack (kWh) |
| 0xBC | HVESS_Enrg_Out / HVESPA–H_Enrg_Out | Cumulative energy from the HVESS system and per pack (kWh) |
| 0xBD | HVESS_Enrg_Tput | Total energy throughput (Wh) |
Battery Capacity
| PID | Display Label | Description |
|---|---|---|
| 0xC2 | HVESS_DEnrg_CAP / HVESPA–H_DEnrg_CAP | Discharge energy capacity, system and per pack (kWh) |
| 0xD0 | REMAINING_ESS_RSRV_CAP | Remaining ESS reserve energy (kWh) |
| 0xD0 | INIT_ESS_RSRV_CAP | Initial ESS reserve energy (kWh) |
| 0xD0 | HEALTH_DIST | Distance since last SOH update (km/miles) |
Vehicle Mode and State
| PID | Display Label | Description |
|---|---|---|
| 0x9A | HEV_MODE | Hybrid/EV vehicle charging state (CSM, CDM, or CIM) |
| 0x51 | FUEL_TYP | Fuel type — includes ELEC, HYB_GAS, HYB_ETH, HYB_DSL, HYB_ELEC, HYB_MIX, HYB_REG, FC_H2 (fuel cell hydrogen) |
Electric Motor Data (up to 8 motors)
| PID | Display Label | Description |
|---|---|---|
| 0xCC | EM A–H RPM | Individual electric motor RPM, motors A through H |
| 0xCD | EM A–H TQ | Individual electric motor torque (Nm), motors A through H |
| 0xD6 | NUMPSATRIPSFLTMEMCLR | Number of propulsion system active trips since fault memory clear |
Fuel Cell Systems
| PID | Display Label | Description |
|---|---|---|
| 0xD5 | FC_VOLT | Fuel cell system voltage (V) |
| 0xD5 | FC_FUEL_RATE | Fuel cell fuel consumed per second (g/s) |
| 0xD5 | FC_CUMUL_CURR | Fuel cell cumulative current per second (mAh/s) |
| 0xD5 | FC_CUMUL_EMER | Fuel cell cumulative energy per second (Wh/s) |
How ARIA Uses This Data
All of the parameters above are captured second-by-second in ARIA’s time-series record — not just instantaneous snapshots. This means ARIA can detect:
- State of charge trends over a drive cycle
- Temperature imbalances developing across cell groups
- Charge rate anomalies during charging sessions
- Degradation patterns in State of Health over time
- Open-loop/closed-loop transitions in hybrid drive mode
When you ask ARIA about your EV or hybrid, it isn’t just reading a current value — it’s analyzing how those values moved throughout your session.
Why Can’t I See All of These on My Vehicle?
Your vehicle determines what’s available — not OBDAI.
The SAE J1979DA standard defines all the parameters above, but manufacturers only support the parameters relevant to their system. A Toyota Prius will broadcast different PIDs than a Chevy Bolt or a BMW i4. When you connect, OBDAI automatically queries your vehicle and shows only the parameters your vehicle actually reports.
This is normal and expected. Not every vehicle supports every parameter in the standard.
What About Tesla and Other Proprietary EVs?
Many EV manufacturers use proprietary protocols for deep battery cell data beyond what J1979DA defines. This data:
- Is not available through standard OBD2
- Requires manufacturer-specific tools or APIs
- Uses protocols outside the J1979-1 standard
OBDAI works with the universal OBD2 standard (J1979-1) — compatible with all 1996+ vehicles. We do not access manufacturer-specific proprietary systems.
Tesla specifically: Has an OBD2 port but provides minimal standard data through it. Most Tesla-specific diagnostics require the Tesla app or Tesla-certified third-party tools. The J1979DA parameters OBDAI supports may return limited data on Tesla vehicles.
Which Hybrid and EV Vehicles Work?
Any hybrid or EV with a standard OBD2 port that broadcasts J1979DA parameters:
- Toyota/Lexus hybrids (Prius, Camry Hybrid, RAV4 Hybrid, RX Hybrid)
- Honda hybrids (Accord Hybrid, CR-V Hybrid, Insight)
- Ford hybrids and PHEVs (Escape Hybrid, F-150 Hybrid, Mustang Mach-E)
- Hyundai/Kia hybrids and EVs (Ioniq 5, EV6, Tucson Hybrid)
- Chevrolet (Bolt EV, Bolt EUV, Volt)
- BMW i-series (i3, i4, iX)
- Mercedes EQ series
- Rivian (R1T, R1S — standard OBD2 port present)
- And most other vehicles with a standard OBD2 port
J1979-2 / UDS Support
The next generation of OBD protocols (J1979-2, based on UDS/Unified Diagnostic Services) is being phased in for 2027+ model year vehicles. OBDAI currently supports the complete J1979-1 / J1979DA parameter set. J1979-2 support is on the roadmap.
Questions? support@obdai.app