Hi,
I’m facing a small problem: I use a custom ESS control to control my Multiplus II, 4 MPPTs, 1 LiFePo-Battery and AC-coupled PV to charge my battery proper especially when near full. Because there is still a problem with the Victron way of charging the battery with “DC-coupled PV – feed in excess” activated.
So my question is, why is the Battery Minimum SoC in the control tab grayed out when in external control mode?
That setting doesn’t do anything when the system is set to External Control. Thats why its grayed out.
That the setting is still available in gui-v2 is a bug; we’ll look into that a bit more and most likely the result is that we’re going to hide it there when system is set to External Control; and make a change in VRM to do the same.
Thanks for highlighting that - even though now its going in the opposite direction of where you wanted to take this .
In your case, where you run your own script/algorithm, you can implemented a minimum SOC in your own script yourself.
Hi Matthijs,
thanks for the quick reply. Ok, hmm. I’m running a modified aggregate_batteries script on a raspberry Pi with venus OS 3.51. I use the minimum SOC setting from the dbus path ‘/Settings/CGwacs/BatteryLife/MinimumSocLimit’ to control my own script. The nice thing is, that I can easily control my script this way using either VRM portal or GUIv2. Otherwise I don’t have any good way to set parameters for my external control script via VRM (or GUIv2 at the moment).
So for me, it would be best, if the minimum SOC would stay editable even in external control mode.
Because for me it’s no argument only because of the use of an external control there shouldn’t be any possiblity to set a minimum SOC anymore? Maybe other external control scripts also use the minimum SOC setting?!
Christian
Hi Christian, I see why you want that for your case, but for others this will be confusing.
I like that the setting hides when selecting external control because that makes it clear that the built-in minimum soc mechanism is disabled in this mode.
We are going ahead with hiding the option in case external control is selected. Both in VRM and in gui-v2.
What might help you at some point is that we are (slowly) starting to work on the option to add controls yourself into gui-v2. Meanwhile perhaps a node-red dashboard could help?
Hello Matthijs,
I already thought that my wish had little chance of success, but I understand your argument.
In fact, I’m currently looking for ways to at least add new menu items to my driver via the GUIv2 or ClassicUI menu. I’ll have to do some more research. Also, the concept for extensions in GUIv2 is probably currently under discussion. I am following this with great interest. I would be very interested in a simple solution for extending menus. JSON files sound quite nice.
Thanks anyway for the answers and keep up the good work, I’m very enthusiastic about the whole Victron universe.
.