Honeywell Series A - Fieldbus device Analog Output or PID integration

3. Fieldbus Integration With Experion System
3.2. Control Integration
46 Experion PKS Series A Fieldbus Interface Module User's Guide R400
Honeywell July 2010
uncertain is mapped to the appropriate Control Builder parameter of PVSTS,
PVSTSFL.NORM, PVSTSFL.BAD, or PVSTSFL.UNCER.
The fieldbus limit indications of no-limit, limited-low, limited-high, and constant are
mapped to the same four indications for Control Builder blocks.
The fieldbus data substatus indicator maps only the limited number of substatus
conditions that have corresponding Control Builder indications. Note that the
handshaking provided by the substatus associated with Good [cascade] status is not
supported from an upstream fieldbus device. This means that control may not originate
in the field and cascade into the Controller.
Fieldbus device Analog Output or PID integration
A
user can functionally "wire" the output from a regulatory control type function block
contained in a Control Module in the Control Builder application to the input of an
Analog Output (AO) or Proportional, Integral, Derivative (PID) function block in a
fieldbus device residing on an H1 link. The Proportional, Integral, Derivative (PID)
function block is a typical Control Builder regulatory control type function block.
The following simplified functional diagram shows how the output from a PID function
block in a Control Module that is assigned and loaded to the CEE in the Control
Processor Module (CPM) is integrated with an Analog Output function block in a
fieldbus compliant device.