This started about 2 weeks ago and may have coincided with updating to Cerbo 3.71, but not positive.
The error is associated with my “Secondary” Multiplus, which is connected with a MK3-USB cable to my Cerbo GX.
I can see both MultiPluses and the BMS from the Cerbo, so this almost seems like a bug.
I have tried clearing the alarm and rebooting the Cerbo, however, the Secondary Multiplus was assigned a new CAN BUS number after rebooting (288 →289). This alone is a problem, as my Node-RED flows all of a sudden do not work, as they are pointing to the original assigned address.
As a test, I rebooted a few more times, and the number assigned continues to switch between 288 and 289.
Please let me know if there is anything else I can do to assist in getting to the bottom of this.
I think you mean VRM instances. These can be manually changed back, so as to avoid having to rewrite the code. This may be affected by future re-boots.
I think that it would be the Cerbo that generates the BMS lost alarm, rather than the muti, but have not played with 2nd multi systems.
Anyone at Victron have any input on this? I’m going to revert back to a prior CErbo firmware to see if that problem goes away to proof or dis=proof me be;eive that this is firmware related.