question

I guess you have picked "Optimized (with BatteryLife) in the ESS-Settings.

In that case the ESS will calculate an "Active SOC limit" based on the previous charge cycle(s), which is shown in the settings as well.

Still no idea why BatteryLife is involved in my setup.

Today, I've noticed that my Cerbo shows up with ESS#5 (slow charging enabled) and charging seems to be limited to 10A. According to my knowledge, ESS#5 is part of BatteryLife in order to maximize battery life.

But as I use "External Control", this shouldn't kick in at all, shouldn't it?

My current SoC is 30% with a current of 53.2V (16p) and I'm quite confident that I could increase the charging current at this point.

I have exactly the same problem and can‘t figure out where battery life come from.

Best regards

Marcel

I also have the same problem. Are there any new findings?

Not really. Sometimes, it works if I change the ESS Mode to "Enabled" and then back to "External control".

I have some progress on this situation.

1st as periodicaly i update set point, in the same time i set Modbus register 2900 to 10 batterylife disable

This need to have good connexion to MultiplusII because in case of loss of connection Batterylife take place again and need a multi reset (on/off) for clearing.

I've seen that even if I set External Control for the system mode, somehow, in the background, the BatteryLife is still working and adjusts the Active SoC Limit despite the fact that is never taken into account.

In a way is good, because the system still tracks the solar conditions and when needed is there with the real situation.

And, probably, the state of all variables are sent to VRM and VRM is showing them accordingly. Maybe some small improvements needs to be done.