VE.Bus System - MultiPlus - Low battery: Alarm (with PACE BMS)

[bartc]

Hello! I’ve noticed my inverter stops at an unexplained voltage with the message:
“VE.Bus System - MultiPlus [275] - Low battery: Alarm.”
This is similar to the message in this topic.

My system consists of a Victron MultiPlus-II 48/5000/70-50 GX and two parallel-connected LifePo4 10kWh battery packs with a PACE P16S200a BMS.

Here are the settings in VE Configure:

I also don’t see any alarms coming from the BMS (via dbus-spy), but I do see the ‘Info/MaxDischargeCurrent’ set to 0:

When I look at the MultiPlus dbus data, I see that ‘Alarms/L1/LowBattery’ is set to 2, which I suspect is blocking discharge:

If I set ‘Controlling BMS’ to ‘None’ in the DVCC menu, I can discharge until the BMS intervenes.

Now for the question: Is the MaxDischargeCurrent value of 0 the cause or the consequence of the MultiPlus alarm? Do you see any other peculiarities?
Would it also be perfectly fine to bypass this by having the MultiPlus manage the charging instead of the BMS (which intervenes on its own if necessary anyway)?

Thanks!

[RensvDr]

I am currently experiencing the same issues with a pace bms, did you ever solve this issue?

I have the problem under soc 70%, above it is fine.

Dcl is 620a and now low battery voltage on the inverter.

[BjoernK (Björn Kellermann)]

Do you have the PACE BMS Tool to configure BMS parameters?
First check alarms in Victron GUI v2 → battery
Than check the same with the BMS Ttool.
Than check you BMS parameters.
Possible root causes:

• single cell under voltage alarm
• cell voltage deviation is to high
• cell under temperature alarm
• pack under voltage alarm
• environment under voltage alarm
• Low SOC

I am not sure if MP2 DC ripple can cause this alarm as well.

Discharge Current Limit (DCL) = 0 is a strong indicator and a warning before BMS protect (open discharge MOSFETs).

You can graph “battery parameters” like DCL in VRM advanced tab.