MultiPlus-II shutdown on Low battery with fully charged Seplos LiFePO₄

I used screened cat 5e cable (as I had some handy) between my 48/10000 and the MK3-USB connected to my Raspberry Pi, this runs in the same trunking as my DC cables for over a 1 m and I have not had any issues, been rock solid.

My problem is every now and again I lose contact with my ET112 Grid Meter, the wires from that run close to some mains wires, so I used 4 core screened signal wire to try to protect it from any spikes. The strange thing is it loses connection when there there is little activity, I cannot correlate it to a heavy inductive load switching on or off.

In my case, I also noticed behaviour that doesn’t fully correlate with pure battery limitations. Especially the MK3-USB interaction: I’ve had situations where simply unplugging the MK3-USB cable triggered a LOW BATTERY event, even though load was minimal and the inverter had already been running from battery for some time.

That makes me suspect that this may not be a pure “battery can’t deliver surge” problem, but rather a combination of:

  • grid interaction / grid-following behaviour,

  • internal state transitions inside the inverter,

  • and possibly communication or measurement timing effects.

Your point about grid code selection makes sense. Since switching to a stricter grid code, the system seems to disconnect from grid earlier, which may avoid a situation where the inverter tries to “follow” a collapsing grid and compensate aggressively - potentially causing large, fast DC current spikes.

Regarding CAN / communication interference:
That’s a very valid hypothesis. In my setup the battery communication cables and DC cables also run in relatively close proximity. I haven’t yet rerouted them, but it’s something I’m planning to test. Given how sensitive CAN can be to noise and grounding, I wouldn’t be surprised if high transient DC currents or inverter switching noise could affect communication stability.

What makes this more confusing is that:

  • the issue does not consistently correlate with high loads,

  • it can happen at relatively low power levels,

  • and in some cases appears triggered by state changes (grid loss, MK3 disconnect, etc.), not by load itself.

So at this point I’m leaning toward this being a combination of control logic + timing + communication effects, rather than simply “battery too small”.

I’ll continue testing (including temporarily running without Cerbo / MK3), and will report back if I find a repeatable pattern.

Hello, Yuras.

I have same issue as you - System blinks while power outages. Grid code changed to Europe and problem still occurs. Did you change LOM settings or European grid code settings?

@klimanskiy.a Do you mean just lights in the house blinking or the full system goes down for 20-30 seconds? My case was that system was going down completely for 30 seconds every time grid was browning out. I have set the grid code to the European and LOM is enabled there. Since that change I had no single LOW-DC alarms after brownout - even with 4kW load at the time of brown out. System is very stable. The only way I notice transfer switch during brownout is that lights in the house slightly blink, but no power consumer is interrupted. Transfer switch happens smoothly.

I have bought another battery though, but have not included into the system - just calibrating it. I want to observe if 2nd battery with improve transfer switch and will report later.

Oh yeah, one minor LOW-DC alaram I caught recently. It happened while being in Inverter mode. I was turning the cord extension on - it has a button. I heard lout pop inside of it, like some spark, and then house went dark because Inverter enterer “Low DC Voltage” and “High DC ripple”. The battery voltage dropped to 47V. My guess it that Inverter tried to handle very high current, but battery was not able to cope.

@YuriyK regarding CANbus cable inteference. If those happen, then in the status for Canbus would show errors. In my case I never had any errors when I have used properly pinned cable.

Exactly. Everything according your description.

Since you have set Grid Code to EU (I guess with LOM enabled), it could be that there are other factors leading to those two alarms.

  1. Could you add DC ripple charts to the VRM and paste them here?
  2. What model of Multi and batteries do you have?
  3. What wiring for DC is used?

I had this issue on my multiplus 12/1200/50/16 just the other day and assumed it was because of my software. I fixed it by lowering the low voltage disconnect in the multiplus firmware settings by approximately 1v lower than what it was set to. The batteries were at 50-80% soc. This change is still within the spec of my batteries, and my batteries have their own disconnect set at 25%soc. Since then the issue hasn’t come up.

