NACS field notes

North American Charging Standard (NACS) ports, adapters, and thermal behavior as seen in the field. Complements CCS guide; does not replace OEM torque or HV procedures. Native NACS and adapter paths fail differently — say which one you have in the first sentence of the ticket.

High continuous current means heat is a first-class failure mode. A session that “starts fine” then collapses at ramp is often thermal or contact resistance, not a mystery protocol bug.

When to use this guide

• Native NACS port overtemp / derate to zero
• Adapter-path failures (NACS vehicle on CCS1 dispenser or reverse)
• Latch / proximity intermittent on NACS handle
• Session OK at low kW, collapses when power ramps
• After handle/cable service, thermal codes appear
• Fleet reports “only Brand X adapters work”

Related: NACS · thermal · adapter

How it presents

Symptom	Likely layer
Overtemp / derate	Handle sensor, pin contact, cooling (if liquid)
Handshake timeout on adapter	Adapter electronics, CCS path behind adapter, vehicle
Latch fail	Mechanical latch, microswitch, bent tongue
Works on native NACS stall, fails with adapter	Adapter or CCS-side dispenser
Works with adapter on CCS, fails native NACS	Native handle/inlet/thermal path
Intermittent disconnect	Latch, PP/proximity, driver tug, damaged inlet door

Presentation false friends

Looks like	Often actually
“NACS incompatible”	Burnt pins / high resistance on that handle
Bad vehicle inlet	Adapter unlocked or wrong orientation
Needs coolant flush	Thermal sensor unseated after handle service
Protocol bug	Derate map after firmware — sister stall comparison
CCS CableCheck fail “on NACS truck”	Adapter + CCS IR path — use CCS guide behind the adapter
Random Faulted	Hot pins from prior session; cool-down not observed

Decision tree

1. Native NACS port or adapter in path?
   ADAPTER ↓ treat as CCS + adapter stack
   NATIVE ↓
2. Thermal derate present?
   YES → inspect pins, sensor, airflow/coolant, repeated high-power sessions
   NO ↓
3. Proximity / latch stable?
   NO → handle / inlet mechanical
   YES ↓
4. Handshake / power stage
   → apply CCS-like stage thinking for the control path in use
5. Only one adapter brand fails?
   → quarantine that adapter family; don’t condemn the stall yet

Ranked causes

1. Contact resistance / dirty or burnt pins after high-power use.
2. Thermal sensor faults or poorly seated sensors after handle service.
3. Adapter path issues — damaged adapters, unlocked adapters, CCS IR fail behind adapter, cheap pass-through problems.
4. Inlet contamination — debris, ice, bent doors, packed snow.
5. Firmware thermal maps too aggressive after update — compare sister units.
6. Vehicle-side thermal — confirm with second vehicle before condemning EVSE.
7. Liquid cooling issues on cooled NACS assemblies — see liquid cooling loops guide.
8. Latch wear from high cycle fleet depots.

Worked examples

Example A — Derate to near zero after 3 minutes at high kW

Observed: Starts ~150+ kW class then falls; OEM thermal code on handle; pins discolored.

Triage: Contact resistance / cooling / sensor. Thermal camera after session (careful — hot). Inspect pins; note ambient and prior session stacking.

Fix: Cable/handle per OEM; do not keep forcing high power into burnt pins. Validate sustained power after repair.

Example B — Native NACS stall OK; CCS1 + adapter fails CableCheck

Observed: Same truck; adapter path only fails; CCS logs show isolation fail.

Triage: Adapter and CCS cable/dispenser behind it. Try second adapter; try known-good CCS cable.

Fix: Often adapter or CCS IR — not the native NACS inlet. Quarantine bad adapters.

Example C — Latch errors, drivers say “won’t lock”

Observed: Intermittent; worse in freeze; microswitch chatter in OEM view.

Triage: Mechanical latch, ice, bent tongue, inlet door interference.

Fix: Handle/inlet mechanical service. Avoid “just yank harder” coaching that breaks more latches.

Example D — Fleet-wide derate after firmware Friday

