Is anyone using the new style JK inverter BMS with dbus-serialbattery driver? #969

NorthTown2022 · 2024-02-12T02:00:30Z

NorthTown2022
Feb 12, 2024

I would love to be able to use the features and functionality of the new inverter style BMS with the dbus-serialbattery driver.

Has anyone made this work?

patatman · 2024-02-21T07:17:49Z

patatman
Feb 21, 2024

I'm trying to get it to work, but for some reason I don't get any output on the serial port.
I can connect with it fine through the JK BMS app on Windows, but the raspberry PI won't find it using the exact same cable.

2 replies

NorthTown2022 Feb 21, 2024
Author

I've got my hands full right now but hoping to take a closer look at this soon. Please keep me posted!

rolandlueders May 22, 2024

I had a similar problem with an Energy Meter. Did you read the name of your serial to usb converter with FT_Prog? This name has to be in a file.
nano /etc/udev/rules.d/serial-starter.rules
There you see a line like
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="USB-RS485_Cable", ENV{VE_SERVICE}="rs485"
duplikate this line and rename the string
USB-RS485_cable
to the name of your converter.
after restart Venus knows what to do

patatman · 2024-02-24T17:03:10Z

patatman
Feb 24, 2024

So my investigation is a bit further.
I now have 2 Waveshare Industrial USB To RS485 Converter with FT232RL Chip.
1 is connected to windows and the JK software, the other is connected to my laptop with a serial output running. I'm thinking about flashing the firmware again, and make sure it's not the issue. Software version of BMS: 15.10(latest)

If the software is not connected, I get no output. Zero.

When the software connects, I get data from the serial port.

The error I'm getting from dbus-serialbattery is:

2024-02-24 16:59:43.764372500 INFO:SerialBattery:Starting dbus-serialbattery
2024-02-24 16:59:43.766242500 INFO:SerialBattery:dbus-serialbattery v1.0.20230531
2024-02-24 16:59:43.767308500 INFO:SerialBattery:Testing Jkbms
2024-02-24 16:59:44.042956500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-02-24 16:59:44.546023500 INFO:SerialBattery:Testing Jkbms
2024-02-24 16:59:44.821963500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-02-24 16:59:45.326331500 INFO:SerialBattery:Testing Jkbms
2024-02-24 16:59:45.598971500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-02-24 16:59:46.101787500 ERROR:SerialBattery:ERROR >>> No battery connection at /dev/ttyUSB1
2024-02-24 16:59:46.102036500

1 reply

patatman Feb 24, 2024

I see this in the JK software:

NorthTown2022 · 2024-02-25T03:30:48Z

NorthTown2022
Feb 25, 2024
Author

I've been using a JK-B2A20S20P with the serial battery driver on a Cerbo GX, awesome driver!

I made a data cable using the same Waveshare USB to RS485 and powered up my JK-PB2A16S-20PH using a set of temporary cables. I updated the software so I'm at v15.10 as well. I didn't bother to set up any parameters except Uart1 Protocol to 001-JK BMS RS485 Modbus V1.0 (also tried 000-4G-GPS Remote Comm), dip one up and the rest down. No luck here. Pretty much same logs with connection errors.

I was hoping this would be plug and play because I'm pretty sure my coding skills won't get me very far! The new style BMS is far superior to my older one but it will stay boxed up until I can use it with the serialbattery driver.

0 replies

mr-manuel · 2024-02-25T08:41:12Z

mr-manuel
Feb 25, 2024
Collaborator

Anyone asked JKBMS for the protocol documentation? Are there not some communication protocols you can select?

3 replies

NorthTown2022 Feb 25, 2024
Author

Hopefully this is available. I've contacted JK for the documentation but it's the weekend so likely no reply for a day or so. For now, this is a screenshot of the available UART and CAN protocols on the phone app.

patatman Feb 25, 2024

I tried some different ones too, but unfortunately none of them seem to enable the serial communication.
I'm trying to hack together a small python program to see if I can reproduce the commands they are sending from their own software.

I'll try and report back once I have something

patatman Feb 25, 2024

Sorry, didn't have time to work on this. Was stuck working on my Energy meter project.

NorthTown2022 · 2024-03-04T15:41:03Z

NorthTown2022
Mar 4, 2024
Author

I asked JK (Nami) for UART protocol documentation and she got back to me with this:

Origional:
极空BMS RS485 Modbus通用协议V1.0.pdf

My Google translation:
Jikong BMS RS485 Modbus universal protocol V1.0.pdf

0 replies

nsuro · 2024-03-27T01:05:47Z

nsuro
Mar 27, 2024

I have some python code working! I don't use dbus-serialbattery but am trying to get modbus communication working with the JK inverter BMS model JK-PB2A16S20P. Hopfully you will find it useful. The modbus map files posted were a big help. Thank you!!! It was what I was looking for.

You have to connect to one of the two rs485/rj-45 ports on the right. Not the left ones. The left ones are rs485 and CAN for inverter communication. The right side ones are for parallel battery communication and our modbus.

I used orange/white to B, orange to A and green/white to GND on my CH340 USB to RS485 connector. The other end rj-45 crimped with standard T568B.

The dip switches on the comm board are to set the slave address. I don't think they can all be down which would be 0. I think they have to be set to any from 1 to 8. Mine is set to 1, first switch up. I think this may be a problem if multiple BMS are in parallel like they designed it for with inverter communication, the master BMS needs to be set to 0 and you wouldn't be able to communicate to it. But not tested. If not using their inverter communication like me than no problem, Just don't use 0.

In the register map you have to add the address field and the HEX field togeather to get the registar you are trying to get.

For example if you wanted BatVol it lists 0x1200 and 0x00E4. Added equals 0x12E4. Also note UINT16 for decoding.

import pymodbus.client as ModbusClient
from pymodbus import pymodbus_apply_logging_config
from pyModbusTCP import utils # Note I used pyModbusTCP to decode the data just because that is what im used to...

unit_id = 1
reg_addr = 0x12E4
num_buff = 1    #Changes depending on lenght of register

# activate debugging
pymodbus_apply_logging_config("DEBUG")

# Setup connecton
c = ModbusClient.ModbusSerialClient(method='rtu', port="/dev/ttyUSB0", stopbits=1, bytesize=8, parity='N', baudrate=115200)

c.connect()

recv = c.read_holding_registers(address=reg_addr, count=num_buff, slave=unit_id)

# Get data out of recived register.
recv_data = recv.registers
    
c.close()    

print(str(recv_data[0]))

For CellCount it lists 0x1000 and 0x006C. Added equals 0x106C. Also note UINT32 for decoding.

import pymodbus.client as ModbusClient
from pymodbus import pymodbus_apply_logging_config
from pyModbusTCP import utils # Note I used pyModbusTCP to decode the data just because that is what im used to...

unit_id = 1
reg_addr = 0x106C
num_buff = 2    #Changes depending on length of register

# activate debugging
pymodbus_apply_logging_config("DEBUG")

# Setup connecton
c = ModbusClient.ModbusSerialClient(method='rtu', port="/dev/ttyUSB0", stopbits=1, bytesize=8, parity='N', baudrate=115200)

c.connect()

recv = c.read_holding_registers(address=reg_addr, count=num_buff, slave=unit_id)

# Get data out of recived register.
recv = recv.registers

#Combine registers and decode data. This is because it is UINT32 and two buffers.
list_32_bits = utils.word_list_to_long(recv)
recv_data_hex = [hex(i) for i in list_32_bits]
recv_data = int(recv_data_hex[0], 16)

c.close()    

print(str(recv_data))

2 replies

NorthTown2022 Mar 31, 2024
Author

Hello @nsuro I'm happy to hear the map files worked for you and thank you for posting :) Are you working on a project for Home Assistant?

nsuro Apr 4, 2024

No, but I should look at home assistant again. I was told that the JK inverter BMS would not work with my Schneider Electric Conext equipment. So before I start buying and building the new batteries I wanted to make sure I could at least communicate with the BMS with RS485/modbus. Intend to try and get some communication working between the two. The pylon protocol may work, don't know. Worst case I will now at least be able to see SoC and other info remotely.

Fugri · 2024-04-04T08:18:08Z

Fugri
Apr 4, 2024

Also throwing myself inhere.
I also have the JK-PB2A16S20P HW: 15 SW: 15.11 and want to connect with a MultiPuls II GX Venus 3.30 and serialbattery v1.2.20240401
Also cant get it to Connect i already tried RS485 CAN and Bluetooth with all the Available Protokolls

CAN-Bus:

@40000000660d289b1676add4` INFO:SerialBattery:
@40000000660d289b167e7604 INFO:SerialBattery:Starting dbus-serialbattery
@40000000660d289b169760ec INFO:SerialBattery:Venus OS v3.30
@40000000660d289b169e2f1c INFO:SerialBattery:dbus-serialbattery v1.2.20240401
@40000000660d28ac3b3a1df4 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
@40000000660d28ac3b41c6e4 INFO:SerialBattery:Testing Daly_Can

Gets stuck here forever and after re plugging the CAN Cable its gets recognized as Daly CAN and fails.

@40000000660d28ef106fb1ec INFO:SerialBattery:DalyBMS 0 cells
@40000000660d28ef107975ec INFO:SerialBattery:Connection established to Daly_Can
@40000000660d28ef1fc4975c INFO:SerialBattery:Found existing battery with DeviceInstance = 1
@40000000660d28ef29734654 INFO:SerialBattery:DeviceInstance = 1
@40000000660d28ef298a3d3c INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
@40000000660d28ef29919fdc INFO:SerialBattery:Used DeviceInstances = ['1']
@40000000660d28ef29985e6c INFO:SerialBattery:com.victronenergy.battery.can0
@40000000660d28ef2ac0a22c INFO:SerialBattery:publish config values = True
@40000000660d28ef2bede72c INFO:SerialBattery:Battery Daly_Can connected to dbus from can0
@40000000660d28ef2bf5de3c INFO:SerialBattery:========== Settings ==========
@40000000660d28ef2bfd3cf4 INFO:SerialBattery:> Connection voltage: NoneV | Current: NoneA | SoC: None%
@40000000660d28ef2c0412f4 INFO:SerialBattery:> Cell count: 0 | Cells populated: 0
@40000000660d28ef2c0b4a9c INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
@40000000660d28ef2c1341ac INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
@40000000660d28ef2c19f484 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 125.0A | MAX BATTERY DISCHARGE CURRENT: 125.0A
@40000000660d28ef2c1fe024 INFO:SerialBattery:> CVCM:     True
@40000000660d28ef2c25df4c INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
@40000000660d28ef2c2c0d54 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
@40000000660d28ef2c31b2a4 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@40000000660d28ef2c38f21c INFO:SerialBattery:Serial Number/Unique Identifier: DalyBMS0cells_50.0Ah
@40000000660d28f02c1ccb14 WARNING:SerialBattery:read_soc_data - triesValid 2

Bluetooth i get a few beeps from BMS when connecting but its not recognized:

@40000000660d2d59370b6094 INFO:SerialBattery:
@40000000660d2d593712e65c INFO:SerialBattery:Starting dbus-serialbattery
@40000000660d2d59372e03c4 INFO:SerialBattery:Venus OS v3.30
@40000000660d2d5937349f2c INFO:SerialBattery:dbus-serialbattery v1.2.20240401
@40000000660d2d6a124f2c04 INFO:SerialBattery:Init of Jkbms_Ble at C8:47:XX:XX:XX:XX
@40000000660d2d6a12572ecc INFO:SerialBattery:Test of Jkbms_Ble at C8:47:XX:XX:XX:XX
@40000000660d2d7810f6f6d4 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
@40000000660d2d781431de54 ERROR:SerialBattery:No BMS found at C8:47:XX:XX:XX:XX
@40000000660d2d78143a3edc ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
@40000000660d2d7826abc5cc 
@40000000660d2d7826af2ce4 INFO:Bluetooth details
@40000000660d2d78289584cc [CHG] Device C8:47:XX:XX:XX:XX RSSI: -70
@40000000660d2d782895afc4 [CHG] Device C8:47:XX:XX:XX:XX RSSI: -62
@40000000660d2d782895b794 [CHG] Device C8:47:XX:XX:XX:XX RSSI: -70
@40000000660d2d782895c34c [CHG] Device C8:47:XX:XX:XX:XX RSSI: -60
@40000000660d2d782b629eec Attempting to disconnect from C8:47:XX:XX:XX:XX
@40000000660d2d782b62c214 [CHG] Device C8:47:XX:XX:XX:XX RSSI is nil
@40000000660d2d782b62d1b4 [CHG] Device CB:4E:FD:B0:A8:4F RSSI is nil
@40000000660d2d782b62dd6c [CHG] Controller 5C:C5:63:1E:A3:7D Discovering: no
@40000000660d2d782b62e924 Successful disconnected
@40000000660d2d7d3082f7dc Device C8:47:XX:XX:XX:XX (public)
@40000000660d2d7d308326bc       Alias: JK_PB2A16S20P-01
@40000000660d2d7d30833274       Paired: no
@40000000660d2d7d3083365c       Trusted: no
@40000000660d2d7d30833e2c       Blocked: no
@40000000660d2d7d30834214       Connected: no
@40000000660d2d7d308345fc       LegacyPairing: no
@40000000660d2d7d308349e4       UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
@40000000660d2d7d30835984       RSSI: -70

Over RS485 same Problem like in the original Post

7 replies

Fugri Apr 4, 2024

I used it the JK Can Protocoll because as far i understand serialbattery implements that not the Virctron Protocol. The Victron Protocoll should work out of the box with a Victron System i guess, but yeah......

I made my own can Cable but Type A or Type B should work.

Also noticed the Pinout of the JK Documentation is wrong and also took a look at the breakout pcb and there isnt even any gnd for the can Interface. But shouldn't really matter because it should be isolated at bms and victron side.

in dbus-serialbattery.py and you need the latest beta for canbus support

And also make sure in the remote console that can is set to a 250k protocoll and you can also check there if you get CAN messages

NorthTown2022 Apr 5, 2024
Author

Having a bit of trouble here getting the GX to recognize the PB2A16S20P. I'm using a type A cable which I made myself as well. It previously tested fine before dbus-serialbattery driver was installed on the same BMS to GX using the Victron CANbus BMS protocol

In config.ini I have set CAN_PORT = can1. The driver acknowledges this change:

On the breakout PCB I have set first dip up (address 1)

Commented out Daly:

Using 250k:

A couple errors, but I think they have been there all evening:

Any ideas? I'm not sure how to get the CAN logs..

Fugri Apr 5, 2024

Logs are here: tail -f /data/log/dbus-canbattery.can0/current

For me at least i needed to set it to CAN_PORT = can0

Also i think you are running older firmware on the BMS right?

Because also the Name of my Can Protocol is different:

And i also have dip 1 up

And for me i also can see CAN Messages coming in in remote console even if serialbattery is disabled and i am on the same cabus protocoll in remote console as you so that shold be fine

You can find the new BMS Firmware and PC Software here: https://drive.google.com/drive/folders/1RsZvSsntvQqFDYC1oDibYVv18V35xeoB

For Firmware update you need dip 1 up and connect to pc via this rs485 port

Also just noticed in that in the official documentation the can and rs485 on the left side are flipped..... Their Documentation really is a shitshow

in top right of the PC bms software you can update the "Fireware" lol

NorthTown2022 Apr 5, 2024
Author

You are correct

I have set CAN_PORT = can0. Here are the logs:

BT is working fine but having communication issues with PC software (only on this BMS). First dip up and Device ID=1. Will try to sort this out this evening before i continue.

mr-manuel Jun 21, 2024
Collaborator

With v1.3.20240621dev I added some checks for the Daly BMS CAN that it does not recognize it anymore without reason.

mr-manuel/venus-os_dbus-serialbattery@63d68bf

NorthTown2022 · 2024-04-07T02:25:26Z

NorthTown2022
Apr 7, 2024
Author

So I got one of my BMS to update to V15.11 but since update no more PC communication (and lost heating in the process) :/ At least BT is still working on both and getting CAN messages:

I've got Daly commented out in dbus-serialbattery.py and Jk250k protocols selected but no joy in picking up SerialBattery(Jkbms_Can) in Device list:

My config:

MAX_BATTERY_CHARGE_CURRENT = 0
MAX_BATTERY_DISCHARGE_CURRENT = 0

; --------- CAN BMS ---------
; Description:
; Specify the CAN port(s) where the BMS is connected to. Leave empty to disable
; Available CAN BMS:
Daly_Can, Jkbms_Can
; Example for one CAN port:
CAN_PORT = can0
; Example for multiple CAN ports:
; CAN_PORT = can0, can8, can9

LOGGING = DEBUG

Any thoughts?

3 replies

Fugri Apr 7, 2024

Can you post the serialbattery log?

Also my config is:

MAX_BATTERY_CHARGE_CURRENT = 125
MAX_BATTERY_DISCHARGE_CURRENT = 125
CAN_PORT = can0

NorthTown2022 Apr 7, 2024
Author

Is this the log you are referring to?

root@einstein:~# tail -F -n 100 /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal
2024-04-05 01:29:48.635387500 DEBUG:SerialBattery:logged to dbus [100]
2024-04-05 01:29:48.636534500 DEBUG:SerialBattery:Cells:[1]3.328V [2]3.33V [3]3.332V [4]3.335V [5]3.333V [6]3.333V [7]3.335V [8]3.333V [9]3.333V [10]3.331V [11]3.331V [12]3.331V [13]3.331V [14]3.331V [15]3.333V [16]3.333V
2024-04-05 01:29:49.618409500 ERROR:SerialBattery:[Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'
2024-04-05 01:29:49.634593500 DEBUG:SerialBattery:logged to dbus [100]
2024-04-05 01:29:49.635802500 DEBUG:SerialBattery:Cells:[1]3.328V [2]3.33V [3]3.332V [4]3.335V [5]3.333V [6]3.333V [7]3.335V [8]3.333V [9]3.333V [10]3.331V [11]3.331V [12]3.331V [13]3.331V [14]3.331V [15]3.333V [16]3.333V
2024-04-05 01:29:50.619421500 ERROR:SerialBattery:[Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'
2024-04-05 01:29:50.628922500 DEBUG:SerialBattery:logged to dbus [100]
2024-04-05 01:29:50.630598500 DEBUG:SerialBattery:Cells:[1]3.328V [2]3.33V [3]3.332V [4]3.335V [5]3.333V [6]3.333V [7]3.335V [8]3.333V [9]3.333V [10]3.331V [11]3.331V [12]3.331V [13]3.331V [14]3.331V [15]3.333V [16]3.333V
2024-04-05 01:29:51.620608500 ERROR:SerialBattery:[Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0'
2024-04-05 01:29:51.622685500 WARNING:SerialBattery:Error while executing calcMaxChargeCurrentReferringToCellVoltage(). Using default value instead.
2024-04-05 01:29:51.624077500 WARNING:SerialBattery:Error while executing calcMaxDischargeCurrentReferringToCellVoltage(). Using default value instead.
2024-04-05 01:29:52.292109500 DEBUG:SerialBattery:Setted setting /Settings/Devices/serialbattery_JK_B2A20S20P/AllowMaxVoltage to 1
2024-04-05 01:29:52.340464500 DEBUG:SerialBattery:Saved AllowMaxVoltage. Before False, after True
2024-04-05 01:29:52.343173500 DEBUG:SerialBattery:Setted setting /Settings/Devices/serialbattery_JK_B2A20S20P/SocCalc to None
2024-04-05 01:29:52.355936500 ERROR:dbus.connection:Unable to set arguments (None,) according to signature 'v': <class 'TypeError'>: Don't know which D-Bus type to use to encode type "NoneType"
2024-04-05 01:29:52.397762500 Traceback (most recent call last):
2024-04-05 01:29:52.397771500 File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 811, in publish_battery
2024-04-05 01:29:52.397775500 self.publish_dbus()
2024-04-05 01:29:52.397777500 File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1100, in publish_dbus
2024-04-05 01:29:52.397781500 self.saveBatteryOptions()
2024-04-05 01:29:52.397783500 File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1259, in saveBatteryOptions
2024-04-05 01:29:52.397952500 result = result and self.setSetting(
2024-04-05 01:29:52.397955500 File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1159, in setSetting
2024-04-05 01:29:52.397959500 return True if method(value) == 0 else False
2024-04-05 01:29:52.397961500 File "/usr/lib/python3.8/site-packages/dbus/proxies.py", line 72, in call
2024-04-05 01:29:52.397965500 return self._proxy_method(*args, **keywords)
2024-04-05 01:29:52.397994500 File "/usr/lib/python3.8/site-packages/dbus/proxies.py", line 141, in call
2024-04-05 01:29:52.397998500 return self._connection.call_blocking(self._named_service,
2024-04-05 01:29:52.398001500 File "/usr/lib/python3.8/site-packages/dbus/connection.py", line 657, in call_blocking
2024-04-05 01:29:52.398005500 message.append(signature=signature, *args)
2024-04-05 01:29:52.398007500 TypeError: Don't know which D-Bus type to use to encode type "NoneType"
2024-04-05 01:29:52.832407500 /opt/victronenergy/serial-starter/run-service.sh: line 15: kill: (1731) - No such process
2024-04-05 03:18:03.158880500 *** CCGX booted (0) ***
2024-04-05 19:47:05.281177500 *** CCGX booted (0) ***
2024-04-05 20:18:05.180851500 *** CCGX booted (0) ***
2024-04-05 23:56:09.695013500 *** CCGX booted (0) ***
2024-04-06 11:37:08.289243500 *** CCGX booted (0) ***
2024-04-07 00:14:14.289668500 *** CCGX booted (0) ***
2024-04-07 00:39:18.256734500 *** CCGX booted (0) ***
2024-04-07 01:36:16.294072500 *** CCGX booted (0) ***
2024-04-07 02:01:21.267943500 *** CCGX booted (0) ***

Fugri Apr 8, 2024

no i mean the canbus log @ /data/log/dbus-canbattery.can0/current

NorthTown2022 · 2024-04-08T11:40:55Z

NorthTown2022
Apr 8, 2024
Author

Ok. The log repeats itself 32 times with different addresses. Please let me know if you'd like the full log:

root@einstein:~# tail -f /data/log/dbus-canbattery.can0/current
@400000006613d5d70b0cb664
@400000006613d5d81d5387bc Traceback (most recent call last):
@400000006613d5d81d53aae4 File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 20, in
@400000006613d5d81d53ba84 from dbushelper import DbusHelper
@400000006613d5d81d53c63c File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in
@400000006613d5d81d53d1f4 from utils import logger, publish_config_variables
@400000006613d5d81d53ddac File "/opt/victronenergy/dbus-serialbattery/utils.py", line 59, in
@400000006613d5d81d566a04 MAX_BATTERY_DISCHARGE_CURRENT = float(
@400000006613d5d81d5675bc ValueError: could not convert string to float: '0\n\nDaly_Can, Jkbms_Can'

6 replies

NorthTown2022 Apr 14, 2024
Author

I edited charge and discharge values but no difference really:

root@einstein:/# tail -f /data/log/dbus-canbattery.can0/current
@40000000661b1c512bd74e04
@40000000661b1c522d1582f4 Traceback (most recent call last):
@40000000661b1c522d15a61c File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 20, in
@40000000661b1c522d15b5bc from dbushelper import DbusHelper
@40000000661b1c522d15c174 File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 8, in
@40000000661b1c522d15cd2c from utils import logger, publish_config_variables
@40000000661b1c522d15d8e4 File "/opt/victronenergy/dbus-serialbattery/utils.py", line 59, in
@40000000661b1c522d184dcc MAX_BATTERY_DISCHARGE_CURRENT = float(
@40000000661b1c522d185984 ValueError: could not convert string to float: '60\n\nDaly_Can, Jkbms_Can'

Perhaps I just need to reset the GX and start over

Fugri Apr 15, 2024

should be enough to reinstall serial battery

NorthTown2022 Apr 16, 2024
Author

So I have installed the latest nightly, v1.2.20240413dev.

Not sure why but I now see SerialBattery(Daly_Can) in Device List. It does not recognize any voltages etc:

This is my new can log:

`root@einstein:~# cd /opt/victronenergy/dbus-serialbattery
root@einstein:/opt/victronenergy/dbus-serialbattery# nano dbus-serialbattery.py
root@einstein:/opt/victronenergy/dbus-serialbattery# tail -f /data/log/dbus-canbattery.can0/current
@40000000661dc3cc1fe2876c INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
@40000000661dc3cc1fef29cc INFO:SerialBattery:> CCCM T: True | DCCM T: True
@40000000661dc3cc1ffa87f4 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
@40000000661dc3cc2005de4c INFO:SerialBattery:> CHARGE FET: None | DISCHARGE FET: None | BALANCE FET: None
@40000000661dc3cc2012da84 INFO:SerialBattery:Serial Number/Unique Identifier: DalyBMS60cells_50.0Ah
@40000000661dc3cc232ecc3c INFO:SerialBattery:Monitoring external current using: None/None
@40000000661dc3cc235b1044 ERROR:SerialBattery:Exception occurred: AttributeError("'NoneType' object has no attribute 'split'") of type <class 'AttributeError'> in /opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py line #253
@40000000661dc3cc390655d4 INFO:SerialBattery:DeviceInstance = 4
@40000000661dc3cc391336b4 INFO:SerialBattery:Changed DeviceInstance = 4
@40000000661dc3cc393a13ec INFO:SerialBattery:Changed CustomName = SerialBattery(Daly_Can)

