When a commercial BESS PCS trips, the fault code tells you where to look — grid side, DC side, temperature, or communication. Nine out of ten faults resolve without replacing hardware: check the grid relay first, then the DC breaker, then temperature, then CAN/RS485 communication. Read the code, isolate the subsystem, and don't replace the converter until you've walked those four checks.
Start With the Fault Code, Not the Alarm Light
The PCS display shows an active code. Write it down before you touch anything. Codes group into four buckets:
| Fault category | What it means | First check |
|---|---|---|
| Grid over/under voltage, frequency | Grid-side issue, not PCS hardware | Grid meter reading at the PCS terminal |
| DC overvoltage, ground fault | Battery side problem | DC breaker, insulation resistance |
| Overtemperature, airflow | Thermal issue | Cabinet fan, ambient temp |
| Communication lost, no battery | Control layer | CAN/RS485 wiring, BMS power |
1. Grid-Side Faults
These are the most common and the most misunderstood. The PCS sees the grid as abnormal and shuts down to protect itself — it's not broken.
- Overvoltage (e.g., 275V on a 230V system): happens at midday when export is constrained. The PCS trips on overvoltage protection. Fix: check the export limit setting or wait for the grid to normalize.
- Undervoltage: weak grid or large load starting on the same feeder. The PCS rides through brief dips but trips on sustained undervoltage.
- Frequency out of range: rare on a stable grid, common on weak rural networks. The DWH series has adjustable frequency protection thresholds for grid-code compliance.
Don't call support for a grid fault. Read the grid voltage on the PCS screen and compare it to the local grid spec. If the grid number is wrong, the PCS is doing its job.
2. DC-Side Faults
- DC overvoltage: the battery BMS is reporting a cell voltage above the PCS trip threshold. On a Dawnice HZEB-LCT or BS06-S stack, this usually means the charge voltage setting in the PCS menu doesn't match the battery spec — set it to 58.4V for 51.2V LFP.
- Ground fault / insulation error: moisture, a chafed cable, or water ingress in the DC conduit. Megger the DC loop. This is common on outdoor containers in humid climates.
- DC breaker tripped: check the battery disconnect switch and DC fuse. Sometimes a surge or momentary fault pops the breaker without leaving a lasting code.
3. Temperature and Cooling
The PCS derates or trips when its internal heatsink gets too hot. On the Dawnice 1 MW / 2 MWh container, the HVAC runs continuously during charge/discharge cycles.
- Check cabinet fan operation — a failed fan triggers overtemperature within hours.
- Check ambient temperature around the container. A unit in direct sun in 40°C weather may derate even if the fan works.
- On liquid-cooled systems, check coolant level and pump status. Low coolant triggers a PCS fault and a BMS alarm simultaneously.
4. Communication Faults
"Communication lost" or "no battery detected" almost never means the PCS is dead. It means the PCS can't read the BMS over CAN or RS485.
- Check CAN H and CAN L wiring — swapped pair = no communication, no fault.
- Check the 120Ω termination resistor on the CAN bus.
- Confirm the BMS is powered on and its display shows normal operation.
- On multi-container plants, check the daisy-chain communication between containers.
This is the same failure pattern we see on residential hybrid installs — the hardware is fine, the wiring isn't.
When to Call Support
Four situations need the factory, not on-site troubleshooting:
- Internal PCS fault (IGBT fault, DC bus overvoltage that won't reset) — hardware protection has tripped.
- Ground fault that won't clear after Megger testing — possible internal insulation failure.
- Repeating fault after reset — the PCS resets, runs for 10 minutes, trips again.
- Firmware-related fault — a known issue that requires a PCS firmware update.
For the Dawnice container platform, Ruibit Energy provides remote diagnostic support through the EMS cloud interface — most PCS faults can be read and cleared without a truck roll.
A PCS fault code is a diagnostic starting point, not a verdict. Walk the four subsystems in order — grid, DC, temperature, communication — and you'll resolve most calls on site. The ones that need factory support are the ones that fail a self-check test inside the converter itself.
If you're seeing a code you can't clear, send us the fault text, the battery model, and the PCS screen photo. We'll tell you which of the four buckets it's in.
Frequently Asked Questions
Q1: What is the most common PCS fault in commercial BESS?
Grid-side faults — overvoltage, undervoltage, or frequency out of range — are the most common. The PCS shuts down to protect itself when it sees an abnormal grid. It's usually not a hardware failure.
Q2: The PCS says "communication lost." What should I check first?
Check the CAN H and CAN L wiring first — a swapped pair produces exactly this symptom with no other fault code. Then verify the 120Ω termination resistor and confirm the BMS is powered on.
Q3: My PCS trips on overvoltage at midday. Is it broken?
No. This usually happens when export is constrained and the grid voltage rises. Check the export limit setting in the PCS, or wait for the grid to normalize. The PCS is protecting itself, not failing.
Q4: Can I reset a PCS fault myself?
Yes, most grid and communication faults clear with a power cycle. But if the fault repeats within 10 minutes of reset, or the PCS shows an internal IGBT or DC bus error, call support — that indicates a hardware issue.
Q5: Does Ruibit Energy provide remote PCS diagnostics?
Yes. The Dawnice container platform connects to a cloud EMS interface. Most PCS fault codes can be read and diagnosed remotely without an on-site visit. Send us the fault text and battery model and we'll tell you which subsystem to check.
