Honeywell Series A - 3.3 Control Mode Interaction; Fieldbus block modes versus control modes

3. Fieldbus Integration With Experion System
3.3. Control Mode Interaction
R400 Experion PKS Series A Fieldbus Interface Module User's Guide 57
July 2010 Honeywell
Bit Quality Substatus, if Quality field is Limits
BAD UNCERTAIN
GOOD
(Non-
Cascade)*
GOOD
(Cascade)*
6
No Comm-
unication,
with no
Last
Usable
Value
Sub-Normal
Unacknow-
leged Critical
Alarm
Local
Override
(LO)
7
Out-Of-
Service
Fault-State
Active
(FSA)
8
Initiate
Fault-State
(IFS)
* The Good (non-cascade) substatus is used by output connections for fieldbus blocks
such as Analog Input and Discrete Input. The Good (cascade) substatus is used by output
connections for fieldbus blocks such as PID. Both of these substatuses are converted to
the single system data quality of Good.
Fieldbus status indications
REFERENCE - INTERNAL
Please refer to Fieldbus Status Display Indications in Appendix C for list of
possible display indications associated with a given fieldbus status and
definitions of related substatuses.
3.3 Control Mode Interaction
Fieldbus block modes versus control modes
Every fieldbus function block including Resource and Transducer blocks contain the
MODE_BLK parameter. This structured parameter consists of the Actual, Target,
Permitted, and Normal modes. The eight possible modes are described in the About
modes of operation paragraph in the Standard Function Blocks section of Appendix A.