Arcbound Field · Field sheet · Cross-brand / Protocol · MET-01
MET-01Energy meter CRC error
Cross-brand / Protocol · DC Fast Chargers
Safety
Qualified EVSE personnel only. Follow site LOTO and OEM HV / arc-flash boundaries. Not a substitute for OEM service manuals or AHJ requirements.
How it presents
- Display
- Energy meter CRC error
- OCPP
- Faulted (StatusNotification) — capture errorCode/info
Symptom
Energy meter CRC error on protocol: CSMS StatusNotification + connector LEDs shows MET-01. Techs see session abort or stall Unavailable until the ranked cause is cleared. Correlate OCPP websocket / SECC / vehicle logs as applicable before opening the cabinet.
Root causes (by observed frequency)
- #1 Most common field cause for Energy meter CRC error (MET-01) on protocol
Stay OEM-agnostic until the protocol stage pins a hardware path
- #2 Installation / commissioning mismatch exposed under load
- #3 Firmware or config drift after update or board swap
Diagnostic procedure
1. Capture CSMS StatusNotification + connector LEDs message for MET-01, connector ID, and last successful session time
Expected: Exact display string + OCPP status/errorInfo if present
Tools: phone photos (scrubbed), CSMS
2. Pull OCPP websocket / SECC / vehicle logs as applicable; confirm whether Energy meter CRC error follows one gun, one cabinet, or the whole site
Expected: Fault correlates to one path
Tools: CSMS export, OEM cloud
3. On hardware, isolate power quality / protective devices before opening HV for MET-01
Expected: Voltage in band; no unexpected trips
Tools: DMM, IR gun, LOTO kit
4. Execute rank-1 cause check for “Energy meter CRC error”; 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. If unresolved, escalate with MET-01 evidence pack (HMI photo, OCPP snippet, readings) — Stay OEM-agnostic until the protocol stage pins a hardware path
Tools: ticket template
The fix
Clear MET-01 (Energy meter CRC error) by correcting the ranked cause on protocol, then run a full validation session.
Suspect module or controller indicated by rank-1 cause
OEM protocol service channel; keep serial for RMA
MET-01
- LOTO and verify zero energy per protocol HV procedure before any bus work
- Correct rank-1 cause for MET-01; do not shotgun-replace modules
- Clear fault latches in HMI/CSMS; confirm StatusNotification returns to Available/Preparing as appropriate
- Run validation: authorize → handshake → ≥5 minutes energy → clean stop; capture MeterValues
- Document firmware, part lots, and scrubbed HMI photos for confirmations
Related entries
Related guides
Field confirmations (3) — subscribers only, one per account.
Missing a sibling fault? Request an entry