Looking to tackle this from a possibly more simple angle: Is it possible that the ‘AC2 relay off’ function I require is not working due to the order that the Assistants are set-up in VEconfigure? Could the Assistants corresponding to the battery SOC be permanently overriding the one for AC load?
Re: 3.)
I take it you have created an assistant that does this?!
Can you show the summary of the other 2 assistants you have?
I think I know what is casing the issue you are experiencing now.
Yes and no, in the strictest sense.
Combining multiple Assistants
Multiple Assistants can be used in one unit. For example the Programmable Relay is often used multiple times. When doing so; this is how they are evaluated:
- an ON condition always has priority over an OFF condition - multi criteria in the ON ( or OFF ) list go by the OR principle
Assistants in the following order:
- AC2 off when load above 3500W
- AC2 on when SOC above 90%
- AC2 off when SOC below 80%
So this is not my forte, but I think in your case:
1.) OK
2.) Becomes 3.)
3.) Becomes 2.)
BUT if the SOC is over 90% and a high load event occurs the ‘ON’ assistant will take priority and continue in the ON state.
At 90% 3.) is not true (but if on, relay AC OUT-2 remains on)
At 90% 2.) is not true (but if on, relay AC OUT-2 remains on)
At =<%90 AND load > 3500w >3s 1 is true, 2 is false, 3 is false, if on, relay AC OUT-2 turns off
At >=%90 AND load > 3500w >3s 1 is true (an OFF condition), 2 is true (an ON condition), 3 is false, if on, relay AC OUT-2 remains on as the ON condition takes precedent.
That’s easy enough to test.
So maybe you might be better using the primary relay to disconnect the load via a slave relay / contactor with 1.) So the AC OUT-2 is on SoC >= 80%, but the primary relay would disconnect the load via a slave relay/contactor when the load > 3500w > 3s, regardless if SoC > 90%
The conflicting signals that you describe make sense as to why the AC2 does not turn off as required with high load. Surely Victron can easily provide a simple work around for such a situation, I cannot believe this is the only instance where this has arisen.
Slave relay/ contactor, I’ve no idea what this means or how to set it up. Am I looking to do this using the Assistant on VEconfigure?
I’ve just created a new topic on the board to just address the Assistants in VE configure to try and get some additional input. Thanks
1 Like
Victron Assistants were originally introduced to handle very simple senarios. They were a step up from the very basic Virtual Switch.
Over time people have demanded more and more from them.
An inverter, in my opinion shouldn’t be fulfilling this role. Dedicated automation software should be used to drive the physical outputs of the inverter. Victron is slowly being dragged into being a software vendor, and supporter… and that is a hiding to nowhere (I had an IT company for 20+ years).
Automations can be create via VA’s that are very powerful, AND complicated, but because it is onboard the device, people see this as a Victron issue when it doesn’t operate as they expected.
Victron should produce kit that communicates and can be controlled via open standards (such as is the case with Victron (ModBus / MQTT)) and finish there.
Automation software can run on an SBC like the Raspberry Pi and you can control and monitor a whole home with it.
Shelly switches:
This is a 16A relay so you could use this to drive the Immersion, and shut it down when the total load exceeds 3500w