Only one battery showing in Venus and frequently disconnects

Describe the bug

My Setup Victron Cerbo GX Victron MPPT 250|100 Solar Charge Controller Victron Multiplus-II 48/5000/70 Battery 1 - 280AH x18s LiFePo4, Daly 150A BMS, Parralel protection board, 1A active Balancer and WNT board Battery 2 - 280AH x18s LiFePo4, Daly 150A BMS, Parralel protection board, 1A active Balancer and WNT board Batteries are connected in series. dbus serial battery driver version 1.4.20240902dev (nightly release)

The Daly WNT board offers RS485, RS232 and CAN connection, Batteries are addressed via dip switches.

The issue I am having is connecting both batteries to the dbus serial driver (via RS485) at once. I have 2x USB to serial converters connected to the cerbo, they both work individually, but if you plug both in at the same time, it causes the first battery to show as disconnected, The driver does not display both modules at the same time, which is what I am hoping to achieve.

Solutions I have already tried

Alternative settings of the dip switches (all off, swapped addresses, set the same etc)
CAN-bus connection to the cerbo - again, it recognises the first battery, when connecting the second, the values change between something completely incorrect to the values of battery pack 1. I have the correct patch leads for going between cerbo and daly, have tried using the line terminator, again tried re-addressing the units ect.
have tried each RS485-USB device separately, both work individually and read correctly, but not together. 4 have NOT tried dbus driver on CAN (cant find the CAN addresses)

How to reproduce

Try to add 2x daly smart BMS in series on RS485 to driver

Expected behavior

I was expecting for the driver to displace data for both Battery 1 and Battery 2.

Driver version

1.4.20240902dev (nightly release)

Venus OS device type

Cerbo GX

Venus OS version

v3.41

BMS type

Daly Smart BMS

Cell count

Battery count

Connection type

Serial USB adapter to RS485

Config file

[DEFAULT]

; --------- Set logging level ---------
; ERROR: Only errors are logged
; WARNING: Errors and warnings are logged
; INFO: Errors, warnings and info messages are logged
; DEBUG: Errors, warnings, info and debug messages are logged
LOGGING = INFO

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 75
MAX_BATTERY_DISCHARGE_CURRENT = 150

; --------- Cell Voltages ---------
; Description:
;     Cell min/max voltages which are used to calculate the min/max battery voltage
; Example:
;     16 cells * 3.45V/cell = 55.2V max charge voltage. 16 cells * 2.90V = 46.4V min discharge voltage
MIN_CELL_VOLTAGE   = 2.900
; Max voltage (can seen as absorption voltage)
MAX_CELL_VOLTAGE   = 3.450
; Float voltage (can be seen as resting voltage)
FLOAT_CELL_VOLTAGE = 3.375

; --------- SOC reset voltage ---------
; Description:
;     May be needed to reset the SoC to 100% once in a while for some BMS, because of SoC drift.
;     Specify the cell voltage where the SoC should be reset to 100% by the BMS.
;       - JKBMS: SoC is reset to 100% if one cell reaches OVP (over voltage protection) voltage
;     As you have to adopt this value to your system, I reccomend to start with
;     OVP voltage - 0.030 (see Example).
;       - Try to increase (add) by 0.005 in steps, if the system does not switch to float mode, even if
;         the target voltage SOC_RESET_VOLTAGE * CELL_COUNT is reached.
;       - Try to decrease (lower) by 0.005 in steps, if the system hits the OVP too fast, before all
;         cells could be balanced and the system goes into protection mode multiple times.
; Example:
;     If OVP is 3.650, then start with 3.620 and increase/decrease by 0.005
; Note:
;     The value has to be higher as the MAX_CELL_VOLTAGE
;     You also have to set CELL_VOLTAGES_WHILE_CHARGING accordingly, if you set CCCM_CV_ENABLE to true
;         else the charging current will be reduced to 0 before the target voltage is reached and the
;         battery will never switch to float
SOC_RESET_VOLTAGE = 3.650
; Specify after how many days the soc reset voltage should be reached again
; The timer is reset when the soc reset voltage is reached
; Leave empty if you don't want to use this
; Example:
;     Value is set to 15
;     day 1: soc reset reached once
;     day 16: soc reset reached twice
;     day 31: soc reset not reached since it's very cloudy
;     day 34: soc reset reached since the sun came out
;     day 49: soc reset reached again, since last time it took 3 days to reach soc reset voltage
SOC_RESET_AFTER_DAYS =

