Brands

ABB

12 published entries

# ABB — field brand hub ABB DCFC tickets in this corpus cluster on **Terra 54** (dual-standard CCS/CHAdeMO) and **Terra 184** (higher power, liquid-cooled). Both speak OCPP to whatever CSMS the site runs; HMI strings and ABB Connected Services still matter for board-level work. Name the family and the gun before you condemn a power module. ## When this OEM shows up / cabinet vs dispenser Terra 54 is a compact dual-standard package: CCS and often CHAdeMO share the cabinet. Faults that hit **only CHAdeMO** while CCS stays Available are connector/CAN/lock path — not a full power-stage condemnation. Terra 184 separates high-power modules and cooling more clearly; cable/coolant issues can look like “module fault” until you prove flow and isolation. **Gun / SECC / latch side:** CCS latch fail, CHAdeMO no-start, isolation at CableCheck, temp sensor open on the connector path. **Power / cooling / grid side:** coolant flow low, power module imbalance, grid undervoltage, OCPP disconnect under peak load, energy register anomalies. **HMI / controller side:** frozen Fault banner, boot loop after FW flash — often recoverable without module RMA if you preserve logs first. Photograph the display code, connector number, and whether the peer gun still works before opening covers. Do not condemn a power module because CableCheck failed once in the rain. On dual-standard pads, always record **which gun** faulted — see [/guides/chademo-legacy](/guides/chademo-legacy) and [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics). ## How faults typically present ### HMI - Terra fault banner + service-menu code (ABB-T54-* / ABB-T184-*). - HMI frozen on Fault while Controllers still heartbeat to Connected Services — photograph before reboot. - Boot loop after flash: do not keep power-cycling; capture version and USB/log dump if entitled. ### OCPP / Connected Services - `StatusNotification` Faulted with ABB `vendorErrorCode` / `info` — log verbatim. - Peak-hour OCPP disconnect with energy still flowing briefly, then stall Unavailable: backhaul or modem path, not always a power module. - Energy register jump: metering path — separate from isolation ([/guides/metering-payment](/guides/metering-payment)). - Heartbeat alive with stale Faulted status: use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). ### Physical cues - Latch not seating, glycol at holster (184), CHAdeMO lock motor noise, water at cable glands, E-stop daisy-chain chatter. ## Ranked common failure patterns ### Terra 54 1. **Isolation error before charge** — Cable/gun IR, wet connectors, or true bus isolation. Swap known-good cable before stack RMA. Entry: [/entries/abb-abb-t54-iso-isolation-error-before-charge](/entries/abb-abb-t54-iso-isolation-error-before-charge). Stage map: [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail). 2. **CCS connector latch fail** — Debris, bent latch, actuator, or feedback. Prove cable + vehicle before SECC board swap. Entry: [/entries/abb-abb-t54-ccs-ccs-connector-latch-fail](/entries/abb-abb-t54-ccs-ccs-connector-latch-fail). If latch is fine but SLAC dies: [/entries/protocol-ccs-h01-ccs-slac-timeout](/entries/protocol-ccs-h01-ccs-slac-timeout), [/entries/protocol-ccs-h02-sdp-failed-secc-not-responding](/entries/protocol-ccs-h02-sdp-failed-secc-not-responding). 3. **CHAdeMO side no start** — Lock, CAN, or vehicle profile; do not swap CCS parts for CHA codes. Entry: [/entries/abb-abb-t54-cha-chademo-side-no-start](/entries/abb-abb-t54-cha-chademo-side-no-start). Related: [/entries/protocol-cha-h01-chademo-can-timeout](/entries/protocol-cha-h01-chademo-can-timeout), [/entries/protocol-cha-h02-chademo-connector-lock-fail](/entries/protocol-cha-h02-chademo-connector-lock-fail). 4. **Grid undervoltage trip** — Upstream PQ / feeder before module blame. Idle voltage lies — measure under load. Entry: [/entries/abb-abb-t54-grid-grid-undervoltage-trip](/entries/abb-abb-t54-grid-grid-undervoltage-trip). Guide: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). 5. **HMI frozen on Fault** — Soft hang; pull Connected Services event first, then controlled reset per OEM. Entry: [/entries/abb-abb-t54-hmi-hmi-frozen-on-fault](/entries/abb-abb-t54-hmi-hmi-frozen-on-fault). Stuck Faulted after reboot: [/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot). 6. **Boot loop after FW flash** — Incomplete flash, media, or config; preserve logs for OEM. Entry: [/entries/abb-abb-t54-fw-boot-loop-after-fw-flash](/entries/abb-abb-t54-fw-boot-loop-after-fw-flash). 7. **Temp sensor open circuit** — Harness/connector before condemning thermal plant. Entry: [/entries/abb-abb-t54-sens-temp-sensor-open-circuit](/entries/abb-abb-t54-sens-temp-sensor-open-circuit). ### Terra 184 1. **Coolant flow low** — Filter, airlock, pump, sensor spoof (flow=0 with pump audible). Never run the pump dry “for a minute” to test. Entry: [/entries/abb-abb-t184-cool-coolant-flow-low](/entries/abb-abb-t184-cool-coolant-flow-low). Guide: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). Airlock after fill: [/entries/site-generic-cool-air-airlocked-loop-after-fill](/entries/site-generic-cool-air-airlocked-loop-after-fill). 2. **Power module imbalance** — Confirm which stage and current-share before full bank swap. Entry: [/entries/abb-abb-t184-pm-power-module-imbalance](/entries/abb-abb-t184-pm-power-module-imbalance). 3. **OCPP disconnect after peak** — Cellular/Ethernet under load; prove RSSI and CSMS path. Entry: [/entries/abb-abb-t184-com-ocpp-disconnect-after-peak](/entries/abb-abb-t184-com-ocpp-disconnect-after-peak). Related: [/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms). 4. **E-stop loop intermittent** — Loose mushroom, daisy-chain aux, moisture in enclosure. Entry: [/entries/abb-abb-t184-estop-e-stop-loop-intermittent](/entries/abb-abb-t184-estop-e-stop-loop-intermittent). 5. **Energy register jump** — Meter CRC / mid-meter path, not isolation. Entry: [/entries/abb-abb-t184-met-energy-register-jump](/entries/abb-abb-t184-met-energy-register-jump). Related: [/entries/protocol-met-01-energy-meter-crc-error](/entries/protocol-met-01-energy-meter-crc-error). ## Log sources / tools | Source | What you pull | |--------|----------------| | Terra HMI / service menu | Fault banner, gun ID, coolant/flow, module map | | ABB Connected Services | Event timeline, FW, serial | | OCPP CSMS | StatusNotification, MeterValues, Heartbeat gaps | | IR gun / DMM / megger | Latch heat, PE, IR, phase voltages | | Known-good CCS / CHAdeMO cable | Moves fault with cable vs stack | For cooling tickets: level, pressure/flow, pump run sound, and photos of fittings after any cable swap. Insulation testing only inside OEM procedure and LOTO. ## Field checklist (first 15 minutes) 1. Photo HMI + connector ID + peer gun status. 2. Terra 54 or Terra 184? One gun or whole cabinet? 3. Weather / recent cable or coolant work? 4. Pull OCPP StatusNotification for the stall window. 5. If ISO/CCS: dry + known-good cable before opening HV. 6. If cooling (184): level, leaks, filter, pump sound — then bleed procedure. 7. If soft-offline: ping path to CSMS, DNS, cert dates — not antenna first. ## When to escalate **Electrician / site power** — Undervoltage / phase events matching Terra grid codes; feeder or transformer issues during multi-stall peaks; E-stop daisy-chain or fire-panel inhibit outside the cabinet. **Network / CSMS** — Peak OCPP disconnects with healthy power stage; wrong chargePointIdentity / URL after board work; meter discrepancies that are host/CSMS mapping, not hardware; Authorize rejects with healthy energy path ([/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag)). **ABB OEM** — Confirmed module imbalance after share/grid proven; coolant pump/sensor with OEM fill procedure already followed; boot-loop / FW latch with Connected Services package attached; SECC/latch actuator confirmed after known-good cable and vehicle. Do not escalate “CHA no start” as a CCS latch RMA, or coolant flow low as a module imbalance without flow evidence. Payment-only failures belong to the PED/billing stack, not the Terra power stage ([/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout)).

Alpitronic

4 published entries

Hypercharger HYC300 module banks share coolant. One low-flow or offline module bank can cascade derates across stalls. Payment-offline and grid overvoltage are separate paths — do not combine tickets.

Ampcontrol

9 published entries

# Ampcontrol / fleet CMS field hub Ampcontrol-class depot CMS issues are **software-shaped**: auth, schedules, connector maps, API keys, tariffs. Hardware is often fine. ## Ownership - **CMS admin / fleet ops:** enrollment, schedules, TZ, tariffs, API keys. - **CSMS admin:** OCPP Authorize and connector IDs. - **EVSE tech:** prove energy path with approved test; catch mis-maps that send LOTO to the wrong stall. - **IT:** WAN path when CMS offline. ## Ranked patterns 1. **Auth / VIN allowlist** — CMS-AUTH, CMS-VEH. 2. **Wrong connector map** — CMS-OCPP (fix before more truck rolls). 3. **Schedule / timezone** — CMS-SCHED, CMS-TZ. 4. **Session not in CMS / tariff / API / offline fallback** — CMS-SESS, CMS-PRICE, CMS-API, CMS-OFF. ## Guides [Fleet CMS triage](/guides/fleet-cms-triage) · [OCPP Faulted](/guides/ocpp-faulted-triage) · [Metering & payment](/guides/metering-payment) Browse Ampcontrol entries below or [database](/database?brand=ampcontrol).

Autel

4 published entries

MaxiCharger DC dual-port thermal and NACS latch codes. App-start failures with healthy OCPP are usually auth mapping, not power stage.

BTC Power

5 published entries

# BTC Power — field brand hub BTC **HP150**-class cabinets show up on public and fleet pads with CCS and NACS paths. Tickets cluster around isolation, door/interlock bounce, OCPP reconnect storms after cellular drop, and PFC under sustained load. Most wasted truck rolls happen when a tech swaps PFC modules before checking **cabinet↔dispenser CAN**, door switch state, or backhaul. ## When this OEM shows up / cabinet vs dispenser HP150-class units are often an integrated service envelope, but ownership still splits in practice: **Dispenser / connector path:** NACS adapter path fault, CCS handshake issues, local display messaging. **Cabinet power path:** isolation trip, input PFC fault. **Interlock / enclosure:** service door switch bounce — chatter that latches Faulted without a true power failure. **Link / network:** OCPP reconnect storm; also prove cabinet↔dispenser CAN before PFC RMA (same lesson as other split architectures). Apply the rule: **one gun vs whole cabinet**. Isolation after a cable swap is cable until proven otherwise. Photograph HMI string, connector ID, and door/switch state before you call it a power-module failure. ## How faults typically present ### Local display / LED bank - BTC-HP-* codes on local display or LED bank. - Door bounce: intermittent Faulted that clears when the door is reseated — do not call it isolation yet. - Isolation trip: often at CableCheck / plug-in; mid-session trip needs MeterValues curve. ### OCPP / CSMS - Reconnect storms: Available → Offline → Faulted churn; Heartbeat gaps. Triage: [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage), [/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms). - Isolation / PFC usually land as Faulted with GroundFailure / InternalError / vendor string — log `vendorErrorCode` verbatim. - NACS path: may fail Authorize/handshake while CCS on the sibling connector works — use [/guides/nacs-field-notes](/guides/nacs-field-notes). ### Cloud / PLC event list - BTC CSMS + cabinet PLC event list before wrenching. Correlate timestamps with modem drops vs door opens vs plug events. ### Physical cues - Door seals, water ingress, hot cable at high SOC ramp, debris in inlets, antenna connectors loose after service. ## Ranked common failure patterns 1. **HP150 isolation trip** — Cable/gun IR or wet path before PFC condemnation. Entry: [/entries/btc-power-btc-hp-iso-hp150-isolation-trip](/entries/btc-power-btc-hp-iso-hp150-isolation-trip). Stage: [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail), [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics). 2. **Service door switch bounce** — Misaligned latch, worn switch, vibration. Reseat, adjust, replace switch before board hunts. Continuity on the loop with the door closed and latched. Entry: [/entries/btc-power-btc-hp-door-service-door-switch-bounce](/entries/btc-power-btc-hp-door-service-door-switch-bounce). 3. **OCPP reconnect storm** — Cellular drop, NAT keepalive, wrong URL/identity after SIM/board swap. Entry: [/entries/btc-power-btc-hp-ocpp-ocpp-reconnect-storm](/entries/btc-power-btc-hp-ocpp-ocpp-reconnect-storm). Modem path: [/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet](/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet). 4. **NACS adapter path fault** — Adapter/latch/SECC/vehicle profile; prove with known-good path and CCS sibling if present. Entry: [/entries/btc-power-btc-hp-nacs-nacs-adapter-path-fault](/entries/btc-power-btc-hp-nacs-nacs-adapter-path-fault). Related: [/entries/protocol-nacs-h01-nacs-handshake-timeout-on-adapter-path](/entries/protocol-nacs-h01-nacs-handshake-timeout-on-adapter-path), [/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero](/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero). 5. **Input PFC fault** — After grid/phase proven under load. Entry: [/entries/btc-power-btc-hp-pfc-input-pfc-fault](/entries/btc-power-btc-hp-pfc-input-pfc-fault). PQ: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). 6. **Handshake before current** — Latch/SLAC/SDP failures with healthy DC bus: [/entries/protocol-ccs-h01-ccs-slac-timeout](/entries/protocol-ccs-h01-ccs-slac-timeout), [/entries/protocol-ccs-h02-sdp-failed-secc-not-responding](/entries/protocol-ccs-h02-sdp-failed-secc-not-responding), [/entries/protocol-ccs-h04-precharge-voltage-mismatch](/entries/protocol-ccs-h04-precharge-voltage-mismatch). 7. **Ground / PE outdoor** — Rain and wash-down at glands/boots ([/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser)). 8. **Stuck Faulted after reboot** — Software latch, not endless power cycles ([/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot)). ## Log sources / tools | Source | What you pull | |--------|----------------| | Local display / LEDs | Live code, door/E-stop state | | Cabinet PLC event list | Door, CAN, PFC, isolation timestamps | | CSMS / OCPP | Reconnect timeline, StatusNotification, MeterValues | | Modem stats | RSRP, APN, disconnect counters | | Known-good cable / NACS path | Moves isolation or NACS fault | | DMM / megger | PE, IR, input phases; interlock loop continuity | ## Field checklist 1. One gun or whole cabinet? 2. Door/interlock state photographed? 3. Weather / recent cable or modem work? 4. OCPP StatusNotification snippet for the stall window 5. Dry + known-good cable if ISO 6. Feeder voltage under load if multi-stall pad 7. CAN / link health before PFC module RMA ## When to escalate **Electrician / site power** — Phase loss / undervoltage matching PFC trips; PE issues on isolation tickets that fail megger at pedestal; breaker/feeder work. **Network / CSMS** — Reconnect storms with modem/CSMS evidence; identity/URL after SIM work; auth-only failures with healthy energy path ([/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag)). **BTC OEM** — PFC module after grid + CAN proven; isolation path confirmed cable-independent (stays with cabinet); door switch hardware after bounce documented and adjustment failed; NACS path after known-good adapter/vehicle proven. Do not escalate door bounce or reconnect storms as PFC RMA. Do not swap modules for NACS adapter faults until the adapter/SECC path is proven. Payment-only: [/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout). Public HP150 pads and depot installs share the same triage order: presentation → one-gun vs cabinet → cable/ISO → interlock → power → network. Write that order into the ticket so the next tech does not restart at module RMA. Keep PE continuity and door-switch photos in every outdoor BTC ticket; wash-down and latch bounce are still the majority of “mystery Faulted” callbacks. Keep PE continuity and door-switch photos in every outdoor BTC ticket; wash-down and latch bounce are still the majority of “mystery Faulted” callbacks. Keep PE continuity and door-switch photos in every outdoor BTC ticket; wash-down and latch bounce are still the majority of “mystery Faulted” callbacks.

