An AC session, message by message
An AC charging session in ISO 15118-2 from SessionSetup to SessionStop: how the Control Pilot and the messages work together, what the schedule in ChargeParameterDiscoveryRes means, and where AC sessions typically go wrong.
Two signals at once
On AC the car's onboard charger draws the current; the charging station only switches the supply on and off and states a limit. That limit could reach the car in two ways, through the PWM duty cycle and through the messages. In a digital session the charger holds the duty cycle at 5 percent, which on its own means use digital communication, and gives the current limit in the messages. IEC 61851-1 says that with digital communication the lower of the PWM value and the digital value applies.
The car's request for energy stays analogue: it closes S2, which moves the pilot from state B to state C. Following the pilot and the messages together is the key to reading an AC session.
| Moment | Control Pilot | Messages |
|---|---|---|
| Plug in | A to B; the charger sets 5 percent | None yet: SLAC, SDP, TCP and the app handshake |
| Negotiation | B, 5 percent | SessionSetup to ChargeParameterDiscovery |
| Start | B to C within 250 ms of PowerDeliveryReq Start (CP-07) | PowerDelivery Start |
| Charging | C, 5 percent | The ChargingStatus loop |
| Stop | C to B after PowerDelivery Stop (CP-08) | PowerDelivery Stop |
| End | B, then A at unplug | SessionStop |
The sequence
- EV: SessionSetupReq
- EV: ServiceDiscoveryReq, the response lists AC_single_phase_core or AC_three_phase_core and the payment options
- EV: PaymentServiceSelectionReq, ExternalPayment here; Contract adds PaymentDetails
- EV: AuthorizationReq, repeats while EVSEProcessing is Ongoing
- EV: ChargeParameterDiscoveryReq, AC_EVChargeParameter: EAmount, EVMaxVoltage, EVMaxCurrent, EVMinCurrent, optional DepartureTime
- EVSE: ChargeParameterDiscoveryRes, AC_EVSEChargeParameter: EVSENominalVoltage and EVSEMaxCurrent, and the SAScheduleList
- EV: PowerDeliveryReq, ChargeProgress Start, the chosen SAScheduleTupleID, optional ChargingProfile; the car then closes S2 (state C)
- EVSE: PowerDeliveryRes, the charger closes its contactor on state C and answers
- EV: ChargingStatusReq, has no fields; repeats for the whole charge
- EVSE: ChargingStatusRes, EVSEID, SAScheduleTupleID, optional EVSEMaxCurrent and MeterInfo, ReceiptRequired, AC_EVSEStatus
- EV: MeteringReceiptReq, only when ReceiptRequired was true
- EV: PowerDeliveryReq, ChargeProgress Stop; the car lowers its current and opens S2
- EV: SessionStopReq, Terminate, or Pause to resume later with the same SessionID
ChargingStatusReq carries nothing. In ISO 15118-2 the car states its needs once, in ChargeParameterDiscoveryReq, and the loop only fetches the charger's status. What the car actually draws is visible in a current log, not in the messages. ISO 15118-20 changes that: its AC charge loop carries the power the car draws.
Schedules: the SAScheduleList
- ChargeParameterDiscoveryRes offers up to three schedule tuples, each with an SAScheduleTupleID, a PMaxSchedule and optionally a SalesTariff. The car can limit how many it wants with MaxEntriesSAScheduleTuple.
- A PMaxSchedule is a list of entries. Each starts at a relative time in seconds and gives PMax, the most power the car may draw from then on, as a PhysicalValue in W.
- The charger may answer Ongoing first and send the schedule later, for example while it asks its backend. TIM-02 covers that loop.
- In PowerDeliveryReq Start the car names the tuple it follows and may add a ChargingProfile, its own plan of up to 24 entries, which has to stay at or below the chosen schedule. An unknown tuple is refused with FAILED_TariffSelectionInvalid, a profile above the schedule with FAILED_ChargingProfileInvalid; SQ-08 checks the tuple.
- The charger can ask for a new schedule with EVSENotification ReNegotiation. The car answers with PowerDelivery Renegotiate and a new ChargeParameterDiscovery.
| Schedule | Phases in use | Nominal voltage | Current per phase |
|---|---|---|---|
| PMax 11 000 W | 3 | 230 V | about 16 A |
| PMax 7 400 W | 1 | 230 V | about 32 A |
| PMax 4 140 W | 3 | 230 V | about 6 A |
PW-01 does this conversion to find the permitted current: PMax divided by the nominal voltage and by the number of phases that carried load. The nominal voltage is the one the charger names in EVSENominalVoltage, or pw.nominalVoltageV from the profile when it names none (230 V, 240 V in the North American profile).
Meter values and receipts
ChargingStatusRes may carry MeterInfo: the meter ID, the reading in Wh and an optional signature. With ReceiptRequired true the car answers with MeteringReceiptReq, which repeats the meter data and, with Plug and Charge, is signed with the contract key. SQ-10 checks that the receipt is sent, and PW-04 that the reading never runs backwards. Energy metering and signed meter values covers meters and signed readings in depth.
Where AC sessions go wrong
| Moment | What goes wrong | Checks and articles |
|---|---|---|
| ChargeParameterDiscovery | The charger refuses the car's parameters with FAILED_WrongChargeParameter, as in the ac-failed demo | SQ-05, The charger answers with a FAILED response code |
| After PowerDeliveryReq Start | The car never closes S2, so no current flows | CP-07, Communication works but no current flows |
| Start of current | Current before state C or before PowerDeliveryRes Start: the outlet was live too early | PW-02 |
| The ChargingStatus loop | The car draws more than the lowest limit in force | PW-01, Measured current, permitted current and the cable |
| The ChargingStatus loop | The charger answers later than V2G_EVCC_Msg_Timeout (2 s in the profile) or stops answering | TIM-01, The session stops during charging |
| Stop | The car keeps drawing after PowerDelivery Stop, or the charger keeps its contactor closed after C to B | PW-03, CP-08, The session does not end cleanly |
| Any time | The charger drops to state F or stops the PWM | CP-09, Control Pilot problems |
The 250 ms allowed between PowerDeliveryReq Start and the B to C change (cp.transition.maxDelayAfterPowerDeliveryS) and the message timeouts are flagged for verification in the limit profile.
Sources
- ISO 15118-2:2014, AC message set, SAScheduleList, ChargingProfile, MeterInfo
- IEC 61851-1:2017, Tables A.6 and A.8
- ISO 15118-3:2015, the 5 percent duty cycle and the transition through X1
- ChargeX Consortium: ev-charge-seq-state, Argonne National Laboratory, Apache-2.0: PlantUML sequence diagrams of SAE J1772 PWM charging and ISO 15118-2 AC sessions with OCPP 1.6J and 2.0.1, and ISO 15118-20 AC with OCPP 2.1