The Alarms folder enables you to configure
alarm groups and tags related to each group. The Alarm worksheet
defines the alarm messages generated by the project. The primary
purpose of an alarm is to inform the operator of any problems or
abnormal condition during the process so he can take corrective
action(s).
The Alarm worksheet is executed by the Background Task
module (see
Execution Tasks). It handles the status of all alarms and save
the alarm messages to the history, if configured to do so, but it
does not display the alarm messages to the operator; the
Alarm/Event Control screen object, available on the Graphics
tab of the ribbon, must be created and configured in a screen in
order to display alarms.
To create a new Alarm worksheet, do one of the
following:
- On the Insert tab of the ribbon, in the Task
Worksheets group, click Alarm;
- Right-click the Alarms folder in the Project Explorer, and
then click Insert on the shortcut
menu; or
- Click New on the
Application menu, click the File
tab, and then select Alarm
Worksheet.
To edit an existing Alarm worksheet, double-click it
in the Project Explorer.
Figure 1. Alarm
worksheet
You can create multiple Alarm groups (worksheets) and
each group can be configured with independent settings, such as
message colors, history log enabled/disabled, and so forth.
Each Alarm worksheet is composed of two areas:
- Header: Settings
applied to all tags and alarms configured in the same alarm group.
These settings allow you to configure the formatting of the message
and the actions that must be triggered based on alarm events (e.g.,
print alarms, send alarms by email, and so forth). For more
information, see Header
Settings.
- Body: Configure alarm
messages and associate them to conditions linked to tags. For more
information, see Body
Settings.
CAUTION:
The settings configured in the body of
each Alarm worksheet are stored in the Tags Database archive(s).
Therefore, changes to the tags database may affect the content of
the Alarm worksheets (body). Notice that each tag/type cannot be
available in more than one Alarm group simultaneously because the
Alarm Group is a property associated to each Tag/Alarm Type (e.g.,
Tag: Level; Alarm Type: Hi; Alarm Group: 2).