We have more and more Installations, where on a more or less frequent basis the “BMS lost” alarm is thrown. Reboot sometimes helps for hours/ days, sometimes only for a few minutes until the battery is lost again. Our customers are starting to get upset and we are running out of options calming them down.
Installations are not new, some are months old and have been running flawlessly.
Update to 3.60 seems only to have accelerated the problem.
Anybody willing to take a look? Would be highly appreciated.
@Victron staff need: VRM-IDs to take a look remotly?
Hi, Welcome.
Any particular GX device or battery?
Just a reminder this isn’t a support site, you should as a supplier or via your supplier have access to L3 support.
The support link is in the community guidelines but, provide a little more detail and we will try help.
two different types of batteries, both LV, one would be Pylontech, the other Voltsmile. The current problemchild is still in the workshop, the prime example for Pylontech is with the customer at a critical installation beeing a backup power system.
Thanks for reminding me of the fact that this is not a support site. I am aware of the fact - anyway before getting any other support we are requested to go this channel.
I am not new to this community - lost all my old entries when the old forum was closed.
Thanks, are the GX’s a mix or a specific model like the CCGX which has known issues with 3.60.
CPU load increased with 3.60 so if thats a variable it would make it worse.
You are welcome to load some example ID’s here (just the numbers in the URL please).
For the most part 3.60 fixed the known CAN issues particularly for the cerbo mk2.
Sorry about the account, there was no way to transfer them across platforms.
they are Cerbo MK2.
One ID, the device still in the workshop, to try would be: 782342
Connected to a batterypack that has a working record (we used it and I crosschecked with another Cerbo) using a cable that is original and works on the other device.
after investigation, one system consisted of an Cerbo GX MK2 that had been having issues; which was fixed by updating to v3.60. Its the Cerbo GX MK2 VE.Can port 2 issue.
two Ekrano GXes that run really stable. Also at v3.60.
What we’ve seen there matches the more global statistics that we’re seeing on VRM: v3.60 is running real stable, and for Cerbo GX MK2 its, as expected, even running more stable than prior versions.
Most of this issues were a one time initialization that happens after installing v3.60 - and that won’t happen again, also not when installing a future update.