Equipment categories

DC Fast Chargers

95 entries

# DC fast chargers (field intro) DCFC cabinets and dispensers are the core of public and depot fast charging. This category indexes isolation, ground fault, CCS/NACS handshake, contactor, and power-stage faults across OEMs—always branch by one gun vs whole cabinet before you open HV. ## What you are diagnosing A StatusNotification Faulted string is not a root cause. Rank presentation: weather/GF, CableCheck isolation, latch/SLAC/SDP, cooling derate, site power, or soft-offline. Photograph HMI, connector ID, and peer gun status. Pull OCPP for the fault window. Then pick the subsystem. ## How it presents - Faulted / Unavailable on one connector or the whole stall - Session aborts at CableCheck, PreCharge, or CurrentDemand - Derate banners before hard fault (thermal/cooling) - Multiple cabinets fault together at peak load (site power) Start maps: [OCPP Faulted triage](/guides/ocpp-faulted-triage), [CCS handshake](/guides/ccs-handshake-basics), [site power quality](/guides/site-power-quality-basics). Protocol samples: [CCS-H01](/entries/protocol-ccs-h01-ccs-slac-timeout), [CCS-H03](/entries/protocol-ccs-h03-cable-check-isolation-fail), [OCPP-F01](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot). ## Field discipline 1. One gun vs whole cabinet (or satellite vs power unit). 2. Known-good cable before power-stage blame on ISO/CCS. 3. Measure feeder under load when multi-stall symptoms align. 4. Re-validate CSMS identity after board/modem swaps. 5. Escalate with an evidence pack—not a bare fault code. OEM hubs: [ChargePoint](/brands/chargepoint), [ABB](/brands/abb), [Tritium](/brands/tritium), [Kempower](/brands/kempower), [BTC Power](/brands/btc-power). Browse DCFC faults below. ## Related brand hubs Use OEM hubs when the cabinet family is known: [ChargePoint](/brands/chargepoint), [ABB](/brands/abb), [Tritium](/brands/tritium), [Kempower](/brands/kempower), [BTC Power](/brands/btc-power). Protocol samples remain the fastest crawlable path for cross-brand OCPP/CCS searches. ## What not to do Do not shotgun power modules on a single CableCheck fail. Do not clear protective GF/ISO without a cause. Do not ignore multi-cabinet coincidence—that is usually site power or LMS.

AC Level 2

20 entries

Wallboxes and pedestals

Payment terminals

7 entries

# Payment terminals (field intro) Payment tickets are where a charger that can deliver energy still fails the driver. This category covers PED/credit terminals, RFID readers, host timeouts, and the OCPP Authorize path that sits between the plastic and the power stage. ## Split money from energy If FreeVend or a technician override starts a session, the DC path is not your first stop. If Authorize never succeeds, do not open the power module. Capture whether the failure is reader hardware, host unreachable, idTag rejected, or CSMS config. ## How it presents - “Tap card” / “Present app” then timeout - PED offline / host unreachable / declined - RFID beep without Authorize.conf Accepted - Sessions work on one payment method only Core entries: [PAY-TO](/entries/ingenico-pay-to-payment-terminal-timeout), [OCPP-F03 Authorize](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). Guide: [Metering & payment](/guides/metering-payment). ## Field discipline 1. Prove energy path with approved FreeVend/test mode if policy allows. 2. Note PED model, firmware, and host error string. 3. Confirm network path from PED/EVSE to payment host and CSMS (they can differ). 4. Re-seat reader cables; check for water in outdoor pedestals. 5. Hand off PCI/host declines to payment ops—not OEM power RMA. Browse payment-related faults below. Keep seals intact on fiscal meters when metering is also in play ([MET-01](/entries/protocol-met-01-energy-meter-crc-error)). ## Boundary with metering Wrong kWh with successful payment is a meter/CT path ([MET-01](/entries/protocol-met-01-energy-meter-crc-error)), not a PED RMA. Successful energy with failed Authorize is payment/auth. Keep those tickets separate so the wrong vendor does not get the crate. ## What not to do Do not break fiscal seals. Do not leave FreeVend on as a permanent retail fix. Do not blame the power stage for host declines.

Modem / cellular

5 entries