It is perhaps not a solution, it may perhaps be a temporary fix.

@YuriyK, @yuras , hello guys! I’ve ecnountered the exact same issue decribed by @YuriyK: a 30-second delay with a low battery alert during a centrilized grid loss scenario, yet a seamless transition when I manually turn off the AC breaker (even under load). I have the same invertor model (multiplus II 10000VA) and my battery is 314Ah NKON ESS Pro. I haven’t been able to catch a big DC drop in the logs yet. Could you take a look at these configs? Any thoughts on the matter are highly welcome.

This is the one which is active now, but I have not had a chance to test it yet in a grid loss scenario ( I caught a low battery in a pass through mode though :smiling_face_with_tear: ):

TAB: General
System frequency	50Hz
Shore current	50.0 A
Overruled by remote	checked
Dynamic current limiter	unchecked
External current sensor connected (see manual)	unchecked
TAB: Grid
Country / grid code standard	Europe:                EN50549-1:2019
AC input 1	Above selected gridcode plus LOM B (compliant)
TAB: European grid code settings
Use AUX1 as disable FeedIn signal	checked
Maximum AC current for charge or feed in	100.0 %
Maximum generated apparant power	100.0 %
connect waiting time	60 s
connect power ramp	0.0 seconds
low frequency connect value	49.500 Hz
high frequency connect value	50.100 Hz
low voltage connect value	85.00 % Un
high voltage connect value	110.00 % Un
re-connect waiting time	60 s
re-connect power ramp	600.0 seconds
low frequency re-connect value	49.500 Hz
high frequency re-connect value	50.200 Hz
low voltage re-connect value	85.00 % Un
high voltage re-connect value	110.00 % Un
rise-in-voltage protection U>	110.00 % Un
under voltage stage 1	85.00 % Un
under voltage stage 1 delay	0.50 s
over voltage stage 1	115.00 % Un
over voltage stage 1 delay	0.50 s
under frequency stage 1	47.500 Hz
under frequency stage 1 delay	30.00 s
over frequency stage 1	52.700 Hz
over frequency stage 1 delay	30.00 s
under voltage stage 2	80.00 % Un
under voltage stage 2 delay	0.20 s
over voltage stage 2	120.00 % Un
over voltage stage 2 delay	0.20 s
under frequency stage 2	47.000 Hz
under frequency stage 2 delay	0.20 s
over frequency stage 2	53.000 Hz
over frequency stage 2 delay	0.20 s
P(f>) start frequency	50.200 Hz
P(f>) stop frequency	50.200 Hz
P(f>) start delay	0.00 s
P(f>) stop delay	30.00 s
P(f>) droop	5.00 %
P(f<) start frequency	49.800 Hz
P(f<) stop frequency	49.800 Hz
P(f<) start delay	0.00 s
P(f<) stop delay	30.00 s
P(f<) droop	5.00 %
P(U) response	Not used
Reactive power regulation	Use a fixed Cos Phi
Filter time for reactive power	3.3 s
Cos phi	1.00 
Use lock-in/out	unchecked
TAB: Inverter
PowerAssist	unchecked
Inverter output voltage	230 V
Inverter DC shut-down voltage	43.20 V
Inverter DC restart voltage	48.00 V
Low DC alarm level	43.60 V
Do not restart after short-circuit (VDE 2510-2  safety)	unchecked
enable AES	unchecked
TAB: Charger
Enable charger	checked
Weak AC input	unchecked
Stop after excessive bulk	unchecked
Lithium batteries	checked
Disable VSense (for diagnostic purposes)	unchecked
Configured for VE.Bus BMS	unchecked
Charge curve	Fixed
Absorption voltage	57.60 V
Float voltage	55.20 V
Charge current	100 A
Repeated absorption time	1.00 Hr
Repeated absorption interval	7.00 Days
Absorption time	1 Hr
TAB: Virtual switch
TAB: Usage
Virtual switch usage	Do not use VS
TAB: Assistants
TAB: Assistant Configuration
Assistants not used
TAB: Advanced
limit internal charger to prioritize other energy sources	unchecked

