search

Louisvdw / dbus-serialbattery

Battery Monitor driver for serial battery in VenusOS GX systems
MIT License
522 stars 164 forks source link

Charging Current Limited by BMS with multi batteries #849

Closed Martinmaker92 closed 10 months ago

Martinmaker92 commented 10 months ago

Describe the problem

i am using 4 Batteries in parallel, 3 of the are connected to the Cerbo

i choose one of them as battery monitor.

now my problem is my maximun input an output current is limited to 150A by my Master BMS (i cant change this value on the BMS)

Because i use 4 batterys i could charge with up to 400Amps without a problem, i have already set these high values in the config file but i think my Master BMS Limits the current to 150Amps.

So how can i let the system ignore this value? i dont want to use a multi battery setup. I have used this before with an oder version of the driver and it worked fine.

image

Driver version

1.0.20230531

Venus OS device type

Cerbo GX

Venus OS version

3.11

BMS type

JKBMS / Heltec BMS

Cell count

18

Connection type

Serial USB adapter to TTL

Config file

[DEFAULT]

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 250.0
MAX_BATTERY_DISCHARGE_CURRENT = 250.0

; --------- 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.700
; Max voltage can seen as absorption voltage
MAX_CELL_VOLTAGE   = 3.450
FLOAT_CELL_VOLTAGE = 3.43

; --------- Bluetooth BMS ---------
; Description: List the Bluetooth BMS here that you want to install
; -- Available Bluetooth BMS:
; Jkbms_Ble, LltJbd_Ble
; Example:
;     1 BMS: Jkbms_Ble C8:47:8C:00:00:00
;     3 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 =

; --------- 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
; True: Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established
;       again or the driver/system is restarted
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 = False

; 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 300 (fixed)
;                      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
                                                                                                             [ Read 269 lines ]
^G Get Help       ^O Write Out      ^W Where Is       ^K Cut Text       ^J Justify        ^C Cur Pos        M-U Undo

Relevant log output

root@einstein:~# nano /data/log/serial-starter/current
  GNU nano 4.9.3                                                                                         /data/log/serial-starter/current
@400000006541f1d821c875dc INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f1dd34760bcc INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f1e72026df84 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f1ec35aba59c INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f2130daf613c INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f2182917284c INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f222034df85c INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f2251b27f144 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f24b325a4434 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f2511011f1ec INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f25a2df40bb4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f25e02d78fdc INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f2861adc6d3c INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f28c0f94f1ec INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f29601947cd4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f29b25dc871c INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f2c202177fe4 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f2c7157a63e4 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f2d03861c8d4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f2d4128280a4 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f2fa362a66d4 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f3000b3b7ef4 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f30929fe38a4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f30f090da65c INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f3351913ab8c INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f33a341050d4 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f3441a252f14 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f34930933034 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f37224130604 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f37805e16cac INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f38124623b5c INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f38707ab1ca4 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f3ad1724cff4 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f3b22dfff294 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f3bc1191b41c INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f3c1249a0c6c INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f3ea0afa4f74 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f3ef2b6d9b6c INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f3f9238bd4a4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f3fc358053c4 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f4231f9e8d14 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f42831dcf614 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f43223868544 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f4373486c124 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f45e17fffd54 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f4632bca8c64 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f46d13fa8274 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f47231730ccc INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f49920b321c4 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f49f00063f9c INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f4a8341058a4 INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f4ae07d3ab74 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f4d426cf8624 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f4da03abc7fc INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f4e3248d817c INFO: Start service vedirect-interface.ttyUSB1 once
@400000006541f4e636752b74 INFO: Start service dbus-serialbattery.ttyUSB1 once
@400000006541f50d0e8b1754 INFO: Start service dbus-cgwacs.ttyUSB1 once
@400000006541f5122674ac54 INFO: Start service gps-dbus.ttyUSB1 once
@400000006541f51c0568644c INFO: Start service vedirect-interface.ttyUSB1 once

 [1/4]                                                                                        /data/log/dbus-serialbattery.ttyUSB0/current
