question

Hi @Semlohnhoj ,

Indeed, I have a Cerbo in my system and the CAN write command was sent through the 'cansend' utility inside the Linux system from Cerbo.

But the 'cansend' is just sending frames over specific CAN bus and those frames, I believe, can be sent by any other means.

In fact, in the VE.Can-registers-public.pdf file from Victron, they tell you how you can send commands over CAN network, using specific registers.

They don't supply however the entire list of available registers, but they can be obtained from VictronConnect application. An (almost) complete list of registers here: https://community.victronenergy.com/questions/262532/victron-energy-registers-description.html

The registers you need to write to are:

0xD050, VE_REG_MULTIC_ESS_MODE

0xD053, VE_REG_MULTIC_ESS_DISCHARGE_SOC

The CAN address of Multi RS can be found from Cerbo - Settings - Services - VE.Can port - Devices - Multi RS - Network Address. Usually is 64 (0x40).

As sender, I've used a 'fake' network address, 0x55 in my tests.

For example, for setting 40% for Discharge SOC, you send the command below.

See that the SOC is in 0.1% units, so 40% is 400, therefore 0x0190 in hex.

cansend can0 1CEF4055#669953D09001FFFF

So, I believe that one can make any script he wants to automate things, store them on Cerbo and from those scripts to read and write to almost any settings of the Multi RS.

The same way the batterylife, dvcc, etc are implemented, just that instead of reading/writing things through dbus, you read/write them through CAN bus, which any dbus setting will end up anyway to be transactioned. A more direct way if you know what you are doing.

Have fun! :-))

Alex