4
RNL confidential Information
Note
• This CAN interface is for DC Combo Charger. 500kbps CAN is adopted.
– Not support GB/T27930 CAN interface
• CAN Message IDs are categorized by fixed IDs and Variable IDs for charging application. The ID categorization is for
avoiding data error during charging communication. Fixed ID needs to be filled during system initialization.
– example – almost fixed) CF_EVSEIsolationStatus_isUsed=1 (almost mandate), CF_EVSEMaximumVoltageLimit_isUsed=1 (mandate),
CF_EVSEMaximumVoltageLimit_isUsed=1(mandate), CF_EVSEMaximumPowerLimit_isUsed=1 (mandate),
CR_EVSEMaximumPowerLimit, CR_EVSEMaximumVoltageLimit, CR_EVSEMaximumCurrentLimit etc.
• Default Value is recommended value for Charging application.
– Default Values = (CR_ExpectedEVServiceCategory=0, CR_ExpectedEVRequestedEnergyTransferMode=3,
CR_EVSEEnergyTransferMode=3,CF_PaymentOption=1)
• Not require to use all of Messages from EV.
• V2G-DC-648] If the EVCC wishes to stop the Communication Session for a non-critical reason (e.g. user interaction)
after having sent a SessionSetupReq message and before having sent a PowerDeliveryReq message with
ReadyToChargeState equal to “TRUE”, the EVCC should not immediately change the CP State, unless this is required
by another requirement in this document, but the EVCC shall send a SessionStopReq message as the next request
message and then wait for a SessionStopRes message. It shall then proceed according to [V2G-DC-413], [V2G-DC-
750], [V2G-DC-657], and [V2G-DC-658]
• If the EVCC wishes to stop the Communication Session for a non-critical reason (e.g. user interaction) after having
sent a PowerDeliveryReq message with ReadyToChargeState equal to “TRUE” and before having sent a
CurrentDemandReq message, the EVCC, in accordance with [V2G-DC-424], shall send a CurrentDemandReq
message, e. g. with EVTargetCurrent equal to “0 A” (zero ampere), and wait for a CurrentDemandRes message
before continuing according to [V2G-DC-673].