Blink

4 published entries

# Blink — field brand hub Blink **IQ 200** AC pedestals/wall units dominate these tickets. Ownership is the station enclosure (relay, RFID, boot/firmware) plus Blink network reachability — not a DC power cabinet. Pedestal owns GFCI/relay, connector, and local controller. CPO/Blink network owns auth backend. Site owns PE and feeder. A “station offline” ticket is often cellular/Wi-Fi or CSMS — not a dead power board. ## When this OEM shows up Common calls: network offline (app/CSMS red), RFID intermittent, relay welded after high-cycle use, boot loop after OTA. Confirm whether the stall has AC power and a live Blink backhaul before condemning the relay. Photograph LEDs and capture OTA version before you force another update. ## How faults present - Local LEDs / HMI: boot loop, solid fault, RFID no-beep. - Blink network / CSMS: offline, Faulted, or Available but Authorize rejects. Triage Faulted with [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Cloud: OTA history matters — boot loops often follow updates. - Soft-offline with Heartbeat gaps points at modem/APN/DNS before board RMA ([/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms)). ## Ranked failure patterns 1. **Blink network offline** — Modem/Ethernet/DNS/TLS before board RMA. Entry: [/entries/blink-blk-iq-net-blink-network-offline](/entries/blink-blk-iq-net-blink-network-offline). 2. **RFID intermittent** — Reader seating, harness, moisture. Entry: [/entries/blink-blk-iq-rfid-rfid-intermittent](/entries/blink-blk-iq-rfid-rfid-intermittent). Related: [/entries/protocol-rfid-01-rfid-reader-no-uid](/entries/protocol-rfid-01-rfid-reader-no-uid), [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). 3. **IQ200 relay welded** — Stuck closed/open after cycling; prove with known-good EV and measure contactor side. Entry: [/entries/blink-blk-iq-relay-iq200-relay-welded](/entries/blink-blk-iq-relay-iq200-relay-welded). 4. **Boot loop after update** — Preserve version; do not keep force-updating. Entry: [/entries/blink-blk-iq-boot-boot-loop-after-update](/entries/blink-blk-iq-boot-boot-loop-after-update). Stuck Faulted after reboot: [/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot). ## Logs / tools Blink portal / CSMS screenshots, OTA version, LED photos, DMM on relay/output, RFID test card, modem link lights, PE continuity. ## Escalate when - **Electrician:** Supply/breaker issues, welded relay needing licensed swap per site policy, shared parking-lot circuit trips. - **Network/Blink ops:** Prolonged offline with good local power; identity/URL after board swap; bad OTA cohort; auth-only failures. - **OEM:** Confirmed relay/board/boot-loop hardware with version package. Do not swap relays for network-offline tickets. ## Field checklist 1. Confirm AC present at the pedestal and breaker not tripped. 2. Is the complaint offline, auth, or no energy after authorize? 3. Photo LEDs + capture OTA/firmware version before another update. 4. Pull Blink/CSMS timeline for Heartbeat gaps vs Authorize rejects. 5. RFID test with known-good credential; reseat reader harness if intermittent. 6. If relay suspected: known-good EV, measure output side per site LOTO rules. 7. Do not swap the relay for a network-offline ticket. Persistent GFCI/ground after dry known-good cable still belongs with PE verification ([/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser)) before OEM board talk.

ChargePoint

13 published entries

# ChargePoint — field brand hub Public and fleet DCFC tickets here are almost always **Express 250** (air-cooled dual-standard) or **Express Plus** (high-power, liquid-cooled, NACS-capable). Start by naming the platform before you open a power section. Codes and ownership paths differ, and Express Plus liquid-cooling triage does not transfer to Express 250 air paths. ## When this OEM shows up / cabinet vs dispenser ChargePoint Express sites split work between a **power cabinet** (PFC / power bricks, fans or coolant skid, contactors, door interlocks) and a **dispenser** (HMI, RFID/payment, connectors, SECC path). Many “station down” tickets are dispenser-side or link-side while the cabinet is healthy. **Own on the dispenser first:** RFID, payment authorize, HMI, gun latch/overtemp, cable IR after a swap. **Own on the cabinet first:** PFC overcurrent, power brick offline, module fans, coolant pump, HDC weld detect, door interlock, site LMS curtail. **Own the link before either RMA:** dispenser↔cabinet CAN loss looks like a dead stall on Cloud and HMI. Prove the bus before condemning a brick. Photograph which side drops first and whether sibling dispensers on the same cabinet still talk. Express Plus adds liquid cooling and NACS. Confirm cable serial and coolant state on Plus before any power-brick RMA. On dual-standard Express 250 pads, record which gun (CCS vs CHAdeMO) faulted. ## How faults typically present ### HMI / station UI - Red banner or fault code on the dispenser (CP-E250-* / CP-XP-* style strings in Cloud often map 1:1). - Connector LEDs may still look “ready” while the stall is Unavailable — trust Cloud / OCPP status over cosmetics. - Door open / interlock: cabinet may refuse to start with little more than a door icon; photograph the latch and switch state before you call it a power fault. - Soft derate with no hard banner: fans, coolant, or LMS — pull Cloud timeline before assuming “working.” ### OCPP / CSMS - `StatusNotification` → Faulted or Unavailable with `vendorErrorCode` / `info` carrying the real ChargePoint string — log it verbatim. - Mid-session drop to 0 A + Faulted: isolation, GF, HDC, PFC, or cooling latch — use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Payment path: Authorize timeout or ReaderFailure while energy path is idle — split money from kWh ([/guides/metering-payment](/guides/metering-payment)). - After reboot: Available → Preparing → Faulted again is a hard latch, not “needs another reboot” ([/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot)). ### ChargePoint Cloud - Cloud event timeline usually beats HMI alone. Pull the stall’s last successful session, firmware, and the exact code before you LOTO. - Multi-stall pads: confirm whether one dispenser, one cabinet, or the whole pad shares the event. - Keep timestamps matched between Cloud export and phone photos of the HMI. ## Ranked common failure patterns ### Express 250 1. **Ground fault under rain / wash-down** — Moisture bridging GF sensing or bad cable boot seals. Do not keep resetting. Dry, inspect boots, measure PE. Entry: [/entries/chargepoint-cp-e250-gf-ground-fault-trip-under-rain](/entries/chargepoint-cp-e250-gf-ground-fault-trip-under-rain). Site PE path: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **Isolation after cable swap** — New cable/gun IR or wet connectors presenting as cabinet isolation. Swap known-good cable before power-stage blame. Entry: [/entries/chargepoint-cp-e250-iso-isolation-fault-after-cable-swap](/entries/chargepoint-cp-e250-iso-isolation-fault-after-cable-swap). Protocol stage: [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics), [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail). 3. **Dispenser–cabinet CAN loss** — Stall looks dead; Cloud may show InternalError / Unavailable. Check terminators, harness, grounding, and which side drops first. Entry: [/entries/chargepoint-cp-e250-comm-dispenser-cabinet-can-loss](/entries/chargepoint-cp-e250-comm-dispenser-cabinet-can-loss). 4. **Power module fan fail** — Filters, blocked inlets, or dead fans before sensor swaps. Entry: [/entries/chargepoint-cp-e250-fan-power-module-fan-fail](/entries/chargepoint-cp-e250-fan-power-module-fan-fail). 5. **Door interlock open** — Misaligned latch, sticky switch, service door left ajar. Entry: [/entries/chargepoint-cp-e250-door-cabinet-door-interlock-open](/entries/chargepoint-cp-e250-door-cabinet-door-interlock-open). 6. **PFC stage overcurrent** — Prove grid / phase / upstream trips with [/guides/site-power-quality-basics](/guides/site-power-quality-basics) before module RMA. Entry: [/entries/chargepoint-cp-e250-pfc-pfc-stage-overcurrent](/entries/chargepoint-cp-e250-pfc-pfc-stage-overcurrent). 7. **HDC contactor weld detect** — High-cycle depots; verify aux feedback before shotgun contactors. Entry: [/entries/chargepoint-cp-e250-hdc-hdc-contactor-weld-detect](/entries/chargepoint-cp-e250-hdc-hdc-contactor-weld-detect). 8. **Station RFID unresponsive** — Reader/harness/config after board work; not a PFC problem. Entry: [/entries/chargepoint-cp-e250-rfid-station-rfid-unresponsive](/entries/chargepoint-cp-e250-rfid-station-rfid-unresponsive). Related: [/entries/protocol-rfid-01-rfid-reader-no-uid](/entries/protocol-rfid-01-rfid-reader-no-uid). ### Express Plus 1. **Liquid cooling pump fail** — Airlock, low level, pump, or sensor after cable/service. Entry: [/entries/chargepoint-cp-xp-cool-liquid-cooling-pump-fail](/entries/chargepoint-cp-xp-cool-liquid-cooling-pump-fail). Loop triage: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). Airlock after fill: [/entries/site-generic-cool-air-airlocked-loop-after-fill](/entries/site-generic-cool-air-airlocked-loop-after-fill). 2. **NACS port overtemp** — Handle/pins, airflow, repeated high-power sessions. Entry: [/entries/chargepoint-cp-xp-nacs-nacs-port-overtemp](/entries/chargepoint-cp-xp-nacs-nacs-port-overtemp). NACS path: [/guides/nacs-field-notes](/guides/nacs-field-notes), [/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero](/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero). 3. **Power brick offline** — One brick offline derates the stall; confirm which brick and link health before full bank swap. Entry: [/entries/chargepoint-cp-xp-mod-power-brick-offline](/entries/chargepoint-cp-xp-mod-power-brick-offline). 4. **Site LMS curtails Express Plus** — Budget / CT map / LMS heartbeat, not a dead brick. Entry: [/entries/chargepoint-cp-xp-lms-site-lms-curtails-express-plus](/entries/chargepoint-cp-xp-lms-site-lms-curtails-express-plus). Related: [/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a). 5. **Payment authorize timeout** — PED/host path separate from energy. Entry: [/entries/chargepoint-cp-xp-pay-payment-authorize-timeout](/entries/chargepoint-cp-xp-pay-payment-authorize-timeout). Related: [/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout). ## Log sources / tools | Source | What you pull | |--------|----------------| | ChargePoint Cloud / CSMS | Event codes, firmware, last good session, connector ID | | Station HMI | Live banner, service menus if entitled | | OCPP export | StatusNotification, MeterValues, Authorize timeline | | Cabinet service UI / LEDs | Brick online map, fan/coolant, door/E-stop | | Multimeter / IR / megger | PE continuity, IR after cable swap, hotspot on NACS | | Known-good cable / gun | Moves isolation vs stays with cabinet | ## Field checklist (first 15 minutes) 1. Express 250 or Express Plus? Name it on the ticket. 2. One dispenser, one cabinet, or whole pad? 3. Photo HMI + Cloud code + connector ID. 4. Weather / recent cable or coolant work? 5. If ISO/GF: dry + known-good cable before HV. 6. If soft-offline: Heartbeat path and Cloud reachability before brick RMA. 7. If Plus thermal: coolant level/flow/pump sound before module swap. ## When to escalate **Electrician / site power** — Feeder undervoltage, phase loss, breaker trips correlating with PFC / GF; PE open at pedestal; LMS / CT wiring after site expansion. **Network / CSMS ops** — Cloud offline with healthy cabinet power; OCPP URL / identity / cert after board or SIM swap; Authorize storms or payment host declines with healthy energy path; LMS policy capping stalls to 0 A during revenue hours. **ChargePoint OEM / RMA** — Confirmed brick/PFC/HDC after grid and link proven; coolant pump or sensor path with flow/pressure evidence; firmware-related latch with Cloud package attached. Do not open an RMA for LMS curtail, rain GF without dry-out/PE check, or CAN loss without bus evidence.

Cross-brand / Protocol

67 published entries

OCPP, CCS, NACS, ISO 15118, and CHAdeMO patterns that cross OEMs. Start here when the stage of fail is clear but the cabinet brand is not.

Delta

4 published entries

UFC100-class: ground fault, backend unreachable, exhaust fan, and connector lock motor. Verify grid and fan path before isolation RMA.

EVBox

4 published entries

