Dbus Serialbattery does not work with new JK Inverter BMS and VE Can post 500kbit/s
Martinmaker92 opened this issue · comments
Describe the bug
I set up my system with new JK Inverter BMS Master/Slave configuration. They didnt appear in my VRM until i changet the setting in service / VE Can Port / Can Bus Profile / to Can Bus BMS (500 kbit/s)
Now i updated the Serialbattery to the latest version an modified the settings. I applied everything and rebootet the Cerbo several times. The settings dont apply to my system. I think the problem could be the can bus, because it is mentioned in the serial battery that it should be 250 kbit/s, but with this setting i cant connect to my BMS.
How to reproduce
See the Description
Expected behavior
The settings in the serialbattery should control my charge current.
Driver version
v1.2.20240408
Venus OS device type
Cerbo GX
Venus OS version
v3.31
BMS type
JKBMS / Heltec BMS
Cell count
16
Battery count
3
Connection type
Serial USB adapter to RS485
Config file
; --------- 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 recalculatedRelevant log output
@40000000663752d0040021bc *** starting serial-starter ***
@40000000663752d01e195474 serstart starting
@40000000663752d01fd4104c INFO: loading config file /etc/venus/serial-starter.conf
@40000000663752d1247c5adc INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@40000000663752d3229b275c INFO: Create daemontools service mk2-dbus.ttyS4
@40000000663752d5077ad15c INFO: Create daemontools service vedirect-interface.ttyS5
@40000000663752d62d479f14 INFO: Create daemontools service vedirect-interface.ttyS6
@40000000663752d8166cc6ac INFO: Create daemontools service vedirect-interface.ttyS7
@40000000663752d93413cb74 INFO: Start service mk2-dbus.ttyS4
@40000000663752db1510b91c INFO: Start service vedirect-interface.ttyS5
@40000000663752dd016421ec INFO: Start service vedirect-interface.ttyS6
@40000000663752de21aab4ac INFO: Start service vedirect-interface.ttyS7
@400000006637547112f97d94 *** CCGX booted (0) ***
@40000000663754713557a99c *** starting serial-starter ***
@40000000663754721ce53974 serstart starting
@40000000663754721ec6613c INFO: loading config file /etc/venus/serial-starter.conf
@40000000663754731c428904 INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@4000000066375475227d6a14 INFO: Create daemontools service mk2-dbus.ttyS4
@4000000066375477048b334c INFO: Create daemontools service vedirect-interface.ttyS5
@4000000066375478247bce3c INFO: Create daemontools service vedirect-interface.ttyS6
@400000006637547a0e91b2bc INFO: Create daemontools service vedirect-interface.ttyS7
@400000006637547b33b68874 INFO: Start service mk2-dbus.ttyS4
@400000006637547d137b28e4 INFO: Start service vedirect-interface.ttyS5
@400000006637547e35b0c61c INFO: Start service vedirect-interface.ttyS6
@40000000663754801b619ee4 INFO: Start service vedirect-interface.ttyS7
@40000000663754dc07fcc6e4 INFO: Start service vedirect-interface.ttyS5
@40000000663754dd14fd8324 INFO: Start service vedirect-interface.ttyS6
@40000000663754de1dd8a1f4 INFO: Start service vedirect-interface.ttyS7
@400000006637567b1d4bb3d4 INFO: Start service mk2-dbus.ttyS4
@40000000663756e92dd75bf4 INFO: Start service vedirect-interface.ttyS5
@40000000663756ea333e6e5c INFO: Start service vedirect-interface.ttyS6
@40000000663756eb3a274694 INFO: Start service vedirect-interface.ttyS7
@4000000066375e7210fda5c4 *** CCGX booted (0) ***
@4000000066375e7234b7c404 *** starting serial-starter ***
@4000000066375e7320eab06c serstart starting
@4000000066375e732230f3dc INFO: loading config file /etc/venus/serial-starter.conf
@4000000066375e742380014c INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@4000000066375e76245cc104 INFO: Create daemontools service mk2-dbus.ttyS4
@4000000066375e7807c357c4 INFO: Create daemontools service vedirect-interface.ttyS5
@4000000066375e792b6fe55c INFO: Create daemontools service vedirect-interface.ttyS6
@4000000066375e7b163c3ce4 INFO: Create daemontools service vedirect-interface.ttyS7
@4000000066375e7c335d7f7c INFO: Start service mk2-dbus.ttyS4
@4000000066375e7e190af12c INFO: Start service vedirect-interface.ttyS5
@4000000066375e80036a0fc4 INFO: Start service vedirect-interface.ttyS6
@4000000066375e812afcdc24 INFO: Start service vedirect-interface.ttyS7
@40000000663760cc195f1ff4 *** CCGX booted (0) ***
@40000000663760cc3b807d94 *** starting serial-starter ***
@40000000663760cd2410d76c serstart starting
@40000000663760cd26196524 INFO: loading config file /etc/venus/serial-starter.conf
@40000000663760ce1dbc86a4 INFO: loading config file /data/conf/serial-starter.d/dbus-serialbattery.conf
@40000000663760d0104c10d4 INFO: Create daemontools service mk2-dbus.ttyS4
@40000000663760d1389724fc INFO: Create daemontools service vedirect-interface.ttyS5
@40000000663760d31ff0f2d4 INFO: Create daemontools service vedirect-interface.ttyS6
@40000000663760d509bb91cc INFO: Create daemontools service vedirect-interface.ttyS7
@40000000663760d61f56be44 INFO: Start service mk2-dbus.ttyS4
@40000000663760d80fccb35c INFO: Start service vedirect-interface.ttyS5
@40000000663760d9328a9f1c INFO: Start service vedirect-interface.ttyS6
@40000000663760db13300e54 INFO: Start service vedirect-interface.ttyS7
@40000000663763c514376464 *** CCGX booted (0) ***Any other information that may be helpful
No response
