JBD BMS - SoC value is not correct

[stixif]

Describe the bug

the BMS Shows 100% on Both (LltJbd)
the VenusOS 96% and 100%

How to reproduce

?

Expected behavior

correct SoC

Driver version of the currently installed driver

v1.3.20240705dev

Driver version of the last known working driver

No response

Venus OS device type

Raspberry Pi 4

Venus OS version

v3.34

BMS type

Jiabaida JDB BMS (LLT Power, Overkill Solar, Smart BMS)

Cell count

18

Battery count

2

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

CUSTOM_BATTERY_NAMES = /dev/ttyACM0:BattPack1,/dev/ttyACM1:BattPack2

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


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

Relevant log output

NR1
@40000000668917ad2b811f84 INFO:SerialBattery:Starting dbus-serialbattery
@40000000668917ad2b983d7c INFO:SerialBattery:Venus OS v3.34
@40000000668917ad2b9e9e4c INFO:SerialBattery:dbus-serialbattery v1.3.20240705dev
@40000000668917bd2c113254 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@40000000668917bd2c18334c INFO:SerialBattery:Testing LltJbd
@40000000668917be2509f0f4 INFO:SerialBattery:Connection established to LltJbd
@40000000668917bf18627844 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@40000000668917bf2b2db7f4 INFO:SerialBattery:DeviceInstance = 1
@40000000668917bf2b3ef9ec INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
@40000000668917bf2b47374c INFO:SerialBattery:Used DeviceInstances = ['3', '1']
@40000000668917bf2b4e9604 INFO:SerialBattery:com.victronenergy.battery.ttyACM1
@40000000668917c0126651cc INFO:SerialBattery:publish config values = False
@40000000668917c0127b0e64 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM1
@40000000668917c012913e14 INFO:SerialBattery:========== Settings ==========
@40000000668917c012baf9ac INFO:SerialBattery:> Connection voltage: 61.85 V | Current: 3.26 A | SoC: 96.44%
@40000000668917c012bb20bc INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@40000000668917c012c365ec INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@40000000668917c012cd127c INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
@40000000668917c012d8f574 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 130.0 A | MAX BATTERY DISCHARGE CURRENT: 130.0 A
@40000000668917c012e29a34 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0 A | MAX BATTERY DISCHARGE CURRENT: 190.0 A (read from BMS)
@40000000668917c012f9a0bc INFO:SerialBattery:> CVCM:     True
@40000000668917c01319e28c INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@40000000668917c0132515bc INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@40000000668917c0132db8ac INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@40000000668917c013361934 INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: True | BALANCE FET: True
@40000000668917c01348babc INFO:SerialBattery:Serial Number/Unique Identifier: 40_280.0Ah


NR2
@40000000668917ac234c27dc INFO:SerialBattery:Starting dbus-serialbattery
@40000000668917ac23665ecc INFO:SerialBattery:Venus OS v3.34
@40000000668917ac23707ca4 INFO:SerialBattery:dbus-serialbattery v1.3.20240705dev
@40000000668917bc248fbfb4 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@40000000668917bc248fdef4 INFO:SerialBattery:Testing LltJbd
@40000000668917bd1c03034c INFO:SerialBattery:Connection established to LltJbd
@40000000668917be008dab94 INFO:SerialBattery:Found existing battery with DeviceInstance = 3
@40000000668917be1a770834 INFO:SerialBattery:DeviceInstance = 3
@40000000668917be1a8d89ec INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_3.pid
@40000000668917be1a980584 INFO:SerialBattery:Used DeviceInstances = ['3', '1']
@40000000668917be1aa0101c INFO:SerialBattery:com.victronenergy.battery.ttyACM0
@40000000668917bf007f0594 INFO:SerialBattery:publish config values = False
@40000000668917bf0097cd54 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM0
@40000000668917bf009f8db4 INFO:SerialBattery:========== Settings ==========
@40000000668917bf00a86b3c INFO:SerialBattery:> Connection voltage: 61.86 V | Current: 3.58 A | SoC: 99.5%
@40000000668917bf00af7bd4 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@40000000668917bf00b62ac4 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@40000000668917bf00bd81ac INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
@40000000668917bf00c46f1c INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 130.0 A | MAX BATTERY DISCHARGE CURRENT: 130.0 A
@40000000668917bf00cbd98c INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0 A | MAX BATTERY DISCHARGE CURRENT: 190.0 A (read from BMS)
@40000000668917bf00d2e63c INFO:SerialBattery:> CVCM:     True
@40000000668917bf00da6c04 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@40000000668917bf00e14dbc INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@40000000668917bf00f3acdc INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@40000000668917bf00f3c834 INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: True | BALANCE FET: True
@40000000668917bf00fb7124 INFO:SerialBattery:Serial Number/Unique Identifier: 40_279.9Ah

