Dbus-serialbattery upgrade stability

Hi,

I have a Motorhome with a Cerbo GX, Multiplus II, 3 solars chargers and 3 DIY 12 Volts 310 Amp battery packs each with a Daly 4S 250 Amp BMS.

My problem is that when I use the Daly IOs App, the batteries never have to same State Of Charge and I cannot use DVCC because the BMS do not have native integration with the Venus-OS.

My research show that I should connect the BMSs in a Serial Connection Mode or RS485.

That requires to install the dbus-serialbattery driver to the Venus-OS.

My question is for the ones that have installed that driver: how stable is that driver when you update the Venus-OS?

If the driver does not reload after an update, is the Cerbo-GX still operational?

Thank you
Simon

there were problems with updates, yes - especially when victron changed to GUI V2

But why you want to do updates? Do you do updates on your dishwasher or coffeemaker?

If my Toilet Paper Holder Roller had software, I would keep it on the latest stable release.

3 Likes

up to you :slight_smile:

I keep up with the latest beta for the Cerbo & serial driver that talks to my DIY JDB 8S pack. It provides quite a bit of information, and the serial driver GUI enhancements are a real bonus too. I’ve read that it’s not very stable on bluetooth, and I think with 3 packs you’ll need some sort of battery aggregator. Mine is connected isolated TTL serial to USB.

The driver is pretty stable even when bouncing around Cerbo firmware when troubleshooting issues. On mine it takes 30ish seconds to find the pack and start showing SOC again after a reboot.

If it doesn’t load, the Cerbo itself is operational but it won’t have good info to handle anything DVCC related. Ours has been very operational in our coach. It took a bit to get the driver parameters dialed in to get charge to switch from bulk to float. It’s not hard, just took me some time. Now that it’s set up, it works great on shore and solar.

1 Like

Thank you for your return on experience.

This is a topic that pops up with some regularity.
When using mods you need to accept that this is not supported by Victron and the mod is maintained by a third party dev on git. Questions and issues need to be addressed with them.
When you experience issues and you think it is Victron’s responsibility, you need to remove any mods and reproduce it on a vanilla system - this is a common cause of issues.

There are always dependencies between the OS and a driver, when one changes the other must as well, so always check with the dev of the mod that there are no known issues and that you are up to date.

What works today might not work tomorrow, that is the bargain you enter into when choosing to use third party mods, just not everyone who chooses this route fully understands what they are getting into to.

3 Likes