The EVSE Directory · Field sheet · BTC Power · BTC-HP-ISO
BTC-HP-ISOFree sampleHP150 isolation trip
BTC Power · HP150 · DC Fast Chargers
Safety
Qualified EVSE personnel only. Follow site LOTO and OEM HV boundaries.
How it presents
Symptom
BTC HP150 isolation trip — cable/moisture/ISO path on HP family before power-module crates. Field techs should correlate HMI/Cloud timestamps with HP family often needs power-cabinet vs dispenser CAN check before module swap
Root causes (by observed frequency)
- #1 Primary field cause for BTC-HP-ISO (HP150 isolation trip) on BTC Power
HP family often needs power-cabinet vs dispenser CAN check before module swap
- #2 Secondary installation or harness issue exposed under load or weather
- #3 Config/firmware drift after update or board/SIM swap
- #4 True OEM module failure after cable/site/config paths are proven
Diagnostic procedure
1. Capture BTC Power HMI/Cloud message for BTC-HP-ISO, connector ID, and last good session
Expected: Exact string + scope
Tools: phone, CSMS
2. Correlate logs; decide one gun vs cabinet vs site for “HP150 isolation trip”
Expected: Fault boundary
Tools: CSMS/OEM cloud
3. Run the rank-appropriate field checks for BTC-HP-ISO (cable/PE/network/cooling as applicable)
Expected: Cause supported or excluded
Tools: DMM, IR, known-good
4. Known-good cable/gun/stall prove when the failure mode allows
Expected: Follows asset
Tools: known-good
5. Escalate BTC Power OEM with evidence pack — HP family often needs power-cabinet vs dispenser CAN check before module swap
Tools: ticket
The fix
Resolve BTC-HP-ISO on BTC Power by ranked field cause (HP family often needs power-cabinet vs dispenser CAN check before module swap), then validate a full session.
Suspect BTC Power assembly for BTC-HP-ISO
OEM channel; keep serials
- Stabilize and document BTC-HP-ISO presentation before replacing modules.
- Correct the ranked field cause for HP150 isolation trip; prefer cable/site/config fixes first.
- Clear latches in HMI/CSMS only after the cause is removed.
- Run authorize → handshake → ≥5 minutes energy → clean stop validation.
- File scrubbed photos, firmware, and readings with the confirmation.
Related entries
Field confirmations (1) — subscribers only, one per account.
Missing a sibling fault? Request an entry