Brands

Alpitronic

4 published entries

# Alpitronic — field brand hub Alpitronic tickets in this corpus center on **Hypercharger (HYC)** module-bank sites. HYC power modules often **share coolant**. One low-flow, airlocked, or offline bank can cascade derates across stalls that look like “four dead chargers” when the root is one wet path or one module group. Name HYC and the stall map before you open a crate of modules. Payment-offline and grid-overvoltage are **separate paths**—do not combine them into one power-stage RMA. ## When this OEM shows up / cabinet vs dispenser HYC deployments present as a high-power cabinet with module banks feeding dispensers/guns. Ownership splits matter: **Cable / gun / ISO side:** CableCheck isolation, wet connectors, cooled-cable quick-connect contamination after a gun swap. **Module / coolant side:** Offline bank, shared-loop flow/pressure, cascade derate across sibling stalls on the same coolant plant. **Money path:** PED / payment terminal offline while energy path may still FreeVend or RFID-start. **Grid side:** Overvoltage / PQ events that trip or derate the cabinet—measure under load, not idle. Confirm whether **one gun**, **one module bank**, or **the whole pad** shares the event. Shared coolant means a sister stall can be evidence, not coincidence. ## How faults typically present ### HMI - Hypercharger fault banners / service codes (ALP-HYC-*). - Soft derate banners long before hard Faulted when cooling or bank health slips. - Module map showing one bank offline while others still report online. ### OCPP / CSMS - `StatusNotification` Faulted or Unavailable with Alpitronic `vendorErrorCode` / `info`—log verbatim. - Isolation at CableCheck: [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics), [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Authorize / ReaderFailure with Ready energy path → money path ([/guides/metering-payment](/guides/metering-payment)). - Peak-hour Faulted cluster with healthy ISO → think grid or shared coolant, not four SECC boards. ### Physical cues - Glycol smell, wet quick-connects after cable service, blocked filters, warm modules next to a silent bank, PED dark while guns look Ready. ## Ranked common failure patterns 1. **HYC isolation fault** — Moisture or damaged cooled/uncooled cable before condemning the ISO board or module bank. Known-good cable prove first. Free sample: [/entries/alpitronic-alp-hyc-iso-hyc-isolation-fault](/entries/alpitronic-alp-hyc-iso-hyc-isolation-fault). Stage map: [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail). Coolant contamination after swaps: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). 2. **Module offline bank** (early-access / Pro depth) — One bank offline derates the stall or pad; shared coolant or power-share can cascade. Prove which bank, link health, and coolant state before full bank swap. Entry: [/entries/alpitronic-alp-hyc-mod-module-offline-bank](/entries/alpitronic-alp-hyc-mod-module-offline-bank). Do not treat this as a free sample unlock—deeper OEM packing stays gated. 3. **Payment terminal offline** — PED/host path dead while FreeVend or RFID may still work. Split money from kWh. Entry: [/entries/alpitronic-alp-hyc-pay-payment-terminal-offline](/entries/alpitronic-alp-hyc-pay-payment-terminal-offline). Related: [/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout), [/guides/metering-payment](/guides/metering-payment). 4. **Grid overvoltage** — Upstream PQ / utility / capacitor events. Idle voltage lies—measure under the failing load. Entry: [/entries/alpitronic-alp-hyc-grid-grid-overvoltage](/entries/alpitronic-alp-hyc-grid-grid-overvoltage). Guide: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). Cluster timing across stalls is the tell. ## Log sources / tools | Source | What you pull | |--------|----------------| | HYC HMI / service UI | Fault banner, module online map, coolant/flow | | CSMS / OCPP | StatusNotification, MeterValues, Authorize timeline | | Payment host / PED | Host reachability, reboot loops, USB power | | DMM / IR / megger | Phase voltages under load, IR after cable swap, hotspots | | Known-good cable | Moves isolation with cable vs stays with cabinet | ## Field checklist (first 15 minutes) 1. Photo HMI + connector ID + module-bank map. 2. One gun, one bank, or whole pad? 3. Weather / recent cable or coolant work? 4. If ISO: dry + known-good cable before HV. 5. If soft derate / bank offline: coolant level/flow/pump sound + sibling stalls. 6. If payment only: FreeVend/RFID prove; leave power modules alone. 7. If grid code: loaded voltage table before module crates. ## When to escalate **Electrician / site power** — Overvoltage / phase events matching HYC grid codes; feeder issues during multi-stall peaks. **Network / payment ops** — PED offline with healthy energy path; host/merchant config; OCPP identity after board/SIM work. **Alpitronic OEM** — Confirmed module bank fault after coolant and grid proven; ISO path after known-good cable fails dry; firmware latch with export attached. Do not RMA a module bank for payment-only failures, rain ISO without dry-out/known-good cable, or grid overvoltage without a loaded voltage table. Shared coolant means one wet path can fake a “module epidemic”—prove the loop. ## Worked examples **Example A — Isolation after overnight rain, one gun.** Peer gun charges. Dry, known-good cooled cable moves the fault → cable/quick-connect. Fault stays → ISO/cabinet path. Do not open four module crates because Cloud said Faulted on one connector. **Example B — Three stalls derate at once after cable service on stall 2.** Shared coolant contamination or airlock after one swap. Bleed/inspect loop per OEM fluid rules before declaring a “module epidemic.” See [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). **Example C — Cards fail, FreeVend works, modules healthy.** Money path only. Pull PED/host timeline; leave HYC power stage closed. [/guides/metering-payment](/guides/metering-payment). **Example D — Pad Faulted at 17:10 with overvoltage banners.** Measure loaded voltage; compare utility event log. Module RMA after a grid spike wastes a truck roll. ## False friends | Looks like | Often actually | |------------|----------------| | All modules bad | Shared coolant / one bank offline cascading | | Dead charger | PED offline with energy path Ready | | SECC failure | CableCheck moisture on one gun | | Random Faulted | Grid OV under multi-stall ramp | ## Related learning [/learn/site-power-vs-charger-fault](/learn/site-power-vs-charger-fault) · [/learn/ccs-session-stages](/learn/ccs-session-stages) · [/help](/help)

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

# Autel — field brand hub Autel tickets here center on **MaxiCharger DC**—often dual-port with CCS and/or NACS. Isolation, NACS latch, power-stage overtemp, and “app start fails while OCPP looks fine” dominate. The recurring mistake is blaming the power stage for **auth mapping** or a **NACS mechanical latch** problem. Name the port (CCS vs NACS) and whether the failure is app-only before you LOTO. ## When this OEM shows up / cabinet vs dispenser MaxiCharger DC presents as a DC cabinet/dispenser package. Ownership: **Port / cable side:** Isolation at CableCheck, NACS latch/tongue, thermal at the handle after high-power sessions. **Power stage side:** Overtemp / derate with airflow or cooling evidence—not app errors. **App / auth side:** Mobile start fails while local RFID/OCPP Authorize path may still work—or OCPP is healthy and the app token map is wrong. Always record **which port** faulted. Dual-port units fail differently per connector. See [/guides/nacs-field-notes](/guides/nacs-field-notes) when NACS or adapters are in the path. ## How faults typically present ### HMI - MaxiCharger screen codes (AUT-MC-*). - Latch / lock fail on NACS while CCS peer may still start. - Thermal derate banners before hard Faulted. ### OCPP / Autel Charge / app - Faulted at CableCheck with vendor strings—log verbatim. - App start fail with Heartbeat OK and local start OK → auth mapping, not HV. - Use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) for Faulted without clear mechanical cause. - Authorize rejects: [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). ### Physical cues - Bent NACS latch tongue, debris/ice, hot handle after stacked sessions, wet CCS cable after wash-down, adapter in path (say it early). ## Ranked common failure patterns 1. **MaxiCharger isolation** — Moisture or cable IR before power-stage blame. Free sample: [/entries/autel-aut-mc-iso-maxicharger-isolation](/entries/autel-aut-mc-iso-maxicharger-isolation). [/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. **NACS port latch** — Mechanical latch, microswitch, debris, or vehicle inlet—second vehicle before condemning EVSE. Free sample: [/entries/autel-aut-mc-nacs-nacs-port-latch](/entries/autel-aut-mc-nacs-nacs-port-latch). [/guides/nacs-field-notes](/guides/nacs-field-notes). 3. **Power stage overtemp** — Airflow, filters, ambient stacking, sensor unseat after service. Free sample: [/entries/autel-aut-mc-therm-power-stage-overtemp](/entries/autel-aut-mc-therm-power-stage-overtemp). If liquid-cooled path present: [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops). Thermal derate protocol: [/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero](/entries/protocol-nacs-h03-nacs-thermal-derate-to-zero) when NACS thermal. 4. **App start fails, OCPP OK** — App account mapping, remote start permissions, or token sync—not a module fault. Entry: [/entries/autel-aut-mc-app-app-start-fails-ocpp-ok](/entries/autel-aut-mc-app-app-start-fails-ocpp-ok). Related remote-start patterns: [/entries/protocol-ocpp-f06-remotestart-fails-while-local-rfid-works](/entries/protocol-ocpp-f06-remotestart-fails-while-local-rfid-works). ## Log sources / tools | Source | What you pull | |--------|----------------| | MaxiCharger HMI | Port ID, fault banner, thermal state | | Autel Charge / OCPP | Authorize, RemoteStart, StatusNotification, MeterValues | | Known-good cable / second vehicle | Isolation and latch prove | | IR / DMM | Handle heat, PE, loaded voltage if PQ suspected | ## Field checklist (first 15 minutes) 1. CCS or NACS port? Adapter in path? 2. Photo HMI + port ID + peer port status. 3. App-only vs local start vs both failing? 4. If ISO: dry + known-good cable. 5. If NACS latch: inspect tongue; second vehicle. 6. If thermal: airflow/filters/session stacking before board RMA. 7. If app-only: leave power stage closed; pull Authorize/RemoteStart timeline. ## When to escalate **Network / app ops** — Account mapping, RemoteStart rights, OCPP identity after board work. **Electrician** — Site undervoltage correlating with thermal/grid-looking codes ([/guides/site-power-quality-basics](/guides/site-power-quality-basics)). **Autel OEM** — Confirmed power stage after cooling/airflow proven; latch actuator after mechanical prove; ISO after known-good cable fails dry. Do not RMA power modules for app-only starts, or swap CCS parts for a NACS latch code. Adapter tickets need the adapter named on the first photo, not buried in the closeout. ## Worked examples **Example A — NACS latch fail; CCS peer starts.** Inspect tongue/debris; second vehicle. Do not RMA power stage for a latch code. **Example B — App start fails; local RFID starts; OCPP Heartbeat OK.** Auth/app mapping. Pull RemoteStart/Authorize timeline; leave DC contactors alone. **Example C — Isolation on CCS after rain; NACS unused.** Treat as CCS CableCheck moisture path. Known-good CCS cable before MaxiCharger board talk. **Example D — Thermal derate after three stacked high-kW sessions.** Airflow/filters/ambient; IR the handle. Adapter-in-path tickets must say so in the first sentence. ## False friends | Looks like | Often actually | |------------|----------------| | Bad power module | App RemoteStart mapping | | Incompatible NACS car | Latch tongue / debris / adapter orientation | | Random Faulted | Port-specific ISO on CCS only | | Needs firmware | Soft thermal derate from blocked inlet | ## Related learning [/learn/ccs-session-stages](/learn/ccs-session-stages) · [/guides/nacs-field-notes](/guides/nacs-field-notes) · [/help](/help) ## Ticket hygiene Capture: HMI photo, connector/port ID, peer status, OCPP errorCode + vendor string verbatim, weather/service notes, and (for thermal/grid) a loaded measurement. Scrub customer PII before `/request` or Pro Q&A. Prefer one branch per ticket—do not merge money-path and HV into one RMA narrative. ## Coordination notes When opening OEM or electrician tickets, attach: HMI photos, connector IDs, OCPP vendor strings, peer-stall status, and any loaded voltage or RF measurements. That evidence pack cuts “replace module” ping-pong. Keep one fault branch per work order. ## Platform notes (MaxiCharger DC) Dual-port units need the failing port named in the first photo. CCS isolation procedures do not fix NACS latch codes. App backends can deny RemoteStart while the station still accepts local RFID—that is intentional product behavior on some sites, not a random Faulted. When an adapter is in the path, write “adapter” on the ticket before any thermal theory. Sustained high-power derate after cable service often traces to a sensor unseated in the handle—not a full power-stage crate.

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.

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

# Delta — field brand hub Delta tickets in this corpus center on **UFC-class** DC fast chargers. Ground fault, backend unreachable, exhaust fan faults, and connector lock motor failures dominate. Verify **grid and fan path** before isolation-style RMAs, and split **soft-offline backend** from true protective GF. Name UFC and whether the stall is alone or pad-wide before opening HV. ## When this OEM shows up / cabinet vs dispenser UFC packages combine power conversion, cooling/exhaust, connector lock, and OCPP/backend connectivity. Ownership: **Protective / PE side:** Ground fault under rain or wash-down—dry and prove PE before board swaps. **Thermal / airflow side:** Exhaust fan fault driving derate or Faulted—filters and fan hardware before sensor theater. **Lock / connector side:** Lock motor fail at Preparing—mechanical debris vs actuator. **Backend / network side:** Backend unreachable with local Ready possible—DNS/TLS/CSMS path, not a power module. Do not treat backend unreachable as “charger dead” without Heartbeat evidence. Do not clear GF repeatedly into a wet fault. ## How faults typically present ### HMI - UFC banners (DEL-UFC-*). - GF latch that returns immediately after clear. - Fan fault / overtemp derate before hard Faulted. - Lock fail with gun not seating. ### OCPP / backend - Faulted GroundFailure—use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Soft-offline: Heartbeat timeout / Unavailable while local may look Ready ([/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms)). - DNS/TLS path: [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms). - Modem RSSI in metal cabinets: [/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet](/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet). ### Physical cues - Wet holster after rain, blocked exhaust, grinding lock motor, antenna inside shielded door, recent SIM swap. ## Ranked common failure patterns 1. **UFC ground fault** — Moisture bridging GF sensing or true PE fault. Free sample: [/entries/delta-del-ufc-gf-ufc-ground-fault](/entries/delta-del-ufc-gf-ufc-ground-fault). PE continuity: [/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser](/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser). 2. **Backend unreachable** — CSMS/DNS/TLS/modem path; energy hardware may be fine. Free sample: [/entries/delta-del-ufc-com-backend-unreachable](/entries/delta-del-ufc-com-backend-unreachable). Prove Heartbeat and URL/certs before power-stage blame. 3. **Exhaust fan fault** — Filter, seized fan, or sensor. Entry: [/entries/delta-del-ufc-fan-exhaust-fan-fault](/entries/delta-del-ufc-fan-exhaust-fan-fault). Thermal siblings: [/entries/protocol-temp-01-connector-overtemp-derate](/entries/protocol-temp-01-connector-overtemp-derate) when derate presents at the gun. 4. **Connector lock motor fail** — Debris, ice, worn actuator, or feedback switch—second vehicle before board RMA. Entry: [/entries/delta-del-ufc-lock-connector-lock-motor-fail](/entries/delta-del-ufc-lock-connector-lock-motor-fail). CCS latch cousins: [/guides/ccs-handshake-basics](/guides/ccs-handshake-basics). ## Log sources / tools | Source | What you pull | |--------|----------------| | UFC HMI / LEDs | GF, fan, lock, backend status | | OCPP / CSMS | Heartbeat gaps, StatusNotification, BootNotification | | Modem / ALEOS if present | RSSI/RSRP vs disconnect times | | DMM / known-good cable | PE, lock continuity, isolation if ISO also present | ## Field checklist (first 15 minutes) 1. Photo HMI + connector ID; one stall or whole pad? 2. GF vs backend vs fan vs lock—name the branch. 3. Weather / wash-down / recent SIM or antenna work? 4. If GF: dry; PE measure; one clear after cause—not spam resets. 5. If backend: Heartbeat, DNS, TLS, RSSI before module crates. 6. If fan: inlet/exhaust clear; listen for seize. 7. If lock: inspect tongue; second vehicle; then actuator path. ## When to escalate **Electrician** — Open PE, feeder GF upstream, undervoltage clusters ([/guides/site-power-quality-basics](/guides/site-power-quality-basics)). **Network / CSMS** — Backend unreachable with healthy RF after antenna prove; wrong OCPP identity after board work. **Delta OEM** — Confirmed GF board after dry/PE; fan assembly after airflow proven; lock motor after mechanical prove. Do not escalate soft-offline as GF, or lock fail as a power-module fault. Payment-only issues belong to PED ([/guides/metering-payment](/guides/metering-payment)), not UFC exhaust fans. ## Worked examples **Example A — GF under rain, returns after clear.** Dry holster/cable; measure PE. One OEM clear after cause—not ten resets. **Example B — Cloud red, local Ready, fan quiet OK.** Backend unreachable / Heartbeat path. Check DNS, TLS, modem RSSI before exhaust-fan RMA. **Example C — Derate then fan fault banner.** Clear filters; confirm fan spin. Do not megger for isolation first. **Example D — Lock motor grind at Preparing; second car same.** Actuator/debris. Peer connector healthy means not “whole UFC dead.” ## False friends | Looks like | Often actually | |------------|----------------| | Dead power stage | Soft-offline backend | | Isolation board | GF moisture / PE open | | SECC fail | Lock motor mechanical | | Antenna bad | Wrong OCPP URL after board swap | ## Related learning [/learn/reading-ocpp-statusnotification](/learn/reading-ocpp-statusnotification) · [/learn/safety-loto-boundary](/learn/safety-loto-boundary) · [/help](/help) ## Ticket hygiene Capture: HMI photo, connector/port ID, peer status, OCPP errorCode + vendor string verbatim, weather/service notes, and (for thermal/grid) a loaded measurement. Scrub customer PII before `/request` or Pro Q&A. Prefer one branch per ticket—do not merge money-path and HV into one RMA narrative. ## Coordination notes When opening OEM or electrician tickets, attach: HMI photos, connector IDs, OCPP vendor strings, peer-stall status, and any loaded voltage or RF measurements. That evidence pack cuts “replace module” ping-pong. Keep one fault branch per work order. ## Platform notes (UFC) UFC soft-offline is easy to misread as a dead power stage because Cloud is red. Always ask whether local Ready and whether a local start still works. Exhaust paths clog after storms and cottonwood season—fan faults spike then. Lock motors fail more in freezing rain than in dry heat. GF clears that return in under a minute are hard latches: stop resetting and measure PE. Pair backend tickets with modem RSSI history when the cabinet is metal.

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).

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.

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

# Ingenico — field brand hub (payment / PED) Ingenico (and similar) **PED** tickets are **money-path** problems. FreeVend or RFID may still start sessions while cards fail. Always split **Authorize / PED / host** from **energy / contactors / ISO**. Do not RMA a power module because the terminal timed out. ## When this OEM shows up / ownership **Payment ops / merchant owns:** Host config, MID, decline rules, key injection, firmware profiles. **EVSE tech owns:** Prove FreeVend/RFID vs card; reseat power/data to PED; known-good PED swap; capture Authorize timeline; keep PCI handling clean. **Network owns:** Firewall/DNS/TLS to host; VLAN for PED. Guide: [/guides/metering-payment](/guides/metering-payment) · [/learn/evse-levels-and-tickets](/learn/evse-levels-and-tickets). ## How faults typically present ### PED / HMI - Timeout / unable to process / reader error (PAY-*). - Dark PED, reboot loop, wet chip slot, flaky NFC. ### OCPP / EVSE - Authorize never arrives or IdTag timeout; energy path Ready or FreeVend OK. - ReaderFailure after firmware—re-pair PED before module crates ([/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage)). ### Physical cues - Loose USB-C, water in hood, cracked NFC antenna area, recent PED firmware, sun-heated terminal. ## Ranked common failure patterns 1. **Payment terminal timeout** — Host path or PED reboot mid-auth. Free sample: [/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout). 2. **Chip read fail wet weather** — Moisture/contamination in slot; dry and inspect before board. [/entries/ingenico-pay-chip-chip-read-fail-wet-weather](/entries/ingenico-pay-chip-chip-read-fail-wet-weather). 3. **Host authorize decline loop** — Merchant/host rules, not EVSE HV. [/entries/ingenico-pay-host-host-authorize-decline-loop](/entries/ingenico-pay-host-host-authorize-decline-loop). Related: [/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag](/entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag). 4. **USB-C power to PED unstable** — Soft reboot mid-tap. [/entries/ingenico-pay-usb-usb-c-power-to-ped-unstable](/entries/ingenico-pay-usb-usb-c-power-to-ped-unstable). 5. **NFC tap intermittent** — Antenna/alignment/EMI; prove chip path separately. [/entries/ingenico-pay-nfc-nfc-tap-intermittent](/entries/ingenico-pay-nfc-nfc-tap-intermittent). ## Log sources / tools | Source | What you pull | |--------|----------------| | PED menu / host | Response codes, reboot log, firmware | | OCPP | Authorize timeline vs StartTransaction | | FreeVend / RFID test | Energy-path prove | | USB power check | Stable 5V / cable integrity | ## Field checklist (first 15 minutes) 1. FreeVend or RFID start while card fails? → money path. 2. Photo PED screen + EVSE Ready state. 3. Timeout vs decline vs chip vs NFC vs power—name one. 4. Reseat power/data; known-good PED if available. 5. Check host reachability before EVSE LOTO. 6. PCI: no test PANs left on site; handle PED swaps per policy. 7. Do not open HV for PED-only. ## When to escalate **Payment host / merchant** — Decline storms, MID config, keys. **Network** — Firewall to host, DNS/TLS. **OEM PED** — Confirmed hardware after power/host proven. **EVSE OEM** — Only if energy path also fails with protective codes. ## Worked examples **A — Cards timeout; FreeVend works; modules cool.** PAY-TO / host—leave contactors closed. **B — Chip fails in rain; NFC sometimes works.** Dry slot; PAY-CHIP before PED condemn. **C — PED reboots when customer taps.** USB-C power path. ## False friends | Looks like | Often actually | |------------|----------------| | Dead charger | PED timeout / host decline | | Bad RFID board | PED power reboot | | Needs power module | Authorize never sent | | Random Faulted | ReaderFailure after FW—re-pair PED | ## Ticket hygiene Capture Authorize timestamps, PED firmware, FreeVend prove, and scrub cardholder data. Prefer [/request](/request) with scrubbed PED photo when the code is missing. ## Related learning [/help](/help) · [/guides/metering-payment](/guides/metering-payment) · brand hubs for the EVSE that mounts the PED (e.g. [/brands/chargepoint](/brands/chargepoint)) ## Money vs energy (drill) If FreeVend works and cards fail, you are done with HV for this ticket. If neither works and StatusNotification is GroundFailure, you are not on a PED ticket. If Authorize is Invalid for one card and others work, chase the account—not the gun. If the PED reboots on every tap, chase USB-C power before host config. Write the prove steps in the closeout so the next tech does not reopen the cabinet. ## Host decline vs timeout vs hardware Decline loops return host codes—call merchant support with the code, not EVSE OEM. Timeouts with PED reboot logs point at power/data. Timeouts with stable PED and no host reachability point at network. Chip wet-weather fails that clear when dry are environmental—replace seals/hood before boards. NFC intermittents with solid chip reads are antenna/EMI—don’t replace the whole EVSE for NFC. After any PED FW update, re-pair and run a known-good test card per site PCI rules. Mounting PED on a vibrating dispenser door can look like “random timeouts”—check mechanical strain on USB-C. Browse Ingenico entries below or [database](/database?brand=ingenico). Cross-link the EVSE brand hub that mounts the PED when the money path and energy path both appear in one ticket—keep them as two branches in the write-up. ## Closeout template “Energy path: FreeVend/RFID [pass/fail]. Money path: chip/NFC/host [result + code]. PED power: [stable/rebooting]. Host reachability: [ok/fail]. Next owner: [payment/network/OEM PED]. HV opened: no.” That closeout stops the next shift from tearing into contactors for a decline loop. Prefer one clear money-path branch; never merge PED timeouts into an isolation RMA narrative on the same work order.

Power Electronics

4 published entries

# Power Electronics — field brand hub Power Electronics tickets here center on **NB 360-class** multi-module DC cabinets. Isolation, module-communication loss, cooling-pump contactor chatter, and input phase-loss dominate. **Input phase-loss often originates upstream**—prove the feeder before a module-bank swap. Name NB360 and whether one module, the cooling plant, or the whole cabinet shares the event. ## When this OEM shows up / cabinet vs dispenser NB multi-module cabinets share conversion stages and often a cooling plant. Ownership: **Cable / ISO side:** CableCheck isolation—known-good cable before module condemnation. **Module / share side:** Module communication loss / current-share fail (early-access depth)—prove which module and link before full bank RMA. **Cooling side:** Pump contactor chatter, flow/pressure, airlock after service ([/guides/liquid-cooling-loops](/guides/liquid-cooling-loops)). **Grid side:** Input phase loss—measure all three phases under load at the cabinet disconnect. Do not shotgun modules because one phase is dead at the disconnect. Do not ignore contactor chatter as “nuisance noise” if the pump is cycling into a dry or airlocked loop. ## How faults typically present ### HMI / keypad - NB series codes (PE-NB-*). - Module map with one stage offline or not sharing. - Coolant / pump alarms with audible contactor chatter. - Phase-loss / undervoltage banners during peaks. ### OCPP / service export - Faulted at CableCheck—[/guides/ccs-handshake-basics](/guides/ccs-handshake-basics), [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage). - Soft derate then Faulted on thermal/coolant paths. - Pad-wide Faulted at the same minute → feeder/PQ first ([/guides/site-power-quality-basics](/guides/site-power-quality-basics)). ### Physical cues - Chatter at pump contactor, glycol weep, warm modules next to a silent peer, single-phase dead at disconnect, recent civil work on the feeder. ## Ranked common failure patterns 1. **NB360 isolation** — Cable/moisture before module bank. Free sample: [/entries/power-electronics-pe-nb-iso-nb360-isolation](/entries/power-electronics-pe-nb-iso-nb360-isolation). [/entries/protocol-ccs-h03-cable-check-isolation-fail](/entries/protocol-ccs-h03-cable-check-isolation-fail). 2. **Module communication loss** (early-access / Pro depth) — Backplane/link/share; confirm which module before full bank swap. Entry: [/entries/power-electronics-pe-nb-mod-module-communication-loss](/entries/power-electronics-pe-nb-mod-module-communication-loss). Not a free sample unlock. 3. **Cooling pump contactor chatter** — Control voltage, coil, airlock, low level, or failsafe cycling. Entry: [/entries/power-electronics-pe-nb-cool-cooling-pump-contactor-chatter](/entries/power-electronics-pe-nb-cool-cooling-pump-contactor-chatter). Airlock: [/entries/site-generic-cool-air-airlocked-loop-after-fill](/entries/site-generic-cool-air-airlocked-loop-after-fill). Contactor cousins: [/entries/site-generic-ctr-coil-contactor-coil-open](/entries/site-generic-ctr-coil-contactor-coil-open). 4. **Input phase loss** — Upstream breaker, lug, or utility; prove at cabinet under load. Entry: [/entries/power-electronics-pe-nb-grid-input-phase-loss](/entries/power-electronics-pe-nb-grid-input-phase-loss). [/guides/site-power-quality-basics](/guides/site-power-quality-basics). ## Log sources / tools | Source | What you pull | |--------|----------------| | NB HMI / keypad | Module map, coolant, phase alarms | | Service log export / OCPP | StatusNotification, MeterValues, fault history | | Clamp / DMM | Phase-to-phase and phase-to-ground under load | | Known-good cable | Isolation prove | ## Field checklist (first 15 minutes) 1. Photo HMI + module map + connector ID. 2. One module, cooling plant, or whole cabinet? 3. Measure three-phase voltage under the failing load. 4. If ISO: dry + known-good cable. 5. If chatter: level/flow/airlock before replacing modules. 6. If phase loss: stop module RMA; call electrician with voltage table. 7. If module-comm: identify which stage; check link before bank crates. ## When to escalate **Electrician** — Phase loss, lug heat, feeder trips, undervoltage clusters. **OEM (Power Electronics)** — Confirmed module-comm after link/grid proven; pump/contactor after coolant procedure followed; ISO after known-good cable fails dry. Do not escalate phase loss as module communication loss, or isolation after rain as a full bank failure. LMS soft caps can look like dead power—confirm site load management before crates ([/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a)). ## Worked examples **Example A — Isolation one gun after cable swap.** Known-good cable; dry connectors. Do not pull the module bank for CableCheck. **Example B — One module offline on map; siblings sharing.** Module-comm / share path (Pro depth). Identify stage and link before ordering a full set. **Example C — Pump contactor chatters; flow alarm after fill.** Airlock or low level. Bleed per OEM; do not run dry “to test.” **Example D — Phase-loss banner; A-B healthy, C dead at disconnect under load.** Electrician/feeder. Stop module crates immediately. ## False friends | Looks like | Often actually | |------------|----------------| | All modules bad | Single phase loss upstream | | Sensor flaky | Pump contactor / airlock cycling | | SECC failure | Cable ISO after service | | Random Faulted | LMS soft 0 A at peak | ## Related learning [/learn/site-power-vs-charger-fault](/learn/site-power-vs-charger-fault) · [/guides/liquid-cooling-loops](/guides/liquid-cooling-loops) · [/help](/help) ## Ticket hygiene Capture: HMI photo, connector/port ID, peer status, OCPP errorCode + vendor string verbatim, weather/service notes, and (for thermal/grid) a loaded measurement. Scrub customer PII before `/request` or Pro Q&A. Prefer one branch per ticket—do not merge money-path and HV into one RMA narrative. ## Coordination notes When opening OEM or electrician tickets, attach: HMI photos, connector IDs, OCPP vendor strings, peer-stall status, and any loaded voltage or RF measurements. That evidence pack cuts “replace module” ping-pong. Keep one fault branch per work order. ## Platform notes (NB360) Multi-module current share means one sick module can look like “the cabinet is weak” without a hard Faulted on every stage. Contactor chatter on the pump circuit is audible evidence—record a short video for the OEM ticket. Phase-loss banners deserve a three-phase table under load before any crate is opened. Isolation after a cable swap is almost never a full bank failure on day one—prove the gun first. Early-access module-comm rows stay Pro-gated; use free ISO samples for the public branch.

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

# Siemens — field brand hub Siemens tickets in this corpus cluster on **Sicharge D**. Isolation, cluster LMS conflicts, MID meter faults, and touch HMI freezes dominate. The classic waste of time is treating an LMS ownership or meter-path problem as an SECC board failure. Name Sicharge D and whether the stall is alone or in a **cluster load-management group** before you open covers. ## When this OEM shows up / cabinet vs dispenser Sicharge D sites often sit in multi-stall clusters with shared LMS policy. Ownership: **Gun / SECC / isolation side:** CableCheck IR, wet cable, latch—prove with known-good cable. **LMS / cluster side:** Soft 0 A, SuspendedEVSE, or “conflict” codes while siblings still charge under budget—policy and CT map, not a dead gun. **Meter path:** MID / mid-meter faults that break billing or refuse start while energy hardware looks fine. **HMI / controller:** Touch screen unresponsive with Controllers still heartbeating—preserve logs before reboot theater. Photograph connector ID, cluster group, and peer stall status. Do not condemn SECC because CableCheck failed once in the rain or because LMS capped the stall at peak. ## How faults typically present ### HMI - Sicharge D touch banners (SIE-SD-*). - Frozen UI with power stage still audible / LEDs alive. - Soft curtail banners without hard Faulted during peak demand. ### OCPP / backend - Faulted at CableCheck with Siemens vendor strings—log verbatim. - LMS conflict: may look like SuspendedEVSE / Unavailable / 0 A without GroundFailure. See [/entries/protocol-load-01-dynamic-load-management-caps-to-0-a](/entries/protocol-load-01-dynamic-load-management-caps-to-0-a). - MeterValues missing or PowerMeterFailure with Authorize OK—meter path ([/guides/metering-payment](/guides/metering-payment)). - Use [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) when status is Faulted without a clear latch. ### Physical cues - Wet CCS cable, stuck touch overlay after sun/heat, CT work at the gear after expansion, cluster stalls dying together at the same minute. ## Ranked common failure patterns 1. **Sicharge isolation** — Cable/gun IR or moisture before SECC/ISO board. Free sample: [/entries/siemens-sie-sd-iso-sicharge-isolation](/entries/siemens-sie-sd-iso-sicharge-isolation). Protocol: [/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. **Cluster LMS conflict** (early-access / Pro depth) — Budget, priority, CT map, or heartbeat failsafe across the cluster. Sibling timing is the tell. Entry: [/entries/siemens-sie-sd-lms-cluster-lms-conflict](/entries/siemens-sie-sd-lms-cluster-lms-conflict). Site power angle: [/guides/site-power-quality-basics](/guides/site-power-quality-basics). Not a free sample unlock. 3. **MID meter fault** — Measurement / seal / mid-meter path; sessions may authorize then fail billing or refuse start. Entry: [/entries/siemens-sie-sd-met-mid-meter-fault](/entries/siemens-sie-sd-met-mid-meter-fault). Related: [/entries/protocol-met-01-energy-meter-crc-error](/entries/protocol-met-01-energy-meter-crc-error), [/guides/metering-payment](/guides/metering-payment). 4. **Touch HMI unresponsive** — Soft hang, overlay, or supply to UI; Controllers may still talk OCPP. Capture backend event first, then controlled reset. Entry: [/entries/siemens-sie-sd-hmi-touch-hmi-unresponsive](/entries/siemens-sie-sd-hmi-touch-hmi-unresponsive). Stuck Faulted after reboot: [/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 | |--------|----------------| | Sicharge HMI / service | Banner, connector ID, LMS group, meter status | | Siemens backend / OCPP | StatusNotification, MeterValues, Heartbeat | | LMS / cluster config | Budget, CT map, priority, failsafe mode | | Known-good cable / DMM | Isolation prove; loaded voltages if PQ suspected | ## Field checklist (first 15 minutes) 1. Photo HMI + connector ID + peer stalls in the same LMS group. 2. Isolation vs soft 0 A vs meter vs frozen UI—name the branch. 3. Weather / recent cable or CT work? 4. If ISO: dry + known-good cable before HV. 5. If LMS: confirm budget/CT/heartbeat before SECC RMA. 6. If meter: Authorize vs MeterValues timeline. 7. If HMI freeze: export events before reboot spam. ## When to escalate **Electrician / site power** — Feeder sag matching cluster trips; CT wiring after expansion; PQ events. **LMS / CSMS ops** — Policy caps during revenue hours; wrong connector mapping; backend identity after board work. **Siemens OEM** — Confirmed ISO after known-good cable; meter hardware after seal/path proven; HMI hardware after soft recovery fails. Do not escalate LMS curtail as isolation, or HMI freeze as a power-module epidemic. Payment-only failures belong to the PED stack ([/entries/ingenico-pay-to-payment-terminal-timeout](/entries/ingenico-pay-to-payment-terminal-timeout)), not Sicharge SECC. ## Worked examples **Example A — CableCheck isolation, one connector, after wash-down.** Known-good cable clears it. Do not replace SECC on a wet gun. **Example B — Four Sicharge stalls show 0 A at peak; no GroundFailure.** LMS cluster conflict / budget. Pull LMS group IDs and CT map before HV. Sibling timing is evidence. **Example C — Authorize OK, MeterValues missing, billing angry.** MID meter path—not isolation. Photograph meter seals and export MeterValues gaps. **Example D — Touch frozen, Heartbeat alive, peer stall charging.** Capture backend events, then controlled UI recovery. Do not treat as pad-wide power death. ## False friends | Looks like | Often actually | |------------|----------------| | Dead SECC | LMS soft cap / cluster conflict | | Power module fail | MID meter / billing path | | Whole site down | One LMS group misconfigured | | Needs reboot | Hard latch returning in <1 min — find cause | ## Related learning [/learn/reading-ocpp-statusnotification](/learn/reading-ocpp-statusnotification) · [/learn/site-power-vs-charger-fault](/learn/site-power-vs-charger-fault) · [/help](/help) ## Ticket hygiene Capture: HMI photo, connector/port ID, peer status, OCPP errorCode + vendor string verbatim, weather/service notes, and (for thermal/grid) a loaded measurement. Scrub customer PII before `/request` or Pro Q&A. Prefer one branch per ticket—do not merge money-path and HV into one RMA narrative.