; --------- Bluetooth BMS ---------
; Description:
;     Specify the Bluetooth BMS and it's MAC address that you want to install. Leave emty to disable
; Available Bluetooth BMS:
;     Jkbms_Ble, LltJbd_Ble
; Example for one BMS:
;     BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00
; Example for multiple BMS:
;     BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00, Jkbms_Ble C8:47:8C:00:00:11, Jkbms_Ble C8:47:8C:00:00:22
BLUETOOTH_BMS =

; --------- Bluetooth use USB ---------
; Description:  Some users reported issues to the built in bluetooth module, you can try to fix it with an USB
;     module. After a change you have to run reinstall-local.sh and to manual reboot the device!
;     The usb bluetooth module must have BLE support (bluetooth version >= 4.0)
;     Other bluetooth devices such as Ruuvi tags not tested yet.
; False: Use the built in bluetooth module
; True: Disable built in bluetooth module and try to use USB module
BLUETOOTH_USE_USB = False

; --------- CAN BMS ---------
; Description:
;     Specify the CAN port(s) where the BMS is connected to. Leave empty to disable
; Available CAN BMS:
;     Daly_Can, Jkbms_Can
; Example for one CAN port:
;     CAN_PORT = can0
; Example for multiple CAN ports:
;     CAN_PORT = can0, can8, can9
CAN_PORT =

; --------- BMS disconnect behaviour ---------
; Description:
;     Block charge and discharge when the communication to the BMS is lost. If you are removing the
;     BMS on purpose, then you have to restart the driver/system to reset the block.
; False:
;     Charge and discharge is not blocked on BMS communication loss for 20 minutes, if cell voltages are between
;     3.25 V and 3.35 V. Else the driver block charge and discharge after 60 seconds.
; True:
;     Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established
;     again or the driver/system is restarted. This is the Victron Energy default behaviour.
BLOCK_ON_DISCONNECT = False

; --------- Charge mode ---------
; Choose the mode for voltage / current limitations (True / False)
; False is a step mode: This is the default with limitations on hard boundary steps
; True is a linear mode:
;     For CCL and DCL the values between the steps are calculated for smoother values (by WaldemarFech)
;     For CVL max battery voltage is calculated dynamically in order that the max cell voltage is not exceeded
LINEAR_LIMITATION_ENABLE = True

; Specify in seconds how often the linear values should be recalculated
LINEAR_RECALCULATION_EVERY = 60
; Specify in percent when the linear values should be recalculated immediately
; Example:
;     5 for a immediate change, when the value changes by more than 5%
LINEAR_RECALCULATION_ON_PERC_CHANGE = 5

; --------- Charge Voltage limitation (affecting CVL) ---------
; Description:
;     Limit max charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float
;     voltage (FLOAT_CELL_VOLTAGE * cell count) and back
;     False: Max charging voltage is always kept
;     True: Max charging voltage is reduced based on charge mode
;         Step mode: After max voltage is reached for MAX_VOLTAGE_TIME_SEC it switches to float voltage. After
;             SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT it switches back to max voltage.
;         Linear mode: After max voltage is reachend and cell voltage difference is smaller or equal to
;             CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL it switches to float voltage after MAX_VOLTAGE_TIME_SEC
;             additional seconds.
;             After cell voltage difference is greater or equal to CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT
;             OR
;             SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT
;             it switches back to max voltage.
; Example when set to True:
;     Step mode:
;          The battery reached max voltage of 55.2V and hold it for 900 seconds, the the CVL is switched to
;          float voltage of 53.6V to don't stress the batteries. Allow max voltage of 55.2V again, if SoC is
;          once below 80%
;     Linear mode:
;          The battery reached max voltage of 55.2V and the max cell difference is 0.010V, then switch to float
;          voltage of 53.6V after 900 additional seconds to don't stress the batteries. Allow max voltage of
;          55.2V again if max cell difference is above 0.080V or SoC below 80%.
; Charge voltage control management enable (True/False).
CVCM_ENABLE = True

; -- CVL reset based on cell voltage diff (linear mode)
; Specify cell voltage diff where CVL limit is kept until diff is equal or lower
CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL        = 0.010
; Specify cell voltage diff where MAX_VOLTAGE_TIME_SEC restarts if diff is bigger
CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_TIME_RESTART = 0.013
; Specify cell voltage diff where CVL limit is reset to max voltage, if value get above
; the cells are considered as imbalanced, if the cell diff exceeds 5% of the nominal cell voltage
; e.g. 3.2 V * 5 / 100 = 0.160 V
CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT        = 0.080

