question

Probably measurement error. The state estimation done inside the inverters is, in particular, known to be a rough approximation.

Does the battery voltage ever actually drop, like over the course of weeks?

Same situation here:

MultiPlus 12/1600 with 4x 150Ah C20. Used for USV, no cycling.

After installation and configuration, before power on the supply (grid), I saw that approx. 13 ... 15 W were taken out of the battery - would be the consumption of the MultiPlus itself, I think (no load on MultiPlus output),

After powering on the supply an putting load on the output, there were approx. 2 ... 3 days for Bulk/Absorption/Float.

After this, storage mode was entered. I see nearly constantly that 10 ... 15 W were taken out of the batteries and, that the power from grid is always slightly lower than power delivered to load.

After approx. 5 days in storage mode, SOC falls below 80% - and the relay assistant shut down my server cabinet :-(

The Ah consumed from batteries in this 5 days confirm the SOC calculation to be ok.

Questions arising are:

1. Why is the Multiplus taking power (its self consumption plus more) from batteries?
2. Why does it ignore that grid power is below load power?
3. Why doesn't it fill up batteries? I set the check mark at "USV-Mode"
4. Storage mode should not accept discharging - why isn't the voltage set to get the battery current to zero or little current into batteries?

I can go to the MultiPlus in a little bit more than two weeks - I think, I have to disable storage mode.

And Im hoping, MultiPlus will not inactively watch the SOC going below the switch off level before I can cange configuration...

Any Ideas to get storage mode useable?

Good day guys. I have the same issue here. Any one here to help solve it?

Unbelievable: four years have passed since problem was reported, and nothing done by manufacturer. Is it really normal behaver for the world’s leader?

I’ve just bought MultiPlus 12/1600/70-16 and got the same issue: after battery is fully charged, SOC drops by 1% per hour. So I’m actually can’t use it safely discharging the battery to only 40% SOC from 100%.

It is obvious, that problem could be solved by software update. Also it’s obvious, that it’s manufacturer bug (SOC should not be calculated down from the moment when the voltage is at the level of Float or Store mode)! Is where any hope, that manufacturer will finaly hear the customers?

Recently I have got an answer from service department of Victron. They admitted, that it is production defect (bad “calibration or something”) and MultiPlus should be sent to dealer to be serviced. So if you have the same problem, best solution is to get service from Victron’s dealer.

In my case I couldn’t stay for a long time without Multi, so the only way for me was to find a possibility to fix calibration issue by myself. And I’ve made it! If you are in the same situation as me here is the procedure:

1)Find current measurement transformer of “charger/inverter” chain inside of you Multi.

2)Find +12v from internal psu, which is used to power all smart functions (microcontroller, operational amplifiers etc.). I used VCC pin number 4 of 324A operational amplifier.

3)Using 68 kOm resister connect +12v you have find in step 2 to one of secondary coil pins of transformer you determined in step one. In my case it is right pin of coil if you are looking from the pcb side (see picture attached). If wrong coil pin will be used, probably no positive or negative effect will be seen. So it’s easy to find out write pin. BUT UNDER ANY SIRCUMSTANSES DON’T USE HIGHT VOLTAGE LOOP PINS WICH IS ON THE OTHER SIDE OF THE TRANSFORMER!!!

That's all. Now my MultiPlus works perfectly! After battery once been charged, at any given time I have all the battery capacity that can be safely used up to a certain SOC level (I set 40%)!

P.S. Resistor nominal in your case could be different. Mine was experimentally determined in range of 15 to 450 kOm. Best stable affect without decreasing of SOC parameter in storage mode I have got with 68 kOm. Any negative impact on the system charging or inverting was not found.