StatusNotification stuck Faulted after reboot

How it presents

Symptom

StatusNotification stuck Faulted after reboot — CSMS still shows Faulted even though local LEDs look ready, often after a dirty shutdown or uncleared vendor errorInfo. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F01.

Root causes (by observed frequency)

1. #1 Latched vendor errorInfo never cleared after the physical cause was fixed

   Clear cause first, then Availability

2. #2 CSMS cached Faulted state ignoring later Available
3. #3 Connector still electrically Faulted (GF/ISO) while UI looks calm
4. #4 Firmware bug leaving StatusNotification stuck until hard power cycle

Diagnostic procedure

1. 1. Compare local connector state vs CSMS StatusNotification errorCode/info

   Expected: Mismatch or match

   Tools: CSMS + HMI

2. 2. Confirm protective/hardware cause is truly clear (GF/ISO/E-stop)

   Expected: No active latch

   Tools: HMI

3. 3. Send ChangeAvailability Operative only after cause clear

   Expected: Available/Preparing

   Tools: CSMS

4. 4. Hard power cycle only if OEM allows and cause is documented clear

   Expected: Fresh BootNotification

   Tools: LOTO discipline

5. 5. Escalate with websocket traces if Available locally but CSMS stuck

   Tools: pcap/CSMS logs

The fix

Unstick Faulted by clearing the real latch, then reconciling CSMS Availability — not reboot spam.

1. Clear the physical latch/cause before fighting the CSMS icon.
2. Issue ChangeAvailability Operative with connectorId scoped correctly.
3. If CSMS cache is stale, force a fresh StatusNotification via OEM procedure.
4. Avoid blind reboots that mask uncleared protective faults.
5. Attach scrubbed StatusNotification snippets to the confirmation ticket.