Rockwell Automation 9301 Series RSView32 Users Guide - Manual (Page 146)

6–20

RSView32 User’s Guide
How event–based alarms work
Alarm events let you create alarms, even without setting up tags in the
tag database. Event–based alarms work just like tag–based alarms.
They appear in alarm summaries, they can be used with alarm system
tags, and they can be logged to disk or printer.
You can filter event–based alarms the same way you filter tag–based
alarms in alarm summaries. You can acknowledge event–based alarms,
either individually, or with wildcards, using the Acknowledge
command. You cannot suppress event–based alarms.
You can time–stamp event–based alarms with the current time, or by
specifying a date and time, either in RSView32 or in your own alarm
detection algorithms.
Alarm events are not processed until the AlarmOn command is
issued, and alarm events are no longer processed after the AlarmOff
command is issued.
Differences between event–based alarms and tag–based
alarms
You cannot specify thresholds for analog alarm events. All analog
alarm events have a value of zero.
You cannot specify alarm labels for event–based alarms. That is, you
cannot use the IntoAlarm and OutOfAlarm labels for digital tag–
based alarms, or the threshold labels for analog tag–based alarms.
Alarm events have no acknowledge and handshake bits.
The Identify feature is not available to event–based alarms, to run a
command, macro, or VBA program.
Event–based alarms are not retentive across project starts or stops.