This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hello,
According to you in ESS, why when we just do a firmware update check from the VRM, all the producers cut off, disappear from the Cerbo and the Grid starts charging the batteries until everything reappears on the Cerbo?
I don't really see the link between a firmware check and the obligation to cut the producers, can someone explain it to me? Off the grid there can't be this switch !?!
Best regards
It is quite simple.The devices have to effectively be locked to scan/update firmware which means they can't be managed, so briefly stop producing. It is architectural and entirely normal.
It doesn't last long and no one should be scanning that often for it to be an issue.
As much as I can understand for an update, but just to read the current version, I find it a little surprising and unnecessary, especially since Cerbo has all the version numbers in its tablets since they appear well in VRM without clicking on the update button. This point seems to me to be perfectible because there is no interest in such a cutting impact to read a number.
The point of that feature is to run an update and a check is needed as the Cerbo version data is not constantly updated.
Ran it again on my own sites and it was a disruption of a few seconds. I doubt the investment in development time is worth the net impact it would have.
I can't say I have ever heard this particular issue raised before, so it can't be a major factor for many users.
If you want to avoid disruption, rather run the check outside of daylight hours.
Alternatively you can connect to them individually via victron connect.