# EVBox — field brand hub EVBox **Livo** AC chargers appear on workplace and fleet Level 2 sites, often with load-balancing groups. Ownership is the unit (RCD, cable lock, OCPP stack) plus site load-manager behavior — not a DC cabinet. Confirm LMS/group policy before calling the charger dead when MeterValues sit at 0 A. ## When this OEM shows up Expect nuisance RCD trips, cable lock stuck, OCPP disconnects, and load-balance commands that drive the stall to **0 A** while the unit looks “online.” Unit owns RCD, lock actuator, and local controller. Site/ops owns load-balance setpoints and backhaul. Electrician owns PE and feeder. ## How faults present - Local UI/LEDs: RCD trip, lock error, fault. - OCPP: disconnect / Faulted; or Available with MeterValues at 0 A under load balance. Faulted path: [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). Zero-amp policy: [/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a). - Cloud / CSMS: group load-balance setpoints and reconnect history. - Physical: ice/debris in lock, wet glands after wash-down, antenna/Ethernet after remodel. ## Ranked failure patterns 1. **RCD trip nuisance** — Moisture, EV leakage, aging RCD; do not keep resetting without cause. Entry: [/entries/evbox-evb-lv-rcd-rcd-trip-nuisance](/entries/evbox-evb-lv-rcd-rcd-trip-nuisance). PE: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **Load balance zero amps** — Group budget / priority, not a dead contactor. Entry: [/entries/evbox-evb-lv-load-load-balance-zero-amps](/entries/evbox-evb-lv-load-load-balance-zero-amps). 3. **Livo OCPP disconnect** — Backhaul/TLS/identity. Entry: [/entries/evbox-evb-lv-com-livo-ocpp-disconnect](/entries/evbox-evb-lv-com-livo-ocpp-disconnect). Related: [/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms). 4. **Cable lock stuck** — Mechanical debris, actuator, ice. Entry: [/entries/evbox-evb-lv-lock-cable-lock-stuck](/entries/evbox-evb-lv-lock-cable-lock-stuck). ## Logs / tools CSMS load-balance logs, StatusNotification/Heartbeat, LED photos, RCD trip count, manual lock release per OEM, DMM on PE, known-good cable if lock allows. ## Escalate when - **Electrician:** Persistent RCD with measured leakage/PE issues; supply faults. - **Network/ops:** OCPP identity/URL; load-balance policy starving stalls. - **OEM:** Lock actuator or RCD hardware after site causes cleared. Do not replace chargers for load-balance zero-amp events. ## Field checklist 1. Is MeterValues at 0 A while status stays Available? Check load-balance setpoints first. 2. Photo local UI and note RCD trip count / lock state. 3. Pull CSMS group load-balance log for the stall window. 4. If RCD: dry, inspect glands/cable, measure PE — do not keep resetting. 5. If OCPP disconnect: Heartbeat/DNS/TLS before board RMA. 6. If lock stuck: debris/ice/manual release per OEM before actuator RMA. 7. Confirm sibling Livo units in the same group still get amps. A whole group starved of amps is ops policy, not ten dead contactors. Use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) only when the stall is actually Faulted.

Eaton

8 published entries

# Eaton switchgear / PQ field hub Eaton gear on charging sites creates tickets that look like “all chargers failed.” Start at the **one-line and breaker**, not the first EVSE HMI. ## Ownership - **Electrician / PQ:** breakers, GF, arc-flash, transformers, CTs, UPS controls. - **EVSE tech:** timestamp correlation, LMS/session coincidence, scrubbed evidence pack. - **Engineer:** settings changes, upsizing, filter banks. ## Ranked patterns 1. **Feeder trip at peak** — coincident ramp / lug heat / curve. [SWG-TRIP](/entries/eaton-swg-trip-feeder-breaker-trip-charging-peak). 2. **GF / arc-flash** — life safety; qualified only. SWG-GF, SWG-ARC. 3. **Transformer overtemp / harmonics** — cooling + engineering. SWG-XFMR, SWG-PF. 4. **Door interlock / UPS dead / CT reversed after service** — restore controls and sensing before EVSE blame. SWG-DOOR, SWG-UPS, SWG-CT. ## Guides [Site power quality](/guides/site-power-quality-basics) · [OCPP Faulted](/guides/ocpp-faulted-triage) Browse Eaton entries below or [database](/database?brand=eaton).

Flo

4 published entries

# Flo — field brand hub Flo **Smart Two** AC units show up on workplace and public Level 2 pads. Ownership is the pedestal: pilot path, meter, auth card, and enclosure thermal — plus Flo network auth. Split “won’t authorize” from “authorizes but no energy” before you open the enclosure. ## When this OEM shows up Typical tickets: auth card not accepted, meter error, pilot diode fail (no charge with EV plugged), overtemp enclosure in sun/poor airflow. Site owns PE and feeder; Flo/CPO owns credential mapping; the unit owns pilot, meter, and local thermal path. ## How faults present - Local LEDs / display: meter error, overtemp, fault. - Flo network / OCPP: Authorize rejected vs Faulted mid-session. Auth-only: [/guides/fleet-cms-triage](/guides/fleet-cms-triage), [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). Hard Faulted: [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Cloud: card credential mapping and meter register history. - Physical: hot enclosure in sun, blocked vents, damaged cable/pilot pins. ## Ranked failure patterns 1. **Auth card not accepted** — Credential/list/reader; not a pilot fault. Entry: [/entries/flo-flo-st-auth-auth-card-not-accepted](/entries/flo-flo-st-auth-auth-card-not-accepted). Related: [/entries/protocol-rfid-01-rfid-reader-no-uid](/entries/protocol-rfid-01-rfid-reader-no-uid). 2. **Smart Two meter error** — Meter path / CRC-class issues affecting session close. Entry: [/entries/flo-flo-st-met-smart-two-meter-error](/entries/flo-flo-st-met-smart-two-meter-error). Metering guide: [/guides/metering-payment](/guides/metering-payment), [/entries/protocol-met-01-energy-meter-crc-error](/entries/protocol-met-01-energy-meter-crc-error). 3. **Pilot diode fail** — CP path; EV never reaches charge-ready. Entry: [/entries/flo-flo-st-pilot-pilot-diode-fail](/entries/flo-flo-st-pilot-pilot-diode-fail). 4. **Overtemp enclosure** — Sun load, blocked vents, failed fan if equipped. Entry: [/entries/flo-flo-st-temp-overtemp-enclosure](/entries/flo-flo-st-temp-overtemp-enclosure). ## Logs / tools Flo portal event log, Authorize timeline, LED photos, IR on enclosure, DMM on CP, known-good credential card, PE continuity ([/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser)). ## Escalate when - **Electrician:** Supply issues, enclosure heat from upstream overload, wiring on pilot, PE problems. - **Network/Flo ops:** Card not in allow-list, site group mis-map. - **OEM:** Meter board or pilot hardware after credential and wiring cleared. Do not OEM-escalate auth rejects that are credential-only. ## Field checklist 1. Split the ticket: auth fail vs meter/pilot/thermal with auth OK. 2. Photo LEDs/display and note ambient sun load on the enclosure. 3. Pull Flo portal Authorize timeline and last good session. 4. Try a known-good credential before opening the pilot path. 5. If meter error: capture register/CRC evidence for [/guides/metering-payment](/guides/metering-payment) — do not treat as isolation. 6. If no charge after authorize: CP/pilot check and second vehicle when available. 7. Clear vents / shade path before condemning overtemp hardware. Soft-offline with healthy local LEDs is backhaul/CSMS ([/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms)), not a pilot diode.

Fluence / BESS

9 published entries

# Fluence BESS field hub (depot EVSE boundary) Fluence (and similar) BESS on depots feed or buffer EVSE. Most “charger down” tickets here are **inhibits and energy limits**, not bad CCS guns. Your job is boundary control and a clean handoff to BESS/fire specialists. ## Ownership - **EVSE tech:** confirm whether stalls died together; capture OCPP; verify site voltage; do not open battery racks. - **BESS ops / OEM:** cells, PCS internals, balance, thermal events. - **Fire contractor:** FACP alarms and fire inhibits. - **Electrician:** feeders, transformers, UPS controls power. ## Ranked patterns 1. **SOC floor / UV under simultaneous ramp** — energy management, not module RMA. Entries: BESS-SOC, BESS-UV. 2. **Fire / interlock open** — walk the chain; never jumper. BESS-FIRE, BESS-INT. 3. **EMS comms loss** — OT network; respect failsafe. BESS-COM. 4. **PCS fault / OV / imbalance / thermal** — specialist. BESS-PCS, BESS-OV, BESS-BAL, BESS-THERM. ## Guides [BESS safety framing](/guides/bess-safety-framing) · [Site power](/guides/site-power-quality-basics) · [OCPP Faulted](/guides/ocpp-faulted-triage) Browse Fluence entries below or [database](/database?brand=fluence).

