search

Louisvdw / dbus-serialbattery

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

JK BMS - SoC daily decreasing by 2% #703

Closed Dighy closed 1 year ago

Dighy commented 1 year ago

Describe the problem

Hello everybody,

I would like to start telling that I'm just beginer and I'm following all the instruction provided. I was replacing my old battery with 24V/280Ah lifepo4 battery monitored by JK Bms (2A8S20P) in a Victron Easy solar 24/3000 with CCGX system. Initially I let it running by setting only the VE Bus System (multiplus) and Solar charger (70A/150V type) with settings like CVL-27.2V and CCL - 50A and I checked the battery behavior at high discharge rate (120A). Everything fine Soc was going from 100% to 99%(float mode) and 68-74% in the morning as per consumption. After few days, I installed the driver version [v1.0.20230508beta] with every setting from default, I set JK-BMS serial battery as master (external control) and behavior was the same like without driver from SoC calculation point of view. Once the latest version was released [v1.0.20230531], I update it by USB in my CCGX and updated the value of CCL to 70A and DCL to 100A through SSL client Putty and reboot the GX. That I noticed is that in the first 2 days SoC was not going to 100% and only to 99% and after that every day maximum was 2% less compare with previous day (eq. 97%-95%-93%......) and now I reached 89% and as per logic CVL is going to 27.6V, then reduced to 27V (float) and after increasing again to 27.6V due to the SoC < 90%. Today, I came back to CCL - 50A and all the others the same as before to see what is going on... I would be so greatful for any support on what is the issue and how to correct it.

Thanks.

Driver version

v1.0.20230531

Venus OS device type

CCGX

Venus OS version

2.94

BMS type

JKBMS / Heltec BMS

Cell count

8

Connection type

Serial USB adapter to RS485

Config file

[DEFAULT]

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 70.0
MAX_BATTERY_DISCHARGE_CURRENT = 100.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.375

; --------- Bluetooth BMS ---------
; Description: List the Bluetooth BMS here that you want to install
; Example with 1 BMS: Jkbms_Ble C8:47:8C:00:00:00
; Example with 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 = 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 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.050V
; 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 = 90

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

; --------- 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,
;              see CC_SOC_LIMIT1 etc.
; Example: The SoC limit will be monitored to control the currents.
; Charge current control management enable (True/False).
CCCM_SOC_ENABLE = True
; Discharge current control management enable (True/False).
DCCM_SOC_ENABLE = True

; 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 <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 only one BMS type to load else leave empty to try to load all availabe
; LltJbd, Ant, Daly, Daly, Jkbms, Lifepower, Renogy, Renogy, Ecs
BMS_TYPE =

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

; 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
; Specifiy how the battery temperature is assembled
; 0 Get mean of temperature sensor 1 and temperature sensor 2
; 1 Get only temperature from temperature sensor 1
; 2 Get only temperature from temperature sensor 2
TEMP_BATTERY = 0

; Temperature sensor 1 name
TEMP_1_NAME = Temp 1

; Temperature sensor 2 name
TEMP_2_NAME = Temp 2

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

; -- ESC GreenMeter and Lipro device settings
GREENMETER_ADDRESS  = 1
LIPRO_START_ADDRESS = 2
LIPRO_END_ADDRESS   = 4
LIPRO_CELL_COUNT = 15
Footer
© 2023 GitHub, Inc.
Footer navigation
Terms
Priv

Relevant log output