And this is the one I had no luck with (differrence: highier value for Low DC alarm level, ESS enabled with 46V cutoffs, battery monitor checked at the General tab):

TAB: General
System frequency	50Hz
Shore current	50.0 A
Overruled by remote	checked
Dynamic current limiter	unchecked
External current sensor connected (see manual)	unchecked
State of charge when Bulk finished	95.0 %
Battery capacity	314 Ah
Charge efficiency	0.95 
TAB: Grid
Country / grid code standard	Europe:                EN50549-1:2019
AC input 1	Above selected gridcode plus LOM B (compliant)
TAB: European grid code settings
Use AUX1 as disable FeedIn signal	checked
Maximum AC current for charge or feed in	100.0 %
Maximum generated apparant power	100.0 %
connect waiting time	60 s
connect power ramp	0.0 seconds
low frequency connect value	49.500 Hz
high frequency connect value	50.100 Hz
low voltage connect value	85.00 % Un
high voltage connect value	110.00 % Un
re-connect waiting time	60 s
re-connect power ramp	600.0 seconds
low frequency re-connect value	49.500 Hz
high frequency re-connect value	50.200 Hz
low voltage re-connect value	85.00 % Un
high voltage re-connect value	110.00 % Un
rise-in-voltage protection U>	110.00 % Un
under voltage stage 1	85.00 % Un
under voltage stage 1 delay	0.50 s
over voltage stage 1	115.00 % Un
over voltage stage 1 delay	0.50 s
under frequency stage 1	47.500 Hz
under frequency stage 1 delay	30.00 s
over frequency stage 1	52.700 Hz
over frequency stage 1 delay	30.00 s
under voltage stage 2	80.00 % Un
under voltage stage 2 delay	0.20 s
over voltage stage 2	120.00 % Un
over voltage stage 2 delay	0.20 s
under frequency stage 2	47.000 Hz
under frequency stage 2 delay	0.20 s
over frequency stage 2	53.000 Hz
over frequency stage 2 delay	0.20 s
P(f>) start frequency	50.200 Hz
P(f>) stop frequency	50.200 Hz
P(f>) start delay	0.00 s
P(f>) stop delay	30.00 s
P(f>) droop	5.00 %
P(f<) start frequency	49.800 Hz
P(f<) stop frequency	49.800 Hz
P(f<) start delay	0.00 s
P(f<) stop delay	30.00 s
P(f<) droop	5.00 %
P(U) response	Not used
Reactive power regulation	Use a fixed Cos Phi
Filter time for reactive power	3.3 s
Cos phi	1.00 
Use lock-in/out	unchecked
TAB: Inverter
PowerAssist	unchecked
Inverter output voltage	230 V
Inverter DC shut-down voltage	43.20 V
Inverter DC restart voltage	48.00 V
Low DC alarm level	46.40 V
Do not restart after short-circuit (VDE 2510-2  safety)	unchecked
enable AES	unchecked
TAB: Charger
Enable charger	checked
Weak AC input	unchecked
Stop after excessive bulk	unchecked
Lithium batteries	checked
Disable VSense (for diagnostic purposes)	unchecked
Configured for VE.Bus BMS	unchecked
Charge curve	Fixed
Absorption voltage	57.60 V
Float voltage	55.20 V
Charge current	100 A
Repeated absorption time	1.00 Hr
Repeated absorption interval	7.00 Days
Absorption time	1 Hr
TAB: Virtual switch
TAB: Usage
Virtual switch usage	Do not use VS
TAB: Assistants
TAB: Assistant Configuration
ESS (Energy Storage System) (size:1031)
*)	System uses LiFePo4 with other type BMS
	(This can be either a BMS connected via CAN bus (e.g. a Lynx Smart BMS) or a 
	BMS system in which the batteries are protected from high/low cell voltages by 
	external equipment.)
*)	The battery capacity of the system is 314 Ah.
*)	Sustain voltage 50.00 V.
*)	Cut off voltage for a discharge current of:
	0.005 C= 46.00 V
	0.25 C= 46.00 V
	0.7 C= 46.00 V
	2 C= 46.00 V
*)	Inverting is allowed again when voltage rises 2.00 V above cut-off(0).
*)	Relevant VEConfigure settings:
	  -  Battery capacity 314 Ah.
	  -  PowerAssist unchecked
	  -  Lithium batteries checked
	  -  Dynamic current limiter unchecked
	  -  Storage mode unchecked


Total size of all assistants including the required
(hidden) system assistants is: 1090
TAB: Advanced
limit internal charger to prioritize other energy sources	unchecked

This happens because bms comms are lost. Normally it happens after a few minutes.
Bms lost is considered a fault condition if the system is being set to being controlled by it.

Thay have a completely different topology and definitely do not have the power bank (peak surge) or huge transformer that is in most victron inverters. So its like comparing tomatoes and potatoes when is come to power inverters.

Several reasons have been mentioned as to why this may not be a reliable source of information.

This is happening because there is a sudden draw from the capacitor bank and it is not being filled back up on time from the DC source (aka the battery) it is connected to.

And proven through testing.that the bms is not a reliable source of information.

This can add a further draw in complication as it is also a load on the system and it tries to move the opposite way to the brown out. Shifting things.

When using ess the dynamic cut off overide the other settings. They are ineffective. See the manual.
Dynamic cut off is designed to be set lower than battery cut off to allow C rated draws. The low battery warning will now come from the dynamic settings.

That’s why I’ve removed the assistant. @YuriyK mentioned that he did not use it. Following another failed transition during a brownout, I decided to mirror this part of Yuriy’s config. Alternatively, I’m thinking about lowering cut-offs in the ESS, but I’m not sure which numbers I should set. 46V cut-off did not work for me.

I also refer to the battery manual to configure my setup.

And this is from NKON+Victron guide the distributor shares:

On your system, confirm it is the ve bus giving the warning not the battery?
I see the battery warning for low is 46.4v so the 46v should be ok.

VE.Bus System it is.

My final experience and some practical advice

Based on my experience, there are a couple of things that may help others facing similar behaviour.

First, I would strongly recommend adding additional battery interconnection cables, as recommended by the battery manufacturer. In my case, using 2×70 mm² cables significantly improved the predictability of inverter switching during grid loss.

Another thing that helped was adjusting the inverter protection thresholds. I lowered the shutdown voltage to 37.2 V and set the restart voltage to 42.1 V, which reduced the number of unexpected shutdown events.

However, based on everything I observed, my conclusion is the following.

A single battery simply cannot deliver the short-term peak current that the inverter demands during certain transitions. This peak demand seems to be either a hardware or firmware characteristic of the inverter, and apparently it is considered normal behaviour by design.

I discussed this with both technical support and official installer, and they all consistently told me the same thing:
for a 10 kW inverter you should ideally have at least a 20 kWh battery bank.

Personally, I’m not even sure that total capacity alone is the real solution. I suspect the number of batteries (parallel current paths) matters more. For example, having two batteries capable of delivering ~200 A peak each would likely solve the issue, because the inverter could draw the transient current from multiple sources simultaneously.

Right now, in many setups there is only a single battery with a BMS limited to ~200 A, which simply isn’t enough for the inverter’s short-term current demand.

Is this behaviour normal?
In my personal opinion - absolutely not. Considering how excellent the rest of the Victron ecosystem is, this particular behaviour was extremely disappointing.

Unfortunately, after a long period of troubleshooting I eventually made the difficult decision to sell my MultiPlus inverter and switch to a Deye inverter. The Deye system certainly has its own disadvantages, but it works with my battery without any issues and fulfills my primary requirement - acting as a large UPS for the flat.

