Overview
A CBEB3344 (C-Battery Energy Box) follows the EMS integration pages. On top of them it says whether it can run and why not, names every fault and who has to act, and keeps a heartbeat both ways. Its own points are in the Register reference.
Limits and state of charge
Section titled “Limits and state of charge”802_WChaRteMaxand802_WDisChaRteMaxare the nameplate rate: fixed for the installation.802_SoCis net: use all of 0–100 %. At 0 % discharging stops, at 100 % charging;802_Statethen reads 5.
States
Section titled “States”802_State |
Name | Meaning |
|---|---|---|
| 1 | DISCONNECTED | Off the DC bus: write 802_SetOp = 1 |
| 3 | CONNECTED | Dispatch it |
| 5 | SOC PROTECTION | At a state of charge limit |
| 99 | FAULT | It cannot run |
713_Sta adds warnings: 0 OK, 1 WARNING (it keeps running), 2 ERROR.
Faults
Section titled “Faults”At 99, stop asking for power and show your operator 701_MnAlrmInfo: the active faults and warnings in words. The battery resumes by itself once the fault is gone, unless someone has to act:
802_AlmRst= 1 resets the PCS’s own faults once their cause is gone, for example after a grid outage.802_EvtVnd1bit 9: physical intervention required, someone has to go to the battery. Do not write802_AlmRstwhile it is set. Safety trips are never reset remotely.
Every bit, and who acts: Fault reference.
Heartbeats
Section titled “Heartbeats”| Point | Whose | Behaviour |
|---|---|---|
715_DERHb |
Ours | +1 every second while it can run. No change for 5 s: treat the battery as gone |
715_ControllerHb |
Yours | +1 every second, both registers in one write. Where the check is on, 10 s without a change holds the battery at 0 W |
One fault does not stop ours: EMS heartbeat lost. You may wait for ours to move before you start counting yours. Write yours on every site, whether the check is on there or not.