; -- CVL reset based on SoC option (step mode & linear mode)
; Specify how long the max voltage should be kept
;     Step mode: If reached then switch to float voltage
;     Linear mode: If cells are balanced keep max voltage for further MAX_VOLTAGE_TIME_SEC seconds
MAX_VOLTAGE_TIME_SEC = 900
; Specify SoC where CVL limit is reset to max voltage
;     Step mode: If SoC gets below
;     Linear mode: If cells are unbalanced or if SoC gets below
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 80

; --------- SOC calculation ---------
; Description:
;     Calculate the SOC in the driver. Do not use the SOC reported by the BMS
; SOC_CALCULATION:
;     True: Calc SOC in the driver, do not use SOC reported from BMS
;         - The SOC is calculated by integration of the current reported by the BMS
;         - The current reported from the BMS can be corrected by
;           the map (SOC_CALC_CURRENT_REPORTED_BY_BMS, SOC_CALC_CURRENT_MEASURED_BY_USER)
;         - The SOC is set to 100% if the following conditions apply for at least SOC_RESET_TIME seconds:
;             * Current is lower than SOC_RESET_CURRENT amps
;             * Sum of cell voltages >= self.max_battery_voltage - VOLTAGE_DROP
;         - The calculated SOC is stored in dbus to persist a driver restart
;     False: Use SOC reported from BMS (none of the other parameters apply)
; More info: https://github.com/Louisvdw/dbus-serialbattery/pull/868
SOC_CALCULATION   = False
SOC_RESET_CURRENT = 7
SOC_RESET_TIME    = 60
SOC_CALC_CURRENT_REPORTED_BY_BMS  = -300, 300
SOC_CALC_CURRENT_MEASURED_BY_USER = -300, 300
; Example to set small currents to zero
;     SOC_CALC_CURRENT_REPORTED_BY_BMS  = -300, -0.5, 0.5, 300
;     SOC_CALC_CURRENT_MEASURED_BY_USER = -300,    0,   0, 300

; --------- Cell Voltage Current limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be in-/decreased depending on min and max cell voltages
; Example:
;     18 cells * 3.55V/cell = 63.9V max charge voltage
;     18 cells * 2.70V/cell = 48.6V min discharge voltage
;     But in reality not all cells reach the same voltage at the same time. The (dis)charge current
;     will be (in-/)decreased, if even ONE SINGLE BATTERY CELL reaches the limits

; Charge current control management referring to cell-voltage enable (True/False).
CCCM_CV_ENABLE = True
; Discharge current control management referring to cell-voltage enable (True/False).
DCCM_CV_ENABLE = True

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
CELL_VOLTAGES_WHILE_CHARGING      = 3.55, 3.50, 3.45, 3.30
MAX_CHARGE_CURRENT_CV_FRACTION    =    0, 0.05,  0.5,    1

CELL_VOLTAGES_WHILE_DISCHARGING   = 2.70, 2.80, 2.90, 3.10
MAX_DISCHARGE_CURRENT_CV_FRACTION =    0,  0.1,  0.5,    1

; --------- Cell Voltage limitation (affecting CVL) ---------
; This function prevents a bad balanced battery to overcharge the cell with the highest voltage and the bms to
; switch off because of overvoltage of this cell.
;
; Example:
;     15 cells are at 3.4v, 1 cell is at 3.6v. Total voltage of battery is 54.6v and the Victron System sees no reason to
;     lower the charging current as the control_voltage (Absorbtion Voltage) ist 55.2v
;     In this case the Cell Voltage limitation kicks in and lowers the control_voltage to keep it close to the MAX_CELL_VOLTAGE.
;
; In theory this can also be done with CCL, but doing it with CVL has 2 advantages:
;     - In a well balanced system the current can be kept quite high till the end of charge by using MAX_CELL_VOLTAGE for charging.
;     - In systems with MPPTs and DC-feed-in activated the victron systems do not respect CCL, so CVL is the only way to prevent the
;       highest cell in a bad balanced system from overcharging.
;
; There are 2 methods implemented to calculate CVL:
;   1. penalty_sum-Method (CVL_ICONTROLLER_MODE = False)
;      The voltage-overshoot of all cells that exceed MAX_CELL_VOLTAGE is summed up and the control voltage is lowered by this "penalty_sum".
;      This is calculated every LINEAR_RECALCULATION_EVERY seconds.
;      In fact, this is a P-Controller.
;   2. I-Controller (CVL_ICONTROLLER_MODE = True)
;      An I-Controller tries to control the voltage of the highest cell to MAX_CELL_VOLTAGE + CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL.
;      (for example 3.45V+0.01V =3.46V). If the voltage of the highest cell is above this level, CVL is reduced. If the voltage is below, CVL is
;      increased until cellcount*MAX_CELL_VOLTAGE.
;      An I-Part of 0.2 V/Vs (CVL_ICONTROLLER_FACTOR) has proved to be a stable and fast controlling-behaviour.
;      This method is not as fast as the penalty_sum-Method but usually smoother and more stable against toggeling and has no stationary deviation.
; More info: https://github.com/Louisvdw/dbus-serialbattery/pull/882
CVL_ICONTROLLER_MODE   = False
CVL_ICONTROLLER_FACTOR = 0.2

; --------- Temperature limitation (affecting CCL/DCL) ---------
; Description:
;     Maximal charge / discharge current will be in-/decreased depending on temperature
; Example:
;     The temperature limit will be monitored to control the currents. If there are two temperature senors,
;     then the worst case will be calculated and the more secure lower current will be set.
; Charge current control management referring to temperature enable (True/False).
CCCM_T_ENABLE = True
; Charge current control management referring to temperature enable (True/False).
DCCM_T_ENABLE = True

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
TEMPERATURES_WHILE_CHARGING      =    0,    2,    5,   10,   15,   20,   35,   40,   55
MAX_CHARGE_CURRENT_T_FRACTION    = 0.00, 0.10, 0.20, 0.40, 0.80, 1.00, 1.00, 0.40, 0.00

TEMPERATURES_WHILE_DISCHARGING   =  -20,    0,    5,   10,   15,   45,   55
MAX_DISCHARGE_CURRENT_T_FRACTION = 0.00, 0.20, 0.30, 0.40, 1.00, 1.00, 0.00

; --------- SOC limitation (affecting CCL/DCL) ---------
; Description:
;     Maximal charge / discharge current will be increased / decreased depending on State of Charge
;     Since the SoC is not as accurate as the cell voltage, this option is disabled by default
; Example:
;     The SoC limit will be monitored to control the currents.
; Charge current control management enable (True/False).
CCCM_SOC_ENABLE = False
; Discharge current control management enable (True/False).
DCCM_SOC_ENABLE = False

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
SOC_WHILE_CHARGING                 =   98,   95,   90,   85
MAX_CHARGE_CURRENT_SOC_FRACTION    = 0.10, 0.20, 0.50, 1.00

SOC_WHILE_DISCHARGING              =    5,   10,   15,   20
MAX_DISCHARGE_CURRENT_SOC_FRACTION = 0.10, 0.20, 0.50, 1.00

; --------- Time-To-Go ---------
; Description:
;     Calculates the time to go shown in the GUI
;     Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY
TIME_TO_GO_ENABLE = True

; --------- Time-To-Soc ---------
; Description:
;     Calculates the time to a specific SoC
; Example:
;     TIME_TO_SOC_POINTS = 50, 25, 15, 0
;     6h 24m remaining until 50% SoC
;     17h 36m remaining until 25% SoC
;     22h 5m remaining until 15% SoC
;     28h 48m remaining until 0% SoC
; Set of SoC percentages to report on dbus and MQTT. The more you specify the more it will impact system performance.
; [Valid values 0-100, comma separated list. More that 20 intervals are not recommended]
; Example: TIME_TO_SOC_POINTS = 100, 95, 90, 85, 75, 50, 25, 20, 10, 0
; Leave empty to disable
TIME_TO_SOC_POINTS =
; Specify TimeToSoc value type [Valid values 1, 2, 3]
; 1 Seconds
; 2 Time string <days>d <hours>h <minutes>m <seconds>s
; 3 Both seconds and time string "<seconds> [<days>d <hours>h <minutes>m <seconds>s]"
TIME_TO_SOC_VALUE_TYPE = 1
; Specify in seconds how often the TimeToSoc should be recalculated
; Minimum are 5 seconds to prevent CPU overload
TIME_TO_SOC_RECALCULATE_EVERY = 60
; Include TimeToSoC points when moving away from the SoC point [Valid values True, False]
; These will be as negative time. Disabling this improves performance slightly
TIME_TO_SOC_INC_FROM = False

