EVSideCableCheck unknown error

How it presents

Symptom

EVSideCableCheck unknown error (CCS-H11) — CCS handshake field fault. Stay OEM-agnostic until the protocol stage pins a hardware path; capture SECC/OCPP/vehicle evidence before opening the cabinet.

Root causes (by observed frequency)

1. #1 Primary ccs handshake cause for CCS-H11: EVSideCableCheck unknown error

   Stage-pin before hardware RMA

2. #2 Cable/vehicle/adapter contribution proven by known-good swap
3. #3 CSMS/SECC/config mismatch after update or board swap
4. #4 True EVSE hardware failure after protocol path is proven clean

Diagnostic procedure

1. 1. Capture CCS handshake stage evidence for CCS-H11 (HMI, OCPP/SECC logs, connector ID)

   Expected: Exact fail stage

   Tools: phone, CSMS, SECC logs

2. 2. Decide one gun vs cabinet vs site vs vehicle cohort

   Expected: Fault boundary

   Tools: CSMS timeline

3. 3. Known-good cable/vehicle prove appropriate to “EVSideCableCheck unknown error”

   Expected: Follows cable/vehicle or stays

   Tools: known-good

4. 4. Correct config/CSMS/SECC settings indicated by the stage

   Expected: Stage advances

   Tools: HMI, CSMS admin

5. 5. Escalate OEM hardware only with stage-pinned evidence pack

   Tools: ticket

The fix

Clear CCS-H11 by pinning the ccs handshake stage and fixing that cause — not shotgun EVSE modules.

• Assembly indicated only after stage pin

  OEM-agnostic until proven

1. Pin the ccs handshake fail stage for CCS-H11 before ordering modules.
2. Correct the ranked cause for “EVSideCableCheck unknown error” (cable, vehicle, config, or CSMS/SECC).
3. Clear latches and restore Availability only after the cause is removed.
4. Validate a full session through the previously failing stage.
5. Attach scrubbed protocol traces and photos to the confirmation ticket.