Equipment category
Fleet CMS
Charge management software and session auth
Faults (9)
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.
CMS-SESSAmpcontrol · Fleet CMS solo+Session not created in CMS
A charging session actually delivers energy at the stall, but the Ampcontrol CMS never creates a corresponding session r…
CMS-OCPPAmpcontrol · Fleet CMS solo+CMS-OCPP mapping wrong connector
The CMS's connector mapping doesn't match reality — a driver plugged into stall A is authorized, billed, and tracked as …
CMS-SCHEDAmpcontrol · Fleet CMS solo+Schedule blocks depot overnight
A CMS charging schedule policy is blocking sessions overnight exactly as configured, so drivers plug in at 2 AM and repo…
CMS-APIAmpcontrol · Fleet CMS solo+API key revoked mid-shift
A CMS or CSMS API key gets revoked or rotated mid-shift, and every integration that depends on it stops working simultan…
CMS-TZAmpcontrol · Fleet CMS solo+Timezone skew mis-schedules
A timezone configuration mismatch causes schedules to fire hours early or late — this most commonly appears right after …
CMS-VEHAmpcontrol · Fleet CMS solo+VIN not in fleet allowlist
A vehicle's VIN isn't in the fleet allowlist, so Plug&Charge or VIN-based authorization fails outright for a new bus or …
CMS-PRICEAmpcontrol · Fleet CMS solo+Tariff push fails — sessions free
A tariff push from the CMS to the CSMS fails silently, so sessions run for free or bill at a stale rate — drivers are ha…
CMS-OFFAmpcontrol · Fleet CMS solo+CMS offline — local fallback weak
When the CMS or its cloud path goes offline, the local fallback authorization is too weak to cover it — chargers refuse …