Stage: DC cable check and isolation test
Before any energy flows on DC, the charger puts a test voltage on the cable and measures its insulation to earth. How DIN SPEC 70121, ISO 15118-2 and ISO 15118-20 carry that test, the Ongoing loop, the timers and what makes it fail.
What the stage does
A DC cable carries several hundred volts. Before the charger raises its output to the battery voltage, it checks that neither DC line has a leak to protective earth: a wet connector, a pinched cable or a fault in the car would otherwise put that voltage where people can touch it. The insulation monitor (IMD) of the charger measures while a test voltage sits on the cable, then the charger brings the voltage back down.
- It follows the charge parameter exchange: ChargeParameterDiscovery in DIN SPEC 70121 and ISO 15118-2, DC_ChargeParameterDiscovery and ScheduleExchange in ISO 15118-20.
- Before its first request the car locks the connector and switches the Control Pilot to state C. The charger will not apply the test voltage without it.
- The car repeats the request; the charger answers Ongoing until the measurement is done and then Finished.
- Pre-charge follows. The contactors of the car stay open throughout.
The messages in the three standards
- EV: ChargeParameterDiscoveryReq, the last exchange before the check
- EV: CP state B to C, connector locked, S2 closed
- EV: CableCheckReq, DC_EVStatus with EVReady and EVErrorCode
- EVSE: CableCheckRes, EVSEProcessing Ongoing, EVSEStatusCode EVSE_IsolationMonitoringActive
- both: more CableCheck pairs, until the charger reports Finished
- EVSE: CableCheckRes, EVSEProcessing Finished, EVSEIsolationStatus Valid or Warning
- EV: PreChargeReq, the next stage
| DIN SPEC 70121 and ISO 15118-2 | ISO 15118-20 | |
|---|---|---|
| Request | CableCheckReq with DC_EVStatus | DC_CableCheckReq, header only |
| Response | CableCheckRes with ResponseCode, DC_EVSEStatus and EVSEProcessing | DC_CableCheckRes with ResponseCode and EVSEProcessing |
| Isolation result | EVSEIsolationStatus in DC_EVSEStatus: Invalid, Valid, Warning, Fault (ISO 15118-2 adds No_IMD) | Not in the message; a failed test ends with a FAILED response code |
| Charger state | EVSEStatusCode, for example EVSE_IsolationMonitoringActive, EVSE_Shutdown, EVSE_EmergencyShutdown | Reported in the charge loop, not here |
Timers
| Timer | Limit profile key | Profile default |
|---|---|---|
| Each CableCheck response (V2G_EVCC_Msg_Timeout, general case) | tim.msgTimeoutS | 2 s |
| From a response to the next request (V2G_SECC_Sequence_Timeout) | tim.sequenceTimeoutS | 60 s |
| The whole Ongoing loop (V2G_EVCC_CableCheck_Timeout) | none | not in the profile |
tim.msgTimeoutS and tim.sequenceTimeoutS are flagged for verification. The standards give the cable check loop a timer of its own; the limit profile has no entry for it yet and TIM-02 does not time this loop, so compare its length on the Timing tab against the standard by hand.
What usually breaks
- The car is still in state B. The charger waits for state C and keeps answering Ongoing until the car gives up. The CP state lane shows B through the whole loop.
- Insulation fault or warning: moisture in the connector, a damaged cable, high capacitance or a leak on the car side. EVSEIsolationStatus Fault, or a FAILED response in ISO 15118-20.
- Two insulation monitors measuring at once, the charger and the car, each seeing the other as a leak. Typical sign: one car fails on a charger that passes with others.
- An IMD or contactor fault in the charger: EVSEStatusCode EVSE_Malfunction, EVSE_Shutdown or EVSE_EmergencyShutdown, or the test voltage never builds up.
- The loop simply takes too long and the car stops waiting. Individual answers may be quick (TIM-01 passes) while the loop as a whole runs past the car timer.
The symptom page is DC session stalls in CableCheck or PreCharge; the insulation monitor itself is described in Isolation monitoring and CableCheck.
In the analyzer
- Stage strip: Cable check, on DC sessions, between the parameter stage and Pre-charge. It passes at the first response with EVSEProcessing Finished and an OK response code.
- Checks: SQ-05 for a refused step, TIM-01 for each response, TIM-03 for the gap to the next request, SQ-01 for a request out of order.
- Timing tab: how long the loop ran and how many pairs it took. Message detail of the last CableCheckRes: EVSEProcessing, EVSEIsolationStatus and EVSEStatusCode, each explained in the code dictionary.
- The CP state lane, when a Control Pilot log is loaded, for the change from B to C before the first request.
- Verdicts: FAILED response when the charger refuses the check, Timeout or Connection lost when the car gives up.
Sources
- DIN SPEC 70121:2014-12, CableCheck request and response, DC_EVSEStatus
- ISO 15118-2:2014, CableCheck request and response, EVSEIsolationStatus, timing tables
- ISO 15118-20:2022, DC_CableCheck request and response
- IEC 61851-23, insulation monitoring of a DC charging station