question

alex019 avatar image
alex019 asked

ESS Minimum SOC (Unless grid fails) 15% But stops by around 50%?

I have been experiencing the following problem for a few weeks now.

At ESS I have: Minimum charging status (unless the electricity grid fails) 15%. and Set power supply 0W

When power is required, it will first come from the batteries until they are equal to or lower than 15%.

This worked well, but now the battery power keeps stopping between 45 and 50%. If there is a power failure after this, then the system breaks down! The system apparently thinks the batteries are empty?.


The system I have running is as follows:

3x Victron Multiplus-II 48/8000 3 phase setup.

1x ET340 Electricity Meter (Multi-phase)

1x BMV-700

1x CerboGX

1x SmartSolar MPPT 250/70 (4000Wp)

1x Fronius Symo 6.0-3-M (Connection IP (sunspec)) On AC output

1x Aurora Power One 4.2 Inverter 1 phase on AC output. (Will be replaced in the near future by a Fronius symo)

3x Overkill Solar BMS (16s 100A) with 3x USB Module for BMS. Considered as SerialBattery(LLT/JBD)

3 sets of 16 cells LifePo4 280Ah. Is 3x280Ah=840Ah total.


Firmware:

CerboGX: v3.13

Multiplus: 508

SerialBattery(LLT/JBD): 1.0.20230531

BMV-700: v3.11

SmartSolar MPPT 250/70: v3.13

Fronius: 0.3.30.0

Fronius DataManager: 3.28.1-3


The reason for 3x BMS instead of 1x is that you can now charge and discharge with 3x100A (300A) instead of 1x100A.

I got the BMS visible in Cerbo by using the Louisvdw/dbus-serialbattery driver.

This is the latest release! Installed via SSH and Root access:

wget -O /tmp/install.sh https://raw.githubusercontent.com/Louisvdw/dbus-serialbattery/master/etc/dbus-serialbattery/install.sh

bash /tmp/install.sh


Addition: When I set a planned charging level with a SOC limit of 100%, the batteries are charged with approximately a maximum of 110A. Before the problems arose, it was (depending on the charging status) around 300A.


What I have done so far to get the problem resolved:

I used Latest Release candidate for the Cerbo. But now back to the stable due to problems.

With VEConfigure3 the 3 multiplus units were reconfigured with the ESS Assistant again.

I also reset the CerboGX to factory settings using venus-data.tgz.

After this, the Cerbo was set up step by step.

Update Louisvdw/dbus-serialbattery driver to the newest (1.0.20230531) on this moment.(>= V1.0) (Not the Nightly build!)

Unfortunately everything without results.


ess discharging
4 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

JohnC avatar image JohnC ♦ commented ·

@Alex019

The trigger points in your pics appear to be default values. So not set too high. The 43.6V is the one providing a 'Warning'. The 37.2V one is the lowest possible to set, and hasn't been reached if the Multis don't show shutdown advice. By then the batt bms is likely initiating your 'system breaks down!'

I'm thinking load spikes from something like an electric motor starting (bad start capacitor, etc). Often too fleeting for Victron recording to pick up. But I don't know what you're running.

A 'bounce back' V maybe something like the 52.6V in your pics. I don't know your batts either.

So maybe it isn't an SOC thing. But I'd still ditch the Multi (VE.Bus) SOC and go with the BMV. We'd need to see the settings, but likely just syncing to 100% too early. A little tricky to set that up with Li batts, but the manual can help there.

0 Likes 0 ·
Alexandra avatar image Alexandra ♦ JohnC ♦ commented ·

What C rating discharge voltages are set in the ESS assistant.

Does the voltage on the battery bank collapse under high loads?

The values in ESS also determine where your inverter determines alot of things based on the load.

0 Likes 0 ·
alex019 avatar image alex019 Alexandra ♦ commented ·

Where can I find the C rating setting?


ve-configure3-settings5.jpg


ve-configure3-settings7b.jpg

ve-configure3-settings7c.jpg

ve-configure3-settings7d.jpg

ve-configure3-settings7e.jpg

ve-configure3-settings7f.jpg

ve-configure3-settings7g.jpg



ve-configure3-settings7j.jpg



No, the voltage does not collapse under heavy load! (by 14000w or more from the battery to the 3x multi)


0 Likes 0 ·
alex019 avatar image alex019 JohnC ♦ commented ·

My entire house installation is connected to AC2 out. Including a 1 phase heat pump for tap water, a 3 phase heat pump for underfloor heating, an electric hob, a dishwasher and a dryer.

However, the system stops by default at about 48% to 50% battery low level.

And often the "heavy" devices are not on at that moment or have been switched on for a while.


The batteries I use are: Grade A EV LF280K 6000 cycles lifepo4 3.2V 280Ah battery

