Using PlantWeb Alerts
December 2009
C-3
When a shutdown condition exists (either
currently active or latched on through the shutdown
recovery parameter) in the transducer block, alerts are
reported even though the mode of the transducer
block is OOS.
Refer to table C-1 for reporting of PlantWeb Alerts.
Alert Handling
Alert handling is diagrammed in figure C-1. There are
two ways of seeing PlantWeb alerts. One way is to
see if the instrument alert condition causing a
PlantWeb alert is detected. The second is to view
alerts reported to the system operator console. For a
PlantWeb alert to be active, it has to pass four tests.
The first is to check if the Instrument alert condition is
enabled. If a condition is not enabled, the instrument
does not check for the alert condition.
Second, the condition that will cause an alert must
exist. For example, the current travel is above the
Travel Limit Hi Alert Point.
Third, the corresponding PlantWeb alert must be
enabled in one or more of the three categories: Failed,
Maintenance or Advise.
Fourth, the transducer block mode must be correct.
See table C-1
Note
Additional details on setting up and
using Instrument Alerts can be found
on page 4-26 of this manual.
Alert Reporting
For PlantWeb alerts to be reported to the operator
console, they must pass four tests:
Alerts must be active
Reports must be selected in Feature Select
Alert priority must be greater than 1
Reporting must not be suppressed for those
conditions that caused active alerts.
Table C-1. PlantWeb Alerts Reporting Requirements
PlantWeb Alert Transducer Block Mode (Actual)
Drive Current AUTO
Drive Signal AUTO
Processor Impaired Any Mode
Output Block Timeout Any Mode
Block Set to Defaults Any Mode
Travel Sensor AUTO
Output Pressure Sensor Any Mode
Supply Pressure Sensor Any Mode
Temperature Sensor Any Mode
Supply Pressure AUTO
Temperature Limit AUTO
Travel Deviation AUTO
Travel Limit AUTO
Cycle Counter AUTO
Travel Accumulator AUTO
Performance Critical AUTO
Performance Reduced AUTO
Performance Information AUTO
Pressure Fallback AUTO
Feature Select in the Resource block determines if
reporting by the instrument is supported. Refer to
page 4-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
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.
C
To Next Page
Loading...
Need help?
General
