The EVSE Directory · Field sheet · Tritium · TRI-PK-ISO
TRI-PK-ISOFree samplePK350 isolation fault
Tritium · PK350 · DC Fast Chargers
Safety
Qualified EVSE personnel only. Follow site LOTO and OEM HV boundaries.
How it presents
Symptom
PK350 isolation fault — cooled-cable/moisture path; PK liquid-cooled rules differ from RTM air-cooled. Field techs should correlate HMI/Cloud timestamps with PK liquid-cooled path vs RTM air-cooled path changes isolation and thermal triage.
Root causes (by observed frequency)
- #1 Primary field cause for TRI-PK-ISO (PK350 isolation fault) on Tritium
PK liquid-cooled path vs RTM air-cooled path changes isolation and thermal triage.
- #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 Tritium HMI/Cloud message for TRI-PK-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 “PK350 isolation fault”
Expected: Fault boundary
Tools: CSMS/OEM cloud
3. Run the rank-appropriate field checks for TRI-PK-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 Tritium OEM with evidence pack — PK liquid-cooled path vs RTM air-cooled path changes isolation and thermal triage.
Tools: ticket
The fix
Resolve TRI-PK-ISO on Tritium by ranked field cause (PK liquid-cooled path vs RTM air-cooled path changes isolation and thermal triage.), then validate a full session.
Suspect Tritium assembly for TRI-PK-ISO
OEM channel; keep serials
- Stabilize and document TRI-PK-ISO presentation before replacing modules.
- Correct the ranked field cause for PK350 isolation fault; 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.
Field photos
Related entries
Field confirmations (1) — subscribers only, one per account.
Missing a sibling fault? Request an entry