I do not understand these logs very well but just incase, here are the lines surrounding line 253:

Also, upon reboot I have discovered I need to go in and comment out Daly_Can again. So far have not seen SerialBattery(Jkbms_Can) in Device List, only SerialBattery(Daly_Can).

Fugri Apr 20, 2024

Finally assembled my pack. After connecting all 16 cells it didn't connect for me anymore. So i did some fixes to the script. So now for me SoC Current Voltage and highest and lowest cell are properly reported.
This is my config and jkbms can code is use
setup.zip

NorthTown2022 Apr 21, 2024
Author

@Fugri thanks for you help :)

Strangely enough, Jkbms_Can did show up in device list but must have been very briefly:

I've edited config.ini, dbus-serialbattery.py and jkbms_can.py with your setup files but still no joy. I'm having PC software related issues with this BMS (and another identical BMS). After upgrading they both lost heating function and no longer communicate with PC software. I feel this may be a contributing factor.

In the near future I will be putting the battery pack back into service at our cottage, summer home or "camp" as we call it for the summer so testing will be probably be on pause for a while.

kommando828 · 2024-04-15T15:24:05Z

kommando828
Apr 15, 2024

The JK docs on this new BMS are as already pointed out are a mess, I have come across this doc which confirms they have everything back to front on pinouts. Hopefully this may be of help. It plus Fugri's earlier pic allowed me to get the Canbus working.

4 replies

Fugri Apr 15, 2024

Do you have a Battery connected to bms? Can you confirm SoC is properly read? And how are your individual Cell Voltages reported?
Cheers

kommando828 Apr 15, 2024

Yes, battery is connected and there is an SOC reported of 68% with a resting cell voltage of 52.87V, average of 3.305V and a delta of 0.003V confirmed with voltage meter on each cell after the BMS was V calibrated, BMS also reports individual cell voltages.

Fugri Apr 15, 2024

I meant in Venus os on the Victron Side

kommando828 Apr 15, 2024

Not using Victron, found your post on the Canbus and used it to get Canbus working. I have Sunny Island SI5048 set to lithium, JK BMS set to Pylontech LV BMS and they are talking to each other. My post was a courtesy as your post had been helpful.

As the data sent is truncated then longer term I would want to get a solution that does the full SMA Canbus but the driver to allow Victron to speak to SMA Sunny Islands has been broken since Venus ver 3.0.

Martinmaker92 · 2024-05-06T08:21:49Z

Martinmaker92
May 6, 2024

Hi guys do you have any solution with this Problem?

i got my New JK BMS yesterday and ran into some problems. I was using 4 old style jk bms with serialbattery and the battery aggregator.

Now with the new one i connectet them in master Slave and via victron type A cable to the cerbo

now i can see the overall Voltega, highest, lowest cell, Ah and thats it. I cant use the Serialbattery now to reduce the charge current when the battery gets full. So is there a solution to get this to work?

ATM i just made a small programm on the cerbo to reduce the CCL when the highest cell gets over 3.4V but thas not the best solution. Is there a way the BMS controlls the CCL?

5 replies

kommando828 May 6, 2024

Assuming you are using Uart 2 which is hard set to JK-BMS RS485 Modbus V1.0 then this is the same port used by the JK Windows program. That reacts differently depending on whether the Dip switch is set to 0 or 1 (well at least on firmware 15.17). 0 gives you access to the parallel tab where all the connected BMS's data can be seen but no settings or firmware updates are allowed. 1 gives you access to only the one connected BMS but also you can change settings and update firmware.