Any other information that may be helpful

what can i do to become the soc value from the BMS

[mr-manuel]

The driver can only get, what the BMS is sending. Have you the same problem with other stable releases?

[stixif]

yes in all versions...
the BMS App shows 100% for both Packs

but in VenusOS i geht 96 and 100...

[stixif]

hi Manuel,
I got something...
JBD communication protocol new-RS485,RS232,UART.pdf

i hope it helps...

[mr-manuel]

I found something: Louisvdw#769 (comment)

Can you check that values on your end?

Please also install the latest nightly. If you already have it installed, please reinstall it. Then post fresh logs here, they should contain some important values to understand the problem.

[stixif]

yes here the same... i have total capacity and cycle capacity.
Bat1
total capacity = 280
cycle capacity = 260
current1.txt

Bat2
total capacity = 279,9
cycle capacity = 260
current2.txt

From the Log...
INFO:SerialBattery:soc: 69 - self.soc: 66.87
soc is the same like the BMS APP

[mr-manuel]

@idstein do you know maybe, why the cycle capacity was used and not the total capacity?

Strange, that the app also do not use the cycle capacity, since with time and degradation the total capacity gets less.

@stixif install the latest nightly, I changed it to test in the meanwhile.

[stixif]

now it works...

but batpack1 is 90% in VenusOS and on the BMS 100%
but the consumed AmpHours are 28Ah

and batpack2 is 100% in VenusOS and BMS
consumed AmpHours 0Ah

but if i disconnect batpack2 it will not load batpack1

@400000006693f6ff05792174 *** CCGX booted (0) ***
@400000006693f7182d3f6d6c INFO:SerialBattery:
@400000006693f7182d48e734 INFO:SerialBattery:Starting dbus-serialbattery
@400000006693f7182d625ebc INFO:SerialBattery:Venus OS v3.34
@400000006693f7182d736234 INFO:SerialBattery:dbus-serialbattery v1.4.20240714dev
@400000006693f72b0bcd4b2c INFO:SerialBattery:
@400000006693f72b0bd7caac INFO:SerialBattery:Starting dbus-serialbattery
@400000006693f72b0d3e6b44 INFO:SerialBattery:Venus OS v3.34
@400000006693f72b0d3e82b4 INFO:SerialBattery:dbus-serialbattery v1.4.20240714dev
@400000006693f74a1a41179c INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@400000006693f74a1a4c42fc INFO:SerialBattery:Testing LltJbd
@400000006693f74b143e655c INFO:SerialBattery:Connection established to LltJbd
@400000006693f74e0210bd6c INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@400000006693f74f26f7c2ec INFO:SerialBattery:DeviceInstance = 1
@400000006693f74f271034bc INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
@400000006693f74f271af2bc INFO:SerialBattery:Used DeviceInstances = ['3', '1', '2']
@400000006693f74f2724d5fc INFO:SerialBattery:com.victronenergy.battery.ttyACM1
@400000006693f7501766de1c INFO:SerialBattery:publish config values = False
@400000006693f7501ad8e6e4 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyACM1
@400000006693f7501ae3f6ec INFO:SerialBattery:========== Settings ==========
@400000006693f7501aed2a64 INFO:SerialBattery:> Connection voltage: 62.66 V | Current: 0.0 A | SoC: 89.97%
@400000006693f7501af55824 INFO:SerialBattery:> Cell count: 18 | Cells populated: 18
@400000006693f7501dd77144 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@400000006693f7501de3cd54 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.870 V | MAX CELL VOLTAGE: 3.475 V| FLOAT CELL VOLTAGE: 3.410 V
@400000006693f7501dee73e4 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 130.0 A | MAX BATTERY DISCHARGE CURRENT: 130.0 A
@400000006693f7501e70d6cc INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 190.0 A | MAX BATTERY DISCHARGE CURRENT: 190.0 A (read from BMS)
@400000006693f7501e7c34f4 INFO:SerialBattery:> CVCM:     True
@400000006693f7501e86338c INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@400000006693f7502039c374 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@400000006693f750204596cc INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@400000006693f75020502dbc INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: True | BALANCE FET: True
@400000006693f750205baf0c INFO:SerialBattery:Serial Number/Unique Identifier: 40_280.0Ah