Sierra Wireless / Semtech

5 published entries

# Sierra Wireless — field brand hub (AirLink modem) Sierra Wireless **AirLink** (and similar cellular gateways) carry the OCPP websocket for many cabinets. Tickets present as soft-offline chargers: Cloud red, local Ready. **RSSI OK ≠ stable websocket.** Fix antenna placement, connectors, SIM/APN, and MTU/keepalive before condemning the EVSE power stage—or the modem—blindly. ## When this OEM shows up / ownership **EVSE tech owns:** Correlate Heartbeat gaps with ALEOS signal history; inspect SMA/antenna location; temporary external antenna prove; document metal-cabinet attenuation. **Network / carrier owns:** APN provisioning, SIM status, private APN firewalls, MTU. **OEM modem owns:** Bricked FW recovery, RF hardware after path proven. Guide: [/guides/ocpp-faulted-triage](/guides/ocpp-faulted-triage) · [/learn/reading-ocpp-statusnotification](/learn/reading-ocpp-statusnotification). ## How faults typically present ### EVSE / CSMS - Heartbeat timeout, BootNotification storms, Unavailable while local Available ([/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms](/entries/protocol-ocpp-f02-heartbeat-timeout-to-csms)). - DNS/TLS failures to CSMS ([/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms)). ### ALEOS / modem - Weak signal LEDs, no service, SIM not provisioned, wrong APN after swap, FW brick after update. ### Physical cues - Antenna inside shielded door, loose SMA, water in connector, recent SIM change, metal cabinet, landscaping that moved the antenna whip. ## Ranked common failure patterns 1. **RSSI too low in cabinet** — Placement/attenuation. Free sample: [/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet](/entries/sierra-wireless-mdm-rssi-rssi-too-low-in-cabinet). 2. **Antenna connector loose** — SMA torque / water intrusion. [/entries/sierra-wireless-mdm-ant-antenna-connector-loose](/entries/sierra-wireless-mdm-ant-antenna-connector-loose). 3. **SIM not provisioned / APN** — Carrier side. [/entries/sierra-wireless-mdm-sim-sim-not-provisioned-apn](/entries/sierra-wireless-mdm-sim-sim-not-provisioned-apn). 4. **Wrong APN after SIM swap** — Config drift. [/entries/sierra-wireless-mdm-apn-wrong-apn-after-sim-swap](/entries/sierra-wireless-mdm-apn-wrong-apn-after-sim-swap). 5. **Modem FW bricks OCPP path** — Recovery image on stable power; don’t leave half-bricked. [/entries/sierra-wireless-mdm-fw-modem-fw-bricks-ocpp-path](/entries/sierra-wireless-mdm-fw-modem-fw-bricks-ocpp-path). ## Log sources / tools | Source | What you pull | |--------|----------------| | ALEOS | RSSI/RSRP history, APN, FW version, LED pattern | | CSMS | Heartbeat gaps, disconnect storms, BootNotification | | Known-good external antenna | Placement prove | | Carrier portal | SIM active, APN profile | ## Field checklist (first 15 minutes) 1. Local Ready + Cloud red? → modem/backhaul branch first. 2. Pull ALEOS RSSI vs OCPP disconnect timestamps. 3. Inspect antenna location and SMA. 4. Temporary external antenna test. 5. Confirm SIM/APN only after RF path looks sane. 6. FW recovery only with stable supply and OEM image. 7. Do not RMA power modules for Heartbeat-only failures. ## When to escalate **Carrier / network** — Provisioning, private APN, firewall to CSMS. **Modem OEM** — RF fail after external antenna prove; bricked FW after recovery fails. **EVSE OEM** — Protective Faulted with healthy Heartbeat (different branch). ## Worked examples **A — Soft-offline evenings only; antenna inside door.** External antenna restores link → relocate permanent antenna. **B — After SIM swap, ALEOS up, OCPP dead.** Wrong APN. **C — RSSI “fine” snapshot; websocket drops every 90s.** Keepalive/MTU/NAT—not a new modem first. ## False friends | Looks like | Often actually | |------------|----------------| | Dead charger | Soft-offline modem path | | Bad power supply | Antenna in shield / loose SMA | | Needs new EVSE board | Wrong APN after SIM swap | | Random Faulted | BootNotification storm after reconnect | ## Ticket hygiene Export ALEOS signal history with CSMS Heartbeat gaps on the same clock. Scrub site credentials. Note cabinet metal and antenna photos. ## Related learning [/help](/help) · [/brands/delta](/brands/delta) (backend unreachable cousins) · [/entries/protocol-net-c01-dns-resolution-failure-to-csms](/entries/protocol-net-c01-dns-resolution-failure-to-csms) ## RF vs OCPP (drill) Heartbeat dead + local Ready → backhaul first. Isolation Faulted + Heartbeat alive → not a modem ticket. RSSI snapshot “OK” with 90-second drops → keepalive/MTU/NAT or multipath fade—not “buy a new modem” as step one. Antenna inside the door is the most common self-inflicted soft-offline on metal cabinets. After SIM swaps, verify APN before reseating EVSE control boards. FW recovery needs stable DC and the OEM image—random files brick units. ## Placement checklist 1. Is the antenna outside the Faraday cage of the door/cabinet? 2. Is the SMA finger-tight then wrenched per OEM (not loose, not crushed)? 3. Does a temporary external antenna restore Heartbeat for 15 minutes? 4. Do disconnects still track weather or only shift changes (SIM/APN work)? 5. Is FW current and known-good, or was there a mid-update brownout? If 1–3 fail, stop blaming OCPP URL first. If 1–3 pass and APN is wrong, stop blaming antennas. If FW is bricked, recover once on stable power—then board. Pair every modem ticket with CSMS Heartbeat CSV so “RSSI fine” arguments die against timestamps. Browse Sierra Wireless entries below or [database](/database?brand=sierra-wireless). For cellular failover flapping on Tritium and similar, see also [/brands/tritium](/brands/tritium). Soft-offline without RF evidence is still an OCPP URL/cert problem until proven otherwise. ## Closeout template “Local Ready: [y/n]. Heartbeat gaps: [times]. ALEOS RSSI/RSRP: [range]. Antenna: [inside door/external/prove result]. SIM/APN: [verified]. FW: [version/recovery]. Next owner: [carrier/network/modem OEM/EVSE if protective]. Power stage opened: no.” Attach the CSMS Heartbeat CSV whenever possible. Prefer RF placement prove before modem RMA, and modem/APN prove before EVSE control-board RMA. Keep the order honest. When in doubt, restore Heartbeat with an external antenna prove before you touch EVSE HV covers.

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.

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.