Observed: Many native NACS stalls derate similarly; pins look fine; sensors seat OK.

Triage: Firmware thermal map. Compare to release notes; sister site on old firmware.

Fix: OEM bulletin / rollback per OEM — not fifty cable swaps overnight.

Example E — Coolant residue near NACS handle after “overtemp”

Observed: Sweet smell / residue; thermal + flow codes possible.

Triage: Stop sessions. Liquid cooling loops guide. HV contamination risk.

Fix: LOTO, OEM leak procedure, cable assembly replacement as required — not towel-and-go.

Field procedure

1. Note native vs adapter; photograph adapter markings / certifications / damage.
2. Inspect pins and latch under bright light; document discoloration.
3. Check for coolant residue on liquid-cooled NACS assemblies.
4. Review thermal derate logs / OEM codes; note time-to-derate and kW curve.
5. Retest after cool-down; note ambient; avoid stacked hot retries.
6. Swap cable/handle assembly only with scrubbed provenance and OEM parts guidance.
7. Validate to sustained power, not a 30-second start; include adapter path if fleet uses adapters.
8. If adapter involved, record whether unlocked/locked adapters are required by site policy.

Inspection checklist

• Native vs adapter stated
• Pin condition photographed
• Latch / door / inlet debris checked
• Thermal codes + time-to-derate logged
• Ambient / prior session heat noted
• Coolant residue absent/present
• Second vehicle or second adapter tested when available
• Sister stall firmware compared if site-wide

Safety

High continuous current means heat. After a derate event, assume pins may still be hot. HV rules unchanged vs CCS. Discharge waits still apply. Never file pins “to clean them up.” Do not defeat thermal sensors. Adapters hanging from inlets are mechanical and HV risks — support the cable. Unlocked adapters under load are a hard no.

Weekend / after-hours notes

• Hot-pin calls after evening peak: cool-down time is data — record it; don’t immediate-condemn without inspection light.
• Adapter chaos on weekends: photograph and bag suspect adapters for day-shift quarantine rather than debating brands in the dark.
• Freeze nights: latch ice vs true motor fail — gentle OEM-approved thaw only; no torches on plastic inlets.
• If pins are burnt, mark stall Unavailable; driver retries make it worse.

Documentation template (ticket / handoff)

SITE / STALL / CABLE ID:
DATE/TIME:
TECH:
PATH: native NACS / adapter (brand/model/photo):
VEHICLE: make/model/year:
AMBIENT / PRIOR SESSIONS:

SYMPTOM: overtemp / latch / handshake / other:
TIME TO DERATE OR FAIL:
PEAK kW BEFORE FAIL:
OEM CODES:

PIN / LATCH INSPECTION:
COOLANT RESIDUE: yes/no
SECOND VEHICLE / SECOND ADAPTER RESULTS:
FIRMWARE (stall vs sister):

ACTIONS:
ROOT CAUSE / HYPOTHESIS:
PARTS:
VALIDATION SUSTAINED kW / DURATION:
ADAPTER POLICY NOTE FOR OPS:

Additional failure modes

Mode	Clues	Action
Stacked sessions without cool-down	Derate earlier each attempt	Enforce cool-down; inspect pins
Inlet door bent into latch path	Latch fail only on certain vehicles	Inlet / body repair
Adapter unlocked under vibration	Intermittent disconnect mid-ramp	Policy: locked adapters only; quarantine
Sensor harness reversed after service	Instant thermal fault at low kW	Reseat/orient per OEM
Cabin heat soak, gun in sun	Afternoon-only derates	Shade/ambient note; still inspect contacts
Vehicle battery thermal limit	Second EVSE also derates same truck	Vehicle-side — don’t RMA handle
Mixed native/adapter fleet confusion	Ticket says “NACS broken”	Force native vs adapter in first line
High cycle latch wear	Depot with tight turnaround	Wear parts plan; don’t wait for total fail

Adapter path stack (explicit)

When an adapter is present, failures can live in any layer:

1. Vehicle NACS inlet mechanical / thermal
2. Adapter contacts, electronics, lock
3. CCS1 dispenser cable / IR / PLC
4. CCS SECC / power stage
5. LMS / auth (less common if EIM works)

Test matrix that saves parts:

Test	Result meaning
Native NACS stall	Isolates vehicle+native path
Same truck + second adapter	Adapter-specific
Same adapter + second CCS cable	Cable behind adapter
Different truck + same adapter	Vehicle vs adapter

Thermal derate log reading (practical)

Record: ambient, starting SOC, peak kW, time-to-first-derate, handle vs inlet vs cable sensor IDs if OEM shows them, whether coolant pump was healthy. A derate with cold pins and healthy cooling points to sensor/map; hot discolored pins point to contact resistance.

Parts hygiene

• OEM handles only; unknown aftermarket thermal behavior is not your experiment on a revenue stall
• Bag and tag removed handles with stall ID and hour-meter/cycle count if available
• Do not sand pins; replacement is the fix when plating is gone
• After handle swap, clear thermal latches per OEM and run a sustained validation, not a tap test

Sustained-power validation script

After any thermal or handle work, do not close the ticket on a 20-second green HMI.

1. Ambient and stall ID recorded
2. Cool-down complete if prior derate occurred
3. Native path session: ramp to site-typical kW
4. Hold until handle/inlet temperatures stabilize per OEM or ≥10–15 minutes if OEM silent
5. Note any derate curve (time, kW)
6. Clean stop; inspect pins warm (PPE/awareness — still hot)
7. If fleet uses adapters: one adapter-path session with approved adapter only
8. Document cable/handle serials

Ticket mistakes that burn time

• Writing “NACS bad” without native vs adapter
• Omitting ambient and prior session stacking
• Replacing handles without OEM thermal clear procedure
• Leaving burnt-pin stalls Available for driver retries
• Mixing coolant top-off into a dry contact-resistance failure

Cross-check derate · adapter · thermal.

Contact resistance vs cooling vs sensor (sort)

Evidence	Contact	Cooling	Sensor/map
Discolored/burnt pins	✓
Coolant flow alarms		✓
Cold pins + instant thermal fault			✓
Sister stall same firmware derates same			✓ firmware map
Pump healthy, hot pins	✓	maybe inadequate
Only one vehicle derates everywhere	vehicle thermal

Always state native vs adapter in the first sentence of every NACS ticket. Cross-link CCS work when adapters are in path: CCS · NACS.

After-hours burnt-pin protocol

Mark Unavailable, photograph pins, bag nothing that is still hot, notify ops that retries will worsen damage, schedule OEM handle/cable with cool-down time built in. Do not file or “polish” pins.

Quick reference

Native vs adapter first. Heat is a first-class fault. Validate sustained power. Quarantine bad adapters. Never defeat thermal sensors. NACS · derate · latch · cooling.

Radio / ops coordination lines (NACS)

Use short, factual updates — not blame:

• “Stall 12 Unavailable: burnt NACS pins; handle ordered; do not retry high power.”
• “Adapter path only failing; native NACS OK; quarantining adapter brand X pending vendor.”
• “Fleet-wide derate after firmware Y; pins clean; holding for OEM bulletin before cable swaps.”

Drivers retrying hot damaged pins is how one bad contact becomes a melted inlet. Ops messaging matters as much as the wrench.

Escalate when

• Fleet-wide derate after firmware → OEM bulletin
• Only one adapter brand fails → ban that adapter pending vendor fix
• Inlet damage → body shop / OEM inlet kit
• Coolant on HV → stop-work OEM procedure
• Thermal sensor replacements recurring → handle harness routing issue
• Metrology-unrelated but safety: repeated arcing marks → Unavailable until repaired

NACS overtemp · thermal derate · adapter · latch · pin damage

Related fault entries

• NACS-H01 — NACS handshake timeout on adapter path
• NACS-H03 — NACS thermal derate to zero
• CP-XP-NACS — NACS port overtemp
• BTC-HP-NACS — NACS adapter path fault
• CAB-NACS — NACS handle overtemp