self.publish_battery_dbus() crash, stops logging data about dbus-serialbattery HOT 4 CLOSED

Hi @mstealth22
These BMS will sometimes shutdown if a critical error happens and then cannot be contacted anymore until the problem is resolved. It mostly happens when the battery is close to full (or empty) and the cells are not balanced.

Check if you see any cell imbalance messages in the Victron VRM -> Alarm logs. If you do, then one of your cells have reached the limit you set up in in the BMS (using the App on your phone).
Also check what your SOC % are when you get this error.

If you do find that there are cell imbalance notifications, then setting the charge voltage lower for a few weeks should give the BMS a chance to balance the cells. You can do this override in the latest VenusOS versions under the DVCC. I suggest you use V13.4 (V3.35 x 4 cells). The default values for your BMS should be so that the cells will be balancing from V3.30.

from dbus-serialbattery.

Thanks for your reply. I checked cell balance, and the battery seems well balanced. I had done a top balance when building, and an active balancer hooked up for a number of charge cycles during buildout to make sure these balanced throughout the discharge curve. I have not confirmed errors recently, nothing in VRM Alarm Log for the Battery LTT. I've left the services installed, and every reboot of the VenusOs the LTT batter shows back up for a few hours, and then crashes, and is disconnected, presumably with the same error as before. It seems pretty predicable, 1-2 hours after a clean boot, and I don't see a correlation to Soc.

BMS doesn't seem to shutdown ever either, and the system seem to perform well overall. (though I've seen that in the past during initial build up) It's a hand off system right now, so I can't remotely get cell balance info (that I know of).

Is there anything else I can check here? Attached is a screenshot of the LTT info, after a reboot just now.

from dbus-serialbattery.

Hi @mstealth22
Your log show that the BMS gave no reply after being queried. So for some reason it is going into a shut down state.
The best would be to find out why that state happens, but I have added a few checks that should get you past the error you were seeing.

Try this build and let me know if it solves your error.
https://github.com/Louisvdw/dbus-serialbattery/releases/tag/v0.4beta2

from dbus-serialbattery.

There is a new build that should fix this issue.
https://github.com/Louisvdw/dbus-serialbattery/releases/tag/v0.4

from dbus-serialbattery.