Error on Canbus for JKBMS #61

rogergrant99 · 2024-07-27T15:16:33Z

rogergrant99
Jul 27, 2024

I am getting an error that I don't quite understand, maybe someone can help me in understanding the problem? Thanks

2024-07-27 15:12:58.661140500 INFO:SerialBattery:
2024-07-27 15:12:58.661848500 INFO:SerialBattery:Starting dbus-serialbattery
2024-07-27 15:12:58.663936500 INFO:SerialBattery:Venus OS v3.33
2024-07-27 15:12:58.664612500 INFO:SerialBattery:dbus-serialbattery v1.2.20240227beta
2024-07-27 15:13:16.594155500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-07-27 15:13:16.594890500 INFO:SerialBattery:Testing Jkbms_Can
2024-07-27 15:13:19.331403500 INFO:SerialBattery:Connection established to Jkbms_Can
2024-07-27 15:13:19.332433500 INFO:SerialBattery:Battery Jkbms_Can connected to dbus from can0
2024-07-27 15:13:19.333164500 INFO:SerialBattery:========== Settings ==========
2024-07-27 15:13:19.333894500 INFO:SerialBattery:> Connection voltage: NoneV | Current: NoneA | SoC: None%
2024-07-27 15:13:19.334752500 INFO:SerialBattery:> Cell count: 1 | Cells populated: 0
2024-07-27 15:13:19.336140500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-07-27 15:13:19.336689500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.9V | MAX CELL VOLTAGE: 3.45V
2024-07-27 15:13:19.337535500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0A | MAX BATTERY DISCHARGE CURRENT: 150.0A
2024-07-27 15:13:19.338236500 INFO:SerialBattery:> CVCM:     True
2024-07-27 15:13:19.339103500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-07-27 15:13:19.340049500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-07-27 15:13:19.340996500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2024-07-27 15:13:19.341793500 INFO:SerialBattery:Serial Number/Unique Identifier: NoneAh
2024-07-27 15:13:23.876818500 INFO:SerialBattery:Found existing battery with DeviceInstance = 7
2024-07-27 15:13:24.147000500 INFO:SerialBattery:DeviceInstance = 7
2024-07-27 15:13:24.148993500 INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_7.pid
2024-07-27 15:13:24.149763500 INFO:SerialBattery:Used DeviceInstances = ['2', '6', '1', '3', '5', '4', '7']
2024-07-27 15:13:24.150687500 INFO:SerialBattery:com.victronenergy.battery.can0
2024-07-27 15:13:24.171855500 INFO:SerialBattery:publish config values = True
2024-07-27 15:13:25.766152500 WARNING:SerialBattery:Error while executing calcMaxChargeCurrentReferringToCellVoltage(). Using default value instead.
2024-07-27 15:13:25.767332500 WARNING:SerialBattery:Error while executing calcMaxDischargeCurrentReferringToCellVoltage(). Using default value instead.
2024-07-27 15:13:25.871257500 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-07-27 15:13:25.886084500 Traceback (most recent call last):
2024-07-27 15:13:25.886093500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 811, in publish_battery
2024-07-27 15:13:25.886097500     self.publish_dbus()
2024-07-27 15:13:25.886099500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1100, in publish_dbus
2024-07-27 15:13:25.886103500     self.saveBatteryOptions()
2024-07-27 15:13:25.886105500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1259, in saveBatteryOptions
2024-07-27 15:13:25.886240500     result = result and self.setSetting(
2024-07-27 15:13:25.886242500   File "/opt/victronenergy/dbus-serialbattery/dbushelper.py", line 1159, in setSetting
2024-07-27 15:13:25.886246500     return True if method(value) == 0 else False
2024-07-27 15:13:25.886249500   File "/usr/lib/python3.8/site-packages/dbus/proxies.py", line 72, in __call__

Answered by rogergrant99

Jul 29, 2024

After looking at CAN data I am thinking that there can only be one BMS per CAN buss. The way I understand it is that the message ID is the only ID provided.... Therefore both BMS send exactly the same ID messages. So I tried to connect one BMS to CAN0 and the other to CAN1 and after a bit of code modification (so the identifier is unique) I got it to work correctly.
Also I discovered that the message ID for CELL_VOLT and CELL_TEMP was different when connected to CAN1 vs CAN0 (but the BATT_STAT is correct...) That one I could not figure out, I don't know if some manipulation is done in the Cerbo before CAN messages are captured... So I added the new (or rewritten) frame id for the CELL_VOL…

View full answer

rogergrant99 · 2024-07-27T16:30:25Z

rogergrant99
Jul 27, 2024
Author

Actually, after switching CAN BUSS speed to 500K this error went away....

1 reply

mr-manuel Jul 27, 2024
Maintainer

But does it work with both?

rogergrant99 · 2024-07-27T17:55:49Z

rogergrant99
Jul 27, 2024
Author

After switching back to 250K i did not get the error... I think it was some confusion between BMS and Cerbo, resetting everything seem to have clear the issue, it now works at both speeds. But I am getting different information than the Bluetooth connection, I show here the different settings depending if I use Bluetooth or CAN bus... Also I have two batteries and only one show up, is there something to set in the config too allow for two batteries on the same can buss?

BLUETOOTH
2024-07-27 17:36:14.831515500 INFO:SerialBattery:========== Settings ==========
2024-07-27 17:36:14.832521500 INFO:SerialBattery:> Connection voltage: 13.35 V | Current: 0.0 A | SoC: 98%
2024-07-27 17:36:14.833154500 INFO:SerialBattery:> Cell count: 4 | Cells populated: 8
2024-07-27 17:36:14.833749500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-07-27 17:36:14.834415500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
2024-07-27 17:36:14.835060500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0 A | MAX BATTERY DISCHARGE CURRENT: 150.0 A
2024-07-27 17:36:14.835694500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 185.0 A | MAX BATTERY DISCHARGE CURRENT: 185.0 A (read from BMS)
2024-07-27 17:36:14.836278500 INFO:SerialBattery:> CVCM: True
2024-07-27 17:36:14.837015500 INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
2024-07-27 17:36:14.837694500 INFO:SerialBattery:> CCCM T: True | DCCM T: True
2024-07-27 17:36:14.838452500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2024-07-27 17:36:14.839111500 INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: True | BALANCE FET: True
2024-07-27 17:36:14.848778500 INFO:SerialBattery:Serial Number/Unique Identifier: 4051628016

CAN@500K
2024-07-27 17:46:05.904244500 INFO:SerialBattery:========== Settings ==========
2024-07-27 17:46:05.904942500 INFO:SerialBattery:> Connection voltage: 13.3 V | Current: 0.0 A | SoC: 98%
2024-07-27 17:46:05.905515500 INFO:SerialBattery:> Cell count: 4 | Cells populated: 4
2024-07-27 17:46:05.909099500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-07-27 17:46:05.909108500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.450 V| FLOAT CELL VOLTAGE: 3.375 V
2024-07-27 17:46:05.909112500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 150.0 A | MAX BATTERY DISCHARGE CURRENT: 150.0 A
2024-07-27 17:46:05.909116500 INFO:SerialBattery:> CVCM: True
2024-07-27 17:46:05.909471500 INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
2024-07-27 17:46:05.910467500 INFO:SerialBattery:> CCCM T: True | DCCM T: True
2024-07-27 17:46:05.911438500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2024-07-27 17:46:05.912446500 INFO:SerialBattery:> CHARGE FET: None | DISCHARGE FET: None | BALANCE FET: None
2024-07-27 17:46:05.913493500 INFO:SerialBattery:Serial Number/Unique Identifier: JKBMSCAN4cells_NoneAh

1 reply

mr-manuel Jul 27, 2024
Maintainer

On CAN not all informations are available yet. No one tested multiple BMS over CAN until now. You would be the first to try and test that.

rogergrant99 · 2024-07-27T21:15:50Z

rogergrant99
Jul 27, 2024
Author

Oh, ok. I tried to get the two BMS to show up but to no avail. Looking at the code it appears that the jkbms_can.py does not have the concept of a unique identifier.... Perhaps that is the issue. If I compare with jkbms_ble.py I can see that it does generate a unique identifier.

except from jkbms_ble.py:
{
def unique_identifier(self) -> str:
"""
Used to identify a BMS when multiple BMS are connected
"""
return self.unique_identifier_tmp
}

1 reply

mr-manuel Jul 27, 2024
Maintainer

The unique identifier should not be the only problem. You have to know how to reach each BMS and therefore which address each BMS has. I don't know yet how exactly this works when multiple BMS are connected and if the automatically get a different address. Maybe it is also not possible with JKBMS. You could ask your seller, if it's possible to daisy chain multiple JKBMS on the CAN port.

rogergrant99 · 2024-07-27T22:35:34Z

rogergrant99
Jul 27, 2024
Author

You are right, I just modified the code to generate a unique ID and it does not help. I will try to figure this out if I can...

5 replies

mr-manuel Jul 28, 2024
Maintainer

What Chat GPT say: While individual devices do not need unique addresses, the messages they send do need unique identifiers. This ensures that each type of data can be distinguished on the network.

rogergrant99 Jul 28, 2024
Author

On the jkbms there is an identifier, I set one to 0 and the second to 1 , that should tag the data appropriately.

mr-manuel Jul 28, 2024
Maintainer

You could try to see if there is a difference in the data with candump like he did: Louisvdw/dbus-serialbattery#950

rogergrant99 Jul 29, 2024
Author

After looking at CAN data I am thinking that there can only be one BMS per CAN buss. The way I understand it is that the message ID is the only ID provided.... Therefore both BMS send exactly the same ID messages. So I tried to connect one BMS to CAN0 and the other to CAN1 and after a bit of code modification (so the identifier is unique) I got it to work correctly.
Also I discovered that the message ID for CELL_VOLT and CELL_TEMP was different when connected to CAN1 vs CAN0 (but the BATT_STAT is correct...) That one I could not figure out, I don't know if some manipulation is done in the Cerbo before CAN messages are captured... So I added the new (or rewritten) frame id for the CELL_VOLT and CELL_TEMP. It all seems to work correctly but I see that the CAN implementation of the jkbms does not provide as much information as the rs-485 or bluetooth.

I include the diff file so you can see what you think.
jkbms_can.diff.txt

Answer selected by rogergrant99

rogergrant99 · 2024-07-28T17:30:47Z

rogergrant99
Jul 28, 2024
Author

That’s what I am actually doing…. But no joy up to now. I got the specs from jkbms and reading through it. Roger

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error on Canbus for JKBMS #61

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 8 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Error on Canbus for JKBMS #61

rogergrant99 Jul 27, 2024

Replies: 5 comments · 8 replies

rogergrant99 Jul 27, 2024 Author

mr-manuel Jul 27, 2024 Maintainer

rogergrant99 Jul 27, 2024 Author

mr-manuel Jul 27, 2024 Maintainer

rogergrant99 Jul 27, 2024 Author

mr-manuel Jul 27, 2024 Maintainer

rogergrant99 Jul 27, 2024 Author

mr-manuel Jul 28, 2024 Maintainer

rogergrant99 Jul 28, 2024 Author

mr-manuel Jul 28, 2024 Maintainer

rogergrant99 Jul 29, 2024 Author

rogergrant99 Jul 28, 2024 Author

rogergrant99
Jul 27, 2024

Replies: 5 comments 8 replies

rogergrant99
Jul 27, 2024
Author

mr-manuel Jul 27, 2024
Maintainer

rogergrant99
Jul 27, 2024
Author

mr-manuel Jul 27, 2024
Maintainer

rogergrant99
Jul 27, 2024
Author

mr-manuel Jul 27, 2024
Maintainer

rogergrant99
Jul 27, 2024
Author

mr-manuel Jul 28, 2024
Maintainer

rogergrant99 Jul 28, 2024
Author

mr-manuel Jul 28, 2024
Maintainer

rogergrant99 Jul 29, 2024
Author

rogergrant99
Jul 28, 2024
Author