JKBMS 11.XW over Bluetooth no MOSFET Temp

[sstolk90]

Describe the bug

I use the nightly build DEV branch with both JK BMS'ses on bluetooth. So far they connect good and all the values are displayed. Exccept for the MOSFET Temp of one of the newer JK BMS'ses. I have 1 BMS with firmware version 10.XW 16 cells and 1 with firmware version 11.XW. The one with 11.ZW does display the MOSFET temp in the JKBMS app but not in this driver. The MOSFET temp of the 10.XW is displayed in the app and also this driver. Maybe the driver gets the information of the 11.XW on a different scheme so that the values are misplaced.

How to reproduce

Always not displayed

Expected behavior

MOSFET Temp not 0 degrees in the Remote Console / MQTT values

Driver version

1.0.20230613dev

Venus OS device type

Venus_GX

Venus OS version

2.92

BMS type

JKBMS / Heltec BMS

Cell count

16

Connection type

Bluetooth

Config file

[DEFAULT]

; If you want to add custom values/settings, then check the values/settings you want to change in "config.default.ini"
; and insert them below to persist future driver updates.

; Example (remove the semicolon ";" to uncomment and activate the value/setting):
; Jkbms_Ble C8:47:8C:E5:01:1B
MAX_BATTERY_CHARGE_CURRENT = 100.0
MAX_BATTERY_DISCHARGE_CURRENT = 100.0

BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:EC:C0:B5, Jkbms_Ble C8:47:8C:E5:01:1B
BLOCK_ON_DISCONNECT = False
TIME_TO_GO_ENABLE = True

BMS_TYPE = Jkbms

; CUSTOM_BATTERY_NAMES = c8478ce5011b:Batterij Onder

; Max voltage can seen as absorption voltage
MAX_CELL_VOLTAGE   = 3.555
FLOAT_CELL_VOLTAGE = 3.535

; 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.56, 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

Relevant log output

==> /data/log/dbus-blebattery.0/current <==
2023-06-16 10:20:46.092590500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2023-06-16 10:20:46.092603500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2023-06-16 10:20:46.092606500 INFO:SerialBattery:Serial Number/Unique Identifier: 2120146523
2023-06-16 10:20:46.264484500 INFO:SerialBattery:DeviceInstance = 4
2023-06-16 10:20:46.266055500 INFO:SerialBattery:com.victronenergy.battery.c8478cecc0b5
2023-06-16 10:20:46.272138500 INFO:SerialBattery:BAT: JKBMS 11.XW 16 cells (20230504)
2023-06-16 10:20:46.350782500 INFO:SerialBattery:publish config values = 1
2023-06-16 10:25:30.836464500 [CHG] Device C8:47:8C:EC:C0:B5 RSSI: -50
2023-06-16 10:25:30.836476500 [CHG] Device C8:47:8C:EC:C0:B5 RSSI: -50

==> /data/log/dbus-blebattery.1/current <==
2023-06-16 10:20:45.454636500 INFO:SerialBattery:Serial Number/Unique Identifier: 2052302250
2023-06-16 10:20:45.506025500 INFO:SerialBattery:DeviceInstance = 5
2023-06-16 10:20:45.506767500 INFO:SerialBattery:com.victronenergy.battery.c8478ce5011b
2023-06-16 10:20:45.507499500 INFO:SerialBattery:BAT: JKBMS 10.XW 16 cells (20221223)
2023-06-16 10:20:45.533133500 INFO:SerialBattery:publish config values = 1

Any other information that may be helpful

No response

[rver2024]

Hi @mr-manuel, has this fix been committed to the latest release in the main branch? I lost track of it since I accidentally damage my JKBMS, I since bought a new one, exactly the same one from JK, installed the latest driver by selecting option 1, but the “MOSFET temperature” is still showing 0. I tried to modify the jkbms_brn.py the way you told me before, but I couldn’t find the line with code “ if fb[70] == 255 and fb[71] == 255: ” anymore. Any inside on how the fix the issue? My new JKBMS is also a 8-cell with 11.XW hardware version, exactly the same as my old BMS. Thank you very much!

[mr-manuel]

Install the latest nightly of the dev branch.

[rver2024]

Install the latest nightly of the dev branch.

Yep, the latest dev version of the nightly works. Thanks!