A DC session, message by message

A DC charging session in ISO 15118-2 and DIN SPEC 70121 from SessionSetup to SessionStop: what each exchange decides, what car and charger do electrically at that moment, and which faults show up where.

Before the first message

  • Plug in: the car's resistor pulls the Control Pilot from A to B, and the charger answers with the 5 percent duty cycle that asks for digital communication.
  • SLAC pairs the two modems, SDP gives the car the address and port of the charger, and the car opens the TCP connection: plain TCP for most DIN SPEC 70121 sessions and for external identification, TLS for Plug and Charge.
  • The app handshake picks DIN SPEC 70121 or ISO 15118-2 for the rest of the session.
  • The DC pins carry no voltage yet: the charger output is off and the car's DC contactors are open.

The layers below are covered in HomePlug Green PHY: powerline on the Control Pilot, SDP and V2GTP: finding the charger and framing messages and The app protocol handshake. From here on the car always asks and the charger always answers, one request at a time (SQ-02, SQ-03).

The sequence

  1. EV: SessionSetupReq, EVCCID; SessionID all zero
  2. EVSE: SessionSetupRes, OK_NewSessionEstablished, EVSEID and the SessionID for the rest of the session
  3. EV: ServiceDiscoveryReq
  4. EVSE: ServiceDiscoveryRes, payment options and energy transfer modes, for example DC_extended
  5. EV: PaymentServiceSelectionReq, ExternalPayment or Contract, and the charge service
  6. EV: AuthorizationReq, repeats while EVSEProcessing is Ongoing
  7. EV: ChargeParameterDiscoveryReq, DC_EVChargeParameter: the car's maximum voltage, current and power, energy request and state of charge
  8. EVSE: ChargeParameterDiscoveryRes, DC_EVSEChargeParameter: the charger's voltage, current and power range, and the SAScheduleList
  9. EV: CableCheckReq, connector locked, pilot in state C; repeats while the charger measures
  10. EVSE: CableCheckRes, EVSEProcessing Finished, EVSEIsolationStatus Valid
  11. EV: PreChargeReq, EVTargetVoltage is the battery voltage, EVTargetCurrent small; repeats
  12. EVSE: PreChargeRes, EVSEPresentVoltage approaches the target
  13. EV: PowerDeliveryReq, ChargeProgress Start; the car closes its contactors
  14. EV: CurrentDemandReq, EVTargetCurrent and EVTargetVoltage; repeats for the whole charge
  15. EVSE: CurrentDemandRes, EVSEPresentVoltage, EVSEPresentCurrent, the limit achieved flags and the meter
  16. EV: PowerDeliveryReq, ChargeProgress Stop; the charger ramps the current down
  17. EV: WeldingDetectionReq, repeats; the car watches the voltage fall with its contactors open
  18. EV: SessionStopReq, ChargingSession Terminate
  19. EVSE: SessionStopRes, then the TCP connection closes

What each step decides

ExchangeWhat it decidesTypical faultsChecks
SessionSetupThe SessionID every later message carriesA SessionID that is not zero in the request of a new session, or one that changes laterSQ-04
ServiceDiscoveryWhat the charger offers: payment options, energy transfer modes, extra servicesThe mode the car needs is not in the listSQ-06, later
PaymentServiceSelectionThe payment option and the services of this sessionAn option or service that was not offeredSQ-07, SQ-05
AuthorizationWhether this session may chargeEVSEProcessing Ongoing until the car gives upTIM-02, see The session stops at authorization
ChargeParameterDiscoveryBoth sets of limits and the scheduleFAILED_WrongChargeParameter; voltage ranges that do not overlapSQ-05, SQ-06, TIM-02, the Negotiation tool
CableCheckWhether the insulation of cable and inlet allows voltage to be appliedA loop that never finishes, an isolation Fault, a car still in state BDC session stalls in CableCheck or PreCharge, Isolation monitoring and CableCheck
PreChargeThat the charger output matches the battery voltage before the contactors closeThe output levels off below the target, or the loop runs out of timeDC-01
PowerDelivery StartThe schedule tuple in use and the start of energy transferA tuple the charger did not send; FAILED_PowerDeliveryNotAppliedSQ-08, SQ-05
CurrentDemandThe operating point, request by requestSlow answers, an output above the target, a charger that stops answeringTIM-01, TIM-05, TIM-06, SQ-09
PowerDelivery StopThe end of energy transferCurrent still flowing afterwardsPW-03, with a current log
WeldingDetectionWhether the car's contactors really openedA voltage that does not fallThe session does not end cleanly
SessionStopThe end of the session, or a pauseA connection closed before the responseTC-02

SQ-01 checks the order of the whole sequence against the state machine of the protocol that was negotiated. A step back is allowed where the standard allows it, for example a new ChargeParameterDiscovery after the charger asked for renegotiation. How the car's limits and the charger's limits combine is explained in How the car sets its limits.

DIN SPEC 70121 differences

StepISO 15118-2DIN SPEC 70121
Payment selectionPaymentServiceSelectionReqServicePaymentSelectionReq
AuthorizationAuthorizationReqContractAuthenticationReq
Payment in practiceExternalPayment, or Contract (Plug and Charge over TLS)ExternalPayment only, normally without TLS
Requested energy transferRequestedEnergyTransferModeEVRequestedEnergyTransferType
Start and stopChargeProgress Start, Stop or RenegotiateReadyToChargeState true or false
EVSEProcessingFinished, Ongoing, Ongoing_WaitingForCustomerInteractionFinished, Ongoing
Isolation statusInvalid, Valid, Warning, Fault, No_IMDInvalid, Valid, Warning, Fault
SessionStopReqChargingSession Terminate or PauseNo fields
Meter in CurrentDemandResOptional MeterInfo and ReceiptRequiredNot part of the message

The electrical steps are the same in both, and IEC 61851-23 governs them. Most cars that offer both list them in the app handshake with different priorities, and many chargers in the field still pick DIN SPEC 70121.

Timing along the way

  • Each answer within V2G_EVCC_Msg_Timeout: 2 s for most messages, 5 s for PowerDelivery, 0.25 s for CurrentDemand in the profile (TIM-01).
  • Authorization and ChargeParameterDiscovery may stay Ongoing for up to V2G_EVCC_Ongoing_Timeout, 60 s in the profile (TIM-02). CableCheck has its own timer, which is not in the profile.
  • PreCharge has to reach the target within dc.prechargeTimeoutS, 7 s, and within dc.prechargeToleranceV, 20 V (DC-01).
  • From the first SDP request to SessionSetupRes within 20 s (TIM-04); between a response and the next request at most 60 s (TIM-03).

All of these values are flagged for verification in the limit profile. Every timer and timeout lists them with their sources, and Limit profiles: the numbers behind every check explains how to change them for a test plan.

Sources

  • ISO 15118-2:2014, DC message set and sequence, timing tables
  • DIN SPEC 70121:2014-12, DC message set and sequence
  • IEC 61851-23, the electrical sequence of a DC charging station
  • ChargeX Consortium: ev-charge-seq-state, Argonne National Laboratory, Apache-2.0: PlantUML sequence diagrams of SAE J1772, ISO 15118-2 and ISO 15118-20 with OCPP 1.6J, 2.0.1 and 2.1, including an ISO 15118-20 DC session with cable check, pre-charge and welding detection