Physical values: how numbers travel in V2G messages
Voltages, currents, power and energy are sent as a small integer with a power of ten: PhysicalValue in DIN SPEC 70121 and ISO 15118-2, RationalNumber in ISO 15118-20. How to read them, worked examples, and the usual misreadings.
Value, Multiplier and Unit
DIN SPEC 70121 and ISO 15118-2 send voltages, currents, power and energy as a PhysicalValue with three parts. The number it stands for is Value times ten to the power of Multiplier, in the unit named by Unit.
| Part | Type in the schema | Range | Note |
|---|---|---|---|
| Value | 16 bit signed integer | -32 768 to 32 767 | The digits |
| Multiplier | Restricted integer | -3 to 3 | The power of ten, encoded in 3 bits |
| Unit | Enumeration | ISO 15118-2: h, m, s, A, V, W, Wh. DIN SPEC 70121 adds Ah, VA and W_s | Required in ISO 15118-2, optional in DIN SPEC 70121 |
The 16 bit Value is why the multiplier exists. 32 767 is not enough for 150 kW written in W, so the sender writes 15 000 with Multiplier 1, or 150 with Multiplier 3. Range is traded for resolution: with Multiplier -1 a current has 0.1 A steps and cannot exceed 3 276.7 A, which is plenty; with Multiplier 3 a power has 1 kW steps.
There is no kW or kWh in the unit list. A kilowatt is always W with Multiplier 3, a kilowatt hour Wh with Multiplier 3.
Worked examples
| Field | Value | Multiplier | Unit | Means |
|---|---|---|---|---|
| EVTargetVoltage | 4000 | -1 | V | 400.0 V |
| EVTargetCurrent | 1255 | -1 | A | 125.5 A |
| EVSEMaximumPowerLimit | 150 | 3 | W | 150 000 W, 150 kW |
| EVSEMaximumPowerLimit | 15000 | 1 | W | 150 000 W, the same power written another way |
| EVMaxCurrent (AC) | 32 | 0 | A | 32 A per phase |
| EVEnergyRequest | 60 | 3 | Wh | 60 000 Wh, 60 kWh |
| PMax in an ISO 15118-2 schedule | 11 | 3 | W | 11 kW |
Two encodings of the same quantity are equal. Compare the scaled numbers, never the raw Value fields: 4000 with Multiplier -1 and 400 with Multiplier 0 are both 400 V.
RationalNumber in ISO 15118-20
ISO 15118-20 replaces PhysicalValue with RationalNumber: a 16 bit Value and an 8 bit Exponent, meaning Value times ten to the power of Exponent. There is no Unit element; the field fixes the unit. EVMaximumChargePower is in W, EVTargetVoltage in V, EVTargetCurrent in A.
| Field | Value | Exponent | Means |
|---|---|---|---|
| EVMaximumChargePower | 15000 | 1 | 150 000 W |
| EVTargetVoltage | 4000 | -1 | 400.0 V |
| EVSEMaximumChargeCurrent | 500 | 0 | 500 A |
- The exponent may be any 8 bit signed number, a much wider range than the -3 to 3 of the first generation, although real messages use small exponents.
- AC values per phase have their own fields with the suffixes _L2 and _L3, each a RationalNumber of its own (IS20-10).
Numbers that are not physical values
| Field | Encoding | Unit |
|---|---|---|
| EVRESSSOC, FullSOC, BulkSOC (DIN SPEC 70121, ISO 15118-2); TargetSOC (ISO 15118-20) | 8 bit integer | percent |
| MeterReading in ISO 15118-2 MeterInfo | 64 bit unsigned integer | Wh, with no multiplier |
| MeterReading in DIN SPEC 70121 MeterInfo | PhysicalValue | as its Unit says |
| ChargedEnergyReadingWh in ISO 15118-20 MeterInfo | 64 bit unsigned integer | Wh, as the name says |
| DepartureTime and the start of a RelativeTimeInterval | 32 bit unsigned integer | seconds from now |
| NotificationMaxDelay | unsigned integer | seconds |
| PMax in a DIN SPEC 70121 schedule | 16 bit signed integer, no multiplier and no unit | see the note |
DIN SPEC 70121 carries PMax as a plain integer. Its unit is given in the text of the standard, not in the schema; check it there before comparing a DIN schedule with a measured power.
Typical misreadings
| What you see | Cause |
|---|---|
| A voltage of 4000 V, or a power of 150 W | The multiplier was ignored |
| A value ten or a thousand times too small | The sign of a negative multiplier was lost, or the multiplier was applied twice |
| A power that looks like an energy | W and Wh confused; the element name says which it is |
| Energy off by a factor of 1 000 | A kWh figure from the backend or the car display compared with Wh from MeterInfo |
| A GB/T 27930 current that is always negative | The CAN field carries a fixed offset, so a charging current reads as a negative number; the analyzer compares magnitudes |
The analyzer scales every PhysicalValue by its Multiplier and every RationalNumber by its Exponent before a check, a tool or a finding uses it. It takes the unit from the meaning of the field and does not check the Unit element, so a sender that labels a current with V is not reported.
CHAdeMO and GB/T 27930 have no self describing numbers: each CAN field has a fixed scale and offset, which the analyzer takes from its field tables. Those tables are flagged for verification.
Sources
- ISO 15118-2:2014, PhysicalValueType, unitSymbolType, unitMultiplierType
- DIN SPEC 70121:2014-12, PhysicalValueType
- ISO 15118-20:2022, RationalNumberType
- Message reference of this tool, generated from the libcbv2g headers