I do not recommend repeating my path. I still believe Victron builds one of the best systems on the market. If you have the option to add a second battery, that is likely the simplest and most reliable solution.

At the same time, I would strongly encourage Victron engineers to look carefully at this behaviour. Situations where a system with only ~500 W load can trigger transient events equivalent to tens of kilowatts during grid transfer should probably be revisited.

For reference: all assumptions about possible grid instability were eliminated after replacing the inverter. The system now works perfectly under the same conditions. I even went further and installed a 12 kW inverter, and my 16 kWh battery works with it without any issues at all.

Apologies if this message sounds emotional. I genuinely wanted this system to work, but I simply did not have the physical space to install additional batteries, and using a smaller inverter was not an option for me.

I hope my experience helps others facing similar problems.

Thanks for Sharing your experience.

Did you try to add a capacitor to your MP2?

There is a long thread about reducing DC ripple, which caused system shutdown.

No, I did not try adding capacitors to the MP2.

There were two main reasons for that. First, to handle the kind of current and voltage involved in a 55V system, the capacitors would need to be quite substantial, and I simply didn’t have appropriate components available. Experimenting with a collection of smaller or cheaper capacitors didn’t seem like a safe approach.

Second, I believe that this kind of experimentation should really be done by Victron engineers rather than end users. If something goes wrong in such a setup, the safety risks are not trivial, and it could also make warranty claims very difficult or impossible.

Considering the cost of the equipment, it’s simply not a type of experiment I felt comfortable performing myself.

@YuriyK
I fully agree Victron should provide instructions when to add which capacitors. On the other hand Victron is quite open for extensions and they cannot give specific instructions for all non-Victron batteries.

Maybe this threat might be of interest for you:

Good morning,

During power assist, the net is on (pass through) and the inverter delivers also power, or, the inverter delivers power alone, during net outage, then the ripple is most visible.

Ripple has nothing to do with net outage, as it is DC side related.

As explained above before by Bjorn, check my topic, there is a link to a pdf sheet (ripple eliminators) where you can find the solution for your issue.

No, not one inverter supplier can be held responsable for making capacitor banks, simple, all installs are different, therefore we made in my topic 3 standard ripple eliminators for the most common installs, and that involved already quite some calculations based on our experiences with installs we did and do.

Now, recently we assisted Matt (18x15KW 3phase install), he obtained great results adding capacitors based on our advice, once more, read this topic and switch over to there (with a question) if you want help from us for your install with ripple.

With the very best regards, Jeroen.

There is potentially another solution which is to install a normally open contactor between the grid input and the inverter. The contactor is kept closed by a 220/230V coil and if the grid voltage drops the contactor opens. It closes again when the grid voltage returns to the nominal value. A voltage sensing relay may additionally be needed. However, this may only work if the voltage fluctuation frequency is not too extreme. You may also require a time delay in the circuit. Such a circuit was commonly used with emergency standby generators in situations where the grid supply frequently switches off and on eg repeated lightning strikes etc. Obviously this does nothing for ripples.

Good evening Mies,

Indeed, that’s written in several other topics, not this one, grid fail, grid over voltage, etc.

All Victron inverters use a 260V transformer to supply the electronics from the grid power, be aware, at 270V these fail, and also the inverter measures the grid input voltage, also that measuring circuit fails above 270V, but that’s another topic.

Regards, Jeroen.

I found the root cause of my issue with the "rapid DC current fluctuations on the battery side".

The 230 VAC grid supply cable feeding the MultiPlus-II was undersized for its length. The resulting voltage variations (220-225V @ 4A) were small but apparently large and fast enough to affect the control loop of the MPII, causing the interference.

After replacing the grid supply cable with a larger conductor size, the system became stable and the DC current fluctuations disappeared completely. Also, the pass-through mode was no longer activated unexpectedly.

The CAN-bus cable never appeared to be the issue.