; --------- Additional settings ---------
; Specify one or more BMS types to load else leave empty to try to load all available
; Available BMS:
;     Daly, Ecs, HeltecModbus, HLPdataBMS4S, Jkbms, Lifepower, LltJbd, Renogy, Seplos
; Available BMS, but disabled by default (just enter one or more below and it will be enabled):
;     ANT, MNB, Sinowealth
BMS_TYPE = Daly

; Exclute this serial devices from the driver startup
; Example:
;     /dev/ttyUSB2, /dev/ttyUSB4
EXCLUDED_DEVICES =

; Auto reset SoC
; If on, then SoC is reset to 100%, if the value switches from absorption to float voltage
; Currently only working for Daly BMS and JKBMS BLE
AUTO_RESET_SOC = True

; Publish the config settings to the dbus path "/Info/Config/"
PUBLISH_CONFIG_VALUES = True

; Select the format of cell data presented on dbus [Valid values 0,1,2,3]
; 0 Do not publish all the cells (only the min/max cell data as used by the default GX)
; 1 Format: /Voltages/Cell (also available for display on Remote Console)
; 2 Format: /Cell/#/Volts
; 3 Both formats 1 and 2
BATTERY_CELL_DATA_FORMAT = 1

; Simulate Midpoint graph (True/False).
MIDPOINT_ENABLE = False

; Battery temperature
; Specify how the battery temperature is assembled
; 0 Get mean of temperature sensor 1 to sensor 4
; 1 Get only temperature from temperature sensor 1
; 2 Get only temperature from temperature sensor 2
; 3 Get only temperature from temperature sensor 3
; 4 Get only temperature from temperature sensor 4
TEMP_BATTERY = 0

; Temperature sensor 1 name
TEMP_1_NAME = Temp 1

; Temperature sensor 2 name
TEMP_2_NAME = Temp 2

; Temperature sensor 2 name
TEMP_3_NAME = Temp 3

; Temperature sensor 2 name
TEMP_4_NAME = Temp 4

; --------- BMS specific settings ---------

; -- LltJbd settings
; SoC low levels
; Note:
;     SOC_LOW_WARNING is also used to calculate the Time-To-Go even if you are not using a LltJbd BMS
SOC_LOW_WARNING = 20
SOC_LOW_ALARM   = 10

; -- Daly settings
; Battery capacity (amps), if the BMS does not support reading it
BATTERY_CAPACITY = 50
; Invert Battery Current. Default non-inverted. Set to -1 to invert
INVERT_CURRENT_MEASUREMENT = 1

; -- JKBMS settings
; Predefines cell count for Jkbms_can
; The cell count should be auto-detected by identifying the highest cell number,
; but this process may be sometimes slow what could cause that cells voltage is not not
; updated in VenusOS. Try this workaround if you experience problems with cell voltage.
JKBMS_CAN_CELL_COUNT = 1

; -- ESC GreenMeter and Lipro device settings
GREENMETER_ADDRESS  = 1
LIPRO_START_ADDRESS = 2
LIPRO_END_ADDRESS   = 4
LIPRO_CELL_COUNT    = 15

; -- HeltecModbus (Heltec SmartBMS/YYBMS) settings
; Set the Modbus addresses from the adapters
; Separate each address to check by a comma like: 1, 2, 3, ...
; factory default address will be 1
HELTEC_MODBUS_ADDR = 1

; --------- Voltage drop ---------
; If you have a voltage drop between the BMS and the charger because of wire size or length
; then you can specify the voltage drop here. The driver will then add the voltage drop
; to the calculated CVL to compensate.
; Example:
;     cell count: 16
;     MAX_CELL_VOLTAGE = 3.45
;     max voltage calculated = 16 * 3.45 = 55.20
;     CVL is set to 55.20 V and the battery is now charged until the charger reaches 55.20 V.
;     The BMS now measures 55.05 V since there is a voltage drop of 0.15 V on the cable.
;     Since the dbus-serialbattery reads the voltage of 55.05 V from the BMS the max voltage
;     of 55.20 V is never reached and max voltage is kept forever.
;     By setting the VOLTAGE_DROP to 0.15 V the voltage on the charger is increased and the
;     target voltage on the BMS is reached.
VOLTAGE_DROP = 0.00

Relevant log output

