Pulsar GFCI trip

How it presents

Display

Pulsar GFCI trip

Symptom

Pulsar GFCI trip on wallbox (pulsar-plus): myWallbox / LED ring shows WB-PP-GFCI. Techs see session abort or stall Unavailable until the ranked cause is cleared. Correlate Wallbox cloud + OCPP if networked before opening the cabinet.

Root causes (by observed frequency)

1. #1 Moisture or contamination bridging ground-fault sensing on WB-PP-GFCI

   Rain, wash-down, or failed cable boot seals rank highest on outdoor DCFC

2. #2 True equipment ground path open or high-impedance bond at pedestal
3. #3 Nuisance trip from EMI / filter aging after power-module work

Diagnostic procedure

1. 1. Capture myWallbox / LED ring message for WB-PP-GFCI, connector ID, and last successful session time

   Expected: Exact display string + OCPP status/errorInfo if present

   Tools: phone photos (scrubbed), CSMS

2. 2. Pull Wallbox cloud + OCPP if networked; confirm whether Pulsar GFCI trip follows one gun, one cabinet, or the whole site

   Expected: Fault correlates to one path

   Tools: CSMS export, OEM cloud

3. 3. On model pulsar-plus hardware, isolate power quality / protective devices before opening HV for WB-PP-GFCI

   Expected: Voltage in band; no unexpected trips

   Tools: DMM, IR gun, LOTO kit

4. 4. Execute rank-1 cause check for “Pulsar GFCI trip”; swap known-good cable/gun or stall if available

   Expected: Fault moves with cable or stays with cabinet

   Tools: known-good cable, IR, OEM service menu

5. 5. If unresolved, escalate with WB-PP-GFCI evidence pack (HMI photo, OCPP snippet, readings) — Confirm CP duty and breaker before board swap on Pulsar-class

   Tools: ticket template

The fix

Clear WB-PP-GFCI (Pulsar GFCI trip) by correcting the ranked cause on wallbox / pulsar-plus, then run a full validation session.

• Suspect module or controller indicated by rank-1 cause

  OEM wallbox service channel; keep serial for RMA

  WB-PP-GFCI

1. LOTO and verify zero energy per wallbox HV procedure before any bus work
2. Correct rank-1 cause for WB-PP-GFCI; do not shotgun-replace modules
3. Clear fault latches in HMI/CSMS; confirm StatusNotification returns to Available/Preparing as appropriate
4. Run validation: authorize → handshake → ≥5 minutes energy → clean stop; capture MeterValues
5. Document firmware, part lots, and scrubbed HMI photos for confirmations