Worked example: the cable check fails
The cablecheck-fail demo read step by step: a DIN SPEC 70121 DC session in which the charger runs its insulation test for four rounds, answers CableCheckRes with FAILED and EVSE_Shutdown, and closes the connection.
What you see
- Load the demo Cable check fails (cablecheck-fail): 4.7 s of a DIN SPEC 70121 DC session, from SLAC to the closed TCP connection, without TLS and without a Control Pilot log.
- Stage strip: SLAC, SDP, TCP / TLS, Handshake, Setup and Parameters passed; Cable check failed; Pre-charge, Energy transfer and Stop not reached.
- Two findings, both errors: SQ-05 and TC-02. Everything before the cable check passes, and every response comes within 70 ms (TIM-01).
The verdict
Never charged, FAILED response, likely party EVSE, confidence high. The explanation reads: session stopped, the charger answered CableCheck with FAILED 4.5 s after the start. The chain of evidence is SQ-05, then TC-02.
Reading the capture step by step
- EV: supportedAppProtocolReq, 1.700 s: DIN SPEC 70121 only, SchemaID 1
- EVSE: supportedAppProtocolRes, 1.743 s: OK_SuccessfulNegotiation
- EVSE: ServiceDiscoveryRes, 1.968 s: DC_extended, ExternalPayment
- EVSE: ContractAuthenticationRes, 2.188 s: OK, Finished at the first answer
- EV: ChargeParameterDiscoveryReq, 2.260 s: DC_extended, up to 420 V and 125 A, EVRESSSOC 45 %
- EVSE: ChargeParameterDiscoveryRes, 2.330 s: OK, up to 500 V and 125 A
- EV: CableCheckReq, 2.450 s
- EVSE: CableCheckRes, 2.500 s: OK, Ongoing, EVSE_IsolationMonitoringActive
- both: three more pairs, every 500 ms, the same answer
- EV: CableCheckReq, 4.450 s: the fifth request
- EVSE: CableCheckRes, 4.500 s: FAILED, Finished, EVSE_Shutdown
- EVSE: TCP FIN, 4.700 s: the charger closes the connection
- EV: TCP FIN, 4.720 s
- Up to the cable check the session is orderly: the charger offered the transfer mode the car asked for (SQ-06), the limits of the two sides overlap, and authorization finished at once.
- While the test runs, each CableCheckRes says OK with EVSEProcessing Ongoing and EVSEStatusCode EVSE_IsolationMonitoringActive. That is the normal shape of a cable check that takes a while.
- Open the last CableCheckRes. Its DC_EVSEStatus holds EVSEIsolationStatus Fault and EVSEStatusCode EVSE_Shutdown next to ResponseCode FAILED. The charger measured the insulation, did not like the result and shut its output down.
- SQ-05 reports the refusal: CableCheckRes answered FAILED at 4.500 s. TC-02 adds that the charger closed the connection at 4.700 s without a SessionStop. The car never sent PreChargeReq.
What the cause is
- The charger ended the session, and it said why: its insulation monitor reported a fault on the DC path during the test. The messages name the result, not the place of the fault.
- The tested path runs from the charger output through the cable and connector into the car up to its open contactors. A fault can sit in any of these: moisture or dirt in the connector or inlet, damaged cable insulation, a fault in the charger output stage, or the car side of the inlet.
- A car that keeps its own insulation monitor connected during the test appears to the charger as a lower insulation resistance. Isolation monitoring and CableCheck explains the measurement and why two monitors on one circuit disturb each other.
- The verdict names the charger because the charger refused and closed. That says who stopped the session, not yet which part has the fault.
What to fix
- Read the log of the insulation monitor in the charger at 4.5 s into the session: it holds the measured resistance and the threshold it compared against.
- Swap one part at a time: another car at this charger, this car at another charger, another cable if the cable is detachable. The part that moves the fault is the part to repair.
- Inspect and dry the connector and the vehicle inlet, and test the cable insulation with an insulation tester.
- If only this car fails, ask whether it disconnects its own insulation monitor while the charger tests. Stage: DC cable check and isolation test lists the other ways the stage fails.
How to confirm the fix
- The CableCheckRes loop ends with ResponseCode OK, EVSEProcessing Finished and EVSEIsolationStatus Valid.
- PreChargeReq follows, the Cable check stage passes and SQ-05 reports all responses OK.
- The connection stays open until the car ends the session with SessionStopReq, so TC-02 passes too.
Sources
- DIN SPEC 70121:2014-12, CableCheck, DC_EVSEStatus, EVSEIsolationStatus and EVSEStatusCode
- IEC 61851-23, insulation monitoring of a DC charging station
- SPEC.md of this tool, FR-ENC-05, the failing demo sessions