[mr-manuel]

Consumed Amp hours in the app or the driver?

[stixif]

in the driver...
but it looks like the same in the App (280AH - Remaining 252AH)

[mr-manuel]

The driver uses the consumed amp hours to have a higher resolution on the SOC. Maybe there is a wrong setting in your BMS? You could try a factory reset of the BMS and see the results.

If the battery is full, is the remaining capacity same as the capacity or the cycle capacity?

I add again the logging, so we see whats happening.

[mr-manuel]

@stixif can you install from the troubleshooting-llt-jbs-soc branch and provide fresh logs?

See Install a specific branch if you don't know how to install a specific branch.

[stixif]

@mr-manuel i do...

i download it...
https://github.com/mr-manuel/venus-os_dbus-serialbattery/archive/refs/heads/troubleshooting-llt-jbs-soc.tar.gz

and rename it and copy to "/var/volatile/tmp/venus-data.tar.gz"

and install with option 8 of the script

current2.txt
current1.txt

[mr-manuel]

From the logfiles the version was not installed somehow. Could you write me on Discord so that I could check your system?

[stixif]

@mr-manuel
??? what is discord... i dont know sorry
or can you tell me how i can install your version?

[mr-manuel]

See Install a specific branch if you don't know how to install a specific branch.

try this

[stixif]

@mr-manuel
sorry...
now I got it! ;)
(i create the venus-data.tar.gz by myself... i never done this before...)
current2.txt
current1.txt

[mr-manuel]

current1:

INFO:SerialBattery:soc (BMS): 99 - self.soc (calc): 99.5 - soc_2 (calc): 107.12 - capacity: 27990 - self.cycle_capacity: 26000.0 - capacity_remain: 27850

current2:

INFO:SerialBattery:soc (BMS): 100 - self.soc (calc): 89.55 - soc_2 (calc): 96.44 - capacity: 28000 - self.cycle_capacity: 26000.0 - capacity_remain: 25075

soc: comes directly from the BMS
self.soc: round(100 * capacity_remain / capacity, 2)
soc_2: round(100 * capacity_remain / self.cycle_capacity, 2)
capacity: comes directly from the BMS
self.cycle_capacity: comes directly from the BMS
capacity_remain: comes directly from the BMS

So the problem here is, that your BMS shows inconsistent data. The SOC is 100%, but the remaining capacity has not reached at least the cycle_capacity in the second case. In the fist case, it's even exceeding this value.

Please ask your seller why that is the case and why this values don't match. Maybe it's a settings issue.

[mr-manuel]

SOC is set to BMS SOC with a7b0c4b.

[stixif]

@mr-manuel
thanks a lot... i will ask...

now i installed the newest snapshot...
but it hangs in the first few minutes the first batpack after a few minutes all works well...

[stixif]

here 2 logs on the time it stucks
@40000000669ac346222b1fac.txt
@40000000669ac3290e9dbcc4.txt

[mr-manuel]

Since this is a different problem open a new issue and provide correct logs. Check the documentation on how to provide correct logs. For this issue the timings were not needed, but for your current problem they are.