Fault database
Search by code, symptom, brand, category, or connector. Full procedures gated by subscription — look for green Free sample badges for open procedures.
Viewing as free
8 results
OCPP-F03Cross-brand / Protocol · DC Fast ChargersFree sampleAuthorize rejected — invalid idTag
Authorize rejected — invalid idTag — badge/app presents locally but CSMS returns Invalid/Blocked, or local list is stale after prolonged offline. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F03.
RFID-01Cross-brand / Protocol · DC Fast ChargersFree sampleRFID reader no UID
RFID reader no UID (RFID-01) — RFID / auth field fault. Stay OEM-agnostic until the protocol stage pins a hardware path; capture SECC/OCPP/vehicle evidence before opening the cabinet.
RFID-02Cross-brand / Protocol · DC Fast Chargers solo+RFID works offline but CSMS rejects
RFID works offline but CSMS rejects (RFID-02) — RFID / auth field fault. Stay OEM-agnostic until the protocol stage pins…
RFID-03Cross-brand / Protocol · DC Fast Chargers solo+Local list full — new cards fail
Local list full — new cards fail (RFID-03) — RFID / auth field fault. Stay OEM-agnostic until the protocol stage pins a …
TRI-RTM-AUTHTritium · RTM75 · DC Fast Chargers solo+Auth timeout local list empty
RTM auth timeout local list empty — offline auth cache/CSMS list, not power electronics. Field techs should correlate HM…
AUT-MC-APPAutel · MaxiCharger DC · DC Fast Chargers solo+App start fails OCPP ok
Autel MaxiCharger DC app-initiated sessions fail to start while OCPP Heartbeat continues normally to the CSMS, meaning t…
FLO-ST-AUTHFlo · Smart Two · AC Level 2 solo+Auth card not accepted
Flo Smart Two rejects RFID card or app authorization with a 'card not accepted' message while the station otherwise show…
CMS-AUTHAmpcontrol · Fleet CMSFree sampleFleet CMS driver auth fail
A driver's credential or fleet app is rejected by the Ampcontrol CMS even though the charger hardware and OCPP path both look completely healthy — other drivers may authorize and charge normally at the exact same stall within minutes, which is the clearest signal that this is an enrollment or mapping problem in software rather than a reader or connector fault.