So try changing the Dip to 0 and 1 and see if either work.

Martinmaker92 May 6, 2024

I have it set to 0 on the master BMS and connected it with the Victron cable on the 2nd RS485 Port

so you mean i should set the battery to 1 and connect it via which method? is this the way to do it to make it work with serialbattery or does the bms itself sets the CCL?

I have the latest Firmware on my bms i think it is 15.17

Thanks for the reply

kommando828 May 6, 2024

I have the BMS but do not use dbus-serial, only passing on what I have found with the BMS and the Windows program, its odd behaviour could be relevant.

Finding it works with 1 will potentially give you other issues as it can not be the master when set as 1, one of your older BMS's will need to be set to master and this may not work,

What I have found with the new BMS is that its Canbus does work once the pinouts are correct, I am running closed loop with an SMA SI5048. So you could set the canbus to 004 Victron and connect directly to your cerbo with the JK BMS set to master.

Note when connectiing to the Canbus port JK have it the wrong way round and Can_L is Can_H.

Martinmaker92 May 6, 2024

ok i have already seen this, and i will try to connect it via canbus on the Battery and USB on the Cerbo. I could connect each one seperate and use the battery aggregator to make them one big battery!

kommando828 May 6, 2024

Give it a try and report back.

If it does not work then as the new JK Uart 2 on the PB2 series BMS seems to behave oddly then Uart 1 may behave better. Uart 1 has several RS485 protocols selectable with the 006 Growatt possibly being the best option. Here is the PDF which could be used to add the option to dbus-serial.

Growatt_BMS_RS485_protocal_1xSxxP_ESS_V2.02-1.pdf

KoljaWindeler · 2024-06-11T07:46:56Z

KoljaWindeler
Jun 11, 2024

Hi everyone, I'm using serial battery with two batteries already (with another BMS) and really like the comfort just to plug the USB in.
I also use aggregated battery and control my charge/discharge current with the single cell voltages.

I've bought a Battery Kit for my 3rd battery that came with this BMS and sadly it is not working out of the box. After reading this thread I understand that it works somewhat with CAN but not in combination with serial battery and I won't get single cell voltage, right? So that would be a no go for me. I want to use the USB that comes with the battery.

I've seen the documentation that @NorthTown2022 attached (thx) and started to modify the existing jkbms driver to work with the new BMS version.

At this point I can request data and parse the overall voltage, temperatures, current, and single cell voltages

But there are still some todos as I'm using some shortcuts ..

no length parsing (using fixed length)
no CRC parsing
some fields not populated (e.g. max cell difference)
no max charge / discharge parsing

But before I dive deeper I'd like to make sure that it is worth the effort .. there is nobody working on the same at the moment, right?

Thanks JKW

40 replies

flashy02 Jul 6, 2024

No, I've not tested it yet, because then I've to disconnect my daisy chain and set every JK on address 1.

KoljaWindeler Jul 6, 2024

Ok, and I assume that works with three USB adapter and 3x address 0x01, right?

flashy02 Jul 6, 2024

I can test it later. I'm still waiting for my amazon parcel with the USB Hub in.

flashy02 Jul 6, 2024

With flying wires and another pi with 4 USB ports and LAN, i have tested the actual dev branch v1.3.20240705dev with address 1 and it looks good. Every JK was found and shown. Now, i would switch again on the MultiModbus-version to test again.

flashy02 Jul 6, 2024

Again, nothing is shown. Same configuration. 3 USB-Cables, still address set to1 and config.ini set to MODBUS_ADDRESSES = 0x01, but nothing is shown.

mr-manuel · 2024-07-06T07:29:40Z

mr-manuel
Jul 6, 2024
Collaborator

@flashy02 please post the logs under this answer. Are your daisy chained BMS recognized from the PC software?

29 replies

KoljaWindeler Jul 9, 2024

Awesome, @mr-manuel we have dynamic address working, could you explain your concept of multiple addresses? Something isn't working here

mr-manuel Jul 10, 2024
Collaborator

Could be that something isn't working. Until now it was only successfully tested with the Renogy BMS.

The concept is, that the driver fetches the addresses from the config.ini and when starting it loops through this addresses and tries to connect to them one after another. If the initialization process was successful, then all found BMS are polled one after the other adjusting automatically the poll interval, if it takes longer than configured.

It could be that the address conversion from config.ini (string) -> utils.py (string) -> dbus-serialbattery.py (conversion to bytes) is not working properly, even if it works for other BMS.

To verify this you can do this simple test, if not already done. Each step has to be working, else the next step will not work for sure.

Use the master branch version, connect one battery at a time and change the address here, to see if every BMS is recognized successfully.
https://github.com/mr-manuel/venus-os_dbus-serialbattery/blob/53d930fe60e85c933df917af179e3817c69c6cc2/etc/dbus-serialbattery/dbus-serialbattery.py#L56
Use the multiple-batteries-per-serial-adapter branch version, connect one battery at a time and use only one address here, to see if every BMS is recognized successfully.
https://github.com/mr-manuel/venus-os_dbus-serialbattery/blob/b59f15e43f6e9f19c6fff634edabf8a479390d88/etc/dbus-serialbattery/config.default.ini#L135-L141
Use the multiple-batteries-per-serial-adapter branch version, connect all batteries together and use all addresses here, to see if every BMS is recognized successfully.
https://github.com/mr-manuel/venus-os_dbus-serialbattery/blob/b59f15e43f6e9f19c6fff634edabf8a479390d88/etc/dbus-serialbattery/config.default.ini#L135-L141

If you want, we can write on my Discord server for dbus-serialbattery to speed up things a bit and to get faster answers, which could save a bit time for all of us ;-)

KoljaWindeler Jul 10, 2024

thanks for the guidance .. @flashy02 could you follow those steps ? sorry to use you here as our tester .. and to speed up things even further: Wo kommst du genau her? du wohnst nicht zufaellig in der naehe von Hannover?
Cheers, Kolja

KoljaWindeler Jul 10, 2024

@flashy02 i think it would still be great to follow the steps that @mr-manuel suggested
I'd say: always use RS485-2 for testing, and ignore RS485-1 for now.
Also ignore address 0x00 as this switches the BMS into the master mode and we don't need an another master besides us on the bus.

I'd assume that address 0x01 / 0x02 / .. should work on the master branch (at least it does here).
Would be interesting if 0x01 / 0x02 are working on the multiple-batteries-per-serial-adapter branch ..

Setup: two batteries, one configured to address 0x01 the other to 0x02.
Steps:

Battery 1 via RS485-2 directly via USB to venus running master branch, no MODBUS address
Battery 2 via RS485-2 directly via USB to venus running master branch, MODBUS address set to 0x02
Battery 1 via RS485-2 directly via USB to venus running multiple-batteries-per-serial-adapter branch, no MODBUS address
Battery 2 via RS485-2 directly via USB to venus running multiple-batteries-per-serial-adapter branch, MODBUS address set to 0x02
battery 1 connected via RS485-2 to battery 2 at RS485-2 and one of them additionally directly RS485-2 via USB to venus running multiple-batteries-per-serial-adapter branch, MODBUS address set to 0x01, 0x02

and as a backup we've just figured out that we only live ~100km apart from each other :)

mr-manuel Jul 10, 2024
Collaborator

There is a new version v1.4.20240710modbus with the latest modifications. You can install it using the install.sh -> 4) specific branch -> 2) multiple-batteries-per-serial-adapter.

kommando828 · 2024-07-07T08:36:24Z

kommando828
Jul 7, 2024

The JK-PB uart2 port behaves differently when the dip switch is in different positions plus when master/slave is initiated using the RJ45 cable connections between batterys.

In a standalone battery Dip set to 1 allows the BMS settings to be altered plus firmware to be uploaded using the Windows app but you get no access to the Parallel tab.

Set Dip to 0 and the Win app loses access to the battery settings and the ability to upload firmware, the parallel tab is ungreyed and you get access to all the data on daisy chained battery's.

If you keep the daisy chain wires in place then turning the Dip from 0 back to 1 does not change the Windows app back to allowing changing settings and firmware. You must first undaisy chain the BMS to regain access to the settings.

This suggests that daisy chaining breaks the JK RS485 protocol and it changes behaviour to a currently undocumented protocol.

Uart 1 also has the JK RS485 protocol as selectable. Maybe the solution is to set Uart1 to the JK RS485 and leave Uart2 in its odd daisychain configuartion and instead connect the ESP32 to uart 1.

0 replies

flashy02 · 2024-07-10T12:13:53Z

flashy02
Jul 10, 2024

I think the multiple-bms-per serial wouldn't work, because at the moment, it is not possible to recognize only one batterie if the daisychain is connected on RS485-2. So at the moment, the only way would be to use 3 USB cables each connected to the equivalent address on RS485-1 while daisychain is connected on RS485-2. I can try the offered steps to test. Naja, nähe ist relativ. Komme aus Region Wolfsburg und du laut LinkedIn und Git Profil wohl Region Celle :-). Kolja Windeler ***@***.***> schrieb am Mi., 10. Juli 2024, 13:36:

…

thanks for the guidance .. @flashy02 <https://github.com/flashy02> could you follow those steps ? sorry to use you here as our tester .. and to speed up things even further: *Wo kommst du genau her? du wohnst nicht zufaellig in der naehe von Hannover?* Cheers, Kolja — Reply to this email directly, view it on GitHub <#969 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIRFMY3CS55SDR3SGQ4HEXLZLUMCVAVCNFSM6AAAAABDEAPDKSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBQHEYDSNA> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

0 replies

mr-manuel · 2024-09-01T06:55:43Z