Ingenico / payment

5 published entries

PED / host money-path: timeouts, wet-weather chip read, host decline loops, USB-C power, NFC intermittents. Always split Authorize timeline from energy path.

Kempower

5 published entries

# Kempower — field brand hub Kempower **Satellite** sites run a **dynamic power pool**: satellites (stalls/dispensers) draw from a shared power unit. Tickets that look like “one dead gun” are often pool assignment, satellite↔power-unit link, or shared coolant — not a failed SECC. Field tickets that ignore the link between satellite and power unit waste hours blaming the wrong box. ## When this OEM shows up / cabinet vs dispenser - **Power unit:** modules, pool allocation, site feed interface, often the OCPP endpoint for the cluster. - **Satellite / dispenser:** user interface, cable, local sensors, RFID, session start path. - **Link:** fiber/copper/comms between satellite and power unit — when this drops, the satellite looks “dead” or stuck Preparing even if the power unit is healthy and siblings still charge. Confirm whether the fault is **one satellite**, **all satellites on one power unit**, or **site-wide**. That single question routes the job. Stall number on the pad is not always the OCPP connector ID — verify mapping before you swap hardware. Confirm which satellite ID, which pool, and whether sibling stalls still charge before you condemn a single stall’s power stage. ## How faults typically present ### HMI / Satellite UI - Kempower Satellite / C-series UI codes (KEM-SAT-*). - Stall Unavailable while adjacent satellites still Preparing/Charging → think link or allocation, not site-wide power death. - Link-lost banners with healthy power-unit LEDs are the classic tell. ### OCPP / ChargEye - Faulted/Unavailable with vendor strings; mid-ramp abort may show as InternalError or vendor CCS code. - Allocation stuck can look like SuspendedEVSE / 0 A without a hard Faulted — check load/pool before isolation megger ([/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a)). - Use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) when status is Faulted without a clear mechanical latch. - Power unit Heartbeat OK while satellite Authorize fails (or reverse) — trace which node owns the OCPP connection for that connector ID. ### Cloud - ChargEye + OCPP beat LED-only. Pull pool assignment, coolant pressure, link status, and module online map for the satellite ID on the ticket. ### Physical cues - Damaged link cable after landscaping, loose terminations, water in junction boxes, glycol/pressure issues at the power-unit loop. ## Ranked common failure patterns 1. **Satellite link to power unit lost** — Fiber/copper/link hardware, connector seating, or config after service. Sibling stalls healthy is the tell. Entry: [/entries/kempower-kem-sat-link-satellite-link-to-power-unit-lost](/entries/kempower-kem-sat-link-satellite-link-to-power-unit-lost). 2. **Dynamic power allocation stuck** — Pool budget, priority map, offline modules, or LMS/failsafe after heartbeat loss. Correlate simultaneous high demand; check module health on the power unit before cable RMA. Entry: [/entries/kempower-kem-sat-dyn-dynamic-power-allocation-stuck](/entries/kempower-kem-sat-dyn-dynamic-power-allocation-stuck). Fleet/CMS angle: [/guides/fleet-cms-triage](/guides/fleet-cms-triage). 3. **Cabinet coolant pressure low** — Shared loop: one low-pressure event can derate multiple satellites. Entry: [/entries/kempower-kem-sat-cool-cabinet-coolant-pressure-low](/entries/kempower-kem-sat-cool-cabinet-coolant-pressure-low). Procedure: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). Airlock after service: [/entries/site-generic-cool-air-airlocked-loop-after-fill](/entries/site-generic-cool-air-airlocked-loop-after-fill). 4. **CCS session abort mid-ramp** — Latch/cable/vehicle/SECC; prove with known-good cable and second vehicle before power-unit blame. Entry: [/entries/kempower-kem-sat-ccs-ccs-session-abort-mid-ramp](/entries/kempower-kem-sat-ccs-ccs-session-abort-mid-ramp). Handshake: [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics), [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail), [/entries/protocol-ccs-h01-ccs-slac-timeout](/entries/protocol-ccs-h01-ccs-slac-timeout). 5. **RFID reader miswired after service** — Harness reversed/loose after panel work; auth fails with healthy energy path. Entry: [/entries/kempower-kem-sat-rfid-rfid-reader-miswired-after-service](/entries/kempower-kem-sat-rfid-rfid-reader-miswired-after-service). Related: [/entries/protocol-rfid-01-rfid-reader-no-uid](/entries/protocol-rfid-01-rfid-reader-no-uid), [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). 6. **Site power under pool ramp** — Many satellites ramping together expose feeder limits. Idle voltage at the pad lies — measure under simultaneous demand ([/guides/site-power-quality-basics](/guides/site-power-quality-basics)). 7. **Network soft-offline** — DNS/TLS/identity after board or SIM work ([/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms)). ## Log sources / tools | Source | What you pull | |--------|----------------| | Satellite UI | Stall code, satellite ID | | ChargEye | Pool map, link status, coolant pressure, FW, module online | | OCPP CSMS | StatusNotification, MeterValues ramp curve, connector mapping | | Known-good cable / second EV | Moves CCS abort | | Coolant gauges | Pressure/flow at power unit | | Link path inspection | Connectors, junction boxes, recent civil work | ## Field checklist 1. One satellite, one power unit’s satellites, or whole site? 2. Link status in OEM tools / LEDs before RMA. 3. Pool demand vs online module capacity. 4. Recent civil work near link routes? 5. Known-good cable if ISO/CCS on one satellite only. 6. Feeder voltage under multi-satellite ramp. 7. RFID/auth vs energy path — split the ticket. ## When to escalate **Electrician / site power** — Feeder/PQ issues when the whole pool drops together; physical damage to link conduit after civil work that needs site electrical. **Network / CSMS / fleet ops** — Auth/RFID mapping after credential or reader changes; allocation policy / LMS caps during peak — ops, not wrench; wrong CSMS connector mapping. **Kempower OEM** — Confirmed link hardware after seating/config documented; coolant pump/skid with pressure evidence and fill procedure followed; SECC/power module after cable + vehicle + pool assignment cleared; pool firmware allocation bugs with ChargEye evidence pack. Do not RMA a satellite power path for allocation stuck or RFID miswire. Do not treat single-stall CCS abort as pool coolant failure without pressure data. Payment-only failures belong to billing ([/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout)).

Power Electronics

4 published entries

NB 360 multi-module: current-share / module-comm loss and cooling pump contactor chatter. Input phase-loss often originates upstream — prove feeder before module bank swap.

Schneider Electric

4 published entries

