The session stops during charging

Energy flowed, then the session ended before the car was done. Who stopped first, and how: a stop request, an error code, a notification, a Control Pilot state, a closed connection or silence.

What you see

  • The stage strip reached Energy transfer, and the session ended without the car reaching its target.
  • The verdict is Stopped early, with one of these categories: EVSE stopped, EV stopped early, Connection lost, Timeout, CP fault or FAILED response.

Who stopped, and how

SignalFromWhat it meansCheck
PowerDeliveryReq with ChargeProgress StopCarThe car ends charging: target reached, user request, or a fault. Normal when SessionStop followsVerdict EV stopped early when it does not finish cleanly
EVErrorCode other than NO_ERROR, or EVReady falseCarA car fault, for example FAILED_RESSTemperatureInhibit, FAILED_EVShiftPosition, FAILED_ChargerConnectorLockFault, FAILED_ChargingVoltageOutOfRangeMessage fields; code dictionary
C to B on the Control Pilot without a stop requestCarThe car opened S2CP state lane
EVSENotification StopChargingChargerThe charger asks the car to stop within NotificationMaxDelaySQ-09; verdict EVSE stopped
DC_EVSEStatusCode EVSE_Shutdown, EVSE_EmergencyShutdown, EVSE_Malfunction, EVSE_UtilityInterruptEventChargerThe charger is shutting down or has a faultMessage fields; code dictionary
RCD true in the AC EVSE statusChargerA residual current was detectedMessage fields
State E or F, or the PWM stopsChargerThe charger dropped the Control PilotCP-09; verdict CP fault
TCP RST or FIN before SessionStopResWhoever sent itThe connection was cut without a stopTC-02; verdict Connection lost
A request without a responseChargerThe charger went silent or answered too lateTIM-01; verdict Timeout
A response without a next requestCarThe car went silentTIM-03

The first of these signals in time is the one that matters. A charger that sends StopCharging and then closes the connection stopped the session; a car that stops sending and then gets a reset from the charger caused it.

Timeouts in the charging loop

  • The car waits V2G_EVCC_Msg_Timeout for each answer: 0.25 s for CurrentDemand and 2 s for ChargingStatus in the profile (TIM-01). A charger whose DC loop answers take a few hundred milliseconds now and then will lose some cars.
  • The charger waits V2G_SECC_Sequence_Timeout, 60 s in the profile, for the next request after a response (TIM-03).
  • TIM-05 gives the polling interval of the loop and TIM-06 the spread of response times, which shows a charger that is usually quick but sometimes slow.

All four values are flagged for verification in the limit profile. See Every timer and timeout.

What to check in this tool

  • The verdict and the findings it marks as key.
  • The last ten messages before the end: status fields in the responses, error codes in the requests.
  • The TCP/TLS lane for a reset or close, and the CP state lane for B, E or F.
  • Timing tab for slow answers just before the end.
  • Code dictionary entries for EVSE notifications, DC EV error codes and DC EVSE status codes.

Patterns that come up often

  • A remote stop from the backend, or an authorization that expired, shows as StopCharging from the charger.
  • A charger that derates to zero current for temperature and then stops: current falls in the Power tab before the stop signal.
  • A charger that closes the connection a moment after its last answer, with no notification: Connection lost with the charger as party. Check the charger log for an internal restart.
  • A car that stops after a burst of slow CurrentDemand answers: TIM-01 findings just before the car's stop request.

Sources

  • ISO 15118-2:2014, EVSENotification, DC_EVErrorCode, DC_EVSEStatusCode, timing tables
  • DIN SPEC 70121:2014-12
  • IEC 61851-1:2017, states E and F