mr-manuel
Sep 1, 2024
Collaborator

Has at least one of you the same problem as here?

mr-manuel/venus-os_dbus-serialbattery#75

0 replies

mhin76 · 2024-09-26T09:20:41Z

mhin76
Sep 26, 2024

Hi all
I have a similar issue trying to connect my JK-B2A24S15P via dbus-serialbattery (v1.3.20240615beta) to my Venus OS (v3.50~22 unofficial release). I am using an "Accessories For JK Jikong Active Balancer BMS Battery Cable RS485" that I connect to the GPS port on my BMS (not the CAN/RS485, the cable would not even fit there) and then an USB-RS485 adapter.

I was reading somewhere that there might be different such RS485 adapter in the market and not all work with every JK BMS!?
Ah, just found it here https://off-grid-garage.com/bms-communication/:

not sure how to differentiate those two versions. Will try TTL to USB later.

but I get ">>> ERROR: No reply - returning" which ends up at "ERROR >>> No battery connection at /dev/ttyUSB0"

btw, it works perfectly via bluetooth. Just would like to make it work via serial.

One setting I have on iOS application to choose the correct protocol (don't know which one it is). See below.

I managed to let the driver ignore the /dev/ttyUSB0 via config.ini (as the BMS is connected to /dev/ttyUSB1). But it is not communicating at all. I see in the log only

2024-09-26 09:23:49.493506500 INFO:SerialBattery:Starting dbus-serialbattery
2024-09-26 09:23:49.494967500 INFO:SerialBattery:Venus OS v3.50~22
2024-09-26 09:23:49.495383500 INFO:SerialBattery:dbus-serialbattery v1.3.20240615beta

and on remote control an "not connected" battery. Any idea what might be wrong?

Here the protocol that also needs to fit to my adapter.

I guess this one should be the correct one:

but also this one might fit:

and here is where I had to chose

1 reply

KoljaWindeler Sep 26, 2024

my setup is working with UART1: 1 / UART2: 1 / CAN: 0
I guess the UART2 is the one that is labled rs485 at the front of my EEL case
JKW

mhin76 · 2024-09-26T13:14:11Z

mhin76
Sep 26, 2024

I only have one UART on my BMS, that is UART1. I replaced now those two components by a TTL-USB not sure if VenusOS is supporting that chip. The behavior is the same as on my previous set-up. Venus OS sends some transmit (transmit LED flashes), but nothing is combing back. If I choose the 013 - (9600)JKBMS... then the read LED flashes very quickly after the transmit LED, but still nothing showing up on the driver. I don't see anywhere to set the BAUD rate. If that might be an issue?

2 replies

KoljaWindeler Sep 26, 2024

hmm is this the right driver for your BMS? this is the JK PB bms ... there is a second .. non PB driver .. have you tried that?

mhin76 Sep 26, 2024

Hi Kolja. Thanks for your fast feedback! What do you mean with driver? The protocol selected? Or that JIKONG RS485 device? I don't see any PB mentioned.

joonasvaabel · 2024-10-06T08:31:37Z

joonasvaabel
Oct 6, 2024

I have problem with connecting multiple JKBMS_pb in parallel:

Setup:
Gerbo GX
RS485 to USB adapter: https://www.waveshare.com/usb-to-4ch-rs485.htm
JKBMS: Firmware 15.32
cable connections to RS485-2

in config,ini:
MODBUS_ADDRESSES = 0x01, 0x02
BMS_TYPE = Jkbms_pb

Everything works fine with the JK Windows PC software: Parallel setup (DIP master 0, 2nd battery 1), or 1, 2, or via separate COM ports from USB adapter. All options work.

But if I connect to Gerbo I get the unique identifier issue. Either battery, 1st or 2nd individually works.

Since the USB adapter provides 4 separate USB ports I tried connecting every possible way:

1st battery direct to USB adapter, 2nd battery direct to USB adapter. DIP switches either 0+1, 1+1 or 1+2
1st battery direct to USB adapter, 2nd battery daisy chained to 1st (and all possible DIP switch positions)

Whatever way two batteries are both recognized, I get the identifier conflict ("4041849190").

If I look at the Battery serial number via bluetooth app I see different serial numbers (ending "3" and "5"):

I don-t know whether JK publishes this faulty info or dbus-serialbattery doesn't read all the identifier fields (last number missing).

I cannot change serial number via app, although there are other customizable fields that I can change:

21 replies

mellanon Nov 3, 2024

@entropia1ac I have connected RS485 to USB Cerbo and set UART1 = 1 and the values are coming through on dbus[65].

Please note the difference between INFO and DEBUG logging. The INFO log level states that GetItems failed.

Forgive my ignorance but I can't see anything appearing in the CerboGX device or the VRM. What am I doing wrong?

2024-11-03 18:21:39.123434500 *** CCGX booted (0) ***
2024-11-03 18:22:29.988811500 INFO:SerialBattery:
2024-11-03 18:22:29.989573500 INFO:SerialBattery:Starting dbus-serialbattery
2024-11-03 18:22:29.992411500 INFO:SerialBattery:Venus OS v3.50~39
2024-11-03 18:22:29.993322500 INFO:SerialBattery:dbus-serialbattery v1.4.20240928
2024-11-03 18:22:46.008763500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-11-03 18:22:46.009718500 INFO:SerialBattery:Testing Jkbms_pb at address "\x02"
2024-11-03 18:22:46.152193500 DEBUG:SerialBattery:VolSmartSleep: 3.285
2024-11-03 18:22:46.152913500 DEBUG:SerialBattery:VolCellUV: 2.6
2024-11-03 18:22:46.153554500 DEBUG:SerialBattery:VolCellUVPR: 2.65
2024-11-03 18:22:46.154162500 DEBUG:SerialBattery:VolCellOV: 3.65
2024-11-03 18:22:46.155355500 DEBUG:SerialBattery:VolCellOVPR: 3.448
2024-11-03 18:22:46.156049500 DEBUG:SerialBattery:VolBalanTrig: 0.01
2024-11-03 18:22:46.159674500 DEBUG:SerialBattery:VolBalanTrig: 0.01
2024-11-03 18:22:46.160527500 DEBUG:SerialBattery:VolSOC_full: 3.449
2024-11-03 18:22:46.162373500 DEBUG:SerialBattery:VolSOC_empty: 2.64
2024-11-03 18:22:46.164007500 DEBUG:SerialBattery:VolSysPwrOff: 2.5
2024-11-03 18:22:46.164748500 DEBUG:SerialBattery:CurBatCOC: 105.0
2024-11-03 18:22:46.167474500 DEBUG:SerialBattery:TIMBatCOCPDly: 5
2024-11-03 18:22:46.168145500 DEBUG:SerialBattery:TIMBatCOCPRDly: 60
2024-11-03 18:22:46.168773500 DEBUG:SerialBattery:CurBatDcOC: 100.0
2024-11-03 18:22:46.169358500 DEBUG:SerialBattery:TIMBatDcOCPDly: 300
2024-11-03 18:22:46.169939500 DEBUG:SerialBattery:TIMBatDcOCPRDly: 60
2024-11-03 18:22:46.170514500 DEBUG:SerialBattery:TIMBatSCPRDly: 5
2024-11-03 18:22:46.171091500 DEBUG:SerialBattery:CurBalanMax: 2.0
2024-11-03 18:22:46.171663500 DEBUG:SerialBattery:TMPBatCOT: 50.0
2024-11-03 18:22:46.172239500 DEBUG:SerialBattery:TMPBatCOTPR: 131072.0
2024-11-03 18:22:46.172783500 DEBUG:SerialBattery:TMPBatDcOT: 50.0
2024-11-03 18:22:46.173339500 DEBUG:SerialBattery:TMPBatDcOTPR: 45.0
2024-11-03 18:22:46.173888500 DEBUG:SerialBattery:TMPBatCUT: 2.0
2024-11-03 18:22:46.182044500 DEBUG:SerialBattery:TMPBatCUTPR: 5.0
2024-11-03 18:22:46.182804500 DEBUG:SerialBattery:TMPMosOT: 100.0
2024-11-03 18:22:46.184752500 DEBUG:SerialBattery:TMPMosOTPR: 80.0
2024-11-03 18:22:46.187286500 DEBUG:SerialBattery:CellCount: 16
2024-11-03 18:22:46.187907500 DEBUG:SerialBattery:BatChargeEN: 1
2024-11-03 18:22:46.188536500 DEBUG:SerialBattery:BatDisChargeEN: 1
2024-11-03 18:22:46.189098500 DEBUG:SerialBattery:BalanEN: 1
2024-11-03 18:22:46.189650500 DEBUG:SerialBattery:CapBatCell: 304.0
2024-11-03 18:22:46.190174500 DEBUG:SerialBattery:SCPDelay: 1500
2024-11-03 18:22:46.332414500 DEBUG:SerialBattery:Serial Nr: 4051749177
2024-11-03 18:22:46.332423500 DEBUG:SerialBattery:Vendor ID: JK_PB2A16S20
2024-11-03 18:22:46.332425500 DEBUG:SerialBattery:HW Version: 15A / 15.3
2024-11-03 18:22:46.332428500 DEBUG:SerialBattery:SW Version: 15.3
2024-11-03 18:22:46.404831500 INFO:SerialBattery:Connection established to Jkbms_pb
2024-11-03 18:22:46.406339500 INFO:SerialBattery:Successful battery connection at /dev/ttyUSB0 and this Modbus address 0x02
2024-11-03 18:22:46.419340500 DEBUG:SerialBattery:setup_instance(): start
2024-11-03 18:22:46.431379500 DEBUG:SerialBattery:setup_instance(): SettingsDevice
2024-11-03 18:22:50.072335500 DEBUG:SerialBattery:setup_instance(): getSettingsWithValues
2024-11-03 18:22:50.092690500 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
2024-11-03 18:22:50.096276500 DEBUG:SerialBattery:setup_instance(): for loop ended
2024-11-03 18:22:50.114748500 DEBUG:SerialBattery:Setted setting /Settings/Devices/serialbattery_4051749177/LastSeen to 1730658170
2024-11-03 18:22:50.766849500 INFO:SerialBattery:DeviceInstance = 1
2024-11-03 18:22:50.779979500 INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
2024-11-03 18:22:50.781036500 INFO:SerialBattery:Used DeviceInstances = ['1']
2024-11-03 18:22:50.783434500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0__0x02
2024-11-03 18:22:50.924109500 INFO:SerialBattery:publish config values = False
2024-11-03 18:22:50.944947500 INFO:SerialBattery:Polling data every 1.000 s
2024-11-03 18:22:50.960549500 INFO:SerialBattery:Battery JKBMS PB Model connected to dbus from /dev/ttyUSB0
2024-11-03 18:22:50.963071500 INFO:SerialBattery:========== Settings ==========
2024-11-03 18:22:50.976889500 INFO:SerialBattery:> Connection voltage: 53.678 V | Current: 16.913 A | SoC: 65%
2024-11-03 18:22:50.979134500 INFO:SerialBattery:> Cell count: 16 | Cells populated: 16
2024-11-03 18:22:50.982435500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-11-03 18:22:50.984963500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.600 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.335 V
2024-11-03 18:22:50.998039500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 105.0 A | MAX BATTERY DISCHARGE CURRENT: 100.0 A
2024-11-03 18:22:51.007383500 INFO:SerialBattery:> CVCM:     True
2024-11-03 18:22:51.011911500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-11-03 18:22:51.012993500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-11-03 18:22:51.015494500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2024-11-03 18:22:51.020734500 INFO:SerialBattery:> CHARGE FET: 1 | DISCHARGE FET: 1 | BALANCE FET: None
2024-11-03 18:22:51.029202500 INFO:SerialBattery:Serial Number/Unique Identifier: 4051749177
2024-11-03 18:22:51.262147500 INFO:SerialBattery:Monitoring external current using: com.victronenergy.battery.ttyS5/Dc/0/Current
2024-11-03 18:22:51.305340500 INFO:dbusmonitor:===== Search on dbus for services that we will monitor starting... =====
2024-11-03 18:22:51.313785500 INFO:dbusmonitor:Found: com.victronenergy.battery.socketcan_can1, scanning and storing items
2024-11-03 18:22:51.357539500 INFO:dbusmonitor:       com.victronenergy.battery.socketcan_can1 has device instance 512
2024-11-03 18:22:51.360917500 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyUSB0__0x02, scanning and storing items
2024-11-03 18:23:16.372247500 INFO:dbusmonitor:GetItems failed, trying legacy methods
2024-11-03 18:23:41.376423500 INFO:dbusmonitor:       com.victronenergy.battery.ttyUSB0__0x02 was skipped because it has no device instance
2024-11-03 18:23:41.376434500 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyS5, scanning and storing items
2024-11-03 18:23:41.398635500 INFO:dbusmonitor:       com.victronenergy.battery.ttyS5 has device instance 277
2024-11-03 18:23:41.401832500 INFO:dbusmonitor:===== Search on dbus for services that we will monitor finished =====
2024-11-03 18:23:42.493854500 DEBUG:SerialBattery:Setted setting /Settings/Devices/serialbattery_4051749177/SocCalc to 65
2024-11-03 18:23:42.505756500 DEBUG:SerialBattery:soc_calc written to dbus: 65
2024-11-03 18:23:42.505765500 DEBUG:SerialBattery:logged to dbus [65]
2024-11-03 18:23:42.510185500 DEBUG:SerialBattery:Cells:[1]3.357V [2]3.357V [3]3.356V [4]3.356V [5]3.355V [6]3.355V [7]3.356V [8]3.356V [9]3.357V [10]3.357V [11]3.357V [12]3.356V [13]3.355V [14]3.355V [15]3.355V [16]3.355V 
2024-11-03 18:23:42.512682500 DEBUG:SerialBattery:Polling data took 1.092 seconds
2024-11-03 18:23:42.738798500 DEBUG:SerialBattery:logged to dbus [65]
2024-11-03 18:23:42.740229500 DEBUG:SerialBattery:Cells:[1]3.357V [2]3.358V [3]3.356V [4]3.356V [5]3.356V [6]3.356V [7]3.356V [8]3.356V [9]3.357V [10]3.357V [11]3.358V [12]3.356V [13]3.357V [14]3.356V [15]3.355V [16]3.355V 
2024-11-03 18:23:42.741287500 DEBUG:SerialBattery:Polling data took 0.225 seconds
tail: /data/log/dbus-serialbattery.ttyUSB0/current has been replaced; following end of new file
2024-11-03 18:23:44.468357500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.399999618530273
2024-11-03 18:23:44.468367500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.468372500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.468376500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.600000381469727
2024-11-03 18:23:44.468671500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.468677500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.5
2024-11-03 18:23:44.468682500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.600000381469727
2024-11-03 18:23:44.468742500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.5
2024-11-03 18:23:44.468795500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.469806500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.470756500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.471681500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.299999237060547
2024-11-03 18:23:44.472496500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.473374500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.474235500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.482522500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.482532500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.482537500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.482542500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.482677500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.5
2024-11-03 18:23:44.484945500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.485728500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.486879500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.487856500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.899999618530273
2024-11-03 18:23:44.488731500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.600000381469727
2024-11-03 18:23:44.489569500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.700000762939453
2024-11-03 18:23:44.490494500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.600000381469727
2024-11-03 18:23:44.491307500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 16.799999237060547
2024-11-03 18:23:44.492218500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 17.100000381469727
2024-11-03 18:23:44.493049500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 17.0
2024-11-03 18:23:44.493889500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 17.200000762939453
2024-11-03 18:23:44.494978500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 17.0
2024-11-03 18:23:44.496735500 DEBUG:SerialBattery:dbusServiceName: com.victronenergy.battery.ttyS5 - dbusPath: /Dc/0/Current - value: 17.200000762939453
2024-11-03 18:23:44.659707500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.671198500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.673224500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.685175500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.686575500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.754109500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.755679500 DEBUG:SerialBattery:current: 16.529 - current_external: 17.2
2024-11-03 18:23:44.769363500 DEBUG:SerialBattery:logged to dbus [65]
2024-11-03 18:23:44.771042500 DEBUG:SerialBattery:Cells:[1]3.357V [2]3.358V [3]3.356V [4]3.356V [5]3.356V [6]3.356V [7]3.355V [8]3.357V [9]3.355V [10]3.357V [11]3.358V [12]3.358V [13]3.357V [14]3.356V [15]3.355V [16]3.355V 
2024-11-03 18:23:44.772251500 DEBUG:SerialBattery:Polling data took 0.255 seconds

2024-11-03 18:30:27.025711500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-11-03 18:30:27.026673500 INFO:SerialBattery:Testing Jkbms_pb at address "\x02"
2024-11-03 18:30:27.320503500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-11-03 18:30:27.822711500 INFO:SerialBattery:-- Testing BMS: 2 of 3 rounds
2024-11-03 18:30:27.824011500 INFO:SerialBattery:Testing Jkbms_pb at address "\x02"
2024-11-03 18:30:28.106117500 INFO:SerialBattery:Connection established to Jkbms_pb
2024-11-03 18:30:28.107009500 INFO:SerialBattery:Successful battery connection at /dev/ttyUSB0 and this Modbus address 0x02
2024-11-03 18:30:31.480346500 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
2024-11-03 18:30:31.769073500 INFO:SerialBattery:DeviceInstance = 1
2024-11-03 18:30:31.771168500 INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
2024-11-03 18:30:31.771896500 INFO:SerialBattery:Used DeviceInstances = ['1']
2024-11-03 18:30:31.773041500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0__0x02
2024-11-03 18:30:31.826482500 INFO:SerialBattery:publish config values = False
2024-11-03 18:30:31.840902500 INFO:SerialBattery:Polling data every 1.000 s
2024-11-03 18:30:31.843036500 INFO:SerialBattery:Battery JKBMS PB Model connected to dbus from /dev/ttyUSB0
2024-11-03 18:30:31.843901500 INFO:SerialBattery:========== Settings ==========
2024-11-03 18:30:31.845086500 INFO:SerialBattery:> Connection voltage: 53.819 V | Current: 19.22 A | SoC: 66%
2024-11-03 18:30:31.846365500 INFO:SerialBattery:> Cell count: 16 | Cells populated: 16
2024-11-03 18:30:31.847812500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-11-03 18:30:31.849893500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.600 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.335 V
2024-11-03 18:30:31.851078500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 105.0 A | MAX BATTERY DISCHARGE CURRENT: 100.0 A
2024-11-03 18:30:31.852176500 INFO:SerialBattery:> CVCM:     True
2024-11-03 18:30:31.853620500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-11-03 18:30:31.854765500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-11-03 18:30:31.856018500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2024-11-03 18:30:31.857018500 INFO:SerialBattery:> CHARGE FET: 1 | DISCHARGE FET: 1 | BALANCE FET: None
2024-11-03 18:30:31.857961500 INFO:SerialBattery:Serial Number/Unique Identifier: 4051749177
2024-11-03 18:30:31.937703500 INFO:SerialBattery:Monitoring external current using: com.victronenergy.battery.ttyS5/Dc/0/Current
2024-11-03 18:30:31.960747500 INFO:dbusmonitor:===== Search on dbus for services that we will monitor starting... =====
2024-11-03 18:30:31.964247500 INFO:dbusmonitor:Found: com.victronenergy.battery.socketcan_can1, scanning and storing items
2024-11-03 18:30:31.983681500 INFO:dbusmonitor:       com.victronenergy.battery.socketcan_can1 has device instance 512
2024-11-03 18:30:31.986832500 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyUSB0__0x02, scanning and storing items
2024-11-03 18:30:56.989448500 INFO:dbusmonitor:GetItems failed, trying legacy methods
2024-11-03 18:31:21.991390500 INFO:dbusmonitor:       com.victronenergy.battery.ttyUSB0__0x02 was skipped because it has no device instance
2024-11-03 18:31:21.993063500 INFO:dbusmonitor:Found: com.victronenergy.battery.ttyS5, scanning and storing items
2024-11-03 18:31:22.010464500 INFO:dbusmonitor:       com.victronenergy.battery.ttyS5 has device instance 277
2024-11-03 18:31:22.013443500 INFO:dbusmonitor:===== Search on dbus for services that we will monitor finished =====

This is my config.ini

[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.

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

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 105.0
MAX_BATTERY_DISCHARGE_CURRENT = 100.0

; --------- Cell Voltages ---------
; Description:
;     Cell min/max voltages which are used for:
;         - Calculating the min/max battery voltage
;         - Trigger the SoC reset when SoC calculation is enabled
; Example:
;     16 cells * 3.45 V/cell = 55.2 V max charge voltage.
;     16 cells * 2.90 V/cell = 46.4 V min discharge voltage
MIN_CELL_VOLTAGE   = 2.600
; Max voltage (can seen as absorption voltage)
MAX_CELL_VOLTAGE   = 3.450
; Float voltage (can be seen as resting voltage)
FLOAT_CELL_VOLTAGE = 3.335

; --------- CAN BMS ---------
; Description:
;     Specify the CAN port(s) where the BMS is connected to. Leave empty to disable
;     Show available CAN ports with: canshow
; Available CAN BMS:
;     Daly_Can, Jkbms_Can
; Example for one CAN port (Cerbo GX, Ekrano GX):
;     CAN_PORT = vecan0
; Example for one CAN port (Raspberry Pi):
;     CAN_PORT = can0
; Example for multiple CAN ports:
;     CAN_PORT = can0, can8, can9
CAN_PORT = 
; Specify the CAN speed in kbps
CAN_SPEED = 250

; --------- Modbus (multiple BMS on one serial adapter) ---------
; Description:
;     Specify the modbus addresses as hexadeximal number for which a dbus-serialbattery instance should be started.
;     If leaved empty, the driver will connect only to the default address specified in the driver.
; Example:
;     MODBUS_ADDRESSES = 0x30, 0x31, 0x32, 0x33
MODBUS_ADDRESSES = 0x02  

; --------- Bluetooth BMS ---------
; Description:
;     Specify the Bluetooth BMS and it's MAC address that you want to install. Leave empty to disable
; Available Bluetooth BMS:
;     Jkbms_Ble, LltJbd_Ble
; Example for one BMS:
;     BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00
; Example for multiple BMS:
;     BLUETOOTH_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 = 

;Jkbms_Ble C8:47:80:1A:36:75

; --------- 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 for 20 minutes, if cell voltages are between
;     BLOCK_ON_DISCONNECT_VOLTAGE_MIN and BLOCK_ON_DISCONNECT_VOLTAGE_MAX. Else the driver block charge and discharge
;     after 60 seconds.
; True:
;     Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established
;     again or the driver/system is restarted. This is the Victron Energy default behaviour.
BLOCK_ON_DISCONNECT = False
; Specify in minutes how long the driver should continue to charge and discharge after the BMS communication is lost
BLOCK_ON_DISCONNECT_TIMEOUT_MINUTES = 20
; Specify a voltage range where the last fetched values of the driver should be to not block charging and discharging
; This is needed since during this time the driver has no idea what is happening
; Should be a safe range where the battery can operate without info for 20 minutes
BLOCK_ON_DISCONNECT_VOLTAGE_MIN = 3.25
BLOCK_ON_DISCONNECT_VOLTAGE_MAX = 3.35

; --------- External current sensor ---------
; Specify the dbus device and path where the external current sensor is connected to
; You can find it by executing the dbus-spy command
; Example for a external current sensor connected to the VE.Bus port:
;     EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = com.victronenergy.vebus.ttyS3
;     EXTERNAL_CURRENT_SENSOR_DBUS_PATH = /Dc/0/Current
EXTERNAL_CURRENT_SENSOR_DBUS_DEVICE = com.victronenergy.battery.ttyS5
EXTERNAL_CURRENT_SENSOR_DBUS_PATH = /Dc/0/Current


; --------- 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 reached and cell voltage difference is smaller or equal to
;             CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL it switches to float voltage after MAX_VOLTAGE_TIME_SEC
;             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 when set to True:
;     Step mode:
;          The battery reached max voltage of 55.2 V and hold it for 900 seconds, the the CVL is switched to
;          float voltage of 53.6 V to don't stress the batteries. Allow max voltage of 55.2 V again, if SoC is
;          once below 80%
;     Linear mode:
;          The battery reached max voltage of 55.2 V and the max cell difference is 0.010 V, then switch to float
;          voltage of 53.6 V after 900 additional seconds to don't stress the batteries. Allow max voltage of
;          55.2 V again if max cell difference is above 0.080 V or SoC below 80%.
; 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 MAX_VOLTAGE_TIME_SEC restarts if diff is bigger
CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_TIME_RESTART = 0.013
; 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 & linear mode)
; Specify how long the max voltage should be kept
;     Step mode: If reached then switch to float voltage
;     Linear mode: If cells are balanced keep max voltage for further MAX_VOLTAGE_TIME_SEC seconds
MAX_VOLTAGE_TIME_SEC = 900
; Specify SoC where CVL limit is reset to max voltage
;     Step mode: If SoC gets below
;     Linear mode: If cells are unbalanced or if SoC gets below
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 75


; --------- 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.55 V/cell = 63.9 V max charge voltage
;     18 cells * 2.70 V/cell = 48.6 V 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.60, 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 temperatures
;     NOTE: The temperatures are in ° Celsius. Temperature sensor 1 to 4 are used for the calculation.
; Example:
;     The temperature limit will be monitored to control the currents. If there are two temperature sensors,
;     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
; Discharge 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
TEMPERATURES_WHILE_CHARGING      =    0,    2,    5,   10,   15,   20,   35,   40,   55
MAX_CHARGE_CURRENT_T_FRACTION    = 0.00, 0.10, 0.20, 0.40, 0.80, 1.00, 1.00, 0.40, 0.00

TEMPERATURES_WHILE_DISCHARGING   =  -20,    0,    5,   10,   15,   45,   55
MAX_DISCHARGE_CURRENT_T_FRACTION = 0.00, 0.20, 0.30, 0.40, 1.00, 1.00, 0.00

; --------- Additional settings ---------
; Specify one or more BMS types to load else leave empty to try to load all available
; Available BMS:
;     Daly, Daren485, Ecs, EG4_Lifepower, EG4_LL, HeltecModbus, HLPdataBMS4S, Jkbms, Jkbms_pb, LltJbd, Renogy, Seplos, Seplosv3
; Available BMS, but disabled by default (just enter one or more below and it will be enabled):
;     ANT, MNB, Sinowealth
BMS_TYPE = Jkbms_pb

; Battery temperature
; Specify how the battery temperature is assembled
; 0 Get mean of temperature sensor 1 to sensor 4
; 1 Get only temperature from temperature sensor 1
; 2 Get only temperature from temperature sensor 2
; 3 Get only temperature from temperature sensor 3
; 4 Get only temperature from temperature sensor 4
TEMP_BATTERY = 0

; Temperature sensor 1 name
TEMP_1_NAME = Temp 1

; Temperature sensor 2 name
TEMP_2_NAME = Temp 2

; Temperature sensor 2 name
TEMP_3_NAME = Temp 3

; Temperature sensor 2 name
TEMP_4_NAME = Temp 4

; Show additional info in GUI -> Serialbattery -> Parameters
; This will show additional information to better understand how the driver works
; and what values are currently set which are not shown elsewhere in the GUI
; You have to scroll down to see the additional information
GUI_PARAMETERS_SHOW_ADDITIONAL_INFO = True

; Telemetry settings
; To help us improve the driver, we are collecting telemetry data. This data is anonymous and
; will only be used to improve the driver. The data is send once every week.
; You can disable this feature by setting this value to False.
; Some data we collect: Venus OS version, driver version, driver runtime, battery type, battery count,
TELEMETRY = False

; -- JKBMS settings
; Predefines cell count for Jkbms_can
; The cell count should be auto-detected by identifying the highest cell number,
; but this process may be sometimes slow what could cause that cells voltage is not not
; updated in VenusOS. Try this workaround if you experience problems with cell voltage.
JKBMS_CAN_CELL_COUNT = 16

; -- Unique ID settings
; Some already assembled BMS have no unique ID and no possibility to set one. In thi case
; you can use the USB port as the unique ID.
; It may be possible that VRM ID's and custom names are not saved/restored correctly in this case.
USE_PORT_AS_UNIQUE_ID = True

entropia1ac Nov 3, 2024

Connect only one battery via RS485 without CAN cable and without parallel connection of other batteries.Reset Cerbo.

mellanon Nov 3, 2024

I disabled DVCC and restarted the whole system. (To prevent system shut down while testing) Disconnected CAN cable on BMS side.
Restarted Cerbo. No luck.

Disconnected RS485 and reconnected CAN with CAN=0. Tried different CAN settings in config.ini. Nothing...

I've re-eanbled DVCC, connected CAN and set CAN=4 so the default Venus OS driver is used now to allow the BMS to manage the MPII again.

When you say reset Cerbo do you mean restart?

Here's a photo of the cerbo connectors.

I find it weird that the cerbo doesn't register the dbus device since the debug log state that it's writing values to dbus.

2024-11-03 18:31:21.991390500 INFO:dbusmonitor: com.victronenergy.battery.ttyUSB0__0x02 was skipped because it has no device instance

This suggests that while the battery driver establishes communication, it’s not correctly exporting the DeviceInstance property over D-Bus, which is essential for dbusmonitor to recognise and interact with the service.

entropia1ac Nov 3, 2024

What version of Cerbo do you have? - mine is 3.40. Does the battery connected via RS485-1 to the PC communicate with the Jk program?

mellanon Nov 3, 2024

Venus OS v3.50~39

Downgrading to 3.40 sounds like the next thing to try.

Thanks for your help so far.

entropia1ac · 2024-11-03T12:08:39Z

entropia1ac
Nov 3, 2024

set UART1: 1

0 replies

mhin76 · 2024-11-04T14:50:53Z

mhin76
Nov 4, 2024

thank you both for sharing! I don't have any DIPs on mine. My adapter has the following connections:

unfortunately I did not get it working with the official RS485 adapter from JK nor with TTL. I have ordered two other TTL to USB adapters. Will test it with them as well. All I see is that Raspberry Venus OS sends info (LED on adapter flashes) but nothing comes back.

I am using Venus v3.50 and dbus-serial-bat 1.3 (if I remember, will check later)

0 replies

Hooorny · 2024-11-14T13:14:22Z

Hooorny
Nov 14, 2024

Problem with JK Inverter BMS in CAN mode

Hi there,

I have the following components:

CerboGX
MP2 5000
JK Inverter BMS PB2A16S20P, HW Ver: V15A, SW Ver: V15.32

Currently the JK BMS is connected only via CAN to the 1st BMS CAN Port of the CerboGX, the 2nd Port is terminated.
The CAN protocol in the BMS is set to Victron_CANbus_BMS and all works fine.

Venus OS detects the JK BMS and uses it for DVCC.

Now I want to use SerialBattery instead of the build in Victron implementation, but I dont get it running.
My first thought was just to change the CAN protocol in the BMS to use "0 - JK BMS CAN 250k" or "6 - JK BMS CAN 500k"

but I always get the following logs:

I use the newest dev version and my config.ini is

BMS_TYPE = Jkbms_pb
CAN_PORT = can1
CAN_SPEED = 500 or 250 (tried both)

can1 is the correct name for the BMS-CAN port, I checked it with canshow and got traffic.
I also tried the VE-CAN Port at the Cerbo which for me is can0 and configured it as 250k / 500k in the remote console.

Still no success ...

Thanks for any help!

9 replies

hadloa Nov 14, 2024

that was the ticket, thanks a bunch!

Hooorny Nov 17, 2024

JKBMS PB currently does not support CAN connection with this driver. Only via RS485. There is no plan to add also CAN ability.

I will experiment with the CAN specifications from JK for the Inverter BMS, perhaps I can add a suitable driver ...

mr-manuel Nov 18, 2024
Collaborator

Could you then make also a how to from A to Z so I could add it then to the documentation?

Hooorny Nov 18, 2024

Could you then make also a how to from A to Z so I could add it then to the documentation?

Sure, if i make it running I will do.

dominikandreas Jan 3, 2025

I tried this as well, but can't get both battery packs to show up. I used 0000 and 1000 for the dip switches and connected a type A cable to my MP 2 GX. It connects to one of the battery packs, but not both:

==> /data/log/dbus-canbattery.can0/current <==
2025-01-03 09:45:39.116537500 INFO:SerialBattery:
2025-01-03 09:45:39.117340500 INFO:SerialBattery:Starting dbus-serialbattery
2025-01-03 09:45:39.121268500 INFO:SerialBattery:Venus OS v3.52 running on MultiPlus-II
2025-01-03 09:45:39.121970500 INFO:SerialBattery:dbus-serialbattery v2.0.20250103dev
2025-01-03 09:45:39.911999500 INFO:SerialBattery:Detected CAN Bus bitrate: 250 kbps
2025-01-03 09:45:41.921850500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2025-01-03 09:45:41.924160500 INFO:SerialBattery:Testing Jkbms_Can at address "\x00"
2025-01-03 09:45:41.934304500 INFO:SerialBattery:-- Connection established to Jkbms_Can
2025-01-03 09:45:41.935677500 INFO:SerialBattery:Successful battery connection at can0 and this address 0x00
2025-01-03 09:45:41.937112500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2025-01-03 09:45:41.938024500 INFO:SerialBattery:Testing Jkbms_Can at address "\x01"
2025-01-03 09:45:41.939926500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2025-01-03 09:45:42.443237500 INFO:SerialBattery:-- Testing BMS: 2 of 3 rounds
2025-01-03 09:45:42.444371500 INFO:SerialBattery:Testing Jkbms_Can at address "\x01"
2025-01-03 09:45:42.446723500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2025-01-03 09:45:42.950358500 INFO:SerialBattery:-- Testing BMS: 3 of 3 rounds
2025-01-03 09:45:42.951672500 INFO:SerialBattery:Testing Jkbms_Can at address "\x01"
2025-01-03 09:45:42.954275500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2025-01-03 09:45:43.456384500 WARNING:SerialBattery:No battery connection at can0 and this address 0x01
2025-01-03 09:45:44.344901500 INFO:SerialBattery:Reconnected to previously identified battery with DeviceInstance: 1
2025-01-03 09:45:44.796908500 INFO:SerialBattery:Use DeviceInstance: 1
2025-01-03 09:45:44.812975500 INFO:SerialBattery:Use dbus ServiceName: com.victronenergy.battery.can0__0x00
2025-01-03 09:45:44.975650500 INFO:SerialBattery:Polling interval: 1.000 s
2025-01-03 09:45:44.979385500 INFO:SerialBattery:Battery JKBMS CAN V2 connected to dbus from can0
2025-01-03 09:45:44.981572500 INFO:SerialBattery:========== Settings ==========
2025-01-03 09:45:44.983923500 INFO:SerialBattery:> Connection voltage: 53.120999999999995 V | Current: 0.0 A | SoC: 47%
2025-01-03 09:45:44.988309500 INFO:SerialBattery:> Cell count: 16 | Cells populated: 16
2025-01-03 09:45:44.997234500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2025-01-03 09:45:44.998620500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.700 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
2025-01-03 09:45:44.999683500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0 A | MAX BATTERY DISCHARGE CURRENT: 200.0 A
2025-01-03 09:45:45.000796500 INFO:SerialBattery:> CVCM:     True
2025-01-03 09:45:45.001710500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2025-01-03 09:45:45.002673500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2025-01-03 09:45:45.003670500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2025-01-03 09:45:45.024341500 INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: False | BALANCE FET: None
2025-01-03 09:45:45.024355500 INFO:SerialBattery:Serial Number/Unique Identifier: can0__0x00
2025-01-03 09:45:45.055290500 INFO:SerialBattery:Using external sensor for current: com.victronenergy.battery.ttyS2/Dc/0/Current
2025-01-03 09:45:45.086457500 INFO:SerialBattery:Using external sensor for SOC: com.victronenergy.battery.ttyS2/Soc

In my config.ini I've defined:

BMS_TYPE = Jkbms_Can
CAN_PORT = can0
BATTERY_ADDRESSES = 0x00, 0x01

Not sure what else to try, selecting the "victron" protocol in the settings via the app works fine without the driver, but I'd like to use dbus-serialbattery to see the individual battery voltages.

Is anyone using the new style JK inverter BMS with dbus-serialbattery driver? #969

Replies: 22 comments · 135 replies

NorthTown2022 Feb 21, 2024 Author

NorthTown2022 Feb 25, 2024 Author

mr-manuel Feb 25, 2024 Collaborator

NorthTown2022 Feb 25, 2024 Author

NorthTown2022 Mar 4, 2024 Author

NorthTown2022 Mar 31, 2024 Author

NorthTown2022 Apr 5, 2024 Author

NorthTown2022 Apr 5, 2024 Author

mr-manuel Jun 21, 2024 Collaborator

NorthTown2022 Apr 7, 2024 Author

NorthTown2022 Apr 7, 2024 Author

NorthTown2022 Apr 8, 2024 Author

NorthTown2022 Apr 14, 2024 Author

NorthTown2022 Apr 16, 2024 Author

NorthTown2022 Apr 21, 2024 Author

mr-manuel Jul 6, 2024 Collaborator

mr-manuel Jul 10, 2024 Collaborator

mr-manuel Jul 10, 2024 Collaborator

mr-manuel Sep 1, 2024 Collaborator

Replies: 22 comments 135 replies

NorthTown2022 Feb 21, 2024
Author

NorthTown2022
Feb 25, 2024
Author

mr-manuel
Feb 25, 2024
Collaborator

NorthTown2022 Feb 25, 2024
Author

NorthTown2022
Mar 4, 2024
Author

NorthTown2022 Mar 31, 2024
Author

NorthTown2022 Apr 5, 2024
Author

NorthTown2022 Apr 5, 2024
Author

mr-manuel Jun 21, 2024
Collaborator

NorthTown2022
Apr 7, 2024
Author

NorthTown2022 Apr 7, 2024
Author

NorthTown2022
Apr 8, 2024
Author

NorthTown2022 Apr 14, 2024
Author

NorthTown2022 Apr 16, 2024
Author

NorthTown2022 Apr 21, 2024
Author

mr-manuel
Jul 6, 2024
Collaborator

mr-manuel Jul 10, 2024
Collaborator

mr-manuel Jul 10, 2024
Collaborator

mr-manuel
Sep 1, 2024
Collaborator