Siemens

Siemens — field brand hub

Siemens tickets in this corpus cluster on Sicharge D. Isolation, cluster LMS conflicts, MID meter faults, and touch HMI freezes dominate. The classic waste of time is treating an LMS ownership or meter-path problem as an SECC board failure. Name Sicharge D and whether the stall is alone or in a cluster load-management group before you open covers.

When this OEM shows up / cabinet vs dispenser

Sicharge D sites often sit in multi-stall clusters with shared LMS policy. Ownership:

Gun / SECC / isolation side: CableCheck IR, wet cable, latch—prove with known-good cable.

LMS / cluster side: Soft 0 A, SuspendedEVSE, or “conflict” codes while siblings still charge under budget—policy and CT map, not a dead gun.

Meter path: MID / mid-meter faults that break billing or refuse start while energy hardware looks fine.

HMI / controller: Touch screen unresponsive with Controllers still heartbeating—preserve logs before reboot theater.

Photograph connector ID, cluster group, and peer stall status. Do not condemn SECC because CableCheck failed once in the rain or because LMS capped the stall at peak.

How faults typically present

HMI

• Sicharge D touch banners (SIE-SD-*).
• Frozen UI with power stage still audible / LEDs alive.
• Soft curtail banners without hard Faulted during peak demand.

OCPP / backend

• Faulted at CableCheck with Siemens vendor strings—log verbatim.
• LMS conflict: may look like SuspendedEVSE / Unavailable / 0 A without GroundFailure. See /entries/protocol-load-01-dynamic-load-management-caps-to-0-a.
• MeterValues missing or PowerMeterFailure with Authorize OK—meter path (/guides/metering-payment).
• Use /guides/ocpp-faulted-triage when status is Faulted without a clear latch.

Physical cues

• Wet CCS cable, stuck touch overlay after sun/heat, CT work at the gear after expansion, cluster stalls dying together at the same minute.

Ranked common failure patterns

1. Sicharge isolation — Cable/gun IR or moisture before SECC/ISO board. Free sample: /entries/siemens-sie-sd-iso-sicharge-isolation. Protocol: /entries/protocol-ccs-h03-cable-check-isolation-fail, /guides/ccs-handshake-basics.

2. Cluster LMS conflict (early-access / Pro depth) — Budget, priority, CT map, or heartbeat failsafe across the cluster. Sibling timing is the tell. Entry: /entries/siemens-sie-sd-lms-cluster-lms-conflict. Site power angle: /guides/site-power-quality-basics. Not a free sample unlock.

3. MID meter fault — Measurement / seal / mid-meter path; sessions may authorize then fail billing or refuse start. Entry: /entries/siemens-sie-sd-met-mid-meter-fault. Related: /entries/protocol-met-01-energy-meter-crc-error, /guides/metering-payment.

4. Touch HMI unresponsive — Soft hang, overlay, or supply to UI; Controllers may still talk OCPP. Capture backend event first, then controlled reset. Entry: /entries/siemens-sie-sd-hmi-touch-hmi-unresponsive. Stuck Faulted after reboot: /entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot.

Log sources / tools

Source	What you pull
Sicharge HMI / service	Banner, connector ID, LMS group, meter status
Siemens backend / OCPP	StatusNotification, MeterValues, Heartbeat
LMS / cluster config	Budget, CT map, priority, failsafe mode
Known-good cable / DMM	Isolation prove; loaded voltages if PQ suspected

Field checklist (first 15 minutes)

1. Photo HMI + connector ID + peer stalls in the same LMS group.
2. Isolation vs soft 0 A vs meter vs frozen UI—name the branch.
3. Weather / recent cable or CT work?
4. If ISO: dry + known-good cable before HV.
5. If LMS: confirm budget/CT/heartbeat before SECC RMA.
6. If meter: Authorize vs MeterValues timeline.
7. If HMI freeze: export events before reboot spam.

When to escalate

Electrician / site power — Feeder sag matching cluster trips; CT wiring after expansion; PQ events.

LMS / CSMS ops — Policy caps during revenue hours; wrong connector mapping; backend identity after board work.

Siemens OEM — Confirmed ISO after known-good cable; meter hardware after seal/path proven; HMI hardware after soft recovery fails.

Do not escalate LMS curtail as isolation, or HMI freeze as a power-module epidemic. Payment-only failures belong to the PED stack (/entries/ingenico-pay-to-payment-terminal-timeout), not Sicharge SECC.

Worked examples

Example A — CableCheck isolation, one connector, after wash-down. Known-good cable clears it. Do not replace SECC on a wet gun.

Example B — Four Sicharge stalls show 0 A at peak; no GroundFailure. LMS cluster conflict / budget. Pull LMS group IDs and CT map before HV. Sibling timing is evidence.

Example C — Authorize OK, MeterValues missing, billing angry. MID meter path—not isolation. Photograph meter seals and export MeterValues gaps.

Example D — Touch frozen, Heartbeat alive, peer stall charging. Capture backend events, then controlled UI recovery. Do not treat as pad-wide power death.

False friends

Looks like	Often actually
Dead SECC	LMS soft cap / cluster conflict
Power module fail	MID meter / billing path
Whole site down	One LMS group misconfigured
Needs reboot	Hard latch returning in <1 min — find cause

Related learning

/learn/reading-ocpp-statusnotification · /learn/site-power-vs-charger-fault · /help

Ticket hygiene

Capture: HMI photo, connector/port ID, peer status, OCPP errorCode + vendor string verbatim, weather/service notes, and (for thermal/grid) a loaded measurement. Scrub customer PII before /request or Pro Q&A. Prefer one branch per ticket—do not merge money-path and HV into one RMA narrative.