The following snapshot shows data items that use the alarm feature:
# ------------------------------------------------------------------------ #
# - Alarm sample definition. - #
# ------------------------------------------------------------------------ #
Alarm MDS_RESTART_REQUEST, 0, , , 1
Alarm MDS_TURNOFF_REQUEST, 0, , , 1
Alarm MDS_APDOOR_ST, 0.5, , 2.5, 3.5
Alarm MDS_COUNT_RATE, 0, , 12000, 15000
Alarm MDS_HVPS_SET_VOLT_EU, -4.5, -0.25, , 0
An alarm is defined on a single line. The definition has the following syntax:
Alarm Name, Red Low, Yellow Low, Yellow High, Red High
It starts with the keyword: 'Alarm' followed by a unique name for the Alarm and the four comma separated limits for Red Low, Yellow Low, Yellow High, Red High. Not all limits need to be specified. If you only require some of the limits you can just leave the ones not required blank. However, you have to specify the commas.
The numeric value of the limits has to be in order, that is the following rule must be true for all limits specified:
Red Low < Yellow Low < Yellow High < Red High
In order for the alarm file to take effect you have to load it. This can either be done at startup with a Load entry in the gseos.ini file [Config] section or by manually loading the file at runtime. Select the file type 'Alarm Files (*.alarm)' in the File Open dialog box.
You can verify all loaded alarms with the GSEOS Explorer. Once an alarm is loaded you can use it in your screen definition to apply it to a data item.