@4000000066e1549813e78714 *** CCGX booted (0) ***
@4000000066e154983237a104 *** starting serial-starter ***
@4000000066e154991ae619cc serstart starting
@4000000066e154991c35daec INFO: loading config file /etc/venus/serial-starter.conf
@4000000066e1549a18ea97ec INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@4000000066e1549b317f8434 INFO: Create daemontools service mk2-dbus.ttyS4
@4000000066e1549d1396464c INFO: Create daemontools service vedirect-interface.ttyS5
@4000000066e1549e351516a4 INFO: Create daemontools service vedirect-interface.ttyS6
@4000000066e154a01b8900ec INFO: Create daemontools service vedirect-interface.ttyS7
@4000000066e154a205fc1cb4 INFO: Start service mk2-dbus.ttyS4
@4000000066e154a2205f6444 INFO: Create daemontools service dbus-serialbattery.ttyUSB0
@4000000066e154a32214ad94 INFO: Start service vedirect-interface.ttyS5
@4000000066e154a42d9e98b4 INFO: Create daemontools service dbus-serialbattery.ttyUSB1
@4000000066e154a506aaf66c INFO: Start service vedirect-interface.ttyS6
@4000000066e154a6287a4824 INFO: Start service vedirect-interface.ttyS7
@4000000066e154a835c9a934 INFO: Start service dbus-serialbattery.ttyUSB0 once
@4000000066e154aa3791cabc INFO: Start service dbus-serialbattery.ttyUSB1 once
@4000000066e154ad28b5b314 INFO: Create daemontools service gps-dbus.ttyUSB0
@4000000066e154b013ab31c4 INFO: Create daemontools service gps-dbus.ttyUSB1
@4000000066e154b33b567f94 INFO: Start service gps-dbus.ttyUSB0 once
@4000000066e154b623ca21dc INFO: Start service gps-dbus.ttyUSB1 once
@4000000066e154bf0d4f10fc INFO: Create daemontools service vedirect-interface.ttyUSB0
@4000000066e154c11503e3f4 INFO: Create daemontools service vedirect-interface.ttyUSB1
@4000000066e154c51b2495e4 INFO: Start service vedirect-interface.ttyUSB0 once
@4000000066e154c722d8fb7c INFO: Start service vedirect-interface.ttyUSB1 once
@4000000066e154cb39423dc4 INFO: Create daemontools service dbus-cgwacs.ttyUSB0
@4000000066e154cd2a8dca8c INFO: Create daemontools service dbus-cgwacs.ttyUSB1
@4000000066e154d20b21ff9c INFO: Start service dbus-cgwacs.ttyUSB0 once
@4000000066e154d334da99fc INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e154d50fe2f2ac INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB0
@4000000066e154d8283dcbc4 INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB1
@4000000066e154db174a0f1c INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
@4000000066e154de2c44060c INFO: Start service dbus-fzsonick-48tl.ttyUSB1 once
@4000000066e154e03a5e3ce4 INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB0
@4000000066e154e705ce1774 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
@4000000066e154e7083e503c INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB1
@4000000066e154ed14da573c INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
@4000000066e154ef1628051c INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB0
@4000000066e154f51ffcaad4 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
@4000000066e154f525a6159c INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB1
@4000000066e154fb2c7c34dc INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
@4000000066e154ff241119d4 INFO: Start service dbus-serialbattery.ttyUSB0 once
@4000000066e1550237a696f4 INFO: Start service dbus-serialbattery.ttyUSB1 once
@4000000066e155243a7e4804 INFO: Start service gps-dbus.ttyUSB1 once
@4000000066e1552e2f84257c INFO: Start service vedirect-interface.ttyUSB1 once
@4000000066e155341039c924 INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e155611426e9a4 *** CCGX booted (0) ***
@4000000066e1556133de2514 *** starting serial-starter ***
@4000000066e155621b9bfc4c serstart starting
@4000000066e155621b9bfc4c serstart starting
@4000000066e155621c0e9ff4 INFO: loading config file /etc/venus/serial-starter.conf
@4000000066e1556316cfdddc INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@4000000066e155642ed98d9c INFO: Create daemontools service mk2-dbus.ttyS4
@4000000066e155660cc34bbc INFO: Create daemontools service vedirect-interface.ttyS5
@4000000066e155672e385814 INFO: Create daemontools service vedirect-interface.ttyS6
@4000000066e15569154e27ac INFO: Create daemontools service vedirect-interface.ttyS7
@4000000066e1556a3b734e94 INFO: Start service mk2-dbus.ttyS4
@4000000066e1556b1df482ac INFO: Create daemontools service dbus-serialbattery.ttyUSB0
@4000000066e1556c1bdd3784 INFO: Start service vedirect-interface.ttyS5
@4000000066e1556d2c239d2c INFO: Create daemontools service dbus-cgwacs.ttyUSB1
@4000000066e1556d36bb15e4 INFO: Start service vedirect-interface.ttyS6
@4000000066e1556f1eae7054 INFO: Start service vedirect-interface.ttyS7
@4000000066e155712c0d1f5c INFO: Start service dbus-serialbattery.ttyUSB0 once
@4000000066e155733ae50c9c INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e15576185126ac INFO: Create daemontools service gps-dbus.ttyUSB0
@4000000066e1557908ddf36c INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB1
@4000000066e1557c29a18244 INFO: Start service gps-dbus.ttyUSB0 once
@4000000066e1557f172ac74c INFO: Start service dbus-fzsonick-48tl.ttyUSB1 once
@4000000066e1558803479f5c INFO: Create daemontools service vedirect-interface.ttyUSB0
@4000000066e1558c1d156964 INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB1
@4000000066e1558e0dee8934 INFO: Start service vedirect-interface.ttyUSB0 once
@4000000066e1559228a501a4 INFO: Create daemontools service dbus-cgwacs.ttyUSB0
@4000000066e155922ba9a684 INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
@4000000066e1559835b6bd74 INFO: Start service dbus-cgwacs.ttyUSB0 once
@4000000066e1559a1403a64c INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB1
@4000000066e1559d2ae5f4dc INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB0
@4000000066e155a01858817c INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
@4000000066e155a32f2cf144 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
@4000000066e155aa09ffedcc INFO: Create daemontools service dbus-serialbattery.ttyUSB1
@4000000066e155ad2a67e36c INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB0
@4000000066e155b014bad0ec INFO: Start service dbus-serialbattery.ttyUSB1 once
@4000000066e155b3321e21ac INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
@4000000066e155b929f8702c INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB0
@4000000066e155bf2fce3e3c INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
@4000000066e155c91728f674 INFO: Start service dbus-serialbattery.ttyUSB0 once
@4000000066e155cc30163034 INFO: Create daemontools service gps-dbus.ttyUSB1
@4000000066e155d23363c8dc INFO: Start service gps-dbus.ttyUSB1 once
@4000000066e155dc17af9b34 INFO: Create daemontools service vedirect-interface.ttyUSB1
@4000000066e155e21a64c46c INFO: Start service vedirect-interface.ttyUSB1 once
@4000000066e155e80bf9d584 INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e155ed38a0930c INFO: Start service dbus-fzsonick-48tl.ttyUSB1 once
@4000000066e155f30f6137bc INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
@4000000066e155f701306ba4 INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
@4000000066e15621395e41a4 INFO: Start service vedirect-interface.ttyUSB1 once
@4000000066e156270f4cbd8c INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e1562a23faea24 INFO: Start service dbus-fzsonick-48tl.ttyUSB1 once
@4000000066e1562e0fb25944 INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
@4000000066e1563126ef182c INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
@4000000066e1563901b89704 INFO: Start service dbus-serialbattery.ttyUSB1 once
@4000000066e156921acfc6f4 INFO: Start service gps-dbus.ttyUSB1 once
@4000000066e1569c1809bd6c INFO: Start service vedirect-interface.ttyUSB1 once
@4000000066e156a2026b3594 INFO: Start service dbus-cgwacs.ttyUSB1 once
@4000000066e156a915abeb94 INFO: Start service dbus-fzsonick-48tl.ttyUSB1 once
@4000000066e156ae308c2b54 INFO: Start service dbus-imt-si-rs485tc.ttyUSB1 once
@4000000066e156b408ac2954 INFO: Start service dbus-modbus-client.serial.ttyUSB1 once
@4000000066e156bd20f0f1fc INFO: Start service dbus-serialbattery.ttyUSB1 once

