Frequently freeze of TimeStamp

kevstone122 commented 1 year ago

Hello Tobi.

Thank you a loot for your great job with this driver. My Chargery is now running around 1 year, but there are still frequently problems with the driver. As i read also in the victron community, a lot of other people have the same issue with the freezing values. (https://community.victronenergy.com/questions/57416/chargery-bms-on-venus-os.html) In NodeRed i check all 30sec the TimeStamp and so i get an information if the value is frozen and then i need to reboot cerbo.

Is there any solution? Do you also have this problem? Can we implement a reconnect in the python script somehow? Disconnect USB cable and connect it back again will also not work in my case. So something with the reconnect we can improve together? I would also donate you something!

Thank you a lot for any feedback!

Best regards Kevin

Tobi177 commented 1 year ago

Hello Kevin,

while I doubt this can be improved, we can surely try to make it better. The first most important thing to ensure you have a galvanic isolation between your venus/cerbo and your Chargery. At the moment, I am using the Chargery 16BMS-P as the 16BMS-T have no accuracye voltage readings for me.

My Chargery hangs from time to time as well, maybe 2-3x within a year. I doubt a reconnect within the script will help to avoid this, as a reconnect of the USB port will not solve this issue. The only good thing is, that the Chargery is still working even, the rs232 port does not submit the values.

Currently, I would think there is no solution for this. Sometimes, the rs232 interface of the Chargery is just stucked. The galvanic isolation will helps a lot, but I will look into serial reconnection within the driver as well.

kevstone122 commented 1 year ago

Hello Tobi,

i am really happy to got an answer from you! My System has an Chargery 24S and i use it with 17 cells. My mothers house has standard 16S system. Both have direct in the USB Slot from the cerbo an Isolation USB Adapter. In this adapter the RS232 is connected to the SUB D. After the SUB D i already have an Opto-Coupler part and after this there is the Chargery. Like you wrote, the isolation is really important and it is already improved a lot, but still every month it happen.

Okay i never thought, that chargery is the problem. From my point of view it happen because of cerbo. A short milli second the USB has problem and after this it cannot start again. Chargery is still sending data. I just restart the Cerbo always. BMS is 1 year running without reboot!

I found out, that the python script will close successfully with the disconnect and then if it will connect again, there is a message like "device already registered at D-bus". So i think the only problem is the D-bus where we need to delete the chargery BMS...

If chargery will not send any data, then also the script should not get stock. So maybe we can find these situations and add it into the python, then the script can handle it somehow and will change into a waiting mode for 5 sec and then start again to collect data.

Thanks for comunication, where i should donate you for this help. I loove the victron system, but with this blocking every month its not really nice if you want to do it also at friends.

Best regards Kevin

kevstone122 commented 1 year ago

Additional: If i take out the Serial Adaoter from the USB Slot of the cerbo and connect it back, it will not work.. So this is the main issue. If this will work (easy to test), then it will maybe also work with the short interrupts and the usb get registered automatic again.

There is also öike an STOP script which is empty. Maybe we should use this to cancel the Dbus registration. Then with reconnect of USB it can register again with the same name.

Best regards Kevin

kevstone122 commented 1 year ago

Hello Tobi,

where can i donate for your help?

Thank you a lot! Best regards Kevin

Tobi177 commented 11 months ago

Thank you for your valuable feedback! This is really much appreciated. We do think you have "forced" a new error while connecting/disconnecting the USB slot. And yes, there was an error that the driver does not close properly on an exception. The driver hangs forever - until reboot. By now, we have uploaded a new version which ensures to exit properly on exceptions. The Venus OS will restart the driver automatically some minutes later again. This is an improvement, but unfortunately we do still think this will not solve all problems with the Chargery hangups. However, it would be great if you check the new version and report back if it is improve your experience.