Peak shaving question

Hi All,

I have a large 3 phase system (18 x 15kva multi’s and 1mw batteries) with a large solar array. What I want to do is in the winter it runs in peaking shaving when solar production is low. I want it to use solar first, then grid then batteries but not recharge batteries unless solar is in excess. The batteries will recharge at night at cheap rate. Is this possible? I’m using keep batteries charged at the moment but obviously its keeping the batteries charged that I don’t want! I tried both optimised modes with peaking shaving set to always but it doesn’t use the grid first. I can see in node red there are more ess states that you are able to use but none really look right.

I have tried a few combinations but working on the live system and when its drawing 130-180kw’s I don’t want to mess it all up trying too much so any pointers would be helpful. I presume if it can be done it will need to be done via nod red which is not a problem as I have lots of automation running through it.

Do you have ESS?

Yes of course! I wouldn’t be able to do the modes without it.

Interesting system, it exceeds the maximum system size Victron supports, unless their docs need updating.

Using our 15kVA Quattros, the maximum system size is a 180kVA three phase system. Which then consists of four units on each of the three phases: 12 units in total.

Solar and batteries are both on the same DC bus, so it is exciting to try prioritise one over the other without charging. Conventional ESS cannot work that way.
If you dig around you might find some similar queries in the modifications section.

Solar is on the AC out, there is 7 different Solaredge inverters spotted around in various buildings, the xmas shut down allowed me to test the Victron solar inverter control via the sunspec protocol which worked perfectly. I got confirmation from Victron it is ok as long as you don’t go over the 400amp ct’s which is fine as the grid connection is only 200 amps. There was an issue with the ve configure/firmware but they remoted in and fixed it.

I’ll have to have a think if there is another way around the issue, maybe limiting the inverter power based on solar production/forecast and run in optimised mode, but I don’t want to limit myself if we turn on a big machine and pull big power for a moment!

Automating the max inverter power could be a way around it since you have PV inverters.
That would be a straight forward nodered flow to implement.