# Schneider Electric — field brand hub Schneider **EVlink / EVinox**-class AC chargers show up on commercial and workplace Level 2 installs. Ownership is the wallbox/pedestal: ground-fault path, phase config on 3P, LED status logic, and max-current commissioning — not a DC power cabinet. Always verify nameplate and breaker before calling OEM for “no power.” ## When this OEM shows up Common tickets: ground fault, missing phase on 3P installs, LED stuck red, wrong max current after config/commissioning. Unit owns GF sensing, local controller, and config. Electrician owns phases/PE/breaker. Network/ops owns OCPP mapping and remote config drift after fleet updates. ## How faults present - LED status: stuck red / fault indication with or without OCPP Faulted. - OCPP/CSMS (networked): Faulted, Unavailable, or Available but capped amps. Faulted triage: [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Local config UI/tools: max current and phase settings often explain “slow” or “won’t start” without a protective trip. - Physical: missing phase after panel work, moisture at glands, incorrect DIP/config after board swap. ## Ranked failure patterns 1. **EVlink ground fault** — Moisture or true PE/GF path. Entry: [/entries/schneider-sch-ev-gf-evlink-ground-fault](/entries/schneider-sch-ev-gf-evlink-ground-fault). PE: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **Missing phase on 3P install** — Upstream or miswired phase; measure before board swap. Entry: [/entries/schneider-sch-ev-phase-missing-phase-on-3p-install](/entries/schneider-sch-ev-phase-missing-phase-on-3p-install). PQ: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). 3. **Wrong max current config** — Commissioned below breaker/cable capability or left at default. Entry: [/entries/schneider-sch-ev-cfg-wrong-max-current-config](/entries/schneider-sch-ev-cfg-wrong-max-current-config). Related load-management confusion: [/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a). 4. **LED status stuck red** — Latched fault or UI/LED board; pull OCPP/vendor code before reset loops. Entry: [/entries/schneider-sch-ev-hmi-led-status-stuck-red](/entries/schneider-sch-ev-hmi-led-status-stuck-red). Related: [/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot). ## Logs / tools Config screenshots (max A, phase mode), LED photos, DMM on L1/L2/L3/N/PE, CSMS StatusNotification, IR if thermal complaint. ## Escalate when - **Electrician:** Missing phase, PE/GF wiring, breaker mismatch. - **Network/ops:** OCPP mapping; remote config drift after fleet updates. - **OEM:** Confirmed GF hardware or LED/controller after supply and config verified. Do not OEM-escalate wrong max-current settings or single-phase loss that is upstream. ## Field checklist 1. Measure L1/L2/L3/N/PE before any board swap on 3P installs. 2. Photo LED state and export CSMS StatusNotification if networked. 3. Screenshot max-current and phase-mode config vs breaker rating. 4. If ground fault: dry, inspect glands, verify PE continuity. 5. If LED stuck red: capture vendor/OCPP code once — avoid reset loops. 6. If “slow charge”: confirm config amps and any LMS cap before OEM. 7. Match nameplate current to feeder before calling the unit dead. Wrong max-current after commissioning is a config ticket, not an OEM failure. Upstream missing phase is electrician work ([/guides/site-power-quality-basics](/guides/site-power-quality-basics)).

Siemens

4 published entries

Sicharge D: isolation, cluster LMS conflict, mid-meter, and HMI freeze. Resolve LMS ownership and meter path before SECC board swaps.

Sierra Wireless / Semtech

5 published entries

AirLink modem path: SIM/APN, RSSI in metal cabinets, antenna connectors, FW bricks, wrong APN after SIM swap. RSSI OK ≠ stable OCPP websocket.

Site stack (generic)

24 published entries

Contactors, SPD/RCD, coolant skids, LMS cabinets, and cable IR — OEM-agnostic site stack that fails independently of charger brand. Prove this layer before OEM RMA.

Tritium

10 published entries

# Tritium — field brand hub Tritium field work splits hard between **PK350** (liquid-cooled ultra-fast) and **RTM75** (air-cooled mid-power). Sites often mix them under one CPO; treat cooling architecture as a first-class branch in every ticket. Isolation, cable-leak, and thermal paths are not interchangeable — name the platform before you pull a rectifier. ## When this OEM shows up / cabinet vs dispenser PK350 deployments typically present as a **power/rectifier section + dispenser UI** with liquid-cooled cables. Isolation and leak-detect faults often track the **cable assembly** or quick-connects, not the whole power stage. RTM75 is air-cooled — fan path, inlet filters, and GF under weather dominate; do not apply PK350 bleed procedures to RTM. **Dispenser / UI ownership:** no-boot HMI, auth timeouts / empty local list, cellular failover flapping. **Power / rectifier ownership:** rectifier stage fault, isolation (PK), ground fault (RTM). **Cable / thermal ownership:** liquid-cooled cable leak detect (PK), gun temperature derate (PK), inlet fan blocked (RTM). **Internal link:** RTM internal CAN bus error — prove harness/termination before power-stage RMA. If one dispenser faults and the peer stays Available, chase cable/gun/ISO first. If the whole unit Faulted with cooling codes, stay in the CDU / cabinet cooling path. Ultra-fast sites also expose feeder limits when multiple PK units ramp together — measure power before condemning modules. Dispenser UI dark with cellular flapping is a **backhaul/UI** ticket until proven otherwise. ## How faults typically present ### HMI / service LEDs - PK dispenser UI: fault strings / service LEDs (TRI-PK-*). - RTM: service LED / local codes (TRI-RTM-*). - UI no-boot: blank or looping screen while power section may still be alive — check supply and link before HV. ### OCPP / Veefil / CSMS - Faulted / Unavailable with Tritium vendor codes in `info`. - Cellular failover flapping: Heartbeat gaps, reconnect storms — use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Auth timeout with empty local list: offline auth policy / CSMS sync, not a gun fault ([/guides/fleet-cms-triage](/guides/fleet-cms-triage)). - Soft derate long before hard Faulted on thermal paths — pull MeterValues curve. ### Physical cues - Glycol smell, puddles at holster, hot cable near handle on PK350; blocked RTM inlets after storms; water at glands on outdoor RTM. ## Ranked common failure patterns ### PK350 1. **Isolation fault** — Cable/gun IR or wet path before rectifier condemnation. Prove with known-good cooled cable. Entry: [/entries/tritium-tri-pk-iso-pk350-isolation-fault](/entries/tritium-tri-pk-iso-pk350-isolation-fault). CableCheck stage: [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail), [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics). 2. **Liquid-cooled cable leak detect** — Quick-connects, jacket damage, residual after swap. Stop sessions; do not “top off and ignore.” Entry: [/entries/tritium-tri-pk-cable-liquid-cooled-cable-leak-detect](/entries/tritium-tri-pk-cable-liquid-cooled-cable-leak-detect). Loop procedure: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). Follow OEM fill/bleed after any cable swap — airlocks fake flow faults ([/entries/site-generic-cool-air-airlocked-loop-after-fill](/entries/site-generic-cool-air-airlocked-loop-after-fill)). 3. **Dispenser UI no boot** — Supply, board, or link; prove backhaul/power to UI. Entry: [/entries/tritium-tri-pk-disp-dispenser-ui-no-boot](/entries/tritium-tri-pk-disp-dispenser-ui-no-boot). 4. **Cellular failover flapping** — SIM/APN/antenna/RSSI in metal cabinets; RSSI OK ≠ stable websocket. Entry: [/entries/tritium-tri-pk-net-cellular-failover-flapping](/entries/tritium-tri-pk-net-cellular-failover-flapping). Heartbeat path: [/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms), [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms), [/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet](/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet). 5. **Gun temperature derate** — Coolant flow, sensor, sun load, repeated high-power sessions. Entry: [/entries/tritium-tri-pk-gun-gun-temperature-derate](/entries/tritium-tri-pk-gun-gun-temperature-derate). 6. **Rectifier stage fault** — After isolation, cooling, and grid proven. Entry: [/entries/tritium-tri-pk-pwr-rectifier-stage-fault](/entries/tritium-tri-pk-pwr-rectifier-stage-fault). Grid check: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). ### RTM75 1. **Ground fault** — Rain, wash-down, boot seals, or true PE open. Entry: [/entries/tritium-tri-rtm-gf-rtm-ground-fault](/entries/tritium-tri-rtm-gf-rtm-ground-fault). PE: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **Inlet fan blocked** — Filters/debris; clear inlet before sensor swaps. Entry: [/entries/tritium-tri-rtm-fan-inlet-fan-blocked](/entries/tritium-tri-rtm-fan-inlet-fan-blocked). 3. **Auth timeout — local list empty** — Offline list / CSMS sync after network outage. Entry: [/entries/tritium-tri-rtm-auth-auth-timeout-local-list-empty](/entries/tritium-tri-rtm-auth-auth-timeout-local-list-empty). Related: [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). 4. **Internal CAN bus error** — Harness, termination, moisture at connectors. Entry: [/entries/tritium-tri-rtm-can-internal-can-bus-error](/entries/tritium-tri-rtm-can-internal-can-bus-error). ### Cross-platform - Handshake / latch before current with healthy power stage: [/entries/protocol-ccs-h01-ccs-slac-timeout](/entries/protocol-ccs-h01-ccs-slac-timeout), [/entries/protocol-ccs-h02-sdp-failed-secc-not-responding](/entries/protocol-ccs-h02-sdp-failed-secc-not-responding), [/entries/protocol-ccs-h04-precharge-voltage-mismatch](/entries/protocol-ccs-h04-precharge-voltage-mismatch). - Stuck Faulted after reboot: [/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot](/entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot). - LMS caps that look like hardware failure: [/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a). ## Log sources / tools | Source | What you pull | |--------|----------------| | Dispenser UI / service LEDs | Live code, boot state | | Tritium Veefil / CSMS | Event log, FW, SIM/modem stats | | OCPP export | Heartbeat gaps, StatusNotification, Authorize, MeterValues | | Coolant tools (PK) | Level, pressure/flow, leak dye/visual | | IR / DMM / megger | Gun heat, PE, IR, phase | | Known-good cooled cable (PK) | Leak/iso moves with cable | For cellular tickets: RSRP/RSRQ, APN, antenna connector seating, and whether Ethernet failover exists. Never run a coolant pump dry to “test.” Photos of leak residue and holster seals (scrub PII). ## Field checklist (first 15 minutes) 1. PK350 or RTM75? (cooling branch) 2. One gun or whole unit? 3. Leak smell/puddle? If yes, stop and contain — do not keep testing. 4. Recent cable/coolant work? 5. OCPP snippet for the fault window 6. Known-good cable swap if ISO/CCS and dry enough 7. Feeder voltage under simultaneous ramp if multi-unit site ## When to escalate **Electrician / site power** — True PE open or feeder events correlating with GF / rectifier trips; supply issues to dispenser UI (separate from rectifier HV); utility/transformer limits under multi-PK ramp. **Network / CSMS ops** — Failover flapping with modem stats pointing at APN/SIM/DNS/TLS; empty local auth list after prolonged offline — policy/sync, not hardware; wrong OCPP identity after board/SIM swap. **Tritium OEM** — Rectifier stage with isolation + cooling + grid cleared; confirmed cooled-cable leak path needing OEM cable/RMA; UI board no-boot after supply and link proven; internal CAN after harness/termination documented; persistent cooling after bleed + filter + leak-free loop. Do not escalate UI no-boot or cellular flap as a rectifier fault. Do not treat RTM GF like PK cable-leak coolant procedure. Payment-only failures belong to the billing stack ([/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout)).

