com.victronenergy.settings/Settings/CGwacs/Hub4Mode is set to 3 (shown as External Control in VRM and the Cerbo).
com.victronenergy.vebus.ttyS4/Hub4/DisableCharge is set to 0.
com.victronenergy.vebus.ttyS4/Hub4/DisableFeedIn is set to 0.
com.victronenergy.vebus.ttyS4/Hub4/L1/AcPowerSetpoint is set to 1000.
The system ramps up to the power setpoint for a few seconds but then idles, repeating this ramp-up and idle cycle. There are no errors or alarms displayed in VRM or on the Cerbo.
Am I missing something? Why isn’t the AcPowerSetpoint being honored?
Given that your setup, mode 2 should let you do what you want. What is doing the calculations? A pi? Where is it getting data from to decide what to do?
Just change the set point from the pi for example and that should achieve what you want.
It is not linked to any control algorithm just yet. Currently I am just trying to gain control. I am writing to modbus tcp via Home Assistant and can see the values being updated to my values in dbus-spy.
In mode 2 I believe the Victron control loop would interfere with my grid setpoint?
It does override, but only for things that for instance protect your battery. I just change the set point and retain full control. It is only overridden for example when the battery demands charge because it is too low. Or the battery is too full. I have all the other stuff such as charging schedule turned off and that is effectively implemented by my code. You probably want to retain the protections unless you are super careful and have a robust test framework backing up your code!
a) Grid power setpoint - Modbus-TCP register 2700
I just change this every 5 seconds based on my calculations. It is the same as changing the set point in the remote console interface.
You can go very complex in the node-red interface: 100s of lines of code in the function blocks. I essentially implemented the dynamic ESS before victron released theirs. It’s still more accurate for my use case and has other refinements to ensure efficient use of the charger.
when using External Control (Mode 3) “com.victronenergy.vebus.ttyS4/Hub4/L1/AcPowerSetpoint” has to be rewritten in intervals. Otherwise the Multiplus goes into Passthru mode.
The timeout is 60 seconds for ESS assistant and 10 seconds for (deprecated) Hub4 assistant.
No, it’s the same dbus path. I’m pretty sure that more than 99% of all users have the ESS assistant installed on their Multis. The info about the Hub4 assistant was just a remark.