@40000000653d21220e099ae4 INFO:SerialBattery:========== Settings ==========
@40000000653d21220e09be0c INFO:SerialBattery:> Connection voltage: 60.11V | Current: -0.0A | SoC: 99%
@40000000653d21220e1e24b4 INFO:SerialBattery:> Cell count: 18 | Cells populated: 0
@40000000653d21220e307c04 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@40000000653d21220e437b4c INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 50.0A | MAX BATTERY DISCHARGE CURRENT: 60.0A
@40000000653d21220e65a564 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A (read from BMS)
@40000000653d21220e790a3c INFO:SerialBattery:> CVCM:     True
@40000000653d21220e9d18b4 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@40000000653d21220eb06a04 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@40000000653d21220ec6cc7c INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@40000000653d21220ed9d394 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
@40000000653d21220eebe0ac INFO:SerialBattery:Serial Number/Unique Identifier: JK_Pack_4
@40000000653d212213b97234 INFO:SerialBattery:DeviceInstance = 1
@40000000653d212213c8d3b4 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
@40000000653d212216aa8f14 INFO:SerialBattery:publish config values = 1
@40000000653d22f2068818a4 *** CCGX booted (0) ***
@40000000653d230d18d3db9c INFO:SerialBattery:Starting dbus-serialbattery
@40000000653d230d1a3fb80c INFO:SerialBattery:dbus-serialbattery v1.0.20230531
@40000000653d230d1b4a6594 INFO:SerialBattery:Testing Daly
@40000000653d230d24560274 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d230d24563154 INFO:SerialBattery:Testing Daly
@40000000653d230d2cc3e854 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d230d2cc40794 INFO:SerialBattery:Testing Ecs
@40000000653d230d31b188e4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d230d31b1aff4 INFO:SerialBattery:Testing HeltecModbus
@40000000653d2311283933fc ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d231128395b0c INFO:SerialBattery:Testing HLPdataBMS4S
@40000000653d23160c327984 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23160c32a094 INFO:SerialBattery:Testing Jkbms
@40000000653d23162019c7f4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23162067f794 INFO:SerialBattery:Testing Lifepower
@40000000653d231632f1679c ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23163355133c INFO:SerialBattery:Testing LltJbd
@40000000653d23170966b724 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d231709a48b44 INFO:SerialBattery:Testing Renogy
@40000000653d23171b2d2d1c ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23171b9b0e04 INFO:SerialBattery:Testing Renogy
@40000000653d23172d056dc4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23172d7152dc INFO:SerialBattery:Testing Seplos
@40000000653d23182ef5d7cc ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d231911901224 INFO:SerialBattery:Testing Daly
@40000000653d231919f77fc4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23191a05b094 INFO:SerialBattery:Testing Daly
@40000000653d23192297a8d4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23192297c044 INFO:SerialBattery:Testing Ecs
@40000000653d23191eeb3ad4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d23191efdebfc INFO:SerialBattery:Testing HeltecModbus
@40000000653d231d15ba5ae4 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d231d15c7477c INFO:SerialBattery:Testing HLPdataBMS4S
@40000000653d232135431414 ERROR:SerialBattery:>>> ERROR: No reply - returning
@40000000653d232135510664 INFO:SerialBattery:Testing Jkbms
@40000000653d23220270fe0c INFO:SerialBattery:Connection established to Jkbms
@40000000653d2322028ca814 INFO:SerialBattery:Battery Jkbms connected to dbus from /dev/ttyUSB0
@40000000653d23220295b864 INFO:SerialBattery:========== Settings ==========
@40000000653d232202e08ca4 INFO:SerialBattery:> Connection voltage: 60.15V | Current: -0.0A | SoC: 99%
@40000000653d232202e0b3b4 INFO:SerialBattery:> Cell count: 18 | Cells populated: 0
@40000000653d232202e0bf6c INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@40000000653d232202e0cb24 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 350.0A | MAX BATTERY DISCHARGE CURRENT: 360.0A
@40000000653d2322031b24a4 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A (read from BMS)

Any other information that may be helpful

No response

mr-manuel commented 10 months ago

If you are using multiple batteries you need to use a battery aggregator else you cannot use the full system power. There is no other way for the system to know all battery details. See How to aggregate multiple batteries?

Martinmaker92 commented 10 months ago

Hi i installted the driver and it shows 450A max current but the limitation still seems to be active at about 100A

i have changed all the parameters in the Config but it still pushes down the power of my mppts, if i set the gridsetpoint to about -4000 all the power comes from the mppts

mr-manuel commented 10 months ago

Which driver have you installed? Did you select the aggregator as BMS in the DVCC settings?

Martinmaker92 commented 10 months ago

I have installed the first battery aggregator which is on the github of dbus serialbatteryI changed the battery in system setup vur noch in DVCC no it works just fine thank you!Am 04.11.2023 21:13 schrieb Manuel @.***>: Which driver have you installed? Did you select the aggregator as BMS in the DVCC settings?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>