BESS undervoltage at cabinet

How it presents

Symptom

Fluence BESS reports an undervoltage (UV) inhibit at the EVSE feed — either the PCS AC output or the shared DC bus — so dependent chargers brown out mid-session or latch Faulted while the BESS HMI independently alarms UV. It shows up most on hot afternoons when several dispensers ramp together and SOC is already drawn down from an overnight fleet pull, so the first minutes of triage are about proving whether the EVSE is really broken or the depot just asked for more than the BESS could deliver at that SOC.

Root causes (by observed frequency)

1. #1 SOC too low to support commanded discharge power once several EVSE ramp to full current simultaneously

   Check the EMS discharge power curve vs SOC first — this is the single most common Fluence depot UV trigger and is not a hardware fault

2. #2 Feeder or transformer voltage sag upstream of the BESS under the same coincident load

   Measure directly at the EVSE input cabinet under load, not just at the BESS terminals, to rule out a shared site power-quality problem

3. #3 UV protection setpoint tightened too aggressively after an EMS firmware or config push

   Compare current UV threshold against the commissioning baseline before assuming a new hardware problem appeared overnight

4. #4 PCS voltage sensor drift or a failed sense lead reporting a false UV that the real bus voltage doesn't support
5. #5 Depot load management (LMS) not staggering EVSE ramp-up, so simultaneous inrush spikes exceed what the BESS discharge ramp rate can track

Diagnostic procedure

1. 1. Pull the EMS event log and line up the UV timestamp against the EVSE Faulted timestamps and the SOC trend line for the same window

   Expected: UV and EVSE faults cluster within seconds of each other, both trailing a SOC dip or a plug-in surge

   Tools: EMS historian, CSMS session log

2. 2. Repeat the load event (or wait for the next peak) and measure voltage directly at the EVSE distribution cabinet, not the BESS terminals

   Expected: Voltage sags below nameplate minimum at the cabinet in step with the alarm, confirming a shared feed issue rather than an EVSE-only fault

   Tools: True-RMS DMM or power quality recorder, qualified electrician

3. 3. Check the EMS discharge power limit curve and current SOC against the depot's simultaneous-charging power draw

   Expected: Commanded discharge power exceeds what the curve allows at the observed SOC

   Tools: EMS HMI / dashboard

4. 4. Review the LMS/scheduling config for stagger settings on EVSE ramp-up and simultaneous session caps

   Tools: Fleet CMS or site LMS admin console

5. 5. If SOC, feeder voltage, and LMS all check out clean, package an evidence pack (EMS log excerpt, cabinet voltage trace, session timeline) and hand off to the BESS specialist for PCS/cell-level review

   Tools: ticket template, scrubbed screenshots

The fix

This is almost always an energy-management or site-power problem, not a failed EVSE power module — restoring SOC headroom, staggering sessions, or fixing a feeder sag clears it far more often than any charger part swap.

1. Stop rotating EVSE power modules or dispensers just because they were the ones that faulted first — if the whole pad sagged together, the hardware downstream of the BESS is very unlikely to be the cause.
2. Work with energy management to restore usable SOC headroom before peak windows, or adjust the depot's charging schedule so fewer vehicles ramp to full current at the same instant.
3. If the cabinet voltage measurement showed a real sag, loop in an electrician to check feeder loading, transformer tap settings, and connection torque between the BESS and the EVSE distribution gear.
4. Only after site voltage and SOC are confirmed clean should the ticket go to BESS ops or the OEM, and only with the EMS log, cabinet voltage trace, and session timeline attached so the specialist isn't starting from zero.
5. Once the underlying cause is corrected, run a validation session during a comparable peak-load window to confirm the UV inhibit no longer trips before closing the ticket.