This program replaces readmess. It must run on pcdirac02 and it displays messages added to the file /home/run/log/monitoring.log by monitoring and SC code.
The script readinfo allows you to start, restart and stop the underlying code to display messages. To use it you must be logged in as run user.
Few fields are available for a message:
Message type | Font color | Background color | Sound |
---|---|---|---|
INFO | black | white | "Run is running", "Run stopped", "Run paused", ... or standard sentence "Monitoring message". |
WARNING | black | yellow | "Monitoring message", if there is no dedicated one. |
ALARM | white | red | "Monitoring message" , if there is no dedicated one. |
How often the code produces sounds and when a message will disappear
from a window depends on the button status, message type and predefined
period of window refresh (see table below). The last set to 5 s, it may
be change by recompiling the code only.
Message type | Pre sound | Disappears | Post sound |
---|---|---|---|
Info | Dedicated or "Monitoring message" only one time | As button pushed or just as time-out expired (40 s) | no sound |
Warning
Alarm |
"Monitoring message" until button will not be pushed with period of window refreshing | If button pushed and there was no the same message in a time-out (40 s) | "OK" |
If there is no active messages to be displayed the "Monitoring window" is closed. You can move the window but cannot close or re-size it. The window is opened on the active virtual display.
2. The simplest way to check is readinfo running: just do readinfo restart. You should hear a sound and see an opened window, of course if the loudspeakers are not disconnected by somebody, who feels her/himself an expert.
3. If you have no message at all, even when a run is started or stopped, it may be due to reasons: