BTC Power

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, /entries/protocol-ocpp-f02-heartbeat-timeout-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.

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. Stage: /entries/protocol-ccs-h03-cable-check-isolation-fail, /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.

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. Modem path: /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. Related: /entries/protocol-nacs-h01-nacs-handshake-timeout-on-adapter-path, /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. PQ: /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-h02-sdp-failed-secc-not-responding, /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).

8. Stuck Faulted after reboot — Software latch, not endless power cycles (/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).

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.

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.