The session does not end cleanly
Charging finished, but the end is messy: current keeps flowing after the stop, the car never opens S2, welding detection does not finish, SessionStop is missing or the connection is cut, or a pause turns into a stop.
A clean end
- EV: PowerDeliveryReq, ChargeProgress Stop; on DC the charger ramps down, on AC the car lowers its draw
- EVSE: PowerDeliveryRes
- EV: C to B on the Control Pilot, the car opens S2; on AC the charger then opens its contactor
- EV: WeldingDetectionReq, DC only, repeated while the car checks that its contactors opened
- EVSE: WeldingDetectionRes, EVSEPresentVoltage falling
- EV: SessionStopReq, ChargingSession Terminate
- EVSE: SessionStopRes
- both: TCP connection closed, after the response, by either side
The verdict reads Completed normally when SessionStop was answered and the Control Pilot then went back to B or A, or when no Control Pilot log was loaded to say otherwise. A reset that follows the closing handshake is how many stacks end a connection and does not count against TC-02.
What goes wrong
| What you see | Likely cause | Who | Check |
|---|---|---|---|
| Current still flows seconds after PowerDelivery Stop | On AC the car keeps drawing; on DC the charger does not ramp down | EV on AC, EVSE on DC | PW-03 (3 s in the profile) |
| The pilot stays in C after PowerDelivery Stop | The car does not open S2 | EV | CP-08 |
| Current after the change from C to B | The charger does not open its contactor in time: 100 ms after IEC 61851-1, 3 s after SAE J1772 | EVSE | PW-03 |
| WeldingDetection repeats and the voltage stays high | The charger output is not discharged, it reports a stale EVSEPresentVoltage, or a contactor in the car is welded | Either | The voltage in WeldingDetectionRes over time |
| The car closes the connection after PowerDelivery Stop without SessionStop | The car ends on its own timer or skips the step | EV | TC-02; the verdict Connection lost or EV stopped early |
| SessionStopReq without a response | The charger is already shutting its stack down | EVSE | TIM-01, SQ-02 |
| A pause the charger asked for ends as a stop (ISO 15118-20) | The car terminated instead of pausing | EV | IS20-06 |
| The capture ends before SessionStop | The recording stopped too early | Capture | The verdict Incomplete capture |
The time the car has to stop drawing (pw.currentZeroTimeS, 3 s) and the time the charger has to open its contactor (pw.switchOpenAfterCToBS, 100 ms, 3 s in the North American profile) come from IEC 61851-1:2017 Table A.6; the North American value is flagged for verification against SAE J1772.
Welding detection and unlocking on DC
- After PowerDelivery Stop the charger stops its output and the car opens its DC contactors. The car then repeats WeldingDetectionReq and watches EVSEPresentVoltage: with its contactors open, the voltage on the charger side should fall towards zero once the charger discharges its output.
- If the voltage stays at battery level, the battery is still connected through a contactor that did not open. The car reports a fault and may refuse to charge again until it is serviced.
- If the voltage falls slowly, the discharge circuit of the charger is slow or faulty, or the value in the response is not a live measurement.
- The connector stays locked until the voltage on the cable is safe. A connector that will not unlock after a clean SessionStop usually points at a charger that still measures voltage at its output.
- Not every car runs welding detection through the messages; some go straight from PowerDelivery Stop to SessionStop.
The voltage below which a DC connector may unlock and the time the charger has to discharge its output are set by IEC 61851-23. A commonly quoted threshold is 60 V; check it against the edition you test to. The limit profile has no value for either.
Pause and resume
- ISO 15118-2: SessionStopReq with ChargingSession Pause keeps the SessionID. The car comes back with a SessionSetupReq carrying that SessionID, and the charger answers OK_OldSessionJoined. SQ-11 checks that the ID is reused.
- DIN SPEC 70121 has no pause: its SessionStopReq has no fields.
- ISO 15118-20 pauses with ChargingSession Pause in SessionStopReq, and ChargeProgress Standby in PowerDeliveryReq holds energy transfer within a session. When the charger asked for a pause, IS20-06 checks that the session ends as one.
- A paused session looks like an ending in the capture. Read the ChargingSession field before you call it a stop.
What to check in this tool
- The last rows of the message table, from PowerDelivery Stop on, and who sent the last message.
- The CP state lane after PowerDelivery Stop, for the change from C to B (CP-08).
- The Power tab, with current columns in the Control Pilot log, for current after the stop (PW-03).
- EVSEPresentVoltage in each WeldingDetectionRes, and how fast it falls.
- The TCP/TLS lane for who closed the connection and when, and the Capture tool for a recording that ended early.
Sources
- ISO 15118-2:2014, PowerDelivery, WeldingDetection, SessionStop, pause and resume
- ISO 15118-20:2022, PowerDelivery, SessionStop and pausing
- IEC 61851-1:2017, Table A.6, sequences 7, 8.1, 9.1 and 10.1
- IEC 61851-23, discharge of the output and unlocking on DC