Notification Scheme; Fieldbus Versus Experion Alarm Priorities - Honeywell Series A User Manual

The FIM constantly monitors the live list for each fieldbus link connected to it. When the
LAS for the link recognizes a new device at a default address, it adds it to its live list
according to the data link layer procedures. The FIM detects the change in the live list
and makes a connection to the new uncommissioned device. It gathers the following
information from the device to be passed to Control Builder.
Name
PdTag
Address
DevID
Vendor
ModelName
Rev
ManufID
DevType
DevRev
DdRev
Control Builder uses the device information to create an item in its Monitoring tree to
represent the new uncommissioned device on the given link. Users can now view and
configure pertinent information for the uncommissioned device through appropriate Link
block and device block configuration forms in Control Builder.
TIP
The FIM must be configured and loaded through Control Builder before you
can view it and its links through the Monitoring tab of Control Builder.
3.6

Notification Scheme

Fieldbus versus Experion Alarm Priorities

The fieldbus alarms will be closely integrated with the existing Experion notification
system. The Experion Server will handle FIM alarms in the same way it handles Control
R400 Experion PKS Series A Fieldbus Interface Module User's Guide
July 2010
3. Fieldbus Integration With Experion System
Description
Physical Device Tag
Device Address
Globally unique Device Identifier
Vendor name string
Model Name string
Application Revision
Manufacturer Identifier
Device Type code
Device Revision
DD Revision
Honeywell
3.6. Notification Scheme
Data Type Access
32-byte string Read/Write
Unsigned8 Read/Write
32-byte string Read Only
32-byte string Read Only
32-byte string Read Only
32-byte string Read Only
Unsigned32 Read Only
Unsigned16 Read Only
Unsigned8 Read Only
Unsigned8 Read Only
71