ChargeVoltage set zero when MultiPlus II connected

yes. AC-in connected only.

but what charge current to manipulate when the PV chargers get disabled as soon as an inverter with ESS Mode 3 gets connected?? The current of the charger/inverter by drawing from grid??

A PV system with PV chargers unchangeable disabled is worthless!

Those guys all use mode 1 or 2 or do not have (Victron) solar chargers.

please do not start this Node-Red-Venus-large discussion again but let’s concentrate on the core question:

What to do to avoid the PV chargers getting disabled by GX/ESS-Assi when using ESS Mode 3 ?

Do you have the possibility to SSH into Cerbo?
Maybe it’s time to look onto dbus and see some values…

Hi Alex! :slight_smile:

sure I have ssh access. I did the ‘simple’ dbus operations already. What do you want me to do? do you like to connect to my computer to do what ever and see the results directly?!

What’s in the /Settings/Services/Bol ?

ups, somethin I’m diong wrong, pls help

root@raspberrypi2:~# dbus -y com.victronenergy.settings.services
/

Use dbus-spy utility and navigate to it…

dbus-spy? do you might use Anydesk? Remote-Desktop-Software für Windows – AnyDesk

or aren’t you on windows?

At the console prompt, just type dbus-spy and press enter

Services
com.victronenergy.adc com.victronenergy.battery.socketcan_can0 JK-BMScom.victronenergy.battery.ttyUSB1 SmartShunt 500A/50mVcom.victronenergy.ble
com.victronenergy.fronius
com.victronenergy.hub4
com.victronenergy.logger
com.victronenergy.modbusclient.tcp
com.victronenergy.modbustcp
com.victronenergy.platform Venuscom.victronenergy.settings
com.victronenergy.solarcharger.ttyUSB4 SmartSolar Charger MPPT 100/20 48Vcom.victronenergy.solarcharger.ttyUSB5 SmartSolar Charger MPPT 100/20 48Vcom.victronenergy.solarcharger.ttyUSB6 SmartSolar Charger MPPT 100/20 48Vcom.victronenergy.solarcharger.ttyUSB7 SmartSolar Charger MPPT 100/20 48Vcom.victronenergy.solarcharger.ttyUSB8 SmartSolar Charger MPPT 100/20 48Vcom.victronenergy.system
com.victronenergy.vebus.ttyUSB0 MultiPlus-II 48/3000/35-32

/Settings/System
/Settings/System/AccessLevel
/Settings/System/ActiveNetworkConnection
/Settings/System/AutoUpdate
/Settings/System/ImageType
/Settings/System/LogLevel
/Settings/System/ReleaseType
/Settings/System/RemoteSupport
/Settings/System/RemoteSupportIpAndPort
/Settings/System/SSHLocal
/Settings/System/TimeZone
/Settings/System/Units
/Settings/System/Units/Temperature
/Settings/System/VncInternet
/Settings/System/VncLocal
/Settings/System/VolumeUnit

Again, at the console prompt, just type dbus-spy and press enter

root@raspberrypi2:~# dbus-spy

Then navigate to:

com.victronenergy.settings
/Settings/Services/Bol

I did

Or just use:
dbus -y com.victronenergy.settings /Settings/Services/Bol GetValue

root@raspberrypi2:~# dbus -y com.victronenergy.settings /Settings/Services/Bol GetValue
1

Good. I just wanted to see if your config has battery opperational limits (bol) support.
1 means that also the DVCC is enabled, but not forced.

This because I want to know what is the execution flow on dvcc.py script in your case.
You can also do this by looking at the /opt/victronenergy/dbus-systemcalc-py driver and especially at the /opt/victronenergy/dbus-systemcalc-py/delegates/dvcc.py script and see there how and why your system is behaving that way.

I feel your frustration, but maybe, no offense, it’s time to take a step back and do a more systematic approach and follow the code, understand it and then, step by step, trying to see what’s happening.

Who knows, maybe you really find a bug… :slight_smile:

how can I debug the .py’s you mentioning?

or should I simply look at them?

put print(…) in?

Simply look at them and understand their flow…

Do you have windows or linux?
For example I am using WinSCP on windows for exploring the Venus OS tree.

I just opend /dbus-systemcalc-py using WinSCP