Processor Load Averages for the GRIDlink VT-IPM2M-113 ADR can be found in GRIDview View / Status
In general Load Averages should be less than 2 but can be higher when there are network communication errors introduced by wireless network, improper configuration or SSL errors when connecting to a server.
When the Load Averages are higher than 4 then Linux begins to shutdown selected less essential processes.
If Load Averages of 5-6 are reached, then higher level processes begin to shutdown and the GRIDlink will become symptomatic. One common example is that the Status page does not update in the time configured in Device / Settings.
A reboot command can be sent from GRIDview Device / Commands / Reboot the device as a temporary measure until the Patch can be loaded. Load Averages can start higher (2-3) in all GRIDlinks after a reboot and then settle down. The problematic units will increase slowly over time.
This patch, when downloaded using GRIDview, over-writes an internal setting of the Cycle Time which has a default value of 20 ms. This determines how fast the firmware scans the retained I/O. As complexity in the GRIDlink code increased from OADR 1.0 to 2.0 and features were added this became more of a problem. The new setting of 5000 ms dramatically reduces Load Averages without sacrificing performance.
All GRIDlinks that were online world-wide received this patch. If you are not sure and are seeing higher than normal Load Averages then contact Tech Support.
Experienced Toolkit users can set this parameters in the Advanced / Special Features section of the Toolkit configuration.