Open herrep opened 11 months ago
Hi Peter, I have the same problem with lack of time. Therefore I cannot imagine to maintain a tool for aggregating different battery systems. I suggest you make a fork, modify it as you need and publish it. Thanks.
Hi Peter, were you able to bring some light in the issue ? I am a "newbee" and also faced with the same problem with JKMS on serial and a BYD LVS System on Can-Bus.
Cheers, Michael
Hi,
My use case concerns two batteries, each equipped with a SEPLOS BMS. These two BMS interact with each other via RS485. One of the two BMS acts as a master and provides BMS CAN-Bus communication with Cerbo GX, visible under product name CAN-SMARTBMS-BAT. The upper protocol level via BMS CAN-Bus provides already an aggregated view on the two batteries. This is the way as defined by the vendor how the battery system that may consist even of more than two battery backs is to be integrated with Victron.
As I have further batteries installed, each equipped with a JK BMS and integrated with Cerbo GX via dbus-serial-battery, I tried to integrate all the BMS, i.e. the 2 JK BMS via RS485/USB and the SEPLOS BMS via BMS CAN-Bus, with dbus-aggregate-batteries.
However, I realized that quite a number of the CAN-SMARTBMS-BAT dbus variables do not match the expected ones retrieved by dbus-aggregate-batteries. The most relevant difference to a BMS driver like dbus-serial-battery is that the CAN-Bus SEPLOS BMS already aggregates values. Here is a listing of all dbus variables of the CAN-SMARTBMS-BAT:
The purpose of this issue is to document the integration of this CAN-SMARTBMS-BAT into dbus-aggregate-batteries and to find out if others have already implemented something. As soon as time permits, I will adapt aggregatebatteries.py and provide updated information.
Best regards, Peter