B0193AW

REV R

I/A Series A2™ System

Integrated Control Software Concepts
March 28, 2003

CONFIGURATOR

COMPOUND COMPOUND COMPOUND

1 2 n

BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK

= Control Processor

PROCESS
Invensys, Foxboro, FIO, FoxCom, EXACT, I/A Series, INTERSPEC, Micro-I/A, SPECTRUM and UFM are
trademarks of Invensys plc, its subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 1990-2003 Invensys Systems, Inc.

All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures................................................................................................................................. xiii

Tables.................................................................................................................................... xv

Preface.................................................................................................................................. xix
Revision Information ............................................................................................................. xix
Reference Documents ............................................................................................................ xix

1. Introduction ...................................................................................................................... 1

2. Compounds and Station Blocks......................................................................................... 3

Compound Functions ............................................................................................................... 4
Compound/Block Process Alarming .......................................................................................... 5
Compound/Block Phasing ........................................................................................................ 5
Compound Attributes ............................................................................................................... 5
Compound Access ..................................................................................................................... 6
Compound/Block Parameters ................................................................................................... 6
Configurable Parameters ...................................................................................................... 6
Connectable Parameters ....................................................................................................... 6
Input Parameters ............................................................................................................. 7
Output Parameters .......................................................................................................... 7
Nonconnectable Parameters ................................................................................................. 7
Compound Parameters ......................................................................................................... 8
The Station Compound/Block .................................................................................................. 8
Dynamic Loading Calculations ............................................................................................ 8
Dynamic Overrun Variables ................................................................................................. 9
Dynamic Free Memory Variable .......................................................................................... 9
Peer-to-Peer Status ............................................................................................................... 9
Database Security ............................................................................................................... 10
Time/Date ......................................................................................................................... 10
Station Block Parameters .................................................................................................... 10
Shadow Parameters .................................................................................................................. 10

3. Blocks.............................................................................................................................. 13
Block Attributes ...................................................................................................................... 13
Block Access ............................................................................................................................ 13
Approximate Block Sizes ......................................................................................................... 14
Block Parameters ..................................................................................................................... 14

iii
B0193AW – Rev R Contents

Common Parameters .......................................................................................................... 14

Editing Parameters ............................................................................................................. 16
Block Function Types ............................................................................................................. 16
Matrix – Blocks versus Stations .......................................................................................... 23
Supervisory Set Point Control (SSC) .................................................................................. 29

4. Block Characteristics ....................................................................................................... 31

Block Initialization .................................................................................................................. 31
Implicit Initialization ......................................................................................................... 31
Explicit Initialization .......................................................................................................... 32
Introduction .................................................................................................................. 32
PRIBLK Parameter ........................................................................................................ 33
Configuring Cascade Schemes ................................................................................................. 37
Standard Cascade Configuration ........................................................................................ 37
External Integral Feedback ................................................................................................. 39
Error Handling ....................................................................................................................... 40
Clamping ................................................................................................................................ 41
Scaling .................................................................................................................................... 41
Secure/Release ......................................................................................................................... 42
Control Block Fail-safe Strategy .............................................................................................. 42
PID Hold Constraint .............................................................................................................. 43

5. Block States ..................................................................................................................... 45

Shutdown State ....................................................................................................................... 45
Define State ............................................................................................................................ 46
Bad State ................................................................................................................................. 46
Bad Detection .................................................................................................................... 46
Manual/Auto States ................................................................................................................. 48
BLKSTA – the Block Status Parameter ................................................................................... 49
Block Status ............................................................................................................................ 51
Status Indicators ................................................................................................................. 51
Status Events ...................................................................................................................... 53

6. Connections .................................................................................................................... 55
Shared Variables ...................................................................................................................... 55
Linkage Syntax ........................................................................................................................ 56
Boolean Connection Extensions .............................................................................................. 56
Connections to Source Data ............................................................................................... 57
Connections to Source Status ............................................................................................. 59
Connections to Status Parameters ....................................................................................... 59
Packed Boolean Connection Extensions .................................................................................. 62

iv
Contents B0193AW – Rev R

Defaults for Integer and Real Connections .............................................................................. 63

Mixed Data Types ................................................................................................................... 63

7. Block Processing.............................................................................................................. 67
Scanning ................................................................................................................................. 68
Scan Overrun ..................................................................................................................... 68
Block Phasing ..................................................................................................................... 68
Relationship Between Block Period and Phase .................................................................... 69
Scan Overload ............................................................................................................... 70
Block Phasing: Cautions and Guidelines ....................................................................... 72
Input/Output (I/O) Blocks ..................................................................................................... 73
I/O Block Processing .......................................................................................................... 73
I/O Block Status ................................................................................................................. 74
I/O Block Validation .......................................................................................................... 74
I/O Fail-safe Status ............................................................................................................. 74
Redundant I/O Blocks ....................................................................................................... 74
Redundant Input Block (AINR) .................................................................................... 74
Redundant Output Block (AOUTR) ............................................................................ 75
Input Signal Conditioning ...................................................................................................... 75
Filtering ............................................................................................................................. 77
First or Second-Order .................................................................................................... 77
Contact Filtering ........................................................................................................... 77
Output Signal Conditioning ................................................................................................... 77

8. Block/Process Alarming................................................................................................... 79
Alarming Overview ................................................................................................................. 79
Process Alarm Generation .................................................................................................. 80
Common Process Alarm Features ............................................................................................ 80
Common Process Alarm Parameters ................................................................................... 81
Alarm Messages .................................................................................................................. 82
Alarm Status Parameter (ALMSTA) ................................................................................... 83
Alarm Option Parameter (ALMOPT) ................................................................................ 84
Criticality and Priority Type .............................................................................................. 85
Alarm Inhibition ................................................................................................................ 86
INHALM ...................................................................................................................... 87
INHIB .......................................................................................................................... 88
INHOPT ...................................................................................................................... 88
CINHIB ........................................................................................................................ 89
INHSTA ....................................................................................................................... 89
Process Alarm Types ............................................................................................................... 90
Absolute Alarming .............................................................................................................. 91
High Absolute Alarming/High Output Alarming .......................................................... 92
Low Absolute Alarming/Low Output Alarming ............................................................. 92
Bad Input/Output Alarming .............................................................................................. 93
Deviation Alarming ............................................................................................................ 93

v
B0193AW – Rev R Contents

High Deviation Alarming .............................................................................................. 94

Low Deviation Alarming ............................................................................................... 95
Mismatch Alarming ........................................................................................................... 95
Out of Range Alarming ..................................................................................................... 95
Rate Of Change Alarming .................................................................................................. 96
Sequence Operational Error Alarming ................................................................................ 97
State Change Alarming ...................................................................................................... 97
Trip Alarming ................................................................................................................... 98

9. Ladder Logic Concepts .................................................................................................... 99

Ladder Logic Overview ........................................................................................................... 99
Ladder Diagram Functions ................................................................................................. 99
PLB Functions ................................................................................................................. 100
Ladder Diagram Description ................................................................................................. 101
Ladder Diagram Display .................................................................................................. 103
Ladder Diagram Execution ............................................................................................... 103
Ladder Diagram Construction .......................................................................................... 103
Symbols ....................................................................................................................... 104
Text and Numeric Entries ........................................................................................... 105
Ladder Diagram Elements ..................................................................................................... 107
Inputs (Contacts) ............................................................................................................ 107
Outputs (Coils) ................................................................................................................ 108
Counters and Timers ........................................................................................................ 109
Transition Counters .................................................................................................... 111
Retentive Timers ......................................................................................................... 111
Non-Retentive Timers ................................................................................................. 113
Timer/Counter Reset (RST) ........................................................................................ 113
Connector Symbols .......................................................................................................... 114
Blank Positions ................................................................................................................. 114
Program Flow Control ..................................................................................................... 114
Master Control Relay (MCR, NCR) ........................................................................... 115
Zone Control Logic (ZCL, NCL) ................................................................................ 115
Special Purpose Coils ....................................................................................................... 116
Initialization (INIT) .................................................................................................... 116
Communication Failure (COMMF) ........................................................................... 116
Power Fail (POWERF) ................................................................................................ 117
Fail-safe (FAILSF) ....................................................................................................... 117
Fanned Outputs .................................................................................................................... 117
Simple and Nested ZCLs ...................................................................................................... 118
Ladder Diagram Constraints ................................................................................................. 120
Programmable Logic Block Operation .................................................................................. 122
Ladder Logic Operation ........................................................................................................ 123
Ladder Logic Scan Cycle .................................................................................................. 124
Scan Phase 1 – Command Processing .......................................................................... 124
Scan Phase 2 – Inputs .................................................................................................. 125

vi
Contents B0193AW – Rev R

Scan Phase 3 – Ladder Solution ................................................................................... 125

Scan Phase 4 – Outputs ............................................................................................... 125
Ladder Logic Modes of Operation .................................................................................... 126
Ladder Logic Status Byte .................................................................................................. 126
Run Flag ...................................................................................................................... 127
Test Flag ...................................................................................................................... 127
Connect Flag ............................................................................................................... 127
Fail-safe Flag ................................................................................................................ 127
Hold Flag .................................................................................................................... 128
Single Scan Flag ........................................................................................................... 128
INIT Flag .................................................................................................................... 128
Logic Machine Error Flag ............................................................................................ 128
PLB Editor Overview ........................................................................................................... 128
Configuration Example ......................................................................................................... 129

10. Sequence Logic ............................................................................................................ 133

Sequential Control Blocks ..................................................................................................... 133
Sequence Block ................................................................................................................ 133
Monitor Block .................................................................................................................. 137
Timer Block ..................................................................................................................... 137
Sequential Control Block States ............................................................................................ 138
Application States ............................................................................................................. 138
Auto State .................................................................................................................... 139
Semi-Auto State ........................................................................................................... 139
Manual State ............................................................................................................... 139
Auto/Manual Transitions ............................................................................................ 141
Sequence States ................................................................................................................ 141
Active State .................................................................................................................. 142
Inactive State ............................................................................................................... 142
Active/Inactive Transitions .......................................................................................... 142
Paused State ................................................................................................................ 142
Tripped State ............................................................................................................... 142
Transition States .............................................................................................................. 143
To_Inactive State ........................................................................................................ 143
To_Manual State ......................................................................................................... 143
To_Paused State .......................................................................................................... 143
Compound Sequence State ................................................................................................... 143
Sequence Processing .............................................................................................................. 144
Sequence Processing Overrun ........................................................................................... 145
Useful Hints on SBX Programming ...................................................................................... 145
Operational Error SBXs .................................................................................................... 145
SBX RETRY Logic ........................................................................................................... 147
Operational Error Conditions Inside Subroutines ............................................................ 148
Operational Error Condition Inside State Change SBX .................................................... 149
Complex Statements ......................................................................................................... 149
Usage of the SUBR_LEVEL Standard Parameter ............................................................. 150

vii
B0193AW – Rev R Contents

11. Integrated Control Configurator Concepts.................................................................. 151

Configuration Aids ................................................................................................................ 151
Help Screens .................................................................................................................... 152
Parameter List .................................................................................................................. 152
Sequential Control Block Reference Information ............................................................. 152
Hardware Interface ................................................................................................................ 152
User Interface ........................................................................................................................ 152
Software Interface ................................................................................................................. 152
Compound Summary Access ............................................................................................ 153
Software Processing .......................................................................................................... 153
System Monitor Interface ................................................................................................. 153
Control Processor Database Installer ................................................................................ 154
Configuration Target ............................................................................................................ 154
Control Station Configuration ......................................................................................... 154
Library Volume Configuration ......................................................................................... 154
Compound Configuration ................................................................................................ 154
Copying Compounds Between Configuration Targets .......................................................... 155
Checkpoint Files ................................................................................................................... 155
Compound and Block Name Conventions ............................................................................ 155
Compound Names ........................................................................................................... 155
Block Names .................................................................................................................... 155
Configurator Editing Modes ................................................................................................. 156
Active Editing .................................................................................................................. 156
Inactive Editing ................................................................................................................ 156
Configuration Validation ...................................................................................................... 157
Programmable Logic and Sequential Control Block Source Files ........................................... 158

12. Control Processor (CP)/Fieldbus Application Interface ............................................... 159

The Interfaces – FBMs, FBCs, or FCMs and ECBs .............................................................. 159
I/O Fail-safe Strategy ........................................................................................................ 162
Cold Start .................................................................................................................... 163
Placing the FBM On-Line ........................................................................................... 163
FBM Exits the Fail-safe State ....................................................................................... 163
The Fail-safe Configuration ......................................................................................... 163
Events Leading to Fail-safe ............................................................................................... 164
FBM Reboot ............................................................................................................... 165
Communications Failure (Commfail) .......................................................................... 165
EEPROM Update ....................................................................................................... 165
FBM Taken Off-Line From the SMDH ...................................................................... 166
Power Failure (Powerfail) ............................................................................................ 166
FBM Restart ................................................................................................................ 166
Fieldbus Scanning ................................................................................................................. 167
Fieldbus Integration Time ..................................................................................................... 167

viii
Contents B0193AW – Rev R

FBM201 to FBM205 and FBM211 to FBM213 .............................................................. 167

FBM01 to FBM05 ........................................................................................................... 168
Cluster I/O ....................................................................................................................... 168
FBM Rate of Change Monitoring ......................................................................................... 168
FBM and FBC Types ............................................................................................................ 169
Equipment Control Blocks (ECBs) ....................................................................................... 169
Diagrams – ECB Interfaces to I/O Blocks and FBMs or FBCs .............................................. 171
Sample DIN Rail Mounted FBM Diagrams ..................................................................... 171
Sample FBMxx & Equivalents and FBC Diagrams .......................................................... 177
Sample FBC Connection Diagrams .................................................................................. 182
Window Equipment Control Blocks ..................................................................................... 183
General Window ECB Concepts ........................................................................................... 183
Overview .......................................................................................................................... 183
Configuration ................................................................................................................... 184
Installation ....................................................................................................................... 184
Validation .................................................................................................................... 184
Initialization ................................................................................................................ 184
Real Time Input Points ............................................................................................... 185
Real Time Output Points ............................................................................................ 186
Shutdown .................................................................................................................... 187
Alarming ..................................................................................................................... 187
Device States and Status .............................................................................................. 187
Individual Window ECBs ..................................................................................................... 188
The Hydrostatic Tank Gauge ECB (ECB13) ................................................................... 188
Overview ..................................................................................................................... 188
HTG ECB Default Displays ........................................................................................ 189
Installation and Configuration ..................................................................................... 189
Real Time Inputs ......................................................................................................... 189
Alarm Set Points .......................................................................................................... 190
Real Time Outputs ...................................................................................................... 190
Gas Chromatograph Window ECB (AMSPRI and AMSSEC) ......................................... 191
Mass Flow Transmitter Window ECB (ECB22) .............................................................. 191
Intelligent Transmitter Window ECB (ECB18) ............................................................... 191
Cluster I/O Window ECB (ECB47) ................................................................................ 192

Appendix A. Signal Conditioning Indexes ......................................................................... 193

Input Signal Conditioning .................................................................................................... 193
FBM Input Signal Conditioning ...................................................................................... 193
Linear and Nonlinear Signal Conversion (FBM) ......................................................... 193
Pulse Rate (FBM) ........................................................................................................ 195
Thermocouples (FBM) ................................................................................................ 196
(FBM) Resistance Temperature Detectors (RTDs) ...................................................... 197
Standard Conversion Tables (for FBMs) ...................................................................... 198
SCIs for Micro-I/A Software Release 6.2.1 (or greater), AW51, and AW70 ...................... 199
SCIs for Micro-I/A Pre-6.2.1 Software Releases, and the Allen-Bradley Station ................ 199

ix
B0193AW – Rev R Contents

Output Signal Conditioning ................................................................................................. 200

SCOs for FBMs, FBCs, and Devices ................................................................................ 200
SCOs for Micro-I/A Software Release 6.2.1 (or greater), AW51, and AW70 .................... 202
SCOs for Micro-I/A Pre-6.2.1 Software Releases, and the Allen-Bradley Station .............. 203

Appendix B. Fieldbus Modules.......................................................................................... 205

Fieldbus Module Types (FBMs) ............................................................................................ 205
FBM201 (0 to 20 mA Inputs) .......................................................................................... 205
FBM202 (Thermocouple/mV Inputs) .............................................................................. 206
FBM203 (RTD Inputs) .................................................................................................... 207
FBM204 (0 to 20 mA Inputs/Outputs) ............................................................................ 208
FBM205 (Redundant 0 to 20 mA Inputs/Outputs) ......................................................... 209
FBM206 (Pulse Inputs) .................................................................................................... 209
FBM207(Contact/dc Inputs) ........................................................................................... 209
FBM211(16-Channel Differential-Isolated 0 to 20 mA Inputs) ....................................... 210
FBM212 (14-Channel Differential-Isolated Thermocouple Inputs) ................................. 211
FBM213 (8-Channel Differential-Isolated RTD Inputs) .................................................. 212
FBM214 (HART Communication Input Interface Module) ............................................ 213
FBM215 (HART Communication Output Interface Module) ......................................... 213
FBM216 (HARTTM Communication Redundant Input Interface Module) ................... 213
FBM217 (32-Channel Group-Isolated Voltage Monitor Inputs) ...................................... 214
FBM218 (HART Communication Redundant Output Interface Module) ...................... 214
FBM219 (32-Channel Group-Isolated Discrete I/O Module) .......................................... 215
FBM220/221 FOUNDATION fieldbus H1 Communications Interface Module ............ 215
FBM223 (PROFIBUS-DP Communication Interface Module) ....................................... 215
FBM224 (Modbus Communication Interface Module) ................................................... 216
FBM237 (Channel Isolated, Redundant-Ready 0 to 20 mA Outputs) .............................. 216
FBM241 (Contact/dc Inputs/Outputs) ............................................................................ 217
FBM242 (Digital Outputs) .............................................................................................. 218
FBM243 (Channel Isolated FoxCom Dual Baud Rate Intelligent
Device Interface Module) ................................................................................................. 218
FBM246 (Channel Isolated FoxCom Redundant Dual Baud Rate
Intelligent Device Interface Module) ................................................................................ 219
FBM01 (0 to 20 mA Inputs) ............................................................................................ 219
FBM02 (Thermocouple/mV Inputs) ................................................................................ 220
FBM03A ([3-wire] and 03B [4-wire] RTD Inputs) .......................................................... 221
FBM04 (0 to 20 mA Inputs/Outputs) .............................................................................. 222
FBM05 (0 to 20 mA Inputs/Outputs) for Redundant Applications .................................. 223
FBM06 (Pulse Inputs, 0 to 20 mA Outputs) .................................................................... 224
FBM17 (0 to 10 V dc, Contact/dc Inputs/Outputs) ......................................................... 224
Analog Signals ............................................................................................................. 224
Digital Signals ............................................................................................................. 224
Analog Signal Specifications ........................................................................................ 226
Digital Signal Specifications ........................................................................................ 226
FBM18 (Intelligent Transmitter Interface) ....................................................................... 226
FBM07/12 (Contact/dc Inputs and Expansion Inputs) .................................................... 227
FBM08/13 (120 V ac Inputs and Expansion Inputs) ........................................................ 228
FBM09/14 (Contact/dc I/O and Expansion I/O) ............................................................. 229

x
Contents B0193AW – Rev R

FBM10/15 (120 V ac I/O and Expansion I/O) ................................................................ 230

FBM20/21 (240 V ac Inputs and Expansion Inputs) ........................................................ 231
FBM11/16 (240 V ac I/O and Expansion I/O) ................................................................ 232
FBM33A (3-wire RTD Inputs) and 33B (2- and 4-wire RTD Inputs) ............................. 232
FBM36 (Thermocouple/mV Inputs) ................................................................................ 233
FBM37 (0 to 20 mA Outputs) ......................................................................................... 234
Cluster I/O FBCs ............................................................................................................. 235

Appendix C. FBM – ECB Cross Reference........................................................................ 237

Legacy FBMs and Equivalents .......................................................................................... 237
Fieldbus Processors ........................................................................................................... 242
Eckardt I/O Cards ............................................................................................................ 243
UCM/UIO ...................................................................................................................... 244
FIO .................................................................................................................................. 245
UFM ................................................................................................................................ 246
Fisher Series 20 Migration Cards ...................................................................................... 247
DIN 200 FBMs and Equivalents ...................................................................................... 248
Honeywell TDC2000 Migration Cards ............................................................................ 252
Honeywell TDC3000 Migration Cards ............................................................................ 256
FCMs and Equivalents ..................................................................................................... 257

Index .................................................................................................................................. 259

xi
B0193AW – Rev R Contents

xii
Figures
2-1. Compound/Block Relationship ..................................................................................... 4
3-1. Block Access ................................................................................................................ 14
3-2. Supervisory Set Point Control Concept ....................................................................... 30
4-1. PRIBLK Cascade Standard Configuration .................................................................. 32
4-2. PRIBLK Cascade Standard Configuration .................................................................. 37
4-3. Cascade Block Strategy with Feedback Control ........................................................... 38
4-4. Cascade Handling Between Two Compounds Across Stations .................................... 39
4-5. Cascade Block Strategy with Feedforward Control ...................................................... 39
5-1. Bad Detection ............................................................................................................. 47
5-2. Block State Transition Diagram .................................................................................. 49
7-1. The Basic Processing Cycle ......................................................................................... 67
7-2. Example of Phased Execution ...................................................................................... 70
7-3. Phase Zero Overload ................................................................................................... 70
7-4. Example of Overrun .................................................................................................... 71
7-5. Avoiding Overrun ....................................................................................................... 71
7-6. Input Signal Conditioning .......................................................................................... 75
7-7. Output Signal Conditioning ....................................................................................... 77
8-1. Block Alarming ........................................................................................................... 79
8-2. INHIB, INHALM, and INHOPT Behavior ............................................................... 87
8-3. Absolute Alarming ...................................................................................................... 91
8-4. Deviation Alarming ..................................................................................................... 94
8-5. Out of Range Alarming ............................................................................................... 96
8-6. Rate of Change Alarming ............................................................................................ 96
9-1. Ladder Logic Components (Simplified) ...................................................................... 99
9-2. Simplified Ladder Logic Diagram ............................................................................. 101
9-3. Ladder Logic Contacts .............................................................................................. 102
9-4. Ladder Logic Connectors .......................................................................................... 102
9-5. Parallel Circuits in Ladder Logic ............................................................................... 102
9-6. Typical Ladder Diagram Display ............................................................................... 103
9-7. Ladder Diagram Work Area ...................................................................................... 104
9-8. Sample Ladder Diagram ............................................................................................ 106
9-9. User-Defined Labelling ............................................................................................. 107
9-10. Retentive Time-On Delay Timing Chart .................................................................. 112
9-11. Retentive Time-Off Delay Timing Chart .................................................................. 113
9-12. COMMF Contact ..................................................................................................... 116
9-13. Fanned Outputs ........................................................................................................ 117
9-14. Zone Control Logic .................................................................................................. 118
9-15. Zone Control Logic (Continued) .............................................................................. 118
9-16. Zone Control Logic (Continued) .............................................................................. 119
9-17. Nested Zone Control Logic ....................................................................................... 119
9-18. Nested Zone Logic (Continued) ............................................................................... 120
9-19. Allowed/Not Allowed Connector Geometry ............................................................. 121
9-20. Programmable Logic Block (PLB) Block Diagram .................................................... 122
9-21. Ladder Logic Functions Diagram .............................................................................. 124

xiii
B0193AW – Rev R Figures

9-22. Typical Ladder Logic Application ............................................................................. 130

9-23. Typical Ladder Logic Application (Continued) ......................................................... 130
9-24. Typical Ladder Logic Application (Continued) ......................................................... 131
9-25. Typical Ladder Logic Application (Continued) ......................................................... 131
9-26. Typical Ladder Logic Application (Continued) ......................................................... 132
10-1. Processing Order Within a Scheduled BPC ............................................................... 144
12-1. System with Two Fieldbuses ..................................................................................... 160
12-2. Typical Control Software Structure ........................................................................... 161
12-3. Typical CP60 and Fieldbus Communications Modules Interface .............................. 162
12-4. DIN Rail Mounted FBM Connections to ECBs 1, 2, 4, 5, 8 and 53 ........................ 171
12-5. FBM214 and 216 Connections to ECB200 and ECB201 ......................................... 172
12-6. FBM215 and 218 Connections to ECB200 and ECB201 ......................................... 172
12-7. FBM220 and 221 Connections to ECB200 and ECB201 ......................................... 172
12-8. FBM223 Connections to ECB200 and ECB201 ....................................................... 173
12-9. FBM224 Connections to ECB200 and ECB201 ....................................................... 174
12-10. Typical FBM243 and ECB73 Configuration ............................................................ 175
12-11. Typical FBM246 and ECB38R Configuration .......................................................... 176
12-12. Connections to ECBs 1, 2, 4, 5, 6, 7 ......................................................................... 177
12-13. Connections to ECBs 8, 9, 12, 13, 14, 15, 16, 18 ..................................................... 178
12-14. Connections to ECBs 19, 20, 21, 22, 23 ................................................................... 179
12-15. Connections to ECBs 12, 23, 34, 36 ......................................................................... 180
12-16. Connections to ECBs 38R, 52 and 53 ...................................................................... 181
12-17. Connections to ECBs 44, 46, 52, and 53 .................................................................. 182

xiv
Tables
2-1. Load Value Accuracy ..................................................................................................... 9
5-1. BLKSTA-Assignable Bits ............................................................................................. 49
5-2. Parameter Status Bits ................................................................................................... 52
6-1. Block Status Symbols .................................................................................................. 60
6-2. Alarm Status Symbols ................................................................................................. 61
6-3. Data Conversion Clamping ......................................................................................... 64
6-4. Data Conversion Results ............................................................................................. 64
6-5. Peer-to-Peer Connections ............................................................................................ 65
7-1. Scan Periods ................................................................................................................ 68
7-2. Legal Phase Values ...................................................................................................... 69
8-1. ALMSTA-Assignable Bits ............................................................................................ 83
8-2. ALMOPT-Assignable Bits ........................................................................................... 85
8-3. PRTYPE Indicators ..................................................................................................... 86
8-4. INHALM-Assignable Bits ........................................................................................... 88
8-5. INHOPT Values ......................................................................................................... 88
8-6. INHSTA-Assignable Bits ............................................................................................ 90
9-1. Ladder Symbols ......................................................................................................... 104
9-2. Text and Numeric Elements ..................................................................................... 106
9-3. Technical Identifiers .................................................................................................. 106
9-4. Ladder Inputs ............................................................................................................ 107
9-5. Ladder Coils .............................................................................................................. 109
9-6. Counters and Timers ................................................................................................ 109
9-7. Counter/Timer State Terminology ............................................................................ 110
9-8. Timer/Counter Registers and Flags ........................................................................... 110
9-9. RTO Truth Table ..................................................................................................... 111
9-10. RTF Truth Table ...................................................................................................... 112
9-11. Effects of MCR and ZCL on Ladder Operation ........................................................ 114
9-12. Ladder Logic Commands .......................................................................................... 124
9-13. Ladder Modes of Operation ...................................................................................... 126
10-1. Operational Modes ................................................................................................... 138
10-2. Sequence States ......................................................................................................... 142
10-3. Compound Sequence State ....................................................................................... 143
11-1. ERCODE Parameter Messages ................................................................................. 157
12-1. FSMM02 Coding ..................................................................................................... 163
12-2. Redundant Output Fallback Values .......................................................................... 164
12-3. FBM201 to FBM213 Integration Time Factors ........................................................ 167
12-4. FBM01 to FBM05 Integration Time Factors ............................................................ 168
12-5. Equipment Control Blocks ........................................................................................ 169
12-6. Window Equipment Control Blocks ......................................................................... 183
B-1. FBM201 Options ..................................................................................................... 205
B-2. FBM201 Conversion Time Factors ........................................................................... 206
B-3. FBM202 Options ..................................................................................................... 206
B-4. FBM202 Conversion Time Factors ........................................................................... 207
B-5. FBM203 Options ..................................................................................................... 207

xv
B0193AW – Rev R Tables

B-6. FBM203 Conversion Time Factors ........................................................................... 208

B-7. FBM204 Options ..................................................................................................... 208
B-8. FBM204 Conversion Time Factors ........................................................................... 209
B-9. FBM207 Options ..................................................................................................... 210
B-10. FBM211 Options ..................................................................................................... 210
B-11. FBM211 Conversion Time Factors ........................................................................... 211
B-12. FBM212 Options ..................................................................................................... 211
B-13. FBM212 Conversion Time Factors ........................................................................... 212
B-14. FBM213 Options ..................................................................................................... 212
B-15. FBM213 Conversion Time Factors ........................................................................... 213
B-16. FBM217 Options ..................................................................................................... 214
B-17. FBM219 Digital Options .......................................................................................... 215
B-18. Modbus Function Codes for Modicon Programmable Controllers ............................ 216
B-19. FBM237 Options ..................................................................................................... 217
B-20. FBM241 Digital Options .......................................................................................... 217
B-21. FBM242 Digital Options .......................................................................................... 218
B-22. FBM01 Options ....................................................................................................... 220
B-23. FBM01 Conversion Time ......................................................................................... 220
B-24. FBM02 Options ....................................................................................................... 221
B-25. FBM02 Conversion Time ......................................................................................... 221
B-26. FBM03 Options ....................................................................................................... 222
B-27. FBM03 Conversion Time ......................................................................................... 222
B-28. FBM04 Options ....................................................................................................... 223
B-29. FBM04 Conversion Time ......................................................................................... 223
B-30. FBM06 Options ....................................................................................................... 224
B-31. FBM17 Analog Options ............................................................................................ 225
B-32. FBM17 Digital Options ............................................................................................ 225
B-33. FBM17 Conversion Time ......................................................................................... 226
B-34. FBM07/12 Options .................................................................................................. 228
B-35. FBM08/13 Options .................................................................................................. 229
B-36. FBM09/14 Options .................................................................................................. 230
B-37. FBM10/15 Options .................................................................................................. 230
B-38. FBM20/21 Options .................................................................................................. 231
B-39. FBM11/16 Options .................................................................................................. 232
B-40. FBM33 Options ....................................................................................................... 233
B-41. FBM33 Conversion Time ......................................................................................... 233
B-42. FBM36 Options ....................................................................................................... 234
B-43. FBM36 Conversion Time ......................................................................................... 234
B-44. FBM37 Options ....................................................................................................... 235
C-1. Legacy FBMs and Equivalents ................................................................................... 237
C-2. Fieldbus Cluster Modules .......................................................................................... 243
C-3. Eckardt Rack I/O Cards ............................................................................................ 243
C-4. UCM or UIO Rack I/O Cards .................................................................................. 244
C-5. FIO Rack I/O Cards ................................................................................................. 245
C-6. UFM Rack I/O Cards ............................................................................................... 246
C-7. Fisher Series 20 Migration Cards ............................................................................... 247
C-8. DIN 200 FBMs and Equivalents ............................................................................... 248
C-9. Honeywell TDC2000 Migration I/O Cards .............................................................. 252

xvi
Tables B0193AW – Rev R

C-10. Honeywell TDC3000 Migration I/O Cards .............................................................. 256

C-11. FCMs and Equivalents .............................................................................................. 257

xvii
B0193AW – Rev R Tables

xviii
Preface
This document is intended for use by process control and applications engineers. It provides
theoretical, descriptive and conceptual information for process control and configuring your
process control database including block processing cycles, phasing, equipment control
blocks, compounds, and blocks. You should read this document prior to attempting any con-
trol configuration. Complete block descriptions and lists of their parameters are found in
Integrated Control Blocks Descriptions (B0193AX).

Revision Information
For Release 7.1, the following changes were made to the document:
Chapter 8 “Block/Process Alarming”
♦ Revised “Process Alarm Types” on page 90 to better reflect real operational
conditions
Chapter 9 “Ladder Logic Concepts”
♦ Corrected text in “Transition Counters” on page 111.

Reference Documents
Refer to the following documents for additional information:
♦ 50 Series Program Development (B0193LQ)
♦ Control Processor Sizing Spreadsheet (B0193BF)
♦ Fieldbus Cluster I/O User’s Guide (B0193RB)
♦ FOUNDATION fieldbus H1 Interface Module (FBM220/221) User Guide (B0400FD)
♦ HART™ Communication Interface Module (FBM214/215/216/218) User’s Guide
(B0400FF)
♦ Integrated Control Block Descriptions (B0193AX)
♦ Integrated Control Configurator (B0193AV)
♦ Object Manager Calls (B0193BC)
♦ PLC™ Interface Block Descriptions (B0193YQ)
♦ Process Operations and Displays (B0193MM)
♦ PROFIBUS-DP™ Communication Interface Module (FBM223) User’s Guide
(B0400FE)
♦ Program Development (B0193BA).
For information on the Gateways and Integrators, refer to the appropriate Gateway and Integrator
documents.

xix
B0193AW – Rev R Preface

xx
1. Introduction
This document provides general control information, and describes continuous control,
sequential control, ladder logic, and block configuration concepts.
Integrated Control Configurator (B0193AV) provides a description of, and procedures for the con-
figurator functions. Integrated Control Block Descriptions (B0193AX) and PLC Interface Block
Descriptions (B0193YQ) describe all of the blocks and ECBs.
This document describes:
Subject Refer to
Compound structure including blocks and Chapter 2 “Compounds and Station Blocks”
parameters
Block descriptions and characteristics Chapter 3 “Blocks”
Block initialization Chapter 4 “Block Characteristics”
Block states Chapter 5 “Block States”
Parameter connections Chapter 6 “Connections”
Compound, block, and I/O processing Chapter 7 “Block Processing”
Process alarming Chapter 8 “Block/Process Alarming”
Ladder logic capability Chapter 9 “Ladder Logic Concepts”
Sequential control capability Chapter 10 “Sequence Logic”
Control configurator concepts Chapter 11 “Integrated Control Configurator
Concepts”
Control Processor/Fieldbus Application Chapter 12 “Control Processor (CP)/Fieldbus
Interface Application Interface”
Window Equipment Control Blocks (defined) Chapter 12 “Window Equipment Control
Blocks” on page 183
Signal Conditioning Appendix A “Signal Conditioning Indexes”
Equipment Control Blocks/Fieldbus Modules Appendix B “Fieldbus Modules”
(defined)

1
B0193AW – Rev R 1. Introduction

2
2. Compounds and Station Blocks
This chapter gives an overview of compounds and blocks, including compound functions,
attributes, and access, and compound/block alarming, phasing, and parameters. This chapter
also covers the station compound or block and shadow parameters.
Process control for I/A Series systems is based on the concepts of compounds and blocks. A com-
pound is a logical collection of blocks that performs a control strategy. A block is a member of a
set of algorithms that performs a certain control task within the compound structure. Figure 2-1
shows the compound/block relationship.
The compound provides the basis for the integration of:
♦ Continuous control
♦ Ladder logic
♦ Sequential control.
Within this structure, any block in any compound can be connected to any other block in any
other compound in the system. The entire compound structure can be viewed through the work-
station SELECT display.
The block contains parameters that have values of the types: Real, Boolean, Packed Boolean,
Boolean Long, Integer, or String.

3
B0193AW – Rev R 2. Compounds and Station Blocks

CONFIGURATOR

COMPOUND COMPOUND COMPOUND

1 2 n

BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK BLOCK

= Control Processor

PROCESS

Figure 2-1. Compound/Block Relationship

Compound Functions
The compound supports the following functions for the related blocks:
♦ Process alarm priority, alarm inhibiting, and alarm grouping
♦ Sequence status notification (see “Sequential Control Block States” on page 138)
♦ Phasing for execution load leveling at execution time.
The compound rules are:
♦ Multiple compounds can be executed within the same station
♦ A single compound cannot cross station boundaries
♦ Blocks in different compounds can be interconnected across station boundaries
♦ Every compound must have a unique name.

4
2. Compounds and Station Blocks B0193AW – Rev R

Compound/Block Process Alarming

Alarms and status messages are generated by specific alarm blocks and by alarm options in selected
blocks.
Alarms have five levels of priority, 1-5, (where 1 = highest priority) that enable you to quickly
focus on the most important plant alarm conditions. An alarm priority of 0 indicates the absence
of any alarm.
These are summarized in a single alarm summary parameter for each compound. This parameter
contains the priority of the highest current alarm in that compound.
To reduce nuisance alarms, alarms can be inhibited at the compound level on a priority level basis.
Alarms can also be inhibited at the block level, on either an alarm type basis, or an overall basis.
Alarms are initiated by the blocks within the compound. Alarm messages are then sent to groups
of stations or applications (for example, Workstations, Historians, Printers) according to config-
ured alarm groups. The UNACK alarm acknowledge output parameter allows you to propagate
alarm acknowledge actions to all blocks in a compound.
Stations, applications, and devices corresponding to various alarm destination groups are config-
ured at the compound level or at the station level in the case of station compounds.
Group numbers for individual block alarm types are configured at the block level.

Compound/Block Phasing
A user-defined phase number can be assigned to each compound using a range of integer values
that varies with assigned period.
Phasing allows the starting time of one compound/block to lead or lag the starting time of
another compound/block, thereby leveling the block processor load.

Compound Attributes
The compound has the following attributes:

Name: User-defined name that must be system-unique and no more than 12

characters in length. The name can be any mix of numerics (0 to 9), upper
case alphabetics (A to Z), and the underscore (_).

Descriptor: 32-character field for user-defined identification.

On/Off: Parameter that enables or disables the execution of all blocks within the
compound, where: 1 = on; 0 = off.

5
B0193AW – Rev R 2. Compounds and Station Blocks

Compound Access
Both compounds and blocks have a set of parameters that comprise the user interface. To access a
compound parameter value, use the following convention:
Compound.Parameter
where:
♦ Compound has (up to) a 12-character name
♦ Parameter has (up to) a 6-character name.

Compound/Block Parameters
Compound and block parameters contain values that are of one of the types Real, String, Integer,
Short Integer, Long Integer, Boolean, Packed Boolean, Packed Long, or Character.
Additionally, parameters are defined as being configurable, and either connectable/settable, not
connectable/not settable, or a combination that is dependent upon the compound, block, and
state.

Configurable Parameters
Configurable parameters are those parameters that can be defined through the Integrated Control
Configurator. They can be displayable only, or displayable and editable.

Connectable Parameters
Connectable parameters are those parameters of the user interface in which secured, change-
driven connections may be made between network stations, or as local direct connections within
the same station.
Each connection consists of a connectable source and a connectable sink. Output parameters (all
outputs are connectable) are sources, while input parameters may be a sink or a source, or both.
Certain parameters that may be considered functional inputs, such as SPT in the PID blocks, and
RATIO in the RATIO block, are settable but not connectable.
A connectable parameter has a value record that contains the parameter’s value, its status, and its
designated value type (Real, Boolean, or Integer). Its status consists of the following Boolean
attributes:

Out-of-Service (OOS)
Defines the validity of the data. This flag is set and reset by the block
algorithm. The OOS status usually originates from I/O type blocks (for
example, AIN, COUT) which detect abnormal I/O conditions, for exam-
ple, that the FBM is out-of-service, or that the compound containing the
block of the I/O parameter is turned OFF.

Secure Defines the conditional settability status of the parameter. The secure flag
is set and reset by the block algorithm. A settable parameter can only be
written if it is not secured. For example, a remote set point, RSP, is unse-
cured and settable when it is not connected. When connected, the param-
eter is secured and not settable.

6
2. Compounds and Station Blocks B0193AW – Rev R

Bad Defines the validity of the data. This flag is set and reset by the block
algorithm. The Bad status usually originates from I/O type blocks (for
example, AIN, COUT) which detect abnormal I/O conditions such as a
bad FBM, type mismatch, bad channel status, or out-of-range conditions.
You can access certain status bits of a parameter value record as explicit connections in control
schemes, by using Boolean connection extensions. Certain CALC and LOGIC block instructions
also have this capability, and user tasks can access these variables implicitly within their specific
algorithms.
In addition, the BAD status of an I/O block’s value record is made available as a unique Boolean-
type connectable output parameter. This value can be accessed explicitly by any other block or
task.

Input Parameters
Input parameters are connectable types that are the receivers of data from other connectable
parameters via a path connection.
If no source path is specified during configuration, then the resident data of the value record is the
actual “source” of data. It can be either the initial default or configured value, or a new value
through a SET call to the input parameter.
If a source path is specified, then the data value is an output parameter of the same or another
block, or a shared variable, thereby securing the input. By linking a shared variable to a block
input during configuration, you can establish a long-term secured connection between a remote
application program and the block input.

Output Parameters
All output parameters are connectable data sources that have value records. There are two types:
settable and nonsettable.
The settability of a settable output is controlled by the secured status of the value record. The
secured status is dependent on whether the block’s operational mode is in Auto or Manual.
In either Auto or Manual, nonsettable output parameters cannot be written by any other source
under any conditions.
Settable outputs may be conditionally released by the block algorithm in the Manual mode.
In Manual, the block unsecures settable output parameters. They can then be written by other
tasks via SET calls. When the block switches to Auto, the block secures and updates its own
output parameter(s).

Nonconnectable Parameters
Nonconnectable parameters have no value records and are not linkable. They mainly consist of
string-type variables like NAME, or nonsettable parameters that are used in the configurator only,
for example, block options. Local algorithm variables are also nonconnectable.
Nonconnectable parameters are generally accessible through GET calls.
There is also a class of nonconnectable input parameters that comprise the block user interface
which can be manipulated through SET calls. An example is an alarm deadband.

7
B0193AW – Rev R 2. Compounds and Station Blocks

Compound Parameters
Refer to Integrated Control Block Descriptions (B0193AX) and PLC Interface Block Descriptions
(B0193YQ) for a detailed description of the compound and its parameters.

The Station Compound/Block

A Station compound containing one Station block for each station in a system, is installed in a
station automatically when a database is downloaded, even in an “empty” database. This block
provides global data storage for station system functions. You can view the station block by calling
up its default display.
A Station Block provides information about the station’s resources. The station block for all sta-
tions are identical. Station blocks are used for each of the following types of stations:
♦ Application Workstations (AWs)
♦ Workstation Processors (WPs)
♦ Application Processors (APs)
♦ Control Processors (CPs)
♦ Integrators and Gateways
♦ Control Stations.
Each Station compound and block has a unique name in any I/A Series network, determined by
embedding the station letterbug in the compound name as follows:
♦ Compound name is: letterbug_STA
♦ Block name is: STATION
♦ Full pathname is: letterbug_STA:STATION.
The Station compound and block have the following restrictions:
♦ The compound cannot be deleted or turned off.
♦ The block cannot be deleted.
♦ User-created blocks cannot be added to the compound.
♦ The compound is not run periodically by the Control Processor Task (CPT).
Refer to Process Operations and Displays (B0193MM) for station block operational procedures and
to Integrated Control Block Descriptions (B0193AX) for a detailed description of the station block
and its parameters.

Dynamic Loading Calculations

The station, when enabled, performs several Dynamic Control Processor loading calculations.
The first is the I/O scan load. The second calculation is for the loading for continuous block pro-
cessing. The third calculation is for sequence processing.
CP load is the total control block load, that is, the load value for continuous blocks, sequence
blocks, and I/O. When the station initializes, the load calculation switch is automatically set to
false and remains in that state under normal operation. You enable (or disable) the loading calcu-
lations at the Station Block display by toggling the ACTIVE pick.

8
2. Compounds and Station Blocks B0193AW – Rev R

You may synchronize the calculations to start at a specified phase number, LODPHS, or to start at
the current phase. You request synchronization, at the block display, by setting the LODSYN
input to true.
LODPHS is specified in phase numbers corresponding to one minute and normalized to the sys-
tem BPC; for example, the default system BPC is 0.5 seconds which normalizes the one minute
period to 120 frames, giving LODPHS a domain of 0 to 119 (modulo 120). Thus, each load out-
put is computed in the BPC frame equal to LODPHS plus their index.
You may also specify the sampling period, LODPER. The value limit is 10 * BPC to 3600 sec-
onds. Default is 10 * BPC.
The station calculates separate load values for ten consecutive BPCs. On the tenth cycle, the sta-
tion calculates two separate averages of the ten most recent cycles – one to calculate the load for
continuous blocks and the other for the station load (continuous and sequence blocks).
At this time, all 22 load values are copied to the Station block output parameters (connectable,
nonsettable). After the tenth cycle, the station suspends calculation until the sampling period
expires, when the calculation cycles begin again. The station makes these calculations every sam-
pling period until the loading calculations are disabled.
Since the real-time clock has a resolution of 10 ms, the load value accuracies are as follows:

Table 2-1. Load Value Accuracy

BPC Maximum Error Usefulness

0.1 s 10.0% not very
0.2 s 5.0% marginal
0.5 s 2.0% useful
1.0 s 1.0% useful
2.0 s 0.5% useful

Dynamic Overrun Variables

The Station block provides an output parameter, OVRRUN, that is set to true (or false) each
cycle to indicate when the Control Processor Task (CPT) processing does (or does not) overrun.
The station increments a separate overrun counter, CUMOVR, when an overrun cycle is
detected. CUMOVR is available as an output of the Station block. You reset this counter by set-
ting the block’s momentary input parameter, RESOVR, to true.

Dynamic Free Memory Variable

The Station block indicates the number of bytes of dynamic free memory available for the control
database.
The station updates this value a minimum of every thirty seconds.

Peer-to-Peer Status
The Station Block supplies status and performance data on the station’s peer-to-peer communica-
tions. The performance and status information provided is as follows:
♦ the current number of peer-to-peer control block input connections configured in the
control data base.

9
B0193AW – Rev R 2. Compounds and Station Blocks

♦ a counter that contains the current number of peer-to-peer connections that have
never been made.
♦ a counter that contains the current number of peer-to-peer connections whose source
blocks or compounds have been deleted via the Integrated Control Configurator.
♦ a counter that contains the current number of peer-to-peer connections that have
been disconnected due to a loss of peer-to-peer communications with the source
station.
Deleted connection errors are temporary. When a station is checkpointed following the deletion
of any of its control blocks, the status of any peer-to-peer sink connections to these blocks in
other stations are changed from deleted to not found, and the station updates the not found and
deleted counters accordingly.
The station software updates counters every two minutes.

Database Security
The Station block contains a database security parameter, Configuration Option (CFGOPT).
When CFGOPT is true, database changes to any active block or ECB are disabled. The block is
active if the compound in which it resides is ON, and the ECB is active if it is ON.

Time/Date
The Station block contains five parameters, YEAR, MONTH, DAY, HOUR, and SECOND
which provide user access to the system clock. These parameters are updated every 30 seconds by
the station block software.

Station Block Parameters

Refer to the Integrated Control Block Descriptions (B0193AX) document for a detailed description
of the station block and its parameters.

Shadow Parameters
A shadow block is a block in a station that provides a standard control strategy interface for an
algorithm actually executing in a connected FBM. Shadow parameters are those parameters in a
shadow block that can be changed by either the CP or the downstream FBM. A shadow parame-
ter has two storage locations; one is written by the CP as a request to the connected FBM (the
“sink” location) and the other is written when the FBM responds to the requested state change or
action (the “source” location). You write the sink parameter via “sets” or connections, and read the
source parameter via “gets” or connections. In every case, you deal with a single parameter name
even though there are two storage locations for each parameter. You can retrieve shadow
parameters:
♦ By GETVAL calls
♦ By opening an Object Manager (OM) read list and issuing OMREAD calls
♦ By connecting to a shadow source parameter.
You can change a shadow parameter:
♦ By SETVAL calls
♦ By opening an OM write list and issuing OMWRITE calls

10
2. Compounds and Station Blocks B0193AW – Rev R

♦ By connecting to a shadow input parameter in the same CP or in a different CP

(through peer-to-peer connection).
Examples of shadow parameters are Auto/Manual in the MDACT block, and On/Off Computer,
Auto/Manual, Remote/Local, Output, Set Point, Ratio, and Bias parameters in the
INTERSPEC™ Integrator shadow blocks.

11
B0193AW – Rev R 2. Compounds and Station Blocks

12
3. Blocks
This chapter defines the path for block parameters, describes the common block parameters, lists
all block types, and lists the control stations that host each type of control block.
A block has one or more inputs/outputs and performs a predefined process function that has been
prespecified by an algorithm.
There are continuous, sequence, and ladder logic block function types that can be mixed and
matched to satisfy your integrated control needs.
This section briefly defines the block set. However, detailed information can be found in
Integrated Control Block Descriptions (B0193AX) and PLC Interface Block Descriptions (B0193YQ).

Block Attributes
A block has the following attributes:

NAME: Name is a user-defined string that must be unique within the compound
and up to 12 characters in length. The name can be any mix of numerics
(0 to 9), upper case alphabetics (A to Z), and the underscore (_).

TYPE: Type is a system-defined name (up to six characters) that identifies the
algorithm control function.
In the Integrated Control Configurator, you can enter the block-type
string (for example, MAIN) or you can select the desired type from a
block type list. To display the block type list, select SHOW from the
menu-bar and select BLOCK TYPE NAMES from the SHOW menu.
Type is entered as a string, but is stored in the database as an indexed inte-
ger. (The OM Get command retrieves this integer value, not the string.)
Therefore, to be consistent with the database, the parameter tables in Inte-
grated Control Block Descriptions (B0193AX) and PLC Interface Block
Descriptions (B0193YQ) list the data type as an integer.

Block Access
To access a block parameter value from outside the resident compound, you must use the entire
path:
Compound:Block.Parameter
Connectivity between blocks in different compounds is through this same convention, whether
the compounds are in the same or different stations.
To connect to either a block parameter value from another block within the same compound, or
to a parameter value from within the same block, you can use:
:Block.Parameter
in the Integrated Control Configurator.

13
B0193AW – Rev R 3. Blocks

Since block names do not have to be unique across compounds, the following example shows two
compounds, REFLUX and EN_BAL, each having a block called F100.

REFLUX EN_BAL

F100 L100 F100 T100

.MEAS .MEAS .MEAS .MEAS
.SPT .SPT .RSP .RSP
and so .OUT .OUT and so
forth. and so and so forth.
forth. forth.

Figure 3-1. Block Access

Approximate Block Sizes

Each control block uses a different amount of memory in a Control Processor. The type and
number of control blocks determines the Control Processor loading. Refer to Control Processor
Sizing Spreadsheet (B0193BF) for complete and precise memory and loading calculations.

Block Parameters
Like compounds, each block contains select parameters that serve as the inputs and outputs of
their respective functions. These parameters follow the same conventions as compound parame-
ters regarding their value types and connectability/settability.
For information on accessing block parameters from a user task, refer to Program Development
(B0193BA), 50 Series Program Development (B0193LQ), and Object Manager Calls (B0193BC).

Common Parameters
All blocks, with exceptions as noted, have the following common parameters:

NAME Name is a user-defined string of up to 12 characters, which must be

unique within the compound, used to access the block and its parameters.
The string can be any mix of numerics (0 to 9), upper case alphabetics
(A to Z), and the underscore (_).

TYPE Type is a system-defined name (up to six characters) that identifies the
algorithm control function.
Type is entered as a string, but is stored in the database as an indexed inte-
ger. (The Object Manager Get command actually retrieves this integer
value, not the string.) Therefore, to be consistent with the database, the
parameter tables in Integrated Control Block Descriptions (B0193AX) and
the PLC Interface Block Descriptions (B0193YQ) list the TYPE parameter’s
data type as an integer.

14
3. Blocks B0193AW – Rev R

DESCRP Description is a user-defined string of up to 32 characters that describe the

block’s function (for example, “PLT 3 FURNACE 2 HEATER
CONTROL”).

PERIOD Period is an indexed, nonconnectable, input parameter that specifies the

block’s execution time base. Data Variable blocks (for example, BOOL,
LONG, and so forth.) do not have the PERIOD parameter.

PHASE Phase is an integer input that causes the block to execute at a specific BPC
within the time determined by the PERIOD. For instance, a block with
PERIOD of 3 (2.0 sec) can execute within the first, second, third, or
fourth BPC of the 2-second time period, assuming the BPC of the
Control Processor is 0.5 sec. “Block Phasing” on page 68 provides further
details.

MA Manual/Auto is a connectable Boolean input that controls the

Manual/Automatic operating state (0 = False = Manual; 1 = True = Auto).
The BLNALM and Data Variable blocks do not have the MA parameter.

INITMA Initialize Manual/Auto specifies the desired state of the MA input during
initialization:
0 = Manual
1 = Auto
2 = No change, except if a reboot, use the MA state specified in the check-
point file
The BLNALM and Data Variable blocks do not have the INITMA
parameter.

LOOPID Loop Identifier is a configurable string of up to 32 characters which iden-

tify the loop or process with which the block is associated. It is displayed
on the detail display of the block, immediately below the faceplate. Data
Variable blocks do not have the LOOPID parameter.

OWNER Owner is a settable string of up to 32 ASCII characters which are used to

allocate control blocks to applications. Attempts to set OWNER are suc-
cessful only if the present value of OWNER is the null string, an all-blank
string, or identical to the value in the set request. Otherwise the request is
rejected with a LOCKED_ACCESS error. OWNER can be cleared by any
application by setting it to the null string; this value is always accepted,
regardless of the current value of OWNER. Once set to the null string, the
value can then be set as desired. The AMSSEC, DSI, EVENT, FBTUNE,
FFTUNE, and Data Variable blocks do not have the OWNER parameter.

15
B0193AW – Rev R 3. Blocks

LOCKRQ Lock Request is a boolean input which can be set true or false only by a set
command from the LOCK U/L toggle key on workstation displays. When
LOCKRQ is set true in this fashion a workstation identifier accompany-
ing the set command is entered into the LOCKID parameter of the block.
Thereafter, set requests to any of the block’s parameters are honored (sub-
ject to the usual access rules) only from the workstation whose identifier
matches the contents of LOCKID. LOCKRQ can be set false by any
workstation at any time, whereupon a new LOCKRQ is accepted, and a
new ownership workstation identifier written to LOCKID. The
AMSSEC, MSG, PLC and DCI output blocks do not have the LOCKRQ
parameter.

LOCKID Lock Identifier is a string identifying the workstation which has locked
access to the block via a successful setting of LOCKRQ. LOCKID has the
format LETTERBUG:DEVNAME, where LETTERBUG is the
6-character letterbug of the workstation and DEVNAME is the 1-6 char-
acter logical device name of the Display Manager task. The AMSSEC,
MSG, PLC and DCI output blocks do not have the LOCKID parameter.

Editing Parameters
You may edit block parameters with the Integrated Control Configurator using the
Compound/Block editing functions as described in Integrated Control Configurator (B0193AV).

Block Function Types

The following list gives a brief overview of all the Integrated Control software block function
types. For a detailed description of each, refer to Integrated Control Block Descriptions (B0193AX)
or PLC Interface Block Descriptions (B0193YQ). For a description of a specific Integrator, Gate-
way, or INTERSPEC Integrator blocks, refer to the appropriate Integrator or Gateway document.

ACCUM The ACCUM block integrates a real input (rate or pulse count) signal
(Accumulator) and scales it to produce a real output quantity of the running total.
Inputs are provided to let you clear, preset, and hold the accumulator
output.
AIN The AIN block supports a single input from an analog-type FBM. Pro-
(Analog Input) visions exist to condition, scale, clamp, and filter the input, and alarm
the hardware status and output value.
AINR The AINR block supports a single input point from two redundant
(Redundant Analog analog-type FBMs. Provisions exist to condition, scale, clamp, and filter
Input) the selected input, and alarm the hardware status and output value.
ALMPRI The ALMPRI block is used to dynamically reassign the priority of an
(Alarm Priority Change) alarm point.
AMSSEC This block is used in conjunction with a gas chromatograph ECB
(Gas Chromatograph (“AMSPRI”). It provides for additional inputs to the GC and contains
Secondary Block) variables for individual applications. Data such as the instrument values
move from the PIO message to the block outputs.

16
3. Blocks B0193AW – Rev R

AOUT The AOUT block provides an auto/manual with bias (AMB) function.
(Analog Output) It biases, clamps, and conditions the input and drives a single output
point within an analog-type FBM. Provisions exist to alarm the hard-
ware status of the connected FBM.
AOUTR The AOUTR block provides an auto/manual with bias (AMB) func-
(Redundant Analog tion. It biases, clamps, and conditions the input and drives a single out-
Output) put point via a dual pair of redundant analog-type FBMs. Provisions
exist to alarm the hardware status when both FBMs have bad status.
BIAS The BIAS block produces an output that is the sum of the two input
(Bias) values, MEAS and BIAS, each of which can be scaled independently.
The block supports measurement alarm messages. It does not support
output alarm messages. The BIAS block supports cascade
initialization.
BIN The Binary Input (BIN) block provides the control strategy with the
(Binary Input) capability to read a single binary value, having two states such as ON
and OFF or START and STOP, from an address in an associated
Fieldbus Module (FBM) or a specified point. BIN is used in a Distrib-
uted Control Interface (DCI) (DCI blocks support connectivity of
I/A Series control stations to various bus resident devices via a general
purpose interface) and in PLC interfaces.
BINR The Redundant Binary Input (BINR) block receives one binary value
(Binary Input, from an external device. The source of the value can be specified as
Redundant) either two or three redundant inputs. The redundant inputs can either
be in the same device or in different devices. The block’s selection algo-
rithm determines which of the two or three input values is presented to
the control strategy as the block output. BINR is used in a Distributed
Control Interface (DCI) (DCI blocks support connectivity of
I/A Series control stations to various bus resident devices via a general
purpose interface.)
BLNALM This block provides independent state-change alarm messages for each
(Boolean Alarm) of eight Boolean-type inputs.
BOOL This block provides the capability of creating a settable and config-
(Boolean Data Variable) urable boolean data value for use by other control blocks.
BOUT The Binary Output (BOUT) block sends one binary value to an
(Binary Output) address in an external device. It also continuously reports, to the
I/A Series system, any changes made by the device to the value at this
address. BOUT is used in a Distributed Control Interface (DCI) (DCI
blocks support connectivity of I/A Series control stations to various bus
resident devices via a general purpose interface.) and PLC interface.
CALC The Calculation block provides up to 50 sequentially executed arith-
(Calculator) metic and logical operations. It has the capability of a programmable
scientific calculator.
CALCA The CALCA block adds dual-operand efficiency to many mathematical
(Advanced Calculation and logical calculation operations.
Block)

17
B0193AW – Rev R 3. Blocks

CHARC This block converts a real input to a real output using a table lookup of
(Characterizer) piecewise linear segments. Up to 20 segments can be used.
CIN The CIN block supports a single input point from a digital input type
(Contact Input) FBM. The block also provides an input inversion option.
COUT The COUT block supports a single output to a digital type FBM. The
(Contact Out) block also provides an output pulsing option.
DEP This block contains user-programmable statements that can manipulate
(Dependent Sequence) compound or block parameters, or shared variables. It can also activate
other sequence and monitor blocks, along with sending messages to dis-
plays and historians.
A Dependent Sequence block’s execution is automatically delayed while
any Exception Sequence block in the same compound is running.
DGAP This block outputs two discrete output values that can be used for
(Differential Gap) on/off control of bi-state or tri-state actuated final actuator devices. The
outputs depend on the difference between the measurement, set point,
and adjustable error GAP. The DGAP block does not support cascade
initialization.
DPIDA The DPIDA block interfaces the control processor to a PIDA-type
(Distributed Controller) algorithm executing in an FBM04, FBM17, FBM37, or FBM22.
DSI The DSI block provides the interface between Panel Display Stations
(Display Station and the compounds and blocks that actualize the control strategy.
Interface)
DTIME This block delays the input a specific length of time before making it
(Deadtime) available at the output. It is typically used to simulate process transport
delay and to compensate feed-forward signals.
EVENT The EVENT block provides message reporting for a sequence of state-
(Sequence of Events) change events detected in a contact input FBM. The connected FBM
must be an input-only type, and may not be a Cluster I/O FBC.
EXC This block contains user-programmable statements that can manipulate
(Exception Sequence) compound or block parameters, or shared variables. It can activate
other sequence and monitor blocks, along with sending messages to dis-
plays and historians.
When it activates, all Dependent Sequence blocks in the same com-
pound delay executing until the Exception Sequence block finishes its
execution.
FBTUNE The FBTUNE block is used to adaptively tune the proportional band,
(Feedback Self-Tuner) the integral time, derivative time, dead time, and the set-point-filter
lead-lag ratio of the PIDA block.
FFTUNE The FFTUNE block is used to adaptively tune the feedforward
(Feedforward Self-Tuner) compensators for the PIDA block.
GDEV This block provides Open/Close control of motor- or air-operated
(General Device) valves, and Run/Stop control of 2-wire, or 3-wire, motor circuits.

18
3. Blocks B0193AW – Rev R

IIN This block is a Distributed Control Interface (DCI) block. (DCI

(Integer Input) blocks support connectivity of I/A Series control stations to various bus
resident devices via a general purpose interface.) IIN can receive one
integer value from an external device. The actual receipt and processing
of this value is subject to the conditions established by the Simulation
Option and the Auto/Manual mode of the IIN block.
IND This block contains user-programmable statements that can manipulate
(Independent Sequence) compound or block parameters, or shared variables. It can also activate
other sequence and monitor blocks, along with sending messages to dis-
plays and historians. An Independent Sequence block does not affect
the execution of other sequence blocks nor does the execution of other
blocks affect the operation of Independent Sequence blocks.
IOUT This block is a Distributed Control Interface (DCI) block. (DCI
(Integer Output) blocks support connectivity of I/A Series control stations to various bus
resident devices via a general purpose interface.) IOUT can send one
integer value to a field device. It also continuously reports any changes
made by the device. These reports are made to the value at the same
address.
LIM The Limiter block provides a position and velocity limiter function for
(Limiter) a real input signal.
LLAG This block performs dynamic signal compensation by making the out-
(Lead-Lag) put dynamically lead or lag the input.
LOGIC The Logic block provides 15 sequentially-executed logical functions.
(Logic)
LONG This block provides the capability of creating a settable and config-
(Long Integer Data urable long integer data value for use by other control blocks.
Variable)
MAIN The MAIN block supports up to 8 inputs from an analog-type FBM.
(Multiple Analog Input) An internal channel for a temperature reference sensor is also provided.
MATH The MATH block provides a set of mathematics functions for special-
(Mathematics) ized control needs.
MCIN The MCIN block supports up to 32 inputs from digital input type
(Multiple Contact Input) FBMs.
MCOUT The MCOUT block supports up to 16 digital outputs to a digital type
(Multiple Contact Out) FBM.
MDACT The MDACT block provides the capability for high-resolution control
(Motor Driven of processes through tri-state (for example: raise, lower, off) devices.
Actuator Controller) The MDACT block supports cascade initialization.
MEALM The MEALM block serves as an alarm annunciator to activate the
(Measurement Alarm) I/A Series alarm mechanism upon alarm conditions detected by an
external source.
MON This block monitors up to 16 process conditions. It monitors parame-
(Monitor Sequence) ter values and Boolean expressions and triggers Exception, Dependent,
or Independent blocks.

19
B0193AW – Rev R 3. Blocks

MOVLV This block operates two related output contacts which open or close a
(Motor-Operated Valve) valve on an incremental basis. It supports optional feedback from one
or two contacts (limit switches) for mismatch alarming.
MRIN The MRIN block provides the control strategy with the capability to
(Multiple Real Input) read eight analog values from contiguous addresses in a Programmable
Logic Controller (PLC). This block is used in a PLC interface.
MROUT The MROUT provides the capability to write eight analog values to
(Multiple Real Output) contiguous addresses in a Programmable Logic Controller (PLC). This
block is used in a PLC interface.
MSG The MSG block generates state change messages upon transitions of its
(Message Generator) Boolean inputs.
MTR This block performs both 2- and 3-wire motor control functions.
(Motor Controller)
MVC The MVC block acts as the interface to the Control Processor embed-
(Multivariable ded MVC as the passing mechanism for Connoisseur controller models
Controller) and configuration parameters.
MVL The MVL block gets Controlled Variable (CV) measurements from
(Multivariable Loop) blocks such as the AIN and writes the Manipulated Variable (MV)
supervisory set points to other regulatory blocks (PIDA, DPIDA, or
RATIO).
OUTSEL The OUTSEL block controls strategies that require the higher or lower
(Output Select) of two input signals to be selected as the final output signal to the pro-
cess, while providing the appropriate handshake data to prevent integral
action from “winding up” in the block containing the unselected signal.
The block also provides separate cascade initialization each of the two
upstream blocks.
PACK This block provides the capability of creating a settable and config-
(Packed Long Data urable packed long data value for use by other control blocks.
Variable)
PAKIN The PAKIN block reads up to 32 bits of discrete data from a group
(Packed Input) address in a Programmable Logic Controller (PLC). Each bit represents
a binary value having opposing states, such as ON and OFF, or START
and STOP. This block is used in a PLC interface.
PAKOUT The PAKOUT writes up to 32 bits of discrete data to a group address
(Packed Output) in a Programmable Logic Controller (PLC). Each bit represents a
binary value having opposing states, such as ON and OFF, or START
and STOP. This block is used in a PLC interface.
PATALM This block compares the relationship of up to 16 Boolean inputs to a
(Pattern Alarm) user-specified pattern.
PATT The PATT block provides pattern matching capability for 16-bit
(Pattern Match) patterns.
PID The PID block provides the functions of the traditional interacting
(Proportional, Integral, 3-term controller. The PID block supports cascade initialization.
Derivative)

20
3. Blocks B0193AW – Rev R

PIDA The PIDA block implements continuous PID or dead-time feedback

(Proportional, Integral, and additive and multiplicative feedforward control of an analog loop,
Derivative, Advanced) providing advanced features beyond those of the PID and PIDX blocks.
PIDE This block provides the same capability as the PID block with the addi-
(PID with EXACT™) tion of the EXACT Self-Tuning algorithm.
PIDX This block provides the same capability as the PID block, with optional
(PID Extended) capability for nonlinear gain compensation, sampling mode, and batch
control preload.
PIDXE This block adds the EXACT algorithm to the PIDX block.
(PID Extended
with EXACT)
PLB The Programmable Logic Block supports ladder logic executing in an
(Programmable FBM, other than Cluster I/O FBCs. The block provides 32 input and
Logic Block) 32 output parameters.
PLCIO The PLCIO block is a functional composite of multiple PLC blocks
(Programmable Logic communicating with a single PLC. It is particularly useful when a large
Controller Input/Output) number of points in the PLC, with a variety of data types, are con-
nected to the I/A Series station. This block is used in a PLC interface.
PLSOUT The PLSOUT block allows the control strategy or operator to output
(Pulse Output ON and OFF, or START and STOP, type commands through momen-
tary pulsed outputs on two separate lines, one for each state. This block
is used in a PLC interface.
PTC This block performs the functions of a proportional-time on/off con-
(Proportional Time troller. The PTC block does not support cascade initialization.
Controller)
RAMP This block performs a general purpose ramp function.
(Ramp)
RATIO This block computes an output that is the scaled multiplication of a
(Ratio) measurement input with a ratio set-point input. The RATIO block
supports cascade initialization.
REAL This block provides the capability of creating a settable and config-
(Real Data Variable) urable real data value for use by other control blocks.
REALM The REALM block optionally supports three types of alarming:
(Real Alarm) ♦ High-low absolute alarming on the measurement.
♦ Rate-of-change alarming on the measurement.
♦ High-low deviation alarming on the difference between measure-
ment and set point.
RIN The Real Input (RIN) block receives one analog value from an external
(Real Input) device. It presents that value, after input processing, at parameter RINP.
RIN is used in a Distributed Control Interface (DCI) (DCI blocks
support connectivity of I/A Series control stations to various bus resi-
dent devices via a general purpose interface.) and a PLC interface.

21
B0193AW – Rev R 3. Blocks

RINR The Redundant Real Input (RINR) block receives one binary value
(Real Input, Redundant) from an external device. The source of the value can be specified as
either two or three redundant inputs. The redundant inputs can either
be in the same device or in different devices. Each of the redundant
inputs is independently scaled, limited, and converted into engineering
units before the block’s selection algorithm is invoked to determine
which of the two or three inputs is set into parameter RINP. RINR is
used in a Distributed Control Interface (DCI) block. (DCI blocks sup-
port connectivity of I/A Series control stations to various bus resident
devices via a general purpose interface.)
ROUT The Real Output (ROUT) block sends one analog value to an address
(Real Output) in an external device. It also continuously reports any changes made by
the device to the value at this address. ROUT is used in a Distributed
Control Interface (DCI) (DCI blocks support connectivity of
I/A Series control stations to various bus resident devices via a general
purpose interface.) and a PLC interface.
SIGSEL This block examines up to eight inputs and produces an output depen-
(Signal Selector) dent upon a relational selection option.
STALM The STALM block serves as alarm annunciator to activate the
(State Alarm) I/A Series alarm mechanism upon alarm conditions detected by an
external source such as HTG.
STATE The STATE block outputs selected 16-bit patterns.
(State)
STRIN The String Input (STRIN) block is a Distributed Control Interface
(String Input) (DCI) block. (DCI blocks support connectivity of I/A Series control
stations to various bus resident devices via a general purpose interface.)
STRIN receives one string value from an external device.
STRING This block provides the capability of creating a settable and config-
(String Data Variable) urable string data value for use by other control blocks.
SWCH This block selects either of two independent inputs. Each input can be
(Switch Position a real, integer, or Boolean variable. The SWCH block supports cascade
Selector) initialization.
TIM This block keeps track of time while control strategies are executing.
(Timer Sequence)
VLV This block is typically used to operate two related output contacts
(On-Off Valve Control) which open or close a valve on an ON/OFF basis.

22
3. Blocks B0193AW – Rev R

Matrix – Blocks versus Stations

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
Block ABG

DCI
INT
ABS

SSG
IG
Type
ABSCAN X
ACCUM X X X X X X X X X X
AIN X X X X X X X X X X X X X X
AINR X X X X X X
ALMPRI X X X X X X X X X X X X X X X
AMSPRI X X X X X
AMSSEC X X X X X
AOUT X X X X X X X X X X X X
AOUTR X X X X X X
BIAS X X X X X X X X
BIN X X X X X X
BINR X
BLNALM X X X X X X X X X X X X X X X X
BOOL X X X X X X
BOUT X X X X X X
CALC X X X X X X X X X X X X X X X
CALCA X X X X X X
CHARC X X X X X X X X X X
CIN X X X X X X X X X X X X
CMPND X X X X X X X X X X X X X X
COUT X X X X X X X X X X X X
D760 X
D761 X
DEP X X X X X X X X X X X X X X
DGAP X X X X X X X X X X
DPIDA X X X X X X
DSI X X X X
DTIME X X X X X X X X X X
ECB1 X X X X X X X X
ECB2 X X X X X X X X
ECB4 X X X X X X X X
ECB5 X X X X X X X X

23
B0193AW – Rev R 3. Blocks

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
ECB6 X X X X X X X X
ECB7 X X X X X X X X
ECB8 X X X X X X X X
ECB9 X X X X X X X X
ECB11 X X X X X X X X
ECB12 X X X X X X X X
ECB13 X X X X X X X
ECB14 X X X X X X X
ECB15 X
ECB16 X
ECB18 X X X X X X X X
ECB19 X
ECB20 X
ECB21 X
ECB22 X X X X X X X X
ECB23 X X X X X X X X
ECB24 X X
ECB29 X
ECB30 X
ECB31 X
ECB32 X
ECB34 X X X X X X
ECB36 X X X X X X
ECB37 X X X X X X
ECB38R X X X X X X
ECB39 X X X X X
ECB40 X
ECB41 X X X X X
ECB42 X X X X X
ECB43 X X X X X
ECB44 X X X X X
ECB45 X X X X X X
ECB46 X X X X X
ECB47 X X X X X

24
3. Blocks B0193AW – Rev R

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
ECB47R X X X X X
ECB48 X X X X X X
ECB48R X X X X X X
ECB49 X X X X X X
ECB50 X X X X X X
ECB51 X X X X X X
ECB52 X X X X X X
ECB53 X X X X X X
ECB57 X
ECB60 X
ECB61 X
ECB62 X
ECB63 X
ECB64 X
ECB65 X
ECB66 X
ECB67 X
ECB68 X
ECB69 X
ECB70 X
ECB71 X
ECB72 X
ECB73 X X X X X
ECB74 X X X X X
ECB75 X X
ECB76 X X
ECB77 S X
ECB78 X
ECB79 X
ECB80 X
ECB81 X
ECB86 X
ECB87 X
ECB88 X

25
B0193AW – Rev R 3. Blocks

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
ECB89 X
ECB89 X
ECB90 X
ECB91 X
ECB92 X
ECB93 X
ECB94 X
ECB95 X
ECB98 X
ECB99 X
ECB100 X
ECB101 X
ECB102 X
ECB103 X
ECB106 X
ECB107 X
ECB108 X
ECB109 X
ECB110 X
ECB200 X X
ECB201 X X
ECB202 X X
ECBP X X X X X X X X X X X X X
(ECPB11)
EVENT X X X X X X X X
EXC X X X X X X X X X X X X X X
FBTUNE X X X X X X
FDBIN X
FDBOUT X
FDIDMS X
FDIIN X
FDIOUT X
FDMSBL X
FDRIN X

26
3. Blocks B0193AW – Rev R

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
FDROUT X
FDSCAN X
FFTUNE X X X X X X X X X X
FCIN X
FCOUT X
FIIN X
FIOUT X
FRIN X
FROUT X
FSIN X
FSOUT X
FTRIG X
GDEV X X X X X X X X X X X X
IIN X
IND X X X X X X X X X X X X X X
IOUT X
LIM X X X X X X X X X
LLAG X X X X X X X X X X
LOGIC X X X X X X
LONG X X X X X X
MAIN X X X X X X X X X X X X
MATH X X X X X X
MCIN X X X X X X X X X X X X X
MCOUT X X X X X X X X X X X X
MDACT X X X X X
MDSCAN X
MEALM X X X X X X
MON X X X X X X X X X X X X X X
MOVLV X X X X X X X X X X X
MRIN X X X X
MROUT X X X X
MSG X X X X X X
MTR X X X X X X X X X X X
MVC X

27
B0193AW – Rev R 3. Blocks

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
MVL X
PACK X X X X X X
PAKIN X X X X
PAKOUT X X X X
PATALM X X X X X X X X X X X X X X X
PATT X X X X X X
PID X X X X X X X X X X
PIDA X X X X X X X
PIDE X X X X X X X X X
PIDX X X X X X X X X X
PIDXE X X X X X X X X
PLB X X X X X X X X
PLCIO X X X X
PLSOUT X X X X
PTC X X X X X X X X X
RAMP X X X X X X X X X X
RATIO X X X X X X X X
REAL X X X X X X
REALM X X X X X X X X X X X X X X X
RIN X X X X X X
RINR X
ROUT X X X X X X
SAIN X
SAIO X
SBIAS X
SCTLR X
SDIN X
SDIO X
SIGSEL X X X X X X X X X X
SRAS X
STALM X X X X X x
STATE X X X X X X
STOT X
STRIN X

28
3. Blocks B0193AW – Rev R

Station Type

Micro-I/A™
CP30, 30B
CP40, 40B

I/O Gate
Triconex
SCADA
AW51
AW70
MDG
DP10
CP10

CP60
TP10

SMG
FDG
ABG
Block

DCI
INT
ABS

SSG
IG
Type
STRING X X X X X X
SWCH X X X X X X X X X X
TIM X X X X X X X X X X X X X X
VLV X X X X X X X X X X X

LEGEND: ABG Allen-Bradley™ Gateway

ABS Allen-Bradley Station
CP10 Control Processor 10
DP10 Display Processor 10
TP10 Tank Processor 10
FDG Foreign Device Gateway
INT INTERSPEC Integrator
IG Instrument Gateway
MDG Modicon™ Gateway
SMG SPECTRUM™ Master Gateway
SSG SPECTRUM Slave Gateway
CP30 Control Processor 30
CP30B Control Processor 30B
CP40 Control Processor 40
CP40B Control Processor 40B
CP60 Control Processor 60
AW51 Application Workstation 51 with control blocks
AW70 Application Workstation 70 with control blocks
SCADA Supervisory Control and Data Acquisition
DCI Distributed Control Interface

Supervisory Set Point Control (SSC)

Supervisory Set Point Control (SSC) is supported in all the PID control blocks, RATIO, AOUT,
and AOUTR control blocks (Figure 3-2).

29
B0193AW – Rev R 3. Blocks

Digital Supervisory
Input Enable

Enable
To
From Process
Process

Disable

PIDA or AOUT
AIN RATIO
IBlock Block
Block

Figure 3-2. Supervisory Set Point Control Concept

The station block Supervisory Groups display allows you to enable or disable control blocks
assigned to each of eight supervisory groups. In addition, the station block shows the fallback sta-
tus and fallback request status for each group, and the (enabled/disabled) running time and set
point for each fallback timer.
You can from the station block Supervisory Groups:
♦ enable or disable SSC for any group
♦ request fallback status for a group,
♦ enable or disable a fallback timer.
SSC is supported in all I/A Series Control processors (CPs) and in most Application Processors
(AP), Workstation Processors (WP) and Application Workstations (AW). The AP10 does not sup-
port SSC, and the WP20 supports all features except the timer enable/disable actions and the
supervisory control enable/disable actions at the group level.

30
4. Block Characteristics
This chapter describes common aspects of block characteristics, including implicit and explicit
block initialization, PRIBLK configuration, configuring cascade schemes, and error handling,
as well as clamping, scaling, secure/release, control block fail-safe strategy, and the PID hold
constant.

Block Initialization
The need for block initialization exists when:
♦ Compounds switch from OFF to ON
♦ Blocks recover from re-established connections or from bad process inputs
♦ Blocks change modes (for example, from Manual to Auto)
♦ Controller blocks in cascade schemes return from open loop conditions
♦ The Control Processor is rebooted
♦ A block or compound is modified or added during on-line configuration while the
compound is ON
♦ The Control Processor recovers from a power failure.
Initialization within controller-type blocks is performed without bumping the process. Achieving
proper initialization depends upon the features available in each type of block and how blocks are
interconnected in a particular control scheme.
There are two types of initialization, referred to as implicit and explicit. Implicit initialization is
the execution of block-specific start-up and validation logic which occurs whenever any block
begins execution within the control strategy, and not thereafter. Explicit initialization is the
bumpless return to control following any disruption of control. It is a process involving multiple
blocks within a cascade, and is a response to exception situations which can occur at any time. All
blocks support implicit initialization, but only controller and output-type blocks, which require
the bumpless transfer function, support both implicit and explicit initialization.

Implicit Initialization
All blocks perform implicit initialization when requested to start up. This occurs automatically
when the compound is first switched on, after a block is modified, on a reboot, after a power fail
recovery, or when a block is added to an existing compound through the on-line configuration
process.
Validation logic is performed by the block to check the integrity of its block record. Critical, “con-
figuration only” (that is, nonconnectable/nonsettable) parameters are checked to make certain
that they are within acceptable values prior to start-up.
If any of these inputs are not within acceptable limits, the block is declared undefined and enters
the Undefined state (refer to “Block States” on page 45). In this state, the block is not processed
and the status of all its connectable parameters is set to Release and Bad.

31
B0193AW – Rev R 4. Block Characteristics

INITMA sets a block’s MA parameter during the execution cycle in which the block implicitly
initializes. The default is 1 (Auto), but INITMA is overridden if the MA parameter has an estab-
lished linkage. Note that INITMA overrides the MA value set by a checkpoint file or by a power
failure recovery.

Explicit Initialization

Introduction
Controller-type and output-type blocks must initialize to the current state of the process. This
means that output block reads back the current state of the device and causes the upstream blocks
control action to initialize to the present state of the process and/or manipulated variable.
The order in which cascaded blocks initialize is in the opposite order that they normally execute.
When controller-type and output-type blocks are cascaded in a control scheme, the open-loop
effects of any downstream block action must be propagated to upstream block(s). This ensures
bumpless return to the current state when the downstream block returns to closed-loop operation.
Blocks that support explicit cascade initialization have two connectable parameters. They are
BCALCI (back calculation in) and BCALCO (back calculation out) which are real input/output
parameters. These parameters have two status bits (INITU - Initialize Unconditional, and INITC
- Initialize Conditional) which are used to notify upstream blocks of the need for initialization
and a PRIBLK acknowledgment request bit (INITC) to ensure that the upstream block does not
initialize until the downstream block acknowledges that it is initialized.
When a block sees one of these status bits (INITU or INITC) set in its BCALCI parameter, it
performs the specified initialization algorithm and sets one of the status bits in its BCALCO
parameter. The BCALCO parameter is connected to the BCALCI of an upstream block as shown
in Figure 4-1.

PRIBLK = 0 PRIBLK = 1 PRIBLK = 1

SPT SPT
RSP OUT RSP OUT MEAS
PID
PID AOUT
FBK FBK
BCALCO MEAS BCALCI BCALCO MEAS BCALCI BCALCO OUT

Manipulated Variable

PNT PNT
AIN
AIN PNT_NO
FBM
Secondary Process Variable HW #4
Primary Process Variable
4AI/4AO

Figure 4-1. PRIBLK Cascade Standard Configuration

When an elaborate initialization scheme is required, you can connect the INITU or INITC status
bits to Boolean logic.

32
4. Block Characteristics B0193AW – Rev R

To provide the bumpless transfer to normal, the BCALCO value of the downstream block is
passed to the BCALCI value of the upstream block when the latter executes.
PRIBLK is a block parameter that allows cascade schemes to initialize properly without bumping
the process during initial start-up and any return to closed-loop operation. These open loop con-
ditions can occur at any point within the cascade.
PRIBLK extends the Explicit Initialization logic to allow cascades to be configured between com-
pounds, between CPs, or between blocks having different block periods. Thus, there are no
boundary restrictions that affect the PRIBLK connections. Also, there is no limitation to the
block period assignment to each level of the cascade, other than process sampling considerations.
PRIBLK is supported by the PID, PIDE, PIDX, PIDXE, PIDA, DPIDA, RATIO, BIAS,
SWCH, OUTSEL, AOUT, and AOUTR blocks.
Configuring PRIBLK to a 0 initializes all blocks of the cascade in the same control processor, at
the configured BPC period for the block. For example, a three-level cascade as shown in
Figure 4-1containing a 30-second period primary block, a 10-second period intermediate block,
and a 1-second period secondary block, results in a delay of up to 40 seconds before the primary
block initializes after the secondary block, for example, switched from Manual to Auto.
Configuring PRIBLK to a 1, initializes blocks only one BPC later than the next lowest down-
stream block in a cascade, provided the upstream blocks are in the same control processor. In the
three-level cascade shown in Figure 4-1, the primary block initializes in 2 BPCs. This is referred to
as “fast initialization”, and is accomplished by forcing execution of the upstream block immedi-
ately when cascade initialization is under way, regardless of its period and phase.

PRIBLK Parameter
General
The PRIBLK parameter initializes a cascade scheme at start-up and any return to closed-loop
operation. A block with PRIBLK = 1 responds to each of these operational events by performing
two unique types of Explicit Initialization.
The types of Explicit Initialization action that PRIBLK enables in response to start-up and return
to closed-loop operation are referred to as Unconditional Initialization and Conditional Initializa-
tion, respectively.
PRIBLK initialization is based on a tight coupling between each adjoining block of a cascade. At
any point along the cascade after the first controller, a given block can be viewed as a secondary to
its upstream block, and as a primary to its downstream block. The roles of primary and secondary
exchange as one moves along the cascade.
The standard connections shown in Figure 4-1 maintain the control/data flow of information
that allows initialization to be coordinated along the entire cascade.
Both types of Explicit Initialization progress from a secondary block to its upstream primary
block. Initialization may begin at any point along the cascade and proceeds to the next primary
block. The most primary block must have PRIBLK set to zero. How far the rippling proceeds
depends on the type of initialization and the mode of each primary block. Thus, the direction in
which initialization is performed is opposite to the forward signal path of the cascade.

33
B0193AW – Rev R 4. Block Characteristics

The amount of time that it takes for explicit initialization to ripple between any two blocks within
a cascade is dependent on the primary block’s PERIOD parameter and the transit time across a
station-to-station interface that may be between the two blocks. Thus, initialization occurs
naturally (that is, from the FBM to the beginning of the cascade) and is governed by the
configuration.
PRIBLK affects the manner in which the incoming demand signal (for example, RSP for PIDs,
REMRAT for RATIO, RBIAS for BIAS, and MEAS for an AOUT or AOUTR) is handled. It
also affects the behavior of the BCALCO output, so that the proper initialization value is made
available to the primary block.

Start-up Initialization (Unconditional Initialization)

Unconditional Initialization occurs whenever a PRIBLK undergoes block initialization, which
occurs when:
♦ The compound makes a transition to ON
♦ The CP reboots and the compound is ON
♦ The CP recovers from a power fail and the compound is ON
♦ The CIO Configurator performs an Add/Modify/Un-delete/LOADALL operation
with the compound ON.
Note that in response to block initialization, the block’s INITMA option asserts the Manual/Auto
state of the block before unconditional initialization occurs.
A block performs unconditional initialization by forcing its OUT parameter to take on the value
of its BCALCI input. The OUT value may then be subjected to output clamping, depending on
the Manual/Auto mode and the configured MCLOPT option. For example, if the block initial-
izes in Manual, then it performs clamping only if MCLOPT is configured to 1. The block always
performs clamping when it initializes in Auto.
Regardless of the state of its PRIBLK option, a block always performs unconditional initialization
whenever it starts up or receives, via the INITU bit of its BCALCI parameter, an unconditional
initialization request from its downstream secondary. The block then requests initialization to its
upstream primary block via the status bits of its BCALCO parameter (INITU), for one block
period when PRIBLK = 0, or until the upstream primary block confirms initialization with an
ACK status bit passed to the downstream block’s set point inputs when PRIBLK = 1. Uncondi-
tional initialization continues to ripple backwards, until it terminates at the beginning of the
cascade.
Since the upstream block specifically acknowledges receipt and action of the BCALCO status bit
from downstream, you must not connect BCALCO to multiple connections (to more than one
upstream block).
If all secondary blocks have their PRIBLK parameters configured to one, and a unconditional ini-
tialization sequence encounters either a block that is out-of-service or one in which the BCALCI
connections are in error (see Security Aspects), then the unconditional initialization request
remains pending at the last primary block that successfully completed initialization. When the
next primary block returns to normal operation, then the pending request continues to ripple
toward the beginning of the cascade. Therefore, unconditional initialization is always destined for
completion and takes precedence over any operational state of a block, including Manual.

34
4. Block Characteristics B0193AW – Rev R

Transfer-of-Control Initialization (Conditional Initialization)

Conditional Initialization is the action taken by a secondary block when control is transferred
back to its primary block; that is, a return to closed-loop operation. A transition to closed-loop
operation occurs whenever a secondary block that has its PRIBLK parameter configured to 1:
♦ Transfers from Manual to Auto, with its set point selected to Remote
♦ Transfers from Local to Remote set point, with the output in Auto and Controlling
♦ Experiences both of the above events simultaneously
♦ Undergoes a return-to-normal transition from a Bad I/O status (AOUT or AOUTR
only).
A secondary block with its PRIBLK option configured to 1 attempts to return to closed-loop
operation by requesting conditional initialization to its primary block. While waiting for its pri-
mary block to respond, it continues controlling, using the Local set point value in SPT. While in
this state, it ignores its remote set point RSP, even though the controller is switched to Remote. In
addition, it switches the live back-calculated set point output BCALCO to the held SPT value.
Thus, it maintains local control and can minimize any load upsets, while it waits for the primary
to initialize.
The action taken by the primary block, in response to a conditional initialization request, depends
on its Manual/Auto mode. If it is in Manual, it does not honor the request. It only honors the
request if it is in Auto by performing the same action as described for the case of unconditional
initialization. Thus, the primary block sets its output to the held SPT of the secondary block.
Transfer to closed-loop operation is completed when the secondary receives acknowledgment, via
the BCALCO/BCALCI parameter, from the primary. When acknowledgment occurs, the second-
ary begins tracking the RSP demand signal into its local set point SPT. In addition, the BCALCO
output switches from the held SPT value to the live back-calculated set point.
Therefore, transferring control to a primary block in Manual forces the secondary’s set point to
the Manual value. At the moment of transfer, any proportional action is transferred to the integral
term of the controller.
Transferring control to a primary block in Auto is performed bumplessly from the held set point
value.
On a return to closed-loop transition, the RSP connection must not have any detectable errors;
that is, the status bits of RSP must indicate that the primary is not Out-of-Service, Bad, or con-
nected with any OM scan errors. If any of these errors are detected, then the secondary block with
PRIBLK set to one continues to use the held local set point. When the error condition returns to
normal, the secondary block reasserts conditional initialization request to the primary, if it is still
switched to Remote and on Control.
Operation of the AOUT or AOUTR block during a transfer of control is analogous to the behav-
ior of a PID block, except that the roles of the MEAS and OUT are interchanged with those of
the RSP and SPT.
A transfer from Manual to Auto, Local to Remote, or Bad to Normal sets the appropriate
BCALCO status output to one. If PRIBLK is set to zero, the block resets the BCALCO status bit
to zero and resumes normal forward calculation at the next block period without waiting for
upstream blocks to initialize. However, an upstream block that is in Auto, and has the same
period, initializes properly.

35
B0193AW – Rev R 4. Block Characteristics

Set Point Behavior

A secondary block, with its PRIBLK set to one and its LR input set to Remote, does not track the
remote set point RSP to the local set point SPT while it waits for initialization acknowledgment
from its primary. Thus, the set point remains in a “pseudo” remote mode until the primary
performs either unconditional or conditional initialization. This is not indicated at the display.
However, the graphics portion of the Select displays indicate the different values between the RSP
and SPT parameters, while the initialization is pending. The two parameters begin tracking as
soon as initialization is completed.

Security Aspects
The block checks the BCALCI input for open loop status and connection errors of the
downstream block. This ensures proper handling of connections across compound and station
interfaces. The upstream block goes to the Hold state when the downstream block is either Bad,
Out-of-Service, or Disconnected.
If the secondary with PRIBLK detects an error condition on its RSP connection while it is closed
loop, the local set point holds the last good set point value until the connection returns to normal.
This action prevents possible process upsets under disruptive conditions, such as, configuration
modification of an upstream block, compound initialization of an upstream block, or reset of a
remote station. Upon return to normal, the downstream block requests conditional initialization.

NOTE
If a primary controller detects an error in its BCALCI connection, then it does not
honor any initialization requests from its secondary block.

Initializing PID Blocks in Auto/Manual

The PID blocks honor explicit initialization requests (that is, the BCALCI initialization status bits
set true) while in the Auto or Manual state, provided PRIBLK = 1 in the downstream block. The
process output initializes to the old value referenced by their BCALCI input parameter. The
sequence of events is as follows:
1. On the first execution cycle the block initializes and sets its OUT parameter to the
value of BCALCI. However, at this point the value of BCALCI from the downstream
block is left over from the last time the compound ran and thus, does not represent
the actual process output.
2. The downstream block is now processed and updates its BCALCO parameter to the
current process output value, setting its BCALCO initialization status bit to the PID
to request explicit unconditional initialization for the next BPC.
3. The PID runs on the next cycle, updates its output to the new BCALCI value, and
sets the Acknowledge bit in its output status.
4. The downstream block runs, detects the acknowledgment via its Measurement con-
nection, and bumplessly drives its output to the existing value.

36
4. Block Characteristics B0193AW – Rev R

Configuring Cascade Schemes

Standard Cascade Configuration
A cascade scheme consists of two or more blocks, with at least one having PRIBLK = 1, config-
ured in the manner depicted in Figure 4-2. Any number and consecutive combination of PID,
BIAS and RATIO blocks may be configured in a cascade. The cascade should have an AOUT
block at the end of the cascade. Figure 4-2 shows a typical two-loop PID cascade that illustrates
the standard connections required to configure a cascade.

PRIBLK = 0 PRIBLK = 1 PRIBLK = 1

SPT SPT
OUT RSP OUT MEAS

RSP PID PID AOUT

FBK FBK
BCALCO MEAS BCALCI BCALCO BCALCI BCALCO
MEAS OUT

Manipulated Variable

PNT PNT
AIN AIN
PNT_NO
FBM
Secondary Process Variable HW #4
Primary Process Variable
4AI/4AO

Figure 4-2. PRIBLK Cascade Standard Configuration

Each secondary block must be configured with its PRIBLK parameter set to one. The first con-
troller block at the beginning of the cascade has its PRIBLK set to zero. The AIN blocks have no
PRIBLK option.
Only two standard cascade connections between a primary (p) and a secondary (s) block are
mandatory:
OUT(p) ---> RSP(s)
BCALCO(s) ---> BCALCI(p)

In the case of a RATIO block, the RSP demand signal connection is replaced by OUT(p) --->
REMRAT(s); for an AOUT block, it is replaced by OUT(p) ---> MEAS(s); and for an BIAS
block, it is replaced by OUT(p) ---> RBIAS(s).
You set PRIBLK = 1 in all blocks after the primary controller, including the AOUT block. You set
PRIBLK = 0 in the primary controller. In each PID-type block, you connect FBK to the same sig-
nal as BCALCI.
Figure 4-3 shows the block connections for a normal cascade control scheme with feedback con-
trol. The AOUT block and the PID block interfacing to it have their PRIBLK option configured
true.

37
B0193AW – Rev R 4. Block Characteristics

from GC
PRIBLK = 0 PRIBLK = 1 PRIBLK = 1

SPT
OUT RSP OUT MEAS
PID PID AOUT
BCALCO BCALCI BCALCO BCALCI
MEAS FBK MEAS FBK BCALCO OUT

PNT PNT
Composition
AIN AIN
PNT_NO
Feedflow Valve
FBM FBM
Feedflow

Figure 4-3. Cascade Block Strategy with Feedback Control

When the AOUT block goes back on control (from either a Manual or Bad state) it initializes and
sets its BCALCO - INITC status bit.
When the downstream PID is processed, its BCALCI - INITC input status bit is set, so it per-
forms its own initialization and back calculation and sets its BCALCO - INITC output status bit.
The upstream block is processed in the same manner. The BCALCO parameter of the PID block
at the top of the cascade is not connected because there is no need for further upstream
initialization.
Note that the feedback input can be connected to the block’s output. However, you should con-
nect it to the same variable as BCALCI.
When PRIBLK is set to zero in all blocks, bumpless initialization occurs when all blocks start in
Auto and have the same period.
Like any connectable parameter, the BCALCI and BCALCO parameters can pass data between
blocks in the same compound, in different compounds, or in different stations. You should be
aware that connections between different stations adds to the time required for communications.
Figure 4-4 shows how initialization occurs between blocks in compounds residing in separate sta-
tions. Communication between compounds occurs when the output (or source) change exceeds
the DELTI parameter of the sink. To avoid offset or limit cycle behavior, it may be necessary to set
DELTI to zero, or a very small value, in the sink block. For example, in Figure 4-5, the DELTI2
parameter in the RATIO block would be set to zero, or a small value, to avoid steady state control
error.

38
4. Block Characteristics B0193AW – Rev R

Station A Station B

from GC
PRIBLK = 0 PRIBLK = 1 PRIBLK = 1

SPT
OUT RSP OUT MEAS
PID PID AOUT
BCALCO BCALCI BCALCO BCALCI
MEAS FBK MEAS FBK BCALCO OUT

Composition PNT PNT

AIN AIN
PNT_NO PNT_NO
Feedflow Valve
FBM FBM
Feedflow

Compound FEEDCOMP Compound FEEDFLOW

Figure 4-4. Cascade Handling Between Two Compounds Across Stations

Again, as in Figure 4-3, all the blocks except the first (primary) controller have their PRIBLK
option configured true.
Figure 4-5 shows the initialization connections for a cascade control scheme with feedforward
control.

from GC
PRIBLK = 0 PRIBLK = 1 PRIBLK = 1

SPT

PID RATIO AOUT

OUT REMRAT OUT MEAS
BCALCO BCALCI
MEAS FBK BCALCO MEAS BCALCI BCALCO OUT

Composition PNT PNT

AIN AIN
PNT_NO PNT_NO
Feedflow Valve

FBM FBM
Feedflow

Figure 4-5. Cascade Block Strategy with Feedforward Control

External Integral Feedback

The external integral feedback input FBK of a PID controller is decoupled from the BCALCI
input to provide the maximum flexibility for controlling PID integral action and anti-windup,
without having to compromise initialization requirements. Under almost all conditions, FBK and
BCALCI should be linked to the same source variable.

39
B0193AW – Rev R 4. Block Characteristics

Figure 4-2 shows the recommended FBK connection for obtaining external integral feedback, or
PID integral action. With this configuration, a PID controller provides integral action only as
long as its integral feedback loop remains closed and tracks its own output. Therefore, in a cascade
scheme, integral action at the primary block occurs only while the secondary controller’s measure-
ment tracks its remote set point.
When the integral feedback loop becomes open, the integral action of the primary block stops.
This behavior is an old analog scheme to prevent integral windup of the primary controller. It is
especially useful in configurations where multiple primary controllers are fanned into a single sec-
ondary controller using a SIGSEL block. When an OUTSEL block is used in conjunction with
PIDA blocks, integral windup is prevented by logic signals transmitted with the
BCALCO/BCALCI connections, provided LIMOPT in the PIDA blocks is set to 1 or 2.
If you desire to eliminate the external integral feedback behavior entirely, then connect FBK to
the PID’s output. This connection provides classic integral action, since the external integral feed-
back loop is closed when the controller output is not limited. This configuration is not recom-
mended because it provides no primary integral windup protection for a non-PIDA or for a PIDA
with LIMOPT = 3 when the secondary output is at its limit. Also, the primary loop cannot be
tuned as tightly.
Integral windup is not a real concern when FBK and BCALCI are tied together in cascades that
utilize Explicit Initialization or the PRIBLK feature, since BCALCI forces the primary block to
track (in Auto) and initialize properly.

Error Handling
In general, error handling is resolved at the application level. It is accomplished through explicit
user configuration of alternate control strategies based upon specific error conditions.
These error conditions are contained on a per-parameter basis within the status record for con-
nectable parameters and shared variables.
In the status record three variables provide information with regard to the validity of the data and
the validity of the connection. These are called Bad, Connect, and Out-of-Service.
The Bad status is set and reset by the block algorithm dependent upon block application.
The Out-of-Service status is set and reset by all blocks to indicate the unavailability of input data
or data dependent upon unavailable inputs.
The Connect status indicates whether any problem exists in regard to the source of a connected
parameter. Such problems include deleted source blocks, nonexistence of source compounds, or
peer-to-peer path failures.
Implicit error handling is performed at the block level according to the following:
♦ If the data or the connection to the data is bad, or if the data is not updated, then cer-
tain controller type blocks (for example, PID, PTC) perform appropriate error
handling. This is dependent upon the specific parameter and algorithm application.
♦ Most control and I/O blocks support the Propagate Error Option (PROPT). When
true, this option sets the ERROR status of the primary output when the input is in
error.
♦ I/O-type blocks also have a connectable BAD parameter for explicit error-handling
purposes.

40
4. Block Characteristics B0193AW – Rev R

♦ For some block types, the error status is not propagated to the output parameters. The
user can explicitly program downstream blocks to react using the AIN output param-
eters BAD, LOR, and HOR.
♦ Most PLC (Programmable Logic Controller and DCI (Distributed Control Interface)
blocks do not provide any alarm detection or reporting capabilities.
Implicit error handling is coupled with the initialization parameters defined for the I/O and
Control-type blocks. The initialization status bits of BCALCO are set according to several algo-
rithm states, one of which is the error state.
In Figure 4-3, if the flow measurement becomes bad, then the AIN block does not update its out-
put and sets the corresponding bad status. If the LASTGV parameter in the AIN block is config-
ured true, the last good value and the error status are picked up by the flow PID measurement.
The PID algorithm performs its error logic, which consists of setting the INITU or INITC status
bit in the BCALCO parameter and transferring to a Hold or Manual state dependent upon the
option. The BCALCO parameter then explicitly propagates the error notification to the upstream
block.

Clamping
Clamping is performed on certain parameters dependent on the specific function. Clamping is
performed as follows:
♦ For any parameter that has a system-specified range, the value written to the parame-
ter is clamped by the block within the specified range. The clamped value is
overwritten into the parameter and used by the algorithm.
♦ In general, clamping is only performed on block outputs. The actual clamped value is
at range ± output span variance (OSV). The default settings are 0-100% for the range,
and 2% for OSV. For the default settings, the actual clamp occurs between -2% and
102%. The maximum allowable value of OSV is 25%.
♦ The clamping of the OUT parameter in the following blocks is performed in identical
manner: PID, PIDE, PIDX, PIDXE, PIDA, DPIDA, BIAS, RATIO, AOUT, and
AOUTR. The algorithm is as follows:
If LOLIM < LSCO1 - OSV, set LOLIM to LSCO1 - OSV
Else if LOLIM > HSCO1 + OSV, set LOLIM to HSCO1 + OSV
After LOLIM is thereby brought into range, HOLIM is prevented from being less
than LOLIM:
If HOLIM < LOLIM, set HOLIM equal to LOLIM
Finally, HOLIM is prevented from exceeding the high end of the range:
If HOLIM > HSCO1 + OSV, set HOLIM to HSCO1 + OSV

Scaling
Real-type data represents continuous-time process variable signals that relate to physical units and
range. Real-type parameters have associated user-specified range and unit parameters.
Certain blocks like AIN, PID, RATIO, BIAS, RIN and others require scaling when the output
and input engineering units differ.

41
B0193AW – Rev R 4. Block Characteristics

Scaling factor parameters are incorporated into these blocks to enable the algorithm to account
for range differences. You can enter the appropriate scaling factors during configuration. Some are
user-specified, others are calculated by the block.
Ranges for associated parameters are always stated. For example, set point must have the same
units and range as measurement; and feedback the same units and range as output.

Secure/Release
A secure/release mechanism is supported on a per-parameter basis. For connectable input parame-
ters (real, Boolean, integer), the secure/release mechanism is governed by the type of connection.
If the parameter has an established linkage, it is automatically secured. If there is no linkage (con-
nection), it is available to all users until someone secures it.
It is the responsibility of the higher level task or program to arbitrate securing any parameter at
the source end. This is done automatically when parameters are opened in OM Write lists.
Outputs are secured and released by the block algorithm according to certain modes (for example,
M/A, L/R, and so forth) and definitions. Some parameters are never settable, therefore they are
always secured. All primary outputs are governed by the Manual-Auto function.
Some specific actions involving block input parameters include:
♦ Unlinked inputs are released during CP reboot to allow for user access
♦ Linked inputs are secured when a block initializes and can no longer be released by the
user
♦ A Controller block which has its LOCSP option configured true, secures the LR
parameter when the block initializes. LOCSW and REMSW overrides have higher
precedence, but LR stays secured when LOCSW and REMSW are no longer asserted.
Inputs to ECBs are not secured. If two AOUT blocks are configured to drive the same FBM out-
put channel, a warning message is displayed at the control configurator and/or the default display,
for each of the blocks. The blocks are not prevented from executing, however, since the duplicated
output channel may be an intentional part of the control strategy. (The two blocks may be in
compounds which are never ON at the same time, for example.) If the duplication of the output
channel is unintentional and the warning message is ignored, unpredictable results ensue, includ-
ing possible process upset.

Control Block Fail-safe Strategy

Fail-safe Support is implemented in the following blocks:
♦ AOUT or AOUTR block
♦ Analog controller blocks (PIDs, RATIO, BIAS)
♦ Propagation through SWCH blocks.
When the block processing logic detects that an FBM containing an analog output has asserted
Fail-safe, an FS Boolean output is set in any AOUT (AOUTR) block connected to that FBM.
Also the FS block status bit (bit 24 of BLKSTA) is set in the AOUT (AOUTR) block.
The Fail-safe status can be propagated upstream in a cascade to analog controller blocks via an FS
status bit (BCALCO.FS) in the BCALCO-BCALCI connection in analog controller blocks or in
a SWCH block.

42
4. Block Characteristics B0193AW – Rev R

The Manual Fail-safe (MANFS) option can be configured in AOUT (AOUTR) blocks and in
analog controller blocks. If the MANFS option is set, the block is set to the Manual mode when
Fail-safe is detected.
The FS BLKSTA bit is set in the analog controller blocks under these conditions:
♦ The analog controller block is in the Auto mode
♦ The analog controller block is in the Manual mode and its MANFS option is set.
If PRIBLK is configured, the AOUT (AOUTR) block also requests the unconditional initializa-
tion of the upstream blocks via its BCALCO output when Fail-safe is detected.
Once set, the FS BLKSTA bit and the FS Boolean output remain set in the AOUT (AOUTR)
block until one of these events occurs:
♦ The block is in Manual, and the output parameter is changed by the you
♦ The block makes a transition from Manual to Auto
♦ PRIBLK is not configured, and the block is in Auto
♦ PRIBLK is configured, and the initialization acknowledgment is received from the
upstream block.
Once set, the FS status bit remains set in the analog controller block until one of these events
occurs:
♦ The block is in Manual, and the output parameter is changed by the operator
♦ The block is in Auto and the downstream cascade closes
♦ The block makes a transition from Manual to Auto.

PID Hold Constraint

A PID block may optionally be driven to the Hold state, in which the block’s OUT parameter is
not changed by block action and is secured against setting, by two methods:
♦ Explicit Hold action, produced by the true state of the HOLD parameter. The block
goes into this explicit Hold state whenever HOLD is true, the block is in Auto, and
parameter MBADOP is false.
♦ Implicit Hold action, which depends on the value of CEOPT. When CEOPT = 0,
there is no Implicit Hold action. When CEOPT = 1, the block goes into the Hold
state whenever a basic input parameter has Bad, Out-of-Service, or off-scan status.
When CEOPT = 2, the block goes into the Hold state whenever a basic input param-
eter has Bad, Out-of-Service, off-scan, or Error status. The basic input parameters are
MEAS, FBK, and BCALCI. As in the case of Explicit Hold, the action requires that
the block be in Auto, with MBADOP false.
Bad status for MEAS, when the PID block’s immediate upstream connection is an AIN, AINR, or
MAIN block, is in turn dependent on several factors, as follows:
♦ If the FBM or FBC has Bad status, the output PNT or PNT_x has Bad status, and
therefore MEAS has Bad status.
♦ If the connected point in the FBM or FBC has Bad status, PNT or PNT_x and
MEAS has Bad status.

43
B0193AW – Rev R 4. Block Characteristics

♦ If the measurement at the analog input point is determined by the AIN, AINR, or
MAIN block to be out-of-range, then HOR or LOR is set true, and, in some circum-
stances, PNT or PNT_x will have Bad status. Parameter BADOPT in the AIN,
AINR, or MAIN block governs whether range violation causes Bad status, in accor-
dance with the following rules:
♦ BADOPT = 0: Neither HOR nor LOR causes Bad status.
♦ BADOPT = 1: LOR causes Bad status.
♦ BADOPT = 2: HOR causes Bad status.
♦ BADOPT = 3: Both HOR and LOR cause Bad status.
In general, the signal values at which the input block declares the point status LOR or HOR, are
approximately lower range value for the low end, and approximately upper range value for the
high end, depending on the value of OSV. However, the actual determination of HOR/LOR sta-
tus depends on the details of the signal conditioning in use for the point. [See Integrated Control
Block Descriptions (B0193AX).]
For FBM types 1 and 4, there is much greater latitude on the low end of the signal span when you
use elevated-zero signal conditioning (that is, 4 to 20 mA with an SCI of 3, 5, or 7). However,
there is very little headroom on the high end of the signal span, regardless of elevated-zero signal
conditioning.
In the AIN, AINR, and MAIN blocks the Bad status of PNT or PNT_x is always identical to the
block’s BAD output parameter.

44
5. Block States
This chapter describes various block states, including the shutdown, define, bad, and
manual/auto states, as well as the block status parameter (BLKSTA) and status indicators and
events.
Block states comprise both System states and Application states. System states result from:
♦ Mismatching or undefined FBM/ECB identifiers
♦ Incorrect or out-of-range parameter values
♦ Off-line/On-line switching
♦ Any other action other than Manual/Auto switching.
The System states are:
♦ Shutdown
♦ Define
♦ Bad.
The Application states under block control are:
♦ Manual/Auto
♦ Local/Remote.

Shutdown State
Shutdown is the state the block exhibits when its compound is off-line, that is, it is turned off by
the compound processor (via Compound On/Off). It is essentially a wait state until the com-
pound goes back on-line.
This event causes a state transition out of the Shutdown state to one of the application states,
Manual or Auto. The block initializes when it asserts this state transition.
Conversely, when the compound is turned off, it causes the block to make a transition out of its
present application state back to the Shutdown state.
In this state:
♦ All connectable parameters are released
♦ The last values, or block history, is saved and maintained
♦ The Out-of-Service status of all value records is set true.
This action notifies other users, which have connections to this block, that the block has been
taken off-line. At Shutdown, all previous history is saved.

45
B0193AW – Rev R 5. Block States

Define State
During initialization, the block validates critical configuration parameters prior to performing a
state transition out of the shutdown state. If validation is successful, the block reverts to an Appli-
cation state, Manual or Auto, depending on the value in INITMA. However, if any of these criti-
cal parameters are not within their legal range, the block will avert going on-line by performing a
state transition back to the Shutdown state and declaring itself Undefined.
During installation, a block will be installed and placed in the Undefined state when an input
connection, specified to a source block residing in the same station, experiences any of the follow-
ing errors:
♦ The source parameter is nonconnectable.
♦ The source parameter name is invalid for its block type.

Bad State
The Bad state results from I/O-related errors, for example, mismatching FBM and ECB identifi-
ers, or bad inputs and handling, or non-operational FBMs.
This Bad status is included as a quality attribute (bad) of the output parameter of input-type
blocks.
In the Bad state:
♦ The AOUT or AOUTR block’s BCALCO initialization status bit is set
♦ Outputs are marked Bad and Secured
♦ The last driven state is retained.
When the data is validated and the block is not Bad, the outputs are reset, marked good, and the
block returns to either Manual or Auto.

Bad Detection
The first checks for a bad input take place in the FBM. Part of the FBM error detection includes
a “bad channel status” test that includes a check of the hardware signal to determine if that signal
exceeded the range of the A/D converter (that is, the signal value was at zero or at its maximum
value). Also included as part of the “bad channel status” test is a rate of change check (assuming
that the ROC parameter of the associated ECB block is a non-zero value) which detects when a
measurement value changes faster then the configured limit and consequently marks the input
channel bad. The “bad channel status” bit that is sent with the raw data value to the analog input
block (via the ECB) is an indicator of the results of these tests which includes other internal FBM
diagnostic checks for erroneous raw data conversion.
The ECB receives the raw data and the channel status, and adds an “ecb_status” which is resolved
at the ECB interface and indicates the availability of the FBM. “ecb_status” is set when the FBM
is not available because it is either not operational, or the path to it (the PIO bus) is in error.
These three entities, raw data, channel_status, and ecb_status are directed to an analog input
block (AIN, AINR, or MAIN). AIN, AINR, and MAIN blocks handle Bad detection identically.

46
5. Block States B0193AW – Rev R

CP
AIN

Data raw data raw data (ch.n)

A
Handling I channel_status channel_status
ECB . FBM
N ecb_status .
CHANNEL n .
Raw Data raw data raw data (ch.1)
O-O-R channel_status channel_status
Hi
Lo Test OR ecb_status
CHANNEL 1

bad status
OR OR
bad
0 bad_status AND BAD to
lor 1 bad_status + lor
bad_status + hor MA
hor 2 pnt.bad other
3 bad_status + lor + hor

BADOPT bad = blocks

BLKSTA bit 12

Figure 5-1. Bad Detection

The AIN or AINR block uses the logical OR of the two status bits, channel_status and
ecb_status, to produce the internal signal, bad_status. If bad_status is true, the input is Bad for all
values of BADOPT, and, when the block is in Auto, the BAD output parameter, the PNT.Bad
status bit, and the BAD bit (bit 12) of the BLKSTA output are all set true.
The raw data goes to two functions.
The raw data goes to the data handling algorithm to produce an output value determined by the
input and the configuration. If the converted value exceeds the normalized signal span specified
by the HSCO, LSCO, and OSV parameters, output clamping occurs. This output clamping acti-
vates one of two signals to indicate that the output is clamped at the high, or low, end of the span.
The raw data also undergoes a raw data out-of-range test to ensure that the data, as received by the
AIN or AINR block, is within the raw signal range in those cases (for example, square root extrac-
tion or table lookup linearization) where an out-of-range input might not produce a limited out-
put. If the data is out-of-range, the block activates one of two signals to indicate that the input is
outside the high, or low, end of the input range.
The results of these two functions at each end of the span are combined to yield two out-of-range
signals. The signal that indicates the output is clamped at the high end, is OR’d with the signal
that indicates the input was too high, to produce the internal signal “hor” (high out-of-range).
Likewise, the two low indicators are OR’d, to produce the internal signal “lor” (low out-of-range).
One, or both, of these signals (“hor” or “lor”) may be included with the bad_status signal
(depending on the configuration of the BADOPT parameter) in the determination of a Bad
input. BADOPT (Bad and Out-Of-Range option) is a nonconnectable, nonsettable, integer
input that determines the conditions that, when the block is in Auto, make the BAD parameter
output, the PNT.Bad status bit, and bit 12 (BAD) of the BLKSTA output, all true.

47
B0193AW – Rev R 5. Block States

The BADOPT value ranges from 0 to 3 and map to the following conditions:

0 Bad_status
1 Bad_status or Low Out-of-range
2 Bad_status or High Out-of-range
3 Bad_status or Low Out-of-range or High Out-of-range.

When an out-of-range condition causes a Bad input condition, the block takes the following
actions:
♦ Sets the appropriate HOR or LOR parameter.
♦ Sets the point Bad status, the BAD output parameter, and the BAD bit in the
BLKSTA parameter.
♦ Activates the BAD alarm, if configured.
The default value of BADOPT is zero. The High and Low out-of-range conditions will set the
BAD output when the BADOPT parameter is defaulted.

Manual/Auto States
Manual/Auto are Application states. Most blocks support the parameter MA for their primary
outputs. MA is a Boolean input that controls the Manual/Auto operational state of the block’s
output(s). The nonsettable outputs of a block are not under MA control.
In Manual, the output is unsecured, which makes it an input or an independent variable from any
external process. In Manual, the block:
♦ Unsecures the settable output parameter(s)
♦ Retains real type output values from last values while in Auto. (Exceptions: Man
clamp and Man alarm options.)
♦ Clears Boolean-type outputs on initial transition.
In Manual, any task or process is allowed to write to settable outputs through SET calls. The out-
puts become available to all users.
In Auto, the block secures its settable outputs, which makes them dependent variables that are
determined by the substate of Auto (for example, Hold, Track, Control). On a transition to Man-
ual, the output is held for reals but is cleared for Booleans. In Auto the block:
♦ Secures its primary settable output parameter(s)
♦ Updates them according to the algorithm.
The following, Figure 5-2, shows a block state transition diagram.

48
5. Block States B0193AW – Rev R

System-Related States
Compound Turned On Operational States
(Application
Start Dependent)
Ok

Block Parameter Initialize Block MA

Man
Validation
FBM Operational
Bad Validation Error or Bad IO
MA MA
Error Channel
Undefined Connectable Bad MA
Parms Auto
Clear Define Primary
Turned
Output(s) Ok
Off,
Marked
Released, Bad
Connect- “Bad” &
Shutdown And Set
able Secured
Not Bad
Parms
Turned Update Block
Legend State
Off, Output to FBM
Compound Released Decision Read-Back Value
Turned Off Logic Condition
From Any State Action

Figure 5-2. Block State Transition Diagram

BLKSTA – the Block Status Parameter

Block Status (BLKSTA) is a connectable, 32-bit output that is bit mapped to indicate the block
operational states at the time the block status is read.
Each individual block description in Integrated Control Block Descriptions (B0193AX) identifies
the bits that make up the BLKSTA parameter for that block.
A list of all the bits that can be assigned to the BLKSTA parameter and their indicated block state
follows:

Table 5-1. BLKSTA-Assignable Bits

Boolean
Connection
Bit No. Indicated Operational State Extension
31 (MSB) FLB Supervisory Control Fallback State BLKSTA.B1
30 SC Supervisor Control BLKSTA.B2
29 SE Supervisor Enabled BLKSTA.B3
28 HOL High Output Limit (Clamped) BLKSTA.B4
27 LOL Low Output Limit (Clamped) BLKSTA.B5
26 MAO Manual/Auto Override BLKSTA.B6
25 LRO Local/Remote Override BLKSTA.B7
24 FS Fail-safe BLKSTA.B8

49
B0193AW – Rev R 5. Block States

Table 5-1. BLKSTA-Assignable Bits (Continued)

Boolean
Connection
Bit No. Indicated Operational State Extension
23 DSB Disabled; MO Manual Override (MDACT, DPIDA) BLKSTA.B9
22 DSR DSR Mismatch (GDEV); DF Device Fail BLKSTA.B10
(MDACT DPIDA)
21 ILK Interlock; RED Redundant Inputs (DPIDA) BLKSTA.B11
20 WLCK Workstation Lock BLKSTA.B12
19 SBX Executing SBX Statements (Sequence blocks); TEST BLKSTA.B13
Test Mode (PLB); HRQ Hold Request (MDACT);
DEV Redundant MEAS input deviation limit (DPDIA);
Set Point Ramp Up (PIDA)
18 PAUS Paused (DEP); SIM Simulation Mode (PLB); BLKSTA.B14
INER Input Error (OUTSEL)
17 TRIP Tripped (MON); FTN Feedforward Tune Active BLKSTA.B15
(PIDA, DPIDA); LM2 Limit Switch 2 On (GDEV);
RAMP Ramp Option (RAMP)
16 ACT Active/Inactive (Sequence blocks); FTNI Feedfor- BLKSTA.B16
ward Tune Inactive (PIDA, DPIDA); REPT Repeat
Option (RAMP); LM1 Limit Switch 1 On (GDEV)
15 ON Compound On BLKSTA.B17
14 UDEF Undefined BLKSTA.B18
13 (Unused) BLKSTA.B19
12 BAD Bad I/O (I/O Blocks only - block in BAD state) BLKSTA.B20
11 MA Manual(= false)/Auto(= true) BLKSTA.B21
10 LR Local(= false)/Remote(= true) BLKSTA.B22
9 STRK Set Point Tracking; FBMR Redundant FBM Fail BLKSTA.B23
(AINR, AOUTR)
8 FBM FBM Failure BLKSTA.B24
7 HLD Holding BLKSTA.B25
6 TRK Tracking BLKSTA.B26
5 CTL Controlling; ACC Accumulating (ACCUM); RMP BLKSTA.B27
Ramp (RAMP)
4 FOL Follow; ASP Alternate Set Point (MDACT); DEV BLKSTA.B28
DEV Redundant I/O Deviation (DPIDA)
3 (Unused) BLKSTA.B29
2 PTN Pre-Tune Mode (EXACT tuning algorithm) BLKSTA.B30
1 STN Self-Tune Mode (EXACT tuning algorithm); BADR BLKSTA.B31
Bad Redundant I/O (AINR, AOUTR)
0 MTN Manual Tune Mode (EXACT tuning algorithm); BLKSTA.B32
SEL Redundant I/O Selected (AINR)

50
5. Block States B0193AW – Rev R

BLKSTA provides bit-mapped status indication of bad I/O, Manual/Auto, and other block states.
1. HOL and LOL are mutually exclusive, set false on a transition to manual, and
updated when the block output is clamped.
2. ON is true whenever the compound that includes this block has its ON parameter set
true.
3. UDEF indicates that, during initialization, the block was unable to validate critical
configuration parameters, and returned to the shutdown state.
4. BAD is set true in an I/O block when the block detects a bad input channel or,
depending on the BADOPT configuration, data that is out-of-range.
5. MA indicates the Auto/Manual state of the block (true = 1 = Auto;
false = 0 = Manual).
6. LR and STRK are mutually exclusive, initialized to the appropriate set point state, and
updated when state transitions occur.
7. FBM is set true when the FBM is found to have bad status.
8. HLD, TRK, CTL, and FOL are mutually exclusive substates of the Auto state, initial-
ized to the appropriate block state and updated when block state transitions occur.
9. PTN, STN, and MTN are mutually exclusive, initialized to the appropriate tune state
and updated when tune state transitions occur.
The BLKSTA parameter is set to zero when a block initializes.
BLKSTA can be accessed by application programs. It can also be accessed by other blocks having
long (32 bits) integer inputs that can be handled as packed Booleans (for example, the MCIN
block when the IOMOPT option is configured false, or the CALC block).
Table 6-1 indicates, in alphabetical order, the literal names assigned to the individual bits of
BLKSTA. These names may be used in Boolean connection extensions (for example,
BLKSTA.LOL).

Block Status
This section discusses two aspects of block status: indicators and events.
Control and I/O blocks are equipped with status indicators to:
♦ Indicate the current block status
♦ Indicate the nature of the event that caused that status
♦ Provide inputs to the control scheme that may initiate an appropriate response to that
event.

Status Indicators
Three types of status indicators that Control and I/O blocks use are:
1. The BAD parameter – a dedicated boolean output of the AIN, AINR, AOUT,
AOUTR, CIN, COUT, EVENT, MAIN, MCIN, MCOUT, MDACT, MTR,
MOVLV, and VLV blocks. Control blocks typically use BAD as a source parameter
for determining control strategy.

51
B0193AW – Rev R 5. Block States

2. Bits from a parameter’s value record status word. The only bits available as named
sources in Control Configurator connections are:

PARM.B (Bad)
PARM.E (Error)
PARM.O (Out-of-Service)
PARM.D (Disconnected)

(PARM represents the name of any parameter.) See “Connections to Source Status”
on page 59.
In addition, user-written software applications may access any of the 16 bits of the
value record status word. These bits are defined as follows:

Table 5-2. Parameter Status Bits

Version 4.1 or Earlier Version 4.2 or Later

Bit Status Bit Status Signal Value
0-4 TYPE 0-3 TYPE
4 Used only in
setval call
5-7 OM 5-7 OM
8 BAD 8 BAD 1= Bad I/O
9 SECURE 9 SECURE/FS 1= Secure/Fail-safe
10 ON 10 INITC/ACK 1= InitC Request/Acknowledge
11 OOS 11 OOS 1= Out-Of-Service
12 SHADOW 12 SHADOW 1= Shadow Parameter
13 ACK 13 LHI 1= Limited High
14 14 LLO 1= Limited Low
15 ERROR 15 ERROR/INITU 1= Error/InitU Request

3. Bits from the 32-bit packed long status parameters, Block Status (BLKSTA) and
Alarm Status (ALMSTA).
The following paragraphs provide some examples of the events that activate some of these
indicators.
1. BAD parameter – Set TRUE when:
The FBM or FBC has failed, or the input point has bad status.
2. Parameter Value Record Status Bit – PARM.Bad
Set TRUE when:
a. An input block detects a bad I/O channel.
b. An AIN, AINR, or MAIN block detects an out-of-range value if BADOPT is
configured to respond to it.

52
5. Block States B0193AW – Rev R

c. An MCIN block receives an invalid BCD input.

Set FALSE when:
A compound owning an input/output parameter is turned ON.
3. Parameter Value Record Status Bit – PARM.Oos (Out-of-Service)
Set TRUE when:
a. A compound owning the input/output parameter is turned OFF.
b. The FBM or FBC is out-of-service.
Set FALSE when:
A compound owning an input/output parameter is turned ON.
4. BLKSTA Bit 8 – FBM Fail
Set TRUE when:
a. The block loses FBM communications or the FBM has failed.
5. BLKSTA Bit 12 – Bad I/O
Set TRUE when:
a. An input block detects a bad I/O channel.
b. An MCIN block receives an invalid BCD input.

Status Events
Among the events that activate these indicators are:
♦ Loss of FBM communications (permanent or temporary)
♦ Compound turns OFF
♦ Compound turns ON with, or without, errors
♦ Block initializes with fatal validation errors
♦ An I/O block has an unresolved ECB linkage
♦ An I/O block receives a Bad ECB status
♦ An I/O block receives a Bad channel status
♦ An I/O block receives an out-of-range value
♦ Block has a source connection resolved
♦ Block has a source connection deleted
♦ Block installation
♦ Block modification with, or without, specified linkage
♦ Download with resolved, or unresolved, linkage.
The following provide examples of the block indications shown at some of these events.
1. Loss of FBM communications.
a. The I/O blocks connected to the lost FBM set their BAD parameter true.
b. The I/O blocks connected to the lost FBM set their BLKSTA Bit 8 (FBM Fail)
true.
c. The OOS bits in the input/output parameters of any connected blocks are set
true.

53
B0193AW – Rev R 5. Block States

d. The output I/O blocks connected to the lost FBM set the BCALCO initialization
status bit true.
2. Loss of FBM communications – temporary (for example, PIO bus switch).
a. The I/O blocks connected to the lost FBM set their BLKSTA Bit 8 (FBM Fail)
true.
b. The OOS bits in the input/output parameters of any connected blocks are set
true.
c. The output I/O blocks connected to the lost FBM set the initialization status bit
of BCALCO true.
3. Compound turned OFF.
The OOS bits in the input/output parameter records of each block in the compound
are set true.
4. Compound turns ON (no block errors).
a. The OOS bits in the input/output parameter record of each block in the com-
pound are reset.
b. The BAD bit in each input/output parameter record is reset.
5. Compound ON and I/O block has a bad channel status.
BLKSTA Bit 12 (Bad I/O) is set.
6. Compound ON and AIN, AINR, or MAIN block receives out-of-range data.
BLKSTA Bit 12 (Bad I/O) is set if BADOPT configured correctly.
7. Source connection broken – for example, source deleted, source resides in a
nonexistent compound, or there is a peer-to-peer path failure.
The OOS bit in the sink parameter record is set.
8. Source compound turned OFF.
The OOS bit in the sink parameter record is set.
9. MCIN block receives an invalid BCD input.
Bit 12 (Bad I/O) in the block status parameter BLKSTA is set.

54
6. Connections
This chapter describes various aspects of process connections, including shared variables, linkage
syntax, boolean and packed boolean connection extensions, default values for integer and real
connections, and mixed data types.
Process connections between blocks, or blocks and shared variables, are long-term secured con-
nections that are established through the Integrated Control Configurator.
A block output to an FBM point is not a secured connection. The user must confirm that no
more than one output block is attached to an FBM point at a time.
A local “block-to-block” parameter linkage is a direct connection from the source parameter to
the receiver in the local database and does not involve the Object Manager.
A remote connection between two parameters in different stations is established by the Object
Manager, which maintains a change-driven read connection from the source to the receiver.
Linkages from blocks in the compound database to application programs is through shared
variables.
Short-term connectionless access from application programs is established through GET/SET
calls. Access security is determined at the host or source by setting the Secure flag in the shared
variable status (GET/SET calls).
GET calls to any parameter in the database, including local algorithm variables, are allowed.
SET calls are monitored for validity of data type, range, setability attribute, and secured/ released
status.
If necessary, the data value may undergo algorithm validation, for example, clamping.
For more information on GET/SET calls, refer to Object Manager Calls (B0193BC).

Shared Variables
A shared variable acts as a unidirectional linkage between an application and the control database.
By linking a shared variable to a block input, the configurator can establish a long-term secured
connection between a remote application program and the compound processor database.
The actual connection is made by the Object Manager which establishes a change-driven read
connection to the block input from the application program via the shared variable.
The application program sets and resets the secure, bad, and on/off flags in the shared variable
status.

55
B0193AW – Rev R 6. Connections

Linkage Syntax
The general format of linkage specifications entered at the Integrated Control Configurator is, as
noted in “Blocks” on page 13:
Compound:Block.Parameter (Cname:Bname.Pname)
or, if internal to one compound or one block:
:Block.Parameter (:Bname.Pname)

Boolean Connection Extensions

If the sink is of Boolean type, then the format:
Cname:Bname.Pname.Extension
may be used to refresh the sink with a wide variety of logical functions of bits within the source
parameter. The source parameter may be of any data type. Both local and peer-to-peer connec-
tions of this type may be made. Although certain restrictions apply based on the type of the
source, the following functions may be requested in the general case, by appropriate “extension”
syntaxes:
♦ Extract a specific bit from the source and copy it to the sink.
♦ Bitwise AND the source with a specific mask and copy the result to the sink.
♦ Bitwise XOR the source with a specific mask and copy the result to the sink.
♦ Perform the AND or XOR on only the high order integer of a Long or Packed Long
source.
♦ Clear specific bits of the sink.
♦ Copy specific bits from the status word of the source value record.
♦ Copy the logical OR of various status bits from the source status word.
♦ Perform similar actions with named bits of source parameters BLKSTA, ALMSTA, or
INHSTA.
♦ Invert the extracted result before using it.
♦ In connection with any of these options, specify a default/fallback value for the sink in
the event the connection is unresolved or the source is BAD or OOS. When the block
is installed, the sink value will be initialized to this default (0/1) value.

NOTE
By connecting the boolean input to itself and specifying a default value, this feature
will allow you to create a boolean constant of 0 or 1 that cannot be changed without
reconfiguring the connection. In addition, this feature may be used to pre-configure
deterministic fallback states for any boolean input that is connected peer-to-peer to
a source parameter in a different station.

If you enter invalid extension information, the connection will be marked Unresolved, the block
will be set Undefined, and the OM Scan status of the input will be set to 0.

56
6. Connections B0193AW – Rev R

The general format of connections to Boolean inputs is one of the following:

Cname.Pname.Extension (Connection to a compound parameter.)

Cname:Bname.Pname.Extension (Connection to a parameter in a different compound.)
:Bname.Pname.Extension (Connection to a parameter in another block of the
same compound or to another parameter of the same
block, or to itself.)

The general format of the Extension field in the above is:

[{0,1}.] [{~, [~]Bbit, [~]{A,X}[H]mask, [.][~] symbol}]
where:
[ ] = optional
{,} = select one
The syntax of the Extension field is best understood by noting the specific examples in the follow-
ing paragraphs. These examples are subdivided into the categories Connections to Source Data,
Connections to Source Status, and Connections to Status Parameters.

Connections to Source Data

The optional characters 0. or 1. at the beginning are used to specify an initial default and fallback
value for the sink. They may be used alone or in conjunction with other fields. When used alone,
the terminal period is deleted.
Examples:

Cname:Bname.Pname.1 Set default result = 1. If connection broken, set result = 1.

\]Else set result = source.
The tilde (~) is used to invert the Boolean result.

Examples:
Cname:Bname.Pname.~ If source = 0, set result = 1. If source non-zero, set result = 0.
Cname:Bname.Pname.1.~ Set default result = 1. If connection broken, set result =1.
Else if source = 0, set result = 1, and if source is non-zero,
set result = 0.

The selected option “Bbit” causes the result to be set equal to the specified bit of the source, where
B1 is the high-order bit. The “bit” specification indicates which bit is selected. There is no space
between “B” and “bit”. “Bit” must be a 1-or 2-digit decimal number which is in range for the data
type of the source (that is, no higher than 16 if the source is an Integer or Packed Boolean, and no
higher than 32 if it is a Long or Packed Long).
The only allowable source types are Integer, Long, Packed Boolean, or Packed Long.
The result is subject to optional inversion.

57
B0193AW – Rev R 6. Connections

Examples:

Cname:Bname.Pname.B12 Set result = Boolean 12 of source.

Cname:Bname.Pname.0.B12 Set default result = 0. If connection broken, set result = 0.
Else set result = Boolean 12 of source.
Cname:Bname.Pname.~B12 Set result = inverse of source Boolean 12.
Cname:Bname.Pname.0.~B12 Set default result = 0. If connection broken, set result = 0.
Else set result = inverse of source Boolean 12.

The selected option “Amask” or “Xmask”, where mask is a hexadecimal mask of 1 to 4 hexadeci-
mal digits, causes the sink to be set to the bitwise AND of the source value with the mask, or the
bitwise XOR of the source value with the mask, respectively. There is no space between the “A” or
“X” and the mask. The source must be of type Integer, Long, Packed Boolean, or Packed Long. If
the source is Long or Packed Long, the mask is applied to the low-order 16 bits. The result is sub-
ject to optional inversion.
Examples:

Cname:Bname.Pname.A30A0 Bitwise AND the low-order 16 bits of source with the

hexadecimal mask 30A0; if the result is non-zero, set
the sink to 1, else set the sink to 0.
Cname:Bname.Pname.~A30A0 Invert the result of the previous example, and set the
sink accordingly.
Cname:Bname.Pname.X30A0 Bitwise XOR the low-order 16 bits of source with the
hexa-decimal mask 30A0; if the result is non-zero, set
the sink to 1, else set the sink to 0.
Cname:Bname.Pname.~X30A0 Invert the result of the previous example, and set the
sink accordingly.

The option “H”, when it follows “A” or “X”, indicates that the specified operation is to be per-
formed on the high-order 16 bits of the source value. The only valid source types are Long or
Packed Long.
Examples:

Cname:Bname.Pname.~XH30A0 Bitwise XOR the high-order 16 bits of the source

with hexadecimal mask 30A0. If the result is non-
zero, set the result = 0, else set the result = 1.
Cname:Bname.Pname.1.~XH30A0 Set the default result = 1. If the connection is
broken, set the result = 1. Else set the result as in
the previous example.

58
6. Connections B0193AW – Rev R

Connections to Source Status

You may connect to certain bits within the status of the source parameter by use of the syntax:
[Cname]:Bname.Pname.[{0,1}.].[~]symbol
(Pname cannot be BLKSTA, ALMSTA, or INHSTA when using this format.)
“Symbol” is a 1- to 4-letter field which specifies various bits within the status field of the source
parameter. The sink is set to the logical OR of the specified bits. The meaning of the letters in
Symbol is as follows:

B 1 = Bad I/O
O 1 = Out-of-Service
D 1 = OM Off-Scan (“Disconnected”)
E 1 = Propagated Error

The results may be optionally inverted.

Examples:

Cname:Bname.Pname..B Sink = Bad status bit of source.

Cname:Bname.Pname..~B Sink = Inverse of Bad status bit of source.
Cname:Bname.Pname..BOD Sink = Logical OR of Bad, OOS, and OM Off-Scan
status bits of source.
Cname:Bname.Pname..~BOD Sink = Inverted result of previous example.

Connections to Status Parameters

You may connect to any bits, or combinations of bits, within the status parameters BLKSTA,
ALMSTA, and INHSTA by using the syntax:
[Cname]:Bname.{BLKSTA, ALMSTA, INHSTA}.[{0,1}.]
{[~]Bbit,[~]{A,X}[H]mask, [~]symbol}
The meanings of B, A, X, and H are as already described. “Symbol”, in this format, refers to one
of the 2- to 4-letter symbolic names assigned to the bits within the status parameters.
Examples:

Cname:Bname.BLKSTA.BAD Result = Value of the BAD bit within the source

BLKSTA.
Cname:Bname.BLKSTA.~BAD Result = Invert of the previous example.
Cname:Bname.ALMSTA.LDA Result = Value of the LDA bit within the source
ALMSTA.
Cname:Bname.ALMSTA.~LDA Result = Invert of the previous example.
Cname:Bname.INHSTA.HOA Result = Value of the HOA bit within the source
INHSTA.
Cname:Bname.INHSTA.~HOA Result = Invert of the previous example.

59
B0193AW – Rev R 6. Connections

Cname:Bname.BLKSTA.B12 Result = Boolean B12 of BLKSTA.

Cname:Bname.BLKSTA.AH30A0 Result = Bitwise AND of the high-order 16 bits
of BLKSTA with hexadecimal 30A0. (If the
result is nonzero, set sink = 1. Else set sink = 0.)

Table 6-1. Block Status Symbols

Symbol Meaning Bit Bbit

ACC 1 = Accumulating Bit 5 B27
ACT 1 = Active Bit 16 B16
ASP 1 = Alternate Set Point Bit 4 B28
BAD 1 = Bad I/O Bit 12 B20
BADR 1 = Bad Redundant I/O Bit 1 B31
CTL 1 = Control Bit 5 B27
DEV 1 = Redundant I/O Deviation Bit 4 B28
DF 1 = Device Fail Bit 22 B10
DSB 1 = Disabled Bit 23 B9
DSR 1 = DSR Mismatch Bit 22 B10
FBM 1 = FBM Failure Bit 8 B24
FBMR 1 = Redundant FBM Fail Bit 9 B23
FLB 1 = Supervisory Control Fallback Bit 31 B1
FOL 1 = Follow Bit 4 B28
FS 1 = Fail-safe output Bit 24 B8
FTN 1 = Feedforward Tune Active Bit 17 B15
FTNI 1 = Feedforward Tune Inactive Bit 16 B16
HLD 1 = Hold Bit 7 B25
HOL 1 = Hi Output Limit Bit 28 B4
HRQ 1 = Hold Request Bit 19 B13
ILK 1 = Interlocked Bit 21 B11
INER 1 = Input Error Bit 18 B14
LM1 1 = Limit Switch 1 On Bit 16 B16
LM2 1 = Limit Switch 2 On Bit 17 B15
LOL 1 = Lo Output Limit Bit 27 B5
LR 1 = Remote, 0= Local Bit 10 B22
LRO 1 = LR Override Bit 25 B7
MA 1 = Auto, 0= Manual Bit 11 B21
MAO 1 = MA Override Bit 26 B6
MO 1 = Manual Override Bit 23 B9
MTN 1 = Manual Tune Bit 0 B32
ON 1 = On Bit 15 B17

60
6. Connections B0193AW – Rev R

Table 6-1. Block Status Symbols (Continued)

Symbol Meaning Bit Bbit

PAUS 1 = Paused Bit 18 B14
PTN 1 = Pre-Tune Bit 2 B30
RAMP 1 = Ramp Option Bit 17 B15
RED 1 = Redundant Inputs Bit 21 B11
REPT 1 = Repeat Option Bit 16 B16
RMP 1 = Ramp Bit 5 B27
SBX 1 = Exec SBX statements Bit 19 B13
SC 1 = Supervisor Control Bit 30 B2
SE 1 = Supervisor Enabled Bit 29 B3
SEL 1 = Redundant I/O Selected Bit 0 B32
SIM 1 = PLB Simulation Mode Bit 18 B14
SPDN 1 = Set Point Ramp Down Bit 19 B13
SPUP 1 = Set Point Ramp Up Bit 18 B14
STN 1 = Self Tune Bit 1 B31
STRK 1 = Set Point Track Bit 9 B23
TEST 1 = PLB Test Mode Bit 19 B13
TRIP 1 = Tripped Bit 17 B15
TRK 1 = Track Bit 6 B26
UDEF 1 = Undefined Bit 14 B18
WLCK 1 = Workstation Lock Bit 20 B12

Example:
The Manual/Auto state of a block is presented in Bit 11 of BLKSTA, where Bit 0 is
the low-order bit. Boolean connection extensions refer to this bit as either
BLKSTA.MA or BLKSTA.B21. (Note that Bit 31, the high-order bit, is referred to in
Boolean connection extensions as B1.) When you use the Amask or Xmask format,
you must refer to the third column (“Bit”) and when you use the Bbit format, you
must refer to the fourth column (“Bbit”). In order to prevent parameter BLKSTA
from becoming unnecessarily long, certain bits are used in a block-dependent fashion,
thereby necessitating “alias” names for some bit positions. See, for example, ACT and
CTL.

Table 6-2. Alarm Status Symbols

Symbol Meaning Bit Bbit

BAD 1 = I/O Bad Alarm Bit 22 B10
HDA 1 = Hi Deviation Alarm Bit 21 B11
HHA 1 = Hi Hi Abs Alarm Bit 25 B7
HMA 1 = Hi Meas Alarm Bit 17 B15
HOA 1 = Hi Output Alarm Bit 19 B13

61
B0193AW – Rev R 6. Connections

Table 6-2. Alarm Status Symbols (Continued)

Symbol Meaning Bit Bbit

INH 1 = Alarms Inhibited Bit 29 B3
LDA 1 = Lo Deviation Alarm Bit 20 B12
LLA 1 = Lo Lo Abs Alarm Bit 24 B8
LMA 1 = Lo Meas Alarm Bit 16 B16
LOA 1 = Lo Output Alarm Bit 18 B14
OPER 1 = Operational Error Alarm Bit 27 B5
OOR 1 = Out of Range Alarm Bit 28 B4
PNT1 1 = Point 1 Alarm Bit 15 B17
PNT2 1 = Point 2 Alarm Bit 14 B18
PNT3 1 = Point 3 Alarm Bit 13 B19
PNT4 1 = Point 4 Alarm Bit 12 B20
PNT5 1 = Point 5 Alarm Bit 11 B21
PNT6 1 = Point 6 Alarm Bit 10 B22
PNT7 1 = Point 7 Alarm Bit 9 B23
PNT8 1 = Point 8 Alarm Bit 8 B24
PTRG 1 = Pre-Target Alarm Bit 19 B13
ROC 1 = Rate of Change Alarm Bit 23 B9
STA 1 = State Alarm Bit 26 B6
TARG 1 = Target Alarm Bit 25 B7
TRIP 1 = Trip Alarm Bit 31 B1
UNAK 1 = Unacknowledged Bit 30 B2

The boolean extension symbols for the inhibit status parameter INHSTA are the same as those for
the ALMSTA parameter, except for the UNAK symbol.

Packed Boolean Connection Extensions

If the sink is a Packed Boolean, then the syntax:
Cname:Bname.Pname.mask [where mask is a four-digit (xxxx) hexadecimal number]
may be used to set and reset specific bits of the sink.
If Pname is a boolean source parameter with a value of FALSE when the connection is refreshed,
then the bits of the sink corresponding to the 1-bits of the mask are cleared.
All other bits of the sink are unchanged. If Pname is TRUE at this time, the bits of the sink corre-
sponding to the 1-bits of the mask are set, and all other sink bits are unchanged.
If Pname is an integer, long integer, packed boolean or packed long, the bits of the low-order 16
bits of the source which correspond to 1-bits of the mask are copied into the sink. All other bits of
the sink are unchanged.
If Pname is a short integer, those bits of the source which correspond to 1-bits in the low-order
byte of the mask are copied to the sink. All other bits of the sink are unchanged.

62
6. Connections B0193AW – Rev R

If Pname is a real, then Pname is converted to an unsigned integer before the mask is applied.
You cannot set any sink bits which are specified in the mask for setting, clearing, or copying.
All other bits of the sink are settable.

Defaults for Integer and Real Connections

The section “Boolean Connection Extensions” on page 56 explains how default values may be
specified for inputs of boolean type. It is also possible to specify such default values for inputs of
integer or real type by configuring the connection according to the following format:
Cname:Bname.Pname.n
where n is the desired default value.
If the sink is of integer type, n is an integer.
Example:
EVAPORATOR:F1200.HOLIM.7000
If the sink is of real type, then n is a real value in floating point or scientific notation.
Examples:
EVAPORATOR.F1200.HOLIM.124.5
EVAPORATOR.F1200.LOLIM.-3.2E-2
The default value specified will only be used until the source value is available (that is, the connec-
tion is resolved and the source status is not BAD or OOS). When that happens, the source value
will be copied into the input parameter, and the default value will be lost. The connection is
secured while the specified default is in use.
If the input parameter is connected to itself, however, the default value specified in the connection
will be preserved until the parameter is reconfigured. You may use this method of specifying
defaults to override the standard default for any parameter, as stated in the parameter tables.

Mixed Data Types

Local connections are input parameter connections to source parameters in the same CP station.
You can connect an input parameter to a source parameter of any data type in any block in the
same CP station.
The CP converts the data from the source format into the sink format when the data is copied
into the sink connection. This is done each block execution cycle prior to processing the block
algorithm.
In most cases, data conversions conform to the standard “C” programming language conventions
used in assignment statements containing mixed data types.
For the cases shown in Table 6-3, however, the converted value is clamped at the specified maxi-
mum positive or minimum negative value. Table 6-4 summarizes the results of the conversion
algorithms.

63
B0193AW – Rev R 6. Connections

Table 6-3. Data Conversion Clamping

Sink Value Source Value Maximum Minimum

Short Integer Integer 127 -128
Short Integer Long integer 127 -128
Short Integer Real value 127 -128
Integer Long integer 32767 -32768
Integer Real value 32767 -32768
Long Integer Real value 2147483647 -2147483648

Table 6-4. Data Conversion Results

Sink Value Source Value Results

Boolean Short integer, integer, long integer, If source not = 0, result = 1
real, packed boolean Else result = 0
Short Integer Boolean, packed boolean, packed long Low-order byte of source
Integer, long integer Clamped source
Real Converted clamped source
Integer Boolean Unsigned low-order byte of source
Short integer Extended low-order byte of source
Long integer Clamped source
Real Converted clamped source
Packed boolean Source
Packed long Unsigned low-order integer of source
Long Integer Boolean Unsigned low-order byte of source
Short integer Extended low-order byte of source
Packed boolean Unsigned low-order integer of source
Integer Extended low-order integer of source
Real Converted clamped source
Packed long Source
Real Boolean, short integer, integer Converted source
Long integer, packed long Converted truncated high-order source
Packed boolean Converted unsigned integer of source

64
6. Connections B0193AW – Rev R

Table 6-4. Data Conversion Results (Continued)

Sink Value Source Value Results

Packed Boolean Boolean If source = 0, mask bits cleared in sink
If source = 1, mask bits set in sink
(unmasked bits are unchanged)
Short integer Masked unsigned low-order byte of
source (unmasked bits are unchanged)
Integer, long integer, packed boolean, Masked unsigned low-order integer of
packed long source, (unmasked bits are unchanged)
Real Masked converted clamped integer of
source (unmasked bits are unchanged)
Packed Long Boolean If source = 0, clear all sink bits
If source = 1, set all sink bits
Short integer Unsigned low-order byte of source
Integer, packed boolean Unsigned low-order integer of source
Real Converted clamped long of source
Long integer Source

Peer-to-peer connections are input parameter connections to source parameters in different CP

stations.
Peer-to-peer connections support a mixture of the following data types. The same conversions
specified for the mixed local connections in Table 6-4 are performed for the combinations of
mixed peer-to-peer connections listed in Table 6-5.

Table 6-5. Peer-to-Peer Connections

Source Value Sink Value

Long Integer Integer, short integer, boolean, packed boolean, packed long
Integer Long integer, short integer, boolean, packed boolean, packed long
Short Integer Long integer, integer, boolean, packed long

Peer-to-peer connections do not support a mixture of real and integer data types, or a mixed con-
nection to a boolean source.

65
B0193AW – Rev R 6. Connections

66
7. Block Processing
This chapter describes the compound processor’s actions in the basic processing cycle (BPC). It
describes scanning, I/O blocks, and input and output signal conditioning.
The compound processor is a task scheduled by the operating system to run every basic processing
cycle (BPC).
The BPC is the smallest resolution of time in which the compound processor can be scheduled to
run. It presently defaults to 0.5 second. Periods are resolved in multiples of the BPC.

Compound Processing

ECB/FBM
Commun- Inputs Continuous Sequence Continuous Outputs
ication from block block block to
ECB Algorithms processing algorithms ECB
(1st list) (2nd list)

System
Block Processing Tasks

One Basic Processing Cycle (BPC)

Figure 7-1. The Basic Processing Cycle

Within each BPC, the compound processor task processes the blocks in the following order:
1. The first list of continuous blocks.
2. Monitor blocks and timer blocks.
3. Exception blocks.
4. Dependent and independent blocks.
5. The second list of continuous blocks.
See the diagram above for a BPC representation.
Ladder Logic processing takes place within the Fieldbus Modules.
After the first list of continuous blocks is processed, the sequence blocks are allotted a specific
time before the second continuous list. If the sequence blocks are not finished in a single BPC,
they are continued during successive BPCs.
Sequential control block processing is defined in greater detail in “Sequential Control Blocks” on
page 133.

67
B0193AW – Rev R 7. Block Processing

Scanning
For Control Processors, the allowable user-specified scan periods are 0 through 13. Each scan
period has the value shown in Table 7-1.

Table 7-1. Scan Periods

0 = 0.1 second 5 = 30 seconds 10 = 5.0 second

1 = 0.5 second 6 = 1 minute 11 = 0.6 seconds
2 = 1 second 7 = 10 minutes 12 = 6 seconds
3 = 2 seconds 8 = 60 minutes 13 = 0.05 seconds*
4 = 10 seconds 9 = 0.2 second
* Available in CP40, CP40B and CP60 only.

The fastest period is 13 and the default period is 1.

For Gateway and Integrator scan periods, refer to the appropriate Gateway and Integrator docu-
ments.
Compounds process in the order in which you install them in the Integrated Control Configura-
tor, subject to variations due to differences in their periods.
Within the compound, blocks also process in the order in which you install them. As with com-
pounds, you can modify the execution sequence by means of the period and phase parameters.
Block execution is initiated by the compound processor when a compound is turned on.
The compound period should be set to the Basic Processing Cycle. A compound period of zero
implies an execution period equal to the BPC.
Phases and periods can be adjusted in individual blocks to alleviate potential overrun situations.

Scan Overrun
A Scan Overrun occurs when a processor has more blocks than it can process within a single scan
cycle.

Block Phasing
A block can never be executed more frequently than the minimum Basic Processing Cycle (BPC)
of the Control Processor (CP). A block with a period of 0 is executed as if the period were 0.5 sec-
ond if the BPC is 0.5 second.
The BPC default value is 0.5 second. However, the BPC can be set to 0.1 second or other values
with System Configurator/Definition.
Phasing is the distribution of the block processing over multiple BPCs. The object is to limit the
number of blocks scheduled for processing in any given BPC.
When the block period is equal to the BPC, the block is processed every cycle and there are no
phasing options.
However, when the block period is greater than the BPC (processed less frequently), the block can
be phased to execute at some time other than the very beginning of the period. This feature is use-
ful in avoiding overruns. Overruns occur when too many blocks are scheduled for execution at the
same BPC.

68
7. Block Processing B0193AW – Rev R

Relationship Between Block Period and Phase

Block periods greater than the BPC are always equal to an integral number of BPCs (for example,
when the BPC is 0.5 seconds, a block period of 2.0 seconds equals 4 BPCs).
Each block uses this integral multiple, N, to set up a modulo N counter that counts BPCs and
triggers block execution every Nth BPC. In the example where N equals 4, the block’s modulo
counter cycles through the counts 0-1-2-3-0-1-2-3-0-1-2-3-0-... , triggering block execution every
fourth cycle.
The block’s Phase value determines whether block execution occurs at the 0 count, the 1 count,
the 2 count, or the 3 count. A Phase value greater than three in this example exceeds the maxi-
mum modulo count and the block will never be executed.
Generally, the legal phase values are the integers from 0 to N-1, where N equals the number of
BPCs in the Period. Table 7-2 lists the phase values for a CP that has a BPC of 0.5 seconds.

Table 7-2. Legal Phase Values

PERIOD PHASE PERIOD PHASE

Value Length Values Value Length Values
0 0.1 sec Not allowed 7 10 min [0 - 1199]
1 0.5 sec [0] default 8 60 min [0 - 7199]
2 1.0 sec [0,1] 9 0.2 sec Not allowed
3 2.0 sec [0,1,2,3] 10 5.0 sec [0 - 9]
4 10 sec [0 - 19] 11 0.6 sec [0] default
5 30 sec [0 - 59] 12 6.0 sec [0 - 11]
6 1 min [0 - 119] 13 0.05 sec* Not allowed
* Available in CP40, CP40B and CP60 only, when permitted by the selected BPC.

Thus, a block having a PERIOD/PHASE assignment of 3/1 executes every 2.0 seconds in the sec-
ond BPC frame of the two second period.

! WARNING
Do not assign a block phase value that is not shown in Table 7-2. Such an
improper assignment causes a warning message in the control configurator and, if
not corrected, causes the block to be undefined. This results in the block not being
processed.

Assume a group of blocks all having a PERIOD value of 1, 2, or 3, and a PHASE value of 0. Exe-
cution of these blocks will follow the patterns shown below.

69
B0193AW – Rev R 7. Block Processing

Basic Processing 0 1 2 3 4 5 6
Cycle (BPC)
(0.5 Sec)

0 0 0 0 0 0 0
PERIOD=1 (0.5 s)
PHASE=0

0 1 0 1 0 1 0
PERIOD=2 (1.0 s)
PHASE=0

0 1 2 3 0 1 2
PERIOD=3 (2.0 s)
PHASE=0

Figure 7-2. Example of Phased Execution

A processor can be overloaded with more blocks than it can process in a single BPC. To prevent
overloading, you can balance the block load within a single phase by changing a block(s) execu-
tion to another phase.

Scan Overload
When blocks are configured initially, they default to a phase of zero. As shown in Figure 7-2,
many blocks can be designated for execution in Phase 0 of a single BPC. When all blocks in a pro-
cessor have a phase of zero, they are processed during a single BPC. In such a case, the processor
must be able to handle all the blocks in a single BPC, or scan overrun may occur.
For example, if the blocks in Figure 7-2 were equal in load, the CP’s total execution time for each
BPC would take the pattern shown in Figure 7-3. BPC0 and BPC4 begin to show the effects of a
Phase 0 pileup; the amount of time required to process the blocks increases as more blocks are
added.

1 3 5

Total Execute Time 0 2 4 6

Figure 7-3. Phase Zero Overload

A Scan Overrun occurs when a processor has more blocks that it can process within a single scan
cycle. During a scan overrun, the Compound Processor continues to process blocks even after the
allocated period for the cycle is over. It simply extends the scan cycle into the next BPC until it has
completed processing the remaining blocks. However, the processor does not perform any of the
operations scheduled for this overrun BPC; to prevent the scan cycles from being offset, the over-
run BPC is ignored. When finished, the Compound Processor waits until the beginning of the
next scheduled BPC to begin the next execution.

70
7. Block Processing B0193AW – Rev R

This situation is illustrated in Figure 7-4. If you add CMP1, a large compound of blocks having a
PERIOD value of 3 and PHASE 0, to the blocks described in Figure 7-3, the PHASE 0 Total
Execute Time is large enough to cause an overrun and the PHASE 1 operation is delayed. The
next processing operation occurs at PHASE 2.

Added CMP1
PERIOD=3/PHASE=0 1 2 3 1 2
0 0

3
Total Execute Time 0 overrun 2 4 overrun 6
Figure 7-4. Example of Overrun

NOTE
When the blocks are configured at longer periods, the Compound Processor may
still overrun intermittently due to a pileup at certain Phase 0 frames.

An overrun guarantees that the control operation goes to completion, but it also results in the loss
of a processing cycle and the skewing of succeeding cycles. An occasional overrun may not affect
control, but repeated occurrences must eventually degrade process control.
To alleviate a potential scan overrun situation, the block phasing should be adjusted for the extra
blocks causing the scan overrun. Configuring block phasing balances out the load on the CP data-
base by spreading block processing evenly throughout the BPCs.
Using the same example, you can configure CMP1, the large added compound executing at
PHASE 0, to execute at other times (for example, Phases 1 and 3) and avoid the overruns that
occurred at BPC0 and BPC4 (PHASE 0).

Part of CMP1
PERIOD=3/PHASE=1 0 1 2 3 0 1 2

Part of CMP1 0 1 2 3 0 1 2
PERIOD=3/PHASE=3

Total Execute Time 0 1 2 3 4 5 6

Figure 7-5. Avoiding Overrun

The following describes how to avoid scan overrun by configuring block phasing.

71
B0193AW – Rev R 7. Block Processing

Block Phasing: Cautions and Guidelines

Phase configuration should take into account a block’s position in the control scheme, its work
load, the number of active options, and so on. Some guidelines follow.

Compound Phasing
♦ The system defaults the Compound Period to the system BPC, and the Compound
Phase to 0.

ECB (Equipment Control Block) Phasing

♦ ECBs are configured with their own periods and phases. The “execution” of an ECB
at its configured period and phase refers only to the capture and storage of input data
from its associated FBM or FBC. This need not be done any more frequently than the
input data is required by the connected control block(s).
♦ ECBs can be configured as part of any ordinary compound or as part of the station’s
ECB compound. (See Integrated Control Configurator (B0193AV), Chapter 3, for the
procedures involved.) Within any one BPC, the Compound Processor guarantees that
the scheduled ECBs are processed prior to the scheduled I/O blocks in that com-
pound. When the I/O block is processed, it receives the input data from the current
contents of the ECB, whether or not those contents were refreshed in the current
BPC. Note that the writing of output data from an output block to its destination
ECB is always controlled by the output block. After all the compound’s I/O control
blocks have been processed, those ECBs which have received fresh output data from
the control blocks transmit the data to their connected FBMs and/or FBCs, in the
current BPC. Therefore, output activity is not under control of periods and phases.
♦ Output type blocks such as AOUT or COUT write their output values to their desti-
nation FBM via their ECB during the BPC frame assigned to the output block after
the output block executes. However, the readback of the FBM’s output registers is ini-
tially scanned by the ECB before the output block executes. This is used to calculate
the BCALCO.

Control Block Phasing

♦ All block phasing is on a global basis. Phase 0 is common to all blocks, compounds
and ECBs.
♦ Block execution order and control processor loading are the major considerations
when any phasing is to be configured. Normally, block execution order in a control
loop should be set up so that the feedback measurement input blocks execute immedi-
ately before the control blocks, and the output blocks should immediately follow the
control blocks. If all blocks in a control loop are in the proper order and have the same
period and phase, then block initializations and bumpless transfers work properly
even when PRIBLK = 0.
♦ In cascade strategies, the primary blocks should execute before the secondary blocks.
Execution of feedforward blocks should be sequential in the data flow direction.

72
7. Block Processing B0193AW – Rev R

♦ If a phase value, outside of the legal phase values for the assigned Period value, is con-
figured, the block, compound, or ECB is never processed. A warning message is
displayed in the Integrated Control Configurator and the block, compound, or ECB
is set undefined. If you reduce the Period value, the existing Phase value is verified to
ensure that it is within the legal range for the new Period value.
♦ When working with a block in a gateway, turn the compound off before altering the
period or phase.

Input/Output (I/O) Blocks

I/O blocks provide the application interface between the physical process inputs and outputs for
the system. They process as part of any compound.
The I/O blocks relate logical names (FLWTRNS100, for example) to physical hardware point
addresses, which are identified by the FBM device ID and point number.
All control references to I/O points (such as from displays or data logging) use the block name
rather than the physical address.
Input blocks have manual modes to enable you to disconnect control schemes from live FBMs for
simulation and checkout purposes.
Output blocks have Manual modes to enable operator intervention in controlling the process.
Analog input blocks convert raw data read from the FBMs to a real value in engineering units.
They also provide signal conditioning.
Piecewise linear characterization is performed for thermocouple conversion (see “Signal Condi-
tioning Indexes” on page 193).
Different AIN blocks can be connected to the same FBM to provide conditioning to different
engineering units.
Redundant I/O blocks provide high availability by utilizing two separate FBMs to support a sin-
gle process point. (See “Redundant I/O Blocks” on page 74).

I/O Block Processing

I/O processing takes place both in the Control Processors and the Fieldbus Modules (FBMs) or
Fieldbus Cards (FBCs). FBMs and FBCs interface to the control system through Equipment
Control Blocks (ECBs), which are “holding places” for the FBM or FBC data.
Each Fieldbus Module or Fieldbus Card has an accompanying ECB. ECBs are created through
the control configurator in the same manner as blocks.
The system monitor and the compound processor are responsible for maintaining this active
interface at the ECB level.
“Control Processor (CP)/Fieldbus Application Interface” on page 159 provides I/O Block, ECB,
and FBM/FBC application interface information. “Equipment Control Blocks (ECBs)” on
page 169 and “Fieldbus Module Types (FBMs)” on page 205 provides detailed information on
ECBs, FBMs, and FBCs.

73
B0193AW – Rev R 7. Block Processing

I/O Block Status

A bad FBM or bad channel status combine to form a bad data status. This bad status is included
in the output value record of input type blocks.
For outputs, a check is made for a non-operational FBM, or loss of communication. These are
combined in a BAD output status which is available as a Boolean output for connection into con-
trol strategies.
Output blocks also perform a readback of the FBM raw output values and this information is
made available in special output parameters. This allows live process values to be fed back into
control schemes for bumpless initialization purposes.

I/O Block Validation

At the system level, a process input/output (PIO) maintenance task checks the security status of
each installed FBM. This task runs periodically.
It establishes the operational status of each FBM and its related ECB.
At the application level, process input values are checked against fixed limits through various
alarm options at the block level.
Analog Inputs:
♦ High/low sensor range check
♦ High/low alarm checks in engineering units
♦ Rate-of-change detection and alarming.
Analog Outputs:
♦ Bad alarming.

I/O Fail-safe Status

The desired fail-safe value of a particular FBM output channel can be configured.
An output point in an FBM can be configured on a per-type (analog or digital) basis to fail to a
fail-safe value or to maintain its current value. An analog output fails to a hold value or fails to a
configured value. A digital output fails to zero, one, or to a hold value. The individual FBM stores
the fail-safe values.
I/O fail-safe mode of operation can be caused by the loss of process I/O communications or by
internal FBM diagnostics. An FBM is reset from fail-safe status by an automatic I/O reset request
from the Control Processor.

Redundant I/O Blocks

Redundant I/O blocks are provided for applications that require higher system availability.

Redundant Input Block (AINR)

The Redundant Analog Input Block accepts inputs from two separate and separately named
FBMs or FBCs. The user designates a primary and a secondary signal. Both signals are converted
and validated but only the primary signal is presented to the block’s point output, unless a failure
is detected.

74
7. Block Processing B0193AW – Rev R

If a failure is detected and the secondary signal is healthy, that signal is used on the block’s point
output.
When either signal fails or when they differ by more than a user-defined parameter, alarms are
generated.

Redundant Output Block (AOUTR)

The Redundant Analog Output Block connects to any pair of FBMs or FBCs providing analog
output, providing they are of the same hardware and software types. Redundant operation of the
FBM01 to FBM46, or FBCs is achieved when a special Termination Cable Assembly (TCA) is
installed. For DIN rail mounted FBMs, a Redundant Adapter is installed on the Baseplate linking
the redundant FBMs. Special TCAs or Redundant Adapters attach to the pair of FBMs and use
diodes to combine the pairs outputs into a single analog signal. There are redundant TCAs avail-
able for FBMs 4, 5, 6, 37, and 39 (FBM04 and FBM06 use identical TCAs). Redundant Adapt-
ers are available for FBM205 and FBM237.
As noted in “Control Processor (CP)/Fieldbus Application Interface” on page 159, the special
TCA and Redundant Adapters provide redundancy correctly only when the fail-safe mask and
fail-safe fallback values in both of the ECBs are configured to the required values.
Alarms can be generated when either output fails.

Input Signal Conditioning

The analog type I/O blocks support a set of signal conditioning algorithms, which are specified by
a set of index numbers.
The AIN reads the analog input point data from the FBM in raw counts. After status validation,
the raw counts are conditioned and converted to engineering units in floating point, according to
the specified conversion index and engineering units range. See Figure 7-6 for an example of
input signal conditioning.
Note that most raw data is normalized in positive valued counts from 0 to 64,000 and can have a
legal converted value in the range of 0 to 65,535 counts.
The conditioned value is converted to the specified units using the high and low sensor range.
The data is then optionally filtered and made available at the output parameter.

Physical Signal Compound A

(mA, V dc, mV dc, Hz, etc.)
AIN
HSCALE
FBM ECB LSCALE

Sensor or
Linear Raw Compound B
Transmitter
A/D Data &
Conversion Status AIN
HSCALE
LSCALE

Other Compounds
Process I/O Serial Bus (Fieldbus)
Data 0 to 64000 counts (normalized)

Figure 7-6. Input Signal Conditioning

75
B0193AW – Rev R 7. Block Processing

Measurement values are linearized using linear/square root conversion, standard curves, and/or
piecewise-linear interpolation. This maintains the accuracy of the raw data over the entire range.
The following types of signal conditioning are provided:
♦ Default = 0, no conditioning
♦ 0 to 64000 raw counts linear (Analog Input 0 to 20 mA)
♦ 1600 to 64000 raw counts linear (Analog Input 0 to 10 V dc)
♦ 12800 to 64000 raw counts linear (Analog Input 4 to 20 mA)
♦ 0 to 64000 raw counts square root (Analog Input 0 to 20 mA)
♦ 12800 to 64000 raw counts square root (Analog Input 4 to 20 mA)
♦ 0 to 64000 raw counts square root with low cutoff (Analog Input 0 to 20 mA)
♦ 12800 to 64000 raw counts square root with low cutoff (Analog Input 4 to 20 mA)
♦ 1600 to 64000 raw counts linear with low cutoff (Analog Input 0 to 10 V dc)
♦ 12800 to 64000 raw counts linear with low cutoff (Analog Input 4 to 20 mA)
♦ 14080 to 64000 raw counts linear (Analog Input 2 to 10 V dc)
♦ 14080 to 64000 raw counts square root with low cutoff (Analog Input 2 to 10 V dc)
♦ type E thermocouple
♦ type E thermocouple EA-2
♦ type J thermocouple
♦ type K thermocouple
♦ type R thermocouple
♦ type S thermocouple
♦ type T thermocouple
♦ type N thermocouple
♦ nickel RTD
♦ platinum RTD (SAMA)
♦ platinum RTD (DIN)
♦ platinum RTD (IEC)
♦ copper RTD.
Every RTD/thermocouple “SCIX” (Signal Conditioning Index) has a table associated with it (see
Appendix A “Signal Conditioning Indexes” on page 193).
The CHARC block can be used to apply user defined piecewise-linear characterization to non-
standard inputs. This is accomplished by connecting the EXTBLK parameter of the input block
to the BLKSTA parameter of the CHARC block, and setting the EXTOPT parameter of the
CHARC block to 1. The CHARC block segments must be configured as required.

76
7. Block Processing B0193AW – Rev R

You can also use “special thermocouple” signal conversion for nonstandard thermocouple inputs
when the cold-junction compensation must be accommodated by the CHARC block. To do this,
you should connect the EXTBLK parameter as described, but the EXTOPT parameter of the
CHARC block should be set to 2. First, the cold junction compensation temperature is converted
by the CHARC block from degrees Celsius into millivolts, using reverse interpolation. Then, the
millivolt equivalent of the cold junction reference is added to the millivolt analog input point
value, and the sum is passed to the CHARC block for forward interpolation. This results in the
generation of a compensated output value in degrees Celsius.

Filtering

First or Second-Order
First- or second-order filter is provided on an optional basis:
Option:
0 = No filtering
1 = First order
2 = Second order Butterworth

Contact Filtering
Contact bounce is filtered by the FBM.

Output Signal Conditioning

Before an output block writes a value to an appropriate type FBM, it is converted to raw counts.
The analog value, which is written to an FBM point, is converted from engineering units to
counts, using the high and low output range. See Figure 7-7 for an example of output signal con-
ditioning. The processing is the inverse operation of signal conditioning described for AIN
blocks.
This value is conditioned according to the applied conditioning index. See “Signal Conditioning
Indexes” on page 193. The result is clamped between the high and low actuator limit value.

CONTROL PROCESSOR
F
to other compounds
I
(optional) ECB
E
L
Change FBM
OUT RAW VALUE D
Driving COUNTS
HSCALE Driven B
Block
or LSCALE READ-BACK U D/A
Read
Application COUNTS S
Back PROCESS S
FBM STATUS I
BAD
G
V dc, mA etc.
AOUT N
A
PROCESS
DOMAIN L

Figure 7-7. Output Signal Conditioning

77
B0193AW – Rev R 7. Block Processing

The following output Signal Conditioning options are applicable for analog output I/O blocks:
♦ Default = 0, no conditioning
♦ 0 to 64000 raw counts linear (Analog Output 0 to 20 mA)
♦ 1600 to 64000 raw counts linear (Analog Output 0 to 10 V dc)
♦ 12800 to 64000 raw counts linear (Analog Output 4 to 20 mA)
♦ 0 to 64000 raw counts square root (Analog Output 0 to 20 mA)
♦ 12800 to 64000 raw counts square root (Analog Output 4 to 20 mA)
♦ 14080 to 64000 raw counts linear (Analog Output 2 to 10 V dc)
♦ 14080 to 64000 raw counts square root with low cutoff (Analog Output
2 to 10 V dc).

78
8. Block/Process Alarming
This chapter provides details on block alarm processing, alarm states, and data recorded in
alarm messages.

Alarming Overview
Block alarming, or process alarming, is used to detect when a specific event or condition with
potentially hazardous consequences has occurred. This event or condition involves a change in the
operation of a monitored field device or block.
When an alarm is triggered in a block, notification is sent through the station block to the Alarm
Manager, which alerts the operator via a message on the process display, and/or a horn on an
annunciator keyboard. In most cases, the station block can also send the alarm alert to an alarm
printer as well. The alarming system is shown in Figure 8-1.
Notification

Device or Block

Point Process Display

Block
Alarming Alarm Manager
Goes into alarm condition
Notification

Device or Block Station

Block
Point
Block
Alarming Alarm Printer
Goes into alarm condition Optional (not available
to all alarms)
Figure 8-1. Block Alarming

There are a number of different types of process alarming, each specific to a particular event or
condition. To enable each type of process alarm, you must determine and configure the following
information (via alarm parameters specific to each block):
♦ which types of alarms you want to enable (alarm options), and which types of alarms
you want to inhibit
♦ the text that appears in the process display if the alarm is initiated
♦ the device group that you want each alarm message sent to
♦ the priority level you want to assign to each alarm
♦ any parameters specific to the alarm type, such as the limit at which the alarm is initi-
ated and the deadband that determines when the alarm condition returns to normal.
Configuration procedures for process alarms are available in Process Operations and Displays
(B0193MM).

79
B0193AW – Rev R 8. Block/Process Alarming

Some blocks have alarming as their primary function, however, most blocks offer alarming on an
optional basis. Also, some blocks, such as PLC and DCI blocks, do not offer alarming features.
Alarming provides the basis for:
♦ Alarm detection via alarm output indicators (see next section)
♦ Message generation, related to the value of certain parameters
♦ Guidance notification.
The following section explains how process alarms are generated.

Process Alarm Generation

Blocks typically generate process alarms by setting a bit in the alarm status parameter (ALMSTA),
which is a packed long value. Additionally, a user-defined message may be sent to the process dis-
plays, depending on whether this feature is inhibited or not. User-defined messages are not sent to
the alarm printer.
Most blocks have a Boolean parameter for each alarm which acts as an alarm indicator; that is, a
parameter set to true when the alarm is active, and false when it is not. Other continuous blocks,
sequence blocks, and applications can connect to output alarm indicators, to pass the alarm on to
the operator and control software.
Refer to the next section to learn more about ALMSTA, alarm inhibition, and other features com-
mon to all process alarms.

Common Process Alarm Features

The following sections detail the common features that block alarms share:
♦ “Common Process Alarm Parameters” on page 81 - alarm parameters that typically
exist in every block that supports alarms
♦ “Alarm Messages” on page 82 - reports on alarms
♦ “Alarm Status Parameter (ALMSTA)” on page 83 - reports the states of alarms
♦ “Alarm Option Parameter (ALMOPT)” on page 84 - indicates availability of alarms
♦ “Criticality and Priority Type” on page 85 - rate each alarm based on the system
importance of the alarm
♦ “Alarm Inhibition” on page 86 - prevents alarm from occurring or being displayed.
Detailed descriptions of the available types of process alarms are provided in “Process Alarm
Types” on page 90.

80
8. Block/Process Alarming B0193AW – Rev R

Common Process Alarm Parameters

Some examples of specific parameters related to the process alarm functions that are held in most
blocks that support alarming, are provided below:
Per Alarm Point:

[Alarm Indicator]1 Set to true when a specific alarm point is in alarm. It can be connected
into control strategies.

[Group Number]1 Allows you to assign a group number from 1 to 8 for alarm device destina-
tion and distribution. You can specify up to eight destination devices for
each group between group number 1 and group number 3. You do this by
configuring the GRx and DVy parameters in the compound containing
the block. You can specify up to 16 destination devices for each group
between group number 4 and group number 8. You do this by configuring
the GRx and DVy parameters of the station block for the station contain-
ing the block.

[Priority Level of A priority level of 1-5 assigned for display and annunciation purposes,
Alarm]1 where:
1 = highest priority (0 = no alarm)
The block does not use this parameter. The alarm message processor uses
it as a filter for the Compound Inhibit (CINHIB) function.

[Alarm Text] A string that is sent to a process display when a specific alarm point is in
alarm (if uninhibited). In some blocks, a “return-to-normal” message may
also be available for when the point goes out of alarm. This string is sent
with the alarm message (see “Alarm Messages” on page 82).
One Per Block:

INHIB All alarms in the block are inhibited. The specific action taken depends on
the value of INHOPT in that block.

INHALM Contains packed Boolean values that represent alarm inhibit requests for
each type of alarm configured in the block. The specific action taken
depends on the value of INHOPT in that block.

INHOPT Defines the behaviors applied to inhibited and, optionally, uninhibited

alarms.

NOTE
More information on the INHIB, INHALM, and INHOPT parameters is available
in “Alarm Inhibition” on page 86.

1.
Name varies, depending on the block in which it is used.

81
B0193AW – Rev R 8. Block/Process Alarming

CRIT Indicates the highest priority of all active alarms within the block.

UNACK A Boolean output parameter which is automatically set true (1) when a
block alarm becomes active. It is settable, by an operator “acknowledge”
pick on a default or user display, or via a user task. It may also be reset
automatically when the alarm condition clears if that option is specified by
the INHOPT parameter.
Additional information is sent to the process display in each alarm message which is not user-
configured. This information is detailed in the next section.

Alarm Messages
When an alarm is generated, an alarm message is sent to the configured device group. This alarm
message consists of the following data:

NOTE
The following terms are used internally with the blocks, and are not parameter
names.

TIME Time of the message

DATE Date of the message

CNAME Compound name (for example, FURNACE)

BNAME Block name (for example, HEATXCHFLW)

PNAME ASCII Parameter name

TYPE MSG Text indicating the type of check violated (for example, HI DEV) or
Fail Text (for example, PUMP FAILURE)
Be aware that this is not the alarm text configured for each block, but is
derived from a separate list.

LIMIT Alarm limit value (usually derived from a user-configurable parameter)

VALUE Alarmed variable value

GROUP # Destination device (usually derived from a user-configurable parameter)

Alarm messages are shown on a process display. Typically, they are not sent to an alarm printer.
This data is derived from block parameters which have differing names specific to each block.
Refer to the “Station Block” chapter of Integrated Control Block Descriptions (B0193AX) for infor-
mation on configuring the station block to send alarm messages to their proper device group.
The next section details the parameter that the blocks use to generate alarms.

82
8. Block/Process Alarming B0193AW – Rev R

Alarm Status Parameter (ALMSTA)

When an alarm condition is detected, the block sets the appropriate bits of Alarm Status (ALM-
STA) to true. When the alarm condition clears, the block resets this bit to false.
ALMSTA is a 32-bit block output parameter that is bit mapped to indicate the following block
alarm states as they apply to those blocks that have alarming capability.
Blocks which do not have alarming capability have no ALMSTA parameter. These blocks include
ALMPRI, BIAS, CALC, CALCA, CHARC, DTIME, LIM, LLAG, MAIN, MCIN, MCOUT,
RAMP, SIGSEL, SWCH, PLB, PLC and DCI blocks.
The remaining blocks have one or more applicable bits. Each individual block description in
Integrated Control Block Descriptions (B0193AX) identifies the bits that make up the ALMSTA
parameter for that block.
A list of all the bits that can be assigned to the ALMSTA parameter and their indicated alarm state
is shown in Table 8-1:

Table 8-1. ALMSTA-Assignable Bits

Boolean
Connection
Bit No. Indicated Alarm State Extension
31 (MSB) TRIP Trip Alarm ALMSTA.B1
30 UNACK (unacknowledged) ALMSTA.B2
29 INH Inhibit Alarm ALMSTA.B3
28 OOR Out of Range Alarm ALMSTA.B4
27 OPER Sequence Operational Error Alarm ALMSTA.B5
26 STAL State Change Alarm ALMSTA.B6
25 HHA High High Absolute (TARG in ACCUM block) ALMSTA.B7
24 LLA Low Low Absolute Alarm ALMSTA.B8
23 RATE Rate of Change Alarm ALMSTA.B9
22 BAD Input/Output Bad (BAD output of block) ALMSTA.B10
21 HDA High Deviation Alarm ALMSTA.B11
20 LDA Low Deviation Alarm ALMSTA.B12
19 HOA High Output Alarm (PTARG in ACCUM block) ALMSTA.B13
18 LOA Low Output Alarm ALMSTA.B14
17 HMA High Measurement Alarm ALMSTA.B15
16 LMA Low Measurement Alarm ALMSTA.B16
15 to 8 PNT1 to PNT8 – Points in STATE Alarm (BLNALM) ALMSTA.B17 –
ALMSTA.B24
7 to 5 CRIT – Criticality (Range 0 to 5) ALMSTA.B25 –
ALMSTA.B27
4 to 0 PRTYPE – Priority Type (Range 0 to 9) ALMSTA.B28 –
ALMSTA.B32

83
B0193AW – Rev R 8. Block/Process Alarming

Conditions that determine how these bits are updated include:

1. CRIT and PRTYPE are updated when any alarm change occurs in the block.
2. HMA and LMA are mutually exclusive, and are updated when High Absolute or Low
Absolute alarm status changes occur.
3. HDA and LDA are mutually exclusive, and are updated when High Deviation or Low
Deviation alarm status changes occur.
4. HOA and LOA are mutually exclusive, and are updated when High Output or Low
Output alarm status changes occur.
5. HHA is updated when High High alarm status changes occur.
6. RATE is updated when Rate alarm status changes occur.
7. BAD is updated when I/O bad alarm changes occur.
8. STAL is updated when State alarm changes occur.
9. UNACK is updated every processing cycle. UNACK is set automatically when a new
alarm condition is detected. It is reset by the operator.
10. TRIP is updated when a Trip alarm change occurs in an EVENT block.
11. OOR is updated when a Range alarm change occurs in an AIN block.
All block types update the alarm status each processing cycle in order to track user changes in the
UNACK status.
The ALMSTA parameter is set to zero when a block initializes.
ALMSTA for all block types except AOUT, COUT, and MCOUT is set to zero on an Auto to
Manual transition. ALMSTA can be accessed by application programs. It can also be accessed by
other blocks having long (32-bit) integer inputs that can be handled as packed Booleans (for
example, the MCIN block when the IOMOPT option is configured false, or the CALC block).
Table 8-1 indicates the literal names assigned to the individual bits of ALMSTA. These names can
be used in Boolean connection extensions (for example, ALMSTA.HHA).
As you will read later, each block only uses certain bits of ALMSTA, depending on the alarms
available in the block. In order for other blocks and applications to determine which alarms are
available in each block, the Alarm Option parameter is used.

Alarm Option Parameter (ALMOPT)

Alarm Option (ALMOPT) is a 32-bit block output parameter that is bit mapped to indicate
which alarms are configured for a particular block. ALMOPT is a non-settable, non-connectable
parameter. Each individual block description in Integrated Control Block Descriptions (B0193AX)
identifies the specific bits that make up the ALMOPT parameter for that block.

84
8. Block/Process Alarming B0193AW – Rev R

A list of all the bits that can be assigned to the ALMOPT parameter and their indicated config-
ured alarms follows:

Table 8-2. ALMOPT-Assignable Bits

Bit Number1 Configured Alarm Option Boolean Connection

(0 to 31) When True (B32 to B1)
0 Alarm Group 8 in Use ALMOPT.B32
1 Alarm Group 7 in Use ALMOPT.B31
7 Alarm Group 1 in Use ALMOPT.B25
16 Low Absolute Alarm Configured ALMOPT.B16
17 High Absolute Alarm Configured ALMOPT.B15
18 Low Output Alarm Configured ALMOPT.B14
19 High Output Alarm Configured ALMOPT.B13
20 Low Deviation Alarm Configured ALMOPT.B12
21 High Deviation Alarm Configured ALMOPT.B11
22 Bad I/O Alarm Configured ALMOPT.B10
24 Low-Low Absolute Alarm Configured ALMOPT.B8
25 High-High Absolute Alarm Configured ALMOPT.B7
26 State Alarm Configured ALMOPT.B6
27 Operational Error Alarm Configured ALMOPT.B5
28 Out-of-Range Alarm Configured ALMOPT.B4
1.
Bit 0 is the least significant bit (starting from the right).

There are no mnemonic names for the individual bits of ALMOPT.

The alarms available in each block are ranked according to their importance in the system using
the criticality and priority type parameters which are described in the following section.

Criticality and Priority Type

It is important for the operator to be aware of which alarms take precedent over others. Each
block uses the criticality and priority type parameters to make this determination automatically
for the operator.
Criticality (CRIT) is an integer output that indicates the priority of the block’s highest currently
active alarm. The integer is a value of 1 through 5 with 1 being the highest priority. An output of
zero indicates the absence of alarms.
Priority Type (PRTYPE) is an indexed output parameter that indicates the alarm type of the high-
est priority active alarm. The PRTYPE output includes the alarm types in Table 8-3.

85
B0193AW – Rev R 8. Block/Process Alarming

Table 8-3. PRTYPE Indicators

Bit Number
(0 to 9) Description When True
0 No Active Alarm
1 High Absolute Alarm
2 Low Absolute Alarm
3 High High Absolute Alarm
4 Low Low Absolute Alarm
5 High Deviation Alarm
6 Low Deviation Alarm
7 Rate of Change Alarm
8 Bad I/O Alarm
9 State Alarm
25 Out of Range Alarm

Together, PRTYPE and CRIT record the level and type of the highest alarm currently active. For
example, assume the Bad and State alarms are both active. If the Bad alarm has priority 3 and the
State alarm has priority 2, then CRIT = 2 and PRTYPE = 9. If the Bad alarm has priority 1 and
the State alarm has priority 4 then CRIT = 1 and PRTYPE = 8. If both alarms have priority 2,
then CRIT = 2 and PRTYPE = 8.
The compound processor maintains a compound criticality parameter in the compound header as
it is processing the blocks. This connectable parameter stores the criticality of the highest priority,
currently-active alarm in the compound, for the Alarm Manager to display.
Despite the priority level of each alarm, any alarm can be inhibited by the operator. The following
section details alarm inhibition.

Alarm Inhibition
Block alarm inhibition is the process by which a block establishes a set of behaviors for specific
alarms, such as preventing the delivery of alarm messages to the process displays and, optionally,
disabling alarm detection.
The following parameters play key roles in inhibiting alarms:
♦ INHIB, INHALM, and INHOPT define the behaviors for the inhibited (and in
some cases, uninhibited) block alarms (see Figure 8-2)
♦ CINHIB (in the CMP block) inhibits alarm messaging and detection at the com-
pound level
♦ INHSTA records which alarms have been inhibited for a particular block.
Figure 8-2 illustrates how INHIB, INHALM, and INHOPT define block alarm inhibition.

86
8. Block/Process Alarming B0193AW – Rev R

Block alarm inhibition is a two step process:

1) Decide which alarms are inhibited: 2) Decide how inhibited and uninhibited
alarms behave, via INHOPT:

*INHOPT
3
INHIB 1
2 INHIBITED ALARMS
UNINHIBITED ALARMS
BLOCK and their behaviors
ALARMS INHALM 1
0
0

INHIB = 1 inhibits all alarms.

*See Table 8-5 “INHOPT Values” for complete
INHALM (see block description) inhibits specific
descriptions of these options.
alarms.

To perform these changes, see “Controlling Alarm States” in

Process Operations and Displays (B0193MM)

Figure 8-2. INHIB, INHALM, and INHOPT Behavior

These inhibiting parameters are described in detail below:

♦ “INHALM” in next section
♦ “INHIB” on page 88
♦ “INHOPT” on page 88
♦ “CINHIB” on page 89
♦ “INHSTA” on page 89.

INHALM
INHALM is a 16-bit packed Boolean input parameter that is supported in the continuous blocks
that perform alarm detection for multiple alarm types or points. The packed Boolean values spec-
ify the alarm types or points to inhibit in the block. INHALM is a configurable, settable, and con-
nectable parameter that is used in conjunction with the CINHIB compound parameter and the
INHIB block parameter to determine which alarm types and points to inhibit in the block.
INHALM is not supported in AOUT, COUT, CHARC, PATALM, or in sequential blocks (DEP,
IND, EXC, MON), since these blocks contain a single alarm that you inhibit by setting the
INHIB parameter in the block. See Integrated Control Block Descriptions (B0193AX) to identify
the specific bits that make up the INHALM parameter for that block.
A list of all the bits that can be assigned to the INHALM parameter and their indicated inhibited
alarms is shown in Table 8-4.

87
B0193AW – Rev R 8. Block/Process Alarming

Table 8-4. INHALM-Assignable Bits

Bit Number* Boolean Connection

(0 to 15) Description When True (B16 to B1)
0 Inhibit Low Absolute Alarm INHALM.B16
1 Inhibit High Absolute Alarm INHALM.B15
2 Low Output Alarm INHALM.B14
3 High Output Alarm INHALM.B13
4 Low Deviation Alarm INHALM.B12
5 High Deviation Alarm INHALM.B11
6 Inhibit Bad I/O Alarm INHALM.B10
7 Rate of Change Alarm INHALM.B9
8 Inhibit Low-Low Absolute Alarm INHALM.B8
9 Inhibit High-High Absolute Alarm INHALM.B7
10 State Change Alarm INHALM.B6
11 Sequence Operational Error Alarm INHALM.B5
12 Inhibit Out-of-Range Alarm INHALM.B4
13 Inhibit Alarm INHALM.B3
14 Unacknowledged INHALM.B2
15 Trip Alarm INHALM.B1

* Bit 0 is the least significant bit (starting from the right).

There are no mnemonic names for the individual bits of INHALM.

INHIB
Inhibit is a Boolean input. When true, it inhibits all block alarms; the alarm handling and detec-
tion functions are determined by the INHOPT setting. Alarms can also be inhibited based on
INHALM and the compound parameter CINHIB.

INHOPT
Inhibit Option specifies the actions in Table 8-5 that apply to all block alarms. Refer to Figure 8-2
for more information on the role of INHOPT in alarm inhibition.

Table 8-5. INHOPT Values

Value Alarm Inhibit Options

0 Inhibit alarm messages when alarms are detected. If an alarm occurs, flash the current
alarm display and the appropriate detail displays, and sound the annunciator horn, if
present.
1 Inhibit the detection of process alarms and the generation of alarm messages. All existing
alarm states in the block are cleared automatically when the alarm is inhibited.

88
8. Block/Process Alarming B0193AW – Rev R

Table 8-5. INHOPT Values (Continued)

Value Alarm Inhibit Options

2 Inhibit alarm messages when alarms are detected. If an alarm occurs, flash the current
alarm display and the appropriate detail displays, and sound the annunciator horn, if
present (same as Value=0) plus enable automatic acknowledgement of alarms when they
return to normal.
3 Inhibit the detection of process alarms and the generation of alarm messages. All existing
alarm states in the block are cleared automatically when the alarm is inhibited (same as
Value=1) plus enable automatic acknowledgement of alarms when they return to normal.

The INHOPT parameter also has the following attributes:

♦ The INHOPT parameter is configurable, but it is not settable or connectable.
♦ If INHOPT = 0 or 2, and alarms are inhibited, alarm detection is performed, but
alarm messages are disabled.
♦ If INHOPT = 1 or 3, and alarms are inhibited, alarm detection is disabled.
♦ If alarm detection is being performed and INHOPT = 0 or 1, alarms must be
acknowledged by an explicit user ACK command to reset the UNACK parameter to
0. This must be done even after the alarm has returned to normal.
♦ If alarm detection is being performed and INHOPT = 2 or 3, alarms are acknowl-
edged automatically when all alarms return to normal. If all alarms have not returned
to normal, they may also may be acknowledged by an explicit user command to set
UNACK to 0. This means that the UNACK parameter will be cleared and the
UNACK Boolean reset in block status when all alarms in the block have returned to
normal. At that time, an ALARM_ACK message is sent to all reporting alarm devices
configured in the block and compound.

CINHIB
Compounds also support an alarm-inhibit parameter for the entire compound. The CINHIB
parameter is a connectable integer that sets the suppression level of all messages at and below the
specified priority level within the compound. The levels of each alarm are based on the value of
CRIT (see “Criticality and Priority Type” on page 85).
Compound Inhibit specifies the priority levels of alarm inhibition within the compound, where:
♦ 0 = no inhibit
♦ 1 = inhibit all inclusive
♦ 2 = inhibit levels 2-5 inclusive
♦ 3 = inhibit levels 3-5 inclusive
♦ 4 = inhibit levels 4-5 inclusive
♦ 5 = inhibit level 5.

INHSTA
Inhibit Status (INHSTA) is a 32-bit block output parameter that is bit mapped to indicate the
status of inhibited alarm options for a particular block. See Integrated Control Block Descriptions
(B0193AX) to identify the specific bits that make up the INHALM parameter for that block.

89
B0193AW – Rev R 8. Block/Process Alarming

A list of all the bits that can be assigned to the INHSTA parameter and their alarm status follows:

Table 8-6. INHSTA-Assignable Bits

Boolean
1
Bit Number Connection
(0 to 31) Name Description When True (B32 to B1)
16 LMA Low Absolute Alarm Inhibited INHSTA.B16
17 HMA High Absolute Alarm Inhibited INHSTA.B15
18 LOA Low Output Alarm Inhibited INHSTA.B14
19 HOA High Output Alarm Inhibited INHSTA.B13
20 LDA Low Deviation Alarm Inhibited INHSTA.B12
21 HDA High Deviation Alarm Inhibited INHSTA.B11
22 BAD Bad I/O Alarm Inhibited INHSTA.B10
23 RATE Rate of Change Alarm Inhibited INHSTA.B9
24 LLA Low-Low Absolute Alarm Inhibited INHSTA.B8
25 HHA High-High Absolute Alarm Inhibited INHSTA.B7
26 STAL State Change Alarm Inhibited INHSTA.B6
27 OPER Sequence Operational Error Alarm Inhibited INHSTA.B5
28 OOR Out-of-Range Alarm Inhibited INHSTA.B4
29 INH Inhibit Alarm Inhibited INHSTA.B3
30 UNACK Unacknowledged Inhibited INHSTA.B2
31 TRIP Trip Alarm Inhibited INHSTA.B1
1.
Bit 0 is the least significant bit (starting from the right).

Process Alarm Types

The following types of process alarms are used in the I/A Series system. A block may have multi-
ple types of process alarms, depending on the block:
♦ Absolute alarming (includes output alarming, pretarget alarming, and target alarming)
♦ Bad input/output (I/O) alarming - see page 93
♦ Deviation alarming - see page 93
♦ Mismatch alarming - see page 95
♦ Out of range alarming - see page 95
♦ Rate of change alarming - see page 96
♦ Sequence operational error alarming - see page 97
♦ State change alarming - see page 97
♦ Trip alarming - see page 98.

90
8. Block/Process Alarming B0193AW – Rev R

NOTE
Other forms of alarming are available as well, but only the following types of alarm-
ing are explicitly initiated by blocks. For examples of other types of alarming, such
as authorized/unauthorized movement alarming, density rate-of-change alarming,
and flow rate alarming, refer to Measurement Integration (B0193RA).

Absolute Alarming
Absolute alarming produces alarms when the measurement has exceeded or dropped below a user
defined high or low limit. There are four types of predefined limits that absolute alarming can
check for:
♦ High-High Absolute Alarming/Target Alarming2
♦ High Absolute Alarming/High Output Alarming2
♦ Low Absolute Alarming/Low Output Alarming2
♦ Low-Low Absolute Alarming.
Figure 8-3 illustrates the principle of absolute alarming.

High absolute
alarm limit deadband

Low absolute deadband

alarm limit

Signal
HA=0 HA=0 HA=1 HA=0 HA=0
LA=1 LA=0 LA=0 LA=0 LA=1

HA = High Alarm Time

LA = Low Alarm

Figure 8-3. Absolute Alarming

There are two user defined settings that you need to configure: high and low alarms limits. Each
set of limits must also have a deadband setting associated with it. The deadband is an absolute
engineering unit that filters out signal jitter, preventing the signal from bouncing in and out of an
alarm state. As the signal passes the defined limits, the alarm is set accordingly.
These four types of absolute alarming are described below.

2.
Different names for the same sub-type of alarming, see below for details.

91
B0193AW – Rev R 8. Block/Process Alarming

High Absolute Alarming/High Output Alarming

High absolute alarming is initiated after the signal has climbed above a predefined threshold.
High-high absolute alarming is generally initiated after a high absolute alarm to provide a warning
that the signal has continued to climb after it crossed the high absolute threshold.

NOTE
In ACCUM, this type of alarming is called target alarming.

NOTE
Certain blocks, such as BIAS, perform high output alarming, which is identical in
function to high absolute alarming. However, high output alarming has its own cor-
responding bits in ALMSTA, ALMOPT, INHALM, and INHSTA.
In ACCUM, this type of alarming is called pretarget alarming, and is completely
identical to high absolute alarming.

In this type of alarming, the signal is compared to the high absolute (or output) alarm limit set for
the block. If the signal is greater than this limit, the block:
♦ sets its high absolute (or output) alarm indicator to true,
♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message that includes the user-defined high absolute (or output)
alarm text.
When the signal falls to, or below, the alarm limit minus the signal deadband, the block sets the
appropriate high alarm indicator to false, resets the appropriate bit in the alarm status parameter,
and outputs a return-to-normal message.

Low Absolute Alarming/Low Output Alarming

Low absolute alarming is initiated after the signal has climbed below a predefined threshold.
Low-low absolute alarming is generally initiated after a low absolute alarm to provide a warning
that the signal has continued to drop after it crossed the low absolute threshold.

NOTE
Certain blocks, such as BIAS, perform low output alarming, which is identical in
function to low absolute alarming. However, low output alarming has its own corre-
sponding bits in ALMSTA, ALMOPT, INHALM, and INHSTA.

In this type of alarming, the signal is compared to the low absolute (or output) alarm limit set for
the block. If the signal is less than this limit, the block:
♦ sets its low absolute (or output) alarm indicator to true,
♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message that includes the user-defined low absolute (or output)
alarm text.

92
8. Block/Process Alarming B0193AW – Rev R

When the signal rises to, or above, the alarm limit (plus the signal deadband, in some cases), the
block sets its low alarm indicator to false, resets the appropriate bit in the alarm status parameter,
and outputs a return-to-normal message.

Bad Input/Output Alarming

Bad I/O alarming is initiated if the device to which the block is connected becomes non-opera-
tional (BAD). It is generated via the alarm status parameter.

NOTE
There is some confusion about the difference between a Bad I/O alarm, and a BAD
status. For a given block, BAD is the status of a parameter which has its BAD bit
set. Status is separate from alarming; it is not an alarm condition. See “Connectable
Parameters” on page 6 for more information on BAD (or IO BAD) status.

For blocks which receive redundant signals, such as DPIDA, the block generates a separate alarm
message when any signal is bad, but it sets the Bad I/O Alarm state and BAD parameter only
when all of the signals are bad.
Additional events may occur in some blocks. For example, in MTR, the block enters the Bad state
and holds the outputs at the last known driven state of the device.

Deviation Alarming
Deviation alarming checks if the deviation negative error signal (deviation) has exceeded or
dropped below a predefined set point. There are two types of predefined limits for which devia-
tion alarming can check:
♦ High Deviation Alarming
♦ Low Deviation Alarming
Figure 8-4 illustrates the principle of deviation alarming.

93
B0193AW – Rev R 8. Block/Process Alarming

HDA
deadband

Setpoint

LDA deadband

Signal
HDA=0 HDA=0 HDA=1 HDA=0 HDA=0
LDA=1 LDA=0 LDA=0 LDA=0 LDA=1

HDA = High Deviation Alarm

Time
LDA = Low Deviation Alarm

Figure 8-4. Deviation Alarming

In addition to setting the setpoint, you need to set both high and low limits and the deadband.
The deadband is an absolute engineering unit that filters out signal jitter, preventing the signal
from bouncing in and out of an alarm state. As the signal passes the defined limits, the alarm is set
accordingly.
The two forms of deviation alarming are described below.

High Deviation Alarming

In high deviation alarming, the deviation (signal minus the set point) is compared to the high
deviation alarm limit set for the block. If the deviation is greater than this limit, the block:
♦ sets its high deviation alarm indicator true,
♦ reports the alarm via the alarm status parameter, and
♦ outputs an alarm message that includes the user-defined high deviation alarm text.
When the deviation falls to, or below, the high deviation alarm limit minus the deadband, the
block sets its high deviation alarm indicator to false, resets the appropriate bit in the alarm status
parameter, and outputs a return-to-normal message.
The alarm value field of the messages reports the deviation in engineering units at the instant the
alarm condition changes to active.

94
8. Block/Process Alarming B0193AW – Rev R

Low Deviation Alarming

In low deviation alarming, the deviation (signal minus the setpoint) is compared to the low devia-
tion alarm limit set for the block. If the deviation is less than this limit, the block:
♦ sets its low deviation alarm indicator true,
♦ reports the alarm via the alarm status parameter, and
♦ outputs an alarm message that includes the user-defined low deviation alarm text.
When the deviation rises to, or above, the low deviation alarm limit plus the deadband, the block
sets its low deviation alarm indicator to false, resets the appropriate bit in the alarm status param-
eter, and outputs a return-to-normal message.
The alarm value field of the messages reports the deviation in engineering units at the instant the
alarm condition changes to active.

Mismatch Alarming
Mismatch alarming initiates when the requested state of a device fails to match the actual state of
a device within a time interval specified at the block level. The time at which the mismatch time-
out begins varies, depending on the block (see the MTR and VLV blocks for examples).

NOTE
Mismatch alarming is generated by the block’s own logic, and not by ALMSTA.

When a mismatch alarm occurs, the mismatch alarm option parameter is set to true, causing the
AUTOPN or MANOPN parameter in the block to be reset to its original state. This allows you
to retry the original request action, without having to toggle the request parameter in the wrong
direction, by creating a leading edge for the timeout to begin again. Also, an alarm report is gener-
ated, using the text in the Name 0 and Name 1 parameters.
When the alarm is acknowledged by the operator, or the field input indicates that the device has
changed state as requested, the mismatch alarms are cleared, and return-to-normal messages are
generated.

Out of Range Alarming

Out of range alarming initiates when the output exceeds or drops below the specified range set for
the block. This type of alarming creates a single alarm when initiated.
However, it can be initiated if:
♦ the signal exceeds the high scale for output range value, and the high out of range
Boolean (HOR) is set, or
♦ the signal drops below the low scale for output range value, and the low out of range
Boolean (LOR) is set.
Figure 8-5 illustrates the principle of out of range alarming.

95
B0193AW – Rev R 8. Block/Process Alarming

OOR status bit in ALMSTA and HOR are set.

High Scale for

Output Range 1

Signal

Low Scale for

Output Range 1 OOR status bit in ALMSTA
and LOR are set.
Time

Figure 8-5. Out of Range Alarming

When initiated, this alarm:

♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message to the configured alarm group that includes the user-
defined alarm text, and the alarm priority.
When the signal returns between the high and low alarm limits, the block resets the appropriate
bit in the alarm status parameter, and outputs a return-to-normal message.

Rate Of Change Alarming

When enabled, rate of change alarming occurs when the magnitude of signal change per period
exceeds a configured delta in the rate-of-change limit for the configured ROCTIM. Figure 8-6
shows how the rate of change is determined for a signal value.

y3

y2

y1

y0

Signal
t0 t1 t2 t3 t4 t5 tx

y = Signal change
t = time period Time

Figure 8-6. Rate of Change Alarming

96
8. Block/Process Alarming B0193AW – Rev R

If the rate of change exceeds the rate-of-change limit over a consecutive time period greater than
the ROCTIM time, the block:
♦ sets the rate of change indicator to true
♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message to the configured alarm group that includes the user-
defined alarm text, and the alarm priority.
When the rate of change no longer exceeds the rate-of-change limit over a consecutive period
greater than the ROCTIM time, the rate of change indicator is set to false and the block generates
a return-to-normal message.
If ROCTIM = 0 then the block compares changes over 1 time period. For example:
If y 1 – y 0 > ROCLIM then set the alarm. If y 2 – y 1 > ROCLIM then alarm stays on.
The alarm returns to normal if y 3 – y 2 < ROCLIM
If ROCTIM = 1 then the block compares changes over 2 time periods. For example:
If y 1 – y 0 > ROCLIM and y 2 – y 1 > ROCLIM then set the alarm.
The alarm returns to normal if y 3 – y 2 < ROCLIM
This type of alarming is performed in blocks such as MEALM.

Sequence Operational Error Alarming

Sequence operational error alarming is performed in sequence blocks, such as MON. MON con-
tains up to 16 user-defined Boolean expressions referred to as monitor cases. Monitor cases can be
defined such that when they are evaluated, either to True or to some BAD marked value, the
MON block activates a named sequence block, which can be an EXC, IND, or DEP block, or
even another MON block.
Sequence operational error alarming is initiated if a monitor case becomes tripped, but the
sequence block associated with the monitor case cannot be found. When initiated, the block:
♦ raises an operational error, and sets the operational error indicator to true
♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message to the configured alarm group that includes the user-
defined alarm text, and the alarm priority.
The alarm is discontinued and a return-to-normal message is issued when the required sequence
block activates.

State Change Alarming

State change alarming is the monitoring of state changes in another block. State change alarming
is performed by the STALM block and is initiated when the monitored indicator moves into an
alarm state. For example, STALM uses state change alarming to serve as alarm annunciator to
activate the I/A Series alarm mechanism upon alarm conditions detected by an external source
such as HTG.
When initiated, the block:
♦ reports the alarm via the alarm status parameter, and
♦ outputs an alarm message to the configured alarm group that includes the user-
defined alarm text, and the alarm priority.

97
B0193AW – Rev R 8. Block/Process Alarming

The alarm is discontinued and a return-to-normal message is issued when the block detects a tran-
sition out of alarm.

Trip Alarming
Trip alarming invokes a specific response which differs from block to block when a certain state
change occurs.
For EVENT, trip alarming indicates a state change in a Boolean output that is set true when the
block reads a new (unreported) event record from its associated FBM.
For MON, trip alarming indicates the BAD bit of a monitor case (see “Sequence Operational
Error Alarming” on page 97) is set.
Other blocks have alternate behaviors for trip alarming.
When initiated, the block:
♦ performs a specific block-dependent action (refer to the block description of the block
for more information)
♦ generates the alarm via the alarm status parameter, and
♦ outputs an alarm message to the configured alarm group that includes the user-
defined alarm text, and the alarm priority.
The alarm is discontinued and a return-to-normal message is issued when the block detects a tran-
sition to the original state.

98
9. Ladder Logic Concepts
This chapter discusses ladder logic and ladder logic diagrams in depth, as well as fanned
outputs, zone control logic, programmable logic (PLB) block operation, and gives a PLB editor
overview.

Ladder Logic Overview

Ladder logic diagrams use symbols traditionally associated with relay circuits. These symbols, con-
sisting of contacts, timers, counters, and coils, are used to build rungs. The rungs are built into
ladders.
Ladder logic capability is a configurable option in digital Fieldbus Modules, where the Ladder
diagrams are processed; ladder logic cannot be processed in the Cluster I/O type of digital mod-
ules however, such as FBC07, FBC09, or FBC10. A Programmable Logic Block (PLB) in the con-
trol processor supports ladder logic operation, integrating it with control block processing. See
below for a simplified diagram showing the interaction of the main Ladder Logic components.

PROGRAMMABLE Physical I/O and

LOGIC External Flag
Physical I/O and BLOCK Parameters
External Flag
(To/From
Table
Other Blocks)
>>BLOCK Control
PROCESSING<< Processor

Contact Fieldbus
Input/Output Module
LADDER
DIAGRAM
(To/From
the Process) >>RUNG
PROCESSING<<

Figure 9-1. Ladder Logic Components (Simplified)

Ladder Diagram Functions

Ladder diagram rungs sense the status of digital inputs and control the status of digital outputs.
Inputs to ladder logic come from physical input points connected to the field terminals of the
Fieldbus Module or from external input flags supplied by control processor blocks. Physical
inputs present process status information from devices such as limit switches, push buttons, and
pressure switches. External input flags allow continuous and sequential blocks and user tasks to
initiate or control ladder logic action.
Outputs from ladder logic go to physical output points connected to the field terminals of the
Fieldbus Module or to physical output parameters and external output flags supplied to control
processor blocks. Physical outputs control devices such as solenoids, motor starters, and indicator
lamps. Physical output parameters and external output flags allow continuous and sequential
blocks and user tasks to monitor ladder logic action.

99
B0193AW – Rev R 9. Ladder Logic Concepts

PLB Functions
A PLB block connects user tasks, other blocks, and other ladder diagrams with:
♦ A ladder diagram’s external I/O flags
♦ A digital Fieldbus Module’s physical inputs and outputs.
Each PLB block defines a ladder diagram.
Creating a PLB establishes a ladder diagram source file. Using this source file, the PLB ladder
logic editor lets you construct a ladder diagram, check it for syntax errors, and produce a printed
copy for documentation. You can choose to have the ladder diagram code installed in a digital
Fieldbus Module or save the source file for later use. You can develop a library of ladder diagrams
and retrieve (copy) them for installation in multiple Fieldbus Modules. You can also save ladder
diagram source files (as part of a compound) on diskette.
The ladder diagrams remain “generic”, independent of hardware, until the associated PLB block is
assigned to a specific Fieldbus Module. The elements then become bound to that hardware
component.
Through the PLB block’s detail (default) display, you can monitor the status of ladder logic con-
tacts, timers, counters, and coils. Alternatively, you can create your own graphic displays. Displays
that you generate access the status of ladder logic elements through external flag parameters. The
PLB’s detail display allows you to force contacts and coils on or off to verify correct operation of
the logic under simulated process conditions.
The ladder logic editor configures and checks at the block level; not at the FBM level. Since up to
eight ladders can be configured to run in the same FBM, you must consider certain interactions
and constraints. These include:
♦ All ladders in a given FBM use a single coil table or table of parameter values. The
available ladder components or “technical identifiers” constitute a fixed pool of
resources associated with the final concatenated ladder. Ensure that one ladder does
not conflict with the outputs of another, for example, turning off an output that
another ladder has just turned on.
♦ FBM state control applies to all ladders in the FBM.
♦ The FBM’s 16 timer/counters are available to all ladders in the FBM. Plan for the
consistent use and selection of these 16 components across ladder boundaries. Always
reset timers and counters prior to use.
♦ Once you configure a timer/counter with a specific technical ID, you cannot associate
that ID with a different timer/counter.
♦ The total number of ladder logic lines for all ladders in a given FBM must be less than
98.
♦ The FBM can accommodate approximately 850 bytes of object code representing the
ladder logic. This can support about 390 user-entered ladder symbols. (Straight line
horizontal and vertical segments can be considered as using no memory.)

100
9. Ladder Logic Concepts B0193AW – Rev R

Ladder Diagram Description

Input parameters are represented as contact symbols (Boolean inputs) on the ladder diagram.
Output parameters are represented as coil symbols, including relays, timers, counters, and condi-
tional coils.
Typical symbols:

––––|/|–––– Normally Closed Contact

––––| |–––– Normally Open Contact
––––( )–––– Coil

A ladder logic diagram is made up of rungs. A ladder rung is a logical element with one or more
input conditions and a single output value. (Outputs can be paralleled for fanout.)
When drawn, the logic consists of two conceptual vertical rails – power source on the left and
return on the right. (These rails do not appear visibly in ladder displays.) Coils, timers, and
counters attach directly to the right-hand rail. Contacts complete a power flow path from the left-
hand rail to the timer, counter, or coil

Power rail Return

( )
Start Pump
PB

Figure 9-2. Simplified Ladder Logic Diagram

Ladder logic is executed rung by rung from top to bottom of the ladder. Ladders are executed at
an average of 300 ladder logic symbols in 20 to 25 ms. During execution, each contact symbol in
the rung is examined and compared with the Boolean value referenced by its technical identifier.
Power flow is enabled through the contact in the following situations:
♦ The contact is represented as normally-open on the ladder diagram and the referenced
input is true (present or active).
♦ The contact is represented as normally-closed on the ladder diagram and the refer-
enced input is false (not present or inactive).
Ladder logic flows from left to right, mimicking power flow from source to destination.
As each ladder logic rung is executed, if the enabled contacts provide a complete path from the left
margin (power rail) to the output coil (or paralleled coils) connected to the right margin (return
rail), then the coil is “activated” (that is, the Boolean value for its associated technical identifier is
set true). The coil remains active until the next cycle when that rung is scanned and the inputs are
again analyzed. If the power flow path no longer exists, the coil is deactivated, unless the coil is a
latching type.
Latching coils, once energized, remain active until an unlatching coil with the same technical
identifier is energized.
You place logic symbols strategically on the ladder rungs to depict a combination of conditions or
sequence of events. This placement determines the control logic.

101
B0193AW – Rev R 9. Ladder Logic Concepts

The contacts can be connected in series in a simple circuit where all conditions must be met for
the path to be completed (ANDing of conditions). A normally open contact provides a path when
the condition for which it is named is true. A normally closed contact provides a path when the
condition for which it is named is false. In this series network, when all the conditions represented
by normally open contacts are true and all the conditions represented by normally closed contacts
are false, the path is complete.

/ ( )
Start Over Pump
PB Temp

Figure 9-3. Ladder Logic Contacts

A row contains up to seven contact symbols; the last position is reserved for a coil symbol. Hori-
zontal “connector” symbols provide power flow through positions in a row where no contact is
configured.
Rows may be interconnected through a vertical connector symbol. A ladder rung comprises all
rows (branches) connecting to a given coil, timer, or counter, or fanout of these. You can scroll
vertically to view a ladder diagram containing more rungs than the screen can display at one time.

Vertical Vertical
Horizontal
Connector, Connector,
Connector Symbol Up Symbol Down Symbol

Figure 9-4. Ladder Logic Connectors

The contacts can be connected in a series, parallel circuit where the parallel portion provides an
alternate set of conditions that allow the path to be completed (ORing of conditions). For
example, the main leg could provide for activating a coil, and the parallel leg provide a path to
keep it activated. When logic continuity exists in at least one path, the rung is true or has a GO
condition.

( )
Start Over Pump
PB Temp

Full Stop
Tank PB

Figure 9-5. Parallel Circuits in Ladder Logic

102
9. Ladder Logic Concepts B0193AW – Rev R

Ladder Diagram Display

As displayed, the ladder diagram omits the left and right rails; their existence is implied.
The following figure shows a typical ladder diagram display.

HELP SYMBOLS COMPILE FILES PRINT NEW LINE NEW TI NEXT TI DONE CANCEL

COMPOUND: VAT4 BLOCK: PUMP1

CIN_10 CIN_15 CO_01

( )
Start Over Pump
PB Temp

CIN_14 CIN_11

Full Stop
Tank PB

Tank fill.

Figure 9-6. Typical Ladder Diagram Display

Ladder Diagram Execution

The Fieldbus Module ladder logic executive performs logical operations based on the placement
of the contacts and coils in the ladder diagram.
Rungs are executed in sequence, in an infinite loop, from beginning to end of the ladder. Each
execution of the loop is termed a scan. As each rung is processed, contact status is evaluated and if
a path exists, the rung output is activated. The actual state of the physical input associated with
the contact is recognized when the rung is executed.
To allow for replacing the program without taking the control off line for an extended period, the
Fieldbus Module provides two application program spaces. This allows an existing program to
execute from one while a revised program is loaded into the other.

Ladder Diagram Construction

You build your ladder diagram in a work area occupying all of the screen below the menu bar,
except for a column at the right for timer/counter preset and reset values. The following figure
shows the work area that is reserved for the ladder rungs and the logic symbols.
The ladder logic editor lets you create ladder diagrams from a set of predefined symbols and iden-
tifiers, preset and reset values for counters and timers, and your choice of text labels for symbols
and rungs. A ladder diagram row accepts up to seven series-contacts and a coil.
From the menu bar you can select SYMBOLS to display the symbols and function key assign-
ments which create these or HELP to display the instruction set and technical identifiers that can
be used for constructing a ladder.

103
B0193AW – Rev R 9. Ladder Logic Concepts

HELP SYMBOLS COMPILE FILES PRINT NEW LINE NEW TI NEXT TI DONE CANCEL

timer
and
work area
counter
preset/
reset
values

Figure 9-7. Ladder Diagram Work Area

Symbols
Table 9-1 below shows the ladder instruction set used to implement ladder logic.

Table 9-1. Ladder Symbols

Symbol Name Description

Normally Open Contact Provides power flow from left to right when the
named signal is present (true state).
Normally Closed Contact Provides power flow from left to right when the
named signal is absent (false state).
——— Connector Provides power flow through a symbol position.

Vertical Connector (down) Joins two rows when used together with a matching
vertical connector (up).
Vertical Connector (up) Joins two rows when used with a vertical connector
(down). Used in pairs, vertical connectors provide
power flow vertically within a ladder diagram.
( ) Energize Coil Sets the Boolean value representing coil status true if
the rung has a power flow path. If the path is lost, the
Boolean value is set false.
( ) Write Not Coil Sets the Boolean value representing coil status false if
the rung has a power flow path. If the path is lost, the
Boolean value is set true.
—(L)— Latch Coil Sets the Boolean value representing coil status true if
the rung has a power flow path. If the path is lost after
the coil is set, the Boolean value remains true until the
associated Unlatch Coil is set.
—(U)— Unlatch Coil Unlatches an output that was previously set by a
Latch Coil instruction.
—(CTU)— Up Counter Increments a counter on off-to-on transitions.
—(CTD)— Down Counter Decrements a counter on off-to-on transitions.

104
9. Ladder Logic Concepts B0193AW – Rev R

Table 9-1. Ladder Symbols (Continued)

Symbol Name Description

—(RST)— Counter/Timer Reset Resets a counter or timer having the same technical
identifier as this symbol.
—(MCR)— Master Control Relay Enables the rungs between this symbol and the NCR
symbol to execute normally if the MCR rung condi-
tion is true. If MCR is false, the area rungs are not
executed and the nonretentive outputs within the area
are de-energized.
—(NCR)— End of Master Control Marks the end of the MCR conditional group of
Relay Zone rungs. This symbol must be alone on its rung.
—(ZCL)— Zone Control Logic Enables the rungs between this symbol and the NCL
symbol to execute normally if the ZCL rung condi-
tion is true. If ZCL is false, the rungs in the zone are
not executed and the outputs are held at their last
state.
—(NCL)— End of Zone Control Marks the end of the ZCL conditional group of
Logic rungs. This symbol must be alone on its rung.
—(RTO)— Retentive timer-on delay Indicates the rung has been true (POWER TRUE)
for at least the specified delay period.
—(RTF)— Retentive timer-off delay Indicated the rung has been false (POWER FALSE)
for at least the specified delay period.
—(TON)— Non-retentive timer-on Same as RTO except that when the rung is false at any
delay time, the accumulated time is zeroed.
—(TOF)— Non-retentive timer-off Same as RTF except that when the rung is true at any
delay time, the accumulated time is zeroed.

Text and Numeric Entries

Two types of text entries identify each contact, coil, and timer or counter in a ladder diagram. A
technical identifier is placed above each symbol and a label for it is optionally placed below the
symbol. An optional rung descriptor can be placed beneath each rung as shown below in the
Sample Ladder Diagram (the rung descriptor is “Schematic for blending initial ingredients”).
A set of numeric entries is associated with each counter (CTU or CTD) or timer symbol (RTO,
TON, RTF, or TOF). These entries, located in the right hand column of the ladder diagram con-
sist of a preset value identified by a “P” suffix, a reset value identified by an “R” suffix; and an
accumulated value identified by an “A” suffix. Accumulated values are not entered or displayed by
the PLB editor.
Table 9-2, following Figure 9-8, describes the text and numeric elements briefly. Table 9-3 lists
the technical identifiers.

105
B0193AW – Rev R 9. Ladder Logic Concepts

HELP SYMBOLS COMPILE FILES PRINT NEW LINE NEW TI NEXT TI DONE CANCEL

CIN_11 IFL_31 TC01_S CIN_18 TC07_S

4.5P
(RTO )
4.0R
Timer1 Rinse Heat
Mixer Stir
Empty Mix

TC01_S

Timer1
Schematic for blending initial ingredients

Figure 9-8. Sample Ladder Diagram

Table 9-2. Text and Numeric Elements

Text and Numeric

Elements Description
Technical Identifier A single row of up to six upper case characters that identifies an
element by type and number (see Table 9-3).
Label Two rows of up to seven characters each, beneath the element.
Preset Value For timer or counter symbol, maximum value, up to 65,535. Timer
values represent tenths of seconds; counter values represent counts.
Reset Value For timer or counter symbol, minimum value, up to 65 535, set in at
reset time. Timer values represent tenths of seconds; counter values
represent counts.
Rung Descriptor Up to three lines of text with up to 60 characters in each. Used for
documentation as the previous diagram shows. Each ladder can have a
maximum of twenty rung descriptors.

Inputs to and outputs from ladder logic are stored as Boolean values referenced by technical iden-
tifiers. These identifiers are chosen from a list of valid names (see Table 9-3).

Table 9-3. Technical Identifiers

Technical Identifiers Meaning

CIN_1 through CIN_32 Physical Inputs
CO_1 through CO_16 Physical Outputs
IFL_1 through IFL_32 External Input Flags
OFL_1 through OFL_32 External Output Flags
TC01_S through TC16_S Timer/Counter Coils
TC01_S through TC16_S Timer/Counter Status Contacts
TC01_O through TC16_O Timer/Counter Overflow Contacts

106
9. Ladder Logic Concepts B0193AW – Rev R

Table 9-3. Technical Identifiers (Continued)

Technical Identifiers Meaning

INT_01 through INT_32 Internal Flags
INIT Initialize Flag
POWERF Power Fail Flag
COMMF Communications Failure Flag
FAILSF Fail-Safe Flag

The user-defined label consists of two text fields that may contain any comments (seven charac-
ters per field) to enhance the readability of the ladder diagram. Each label is associated with the
technical identifier, not with the symbol, as may be seen by the following rung example.

CO_15 CO_15
/ ( )
AREA123 AREA123
AGITATE AGITATE

Figure 9-9. User-Defined Labelling

Ladder Diagram Elements

Inputs (Contacts)
Ladder diagram inputs are represented as (relay type) contacts on the ladder diagram. These
inputs include the following:
♦ External input flag
♦ Internal coils
♦ Contact input
♦ External output flag
♦ Contact output
♦ Timer/Counter flag
Within the ladder diagram, an input can be represented as a normally open (NO) or a normally
closed (NC) contact. The technical identifier assigned to the contact indicates the source of the
input, as shown in Table 9-4. The input (with its technical identifier) can be used in the ladder as
many times as desired in NO and NC states.

Table 9-4. Ladder Inputs

Type of Applicable Contact Technical

Input Instructions Symbols Identifier Source
External Normally Open -| |- IFL_nn Ladder Logic Interface Block
Input Normally Closed -|/|- (PLB Block).
Flag
Contact Normally Open -| |- CIN_nn Fieldbus Module Physical Input.
Input Normally Closed -|/|-

107
B0193AW – Rev R 9. Ladder Logic Concepts

Table 9-4. Ladder Inputs (Continued)

Type of Applicable Contact Technical

Input Instructions Symbols Identifier Source
Contact Normally Open -| |- CO_nn Energize Coil, Write Not Coil,
Output Normally Closed -|/|- and Latch Coil instructions.
Internal Normally Open -| |- INT_nn Energize Coil, Write Not Coil,
Flag Normally Closed -|/|- and Latch Coil instructions.
External Normally Open -| |- OFL_nn Energize Coil, Write Not Coil,
Output Normally Closed -|/|- and Latch Coil instructions.
Flag
Timer/ Normally Open -| |- TCnn_S Up Counter, Down Counter,
Counter Normally Closed -|/|- TCnn_O Retentive Timer On-Delay,
Retentive Timer Off-Delay,
Non-Retentive Timer
On-Delay, and Non-Retentive
Timer Off-Delay

The control processor can obtain the status of a ladder logic physical input through the CIN_nn
parameter of the PLC block.

Outputs (Coils)
Outputs are represented as coils (see Table 9-5). The symbol and technical identifier assigned to
the coil determines the type of output provided:
♦ Contact output
♦ External output flag
♦ Internal flag
♦ Timer
♦ Counter.
Contact outputs control the status of Fieldbus Module output channels.
External output flags allow control processor blocks to monitor the status of a ladder rung.
Internal flags allow you to create AND conditions of more than seven elements in a single ladder
rung by cascading INT_nn elements.
Timer/counter flags allow you to condition rung outputs on the passage of a specified length of
time or the occurrence of a specified number of events.
Within the ladder diagram, any of these outputs can be represented as a normally open or a nor-
mally closed contact and used in both forms as many times as needed. However, a coil provides
only one physical output (CO_nn). To send output to an additional Fieldbus Module channel,
you would configure an additional coil, with its own technical identifier, in parallel with the first.

108
9. Ladder Logic Concepts B0193AW – Rev R

Table 9-5. Ladder Coils

Type of Coil Technical Primary

Output Applicable Instructions Symbols Identifier Destination
Contact Energize Coil -( )- CO_nn Fieldbus Module
Output Write Not Coil -(/)- physical output.
Latch Coil -(L)-
External Energize Coil -( )- OFL_nn Ladder Logic
Flag Output Write Not Coil -(/)- Interface block
(PLB Block).
Latch Coil -(L)-
Internal Flag Energize Coil -( )- INT_nn Internal
Write Not Coil -(/)-
Latch Coil -(L)-
Timer Retentive Timer-On Delay -(RTO)- TCnn_S Internal
Retentive Timer-Off Delay -(RTF)-
Non-retentive Timer-On -(TON)-
Delay
Non-retentive Timer-Off -(TOF)-
Delay
Counter Up Counter -(CTU)- TCnn_S Internal
Down Counter -(CTD)-

Counters and Timers

The ladder logic Fieldbus Module has timer/counter structures numbered 1 through 16. To
implement a timer or counter, you configure it as one of the following types:

Table 9-6. Counters and Timers

Category Type Symbol

Transition Counters Up Counter --(CTU)--
Down Counter --(CTD)--
Retentive Timers On Delay --(RTO)--
Off Delay --(RTF)--
Non-retentive Timers On Delay --(TON)--
Off Delay --(TOF)--

NOTE
All timers and counters use a “TC” technical identifier prefix, followed by a number
from 01 through 16, inclusive. For example, TC01 or TC16.

109
B0193AW – Rev R 9. Ladder Logic Concepts

Table 9-7. Counter/Timer State Terminology

Term Description
Ladder Rungs Evaluate to true or false.
Counters/Timers Are reset (contain the configured reset value), counting or timing,
count satisfied or delay timed out (at or above the configured preset
value), or overflow (at or beyond the maximum or minimum count
or time value)
Flags Are either true (raised, set, or 1-state) or false (lowered, reset,
cleared, 0-state).
Coils Are either Energized (activated) or De-energized (deactivated).

Associated with each timer/counter are two flags for communicating with the ladder and three
registers for controlling timer/counter operation.
Each timer or counter has a status flag and an overflow flag. The status flag is set when the pre-
specified count or time delay has been satisfied. The overflow flag is set when the maximum or
minimum count or delay time has been exceeded, and wrap has occurred.
Each timer or counter has three 16-bit registers, supporting counts from 0 to 65,535 and delay
times from 0 to 6,553.5 seconds. The registers store an initial value, a final value, and a current,
accumulated value. You specify initial and final values during configuration. Refer to Table 9-8.

Table 9-8. Timer/Counter Registers and Flags

Category Type Description

Registers Accumulated The number of counts or ticks since the last reset (not displayed)
Count/Time in the ladder editor.
Preset Value The target value for timers and counters; set through ladder
configuration.
Reset Value The initial value for timers and up counters; set through ladder
configuration and loaded by an RST operation.
Flags Status Flag Set if the accumulated value is equal to or greater than the preset
value for a timer or up counter, or less than the preset value for a
down counter. The status flag remains set until the timer/counter
is reset.
Overflow Flag Set on transition from 65,535 to 0 when counting up (overflow)
or from 0 to 65,535 when counting down (underflow).
When overflow is set, counts continue to accumulate via
wrapping, but the status flag retains the value it had when the
overflow or underflow occurred. The overflow flag remains
set – and the status flag frozen – until the timer/counter is reset.

110
9. Ladder Logic Concepts B0193AW – Rev R

Transition Counters
Up counters operate on rung transitions from false to true. Starting from a configured reset value,
an Up counter increments on each transition toward a configured preset value.
Down counters operate on rung transitions from false to true. Down counters are SET immedi-
ately following a reset signal to reset its value. When the count decrements and counts past the
preset value, the status is set FALSE. Once the count has been satisfied, the counter’s status flag is
set and remains so until the Reset coil for that counter is energized.

Retentive Timers
A retentive timer indicates, through its status flag, that its rung has been in a particular state for at
least the specified delay period. The delay period is determined as the difference between the pre-
set and reset values configured for the timer. Starting from the reset value, the timer counts clock
pulses or ticks that occur every tenth of a second. This type of timer retains the accumulated
count during intervals when its rung state is false.
An on-delay timer counts ticks whenever its rung state is true. As long as the delay is in effect, the
timer’s status flag is false. When the accumulated count equals the preset value, the timer’s status
flag is set true.
An off-delay timer counts ticks whenever its rung state is false. As long as the delay is in effect, the
timer’s status flag is true. When the accumulated count equals the preset value, the timer’s status
flag is set false.
Once the delay has been satisfied, the timer’s status flag retains its state until the timer’s reset rung
is set true. Regardless of timer rung state, the count for either type of timer is forced to the reset
value and the timer’s status flag held false whenever the timer’s reset rung is true.
Table 9-9 for On-Delay and Table 9-10 for Off-Delay timers show the cause and effect relation-
ships among Reset coil state, timer rung state, accumulated tick count, and reset/preset values.
This section has two figures (for the On-Delay and the Off-Delay timers) that show the counting
action with various changes in timer rung state.

Table 9-9. RTO Truth Table

On-Delay Status Overflow

Reset Rung Timer Rung Accumulator Flag Timer Flag
(RST Coil) (RTO Coil) Register (_S Coil) Advance (_O Coil)
True* Don’t care = Reset Value* False* No False*
False True* > Reset Value False Yes* False
False False* > Reset Value False No* False
False True* > Reset Value False Yes* False
False True = Preset Value* True* Yes False
False True > 6,553.5* True Yes True*

* Note that in each row, the emphasized entry initiates change in other asterisked entries in the same
row.

111
B0193AW – Rev R 9. Ladder Logic Concepts

CIN_15 TC01_S
(RTO)

Normally
open input
contact (CIN_15)

Gated “Ticks”

Time < Preset Time >= Preset

Timer Status

Time >=
Timer Overflow 65535
(TC01_O) (6,553.5 S)

RST Coil
(TC01_S)

Figure 9-10. Retentive Time-On Delay Timing Chart

Table 9-10. RTF Truth Table

Reset Rung Off-Delay Timer Accumulator Status Flag Timer Overflow Flag
(RST Coil) Rung (RTF Coil) Register (_S Coil) Advance (_O Coil)
True* don’t care = Reset Value* False* No False*
False True* = Reset Value True* No False
False False* > Reset Value True Yes* False
False True* > Reset Value True No* False
False False = Preset Value* False* Yes False
False False > 6,553.5* False Yes True*

* Note that in each row, the emphasized entry initiates change in other asterisked entries in the same
row.

112
9. Ladder Logic Concepts B0193AW – Rev R

CIN_15 TC01_S
(RTF)

Normally
open input
contact (CIN_15)

Gated “Ticks”

Time < Preset Time >= Preset

Timer Status

Time >=
Timer Overflow 65535
(TC01) (6,553.5 S)

RST Coil
(TC01_S)

Figure 9-11. Retentive Time-Off Delay Timing Chart

The coil symbol that you insert in the ladder determines whether a specific structure is treated as
a counter or a timer. You complete the definition by associating a technical identifier with the coil
symbol. To use a timer or counter to control a rung, you insert a contact symbol in the rung and
assign it the timer or counter identifier, together with an “_S” for the status flag or “_O” for the
overflow flag. To control the reset of a counter or timer, you build a rung that outputs to a Reset
coil that you give the same technical identifier as that of the counter or timer.
Counting, timing, and reset operations, including related changes in the status and overflow coils,
are performed when the corresponding symbols are encountered during ladder solution.
The tick interval is 0.1 seconds. This clock tick is a global Fieldbus Module function that is not
synchronized with ladder scans in any way. This means that turning a timer on and off rapidly to
accumulate short times may produce unpredictable results.

Non-Retentive Timers
The non-retentive on-delay timer (TON) is identical in operation to the RTO coil, except that
any period of false rung state is treated as if a Reset (RST) has occurred, that is, timing accumula-
tion does not bridge false-rung periods. Similarly, non-retentive off-delay timers (TOF) treat peri-
ods of true rung state as if a Reset had occurred.

Timer/Counter Reset (RST)

The timer/counter Reset instruction loads the configured reset value into a counter’s or timer’s
accumulator and resets the status and overflow flags. When configured, the timer/counter Reset
coil is given the same reference (technical identifier) as the timer or up/down counter coil it is to
reset. The referenced counter/timer is prevented from counting or timing as long as the reset rung
is true.
To ensure predictable operation, you should configure a reset value that is less than the preset
value, except for CTD coils.

113
B0193AW – Rev R 9. Ladder Logic Concepts

! WARNING
Without a Reset (RST) instruction the counter’s accumulator starts at a zero value.
For the down counter, this means the first count rolls the counter over to 65,535
and sets the overflow flag. You should always configure a Reset for twice the counter
structures you plan to use.

Connector Symbols
There are two types of symbols providing only power flow: horizontal connectors and vertical
connectors.
Horizontal connector symbols provide power flow through symbol positions where no symbol is
configured.
Two different connector symbols are needed to connect two ladder rows in the form of a branch.
A down vertical connector must be attached to the upper ladder row. An up vertical connector is
inserted as the final element of the row beneath it. The vertical connectors must meet one another
to form a single vertical line. The connectors are inserted equidistant between two symbol’s
positions.

Blank Positions
A blank in a symbol position interrupts rung power flow.

Program Flow Control

The program flow control instructions – Master Control Relay and Zone Control Logic – provide
a means of conditionally skipping execution of one or more ladder logic rungs within a ladder
logic diagram. These instructions come in pairs. The first one has a conditional input which
defines whether a zone of ladder rungs is to be processed. The second one (no conditional input)
is inserted to mark the end of the conditional group of rungs.
Each of these instructions when false causes a zone of ladder logic to be skipped. However, the
effect on outputs, counters, and timers differs according to the instruction used. The following
Table 9-11 summarizes the effects that Master Control Relay and Zone Control Logic have on the
operation of ladder logic.

Table 9-11. Effects of MCR and ZCL on Ladder Operation

Effect When Effect When

Ladder Element MCR False ZCL False
Non retentive outputs Set false Do not change
Retentive outputs Do not change Do not change
Counters Do not count transitions Still count transitions
Counter/timer registers Do not change Status and overflow reflect
and flags Counter/Timer changes

114
9. Ladder Logic Concepts B0193AW – Rev R

NOTE
1. MCR is Master Control Relay; ZCL is Zone Control Logic.
2. MCR transitions do not cause counters to count.
3. MCR can affect ZCL rungs.
4. When MCR is false, the only coil that can be written true is MCR itself.

Master Control Relay (MCR, NCR)

You can use Master Control (MCR) and End of Master Control (NCR) coils to divide a ladder
diagram into several master control zones. An MCR coil marks the beginning of the zone and an
NCR coil marks the end.
MCR is a coil that is referenced by all output operations as they are encountered during the ladder
solution. MCR is set true at the top of each scan. At any point in the ladder, MCR can be written
in the same way as any other coil.
Ordinary contacts determine whether to set the MCR coil value true when the first rung in the
MCR zone is processed. The state of the MCR coil has the following effects:
♦ MCR true – The rungs situated between the MCR coil and the End Master Control
Relay (NCR) coil are executed normally.
♦ MCR false – The rungs situated between the MCR coil and the NCR coil are not exe-
cuted. The following additional effects take place:
♦ The states of non-retentive outputs within the zone are set false. Retentive outputs
within the zone are not affected.
♦ Counters do not count transitions.
♦ MCR transitions do not cause counters to count.
♦ Counter/timer registers and flags are not affected.
♦ The only coil that can be written true is MCR itself.
♦ A ZCL zone nested in a MCR is affected by the MCR as follows: if both zones are
off, the ZCL will not turn on until the MCR is true.
The ladder logic implementation allows nested and overlapping ZCLs and MCRs in any
combination.
MCR does not affect rungs inside a zone that is bypassed.

Zone Control Logic (ZCL, NCL)

You can use Zone Control (ZCL) and End of Zone Control (NCL) coils to divide a ladder dia-
gram into several zones. A ZCL coil marks the beginning of the zone and an NCL coil marks the
end.
Ordinary contacts determine whether to set the ZCL coil value true when the first rung in the
ZCL zone is processed. The state of the ZCL coil has the following effects:
♦ ZCL true – the rungs situated between the ZCL coil and the NCL coil are executed
normally.
♦ ZCL false – the rungs situated between the ZCL coil and the NCL coil are skipped
(not executed) and rung outputs within the zone do not change state.

115
B0193AW – Rev R 9. Ladder Logic Concepts

If the state of a timer rung is such that the timer is ticking, if the zone transitions to false, the tim-
ers cease operation.
The ladder logic implementation allows nested and overlapping ZCLs and MCRs in any
combination.

Special Purpose Coils

The special purpose instructions include the following coils:
♦ Initialization
♦ Communication Failure
♦ Power fail
♦ Fail safe.

Initialization (INIT)
NOTE
The INIT coil is global within the same FBM; that is, if there are multiple ladders
resident in a given FBM, activating the INIT coil in any one of those ladders initial-
izes all the ladders in the FBM.

The Initialization (INIT) coil has two functions:

1. When your program writes the INIT coil true, INIT forces the next scan to be an ini-
tialization cycle. This forces a reset of all timers, counters, and coils at the start of the
next scan. The INIT coil remains true for one scan.
2. Following cold start or receipt of an initialize command, INIT is true for one scan.
You can reference INIT to initialize certain coils prior to beginning operation.

Communication Failure (COMMF)

Communications software sets Communication Failure (COMMF) false during exchanges with
the control processor as long as the communications timer has not timed out. If communications
fail, COMMF is set true and remains true until communications are restored.
COMMF does not indicate the type of messages received, control processor state, or whether
replies actually reach the control processor.
Use the COMMF contact to have your ladder respond to a communication failure between the
FBM and the control processor. For instance, the rung diagrammed below will cause the ladder to
fall back to the fail-safe mode. (In addition all other ladders in the FBM will go to fail-safe – see
Note under Fail-safe.)

COMMF FAILSF
( )

Figure 9-12. COMMF Contact

116
9. Ladder Logic Concepts B0193AW – Rev R

Power Fail (POWERF)

The Power Fail (POWERF) coil is false as long as the execution of the Fieldbus Module ladder
application is uninterrupted.
POWERF is set true following a warm start caused by either of the following conditions:
♦ Recovery from a power interruption.
♦ A command to the Fieldbus Module to go offline and back to online.
POWERF is true for exactly one scan following recovery, and then becomes false. You cannot set
or reset POWERF. If failure occurs in the middle of the processing of a rung, recovery starts at the
beginning of the ladder with POWERF true, and all input and output values are as they were at
the end of the last complete scan before the failure.

Fail-safe (FAILSF)
NOTE
The FAILSF coil is global within the same FBM; that is, if there are multiple lad-
ders resident in a given FBM, activating the FAILSF coil in any one of those ladders
puts all the ladders in the FBM into the configured fail-safe mode.

Writing the Fail-safe (FAILSF) coil true forces physical outputs to the preconfigured fail-safe state.
It does not affect values in the coil table. During the output exchange portion of the scan cycle,
the value of the output coil is checked and the physical outputs are handled based on the values of
the fail-safe, connect, and hold flags. Writing the FAILSF coil true will not override a control pro-
cessor specification of disconnect-hold.

Fanned Outputs
Fanned outputs are supported when implemented as a single vertical column branching down
from the first line of the rung, immediately after the seventh element position. See Figure 9-13.

CIN_1 IFL_5 CIN_3 IFL_1 CIN_9 CIN_10 CIN_2 CO_1

/ ( )
AUTO FILL TANK2 TANK3 INTLK MOTOR OVER PUMP
TEMP

CIN_16 CO_1 CIN_11 CIN_12 IFL_2

CO_5
/
( )
FULL PUMP FAN VALVE4 INTLK2
HEATER

CO_7

( )
AGITAT

Figure 9-13. Fanned Outputs

117
B0193AW – Rev R 9. Ladder Logic Concepts

Simple and Nested ZCLs

Figure 9-14 through Figure 9-16 illustrate the use of simple Zone Control Logic, and Figure 9-17
through Figure 9-18 show the inclusion of a nested “Fast” zone within the “Manual” zone.

START “MANUAL” ZONE

RUNGS INCLUDED
IN “MANUAL” LOGIC
(executed only if
“MANUAL” is true)

END “MANUAL” ZONE

START “AUTO” ZONE

RUNGS INCLUDED
IN “AUTO” LOGIC
(executed only if
“MANUAL” is false)

END “AUTO” ZONE

Figure 9-14. Zone Control Logic

CIN_1
( ZCL )

SET
MANUAL

START “MANUAL” ZONE

IFL_3 IFL_2 CO_7

( )
STOP START AGITATE

( NCL )

END “MANUAL” ZONE

Figure 9-15. Zone Control Logic (Continued)

118
9. Ladder Logic Concepts B0193AW – Rev R

CIN_1
( ZCL )
SET
MANUAL

START “AUTO” ZONE

IFL_5 CO_1
( )
FILL PUMP

( NCL )

END “AUTO” ZONE

Figure 9-16. Zone Control Logic (Continued)

SET STATUS OF “MANUAL” ZONE CONTROL COIL

START “MANUAL” ZONE

RUNGS INCLUDED
IN “MANUAL” LOGIC
(executed if
“MANUAL” is true)

Set status of “FAST” zone control coil

START “FAST” ZONE

RUNGS INCLUDED
IN “FAST” LOGIC
(executed only if
“FAST” is true)
END “FAST” ZONE
END “MANUAL” ZONE

Figure 9-17. Nested Zone Control Logic

119
B0193AW – Rev R 9. Ladder Logic Concepts

CIN_1
( ZCL )

MANUAL
OP

START “MANUAL” ZONE

IFL_3 IFL_2
CO_7
( )
STOP START AGITATE

[Additional rungs in “MANUAL” zone]

CIN_8
( ZCL )

FST/SLO
START “FAST” ZONE

IFL_3 IFL_2 CIN_1

CO_6
( )
STOP START MANUAL SHUNT
OP

[Additional rungs in “FAST” zone within “MANUAL” zone]

( NCL )

END “FAST” ZONE

( NCL )
END “MANUAL” ZONE

Figure 9-18. Nested Zone Logic (Continued)

Ladder Diagram Constraints

The object code produced by ladder logic compilation is executable only in a Fieldbus Module
and cannot exceed 1K of FBM memory. The ladder logic editing process supports a maximum of
32 contact inputs, 16 contact outputs, and 16 timers/counters for a single Fieldbus Module.
The ladder logic compiler imposes the following restrictions in the composition of a ladder
diagram:
♦ All elements having the same technical identifier (one coil and multiple contacts) have
the same user label.
♦ A maximum of eight logic symbols (not including branches) can be inserted within a
ladder row.
♦ Output symbols may appear only as the final element within a row.
♦ Fanned outputs must be arranged in a vertical column.

120
9. Ladder Logic Concepts B0193AW – Rev R

♦ MCR and ZCL symbols may not be included in an output fan.

♦ A rung that contains an NCL symbol (end of ZCL) may not include any other sym-
bols. Similarly for NCR symbols.
♦ There must be an equal number of ZCL and NCL symbols within a ladder diagram.
♦ The following geometry is not allowed:

♦ The following geometry is allowed only in the first line of a rung. This constraint dis-
allows nested branches, which are not supported in ladder diagrams:

♦ Use no more than two vertical connectors to link a row of adjoining symbols to a pre-
ceding ladder line.

( ) [Ladder line n]

Allowed

[Ladder line n+1]

( ) [Ladder line n]

Not Allowed

[Ladder line n+1]

Figure 9-19. Allowed/Not Allowed Connector Geometry

The following considerations relate to the use of overlapping technical identifiers in different seg-
ments of the same composite ladder.
A given technical identifier (for example, OFL_1) may be entered in more than one ladder seg-
ment, but doing so does not create additional OFLs. There is only one OFL_1, with a single data
value, in the FBM. It may be entered as an output coil in multiple segments of the ladder, in
which case the final concatenated ladder will have more than one rung ending with symbol
OFL_1. When the OFL_1 value is transmitted to the control processor, its value will depend on
the evaluation of the highest-numbered rung ending in OFL_1, that is, the last calculation of
OFL_1 during the ladder scan. All PLBs connected to that FBM will receive this value of OFL_1
as an input. This implies that if the usage of technical identifiers is overlapped, a PLB block could
receive values of parameters from the FBM different from the ones expected on the basis of their
own ladder segments. The same considerations apply to overlapped usage of COs, TCs, and IFLs.
If any IFL is referenced in multiple segments of a composite ladder, the value sent down to the
FBM for use in solving the ladder will be the value of that IFL parameter in the PLB which is pro-
cessed last. This will depend on the zones, and positions within the zones, of the various PLBs
involved, as shown on the Block/ECB Functions screen of the Integrated Control Configurator.

121
B0193AW – Rev R 9. Ladder Logic Concepts

Programmable Logic Block Operation

The programmable logic block (PLB), shown in the PLB Block Diagram, supports ladder logic
executing in a digital Fieldbus Module. The block executes at the interval you specify (one of 13
user-specified scan intervals from 50 ms to 1 hr; default of 500 ms). At the configured interval,
the PLB reads each physical I/O channel and each ladder logic external output flag reference from
the Fieldbus Module and updates the appropriate block parameter values. The block processor
writes each external input parameter value to the appropriate ladder logic external input flag refer-
ence in the Fieldbus Module. Refer to Integrated Control Block Descriptions (B0193AX) for
detailed information on block parameters.

Manual/Auto

Device ID

TO/FROM
TO/FROM OFL_1 through OFL_32 PROGRAMMABLE OFL_1 through OFL_32 OTHER
FIELDBUS CONTROL
BLOCKS
MODULE LOGIC
IFL_1 through IFL_32 IFL_1 through IFL_32

CIN_1 through CIN_32 CIN_1 through CIN_32

BLOCK
CO_1 through CO_32 CO_1 through CO_32
(PLB)
Fieldbus Module Status
Block Status
Ladder Logic Status (BAD Parameter)

Figure 9-20. Programmable Logic Block (PLB) Block Diagram

As part of normal Fieldbus data input processing, all inputs and outputs are written to and read
from the Fieldbus Module in one transaction:
♦ The Interface block writes the current External Input Flags to the Fieldbus Module.
These are signals from other blocks to initiate or modify ladder logic actions.
♦ The Fieldbus Module returns its latest scanned data for:
♦ Fieldbus Module status
♦ External Output Flags. These are signals to other blocks of the results of ladder
logic actions.
The Fieldbus Module ladder logic now executes the new External Input Flags.
The PLB has an Auto/Manual mode that determines control of block output parameters. Opera-
tionally, MA lets you switch control of block flag outputs and physical outputs from the ladder
program (Auto) to the user (Manual).
In Auto, the block secures its own output parameters and updates them according to ladder logic
and Fieldbus Module inputs.
The block reads the ladder logic external output flag references from the Fieldbus Module and
updates the appropriate output parameters with these values. The block writes input parameter
values to the appropriate ladder logic external input flag references of the Fieldbus Module.

122
9. Ladder Logic Concepts B0193AW – Rev R

The input parameter values are written to the specified ladder logic input flag registers. If either
the Fieldbus Module is not operational or the ladder program is off-line, the inputs are not writ-
ten and the outputs are not updated. The BAD parameter is updated and the BAD status of all
output flag records are set.
When the block is placed into Manual, the external output flag parameters from the ladder pro-
gram are updated by the block. The input flag parameters continue to be written to the external
input flags in the ladder program.
The Manual mode allows you to disconnect outputs from the Fieldbus Module ladder logic for
checkout or simulation from an external source. In Manual, the block unsecures its Boolean type
outputs. Any task or process is then allowed to use Set calls to write to the outputs.
Ladder segments in different Fieldbus Modules can communicate with each other through the
PLB input and output flag parameters. An external output flag from a ladder program in one
Fieldbus Module can be connected to an external input flag of a ladder program in another Field-
bus Module through the respective block’s output and input flag parameters. Switching the MA
state of the upstream block to manual would allow for the independent and isolated operation of
each flag under user control.
The physical inputs at the Fieldbus Module can be read by a CIN block. The physical outputs at
the Fieldbus Module can be read by a COUT block. Both physical inputs and physical outputs
are read by the PLB.
In Manual, the block writes ladder logic external output flags. The block supports Manual/Auto
mode for manually updating block outputs. Manual does not affect the operation of the input
parameters or external input flags. In the manual mode, the updating of the output parameters is
halted and control of the output parameters by workstations, other blocks, displays, and processes
(programs) is possible.
Various software subsystems access internal information to edit a ladder diagram, display rung
power flow, read and write timer/counter values, and control the modes of ladder logic operation.
Displays that you configure can access ladder logic through external flag parameters in PLBs.

Ladder Logic Operation

The ladder logic functions in the Fieldbus Module can be divided into two modes: foreground
and background. Communications and other interrupts are handled in the foreground. The cyclic
control function defined by the ladder program is handled in the background. The foreground
and background communicate through shared buffers. The background, when it needs to access
the shared buffers, locks out the foreground by shutting off interrupts for periods of up to 1 ms
(refer to Figure 9-21).

123
B0193AW – Rev R 9. Ladder Logic Concepts

To/from
Channel, Control, SHARED Process
and Security BUFFERS
Commands BACKGROUND
Communications;
Other interrupts
Ladder program

Coil, Register,
FIELDBUS MODULE
and Status Data

LADDER LOGIC CONTROL COMPOUND/BLOCK

PROCESSING BLOCKS PROCESSING
SOFTWARE SOFTWARE

DISPLAY
SOFTWARE CONTROL PROCESSOR

Figure 9-21. Ladder Logic Functions Diagram

Ladder Logic Scan Cycle

The Fieldbus Module ladder logic processor operates in a cycle referred to as a scan. Each scan
requires the following four phases:
1. Processing commands from the control processor.
2. Reading inputs from physical and logical channels.
3. Solving the ladder.
4. Writing outputs to physical and logical channels.
These phases form an infinite loop. Once placed in run, the program repeats until halted. One
pass through the loop (one scan) typically takes from 10 to 30 ms. The actual scan time depends
on the complexity of the ladder program and the state of the logic.

Scan Phase 1 – Command Processing

Table 9-12 lists the commands that the control processor uses to direct ladder logic in the Field-
bus Module.
The control processor exchanges blocks of data with the Fieldbus Module. In Scan Phase 1, the
Fieldbus Module checks for the receipt of any commands that require mode changes. Executing
mode changes first avoids the inconsistency between blocks of data that would result from execut-
ing only a portion of the user program.

Table 9-12. Ladder Logic Commands

Command Description
1. Read Channel Data Read both the state of the physical I/O and the logical outputs
of the ladder.
2. Write Channel Data Write the external input flag values used by the ladder logic
processor.

124
9. Ladder Logic Concepts B0193AW – Rev R

Table 9-12. Ladder Logic Commands (Continued)

Command Description
3. Object Code Download Download object code to the program code space that is not in
use.
4. Switch Program Switch the logic processor to the program code space that is
not in use.
5. Write Ladder Logic Status Determine the ladder logic operating mode.
6. Read Coil Table Data Read the Boolean state of all 255 coils to support displays. This
command also updates the register values read by the read
register data command.
7. Read Register Values Read the preset, reset, and accumulator register values to
support displays. The values supplied are those saved at the
time of the most recent read coil table request.
8. Write Register Values Change the values of the timer/counter preset and reset
registers to support displays.
9. Write Force On List Write the Fieldbus Module force-on list when the logic
processor is in test mode. All force lists are optionally erased
on exit from test mode.
10. Write Force Off List Write the Fieldbus Module force-off list when the ladder
processor is in test mode. All force lists are optionally erased
on exit from test mode.

Scan Phase 2 – Inputs

The inputs to the ladder logic come from two sources:
1. Physical inputs come from the process through channels provided by the Fieldbus
Module hardware.
2. Logical inputs come from control blocks and tasks through Ladder Logic Interface
blocks (PLB Blocks) in the control processor.
During the input phase of the scan cycle, the values associated with each input are transcribed
into fixed locations in the ladder logic coil memory.

Scan Phase 3 – Ladder Solution

The end of the input phase transfers control to rung evaluation software to execute the ladder pro-
gram. Execution starts at the beginning of the object code array and proceeds until the end of the
program is reached. The rung evaluation alters only local variables and has no effect on any phys-
ical I/O processes.

Scan Phase 4 – Outputs

Scan Phase 4, outputs, is the mirror image of the input phase. The outputs from the ladder logic
are handled two ways:
1. Physical outputs go to channels provided by Fieldbus Module hardware.
2. Logical outputs are provided to Ladder Logic Interface blocks (PLB Blocks) in the
control processor through the external flag buffer.

125
B0193AW – Rev R 9. Ladder Logic Concepts

The values in coil memory are always transcribed to the corresponding Fieldbus Module external
flag buffer. External flag outputs await the control processor’s next communications request.
The ladder logic sets physical outputs as specified under one of the following situations:
1. I/O connected and fail-safe false: The values in coil memory are transcribed to the
corresponding physical Fieldbus Module outputs.
2. Fail-safe true: The physical outputs are set to the preconfigured values specified by the
configuration table.
3. I/O not connected: The physical outputs are set as specified by the fail-safe and hold
flags.
During the output phase, the buffers that hold the data blocks for display support are also
updated. This buffering allows the foreground to handle all the normal communications messages
asynchronously with ladder evaluation.

Ladder Logic Modes of Operation

In conjunction with the Test and Install modes of the ladder logic configuration/operation soft-
ware, the control processor sends commands to the Fieldbus Module to establish ladder modes of
operation. In Test mode, you can operate the ladder program with I/O connected or disconnected
in continuous (Run) or Single Scan cycling. When you disconnect I/O, you can choose either the
hold or the fail-safe option for outputs. These choices are summarized as follows:

Table 9-13. Ladder Modes of Operation

I/O Connected I/O Disconnected

Run Run/Hold
Run/Fail-Safe
Single Scan Single Scan/Hold
Single Scan/Fail-Safe

Ladder Logic Status Byte

When the Fieldbus Module is on-line, the logic status byte controls and reports the ladder modes
of operation. The effect and meaning of the flags in the status byte are defined individually in the
pages that follow. With the exception of the Hold flag, the functions controlled by these flags are
independent.

Logic Status Byte Flags

1. Run
2. Test
3. Connect
4. FailSafe
5. Hold
6. Single Scan
7. INIT
8. Logic Machine Error

126
9. Ladder Logic Concepts B0193AW – Rev R

Run Flag
The Run flag defines whether the logic solving portion of the scan cycle is running.

Run Flag Set To One Run Flag Set To Zero

Ladder program executes. Ladder program does not execute.

The I/O exchange portions of the scan cycle always occur. The Connect, Hold, and Fail-safe flags
determine behavior of the outputs as defined in the following sections.

Test Flag
The ladder logic configuration/operation software in the control processor controls the Test flag.

Test Flag Set To One – The ladder logic performs the following functions:
Accepts and processes force lists.
Writes to timer/counter accumulator registers.

The added processing required to support force lists causes the cycle time performance of the lad-
der logic to be degraded when the Test flag is set to one.

Connect Flag
The state of the Connect flag determines whether the physical I/O is controlled by the ladder
logic.

Connect Flag Set To One Connect Flag Set To Zero

Outputs are connected to the Cycling the ladder logic has no effect on the
ladder logic. physical outputs.

In the Test mode of the ladder logic configuration/operation software in the control processor,
you select an operating mode that includes setting the state of the Connect flag to one.

Fail-safe Flag
When the Fail-safe flag is set to one, the physical outputs are driven to the state determined by the
Fieldbus Module configuration table (established through the Integrated Control Configurator).
Control of the Fail-safe flag depends upon the status of the Connect flag as follows:

Connect Flag Set To One Connect Flag Set To Zero

The fail-safe coil in the ladder controls The ladder logic configuration/operation software
the Fail-safe flag. in the control processor controls the Fail-safe flag.

The Fail-safe flag has priority over the Hold flag. If both are set to one, the result is fail-safe status.
Fail-safe status is also the default, should the control processor ever set the Connect flag to zero
without setting either Fail-safe or Hold to one.

127
B0193AW – Rev R 9. Ladder Logic Concepts

Hold Flag
The Hold flag is recognized only if the Connect flag is set to zero. When the Hold flag is set to
one, the physical outputs are held at the state that was in effect at the time the flag was set to one.

Hold Flag Set To One Hold Flag Set To Zero

The physical outputs are held at the state in The physical outputs are either in fail-safe
effect at the time the flag is set to one. or are connected.

Single Scan Flag

The Single Scan flag is recognized only if the Run flag is not set to one. Other combinations are as
follows:

Single Scan Flag Set To One and Run Single Scan Flag Set To Zero and Run
Flag Set To One Flag Set To One
The Single Scan flag initiates a single scan. The ladder processor cycles continuously.
The scan sets the flag to zero.

INIT Flag
If you choose to install the ladder in run mode and initialize on start up, the control processor sets
the INIT flag in the ladder status byte. The ladder program performs a cold start initialization of
the ladder prior to executing the first scan. All coils are reset, the INIT coil is set, and all
timer/counters are reset.
The ladder logic also sets the INIT flag any time a cold program start is requested by other soft-
ware in the control processor or the INIT coil is set by the internal logic. INIT is set to zero auto-
matically at the end of the first scan following initialization.

Logic Machine Error Flag

The Logic Machine Error flag is set if the ladder logic is ordered to switch to a code buffer that
fails the checksum test. The ladder logic also sets fail-safe and halt status.
The only recovery from a logic machine error condition is to load a valid object program and
switch to it. This will set the error flag to zero. You can then set the status as desired.
An additional FBM ladder operational mode exists, based on the configurable simulation option
SIMOPT, which is an ECB8 parameter. When downloaded to the FBM, SIMOPT causes the
ladder logic to disregard the physical contact inputs to the FBM in favor of the values specified by
the configurable and settable packed long parameter SIMCIN. SIMCIN is also an ECB8
parameter.

PLB Editor Overview

The ladder logic domain of the configurator allows you to:
♦ Create or modify one ladder diagram segment
♦ Check for syntax errors in existing ladder diagram source code
♦ Print a copy of the ladder diagram segment being edited.

128
9. Ladder Logic Concepts B0193AW – Rev R

You can configure ladder logic from any system display station equipped with a keyboard and
pointer device. In the Edit mode of operation, you can insert, delete, and move symbols in the
diagram.
As you construct a ladder diagram, the PLB editor builds a source file representing the desired
logic. The editing screen displays the ladder corresponding to the PLB name. An “empty” ladder
file causes a display of the ladder name only.
Editing consists of placing logic symbols that represent contacts, relays, timers, and counters
within the rungs of the ladder. If you elect to save the edited version, the original ladder is
replaced by the new. You can check your ladder for syntax errors at any point in your editing.

Configuration Example
When configuring PLBs for different segments of a single ladder diagram, avoid assigning an
external input flag to more than one block. If two PLBs were to update the same input flag, the
flag value received from the first block would be overwritten when the other block was processed.
The five-part diagram accompanying the configuration example shows part of a control strategy
to pump a fluid from either of two tanks. The first part shows the process, the next two show the
control blocks, the fourth shows the I/O table and flag table connections to the PLBs, and the
fifth shows a portion of the ladder diagram.
The example is not a practical application. It is intended only to show concepts associated with
segments, while limiting each segment to one rung for simplicity. Arbitrarily, some of the control
is implemented through external I/O flags and some through physical I/O channels to demon-
strate the two methods of communicating with ladder logic.
In the example, an operator presses one of two switches to select a tank to supply fluid. If the
tank’s low level switch is not closed, the ladder logic output to an On/Off Valve controller (VLV)
block opens the tank’s drain valve. Ladder logic causes the pump to run if either tank valve is
open.
Physical contact inputs are available to the ladder from input channels of the Fieldbus Module.
Contact inputs from the operator panel and from valve limit switches activate one of the module’s
physical output channels to operate a motor control relay in the process. To demonstrate another
input path, one input is routed through an MCIN block to the PLB as an external input flag to
the ladder. To demonstrate other output paths, the PLBs transfer external output flags from the
ladder to VLV blocks and a COUT block.

129
B0193AW – Rev R 9. Ladder Logic Concepts

P1 control
V2 control

V1 control

V1 position
P1
Pump

V2 position

T2 empty

T1 empty Maint Disable

Drain T2
T1 T2 Panel
Tank Switch Tank Oper Drain T1
Switch
Low Level Low Level

Figure 9-22. Typical Ladder Logic Application

T1 Empty CIN_1
Fieldbus
T1 PLB OFL_1
Drain T1 Module VLV
CIN_2 (Segment 1) To V1
BLOCK

T2 Empty CIN_3
Physical T2 PLB OFL_2
Input VLV To V2
Drain T2 (Segment 2)
CIN_4 BLOCK
Channels
1–4

CIN_1
OFL_1 OFL_2
::
CIN_4 LADDER
DIAGRAM
(Segments 1, 2)

Figure 9-23. Typical Ladder Logic Application (Continued)

130
9. Ladder Logic Concepts B0193AW – Rev R

To pump
FIELDBUS P1
MODULE
V1 Posit FIELDBUS
MODULE
Physical
V2 Posit MOTOR
Output
IFL_1 Channels CONTROL
Physical ALL PLB
RELAY
Maint Input (Segment 3)
CIN_7 OFL_3
Disable Sw Channels MCIN COUT
5–7 BLK BLK
IFL_1
CIN_5
:: LADDER PUMP ON
CIN_6 DIAGRAM LAMP
(Segment 3)

Figure 9-24. Typical Ladder Logic Application (Continued)

CIN_1 PMPCTRL:T1 OFL_1 CIN_3 PMPCTRL:T2 OFL_2 PMPCTRL:ALL OFL_32

CIN_2 CIN_4 CO_1 IFL_1

: : : :
CIN_5 PLB CIN_6 PLB PLB

(Tank 2 Logic) (Common

Logic)

(Tank 1 Logic)

Contact Input Output Contact

1 2 . . 32 Input 1 . . . 32 Flag Flag 1 2 . . 32 Output 1 . . . 32
Table Table Table Table

Figure 9-25. Typical Ladder Logic Application (Continued)

131
B0193AW – Rev R 9. Ladder Logic Concepts

CIN_1 CIN_2 OFL_1

[Tank 1] Drain Tank_1 Open

Tank_1 Empty Valve1

CIN_3 CIN_4 OFL_2

[Tank 2] Drain Tank_2 Open

Tank_2 Empty Valve2

OFL_1 CIN_5 IFL_1 CO_1

[Common]
Run
Pump
OFL_2 CIN_6
OFL_32
Open Valve2
Valve2 Open Pump On

Figure 9-26. Typical Ladder Logic Application (Continued)

132
10. Sequence Logic
This chapter covers sequence logic control: sequential control block types and their various
states, sequence processing, and SBX programming.
Sequence logic control complements continuous and ladder logic control with regulatory feed-
back applications at the equipment control level. For example, the sequential control software can
be used to supervise a sequence of activities such as filling a tank, blending its contents, and drain-
ing the tank.
Whereas most continuous control blocks have fixed algorithms, sequence control blocks have
user-defined algorithms. Sequential control software enables you to:
♦ Define a sequence of events
♦ Monitor process conditions, taking corrective action when required
♦ Time events
♦ Manipulate any compound or block parameter or any shared variable
♦ Output messages to any logical device or to the historian.
To introduce sequential control to a control strategy, you must define sequential control blocks
and add them to compounds.
Sequential control blocks are configured through the Integrated Control Configurator just as con-
tinuous blocks are, except that in addition to configuring parameters, you must define sequence
logic for the block. The Configurator offers a series of menu functions that support creating
sequence logic.
Sequence logic is created with the Sequence Language, a subset of the High Level Batch Language
(HLBL). The Sequence Language is a high level programming language resembling Pascal, but
specifically geared toward creating process control strategies. Configuring sequential control
blocks is described in Integrated Control Configurator (B0193AV).

Sequential Control Blocks

Sequential control is performed at the compound level through sequential control blocks of the
following types:
♦ Sequence (IND, DEP, and EXC)
♦ Monitor (MON)
♦ Timer (TIM).

Sequence Block
There are three Sequence block types:
♦ Independent (IND)
♦ Dependent (DEP)
♦ Exception (EXC).

133
B0193AW – Rev R 10. Sequence Logic

IND and EXC blocks run independently of other Sequence blocks in the same compound. DEP
blocks pause when an EXC block in the same compound is active.
This relationship between DEP and EXC blocks allows you to separate a sequence algorithm for
handling normal conditions from a sequence algorithm for handling alarm conditions. For exam-
ple, if a Monitor (MON) block detects an alarm condition and activates an EXC block to take
corrective action, the DEP block pauses until the corrective action is complete. When the EXC
block is done, the DEP block can finish executing its sequence algorithm.
A Sequence block contains a user-defined sequence algorithm. You can use a Sequence block to:
♦ Manipulate parameters and shared variables.
See the table “Sequence Compiler Limits” in Integrated Control Configurator
(B0193AV), for the maximum number of external references in each subroutine or in
the main code and all SBXs.
♦ Change the flow of execution based on the state of parameters and shared variables.
♦ Activate other Sequence and Monitor blocks.
♦ Measure time.
♦ Report to the Historian.
♦ Send information to logical devices, such as printers.
See the table “Sequence Compiler Limits” in Integrated Control Configurator
(B0193AV) for message related limits.
♦ Call a subroutine and pass arguments, if any.
♦ Make calculations.
♦ Simulate a process for testing purposes.
A Sequence block is composed of:
♦ Standard Parameters
♦ Block Type Identification
♦ Symbolic Constants
♦ Local Block Variables.
See the table “Sequence Compiler Limits” in Integrated Control Configurator
(B0193AV) for local variable related limits.
♦ User Labels
♦ Include Files
♦ Subroutines (variables and statements)
♦ Standard Block Exception Handlers
♦ Block Statements, grouped into Steps.
Each statement, whether in the block’s main section, in its subroutines, or in its stan-
dard block exception handlers, may optionally have a label.
See the table “Sequence Compiler Limits” in Integrated Control Configurator
(B0193AV) for labels related limits.
Standard parameters show block operation details and allow you to control block operation and
connect the block in a control strategy that includes continuous blocks, ladder logic blocks, and
other sequence blocks.

134
10. Sequence Logic B0193AW – Rev R

Block Type identification is a small block of information at the start of the sequence language file
where you provide data such as block name, type, creator, revision level and date.
Symbolic constants are identifiers which represent constant values. They are used to indicate or
illustrate the meaning of such values. The constants are an aid in compiling sequence blocks.
Changing the value of a constant in an include file does not affect currently running or already
compiled sequence blocks automatically. After such a change, the blocks containing source code
in which the constants are used have to be recompiled to effect the change.
Block variables are local and are not accessible from outside the block. You define their number
and their size. There are no user labels for local block variables. Refer to them by their declared
names. You can use them in any HLBL expression and you can assign them to each other, to user
(array) parameters, and to external references.
Local block variables can be any of the following types:
♦ Boolean and boolean array
♦ Long integer and long integer array
♦ Real and real array
♦ String and string array.
For local variables there are three string lengths: short (6 characters), medium (12
characters), or long (80 characters).
All arrays in the local block variables (main section) and the local subroutine variables may be
multi-dimensional, with a maximum of 256 dimensions.
When specifying the types of main section or subroutine local variables, you may use a comma-
separated list of variables before the type specification.
See the table “Sequence Compiler Limits” in Integrated Control Configurator (B0193AV) for the
maximum number of comma-separated arguments before a data type specification.

Example: THIS_VAR, THAT_VAR, OTHER_VAR: R;

STR_VAR1, STR_VAR2, OTHER_STR: S12;
MY_BOOLS, YOUR_BOOLS: B [5];

The type specifications for local block variables are:

B = Boolean
I = Long Integer
R = Real
S = String of 80 Characters
S6 = String of 6 Characters
S12 = String of 12 Characters

User-labeled parameters can be referenced by the Sequence block’s user-defined algorithm. There
are a fixed number of each of the following types: real, long integer, Boolean, and string. All types
except string and the data store arrays can be linked with parameters in other blocks and com-
pounds and shared variables. The strings and data store arrays are settable but not connectable.

135
B0193AW – Rev R 10. Sequence Logic

The standard parameters, all of which may be user-labelled, are:

BI0001 – BI0024: Boolean Inputs

II0001 – II0008: Long Integer Inputs
RI0001 – RI0015: Real Inputs
SN0001 – SN0010: Strings (always up to 80 characters) *
BO0001 – BO0016: Boolean Outputs
IO0001 – IO0005: Long Integer Outputs *
RO0001 – RO0015: Real Outputs *
BA0001[16]: Boolean Array Data Store *
BA0002[16]: Boolean Array Data Store *
BA0003[16]: Boolean Array Data Store *
BA0004[16]: Boolean Array Data Store *
IA0001[16]: Long Integer Array Data Store *
RA0001[16]: Real Array Data Store *
RA0002[16]: Real Array Data Store *

* Not available in the Monitor (MON) block (see page 137).

Standard and user-labeled parameters are described in Integrated Control Block Descriptions
(B0193AX). Configuring parameters is described in Integrated Control Configurator (B0193AV).
An include file can be any set of HLBL statements. Use include files to define specific constructs
such as sophisticated WAIT loops or complicated expressions of a set of parameters, or to define
objects with a global scope such as symbolic constants, subroutines, or standard block exception
handlers. You cannot compile include files separately.
The subroutine allows you to specify a general piece of control logic just once and apply it as often
as required in the block algorithm. A subroutine is a sequence of HLBL user-defined statements
that can be called from the sequence block’s main code or from another subroutine. Subroutines
can use any HLBL statement except for standard block exception handlers.
You can use a user-defined number of arguments to parameterize a subroutine. The data types of
these arguments must be one of the data types supported in HLBL for block parameters and local
variables.
You cannot install a sequence subroutine in a station as an independent entity and you cannot
access it from outside the sequence block in which it is installed.
An Independent, Dependent, or Exception block may have subroutines. Monitor and Timer
blocks do not support subroutines.
See the table “Sequence Compiler Limits” in Integrated Control Configurator (B0193AV) for sub-
routine related limits.
A Standard Block Exception Handler (SBX) is a user-specified section of HLBL statements that
allows the sequence block to react to an operational error during automatic execution or to an
outside interruption during normal block operation.

136
10. Sequence Logic B0193AW – Rev R

There are five events for which SBXs can be specified. Two are error handling SBXs:
♦ User errors (OP_ERR between 2000 and 3000)
♦ System errors (all other errors).
The other three are state change SBXs:
♦ Switch to Inactive
♦ Switch to Manual
♦ Switch to Paused.
Sequence language statements define the sequential control algorithm, as specified by the user.
The Sequence language is described in Integrated Control Configurator (B0193AV).

Monitor Block
A Monitor (MON) block contains up to 16 user-defined Boolean expressions called cases. The
result of the evaluation of a monitor case is stored in the associated boolean output parameter.
When one of the cases evaluates to true, the MON activates a sequence block (EXC, DEP, IND,
or MON). In this way, up to 16 blocks can be activated from the MON block.
A Monitor block is composed of:
♦ Standard Parameters
♦ Blocktype Identification
♦ Symbolic Constants
♦ User Labels
♦ Monitor Cases (up to 16).
User-labeled parameters can be referenced by the Monitor block’s user-defined algorithm. There
are a fixed number of each of the following types: real, long integer, and boolean. All types can be
linked with parameters in other blocks and compounds and shared variables.
Standard and user-labeled parameters are listed and described in Integrated Control Block Descrip-
tions (B0193AX). Configuring parameters is described in Integrated Control Configurator
(B0193AV).
A monitor case consists of a monitor condition and an optional activation request that is per-
formed when the condition is true.
Example:
0001 WHEN level_hi DO :tank_1:hi_level_exc
♦ The case number is 0001.
♦ The condition is “level_hi”, where level_hi is a user labeled parameter.
♦ The request is “DO :tank_1:hi_level_exc”. “hi_level_exc” is the block name for a
sequence block in the compound “tank_1”. This block will be activated when the
condition “WHEN level_hi” is evaluated true.

Timer Block
A Timer (TIM) block keeps track of time while control strategies are executed. It is composed of
standard parameters and four timers. TIM blocks do not contain any Sequence language
statements.
Standard parameters show block operation details and allow you to control block operation.

137
B0193AW – Rev R 10. Sequence Logic

A timer is composed of a real and a Boolean parameter. The Boolean parameter value determines
whether the real parameter is updated or not when the block is processed. When the Boolean
value is true, the real parameter is updated. When the Boolean value is false, the real parameter is
not updated.
The TIM block is processed when the compound in which it resides is On and the block is in
Auto. When a TIM block is processed, timers that have been started are updated every scheduled
Basic Processing Cycle (BPC). Timers are started by an external source, such as a statement in a
Sequence block.
Standard parameters are listed and described in Integrated Control Block Descriptions (B0193AX).
Configuring parameters is described in Integrated Control Configurator (B0193AV).

Sequential Control Block States

Block states describe the operational behavior of a block. All blocks have the Application states
Manual and Auto.
In addition to the Application states, the sequential control blocks have the following Sequence
states: Active, Inactive, Paused, and Tripped. Tripped applies only to the Monitor block. The set
of operational modes for sequential blocks include:

Table 10-1. Operational Modes

Application States Sequence States Transition

Auto Active To_Manual
Semi-Auto (Step Mode) Inactive To_Inactive
Manual Paused To_Paused
Subr-Trace Tripped
SBX-Trace Suspended on SENDCONF

The Sequence states and the Application states control sequential control block algorithm execu-
tion and the operational state of block outputs.

Application States
The Application states, Auto, Semi-Auto, and Manual, control the operational state of a block’s
outputs. In conjunction with the Sequence states, they also control sequential control block algo-
rithm execution.
The Application state is determined by the value of the block’s MA parameter. When MA is true,
the block is in the Auto state. When MA is false, the block is in the Manual state.
Another block parameter, RSTMA, controls the value of the MA parameter when the compound
changes from Off to On. When RSTMA is 0, MA becomes false; when RSTMA is 1, MA
becomes true; when RSTMA is 2, MA does not change upon the compound switch. You set the
value of RSTMA during block configuration using the Integrated Control Configurator.

138
10. Sequence Logic B0193AW – Rev R

Auto State
In the Auto state, a block’s output parameters are secured. This means that the block algorithm is
responsible for updating the output parameters. External sources (other blocks and applications)
cannot write values to block output parameters.
Sequential control block algorithms are processed as follows in the Auto state:
♦ TIM block timers that have been started are updated once every scheduled BPC. A
timer is started with a START_TIMER statement in an IND, DEP, or EXC block.
♦ MON block cases are evaluated each scheduled BPC. If a case trips, it may lead to
activation of an EXC block. If the EXC block activated is remote, tripping and untrip-
ping may require several BPCs to complete.
♦ IND, DEP, and EXC blocks process the number of statements specified by the block’s
BPCSTM parameter each scheduled BPC. When a statement requiring suspension
such as WAIT or WAIT UNTIL executes, fewer statements may be processed than
the number specified by BPCSTM.
Since Sequence block algorithms vary in length, a block may execute completely in one BPC or it
may require several BPCs to execute completely.
Once all statements have been executed, the Sequence block is no longer processed unless a state-
ment in the user algorithm causes it to repeat.
If the sequence block contains state change logic, that logic will be executed if the block switches
from the Active/Auto mode to the Inactive, Manual or Paused state. The logic for the state
changes are user-defined in SBXs 3, 4, and 5.
The order of statement execution can be altered while in the Auto state. An operator, at a user-
defined or default display, can redirect statement execution to a new start location by writing the
desired statement number to the STMRQ parameter.

Semi-Auto State
In Semi-Auto (or Step mode), the sequence block executes only the HLBL statements that belong
to a particular step. Statement execution stops when a step boundary is passed. Steps can be
requested in any order, at a user-defined or default display, by writing the desired step number to
the STEPRQ parameter. The block is divided into steps by means of the step labels in HLBL.
If the sequence block contains state change logic, the corresponding logic will be executed if the
block switches from the Active/Step mode to the Inactive, Manual, or Paused state.
The logic for the state changes are user-defined in SBXs 3, 4, and 5.

Manual State
In the Manual state, output parameters are not secured. This means that external sources (other
blocks and applications) can write values to the block’s output parameters. Unlike continuous
control blocks, sequential control blocks may have their own statements write to their own output
parameters while the block is in Manual.
Sequential control block algorithms are processed as follows in the Manual state:
♦ TIM blocks are not processed.
♦ MON block cases are executed one at a time by user request. The user selects a case
for execution, from a user-defined or default display, by writing the desired case num-
ber to the CASERQ parameter.

139
B0193AW – Rev R 10. Sequence Logic

If a requested case trips (that is, the evaluated condition is true), a block activation request is exe-
cuted. After the case has been processed completely (tripped and untripped), the standard param-
eter CASENO is set to indicate the number of the next case. The next case is not evaluated unless
requested. The TRPCHG parameter is incremented each time a case changes to or from the
tripped state.
The processing of EXC blocks already activated by tripped cases in the MON block are not
affected by other case evaluation requests to the MON block.
♦ IND, DEP, and EXC block statements are executed one at a time by request. You can
select a statement for execution from a user-defined or a default display by:
♦ Writing to the parameter STEPRQ the step number which begins with the
requested statement.
♦ Writing to the parameter STMRQ the number of the requested statement.
♦ Setting NXTSTM to true.
A statement requiring several BPCs to execute, such as a WAIT statement, need only be requested
once to initiate execution.
Statement execution can be cancelled by requesting that another statement be executed. The stan-
dard parameter STMNO indicates the number of the statement currently executing. When the
statement finishes execution, STMNO is set to the number of the next statement dictated by exe-
cution flow. That statement is not executed unless requested by:
♦ Writing its number to the parameter STMRQ
♦ Setting NXTSTM to true.
When the requested statement calls a subroutine, all the HLBL statements of that subroutine (and
any nested subroutine) are executed. The parameter SUBRNO indicates in which subroutine, if
any, the currently executed statements reside. The parameter STMNO indicates the statement
number within that subroutine.
The Subr-Trace and SBX-Trace modes enable you to single step through statements of subrou-
tines and SBXs. You can switch the block into one of the Trace modes only when the block is in
the Active/Manual state.
Subr-Trace is a substate of the Manual state that enables you to single-step through a subroutine.
You enter this substate by selecting the “SUBR TRACE” button in the ALL CODE display. This
enters the integer value “1” into the TRACRQ parameter which, in turn, sets the block into the
Subr-Trace mode when the block is in Manual. After granting the request, the block resets
TRACRQ to 0.
Once in the Subr-Trace mode, you “select” a subroutine by requesting a call-subroutine statement
in the block’s main section. The block is then idle before the first statement in the requested sub-
routine. You can then single-step through the subroutine statements by toggling the NXTSTM
parameter. STEPRQ and STMRQ cause the execution of a single statement in the block’s main
section.
When you switch into the SBX-Trace mode, the block environment (that is, step, subroutine,
statement number) is saved. The block returns to this environment when you exit the SBX-Trace
mode.

140
10. Sequence Logic B0193AW – Rev R

Once in the SBX-Trace mode, you “select” an SBX by setting the SBXRQ parameter to a value of
1 to 4. SBX5 (a switch to Paused) applies only to the DEP block (the block ignores out of range
values). When you select an SBX, the block idles at the first statement within that SBX. You can
then single-step through the SBX statements by toggling the NXTSTM parameter. The block
ignores step- and statement-requests while it is in the SBX-Trace mode.
In the Manual, Subr-Trace, and SBX-Trace modes, the block does not secure its output parame-
ters. External sources (other blocks and applications) can write values to the block’s outputs.
While the block is in one of these modes, the EXC, DEP, or IND block algorithm can update its
output parameters after a step-, statement-, or next-statement request.
To exit from the Trace mode, select the “TRACE” field in the faceplate.

Auto/Manual Transitions
You can change the block Auto/Manual state from external sources such as user-defined and
default displays, other blocks, and applications.
If a statement is in execution when you request a state change, the statement’s execution is com-
pleted as if it had begun in the requested state. Then any following statements are executed as
appropriate for the requested state.

NOTE
If one or more cases are making a transition from Active to Tripped (for example,
the blocks to be activated are remote blocks) when you change a MON block from
Automatic to Manual, then the block activation is completed but the cases do not
trip.

Sequence States
The Sequence states, Active, Inactive, Paused, and Tripped, in conjunction with the Application
states, control sequential control block algorithm execution. The Sequence states are determined
by the values of the block’s ACTIVE, PAUSED, and TRIPPD parameters. When ACTIVE is
true, the block is in the Active state. When ACTIVE is false, block is in the Inactive state.
Another block parameter, RSTACT, controls the value of the ACTIVE parameter when the com-
pound in which it resides changes from Off to On, or when the control processor in which it
resides undergoes a restart operation, as follows:
♦ RSTACT = 0: ACTIVE is false.
♦ RSTACT = 1: ACTIVE is true.
♦ RSTACT = 2: ACTIVE retains the value from the checkpoint file when the Control
Processor is restarted, or remains 0 when the compound makes a transition from Off
to On.
When a DEP block is in the ACTIVE state, it may also be in the PAUSED state. A DEP block is
Paused when the PAUSED parameter is true.
When a MON block is in the Active state, it may also be in the Tripped state. A MON block is
tripped when the TRIPPD parameter is true.

141
B0193AW – Rev R 10. Sequence Logic

Table 10-2. Sequence States

State Description
Inactive An IND, DEP, or EXC block is not executing any statements or a MON block
is not evaluating conditions.
Active An IND, DEP, or EXC block is executing statements or a MON block is
evaluating conditions.
Paused A DEP block’s execution is suspended because one or more EXC blocks in
the same compound are Active. The DEP block remains suspended until all
such EXC blocks are done executing.
Tripped A condition evaluated by a MON block causes it to activate other blocks. The
MON block remains tripped until all activated blocks are done executing.

Active State
In the Active state, an IND, DEP, EXC, or MON block is processed. (The TIM block does not
have an Active state. It is processed when the compound is On and the Application state is Auto.)
How statements are executed depends upon the Application states Auto, Step, and Manual.

Inactive State
In the Inactive state, an IND, DEP, EXC, or MON block is not processed. (TIM blocks do not
have an Inactive state. TIM blocks are not processed when the Application state is Manual.)

Active/Inactive Transitions
You can change the block Active/Inactive state from external sources such as user-defined and
default displays, other blocks, and applications.
When a linkage to the ACTIVE parameter exists, it is secured. This means that you cannot access
the parameter directly. To activate or deactivate the block, you can:
♦ Access the ACTIVE parameter through the source of the linkage
♦ Write the number of a non-existing statement to STMRQ.
Writing the number of a non-existing statement to STMRQ directs statement execution to the
end of the algorithm. Although the block is in effect deactivated, the ACTIVE parameter remains
true until it has been released. When released, it is automatically set to false.

Paused State
In the Paused state, DEP block statement execution is suspended due to active EXC blocks in the
same compound. The PAUSED parameter indicates whether a DEP block is in the Paused state.
When PAUSED is true, the block is in the Paused state.

Tripped State
In the Tripped state, a MON block has one or more cases tripped. A case trips when it is evaluated
as true and activates another block. The TRIPPD parameter indicates whether a MON block is in
the Tripped state. As long as at least one case is tripped, the TRIPPD parameter is true; otherwise,
TRIPPD is false.

142
10. Sequence Logic B0193AW – Rev R

Transition States
The Transition states, To_Inactive, To_Manual, and To_Paused, are intermediate states that the
Sequence Control block assumes while the block is executing one of the three standard block
exception handlers (SBXs 3, 4, and 5) that are provided for state change handling.

To_Inactive State
The To_Inactive state is an intermediate state that an IND, DEP, or EXC block assumes while
SBX 3 is executing. SBX 3 is the user-defined, user-enabled response to an externally initiated
change of block state from the Active/Auto (or Active/Step) state to the Inactive state.
The MON and TIM blocks do not have a To_Inactive state since they do not contain SBXs.

To_Manual State
The To_Manual state is an intermediate state that an IND, DEP, or EXC block assumes while
SBX 4 is executing. SBX 4 is the user-defined, user-enabled response to an externally initiated
change of block state from the Active/Auto (or Active/Step) state to the Manual state.
The MON and TIM blocks do not have a To_Manual state since they do not contain SBXs.

To_Paused State
The To_Paused state is an intermediate state that a DEP block assumes while SBX 5 is executing.
SBX 5 is the user-defined, user-enabled response to an externally initiated change of block state
from the Active/Auto (or Active/Step) state to the Paused state.
The IND and EXC blocks do not have a To_Paused state since they do not have a Paused state.
The MON and TIM blocks do not have a To_Paused state since they do not contain SBXs.

Compound Sequence State

The collective operational state of all sequential control blocks in a compound is represented by
the compound parameter SSTATE. SSTATE can be one of three values:
♦ SSTATE = 0 (Inactive)
♦ SSTATE = 1 (Active)
♦ SSTATE = 2 (Exception).
See Table 10-3 for further definition.

Table 10-3. Compound Sequence State

SSTATE Value Description

Inactive All MON blocks and all Sequence blocks (IND, DEP, or EXC) in the
(SSTATE = 0) compound are Inactive.
Active One or more MON blocks and/or one or more Sequence blocks
(SSTATE = 1) (IND and DEP) in the compound are Active. No EXC blocks are active.
Exception One or more EXC blocks in the compound are Active. IND blocks may
(SSTATE = 2) be active; TIM blocks may be running.

143
B0193AW – Rev R 10. Sequence Logic

When a compound is switched OFF, all the sequence blocks in that compound go to the Manual
state, thereby releasing their output parameters.

Sequence Processing
Sequential control blocks are processed every scheduled Basic Processing Cycle (BPC) as defined
for the Control Processor in which they operate. The following figure shows the processing order
within a scheduled BPC.

1 BPC

Compound A Continuous/LLI Continuous/LLI

MON/TIM EXC DEP/IND
Compound B Continuous/LLI Continuous/LLI
MON/TIM EXC DEP/IND
Compound C Continuous/LLI Continuous/LLI
MON/TIM EXC DEP/IND

1 2 3 4 5

Figure 10-1. Processing Order Within a Scheduled BPC

The scheduled BPC is determined by the block parameters PHASE and PERIOD. The PHASE
parameter specifies when a block should be executed relative to the other blocks in that PERIOD.
The PERIOD parameter specifies how frequently a block should be executed. For more informa-
tion, refer to “Block Phasing” on page 68, and “Relationship Between Block Period and Phase” on
page 69.
When a sequential control block is activated, it begins executing its block algorithm in the next
scheduled BPC as defined by the block parameters PERIOD and PHASE.
When a MON or TIM block is processed, its entire algorithm is executed each scheduled BPC
until deactivated.
When an IND, DEP, or EXC block is processed, a specified number of statements in the algo-
rithm are executed each BPC. The number of statements processed is determined by the value of
the block’s BPCSTM parameter. When the last statement is executed, the block automatically
deactivates itself.
Sequence language statements are executed in the order programmed by the user. Statement exe-
cution continues in a given BPC until:
♦ The number of statements specified by the BPCSTM parameter are executed in Auto,
or in Step mode.
♦ The last statement of a step is executed in Step mode.
♦ One statement is executed by request in Manual for an IND, DEP, or EXC block.
The number of statements executed in automatic may be less than the number specified by the
BPCSTM parameter if an executed statement requires more than one BPC to complete. For
example:
♦ A statement makes a request to access a block parameter in a remote Control
Processor.
♦ A WAIT or WAIT UNTIL statement has a wait condition exceeding the BPC.

144
10. Sequence Logic B0193AW – Rev R

Sequence Processing Overrun

If the block processor cannot process all scheduled blocks in a BPC, there is BPC overrun. In a
serious system overload, sequence (and continuous) blocks are always processed, even if it delays
the next BPC for the remaining blocks not yet processed.

Useful Hints on SBX Programming

Operational Error SBXs
The sequence Interpreter has comprehensive error protection. In case of any operational error, the
parameter OP_ERR assumes an integer number that indicates the kind of failure.
If OP_ERR has a value larger than 3000, a serious error has occurred. When a serious error has
occurred, you must be careful when defining SBX (exception logic) TO_SYS_ERROR. An
attempt to continue to run or retry the same statement may cause memory violation (for CP30 or
CP40), memory corruption, or unpredictable control algorithm behavior. The nature of this kind
of error is usually a software or hardware problem. Therefore, you should use basic logic (no sub-
routine calls and external references) to write OP_ERR, SBRNO, SBXNO, BLOCK_STMNO,
and STMNO, then stop the block, collect any related information, and report the information to
the Customer Satisfaction Center (CSC) at 1-866-746-6477.
All other error conditions, including user errors (SBX TO_USR_ERROR: 2000 < OP_ER <
3000), allow retrying the same statement. (If you do this, you should be careful to avoid infinite
loops.) For most of the cases the “retry” does not clear the error.
Example: OP_ERR 2314 “string type expected in string expression” does not go away after retry.
The important thing to remember is that if you decide to continue you may end up with unex-
pected results.
LOC_VAR, STR1 : S;
STATUS : B;
LOC_VAR := “:CONTROLLER_1.BI0001”;
STATUS := :’LOC_VAR’;
STR1 := “:MAIN_LOOP.BO0001”;
LOC_VAR := STRING :’STR1’;
:’LOC_VAR’ := TRUE;
STR1 is not a FPN (full path name) for a string type parameter. In this case LOC_VAR keeps its
value unchanged and CONTROLLER_1 BI0001 parameter is set to “TRUE”.

145
B0193AW – Rev R 10. Sequence Logic

The following example caused a CP failure on a CP30 with software V2.2.1a or older:
Example:
INDEPENDENT_SEQUENCE
{* A TEST CASE *}
CONSTANTS
VARIABLES
USER_LABELS
SUBROUTINE SUBR2(IN II : I)
VARIABLES
STATEMENTS
II0002 := II;
ENDSUBROUTINE

SUBROUTINE SUBR3()
VARIABLES
RR : R;
STATEMENTS
RR := :WRONG:PATH.NAME; {* OP_ERR ‘-1’ *}
IO0003 := ROUND(RR);
{* All subroutines in the block share the same memory for local vari-
ables and arguments. In the example, RR has a value of II0001 which is
left after SUBR2 call. When II0001 is equal to ‘1’, the CP crashes
because ‘01 00 00 00’ is not a valid binary representation of a float
number.
*}
ENDSUBROUTINE
SUBROUTINE SUBR1()
VARIABLES
STATEMENTS
CALL SUBR2(II0001);
CALL SUBR3();
ENDSUBROUTINE
BLOCK_EXCEPTION TO_SYS_ERROR
STATEMENTS
SN0001 := “ERROR= “,OP_ERR,” B_STMNO= “, BLOCK_STMNO;
ENDEXCEPTION
{*Wrong practice: continue to run no matter what! *}
STATEMENTS
<<START>>
CALL SUBR1();
WAIT 0.1;
GOTO START;
ENDSEQUENCE
CPs with software V2.2.1b or later zero out denormalized values for cases like the above to avoid
system failure but this may cause unexpected algorithm behavior by using a value of zero instead
of what would be appropriate.

146
10. Sequence Logic B0193AW – Rev R

A common practice might be:

* TO_SYS_ERROR SBX – stop running if OP_ERROR > 3000
* TO_USR_ERROR SBX – stop running except OP_ERR 2401 if found necessary for
the algorithm strategy.
You should be careful when continuing under error conditions triggered TO_SYS_ or
TO_USR_ERROR SBXs.

SBX RETRY Logic

If you want the same number of retries on any HLBL statement which caused an operational
error, you must build the logic to properly reset the retry counter. It is important to remember
that each HLBL statement can produce more then one error. Therefore, you should choose a
proper limit for retries since the RETRY instruction repeats the entire statement not just the
faulty element. An example of the proper implementation of the “retry” is as follows:
RETRY_CNT : I; {* to count retries on individual statements *}
SAVED_STMNO : I;
SAVED_STMNO := -1; {* initialization to guarantee miscompare with
BLOCK_STMNO *}

BLOCK_EXCEPTION <TO_SYS_ERROR or TO_USR_ERROR>_SBX

IF OP_ERR <> ERR1 AND OP_ERR <> ERR2 AND OP_ERR <> ERR3 THEN
GOTO FINAL;
{* ERRx are errors to retry. For TO_SYS_ERROR SBX the statement
must be replaced with IF OP_ERR > 3000 THEN GOTO FINAL ENDIF;
*}
ENDIF
IF BLOCK_STMNO <> SAVED_STMNO THEN
RETRY_CNT := 0;
SAVED_STMNO := BLOCK_STMNO;
ENDIF;
IF RETRY_CNT < LIMIT THEN
RETRY_CNT := RETRY_CNT + 1;
{* In some cases, you may want to add the “WAIT” statement at this
point. For example, OP_ERR ‘-1’ or ‘-45’
*}
RETRY;
ENDIF;
<<FINAL>>
SENDMSG (“ERROR! op_err=”,OP_ERR,” stm=”, BLOCK_STMNO,
“ SBXNO=”,SBXNO) to SN0001; {* or to MSGGRx *}
EXIT;
ENDEXCEPTION

147
B0193AW – Rev R 10. Sequence Logic

The above SBX design assumes that SAVED_STMNO must be set to -1 (initialized):
1. In the first statement of the:
♦ Main code section
♦ Each subroutine
♦ State change SBX (TO_INACTIVE, TO_MANUAL, TO_PAUSED).
2. In the last statement of the state change SBX unless the logic terminates the block.
3. In the first statement after any label which is used as the “GOTO” statement argu-
ment to change execution flow backwards or to jump from any type of SBX to the
block main section.

Operational Error Conditions Inside Subroutines

Presently in an SBX there is no information about the subroutine number and statement number
of a subroutine which has triggered an SBX execution. BLOCK_STMNO always refers to the
main section. In the SBX the STMNO refers to the current SBX statement, SUBRNO is 0 unless
the SBX itself calls a subroutine. To make the retry logic work properly, SAVED_STMNO must
be reset before each subroutine statement which may trigger the SBX retry logic. In most cases,
this results in a significant overhead. An alternative is to use a more elaborate approach which is
primarily based on an assumption that the retries make sense only on statements with external ref-
erences. Related OP_ERRs which may be fixed with retries are:
♦ All negative values. They are related only to external references outside the CP or to
targets which do not exist.
♦ “3”: Attempt to write a secured parameter (for example, an output parameter while
the block is in AUTO).
♦ “18”: Locked access (for example, the OWNER parameter of a block).
♦ “2401”: Attempt to set the ACTIVE parameter to a value that is already assumed.
The idea of the approach is to reset SAVED_STMNO inside subroutines before each statement
with:
♦ External references (including ACTCASES, ABORT and ACTIVATE statements) to
a remote station database.
♦ Any of external sets including ABORT, and ACTIVATE statements which may pro-
duce OP_ERR 3, 18, or 2401 if retry is expected.
If speed and memory are not major issues, instead of resetting the SAVED_STMNO multiple
times for the kind of statement listed above, you may program HLBL logic to avoid usage of this
statement more than once inside of each subroutine. To remove multiple external references from
the subroutines, you can create a set of SET_VALx and GET_VALx subroutines to be called
when needed.

148
10. Sequence Logic B0193AW – Rev R

Example:
For SET_VALx() (where ‘x’ stands for R,I,B,S data type)
SUBROUTINE SET_VALR(IN FPN : S; INOUT VAR : R)
STATEMENTS
SAVED_STMNO := -1;
VAR := :’FPN’;

ENDSUBROUTINE

SUBROUTINE SET_VALI(IN FPN : S; INOUT VAR : I)

STATEMENTS
SAVED_STMNO := -1;
VAR := :’FPN’;
ENDSUBROUTINE

SUBROUTINE SET_VALB(IN FPN : S; INOUT VAR : B)

STATEMENTS
SAVED_STMNO := -1;
VAR := :’FPN’;
ENDSUBROUTINE

SUBROUTINE SET_VALS(IN FPN : S; INOUT VAR : S)

STATEMENTS
SAVED_STMNO := -1;
VAR := STRING :’FPN’;
ENDSUBROUTINE

NOTE
To continue after unsuccessful retries the you can secure the results by writing the
default value into VAR. Example:
SUBROUTINE SET_VALB(IN FPN : S;
INOUT VAR : B;
IN DFLT : B )
STATEMENTS
SAVED_STMNO := -1;
VAR := DFLT;
VAR := :’FPN’;
ENDSUBROUTINE

Operational Error Condition Inside State Change SBX

Presently in an operational error SBX there is no information about the state change SBX which
has triggered an operational error SBX execution. The situation is exactly the same as described
for subroutines. All recommendations for the retry logic which were given before are suitable for
the state change SBXs.

Complex Statements
You should avoid complex HLBL statements such as the following:

149
B0193AW – Rev R 10. Sequence Logic

SAVED_STMNO := -1; {* the initialization is not needed for the main code
section. *}
IF :COMP1:BLOCK1.BO0001 <> :COMP2:BLOCK2.BO0002 THEN
...........
ENDIF
This statement can produce OP_ERR “-1” twice and RETRY_CNT is not reset for the second
one. It is preferable to avoid usage of two or more external references in the single statement. You
should use extra assignment statement instead:
SAVED_STMNO := -1;
TMP_BOOL := :COMP2:BLOCK2.BO0002;
SAVED_STMNO := -1;
IF :COMP1:BLOCK1.BO0001 <> TMP_BOOL THEN
............
ENDIF
You may also double the number of retries by setting a proper value for LIMIT (the variable
LIMIT was used in the above example for SBX programming).

Usage of the SUBR_LEVEL Standard Parameter

Some applications use SBX logic to decide to “retry” or to “not retry” a particular HLBL state-
ment on a particular OP_ERR. Those applications may need more precise identification for sub-
routines which triggered the SBX. While the subroutine statement identification is the user’s
responsibility, there are ways to identify the subroutine.
The subroutine can be identified in the SBXs by the BLOCK_STMNO and SUBR_LEVEL stan-
dard parameters in cases when:
♦ HLBL logic does not have subroutine calls from other subroutines (the maximum
nesting level is one).
♦ All subroutines have not more than one call of another subroutine (no limits on the
nesting level).
Remember that if the SBX does the identification inside a subroutine (the SBX calls another sub-
routine), the SUBR_LEVEL is incremented by one.
If subroutines are called from the state change SBXs and the block main section, you user must set
the special flag at the beginning of the each state change SBX to be used in the operational error
SBX to ensure the correct subroutine identification. The flag must be cleared at the end of the
state change SBX.

150
11. Integrated Control Configurator
Concepts
This chapter discusses various integrated control configurator concepts, for example, hardware
and software interfaces, and control station, library volume, and compound configuration.
The Integrated Control Configurator is both a configurator and a compound/block editor. As a
configurator, it allows you to add or modify Fieldbus Module (FBM) software data as necessary.
Hardware configuration takes place in the System Configurator as part of system startup, expan-
sion, or maintenance. A list of the configured modules is passed to the control configurator, where
it is accessible from the menu-bar function combination SHOW/Configured ECBs.
When you add an FBM to your system, you create an Equipment Control Block (ECB) for each
FBM selected. The ECB is the “holding place” for that FBM’s software data. ECBs are created
using the Insert Block/ECB function of the ICC main menu or the FBM/Fix All menu-bar
function.
Additionally, database files are provided for each library volume as it is created in the system.
Once installed, these files can be identified by the lowercase characters “vol.”
All modifications to this physical data are made through the Integrated Control Configurator.
These modifications can be made to on-line stations or off-line library volumes. As a com-
pound/block editor, the Integrated Control Configurator provides compound/block-building
templates along with a full range of editing functions.
With it you can:
♦ Create and integrate continuous, sequence, and ladder logic type blocks in a single
compound structure
♦ Group and connect compounds
♦ Modify, copy, and delete compounds and blocks
♦ Configure and modify Fieldbus modules
♦ Assign control schemes to stations in a distributed processing environment
♦ Build and maintain compound libraries
♦ Add device ECB blocks on line.

Configuration Aids
Configurator selections are either from a menu bar along the top of the workstation screen, or
from menus that appear, making additional choices possible.
From initial start-up, your directions on “what to do next” are provided by the logical structure of
the configurator.
As all-inclusive as the configurator program is, however, there are times when more information
and further assists are necessary. The following aids provide that assistance.

151
B0193AW – Rev R 11. Integrated Control Configurator Concepts

Help Screens
Help screens provide necessary backup information. They provide help on issues such as ranges,
choices, and error messages. They also provide help on the help function itself.

Parameter List
When you edit a compound/block, you can select either the standard parameters, or the complete
list of parameters for that compound/block.

Sequential Control Block Reference Information

When a block is defined as one of the Sequence types, the configurator program transfers control
to the Sequence Environment. Selecting EDIT from this environment provides an Interactive
Character Editor (ICE) or the UNIX® “vi” editor for building and compiling source code for
user-defined sequence blocks.
ICE and vi command information can be found in the applicable UNIX or VENIX™
documentation.
After the source code is compiled, control is again resumed by the configurator program.

Hardware Interface
The configurator operates with any Control Processor or any Application Processor or Personal
Computer that contains a Fieldbus interface card. It also operates with any Workstation Processor
supported by the Human Interface (HI) library.
The configurator must have a display screen and a keyboard.

User Interface
An alphanumeric keyboard is the primary input device.
A secondary input device is a mouse or trackball.

Software Interface
The configurator uses software processing routines to find:
♦ Control Processor letterbug names
♦ Fieldbus Module letterbug names for system-configured FBMs
♦ Control Processor database file (checkpointed) name
♦ Control Processor file status
♦ Control type availability for a Control Processor.

152
11. Integrated Control Configurator Concepts B0193AW – Rev R

Compound Summary Access

The Compound Summary Access (CSA) utility displays the list of active compounds and returns
the associated letterbug (if any) to the configurator. This provides a means of determining if a spe-
cific active compound name exists in the system.
CSA is a search and find utility and the “doorway” to the configurator.
Refer to Integrated Control Configurator (B0193AV), Chapter 2, for more on CSA.

Software Processing
Software processing provides the functions to:
♦ Initialize the software processing facilities.
♦ Reset access to the local host.
♦ Determine the host associated with a specified Control Processor.
♦ Return a file containing the letterbug and note the installed (active) Control
Processors.
♦ Return a file containing a list of the active printers.
♦ Return a file containing a list of the active Workstation Processors.
♦ Return a file containing a list of the active historians.
♦ Lock or permit access to the Control Station database file associated with a specified
Control Station letterbug.
♦ Lock or permit access to a library volume database.
♦ Unlock a Control Processor database.
♦ Return a list of FBMs, which were configured with the System Configurator, for a
specified Control Station letterbug.
♦ Return a list of the subset of the above System Configurator-configured FBMs which
have actually been created.
♦ Return a glossary of equipment configuration parameters for each FBM type, to aid
you in configuring an FBM which has not been pre-defined using the System
Configurator.

System Monitor Interface

The configurator requests a Control Processor database checkpoint of an active station in the fol-
lowing manner:
♦ The configurator finds the name of the system monitor responsible for the station.
♦ The configurator requests a checkpoint of the station from that system monitor.
♦ The system monitor responds when the checkpoint is in progress.
When the checkpoint is complete or the checkpoint fails (times-out), the system monitor sends a
message to the configurator indicating the result of the checkpoint. If so configured, the system
monitor creates a history of the event and prints a message to a communications server.

153
B0193AW – Rev R 11. Integrated Control Configurator Concepts

Control Processor Database Installer

This Control Processor-resident routine:
♦ Receives and acknowledges INSERT commands sent by the configurator, communi-
cated through an Interprocess Communication (IPC) interface.
♦ Updates the CP checkpoint file authorization code at the successful completion of an
INSERT command.
♦ Initializes a compound or block after a modification is made.
♦ Provides single-channel, single-instance registration with the IPC subsystem, guaran-
teeing that only one Integrated Control Configurator can connect to a CP at a time.

Configuration Target
You can select either a Control Station or a Library Volume as your configuration target.

Control Station Configuration

Before beginning an editing session with a new configuration target, the configurator:
♦ Retrieves all the appropriate station data
♦ Provides a list of the Control Stations that are configured for the system
♦ Compares the authorization codes of the resident CP database and the checkpointed
CP database
♦ Provides the means to make necessary adjustment(s) to mismatched, invalid data, or
disconnected hardware.
When you select DONE on the menu bar to exit the edit session, all data pertaining to the selected
station is validated and checkpointed.

Library Volume Configuration

Before beginning an editing session with a new Library Volume, the configurator provides a list of
volume letterbugs which have been configured for the user’s system. Once a volume letterbug has
been selected and the edit session initiated, the session status field displays INACTIVE, indicating
that there is no Control Station involved. The rest of the user interface is similar to that used for
Control Stations. When the user selects DONE from the menu bar, the volume data is validated and
the edit session is exited.

Compound Configuration
When you choose a Compound name, the configurator determines if the compound name exists,
is valid (up to 12 characters), and is unique in the system.
If the compound does not exist, the configurator assumes that you are attempting to add a com-
pound to the “working” library volume. It returns the letterbug of a default library volume, and
enters the INACTIVE editing mode.
If the compound does exist, the configurator displays the station or volume letterbug and the
compound name, along with a list of all the compounds in that Control Processor (in the leftmost
column on the screen). It then enters the ACTIVE mode.

154
11. Integrated Control Configurator Concepts B0193AW – Rev R

You can also search for a selected compound name. This feature allows you to quickly find a spe-
cific compound from all the compounds in the defined domain. Once you make the selection, the
Compound Summary File informs the configurator in which checkpoint file the compound
resides.

Copying Compounds Between Configuration Targets

The configurator provides an editable area called a paste buffer. The paste buffer resembles a con-
ventional configurator volume, but its contents are not associated with a particular station or
library volume (targets).
The paste buffer allows you to copy compounds between stations or volumes. To do this, copy a
selected compound into the paste buffer.
Then choose a compound in the list and select PASTE to move the contents of the paste buffer into
the list just before the selected compound.
Since all compound names are unique within the system, you must rename the compound that
you copied into the paste buffer. You can copy more than one compound into the paste buffer.
However, if you are copying more than one compound, select PASTE AND APPEND rather than
PASTE.
PASTE overwrites the contents of the buffer, while PASTE AND APPEND queues the com-
pounds in the buffer for later retrieval.

Checkpoint Files
You can request a Control Station database checkpoint during an edit session by selecting CHECK-
POINT from the menu bar. This checkpoints the entire database.

Compound and Block Name Conventions

Compound Names
Compound names are up to 12 characters in length and must be globally unique in the active sys-
tem. When you request that a new compound be added, the configurator station interface checks
to see if another compound by the same name exists. If the proposed compound name already
exists, the station interface returns a message that the compound cannot be added using that
name.
However, if the proposed compound name proves to be unique, the compound is added to the
Compound Summary File.
When you delete a compound, the compound is removed from the Compound Summary File.

Block Names
Block names, also up to 12 characters in length, must be unique within a compound but not
necessarily throughout the system. The configurator displays an error message if you try to add a
block to a compound when another block by the same name already exists within that
compound.

155
B0193AW – Rev R 11. Integrated Control Configurator Concepts

Configurator Editing Modes

The configuration target determines the editing mode of the configurator. If the target is a library
volume, the editing mode is always INACTIVE. If the target is a station, and an IPC connection
can be established with the appropriate station database installer, the editing mode is ACTIVE.

Active Editing
In the Active editing mode, the configurator is connected to a Control Station for interactive dis-
play and editing. In this mode you can:
♦ ADD and DELETE compounds, blocks, and ECBs
♦ MODIFY compound, block, and ECB parameters and connections
♦ COPY compounds to and from the paste buffer
♦ SAVE and LOAD compounds from floppy disk
♦ CHANGE Fieldbus Module per-unit and per-point parameters.
When you finish modifying a block or another modifiable object definition, the configurator
automatically installs it when you select DONE.
The station returns acknowledgment messages on receipt of these commands informing the con-
figurator either of acceptance or rejection. The configurator maintains its station workfile to
reflect these results.
When you change a Fieldbus Module (FBM) configuration with the System Configurator, you
can optionally update the Control Station with the change. If the FBM is not known to the sta-
tion (no ECB present in the station checkpoint file), or the FBM data has either been deleted or
modified, you can use the configurator to produce appropriate insert commands so that the sta-
tion will install the appropriate ECB for the module.
The configurator makes a request to the system monitor to initiate a checkpoint operation and
the Control Station responds. When the operation is complete, the configurator is enabled for
further edit operations.
In addition, an ECB for a non-system configured FBM can be built from scratch, as in the case of
any other new block. The FBM corresponding to the new ECB is specified by entering the
DEV_ID parameter in the ECB configuration.

Inactive Editing
In this editing mode, the configurator is not connected to a station but modifies the database of a
Library Volume. Editing a Library Volume is essentially the same as editing a station. The internal
differences are that:
♦ There is no station in the communications loop
♦ There is no validity checking for installation commands
♦ There is no IPC linkage.
A workfile (which also exists for the active mode) substitutes as the station and adjusts the inactive
data base in response to changes.

156
11. Integrated Control Configurator Concepts B0193AW – Rev R

Configuration Validation
Whenever you install a new block or modify the parameters of an existing block, certain parame-
ters of the affected block are validated according to block-specific rules. If a violation is detected, a
warning message is sent to the control configurator and displayed at the console. The same mes-
sage is shown on the primary page of the block’s detailed display. The string parameter ERCODE
is also set to contain the violation message. Certain violations are considered fatal errors, and pre-
vent the block from being installed. Others are considered only warnings. These warning mes-
sages are handled the same way as error messages, except that the incorrect configuration is
preserved in the configuration work file. This allows you to see the error that must be corrected.
Validation of block parameters does not proceed past the first error encountered by the block
logic. Table 11-1 shows the warning messages. At present, all warnings except “W59 – DUPLI-
CATE OUTPUT CHANNEL” cause the block to be marked Undefined.

Table 11-1. ERCODE Parameter Messages

Message Meaning
“W43 – INVALID PERIOD/PHASE PHASE does not exist for given block PERIOD, or block
COMBINATION” PERIOD not compatible with compound PERIOD.
“W44 – INVALID High range value is less than or equal to low range value.
ENGINEERING RANGE”
“W45 – CONFIGURATION A parsing error has been detected in a CALC, CALCA,
ERROR IN STEP nn” LOGIC, or MATH block; nn identifies the step in error.
“W46 – INVALID INPUT The source parameter specified in the input connection
CONNECTION” cannot be found in the source block, or the source
parameter is not connectable, or an invalid boolean
extension connection has been configured.
“W47 – INVALID PARAMETER A tuning block is connected to a PIDA block containing a
CONNECTION” connected tuning constant.
“W48 – INVALID BLOCK The configured value of a block option is illegal.
OPTION”
“W49 – INVALID BLOCK An illegal block extension has been configured for
EXTENSION” EXTBLK (AIN, AINR, MAIN blocks), NLNBLK (PIDA
block), or PIDBLK (FBTUNE, FFTUNE blocks).
“W50 – INVALID SIGNAL An SCI or SCO parameter setting is invalid.
CONDITIONING INDEX”
“W51 – INVALID An I/O block is connected to an ECB or the wrong type.
HARDWARE/SOFTWARE TYPE”
“W52 – INVALID I/O An I/O block is connected to an ECB when the specified
CHANNEL/GROUP NUMBER” point number is invalid or when the specified group or
octet number is invalid.
“W53 – INVALID PARAMETER A parameter value is not in the acceptable range.
VALUE”

157
B0193AW – Rev R 11. Integrated Control Configurator Concepts

Table 11-1. ERCODE Parameter Messages (Continued)

Message Meaning
“W54 – ECB DOES NOT EXIST” An I/O block has a connection to an ECB that does not
exist or has not yet been installed. When the ECB is
installed, previously installed I/O blocks waiting for that
ECB will initialize automatically.
“W55 – CONTROLLER DOES An FBTUNE or FFTUNE block has an unspecified or
NOT EXIST” unresolved extension connection to a PIDA controller
block. When the PIDA is installed, previously installed
tuning blocks waiting for that PIDA will initialize
automatically.
“W56 – INVALID CONTROLLER An FBTUNE or FFTUNE block has an extension
MODE” connection to a PIDA block whose mode (MODOPT)
is not tunable.
“W57 – TUNING_CONSTANT An FBTUNE or FFTUNE block has an extension
LINKED” connection to a PIDA block that has a linked tuning
constant.
“W58 – INSTALL ERROR; A Database Installer error has occurred.
DELETE/UNDELETE BLOCK”
“W59 – DUPLICATE OUTPUT This block and another output block are connected to
CHANNEL” the same output point. Since this may be intentional, this
message is only a warning.

Programmable Logic and Sequential Control Block

Source Files
The Ladder Logic and Sequential control block types contain some fixed sets of parameters, but,
in addition, supply the Ladder Logic source code (for Ladder Logic), and/or Sequence Language
source code (for Sequence blocks). Either allows you to define the operation of the block.
When you define a block type as being either a Programmable Logic block (PLB) or one of the
Sequence types, additional functions highlight in the Block Functions menu, as appropriate.
They are:
♦ Edit Ladder Logic
♦ Edit Sequence Logic.
Ladder Logic and Sequence Control Logic are described in “Ladder Logic Overview” on page 99
and “Sequential Control Blocks” on page 133, respectively.

158
12. Control Processor (CP)/Fieldbus
Application Interface
The communications network between the I/A Series System Control Processor and the process
instrumentation consists of a hardware interface built around the Fieldbus Module (FBM),
Fieldbus Cluster Module (FBC), and Fieldbus Communications Module (FCM) and a
software interface centered about the Equipment Control Block (ECB). This section discusses
the interfaces – FBMs, FBCs, FCMs and ECBs, Fieldbus scanning, Fieldbus integration time,
FBM and FBC types, and ECB types.

The Interfaces – FBMs, FBCs, or FCMs and ECBs

The Fieldbus and the Fieldbus Modules, Fieldbus Cluster Modules, or Fieldbus Communications
Modules provide the hardware interface between the process and the Control Processor.

NOTE
Throughout this chapter, the different FCM types, for example DCMs or FBIs, are
referred to as FCMs.
FBM is used throughout this chapter to refer to all equivalents including migration
cards and FBCs.
For a complete list of FCMs, see Appendix C “FBM – ECB Cross Reference”.

Physically, the I/A Series System Control Processor connects to the process in an Ethernet net-
work via a Fieldbus to FBMs, FBCs, or FCMs. The System Configurator/Definition limits the
number of FBMs to 48 maximum for the CP10, 64 for the CP30, CP30B, CP40, CP40B, and
120 for the CP60 (30 behind any single FCM). The appropriate number of ECBs can be deter-
mined using the CP Sizing Spreadsheet and/or Station Block. FBMs and FBCs differ depending
on the electrical nature and distribution of inputs and outputs (FBM and FBC varieties are listed
in “FBM and FBC Types” on page 169).
The Equipment Control Block (ECB) provides the software interface between the FBM, FBC, or
FCM and the I/O blocks.
ECBs differ depending on the FBM, FBC, or FCM and its application [the varieties of ECBs are
listed in “Equipment Control Blocks (ECBs)” on page 169].
When you configure an FBM, FBC, or FCM and its software application type, the System Con-
figurator/Definition automatically adds the appropriate ECB type.
The following figures show:
♦ The FBM as the interface between the process and the Control Processors
(Figure 12-1).
♦ The ECB as the interface between the I/O blocks of a compound and the FBM data
(Figure 12-2).
♦ A typical CP60 and Fieldbus Communications Module Interface (Figure 12-3).

159
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

When compound processing starts, each FBM or equivalent reads the I/O data (both input and
output channels) from the process instrumentation on a per-FBM basis. Any ECBs should be
configured for a scan period equal to the fastest scan period specified for any Input-type I/O block
configured for that FBM. The FBM then conditions, digitizes, and normalizes the data, as neces-
sary, and stores the data and the status into its ECB.
As a control compound is processed, the input blocks retrieve the data from the ECB. Using this
new data, the Compound Processor generates new outputs which are forwarded to the appropri-
ate ECB. The ECB transmits the data to its FBM or FBC which converts the output value to a
signal (such as 4 to 20 mA, 0 to 10 V dc, or pulses) compatible with the process instrumentation.

up to 48, 64, or 120 FBMs

FIELDBUS
or FBM Equivalents
Control Processor 1

N FBM001 FBM002 FBM048

O
D
E PROCESS INSTRUMENTATION
B For Example, T/C, RTD, Transmitter, Switch, or Valve
U
S

up to 48, 64, or 120 FBMs

FIELDBUS
or FBM Equivalents
Control Processor 2

FBM049 FBM050 FBM096

PROCESS INSTRUMENTATION
For Example, T/C, RTD, Transmitter, Switch, or Valve

Figure 12-1. System with Two Fieldbuses

160
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Control Processor 2
Compound #1 ECBP

other blocks I/O ECB for

to/from blocks Fieldbus
in compound FBM049
other
CP’s
Connects to all FBMs
(FBM049 – FBM096)
N associated with this
O COMPOUND #2 Control Processor
D
E Block #1
B
U ECB for
Block #2
S FBM050

Block #3

COMPOUND #n
to/from
other ECB for
CP’s Block x
FBM096

Figure 12-2. Typical Control Software Structure

161
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

I/A Series System

Control Station
(Fault-Tolerant)
10 Mbps (10Base2)
Ethernet Trunk Fieldbus
(REDUNDANT)

10BASE2 OPTIONAL FIBER OPTIC

TO FIBER EXTENSION OF THE
CONV. Ethernet Trunk Fieldbus

FIBER
OPTIC 10 Mbps (10Base2) Ethernet Trunk Fieldbus (REDUNDANT)
CABLING
FIBER TO To Additional, Similar
10BASE2 Equipment Groupings
CONV. (If Applicable)

F F 2 Mbps F F 2 Mbps
C C Module fieldbus C C Module fieldbus
M M (Shielded Twisted- M M (Shielded Twisted-
10 10 Pair and/or Fiber 10 10 Pair and/or Fiber
E E Optic cabling) E E Optic cabling)

F F F F F F
B B B B B B
M M M M M M

Baseplate-Mounted equipment Baseplate-Mounted equipment

DIN Rail Mounted FBMs (FBM201, FBM202,

etc.) Up to 30 Per FCM10E PAIR

Figure 12-3. Typical CP60 and Fieldbus Communications Modules Interface

I/O Fail-safe Strategy

Non-Ladder Logic FBMs use one of two strategies for obtaining output values:
♦ Normal strategy, in which the FBM uses the outputs received from the CP, as deter-
mined by the application software.
♦ Fail-safe strategy, in which the FBM uses outputs from its gate array registers. The
gate array registers contain:
♦ The current value for each of the FBM’s outputs
♦ A fallback value for each of the FBM’s outputs
♦ A hold/fallback bit for each output, to specify which of the two values each output
will take.
Fail-safe is an FBM hardware logic state, designed to provide I/O security. This section describes
the events that place the FBM in the Fail-safe state, and the actions of the FBM while in the Fail-
safe state.
FBM fail-safe strategies are implemented by both software and hardware. The state of fail-safe is
indicated by the LEDs (RED/GREEN) on each FBM.

162
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Whenever the RED LED is on, the I/O hardware has asserted Fail-safe. If the software is asserting
fail-safe, the LEDs are unchanged in legacy FBMs or the GREEN LED is blinking in DIN FBMs.

Cold Start
(RED LED)
When the FBM is first powered up, the FBM firmware writes zeroes to the gate array registers and
places the FBM in its Fail-safe state. Since all the hold/fallback bits equal 0 (Fallback) and each
fallback value equals 0, each output is at its de-energized value of 0, waiting for the FBM to go
on-line.

Placing the FBM On-Line

(RED/GREEN LED)
When the application software takes control it:
♦ Reads all the gate array registers
♦ Computes the current value of each I/O point
♦ Writes the current value into the Current Value register.

FBM Exits the Fail-safe State

(Solid GREEN LED)
When the FBM receives the write message, it exits the Fail-safe state and:
♦ turns the RED LED to solid GREEN if it is on or
♦ turns the blinking GREEN LED to solid GREEN.
In this state, the control strategy is sending its outputs to the FBM.
At this point, the application software maintains control until some event disrupts that control
and forces the FBM to Fail-safe.

The Fail-safe Configuration

The CP, as part of I/O hardware initialization, writes the ECB fail-safe configuration from the
ECB to the FBM gate array registers. For example, the CP implements the Fail-safe configuration
by writing the following type 02 ECB parameters to a type 04 FBM:

FSMM02 Fail-safe Main Mask, ECB type 02 – provides the four bits to the
hold/fallback register that determine how the four output channels (05,
06, 07, and 08) respond during Fail-safe. If the bit = 1, the output goes to
hold and takes its value from the current value register. If the bit = 0, the
output goes to fallback and assumes the value from the fallback register.
FSMM02 is digitally coded as follows:

Table 12-1. FSMM02 Coding

Bit number 7 6 5 4 3 2 1 0 (LSB)

Channel number 08 07 06 05 xx xx xx xx

163
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

If, for example, channel 05 is to assume the fallback value in FS5D02

while channels 06, 07, and 08 hold their current value, then FSMM02
must = decimal 224, or hexadecimal E0 (bits 7, 6, and 5 = true).

FS5D02 Fail-safe, channel 5 Data, ECB type 2 – the fallback value for the channel
5 output is written to the fallback value register.
The value represents the D/A raw count and must be related to the
intended signal conditioning. For example, if this output is going to a
4-20 mA device (raw count range: 12,800 to 64,000) then FS5D02 must
be within that range.
FS6D02, FS7D02, and FS8D02, the fallback values for channels 6, 7, and
8 are likewise written to the fallback value register.
You should be especially careful when configuring the fail-safe mask and fail-safe values in ECBs
associated with redundant analog output FBMs. In addition to installing a special Termination
Cable Assembly (TCA) or Redundant Adaptor (RA), you must configure the ECB of each side so
that its FBM “fails low”. This is a constraint imposed by the hardware arrangement of the redun-
dant-type TCA or RA. Unless a failed FBM outputs 0 mA, the good side does not take over and
drive the output correctly. This implies that the fail-safe mask of each ECB must specify Fallback
for each channel, rather than Hold. The Fallback value must be 0 raw counts for each channel,
even if the normal low end of the output span is 12,800 raw counts, corresponding to 4 mA. The
following table summarizes the required ECB parameter values:

Table 12-2. Redundant Output Fallback Values

FBM ECB Mask Fallback Value

204 and 04 2 FSMM02 = 0 FS5D02 = 0, ... , FS8D02 = 0
205 and 05 2 FSMM02 = 0 FS5D02 = 0, ... , FS8D02 = 0
237 53 FSMM53 = 0 FS1D53 = 0, ... , FS8D53 = 0
06 4 FSMM04 = 0 FS5D04 = 0, ... , FS8D04 = 0
39 23 FSMM23 = 0 FS5D23 = 0, ... , FS8D23 = 0

Events Leading to Fail-safe

Some of the events that cause the FBM to go from control to the Fail-safe state include:
♦ FBM reboot
♦ Fieldbus Communications failure
♦ EEPROM update
♦ FBM taken off-line from the SMDH
♦ Power failure
♦ FBM restart.
The FBM response to each of these events is described below.

164
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

FBM Reboot
(Previously GREEN LED)
The FBM goes to the hardware Fail-safe state (RED LED) and the FBM outputs assume the Fail-
safe configuration until the FBM is back on-line and the application software resumes control
(GREEN LED).

Communications Failure (Commfail)

Fieldbus Communications Failure or CP Failure:
Two ECB parameters determine the if and when of a communications failure between the CP and
the FBM configured in that ECB.

FSENAB Fail-safe Enable is a boolean parameter that, when true, enables the
FSDLAY timer. If communications fail with FSENAB false, there is no
fail-safe activity: the FBM continues to drive the outputs using the current
values, which is equivalent to holding the outputs. The GREEN LED
remains on.

NOTE
FSENAB does not affect the hardware Fail-safe behavior. Setting FSENAB false
does prevent the FBM from going to the Fail-safe state because of a CP-to-FBM
communications failure, but it cannot prevent the FBM from going to Fail-safe for
any other reason.

FSDLAY Fail-safe Delay is a timer that, when enabled by FSENAB, specifies (in
units of 0.01 seconds) the length of time the FBM waits for a communica-
tion from the CP before entering a Commfail or software Fail-safe state
(in which outputs are under hardware control). This state asserts the out-
put values specified by the fail-safe (solid RED LED) configuration.
Example:
The default value of 1000 causes the FBM to wait 10 seconds between CP
communications before going to the Fail-safe state, if FSENAB is set true.
The ECB parameter FSOPTS is the Fail-Safe Option and is a configurable option that specifies
the fail-safe conditions and action to be taken in an FBM for an output point in a ROUT block.

EEPROM Update
(Alternately flashing RED and GREEN LEDs)
The FBM goes to the Fail-safe state and the FBM outputs assume the Fail-safe configuration
defined by the gate array registers prior to the EEPROM update. The FBM maintains this defini-
tion until the EEPROM update is completed and the application software resumes control
(GREEN LED).

165
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

FBM Taken Off-Line From the SMDH

If the FBM is taken off-line from SMDH, the CP sends a message to the FBM as long as the
CP-to-FBM communications are good, shutting down the FBM. The FBM goes to the software
Fail-safe state (GREEN LED) and the outputs assume the fail-safe configuration values.
If the CP-to-FBM communications are bad, the FBM responds in one of two ways:
1. FSENAB is configured true. The FBM goes to software fail-safe state (solid GREEN
LED for FBMs, blinking GREEN LED for DIN FBMs) after the delay timer times
out, and the outputs assume the fail-safe configuration values.
2. FSENAB is configured false. The FBM, unaware of any communications breakdown,
continues to drive the outputs using the current values – essentially a Hold state (solid
GREEN LED for FBMs, blinking GREEN LED for DIN FBMs).

Power Failure (Powerfail)

FBM01 to FBM46 and Equivalents
When the main power fails, FBM outputs are de-energized (zero state) since it is the main power
that drives them. If the FBM has battery-backup, where the battery maintains the hardware fail-
safe configuration in the gate array registers, the LEDs are dark.
If main power returns while the FBM is still battery-backed, the FBM continues the fail-safe con-
figuration, now via the software. But if the main power returns after the backup battery dis-
charges, the fail-safe configuration is gone, and the FBM reverts to a Cold Start state.

FBM201 to FBM246 (DIN Rail Mounted FBMs and Equivalents)

When the main and secondary (if used) power fails, FBM outputs are de-energized (zero state)
since it is the main and secondary (if used) power that drives them. If main or secondary (if used)
power returns, the FBM reverts to a Cold Start state.

FBM Restart
(RED/GREEN to GREEN LED)
The manipulations associated with this state change do not bump the outputs. The outputs have
the values written to the gate array registers, by the application software, prior to transition to
restart. If the software was never run, the registers have the zero values received on power-up ini-
tialization, and the outputs are de-energized.
The application starts operation in the normal run state unless the transition is a battery-backed
powerfail recovery, in which case the state is “fail-safe because of powerfail”. If the CP then recov-
ers communications in less than “communication ride-through time”, logic in the CP recognizes
the event as a power glitch and suppresses the fail-safe transition.
All references to gate array hardware in the descriptions of fail-safe operations refer to non-Cluster
FBMs. In the case of Cluster I/O FBCs, the fail-safe masks and fail-safe fallback values are
retained in the data structures maintained by the FBP10 for each of the attached output type
FBCs.

166
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Fieldbus Scanning
Control Processor scan of a Fieldbus Module is performed on a per-FBM basis. For FBM01 to
FBM46, the Control Processor treats the Main digital type FBM and its Expansion Module as
one FBM when scanning the Fieldbus.
The ECB parameter, PERIOD, determines the period at which an FBM is scanned.
Fieldbus scanning of FBM data completes before block processing begins.
The Analog-type FBMs read in their Analog inputs every 10 ms, for purposes of integration,
independent of CP/Fieldbus scan intervals.

Fieldbus Integration Time

The FBM converts each analog input to a digital value within a time interval called the update
time, presently set to 25 ms.
The converted value at each update interval is summed and averaged over a specified time period
called the integration time or conversion time. This continuous integration technique provides a
filter time equal to the integration period.
A new value is available to the CP each update period. The value represents the average of all the
updated values over the last integration period.
The integration time should be twice the loop scan period for best resolution and most effective
anti-aliasing and filtering.

FBM201 to FBM205 and FBM211 to FBM213

Analog input FBMs use a fixed resolution of 15 bits for each analog input. The Resolution (RES)
parameter for each ECB allows you to select a RES value of 1 to 5 which selects the conversion
time of the input. Conversion Times of 50 ms, 100 ms, 200 ms, 500 ms and 1000 ms can be
specified for analog inputs. Specifying a longer conversion time gives more filtering by providing a
longer filter time constant.
Table 12-3 illustrates these time factors:

Table 12-3. FBM201 to FBM213 Integration Time Factors

Resolution Update Time Conversion Time RES Value

15 bits 25 ms 50 ms 5
15 bits 25 ms 100 ms 1
15 bits 25 ms 200 ms 2
15 bits 25 ms 500 ms 3
15 bits 25 ms 1000 ms 4

For example, for a 100 ms interval, a new analog value is converted every 25 ms. Each 25 ms sam-
ple is continuously averaged with the previous 25 ms samples over a 100 ms interval.
The higher 500 and 1000 conversion times are normally required for the fixed span thermocouple
and RTD applications to meet the wider temperature spans (FBM202 and FBM212 -
Thermocouple Input, and FBM203 and FBM213 - RTD Input). Lower conversion times
(50 ms, 100 ms, or 200 ms) may result in unreliable measurement values.

167
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

FBM01 to FBM05
Resolutions of 11, 12, 13, 14, and 15 bits can be specified for analog inputs. The greater the reso-
lution, the longer the conversion time. The Resolution (RES) parameter for each ECB allows you
to select a RES value of 1 to 5 which selects the resolution and integration time of the input. Spec-
ifying 15-bit resolution gives more filtering by providing a longer filter time constant.
Table 12-4 illustrates these time factors:

Table 12-4. FBM01 to FBM05 Integration Time Factors

Resolution Update Time Integration Time RES Value

11 bits 25 ms 50 ms 5
12 bits 25 ms 100 ms 1
13* 25 ms 200 ms 2
14 25 ms 500 ms 3
15 25 ms 1000 ms 4

* Default value for typical applications. 14-bit resolution is default for thermocouple and RTD
applications (FBM02 and FBM03).

For example, for a 12-bit specified resolution, a new analog value is converted to 12 bits every
25 ms. Each 25 ms sample is continuously averaged with previous 25 ms samples over a 100 ms
interval.
The higher 14-bit and 15-bit resolutions are normally required for the fixed span thermocouple
and RTD applications to meet the wider temperature spans (14-bit resolution is the default value
for FBM02 – Thermocouple Input and FBM03 – RTD Input). Lower resolutions (12 or 13 bits)
may result in unreliable measurement values.

Cluster I/O
The three Cluster I/O analog input modules (FBC01, FBC17, and FBC21) always provide 12-bit
resolution. No user options exist for Cluster I/O.

FBM Rate of Change Monitoring

FBMs containing analog input points perform rate-of-change checking on each such point by
using the configured ECB parameters ROCx, (ROCV in the RIN block for HART FBMs) where
x = 1, 2, ... The value of ROCx is the maximum rate of change for that channel, expressed in units
of normalized raw counts per 100 milliseconds. If the input changes by more than that amount in
100 milliseconds, the channel status is marked Bad.
The default value of zero for any ROC parameter inactivates rate-of-change checking for that
channel. (For ECB34 and 36, the parameters are labelled ROC1MD through ROC4MD. Cluster
I/O analog inputs do not have rate-of-change checking.)

168
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

FBM and FBC Types

Digital-type FBMs can execute four different applications or software types selected by configur-
ing the software type of ECB during System Configuration/Definition or Integrated Control
Configuration. These are:
♦ Digital Input/Digital Output
♦ Ladder Logic (LL)
♦ Sequence of Events (SOE)
♦ Pulse Counters (PC).
You must select how a digital-type FBM is to function. It can operate in the Ladder Logic mode,
or in the Sequence of Events mode, or in the Pulse Counter mode, or in the Digital Input/Digital
Output mode, but it cannot combine modes. Cluster I/O FBCs of the digital type (FBC07,
FBC09, and FBC10) operate only in the Digital Input/Digital Output mode.
Digital inputs can always be read by the CP as independent inputs, even though LL, SOE, or PCs
are executing in the FBM.
More than one type of I/O block can be connected to an FBM or FBC.
An FBM or FBC is identified by a user-defined, physical device ID label. This device ID label,
referred to as the “letterbug”, is used to relate the ECB to a specific FBM or FBC.
For a complete list of FBMs, see Appendix C “FBM – ECB Cross Reference”.

Equipment Control Blocks (ECBs)

When you configure an FBM, the System Configurator/Definition creates a file with the appro-
priate ECB (software) types, which is used by the Integrated Control Configurator (ICC). Use the
ICC’s FBM Fix All function or the Insert Block/ECB function to add the ECB to the control
database and to specify or modify the parameter values for this added ECB.

Table 12-5. Equipment Control Blocks

ECB Number Description

ECB01 Analog Input
ECB02 Analog Input and Analog Output
ECB03 TDC2000 Bipolar Thermocouple Multiple Range Calibration Support
ECB04 Pulse In and Analog Output
ECB05 Digital In, Sustained/Momentary, and Digital Out
ECB06 Sequence of Events Input
ECB07 Digital In and Pulse Count Input
ECB08 Ladder Logic
ECB09 Analog I/O, Digital I/O
ECB11 Reserved for Primary FBM
ECB12 Intelligent Transmitter 2 Interface (Parent)
ECB13 HTG Interface Unit
ECB18 Intelligent Transmitter 2 Interface (Child)

169
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

Table 12-5. Equipment Control Blocks (Continued)

ECB Number Description

ECB22 Coriolis Mass Flow Transmitter
ECB23 Intelligent Field Device and Analog Output
ECB34 MDACT Feedback Lag, Tri-State
ECB36 MDACT Pulse Width, Tri-State
ECB38R Intelligent Field Device In and Analog Out, Dual Baud Rate, Redundant
AMSPRI (ECB39) Gas Chromatography Interface
ECB41 Analog Input, Cluster I/O
ECB42 Digital Input, Cluster I/O
ECB43 Analog Output, Cluster I/O
ECB44 Digital Output, Cluster I/O
ECB46 Digital I/O, Cluster I/O
ECB47 FBP10 Cluster I/O Interface
ECB47R FBP10R ECKARDT Migration
ECB48R Redundant SPECTRUM UCM
ECB52 DPIDA Interface
ECB53 Analog Output
ECB73 FoxCom™
ECB110 FCM Variants
ECB200 Distributed Control Interface (DCI) – FBM
ECB201 Distributed Control Interface (DCI) – Device
ECB202 HART and Modbus Communication Redundant FBM ECB

The ECB types listed in Table 12-5 that interface to FBMs, FBCs or other stations, include the
ECB Primary (ECBP). An ECBP is associated with each Control Station and specifies Fieldbus
communication parameters (for example, bus switching and watch dog timer).
You can establish the ECB type during System Configuration/Definition when you select the
FBM Hardware/software type, or specify it when executing the ICC Insert Block/ECB function
to add the ECB. When adding an ECB in the ICC, you must specify the ECB type first, then
define its hardware and software type.
For a list the ECB Assignments by System Configurator/Definition, see Appendix C “FBM –
ECB Cross Reference”.
FBMs 12a, 12b, 13, 14a, 14b, 14c, 14d, 15, 16, 21, 25a, 25b, 25c, 27a, 27b, 42a, and 42c are all
I/O Extenders. They have no software type of their own. They interface to the I/O blocks
through the ECB of the main FBM.

170
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Diagrams – ECB Interfaces to I/O Blocks and FBMs or

FBCs
This section uses a series of interface diagrams to show the relationship of the ECBs to the I/O
blocks at the Control interface; and to the FBMs or FBCs at the Process interface. The diagrams
in this section do not represent the complete list. Rather, the diagrams are provided as examples.
Each diagram shows all the I/O blocks and all the FBMs or FBCs that connect to the ECB in the
center of the diagram. The FBM01 to FBM46 Diagrams are arranged by ECB number except for
ECB18 which is shown as a part of the ECB12 diagram.

Sample DIN Rail Mounted FBM Diagrams

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE

ANALOG IN ANALOG IN/OUT

FBM201 AIN
AIN FBM202 FBM204
FBM203 AINR ECB2 FBM205
ECB1
FBM211
MAIN FBM212 AOUT
FBM213
AINR AOUTR

DI, S/M, DO
PULSE INPUT
CIN
MCIN FBM207
AINR COUT FBM217
ECB4 FBM206 MCOUT FBM219
MAIN ECB5 FBM241
FBM241b
MTR
FBM241c
MOVLV
FBM241d
VLV
FBM242
GDEV

LADDER LOGIC
FBM207 ANALOG OUT
FBM217 AOUT
FBM219
PLB
FBM241
ECB53 FBM237
FBM241b
CIN ECB8
FBM241c
FBM241c AOUTR
MCIN FBM242

Figure 12-4. DIN Rail Mounted FBM Connections to ECBs 1, 2, 4, 5, 8 and 53

171
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

I/O BLOCK ECB ECB FBM H/W

TYPES TYPE TYPE TYPE

IIN

RIN
ECB201 ECB200 FBM214
RINR

STRIN

Figure 12-5. FBM214 and 216 Connections to ECB200 and ECB201

I/O BLOCK ECB ECB FBM H/W

TYPES TYPE TYPE TYPE

IIN

RIN
ECB201 ECB200 FBM215
STRIN

ROUT

Figure 12-6. FBM215 and 218 Connections to ECB200 and ECB201

I/O BLOCK ECB ECB FBM H/W

TYPES TYPE TYPE TYPE

BIN

BINR

BOUT FBM220
ECB201 ECB200
FBM221
RIN

RINR

ROUT

Figure 12-7. FBM220 and 221 Connections to ECB200 and ECB201

172
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

I/O BLOCK ECB ECB FBM H/W

TYPES TYPE TYPE TYPE

IIN

IOUT

BIN

BINR

BOUT

RIN

RINR ECB201 ECB200 FBM223

ROUT

STRIN

STROUT

PAKIN

PAKOUT

PLSOUT

Figure 12-8. FBM223 Connections to ECB200 and ECB201

173
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

I/O BLOCK ECB ECB FBM H/W

TYPES TYPE TYPE TYPE

IIN

IOUT

BIN

BINR

BOUT

RIN ECB201 ECB200 FBM224

RINR

ROUT

PAKIN

PAKOUT

PLSOUT

Figure 12-9. FBM224 Connections to ECB200 and ECB201

174
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

AIN*

PNT
MEAS
REALM REALM
or PID or
MEALM MEALM
OUT or
Optional Real (REALM) Optional Real (REALM)
or Measurement (MEALM) or Measurement (MEALM)
Alarm Block Alarm Block
AOUT**
To Displays and
Maintenance or
Data Collection
ECB74 ECB18

* The AIN block is only needed

in configurations in which you wish
ECB73 to incorporate filtering (for example,
for Intelligent Transmitters which
require signal conditioning).
FBM243
** AOUT block is necessary to
characterize the output signal
IT to the Intelligent Positioner
(requires SCO = 14)

Water

Intelligent Positioner Intelligent Transmitter

Figure 12-10. Typical FBM243 and ECB73 Configuration

175
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

AIN*

PNT
MEAS
REALM REALM
or PID or
MEALM MEALM
OUT or
Optional Real (REALM) Optional Real (REALM)
or Measurement (MEALM) or Measurement (MEALM)
Alarm Block Alarm Block
AOUT**
To Displays and
Maintenance or
Data Collection
ECB74 ECB18

* The AIN block is only needed

in configurations in which you wish
ECB38R to incorporate filtering (for example,
for Intelligent Transmitters which
require signal conditioning).
FBM246
** AOUT block is necessary to
characterize the output signal
IT to the Intelligent Positioner
(requires SCO = 14)

Water

Intelligent Positioner Intelligent Transmitter

Figure 12-11. Typical FBM246 and ECB38R Configuration

176
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Sample FBMxx & Equivalents and FBC Diagrams

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE
ANALOG IN ANALOG IN/OUT
1
AIN AIN
ECB1 2
4
3 AINR ECB2
MAIN 5
3A
3B
AOUT
AINR 33
AOUTR
36
DI, S/M, DO
PULSE IN / ANALOG OUT
CIN 7,7A,7B,H7 12A, 12B
MAIN MCIN 8, H8 13
COUT 9,9A,9B, H9 14A, 14B
AIN MCOUT 10 14C, 14D
11 15
ECB5 20 16
ECB4 6
AINR 24A, 24B 21
MTR 24C 25A, 25B
MOVLV 26A, 26B 25C
AOUT VLV 26C 27A, 27B
GDEV 41A, 41C 27C
AOUTR 42A, 42C
MAIN EXPANDER

SEQUENCE OF EVENTS DIGITAL IN / PULSE COUNT OUT

7A 12A AINR 7A 12A

7B 12B 7B 12B
EVENT AIN

8 13 MAIN 8 13
CIN ECB6 ECB7
20 21 CIN 20 21
MCIN MCIN
24A 25A 24A 25A
24B 25B GDEV 24B 25B
24C 25C 24C 25C

Figure 12-12. Connections to ECBs 1, 2, 4, 5, 6, 7

177
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE

AI/AO/DI/DO
LADDER LOGIC 7, 7A, 7B 12A, 12B
AIN
8 13 17A
AOUT
PLB 9, 9A, 9B 14A, 14B 17B
CIN
10 14C, 14D 17C
COUT
11 15 17D
CIN ECB8 20 16 ECB9
24A, 24B 21
MTR
24C 25A, 25B
MCIN MOVLV 22
26A, 26B 25C
27A, 27B VLV
26C
27C GDEV
41A, 41C
42A, 42C
AINR
MAIN EXPANDER

AOUTR

IT2 INTERFACE HYDROSTATIC TANK GAUGE

(PARENT)
AIN ECB12 FBM18 AIN
23
AINR ECB13
AINR (HIU)
ECB18 IT2 MCIN
(CHILD)
MAIN MAIN
ECB18 IT2
(CHILD)

DISPLAY STATION INTERFACE

DSI ECB14 DS

ALLEN-BRADLEY PLC INTERFACE MODICON PLC INTERFACE

A/B COMM MODICON
ABSCAN ECB15 ADAPTER MDSCAN ECB16
MODEM

Figure 12-13. Connections to ECBs 8, 9, 12, 13, 14, 15, 16, 18

178
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE

760 CONTROLLER INTERFACE FOREIGN DEVICE INTERFACE

D760 ECB19 760 FDBIN

CONTROLLER FDIIN
FDRIN
ECB20 FOREIGN
761 CONTROLLER INTERFACE DEVICE
FDBOUT
761 FDIOUT
D761 ECB21
CONTROLLER FDROUT

MASS FLOW TRANSMITTER IT2 IN / ANALOG OUT

38 AIN
AIN ECB22
(CORIOLIS)
AINR ECB23 39

AINR
AOUT

MAIN
AOUTR

MAIN

Figure 12-14. Connections to ECBs 19, 20, 21, 22, 23

179
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE
MDACT FEEDBACK LAG MDACT PULSE WIDTH
17A 17A
MDACT ECB34 17B MDACT ECB36 17B
17C 17C
GDEV 17D GDEV 17D

MTR MTR

MOVLV MOVLV

VLV VLV

COUT COUT

CIN CIN

AIN AIN

AOUT AOUT

AINR AINR

AOUTR AOUTR

IT2 INTERFACE (DUAL BAUD RATE) IT2 IN / ANALOG OUT (DUAL BAUD RATE)

MAIN MAIN

ECB12 AIN
AIN 43
ECB73
AINR
ECB23 44
AINR

AOUT

AOUTR

Figure 12-15. Connections to ECBs 12, 23, 34, 36

180
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE
IT2 IN / ANALOG OUT
(DUAL BAUD RATE, REDUNDANT)
DPIDA INTERFACE

MAIN 4
DPIDA ECB52 17
AIN 22
37

AINR ANALOG OUT

ECB38R 46
AOUT
AOUT
ECB53 37
AOUTR
AOUTR

Figure 12-16. Connections to ECBs 38R, 52 and 53

181
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

Sample FBC Connection Diagrams

I/O BLOCK ECB FBM H/W I/O BLOCK ECB FBM H/W
TYPE TYPE TYPE TYPE TYPE TYPE

ANALOG IN (CLUSTER I/O) DIGITAL IN (CLUSTER I/O)

AIN FBC21 CIN

ECB41 FBC01 ECB42 FBC07

MCIN
MAIN
FBC17
GDEV
FBC02
AINR

ANALOG OUT (CLUSTER I/O) DIGITAL OUT (CLUSTER I/O)

AOUT ECB43 FBC04
VLV

COUT
AOUTR
GDEV
ECB44 FBC09
MOVLV

MTR

MCOUT

DIGITAL IN/OUT (CLUSTER I/O)

CIN

MCIN

COUT
ECB46 FBC10
GDEV

MOVLV

MTR

VLV

MCOUT

Figure 12-17. Connections to ECBs 44, 46, 52, and 53

182
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Window Equipment Control Blocks

Window Equipment Control Blocks (window ECBs) provide an extended communications inter-
face between the I/A Series System and Intelligent Field Devices (IFDs), the next generation of
field devices. IFDs, as their name implies, incorporate intelligence at the hardware device level,
such as signal conditioning and even process control, and so require a new software interface. This
interface is the Window ECB, which integrates IFDs into the I/A Series System while providing
access to the IFDs extended capabilities.
Window ECBs are device-specific and will grow in number as the number of IFDs increases.
This section discusses:
♦ General Window ECB Concepts
♦ Individual Window ECBs
The following table lists the current Window ECBs and the specific devices they support.

Table 12-6. Window Equipment Control Blocks

Window ECB Supported Device

ECB18 The 820 Series and 860 Series Intelligent Transmitters and Vortex Meters
ECB22 Mass Flow Transmitter
ECB13 Hydrostatic Tank Gauge Interface Unit
ECB47 Cluster I/O FBP10 Communications Interface
AMSPRI 931D Process Gas Chromatograph

General Window ECB Concepts

Overview
Because IFDs are intelligent devices, the model of the FBM (hardware) and ECB (software) pro-
viding the device interface to the CP no longer holds in exactly the same way. Many of the func-
tions performed by CP blocks, such as signal conditioning and translation to engineering units,
may now be performed by the IFD. Accordingly, the software interface to the IFD, which the
window ECB provides, requires both less and more support from the CP. Some IFDs connect
directly to an FBM, others, to an intermediary device.
On the one hand, many of the functions previously performed by ECB and I/O blocks are now
performed directly by the device. Thus, many signals require only appropriate pass through to the
I/A Series System to be integrated into the control context. On the other hand, because the
devices themselves offer more configuration and reporting capabilities, the software interface
between the I/A Series System and the device must now make these capabilities accessible from
the CP. Thus, window ECBs perform two basic functions:
♦ The Window ECB offers access to IFD inputs and outputs as I/A Series System
parameters, allowing inputs to be set for simulation purposes and connected directly
to I/A Series System blocks, including control (for example, PIDE) and alarm (MSG,
STALM, and MEALM) blocks.

183
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

♦ The Window ECBs, through an extended, graphically-based interface—namely, the

window—provide access to the IFD’s sophisticated, on-board capabilities, ranging
from minimal amounts of device configuration to device-specific functions that go far
beyond the management of control-related contact points.
The following subsections detail general Window ECB capabilities and requirements.

Configuration
Window ECBs operate directly on the device for configuration. Configuration parameters are of
two types. The first group representing essentially non-dynamic data specifies the operation of the
window ECB, for example, period, phase, and source connections for outbound process data.
These parameters are configurable through the Integrated Control Configurator in the same way
as parameters of standard blocks.
The second group of parameters represents dynamic, real time data, usually measurements or sta-
tus information (the parameter names and data types vary with each window ECB). These param-
eters are normally not settable, since they reflect current device values. However, a special BYPASS
switch allows for simulation setting.
To support device-specific alarm functions, window ECBs can be connected to other blocks, such
as STALM, MEALM, and MSG.

Installation
The window ECB presents the device as a group of I/A Series System parameters, providing access
to device-specific parameters, but also thereby integrating device outputs into the generic parame-
ter interface demanded by the I/A Series Control System. Accordingly, all window ECBs, regard-
less of device, follow the same overall design. The following description of the generic window
ECB also serves as a narrative of how the window ECB is installed, made active, operates, and is
shut down.

Validation
Window ECBs validate themselves only regarding normal connection. Device parameter valida-
tion is, for IFDs, device-resident and thus will take place prior to connection.

Initialization
Initialization is invoked as part of the PIO Maintenance task based upon the generic flag request
mechanism. Initialization performs two basic functions:
1. The initialization required by the window ECB’s processes (the connected dynamic
data). This initialization is executed before any other ECB code, allowing resetting the
ECB history of the previous cycle states.
2. The initialization of non-dynamic data by directly reading the device.
During initialization, all parameters are marked OOS (out of service), and remain OOS until the
first input/output scan.
The trigger event for start up initialization is the ECB off-line to on-line transition. Upon com-
pletion, the static data upload function triggers the update of displays and other processes depen-
dent on the data. Device-specific window ECBs provide for multiple trigger events for complete
and partial re-initializations at times other than start up; for example, device reconfiguration and
communication failures (see the individual window ECBs for details).

184
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Real Time Input Points

To provide real time input points, window ECBs present device values as I/A Series System
parameters of the appropriate type. Window ECBs thus include a portion of the functionality
usually provided by CIN and AIN blocks. In addition, window ECBs support simulation and
hardware testing.
The window ECB for Cluster I/O (ECB47) does not contain any real time input or output point
data. This dynamic data is contained in the ECBs for the separate FBCs attached to the cluster,
and these ECBs are not treated as window ECBs. ECB47, which serves the cluster’s communica-
tion interface, the FBP10, is considered a window ECB since it is treated as such by System Man-
agement and the CP I/O scan logic. The information in this section and the section on Real Time
Output Points does not apply to the ECB47 window.

Input Point Parameters

Each window ECB input point is associated with three parameters, DEVICE_VALUE,
POINT_VALUE, and BYPASS.
DEVICE_VALUE is always secured, since the value can be updated only from the device and
thus cannot be overwritten if data flow is interrupted. If the device can supply “bad” values, the
input point must have a “last good value” parameter (see below).
POINT_VALUE is the value to which the control strategy connects. Its behavior is controlled by
the BYPASS parameter.
The BYPASS parameter is a single bit of a packed boolean or packed long parameter. By default, it
is set to Off, which enables direct copying of DEVICE_VALUE to POINT_VALUE, to be
updated every input cycle. When simulation is required, however, you can set BYPASS to On,
and enable manual setting of the POINT_VALUE. The point’s DEVICE_VALUE parameter
continues to reflect the real time value from the device, and is immediately copied to
POINT_VALUE upon turning BYPASS off.
The “last good value” parameter is required if (and only if) the device can supply “bad” values. It
is a packed boolean or packed long configurable parameter.

Input Point Scanning

Input points are updated through real time input scanning based on the window ECB’s period
and phase parameters. The scanning first sends data requests to the device, then processes the
communication responses from the device to update the input point parameters.
Updating a window ECB input point requires the simultaneous update of related status parame-
ters, to be consistent with I/A Series System Control conventions. The following parameters
ensure compliance:
♦ OM on scan, which is true unless the value is a sink for a broken or invalid
connection.
♦ ON control, which is always true unless the window is Off.
♦ OOS (Out-Of-Service), set in all cases when fresh data is not available (for example,
communication interruption, during initialization, window Off).
♦ BAD, which implies a fault or error condition.
♦ ERROR, which indicates a problem with the upstream data required to compute the
value.

185
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

Real Time Output Points

The control system acts by manipulating output points for data that are sent to the device. The
output points are, however, more than the result of a conversion to the device’s signal conven-
tions. Rather, they are one of the means whereby the I/A Series System implements its control
strategy, for events ranging from state transitions such as initialization to communication failures
and field device state changes.
Accordingly, the functionality associated with a point can range from a switch toggled from a pro-
cess operator display to a set point fed from a complex cascade. The former, a simple settable out-
put, is implemented with a single shadow parameter. The latter requires all the elements of the
I/A Series System cascade interface, including connection points for the cascade’s INITI,
BCALCI inputs and support for the PRIBLK handshake.

Output Point Parameters

The following parameters support this wide range of output point functions:
♦ Device output point, a shadow parameter that associates two values with the same
name: a current field value and a hidden, “in-transit” write value.
♦ Control output point, the device output point’s point value parameter, to enable test,
simulation, and reconfiguration.
♦ R/L switch, to enable remote and local connections for output manipulation.
♦ Upstream BCALCI support, provided by the shadow parameter point in simple cases
and a device-supported parameter for complex cases, to be called BCALCO only in
this case.
♦ Upstream INITI support, expected to be connected to INITO, if any controller is to
be connected upstream.
♦ The PRIBLK handshake, to ensure that the output value has been computed before
being output. A per-point enable is required in multiple point contexts.

Output Point Scanning

As with input point scanning, a first phase constructs the outbound messages to the device, the
second phase interprets and acts on the replies. The write operation is the inverse of the data
transformation performed by input scanning. The model for state definition and transition logic
requirements is the AOUT block, which is the point of reference for the window ECB output
point parameters.
Initialization allows for outputs to be read back.
In the updating of shadow parameters the read half of the parameter is to be updated at the proper
control point in cases of communication failure. In such cases, the value waiting to be written
back cannot necessarily simply be kept.
Device status requirements ensures the output value is “good” before being sent to the device, in
cases where the device does not itself perform validation.

Commfail Issues
For IFDs, communication failures must be handled by the device, since all the I/A Series System
can do is create alarms once communication has failed.

186
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Shutdown
The trigger event for shutdown is the SMDH off-line action. It is functionally similar to turning
off a compound: the window ECB goes OOS and real time scanning of the device is shut down.

Alarming
The I/A Series System supports two families of alarms: process alarms and system alarms. Process
alarms highlight process conditions; system alarms report exception conditions relating to the
control system itself. IFDs, which include both diagnostic logic to report hardware faults and
application-level intelligence recognizing process exception conditions require both process and
system alarms.
Alarm blocks—STALM, MEALM, and MSG—provide I/A Series System support for device-res-
ident alarms, by converting the device’s detection of alarm conditions into a parameter interface
to the I/A Series System.

Device States and Status

The ECBSTA parameter is designed to coordinate control actions with device states and status for
IFDs, whose device states are often complex.
The ECBSTA parameter has two portions, a generic control status section and a device-specific
section. The device-specific portion is defined by each particular window ECB.
The generic portion of ECBSTA provides information in three basic categories: window, device,
and data flow. Each is mutually exclusive and inherently hierarchical.

Window States
A window has two states, On and Off. Transitions are triggered by SMDH on-line and off-line
actions.
Off shuts down all mechanisms associated with the window. All parameters are marked OOS.
Existing values are left unchanged. Where appropriate, output parameters are released.
On turns on all mechanisms associated with the window. With the window state on, the device’s
functions are part of the user’s real time control strategy. The device state must be ON_SCAN.

Device States
Devices have five explicit, mutually exclusive states. A sixth state, OFF, follows from the OFF
window state.
1. ON_SCAN, which is the device state that supports real time control. In the
ON_SCAN state, device parameters can be used by the I/A Series System.
2. COMM_FAIL, which is entered when communication fails and left when communi-
cation is resumed. In this state, window points are BAD and OOS.
3. DEVICE_FAILED, which is entered when the device reports a fatal hardware fault or
other fatal error condition, except a communication failure.
4. DEVICE_NOT_READY, which is the transition state, as in normal start-up.
5. DEVICE_OOS, a transition state set by the operator or other external control. The
device is healthy, but not to be used for its normal functions.

187
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

Data Flow Indicators

In the case of data flowing up from a device, the status section of the ECBSTA parameter provides
all necessary information for control and display purposes.
For data flowing down to the device, status alone does not suffice. To account for per-point status,
there is a packed boolean OUTSTA parameter. Each output point is assigned two bits. The first
bit, when set, indicates data is being held by the window I/A Series System output interface logic.
The second, when set, indicates that the output is not writable at the device level. OUTSTA is
marked OOS if the device is not ON_SCAN.

Additional Status Indicators

These are window-level device interface properties:
1. Window Configuration Error, which indicates an invalid parameter connection, indi-
cated in the ECBSTA parameter.
2. Initialization Complete, which indicates that the window’s support data from the
device is complete.
3. Simulation Active, which indicates that the window ECB is in simulation mode.
4. Bypass Active, which is set if any of the window BYPASS switches is set (it is the OR
of all per-point window BYPASS switches).
5. Output Point Open, which is set if any of the point OUTSTA parameters is set (it is
the OR of all window point OUTSTA parameters).
6. Fail-safe, which indicates that the device considers that I/A Series System control has
failed and is controlling I/A Series System outputs to itself.

Individual Window ECBs

Individual window ECBs conform to the general window ECB design presented earlier. This sec-
tion discusses conceptual features specific to the each window ECB.

The Hydrostatic Tank Gauge ECB (ECB13)

The Hydrostatic Tank Gauge ECB (HTG ECB) is the I/A Series System software window onto
the Intelligent Field Device Hydrostatic Tank Gauge Interface Unit (HIU). See Integrated Control
Block Descriptions (B0193AX) for complete information on the HTG ECB.

Overview
The HTG ECB dynamic data consists of up to 24 tank measurements and 9 status inputs. Non-
dynamic data includes alarm set points, I/O names, system select parameters, and maintenance
data (letterbug, alias, etc.). A default I/A Series System display with several levels of detail can be
used. A group of HTGs can be supervised through a Tank Farm display.
The HTG ECB does not generate process alarms, but provides the output parameters for other
blocks to generate them. Selected alarm set points can be adjusted by the operator through the
window ECB display without entering the IFD environment. An HTG support compound is
provided. A typical, full-featured HTG support compound consists of 13 Measurement alarm
blocks, 14 state alarm blocks, and a variable number of message blocks.
HTG ECB options include a security feature for selected actions, and last good value retention.

188
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

HTG ECB Default Displays

The default display allows the user to set the following HIU parameters:
♦ Inbound/Outbound Movement allowed/not allowed
♦ Mass Deviation Alarm and Unauthorized Movement Alarm enable/disable
♦ Density Rate of Change Alarm enable/disable
♦ Flow Rate Alarm enable/disable
♦ Flow Rate Alarm set points (HI/LO).
Hardware faults reported in the display include:
♦ Calibration error
♦ Database error
♦ Sensor Power Lost
♦ Pressure P1, P2, or P3 Lost
♦ Temperature T1, T2, or T3 Lost
♦ RTD Lost
♦ Enclosure Temperature Lost
♦ Level Mismatch.
See Integrated Control Block Descriptions (B0193AX) for a complete list of the HTG ECB
parameters.

Installation and Configuration

The HTG ECB performs no validation on configurable parameters. Initialization proceeds as for
window ECBs in general. HIU response messages are validated as received and then written to the
parameters. The upload from the HIU increments the ECB ACHNGE parameter, which triggers
the update of all dependent processes, in particular the display.

Real Time Inputs

Real time input points consist of the following 24 process variables (measurements) plus one
packed boolean:
♦ Net mass
♦ Gross mass
♦ Net volume
♦ Gross volume
♦ Available volume
♦ Level
♦ Density
♦ Reference density
♦ Liquid temperature
♦ Time to fill
♦ Air density
♦ Pressure (3 points)

189
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

♦ Flow rate
♦ Density rate change
♦ Vapor specific gravity
♦ Reference temperature
♦ Water level
♦ Auxiliary reference density
♦ Sensor temperature (3 points).
♦ One packed boolean for 5 HIU contact input point statuses.
The packed boolean input reports the status of 5 HIU contact input points.
The ECB outputs (from the ECB to the CP) are:
♦ 8 HTG status words (16 bits each, packed booleans)
♦ A channel status word (packed boolean)
♦ 25 alarm set points (real values)
♦ A Hardware Fault message string (a string)
♦ 8 engineering units (strings)
♦ Five contact names (strings).

Alarm Set Points

Alarm set points include:
♦ High-high levels
♦ High and low levels
♦ Liquid temperature high and low
♦ High and low density
♦ High and low water level
♦ High and low transmitter temperatures (1-3)
♦ High and low transmitter pressures (1-3)
♦ High and low product flow
♦ Rate-of-change of product density
♦ Mass deviation.

Real Time Outputs

Since the HIU has a completely self-contained control algorithm in its hardware, the only real
time output points (from the CP to the HTG ECB) consist of a subset of parameters which the
user can set from the display:
♦ ASSEL, a shadow output for the SEALM bit fields settable from the operator’s display
♦ ALMHFL, the high flow rate alarm limit
♦ ALMLFL, the low flow rate alarm limit.
The Output Scanner calls an ECB function to fill an output buffer and then sets the
NEED_OUTPUT. Upon a response from the HIU, another ECB function stores the actual
device values into the output ECB parameters.

190
12. Control Processor (CP)/Fieldbus Application Interface B0193AW – Rev R

Gas Chromatograph Window ECB (AMSPRI and AMSSEC)

The window ECB for the gas chromatograph (AMSPRI) provides 931D gas chromatograph anal-
ysis data and status information for direct input into the control scheme, simulation control, and
bad value detection. Optionally, secondary blocks (AMSSEC) can provide additional instrument
measurement and status data.
The AMSPRI provides up to 12 discrete data sets as inputs to the control scheme. Each data set
contains:
♦ A real value
♦ 8 user-configurable status conditions (packed booleans)
♦ An event strobe indicator.
The AMSPRI can also pass the following non-dynamic data:
♦ Up to 5 user-defined text strings for display enhancement
♦ Up to 12 user-defined strings for data set labels
♦ Identification information.
There are also 32 status conditions available to the control scheme for connection to alarm blocks.
The AMSPRI can also be connected to a secondary block (AMSSEC) for additional instrument
data and connections to alarm blocks.

Mass Flow Transmitter Window ECB (ECB22)

The Mass Flow Transmitter Window ECB (MFT ECB) receives up to 6 fully conditioned mea-
surements from the device each scan cycle for connection to the control scheme. Status condition
reporting, simulation control, and bad value detection are also available. A “last good value”
retention capability is optional.
Mass flow measurements include:
♦ Mass Flow
♦ Density
♦ Temperature
♦ Total
♦ Volumetric Flow
♦ Percent Solids.

Intelligent Transmitter Window ECB (ECB18)

The Intelligent Transmitter window ECB (IT ECB) receives up to three measurement values and
status conditions from the device for integration into the control scheme. ECB18 is internally a
window ECB interface to the ECB12 parent IT ECB directly accepting communication variables,
information parameters, and bypass switches.
From the IT ECB, operators can set upper and lower range levels for each input. Status conditions
are also available, for display and for optional connections to the control scheme. The IT ECB
supports both hardware fault reporting and bad measurement detection.
Optional features include marking primary measurements as bad when the temperature measure-
ment is out of range, and “last good value” retention.

191
B0193AW – Rev R 12. Control Processor (CP)/Fieldbus Application Interface

Cluster I/O Window ECB (ECB47)

The Cluster I/O modules are served by an FBP10 communications interface which uses an
ECB47 for its interface to the CP. This ECB is viewed as a parent from the point of view of Sys-
tem Management and CP input/output scanning, with the ECBs of the cluster modules consti-
tuting the children.
The ECB47 retains and reports various types of status information for the FBCs, as well as the
status of the FBP10 itself. The ECB47 does not contain any dynamic data; therefore, it does not
require Bypass and Last Good Value parameters.
Data contained in the ECB47 is of the following types:
♦ Scan control for the FBP10 as distinguished from that for the attached FBCs (period
and phase)
♦ Commfail-related parameters
♦ Status data for the FBP10, the FBCs in the cluster, and the ECB47 itself
♦ Option parameters related to the cluster as a whole (Fan/Power and Error Reporting)
♦ System Management related parameters such as UPLREQ and OPSTAT.

192
Appendix A. Signal Conditioning
Indexes
This Appendix defines the conversion algorithms for signal conditioning indexes. These are
optionally offered for both the AIN and MAIN block types. The inverses of some of these
algorithms are available for use in the AOUT and AOUTR blocks.

Input Signal Conditioning

Each Signal Conditioning Input (SCI) index specifies a particular conversion algorithm that con-
verts the raw count data value to a real floating point value in the specified engineering units span.
The following subsections group the signal conditioning indexes according to Foxboro product
offerings:
♦ Fieldbus Modules (FBMs)
♦ Micro-I/A software release 6.2.1 (or greater), Application Workstation 51 (AW51)
Integrator, and Application Workstation 70 (AW70) Integrator
♦ Micro-I/A pre-6.2.1 software releases, and the Allen-Bradley Station.

FBM Input Signal Conditioning

Characterizer tables are used to convert raw data from either an FBM202, FBM212, or FBM02
and FBM36 Millivolt I/O Modules (for thermocouple temperature measurements), or an
FBM203, FBM213, or FBM03 RTD I/O Module (for resistance temperature measurements).
Characterizer tables support various standard thermocouple and RTD sensor types for signal con-
version indexes in the range 20 through 39.
The thermocouple FBM provides a fixed millivolt range of -10.5 to 69.5 mV for 0 to 64,000
counts. The overall conversion resolution is 2.5 microvolts/count.
The RTD FBM provides a fixed resistance range of 0 to 320 Ohms for 0 to 64,000 counts. The
overall conversion resolution is 10 milliohms/count.
The engineering span is specified by the high scale and low scale parameters for the PNT output.
The high scale and low scale values correspond to the raw signal values of 64,000 counts and
0 counts, respectively. Note that the user may use the CHAR block extender to build custom
piecewise linear SCIs.

Linear and Nonlinear Signal Conversion (FBM)

SCI = 0: No Conditioning
converted_value = raw_value
SCI = 1: Linear 0 to 64000 raw counts
converted_value = (raw_value * (HSCO1 - LSCO1) / 64000) + LSCO1

193
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

SCI = 2: Linear 1600 to 64000 raw counts

converted_value = ((raw_value - 1600) * (HSCO1 - LSCO1) / 62400) + LSCO1
SCI = 3: Linear 12800 to 64000 raw counts
converted_value = ((raw_value - 12800) * (HSCO1 - LSCO1) / 51200) + LSCO1
SCI = 4: Square Root 0 to 64000 raw counts
converted_value = (SQRT(64000 * raw_value) * (HSCO1 - LSCO1) / 64000) +
LSCO1
SCI =5: Square Root 12800 to 64000 raw counts
IF raw_value <= 12800
THEN
converted_value = LSCO1;
ELSE
converted_value = (SQRT(51200 * (raw_value - 12800)) * (HSCO1 -
LSCO1) / 51200) + LSCO1;
SCI = 6: Square Root 0 to 64000 raw counts with low cutoff
IF raw_value <= 480
THEN
converted_value = LSCO1;
ELSE
converted_value = (SQRT(64000 * raw_value) * (HSCO1 - LSCO1) /
64000) + LSCO1;
SCI = 7: Square Root 12800 to 64000 raw counts with low cutoff
IF raw_value <= 13184
THEN
converted_value = LSCO1;
ELSE
converted_value = (SQRT(51200 * (raw_value - 12800)) * (HSCO1-
LSCO1) / 51200) + LSCO1;
SCI = 9: Linear 1600 to 64000 raw counts with low cutoff
IF raw_value <= 1600
THEN
converted_value = LSCO1;
ELSE
converted_value = ((raw_value - 1600) * (HSCO1 - LSCO1) / 62400)
+ LSCO1;
SCI = 10: Linear 12800 to 64000 raw counts with low cutoff
IF raw_value <= 12800
THEN
converted_value = LSCO1;
ELSE
converted_value = ((raw_value - 12800) * (HSCO1 - LSCO1) /
51200) + LSCO1;
SCI = 12: Linear 14080 to 64000 raw counts
IF raw_value <= 14080
THEN
converted_value = ((raw_value - 14080) * (HSCO1 - LSCO1) /
49920) + LSCO1

194
Appendix A. Signal Conditioning Indexes B0193AW – Rev R

SCI = 13: Square Root 14080 to 64000 raw counts with low cutoff
IF raw_value <= 14080
THEN
converted_value = LSCO1;
ELSE
converted_value = (SQRT(49920 * (raw_value - 14080)) * (HSCO1
- LSCO1) / 49920) + LSCO1;

Pulse Rate (FBM)

SCI = 8: Pulse Rate
SCI = 8, converts the incoming pulse rate raw value into the proper engineering units.
The FBM can measure a range of pulse rate frequencies from 1/(integration time) to the
maximum hardware limit of 25 kHz for FBM206 or 12.5 kHz for FBM06.
The integration time is a selectable FBM configuration parameter with the choices of: 0.1,
0.2, 0.5, and 1.0 seconds.
The chosen integration time affects the resolution of the FBM time base with correspond-
ing resolutions of 12, 13, 14, and 15 bits.
Also, the low cutoff pulse rate frequencies (fco) for the corresponding integration times
are 10 Hz, 5 Hz, 2 Hz, and 1 Hz, respectively.
A meter factor scaling constant (MTRF) is provided for the SCI 8 option. It can be used
to translate the measured pulse rate signal (Hz) to the desired rate measurement in the
chosen engineering units; for example, flow rate in gallons per minute.
Therefore, the possible span of the converted value can range between the low cutoff fre-
quency and the maximum FBM pulse rate frequency of 12.5 kHz.
MTRF has the units of the configured engineering units (EO) per Hz.
converted_value = MTRF * pulses_per_second (EO)
The assigned values for the output engineering range scale parameters, HSCO1 and
LSCO1, are not used during the conversion process, because the output span is not nor-
malized to the FBM’s conversion span. They are provided for display indication purposes
only, and are usually configured to represent the range of the measuring device; for exam-
ple, a flow meter. If the range of the measuring device is unknown, then they may be set to
the engineering units that correspond to the FBM’s conversion range, which ranges
between fco and 12.5 kHz; that is,
HSCO1 = MTRF * 12,500
LSCO1 = MTRF * fco

195
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

Thermocouples (FBM)
SCI = 20: Type B Thermocouple

Material : Platinum-Platinum
Range : 0 to 1820 deg C
Curve : P331-0/68 (TI 15-18a)

SCI = 21: Type E Thermocouple

Material : Chromel™-Constantan
Range : -270 to 910 deg C
Curve : S303-0/68 (TI 5-17c)

SCI 23: Type J Thermocouple

Material : Iron-Constantan
Range : -210 to 1200 deg C
Curve : S99J-0/68 (TI 5-12f)

SCI 24: Type K Thermocouple

Material : Chromel-Alumel™
Range : -270 to 1372 deg C
Curve : K223-0/68 (TI 5-13c)

SCI 25: Type N Thermocouple

Material : Nicrosil-Nisil
Range : -270 to 1300 deg C
Curve : IPTS-68 (TI 5-19)

SCI = 26: Type R Thermocouple

Material : Platinum-Platinum
Range : -50 to 1768 deg C
Curve : P329-0/68 (TI 5-14d)

196
Appendix A. Signal Conditioning Indexes B0193AW – Rev R

SCI = 27: Type S Thermocouple

Material : Platinum-Platinum
Range : -50 to 1768 deg C
Curve : P307-0/68 (TI 5-15e)

SCI = 28: Type T Thermocouple

Material : Copper-Constantan
Range : -270 to 400 deg C
Curve : S233-0/68 (TI 5-11c)

(FBM) Resistance Temperature Detectors (RTDs)

SCI = 40: Copper RTD (SAMA)

Material : Copper
Range : -70 to 150 deg C
Curve : CR-229 (TI 5-25a)

SCI = 41: Nickel RTD (SAMA)

Material : Nickel
Range : -100 to 160 deg C
Curve : NR-227 (SAMA) (TI 5-24a)

SCI = 42: Platinum RTD (100 Ohm DIN 43760-1968)

Material : Platinum
Range : 0 to 620 deg C
Curve : PR-238 (TI 5-26a)

SCI = 43: Platinum RTD (100 Ohm IEC) (DIN 43760-1980)

Material : Platinum
Range : -200 to 620 deg C
Curve : Foxboro drawing 10104MV (TI 5-28)

197
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

SCI = 44: Platinum RTD (100 Ohm SAMA)

Material : Platinum
Range : -200 to 600 deg C
Curve : PR-279 (SAMA) (TI 5-27a)

Standard Conversion Tables (for FBMs)

The following Foxboro Technical Information sheets (TIs) contain the standard conversion tables.

TI # Title
5-18a Thermocouple Temperature/mV Data For Platinum-6% Rhodium vs. Platinum-30%
Rhodium Thermocouples, Type B
5-17c Thermocouple Temperature/mV Data For Nickel-Chromium vs. Copper-Nickel
(Chromel-Constantan) Thermocouples, Type E
5-34 Electromotive Force vs. Temperature For PRC Thermocouple Curve EA-2
5-12f Thermocouple Temperature/mV Data For Iron vs. Copper-Nickel (Iron-Constantan)
Thermocouples, Type J
5-13c Thermocouple Temperature/mV Data For Nickel-Chromium vs. Nickel-Aluminum
(Chromel-Alumel) Thermocouples, Type K
5-19 Temperature-Electromotive Force (EMF) Tables For Type N (Nicrosil vs. Nisil)
Thermocouples
5-14d Thermocouple Temperature/mV Data For Platinum vs. Platinum-13% Rhodium
Thermocouples, Type R
5-15e Thermocouple Temperature/mV Data For Platinum vs. Platinum-10% Rhodium
Thermocouples, Type S
5-11c Thermocouple Temperature/mV Data For Copper vs. Copper-Nickel
(Copper-Constantan) Thermocouples, Type T
5-25a SAMA Copper RTD Temperature-Resistance Tables Curve CR-229
(Degrees C vs. Absolute Ohm) and Curve CR-228 (Degrees F vs. Absolute Ohm)
5-24a SAMA Type II Nickel RTD Temperature-Resistance Tables Curve NR-227
(Degrees C vs. Absolute Ohm) and Curve NR-226 (Degrees F vs. Absolute Ohm)
5-26a DIN Platinum RTD Temperature-Resistance Tables Curve PR-238 (Degrees C vs.
Absolute Ohm) and Curve PR-239 (Degrees F vs. Absolute Ohm)
5-28 ASTM* and IEC* Platinum RTD Temperature-Resistance Tables (Degrees C vs.
Absolute Ohm and Degrees F vs. Absolute Ohm)
5-27a SAMA 100 Ohm (Nominal) Platinum RTD Temperature-Resistance Tables Curve
PR-279 (Degrees C vs. Absolute Ohm) and Curve PR-278 (Degrees F vs. Absolute Ohm)

198
Appendix A. Signal Conditioning Indexes B0193AW – Rev R

SCIs for Micro-I/A Software Release 6.2.1 (or greater), AW51,

and AW70
The following SCIs apply to Micro-I/A, software release 6.2.1 or greater, the Application Work-
station 51 (AW51) Integrator, and the Application Workstation 70 (AW70) Integrator:
SCI = 0: No linearization; output = input
SCI = 1: Linear (0 to 64000) (“0 to 100%”)
SCI = 2: Linear (1600 to 64000) (“0 to 100%, Elevated Zero”)
SCI = 3: Linear (12800 to 64000) (“20 to 100%”)
SCI = 4: Square root (0 to 64000) (“0 to 100%”)
SCI = 5: Square root (12800 to 64000), clamped (“20 to 100%”)
SCI = 6: Square root, low cutoff (0 to 64000), clamp < 3/4% (“0 to 100%”)
SCI = 7: Square root, low cutoff (12800 to 64000), clamp < 3/4% (“20 to 100%”)
SCI = 9: Linear, low cutoff (1600 to 64000) (“0 to 100%, Elevated Zero”)
SCI = 10: Linear, low cutoff (12800 to 64000)(“20 to 100%”)
SCI = 11: Square root (IT2 signal)
SCI = 50: Linear (0 to 65535)
SCI = 51: Linear (-32768 to 32767)
SCI = 52: Linear (0 to 32767)
SCI = 53: Linear (0 to 1000)
SCI = 54: Linear (0 to 9999)
SCI = 55: Linear (0 to 2048)
SCI = 56: Linear (409 to 2048)
SCI = 57: Square root (0 to 2048)
SCI = 58: Square root (409 to 2048)
SCI = 59: Linear (0 to 4095)

SCIs for Micro-I/A Pre-6.2.1 Software Releases, and the Allen-

Bradley Station
The following SCIs apply to Micro-I/A software releases prior to 6.2.1, and to the I/A Series
Allen-Bradley Station:
SCI = 0: No linearization; output = input
SCI = 1: Linear (0 to 64000) (“0 to 100%”)
SCI = 2: Linear (1600 to 64000) (“0 to 100%, Elevated Zero”)
SCI = 3: Linear (12800 to 64000) (“20 to 100%”)
SCI = 4: Square root (0 to 64000) (“0 to 100%”)
SCI = 5: Square root (12800 to 64000), clamped (“20 to 100%”)
SCI = 6: Square root, low cutoff (0 to 64000), clamp < 3/4% (“0 to 100%”)
SCI = 7: Square root, low cutoff (12800 to 64000), clamp < 3/4% (“20 to 100%”)

199
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

SCI = 9: Linear, low cutoff (1600 to 64000) (“0 to 100%, Elevated Zero”)
SCI = 10: Linear, low cutoff (12800 to 64000)(“20 to 100%”)
SCI = 11: Linear (-32768 to 32767)
SCI = 12: Linear (0 to 32767)
SCI = 13: Linear (0 to 1000)
SCI = 14: Linear (0 to 9999)
SCI = 15: Linear (0 to 2048)
SCI = 16: Linear (409 to 2048)
SCI = 17: Square root (0 to 2048)
SCI = 18: Square root (409 to 2048)
SCI = 19: Linear (0 to 4095)

Output Signal Conditioning

The following subsections group the output Signal Conditioning indexes (SCOs) according to
Foxboro product offerings:
♦ Fieldbus Modules (FBMs), Fieldbus Cluster I/O Fieldbus Cards (FBCs), and devices
♦ Micro-I/A software release 6.2.1 (or greater), Application Workstation 51 (AW51)
Integrator, and Application Workstation 70 (AW70) Integrator
♦ Micro-I/A pre-6.2.1 software releases, and the Allen-Bradley Station.

SCOs for FBMs, FBCs, and Devices

Before an output block writes a value to an appropriate type FBM, FBC, or a device, it is con-
verted to raw counts.
The analog value, which is written to an FBM, FBC, or device point, is converted from engineer-
ing units to counts using the high and low output range. The processing is the inverse operation
of input signal conditioning (SCI). This value is conditioned according to the applied signal con-
ditioning output (SCO) index. The result is clamped between the high and low actuator limit
value.
If the output (OUT) of the block is sent to an FBM, FBC, or a device, then it must be converted,
by the application of signal conditioning, from engineering units within Range Output 1 (RO1)
into raw count, which is an integer value in the range used by the particular FBM, FBC, or
device. The value IOMOPT = 1 specifies that FBMs, FBCs, or devices are connected.
You may also apply signal conditioning, for test purposes, when no FBMs, FBCs, or devices are
connected. You should configure IOMOPT = 0 in this case. The values of IOM_ID, IOMIDR,
and PNT_NO are ignored.
The value IOMOPT = 2 indicates that there are no connected FBMs or FBCs, and that signal
conditioning is not used. The values of IOM_ID, IOMIDR, PNT_NO, and SCO are all
ignored.
The value IOMOPT = 3 is used with Integrators and Gateways and stores the device’s input data
bit values in the standard I/A Series control processor order. Integrators and Gateways may have
their own SCO indexes. Refer to the appropriate document.

200
Appendix A. Signal Conditioning Indexes B0193AW – Rev R

The values of SCO, which must be in the ranges 0 to 5 or 12 to 13, cause the following inverse
linear or inverse square root signal conditioning to be applied to the scaled, balanced, and
clamped input. In each case, the input to the signal conditioning algorithm is the value of OUT,
and the output of the algorithm is stored in RAWC:
The following output Signal Conditioning indexes are applicable for analog output blocks used in
conjunction with FBMs, FBCs, and devices:
SCO = 0: No Conditioning
raw count = output
SCO = 1: 0 to 64000 inverse linear
(Analog Output 0 to 20 mA)
raw count = (output - LSCO1) * 64000 / (HSCO1 - LSCO1)
SCO = 2: 1600 to 64000 inverse linear
(Analog Output 0 to 10 V dc)
raw count = ((output - LSCO1) * 62400 / (HSCO1 - LSCO1) + 1600
SCO = 3: 12800 to 64000 inverse linear
(Analog Output 4 to 20 mA)
raw count = ((output - LSCO1) * 51200 / (HSCO1 - LSCO1) + 12800
SCO = 4: 0 to 64000 inverse square root
(Analog Output 0 to 20 mA)
raw count = ((output - LSCO1) * 62400 / (HSCO1 - LSCO1))2 / 64000
SCO = 5: 12800 to 64000 inverse square root, clamped
(Analog Output 4 to 20 mA)
raw count = ((output - LSCO1) * 51200 / (HSCO1 - LSCO1))2 / 51200 +
12800
SCO = 12: 14080 to 64000 inverse linear
(Analog Output 2 to 10 V dc)
raw count = ((output - LSCO1) * 49920 / (HSCO1 - LSCO1)) + 14080
SCO = 13: 14080 to 64000 inverse square root with low cutoff
(Analog Output 2 to 10 V dc)
raw count = ((output - LSCO1) * 49920 / (HSCO1 - LSCO1))2 / 49920 +
14080
Each SCO value has an associated raw span, consisting of the difference between the upper and
lower range values of the raw value. For example, SCO = 2 has a raw span of 64000 minus 1600,
or 62400. The upper range value is always 64000 for any nonzero SCO.
The effect of inverse linear signal conditioning is to place RAWC at the same relative position
within the raw span as OUT occupies within the engineering units span.

201
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

Example:
If,
LSCO1 = 200C
HSCO1 = 900C
OUT = 500C
SCO =2

Then,
RAWC = ((50 - 20) * 62400 / (90 - 20)) + 1200
= (30 * 62400/70) + 1200 = 27943

Inverse square root signal conditioning is similar, but the relationship between RAWC and OUT
is non-linear.

SCOs for Micro-I/A Software Release 6.2.1 (or greater), AW51,

and AW70
The following output Signal Conditioning indexes are applicable for analog output blocks used in
conjunction with Micro-I/A Software Release 6.2.1 (or greater), the Application Workstation 51
(AW51) Integrator, and the Application Workstation 70 (AW70) Integrator:
SC0 = 0: No conditioning
SC0 = 1: Inverse linear (0 to 64000)
SC0 = 2: Inverse linear (1600 to 64000)
SC0 = 3: Inverse linear (12800 to 64000) (“20 to 100%”)
SC0 = 4: Inverse square root (0 to 64000) (“0 to 100%”)
SC0 = 5: Inverse square root (12800 to 64000) (“20 to 100%”)
SC0 = 50: Linear (0 to 65535)
SC0 = 51: Inverse linear (-32768 to 32767)
SC0 = 52: Inverse linear (0 to 32767)
SC0 = 53: Inverse linear (0 to 1000)
SC0 = 54: Inverse linear (0 to 9999)
SC0 = 55: Inverse linear (0 to 2048)
SC0 = 56: Inverse linear (409 to 2048)
SC0 = 59: Inverse linear (0 to 4095)

202
Appendix A. Signal Conditioning Indexes B0193AW – Rev R

SCOs for Micro-I/A Pre-6.2.1 Software Releases, and the

Allen-Bradley Station
The following output Signal Conditioning indexes apply to the Micro-I/A software releases prior
to 6.2.1, and to the I/A Series Allen-Bradley Station:
SC0 = 0: No conditioning
SC0 = 1: Inverse linear (0 to 64000)
SC0 = 2: Inverse linear (1600 to 64000)
SC0 = 3: Inverse linear (12800 to 64000) (“20 to 100%”)
SC0 = 4: Inverse square root (0 to 64000) (“0 to 100%”)
SC0 = 5: Inverse square root (12800 to 64000) (“20 to 100%”)
SC0 = 11: Inverse linear (-32768 to 32767)
SC0 = 12: Inverse linear (0 to 32767)
SC0 = 13: Inverse linear (0 to 1000)
SC0 = 14: Inverse linear (0 to 9999)
SC0 = 15: Inverse linear (0 to 2048)
SC0 = 16: Inverse linear (409 to 2048)
SC0 = 19: Inverse linear (0 to 4095)

203
B0193AW – Rev R Appendix A. Signal Conditioning Indexes

204
Appendix B. Fieldbus Modules
This appendix lists and describes Fieldbus Module types and their software configurable
specifications.

Fieldbus Module Types (FBMs)

FBM201 (0 to 20 mA Inputs)
The 0 to 20 mA Input Interface Module contains eight 20 mA dc analog input channels. Each
channel accepts a 2-wire, analog sensor input such as a 4 to 20 mA transmitter or a self-powered
20 mA source.
The module performs the signal conversion required to interface the electrical input signals from
the field sensors to the redundant Fieldbus.
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options for this program and their ranges follow.

Table B-1. FBM201 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Input Range (each channel): 0 to 20.4 mA dc.

Rated Mean Accuracy: ±0.03% of span.
Conversion Time (software configurable): see Table B-2.

205
B0193AW – Rev R Appendix B. Fieldbus Modules

Table B-2. FBM201 Conversion Time Factors

Settling Time*
Conversion Time Resolution (Milliseconds) Update Time RES Value
50 ms 15 bits 100 25 ms 5
100 ms 15 bits 125 25 ms 1
200 ms 15 bits 200 25 ms 2
500 ms 15 bits 500 25 ms 3
1000 ms 15 bits 1000 25 ms 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.

FBM202 (Thermocouple/mV Inputs)

The Thermocouple/mV Input Interface Module contains eight isolated thermocouple input
channels, and one isolated reference junction compensation channel (for terminal temperature
sensing).
Each channel has a full scale indication on burnout feature (up-scale) and accepts standard ther-
mocouples for various temperature ranges.
The module performs the signal conversion required to interface the electrical input signals from
the thermocouples to the redundant Fieldbus.
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options and their ranges follow.

Table B-3. FBM202 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-9) Normalized Raw Counts/100 ms

Input Range: -10.5 to 78.125 mV dc equals 0 to 65535 raw counts.

Reference Junction:
For discrete and direct terminal connections, a 100 ohm platinum RTD is internally pro-
vided at the termination cable assembly.
For a plug termination connection, the reference junction connection is provided by the
user with a 4-wire 100 ohm platinum RTD (IEC 751, Class B).
Rated Mean Accuracy: ± 0.03% of span.
Conversion Time (software configurable): see Table B-4.

206
Appendix B. Fieldbus Modules B0193AW – Rev R

Table B-4. FBM202 Conversion Time Factors

Settling Time*
Conversion Time Resolution (Milliseconds) Update Time RES Value
50 ms 15 bits 100 25 ms 5
100 ms 15 bits 125 25 ms 1
200 ms 15 bits 200 25 ms 2
500 ms 15 bits 500 25 ms 3
1000 ms 15 bits 1000 25 ms 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.

FBM203 (RTD Inputs)

The Platinum and Nickel Resistance Temperature Detector (RTD) Input Interface Module con-
tains eight RTD input channels. Each channel accepts a 2- or 3-wire RTD sensor input within a 0
to 320 ohm resistance range.
The module performs the signal conversion required to interface the electrical input signals from
the RTD to the redundant Fieldbus.
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options and their ranges follow.

Table B-5. FBM203 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Input Range (each channel): 0 to 320 ohms.

Sensor Current: 0.25 mA dc.
Rated Mean Accuracy: ±0.03% of span.
Conversion Time (software configurable): see Table B-6.

207
B0193AW – Rev R Appendix B. Fieldbus Modules

Table B-6. FBM203 Conversion Time Factors

Settling Time*
Conversion Time Resolution (Milliseconds) Update Time RES Value
50 ms 15 bits 100 25 ms 5
100 ms 15 bits 125 25 ms 1
200 ms 15 bits 200 25 ms 2
500 ms 15 bits 500 25 ms 3
1000 ms 15 bits 1000 25 ms 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.

FBM204 (0 to 20 mA Inputs/Outputs)
The Channel Isolated 0 to 20 mA Input/Output Interface Module contains four 20 mA dc ana-
log input channels and four 20 mA dc analog output channels.
Each input channel accepts an analog sensor input such as a 4 to 20 mA transmitter or a self-pow-
ered 20 mA source.
Each output channel drives an external load and produces a 0 to 20 mA output.
The module performs the signal conversion required to interface the electrical input/output sig-
nals from/to the field sensors to/from the redundant Fieldbus.
The module independently connects to the redundant Fieldbus. This module executes the Analog
I/O application program. The configurable options and their ranges follow.

Table B-7. FBM204 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms
Analog Output:
Fail-safe Configuration (Hold/ 0 = fallback; 1 = hold
Fallback on a per-channel basis)
Rate of Change Limits (Channels 1-4) Normalized Raw Counts/100 ms

Rated Mean Accuracy: ±0.03% of span for inputs and ±0.05% of span for outputs.
Conversion Time (software configurable): see Table B-8.

208
Appendix B. Fieldbus Modules B0193AW – Rev R

Table B-8. FBM204 Conversion Time Factors

Settling Time*
Conversion Time Resolution Update Time (Milliseconds) RES Value
50 ms 15 bits 25 ms 100 5
100 ms 15 bits 25 ms 125 1
200 ms 15 bits 25 ms 200 2
500 ms 15 bits 25 ms 500 3
1000 ms 15 bits 25 ms 1000 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.

FBM205 (Redundant 0 to 20 mA Inputs/Outputs)

The Redundant, Channel Isolated 0 to 20 mA I/O Interface (FBM205) which contains four 0 to
20 mA dc analog input channels and four 20 mA dc analog output channels. The module can be
used as a non-redundant (single) module or as a redundant pair (two FBM 205s). The redundant
pair of Fieldbus Modules combine to provide redundancy at the Fieldbus Module level. Field I/O
is wired to one common termination assembly. Each Fieldbus Module independently attempts to
hold the output(s) at its specified output value(s), and each independently reports its observed
value of the inputs. A redundant analog input (AINR) and output (AOUTR) block in the control
software validates each input and output in conjunction with information to/from the Fieldbus
Module.
The FBM205 is similar to the FBM204 module, except for the current sense resistor for inputs
and current steering diodes for outputs, which are absent from the FBM205 inputs/outputs. A
special redundant adapter used with the FBM205 includes a current sense resistor and current
steering diodes. This allows two FBM205 modules to monitor the same transmitter.
The FBM205 meets the same physical and performance specifications as the FBM204. Refer to
FBM204 for the input/output configurable options for FBM205.

FBM206 (Pulse Inputs)

The Pulse Inputs Interface module contains eight configurable pulse input channels. Each input
channel accepts a pulse input, with a maximum rate of 25 kHz.
The input devices include vortex and turbine meters, solid state or electro-mechanical contacts
and other sensors with similar pulse outputs.
The module performs the signal conversion required to interface the electrical input signals from
the field sensors from the redundant Fieldbus.
The module independently connects to the redundant Fieldbus.
This module executes the Pulse Input application program.

FBM207(Contact/dc Inputs)
The Contact/dc Input Interface Module functions as a 16-channel dc voltage monitor (FBM207)
or 16-channel contact sensor (FBM207b).
It performs the signal conversion required to interface these digital (that is, on/off state) electrical
input signals from the field sensors to the redundant Fieldbus.

209
B0193AW – Rev R Appendix B. Fieldbus Modules

The module independently connects to the Fieldbus.

The module is capable of executes the Digital I/O application program. The configurable options
for the program are:

Table B-9. FBM207 Options

Option Range
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
Sustained or Momentary Output Configuration 0 = sustained; 1 = momentary
(on a per-channel basis)

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.
Input Range (each channel): Contact open (off) or closed (on).

FBM211(16-Channel Differential-Isolated 0 to 20 mA Inputs)

The 16-Channel Differential-Isolated Analog Input Module (0 to 20 mA) contains sixteen 0 to
20.4 mA dc analog input channels.
Each input channel accepts a 2-wire, field powered 0 to 20 mA source.
The module performs the signal conversion required to interface the electrical input signals from
the field sensors to the redundant Fieldbus. Differential-Isolated means that the inputs are electri-
cally separate module-to-module but not channel-to-channel on the same card
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options and their ranges follow.

Table B-10. FBM211 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms
Analog Output:
Fail-safe Configuration 0 = fallback; 1 = hold
(Hold/Fallback on a per-channel basis)
Rate of Change Limits (Channels 1-4) Normalized Raw Counts/100 ms

210
Appendix B. Fieldbus Modules B0193AW – Rev R

Rated Mean Accuracy: ±0.03% of span.

Conversion Time (software configurable): see Table B-11.

Table B-11. FBM211 Conversion Time Factors

Settling Time*
Conversion Time Resolution Update Time (Milliseconds) RES Value
50 ms 15 bits 50 ms 100 5
100 ms 15 bits 50 ms 125 1
200 ms 15 bits 50 ms 200 2
500 ms 15 bits 50 ms 500 3
1000 ms 15 bits 50 ms 1000 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.

FBM212 (14-Channel Differential-Isolated Thermocouple

Inputs)
The 14-Channel Differential-Isolated Analog Input Fieldbus Module for Thermocouples con-
tains 14 analog single-ended input channels, and one isolated reference junction compensation
channel (for terminal temperature sensing).
Each channel has a full scale indication on burnout feature (up-scale) and accepts standard ther-
mocouples for various temperature ranges.
The module performs the signal conversion required to interface the electrical input signals from
the thermocouples to the redundant Fieldbus. Each channel has a differential input to allow volt-
age differences between channels without introducing errors. The channels are not galvanically
isolated from each other, but are galvanically isolated from ground and module logic. Differential
group isolated inputs and outputs use the FBM subsystem power supply for field power.
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options and their ranges follow.

Table B-12. FBM212 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-9) Normalized Raw Counts/100 ms

Input Range: -10.5 to 78.125 mV dc.

211
B0193AW – Rev R Appendix B. Fieldbus Modules

Reference Junction:
For discrete and direct terminal connections, a 100 ohm platinum RTD is internally pro-
vided at the termination cable assembly.
For a wire termination connection, the reference junction connection is provided by the
user with a 4-wire 100 ohm platinum RTD (IEC 751, Class B).
Rated Mean Accuracy: ± 0.03% of span.
Conversion Time: see Table B-13.

Table B-13. FBM212 Conversion Time Factors

Settling Time*
Conversion Time Resolution Update Time (Milliseconds) RES Value
50 ms 15 bits 50 ms 100 5
100 ms 15 bits 50 ms 125 1
200 ms 15 bits 50 ms 200 2
500 ms** 15 bits 50 ms 500 3
1000 ms** 15 bits 50 ms 1000 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.
** Use 500 ms or 1000 ms conversion time for FBM212

FBM213 (8-Channel Differential-Isolated RTD Inputs)

The 8-Channel Differential-Isolated Resistance Temperature Detector (RTD) Input Interface
Module contains eight RTD input channels. Each channel accepts a 2- or 3-wire RTD sensor
input within a 0 to 320 ohm resistance range.
The module performs the signal conversion required to interface the electrical input signals from
the RTD to the redundant Fieldbus. Each channel has a differential input to allow voltage differ-
ences between channels without introducing errors. The channels are not galvanically isolated
from each other, but are galvanically isolated from ground and module logic. Differential group
isolated inputs and outputs use the FBM subsystem power supply for field power.
The module independently connects to the redundant Fieldbus. This module executes the Analog
Input application program. The configurable options and their ranges follow.

Table B-14. FBM213 Options

Option Range
Analog Input Conversion Time 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms conversion time, 25 ms update period
2 = 200 ms conversion time, 25 ms update period
3 = 500 ms conversion time, 25 ms update period
4 = 1000 ms conversion time, 25 ms update period
5 = 50 ms conversion time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

212
Appendix B. Fieldbus Modules B0193AW – Rev R

Input Range (each channel): 0 to 320 ohms.

Sensor Current: 0.25 mA dc.
Rated Mean Accuracy: ±0.03% of span.
Conversion Time (software configurable): see Table B-15.

Table B-15. FBM213 Conversion Time Factors

Settling Time*
Conversion Time Resolution Update Time (Milliseconds) RES Value
50 ms 15 bits 50 ms 100 5
100 ms 15 bits 50 ms 125 1
200 ms 15 bits 50 ms 200 2
500 ms** 15 bits 50 ms 500 3
1000 ms** 15 bits 50 ms 1000 4
* Value settles within a 1% band of steady state for a 10 to 90% input step change.
** Use 500 ms or 1000 ms conversion time for FBM213.

FBM214 (HART Communication Input Interface Module)

The FBM 214 provides analog and digital communications to and from HART compliant field
devices. It also supports standard 4 to 20mA signals from analog devices. FBM214 contains eight
group isolated input channels. Each of the eight channels accepts a digital HART Frequency-Shift
Keying (FSK) signal superimposed on a 4 to 20 mA analog input signal. Each channel provides
bi-directional digital communications with a HART compliant field device, and performs analog
to digital conversion on the 4 to 20 mA input control signal from that device. Refer to HART
Communication Interface Module (FBM214/215/216/218) User’s Guide (B0400FF).

FBM215 (HART Communication Output Interface Module)

The FBM 215 provides analog and digital communications to and from HART compliant field
devices. It also supports standard 4 to 20mA signals from analog devices. FBM215 contains eight
channel-isolated output channels. Each of the eight channels accepts a digital HART Frequency-
Shift Keying (FSK) signal superimposed on a 4 to 20 mA analog output signal. Each channel pro-
vides bi-directional digital communications with a HART compliant actuator, and provides an
output signal of 4 to 20 mA to the actuator. Refer to HART Communication Interface Module
(FBM214/215/216/218) User’s Guide (B0400FF).

FBM216 (HARTTM Communication Redundant Input Interface

Module)
The FBM 216 provides analog and digital communications to and from HART compliant field
devices. It also supports standard 4 to 20mA signals from analog devices. FBM216 contains eight
group isolated input channels. Each of the eight channels accepts a digital HART Frequency-Shift
Keying (FSK) signal superimposed on a 4 to 20 mA analog input signal. Each channel provides
bi-directional digital communications with a HART compliant field device, and performs analog
to digital conversion on the 4 to 20 mA input control signal from that device.

213
B0193AW – Rev R Appendix B. Fieldbus Modules

A redundant pair of the modules combine to provide redundancy at the Fieldbus Module (FBM)
level. Refer to HART Communication Interface Module (FBM214/215/216/218) User’s Guide
(B0400FF).

FBM217 (32-Channel Group-Isolated Voltage Monitor Inputs)

The 32-Channel Group-Isolated dc Input Module provides 32-channel digital voltage input
channels. It performs voltage or contact sensing (that is, on/off state).
It performs the signal conversion required to interface these digital (that is, on/off state) electrical
input signals from the field sensors to the redundant Fieldbus. Group-Isolated means that the
inputs are electrically separate module-to-module but not channel-to-channel on the same card.
The module independently connects to the Fieldbus.
The module executes the Digital I/O application program. The configurable options for the pro-
gram are:
Table B-16. FBM217 Options

Option Range
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
Sustained or Momentary Output 0 = sustained; 1 = momentary
Configuration (on a per-channel basis)

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.
Input Range (each channel): Contact open (off) or closed (on).

FBM218 (HART Communication Redundant Output Interface

Module)
The FBM 218 provides analog and digital communications to and from HART compliant field
devices. It also supports standard 4 to 20mA signals from analog devices. FBM218 contains eight
channel-isolated output channels. Each of the eight channels accepts a digital HART Frequency-
Shift Keying (FSK) signal superimposed on a 4 to 20 mA analog output signal. Each channel pro-
vides bi-directional digital communications with a HART compliant actuator, and provides an
output signal of 4 to 20 mA to the actuator.
A redundant pair of the modules combine to provide redundancy at the Fieldbus Module (FBM)
level. Refer to HART Communication Interface Module (FBM214/215/216/218) User’s Guide
(B0400FF).

214
Appendix B. Fieldbus Modules B0193AW – Rev R

FBM219 (32-Channel Group-Isolated Discrete I/O Module)

The 32-Channel Group-Isolated Discrete Input/output Module provides 24-channel digital input
channels and eight digital output channels. It performs voltage or contact sensing (that is, on/off
state).
For input functions, all twenty-four input channels are used exclusively for either contact sensing
or voltage monitoring. For output functions, all eight output channels are used for dc output
switching, either with an internal or external power source.
The module performs the signal conversion required to interface the digital electrical input/out-
put signals from/to the field sensors/actuators to/from the redundant Fieldbus. Group-Isolated
means that the inputs are electrically separate module-to-module but not channel-to-channel on
the same card.
The module executes the Digital I/O or Ladder Logic application program. The configurable
options and their ranges follow.

Table B-17. FBM219 Digital Options

Option Range
All Applications
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
DI/DO; Ladder Logic Applications
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
DI/DO Applications Sustained or 0 = sustained; 1 = momentary
Momentary Output Configuration
(on a per-channel basis)

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.
Input Range (each channel): Contact open (off) or closed (on).

FBM220/221 FOUNDATION fieldbus H1 Communications

Interface Module
FBM220/221 provide an interface between Foundation fieldbus field devices and the I/A Series
system. FBM220 supports one H1 segment and FBM221 provides integration of four H1 chan-
nel isolated fieldbus segments. For information regarding configuration options, refer to the
descriptions of these blocks in Integrated Control Block Descriptions (B0193AX).

FBM223 (PROFIBUS-DP Communication Interface Module)

The FBM223 provides an interface between PROFIBUS-DP slave devices and the I/A Series sys-
tem. Refer to PROFIBUS-DP Communication Interface Module (FBM223) User’s Guide
(B0400FE).

215
B0193AW – Rev R Appendix B. Fieldbus Modules

FBM224 (Modbus Communication Interface Module)

The Modbus Communication Interface Module is used to integrate third-party devices that have
a Modbus interface, into an I/A Series System. The FBM224 provides digital communication to
and from Modbus slave devices (input/output devices) on Modbus networks.
Devices with which the FBM224 can successfully communicate are those that support the appro-
priate Modbus function codes from the list in Table B-18 and operate in the Modbus RTU mode.
These devices must respond as slave devices to some or all of the subset of commands of the Mod-
bus function codes as listed in Table B-18. Refer to Modbus Communication Interface Module
(FBM224) User’s Guide (B0400FK).

Table B-18. Modbus Function Codes for Modicon Programmable Controllers

Code Function
1 Read Coil Status
2 Read Input Status
3 Read Holding Registers
4 Read Input Registers
5 Force Single Coil
6 Preset Single Register
8 Loopback Diagnostic Test
15 Force Multiple Coils
16 Preset Multiple Registers

FBM237 (Channel Isolated, Redundant-Ready 0 to 20 mA

Outputs)
The Channel Isolated, Redundant-Ready 0 to 20 mA Output Interface Module (FBM237) con-
tains eight 0 to 20 mA dc analog output channels. The module can be used as a non-redundant
(single) module or as a redundant pair (two FBM237s). The pair of Fieldbus Modules combine to
provide redundancy at the Fieldbus Module level, with associated field I/O signals wired to one
common termination assembly. Each redundant Fieldbus Module independently attempts to hold
the output(s) at its specified output value(s). A redundant analog output (AOUTR) block in the
control software validates each output in conjunction with information from the Fieldbus
Module.
The module performs the signal conversion required to interface the electrical output signals to
the field sensors from the redundant Fieldbus.

216
Appendix B. Fieldbus Modules B0193AW – Rev R

This module executes the Analog I/O application program. The configurable options and their
ranges follow.

Table B-19. FBM237 Options

Option Range
Analog Output:
Fail-safe Configuration 0 = fallback; 1 = hold
(Hold/Fallback on a per-channel basis)
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Rated Mean Accuracy: ±0.05% of span.

FBM241 (Contact/dc Inputs/Outputs)

The Channel Isolated Voltage Monitor/Contact Sense I/O Interface Module
(FBM241/FBM241b/FBM241c/ FBM241d) functions as an eight-channel dc voltage monitor
with eight-channel output switching, or as an eight-channel contact sensor with eight-channel
output switching. The Module is available in four distinct types, to provide the following discrete
input and output functions:
♦ FBM 241 – Accepts eight inputs from a dc voltage source, and provides eight dc
switching outputs with an external source.
♦ FBM 241b – Accepts eight inputs from a dc voltage source, and provides eight dc
switching outputs with an internal source.
♦ FBM 241c – Accepts eight contact sensing inputs, and provides eight dc switching
outputs with an external source.
♦ FBM 241d – Accepts eight contact sensing inputs, and provides eight dc switching
outputs with an internal source.
For input functions, all eight input channels are used exclusively for either contact sensing or volt-
age monitoring. For output functions, all eight output channels are used for dc output switching,
either with an internal or external power source.
The module performs the signal conversion required to interface the digital electrical input/out-
put signals from/to the field sensors/actuators to/from the redundant Fieldbus.
The module executes the Digital I/O or Ladder Logic application program. The configurable
options and their ranges follow.

Table B-20. FBM241 Digital Options

Option Range
All Applications
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
DI/DO; Ladder Logic Applications
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)

217
B0193AW – Rev R Appendix B. Fieldbus Modules

Table B-20. FBM241 Digital Options (Continued)

Option Range
DI/DO Applications Sustained or
Momentary Output Configuration 0 = sustained; 1 = momentary
(on a per-channel basis)

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

FBM242 (Digital Outputs)

The Digital Output Interface Module (FBM242) is a discrete output function providing sixteen
dc switching outputs with an external power source.
The module is a nonredundant (single) module. Field Outputs are wired to one common termi-
nation assembly.
The module performs the signal conversion required to interface the digital electrical output sig-
nals to the field sensors/actuators from the redundant Fieldbus.
The module executes the Digital I/O and Sustained/Momentary (S/M) application program.

Table B-21. FBM242 Digital Options

Option Range
Sustained or Momentary Output 0 = sustained; 1 = momentary
Configuration (on a per-channel basis)

If the Momentary configuration is selected, then the Output Interval is configurable in incre-
ments of 10 ms with a 50% duty cycle.

FBM243 (Channel Isolated FoxCom Dual Baud Rate Intelligent

Device Interface Module)
FBM243 (Foxboro part number P0914TK) contains eight individual channels that provide iso-
lated power and FoxCom communication capabilities to an Intelligent Transmitter/Positioner
over a single twisted pair of wires. The module also allows the use of an external power supply to
power the IT. The use of an external power supply common to two or more loops requires a Cable
Balun Module to maintain communication signal line balance.
The module provides bidirectional digital communications at 4800 baud rate between the Intelli-
gent Field Device and the system redundant Fieldbus, or provides bidirectional digital communi-
cations at 600 baud rate between the field device and the module while allowing a simultaneous 4
to 20 mA analog signal to an emergency shutdown system. The baud rate is determined by the
configuration of the field device connected to each channel, independently of the other channels.

218
Appendix B. Fieldbus Modules B0193AW – Rev R

The module is an IT host, enabling the system to receive digital messages from the transmitter in
engineering units. Each message is received 10 times per second at 4800 baud, and two times per
second at 600 baud and contains:
♦ Up to three measured variables in IEEE 32-bit floating-point format
♦ Security information
♦ Diagnostics
♦ Message checking.
This information is available to all elements of the system.
Since communication is bidirectional, the system can display the output, transmitter temperature
(°C and °F), and continuous self-diagnostics. In addition, information that can be displayed or
reconfigured from the console or a Hand-Held Terminal (HHT) is as follows:
♦ Output in engineering units
♦ Fail-safe status
♦ Tag number, name, and location
♦ Device name (letterbug)
♦ Last calibration date
♦ Two levels of upload/download capabilities.

FBM246 (Channel Isolated FoxCom Redundant Dual Baud Rate

Intelligent Device Interface Module)
FBM246 (Foxboro part number P0917XN) contains eight individual channels. The pair of
FBM246s is a redundant version of the FBM243 and supports both transmitters and valve posi-
tioners. The eight FoxCom channels can support any combination of these devices. Individual
transmitters or positioners may be in either analog or digital mode.

NOTE
FBM246 is primarily a digital interface and operation of all transmitters in digital
mode provides substantially better performance. Analog mode should be used only
for special applications (For example, when the measurement is required for an
Emergency Shutdown System that requires 4 to 20 mA signals).

The two modules combine to provide redundancy at the FBM level. To achieve redundancy, a
Redundant Adapter module is placed on the two adjacent baseplate termination cable connectors
to provide a single termination cable connection. A single termination cable connects from the
Redundant Adapter to the associated termination assembly (TA).

FBM01 (0 to 20 mA Inputs)
The 0 to 20 mA Input Interface contains eight 20 mA dc analog input channels. Each channel
accepts a 2-wire, analog sensor input such as a 4 to 20 mA transmitter or a self-powered 20 mA
source.
The module performs the signal conversion required to interface the electrical input signals from
the field sensors to the redundant Fieldbus.

219
B0193AW – Rev R Appendix B. Fieldbus Modules

The module is a non-expandable main type, and independently connects to the redundant
Fieldbus.
This module executes the Analog Input application program. The configurable options for this
program and their ranges follow.

Table B-22. FBM01 Options

Option Range
Analog Input Resolution 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
5 = 50 ms integration time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Input Range (each channel): 0 to 20.4 mA dc.

Rated Mean Accuracy: ±0.05% of span.
Conversion Time (software configurable): see Table B-23.

Table B-23. FBM01 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.05 0.125 0.0250 11
0.1 0.25 0.0125 12
0.2 0.50 0.0075 13
0.5 1.00 0.005 14
1.0 2.00 0.005 15
* Value settles within a 1% band of steady state for a 10 to 90% input step change.
** Monotonic; assures that the signal for Fieldbus communications either increases
or remains the same for increasing analog input signals.

FBM02 (Thermocouple/mV Inputs)

The Thermocouple/mV Input Interface contains eight isolated thermocouple input channels, and
one isolated reference junction compensation channel (for terminal temperature sensing).
Each channel has a full scale indication on burnout feature and accepts standard thermocouples
for various temperature ranges.
The module performs the signal conversion required to interface the electrical input signals from
the thermocouples to the redundant Fieldbus.
The module is a non-expandable main type, and independently connects to the redundant Field-
bus. This module executes the Analog Input application program. The configurable options and
their ranges follow.

220
Appendix B. Fieldbus Modules B0193AW – Rev R

Table B-24. FBM02 Options

Option Range
Analog Input Resolution 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
5 = 50 ms integration time, 25 ms update period
Rate of Change Limits (Channels 1-9) Normalized Raw Counts/100 ms

Input Range: -10 to 70 mV dc.

Reference Junction:
For discrete and direct terminal connections, a 100 ohm platinum RTD is internally pro-
vided at the termination cable assembly.
For a plug termination connection, the reference junction connection is provided by the
user with a 4-wire 100 ohm platinum RTD (DIN 43760, Class B).
Rated Mean Accuracy: ± 0.025% of span.
Conversion Time (software configurable): see Table B-25.

Table B-25. FBM02 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.05 0.125 0.0250 11
0.1 0.4 0.0125 12
0.2 0.6 0.0075 13
0.5 1.2 0.005 14
1.0 2.1 0.005 15
* Value settles within a 1% band of steady state for an input step change of 0 to 60 mV.
** Monotonic; assures that the signal for Fieldbus communications either increases or
remains the same for increasing analog input signals.

FBM03A ([3-wire] and 03B [4-wire] RTD Inputs)

The RTD Input Interface contains eight Resistance Temperature Detector (RTD) input channels.
Each channel accepts either a 2- and 4-wire RTD, or 3-wire RTD sensor input within a 0 to
320 ohm resistance range.
Within the same module, 3-wire RTDs may not be mixed with 2- or 4-wire RTDs.
The module performs the signal conversion required to interface the electrical input signals from
the RTD to the redundant Fieldbus.
The module is a non-expandable main type, and independently connects to the redundant
Fieldbus.

221
B0193AW – Rev R Appendix B. Fieldbus Modules

This module executes the Analog Input application program.

The configurable options and their ranges follow.

Table B-26. FBM03 Options

Option Range
Analog Input Resolution 1, 2, 3, 4, 5
(on a per module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
5 = 50 ms integration time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Input Range (each channel): 0 to 320 ohms.

Sensor Current: 0.25 mA dc.
Rated Mean Accuracy: ±0.025% of span.
Conversion Time (software configurable): see Table B-27.

Table B-27. FBM03 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.05 0.125 0.0250 11
0.1 0.4 0.0125 12
0.2 0.6 0.0075 13
0.5 1.2 0.005 14
1.0 2.4 0.005 15
*Value settles within a 1% band of steady state for an input step change of 30 to 320 ohms.
**Monotonic; assures that the signal for Fieldbus communications either increases or
remains the same for increasing analog input signals.

FBM04 (0 to 20 mA Inputs/Outputs)
The 0 to 20 mA Input/Output Interface contains four 20 mA dc analog input channels and four
20 mA dc analog output channels.
Each input channel accepts an analog sensor input such as a 4 to 20 mA transmitter or a self-
powered 20 mA source.
Each output channel drives an external load and produces a 0 to 20 mA output.
The module performs the signal conversion required to interface the electrical input/output sig-
nals from/to the field sensors to/from the redundant Fieldbus.
The module is a non-expandable main type, and independently connects to the redundant
Fieldbus.

222
Appendix B. Fieldbus Modules B0193AW – Rev R

This module executes the Analog I/O application program. The configurable options and their
ranges follow.

Table B-28. FBM04 Options

Option Range
Analog Input Resolution 1, 2, 3, 4, 5
(on a per-module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
5 = 50 ms integration time, 25 ms update period
Analog Output: 0 = fallback; 1 = hold
Fail-safe Configuration (Hold/Fall-
back
on a per-channel basis)
Rate of Change Limits (Channels 1-4) Normalized Raw Counts/100 ms

Rated Mean Accuracy: ±0.05% of span.

Conversion Time (software configurable): see Table B-29.

Table B-29. FBM04 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% Of Range) Bits
0.05 0.125 0.0250 11
0.1 0.25 0.0125 12
0.2 0.50 0.0075 13
0.5 1.00 0.005 14
1.0 2.00 0.005 15
*Value settles within a 1% band of steady state for a 10 to 90% input step change.
** Monotonic; ensures that the signal for Fieldbus communications either increases
or remains the same for increasing analog input signals.

FBM05 (0 to 20 mA Inputs/Outputs) for Redundant Applications

The FBM05 provides redundant input capability using a single transmitter. The FBM05 is simi-
lar to the FBM04 module, except for the internal current sense resistor, which is absent from the
FBM05 inputs.
A special termination block is provided that includes a current sense resistor. This allows two
FBM05 modules to monitor the same transmitter.
The input accuracy for the FBM05 is 0.3% of span. This is based on 0.05% for the input module
and 0.25% for the external sense resistor. Otherwise, the FBM05 meets the same physical and
performance specifications as the FBM04.

223
B0193AW – Rev R Appendix B. Fieldbus Modules

The special termination block (TCA) also provides for each of the output points and its corre-
sponding point in the other member of the redundant pair to drive a single process point.

FBM06 (Pulse Inputs, 0 to 20 mA Outputs)

The Pulse Input, 0 to 20 mA Output Interface, contains four configurable pulse input channels
and four 20 mA dc analog output channels.
Each input channel accepts a pulse input, with a maximum rate of 12.5 kHz.
The input devices include vortex and turbine meters, solid state or electro-mechanical contacts
and other sensors with similar pulse outputs.
Each output channel drives an external load and produces a 0 to 20 mA output.
The module performs the signal conversion required to interface the electrical input/output sig-
nals from/to the field sensors to/from the redundant Fieldbus.
The module is a non-expandable main type, and independently connects to the redundant
Fieldbus.
This module executes the Pulse Input/Analog Output application program.
The configurable options and their ranges follow.

Table B-30. FBM06 Options

Option Range
Analog Output: 0 = fallback; 1 = hold
Fail-safe Configuration Hold/Fallback
(on a per-channel basis)
Analog Output Fail-safe 0 to 64000 counts
Fallback Data (on a per-channel basis)

FBM17 (0 to 10 V dc, Contact/dc Inputs/Outputs)

The 0 to 10 V dc, Contact/dc Input/Output Interface Module is a non-expandable main module
that provides the following input and output functions for analog and digital field signals.

Analog Signals
INPUTS – Four 0 to 10 V dc channels used collectively for either:
♦ dc voltage measuring only
♦ Slidewire (position) sensing only.
OUTPUTS – Two 0 to 10 V ac channels used for driving positioners, controllers or remote
indicators.

Digital Signals
INPUTS – 4 channels used collectively for either:
♦ Contact sensing only
♦ dc voltage monitoring only.

224
Appendix B. Fieldbus Modules B0193AW – Rev R

OUTPUTS – 4 channels used collectively for either:

♦ dc output switching with an external source only (for example, to control powering of
various external loads).
♦ dc output switching with an internal source only (for example, to power external solid
state relays or similar devices).
The module performs the signal conversion required to interface these analog and digital electrical
input/output signals from/to the field sensors/actuators to/from the redundant Fieldbus.
The configurable analog options and their ranges follow.

Table B-31. FBM17 Analog Options

Option Range
Analog Input Resolution 1, 2, 3, 4
(on a per-module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
Analog Output: 0 = fallback; 1 = hold
Fail-safe Configuration Hold/Fallback
(on a per-channel basis)
Rate of Change Limits (Channels 1-4) Normalized Raw Counts/100 ms

The configurable digital options and their ranges follow.

Table B-32. FBM17 Digital Options

Option Range
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
Digital Output Fail-safe Specifiable per channel
Fallback Data (on a per-channel basis)

Analog Input Configurable Specifications: See Table B-33.

225
B0193AW – Rev R Appendix B. Fieldbus Modules

Table B-33. FBM17 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.1 0.3 0.013 12
0.2 0.5 0.008 13
0.5 1.1 0.005 14
1.0 2.1 0.005 15
*Output value settles within a 1% band of steady state for a 10 to 90% input step change.
** Monotonic (that is, the signal used for Fieldbus communications increases or remains
the same for increasing analog input signals).

Analog Signal Specifications

INPUTS
Voltage Measuring:
♦ Range (each channel): -0.2 to 10.2 V dc
♦ Rated Mean Accuracy (each channel): ±0.025% of span.
OUTPUTS (Output Drivers)
♦ Capacity: 2 independent channels
♦ Range (each channel): -0.2 to 10.2 V dc
♦ Current (each channel): 10 mA (maximum)
♦ Rated Mean Accuracy: ±0.05% of span
♦ Settling Time: 10 ms (to 1% of final value for 10 to 90% step change)
♦ Linearity Error: ±0.025% of span
♦ Resolution: 12 bits.

Digital Signal Specifications

INPUTS
♦ Capacity: 4 independent channels
♦ Filter Time: Configurable (4, 8, 16, or 32 ms)
♦ Contact Sensor
♦ Range (each channel): Contact open (off) or closed (on).
OUTPUTS
♦ Output Switch (with external source)
♦ Output Switch (with internal source).

FBM18 (Intelligent Transmitter Interface)

The Intelligent Transmitter Interface contains eight individual channels, each providing isolated
power and communication capabilities to an Intelligent Transmitter over a single pair of wires.
The module provides bidirectional digital communications between the Intelligent Transmitter
and the system redundant Fieldbus.

226
Appendix B. Fieldbus Modules B0193AW – Rev R

The module is a transmitter host, enabling the system to receive digital messages from the trans-
mitter in engineering units. Each measurement message is received ten times per second and
contains:
♦ Up to three measured variables, that is, primary pressure, static pressure (d/p cell
only), and sensor temperature in IEEE 32-Bit Floating Point
♦ Security information
♦ Diagnostics
♦ Message checking.
This information is available to all elements of the system.
Since the communications are bidirectional, the generator can display the output, transmitter
serial number, sensor temperature (degrees C and F), and continuous self-diagnostics.
In addition, information that can be displayed or reconfigured from the console and/or a Hand-
Held Terminal is:
♦ Output in percent or engineering units
♦ Zero and Span
♦ Elevation or Suppression
♦ Linear or Square Root Output
♦ Damping
♦ Fail-safe
♦ Tag Number, Name, and Location
♦ Last calibration date
♦ Two levels of upload/download capabilities.
This module executes the interface application program.

FBM07/12 (Contact/dc Inputs and Expansion Inputs)

The Contact/dc Input Interface Module (an expandable main module) and its counterpart Con-
tact/dc Expansion Input Interface Module individually function as a 16-channel contact sensor or
16-channel dc voltage monitor.
Each module performs the signal conversion required to interface these digital (that is, on/off
state) electrical input signals from the field sensors to the redundant Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module.
The expansion module connects to the Fieldbus via any appropriate main module and is func-
tionally dependent on the supporting main module.
The main module is capable of executing any one of the application programs identified in the
following schedule:
♦ When used alone or in conjunction with an expansion module that interfaces field
input signals only, the main module executes the Digital I/O, or Sequence of Events
Monitor, or Pulse Count Inputs, or Ladder Logic program.
♦ When used in conjunction with an expansion module that interfaces field input and
output signals, the main module executes either the Digital I/O or Ladder Logic
program.

227
B0193AW – Rev R Appendix B. Fieldbus Modules

The configurable options for each program are:

Table B-34. FBM07/12 Options

Option Range
(All applications)
Inputs:
Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time *
(DI/DO; Ladder Logic applications)
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
(DI/DO Applications)
Sustained or Momentary Output
Configuration (on a per-channel basis) 0 = sustained; 1 = momentary

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.
Input Range (each channel): Contact open (off) or closed (on).

NOTE
Subject to prevalent wiring rules on mixing field wiring, FBM Main modules 7, 8,
9, 10, 11, 20, 24, 26, and 41 can mix with expansion modules 12, 13, 14, 15, 16,
21, and 42.

FBM08/13 (120 V ac Inputs and Expansion Inputs)

The 120 V ac Input Interface Module (an expandable main module) and its counterpart 120 V ac
Expansion Input Interface Module each function as a 16-channel 120 volt ac monitor.
Each module performs the signal conversion required to interface these digital (that is, on/off
state) electrical input signals from the field sensors to the redundant Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module. The expansion module connects to the Fieldbus via any expand-
able main module and is functionally dependent on the supporting main module.
The main module is capable of executing any one of the application programs identified in the
following schedule:
♦ When used alone or in conjunction with an expansion module that interfaces field
input signals only, the main module executes either the Digital I/O, Sequence of
Events Monitor, Pulse Count Inputs or Ladder Logic program.
♦ When used in conjunction with an expansion module that interfaces field input and
output signals, the main module executes either the Digital I/O or Ladder Logic
program.

228
Appendix B. Fieldbus Modules B0193AW – Rev R

The configurable options for each program are:

Table B-35. FBM08/13 Options

Option Range
(All applications)
Main Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback 0 = fallback; 1 = hold
(on a per-channel basis)
Digital Output: Specifiable per channel
Fail-safe Fallback Data
(on a per-channel basis)
Sustained or Momentary Output
configuration (on a per-channel basis) 0 = sustained; 1 = momentary

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

FBM09/14 (Contact/dc I/O and Expansion I/O)

The Contact/dc Input/Output Interface Module (an expandable main module) and its counter-
part Contact/dc Expansion Input/Output Interface Module each provide the following I/O
functions:
INPUTS – 8 channels used collectively for either:
♦ Contact sensing only
♦ dc voltage monitoring only.
OUTPUTS – 8 channels used collectively for either:
♦ dc output switching with an external source only (for example, to control powering of
various external loads)
♦ dc output switching with an internal source only (for example, to power external solid
state relays or other similar devices).
Each module performs the signal conversion required to interface these digital electrical
input/output signals from/to the field sensors or actuators to/from the redundant Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module.
The expansion module connects to the Fieldbus via any expandable main module and is function-
ally dependent on the main module.
When used alone or in conjunction with any expansion module, the main module executes either
the Digital I/O or Ladder Logic application program.

229
B0193AW – Rev R Appendix B. Fieldbus Modules

The configurable options for each program are:

Table B-36. FBM09/14 Options

Option Range
(All applications)
Main Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

FBM10/15 (120 V ac I/O and Expansion I/O)

The 120 V ac Input/Output Interface Module (an expandable main module) and its counterpart
120 V ac Expansion Input/Output Module each provide the following functions:
♦ 8 input channels for 120 Volt ac voltage monitoring
♦ 8 output channels for 120 Volt ac output switching with current overload protection.
Each module performs the signal conversion required to interface these digital (that is, on/off
state) electrical input/output signals from/to the field sensors or actuators to/from the redundant
Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module.
The expansion module connects to the Fieldbus via any expandable main module and is function-
ally dependent on the supporting module.
When used alone or in conjunction with any expansion module, the main module executes either
the Digital I/O or Ladder Logic application program.
The configurable options for each program are specified in Table B-37.

Table B-37. FBM10/15 Options

Option Range
(All applications)
Main Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback (on a per-channel basis) 0 = fallback; 1 = hold
Digital Output: Fail-safe Fallback Data (on a per-channel basis) Specifiable per channel
(DI/DO applications)
Sustained or Momentary Output Configuration
(on a per-channel basis) 0 = sustained; 1 = momentary

230
Appendix B. Fieldbus Modules B0193AW – Rev R

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

FBM20/21 (240 V ac Inputs and Expansion Inputs)

The 240 V ac Input Interface Module (an expandable main module) and its counterpart 240 V ac
Expansion Input Interface Module each function as a 16-channel 240 Volt ac monitor.
Each module performs the signal conversion required to interface these digital (that is, on/off
state) electrical input signals from the field sensors to the redundant Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module.
The expansion module connects to the Fieldbus via any expandable main module and is function-
ally dependent on the supporting main module.
The main module is capable of executing any one of the application programs identified in the
following schedule:
♦ When used alone or in conjunction with an expansion module that interfaces field
input signals only, the main module executes either the Digital I/O, Sequence of
Events Monitor, Pulse Count Inputs, or Ladder Logic program.
♦ When used in conjunction with an expansion module that interfaces field input and
output signals, the main module executes either the Digital I/O or Ladder Logic
program.
The configurable options for each program are:

Table B-38. FBM20/21 Options

Option Range
(All applications)
Main Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback (on a per-channel basis) 0 = fallback; 1 = hold
Digital Output: Fail-safe Fallback Data (on a per-channel basis) Specifiable per channel
(DI/DO application)
Sustained or Momentary Output Configuration
(on a per-channel basis) 0 = sustained; 1 = momentary

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

231
B0193AW – Rev R Appendix B. Fieldbus Modules

FBM11/16 (240 V ac I/O and Expansion I/O)

The 240 V ac Input/Output Interface Module (an expandable main module) and its counterpart
240 V ac Expansion Input/Output Module each provide the following functions:
♦ 8 input channels for 240 Volt ac voltage monitoring
♦ 8 output channels for 240 Volt ac output switching with current overload protection.
Each module performs the signal conversion required to interface these digital (that is, on/off
state) electrical input/output signals from/to the field sensors or actuators to/from the redundant
Fieldbus.
The expandable main module independently connects to the Fieldbus and is capable of support-
ing a single expansion module.
The expansion module connects to the Fieldbus via any expandable main module and is function-
ally dependent on the supporting main module.
When used alone or in conjunction with any expansion module, the main module executes either
the Digital I/O or Ladder Logic application program.
The configurable options for each program are:

Table B-39. FBM11/16 Options

Option Range
(All applications)
Main Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Expansion Input Filter Time 0 = 4 ms; 1 = 8 ms;
2 = 16 ms; 3 = 32 ms
Digital Output:
Fail-safe Configuration Hold/Fallback (on a per-channel basis) 0 = fallback; 1 = hold
Digital Output: Fail-safe Fallback Data (on a per-channel basis) Specifiable per channel
(DI/DO application)
Sustained or Momentary Output Configuration
(on a per-channel basis) 0 = sustained; 1 = momentary

If the Momentary Output configuration is selected, then the Output Interval is also configurable
in increments of 10 ms with a 50% duty cycle.

FBM33A (3-wire RTD Inputs) and 33B (2- and 4-wire RTD
Inputs)
The Copper RTD Input Interface contains eight Resistance Temperature Detector (RTD) input
channels. Each channel accepts either a 2- and 4-wire copper RTD or a 3-wire copper RTD sen-
sor input within a 0 to 30 ohm resistance range.
Within the same module, 3-wire RTDs may not be mixed with 2- or 4-wire RTDs.
The module performs the signal conversion required to interface the electrical input signals from
the RTDs to the redundant Fieldbus.

232
Appendix B. Fieldbus Modules B0193AW – Rev R

The module is a non-expandable main type, and independently connects to the redundant
Fieldbus.
This module executes the Analog Input application program.
The configurable options and their ranges follow.

Table B-40. FBM33 Options

Option Range
Analog Input Resolution 1, 2, 3, 4, 5
(on a per module basis)
1 = 100 ms integration time, 25 ms update period
2 = 200 ms integration time, 25 ms update period
3 = 500 ms integration time, 25 ms update period
4 = 1000 ms integration time, 25 ms update period
5 = 50 ms integration time, 25 ms update period
Rate of Change Limits (Channels 1-8) Normalized Raw Counts/100 ms

Input Range (each channel): 0 to 30 ohms.

Sensor Current: 0.25 mA dc.
Rated Mean Accuracy: ±0.125% of span (±0.04 ohms).
Conversion Time (software configurable): see Table B-41.

Table B-41. FBM33 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.05 0.2 0.125 11
0.1 0.4 0.0625 12
0.2 0.6 0.0375 13
0.5 1.2 0.025 14
1.0 2.4 0.025 15
* Value settles within a 1% band of steady state for an input step change of 3 to 30 ohms.
** Monotonic; assures that the signal for Fieldbus communications either increases or
remains the same for increasing analog input signals.

FBM36 (Thermocouple/mV Inputs)

The Thermocouple/mV Input Interface contains eight isolated thermocouple input channels, and
one isolated RTD reference junction compensation channel (for terminal temperature sensing).
Each thermocouple/mV channel has a full scale indication on burnout feature and accepts Type R
thermocouples.
The module performs the signal conversion required to interface the electrical input signals from
the thermocouples to the redundant Fieldbus.
The module is a main type, and independently connects to the redundant Fieldbus. This module
executes the Analog Input application program. The configurable options and their ranges follow.

233
B0193AW – Rev R Appendix B. Fieldbus Modules

Table B-42. FBM36 Options

Option Range
Analog Input Resolution 0 to 21.1 mV
(on a per-module basis)
Rate of Change Limits (Channels 1-9) Normalized Raw Counts/100 ms

Input Range: 0.1 to 21.1 mV.

Reference Junction:
For discrete and direct terminal connections, a 100 ohm platinum RTD is internally pro-
vided at the termination cable assembly.
For a plug termination connection, the reference junction connection is provided by the
user with a 4-wire 100 ohm platinum RTD (DIN 43760, Class B).
Rated Mean Accuracy: ± 0.025% of span.
Conversion Time (software configurable): see Table B-43.

Table B-43. FBM36 Conversion Time

Conversion Time Settling Time* Linearity Error** Resolution

(Seconds) (Seconds) (% of Range) Bits
0.05 0.2 0.1 11
0.1 0.4 0.05 12
0.2 0.6 0.03 13
0.5 1.2 0.02 14
1.0 2.1 0.02 15
* Value settles within a 1% band of steady state for an input step change of 10 to 90%.
** Monotonic; assures that the signal for Fieldbus communications either increases or
remains the same for increasing analog input signals.

FBM37 (0 to 20 mA Outputs)
The Redundant 0 to 20 mA Output Interface Module (FBM37) consists of a pair of Fieldbus
Modules (two FBM237s), each of which contains eight 0 to 20 mA dc analog output channels.
The module can be used as a nonredundant (single) module or as a redundant pair (two) mod-
ules. The pair of Fieldbus Modules combine to provide redundancy at the Fieldbus Module level,
with associated field output signals wired to two termination assemblies. Each redundant Fieldbus
Module independently attempts to hold the output(s) at its specified output value(s). A redun-
dant analog output (AOUTR) block in the control software validates each output in conjunction
with information from the Fieldbus Module.
The module performs the signal conversion required to interface the electrical output signals to
the field sensors from the redundant Fieldbus.
The module is a main type, and independently connects to the redundant Fieldbus.
This module executes the Analog Output application program. The configurable options and
their ranges follow.

234
Appendix B. Fieldbus Modules B0193AW – Rev R

Table B-44. FBM37 Options

Option Range
Analog Output:
Fail-safe Configuration (Hold/Fallback 0 = fallback; 1 = hold
on a per-channel basis)

Rated Mean Accuracy: ±0.05% of span.

Cluster I/O FBCs

Refer to Fieldbus Cluster I/O User’s Guide (B0193RB) for hardware specifications of the Fieldbus
Cluster modules (FBCs) currently available to I/A Series users.

235
B0193AW – Rev R Appendix B. Fieldbus Modules

236
 Appendix C. FBM – ECB Cross
Reference
The following tables present the complete list of all types of FBMs and equivalents, FCMs and
equivalents, and fieldbus processors. All of these modules and processors interface to control
processors.

Legacy FBMs and Equivalents

The following is a list of legacy FBMs and equivalents. The table heading definitions are as
follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type
♦ EXP – Expander type
♦ Notes – Additional ECBs in use on this FBM.

Table C-1. Legacy FBMs and Equivalents

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
FBM01 0 to 20 mA Input 8A 1 IOM1 1
BAMM01 Bailey RTD 4A 1 IOM1 1
0-320 Ohms
BASM01 Bailey 4 to 20 mA, 16A 47,1,1 IOM56 52,1,
1 to 5 V dc, 0 to 10 V dc, 1
-10 to +10 Vdc
BASI01 Bailey 4 to 20 mA, 15A 47,1,1 IOM56 52,1,
0 to 5 V dc, 0 to 10 V dc, 1
-10 to 10 V dc, 0 to 1 V dc
F1M01A Fisher™ Series 10 8A 1 IOM1 1
1-5 Vdc, 4-20 mA
F1M01C Fisher Series 10 4A 1 IOM1 1
1-5 Vdc, 4-20 mA, ISO
F1M01E Fisher Series 10 8A 1 IOM1 1
0-10 V dc
F1M01F Fisher Series 10 4A 1 IOM1 1
0-10 V dc ISO
FBM02 Thermocouple/mV Input 8A 1 IOM1 2
BASM02 Bailey thermocouple, +/- 8A 1 IOM1 2
100 mV

237
 B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-1. Legacy FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
F1M02 Fisher Series10 4A 1 IOM1 2
-10.2 to 70 mV,
5 kinds of ISO
thermocouple
FBM03 RTD Input 8A 1 IOM1 3
0-320 Ohms
BASI03 Bailey mV, TC, RTD, 16A 47,1,1 IOM55 52,2,
+/-10V 2
BASM03 Bailey RTD 8A 1 IOM1 3
platinum, nickel
0-320 Ohms
BASM33 Bailey RTD copper 8A 1 IOM1 3
0-30 ohms
F1M03A Fisher Series 10 RTD 4A 1 IOM1 3
-50 to 200 F
F1M03C Fisher Series 10 RTD 4A 1 IOM1 3
100 to 500 F
F1M03D Fisher Series 10 RTD 4A 1 IOM1 3
FBM03A RTD 3 wire 8A 1 IOM1 3
(uses FBM03)
FBM03B RTD 4 wire 8A 1 IOM1 3
(uses FBM03)
FBM04 0 to 20 mA 4A 4A 1 IOM2,52 4 PID - ECB52
Input/Output
F1M04A Fisher Series 10 4A 1 IOM2 4
1-5 V dc
F1M04B Fisher Series 10 4A 1 IOM2 4
4-20 mA
FBM05 Redundant 4A 4A 1 IOM2 5
0 to 20 mA Input/Output
FBM06 Pulse Input, 4P 4A 4 IOM4 6
0 to 20 mA Output
BDSI06 Bailey pulse 8P 47,4,4 IOM4 52,6,
6
F1M06 Fisher Series 10 4P 4 IOM4 6 3 types
4-30 V dc,
dry contacts,
or current pulse
FBM07 Contact/dc input 16D 5 IOM5 7
BSEM01 Bailey 24 V dc, 16D 6 IOM6 7 14
48 Vdc, 120 V ac/dc SOE
BDSI07 Bailey 24 V dc, 16D 5 IOM5 7
125 V ac/dc
FBM07A 15 to 130 V dc 16D 5 IOM5-8 7 SOE-ECB6,
(uses FBM07) pulse count-
ECB7, ladder-
ECB8
FBM07B 24 V dc Contact Sense 16D 5 IOM5-8 7 SOE-ECB6,
Input pulse count-
(uses FBM07) ECB7, ladder-
ECB8

238
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-1. Legacy FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
F1M07 Fisher Series 8D 5 IOM5-8 7 SOE-ECB6,
104-30 V dc, pulse count-
dry contact, 120 V ac ECB7,
ladder-ECB8
FBM08 120 V ac Input 16D 5 IOM5-8 SOE-ECB6,
pulse count-
ECB7,
ladder-ECB8
FBM09 Contact/dc Input/Output 8D 8D 5 IOM5 9
BDSM09 Bailey 24 V dc solid state 16D 5 IOM5 9 14
BDSM9A Bailey 24 V dc, 8D 8D 5 IOM5 9
125 V ac/dc/24 V dc
BDSM9B Bailey 24 Vdc 16D 16D 5 IOM5 9 14
F1M09 Fisher Series 10 FET 8D 5 IOM5 9 3 types
4-30 V dc,
relay or relay external
FBM09A Voltage Monit 8D 8D 5 IOM5, 8 9 ladder-ECB8
- 15 to 130 V dc Input,
60 V dc @ 0.5 mV Output
FBM09B Voltage Monit 8D 8D 5 IOM5, 8 9 ladder-ECB8
- 15 to 130 V dc Input,
0 to 10 V dc Output
FBM09C Contact Sense - 24 V dc 8D 8D 5 IOM5,8 9 ladder-ECB8
Input, 60 V dc @ 0.5 mV
Output
FBM09D Contact Sense 8D 8D 5 IOM5,8 9 ladder-ECB8
- 24 V dc Input,
0 to 10 V dc Output
FBM10 120 V ac Input/Output 8D 8D 5 IOM5, 8 ladder-ECB8
BDSO10 Bailey 24-240 V dc solid 8D 5 IOM5, 8 10 14 ladder-ECB8
state
FBM11 240 V ac 8D 8D 5 IOM5, 8 11 ladder-ECB8
Input/Output
FBM12 FBM07 Expander 16D see 12
above
FBM12A FBM07A Expander 16D see 12
above
FBM12B FBM07B Expander 16D see 12
above
FBM13 FBM08 Expander 16D see 13
above
FBM14 FBM09 Expander 8D 8D see 14
above
FBM14A FBM09A Expander 8D 8D see 14
above
FBM14B FBM09B Expander 8D 8D see 14
above
FBM14C FBM09C Expander 8D 8D see 14
above
FBM14D FBM09D Expander 8D 8D see 14
above

239
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-1. Legacy FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
FBM15 FBM10 Expander 8D 8D see 15
above
FBM16 FBM11 Expander 8D 8D see 16
above
FBM17 0 to 10 V dc, 4A, 2A, 9 IOM9,34 17 MDACT -
Contact/dc Input/Output 4D 4D , ECB34,
36,52 MDPulse -
ECB36,
PID - ECB52
FBM17A 15 to 130 V dc Input, 4A, 2A, 9 IOM9,34 17 MDACT -
60 V dc @ 0.5 mV Output 4D 4D , ECB34,
36,52 MDPulse -
ECB36,
PID - ECB52
FBM17B 15 to 130 V dc Input, 4A, 2A, 9 IOM9,34 17 MDACT -
0 to 10 V dc 4D 4D , ECB34,
Output 36,52 MDPulse -
ECB36,
PID - ECB52
FBM17C 24 V dc Input, 4A, 2A, 9 IOM9,34 17 MDACT -
60 V dc @ 0.5 mV Output 4D 4D , ECB34,
36,52 MDPulse -
ECB36,
PID - ECB52
FBM17D 24 V dc Input, 4A, 2A, 9 IOM9,34 17 MDACT -
0 to 10 V dc 4D 4D , ECB34,
Output 36,52 MDPulse -
ECB36,
PID - ECB52
FBM18 Intelligent Transmitter 8 In 12 IOM12, 18 Multibaud-
Input/Output 37 ECB37
FBM19 {unspecified AIN} ?A 1 IOM1 19
FBM20 240 V ac Input 16D 5 IOM5-8 20 SOE-ECB6,
pulse count-
ECB7,
ladder-ECB8
FBM21 FBM20 Expander 16D see 21
above
FBM22 Single 0 to 20 mA 1A 1A 9 IOM9,52 22 PID - ECB52
Input/Output Auto/Manual
FBM23 HTG Interface Unit 32D 13 IOM13 23
(HIU)
FBM24 Contact/125 V dc Input - 16D 5 IOM5-8 24 SOE-ECB6,
External Power pulse count-
ECB7, ladder-
ECB8
FBM24A 24 to 125 V dc 16D 5 IOM5-8 24 SOE-ECB6,
Input/Output pulse count-
ECB7, ladder-
ECB8

240
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-1. Legacy FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
FBM24B Contact Sense 16D 5 IOM5-8 24 SOE-ECB6,
Input/Output pulse count-
ECB7, ladder-
ECB8
FBM24C Contact Sense Input/Out- 15D 5 IOM5-8 24
put - External Power
(16th=power connection)
FBM25 FBM24 Expander 16D see 25
above
FBM25A FBM24A Expander 16D see 25
above
FBM25B FBM24B Expander 16D see 25
above
FBM25C FBM24C Expander 16D see 25
above
FBM26 Contact/125 V dc Input/ 8D 8D 5 IOM5, 8 26 ladder-ECB8
Output - External
BDSO26 Bailey 4 -50 V dc solid 8D 5 IOM5, 8 26 14 ladder-ECB8
state
FBM26A 24 to 125 V dc Input 8D 8D 5 IOM5, 8 26 ladder-ECB8
(uses FBM26)
FBM26B Contact Sense Input 8D 8D 5 IOM5, 8 26 ladder-ECB8
(uses FBM26)
FBM26C Contact Sense Input - 7D 8D 5 IOM5, 8 26 ladder-ECB8
External Power
(8th=external power)
FBM27 FBM26 Expander 8D 8D see 27
above
FBM27A FBM26A Expander 8D 8D see 27
above
FBM27B FBM26B Expander 8D 8D see 27
above
FBM27C FBM26C Expander 8D 8D see 27
above
FBM33 Copper RTD Input, 8A 1 IOM1 33
Expanded Range
FBM33A Expanded Range Copper 8A 1 IOM1 33
RTD 3-wire
FBM33B Expanded Range Copper 8A 1 IOM1 33
RTD
2- and 4-wire
FBM36 Type R 8A 1 IOM1 36
Thermocouple/mV Input
FBM37 0-20 mA Output 8A 53 IOM53 37
BAS037 Bailey 1 to 5 V dc, 14A 47,53, IOM56 52,
4 to 20 mA 53 37,37
BAOM37 Bailey 0 to 10 V dc, 8A 53 IOM53 37
1 to 5 V dc,
4 to 20 mA
FBM38 Coriolis Mass Flow Coriolis 22 IOM22

241
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-1. Legacy FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT EXP Notes
FBM39 Intelligent Transmitter 4 IT 4A 23 IOM38 39 Multibaud -
Inputs/ ECB38
0 to 20 mA Out
FBM41 Isolated Contact 24 V dc 8D 8D 5 IOM5, 8 41 ladder-ECB8
In/0 to 60 V dc Out
BDSO41 Bailey 5-160 dc solid state 8D 5 IOM5, 8 41 14 ladder-ECB8
FBM41A 15 to 60 V dc Input, 0 to 8D 8D 5 IOM5, 8 41 ladder-ECB8
60 V dc @ 2.25 A Output
FBM41C 24 V dc Contact Sense 8D 8D 5 IOM5, 8 41 ladder-ECB8
Input,
0 to 60 V dc @ 2.25 A
Output
FBM42 FBM41 Expander 8D 8D see 42
above
FBM42A FBM41A Expander 8D 8D see 42
above
FBM42C FBM41C Expander 8D 8D see 42
above
FBM43 Dual Baud Rate Intell. 8 IT 12,73 IOM37, 43 foxcom -
Device Interface 73 ECB73 (parent
18, 43), ECB12
(parent 18)
FBM44 Dual Baud Rate 4 IT 4A 23 IOM38 44
IT/0 to 20 mA Out
Redundant Output
FBM45 Gas ?? ?? 39 IOM39 45
Chromatograph
FBM46 Dual Baud Rate 4 IT 4A 38R IOM49 98
IT/0 to 20 mA In/Out
Redundant

Fieldbus Processors
The following is a list of fieldbus processors. The table heading definitions are as follows:
♦ Type – FBP Type
♦ Signal Description – Purpose of FBP
♦ In – Number of input channels (dependent on I/O cards)
♦ Out – Number of output channels (dependent on I/O cards)
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM Number – The software that is downloaded to this FBM
♦ HWT – Hardware type.

242
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-2. Fieldbus Cluster Modules

SW
Type Signal Description In Out ECB# IOM# HWT
FBP10 Eckardt Migration 47 IOM42 52
FBP10R Eckardt Migration 47R IOM47 87
(Redundant)
FBP11 Spectrum UCM 43 IOM43 53
FBP11R Spectrum UCM 48 IOM48 88
(Redundant)
FBP12 Spectrum FIO™ N/A N/A 44 IOM44 54
FBP13 Spectrum UFM™ N/A N/A 45 IOM45 55
FBP14 Spectrum UIO 46 IOM46 56

Eckardt I/O Cards

The following is a list of I/O cards that are found in Eckardt racks.The table heading definitions
are as follows:
♦ Type – FBP Type
♦ Signal Description – Purpose of FBP
♦ In – Number of input channels (dependent on I/O cards)
♦ Out – Number of output channels (dependent on I/O cards)
♦ SW ECB# – Equipment control block software type used for this FBM
♦ HWT – Hardware type.

Table C-3. Eckardt Rack I/O Cards

Type Signal Description In Out SW ECB# HWT

FBC01 0 to 20 mA Inputs 32A 41 58
FBC01R 0 to 20 mA (Redundant) 32A 41 90
FBC02 Thermocouple Inputs 32A 41 63
FBC02R Thermocouple (Redundant) 32A 41 95
FBC04 0 to 20 mA Outputs 16A 43 61
FBC04R 0 to 20 mA (Redundant) 16A 43 93
FBC07 Contact/DC Inputs 32D 42 60
FBC07R Contact/DC (Redundant) 32D 42 92
FBC09 Contact/DC Outputs 32D 44 62
FBC09R Contact/DC (Redundant) 32D 44 94
FBC10 Contact/DC Input/Output 32D 32D 46 86
FBC10R Contact/DC (Redundant) 32D 32D 46 97
FBC17 0 to 10 V DC Inputs 32A 41 59
FBC17R 0 to 10 V DC (Redundant) 32A 41 91
FBC21 0 to 20 mA Inputs 16A 41 57
FBC21R 0 to 20 mA (Redundant) 16A 41 89

243
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

UCM/UIO
The following is a list of I/O cards that can be found in either UCM or UIO racks. The table
heading definitions are as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ HWT – Hardware type.

Table C-4. UCM or UIO Rack I/O Cards

SW
Type Signal Description In Out ECB# HWT
3A2-V2D High Lvl ISO 2A 41 65
3A2-V3D High Level 2A 41 65
3A2-E2D AC Voltage input 2A 41 65
3A2-I2D ISO Current Input 2A 41 65
3A2-I2DA ISO High Lvl 2A 41 65
3A2-I3D Current Input 2A 41 65
3A2-I3DA High Level 2A 41 65
3A2-H3D High Level 2A 41 65
3A4-I2D Quad Current In 4A 41 66
3A2-M2D MV/TC Adj Range 2A 41 65
3A2-T2DJ1 Thermocouple Input 2A 41 68
3A2-T2DJ2 Thermocouple Input 2A 41 68
3A2-T2DK1 Thermocouple Input 2A 41 68
3A2-T2DK2 Thermocouple Input 2A 41 68
3A4-M2DA1 Millivolt/TC Input 2A 41 69
3A4-M2DA2 Millivolt/TC Input (4 channel UCM ONLY) 4A 41 69
3A4-M2DA3 Millivolt/TC Input (4 channel UCM ONLY) 4A 41 69
3A4-M2DA4 Millivolt/TC Input (4 channel UCM ONLY) 4A 41 69
3A4-M2DA5 Millivolt/TC Input (4 channel UCM ONLY) 4A 41 69
3A4-M2DA6 Millivolt/TC Input (4 channel UCM ONLY) 4A 41 69
3A4-M2DA7 Millivolt/TC Input(4 channel UCM ONLY) 4A 41 69
3A2-R2DC Copper RTD 2A 41 71
3A2-R2DN Nickel RTD 2A 41 71
3A2-R2DP Plat 1 RTD 2A 41 71
3A2-R2DP Plat 2 RTD 2A 41 71
3A2-R2DP Plat 3 RTD 2A 41 71
3A2-R2DP2 Plat RTD 2A 41 71
3C8-C3D Octal Contact In 8D 42 77
3C8-E2D Octal Line V Mon 8D 42 77
3A2-F2D Pulse Rate Counter 2P 41 75
3A2-Q2D Pulse Input Count 2P 41 73
3A2-D3V Dual Voltage Out 2A 43 78

244
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-4. UCM or UIO Rack I/O Cards (Continued)

SW
Type Signal Description In Out ECB# HWT
3A2-D2I Dual Current Out 2A 43 78
3A2-D3I Dual Current Out 2A 43 78
3C4-D2CS dc Switch Out 4D 44 80
3C4-D2KS ac Switch Out 4D 44 80
3C8-D2CS Octal Contact Out 8D 44 81
3C4-D2VS dc Volt Out 4D 44 80
3C4-D2CP dc Pulse Out 4D 44 82
3C4-D2KP ac Pulse Out 4P 44 82
3C4-D2VP dc Pulse Out 4P 44 82
3AS-I2I Single Loop I/O 1A 1A 45 84
3AS-I3I Single Loop I/O 1A 2A 45 84
3AD-I3I Dual Loop I/O (4 channel UCM ONLY) 2A 2A 45 85

FIO
The following is a list of I/O cards that can be found in FIO racks. The table heading definitions
are as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ HWT – Hardware type.

Table C-5. FIO Rack I/O Cards

SW
Type Signal Description In Out ECB# HWT
3F8-V2DA1 Octal High Level 8A 41 67
3F8-V2DA2 Octal High Level 8A 41 67
3F8-V2DA Octal High Level 8A 41 67
3F4-I2D1A Quad 0-20mAdc, 16V 4A 41 66
3F4-I2D2A Quad 0-20mAdc, 22V 4A 41 66
3F8-I2DA Octal High Level 8A 41 67
3F8-H2DA Octal High Level 8A 41 67
3F8-T2DA1 Octal Thermocouple 8A 41 70
3F8-T2DA2 Octal Thermocouple 8A 41 70
3F8-T2DA3 Octal Thermocouple 8A 41 70
3F8-T2DA4 Octal Thermocouple 8A 41 70
3F8-T2DA5 Octal Thermocouple 8A 41 70
3F8-T2DA6 Octal Thermocouple 8A 41 70
3F8-T2DA7 Octal Thermocouple 8A 41 70
3F8-M2DA1 Octal Millivolt 8A 41 67
3F8-M2DA2 Octal Millivolt 8A 41 67

245
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-5. FIO Rack I/O Cards (Continued)

SW
Type Signal Description In Out ECB# HWT
3F8-M2DA3 Octal Millivolt 8A 41 67
3F8-M2DA4 Octal Millivolt 8A 41 67
3F8-M2DA5 Octal Millivolt 8A 41 67
3F8-M2DA6 Octal Millivolt 8A 41 67
3F8-M2DA7 Octal Millivolt 8A 41 67
3F8-R2DCA Octal RTD (Copper) 8A 41 72
3F8-R2DNA Octal RTD (Nickel) 8A 41 72
3F8-R2DPA1 Octal RTD (Plat 1) 8A 41 72
3F8-R2DPA2 Octal RTD (Plat 2) 8A 41 72
3F8-R2DPA3 Octal RTD (Plat 3) 8A 41 72
3F8-C2DCA Octal Contact 8D 42 77
3F8-C2DNA Octal Prox Sensor 8D 42 77
3F8-E2DA Octal HL Digital 8D 42 77
3F4-F2DA Quad Pulse Rate 4P 41 76
3F4-Q2DA Quad Pulse Counter 4P 41 74
3F4-D2VA Quad High Lvl Out 4A 43 79
3F4-D2IA Quad High Lvl Out 4A 43 79
3F8-D2CSA Octal dc Switch 8D 44 81
3F8-D2ZA Octal Solenoid Dvr 8D 44 81
3F8-D2KSA Octal ac Switch 8D 44 81
3F4-D2WA Quad Solenoid Dvr 4D 44 80
3F8-D2CPA Octal dc Pulse Sw 8P 44 83
3F8-D2KPA Octal ac Pulse Sw 8P 44 83

UFM
The following is a list of I/O cards that can be found in UFM racks. The table heading definitions
are as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type.

Table C-6. UFM Rack I/O Cards

SW
Type Signal Description In Out ECB# HWT
3A8-V2D1 Octal High Level 41 67
3A8-I2D1 Octal High Level 41 67
3A8-M2D1 Octal Millivolt 41 67
3A8-M2D2 Octal Millivolt 41 67

246
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-6. UFM Rack I/O Cards (Continued)

SW
Type Signal Description In Out ECB# HWT
3A8-M2D3 Octal Millivolt 41 67
3A8-T2D1 Octal Thermocouple 41 70
3A8-T2D2 Octal Thermocouple 41 70
3A8-T2D3 Octal Thermocouple 41 70
3A8-R2DC1 Octal RTD (Copper) 41 72
3A8-R2DN1 Octal RTD (Nickel) 41 72
3A8-R2DP1 Octal RTD (Plat 1) 41 72
3A8-R2DP2 Octal RTD (Plat 2) 41 72
3A8-R2DP3 Octal RTD (Plat 3) 41 72
3D8-C2D1 Octal Contact 42 77

Fisher Series 20 Migration Cards

The following is a list of Fisher Series 20 migration cards. The table heading definitions are as
follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type
♦ Notes – Additional ECBs in use on this FBM.

Table C-7. Fisher Series 20 Migration Cards

SW
Type Signal Description In Out ECB# IOM# HWT Notes
F2M67A Fisher Series 20 16D 16D 47,5 IOM59 52,9 16 I/O channels -
FBP10, FBM09 Jumper for either input
or output only
F2M68A Fisher Series 20 16A 8A 47,1, IOM58 52,1,3 Inputs and Outputs are
FBP10, 2 FBM01s, 53 7 independent and both
FBM37 may be used
FRM701 Fisher Controller 4A, 2D 1A, 7D 47,9 IOM57 52,17
Configurable FBP10,
1 or 2 FBM17s
FRM711 Fisher Controller 5A, 4D 2A, 2D 47,9 IOM57 52,17
Computing FBP10,
1 or 2 FBM17s
FRMMPU Fisher Controller 10A, 3A, 4D 47,9,1 IOM57 52,17,
FBP10, 2 FBM17, 4D 1
FBM01

247
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

DIN 200 FBMs and Equivalents

The following is a list of DIN 200 FBMs and equivalents. The table heading definitions are as
follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type
♦ Notes – Additional ECBs in use on this FBM.

Table C-8. DIN 200 FBMs and Equivalents

SW
Type Signal Description In Out ECB# IOM# HWT Notes
FBM201 8 Input, 0-20 mA 8A 1 IOM83 201
WAI01A Westinghouse 4A 1 IOM83 201
-512 to +512 mV dc
WAI01B Westinghouse 4A 1 IOM83 201
-1.02 to +1.02 V dc
WAI01C Westinghouse 4A 1 IOM83 201
-10.24 to +10.24 V dc
WAI01D Westinghouse 4A 1 IOM83 201
0 to 20.48 mA
WAW01A Westinghouse 6A 1 IOM83 201
0 to 1.02 V dc
WAW01B Westinghouse 6A 1 IOM83 201
0 to 5.12 V dc
WAW01C Westinghouse 6A 1 IOM83 201
0 to 10.24 V dc
WAW01D Westinghouse 6A 1 IOM83 201
0 to 20.48 mA
WAW01E Westinghouse 6A 1 IOM83 201
0 to 20.48 mA
WAW01F Westinghouse 6A 1 IOM83 201
0 to 51.2 mA
WAX01A Westinghouse 12A 1 IOM83 (2) 201
0 to 1.02 V dc
WAX01B Westinghouse 12A 1 IOM83 (2) 201
0 to 5.12 V dc
WAX01C Westinghouse 12A 1 IOM83 (2) 201
0 to 10.24 V dc
FBM202 8 Input, 8A 1 IOM84 202
Thermocouple/mV
WAI02A Westinghouse 4A 1 IOM84 202
-100 to +100 mV thermo
WAV02A Westinghouse 6A 1 IOM84 202
-100 to +100 mV thermo

248
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-8. DIN 200 FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
WAX02A Westinghouse 12A 1 IOM84 (2) 202
-100 to +100 mV thermo
FBM202B 8 Input, 8A 1 IOM84 202
Thermocouple/mV
(Type R)
FBM203 8 Input, RTD 8A 1 IOM85 203
(Pt, Ni)
WRF03A Westinghouse 6A 1 IOM85 203
0 to 640 ohm RTD
WRF03B Westinghouse 6A 1 IOM85 203
0 to 320 ohm RTD
WRT03A Westinghouse 4A 1 IOM85 203
0 to 30 ohm RTD
WRT03B Westinghouse 4A 1 IOM85 203
0 to 320 ohm RTD
FBM203B 8 Input, RTD (Pt,Ni,Cu) 8A 1 IOM85 203
FBM204 4 Input, 0-20 mA / 4 Out- 4A 4A 2 IOM86 204 PID - ECB52
put, 0-20 mA
WLJ04A Westinghouse 9A 3A 2 IOM86 204 PID - ECB52
0 to 10.24 V dc
WLJ04B Westinghouse 9A 3A 2 IOM86 204 PID - ECB52
0 to 5.12 V dc/10.24 V dc
WLJ04C Westinghouse 9 AIN/ 3A 2 IOM86 204 PID - ECB52
0 to 20.48 mA 3 AO
FBM205 4 Input,0-20 mA / 4 Out- 4A 4A 2 IOM87 205
put, 0-20 mA
(Redundant capable)
FBM206 8 Input, Pulse 8P 4 IOM88 206
WPA06A Westinghouse Pulse 4D 4 IOM88 206
Counter
FBM207 16 Input, 16D 5 IOM89 207 SOE-ECB6,
Voltage Monitor pulsect-ECB7,
ladder-ECB8
WCI07A Westinghouse 16D 5 IOM89 207
48 V dc
WDI07A Westinghouse 16D 5 IOM89 207
5 V dc
WDI07B Westinghouse 16D 5 IOM89 207
24 V ac/dc
WDI07C Westinghouse 16D 5 IOM89 207
48 V ac/dc
WDI07D Westinghouse 16D 5 IOM89 207
120 V ac/dc
WDI07E Westinghouse 16D 5 IOM89 207
12 V dc
WID07A Westinghouse 5 V dc 16D 5 IOM89 207
WID07B Westinghouse 24 V ac/dc 8D 5 IOM89 207
WID07C Westinghouse 24 V ac/dc 16D 5 IOM89 207
WID07D Westinghouse 48 V ac/dc 8D 5 IOM89 207
WID07E Westinghouse 48 V ac/dc 16D 5 IOM89 207

249
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-8. DIN 200 FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
WID07F Westinghouse 8D 5 IOM89 207
120 V ac/dc
WID07G Westinghouse 16D 5 IOM89 207
120 V ac/dc
WID07H Westinghouse 12 V dc 16D 5 IOM89 207
WID07I Westinghouse 12 V ac/dc 16D 5 IOM89 207
WID07J Westinghouse 16D 5 IOM89 207
48 V dc pulse
WID07K Westinghouse 120 V ac, 8D 5 IOM89 207
high threshold
WID07L Westinghouse 120 V ac, 16D 5 IOM89 207
high threshold
WID07M Westinghouse 220 V ac 8D 5 IOM89 207
WID07N Westinghouse 220 V ac 16D 5 IOM89 207
WID07O Westinghouse 220 V dc 8D 5 IOM89 207
WID07P Westinghouse 220 V dc 16D 5 IOM89 207
FBM207B 16 Input, 24 V dc Contact 16D 5 IOM89 207 SOE-ECB6, pulsect-
Sense ECB7, ladder-ECB8
FBM207C 16 Input, 48 V dc Contact 16D 5 IOM89 207 SOE-ECB6, pulsect-
Sense ECB7, ladder-ECB8
FBM211 16 Input, 0-20 mA 16A 1 IOM90 211
Differential
WAH01A Westinghouse 4A 1 IOM90 211
-10.24 to +10.24 V dc
WAH01B Westinghouse 4A 1 IOM90 211
-5.12 to +5.12 V dc
WAH01C Westinghouse 4A 1 IOM90 211
0 to +10.24 V dc
WAH01D Westinghouse 4A 1 IOM90 211
0 to +5.12 V dc
FBM212 16 Input, Thermocou- 14A 1 IOM91 212
ple/mV Differential
FBM213 8 Input, RTD 8A 1 IOM92 213
(Pi, Ni) Differential
FBM214 8 Communication, 8 In 200/ IOM 214
HART Input 201 214
FBM215 8 Communication, 8 Out 200/ IOM 215
HART Output 201 215
FBM216 8 Communication, 8 In 201/ IOM 216
HART Input (Redundant) 202 216
FBM217 32 Input, Voltage Monitor 32D 5 IOM96 217 SOE-ECB6, pulse
(Group Isolated) count-ECB7,
ladder-ECB8
FBM218 8 Communication, HART 8 Out 201/ IOM 218
Output (Redundant) 202 218
FBM219 24 Input, Voltage Moni- 24D 8D 5 IOM98 219 ladder-ECB8
tor/8 Output, Switch
(External Source)

250
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-8. DIN 200 FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
FBM219B 24 Input, Voltage Moni- 24D 8D 5 IOM98 219 ladder-ECB8
tor/8 Output, Switch
(Internal Source)
FBM220 1 Communication Port, 1 In 1 Out 200/ IOM 220
Fieldbus Foundation 201 220
FBM221 4 Communication Ports, 4 In 4 Out 200/ IOM 221
Fieldbus Foundation 201 221
FBM223 2 Communication Ports, 2 In 2 Out 200/ IOM 223
Profibus DP 201 223
FBM224 4 Communication Ports, 4 In 4 Out 200/ IOM 224 2000 pts/
Modbus (Redundant 201 224 64 devices
capable)
FBM237 8 Output, 0-20 mA 8A 53 IOM93 237
WAO37A Westinghouse 4A 53 IOM93 237
0 to 20.48 mA
WAO37B Westinghouse 4A 53 IOM93 237
0 to 10.24 V dc
WAO37C Westinghouse 4A 53 IOM93 237
-10.24 to 10.24 V dc
WAO37D Westinghouse 4A 53 IOM93 237
0 to 5.12 V dc
WAO37E Westinghouse 4A 53 IOM93 237
-5.12 to 5.12 V dc
WAO37F Westinghouse 4A 53 IOM93 237
-10.24 to 10.24 V dc
WAO37G Westinghouse 4A 53 IOM93 237
0 to 20.48 mA
FBM241 8 Input, Voltage Moni- 8D 8D 5 IOM94 241 ladder-ECB8
tor/8 Output, Switch
(External Source)
FBM241B 8 Input, Voltage Moni- 8D 8D 5 IOM94 241 ladder-ECB8
tor/8 Output, Switch
(Internal Source)
FBM241C 8 Input, Contact Sense/8 8D 8D 5 IOM94 241 ladder-ECB8
Output, Switch (External
Source)
FBM241D 8 Input, Contact Sense/8 8D 8D 5 IOM94 241 ladder-ECB8
Output, Switch (Internal
Source)
FBM242 16 Output, DC Switch 16D 5 IOM95 242 ladder-ECB8
(External Source)
WBO09A Westinghouse 60 V dc 16D 5 IOM95 242
WBO09B Westinghouse 20 V dc 16D 5 IOM95 242
WRO09A Westinghouse inductive, 4D 5 IOM95 242
mercury
WRO09B Westinghouse non- 4D 5 IOM95 242
inductive, mercury
WRO09C Westinghouse inductive, 4D 5 IOM95 242
solid state
WRO09D Westinghouse non- 4D 5 IOM95 242
inductive, solid state

251
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-8. DIN 200 FBMs and Equivalents (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
WTO09A Westinghouse triac 8D 5 IOM95 242
FBM243 8 Channel Isolated, dual 8 In 8 Out 73 IOM97 243
baud rate FoxCom (Intell.
Dev.)
FBM246 4 Redundant Channel 4 In 4 Out 73 IOM97 246 parent ECB 18 or 74
Isolated, dual baud rate
FoxCom (Intell. Dev.)

Honeywell TDC2000 Migration Cards

The following is a list of Honeywell™ TDC2000 migration cards. The table heading definitions
are as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type
♦ Notes – Additional ECBs in use on this FBM.

Table C-9. Honeywell TDC2000 Migration I/O Cards

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H2C02A Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA,
(4) 5 V dc or +/- 5 V dc
H2C02B Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA,
(4) 40 V dc or +/- 40 V dc
H2C02D Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA, (4) 0-1 mA
H2C02E Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA, (4) 0-10 mA
H2C02F Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA,
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc
H2C02G Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA,
(4) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt
H2C02H Honeywell TDC2000 8A 1 IOM1 2
(4) 4-20.4 mA, (4) 1 V dc or
+/- 1 V dc

252
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-9. Honeywell TDC2000 Migration I/O Cards (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H2C02J Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA,
(4) 5 V dc or +/- 5 V dc
H2C02K Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA,
(4) 40 V dc or +/- 40 V dc
H2C02L Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA, (4) 4-20.4 mA
H2C02M Honeywell TDC2000 8A 1 IOM1 2
(8) 0-1 mA
H2C02N Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA, (4) 0-10 mA
H2C02P Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA, (4) -10.5-71.419
or 0-100 or +/-100 mV dc
H2C02Q Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA, (4) 0-30 ohm Cu,
120 ohm Ni or 320 ohm Pt
H2C02R Honeywell TDC2000 8A 1 IOM1 2
(4) 0-1 mA, (4) 1 Vdc or
+/- 1 V dc
H2C02S Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 5 V dc or
+/- 5 V dc
H2C02T Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 40 V dc or
+/- 40 V dc
H2C02U Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 4-20.4 mA
H2C02V Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 0-1 mA
H2C02W Honeywell TDC2000 8A 1 IOM1 2
(8) 0-10 mA
H2C02X Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) -10.5-71.419
or 0-100 or +/-100 mV dc
H2C02Y Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 0-30 ohm
Cu, 120 ohm Ni or
320 ohm Pt
H2C02Z Honeywell TDC2000 8A 1 IOM1 2
(4) 0-10 mA, (4) 1 Vdc or
+/- 1 V dc
H2D02A Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 5 V dc
H2D02B Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 40 V dc
H2D02C Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 4-20.4 mA

253
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-9. Honeywell TDC2000 Migration I/O Cards (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H2D02D Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 0-1 mA
H2D02E Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 0-10 mA
H2D02G Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 30ohm Cu,
120ohm Ni or 320ohm Pt
H2D02H Honeywell TDC2000 8A 1 IOM1 2
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc, (4) 1 V dc or
+/- 1 V dc
H2J02A Honeywell TDC2000 8A 1 IOM1 2
(4) Ref RTD for TC, (4) 5 V dc
or +/- 5 V dc
H2J02B Honeywell TDC2000 8A 1 IOM1 2
(4) Ref RTD for TC,
(4) 40 V dc or +/- 40 V dc
H2J02C Honeywell TDC2000 8A 1 IOM1 2
(4) Ref RTD for TC,
(4) 4-20.4 mA
H2J02D Honeywell TDC2000 8A 1 IOM1 2
(4) Ref RTD for TC,
(4) 0-1 mA
H2J02E Honeywell TDC2000 8A 1 IOM1 2
(4) Ref RTD for TC,
(4) 0-10 mA
H2J02F Honeywell TDC2000 (4) Ref 8A 1 IOM1 2
RTD for TC,
(4) -10.5-71.419 or 0-100 or
+/-100 mV dc
H2J02G Honeywell TDC2000 (4) Ref 8A 1 IOM1 2
RTD for TC, (4) 0-30 ohm Cu,
120 ohm Ni or 320 ohm Pt
H2J02H Honeywell TDC2000 (4) Ref 8A 1 IOM1 2
RTD for TC, (4) 1 V dc or
+/- 1 V dc
H2M01A Honeywell TDC2000 5 V dc 8A 1 IOM1 2
or 1-5 V dc or +/- 5 V dc
H2M01B Honeywell TDC2000 4-20 8A 1 IOM1 2
mA
H2M01C Honeywell TDC2000 8A 1 IOM1 2
4-20 mA (powered)
H2M01D Honeywell TDC2000 8A 1 IOM1 2
4-20 mA
H2M02 Honeywell TDC2000 8A 1 IOM1 2
-10.5-71.419 or 0-100 or +/-
100 mV dc
H2M02A Honeywell TDC2000 5 V dc 8A 1 IOM1 2
or +/- 5 V dc

254
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

Table C-9. Honeywell TDC2000 Migration I/O Cards (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H2M02B Honeywell TDC2000 8A 1 IOM1 2
40 V dc or +/- 40 V dc
H2M02E Honeywell TDC2000 8A 1 IOM1 2
-10.5-71.419 or
0-100 or +/-100 mV dc (on
card cold junc sense)
H2M03 Honeywell TDC2000 8A 1 IOM1 3
(4) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt, (4) 5 V dc or
+/- 5 V dc
H2M03A Honeywell TDC2000 8A 1 IOM1 3
(4) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt, (4) 40 V dc or
+/- 40 V dc
H2M03B Honeywell TDC2000 8A 1 IOM1 3
(4) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt, (4) 4-20.4 mA
H2M03C Honeywell TDC2000 (4) 0-30 8A 1 IOM1 3
ohm Cu, 120 ohm Ni or 320
ohm Pt, (4) 0-1 mA
H2M03D Honeywell TDC2000 (4) 0-30 8A 1 IOM1 3
ohm Cu, 120 ohm Ni or 320
ohm Pt, (4) 0-10 mA
H2M03E Honeywell TDC2000 (4) 0-30 8A 1 IOM1 3
ohm Cu, 120 ohm Ni or 320
ohm Pt, (4) -10.5-71.419 or
0-100 or +/-100 mV dc
H2M03F Honeywell TDC2000 8A 1 IOM1 3
(8) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt
H2M03G Honeywell TDC2000 8A 1 IOM1 3
(4) 0-30 ohm Cu, 120 ohm Ni
or 320 ohm Pt Ref RTD for
TC, (4) 1 V dc or +/- 1 V dc
H2M04 Honeywell TDC2000 4A 1 IOM2 4
0-20.4 mA
H2M06 Honeywell TDC2000 24 V dc 4P 4 IOM4 6
or 48 V dc external pulse
H2M06A Honeywell TDC2000 4P 4 IOM4 6
125 V dc external pulse
H2M07 Honeywell TDC2000 5 V dc 16D 5 IOM5 7
(jumper input source or
power bus)
H2M07E Honeywell TDC2000 16D 5 IOM5 7
24 V dc (supplied at term.)
H2M09 Honeywell TDC2000 60 V dc 8D 5 IOM5 9
contact
H2M17 Honeywell TDC2000 4A 2A, 9 IOM9,34, 17 MDACT -
5 V dc in, 4D 36, ECB34,
(2) 0-20.4 mA 52 MDPulse -
(4) 60 Vdc out ECB36,
PID - ECB52

255
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

Table C-9. Honeywell TDC2000 Migration I/O Cards (Continued)

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H2M24 Honeywell TDC2000 16D 5 IOM 24 SOE-ECB6,
125 V dc contact (external 5-8 pulse count-
power) ECB7, ladder-
ECB8
H2M26 Honeywell TDC2000 8D 5 IOM5,8 26 ladder-ECB8
125 V dc

Honeywell TDC3000 Migration Cards

The following is a list of Honeywell TDC3000 migration cards. The table heading definitions are
as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ In – Number of input channels
♦ Out – Number of output channels
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type
♦ Notes – Additional ECBs in use on this FBM.

Table C-10. Honeywell TDC3000 Migration I/O Cards

SW
Type Signal Description In Out ECB# IOM# HWT Notes
H3M01 Honeywell TDC3000 16A 1,47 IOM01, 1,52 sw type is
0 to 5 V dc, 1 to 5 V dc, IOM54 42 before
4 to 20 mA 6.1.1
H3M03 Honeywell TDC3000 8A 3 IOM01
-10.5-+71.4 mV, 0-5 V, 0-100 mV,
thermoc, RTD
H3M06 Honeywell TDC3000 8P 4 IOM04 6 dual
pulse input FTAs FBM06s
H3M07 Honeywell TDC3000 32D 6 IOM05 7
digital input FTAs
H3M09 Honeywell TDC3000 16D 5 IOM05 9
digital output FTAs
H3M37 Honeywell TDC3000 analog out- 8A 53 IOM53 37
put FTAs 0 to 20.4 mA

256
Appendix C. FBM – ECB Cross Reference B0193AW – Rev R

FCMs and Equivalents

The following is a list of FCMs and equivalents. The table heading definitions are as follows:
♦ Type – FBM Type
♦ Signal Description – Purpose of FBM
♦ SW ECB# – Equipment control block software type used for this FBM
♦ IOM – The software that is downloaded to this FBM
♦ HWT – Hardware type.

Table C-11. FCMs and Equivalents

Type Signal Description SW ECB# IOM# HWT

FBI10E half-y version of FCM 110 IOM82 200
FCM10E DIN/copper version of FCM 110 IOM82 200
FCM10Ef Fibre version of FCM 110 IOM82 200
WFCM10E Westinghouse DIN/copper version of FCM 110 IOM82 200
WFCM10Ef Westinghouse fibre version of FCM 110 IOM82 200
DCM10E DIN rail mount version of FCM 110 IOM82 200

257
B0193AW – Rev R Appendix C. FBM – ECB Cross Reference

258
Index
A
Absolute alarming 91
Alarm types
absolute 91
block 79
deviation 93
mismatch 95
out of range 95
output 91
pretarget 92
process 79, 90
rate of change 96
sequence operational error 97
state change 97
trip 98
Alarms
Alarm Status (ALMSTA) 83, 84, 87, 89
indicators 80
messages 82
Application states
about 138
auto 139
auto/manual transitions 141
manual 139
semi-auto 139

B
Balun module 218
Basic Processing Cycle (BPC) 67
Block
access 13
attributes 13
function types 16
sizes 14
Block alarming 79
Block initialization
explicit 31, 32
PID blocks in manual state 36
Block parameters 14
editable parameters 16
Block states
bad state 46
define state 46
manual/auto states 48

259
B0193AW – Rev R Index

shutdown state 45
Block status
events 53
indicators 51
Block Status (BLKSTA) 49
BPC
block algorithm schedules 139
overruns 145
processing order 144

C
Cable Balun 218
Cascade
operational description 33
standard configuration 37
Clamping 41
Communication Failure (COMMF) 116
Communications
peer-to-peer 9
Compound
access 6
attributes 5
functions 4
process alarming 5
rules 4
Compound parameters 8, 10
Compound phasing 72
Compound/block parameters 6
configurable 6
connectable 6
nonconnectable 7
Compound/block phasing 5
Compound/block relationship 3
Control block phasing 72
Control Processor
station resources 8
CP
resources 8

D
Database security, (CFGOPT) 10
Deviation alarming 93
Display
Station Block Detail Display 8
Distributed 41
Distributed Control Interface blocks 41
Dynamic loading calculations
BP load 8
LODPER 9

260
Index B0193AW – Rev R

LODPHS 9
LODSYN 9
station load 9

E
Equipment Control Block (ECB) phasing 72
Error handling 40

F
Fail Safe (FAILSF) 117
Failsafe
events leading to 164
support 42
FBM types 169
Fieldbus application interface 159
Equipment Control Blocks (ECBs) 159
Fieldbus Modules (FBMs) 159
FoxCom 218, 219

G
Gas Chromatograph (GC) ECB 191

H
Hydrostatic Tank Gauge ECB
default displays 189

I
INITC 52
Initialization coil 116
INITU 52
Input signal conditioning 75
Input/Output (I/O) blocks 73
Integrated control configurator 151
configuration target 154
editing modes 156
software processing 153
Intelligent Transmitter (IT) ECB 191

L
Ladder diagram
constraints 120
construction 103
contact inputs 107
description 101
display 103

261
B0193AW – Rev R Index

execution 103
fanned outputs 117
functions 99
PLB functions 100
Zoned Control Logic 118
Ladder logic
configurator overview 128
scan cycle 124
status byte 126
technical identifiers 106
timer/counter structures 109

M
Mass Flow Transmitter (MFT) ECB 191
Mismatch alarming 95
Module
Cable Balun 218
Monitor block 137

O
Object Manager
OM 52
Out of range alarming 95
Output alarming 91
Output signal conditioning 77

P
Peer-to-peer communications 9
PID hold constraint 43
PLB functions 100
Power Fail (POWERF) 117
Pretarget alarming 92
PRIBLK
cascade standard configuration 37
initial startup 34
security 36
set point behavior 36
transfer of control 35
Process alarming 79
Process connections 55
shared variables 55
Program flow control
Master Control Relay (MCR) 114
Zone Control Logic (ZCL) 114
Programmable logic block (PLB)
diagram 122
Programmable Logic Controller blocks 41

262
Index B0193AW – Rev R

R
Rate of change alarming 96
Redundant I/O blocks 74
Redundant Input block (CAINR) 74
Redundant output block (AOUTR) 75

S
Scanning 68
scan overrun 68, 70
Secure/release mechanism 42
Security, database 10
Sequence block types 133
Sequence logic 133
Sequence operational error alarming 97
Sequence processing 144
Sequence states
about 141
active 142
active/inactive transitions 142
inactive 142
paused 142
tripped 142
Sequential control blocks 133
block states 138
Shadow parameters 9, 10
State change alarming 97
Station
resources 8
Station block
free memory variable 9
overrun variables 9
peer-to-peer connection 9
Station Block Detail Display 8
Station compound/block 8
Supervisory Enable
SE 52

T
Timer block 137
Timer/counter structures 109
Transition states
about 143
to_inactive 143
to_manual 143
to_paused 143
Trip alarming 98

263
B0193AW – Rev R Index

W
Window ECBs 183

33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
www.foxboro.com
Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your local Foxboro representative.
Facsimile: 1-508-549-4999
Printed in U.S.A. 0303