Victron VenusOS driver for serial connected BMS - JBD / Daly / ANT / JKBMS / Heltec / Renogy / Tian / ECS

[Louisvdw]

Updated to firmware 2.8 at the same time as adding a Victron charge controller and lost the connection to the BMS

Check your logfiles to see that serial starter is trying the driver on the correct ports. Then look at the dbus-serialbattery logs for those ports as they should give you a good indication of what it happening.

 

[jbpomme]

Hopefully not breaking any rules here, but I propose a "bounty" of sorts on the battery bank functionality. In the interest of simplicity and transparency, I donated via Ko-Fi (https://ko-fi.com/louisvdw), I encourage others do the same to support the project in general and show support for new feature development. [I see that quite a few people have already, so thank you!]

I've been using the driver everyday and find it indispensable. Multi battery would be the cherry on top.

I'm throwing in $100 towards multi battery. Anyone else?

It's done. Louis is doing a great job!

 

[Boot103]

Amazing job. Im running two JBD BMS boards as I have 2 x 8s banks. Is it possible to add both and Name them A and B ?

 

[spaner]

You can keep it here. Anything with the driver and BMS support is fine in this thread

Looking forward to the electrodacus SMBS0 driver !!! Thanks to airtime for sending the unit !!!

 

[charlesrg]

Awesome work guys.

 

[csab3266]

I use the serial battery driver on a GX device (Raspberry, Venus 2.84) with an Overkill Solar BMS (16s) and a Multiplus II. While discharging the battery the driver works flawless but when the multiplus starts charging the driver disconnects and shows "Not connected".

While charging:


Charging stopped:


cat /data/log/serial-starter/current | tai64nlocal:

2022-03-02 14:19:47.437218500 INFO: Start service gps-dbus.ttyUSB0 once
2022-03-02 14:19:56.801020500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-03-02 14:20:02.146130500 INFO: Start service dbus-cgwacs.ttyUSB0 once
2022-03-02 14:20:07.430442500 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
2022-03-02 14:20:10.697116500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
2022-03-02 14:20:13.964845500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2022-03-02 14:20:17.251243500 INFO: Start service dbus-serialbattery.ttyUSB0 once
2022-03-02 14:20:20.536951500 INFO: Start service gps-dbus.ttyUSB0 once
2022-03-02 14:20:29.887434500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-03-02 14:20:35.188401500 INFO: Start service dbus-cgwacs.ttyUSB0 once
2022-03-02 14:20:40.474041500 INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
2022-03-02 14:20:43.761693500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
2022-03-02 14:20:47.071986500 INFO: Start service dbus-modbus-client.serial.ttyUSB0 once
2022-03-02 14:20:50.343984500 INFO: Start service dbus-serialbattery.ttyUSB0 once

cat /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal:

2022-03-02 14:29:16.497792500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:17.502094500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:18.503478500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:19.733087500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:20.505885500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:26.516017500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:28.518624500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:32.784580500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:36.524824500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:37.525355500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:38.532549500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:42.535696500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:49.897733500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:50.546211500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:51.803000500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:54.550716500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:55.548247500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:57.559852500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:29:58.551660500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:30:10.567126500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:30:23.897397500 ERROR:SerialBattery:>>> ERROR: No reply - returning

Can somebody help?

 

[Louisvdw]

Is it possible to add both and Name them A and B

I'll create a ticket so that we can add this. At the moment there is no option for custom name, but it has been requested before.
Edit: https://github.com/Louisvdw/dbus-serialbattery/issues/100

 

[Louisvdw]

"Not connected"

What most likely is happening is that you have a miscomfigured battery, or your cells are not balanced.
The only time I have seen the JBD BMS disconnect is when it reapeatedly gets an overvoltage on the cells.

If you look at your alarm logs in your VRM cloud, do you see cell imbalance alarms?
First check that your cell capacities match what you have set up in your BMS (The setting in your BMS should be the same or lower, but not more). Then if you have changed the min/max cell settings from the default return them to the defaults. If they were the defaults, lower the max cell to 3.35V and keep them there for 1 week, raise them by 0.05V after a week if you do not see any disconnects up to the normal 3.45v (this is to give your BMS time to balance the cells and you can keep them lower for longer if need be).

 

[csab3266]

Thanks a lot for your reply.

What most likely is happening is that you have a miscomfigured battery, or your cells are not balanced.
The only time I have seen the JBD BMS disconnect is when it reapeatedly gets an overvoltage on the cells.

I made a top balancing a few weeks ago. The biggest difference is between 0.009 - 0.011V. Will recheck my BMS settings.

If you look at your alarm logs in your VRM cloud, do you see cell imbalance alarms?
First check that your cell capacities match what you have set up in your BMS (The setting in your BMS should be the same or lower, but not more). Then if you have changed the min/max cell settings from the default return them to the defaults. If they were the defaults, lower the max cell to 3.35V and keep them there for 1 week, raise them by 0.05V after a week if you do not see any disconnects up to the normal 3.45v (this is to give your BMS time to balance the cells and you can keep them lower for longer if need be).

No, there are no imbalance alarms in my log. The disconnect is also at low SoC (e.g. cell voltage 3.1V).
Does this log provide further information?

2022-03-02 14:19:12.826603500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:19:12.840812500 Traceback (most recent call last):
2022-03-02 14:19:12.840820500 File "/data/etc/dbus-serialbattery/dbushelper.py", line 159, in publish_battery
2022-03-02 14:19:12.840825500 self.publish_dbus()
2022-03-02 14:19:12.840827500 File "/data/etc/dbus-serialbattery/dbushelper.py", line 206, in publish_dbus
2022-03-02 14:19:12.840832500 self._dbusservice['/System/MaxCellVoltage'] = self.battery.get_max_cell_voltage()
2022-03-02 14:19:12.840837500 File "/data/etc/dbus-serialbattery/battery.py", line 178, in get_max_cell_voltage
2022-03-02 14:19:12.840981500 return min_voltage
2022-03-02 14:19:12.840984500 UnboundLocalError: local variable 'min_voltage' referenced before assignment
2022-03-02 14:19:45.079138500 WARNING:SerialBattery:dbus-serialbattery v0.1
2022-03-02 14:19:45.081405500 WARNING:SerialBattery:Testing LltJbd
2022-03-02 14:19:45.375376500 WARNING:SerialBattery:Connection established to LltJbd
2022-03-02 14:19:45.689960500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:19:45.696779500 Traceback (most recent call last):
2022-03-02 14:19:45.696785500 File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 110, in <module>
2022-03-02 14:19:45.696790500 main()
2022-03-02 14:19:45.696792500 File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 95, in main
2022-03-02 14:19:45.696797500 if not helper.setup_vedbus():
2022-03-02 14:19:45.696800500 File "/data/etc/dbus-serialbattery/dbushelper.py", line 74, in setup_vedbus
2022-03-02 14:19:45.696804500 self._dbusservice.add_path('/Info/BatteryLowVoltage', self.battery.min_battery_voltage, writeable=True)
2022-03-02 14:19:45.696898500 AttributeError: 'LltJbd' object has no attribute 'min_battery_voltage'
2022-03-02 14:20:18.159733500 WARNING:SerialBattery:dbus-serialbattery v0.1
2022-03-02 14:20:18.161602500 WARNING:SerialBattery:Testing LltJbd
2022-03-02 14:20:18.517769500 WARNING:SerialBattery:Connection established to LltJbd
2022-03-02 14:20:18.826107500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:20:18.832944500 Traceback (most recent call last):
2022-03-02 14:20:18.832951500 File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 110, in <module>
2022-03-02 14:20:18.832956500 main()
2022-03-02 14:20:18.832958500 File "/opt/victronenergy/dbus-serialbattery/dbus-serialbattery.py", line 95, in main
2022-03-02 14:20:18.832963500 if not helper.setup_vedbus():
2022-03-02 14:20:18.832966500 File "/data/etc/dbus-serialbattery/dbushelper.py", line 74, in setup_vedbus
2022-03-02 14:20:18.832971500 self._dbusservice.add_path('/Info/BatteryLowVoltage', self.battery.min_battery_voltage, writeable=True)
2022-03-02 14:20:18.833069500 AttributeError: 'LltJbd' object has no attribute 'min_battery_voltage'
2022-03-02 14:20:51.314162500 WARNING:SerialBattery:dbus-serialbattery v0.1
2022-03-02 14:20:51.316049500 WARNING:SerialBattery:Testing LltJbd
2022-03-02 14:20:51.585044500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:20:51.586558500 WARNING:SerialBattery:Testing Ant
2022-03-02 14:20:51.859926500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2022-03-02 14:20:51.861581500 ERROR:SerialBattery:>>> ERROR: Incorrect Data
2022-03-02 14:20:51.862179500 WARNING:SerialBattery:Testing Daly

Don't know if it's just a coincidence: The problem started after removing a WiFi stick from the raspberry.

 

[Louisvdw]

The problem started after removing a WiFi stick from the raspberry.

It seems like the JBL cannot get the battery voltage which comes from the cell count.
The most likely problem would be a loose connection that got bumped when you removed the wifi stick. Remove all your USB connections, check that all the wires are still firmly connected and fasten them again and plug them back in. You can also check the wire connections on the BMS side as well and make sure they are firmly in their sockets.

 

[Louisvdw]

@csab3266 please see if beta release https://github.com/Louisvdw/dbus-serialbattery/releases/tag/v0.11beta solves your error.

 

[linkcat]

This is amazing, I'm on the design phase of my system for off grid (already did it for the van) and this is going to rock. If you need some betatesters, count with me. Currently, 2 packs of diy batteries with JBD bms + victron shunt, scc and inverter/charger with a pi2 (os venus). In the future, i'm planning something bigger for home.

Edit: When I bought my BMS (JBD), I order it as UART, and I guess it has the UART connected to the bluetooth stick. Can I remove the bluetooth stick and connect there some other adapter. An Usb (to the pi) and on the other end RS485 to the UART could work?




Cheers

 

[Blizzard]

I use the serial battery driver on a GX device (Raspberry, Venus 2.84) with an Overkill Solar BMS (16s) and a Multiplus II. While discharging the battery the driver works flawless but when the multiplus starts charging the driver disconnects and shows "Not connected".

While charging:
View attachment 85806

Charging stopped:
View attachment 85807

cat /data/log/serial-starter/current | tai64nlocal:



cat /data/log/dbus-serialbattery.ttyUSB0/current | tai64nlocal:


Can somebody help?

Hi, I was wondering, did you update the Multiplus to the latest firmware? I did (494) and got weird outputs. This could effect the BMS also.
Findings:
1 All my assistants/setups were gone, reinstalling I see now in remote 2 ESS releases.
2 In VRM I see sometimes weird values, battery drains a lot and it goes nowhere...
I will this weekend flash back to the previous one, and install the new smartdaly also (now working on a cheap balancer)

 

[jontm]

Hi!

My Victron Quattro is too old to use firmwares (small CPU) that support DVCC according to Victron manuals at least...
Do i strictly need to enable DVCC if I do not require functionality like the BMS talking to the Quattro ?
My aim is just to be able to have remote monitoring of everything in Victron VRM... I am fine with not being able to adjust charge current dynamically.

 

[bond007taz]

legit... i got an overkill bms 100a 8s 24v and connected their "JBD-UART-TOOLS" UART to USB adapter into the Overkill's BMS UART port and then connected the USB to my Cerbo GX (updated the driver on the GX via SSH) and rebooted the Cerbo GX and boom, it is show my BMS details - LEGIT! Thanks! Can't wait to be able to change the "SerialBattery" to another name, but i dont care, i am extremely happy I can view the BMS details with my Victron setup!!! Thank you

 

[Louisvdw]

Do i strictly need to enable DVCC

You should be able to get your battery into the GX display using the driver without the DVCC option. Your battery will not be used as the battery monitor in the system, but at least you will see you data.

 

[Blizzard]

Not yet

Idea to programm in your script letting Venus OS to abort/wait updating unless your driver is accepting the latest firmware?

 

[Refinished]

Is there development around the SBMS0 or is that on hold for some technical or other reason? Trying to decide in which basket to put my eggs! And happy to supply some ko-fi...

 

[Louisvdw]

development around the SBMS0

We do have some work around the SMBS0 happening. Not sure when we will have a working prototype yet though.

 

[aries]

I'm looking forward to getting this setup.

I have the 24v/100a JBD BMS. The Bluetooth module connects to the left most white connector (UART), is it possible to utilize this driver with either the RS485 or RS232 pins so I can utilize Bluetooth simultaneously?