I have created an EPICS IOC which reports any Guardian nodes which use source file(s) which have been modified in userapps but have not been loaded into the nodes. On the next restart of such nodes (e.g. guardian reboot) the new code will be automatically loaded, and so this system permits us to load new code in a scheduled and orderly way, for example by the code-author/node-manager during Tuesday maintenance.

This is similar to the front-end filter-module configuration file change (CFC) system, so I've called this GRD-CFC.

The CDS Overview MEDM has a "GRD CFC" button at the bottom showing the GRD-CFC status as GREEN/YELLOW. Pressing this button opens the H1CDS_GUARDIAN_CFC.adl MEDM (attached).

This MEDM has three main areas:

• Top is the system overview. the magenta box encompasses the CFC summary (it will be yellow if one of more nodes are in need of reloading), the STATUS shows the IOC status
• Middle is the main Guardian nodes table. The grey boxes will turn yellow if any node has one or more source files which need to be loaded
• Bottom is the IOC details section. the yellow box encompassing server start and runtime information. The red box encompasses the database files' validity.

If any nodes are reporting pending changes, you can get pending file details by running the shell command:

guardian_modified_not_loaded

The output from this command provides information on how to list the line differences between pending files and what is running.