I have a newly installed (not by me) system that works great except for one thing. Occasionally (2-3 times a day) the buzzer goes off and the cerbo reboots. The buzzer is hooked up to a contact on the bms, it beeps 2, maybe three times (the third beep is weak) pauses then beeps again. About this time the cerbo gx mk2 reboots. There is no loss in service, ac or dc.
I’m running v3.55 large image with signalk enabled (I just turned it off for the night to see if that’s the problem).
I checked to see if the vrm reboot on lost contact was enabled, it was not.
V3.55 is last stable release, V3.60 is currently beta.
This could be something on the BMS causing a low voltage (hence the beeps from the BMS) causing the Cerbo to reboot, or it could be the BMS beeping loss of comms, you need to determine which happens first. Without knowledge of the battery / BMS hard to tell. You could try and power the Cerbo independently to see if it is a power issue. There are also known problems with the VE Can port solved by V3.60 but I did not think this would cause the reboot.
I have my bms on ve1 and n2k on ve2. I disconnected the n2k and the crashing has stopped. I’ve heard a suggestion that it’s because ve2 is not galvanically isolated. I’m considering switching the ve1/ve2 loads.
I switched the networks so now the nmea 2000 network is on the galvanically isolated ve1, and the canbus with the alternator, bms and battery charger are on ve2. The instance numbers of all of victron devices changed, but that didn’t seem to have any ill effect. The cerbo no longer reboots and has been stable ever since I switched ve1/2.