ESS consisting of
1 Victron Multiplus 5000
2 Vicntron MPPT
2 Pylontech US5000
4 solar panels 550W
After a power cut, it switched over to the mains and the mains connection to
the Multiplus was also cut off, but the Multiplus remained on and the system’s batteries
were almost completely discharged. What is the best way to slowly recharge the batteries now?
You could set the maximum charging current to whatever you feel comfortable with. But my Pylontech batteries regularly discharge to 10%, and then they’re charged at full whack. Of course, the BMS limitations still apply.
Did the BMS, or rather the MultiPlus, switch off the batteries?
Why didn’t the two MPPTs charge the batteries?
If you want to charge the batteries fully, and there isn’t much sun coming in at the moment, I’d charge them using the “Keep batteries charged” function and leave them like that for a while.
The 5000 only has a charging current of 70 A, i.e. 35 A per US5000, which can handle a charging current of 80 A or 100 A, depending on the firmware.
Of course, you can reduce the charging current further, as suggested by @pcdewolff.
The latest US5000 firmware (2.3) is significantly more cautious about charging at the upper end of the SOC range.
Thanks. When I checked recently, the Pylontech batteries weren’t detected; now they are, but the MPPTs still aren’t charging them. I still don’t know why, or what could be causing it.
Yes, the MultiPlus can do that; I’ll do that too. I’d just like the batteries to charge and discharge more slowly to avoid the individual cells becoming unbalanced.
You can set the maximum charge and discharge current in VictronConnect, can’t you?
And if you’re worried about imbalance, set ESS to ‘Keep charged’ for a few hours. In ESS, you can also set a scheduled full charge, so it balances the cells every week, for example.
This can happen if it was a deep discharge and the master was the first battery to disable its discharge FET.
After doing that, the battery enters a deep sleep, during which it doesn’t send any CAN messages.
But it keeps the charge FET in an ON state and after you apply charging power and the cells reach a reasonable SOC, it resume communication.
But here there is a vicious circle, because without CAN comm, there is no battery detected and no charging applied.
Rare use case that is not handled properly in the DVCC and in the battery’s firmware…
Is the red LED blinking on the US5000?
Was the battery discharged slowly, or was there a high discharge current?
What battery voltage do you see on the Cerbo GX or MultiPlus? Zero? 44-45? 48?
If the battery is not detected and no voltage is reported, there are two possible causes based on my personal experience:
Low-voltage (LV) protection is active. You may need to connect to the battery using a console cable, check the BMS status, and clear the fault if necessary. In some cases, the battery can recover when charging voltage is applied.
The MOSFETs on the main BMS board have failed. This can happen during high-current charging or discharging. If the MOSFETs are damaged, the entire BMS board should be replaced.
I’m extremely critical of this design. The BMS is supposed to protect the battery, yet its own power electronics can fail permanently under normal operating conditions. In my experience, the protection circuitry itself becomes the point of failure.
A battery protection system that requires replacing the entire BMS board after such a failure is, in my opinion, a serious design weakness. Especially when the battery has never been operated outside its specified current limits.