9.1.1
Alarm Definition
The alarms can be defined in the following screen
1. Group of alarms
2. Tag of group
3. Alarm number
4. Alarm text
5. History
6. Add button
7. Delete button
8. Accept button
9. Discard button
–
Each tag must have a unique group of alarms associated with it. There
can be 16 different groups of alarms.
–
A two byte tag for the defined group
–
The unique number of the alarm also indicating the position of the alarm
bit in the defined alarm tag
–
The text that is displayed as alarm text in the alarm window
–
If this option is selected then the defined alarm is also logged in the
memory as a historical alarm. There are two types of historical alarm:
History with Acknowledge - Whenever the alarm comes, this will get
added in the historical alarm container. And if the same alarm is already
present in the alarm container then the previous one will get overwrite by
the new one. At the same time, the acknowledgement task will be used
for considering the same alarm as a new event.
History without Acknowledge - Whenever the alarm comes, this will get
added in the historical alarm container. And if the same alarm is already
present in the alarm container then the new one will be considered as a
new alarm. The acknowledgement task will not be having any effect
–
Add a new alarm in the alarm definition window
–
Deletes selected alarm from the table
–
When user needs to change attributes of any defined alarm then he can
select the alarm, do the necessary changes & can press this button to
save the changes
–
This button acts as cancel button while doing changes to existing alarm.
Alarm
151