question

marv2097 avatar image
marv2097 asked

ESS Power Not Balanced in Parallell Multiplus II System

Hi All, I have recently upgraded to 2 Multiplus IIs (48/5000) running in parallel, the main motive was increase the maximum power output, allow faster scheduled charging and to allow the option for a total of 100A transfer switch capacity to allow moving more loads to the AC out.

In early testing of the system I have been getting strange levels of export/import when I would normally expect ESS to keep this around 0. The issue is more common when the ESS system is trying to charge the batteries ie when there is excess solar. I asked this question here which has all my ESS settings etc but I now feel I have a better grasp of what's going on and wanted to start a new discussion as I feel this is impacting more people than just myself.

https://community.victronenergy.com/questions/239228/random-ess-discharge-behaviour.html

I have also read the wiring unlimited and a number of other useful documents such as:

https://www.victronenergy.com/live/ve.bus:manual_parallel_and_three_phase_systems
https://www.victronenergy.com/live/_media/ve.bus:rva_-_theory_on_wiring_large_systems.pdf
https://www.victronenergy.com/upload/documents/Wiring-Unlimited-EN.pdf


Having read a *lot* of forum posts that describe very similar issues and there seems to be 3 common themes that they are advised to look at.

1 - Hardware Revision of the Multi too far apart.
Both of my units were purchased at the same time and are 1 week apart. Running same firmware. v506.
When running as a single unit then ESS works exactly as expected regardless of which Multi is being used.

2 - Mismatch in cable length/thickness - ie impedance is different. Cables too thin/thick etc.
AC In has 6mm2 Twin+Earth at 2m in length running to a sub panel.
DC has 70mm2 Copper at 1.5m length running to Lynx Distributor then 50mm2 at 1.5m to each of the 2 Seplos batteries.
Both multi's have exactly same length/thickness/batch of cables and these have all been remade, cleaned and torqued to spec.

Through testing (see below) I can prove the the cables in my case make no difference.

3 - Make the newest multi the master
I have tried both multi's as master. While this has minimal impact on the forced load tests (export or charging) it does change the behaviour when trying to stick to a 0w setpoint in normal ESS operation.


Master - Slave operation

For ESS/hub4 operation it appears the master takes the desired AC setpoint, compares to its AC readings and regulates to this. It then shares its duty cycle with the slave. As such the Master assumes if it does 50% of the required load then, by virtue of the slave having the same duty cycle it will do the other 50%. Unfortunately this does not seem to be the case in my system. One multi is providing more power for the same duty cycle than the other by a significant amount. Is there any reason the slaves dont sync with the timing of the master but have their own feedback based on a desired share of the setpoint?
** If I have this understanding wrong or someone at victron could correct me that would be great **

All of this leads me to a couple of possible conclusions.
- Significant Hardware/Component difference. My multis are HQ2313 and HQ2314. Could something be different internally them?
- Hardware fault. A failure that is not enough to stop the multi working but is causing a difference in internal resistance.
- Multi or Assistant firmware bug. Could the combination of config, firmware and hardware I have be something that's not working as it should?

If anyone can help me understand why this is happening and why this only really impacts charging regulation that would be very much appreciated. Thank you




Test methodology: Testing was done by setting the ESS grid setpoint to 4kw to force charging of the batteries. During the test an AC/DC current clamp was used measure amperage on both the AC in cable and DC in cable. The AC and DC cables were marked 'A' and 'B' and swapped in sequence. The export test was done the same way just with -4kw grid set point. Multi #2 was used as the Master throughout the tests. The testing was done with the same current clamp and repeated multiple times to ensure consistency.

Test results summary:

When charging Multi #1 is consistently doing more work. Even with both AC and DC cables swapped the behaviour is almost identical (within 0.5%). This rules out any impedance discrepancies in wiring and connections external to the Multis.

Exporting power is relatively well balanced and as I would expect for a parallel system. Scheduled charging was also tested and was balanced.

1699047330592.png


ESSmultiplus in paralleless grid setpoint not reached
1699047330592.png (56.0 KiB)
2 |3000

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

3 Answers
marv2097 avatar image
marv2097 answered ·

When I posted this I was running v506 firmware on the Multi's and 3.11 On the GX, This was the latest firmware at the time. I also tested both multis individually and they have been working fine. Both have very similar efficiency for charging and discharging and work great on their own with ESS.


I have now upgraded to v508 on the multis and 3.14 on the GX and things are working much better. Nothing else has changed but im getting much closer balance between them and they are sharing the load: The same test before and after FW update.

Before:

1706869511070.png
After:
1706869464079.png


At the moment I have no idea why the FW has resolved the issue but I am happy that it has and can no go back to running a normal parallel system with the plan to try out dynamic ESS.


Out of frustration I also started work on a distributed ESS system which allows separate ESS systems that share the same AC circuit to work together. This has the advantage of allowing different battery voltages sizes/chemistry and multiplus sizes. It requires a gx device per multi and is still very much a proof of concept but it was working quite well. This may not be needed now the parallel setup is working but let me know if interested and I will share more details.


1706869464079.png (11.3 KiB)
1706869511070.png (13.2 KiB)
2 |3000

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

seriusrod avatar image
seriusrod answered ·

I've got the same scenario and I'm also interested in a response from the Victron staff.

2 |3000

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

daniel-feist avatar image
daniel-feist answered ·

Is the "ESS Assistant" correctly installed on both units? I've seen similair issue before and it was caused by the assistent having been installed on one unit, but not the other.

1 comment
2 |3000

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

seriusrod avatar image seriusrod commented ·
Hello Daniel. I'm my case, yes. I used direct configuration using the mk3 and flashed the same configuration on both units.

I'm fact, on the slave it only allows a reduced version of the ESS, that doesn't have voltages.


1 Like 1 ·