@4000000066e154e5218a5b6c INFO:SerialBattery:========== Settings ==========
@4000000066e154e52198846c INFO:SerialBattery:> Connection voltage: 60.0 V | Current: 0.0 A | SoC: 85.8%
@4000000066e154e521a54224 INFO:SerialBattery:> Cell count: 18 | Cells populated: 0
@4000000066e154e521b11194 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@4000000066e154e52277a96c INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
@4000000066e154e522844bcc INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 75.0 A | MAX BATTERY DISCHARGE CURRENT: 150.0 A
@4000000066e154e522a3e98c INFO:SerialBattery:> CVCM:     True
@4000000066e154e522f3885c INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@4000000066e154e522f3a79c INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@4000000066e154e522f3b354 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@4000000066e154e522fadf44 INFO:SerialBattery:> CHARGE FET: None | DISCHARGE FET: None | BALANCE FET: None
@4000000066e154e52306e564 INFO:SerialBattery:Serial Number/Unique Identifier: 20230708
@4000000066e154f90230ef9c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e154f91932a154 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e154f91a31ae4c WARNING:SerialBattery:Polling took too long. Set to 2.000 s
@4000000066e154f93501dcc4 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e154fa107518bc INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e154fb0139ed3c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e154fb1855ba8c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e154fc1290d884 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e154fd0fcd576c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e154fd270069c4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155351d52d7f4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155372183b064 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155610b89dd74 *** CCGX booted (0) ***
@4000000066e155931299e8d4 INFO:SerialBattery:
@4000000066e1559312a87b4c INFO:SerialBattery:Starting dbus-serialbattery
@4000000066e1559314fec374 INFO:SerialBattery:Venus OS v3.41
@4000000066e15593154123a4 INFO:SerialBattery:dbus-serialbattery v1.4.20240902dev
@4000000066e155a31684cf04 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@4000000066e155a31691466c INFO:SerialBattery:Testing Daly at address "\x40"
@4000000066e155a332fb3754 INFO:SerialBattery:Connection established to Daly
@4000000066e155a82a8dd644 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@4000000066e155a907e1344c INFO:SerialBattery:DeviceInstance = 1
@4000000066e155a90805276c INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
@4000000066e155a908177304 INFO:SerialBattery:Used DeviceInstances = ['2', '1']
@4000000066e155a9084b776c INFO:SerialBattery:com.victronenergy.battery.ttyUSB0__0
@4000000066e155a90f530ebc INFO:SerialBattery:publish config values = False
@4000000066e155a911f55404 INFO:SerialBattery:Polling data every 1.000 s
@4000000066e155a9121be31c INFO:SerialBattery:Battery Daly connected to dbus from /dev/ttyUSB0
@4000000066e155a912b2ef14 INFO:SerialBattery:========== Settings ==========
@4000000066e155a913026ea4 INFO:SerialBattery:> Connection voltage: 60.1 V | Current: -0.06 A | SoC: 86.0%
@4000000066e155a913127fec INFO:SerialBattery:> Cell count: 18 | Cells populated: 0
@4000000066e155a913219b1c INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@4000000066e155a9133142ec INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
@4000000066e155a91374666c INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 75.0 A | MAX BATTERY DISCHARGE CURRENT: 150.0 A
@4000000066e155a913856dcc INFO:SerialBattery:> CVCM:     True
@4000000066e155a913967144 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@4000000066e155a913a6152c INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@4000000066e155a913b76aac INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@4000000066e155a9143652f4 INFO:SerialBattery:> CHARGE FET: None | DISCHARGE FET: None | BALANCE FET: None
@4000000066e155a9144cffa4 INFO:SerialBattery:Serial Number/Unique Identifier: 20230708
@4000000066e155b908110294 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155b90d80d344 WARNING:SerialBattery:Polling took too long. Set to 3.000 s
@4000000066e155c326240bb4 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155c3392fc34c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155c43a400a6c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155c515ac0ad4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155c53120223c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155c60cba2bcc INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155c70d059864 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155c7242b29b4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155ca07b50f84 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155ca1c5da66c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155e91e465014 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155ea1a2cdbec INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155eb237f074c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e155f008510d1c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e155f022431c4c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156151398cad4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a213545b4c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e156a227c0912c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a32394a28c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a430657914 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a5301983c4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a62670c83c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156a713d80e24 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e156a735e1c12c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156ba3704b58c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e156d4018bf924 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e1574f2b7a553c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e1575004712b3c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e157510ea6e09c INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e15765057149a4 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e157653b652d64 WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e1576618ab25bc INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e157670e1ca1fc INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.
@4000000066e1576735b2642c WARNING:SerialBattery:No data received in read_alarm_data()
@4000000066e157680e3c4b74 INFO:SerialBattery:refresh_data: result: False. If you don't see this warning very often, you can ignore it.

Any other information that may be helpful

Nil

Louisvdw / dbus-serialbattery