Alpitronic

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/ocpp-faulted-triage.
• Authorize / ReaderFailure with Ready energy path → money path (/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. Stage map: /entries/protocol-ccs-h03-cable-check-isolation-fail. Coolant contamination after swaps: /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. 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. Related: /entries/ingenico-pay-to-payment-terminal-timeout, /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. Guide: /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.

Example C — Cards fail, FreeVend works, modules healthy. Money path only. Pull PED/host timeline; leave HYC power stage closed. /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/ccs-session-stages · /help