# Modem / cellular (field intro) Cellular backhaul is why a healthy power stage still looks “down” on the CSMS. This category covers LTE/5G modems, SIM/APN paths, antenna placement, and the DNS/TLS failures that present as Heartbeat timeouts or soft-offline stalls. ## What you are diagnosing Most modem tickets are not “radio dead.” They are APN mismatch after a SIM swap, DNS that cannot resolve the CSMS host, TLS/cert drift after a board change, NAT keepalive killing the WebSocket, or RSSI that collapses when the cabinet door is closed. Photograph the modem LEDs, pull the last BootNotification/Heartbeat window, and decide whether the charger can reach the CSMS at all before you RMA a control board. ## How it presents - Station Available locally, Cloud/CSMS offline - Heartbeat gaps with intermittent sessions - Authorize failures while FreeVend still works (money path ≠ RF path—but both can share the modem) - Multi-stall pads where only cabinets with poor antenna runs fail Start with [NET-C01 DNS](/entries/protocol-net-c01-dns-resolution-failure-to-csms), [OCPP-F02 Heartbeat](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), and [MDM-RSSI](/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet). Broader map: [OCPP Faulted triage](/guides/ocpp-faulted-triage). ## Field discipline 1. Confirm SIM active and APN matches carrier/CPO docs. 2. Resolve CSMS hostname from the cabinet network path. 3. Check RSSI/RSRP with door closed (cabinet attenuation is real). 4. After modem or SBC swap, re-enter CSMS URL, chargeBoxIdentity, and certs. 5. Escalate to site IT when firewall rules block outbound 443/wss to the CSMS. Do not index every weak RSSI as a new antenna part until DNS and APN are proven. Browse faults in this category below. ## Antenna and cabinet reality Metal cabinets attenuate. An RSSI that looks fine with the door open can collapse shut. Route antennas per OEM; avoid coiling spare cable against the sheet metal. After civil work, check that landscapers did not bend or bury the antenna whip. ## What not to do Do not RMA the SBC because Cloud is red before APN/DNS/TLS are proven. Do not assume one working stall proves the pad’s backhaul—antenna runs differ per cabinet.

Contactors & protection

6 entries

Contactors, breakers, GFCI/RCD, surge

Liquid cooling

9 entries

# Liquid cooling (field intro) High-power DC cables and modules dump heat into glycol loops. This category is for flow, pressure, leak-detect, pump, and airlock failures that present as derate banners long before a hard Faulted state. ## What you are diagnosing Cooling faults are often introduced by the last cable swap: air in the loop, wrong fluid, incomplete bleed, or a wet quick-connect that trips leak-detect. Running a pump dry “just to test” destroys seals. Confirm the stall actually has a liquid loop before you bleed anything—air-cooled cabinets still exist. ## How it presents - Overtemperature / flow low / coolant level / pump fault - Power derate under sustained high kW - Glycol smell or puddles at holster - Fault only after recent cable or CDU service Entries: [ABB-T184-COOL](/entries/abb-abb-t184-cool-coolant-flow-low), [TRI-PK-CABLE](/entries/tritium-tri-pk-cable-liquid-cooled-cable-leak-detect). Guide: [Liquid cooling loops](/guides/liquid-cooling-loops). ## Field discipline 1. Stop sessions if leak-detect or visible fluid—contain first. 2. Check level, filter/strainer, pump sound, and quick-connect residue. 3. Bleed per OEM after any open-loop work; document fluid type. 4. Prove with IR on cable/holster under a controlled load when safe. 5. Escalate to OEM after bleed + filter + leak-free known-good cable path. Browse cooling faults below. Pair with brand hubs for [ABB](/brands/abb) and [Tritium](/brands/tritium) when the cabinet is liquid-cooled ultra-fast. ## Cable vs CDU vs module Leak at the holster is usually cable/quick-connect. Flow fault with dry holster points to pump, strainer, or airlock in the CDU. Module overtemp with good flow may be module or sensor—prove flow numbers before the crate. ## What not to do Do not invent coolant chemistry. Do not keep driving sessions on active leak-detect. Do not skip bleed after opening the loop.

Cables & connectors

32 entries

CCS/NACS/CHAdeMO/J1772 cable IR and latch

Power cabinet / LMS

10 entries

# Power cabinet / LMS (field intro) Power cabinets and load-management systems (LMS) decide how many amps each stall may draw. Tickets here look like “charger broken” when the real story is dynamic caps, offline modules in a shared pool, or a cabinet feed that collapses under simultaneous ramp. ## What you are diagnosing LMS can legally command 0 A during peaks. Shared power units (for example Kempower pools) can starve satellites when modules are offline. Site switchgear and transformers create undervoltage that every brand reports differently. Your job is to separate **curtailment**, **cabinet hardware**, and **utility feed** before RMA. ## How it presents - Sessions start then collapse as more stalls plug in - All connectors Available but deliver near-zero power - One power unit’s satellites fail together - Voltage sag under load with healthy idle readings Entries: [LOAD-01](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a), [KEM-SAT-LINK](/entries/kempower-kem-sat-link-satellite-link-to-power-unit-lost). Guides: [site power quality](/guides/site-power-quality-basics), [fleet CMS](/guides/fleet-cms-triage) when schedules/mapping interact with caps. ## Field discipline 1. Ask ops whether LMS/curtailable rates were active in the window. 2. Compare idle vs loaded voltage at the cabinet. 3. Count online modules / available pool kW vs demanded sessions. 4. Confirm connector ID mapping in CSMS for multi-dispenser cabinets. 5. Hand feeder/transformer issues to the electrician with measurements attached. Browse power-cabinet and LMS faults below. Do not condemn a dispenser because the LMS did its job at 17:00. ## Shared vs dedicated power Dedicated cabinets fail alone. Shared power units fail as a group of satellites. LMS fails as a schedule: power returns when the curtail window ends. Write which pattern you saw in the first sentence of the ticket. ## What not to do Do not override LMS without ops approval. Do not condemn dispensers because the pool was empty at peak. Do not skip loaded voltage measurements when the whole pad sags.

BESS

10 entries

Battery energy storage at depot/site

Switchgear

9 entries

Site MV/LV switchgear and transformers

Fleet CMS

9 entries

Charge management software and session auth