question

zahnpasta avatar image
zahnpasta asked

Battery keeps charing and discharging all the time and never rests - Serial Battery

I have got a 3 phase Multiplus 2 5000 and a 2 batterie 18S system.

As soon as the set voltage is reached and DC feed in is active, the power constantly fluctuates between approx. 300w charging and then 300w discharging again. the battery never goes to rest, is that normal? There is a constant fluctuation between charging and discharging.

When the set voltage is more like 0.1 - 0.2V above the set MAX_CELL_VOLTAGE, Victrons start to discharge ramping up to almost full power depending on voltage above the set value.

bildschirmfoto-2023-09-17-um-145151.png

bildschirmfoto-2023-09-17-um-145219.png

Another problem is, the system ignores the set „max charging current“. Why is that?


268968438-a4281343-bcfd-4ebf-a2e3-9cd14286201d.jpeg

268968506-4e033973-5808-4c5c-86f4-3727eba0d3d3.jpeg




Driver version

latest

Venus OS device type

Raspberry Pi

Venus OS version

latest

BMS type

Smart BMS (LLT, JBD, Overkill Solar)

Cell count

2 x 18

Connection type

Serial USB adapter to RS485


Config file

[DEFAULT]

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 150.0
MAX_BATTERY_DISCHARGE_CURRENT = 150.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.900
; Max voltage can seen as absorption voltage
MAX_CELL_VOLTAGE   = 3.450
FLOAT_CELL_VOLTAGE = 3.450

; --------- 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 = True

; --------- 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 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
;                      it switches back to max voltage.
; Example: 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 90%
;          OR
;          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 300 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 90%.
; 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 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)
; Specify how long the max voltage should be kept, if reached then switch to float voltage
MAX_VOLTAGE_TIME_SEC = 900
; Specify SoC where CVL limit is reset to max voltage, if value gets below
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 95


; --------- 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.45, 3.43, 3.40, 3.35, 3.30
MAX_CHARGE_CURRENT_CV_FRACTION =    0,   0.02,   0.05,   1,   1

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


; --------- 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
TEMPERATURE_LIMITS_WHILE_CHARGING = 0,   2,   5,  10,  15, 20, 35,  40, 55
MAX_CHARGE_CURRENT_T_FRACTION     = 0, 0.1, 0.2, 0.4, 0.8,  1,  1, 0.4,  0

TEMPERATURE_LIMITS_WHILE_DISCHARGING = -20,   0,   5,  10, 15, 45, 55
MAX_DISCHARGE_CURRENT_T_FRACTION     =   0, 0.2, 0.3, 0.4,  1,  1,  0


; --------- SOC limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be increased / decreased depending on State of Charge,
; 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

; Charge current soc limits
CC_SOC_LIMIT1 = 98
CC_SOC_LIMIT2 = 95
CC_SOC_LIMIT3 = 91

; Charge current limits
CC_CURRENT_LIMIT1_FRACTION = 0.1
CC_CURRENT_LIMIT2_FRACTION = 0.3
CC_CURRENT_LIMIT3_FRACTION = 0.5

; Discharge current soc limits
DC_SOC_LIMIT1 = 10
DC_SOC_LIMIT2 = 20
DC_SOC_LIMIT3 = 30

; Discharge current limits
DC_CURRENT_LIMIT1_FRACTION = 0.1
DC_CURRENT_LIMIT2_FRACTION = 0.3
DC_CURRENT_LIMIT3_FRACTION = 0.5


; --------- 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 d h m s
; 3 Both seconds and time string " [d h m s]"
TIME_TO_SOC_VALUE_TYPE = 2
; 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 only one BMS type 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:
; https://louisvdw.github.io/dbus-serialbattery/general/install#how-to-enable-a-disabled-bms

Relevant log output


