Alert Reporting; Plantweb Alerts Set Block Status; Setting Plantweb Alerts; Using Plantweb Alerts - Fisher FIELDVUE DVC6200f Instruction Manual

Instruction Manual
D103412X012

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.
Features Selected in the Resource block determines if reporting by the instrument is supported. Refer to page 47 for
additional information on Features Selected.
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 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 the PlantWeb Alerts Set PV Status (PWA_SET_STATUS [97]) parameter in the transducer block

Setting PlantWeb Alerts

Refer to table C‐2 for information on setting PlantWeb alerts. When selected, PlantWeb alarms will set the PV status
according to table C‐4.

Using PlantWeb Alerts

Refer to table C‐3 for information on using PlantWeb alerts.
PlantWeb Alerts
July 2013
277