Wallbox

4 published entries

# Wallbox — field brand hub Wallbox tickets in this corpus center on **Pulsar Plus** AC wallboxes (workplace / residential / light commercial). There is no DC cabinet↔dispenser split — ownership is enclosure, CP/pilot path, GFCI/PEN protection, and Wi-Fi/app schedule. ## When this OEM shows up Expect GFCI trips after rain or wash-down, CP state faults with no EV, UK-style PEN faults on relevant installs, and Wi-Fi drops that kill scheduled charging. Confirm whether the complaint is “won’t start,” “trips mid-session,” or “schedule didn’t run” before opening the enclosure. Wall unit owns GFCI, PP/CP, and local UI. Site owns feeder breaker, PE bond, and often the Wi-Fi/AP path. Do not open the EVSE for a tripped upstream breaker that only looks like a charger fault. ## How faults present - Local LEDs / app: fault icons, GFCI trip, CP error. - OCPP (networked installs): Faulted / Unavailable; schedule failures may stay Available with no session — check app/backend, not just StatusNotification. Use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) when Faulted. - Cloud / myWallbox-class app: schedule and Wi-Fi history often explain “didn’t charge overnight.” - Physical: moisture at cable gland, wet holster after wash-down, weak Wi-Fi after AP changes. ## Ranked failure patterns 1. **Pulsar GFCI trip** — Moisture, contamination, or true ground path. Dry and inspect before board swaps. Entry: [/entries/wallbox-wb-pp-gfci-pulsar-gfci-trip](/entries/wallbox-wb-pp-gfci-pulsar-gfci-trip). PE: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **CP state fault, no EV** — Pilot wiring, diode path, or stuck state with nothing plugged. Prove with second vehicle/cable when possible. Entry: [/entries/wallbox-wb-pp-cp-cp-state-fault-no-ev](/entries/wallbox-wb-pp-cp-cp-state-fault-no-ev). 3. **PEN fault (UK-style)** — Protective earth/neutral monitoring on applicable installs — electrician territory if wiring. Entry: [/entries/wallbox-wb-pp-pen-pen-fault-uk-style](/entries/wallbox-wb-pp-pen-pen-fault-uk-style). 4. **Wi-Fi drop loses schedule** — AP coverage / credentials; energy path may be fine. Entry: [/entries/wallbox-wb-pp-wifi-wi-fi-drop-loses-schedule](/entries/wallbox-wb-pp-wifi-wi-fi-drop-loses-schedule). Soft-offline Heartbeat gaps: [/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms). ## Logs / tools App/cloud event history, LED state photos, DMM on CP/PE, outlet/breaker verification, known-good cable/vehicle. For networked OCPP sites: Heartbeat and StatusNotification export. ## Escalate when - **Electrician:** PEN/PE, breaker, supply voltage, wet conduit, shared-circuit trips under load. - **Network/site IT:** Wi-Fi/SSID changes, VLAN, captive portal. - **OEM:** Confirmed CP board / GFCI hardware after wiring and moisture cleared. Do not OEM-escalate schedule misses that are Wi-Fi only. ## Field checklist 1. Breaker tripped or EVSE GFCI? Check upstream first. 2. Schedule miss vs hard fault — pull app Wi-Fi history. 3. Photo LEDs; note weather / wash-down. 4. Known-good cable/vehicle if CP or GFCI. 5. PEN/PE issues: stop and call electrician on applicable installs. 6. Networked sites: OCPP Heartbeat vs local charge capability. Keep GFCI, CP, PEN, and Wi-Fi as separate ticket paths — do not combine them into one board RMA.