Hi last week Matthijs released 3.70-2 beta to solve my VE.Can bus crashing problem. I’m running that release 4+ days and noticed this message this morning “System Load high, closing side panel to reduce CPU load” I don’t know what the side panel is per-say I usually leave the Overview screen open on my Cerbo.
I searched for other reports of this and see one user saying every time he lost AC power he would get this message on V3.55. We are onboard our boat anchored overnight and was on generator power for HVAC till this morning when I shut the generator down. It’s possible that message is related to losing AC power from the generator?
I used Putty to root into my Cerbo and search /var/log/messages for any reports of VE.Can daemon crashing and I saw none Yay! BUT I noticed uptime was 14 hours and went back through the logs and see my Cerbo crashed overnight. Not good, no Alarm or Event logged so IF I didn’t root in I wouldn’t have known. Reporting reboots is a good idea IMO!
Crashed was actually forced reboot due to load being too high so IDK was the Cerbo message from the loss of power or the forced restart overnight?
That system is indeed quite busy; approx 20% idle cpu on average while I was logged in. Which doesn’t leave much headroom, but also isn’t a problem.
There is one thing you might try - could require changing few configuration settings on your Cerbo GX MK2, but not much, which is to swap the canbus connections.
From what I’ve seen, you have you Victron VE.Can network on VE.Can port 1.
And the NMEA2000 network on VE.Can port 2.
Try swapping that around - I’d be interested also to login again after you’ve done that.
I expect that to reduce the CPU usage with quite a bit. Ie. 10% orso, perhaps more.
Also its probably better to that for the NMEA2000 network, because on your Cerbo GX MK2, the VE.Can 1 port is isolated, and VE.Can 2 port is not. And for NMEA2000 its best to use isolated can ports.
It would be interesting to know when you were logged on to my Cerbo as we were underway with our full compliment of navigation electronics powered on so the NMEA 2K traffic would have been at it’s peak IMO. We use Starlink while underway so your access was through Starlink but now we are on my house WiFi. We returned to our home dock about an hour ago and I just saw this note from you so I swapped the N2K connection to VE.Can1 and the BMS’s are now in VE.Can2. All our Navigation gear is powered down and the boat is in a relatively quiet/parked/docked state so have a look and share what you see…
Top is showing about 50% load
root@einstein:~# uptime
23:33:03 up 5:30, load average: 3.85, 4.19, 4.61
Though most relevant will be looking at it while your nav system cq. N2K network is all up and running and busy. And we’ve looked into it more; and indeed: processing CAN traffic on VE.Can 2 port is more CPU intensive than doing the same bus load on VE.Can 1. Reason is difference in hardware internally,
NP Matthijs, we have not had a Cerbo Crash nor any VECan bus errors in /var/log/messages since upgrading to the V3.70-2 so things are looking good here at the moment. When shelling into the Cerbo I typically see 25-30% idle time and the responsiveness of the system as a whole has been much better! FWIW this Friday is a holiday in the US and we will be out on the boat from about noon time Eastern Standard Time USA till Saturday afternoon so we should have lots of navigational electronics running. Would be a good time for your to check our system say Friday afternoon or Saturday morning if you wanted to check the system with more load than at the dock…
Hey, short update: I logged in just now. Looks like you have your N2K network up and running as I see a similar busload, but as expected its now on VE.Can port 1 instead of VE.Can port 2:
