3. Fieldbus Integration With Experion System
3.6. Notification Scheme
R400 Experion PKS Series A Fieldbus Interface Module User's Guide 73
July 2010 Honeywell
Fieldbus Alarm Priority Experion Alarm Priority Experion Alarm Severity
11 High 11
12 Urgent 12
13 Urgent 13
14 Urgent 14
15 Urgent 15
Advanced Alarming
Prior to R400
, diagnostic alarms were not supported.
With R400, FF devices are configured with a feature of configuring alarm conditions on
diagnostic parameters. The alarms that are generated are based on the status of these
parameters in a device. Individual bits in these strings are selected and configured as a
condition to generate the alarms. Therefore, the conditions that are used for generating
manufacturer-specific alarms are contained in bit string parameters of FF Transducer
blocks and Resource blocks. FIM monitors all the parameters in the condition to generate
corresponding alarms, which are activated with conditions and attached to the H1
connection.
Note: You can configure alarm conditions and save in the ERDB.
Considerations
Following are some of the considerations for configuring diagnostic parameters.
Each condition is associated with at most 5 parameters of a device.
You can select any combination of available bits.
Different conditions can utilize the same or different parameters/bits.
You can enable and disable the conditions at the template level and device level from
both Project and Monitoring modes.
Fieldbus Alarm Conditions
Fi
eldbus devices provide both process and device related alarms. The process alarms are
associated with process variable conditions and they are reported as process alarms into
the Experion system. The device alarms are associated with actual device conditions or
processes within the block as indicated by BLOCK_ERR and XD_ERROR bitstring
alarms. These alarms are reported as device or system alarms into the Experion
To Next Page
Loading...
