Skip to content

V2G_EVCC_CableCheck_Timeout handling

What is the exact behavior when V2G_EVCC_CableCheck_Timeout (40s) occurs? Chapter 8.8 does not specify this case.

Add requirement similar to DIN 70121:

[V2G-DC-380] At any point in time in the V2G Communication Session while the EVCC monitors the V2G_EVCC_CableCheck_Timer, if V2G_EVCC_CableCheck_Timer is equal or larger than V2G_EVCC_CableCheck_Timeout, the EVCC shall:

  1. without any delay, change to CP State B, if the EVCC is not in CP State B,
  2. terminate the V2G Communication Session, and
  3. close the TCP connection according to [V2G-DC-107].

CableCheck related requirements in ISO15118-2: [V2G2-702] The EVCC shall stop waiting for the Cable Check of the EVSE to finish and stop monitoring the V2G_EVCC_CableCheck_Timer when V2G_EVCC_CableCheck_Timer is equal or larger than V2G_EVCC_CableCheck_Timeout. It shall then apply the error handling as defined in subclause 8.8.

[V2G2-584] The SECC shall respond with CableCheckRes containing “ResponseCode = OK” and "EVSEProcessing=Finished" within V2G_SECC_Msg_Performance_Time according to Table 109, if the processing of the information is successfully passed and cable check is finished. The allowed next request shall be PreChargeReq and the V2G_SECC_Sequence_Timeout is set according to Table 109.

[V2G2-621] The SECC shall respond with CableCheckRes containing “ResponseCode = OK” and "EVSEProcessing=Ongoing" within V2G_SECC_Msg_Performance_Time according to Table 109, if the processing of the information is successfully passed and the Cable Check is ongoing. The allowed next request shall be CableCheckReq and the V2G_SECC_Sequence_Timeout is set according to Table 109.

[V2G2-585] The SECC shall respond with CableCheckRes containing “ResponseCode = FAILED” within V2G_SECC_Msg_Performance_Time according to Table 109, if the processing of the information is not successful.