Stage: PowerDelivery and the energy transfer loop

PowerDelivery Start opens the energy transfer, then the car and the charger exchange a request and a response several times a second for as long as energy flows. The loops of the three standards, the limits they carry, renegotiation and what breaks.

What the stage does

  • PowerDeliveryReq with ChargeProgress Start asks the charger to deliver energy. In DIN SPEC 70121 the same request carries ReadyToChargeState true; in ISO 15118-2 it names the schedule tuple the car picked (SQ-08).
  • On AC the car switches the Control Pilot from B to C within 250 ms of sending PowerDeliveryReq Start, and the charger closes its contactor on state C before it answers. On DC the car has already closed its own contactors after pre-charge.
  • Then the loop runs: the car states what it wants, the charger answers with what it delivers and what it can deliver, until one side asks to stop.

The loops

  1. EV: PowerDeliveryReq, ChargeProgress Start; on AC the car now goes from B to C
  2. EVSE: PowerDeliveryRes, OK; on AC the contactor is closed
  3. EV: CurrentDemandReq, DC: EVTargetVoltage, EVTargetCurrent, the limits of the car
  4. EVSE: CurrentDemandRes, EVSEPresentVoltage, EVSEPresentCurrent, the limit achieved flags
  5. both: the loop repeats, several times a second, for the whole charge
  6. EV: PowerDeliveryReq, ChargeProgress Stop: the next stage
Standard and energyLoop request and responseWhat the car sends, what the charger answers
DIN SPEC 70121, DCCurrentDemandReq, CurrentDemandResTarget voltage and current; present voltage and current, limits reached
ISO 15118-2, DCCurrentDemandReq, CurrentDemandResAs DIN, plus EVSEID, the schedule tuple, meter values and ReceiptRequired
ISO 15118-2, ACChargingStatusReq, ChargingStatusResAn empty request; EVSEMaxCurrent, meter values and ReceiptRequired
ISO 15118-20, DCDC_ChargeLoopReq, DC_ChargeLoopResPresent voltage and a control mode block; present voltage and current, limits reached
ISO 15118-20, ACAC_ChargeLoopReq, AC_ChargeLoopResA control mode block; a control mode block, meter values, optionally a target frequency

ISO 15118-20 has two control modes. In scheduled mode the car follows a schedule and names its own targets; in dynamic mode the charger sets the operating point. The BPT variants of the blocks carry discharge values as well, for bidirectional transfer.

Limits and renegotiation

  • On AC the permitted current is the lower of the PWM duty cycle and EVSEMaxCurrent. A car has pw.settlingTimeS to follow a lower limit (PW-01).
  • On DC the charger announces EVSEMaximumCurrentLimit, EVSEMaximumVoltageLimit and EVSEMaximumPowerLimit and raises EVSECurrentLimitAchieved, EVSEVoltageLimitAchieved or EVSEPowerLimitAchieved when it holds the car below its request.
  • In ISO 15118-20 the charger stays inside the limits it announced (IS20-03) and, in scheduled mode, at or below the target of the car (IS20-04); power flows back only in a bidirectional session (IS20-05).
  • ISO 15118-2: EVSENotification ReNegotiation, or ChargeProgress Renegotiate from the car, sends the session back to ChargeParameterDiscovery for a new schedule. ISO 15118-20 uses ChargeProgress ScheduleRenegotiation and a new ScheduleExchange (IS20-09).
  • When ReceiptRequired is set, the car answers with MeteringReceiptReq (SQ-10); in ISO 15118-20 the same role falls to MeteringConfirmationReq.
TimerLimit profile keyProfile default
PowerDelivery response (V2G_EVCC_Msg_Timeout, long case)tim.msgTimeoutLongS5 s
CurrentDemand responsetim.msgTimeoutCurrentDemandS0.25 s
Other loop responses, general casetim.msgTimeoutS2 s
PowerDeliveryReq Start to the B to C change on ACcp.transition.maxDelayAfterPowerDeliveryS250 ms
Time the car has to follow a lower limitpw.settlingTimeS5 s
Allowed overshoot above the permitted currentpw.currentMarginPct and pw.currentMarginA5 percent and 0.5 A

The message timeouts, the B to C delay and the current margins are flagged for verification in the limit profile; the settling time is taken from IEC 61851-1:2017 Table A.6.

What usually breaks

  • PowerDelivery Start is refused: FAILED_ChargingProfileInvalid, FAILED_TariffSelectionInvalid, FAILED_PowerDeliveryNotApplied or FAILED_ContactorError.
  • On AC the car never goes to state C, or the charger never closes its contactor: the loop runs and no current flows.
  • The car draws more than the permitted current, or does not follow a lower limit in time (PW-01).
  • A slow answer in the charge loop: CurrentDemand has the tightest response timer of the session, and one late answer is enough for the car to stop.
  • The charger stops the session: EVSENotification StopCharging, EVSEStatusCode EVSE_Shutdown or EVSE_EmergencyShutdown, or an isolation fault while charging.
  • The car stops on its own, early: an EVErrorCode, a full battery reached sooner than expected, or a limit it did not accept.

Symptom pages: Communication works but no current flows, Charging is slower than expected and The session stops during charging.

In the analyzer

  • Stage strip: Energy transfer. It runs from PowerDelivery Start (in ISO 15118-20 from the first charge loop request) to PowerDelivery Stop.
  • Checks: PW-01 to PW-04 and CP-07 in Power and cable and Control Pilot, SQ-08 to SQ-10, TIM-01 and TIM-05, and IS20-01 to IS20-05 and IS20-09 for ISO 15118-20.
  • Power tab: the permitted current against the measured one, with the Headroom view. Curve tool: voltage, current and power over the charge. Negotiation tool: what each side announced.
  • Timers tool: every response time against its limit, with the ones close to the limit highlighted.
  • Verdicts: Completed normally, EV stopped early, EVSE stopped, Timeout, FAILED response, CP fault or Connection lost.

Sources

  • DIN SPEC 70121:2014-12, PowerDelivery and CurrentDemand
  • ISO 15118-2:2014, PowerDelivery, CurrentDemand, ChargingStatus, MeteringReceipt, renegotiation, timing tables
  • ISO 15118-20:2022, PowerDelivery, DC_ChargeLoop, AC_ChargeLoop, scheduled and dynamic control, clause 8.3 and 8.4
  • IEC 61851-1:2017, Table A.6, the car following a new limit
  • 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 PowerDelivery and the charge loop with the backend messages beside them