Table of Contents
Note
Additional details on setting up and
using Instrument Alerts can be found
on page 5-29 of this manual.
Alert Reporting
For PlantWeb alerts to be reported to the operator
console, they must pass four tests:
d
Alerts must be active
d
Reports must be selected in Feature Select
d
Alert priority must be greater than 1
d
Reporting must not be suppressed for those
conditions that caused active alerts.
Feature Select in the Resource block determines if
reporting by the instrument is supported. Refer to
page 5-5 for additional information on Feature Select.
Failed Priority (FAILED_PRI [68]), Maintenance
Priority (MAINT_PRI [69]), and Advise Priority
(ADVISE_PRI [70]) determine the PlantWeb alert
priorities. Although 16 priorities are available only
three are actually meaningful for PlantWeb alerts. If
the priority is 0, no reporting occurs. If the priority is 1,
reporting is simulated within the instrument, but the
alert is not actually reported over the bus. The alert
March 2006
PlantWeb
condition is reported for priorities 2 through 15, with
the higher priorities taking precedence over the lower
priorities.
Failed Suppress (FAILED_MASK [65]), Maintenance
Suppress (MAINT_MASK [66]), and Advise Suppress
(ADVISE_MASK [67]) determine which of the alert
conditions are suppressed so that they are not
reported.
PlantWeb Alerts Set Block Status
If a PlantWeb Alert is active, the AO or DO Block
Readback parameter status may change. This
behavior is controlled with Feature Select in the
resource block. Refer to page 5-5 for additional
information on Feature Select.
Setting PlantWeb Alerts
Refer to table 9-1 for information on setting PlantWeb
alerts. When selected, PlantWeb alarms will set the
PV status according to table 9-3.
Using PlantWeb Alerts
Refer to table 9-2 for information on using PlantWeb
alerts.
R
Alerts
9
9-3
Hide quick links:
Table of Contents
