IEC 61851-24: digital communication for DC charging
The IEC umbrella for the data a DC charger and car must exchange to control charging. Its annexes point to the three concrete protocols: CHAdeMO (A), GB/T 27930 (B) and DIN SPEC 70121 or ISO 15118 for CCS (C).
What the standard does
IEC 61851-23 says what a DC station must do; IEC 61851-24 says what the station and car must tell each other so it can do it. The main text lists the parameters in abstract form (maximum voltage and current of the car, the current request, the charger's available output, present values, status and error information) and the phases of a DC session. The annexes then map those abstract parameters to the concrete messages of each system.
| Annex | System | Protocol | Physical link | Tool module |
|---|---|---|---|---|
| A | System A | CHAdeMO | CAN at 500 kbit/s plus analogue lines | can/chademo |
| B | System B | GB/T 27930 | CAN with SAE J1939 addressing | can/gbt27930 |
| C | System C (CCS) | DIN SPEC 70121, with ISO 15118 as its successor | HomePlug Green PHY on the pilot (ISO 15118-3) | hlc/din70121, hlc/iso15118-2, hlc/iso15118-20 |
The common parameters
| Abstract parameter | CHAdeMO | GB/T 27930 | DIN SPEC 70121 |
|---|---|---|---|
| Car maximum voltage | 0x100 | BHM, BCP | EVMaximumVoltageLimit in ChargeParameterDiscoveryReq |
| Charger available output | 0x108 | CML | EVSEMaximumVoltageLimit and EVSEMaximumCurrentLimit |
| Current request | 0x102 | BCL | EVTargetCurrent in CurrentDemandReq |
| Present output | 0x109 | CCS | EVSEPresentVoltage and EVSEPresentCurrent |
| Stop and fault information | status and fault flags in 0x102 and 0x109 | BST, CST, BEM, CEM | DC_EVStatus, DC_EVSEStatus, ResponseCode |
The table is the tool's own mapping of the fields it decodes, arranged by the abstract parameters. It helps compare a CHAdeMO, GB/T and CCS session of the same car or charger side by side.
How it relates to the protocol modules
- The tool does not implement IEC 61851-24 as such. It implements the concrete protocols the annexes point to, one module per standard, registered in the protocol registry.
- Because all three share the same abstract parameters, the checks look alike: CH-02, GB-05 and the SQ and IS20 checks all ask whether the charger stayed at or below what the car requested.
- Timing for systems A and B comes from their own specifications (cyclic periods and timeouts, CAN-02, GB-01 to GB-04); for system C the V2G timers of DIN SPEC 70121 and ISO 15118 apply (TIM-01 to TIM-06).
The annex letters and the exact version of each protocol the 2014 annexes reference (for example which CHAdeMO version Annex A describes) should be checked against the edition in use; a second edition may add ChaoJi.
Loss of communication
All three systems treat a silent peer as a reason to stop: the charger must end the energy transfer when the car's messages stop, and the car when the charger's stop. In CAN systems this is a missed cyclic frame for longer than a timeout; in CCS it is a missing response (V2G_EVCC_Msg_Timeout) or a closed TCP connection. CAN-01, CAN-02 and TIM-01 flag the moment the traffic stopped, which is usually the moment the other side began its shutdown.
Sources
- IEC 61851-24:2014, main text and Annexes A, B and C
- IEC 61851-23:2014, the station requirements the communication serves