1 bank of 16 cells and that 3x (3 banks) each with its own BMS 3x Overkill Solar BMS (16s 100A) with 3x USB Module for BMS. Considered as SerialBattery(LLT/JBD) This information is in the initial post.


Syncing to 100% too quickly/early is probably due to the solar panel power. This usually happens on sunny days.

Which manual describes how to set this up? It is a pity that all the information from the BMS

(which is much more detailed and accurate cannot be used)

0 Likes 0 ·
3 Answers
JohnC avatar image
JohnC answered ·

@Alex019

Given you have a BMV in the system, I presume that's where you are deriving the SOC. There are potentially other sources, and being a calculated figure, please confirm. This is where I'd start looking. And yes, it's very possible that the BMV has drifted or prematurely synced, thence providing an overstated figure.

Can you provide a screen snip of the settings? And anything else relevant to how you handle that SOC.

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

alex019 avatar image
alex019 answered ·

The Battery monitor is currently the Multiplus-II. However, I also had 1 of the 3 BMSs as a battery monitor.

I did not use the BMV700 as a battery monitor because it sometimes showed 100% too quickly.

When the problem occurs, the BMV700 also indicates around 50% capacity.

This also applies to the Multiplus and the BMS.


DeviceList

device-list.jpg


BMV700

bmv700.jpg


BMV700-Device

bmv700-device.jpg


Settings-SystemSetup-BatteryMonitoring

settings-system-setup-battery-monitoring.jpg


ESS-Settings

ess-settings.jpg


2 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Alexandra avatar image Alexandra ♦ commented ·

The inverter Ve Bus as a battery monitor does not work well especially If the system is not getting up to 100% SOC And being held there everyday.

You will see it in the voltages. So ignore percentage for now.

Sort out the BMV Sync problem. Then the SOC issue will be solved. (Although the 500A shunt is marginal for the 3 x 8kva system is that the shunt you have?)

Share the settings here and we can see why it is being falsely triggered.

How do you have grid on AC I put 1&2 by the way?

0 Likes 0 ·
alex019 avatar image alex019 Alexandra ♦ commented ·

I have the 3 phase grid connection on AC IN (1 phase per unit)

The house installation is on AC Out 2 (Critical load/switchedLoad)

Also the Fronius symo and the Power One Aurora inverter.

devicelistbmv.png

bmv700.png

bmv700-alarms.png

bmv700-device.png

The Shunt is a 500A. The system may (if I remember correctly) supply a maximum of 110A charging current per Unit. Total 330A

The BMSs can charge and discharge at 100A each. This is 300A at a time.

A shunt of 500A seems more than sufficient to me. I have (fortunately) never exceeded 300A total.

If any information is missing, I would like to know what information is still missing.

0 Likes 0 ·
devicelistbmv.png (37.8 KiB)
bmv700.png (25.3 KiB)
bmv700-alarms.png (30.3 KiB)
bmv700-device.png (29.6 KiB)
alex019 avatar image
alex019 answered ·

I don't think the BMV700 is the problem. I see on the https://github.com/Louisvdw/dbus-serialbattery/ forum that they actually advise NOT to use the BMV700 for battery monitoring.

I also found the following:

In the multiplus-II AlarmSetup, Low Battery Voltage was set to off. Turn this on and then get a Low battery voltage. The moment this occurs, the discharge stops. (at approximately 50% battery capacity)multiplus-ii.png


multiplus-ii-alarmsetup.png

lowvoltagealarmmultiplus.png

multiplus-ii-alarmstatus.png

multiplus-ii-alarmstatus2.png

multiplus-ii-novebusalarm.png

However, when I look at the alarms and the CellVoltages of the BMSs, I see no reason why the Multi gives this alarm.

BMS1Alarms

bms1alarms.png

BMS1CellVoltage

bms1cellvoltage.png


BMS2Alarms

bms2alarms.png

BMS2CellVoltage

bms2cellvoltage.png


BMS3Alarms
bms3alarms.png

BMS3CellVoltage

bms3cellvoltage.png


When I charge the batteries with about 10% (to about 60%), the system works again up to about 50% and the Low Battery voltage alarm occurs again.


So I don't know where this alarm comes from or is caused by!

The battery data comes via the driver of Louisvdw/dbus-serialbattery from the BMS


4 comments
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

JohnC avatar image JohnC ♦ commented ·
@Alex019

The warnings/shutdowns are seemingly coming from the Multis. Your system is running big amps and the trigger points may be set too high to handle a large load. Even wiring resistance could be part of it. Like do the batteries bounce back to a good V if you remove loads? VE.Configure is needed to adjust them.

I'd disable the VE.Bus SOC and concentrate on the BMV. In theory the battery bms would be treated as gospel, but if you can't get that across to ESS then a bit pointless.

The BMV settings are available using Victron Connect (via VRM), and likely need some attention before you gain confidence in them.

0 Likes 0 ·
Show more comments

Related Resources

Additional resources still need to be added for this topic