I have recently observed strange behaviour with Dynamic ESS in Green mode.
My system:
Cerbo GX MK2, Venus OS v3.79
3 × MultiPlus-II 48/6500/100-50, three-phase configuration, one unit per phase
VE.Bus firmware 2602560 / v560
8 × Pylontech US5000, total 38.4 kWh
All 8 batteries checked with BatteryView; firmware v2.3
AC-coupled PV on AC-out: 6.96 kW inverter capacity / 9.6 kWp of panels
Dynamic ESS: Green mode
Maximum DESS charging power: 15 kW
Maximum DESS discharging power: 18 kW
Maximum import and export power: 17 kW
Minimum SOC: 15%
MultiPlus charging current set to 100 A per unit
AC input current limit: 25 A per phase
Today, Dynamic ESS indicates that battery balancing is scheduled.
At approximately 89% SOC, I saw the following on the Pylontech:
CVL: 52.80 V
CCL: 160 A
DCL: 800 A
Battery voltage: approximately 49.98 V
Actual charging current: only approximately 24.3 A, or about 1.2 kW
The BMS is therefore still allowing a maximum charging current of 160 A, but Dynamic ESS is only requesting approximately 24 A at that point.
At the same time, I can see energy/PV being exported to the grid while the battery is not yet at 100%. A few minutes later, Dynamic ESS then starts charging the battery from the grid, while the purchase price at that moment is approximately €0.13/kWh.
This seems illogical in Green mode: first exporting available solar energy and shortly afterwards importing energy from the grid to continue charging the same battery.
If I disconnect the grid connection, the available AC-coupled PV is used immediately to continue charging the battery. The MultiPlus units and the battery can therefore process the charging power without any problem.
My questions:
1. Is this expected behaviour during a balancing cycle scheduled by Dynamic ESS?
2. Could this be related to recent changes in VRM/Dynamic ESS?
3. Why is DESS requesting only approximately 1.2 kW of charging power while the BMS is still allowing a CCL of 160 A?
4. Why is solar energy exported first, only for energy from the grid to be used shortly afterwards to continue charging the battery?
Could this be related to the recent update?
Or is this a known issue