root@raspberrypi4:~# tail -F -n 100 /data/log/dbus-serialbattery.ttyACM0/current | tai64nlocal
2023-09-16 16:27:55.584967500 INFO:SerialBattery:Connection established to LltJbd
2023-09-16 16:27:55.584972500 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
2023-09-16 16:27:55.584975500 INFO:SerialBattery:========== Settings ==========
2023-09-16 16:27:55.584978500 INFO:SerialBattery:> Connection voltage: 62.02V | Current: 4.2A | SoC: 99.94%
2023-09-16 16:27:55.584982500 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
2023-09-16 16:27:55.584985500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2023-09-16 16:27:55.585051500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A
2023-09-16 16:27:55.585056500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 200.0A | MAX BATTERY DISCHARGE CURRENT: 200.0A (read from BMS)
2023-09-16 16:27:55.585060500 INFO:SerialBattery:> CVCM:     True
2023-09-16 16:27:55.585111500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2023-09-16 16:27:55.585314500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2023-09-16 16:27:55.585588500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-09-16 16:27:55.585851500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2023-09-16 16:27:55.619346500 INFO:SerialBattery:DeviceInstance = 1
2023-09-16 16:27:55.619351500 INFO:SerialBattery:com.victronenergy.battery.ttyACM0
2023-09-16 16:27:56.012450500 INFO:SerialBattery:publish config values = 1
2023-09-16 16:53:27.259951500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-16 16:53:27.260535500 INFO:SerialBattery:dbus-serialbattery v1.0.20230531
2023-09-16 16:53:27.260823500 INFO:SerialBattery:Testing Daly
2023-09-16 16:53:27.393185500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:27.393555500 INFO:SerialBattery:Testing Daly
2023-09-16 16:53:27.523495500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:27.523953500 INFO:SerialBattery:Testing Ecs
2023-09-16 16:53:27.589869500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:27.589874500 INFO:SerialBattery:Testing HeltecModbus
2023-09-16 16:53:28.104136500 WARNING:SerialBattery:Error reading settings from BMS, retry (1/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:28.517554500 WARNING:SerialBattery:Error reading settings from BMS, retry (2/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:28.929863500 WARNING:SerialBattery:Error reading settings from BMS, retry (3/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:29.344372500 WARNING:SerialBattery:Error reading settings from BMS, retry (4/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:29.755029500 WARNING:SerialBattery:Error reading settings from BMS, retry (5/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:30.168021500 WARNING:SerialBattery:Error reading settings from BMS, retry (6/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:30.577120500 WARNING:SerialBattery:Error reading settings from BMS, retry (7/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:30.988794500 WARNING:SerialBattery:Error reading settings from BMS, retry (8/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:31.402620500 WARNING:SerialBattery:Error reading settings from BMS, retry (9/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:31.810489500 WARNING:SerialBattery:Error reading settings from BMS, retry (10/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-16 16:53:31.810787500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-09-16 16:53:36.324209500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:36.324493500 INFO:SerialBattery:Testing Jkbms
2023-09-16 16:53:36.597123500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:36.602836500 INFO:SerialBattery:Testing Lifepower
2023-09-16 16:53:36.879485500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-16 16:53:36.884701500 INFO:SerialBattery:Testing LltJbd
2023-09-16 16:53:37.618837500 INFO:SerialBattery:Connection established to LltJbd
2023-09-16 16:53:37.619131500 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
2023-09-16 16:53:37.619390500 INFO:SerialBattery:========== Settings ==========
2023-09-16 16:53:37.619687500 INFO:SerialBattery:> Connection voltage: 60.96V | Current: 2.63A | SoC: 99.65%
2023-09-16 16:53:37.619942500 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
2023-09-16 16:53:37.620210500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2023-09-16 16:53:37.620484500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A
2023-09-16 16:53:37.620753500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 200.0A | MAX BATTERY DISCHARGE CURRENT: 200.0A (read from BMS)
2023-09-16 16:53:37.621002500 INFO:SerialBattery:> CVCM:     True
2023-09-16 16:53:37.621277500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2023-09-16 16:53:37.621539500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2023-09-16 16:53:37.621799500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-09-16 16:53:37.622063500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2023-09-16 16:53:37.659004500 INFO:SerialBattery:DeviceInstance = 1
2023-09-16 16:53:37.659539500 INFO:SerialBattery:com.victronenergy.battery.ttyACM0
2023-09-16 16:53:38.065192500 INFO:SerialBattery:publish config values = 1
2023-09-17 11:11:35.062177500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-17 11:11:35.062752500 INFO:SerialBattery:dbus-serialbattery v1.0.20230531
2023-09-17 11:11:35.063031500 INFO:SerialBattery:Testing Daly
2023-09-17 11:11:35.194515500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:35.194835500 INFO:SerialBattery:Testing Daly
2023-09-17 11:11:35.323688500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:35.323970500 INFO:SerialBattery:Testing Ecs
2023-09-17 11:11:35.384895500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:35.385856500 INFO:SerialBattery:Testing HeltecModbus
2023-09-17 11:11:35.898199500 WARNING:SerialBattery:Error reading settings from BMS, retry (1/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:36.308385500 WARNING:SerialBattery:Error reading settings from BMS, retry (2/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:36.717879500 WARNING:SerialBattery:Error reading settings from BMS, retry (3/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:37.128419500 WARNING:SerialBattery:Error reading settings from BMS, retry (4/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:37.539914500 WARNING:SerialBattery:Error reading settings from BMS, retry (5/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:37.950015500 WARNING:SerialBattery:Error reading settings from BMS, retry (6/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:38.363453500 WARNING:SerialBattery:Error reading settings from BMS, retry (7/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:38.771875500 WARNING:SerialBattery:Error reading settings from BMS, retry (8/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:39.182000500 WARNING:SerialBattery:Error reading settings from BMS, retry (9/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:39.591710500 WARNING:SerialBattery:Error reading settings from BMS, retry (10/10): Checksum error in rtu mode: '\x12a' instead of 'a\x91' . The response is: '\x01\x01\x03\x12a' (plain response: '\x01\x01\x03\x12a')
2023-09-17 11:11:39.592009500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-09-17 11:11:44.105624500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:44.105963500 INFO:SerialBattery:Testing Jkbms
2023-09-17 11:11:44.386833500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:44.396703500 INFO:SerialBattery:Testing Lifepower
2023-09-17 11:11:44.674326500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-09-17 11:11:44.679673500 INFO:SerialBattery:Testing LltJbd
2023-09-17 11:11:45.415823500 INFO:SerialBattery:Connection established to LltJbd
2023-09-17 11:11:45.416296500 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
2023-09-17 11:11:45.416592500 INFO:SerialBattery:========== Settings ==========
2023-09-17 11:11:45.417150500 INFO:SerialBattery:> Connection voltage: 62.51V | Current: 14.04A | SoC: 100.0%
2023-09-17 11:11:45.417590500 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
2023-09-17 11:11:45.417975500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2023-09-17 11:11:45.418309500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A
2023-09-17 11:11:45.418890500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 200.0A | MAX BATTERY DISCHARGE CURRENT: 200.0A (read from BMS)
2023-09-17 11:11:45.419236500 INFO:SerialBattery:> CVCM:     True
2023-09-17 11:11:45.419806500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2023-09-17 11:11:45.420132500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2023-09-17 11:11:45.420564500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-09-17 11:11:45.420891500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2023-09-17 11:11:45.463635500 INFO:SerialBattery:DeviceInstance = 1
2023-09-17 11:11:45.464961500 INFO:SerialBattery:com.victronenergy.battery.ttyACM0
2023-09-17 11:11:45.864090500 INFO:SerialBattery:publish config values = 1



### Any other information that may be helpful

_No response_



victron products
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

0 Answers

Related Resources

Additional resources still need to be added for this topic