🔋 EV & Hybrid Data Field Prioritization
🔋

EV & Hybrid Data Field Prioritization (Battery, Charging, Energy)

This document describes which fields to use for electric (BEV) and hybrid (HEV/PHEV) vehicles and in which order. Cloud Connect fields (MDI_CC_*, OEM stack) always come first. Use the highest-priority field available for a given vehicle and move to the next one only if it is null or unsupported. Availability depends on make, model and year, so check vehicle coverage first.

1. Identify the powertrain

- MDI_OBD_HEV_ENGINE_MODE (1203): 0 = Off, 1 = Combustion, 2 = Electric. On a hybrid, it tells you whether the vehicle is currently running on fuel or on the battery.

- Otherwise, rely on your vehicle database (VIN decoding).

2. Traction battery state of charge (SoC, %)

Priority 1: MDI_CC_BATTERY_CHARGE_LEVEL (10282, %). OEM reading.

Priority 2: MDI_OBD_HEV_BATTERY_STATE_OF_CHARGE (1209, %). Standard OBD reading, fallback only.

Do not confuse it with the 12 V battery. For the 12 V vehicle battery, use MDI_CC_VEHICLE_BATTERY_VOLTAGE (10247, V) first, then MDI_EXT_BATT_VOLTAGE (151, mV). BATT_VOLT / BATT_CHARGING (59 / 63) are the device's own internal battery.

3. Remaining range

Priority 1: MDI_CC_DISTANCE_REMAINING (10360, km). Remaining distance reported by the vehicle.

4. Charging

Priority 1: MDI_CC_CHARGING_STATE (10406, boolean). The battery is actually charging.

Priority 2: MDI_CC_CHARGE_CABLE_CONNECTED (10284, boolean). The cable is plugged in.

Charge power and current: MDI_CC_BATTERY_CHARGE_POWER (10350, W) and MDI_CC_BATTERY_CHARGE_CURRENT (10351, A).

Suggested session logic: a charging session starts when CHARGING_STATE goes true (cable connected) and ends when it goes false or the cable is unplugged. Energy added can be estimated either as SoC end minus SoC start, times the usable battery capacity from your vehicle database, or by integrating charge power over time (kWh = sum of W x seconds / 3,600,000).

5. Battery current, voltage and power

Current, priority 1: MDI_CC_BATTERY_CURRENT (10349, A).

Current, priority 2: MDI_OBD_HEV_BATTERY_CURRENT (1208, mA, divide by 1,000 for A).

Voltage: MDI_OBD_HEV_BATTERY_VOLTAGE (1207, mV, divide by 1,000 for V).

Power (kW) = V x A / 1,000.

6. Energy consumption

Priority 1: MDI_CC_TOTAL_POWER_CONSUMPTION (10355), total EV power consumption, broken down into MDI_CC_AIR_CONDITIONER_POWER_CONSUMPTION (10352, W), MDI_CC_AUXILIARIES_POWER_CONSUMPTION (10353, W) and MDI_CC_PTC_POWER_CONSUMPTION (10354, W, cabin heater).

Priority 2, OBFCM (Euro 6d and later, PHEV/EV): MDI_OBD_OBFCM_HEV_TOTAL_GRID_ENERGY (1436, kWh, lifetime grid energy supplied to the battery), then MDI_OBD_OBFCM_HEV_RECENT_GRID_ENERGY (1430, kWh, recent).

PHEV distance split (OBFCM only): MDI_OBD_OBFCM_HEV_TOTAL_ODOMETER_CDO_ENG_OFF (1433, km, charge-depleting with engine off, i.e. electric driving), ..._CDO_ENG_ON (1434, km), ..._CIO (1435, km, charge-increasing). Fuel used in each mode: MDI_OBD_OBFCM_HEV_TOTAL_FUEL_CONSUMED_CDO / _CIO (1431 / 1432, mL).

Useful calculations: grid consumption (kWh/100 km) = change in TOTAL_GRID_ENERGY / change in odometer x 100. PHEV electric share (%) = TOTAL_ODOMETER_CDO_ENG_OFF / MDI_OBD_OBFCM_TOTAL_ODOMETER (1424) x 100.

7. Battery health, temperature and warnings

State of health: MDI_CC_HEV_BATTERY_STATE_OF_HEALTH (10367, %).

Temperature, priority 1: MDI_CC_HEV_BATTERY_TEMPERATURE (10414, °C). Priority 2 (VAG group): MDI_CC_VAG_HYBRID_BATTERY_TEMPERATURE (10336).

Warnings, priority 1: MDI_CC_BATTERY_WARNING (10368). Priority 2: MDI_OBD_HEV_BATTERY_WARNING (1528) and MDI_OBD_HEV_HAZARD_WARNING_LAMP (1136).

Data implementation rules

- Unit normalization: mA and mV divide by 1,000; W divide by 1,000 for kW; OBFCM fields are sent as strings, so parse them as numbers.

- Lifetime vs recent: TOTAL OBFCM fields are permanent lifetime counters, never reset them. RECENT fields reset after 50 h of engine run or a code clear, so apply the same offset logic as for fuel (article 278).

- Odometer: EVs use the same mileage fields as other vehicles, CC first: MDI_CC_DASHBOARD_MILEAGE (10342, km), then MDI_DASHBOARD_MILEAGE (km), then MDI_OBD_MILEAGE (km), see article 289.

Device Manager

Please see article 249