Skip to content

How it behaves

  • A setpoint applies within 5 s and stays until you change it, also across a restart on our side.
  • Write a point only when its value changes, at most once per second, and always the whole point with function code 16. A refused write returns a Modbus exception and writes nothing.
  • 704_WSet = 0 puts the PCS in standby. The next setpoint other than 0 starts it again.
  • 704_WSetEna = 0 or 802_SetInvState = 1 ends control.
Limit Points
Power 802_WChaRteMax, 802_WDisChaRteMax
Battery limit now 802_AChaMax, 802_ADisChaMax × 802_V

Read both every cycle and stay below the lower of the two: the battery limit changes with state of charge and temperature. We cap your setpoint to it anyway and hold 0 W during a fault, so 701_W can be lower than you asked.

  • 802_SoC is the state of charge. At its lower limit discharging stops, at its upper limit charging.
  • 713_WHRtg is the usable energy, 713_WHAvail the energy available now.

701_InvSt says what the PCS is doing: 3 running, 7 standby, 6 fault, 0 off. Every value: Register reference.

At 701_InvSt = 6, stop asking for power. A fault clears by itself once its cause is gone, unless it is latched:

  • 802_AlmRst = 1 resets latched faults once their cause is gone, for example after a grid outage. It reads 0 again once done.
  • One write per reset. Never write 802_AlmRst on a timer.

How much a system says about its faults depends on the system. A CBEB3344 names each fault and who has to act: see CBEB3344.