@alexpescaru, thank you for the help and pointers. I am tied up for the next several days and won’t be able to dig in deep until this coming weekend.
I ran the uptime command spaced out over a period of time.
root@einstein:/etc# uptime
13:47:23 up 12:17, load average: 0.17, 0.81, 1.30
root@einstein:/etc# uptime
13:53:37 up 12:23, load average: 0.61, 0.98, 1.25
root@einstein:/etc# uptime
14:11:24 up 12:41, load average: 3.71, 2.25, 1.51
14:13:10 up 12:43, load average: 4.67, 2.83, 1.80
14:25:58 up 12:56, load average: 0.61, 1.01, 1.44
I will have to study the reported result and their meaning, but I gather that at 13:47:23 the load average was not that bad. Starting at 14:11:24 and forward, a load average of 4.67 is very high.
You mentioned changing the watchdog timer values to ‘10’. Would this mean changing both “max-load-5 = 6”, and “max-load-15 = 6” to ‘10’? Just want to be sure before I edit anything.
root@einstein:/etc# cat watchdog.conf
log-dir = /var/volatile/log/watchdog
min-memory = 2500
max-load-5 = 6
max-load-15 = 6
repair-binary = /usr/sbin/store_watchdog_error.sh
test-prescaler = 60
retry-timeout = 0
As I type this response out, I heard my heat pumps come on indicating a heavier load on my system. Although I am connected to 50-amp split phase shore power and so having all power passed through, I know that my Node Red flows are looking at the actual current flow and determining if any loads on the the system should be shed/turned off to reduce the current/power demands. I believe what you suggest about delaying some of the flow is aimed at addressing this loading. I will certainly look at that.
The basic reason I have Node Red running at all is to provide a load monitoring/load shedding function. These nodes look at current loading of my system and send http message to relays to disconnect or reconnect loads automatically as needed. These nodes just need to be able to monitor the system values and so could be moved to an external computer. What I don’t know is how the external computer would be able to monitor what is happening on the devices connected to the Cerbo.
I hope that this next question will make sense. To start by stating my understanding of my system, the Cerbo GX running the stock Venus OS software monitors my connected devices and provides some built in options for displaying what is currently happening via the gui, transmitting information via VRM to the cloud, and giving access to setting values for generator start/run/stop times, input current limits, etc. I make the assumption that the Victron Engineers make decisions and optimize the stock software so that it will run in the Cerbo without issues. Of course as new features are added, bugs crop up and fixes are released.
The Venus Large image which includes Node Red and Signal K add additional resources but cost additional CPU time and load.
The Venus software can be loaded onto other platforms such as a Raspberry Pi computer.
Now comes the lack of knowledge/lack of understanding question. If I ran the stock Venus software on the Cerbo and the Venus Large on a separate computer, would they run in parallel? Would they share information? Or would the Venus Large running on a more robust computer replace the Cerbo completely? The Cerbo seems to be set up to connect all of the different Victron systems together easily. How are the different devices, i.e. Multiplus II, MPPT, Smart Shunt, etc connected to an external computer.? I am sure that there might be more options that I have not thought of.
I appreciate your time and your help.