root@ccgx:~# tail -F -n 100 /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal
2023-06-10 14:05:00.418178500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:00.421230500 INFO:SerialBattery:Testing Ecs
2023-06-10 14:05:00.680324500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:00.682613500 INFO:SerialBattery:Testing HeltecModbus
2023-06-10 14:05:05.664882500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:05.666927500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-06-10 14:05:10.243922500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:10.260524500 INFO:SerialBattery:Testing Jkbms
2023-06-10 14:05:10.622829500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:10.656490500 INFO:SerialBattery:Testing Lifepower
2023-06-10 14:05:11.034053500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:11.049800500 INFO:SerialBattery:Testing LltJbd
2023-06-10 14:05:11.470241500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:11.539241500 INFO:SerialBattery:Testing Renogy
2023-06-10 14:05:11.907924500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:11.956294500 INFO:SerialBattery:Testing Renogy
2023-06-10 14:05:12.359554500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:12.409389500 INFO:SerialBattery:Testing Seplos
2023-06-10 14:05:13.498134500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:14.001186500 INFO:SerialBattery:Testing Daly
2023-06-10 14:05:14.174892500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:14.177150500 INFO:SerialBattery:Testing Daly
2023-06-10 14:05:14.358791500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:14.361598500 INFO:SerialBattery:Testing Ecs
2023-06-10 14:05:14.927333500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:14.938899500 INFO:SerialBattery:Testing HeltecModbus
2023-06-10 14:05:19.480098500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:19.491206500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-06-10 14:05:24.056239500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-10 14:05:24.058070500 INFO:SerialBattery:Testing Jkbms
2023-06-10 14:05:24.272273500 INFO:SerialBattery:Connection established to Jkbms
2023-06-10 14:05:24.313045500 INFO:SerialBattery:Battery Jkbms connected to dbus from /dev/ttyUSB0
2023-06-10 14:05:24.317409500 INFO:SerialBattery:========== Settings ==========
2023-06-10 14:05:24.339809500 INFO:SerialBattery:> Connection voltage: 27.49V | Current: 6.23A | SoC: 89%
2023-06-10 14:05:24.348689500 INFO:SerialBattery:> Cell count: 8 | Cells populated: 0
2023-06-10 14:05:24.365962500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2023-06-10 14:05:24.370631500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 70.0A | MAX BATTERY DISCHARGE CURRENT: 100.0A
2023-06-10 14:05:24.397823500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 75.0A | MAX BATTERY DISCHARGE CURRENT: 140.0A (read from BMS)
2023-06-10 14:05:24.419063500 INFO:SerialBattery:> CVCM:     True
2023-06-10 14:05:24.422176500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2023-06-10 14:05:24.432216500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2023-06-10 14:05:24.450465500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-06-10 14:05:24.455104500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2023-06-10 14:05:24.465389500 INFO:SerialBattery:Serial Number/Unique Identifier: Ghy Baterie 7.2K
2023-06-10 14:05:25.073299500 INFO:SerialBattery:DeviceInstance = 1
2023-06-10 14:05:25.075984500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
2023-06-10 14:05:25.560512500 INFO:SerialBattery:publish config values = 1
2023-06-11 05:52:48.388214500 *** CCGX booted (1) ***
2023-06-11 05:54:15.352873500 INFO:SerialBattery:Starting dbus-serialbattery
2023-06-11 05:54:15.389372500 INFO:SerialBattery:dbus-serialbattery v1.0.20230531
2023-06-11 05:54:15.437346500 INFO:SerialBattery:Testing Daly
2023-06-11 05:54:15.668394500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:15.674437500 INFO:SerialBattery:Testing Daly
2023-06-11 05:54:15.885802500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:15.887633500 INFO:SerialBattery:Testing Ecs
2023-06-11 05:54:16.112791500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:16.114470500 INFO:SerialBattery:Testing HeltecModbus
2023-06-11 05:54:20.990416500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:20.992216500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-06-11 05:54:25.631865500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:25.634154500 INFO:SerialBattery:Testing Jkbms
2023-06-11 05:54:26.070250500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:26.085905500 INFO:SerialBattery:Testing Lifepower
2023-06-11 05:54:26.521666500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:26.553496500 INFO:SerialBattery:Testing LltJbd
2023-06-11 05:54:26.980406500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:27.007841500 INFO:SerialBattery:Testing Renogy
2023-06-11 05:54:27.423674500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:27.455473500 INFO:SerialBattery:Testing Renogy
2023-06-11 05:54:27.948149500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:27.986388500 INFO:SerialBattery:Testing Seplos
2023-06-11 05:54:29.104338500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:29.607481500 INFO:SerialBattery:Testing Daly
2023-06-11 05:54:29.789763500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:29.791533500 INFO:SerialBattery:Testing Daly
2023-06-11 05:54:29.987914500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:29.989622500 INFO:SerialBattery:Testing Ecs
2023-06-11 05:54:30.519377500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:30.544188500 INFO:SerialBattery:Testing HeltecModbus
2023-06-11 05:54:35.136473500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:35.149535500 INFO:SerialBattery:Testing HLPdataBMS4S
2023-06-11 05:54:39.718108500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2023-06-11 05:54:39.794737500 INFO:SerialBattery:Testing Jkbms
2023-06-11 05:54:40.544066500 INFO:SerialBattery:Connection established to Jkbms
2023-06-11 05:54:40.615324500 INFO:SerialBattery:Battery Jkbms connected to dbus from /dev/ttyUSB0
2023-06-11 05:54:40.735716500 INFO:SerialBattery:========== Settings ==========
2023-06-11 05:54:40.862151500 INFO:SerialBattery:> Connection voltage: 26.92V | Current: 10.51A | SoC: 83%
2023-06-11 05:54:40.864012500 INFO:SerialBattery:> Cell count: 8 | Cells populated: 0
2023-06-11 05:54:40.993437500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2023-06-11 05:54:40.995360500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 50.0A | MAX BATTERY DISCHARGE CURRENT: 100.0A
2023-06-11 05:54:41.124907500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 75.0A | MAX BATTERY DISCHARGE CURRENT: 140.0A (read from BMS)
2023-06-11 05:54:41.235411500 INFO:SerialBattery:> CVCM:     True
2023-06-11 05:54:41.307494500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2023-06-11 05:54:41.400694500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2023-06-11 05:54:41.476469500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-06-11 05:54:41.613432500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2023-06-11 05:54:41.676390500 INFO:SerialBattery:Serial Number/Unique Identifier: Ghy Baterie 7.2K
2023-06-11 05:54:42.644408500 INFO:SerialBattery:DeviceInstance = 1
2023-06-11 05:54:42.659331500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
2023-06-11 05:54:43.215483500 INFO:SerialBattery:publish config values = 1

Any other information that may be helpful

No response

joseal commented 1 year ago

Hi @mr-manuel,

I'm sorry, you were more than right... I had a wrong understanding of this feature (I had the impression that you were temporarely adjusting the OVP), reason why I was so lost....

After review with more calm all the thread and look at the source, now I've a much better understanding of the issue and the challanages behind it.

I can confirm that the feature works just fine (still need to do some fine tuning, to find the best values for me, but it is working):

image

It's not so good as being able to play with the OVP value, but it is good workaround!

Thanks again for the good work and patience.

mr-manuel commented 1 year ago

I'm sorry, you were more than right... I had a wrong understanding of this feature (I had the impression that you were temporarely adjusting the OVP), reason why I was so lost....

Unfortunately this is not possible via serial connection. I also wrote with the JKBMS developers and they were not really cooperative. They just told me that it's not possible via serial connection. With the Bluetooth connection it works without problems.

Neverthless, the workaround works for all BMS where you cannot reset the SOC via software.

Pengo84 commented 1 year ago

Hello mr-manuel, does it mean when I connect via Bluetooth the JK-Bms with VenusOS the SoC will be set right when the voltage of 3.45V is reached?

mr-manuel commented 1 year ago

The SoC of the JKBMS connected via Bluetooth will set to 100% when switching to float mode. PR is still open: https://github.com/Louisvdw/dbus-serialbattery/pull/736

Pengo84 commented 1 year ago

Do I have to set anything for this or is everything already set automatically?

mr-manuel commented 1 year ago

As soon as it is merged with the dev branch I will post an instruction here.

Valdiralita commented 1 year ago

Ive tested the dev version the previous days and it works really well. Im using the following settings:

OVP: 3,6V OVPR 3.55V MIN_CELL_VOLTAGE = 2.750 MAX_CELL_VOLTAGE = 3.450 FLOAT_CELL_VOLTAGE = 3.375 BULK_CELL_VOLTAGE = 3.601 BULK_AFTER_DAYS = 1

I'll continue using the dev branch until this is merged.

Pengo84 commented 1 year ago

Hello, another question about this marked value, what is it and what is it good for?

Bildschirmfoto 2023-07-23 um 15 09 10
mr-manuel commented 1 year ago

Hello, another question about this marked value, what is it and what is it good for?

https://github.com/Louisvdw/dbus-serialbattery/blob/a24d6ef458239a1bc70399f774ae71348e48bf9d/etc/dbus-serialbattery/config.default.ini#L290-L302

Joeknx commented 1 year ago

Thanks for the bulk voltage hack. It works with the JKBMS, bulk (3,535) slightly under OPV (3,54). I have Grade A LF280K from EVE and they stay very balanced.

Some questions/suggestions: Can the tDiff be changed? 900 is pretty long for bulk. When i "reinstall local" to start the bulk voltage for testing, the battery is charged with full speed (in my case 70A). 5A or so would be better in my opinion.

mr-manuel commented 1 year ago

If you are using the latest nightly from the dev branch, then MAX_VOLTAGE_TIME_SEC is used.

maxx8888 commented 1 year ago

I'm not sure if i understand this Solution correctly. Basically it means i need to run Batteries into OverVoltageProject from BMS every few days? Or just short before disconnect? How is this working on multiple Batteries? Aggregate Batteries will run all of them up until they disconnect? If the Packs do not align, Pack1 would make reset on Day1, Pack2 reset on Day2 and so on? Worried about Battery life and important disabled Alarm which might stay disabled.

I've exactly this issue on 5x Batteries with JKBMS. What i've tried on one of them is to calibrate BMS on discharge to measure around 0,5 Amps less than what the actual current is. That means during discharging it measures to less and SOC stays higher than it really is. On the next re-charge the BMS hits 100% as the battery still absorbs more than what the BMS is expecting. This seems to work for a few days now... need to monitor. This Solution might also make troubles when Batteries get empty before SOC shows that...