Experion PKS

Series C Fieldbus Interface Module User's Guide

EPDOC-X125-en-432B
March 2018

Release 432
 Document Release Issue Date
EPDOC-X125-en-432B 432 0 March 2018

Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be used solely
for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or
disclosed to a third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied
warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated
in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information
and specifications in this document are subject to change without notice.
Copyright 2018 - Honeywell International Sàrl

2 www.honeywell.com
Contents

1 About this guide ................................................................................................................................... 11

2 Series C FIM4/FIM8 Purpose ............................................................................................................... 13
2.1 Series C FIM4 versus FIM2 ............................................................................................................................. 14
2.2 Series C FIM4/FIM8 functional overview ....................................................................................................... 15
3 Getting Started ..................................................................................................................................... 17
3.1 What Task Do You Want to Complete .............................................................................................................. 18
4 Series C FIM4/FIM8 planning and design ........................................................................................... 19
4.1 General planning references ............................................................................................................................. 20
4.1.1 Planning for system security .............................................................................................................. 20
4.2 Fieldbus network wiring and installation references ........................................................................................ 21
4.3 Identifying Series C FIM4/FIM8 components ................................................................................................. 22
4.4 Identifying Series C Mark II FIM4 components .............................................................................................. 24
4.5 Differences between FIM4 and FIM8 .............................................................................................................. 26
4.6 Selecting and calculating Fieldbus wiring requirements .................................................................................. 27
4.7 Reviewing intrinsically safe application considerations ................................................................................... 28
4.8 Reviewing Series C FIM4/FIM8 performance data ......................................................................................... 29
4.8.1 Subscription and Publication Rates ................................................................................................... 30
5 Series C FIM4/FIM8 installation and upgrades .................................................................................. 31
5.1 Installation declarations .................................................................................................................................... 32
5.2 Installing Input/Output termination assembly CC- or CU-TFB401, CC- or CU-TFB411, CC- or CU-
TFB402, or CC- or CU-TFB412, or CC- or CU-TFB811 ................................................................................. 33
5.3 Installing Input/Output termination assembly DC-TFB402 or DC-TFB412 ................................................... 45
5.4 Setting unique device index for Series C FIM4 ................................................................................................ 52
5.5 Installing Series C FIM4 CC- or CU-PFB401 .................................................................................................. 53
5.6 Installing redundant power conditioner IOTA F660A or F860 ........................................................................ 54
5.7 Upgrading Series C FIM4/FIM8 firmware ....................................................................................................... 56
5.8 Converting non-redundant Series C FIM4 to redundant Series C FIM4/FIM8 ................................................ 57
5.9 Converting redundant Series C FIM4/FIM8 to non-redundant Series C FIM4/FIM8 ..................................... 59
6 Series C FIM4/FIM8 configuration ....................................................................................................... 61
6.1 Non-Experion interface precautions ................................................................................................................. 62
6.2 Free VCR recommendation .............................................................................................................................. 63
6.3 Adding FIM4/FIM8 block to project ................................................................................................................ 64
6.4 Checking FFLink configuration ....................................................................................................................... 66
6.5 FFLink configuration parameters reference ..................................................................................................... 68
6.6 Creating a Fieldbus device type from vendor DD ............................................................................................ 73
6.7 Editing device block parameters ....................................................................................................................... 77
6.8 Adding a fieldbus device to project .................................................................................................................. 78
6.9 Assigning a device to a FFLink in Project ........................................................................................................ 79
6.10 Checking device configuration ....................................................................................................................... 80
6.11 Making fieldbus block template and assigning function block to device ....................................................... 82
6.12 Configuring advanced alarming ..................................................................................................................... 83
6.12.1 Opening the configuration dialog box ............................................................................................. 83
6.12.2 Configuring/creating a condition ..................................................................................................... 84
6.12.3 Managing the conditions .................................................................................................................. 86

3
CONTENTS

6.12.4 Enabling or disabling a condition .................................................................................................... 86

6.12.5 Assigning criticalities and priorities ................................................................................................ 88
6.12.6 Editing an existing condition ........................................................................................................... 88
6.13 Block Offnet diagnostic alarm ........................................................................................................................ 90
6.13.1 Behavior of the Block Offnet and Device Offnet System alarms in various communication
loss scenarios ......................................................................................................................................... 90
6.13.2 Behavior of the Block Offnet and Device Offnet System alarms in various operational scenarios 90
7 Series C FIM4/FIM8 configuration form reference ............................................................................ 93
7.1 FIM4/FIM8 device Diagnostics tab parameters ............................................................................................... 94
7.2 FIM4/FIM8 Main tab parameters ..................................................................................................................... 95
7.3 FIM4/FIM8 Redundancy tab parameters .......................................................................................................... 97
7.4 FIM4/FIM8 System Time tab parameters ........................................................................................................ 98
7.5 FIM4/FIM8 Statistics tab parameters ............................................................................................................... 99
7.6 FIM4/FIM8 Peer Connections tab parameters ............................................................................................... 100
7.7 FIM4/FIM8 Hardware Information tab parameters ........................................................................................ 101
7.8 FIM4/FIM8 FTE tab parameters .................................................................................................................... 102
7.9 FIM4/FIM8 UDP/TCP tab parameters ........................................................................................................... 104
7.10 FIM4/FIM8 IP/ICMP tab parameters ........................................................................................................... 106
7.11 FIM4/FIM8 QVCS tab parameters ............................................................................................................... 108
7.12 FIM4/FIM8 Server History tab parameters .................................................................................................. 109
7.13 FIM4/FIM8 Server Displays tab parameters ................................................................................................ 110
7.14 FIM4/FIM8 Control Confirmation tab parameters ....................................................................................... 112
7.15 FIM4/FIM8 Identification tab parameters .................................................................................................... 113
8 Block instantiation support ............................................................................................................... 115
8.1 Control Builder supports block instantiation .................................................................................................. 116
8.2 Instantiable block implementation considerations .......................................................................................... 117
8.2.1 Adding instantiable block to device in Project tab .......................................................................... 117
8.2.2 Checking instantiated block configuration in Project tab ................................................................ 118
8.2.3 Making optional instantiated block resource usage check ............................................................... 119
8.2.4 Adding instantiated block to CM ..................................................................................................... 120
8.2.5 Loading Project device to physical device ...................................................................................... 121
8.2.6 Deleting (de-instantiate) instantiated block from Project tab .......................................................... 121
8.2.7 Deleting (de-instantiate) instantiated block from physical device .................................................. 122
8.2.8 Replacing failed device that includes instantiable blocks with like device ..................................... 122
9 Loading FIM4/FIM8 components online ........................................................................................... 125
9.1 About load operations ..................................................................................................................................... 126
9.2 About load dialog ........................................................................................................................................... 127
9.3 Load order guidelines ..................................................................................................................................... 128
9.4 General load considerations ............................................................................................................................ 130
9.5 About fieldbus device states ........................................................................................................................... 131
9.6 Fieldbus device matching rules ...................................................................................................................... 132
9.7 Identifying load interactions for fieldbus-related operations .......................................................................... 133
9.8 Loading a Series C FIM4/FIM8 and its links ................................................................................................. 134
9.9 Matching uncommissioned device to Project device or vice versa ................................................................ 135
9.10 Using optional safe handling of new devices ............................................................................................... 137
9.10.1 About safe handling option ............................................................................................................ 137
9.10.2 Enabling and disabling safe handling ............................................................................................ 137
9.10.3 Safe handling and previously commissioned devices ................................................................... 137
9.10.4 Removing power during a safe handling operation ....................................................................... 137
9.11 Loading FFLink contents or fieldbus device ................................................................................................ 138
10 Fieldbus device commissioning ..................................................................................................... 139
10.1 Getting started ............................................................................................................................................... 140

4 www.honeywell.com
 CONTENTS

10.1.1 Read this first ................................................................................................................................. 140

10.1.2 Initial checks and operations ......................................................................................................... 141
10.2 Connecting devices ....................................................................................................................................... 143
10.3 Checking device ............................................................................................................................................ 145
10.4 Checking control strategy ............................................................................................................................. 146
10.5 Flowchart summary ...................................................................................................................................... 147
11 Series C FIM4/FIM8 redundancy functionality ............................................................................... 149
11.1 Redundant Series C FIM4/FIM8 overview .................................................................................................. 150
11.2 Switchover and secondary readiness ............................................................................................................ 151
11.3 Switchover behavior considerations ............................................................................................................. 152
11.4 Failure conditions and switchover ................................................................................................................ 153
11.5 Fieldbus network switchover considerations ................................................................................................ 154
11.6 Switchover versus fieldbus network activities .............................................................................................. 155
11.7 Switchover events ......................................................................................................................................... 156
12 Series C FIM4/FIM8 operation ......................................................................................................... 157
12.1 Series C FIM4/FIM8 startup ......................................................................................................................... 159
12.2 Initiating Series C FIM4/FIM8 shutdown .................................................................................................... 160
12.3 Series C FIM4/FIM8 IOTA display and LED descriptions .......................................................................... 161
12.4 Control Builder Block icon descriptions ...................................................................................................... 164
12.4.1 FIM4/FIM8 block icons ................................................................................................................. 164
12.4.2 FIM4/FIM8 link icons ................................................................................................................... 165
12.4.3 Fieldbus Device icons .................................................................................................................... 165
12.4.4 Fieldbus block icons ...................................................................................................................... 166
12.5 Activating or inactivating FIM4/FIM8 link .................................................................................................. 167
12.6 Initiating Series C FIM4/FIM8 link segment commands ............................................................................. 168
12.6.1 Initiating a PurgeNVS SEG command .......................................................................................... 168
12.6.2 Initiating a CompactNVS SEG Command .................................................................................... 169
12.6.3 Automated NVS compaction ......................................................................................................... 169
12.7 Activating or inactivating fieldbus block ..................................................................................................... 170
12.8 Checking/changing fieldbus device functional class .................................................................................... 171
12.9 Checking live list and commissioning an uncommissioned device .............................................................. 173
12.10 Viewing and optimizing link schedule configuration ................................................................................. 174
12.10.1 Calling up Link Schedule ............................................................................................................ 174
12.10.2 Additional Link Schedule terms reference .................................................................................. 176
12.10.3 Configuring link schedule optimization ...................................................................................... 177
12.11 Initiating synchronization command .......................................................................................................... 178
12.12 Initiating switchover command .................................................................................................................. 179
12.13 Using fieldbus methods manager ................................................................................................................ 180
12.14 Using controller menu functions ................................................................................................................ 184
12.15 Using station detail displays ....................................................................................................................... 185
12.16 Foundation fieldbus detail displays/faceplates ........................................................................................... 186
12.16.1 Naming conventions for Detail Displays ..................................................................................... 186
12.16.2 Detail Displays contents based on FF control points loading ...................................................... 186
12.16.3 Tabs of FF Detail Displays .......................................................................................................... 186
12.16.4 Detail Displays tabs of the different Foundation Fieldbus blocks ............................................... 187
12.16.5 Common functionalities of faceplates ......................................................................................... 189
12.16.6 FF Detail Displays example templates for Control Builder ........................................................ 190
12.17 Using Station event summary display ........................................................................................................ 191
13 Experion PKS Host Registration with Foundation Fieldbus ........................................................ 193
13.1 New features ................................................................................................................................................. 194
13.2 Conditional support for FF devices .............................................................................................................. 196
13.3 About EDDL ................................................................................................................................................. 197
13.4 About DD View tab ...................................................................................................................................... 198

5
CONTENTS

13.5 Multi-capability support for FF devices ....................................................................................................... 202

13.6 About Field Diagnostic support .................................................................................................................... 203
13.7 Parameter definitions .................................................................................................................................... 207
13.8 Persistent data handling ................................................................................................................................ 208
14 Series C FIM4/FIM8 maintenance .................................................................................................... 209
14.1 Periodic checks ............................................................................................................................................. 211
14.2 Recommended spare parts ............................................................................................................................ 212
14.3 Series C FIM4/FIM8 removal and installation under power ........................................................................ 213
14.4 Replacing device template with a different one ........................................................................................... 214
14.5 Correcting some common UTR errors ......................................................................................................... 220
14.6 Replacing failed Series C FIM4 CC- or CU-PFB401 .................................................................................. 221
14.7 Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401, CC-or CU-TFB411, CC- or CU-
TFB402, or CC- or CU-TFB412 ..................................................................................................................... 222
14.8 Relocating Series C FIM4/FIM8 or reassigning IP address ......................................................................... 224
14.9 Upgrading firmware in uncommissioned device .......................................................................................... 225
14.10 Replacing a failed device with a like device having the same model name and device revision ............... 226
14.11 Replacing a failed device with a different device using a different block type .......................................... 227
14.12 Unlike device replacement report ............................................................................................................... 229
14.13 Changing or clearing tag and/or address of uncommissioned device ......................................................... 231
14.14 Preparing Fieldbus device for a move or software migration ..................................................................... 232
14.14.1 Migrating Fieldbus device type to a release supporting Enable Block Offnet Diagnostic
Alarm ................................................................................................................................................... 232
14.15 Using fieldbus device simulate function ..................................................................................................... 234
14.16 Checking fieldbus device calibration .......................................................................................................... 236
15 Series C FIM4/FIM8 troubleshooting .............................................................................................. 239
15.1 Isolating problems ........................................................................................................................................ 240
15.2 Fault classifications ...................................................................................................................................... 241
15.3 Initial checks ................................................................................................................................................. 242
15.3.1 Checking Control Builder error code reference ............................................................................. 242
15.3.2 Checking front panel display and LEDs ........................................................................................ 242
15.3.3 Viewing flash log ........................................................................................................................... 242
15.3.4 Viewing release information log .................................................................................................... 242
15.3.5 Viewing trace log ........................................................................................................................... 243
15.3.6 Checking version and revision log ................................................................................................ 243
15.3.7 Checking server point build log ..................................................................................................... 243
15.3.8 Checking server point build error log ............................................................................................ 243
15.3.9 Checking error log ......................................................................................................................... 243
15.3.10 Viewing link schedule log ........................................................................................................... 243
15.3.11 Checking Fieldbus library manager log ....................................................................................... 244
15.3.12 Using CTool to capture diagnostic data ....................................................................................... 244
15.4 Series C FIM4/FIM8 self-test diagnostic codes ........................................................................................... 245
15.5 FIM link communication error ..................................................................................................................... 251
15.6 Fixing common problems ............................................................................................................................. 252
15.6.1 Loss of power ................................................................................................................................ 252
15.6.2 Poweron Self-Test Fault ................................................................................................................. 252
15.6.3 Fatal ECC error .............................................................................................................................. 253
15.6.4 Background Diagnostic failure ...................................................................................................... 253
15.6.5 No IP address ................................................................................................................................. 253
15.6.6 No time reference .......................................................................................................................... 254
15.6.7 Isolated (lonely) Node ................................................................................................................... 254
15.6.8 Device Index setting does not match displayed value ................................................................... 255
15.6.9 Duplicate Device Index setting ...................................................................................................... 255
15.6.10 Device Index value is zero upon power up .................................................................................. 256

6 www.honeywell.com
 CONTENTS

15.6.11 Device reload or replacement fails .............................................................................................. 256

15.6.12 Generation of excessive alarms ................................................................................................... 256
15.6.13 Alarms not occurring when expected .......................................................................................... 257
15.6.14 Connected Fieldbus device is not detected by the FF link .......................................................... 257
15.7 Getting further assistance ............................................................................................................................. 258
15.7.1 Other troubleshooting sources ....................................................................................................... 258
15.7.2 Guidelines for requesting support .................................................................................................. 259
16 Fieldbus integration with Experion control reference .................................................................. 261
16.1 Series C FIM4/FIM8 handles data integration ............................................................................................. 263
16.2 About link object .......................................................................................................................................... 264
16.3 Network management description ................................................................................................................ 265
16.4 System management description .................................................................................................................. 266
16.5 About device objects ..................................................................................................................................... 267
16.6 About VFD objects ....................................................................................................................................... 268
16.7 Type creation makes integration possible ..................................................................................................... 269
16.8 Fieldbus device analog input integration ...................................................................................................... 270
16.9 Fieldbus analog input data manipulation ...................................................................................................... 271
16.10 Fieldbus device analog output or PID integration ...................................................................................... 272
16.11 Fieldbus analog output or PID data manipulation ...................................................................................... 274
16.12 Fieldbus device discrete input integration .................................................................................................. 275
16.13 Fieldbus discrete input data manipulation .................................................................................................. 276
16.14 Fieldbus device discrete output data integration ........................................................................................ 277
16.15 Fieldbus discrete output data manipulation ................................................................................................ 278
16.16 Interface connections summary .................................................................................................................. 279
16.17 About SCM parameter interaction .............................................................................................................. 280
16.18 Fieldbus status data details ......................................................................................................................... 281
16.19 Fieldbus status indications .......................................................................................................................... 282
16.19.1 Sub status Definitions for Quality Status ..................................................................................... 286
17 Control mode interaction reference ............................................................................................... 289
17.1 Fieldbus block modes versus control modes ................................................................................................ 290
17.2 Control mode priorities and indications ....................................................................................................... 292
17.3 Rotary Switch Model versus Toggle Switch Model ..................................................................................... 293
17.4 Display indications and mode calculation .................................................................................................... 294
17.5 Mode change conditions ............................................................................................................................... 295
17.6 Access control through GRANT_DENY parameter .................................................................................... 297
18 Fieldbus Link Active scheduler and Link Master functions ......................................................... 299
18.1 Link Schedule ............................................................................................................................................... 301
18.2 Function block execution schedule ............................................................................................................... 302
18.3 About using mixed macrocycles on FF Links .............................................................................................. 304
18.3.1 About macrocycles ........................................................................................................................ 304
18.3.2 About mixed macrocycles ............................................................................................................. 304
18.3.3 Scenarios during which mode shed occurs when using mixed macrocycles ................................. 304
19 Tags, Addresses, and Live List Reference .................................................................................... 307
19.1 Tag and address assignments ........................................................................................................................ 308
19.2 About Fieldbus address assignments in Control Builder .............................................................................. 309
19.3 Live list and uncommissioned devices ......................................................................................................... 310
20 Notification Scheme Reference ....................................................................................................... 311
20.1 Fieldbus versus Experion Alarm Priorities ................................................................................................... 312
20.1.1 Advanced Alarming ....................................................................................................................... 312
20.2 Fieldbus Alarm Conditions ........................................................................................................................... 314
20.2.1 Loading alarm conditions .............................................................................................................. 316
20.2.2 Alarm server operation .................................................................................................................. 316

7
CONTENTS

21 Fieldbus Technology Overview ....................................................................................................... 317

21.1 Open communications architecture .............................................................................................................. 318
21.2 Communication layer description ................................................................................................................. 319
21.3 Standard Function Blocks ............................................................................................................................. 321
21.3.1 Blocks for basic control functionality ............................................................................................ 321
21.3.2 About modes of operation ............................................................................................................. 322
21.3.3 Analog Input block ........................................................................................................................ 323
21.3.4 Analog Output block ...................................................................................................................... 325
21.3.5 Bias/Gain block ............................................................................................................................. 326
21.3.6 Control Selector block ................................................................................................................... 328
21.3.7 Discrete Input block ....................................................................................................................... 330
21.3.8 Discrete Output block .................................................................................................................... 331
21.3.9 Manual Loader block ..................................................................................................................... 333
21.3.10 Proportional/Derivative block ..................................................................................................... 335
21.3.11 Proportional/Integral/Derivative block ........................................................................................ 338
21.3.12 Ratio block ................................................................................................................................... 341
21.4 Device Descriptions and Block Parameters .................................................................................................. 344
21.4.1 About Device Descriptions ............................................................................................................ 344
21.4.2 Device Description Language ........................................................................................................ 344
21.4.3 Device Description infrastructure .................................................................................................. 344
22 Standard Function Block Parameters Reference .......................................................................... 347
22.1 ACK_OPTION ............................................................................................................................................. 351
22.2 ALARM_HYS .............................................................................................................................................. 352
22.3 ALARM_SUM ............................................................................................................................................. 353
22.4 ALERT_KEY ............................................................................................................................................... 354
22.5 BAL_TIME ................................................................................................................................................... 355
22.6 BIAS ............................................................................................................................................................. 356
22.7 BKCAL_HYS ............................................................................................................................................... 357
22.8 BKCAL_IN ................................................................................................................................................... 358
22.9 BKCAL_OUT ............................................................................................................................................... 359
22.10 BKCAL_OUT_D ........................................................................................................................................ 360
22.11 BKCAL_SEL_1 .......................................................................................................................................... 361
22.12 BKCAL_SEL_2 .......................................................................................................................................... 362
22.13 BKCAL_SEL_3 .......................................................................................................................................... 363
22.14 BLOCK_ALM ............................................................................................................................................ 364
22.15 BLOCK_ERR ............................................................................................................................................. 365
22.16 BLOCK_ERR.DISABLED ........................................................................................................................ 366
22.17 BYPASS ...................................................................................................................................................... 367
22.18 CAS_IN ...................................................................................................................................................... 368
22.19 CAS_IN_D ................................................................................................................................................. 369
22.20 CHANNEL ................................................................................................................................................. 370
22.21 CLR_FSTATE ............................................................................................................................................. 371
22.22 CONFIRM_TIME ...................................................................................................................................... 372
22.23 CONTROL_OPTS ...................................................................................................................................... 373
22.24 CYCLE_SEL .............................................................................................................................................. 374
22.25 CYCLE_TYPE ........................................................................................................................................... 375
22.26 DEV_REV .................................................................................................................................................. 376
22.27 DEV_TYPE ................................................................................................................................................ 377
22.28 DD_RESOURCE ........................................................................................................................................ 378
22.29 DD_REV ..................................................................................................................................................... 379
22.30 DISC_ALM ................................................................................................................................................ 380
22.31 DISC_LIM .................................................................................................................................................. 381
22.32 DISC_PRI ................................................................................................................................................... 382
22.33 DV_HI_ALM ............................................................................................................................................. 383

8 www.honeywell.com
 CONTENTS

22.34 DV_HI_LIM ............................................................................................................................................... 384

22.35 DV_HI_PRI ................................................................................................................................................ 385
22.36 DV_LO_ALM ............................................................................................................................................ 386
22.37 DV_LO_LIM .............................................................................................................................................. 387
22.38 DV_LO_PRI ............................................................................................................................................... 388
22.39 FAULT_STATE .......................................................................................................................................... 389
22.40 FEATURES ................................................................................................................................................ 390
22.41 FEATURE_SEL .......................................................................................................................................... 391
22.42 FF_GAIN .................................................................................................................................................... 392
22.43 FF_SCALE ................................................................................................................................................. 393
22.44 FF_VAL ...................................................................................................................................................... 394
22.45 FIELD_VAL ............................................................................................................................................... 395
22.46 FIELD_VAL_D .......................................................................................................................................... 396
22.47 FREE_SPACE ............................................................................................................................................ 397
22.48 FREE_TIME ............................................................................................................................................... 398
22.49 FSTATE_TIME ........................................................................................................................................... 399
22.50 FSTATE_VAL ............................................................................................................................................. 400
22.51 FSTATE_VAL_D ........................................................................................................................................ 401
22.52 GAIN .......................................................................................................................................................... 402
22.53 GRANT_DENY ......................................................................................................................................... 403
22.54 HARD_TYPES ........................................................................................................................................... 404
22.55 HI_ALM ..................................................................................................................................................... 405
22.56 HI_HI_ALM ............................................................................................................................................... 406
22.57 HI_HI_LIM ................................................................................................................................................. 407
22.58 HI_HI_PRI .................................................................................................................................................. 408
22.59 HI_LIM ....................................................................................................................................................... 409
22.60 HI_PRI ........................................................................................................................................................ 410
22.61 IO_OPTS .................................................................................................................................................... 411
22.62 IN ................................................................................................................................................................ 412
22.63 IN_1 ............................................................................................................................................................ 413
22.64 LIM_Notify ................................................................................................................................................. 414
22.65 L_TYPE ...................................................................................................................................................... 415
22.66 LO_ALM .................................................................................................................................................... 416
22.67 LO_LIM ...................................................................................................................................................... 417
22.68 LO_LO_ALM ............................................................................................................................................. 418
22.69 LO_LO_LIM .............................................................................................................................................. 419
22.70 LO_LO_PRI ............................................................................................................................................... 420
22.71 LO_PRI ....................................................................................................................................................... 421
22.72 LOW_CUT ................................................................................................................................................. 422
22.73 MANUFAC_ID .......................................................................................................................................... 423
22.74 MAX_NOTIFY .......................................................................................................................................... 424
22.75 MEMORY_SIZE ........................................................................................................................................ 425
22.76 MIN_CYCLE_T ......................................................................................................................................... 426
22.77 MODE_BLK ............................................................................................................................................... 427
22.78 NV_CYCLE_T ........................................................................................................................................... 428
22.79 OFFNETALM_ENABLED ........................................................................................................................ 429
22.80 OUT ............................................................................................................................................................ 430
22.81 OUT_D ....................................................................................................................................................... 431
22.82 OUT_HI_LIM ............................................................................................................................................. 432
22.83 OUT_LO_LIM ........................................................................................................................................... 433
22.84 OUT_SCALE ............................................................................................................................................. 434
22.85 OUT_STATE .............................................................................................................................................. 435
22.86 PV ............................................................................................................................................................... 436
22.87 PV_D .......................................................................................................................................................... 437

9
CONTENTS

22.88 PV_FTIME ................................................................................................................................................. 438

22.89 PV_SCALE ................................................................................................................................................ 439
22.90 PV_STATE ................................................................................................................................................. 440
22.91 RA_FTIME ................................................................................................................................................. 441
22.92 RATE .......................................................................................................................................................... 442
22.93 RCAS_IN .................................................................................................................................................... 443
22.94 RCAS_IN_D ............................................................................................................................................... 444
22.95 RCAS_OUT ................................................................................................................................................ 445
22.96 RCAS_OUT_D ........................................................................................................................................... 446
22.97 READBACK .............................................................................................................................................. 447
22.98 READBACK_D ......................................................................................................................................... 448
22.99 RESET ........................................................................................................................................................ 449
22.100 RESTART ................................................................................................................................................. 450
22.101 ROUT_IN ................................................................................................................................................. 451
22.102 ROUT_OUT ............................................................................................................................................. 452
22.103 RS_STATE ................................................................................................................................................ 453
22.104 SEL_1 ....................................................................................................................................................... 454
22.105 SEL_2 ....................................................................................................................................................... 455
22.106 SEL_3 ....................................................................................................................................................... 456
22.107 SEL_TYPE ............................................................................................................................................... 457
22.108 SET_FSTATE ........................................................................................................................................... 458
22.109 SHED_OPT .............................................................................................................................................. 459
22.110 SHED_RCAS ............................................................................................................................................ 460
22.111 SHED_ROUT ........................................................................................................................................... 461
22.112 SIMULATE ............................................................................................................................................... 462
22.113 SIMULATE_D .......................................................................................................................................... 463
22.114 SP .............................................................................................................................................................. 464
22.115 SP_D ......................................................................................................................................................... 465
22.116 SP_HI_LIM .............................................................................................................................................. 466
22.117 SP_LO_LIM ............................................................................................................................................. 467
22.118 SP_RATE_DN .......................................................................................................................................... 468
22.119 SP_RATE-UP ............................................................................................................................................ 469
22.120 ST_REV .................................................................................................................................................... 470
22.121 STATUS_OPTS ........................................................................................................................................ 471
22.122 STRATEGY .............................................................................................................................................. 472
22.123 TAG_DESC .............................................................................................................................................. 473
22.124 TEST_RW ................................................................................................................................................. 474
22.125 TRK_IN_D ............................................................................................................................................... 475
22.126 TRK_SCALE ............................................................................................................................................ 476
22.127 TRK_VAL ................................................................................................................................................. 477
22.128 UPDATE_EVT ......................................................................................................................................... 478
22.129 WRITE_ALM ........................................................................................................................................... 479
22.130 WRITE_LOCK ......................................................................................................................................... 480
22.131 WRITE_PRI ............................................................................................................................................. 481
22.132 XD_SCALE .............................................................................................................................................. 482
22.133 XD_STATE ............................................................................................................................................... 483
23 Glossary of Fieldbus Terms ............................................................................................................ 485
24 Notices .............................................................................................................................................. 489

10 www.honeywell.com
1 About this guide

This document provides information for planning, installing, configuring, operating, maintaining and
troubleshooting hardware components and software function blocks associated with the Series C Fieldbus
Interface Modules (FIM4/FIM8). It also includes some basic FOUNDATION Fieldbus technology data for
reference.

Revision history

Revision Date Description

A July 2016 B
B March 2018 Updated PAR # 1-8BWZCWL information in the document.

Intended audience
Personnel who are responsible for integrating Fieldbus devices with the Experion system.

Prerequisite skills
• Familiar with working in a Windows operating environment.
• Familiar with using these Experion applications
• Configuration Studio
• Control Builder
• Series C Platform Analyzer
• Familiar with FOUNDATION Fieldbus technology.

How to use this guide

Choose a topic associated with the task you want to complete on the tree view in the PDF collection or click one
of the topic references listed in the What Task Do You Want to Complete section. This guide covers tasks for
planning your installation through troubleshooting considerations.
Related documents
For more information about using Control Builder, see Control Building User’s Guide.

11
1 ABOUT THIS GUIDE

12 www.honeywell.com
2 Series C FIM4/FIM8 Purpose

The Series C Fieldbus Interface Module (FIM4/FIM8) serves as the bridge between the Experion control
environment and the Fieldbus control functions. It supports both the publish/subscribe and the client/server
communication methods to communicate with Fieldbus function blocks. The Fieldbus function blocks
implementing control algorithms, such as a PID function block, must be connected downstream from CEE
function blocks. For example, a control strategy may use a CEE PID as an upstream PID and a Fieldbus PID as
a downstream PID.

Attention
• With R400, FIM8 is introduced.
• FIM8 supports up to eight H1 links.
• The FIM8 IOTA is only available in a redundant form factor. Therefore, a single FIM8 module combined with the
redundant FIM8 IOTA can be used for non-redundant operations. A pair of FIM8 modules combined with the
redundant FIM8 IOTA can be used for redundant operations.
• FIM4 and FIM8 have distinct IOTA. A FIM8 module cannot be mounted on a FIM4 IOTA and a FIM4 module
cannot be mounted on a FIM8 IOTA.
• With R431.3, for Series C Mark II, only FIM4 IOTA is available.
• Series C Mark II does not support Intrinsically Safe (IS) application.

Related topics
“Series C FIM4 versus FIM2” on page 14
“Series C FIM4/FIM8 functional overview” on page 15

13
2 SERIES C FIM4/FIM8 PURPOSE

2.1 Series C FIM4 versus FIM2

The Series C Fieldbus Interface Modules (FIM4/FIM8) is designed to complement the C300 Controller and
support Fault Tolerant Ethernet (FTE) communications within Experion R300 (for FIM4)/Experion R400 (for
FIM8). While the Series C FIM is functionally equivalent to the Chassis I/O-Series A (FIM2) FIM, its physical
design, including mounting and wiring requirements, is drastically different as shown in the following figure.
The Series C FIM4/FIM8 support up to four and eight H1 links respectively while the FIM2 only supports upto
two. Please refer to the Series A Fieldbus Interface Module User's Guide for information that is specific to
integrating Fieldbus through a FIM2.

Table 1: Series C FIM4 Mounted on non-redundant Input/Output Termination Assembly (IOTA).

14 www.honeywell.com
 2 SERIES C FIM4/FIM8 PURPOSE

2.2 Series C FIM4/FIM8 functional overview

Like the FIM2, the Series C FIM4/FIM8 features a multi-level function block model based upon the hardware
hierarchy and the physical Fieldbus network. The Experion Control Builder application supports integral
creation and configuration of Fieldbus function blocks with Experion system function blocks to incorporate
Fieldbus devices in a unified Experion Control Strategy. This means Experion function blocks and Fieldbus
function blocks can be easily interconnected, so control can reside on the Fieldbus link, in the Control
Processor/Control Execution Environment (CEE), or cascaded from CEE to the Fieldbus device. The following
figure shows how icons are used to identify Series C FIM, H1 Links, and Fieldbus devices in the Control
Builder Project tab.

Table 2: Typical Series C FIM4 Hardware/Function Block Hierarchy in Project Tab

15
2 SERIES C FIM4/FIM8 PURPOSE

Table 3: Typical Series C FIM8 Hardware/Function Block Hierarchy in Project Tab

The Series C FIM4/FIM8 platform block represents the physical module and IOTA. This block is the parent of
Link blocks, which represents an H1 link by FIM4/FIM8. Link blocks are instantiated automatically with the
creation of FIM4/FIM8. Hence, FIM4 instantiates 4 Link blocks and FIM8 instantiates 8 Link blocks.

16 www.honeywell.com
3 Getting Started

This section provides a quick reference to topics in this book for a given task related to using the Series C
FIM4/FIM8 to integrate Fieldbus devices with the Experion system.

Related topics
“What Task Do You Want to Complete” on page 18

17
3 GETTING STARTED

3.1 What Task Do You Want to Complete

The following table lists some of the tasks covered in this document that are related to implementing a Series C
FIM4 (for Experion R300)/FIM8 (for Experion R400). If you are viewing this document online, just click the
reference to jump to the topic in this document.
If you want to . . . Then, see this topic . . .
Plan and Design a Series C FIM4/FIM8 installation. “Series C FIM4/FIM8 planning and design” on page 19
Install Series C FIM4/FIM8 hardware. “Series C FIM4/FIM8 installation and upgrades” on page 31
Wire Series C FIM4/FIM8 hardware. “Series C FIM4/FIM8 installation and upgrades” on page 31
Add FIM4/FIM8 block with Links to Project. “Adding FIM4/FIM8 block to project” on page 64
Check FFLink configuration. “Checking FFLink configuration” on page 66
Make a Fieldbus device Type from vendor DD. “Creating a fieldbus device type from vendor DD”
Edit device block parameters. “Editing device block parameters” on page 77
Add a Fieldbus device to Project. “Adding a fieldbus device to project” on page 78
Assign a device to an FFLink in Project. “Assigning a device to a FFLink in Project” on page 79
Check a device's configuration. “Checking FFLink configuration” on page 66
Make Fieldbus block template and assign the block to a “Making fieldbus block template and assigning function
device. block to device” on page 82
Use an instantiable block. “Control Builder supports block instantiation” on page 116
Load blocks to FIM4/FIM8 components. “Loading FIM4/FIM8 components online” on page 125
Review a typical scenario for commissioning a Fieldbus “Fieldbus device commissioning” on page 139
device.
Use a redundant Series C FIM4/FIM8 pair. “Series C FIM4/FIM8 redundancy functionality” on
page 149
Power up a Series C FIM4/FIM8. “Series C FIM4/FIM8 startup” on page 159
Change the functional class of a Fieldbus device. “Checking/changing fieldbus device functional class” on
page 171
Check the current link schedule. “Other troubleshooting sources” on page 258
Use Fieldbus Methods Manager to interact with vendor “Using fieldbus methods manager” on page 180
supplied Methods for given device.
Review maintenance related requirements. “Series C FIM4/FIM8 maintenance” on page 209
Investigate the cause of a problem. “Series C FIM4/FIM8 troubleshooting” on page 239
Know more about how Fieldbus is integrated with Experion “Fieldbus integration with Experion control reference” on
control. page 261
Know more about FOUNDATION Fieldbus technology. “Fieldbus Technology Overview” on page 317
Check definitions for Fieldbus standard function block “Standard Function Block Parameters Reference” on
parameters. page 347

18 www.honeywell.com
4 Series C FIM4/FIM8 planning and design

This section includes the following topics on information and tasks associated with planning and designing an
Experion System to include Series C FIM4s/FIM8 and Fieldbus devices.

Related topics
“General planning references” on page 20
“Fieldbus network wiring and installation references” on page 21
“Identifying Series C FIM4/FIM8 components” on page 22
“Identifying Series C Mark II FIM4 components” on page 24
“Differences between FIM4 and FIM8” on page 26
“Selecting and calculating Fieldbus wiring requirements” on page 27
“Reviewing intrinsically safe application considerations” on page 28
“Reviewing Series C FIM4/FIM8 performance data” on page 29

19
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.1 General planning references

Please refer to the following PDF Collection publications for planning and design details for the Experion
system in general and the Fault Tolerant Ethernet supervisory network. For the sake of brevity, this Guide does
not repeat the applicable general guidelines, considerations, cautions, and so on that are covered in these other
Guides.
• Control Hardware Planning Guide
• Server and Client Planning Guide
• Fault Tolerant Ethernet Overview and Implementation Guide

4.1.1 Planning for system security

System security must be achieved at all levels in the Experion system to manage security threats.
For details on security related planning, refer to the Network and Security Planning Guide.
For controller hardware specific security planning, refer to the chapter Securing controller hardware of the
Network and Security Planning Guide.

20 www.honeywell.com
 4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.2 Fieldbus network wiring and installation references

Please refer to the following publications for guidance in designing and implementing the Fieldbus network to
be interfaced to the Experion system through the Series C FIM H1 links.

Publication Number/Title Scope Source

AG-140 / Wiring and Installation 31.25 Overview of what you need to know to Fieldbus Foundation
kbit/s, Voltage Mode, Wire Medium wire, power, and layout network
9005 Mountain Ridge Drive
Application Guide components
Bowie Building - Suite 190
Austin, Texas 78759-5316 USA
http://www.fieldbus.org/
AG-163 / 31.25 kbit/s Intrinsically Safe Complements the previous document, Fieldbus Foundation
Systems Application Guide introduces you to the principles of
9005 Mountain Ridge Drive
intrinsic safety, and outlines how to
apply approved devices in a hazardous Bowie Building - Suite 190
area. Austin, Texas 78759-5316 USA
http://www.fieldbus.org/
AG-180 / Engineering Guide and A general comprehensive reference. Fieldbus Foundation
Intrinsically Safe Systems Combo
9005 Mountain Ridge Drive
Bowie Building - Suite 190
Austin, Texas 78759-5316 USA
http://www.fieldbus.org/

21
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.3 Identifying Series C FIM4/FIM8 components

The following table identifies the Series C FIM4/FIM8 components that will be required to provide a non-
redundant or redundant Fieldbus interface with an Experion R300 (for FIM4)/Experion R400 (for FIM8) or later
system. The CC prefix in a model number means the component's printed wiring boards are coated to provide
additional protection from the environment and the CU prefix means the boards are uncoated. For FIM8 the
IOTA and the module are manufactured only as CC.

Component Description Honeywell Model Number

Series C Fieldbus Module mounts on non-redundant or redundant Input/Output CC-PFB401
Interface Module (FIM4) Termination Assembly. Serves as a ' 'between the Experion
CU-PFB401
system and H1 Fieldbus links.
Series C Fieldbus Module mounts on redundant Input/Output Termination CC-PFB801
Interface Module (FIM8) Assembly. Serves as a ' 'between the Experion system and H1
Fieldbus links.
Non-Redundant Input/ Provides physical connection to Series C FIM, H1 Links, and CC-TFB401
Output Termination FTE cables. Mounts on carrier in Series C cabinet.
CU-TFB401
Assembly (IOTA) (FIM4)
Non-Redundant Input/ Same as row above - This model supersedes model CC/CC- CC-TFB402
Output Termination TFB401.
CU-TFB402
Assembly (IOTA) (FIM4)
Redundant Input/Output Provides physical connection to Primary and Secondary CC-TFB411
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on carrier
CU-TFB411
(IOTA) (FIM4) in Series C cabinet.
Redundant Input/Output Same as row above - This model supersedes model CC/CU- CC-TFB412
Termination Assembly TFB411.
CU-TFB412
(IOTA) (FIM4)
Non-Redundant Input/ Provides physical connection to Series C FIM, H1 Links, and DC-TFB403
Output Termination FTE cables. Mounts on the backplane in Series C Mark II
Assembly (IOTA) (FIM4) cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary DC-TFB413
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on the
(IOTA) (FIM4) backplane in Series C Mark II cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary DC-TFB813
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on the
(IOTA) (FIM8) backplane in Series C Mark II cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary CC-TFB811
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on carrier
(IOTA) (FIM8) in Series C cabinet.
Redundant Power Provides physical connection to Series C FIM IOTA to
Conditioner IOTA provide the necessary field power to bus-powered devices on
(Optional) a given link. The models listed below are available from the
vendor MTL-Relcom. (The Series C FIM4/FIM8 does not
provide power for the H1 network.)
Redundant Fieldbus power IOTA F660A
8-segment redundant Fieldbus power IOTA F860
Non-Redundant Power Same as above but in a non-redundant version. The model
Conditioner IOTA listed below is available from the vendor MTL-Relcom.
(Optional)
Non-Redundant Fieldbus power IOTA F660A-NR

22 www.honeywell.com
 4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

Component Description Honeywell Model Number

Power Conditioner Cable Provides pre-fabricated cable with 16-pin connectors for
power conditioner to Series C FIM IOTA connections. The
cables listed below are available from the vendor MTL-
Relcom.
30 cm (1 ft) FCAB-05
1 m (3 ft) FCAB-06
2 m (6.5 ft) FCAB-07
4 m (13 ft) FCAB-08
Control Firewall (9 ports) Provides efficient distribution of FTE cables to multiple CC-PCF901
Series C FIMs.
CU-PCF901
Control Firewall IOTA Provides physical connection for one uplink and up to eight CC-TCF901
separate FTE distribution cables Mounts on carrier in Series
CU-TCF901
C cabinet.
FTE Cable Provides pre-fabricated STP CAT5 Cable with RJ 45
connectors for FTE connections.
2 m (6.5 ft) 51305482-102 (Y)
(Y) = Yellow coded 513054820202 (G)
(G) = Green coded
5 m (16 ft) 51305482-105 (Y)
513054820205 (G)
10 m (33 ft) 51305482-110 (Y)
513054820210 (G)
20 m (65.5 ft) 51305482-120 (Y)
51305482-220 (G)
Fieldbus Device Usage Total number of FIMs per Server actually in use.
Licenses
(Purchase License model numbers in combinations that
support the total number of FIMs required. Licenses must be
purchased starting with the first FIM used.)
1 TC-FFLX01
5 TC-FFLX05
10 TC-FFLX10
50 TC-FFLX50

23
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.4 Identifying Series C Mark II FIM4 components

The following table identifies the Series C Mark II FIM4 components that will be required to provide a non-
redundant or redundant Fieldbus interface with an Experion R431.3 (for FIM4) or later system. The xC prefix in
a model number means the component's printed wiring boards are coated to provide additional protection from
the environment and the CU prefix means the boards are uncoated.

Component Description Honeywell Model Number

Series C Fieldbus Module mounts on non-redundant or redundant Input/Output CC-PFB401
Interface Module (FIM4) Termination Assembly. Serves as a 'gateway' between the
Experion system and H1 Fieldbus links.
Series C Fieldbus Module mounts on non-redundant or redundant Input/Output CC-PFB801
Interface Module (FIM8) Termination Assembly. Serves as a 'gateway' between the
Experion system and H1 Fieldbus links.
Non-Redundant Input/ Provides physical connection to Series C FIM, H1 Links, and DC-TFB402
Output Termination FTE cables. Mounts on the backplane in Series C Mark II
Assembly (IOTA) (FIM4) cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary DC-TFB412
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on the
(IOTA) (FIM4) backplane in Series C Mark II cabinet.
Non-Redundant Input/ Provides physical connection to Series C FIM, H1 Links, and DC-TFB403
Output Termination FTE cables. Mounts on the backplane in Series C Mark II
Assembly (IOTA) (FIM4) cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary DC-TFB413
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on the
(IOTA) (FIM4) backplane in Series C Mark II cabinet.
Redundant Input/Output Provides physical connection to Primary and Secondary DC-TFB813
Termination Assembly Series C FIMs, H1 Links, and FTE cables. Mounts on the
(IOTA) (FIM8) backplane in Series C Mark II cabinet.
Control Firewall (9 ports) Provides efficient distribution of FTE cables to multiple CC-PCF901
Series C FIMs.
Control Firewall IOTA Provides physical connection for one uplink and up to eight DC-TCF901
separate FTE distribution cables Mounts on carrier in Series
C Mark II cabinet.
FTE Cable Provides pre-fabricated STP CAT5 Cable with RJ 45
connectors for FTE connections.
2 m (6.5 ft) 51305482-102 (Y)
(Y) = Yellow coded 513054820202 (G)
(G) = Green coded
5 m (16 ft) 51305482-105 (Y)
513054820205 (G)
10 m (33 ft) 51305482-110 (Y)
513054820210 (G)
20 m (65.5 ft) 51305482-120 (Y)
51305482-220 (G)
Fieldbus Device Usage Total number of FIMs per Server actually in use.
Licenses
(Purchase License model numbers in combinations that
support the total number of FIMs required. Licenses must be
purchased starting with the first FIM used.)

24 www.honeywell.com
 4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

Component Description Honeywell Model Number

1 TC-FFLX01
5 TC-FFLX05
10 TC-FFLX10
50 TC-FFLX50

25
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.5 Differences between FIM4 and FIM8

The following table lists the differences between FIM4 and FIM8:

FIM4 FIM8
The Series C FIM4 provides four interfaces to Fieldbus The Series C FIM8 provides eight interfaces to Fieldbus
networks and Fieldbus devices located on each network. networks and Fieldbus devices located on each network.
The FIM4 IOTA is available in both non-redundant and The FIM8 IOTA is available only in a redundant form factor.
redundant form factors.
The FIM4 has one connector for a Fieldbus Power The FIM8 has two Fieldbus Power Conditioners, one for links
Conditioner for all four links. 1-4 and one for links 5-8.
The FIM4 has four H1 Link Status LEDs. The FIM8 has eight H1 Link Status LEDs.

26 www.honeywell.com
 4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.6 Selecting and calculating Fieldbus wiring requirements

The preferred cable for connecting Fieldbus devices is #18 AWG (0.8mm2) shielded, twisted pair wire. It is
important to calculate how the planned topology for your Fieldbus segment, selected wiring, supplied power
and intended mix of Fieldbus devices may affect the overall performance of a Fieldbus network. It is beyond the
scope of this document to address all possible Fieldbus wiring scenarios.
You may also want to visit the Relcom Inc. website http://www.relcominc.com/ for more information on
available Fieldbus wiring products and more wiring design and installation data. They also offer a free Fieldbus
Wiring Guide for downloading.

27
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.7 Reviewing intrinsically safe application considerations

The Series C FIM4/FIM8 accepts up to three Intrinsically Safe (IS) mounted field devices on each H1 network
it supports.
Ensure you take the reduced current limit of 83 mA into consideration when calculating performance
characteristics for the planned IS Fieldbus segment.
You are responsible for adhering to all applicable national codes and local ordinances for applying intrinsically
safe equipment in a potentially explosive atmosphere.

28 www.honeywell.com
 4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

4.8 Reviewing Series C FIM4/FIM8 performance data

The following table lists the Series C FIM4/FIM8 performance-related data for quick reference.

Number of Series C FIMs per C300 Controller • FIM4: 15 non-redundant or redundant (60 Links) (Regardless
of redundancy).
• FIM8: 8 non-redundant or redundant (64 Links) (Regardless of
redundancy).
Number of Series C FIMs per Experion server 125 non-redundant or redundant pairs(In any combination of
FIM2, FIM4, and FIM8).
Number of H1 Links per Series C FIM • FIM4: Up to 4
– (Each network defined as a FOUNDATION Fieldbus 31.25
kbps H1 network.)
• FIM8: Up to 8
– (Each network defined as a FOUNDATION Fieldbus 31.25
kbps H1 network.)
Number of Devices per H1 Link • Up to 16 for non-intrinsically safe applications.
• Up to 3 for intrinsically safe applications.
(See Note 1 below.)
Number of Devices per Experion server • FIM4: 8000 maximum
• FIM8: 12000 maximum
Number of Blocks per Series C FIM • FIM4: 1600 maximum
(See Note 2 below.)
• FIM8: 3200 maximum
Maximum Single-Variable Publications per Second 16
on an H1 network
Available macrocycle periods 250, 500 milliseconds; 1, 2, 4, 8, 16, and 32 seconds.
Number of Unique Block Types per Series C FIM 200 maximum across all devices connected to all links.
Number of VCRs per H1 Link 128 maximum
(See Note 3 below.)
Number of Agents per Link • 100 for FIM4/FIM8
• 50 for FIM2
Number of FB start entries per Link • 100 for FIM4/FIM8
• 50 for FIM2
Number of Blocks per Device Up to 35
Number of Peer connections per Series C FIM Up to 5
Link Active Scheduler Capabilities Series C FIM supports two LAS domains.
2000 bytes maximum LAS schedule size.
LAS schedule can contain up to four sub-schedules. Each sub-
schedule can consist of up to 64 sequences.
(See Note 4 below.)

29
4 SERIES C FIM4/FIM8 PLANNING AND DESIGN

Notes:
1. The maximum number of supportable devices per network is highly dependent on application, bandwidth, devices,
available current, bus length, and topology. An understanding of Fieldbus is crucial to system sizing.
2. Blocks are counted whether the Fieldbus device's blocks are being used/loaded or not in the FIM strategy. Resources to
support every device's block set must be reserved when the Fieldbus device is configured on one of the FIM4's/FIM8’s
H1 networks.
3. Each Series C FIM4/FIM8 H1 network uses 2 VCRs, each device uses 2 VCRs, and each published connection to/from
a Controller function block uses 1 VCR. Connections between devices do not use Series C FIM4/FIM8 VCRs.
4. A 2-second macrocycle could, for example, have sub schedule periods of 1 second, 500 milliseconds, and 250
milliseconds.
5. Do not use the Series C FIM4/FIM8 with any control module executing more frequently than the Fieldbus device.

4.8.1 Subscription and Publication Rates

Subscription and publication rates are applicable per link. The FIM4 and FIM8 support a subscription rate up to
200 msec.
Note: You cannot configure the subscription rate directly as it varies based on the selected publication rate.

Publication Rate Subscription Rate

Immediate 200ms
250ms 250ms
500ms 500ms
1 second 1 second

30 www.honeywell.com
5 Series C FIM4/FIM8 installation and upgrades

This section includes the following topics on information and tasks associated with installing Series C FIM4/
FIM8 hardware and upgrading Series C FIM4/FIM8 firmware as well as converting from non-redundant to
redundant configuration or vice versa.

Topic
“Installation declarations” on page 32
“Installing Input/Output termination assembly CC- or CU-TFB401, CC- or CU-TFB411, CC- or CU-TFB402, or CC- or
CU-TFB412, or CC- or CU-TFB811” on page 33
“Installing Series C FIM4 CC- or CU-PFB401” on page 53
“Upgrading Series C FIM4/FIM8 firmware” on page 56
“Converting non-redundant Series C FIM4 to redundant Series C FIM4/FIM8” on page 57
“Converting redundant Series C FIM4/FIM8 to non-redundant Series C FIM4/FIM8” on page 59

Related topics
“Installation declarations” on page 32
“Installing Input/Output termination assembly CC- or CU-TFB401, CC- or CU-TFB411, CC- or CU-TFB402,
or CC- or CU-TFB412, or CC- or CU-TFB811” on page 33
“Installing Input/Output termination assembly DC-TFB402 or DC-TFB412” on page 45
“Setting unique device index for Series C FIM4” on page 52
“Installing Series C FIM4 CC- or CU-PFB401” on page 53
“Installing redundant power conditioner IOTA F660A or F860” on page 54
“Upgrading Series C FIM4/FIM8 firmware” on page 56
“Converting non-redundant Series C FIM4 to redundant Series C FIM4/FIM8” on page 57
“Converting redundant Series C FIM4/FIM8 to non-redundant Series C FIM4/FIM8” on page 59

31
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.1 Installation declarations

Attention
This equipment shall be installed in accordance with the requirements of the National Electrical Code (NEC), ANSI/
NFPA 70, or the Canadian Electrical Code (CEC), C22.1. It is intended to be mounted within an enclosure or suitable
environment acceptable to the local authority having jurisdiction, as defined in the NEC, or authorized person as
defined in the CEC.

Electrostatic discharge can damage integrated circuits or semiconductors if you touch connector pins or tracks on
a printed wiring board. Follow these guidelines when you handle any electronic component:
• Touch a grounded object to discharge static potential,
• Wear an approved wrist-strap grounding device,
• Do not touch the wire connector or connector pins,
• Do not touch circuit components inside a component,
• If available, use a static safe workstation,
• When not in use, keep the component in its static shield box or bag.

WARNING
Unless the location is known to be non-hazardous, do not perform the following:
• Connect or disconnect cables,
• Install or remove fuses, terminal blocks, and so on,
• While the component is powered.

Attention
The procedures for installing/upgrading FIM8 module and IOTA is similar to FIM4.

32 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.2 Installing Input/Output termination assembly CC- or CU-TFB401, CC-

or CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412, or CC- or CU-
TFB811
Following are the considerations for installing Input/Output termination assembly CC- or CU-TFB401, CC- or
CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412, or CC- or CU-TFB811.
• You can use a redundant IOTA to support a non-redundant Series C FIM application. You must ensure to
install the non-redundant Series C FIM in the upper module slot on the IOTA.
• You are responsible for supplying power, power conditioning and wiring for each Fieldbus H1 link.
• Ensure that the enclosure is connected to a protective earth ground using #8 AWG solid copper wire. There
should be contact between the grounding bus bar and the enclosure as well as the carrier.
• The Series C FIM supports connectivity of 350 mA for up to 16 non-intrinsically safe mounted devices or 83
mA for up to three intrinsically safe (IS) mounted devices per H1 link.
• You are responsible for observing all local ordinances governing the wiring and installation of electrical
equipment.
• The Series C FIM is designed for removal and insertion under power. Ensure to observe general precautions
when working with powered electrical equipment.
• The orientation of the FTE A and FTE B connectors may be reversed depending on the IOTA version that is
installed. Ensure to always connect the yellow cable to the FTE A connector and the green cable to the FTE
B connector.

Tip
When securing a redundant IOTA to the carrier channel assembly (CCA), install the mounting screws in all
locations on one side of the board first and then install the screws in the locations on the other side.

Prerequisites
• Carrier channel assembly for mounting IOTA is installed in a cabinet.
• Series C power supply is installed.
• Control Firewalls (CF9s) are installed.
• All wiring and pre-fabricated cables are available and labeled as applicable.
• You have the mounting hardware supplied with the components.

CAUTION
Ensure that you do not fully tighten the IOTA mounting screws before installing and tightening the screws in the
24V + and COM terminals to keep these screws from binding during IOTA installation.

To mount an IOTASeries C FIM4 Kit

1 Select the desired mounting location on carrier channel assembly (CCA) and align mounting holes in IOTA
with screw hole locations on the carrier. See the following dimension drawings for details.
• Ensure that the component side of IOTA is facing up. Secure IOTA to CCA using screws, washers, and
spacers provided.
• Insert spacers and washers between bottom of IOTA and top of CCA.
• Tighten mounting screws only half way.

33
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

2 Tighten the screws in terminals 24 Vdc + and COM (logic ground) to the vertical bus bar to connect the
cabinet resident 24 Vdc power supply to the IOTA.
3 Tighten the mounting screws fully.

34 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 1: Mounting Dimensions for Non-Redundant IOTA CC- or CU-TFB401 (shown) or CC- or CU-TFB402

35
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 2: Mounting Dimensions for Redundant IOTA CC- or CU-TFB411 (shown) or CC- or CU-TFB412

To wire a CC/CU-TFB401 or CC/CU-TFB411 IOTA

1 Connect yellow FTE cable from Control Firewall (CF9) to J7 FTE A connector on a non-redundant IOTA.
For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect yellow FTE cable from
CF9 to J9 FTE A on the IOTA.
2 Connect green FTE cable from Control Firewall (CF9) to J8 FTE B connector on a non-redundant IOTA.
For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect green FTE cable from
CF9 to J10 FTE B on the IOTA.

Refer to “Figure 3: Typical Connector Locations on Non-Redundant Model CC/CU-TFB401 IOTA” and
“Figure 4: Typical Connector Locations on Non-Redundant Model CC/CU-TFB401412 IOTA” for typical
connector locations on a non-redundant model CC/CU-TFB401 and a redundant model CC/CU-TFB411
IOTAs respectively.

36 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

3 Repeat Step 1 to connect FTE yellow and green cables for partner Series C FIM4 in the lower module slot
on a redundant IOTA to J7 FTE A and J8 FTE B connectors, respectively. Otherwise, go to Step 3.
4 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 1 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J2-1 and the negative (-) lead to
J2-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
5 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 2 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J3-1 and the negative (-) lead to
J3-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
6 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 3 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J4-1 and the negative (-) lead to
J4-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
7 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 4 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J5-1 and the negative (-) lead to
J5-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
8 If you have the optional redundant power conditioner IOTA, use the cable provided to connect to J6on a
non-redundant or a redundant IOTA.

37
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 3: Typical Connector Locations on Non-Redundant Model CC/CU-TFB401 IOTA

38 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 4: Typical Connector Locations on Non-Redundant Model CC/CU-TFB401412 IOTA

To wire a CC/CU-TFB402 or CC/CU-TFB412 IOTA

1 Connect yellow FTE cable from Control Firewall (CF9) to J8 FTE A connector on a non-redundant CC-
TFB412 IOTA. For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect yellow
FTE cable from CF9 to J10 FTE A on the IOTA.
2 Connect green FTE cable from Control Firewall (CF9) to J7 FTE B connector on a non-redundant CC-
TFB412 IOTA. For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect green
FTE cable from CF9 to J9 FTE B on the IOTA.

Refer to “Figure 5: Typical Connector Locations on Non-Redundant Model CC/CU-TFB402 IOTA” and
“Figure 6: Typical Connector Locations on Redundant Model CC/CU-TFB412 IOTA” for typical connector
locations on a non-redundant model CC/CU-TFB402 and a redundant model CC/CU-TFB412 IOTAs
respectively.

39
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

3 For non-redundant FIM4 Kit, connect yellow FTE cable to J10 FTE A connector, and green FTE cable to J9
FTE B connector on the IOTA. For redundant FIM4 Kit, connect yellow FTE cable to J10 and J8 FTE A
connectors on a redundant IOTA, and connect green FTE cable to J9 and J7 FTE B connectors on the IOTA.

4 Repeat Step 1 to connect FTE yellow and green cables for partner Series C FIM4 in the lower module slot
on a redundant IOTA to J8 FTE A and J7 FTE B connectors, respectively. Otherwise, go to Step 3.
5 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 1 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J2-1 and the negative (-) lead to
J2-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
6 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 2 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J3-1 and the negative (-) lead to
J3-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
7 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 3 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J4-1 and the negative (-) lead to
J4-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
8 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 4 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J5-1 and the negative (-) lead to
J5-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
9 If you have the optional redundant power conditioner IOTA, use the cable provided to connect to J6on a
non-redundant or a redundant IOTA.

40 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 5: Typical Connector Locations on Non-Redundant Model CC/CU-TFB402 IOTA

41
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 6: Typical Connector Locations on Redundant Model CC/CU-TFB412 IOTA

To wire CC/CU-TFB811 IOTA

1 Connect yellow FTE cable from Control Firewall (CF9) to J8 FTE A connector on a redundant IOTA. For
Series C FIM8 mounted in the upper module slot on a redundant IOTA, connect yellow FTE cable from CF9
to J8 FTE A on the IOTA.
2 Connect green FTE cable from Control Firewall (CF9) to J7 FTE B connector on a redundant IOTA. For
Series C FIM8 mounted in the upper module slot on a redundant IOTA, connect green FTE cable from CF9
to J7 FTE B on the IOTA.

Refer to “Figure 7: Typical Connector Locations on Redundant Model CC/CU-TFB811 IOTA” for typical
connector locations on redundant model CC/CU-TFB811 IOTAs.
3 Repeat Step 1 to connect FTE yellow and green cables for partner Series C FIM8 in the lower module slot
on a redundant IOTA to J10 FTE A and J9 FTE B connectors, respectively. Otherwise, go to Step 3.

42 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

4 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 1 on a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J2-1 and the negative (-) lead to
J2-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
5 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 2 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J3-1 and the negative (-) lead to
J3-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
6 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 3 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J4-1 and the negative (-) lead to
J4-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
7 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 4 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J5-1 and the negative (-) lead to
J5-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
8 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 5 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J13-1 and the negative (-) lead to
J13-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
9 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 6 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J14-1 and the negative (-) lead to
J14-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
10 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 7 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J15-1 and the negative (-) lead to
J15-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
11 Observing polarity and using the molded plug provided in the connector make applicable connections as
follows for FFLINK 8 on a redundant IOTA:
• Connect the positive (+) lead of the Fieldbus H1 link cable to terminal J16-1 and the negative (-) lead to
J16-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
12 If you have the optional redundant power conditioner IOTA, use the cable provided to connect to J17 on a
redundant IOTA for FFLINK 1 to 4 and connect to J18 for FFLINK 5-8.

43
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 7: Typical Connector Locations on Redundant Model CC/CU-TFB811 IOTA

44 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.3 Installing Input/Output termination assembly DC-TFB402 or DC-

TFB412
Following are the considerations for installing Input/Output termination assembly DC-TFB402 or DC-TFB412.
• You can use a redundant IOTA to support a non-redundant Series C FIM application. You must ensure to
install the non-redundant Series C FIM in the upper module slot on the IOTA.
• You are responsible for supplying power, power conditioning and wiring for each Fieldbus H1 link.
• Ensure that the enclosure is connected to a protective earth ground using #8 AWG solid copper wire. There
should be contact between the grounding bus bar and the enclosure as well as the carrier.
• The Series C FIM supports connectivity of 350 mA for up to 16 non-intrinsically safe mounted devices.
• You are responsible for observing all local ordinances governing the wiring and installation of electrical
equipment.
• The Series C FIM is designed for removal and insertion under power. Ensure to observe general precautions
when working with powered electrical equipment.
• The orientation of the FTE A and FTE B connectors may be reversed depending on the IOTA version that is
installed. Ensure to always connect the yellow cable to the FTE A connector and the green cable to the FTE
B connector.

Tip
When securing a redundant IOTA to the backplane, install the mounting screws in all locations on one side of the
board first and then install the screws in the locations on the other side.

Prerequisites
• Backplane for mounting IOTA is installed in a cabinet.
• Series C power supply is installed.
• Control Firewalls (CF9s) are installed.
• All wiring and pre-fabricated cables are available and labeled as applicable.
• You have the mounting hardware supplied with the components.

To mount an IOTA Series C FIM4 Kit

1 Select the desired mounting location on backplane and align mounting holes in IOTA with screw hole
locations on the carrier. See the following dimension drawings for details.
• Ensure that the component side of IOTA is facing up. Secure IOTA to backplane using screws, washers,
and spacers provided.
• Insert spacers and washers between bottom of IOTA and top of backplane.

45
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

2 Tighten the mounting screws.

46 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 8: Mounting Dimensions for Non-Redundant IOTA DC-TFB402

47
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 9: Mounting Dimensions for Redundant IOTA DC-TFB412

To wire a DC-TFB402 or DC-TFB412 IOTA

1 Connect yellow FTE cable from Control Firewall (CF9) to J8 FTE A connector on a non-redundant CC-
TFB412 IOTA. For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect yellow
FTE cable from CF9 to J10 FTE A on the IOTA.
2 Connect green FTE cable from Control Firewall (CF9) to J7 FTE B connector on a non-redundant CC-
TFB412 IOTA. For Series C FIM4 mounted in the upper module slot on a redundant IOTA, connect green
FTE cable from CF9 to J9 FTE B on the IOTA.

Refer to “Figure 5: Typical Connector Locations on Non-Redundant Model CC/CU-TFB402 IOTA” and
“Figure 6: Typical Connector Locations on Redundant Model CC/CU-TFB412 IOTA” for typical connector
locations on a non-redundant model CC/CU-TFB402 and a redundant model CC/CU-TFB412 IOTAs
respectively.

48 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

3 For non-redundant FIM4 Kit, connect yellow FTE cable to J10 FTE A connector, and green FTE cable to J9
FTE B connector on the IOTA. For redundant FIM4 Kit, connect yellow FTE cable to J10 and J8 FTE A
connectors on a redundant IOTA, and connect green FTE cable to J9 and J7 FTE B connectors on the IOTA.

4 Repeat Step 1 to connect FTE yellow and green cables for partner Series C FIM4 in the lower module slot
on a redundant IOTA to J8 FTE A and J7 FTE B connectors, respectively. Otherwise, go to Step 3.
5 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 1 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J2-1 and the negative (-) lead to
J2-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
6 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 2 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J3-1 and the negative (-) lead to
J3-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
7 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 3 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J4-1 and the negative (-) lead to
J4-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.
8 Observing polarity and using the molded plug provided in the connector, make applicable connections as
follows for FFLink 4 on a non-redundant or a redundant IOTA:
• Connect the positive (+) lead for the Fieldbus H1 link 1 cable to terminal J5-1 and the negative (-) lead to
J5-2.
• Connect the cable shield to the field wiring shield landing bus bar in the enclosure.

49
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 10: Typical Connector Locations on Non-Redundant Model DC-TFB402 IOTA

50 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 11: Typical Connector Locations on Redundant Model DC-TFB412 IOTA

51
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.4 Setting unique device index for Series C FIM4

Following are the considerations for Setting unique device index for Series C FIM.
• The Device Index setting on a redundant Series C FIM IOTA is assigned to the upper module slot.
• For a redundant Series C FIM application, ensure to set the Device Index to be an odd number. The odd
number will be used for the primary Series C FIM and a one (1) will be added to the number to be used as a
device index for the secondary Series C FIM. For example, if you set the Device Index to 17 for the primary
Series C FIM, the Device Index for the secondary Series C FIM would be 18.
• We recommend setting the Device Index for a non-redundant Series C FIM application to an odd number
also, so you can easily upgrade to a redundant Series C FIM application at a later date, if desired.
• For FIM8 you need to set odd device index only.

Prerequisites
You have mounted and wired the IOTA for a given non-redundant Series C FIM or a redundant Series C FIM
pair.

To set unique device indexes

1 Locate the three binary-coded decimal rotary switches on the left side of the IOTA.
2 Use a small flat-bladed screwdriver or your thumbnail to set the left-hand switch (100) to the desired most
significant decimal number, middle switch (10) to next desired most significant decimal number and the
right-hand (1) switch to the desired least significant decimal number. The applicable setting range is 01 to
509.

52 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.5 Installing Series C FIM4 CC- or CU-PFB401

Following are the considerations for Installing Series C FIM4 CC- or CU-PFB401.
• You can install a non-redundant Series C FIM4 on a redundant IOTA. Ensure to install the non-redundant
Series C FIM4 in the upper module slot on the IOTA.
• You can install series C FIM8 CC-PFB801 on a FIM8 IOTA only.
It is not applicable for Series C Mark II.
• The IOTA and Series C FIM4 are keyed, so you cannot install any other Series C module on a Series C
FIM4 non-redundant or a redundant IOTA.

Prerequisites
You have installed a non-redundant or a redundant IOTA, as applicable.
Only use a #2 Phillips screwdriver to carefully tighten the long gray plastic screw on the Module's face. Do not
use either a #1 Phillips screwdriver or a battery powered screw driver to remove or install the plastic screw as
this can damage the screw head.

To mount a Series C FIM4

1 Align Series C FIM4 connector pins over connector/slot on IOTA. On redundant IOTA, ensure that it is the
upper slot location.
2 Carefully press the Series C FIM until it is fully seated in the connector.
3 Use the three screws provided to secure the Series C FIM to the IOTA.
4 For redundant applications, repeat Steps 1 to 3 to mount a second Series C FIM on the bottom or secondary
connector location on the redundant IOTA.

53
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.6 Installing redundant power conditioner IOTA F660A or F860

Attention
This section is not applicable for Series C Mark II.

Following are the considerations for Installing redundant power conditioner IOTA F660A or F860
• The optional power conditioner is supplied by the vendor MTL-Relcom. Refer to the vendor supplied
documentation for more information about the product.
• The F660A redundant power conditioner includes the following components.
One unpopulated IOTA part number F660A-C
Eight power modules part number FPS-IPM
One Alarm module part number F660A-ALM
• The F660A-NR non-redundant power conditioner includes the following components.
One unpopulated IOTA part number F660A-C
Four power modules part number FPS-IPM
One alarm module part number F660A-ALM
Four blanking modules part number FPS-BLK
• The F860 8-segment redundant power conditioner includes the following components.
One unpopulated IOTA part number F860-CA
Two 8-segment power modules F801
• You should mount the Power Conditioner IOTA above or below the associated Series C FIM IOTA on the
carrier.
• The optional power conditioner supplies redundant power to all four H1 links on the associated Series C
FIM IOTA as well as alarm contacts to monitor circuit status.
• The following procedure is based on installing a model F660A redundant power conditioner. The procedure
is very similar for a model F860 redundant power conditioner except that it has two 16-pin connectors for
powering 4-segments on two separate Series C FIMs.
If you use a non-isolated power conditioner, you must provide a separate isolated input power source for the
power conditioner IOTA, since the Series C power subsystem is not isolated.

Prerequisites
You have installed a non-redundant or a redundant IOTA, as applicable.

To mount a power conditioner

1 Select the desired mounting location on carrier and align mounting holes in IOTA with screw hole locations
on the carrier. See the following dimension drawing for details.
2 Ensure that the component side of IOTA is facing up. Secure IOTA to carrier using screws, washers, and
spacers provided. Insert spacers and washers between bottom of IOTA and top of carrier.

54 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

Figure 12: Mounting Dimensions for Redundant Power Conditioner IOTA F660A

To wire a power conditioner to an IOTA

1 Tighten the screws in both sets of terminals for 24 Vdc + and COM (logic ground) to the vertical bus bar to
connect to the cabinet resident 24 Vdc power supply.
2 Connect the cable plug from the 16-pin connector on the IOTA to the mating 16-pin connector on the
associated Series C FIM IOTA.

55
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.7 Upgrading Series C FIM4/FIM8 firmware

Please refer to the Upgrading Firmware in Multiple Series C Devices section in the Control Hardware and I/O
Module Firmware Upgrade Guide for information about upgrading firmware in a Series C FIM.

56 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.8 Converting non-redundant Series C FIM4 to redundant Series C FIM4/

FIM8
Following are the considerations for converting non-redundant Series C FIM4 to redundant Series C FIM4/
FIM8
• The Series C FIM4/FIM8 redundant pair must have odd/odd+1 device index number combination, which
means the primary or non-redundant Series C FIM4/FIM8 must have an odd address to support an odd+1
address for the secondary Series C FIM4/FIM8. For example, if you set the Device Index to 17 for the
primary Series C FIM4/FIM8, the Device Index for the secondary Series C FIM4/FIM8 would be 18.
• You can make the conversion to Series C FIM4/FIM8 redundancy while the process is online.
• The partner Series C FIM4/FIM8 to be added is at the same firmware revision level as the existing primary
Series C FIM4/FIM8.

Prerequisites
• The non-redundant Series C FIM4/FIM8 to be converted is currently mounted in the upper module slot on a
redundant IOTA.
• The non-redundant Series C FIM4//FIM8 to be converted has an odd number device index.
• You have logged on with sufficient security level to make changes in a control strategy in Control Builder.

To convert to redundant Series C FIM4/FIM8

1 The following procedure outlines how to convert an existing non-redundant Series C FIM4/FIM8 to a
redundant one given that specified prerequisites are met.
2 Install Secondary Series C FIM4/FIM8 in the lower module slot on a redundant IOTA. See previous section
on Wiring CC/CU-TFB811 IOTA and procedures for more information.
3 In the Project tab, double-click the FIM4/FIM8 icon for the current non-redundant Series C FIM4/FIM8 to
open the FIM4/FIM8 Block Parameters form.
4 Click the Module is redundant check box.
5 Check that Secondary Tag Name is specified. The default name is Tag Name plus SEC suffix.
6 Click OK to save the changes and close the form.
7 Check that FIM4/FIM8 icon is now redundant and the icon for the secondary FIM4/FIM8 appears in the
Project tree.
8 Double-click the Secondary FIM4/FIM8 icon to open FIM4SEC Block Parameters form or FIM8 SEC
Block Parameters form. Configure block as required. See for reference.
9 Click OK to save changes and close the form.
• Right-click the Primary FIM4/FIM8 icon and select Load from the list.
• Click Continue to acknowledge the Warning prompt, if applicable.
• Confirm that only the FIM4/FIM8 block is selected for download, as shown in the sample illustration
below.
• Click OK to load the block.

57
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

10 Right-click the Secondary FIM4 icon and select Load from the list. Click Continue to acknowledge
Warning, if applicable; and click OK to load the block.
11 If both Series C FIM4/FIM8 are installed and auto synchronization is enabled, the modules will synchronize
when power is applied.

58 www.honeywell.com
 5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

5.9 Converting redundant Series C FIM4/FIM8 to non-redundant Series C

FIM4/FIM8
The following procedure outlines how to convert an existing redundant Series C FIM4/FIM8 to a non-redundant
one given that specified prerequisites are met.

Attention
• You must perform the steps to convert the non-redundant series C FIM4/FIM8 to redundant Series C FIM4/FIM8
and vice versa correctly. If not, when a link is made active, you may see an unexpected Uncommissioned Device
which appears on the link in the Control Builder monitoring mode. This device is a representation of the secondary
FIM4/FIM8 link and has no functional impact.
• The appearance of the FIM4/FIM8 link as Uncommissioned Device in the Control Builder monitoring mode is
suppressed if:
1. You perform FIM4 switchover if FIM4/FIM8 is redundant.
2. You remove the secondary FIM4/FIM8 from the IOTA if the FIM4/FIM8 is non-redundant.

Following are the considerations for Converting redundant Series C FIM4/FIM8 to non-redundant Series C
FIM4/FIM8.
• Only the Series C FIM4/FIM8 with odd+1 device index number, which is installed in the lower module slot
on a redundant IOTA, can be removed from the system.
• If you try to delete a secondary Series C FIM4/FIM8 from the Monitoring tab while the redundant Series C
FIM4/FIM8 pair is synchronized, the command will be rejected.
• If the secondary Series C FIM4/FIM8 is still installed when the primary/non-redundant Series C FIM4/FIM8
is loaded, an alarm will signal the presence of an unconfigured partner.
• You can use a redundant IOTA to support a non-redundant Series C FIM4/FIM8 application. Just be sure the
non-redundant Series C FIM4/FIM8 is installed in the upper module slot on the IOTA.

Prerequisites
• The Primary Series C FIM4/FIM8 has an odd number for its device index.
• The Secondary Series C FIM4/FIM8 has an odd+1 number for its device index and it is installed in the
lower module slot on the redundant IOTA.
• You have logged on with sufficient security level to make changes in a control strategy in Control Builder.

To convert to non-redundant Series C FIM4/FIM8

1 In the Monitoring tab, double-click the Primary FIM4/FIM8 block icon to open the FIM4/FIM8 Block
Parameters form.
2 On the Main tab, confirm that block Redundancy Role is Primary and Device Index is an odd number.
3 If the Series C FIM4/FIM8 with the odd device index number is not the Primary, click the Redundancy tab
and click Initiate Switchover to issue a switchover command.
4 On the Redundancy tab, click Disable Synchronization to disable auto synchronization. Click Yes to
confirm the action.
5 Click OK to close the form.
6 Loosen the three screws in the secondary Series C FIM4/FIM8 and remove it from the lower module slot on
the redundant IOTA. Remove FTE cable connections, as applicable.
7 In the Monitoring tab, right-click the secondary FIM4/FIM8 icon and select Delete from the list. Click
Delete selected object(s) to confirm the action.
8 In the Project tab, right-click the secondary FIM4/FIM8 icon and select Delete from the list. Click Delete
selected object(s) to confirm the action.

59
5 SERIES C FIM4/FIM8 INSTALLATION AND UPGRADES

9 In the Project mode, clear the Module is Redundant check box.

• Right-click the primary/non-redundant FIM4/FIM8 icon and select Load from the list.
• Click Continue to acknowledge the Warning prompt, if applicable.
• Confirm that only the FIM4/FIM8 block is selected for download.
• Click OK to load the block.

60 www.honeywell.com
6 Series C FIM4/FIM8 configuration

This section includes the following topics on information and tasks associated with Configuring FIM4/FIM8,
FFLinks, and Fieldbus Devices for use in control strategies created in Control Builder.

Topic
“Adding FIM4/FIM8 block to project” on page 64
“Checking FFLink configuration” on page 66
“FFLink configuration parameters reference” on page 68
“Creating a fieldbus device type from vendor DD”
“Editing device block parameters” on page 77
“Adding a fieldbus device to project” on page 78
“Assigning a device to a FFLink in Project” on page 79
“Checking device configuration” on page 80
“Making fieldbus block template and assigning function block to device” on page 82
“Configuring advanced alarming” on page 83

Please refer to the Control Building User's Guide for basic functionality details about calling up, navigating and
interacting with the application. Also, be aware that menus, selections, tree views, and configuration forms may
vary depending upon the licensed options installed on your system.

Attention
The procedures for Configuration FIM8 module and IOTA is similar to FIM4.

Related topics
“Non-Experion interface precautions” on page 62
“Free VCR recommendation” on page 63
“Adding FIM4/FIM8 block to project” on page 64
“Checking FFLink configuration” on page 66
“FFLink configuration parameters reference” on page 68
“Creating a Fieldbus device type from vendor DD” on page 73
“Editing device block parameters” on page 77
“Adding a fieldbus device to project” on page 78
“Assigning a device to a FFLink in Project” on page 79
“Checking device configuration” on page 80
“Making fieldbus block template and assigning function block to device” on page 82
“Configuring advanced alarming” on page 83
“Block Offnet diagnostic alarm” on page 90

61
6 SERIES C FIM4/FIM8 CONFIGURATION

6.1 Non-Experion interface precautions

You can use available non-Experion handheld and standalone Fieldbus interfaces to change parameters in
Fieldbus devices. These interfaces are particularly useful for bench configuration and calibration functions. You
can connect third-party interfaces to the Fieldbus network through one of the four data link visitor addresses
(252 to 255) reserved for them. While some interface products appear to successfully co-exist with the Experion
Fieldbus Interface Module, others may impede or disrupt the ability to perform some system operations. Be sure
you review the following precautions before using a non-Experion interface with Fieldbus devices in an
Experion system.

CAUTION
• Why you need to be very careful when using non-Experion handhelds and non-Experion standalone Fieldbus
interfaces with devices in an Experion system:
• They do not honor Experion access rights and they may or may not have their own independent personnel
access control mechanisms.
• They do not record changes in Experion event log files and they may or may not have their own
independent change recording mechanisms.
• If they are used to change the values of parameters, the stored values for those parameters may not be
updated in the Experion Control Builder 'Monitor' or 'Project' databases. In this case, a reload of the device
may result in loss of changed values. Users are responsible for uploading and/or updating Experion databases
manually to maintain up-to-date values.
• They might be able to affect the configuration of Fieldbus devices beyond the control of Experion systems.
The alternations could include changes to link publication schedules, backup link publication schedules,
function block execution schedules, function block connections, tag names, and so on. Users are responsible
for making sure that no alteration could occur from using a non-Experion interface, since Honeywell cannot
guarantee that an alteration will not occur.
• Only highly trained individuals who completely understand Foundation Fieldbus and the Experion
configuration and support role for Foundation Fieldbus should use non-Experion interfaces with devices in an
Experion system.
• Never connect non-Experion interfaces while commissioning devices and/or loading (or reloading) Control
Modules containing Fieldbus function blocks.
• Never make any parameter changes without the knowledge and cooperation of plant/mill operations personnel.
• Never use non-Experion interfaces to load or commission devices.
• Always connect non-Experion Interfaces to the network as visitor only at one of these four addresses: 252,
253, 254, or 255.
• Always connect non-Experion Interface to the network as Basic Device Type. Never connect as Link Master
Type.
• You can use any spare connection terminal on the bus to connect non-Experion interfaces; but you must make
sure that the connection is secure or it could disrupt link communications.
• Carefully consider the need for using a non-Experion interface in the field, since most of them are very SLOW
in comparison to Experion operations.
• Be aware that non-Experion interfaces can use significant bandwidth that could affect Experion performance.
• Always remove non-Experion interfaces from the network when their intended task is completed.

62 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

6.2 Free VCR recommendation

We recommend that you leave at least one VCR free during configuration so that device replacement will not
require you to free a VCR first. Each Fieldbus segment requires at least one free VCR to support reloading or
replacing a device on the segment. If you configure each segment with the maximum number of VCRs allowed,
128 per segment for Series C FIM, you will need to free a VCR before you can complete a device replacement
on the given segment. Typically, you can free a VCR by deleting a Control Module or device from the
Monitoring tab in Control Builder. Control Builder displays a Warning message when a segment is low on free
VCRs.

Attention
• When the number of VCRs used on an FF Link is greater than 64, you must clear the Update Parameter checkbox,
as Update to Project must be performed in several steps. For each step, select the CMs such that the total number
of VCRs used by these CMs is less than the available VCRs on the link, which is (128 - total number of VCRs)
used on the Project mode.
• When the number of VCRs used on an FF Link is greater than 50% of the maximum VCR (128) link count, the
Update to Project or Upload operation clears all existing connections between the FF and Experion blocks in the
Project mode. Therefore, to prevent this, you must select the Parameters Only checkbox when performing an
Update to Project or Upload. This updates only the parameter values from the Monitoring mode.

63
6 SERIES C FIM4/FIM8 CONFIGURATION

6.3 Adding FIM4/FIM8 block to project

Following are the considerations for adding FIM4/FIM8 block to project.
• You cannot add a FIM4/FIM8 block to the Project tab without first configuring the applicable IP addresses
for the FTE network and NTP servers.
• You can only view FIM4/FIM8 blocks in Project tab set for the Assignment view. The Assignment view
shows the relationship among all blocks while the Containment view only shows templates that contain
other templates or Control Modules (CM), Sequential Control Modules, (SCM) and basic blocks. To toggle
the view, right-click in an open area of the tab window and select Assignment View or Containment View
from the list, as applicable.
• You can configure a FIM4/FIM8 block in the Control Builder Project tab without the FIM4/FIM8 hardware
being installed. However, it is good idea to have the FTE communications driver and hardware that is going
to be used for the system installed, configured, and running. The FIM4/FIM8 needs its device index number
specified on its configuration form to complete its IP address data. Like the C300 Controller, the Series C
FIM4/FIM8 represents a hardware module and the block configuration specifies the communication path to
the hardware.
• Each FIM4/FIM8 block is automatically assigned a unique default tag name when it is created. If your
system will include multiple FIM4s/FIM8, you may want to adopt a more structured syntax for naming
them.
• The block tag name can be up to 16 characters long and must contain at least one letter (A-Z). It must not
contain an embedded space or leading space, and dots are allowed in parameter naming only.
• The item name can be up to 40 characters long and must contain at least one letter (A-Z). It is a name by
which an entity is known within the context of the enterprise model. The Item name must be unique among
children of the same containment parent in the Enterprise Model Builder hierarchy and should conform to
the standard convention for names within the system.
• The Series C FIM4/FIM8 module includes a temperature sensor that monitors its ambient temperature. If the
module's ambient temperature exceeds the configurable Temperature High Alarm value, it will trigger an
alarm. The module's temperature sensing function automatically compensates for wild swings in the ambient
to minimize nuisance alarms.
• If you are using a power conditioning solution that is not integrated with the Series C FIM4/FIM8 and does
not connect to the power conditioner connector on the IOTA, check the Suppress H1 Power Alarm check
box on FIM4s/FIM8s Main tab to suppress power alarms.

Prerequisites
• You have started Configuration Studio and launched the Control Builder application.
• You have logged on with sufficient privileges to create control strategies using Control Builder.
• You have configured the applicable IP addresses when you set up your FTE network.
• You have configured applicable Base IP address and IP addresses for network time protocol (NTP) servers
through the System Preferences dialog in Control Builder. See the Control Building User's Guide for more
information about setting IP addresses.

To create a FIM4/FIM8 block

1 On the File menu from the Control Builder, click New > Interface Modules > FIM4 - Fieldbus Interface
Module. Calls up the FIM4 block parameters configuration form Main tab with Tag Name box highlighted.

Attention
• To create FIM8, you must click New > Interface Module > FIM8-Fieldbus Interface Module.

2 In the Tag Name box, key in desired block tag name or accept the default one.
3 Click the Item Name box and key in the name of the item that this object will be associated with in the
Enterprise Model Builder hierarchy.

64 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

4 Click the Device Index box and key in the device index number set on the Series C FIM's IOTA.
5 Click Alarming Enabled to enable the alarming option for the block.
6 Click Temperature High Alarm (deg. C) box and key in desired threshold at which an alarm is generated
for Series C FIM hardware temperature, or accept the default setting of 80 deg. C.
7 Click CPU Free Low Alarm Limit (%) box and key in desired threshold at which an alarm is generated for
Series C FIM CPU availability in percent, or accept the default value of 15 percent.
8 If Series C FIM4/FIM8 is to be part of a redundant pair, click Module is redundant check box to select it.
Otherwise, go to Step 10.
9 For redundant FIM4/FIM8, the Secondary Tag Name is a combination of configured Tag Name plus SEC
suffix.
10 If you want to suppress H1 power alarms, click the Suppress H1 Power Alarm check box to select it.
Otherwise, go to the next step.
11 If you want to enable the safe handling of new devices option, click the Safe Handling of New Devices
Enable check box to select it. Otherwise, go to the next step.
See “Using optional safe handling of new devices” on page 137for more information.
12 If you want to set a delay time for the device drop off link alarm, click the Device Drop Off Alarm Delay
box and key in the desired delay time in seconds. Otherwise, go to the next step.
13 Refer to the Control Building User's Guide and/or the online help to complete configuration data on the
Redundancy, Server History, Server Display, Control Confirmation, and Identification tabs. The
Statistics and Version tabs only contain read-only parameters.
14 When you completed entering configuration data, click OK to close the configuration form and add icon for
non-redundant or redundant FIM4/FIM8 to the Project tab. The FIM4/FIM8 also includes icons for the four
H1 Fieldbus links that it can support.
15 If you have redundant FIM4/FIM8 configuration, right-click the Secondary FIM4/FIM8 icon and select
Module Properties from the list to call up the Parameters configuration form. Configure as required and
click OK to close the form.

65
6 SERIES C FIM4/FIM8 CONFIGURATION

6.4 Checking FFLink configuration

Following are the considerations for checking FFLink configuration
• Like the Series C FIM, you can configure a FFLink through the Project tab of Control Builder without
having the H1 link installed. However, some parameters on the FFLink configuration form can only be
viewed through the Monitoring tab with the Series C FIM4/FIM8 and FFLink installed and communicating
with the system.
• Be sure to click the plus sign in front of the FIM4/FIM8 icon to open its directory tree and expose the
FFLink icons. With the Hierarchal Building license option, must have the Assignment View active to view
FIM4/FIM8 and FFLink blocks.
• In a redundant Series C FIM application, the FFLink blocks are shown with the primary FIM4/FIM8 block
only.
• We recommend that you accept the default values listed for parameters on the System Management and
Network Management (LM) tabs, unless you have prior experience with the devices you are adding to the
FFLink. The default settings were carefully chosen to provide the most logical initial settings for most
applications. It is more efficient to make any needed adjustments to these parameters in the Monitoring
mode.
• A wizard will guide you though the FFLink configuration process.
• The block name can be up to 16 characters long and must contain at least one letter (A-Z). It must not
contain an embedded space or leading space, and dots are allowed in parameter naming only.
• The item name can be up to 40 characters long and must contain at least one letter (A-Z).
• The following illustration shows the entry fields that are common for time related values. The values shown
are the maximums for the given field. Use the Left and Right Arrow keys on the keyboard to move the
cursor left or right in the field and use the increase and decrease buttons provided to adjust values in the
selected field.

66 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

Table 4: Typical Entry Fields for Time Related Values.

Prerequisites
You have completed the previous procedure to add a FIM4/FIM8 block to the Project tab.

To check FFLink values

1 Right-click the FFLink icon and select Module Properties from the list. Calls up the FFLink Block
Parameters configuration form with the Name box highlighted.
2 In the Name box, key in desired block tag name or accept the default one.
3 Click the Item Name box and key in the name of the item that this object will be associated with in the
Enterprise Model Builder hierarchy.
4 Click the Description box, key in desired descriptive text of up to 132 characters. This text will appear in
applicable detail and group displays associated with this block.
5 Click the Link Schedule Optimization box, select desired setting from the list: OPT, OPT_NOFORCE,
or NO_OPT. Default selection is OPT.
6 Click the Sample Skew box; select the desired setting from the list: SKEW or NOSKEW. The default
selection is SKEW.
7 Refer to the Control Building User's Guide and/or the online help to complete configuration data on the
Server History, Server Display, Control Confirmation, and Identification tabs. The Network
Management (Basic), Statistics, and Version tabs only contain read-only parameters.
8 When you completed entering configuration data, click OK to close the configuration form.
9 Repeat this procedure for Links 2, 3, and 4, as required.

67
6 SERIES C FIM4/FIM8 CONFIGURATION

6.5 FFLink configuration parameters reference

The following table summarizes the Fieldbus related parameters that are user configurable through the FFLINK
Block configuration form. These parameters let you uniquely identify the FFLink component in the control
strategy and tune the performance of FFLink communications. Only the FFLink parameters that are user
configurable are listed. Some parameters are only available in the Monitoring mode and they are identified as
Monitor Only in the table.

Tab Parameter Description

Main Acting Primary Link Master Monitor Only
(ACTINGLM) This read-only parameter indicates whether or not this node is the
acting primary Link Master. A check mark in the check box means that
the node is the acting primary Link Master. A blank check box means
that the node is not the acting primary Link Master.
Link Schedule Optimization Specifies if the link schedule is to be automatically optimized or not.
(SCHDOPTIMIZE)
Use the OPT selection for Link Scheduling Optimization that changes
ORDERINCM values. The optimized schedule is used to update the
natural schedule details. The ORDERINLINK/ORDERINCM
parameter values are updated to match the sequence of the optimized
schedule. The next time that the schedule is viewed/loaded, no prompt
asks for confirmation of the action.
Use the OPT_NOFORCE selection for Link Scheduling Optimization
that ignores ORDERINCM values. The optimized schedule is used to
update the natural schedule details. The ORDERINLINK/
ORDERINCM parameter values are left unchanged. The next time that
the schedule is viewed/loaded, a prompt will ask for confirmation of
this action.
Use the NO_OPT selection to disable Link Schedule Optimization for
this Link and use ORDERINCM values. The natural schedule is used.
The DISABLELINKOPT is set true so that an optimized schedule is
no longer created for the link. If an optimized schedule is required
later, change this parameter selection to OPT or OPT_NOFORCE.
Sample Skew Determines when input blocks will execute.
(SAMPLESKEW)
Use the SKEW selection to schedule each input block to execute at the
time closest to where they converge on a common block like an input
selector (minimum loop latency).
Use the NO_SKEW selection to schedule input blocks to execute at
the same time where they converge on a common block like an input
selector (minimum scan skew).
System Step Timer Preset Specifies the preset time for the System Management step timer in
Management seconds. The default value is specified by the communications profile
(T1)
for the application area.
This is an inter-sequence timer. It ensures that devices responding to
system management requests have sufficient time to carry out
necessary actions and transmit a response.
Preset Set Addr Seq Timer Specifies the preset value for the System Management set address
sequence timer in seconds. The default value is specified by the
(T2)
communications profile for the application area.
This is a sequence duration timer. It ensures that incorrectly executed
or incomplete sequences are aborted in the SMK.

68 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

Tab Parameter Description

Preset Addr Wait Timer Specifies the preset value for the set address wait timer in seconds. The
default value is specified by the communications profile for the
(T3)
application area.
This timer allows time for a device at a new address to be accessed and
added to the delegated token list of the LAS.
Network Def Min Token Delegation Defines the default minimum amount of local link capacity that the
Management Time LAS allocates to a single Pass Token Data Link Protocol Data Unit
(LM) (PT DLPDU) sent to the Data Link Entity (DLE). Its range is 32 to
(LMINFREC.DMDT)
32767, its default value is 84 + Data Link Protocol Data Units
(DLPDU) Physical Layer Overhead (PhLO) value, which permits the
sending of one URGENT DLPDU, and its unit is the transmission
duration of one octet.
Def Token Hold Time Defines the default initial amount of local link capacity that the LAS
DLE allocates to each DLE, in one cycle of 'circulating the token',
(LMINFREC.DTHT)
when the LAS sends one or more PT DLPDUs to the DLE. Its range is
276 to 65000 and its default value is 276 + Data Link Protocol Data
Units (DLPDU) Physical Layer Overhead (PhLO) value, which
permits the sending of one URGENT DLPDU, and its unit is the
transmission duration of one octet.
Target Token Rotation Time Specifies the desired upper bound on the time required for one cycle of
the 'circulating the token' to all the DLEs on the local link that the LAS
(LMINFREC.TTRT)
DLE uses. One cycle of 'circulating the token' is measured as the
interval between successive occurrences of the LAS DLE sending a PT
DLPDU, with a token-use sub field specifying Restart to the lowest
numbered node address represented in the local link live list. Its range
is 1 to 60000. The unit is one millisecond.
Link Maint Token Hold Specifies the initial amount of local link capacity that the LAS DLE
Time should allocate to LAS related link maintenance activities in one cycle
of 'circulating the token'. Its range is 292 to 65000 and its default value
(LMINFREC.LTHT)
is 292 + Data Link Protocol Data Units (DLPDU) Physical Layer
Overhead (PhLO) value + Immediate Response Recovery Delay
(IRRD) value + Slot Time (ST) value, which permits the probing of
one node address and the sending of one time available DT DLPDU.
The unit is the transmission duration of one octet.
Time Distribution Period Determines the minimum frequency of time distribution on the local
link. Its initial value is the minimum value required for the link's time
(LMINFREC.TDP)
synchronization class and its range is 5 milliseconds to 55 seconds.
The unit is one millisecond.
LAS DB Status Distribution This parameter is used by the LAS to determine the time between two
Period successive distributions of the LAS' database by means of the LAS
database status SPDUs sent on the local link. Its range is 100
(LMINFREC.LDP)
milliseconds to 55 seconds. The unit is one millisecond.

69
6 SERIES C FIM4/FIM8 CONFIGURATION

Tab Parameter Description

Slot Time Indicates the configured slot time value. It is a fundamental link
parameter with multiple uses. Each Link Master DLE connected to the
(LMLSTREC.ST)
link uses Slot-time to determine how long that DLE monitors the link
for inactivity before sending a CLAIM LAS (CL) DLPDU. Slot-time
is defined such that the nominal link-inactivity monitoring periods of
two DLEs that have consecutive node addresses and do not hold any
token differ by exactly one slot time. Its range is 1 to 4095, and its unit
is the transmission duration of one octet. The default value is 8, which
should be valid for most applications.
Slot-time defines the minimum upper bound on the maximum two-
way asynchronism in immediate communications among interacting
DLEs on the local link when trying to initialize the link, maximized
across all pairs of DLEs on that local link. It is an aggregate measure
of the worst-case implementation delays within the intervening media,
the PhL, and the PhL/DLL interfaces, all of which limit the speed of
two-way DLE interaction on the local link.
DLPdu Physical Layer Indicates the configured Data Link Protocol Data Units (DLPDU)
Overhead Physical Layer Overhead (PhLO) value. The DLE uses it to account
for the Physical Layer induced delay between the end of the last octet
(LMLSTREC.PHLO)
of one DLPDU, as it appears on the link, and the beginning of the first
octet of any other DLPDU, as it appears on the link. It is measured in
units of one octet-duration. Its range is 2 to 63.
Max Response Delay Indicates the configured maximum response delay value. It is a
measure, in units of one slot time, greater than the worst-case period of
(LMLSTREC.MRD)
local Physical Entity inactivity that a DLE can observe. The DLE uses
it to record the Link's maximum response delay. Its range is 1 to 11.
First Unpolled Node ID Indicates the first unused node address value. It is the first node
address of a series of consecutive node addresses, which are to be
(LMLSTREC.FUN)
omitted from the orderly probe of node addresses for DLE's not
specified by the local link live list. Its range is 21 to 247.
This Link This parameter is a two-octet primary identifier for the local link,
within the extended link, whose values are constrained. The DLE uses
(LMLSTREC.TL)
it to record the local link ID. Its default un-initialized value is zero,
which does not permit a bridge to forward to another link. Its range is
0, and 4096 to 65279.
Minimum Inter Pdu Delay Specifies the minimum duration for an interval of non-transmission
that a DLE provides after either receiving or transmitting a DLPDU. It
(LMLSTREC.MID)
is measured in units of the transmission duration of one octet. The
default value is 16 and its range is 0 to the smaller of 120 or
(Maximum Response Delay -1) x Slot Time.
Number of Consecutive Specifies the number of consecutive unused node addresses, which are
Unpolled to be omitted from the orderly probe of node addresses for DLE's not
specified by the local link live list. Its range is 0 to 228 and its default
(LMLSTREC.NUN)
value is 196
Preamble Extension Specifies an extension period for the preamble. A preamble is
transmitted at the beginning of each Physical Layer Protocol Data Unit
(LMLSTREC.PMBEXTN)
(PhPDU) to synchronize bit times. The period may be extended, but
not reduced. It is an Unsigned8 variable with allowable values between
0 and 7.

70 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

Tab Parameter Description

Post Trans Gap Extension Specifies an extension to the minimum period during which a
subsequent transmission shall not commence after transmission of a
(LMLSTREC.PTGEXTN)
PhPDU. For the same minimum period after reception of a PhPDU,
the receiving Physical Layer entity shall ignore all received signaling.
A Medium Dependent Sublayer (MDS) entity shall set a minimum
post transmission period of four nominal bit times. The period may be
extended, but not reduced. It is an Unsigned8 variable with allowable
values between 0 and 7.
Max Inter Channel Signal Defines the maximum accepted differential delay between any two
Skew active channels, as measured from the first PhPDU of a start delimiter,
if the device is to receive concurrently on more than one channel. The
(LMLSTREC.MXICSSW)
delay shall not exceed five nominal bit times. This period may be
extended, but not reduced. The value of the post transmission gap shall
be greater than the value of inter channel skew. It is an Unsigned8
variable with allowable values between 0 and 7.
Time Sync Class Specifies one of the time synchronization classes. The DLE uses it to
record the Link's time synchronization class and to determine the
(LMLSTREC.TIMSCLS)
DLE's own requirement for the minimum time distribution period it
needs to maintain the specified level of time synchronization. Its
default value is 10 ms. The eight classes are None, 1microsecond, 10
microseconds, 100 microseconds, 1 millisecond, 10 milliseconds, 100
milliseconds, and 1 second.
Primary Link Master • Monitor Only
(PRIM_LM_FLG) • Indicates whether or not this node is the primary Link Master. A
check mark in the check box means that the node is the primary
Link Master. A blank check box means that the node is not the
primary Link Master.
• A write to this parameter orders the receiving Link Master to try to
become the Link Active Scheduler (LAS). If the Link Master
becomes the LAS, it returns an FMS Write.rsp(+), which turns the
flag On (check mark). If this attempt fails, it returns an FMS
Write.rsp(-), which keeps the flag Off (blank).
Notes:
• It is a configuration error to have more than one device on a link
configured as the primary Link Master.
• The Series C FIM is the designated primary Link Master for both
of its Links.
• The value of this parameter may only be set to On (check mark)
through a FMS Write or a local interface.
• When this parameter is On and the device is attached to the
network at one of the default addresses, the NMA regards the
value as a configuration value and does not attempt to acquire the
LAS.
• When this parameter is On or it receives a FMS Write.ind to turn it
On from the NMA of a Link Master device that is not the LAS and
is at an assigned address instead of a default one on the network,
the NMA instructs the Data Link Management Entity (DLME) to
acquire the LAS. The two possible outcomes are as follows.
• If the DLME indicates that the attempt failed, the NMA sets the
value of this parameter to Off. If a FMS write response is pending,
the NMA returns a negative response.
• If the request succeeds on either the first or the second attempt, the
NMA sets the value of the parameter to On (if not On already). If
an FMS write response is pending, the NMA returns a positive
response.

71
6 SERIES C FIM4/FIM8 CONFIGURATION

Tab Parameter Description

Boot Operational Function Specifies the Operational Function Class that the device assumes when
Class it is powered up. The class selections are Basic, Link Master, and
Bridge. The Series C FIM is the Primary Link Master for all Links.
(BOOT_OPER)
Device Alarm Conditions Status To enable/disable the alarm conditions status.
Diagnostics
Non-Cache parameters The parameter's real time values are available from the devices and not
from the FIM memory after configuring non-cache parameters in FIM.
Maintenance tab Enable Block Offnet This parameter is used for enabling or disabling the Block Offnet
Diagnostic Alarm Diagnostic Alarm. By default, this parameter is disabled.
(OFFNETALM_ENABLED)

72 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

6.6 Creating a Fieldbus device type from vendor DD

Following are the considerations for creating a Fieldbus device type from vendor DD
• The DD or EDD files can be stored in this directory location C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\system\ER\Release. This directory must include these three files:
The *.FFO file is the DD binary file, or *.FF5 file is the EDD binary file.
The *.SYM file is the device symbol file
The *.CFF file is the device capability file.
• You can skip this procedure, if a block for the given device type already exists in the Control Builder
Library database.
• If you use a version 4.02.02 or older Honeywell Fieldbus device or a version 2.02.02 or older FlowServe
Fieldbus device as a backup Link Master node with redundant Series C FIMs, we recommend that you
assign the device to address 40 (decimal).
• Do not assign addresses below 30 to any backup Link Master devices.

Prerequisites
You must have the Device Description (DD) files or Enhanced Device Description (EDD) files for the Fieldbus
device either on a disk supplied by the manufacturer or downloaded from the vendor's web site. This means you
can make a device block type without being connected to a device.

Attention
• Experion supports DD files and EDD files and continues to process the DD to create a device block type in the
Control Builder library.
• As part of importing a DD file, if the DD file contains parameters in a no_download list, then the parameter load
destination will be set as “No load.”

To create Fieldbus device type

1 On the File menu, click New- > Type- > Fieldbus Device.
2 In the Select Device Type dialog box, Click to browse for the applicable DD file location in the Device
DD Files box.
Or
In Device List box, click the device you want to add to the Control Builder Library.

73
6 SERIES C FIM4/FIM8 CONFIGURATION

A dialog box appears displaying information about the DD version files which are equal to or more than
version 5.
3 Click OK.
If a device supports single or multi-capability feature, then the following dialog box appears.

4 Select any one of the capability levels supported for the device and then click OK.

74 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

Attention
If the DD file template already exists, the following message appears.

• Click Save As to save the device with a different name for device type.
Or
• Click OverWrite to select a device type and overwrite that device type with a new device type.
To select a device type, under Select a Device Template to Overwrite (or) Refresh, select a device type that
you want to overwrite with a new device type.
Or
• Click Refresh to select a device type that you want to refresh with the changes.
To select a device type, under select a Device Template to Overwrite (or) Refresh, select a device type that
you want to refresh with the changes.

5 Click OK to acknowledge the version of DD files.

A dialog box appears displaying information about the DD files, which have Conditionals.

6 Click OK to import the DD files. Monitor progress through the Opening Device Honeywell Files, Creating
Definition Files, and Importing the Block Type to ERDB progress dialog boxes that open in succession.

Attention
If the DD files do not contain Conditionals, then the process of importing DD files continues without displaying a
message about the presence of Conditionals.

75
6 SERIES C FIM4/FIM8 CONFIGURATION

7 Click OK.
In the Library tab, a new device block type is created under the Honeywell's name and the DD files with
constructs are supported.
8 In the Library tab, select a new device block type under the Honeywell's name.
This completes the procedure. Go to the next section Editing device block parameters.

76 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

6.7 Editing device block parameters

Following are the considerations for editing device block parameters
• Be sure you review the Load Destination column for manufacturer specific parameters listed on the
Honeywell tab in the Parameter Definition Editor.
The NOLOAD setting essentially means that the parameter will not be loaded to the device, when the device
is downloaded from the Project tab in Control Builder, so the corresponding parameter in the device itself
will not be overwritten.
The LOAD setting means that the parameter will be loaded to the device and will overwrite the
corresponding parameter in the device itself. Re-set the Load Destination to LOAD, if you want to change
the settings for any given parameter during block configuration.
• Be very judicious about selecting what parameters to edit. By keeping the default values, you may use the
same block type for like vendor devices used in multiple locations in your application. You can make
adjustments to selected device parameters through Control Builder configuration access. Honeywells usually
supply a text file that includes definitions for each function block used in their device.

Prerequisites
You have completed the previous procedure to add Fieldbus device type to the Library tab.

To make edits
1 On the Library tab, click the plus sign (+) for the Fieldbus device type that includes the blocks you want to
edit. Do the same for the device icon to expose its blocks.
2 Double-click the block you want to edit to open the Parameter Definition Editor in the Control Drawing
view pane of Control Builder.
3 View or edit parameters for the selected block in the Parameter Definition Editor. Refer to the Parameter
Definition Editor Reference for more information about using the Parameter Definition Editor.
4 Click the close button on upper right-hand corner of the PDE to close it.
5 If prompted to save changes, click Yes to save edits or No to cancel them.
6 Repeat the procedure for other device blocks, as required.

77
6 SERIES C FIM4/FIM8 CONFIGURATION

6.8 Adding a fieldbus device to project

Following are the considerations for adding fieldbus device to Project.
• Devices created in Project tab automatically include only their fixed function blocks, transducer blocks, and
resource blocks. If the device block type includes instantiable blocks, you must drag and drop the
instantiable block from the block type in the Library tab to the device icon in the Project tab to instantiate
(create) it in the device in Project. See“Instantiable block implementation considerations” on page 117 for
reference.
• You can use drag and drop or menu selections method to assign a device to an FFLink in the Project tab.
• We suggest that you wait to check all block configuration parameters until after the device is assigned to a
FFLink.

Prerequisites
You have completed the previous procedures to add FIM4/FIM8, Links, and device Type through Control
Builder.

To use drag and drop method

1 Click sign in front of the applicable vendor type directory in the Library tab to show stored device block
types.
2 Drag the device icon to an open area in the Project tab. (Note that cursor appears with + sign, when
positioned in a valid location.) Calls up the Name New Function Block(s) dialog box.
3 In the Destination box, key in desired name consisting of up to 16 characters or accept the default name for
the device. Click Finish.
4 Check that device instance with given name is created in Project tab under the Unassigned category.
5 Repeat this procedure to add other devices or go to the next section Assigning a device to an FFLink in
Project.

To use the file menu method

1 On the File menu, click New- > Devices- > Some Honeywell Name Fieldbus Device. (Note that the
Devices menu is dynamically updated to include the vendor and device data for block types created through
the Type function.) Calls up the Block Parameters configuration form for given device with Name box
highlighted
2 In the Name box, key in desired name consisting of up to 16 characters or accept the default name for the
device. Click OK.
3 Check that device instance with given name is created in Project tab under the Unassigned category.
4 Repeat this procedure to add other devices or go to the next section Assigning a device to an FFLink in
Project.

78 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

6.9 Assigning a device to a FFLink in Project

Following are the considerations for assigning a device to a FFlink in Project
• An alternate method to the following procedure is to just drag and drop the device to the applicable FFLink
in Project.
• If duplicate address error message appears, go to the next section Checking device configuration for details
on changing the device's network node address. It is possible for device addresses to be set to the same
default value of 20.

Prerequisites
You have created a Series C FIM block in the Project tab.

To assign a device to a FFLink

1 Click Edit- > Execution Environment Assignment. Or, click the assign button in the toolbar. Calls up
the Execution Environment Assignments dialog box.
2 Click Devices tab. Shows all devices currently in Project tab.
• Click the device you want to assign to a FFLink to highlight it.
• Confirm that the desired FFLink is selected in the Assign To list box.
• Click the Assign → button to assign the selected device to the selected FFLink.
• Check that device is added to the Assigned Modules list box with the assign state icon .
3 Repeat Steps 3 and 4 of other devices as required.
4 Click Close.

79
6 SERIES C FIM4/FIM8 CONFIGURATION

6.10 Checking device configuration

Following are the considerations for Checking device configuration.
• While the device has been assigned to a FFLink, this is still offline configuration of a matching physical
device that is to be connected to this FFLink.
• Each device on the link must have a unique physical device tag (PD_TAG) that the Fieldbus system relates
to a node address. The physical device tag, node address, and the manufacturer device identifier (DEV_ID)
are used to match a configured device to a physical device.
• The preferred address range for Fieldbus devices is 20 to 40 decimal (0x14 to 0x28 hexadecimal). This
provides the most optimized default network range where the first unused node address (FUN) is 41decimal
(0x29 hexadecimal) and the number of unused addresses is (NUN) is 206. We recommend that the Fieldbus
device designated as the backup Link Master be given 21decimal (0x15 hexadecimal) as its assigned
address. All address number entries and displays are based on the decimal system in Control Builder, but the
Fieldbus Foundation uses the hexadecimal system.
• The Device Identification field is blank until the Project device is matched to an uncommissioned device.
• The Physical Device Tag (PD_TAG) and Device State (DEVSTATE) parameters on the Main tab are
unavailable, since they are only active in the Monitoring tab after the FIM4/FIM8/FFLINK/DEVICE is
loaded and communicating with the system.
• In the Experion system, each independent component in the control strategy must have a unique tag name
(NAME). This is automatically enforced through the Control Builder application. For this reason, the unique
name that was assigned to the device when it was created in Project is also assigned as the device's physical
device tag. This is done to assure that the names are unique within the system. This means a change in
NAME results in an automatic change in PD_TAG to keep them the same. However, a change in PD_TAG
does not result in an automatic change in the assigned NAME.
• Note that the name and physical device tag can be different. Since it is possible to change a physical device
tag configuration using a handheld communicator, you must be sure the device name specified on device
configuration form matches the device name configured in the device.
• We recommend that you do not change the default value settings for the active parameters on the System
Management tab unless you are familiar with tuning the performance of Fieldbus links. In most cases, the
parameter values will mirror those configured for the FFLink. The unavailable parameters are only
accessible in the Monitoring tab with the FIM4/FIM8/FFLINK communicating with the system.
• If the form includes a Block Instantiation tab, this device supports instantiable blocks. Please see
“Instantiable block implementation considerations” on page 117 in this book for more information.

Tip
You can simplify the retrieval of important diagnostic information from any Fieldbus device by configuring
meaningful information in the Description field on the configuration form of all associated transducer and resource
blocks in the Project tab. Operators can quickly trace any device-specific alarms to the applicable block through the
device name and description that is displayed on the Alarm Summary in Station. This is especially useful for
diagnosing problems in devices with several transducer blocks, like temperature multiplexers.

Prerequisites
You have assigned the device to a FFLink in the Project tab.

To configure a fieldbus device

1 Double-click the device icon in the Project tab. Calls up the parameter configuration dialog box with Tag
Name (Tag NAME) box highlighted.
2 Accept the assigned name or key in a new one of up to 16 characters. Must be unique within the system.
3 Click the Item Name (Item Name) box. Key in the name of the Entity that this object will be associated
with in the Enterprise Model Builder hierarchy.
4 Click the Description box. Key in desired description for the device consisting of up to 59 characters or
leave it blank.

80 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

5 Click the Device Network Node Address (ADDR) box. Accept the default or key in the device's current
address assignment.
6 Click the Continue button to the right of the Associated Asset (ASSOCASSET) box to call up the Point
Selection dialog. Select an asset from those configured in the Enterprise Model Database to set the Scope of
Responsibility (SOR) for the device/Fieldbus point.
(No validation is done at configuration time. If you enter an asset that does not exist in the points database,
the associated asset for the Fieldbus point reverts to the server point. If the asset does exist but is not an
area enabled asset, then the first area-enabled asset up the tree is used for the SOR of that Fieldbus device.
A subsequent upload of that Fieldbus device point to Control Builder returns the area-enabled asset and not
the original non-assignable asset entered.)
7 Click the System Management tab to display it.
8 Click the Step Timer Preset (T1) box. Accept the default value or key in a new value. This is the preset
value for the System Management step timer. The default value is 15. 0000s.
9 Click the Preset Set Addr Seq Timer (T2) box. Accept the default value or key in a new value. This is the
preset value for the System Management set address sequence timer. The default value is 01:30. 0000s.
10 Click the Preset Set Addr Wait Timer (T3) box. Accept the default value or key in a new value. This is the
preset value for the SM set address wait timer. The default value is 45. 0000s.
11 Click the Network Management (LM) tab to display it. We recommend that you accept the default values
for the parameters on this tab, and revisit this tab in the Monitoring mode, when the FIM4/FIM8/FFLINK is
communicating with the system.
12 Refer to the Control Building User's Guide and/or the online help to complete configuration data on the
Server History, Server Display, Control Confirmation, and Identification tabs. The Network
Management (Basic) and Version tabs only contain read-only parameters.
13 Click OK.
14 Repeat this procedure for another device, as required.

81
6 SERIES C FIM4/FIM8 CONFIGURATION

6.11 Making fieldbus block template and assigning function block to

device
Following are the considerations for making fieldbus block template and assigning function block to device
• The following procedure makes and assigns a Fieldbus analog input block template for example purposes
only. You can easily adapt this procedure to apply to another Fieldbus Library block.
• When assigning a user template to a non-Honeywell Fieldbus device, warning messages may be generated
because of manufacturer specific parameters associated with the device. Be sure that default values for
manufacturer specific parameters are applicable for your given application.

Prerequisites
• You have created a Control Module in the Project tab.
• You have created a Fieldbus device and assigned it to a FIM4/FIM8 link in the Project tab.

To configure fieldbus block template

1 In Project mode, click Library tab, click + sign for FIELDBUS icon, and click AI block icon.
2 Click Templates > Make Template to call up AI Block configuration form.
3 On the Process tab, fill in configuration data in the appropriate boxes to configure the block for operation in
your application using the Control Building User's Guide and online Help for reference.
4 Repeat Step 3 for the other tabs: Alarm, Maintenance, Tune, Ranges, Identification, Block Pins,
Configuration Parameters, Monitoring Parameters, Block Preferences, and Template Defining, as
applicable.
5 When configuration entries are completed, click OK to close the AI Block configuration form and add the
configured AI block as a template under its assigned name in the USER Library on the Library tab.
6 In the Project tab, select and double-click an instantiated Control Module (CM) that is to contain the AI
block template to open the CM in the control drawing of Control Builder. .
7 Drag and drop the AI block icon from the USER Library to the open Control Module in the control drawing
to add the AI block to the CM.
8 Right-click the AI block in the open CM and select Function Block Assign from the list to open Function
Block Assignment Dialog that lists all compatible device blocks that have been assigned to a FIM4/FIM8
Link. .
9 Click the check box to select the desired device. Click Assign.
• If Block Assignment Validation dialog appears with warning message(s), Go to the next Step.
• Otherwise, Go to Step 11.
10 Note the warning message and click Continue.
11 The AI block is assigned to the selected device as noted on the face of the block.
12 Click the close button to close the CM. Click Yes to save the changes to the CM.

82 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

6.12 Configuring advanced alarming

Advanced alarming provides the ability to monitor the diagnostic parameters and generate the system alarms.
The definition of the conditions, association between conditions and diagnostic parameters are user-defined.
The condition configuration is configured in the Control Builder and saved in ERDB and loaded to FIM.
Note: Advanced alarming feature monitors device parameters on a slow schedule.

Attention
If advanced alarming and Field Diagnostics are configured for a device, then while loading the device, a message
appears informing you to use either advanced alarming or Field Diagnostics and then proceed with the load operation.

Following are some of the considerations for configuring diagnostic parameters.

• You can generate alarms based on the conditions which are configured. These conditions are user-defined
aggregations of device diagnostics that are individually generated in Experion.
• You can assign criticalities after the device specific conditions are created to generate the alarms.
• Each condition is loaded to the FIM and is associated with a unique diagnostic parameter to generate alarm.
The alarm server similar to the existing system alarms tracks such alarms.
• Each condition has up to 5 parameter references that are used to select bits for alarm generation. Each
reference selects one or more bits from the parameter.
• You can enable or disable each condition during the run time. When an active condition is disabled then it is
removed from the alarm summary display.
• By default, all conditions are enabled when they are created.
• Based on the system performance, you can reconfigure the alarms to eliminate the conditions that cause
redundant or unnecessary alarms to appear.
• Only the condition status can be modified from the device instance.
• You can define a maximum of 32 conditions per device and configure only five parameters per condition.
• For 32 conditions, parameter references must not exceed 36.
• You can configure only ten unique parameters per device template.

Attention
Fieldbus parameters used to generate Advanced Alarms must be periodically read from the device. This increases the
utilization of unscheduled traffic bandwidth. Ensure to select only those parameters, which are to be monitored.
Ensure that you select only those parameters that are to be monitored.

Group the bit strings which have similar meaning. For example, calibration conditions, temperature conditions,
and so on.

Related topics
“Opening the configuration dialog box” on page 83
“Configuring/creating a condition” on page 84
“Managing the conditions” on page 86
“Enabling or disabling a condition” on page 86
“Assigning criticalities and priorities” on page 88
“Editing an existing condition” on page 88

6.12.1 Opening the configuration dialog box

The default configuration of an advanced alarming for a device template is performed in the configuration
dialog box. Configuration of alarm conditions is limited to the device template in the template library.

83
6 SERIES C FIM4/FIM8 CONFIGURATION

Note:
• The configuration for a device type can be used by all instances of the same type of devices.
• You cannot invoke the Configuration dialog box from the List View.
For more information on creating a device template, see “Creating a fieldbus device type from vendor DD”.

To open the Configuration form from device template/device instance

• On the Field Devices menu, select Configure Advanced Alarming.
– Or
– In the Library mode, right-click on the device template to select Configure Advanced Alarming.
Or
– Press Ctrl+Alt+A.

Attention
– It is not possible to generate any default values for this configuration from the DD, as such; it is a Honeywell-
specific function.
– You can invoke the Configuration dialog box in view only mode from the device instance.
– For more information to open the Configuration dialog box, see “Opening the configuration dialog box” on
page 83.

6.12.2 Configuring/creating a condition

To configure a condition
1 From the Configure Advanced Alarming Dialog, click Condition Listing tab.

84 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

2 Click New.
The Condition Configuration dialog box appears.
3

4 Type the name for the condition in the Condition.

Attention
• The condition name must be unique.
• The condition name must be within the maximum limit of 32 characters.
• The condition name must contain alphanumeric characters. If the condition name contains only numeric or
special characters, then an error message appears displaying the information to provide a valid name.
• An error message appears when you want to configure more than 32 conditions.
• Click OK to continue.

5 The default values for Alarm Criticality and Priority are Failed and Urgent respectively.
From the Alarm Criticality tab, select the appropriate criticality for the condition.
6 From the Priority tab, select the appropriate priority for the condition.
7 From the FF Conditions, select the appropriate check box to choose the parameters.
The selection of parameters is based on the Parameter Reference selection.
To select a parameter/multiple parameters for a condition:
• Select a parameter from the list and the list of available bits are seen.
• Select one or more bits from the list, the summary of all the selections for the condition appears as a tree
view.

85
6 SERIES C FIM4/FIM8 CONFIGURATION

Attention
• It is highly recommended that you must select only a single parameter bit for each condition to easily identify
the cause of the alarm that is generated and to identify the bit transition in the alarm and event summary.
• You must enter an appropriate condition name to reflect the failure mode of the selected bitstrings.
• You must select the appropriate bits from one or more device parameters.
• To clear the selected parameters/bits from the available list, clear the check box.
• Click Clear to clear all the selected options or clear the check box to clear the selected parameters/bits from
the available list. An error message appears displaying the information to clear all the configuration
information selected for the condition. Click Yes to continue.

8 Click Save.

Attention
While exporting/importing the device, the configured alarm conditions are also exported/imported automatically.

6.12.3 Managing the conditions

After you invoke the configuration dialog box, you can manage the conditions by creating, editing and deleting
the conditions. In the Criticality Mapping tab, invoked from the Configuration dialog box, you can view the
list of conditions assigned for a particular criticality. Therefore, you can manage the conditions created for each
device.

6.12.4 Enabling or disabling a condition

You can disable an active alarm condition, which causes it to clear the corresponding alarm from the Alarm
Summary. Similarly, enabling a condition, which consists of at least one data bit string, generates the
corresponding alarm.

Attention
• By default, all the conditions are enabled in the Configure Advanced Alarming dialog box.
• When you enable/disable alarm conditions, the device instance updates the changes from the template as long as
the alarm conditions are not manually changed directly on the device instance.
• When you enable/disable alarm conditions on the device instance, the device instance stops updating changes from
the template. However, if you perform an 'Upload' and 'Update to Project' from the Monitoring view, and if the
project instance matches the template, the device instance again starts updating changes from the template.
Therefore, caution must be exercised when enabling/disabling alarm conditions on the device instance as the
instance will start replicating the template.
• For example, consider a scenario where an engineer changes the value on the device instance (to have it different
from the template). Coincidentally, the engineer sets the device instance value same as the template even though
the intention was not to follow the template. In such a case, the device instance value changes when the value is
changed in the template. However, the engineer would be assuming that the value what was set is retained on the
device instance.

To enable/disable a condition
1 From the Configure Advanced Alarming Dialog, click Condition Listing tab.
2 Select the condition that you want to disable and clear the check box under the Enable column.
Or
Select the condition that you want to enable and select the check box under the Enable column.

86 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

The selected condition is disabled and the changed setting is saved in the database.

Attention
• The conditions can be enabled/disabled in the Device Diagnostics tab in the configuration form of FF devices
from Project /Monitoring modes.

• To enable/disable a condition in Project mode, perform the following steps:

1. Right-click the device instance to select Module Properties.
The configuration form appears.
2. Click the Device Diagnostics tab.
3. Under the Alarm Conditions Status, select or clear the check box to enable/disable the conditions.

87
6 SERIES C FIM4/FIM8 CONFIGURATION

6.12.5 Assigning criticalities and priorities

After defining the conditions, you can view the summary of all the criticality assignments.
You can assign criticality from the list. This attribute remains with the condition and appears on the alarm
summary when the alarm is generated. The criticalities that are available are failure, Maintenance, Check
function, and OffSpecification.
Note: You cannot change the criticality assignments in this view.
For example, when you select Maintenance criticality, the conditions, which are assigned to the same
criticalities, are listed.

6.12.6 Editing an existing condition

To edit an existing condition

1 From the Configure Advanced Alarming Dialog, click Condition Listing tab.
2 Double-click a condition.
Or
Click a condition and Click Edit.
The Condition Configuration dialog box appears.

88 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

3 Perform through steps 4 to step 7 of the section “Configuring/creating a condition” on page 84.

Attention
• You can delete an alarm condition, based on the required alarms to be generated.
• To delete a condition in the Condition Listing tab
1. Select the condition to click Delete.
2. Click Yes to confirm the deletion of the selected condition or press DELETE on the keyboard.

89
6 SERIES C FIM4/FIM8 CONFIGURATION

6.13 Block Offnet diagnostic alarm

Fieldbus function block can optionally be configured to generate a high-priority alarm, when the device
containing the block is disconnected from the network. This is accomplished with the introduction of a new
parameter OFFNETALM_ENABLED. When this parameter is set to 'True' and if the device is off the network,
the Block Offnet Diagnostic Alarm is generated. If you set this parameter to 'False' when the Block Offnet
Alarm is active, the alarm returns to normal. This parameter can be configured before load and can be changed
at runtime, even if the device is offline.

Attention
• When you load the fieldbus block, the value of the Enable Block Offnet Diagnostic Alarm parameter is written to
the Fieldbus Interface Module if;
– the partial load option is selected or cleared.
– the physical device is online or offnet.
• It is not possible to load a CM containing a function block while the device is offnet.

6.13.1 Behavior of the Block Offnet and Device Offnet System alarms in various communication loss
scenarios
The following table lists the behavior of the Block Offnet and Device Offnet System alarms in the various
communication loss scenarios.

Communication loss Behavior of Block Offnet Alarm Behavior of Device Offnet System Alarm
scenario
Loss of communication Block Offnet Alarm is not reported for each Device Offnet System Alarm is not reported
between C300 and FIM loaded function block in the device. for the device.
(This condition occurs if
both the FTE cables are
disconnected.)
Loss of communication A high-priority Block Offnet Alarm is A high-priority Device Offnet System Alarm
between an FF device and reported for only those loaded function is reported for the device.
FIM blocks in the device, which are configured
to report the Block Offnet Alarm.
Communication resumes Previously reported Block Offnet Alarms The Device Offnet System Alarm changes
between an FF Device and change from 'Active' to 'Returned to from 'Active' to 'Returned to Normal' in the
FIM Normal' in the Alarm Summary Display. System Alarm Summary Display.

6.13.2 Behavior of the Block Offnet and Device Offnet System alarms in various operational scenarios
The following table lists the behavior of the Block Offnet and Device Offnet System alarms in the various
operational scenarios. These behaviors are also dependent on whether the devices are online or off the network.

Scenario Behavior of Block Offnet Alarm Behavior of Device Offnet System Alarm
Inactivating a Fieldbus A Block Offnet Alarm is not reported for A high-priority Device Offnet System Alarm
Link when the device is each loaded function block. is reported for the device.
online.
Inactivating a Fieldbus Previously reported Block Offnet Alarms A high-priority Device Offnet System Alarm
Link when the device is off changes from 'Active' to 'Disabled' in the is reported for the device.
the network. Alarm Summary.

90 www.honeywell.com
 6 SERIES C FIM4/FIM8 CONFIGURATION

Scenario Behavior of Block Offnet Alarm Behavior of Device Offnet System Alarm
Activating a Fieldbus Link. Previously reported Offnet Alarms changes Previously reported Offnet Alarms changes to
to 'Disabled' when the Link is inactivated in 'Disabled' when the Link is inactivated in the
the Alarm Summary. When activated, these Alarm Summary. When activated, these alarms
alarms are regenerated to indicate the are regenerated to indicate the current
current condition of the alarm. condition of the alarm.
If the Offnet condition does not exist, the If the Offnet condition does not exist, the
previously reported alarms remain in the previously reported alarms remain in the
Alarm Summary as 'Disabled'. Alarm Summary as 'Disabled'.
Activating or Inactivating a Changing the EXECSTATE parameter value Changing the EXECSTATE parameter value
CM containing a FF has no effect on the alarms reported by has no effect on the alarms reported by
function block. Fieldbus blocks. Fieldbus blocks.
Changing the state of a Changing the state of a CEE containing Changing the state of a CEE containing
CEE containing a FF Control Modules, which contain Fieldbus Control Modules, which in turn contain
function block to 'Idle' or blocks, has no effect on the alarms reported Fieldbus blocks, has no effect on the alarms
'Run.'. by the Fieldbus blocks. reported by the Fieldbus blocks.
Deleting a Device, Link, No alarms are reported for device offnet No alarms are reported for device offnet
FIM or CM containing an conditions. conditions.
FF function block
Enabling the reporting of A change event is logged in the Event
the Block Offnet Summary indicating
Diagnostic Alarm for an OFFNETALM_ENABLED is set to ON.
individual FF function
block when the device is
online.
(The precondition is that
the Block Offnet
Diagnostic Alarm is
configured not to be
reported for the function
block, when the device
goes off the network.)
Enabling the reporting of A high-priority Block Offnet Alarm is A high-priority Device Offnet System Alarm
the Block Offnet reported for that function block. is reported for the device, when the device
Diagnostic Alarm for an goes offnet. There is no change in the system
A change event is logged in the Event
individual FF function alarm.
Summary indicating
block when the device is
OFFNETALM_ENABLED is set to ON.
off the network.
(The precondition is that
the Block Offnet
Diagnostic Alarm is
configured not to be
reported for the function
block, when the device
goes off the network.)
Disabling the reporting of A change event is logged in the Event
the Block Offnet Summary indicating
Diagnostic Alarm for an OFFNETALM_ENABLED is set to OFF.
individual FF function
block when the device is
online.

91
6 SERIES C FIM4/FIM8 CONFIGURATION

Scenario Behavior of Block Offnet Alarm Behavior of Device Offnet System Alarm
Disabling the reporting of The previously reported Block Offnet Alarm There is no change to the Device Offnet
the Block Offnet for that function block changes from 'Active' System Alarm.
Diagnostic Alarm for an to 'Disabled' in the Alarm Summary.
individual FF function
A change event is logged in the Event
block when the device is
Summary indicating
off the network.
OFFNETALM_ENABLED is set to OFF.

Attention
Block alarm disable settings are not retained during device replacement. Hence, you must manually update the block
alarm disable setting configuration or reload the configuration from the ERDB.

92 www.honeywell.com
7 Series C FIM4/FIM8 configuration form reference

Related topics
“FIM4/FIM8 device Diagnostics tab parameters” on page 94
“FIM4/FIM8 Main tab parameters” on page 95
“FIM4/FIM8 Redundancy tab parameters” on page 97
“FIM4/FIM8 System Time tab parameters” on page 98
“FIM4/FIM8 Statistics tab parameters” on page 99
“FIM4/FIM8 Peer Connections tab parameters” on page 100
“FIM4/FIM8 Hardware Information tab parameters” on page 101
“FIM4/FIM8 FTE tab parameters” on page 102
“FIM4/FIM8 UDP/TCP tab parameters” on page 104
“FIM4/FIM8 IP/ICMP tab parameters” on page 106
“FIM4/FIM8 QVCS tab parameters” on page 108
“FIM4/FIM8 Server History tab parameters” on page 109
“FIM4/FIM8 Server Displays tab parameters” on page 110
“FIM4/FIM8 Control Confirmation tab parameters” on page 112
“FIM4/FIM8 Identification tab parameters” on page 113

93
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.1 FIM4/FIM8 device Diagnostics tab parameters

Device Diagnostics tab is common to all configuration forms for tagged blocks in Control Builder. The
following table summarizes the parameter data you can monitor and configure on this tab of the configuration
form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Alarm Conditions Alarm Conditions Status Yes To enable/disable the alarm
Status conditions status.
Non-cache Non-cache Parameters Yes The parameter's real time
values are available from the
devices and not from the
FIM memory after
configuring non-cache
parameters in FIM.

94 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.2 FIM4/FIM8 Main tab parameters

The following table summarizes the parameter data you can monitor and/or configure on the Main tab of the
configuration form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Tag Name NAME Project Only System assigned or user configured
unique name. Consisting of up to 16
characters and at least one character
must be a letter (A-Z).
Item Name Item Name Project Only A non-unique name by which an
entity is known within the context of
the enterprise model.
Application Image Version IMAGEVER No Identifies current version of firmware
installed in module.
Controller Command FIMCOMMAND Monitoring Only Allows user to initiate commands to a
Series C FIM4/FIM8.
Device Index DEVICEIDX Project Only - Matches Unique FTE device index of the
Hardware Setting Series C FIM4/FIM8. Set on Series C
FIM4/FIM8 IOTA switches.
Ethernet IP Address IPADDRESS No IP address of the Series C FIM4/
FIM8, derived as the Embedded FTE
Base Ethernet IP Address plus
configured Device Index.
Temperature High Alarm OVERTEMPTHLD Yes Set threshold value for modules
(deg C) Temperature High alarm.
CPU Free Low Alarm (%) CPULOLM Yes Set CPU Free Low Capacity alarm
limit, in percent.
CPU Free Low Low Alarm CPULOLOLM No Set CPU Free Low Low Capacity
(%) alarm limit, in percent.
Controller State FIMSTATE No Shows Series C FIM4//FIM8 current
state.
Redundancy Role RDNROLESTATE No Shows Series C FIM4/FIM8 current
redundancy role.
Synchronization State RDNSYNCSTATE No Shows Series C FIM4/FIM8 current
synchronization state.
Module is redundant MODISREDUN Project Only Module is part of redundant pair.
Secondary Tag Name SECMODNAME Project Only System assigned name based on tag
name with sec suffix for secondary
block.
Suppress H1 Power Alarm NOPWRDIAG Yes Suppresses H1 Link Power
Diagnostic alarms. This option should
be selected if integrated power
alarming functionality is not to be
used.
Enable Safe Handling of New SAFEHANDLINGENA Yes Enables safe handling of new
Devices BLED uncommissioned field devices.
Devices previously loaded are not
safe handled when rejoining the link.
See “Using optional safe handling of
new devices” on page 137 for more
information

95
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

Plain Text Parameter Name User Configurable Notes

Device Drop Off Alarm DEVDROPOFFDELAY Yes Sets the amount of time, in seconds, a
Delay device must be offnet before Device
Offnet and Block Offnet Diagnostic
Alarms are generated.

96 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.3 FIM4/FIM8 Redundancy tab parameters

The following table summarizes the parameter data you can monitor on the Redundancy tab of the
configuration form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Redundancy Status
Auto Synchronization State RDNAUTOSYNC No Shows current auto synchronization
state
Redundancy Compatibility RDNCMPT No Shows redundant partner
compatibility
Inhibit Sync Reason RDNINHIBITSYNC No Shows reason that redundancy
synchronization is inhibited
Initial Sync. Progress (%) RDNSYNCPROG No Shows current synchronization
progress in percent
Last Synchronization Time SYNCTIMEBEG No Shows system time when initial
synchronization was completed.
Last Loss of Sync. Time SYNCTIMEEND No Shows system time when last
synchronization was lost.
Redundancy Controllability RDNCTLABILITY No
Redundancy Statistics
Redundancy Traffic (bytes/ RDNXFERAVG No
sec)
Max Redun. Traffic (bytes/ RDNXFERMAX No
sec)
Redundancy Delay (%) RDNDELAYAVG No
Max Redundancy Delay (%) RDNDELAYMAX No
Max Initial Sync Time (sec) RDNINSTIMEMAX No
Max Switchover Time (msec) RDNSOTIMEMAX No
Disable Synchronization DSBLSYNCCMD No Button to initiate command in
Monitoring mode
Alternate Sync. Over FTE ALTSYNCCMD No Button to initiate command in
Monitoring mode.
Become Primary BECMPRICMD No Button to initiate command in
Monitoring mode.
Enable Synchronization ENBLSYNCCMD No Button to initiate command in
Monitoring mode.
Initiate Switchover SWITCHCMD No Button to initiate command in
Monitoring mode.
Redundancy History
Time RDNHISTTIME No Show time of related state.
State RDNHISTSTATE No List the last 16 redundancy related
activities.
Reason RDNHISTREASON No Identify reason for redundant history
state
Redundancy Link Failed RDNLINKFAILED No Status indicator to signal link failure

97
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.4 FIM4/FIM8 System Time tab parameters

The following table summarizes the parameter data you can monitor on the System Time tab of the
configuration form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

System Time
Current System Time CURTIME No Shows current system time.
Current System Time Source TIMESOURCE No Shows source of system time. Default
is Simple Network Time Protocol.
SNTP Status
SNTP Status SNTPSTAT No Shows status for time source.
SNTP Skew Limit (msec) SNTPSKEWTHLD No
SNTP Skew Limit Exceeded NUMSNTPSKEWEX No Shows number times SNTP knew
threshold was exceeded.
Max. SNTP Skew (msec) MAXSNTPSKEW No Shows maximum skew recorded.
System Time Synchronization Status
Time Synchronization Status TIMESYNCSTAT No
Time of Last Time Sync TIMELASTSYNC No Shows time Controller Time Synced
with time source
Skew at Last Time Sync TIMELASTSKEW No Shows time skew from last synced
(msec) time.

98 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.5 FIM4/FIM8 Statistics tab parameters

The following table summarizes the parameter data you can monitor on the Statistics tab of the configuration
form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Reset All Statistics STATSRESET No Button to initiate reset in Monitoring
mode.
CPU Utilization
CPU Free (%) CPUFREEAVG No
Minimum CPU Free (%) CPUFREEMIN No
Notification Statistics
Notification Rate TNUMNTFRQUAVG No
Maximum Notifications Rate TNUMNTFRQUMAX No
Hardware Temperature
Current Temperature (deg C) CTEMP No
Maximum Temperature (deg CMAXTEMP No
C)
Maximum Temperature (deg CMINTEMP No
C)

99
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.6 FIM4/FIM8 Peer Connections tab parameters

The following table summarizes the parameter data you can monitor on the Peer Connections tab of the
configuration form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Peer Initiator Connections
Initiating to ACEs TNUMACEINCON No
Initiating to C300s TNUMC3INCON No
Initiating to C200s TNUMCPMINCON No
Initiating to FIM4/FIM8 TNUMSCFIMINCON No
Initiating to SIM-C200s TNUMSCEINCON No
Initiating to LIOMs TNUMLIOMINCON No
Peer Responding Connections
Responding to ACEs TNUMACEOUTCON No
Responding to C300s TNUMC3OUTCON No
Responding to C200s TNUMCPMOUTCON No
Responding to FIM4/FIM8 TNUMSCFMOUTCON No
Responding to SIM-C200s TNUMSCEOUTCON No
Responding to LIOMs TNUMLIOMOUTCON No

100 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.7 FIM4/FIM8 Hardware Information tab parameters

The following table summarizes the parameter data you can monitor on the Hardware Information tab of the
configuration form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Firmware Version
Boot Image Version BOOTIMAGEVER No
Application Image Version IMAGEVER_D No
Hardware Factory Information
Module Type MODTYPE No
Serial Number SERIALNUM No
Programmable Logic Set FWREVISION No
Version
Hardware Major Revision HWREVMAJ No
Hardware Minor Revision HWREVMIN No
Network Interface Address Information
FTE Interface A MAC MACADDRA No
Address
FTE Interface B MAC MACADDRB No
Address
Redun. Interface MAC MACADDRR No
Address

101
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.8 FIM4/FIM8 FTE tab parameters

The following table summarizes the parameter data you can monitor on the FTE tab of the configuration form
for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

FTE Mart Statistics (Provides statistics related to the MAC Address Resolution Table (MART). This deals with on-line
media access control (MAC) address mapping. Two separate tables are maintained - One for FTE nodes and one for non-
FTE nodes. The media access control address entry information is obtained by extracting the source media access control
address from received diagnostic messages.)
Address Count FTEMARTADDRCOUNT No Number of IP addresses contained in
FTE MART.
Max Depth FTEMARTMAXDEPTH No Maximum depth that the FTE MART
has reached (largest number of entries
in table).
Average Depth FTEMARTAVGDEPTH No Average depth of FTE MART
(average number of entries in table).
Address Collisions FTEMARTCOLLCOUNT No Number of collisions that have
occurred when hashing the FTE
MART.
Current FTE Traffic
LAN_A Tx Rate (kBit/sec) LANATXRATE No Indicates communication transmission
rate in kilobits per second (kbps) for
port A (Yellow Tree Port) on the FTE
Bridge.
LAN_B Tx Rate (kBit/sec) LANBTXRATE No Indicates communication transmission
rate in kilobits per second (kbps) for
port B (Green Tree Port) on the FTE
Bridge.
LAN_A Rx Rate (kBit/sec) LANARXRATE No Indicates communication receive rate
in kilobits per second (kbps) for port
A (Yellow Tree Port) on the FTE
Bridge.
LAN_B Rx Rate (kBit/sec) LANBRXRATE No Indicates communication receive rate
in kilobits per second (kbps) for port
B (Green Tree Port) on the FTE
Bridge.
FTM Statistics
Number of FTE nodes NUMFTENODES No Current number of FTE nodes within
FTE community.
Max number of FTE nodes MAXFTENODES No Maximum number of FTE nodes that
have been detected within FTE
community.
Max node ID MAXNODEID No Highest Device Index supported
within FTE community.
IP checksum errors BADIPCSUM No Number of FTE IP messages which
were received but determined as
having bad IP checksums.
UDP checksum errors BADUDPCSUM No Number of FTE UDP messages which
were received but determined as
having bad UDP checksums.

102 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

Plain Text Parameter Name User Configurable Notes

Non-FTE Mart Statistics
Address Count NONFTEMARTADDRCOUN No Number of IP addresses contained in
T non-FTE MART.
Max Depth NONFTEMARTMAXDEPTH No Maximum depth that non-FTE MART
has reached (largest number of entries
in table.
Average Depth NONFTEMARTAVGDEPTH No Average depth of non-FTE MART
(average number of entries in table).
Address Collisions NONFTEMARTCOLLCOUN No Number of collisions that have
T occurred when hashing non-FTE
MART.
Peak FTE Traffic
LAN_A Tx Rate Max (kBit/ LANATXRATEMAX No Indicates maximum communication
sec) transmission rate in kilobits per
second (kbps) for port A (Yellow Tree
Port) on the FTE Bridge.
LAN_B Tx Rate Max (kBit/ LANBTXRATEMAX No Indicates maximum communication
sec) transmission rate in kilobits per
second (kbps) for port B (Green Tree
Port) on the FTE Bridge.
LAN_A Rx Rate Max (kBit/ LANARXRATEMAX No Indicates maximum communication
sec) receive rate in kilobits per second
(kbps) for port A (Yellow Tree Port)
on the FTE Bridge.
LAN_B Rx Rate Max (kBit/ LANBRXRATEMAX No Indicates maximum communication
sec) receive rate in kilobits per second
(kbps) for port B (Green Tree Port) on
the FTE Bridge.
Number of FTE Nodes NUMFTENODES No
Max Number of FTE Nodes MAXFTENODES No
Max Device Index MAXNODEID No
IP Checksum Errors BADIPCSUM No
UDP Checksum Errors BADUDPCSUM No
LAN_A (Yellow) failed LANAFAILED No Status indicator for port A (Yellow
Tree Port) on the FTE Bridge. If this
LED is lit, it is an indication that
communications have failed on Port
A.
LAN_B (Green) failed LANBFAILED No Status indicator for port B (Green
Tree Port) on the FTE Bridge. If this
LED is illuminated it is an indication
that communications have failed on
Port B.
InterLAN comm. failed INTERLANFAILED No Status indicator for Inter-LAN
communications - indicates that inter-
LAN communications have failed.
Crossover cable failed XOVERFAILED No Status indicator for Crossover cable -
indicates that the Crossover cable has
failed.

103
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.9 FIM4/FIM8 UDP/TCP tab parameters

The following table summarizes the parameter data you can monitor on the FTE tab of the configuration form
for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

UDP Statistics (Provides unreliable connectionless packet delivery service between clients.)
Datagrams Delivered UDPINDGRAMS No Total number of User Datagram
Protocol (UDP) datagrams delivered
to destination protocol ports.
Datagrams for Unknown UDPNOPORTS No Total number of received UDP
Ports datagrams for which there was no
application at the destination port.
Datagrams Dropped for UDPINERRORS No Number of received UDP datagrams
errors that could not be delivered.
Datagrams Sent to UDPOUTDGRAMS No Total number of UDP datagrams sent
Applications from this entity.
TCP Statistics (Provides reliable stream delivery service between clients.)
Active Opens TCPACTIVEOPEN No Number of times TCP connections
have made a direct transition to the
SYN-SENT state from the CLOSED
state.
Passive Opens TCPPASSIVEOPENS No Number of times TCP connections
have made a direct transition to the
SYN-RCVD state from the LISTEN
state.
Failed Connection Attempts TCPATTEMPTFAILS No Number of times TCP connections
have made a direct transition to
CLOSED state from either SYN-
SENT state or SYN-RCVD state, plus
number of times TCP connections
have made a direct transition to
LISTEN state from SYN-RCVD state.
Connections Resets TCPESTABRESETS No Number of times TCP connections
have made a direct transition to
CLOSED state from either
ESTABLISHED state or CLOSE-
WAIT state.
Current Connections TCPCURRESTAB No Number of TCP connections for
which current state is either
ESTABLISHED or CLOSE-WAIT.
Segments Received TCPINSEGS No Total number of segments received,
including those received in error.
Segments Sent TCPOUTSEGS No Total number of segments sent,
including those on current
connections but excluding those
containing only retransmitted octets.
Segments Retransmitted TCPRETRANSSEGS No Total number of segments
retransmitted - that is, number of TCP
segments transmitted containing one
or more previously transmitted octets.

104 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

Plain Text Parameter Name User Configurable Notes

Segments Discarded For TCPINERRS No Total number of segments received in
Errors error (for example, bad TCP
checksums).
Reset Segments Sent TCPOUTRESETS No Number of TCP segments sent
containing the RST flag.
Local UDP Listeners <PJ>UDPLISTENERS</PJ> No Shows path information for all open
ports on the FTE Bridge module.
Current TCP Connections <PJ>TCPCONNTABLE</PJ> No Shows path information for all
currently connected clients of the FTE
Bridge module.

105
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.10 FIM4/FIM8 IP/ICMP tab parameters

The following table summarizes the parameter data you can monitor on the IP/ICMP tab of the configuration
form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

IP Statistics (Provides packet delivery services between nodes.)
Datagrams Received from IPINRECEIVES No Total number of input datagrams
Below. received from connected nodes,
including those received in error.
Datagrams Format Errors IPINHDRERRORS No Number of input datagrams discarded
Drops due to errors in their Internet Protocol
(IP) headers, including bad
checksums, version number mismatch,
other format errors, time-to-live
exceeded, errors discovered in
processing their IP options, etc.
Datagrams Misdelivery IPINADDRERRORS No Number of input datagrams discarded
Drops because the IP address in their IP
header's destination field was not a
valid address to be received at this
entity.
Unknown Protocol IPINUNKNOWNPORTS No Number of locally-addressed
Datagrams datagrams received successfully but
discarded because of an unknown or
unsupported protocol.
Datagrams Discarded for IPINDISCARDS No Number of input IP datagrams for
Resrcs which no problems were encountered
to prevent their continued processing,
but which were discarded; for
example, for lack of buffer space.
Datagrams Delivered IPINDELIVERS No Total number of input datagrams
Above successfully delivered to IP user-
protocols, including Internet Control
Message Protocol (ICMP).
Datagrams Sent Out IPOUTREQUESTS No Total number of IP datagrams which
local IP user-protocols (including
ICMP) supplied to IP in requests for
transmission.
Out Datagrams Discarded IPOUTDISCARDS No Number of output IP datagrams for
which no problem was encountered to
prevent their transmission to their
destination, but which were discarded;
for example, for lack of buffer space.
Datagrams Drops for No IPOUTNOROUTES No Number of IP datagrams discarded
Routes because no route could be found to
transmit them to their destination.
Fragments Needing IPREASSEMREQS No Number of IP fragments received
Reassembly which needed to be reassembled at this
entity.
Fragments Reassembled IPREASSEMOKS No Number of IP datagrams successfully
reassembled.

106 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

Plain Text Parameter Name User Configurable Notes

Fragments Reassembly IPREASSMFAILS No Number of failures detected by the IP
Fails reassembly algorithm, for whatever
reason: timed out, errors, etc.
Datagrams Fragmented IPFRAGOKS No Number of IP datagrams that have
been successfully fragmented at this
entity.
Datagrams Fragmentation IPFRAGFAILS No Number of IP datagrams that have
Fails been discarded because they needed to
be fragmented at this entity but could
not be. For example, because their do
not Fragment flag was set.
Fragments Created IPFRAGCREATES No Number of IP datagram fragments that
have been generated as a result of
fragmentation at this entity.
Routing Entries Discarded IPROUTINGDISCARDS No Number of routing entries which were
chosen to be discarded even though
they are valid.
ICMP Statistics (Controls transmission of error and control messages between hosts and gateways.)
Messages Received ICMPINMSGS No Total number of ICMP messages
which the entity received.
Messages with Format ICMPINERRORS No Number of ICMP messages which
Errors entity received but determined as
having ICMP-specific errors such as
bad ICMP checksums and bad length.
Dest. Unreachable Msgs ICMPINDESTUNREACHS No Number of ICMP Destination
Recvd Unreachable messages received.
Echo Messages Recvd ICMPINECHOS No Number of ICMP Echo (request)
messages received.
Echo Reply Messages ICMPINECHOREPS No Number of ICMP Echo Reply
Recvd messages received.
Messages Sent ICMPOUTMSGS No Total number of ICMP messages
which this entity attempted to send.
Out Error Messages ICMPOUTERRORS No Number of ICMP messages which this
entity did not send due to problems
discovered within ICMP such as a lack
of buffers.
Dest. Unreachable Msgs ICMPOUTDESTUNREACHS No Number of ICMP Destination
Sent Unreachable messages sent.
Echo Messages Sent ICMPOUTECHOS No Number of ICMP Echo (request)
messages sent.
Echo Reply Messages ICMPOUTECHOREPS No Number of ICMP Echo Reply
Sent messages sent.

107
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.11 FIM4/FIM8 QVCS tab parameters

The QVCS tab is common to all configuration forms for tagged blocks in Control Builder. If you have a
Qualification and Version Control System (QVCS) license, this tab shows current QVCS information for the
selected FIM4/FIM8 block. Please refer to the online help and the Qualification and Version Control System
User's Guide for more information about the data on this tab.

108 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.12 FIM4/FIM8 Server History tab parameters

The Server History tab is common to all configuration forms for tagged blocks in Control Builder. The
following table summarizes the parameter data you can monitor and configure on this tab of the configuration
form for the selected FIM4//FIM8 block.

Attention
The configuration settings you make for Server Load Options on the System Preferences dialog determines whether
or not the data entered on the Server History tab is loaded to the Experion server. See the Control Building User's
Guide for information about setting system preferences.

Plain Text Parameter Name User Configurable Notes

Access Levels
Control Level SCANCTRLLVL Yes Indicates Server control level to be
associated with this function.
History Configuration
Number of History HIST.NUMPARAMS Yes Defines number of history parameters
Parameters to be included in History
Configuration table.
Parameter HIST.PARAM Yes Valid parameter name for a parameter
associated with the given point that is
to be collected and stored as historical
data at predetermined intervals.
Description No Provides a brief description of the
entered parameter.
FAST HIST.FAST Yes Select the Fast type of history
collection.
STD HIST.STD Yes Select the Standard type of history
collection.
EXTD HIST.EXTD Yes Select the Extended type of history
collection.
EXC HIST.EXC Yes Select the Exception type of history
collection.
(Station only)
Gating Parameter HIST.GATEPARAM Yes Optional gating parameter to define
conditions under which data for this
parameter should be collected.
Gate State HIST.GATEPARAM Yes Defines gate state for configured
gating parameter.
Create New or Edit Existing N/A Launch the Server scripting
Server Scripts (Button) configuration utility.

109
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.13 FIM4/FIM8 Server Displays tab parameters

The Server Displays tab is common to all configuration forms for tagged blocks in Control Builder. The
following table summarizes the parameter data you can monitor and configure on this tab of the configuration
form for the selected FIM4/FIM8 block.

Attention
The configuration settings you make for Server Load Options on the System Preferences dialog determines whether
or not the data entered on the Server Displays tab is loaded to the Experion server. See the Control Building User's
Guide for information about setting system preferences.

Plain Text Parameter Name User Configurable Notes

Point Detail Display SCANPNTDTL Yes By default, a Display template is
already entered into Point Detail
Display box (for example,
sysDtlFTEB.dsp). This template can
be used for creating your own display
or it can be used as is, provided that
your function block name matches
name built into detail display that is
supplied as a template.
Group Detail Display SCANGRPDTL Yes By default, a Display template is
already entered into the Group Detail
Display box (for example,
sysGrpFTEB.dsp). This template can
be used for creating your own display
or it can be used as is, provided that
your function block name matches
name built into detail display that is
supplied as a template
Associated Display SCANASSOCDSP Yes Name of the Server display to be
associated with this function block.
Trends
Number of Trends TREND.NUMPARAMS Yes Defines the number of trend
parameters to be included in the
Trends Configuration table.
Trend # Yes Defines Trend number to be
associated with this trend parameter
Pen Yes Defines color of pen that will be used
to trace assigned parameter on Station
Trend display.
Trend Parameter Yes Valid parameter name for a parameter
associated with given point that is
configured for history collection.
Description No Provides a brief description of the
entered parameter.
Groups
Number of Groups GROUP.NUMPARAMS Yes Defines the number of group
parameters to be included in Groups
Configuration table.
Group # GROUP.NUMBER Yes Defines Group number to be
associated with this group parameter.

110 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

Plain Text Parameter Name User Configurable Notes

Pos # GROUP.POSITION Yes Defines number of position
configured parameter will occupy in
the Station Group display.
Group Parameter GROUP.PARAM Yes Valid parameter name for a parameter
associated with the given point that is
configured in the system.
Description No Provides a brief description of the
entered parameter.

111
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.14 FIM4/FIM8 Control Confirmation tab parameters

The Control Confirmation tab is common to all configuration forms for tagged blocks in Control Builder. If
you have an optional Electronic Signature license, you can configure electronic signature information for the
tagged block through this tab on the block's configuration form in Control Builder. Please refer to the online
help and the Server and Client Configuration Guide for information about the data on this tab.
The Electronic Signature function aligns with the identical Electronic Signatures function that is initiated
through Quick Builder and Station for Server points. When this block is loaded to a controller, its control
confirmation configuration (electronic signatures) is also loaded to the Server. This means you can view the
control confirmation configuration for this tagged object in Station and make changes to it. If you make changes
through Station, you must initiate an Upload or Upload with Contents function through the Controller menu
in Control Builder for the object in the Monitoring tab to synchronize changes in the Engineering Repository
Database (ERDB).

112 www.honeywell.com
 7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

7.15 FIM4/FIM8 Identification tab parameters

The Identification tab is common to all configuration forms for tagged blocks in Control Builder. The
following table summarizes the parameter data you can monitor and configure on this tab of the configuration
form for the selected FIM4/FIM8 block.

Plain Text Parameter Name User Configurable Notes

Name NAME Yes Unique block name consisting of up
to 16 characters to identify the block.
At least one character in the name
must be a letter (A-Z).
Description DESC Yes Descriptive text appears on detail and
group displays to uniquely describe
this particular function block
Block Comment 1 BLCKCOMMENT1 Yes Comment to be associated with this
block consisting of up to 40
characters.
Block Comment 2 BLCKCOMMENT2 Yes Comment to be associated with this
block consisting of up to 40
characters.
Block Comment 3 BLCKCOMMENT3 Yes Comment to be associated with this
block consisting of up to 40
characters.
Block Comment 4 BLCKCOMMENT4 Yes Comment to be associated with this
block consisting of up to 40
characters.
Library No Identifies Control Builder Library that
is source of template.
System Template No Identifies System Template that is
source for this block.
Base Template No Identifies Base Template that is used
for this block.
Created By CREATEDBY No Identifies user who created block, if
operator security is implemented.
Otherwise, may just show Default
login.
Date Created DATECREATED No Shows date and time template was
created. If this block is in Version
Control System, shows date and time
initial version of template was
created.
Last Modified By MODIFIEDBY No Identifies user who made last
modifications to block, if operator
security is implemented. Otherwise,
may just show default login. If this
block is in Version Control System,
modifications apply to last version of
block.
Date Last Modified VERSIONDATE No Shows date and time last modification
was made to block's configuration. If
this block is in Version Control
System, modification date and time
applies to last version of block.

113
7 SERIES C FIM4/FIM8 CONFIGURATION FORM REFERENCE

114 www.honeywell.com
8 Block instantiation support

In addition to the permanent or fixed function blocks that manufacturer's define for their Foundation Fieldbus
(FF) devices, they can define optional instantiable function blocks. This gives users the ability to instantiate
(create) additional function blocks within the Function Block Application Process for the given Fieldbus device.
The Fieldbus Foundation refers to this function as Block Instantiation and they include it in their Host
Interoperability Support Test (HIST).
Please refer to the Fieldbus Technology Overview section for more information about Standard Function Blocks
in general.
This section includes the following topics on information related to block instantiation support in Control
Builder.

Related topics
“Control Builder supports block instantiation” on page 116
“Instantiable block implementation considerations” on page 117

115
8 BLOCK INSTANTIATION SUPPORT

8.1 Control Builder supports block instantiation

Attention
The Type function in Control Builder only supports Block Instantiation in Fieldbus devices with single Capability
Levels. It does not support Fieldbus devices with multiple Capability Levels.

The Type function in Control Builder supports the functions associated with instantiable blocks in Fieldbus
devices with single capability levels. It lets you build block types for devices that support block instantiation
that include both the fixed function blocks and the instantiable function blocks. This means you can view the
instantiable blocks as part of the device's block hierarchy in the Library tab of Control Builder. The icon for an
instantiable function block has a slash across it and a letter I_ tag prefix as illustrated below, so you can easily
distinguish it from a fixed function block

Figure 13: Typical icon for Instantiable block in Fieldbus device.

Attention
A manufacturer may choose to define Transducer blocks as instantiable instead of fixed. In this case, be sure you
instantiate a Transducer block for each physical sensor that is to be used in the device. A Transducer block usually
corresponds to a physical sensor in the vendor's device.

116 www.honeywell.com
 8 BLOCK INSTANTIATION SUPPORT

8.2 Instantiable block implementation considerations

The following topics review considerations that are unique to implementing control strategies that include
Fieldbus devices with optional instantiated blocks. Please use these considerations to supplement the
appropriate procedures in other parts of this document that are tailored to Fieldbus devices with only fixed
function blocks including resource and transducer blocks.

Attention
When you perform upload/update to Project for FF block instantiable parameters, the parameters will not be updated
to the Project view.

Related topics
“Adding instantiable block to device in Project tab” on page 117
“Checking instantiated block configuration in Project tab” on page 118
“Making optional instantiated block resource usage check” on page 119
“Adding instantiated block to CM” on page 120
“Loading Project device to physical device” on page 121
“Deleting (de-instantiate) instantiated block from Project tab” on page 121
“Deleting (de-instantiate) instantiated block from physical device” on page 122
“Replacing failed device that includes instantiable blocks with like device” on page 122

8.2.1 Adding instantiable block to device in Project tab

Following are the considerations for adding instantiable block to device in Project tab
• Devices created in Project tab automatically include only their fixed function blocks, transducer blocks, and
resource blocks. If the device block type includes instantiable blocks, you must add the instantiable block
from the block type in the Library tab to the device icon in the Project tab to instantiate (create) it in the
device in Project.
• Default name of instantiated block may be appended with a letter. For example, a block with default name
I_AI becomes I_AIA.
• Device does not have to be connected to the link to instantiate a block.
• An error message is generated, if device cannot support an additional block.

Prerequisites
• You have logged onto Control Builder with sufficient security privileges to make changes in control
strategies.
• You have created a device type that includes instantiable blocks.

To add instantiable block to device in Project tab

1 See Adding a Fieldbus Device to Project for reference.
2 Open corresponding manufacturer's device hierarchy in the Library tab.
3 Drag the instantiable block onto the applicable device icon in the Project tab.
4 Key in desired name for the block or accept the default in the open Name New Function Block(s) dialog.
5 Click Finish to close the dialog and add the block to the device hierarchy in Project, as shown in the
following illustration.

117
8 BLOCK INSTANTIATION SUPPORT

Figure 14: Instantiated block added to device in Project tab.

8.2.2 Checking instantiated block configuration in Project tab

Following are the considerations for checking instantiated block configuration in Project tab
• The Instantiation tab only appears if the device supports Block Instantiation.
• See “Checking device configuration” on page 80for reference.

Prerequisites
You have completed the previous procedure.

To check instantiated block configuration in Project tab

1 In the Project tab, right-click applicable device instantiable block and select Block Properties from list to
open the form.
2 Click Block Instantiation tab.
3 Check Block Template Type column for list of instantiated blocks in device.
4 Check Block Tag column to view assigned tag to see if block is used in a Control Module or not as shown in
the following illustration.
5 Click OK to close the form.

118 www.honeywell.com
 8 BLOCK INSTANTIATION SUPPORT

Figure 15: Block Instantiation tab for instantiable block included with device in Project tab.

8.2.3 Making optional instantiated block resource usage check

Following are the considerations for making optional instantiated block resource usage check
• Some vendors provide resource information as an option. You can use this information to determine if the
configured block contents will fit within the available resources of the device.
• A resource represents a finite entity used by a device such as Central Processing Unit (CPU) or Memory.

To make optional instantiated block resource usage check

1 In the Project tab, right-click applicable device instantiable block and select Block Properties from list to
open the form.
2 Click Block Instantiation tab.
3 Check Resource # column for the amount of resource used by a particular block. The # (1, 2, …) columns
can vary depending on vendor and function block type.
4 In Resource Statistics grid, check Limit and Used columns to view resource allocations against assigned
limits, as shown in the following illustration.
5 Click OK to close the form

119
8 BLOCK INSTANTIATION SUPPORT

Figure 16: Block Instantiation tab with optional resource information.

8.2.4 Adding instantiated block to CM

Following are the considerations for adding instantiated block to CM.
• You add instantiated blocks to a Control Module the same way you do fixed blocks. They also are
configured in the same way and have the same graphical appearance as shown in the following figure.

Figure 17: Typical graphical representation of instantiated block in Control Builder.

• See the Control Building User's Guide for reference.

120 www.honeywell.com
 8 BLOCK INSTANTIATION SUPPORT

To add instantiated block to CM

1 In Project tab, double-click the icon for the Control Module that is to contain a Fieldbus block in its strategy
to open the CM in the control chart drawing area.
2 In Project tab, click the plus sign for the FIM4/FIM8, the FFLINK, and the contained device to expand
the directories down to the device block level.
3 Drag the applicable instantiated block to the open CM.
4 Double-click the instantiated block to open its configuration form and configure the block, as desired.
5 Click the close button on the CM and click Yes to save the changes and close the CM.

CAUTION
A physical device may go offline while its instantiable blocks are being instantiated through a device load.

8.2.5 Loading Project device to physical device

Following are the considerations for loading Project device to physical device.
• Block instantiation in a physical device only occurs during a load.
• Be sure you load a device from Project before you load a Control Module that contains instantiable blocks.
If you load a Control Module that contains instantiable block(s) before the associated device in Project is
loaded and its blocks instantiated, the Control Module load will fail.
• The existing load order, FIM4/FIM8/FFLink load, and device match functions also apply for devices with
instantiable blocks.
• Device load from Project synchronizes the contents of the Project device with the physical device and
instantiates applicable instantiable blocks in the physical device.
• You must load the Control Module(s) containing fixed and/or instantiated blocks associated with the device
for the fixed and instantiated blocks to appear in the device hierarchy in Monitoring tab.
• After loading a device from Project or Monitoring tab, the physical device function block contents matches
that of the corresponding Project or Monitoring device. This means necessary blocks will be instantiated and
unnecessary Blocks will be removed or de-instantiated.

To load Project device to physical device

1 See “Load order guidelines” on page 128 for reference.
2 See “Loading a Series C FIM4/FIM8 and its links” on page 134for reference.
3 See “Matching uncommissioned device to Project device or vice versa” on page 135 for reference.
4 Right-click device icon and select Load from list.
5 Review information on Load dialog for load details and any warning messages identifying pre-load
considerations.
6 Click OK to initiate the load and monitor Load Progress dialog for load related activities.
7 Upon successful device load, open device icon in Monitoring tab to view block hierarchy. Only transducer
and resource blocks appear in the device hierarchy after an initial load.
8 Right-click device icon and select Upload from the list. Click Continue to load device data into the Monitor
database.

8.2.6 Deleting (de-instantiate) instantiated block from Project tab

Prerequisites
• You cannot delete an Instantiable block from Project, if it is loaded and viewable in the Monitoring tab.
See the next section to delete an instantiated block for a physical device.

121
8 BLOCK INSTANTIATION SUPPORT

• You cannot delete an instantiated block that is contained in a Control Module unless you un-assign or delete
the block from the CM first.

To delete (de-instantiate) instantiated block from Project tab

1 In Project tab, click the + plus sign for the FIM4/FIM8, the FFLINK, and the contained device to expand
the directories down to the device block level.
2 Right-click applicable instantiated block icon in the hierarchy and select Delete from the list.
3 Click Continue to initiate action and track progress in Delete dialog.
4 Upon successful deletion the instantiated block icon is removed form the device hierarchy.

8.2.7 Deleting (de-instantiate) instantiated block from physical device

Following are the considerations for deleting (de-instantiate) instantiated block from physical device
• Deleting a block from Monitoring tab, does not de-instantiate a block in a device. Only a load of a device
will achieve this
• You must re-load Project device to re-synchronize contents with physical device after any control strategy
changes or physical device maintenance that may alter contents in either device.

Prerequisites
You cannot delete an instantiated block directly from a physical device.

To delete (de-instantiate) instantiated block from physical device

1 In the Monitoring tab, locate the CM that contains the instantiated block that is to be deleted and delete the
CM.
2 In the Project tab, unassign or delete the instantiated block from the CM that was deleted in the Monitoring
tab, and then delete the block from the device in Project, as noted in the previous procedure. Make any
control strategy changes, as required.
3 Load device from Project to re-synchronize contents with physical device.
4 Load device from Project to re-synchronize contents with physical device.
5 Load reconfigured CM.
6 Right-click device icon and select Upload from the list. Click Continue to load device data into the
Monitoring database.

8.2.8 Replacing failed device that includes instantiable blocks with like device
Following are the considerations for Replacing failed device that includes instantiable blocks with like device
• A device replacement can cause changes in a device's block layout, since the Object Dictionary (OD) index
for an instantiated block can change.
• If connections to instantiable blocks of the replaced field device are through SCM expressions, such an
SCM will not be automatically shown as a part of the Load List under the device in the Load Dialog. This
means that the SCM will not be automatically loaded. In this case, you must inactivate the SCM and reload
it as a separate procedure.
• If a Control Module (CM) or a Sequential Control Module (SCM) has connections to contained Fieldbus
parameters, they will appear as a part of the Load List under the device in the Load Dialog and will be
automatically loaded. See the Load Dialog example in the following illustration. However, special
consideration must be given to inactive Sequential Control Modules.

122 www.honeywell.com
 8 BLOCK INSTANTIATION SUPPORT

Prerequisites
• See “Replacing a failed device with a like device having the same model name and device revision” on
page 226 for general replacement procedure.

Figure 18: Typical Load Dialog for Fieldbus device.

123
8 BLOCK INSTANTIATION SUPPORT

124 www.honeywell.com
9 Loading FIM4/FIM8 components online

The Experion system provides the ability to build control strategies offline, without being connected to the
actual field components. The process of transferring the Control Strategy to the 'live' working components in the
field is called the load operation. This section includes the following topics on information and tasks associated
with loading FIM4/FIM8 components through Control Builder.

Topic
“About load operations” on page 126
“About load dialog” on page 127
“Load order guidelines” on page 128
“General load considerations” on page 130
“About fieldbus device states” on page 131
“Fieldbus device matching rules” on page 132
“Identifying load interactions for fieldbus-related operations” on page 133
“Loading a Series C FIM4/FIM8 and its links” on page 134
“Matching uncommissioned device to Project device or vice versa” on page 135
“Using optional safe handling of new devices” on page 137

Related topics
“About load operations” on page 126
“About load dialog” on page 127
“Load order guidelines” on page 128
“General load considerations” on page 130
“About fieldbus device states” on page 131
“Fieldbus device matching rules” on page 132
“Identifying load interactions for fieldbus-related operations” on page 133
“Loading a Series C FIM4/FIM8 and its links” on page 134
“Matching uncommissioned device to Project device or vice versa” on page 135
“Using optional safe handling of new devices” on page 137
“Loading FFLink contents or fieldbus device” on page 138

125
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.1 About load operations

The load operation functionally copies configuration data from the control strategy that is stored in the
Engineering Repository Database (ERDB) to the assigned field component in the system architecture. The load
operation has been expanded to include Fieldbus components. It indirectly assures that the planned system
matches the actual one. The communication addresses and physical location assignments specified for
components through Control Builder configuration must match the actual addresses and locations of
components in the system. The following illustration shows a simplified graphical representation of what
happens during a load operation.

Figure 19: Overview of load operations used to initiate FIM4 components online.

126 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.2 About load dialog

The following figure shows a sample Load Dialog invoked for a load with contents operation for a Series C
FIM. It provides a brief description of the dialog features for quick reference.

CAUTION
The load operation is still an offline function. The Load Dialog provides the ability to automatically inactivate a
component during a load and then return the component to its active state. Do not use this automatic inactivate/
activate function, if your process cannot tolerate the load disruption and consequent delay in activation. In this
case, you must manually toggle the component state through the Monitoring tab in Control Builder.

Figure 20: Load Dialog provides more load choices.

127
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.3 Load order guidelines

Load control strategy components from the Project tab in the following order to avoid possible load interaction
generated error messages.

Order Component Typical Loaded Icon in Monitoring Tab

1 C300/CEEC300*

2 FIM4 /FFLINK

3 FIM8 /FFLINK

4 Check for Uncommissioned Fieldbus devices and initiate

match function, as applicable

5 Fieldbus Device

6 IOM*

7 CM or SCM*

128 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

*Please refer to the Control Building User's Guide for more information about loading these components.

129
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.4 General load considerations

The following are some general load considerations to keep in mind, when you are loading Fieldbus
components. In most cases, the Load Dialog box will quickly guide you through the load operations and will
alert you to potential load problems.

If you are loading . . . Then, consider this . . .

A FIM4/FIM8. Be sure ALIV does not appear in the LED display on the front of the FIM4/
FIM8. If it does, you must first load the FIM4/FIM8 personality firmware
using the Series C hardware firmware tool (Ctool) utility supplied with
Experion Engineering Tools.
A CM that contains only Fieldbus function We recommend that CMs containing only Fieldbus function blocks be
blocks. assigned and loaded to the appropriate FIM4/FIM8 LINK. They will only
take up unnecessary memory and execution time in the CEE. .
A CM that contains both Experion and Be sure CMs that contain Experion function blocks are assigned and loaded
Fieldbus function blocks. to a CEE. Control Builder enforces this.
A Fieldbus device. Be sure the device configuration in Project tab has the proper PD_TAG
specified. While you can load a device to the FFLink from Project, you
cannot load and commission a device until it is connected to the link and its
PD_TAG and address agree with those specified in Project. Please see the
next two sections Fieldbus device states and Fieldbus device matching rules
for more information.

130 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.5 About fieldbus device states

A Fieldbus device is unaware of the steps being executed to configure a network. Its System Management
Kernel (SMK) does sense the completeness of its configuration to determine what services it can provide. The
following table shows the three major states a SMK in a field device must go through and the associated
services for each state before a device can fully function on the network.

SMK State System Management Services

Unitialized • SM_IDENTIFY
• SET_PD_TAG (Clear = False)
Initialized • SM_IDENTIFY
• SET_ADDRESS
• SET_PD_TAG (Clear = True)
Operational • SM_IDENTIFY
• CLEAR_ADDRES
• FIND_TAG_QUERY
• FIND_TAG_REPLY
• FB_START
• SMIB_Acess

In the uninitialized state, a Fieldbus device has neither a physical device tag nor a node address assigned by a
master configuration device. The only access to the device is through system management, which permits
identifying the device and configuring the device with a physical device tag.
In the initialized state, a Fieldbus device has a valid physical device tag, but no node address has been assigned.
The device is ready to be attached to the network at a default system management node address. Only system
management services for assigning a node address, clearing the physical device tag, and identifying the device
are available.
In the operational state, a Fieldbus device has both a physical device tag and an assigned node address. Its
application layer protocols are started to allow applications to communicate across the network. Additional
network management configuration and application configuration may be needed for the device to become
operational.

131
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.6 Fieldbus device matching rules

The Series C FIM initiates the following matching rules depending upon whether or not the device
identification (DEV_ID) is specified, when a device is loaded from Control Builder.

If the Device ID is . . . And, the Device State Then, the matching rule is . . .
Is . . .
Specified. Uninitialized The device ID (DEV_ID) must match. If the desired physical device tag
(PD_TAG) and node address (ADDR) are available, FIM4/FIM8 will
assign them to the device.
Initialized The device ID (DEV_ID) and physical device tag (PD_TAG) must
match. If the desired address is not in use, FIM4/FIM8 will assign it to
the device.
Operational The device ID (DEV_ID), physical device tag (PD_TAG), and node
address (ADDR) must match those specified through configuration in
Control Builder. Any mismatch results in an error.
Not specified. Initialized The physical device tag (PD_TAG) must match. If the desired node
address (ADDR) is not in use, FIM4/FIM8 will assign it to the device.
Operational The physical device tag (PD_TAG) and node address (ADDR) must
match those specified through Control Builder. Any mismatch results in
an error.

132 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.7 Identifying load interactions for fieldbus-related operations

The following table provides a matrix of load interactions for given Fieldbus related operations.

Attention
If you make on-line changes to parameter values in Fieldbus devices, the changed values are not written to the
Monitoring or Project copy of the control strategy. You must initiate an Upload function to write the new values to
Monitoring followed by an Update to Project function to write the Monitoring values to the Project copy.

Operation Build Link Load Load LM Load Used State Required for
Schedules Schedule into Schedules into Function Operation
FIM4/FIM8s Blocks
LM-Capable
Link
Devices
Load Device No No This device only, Yes Blocks in device = OOS,
if LM-capable
or Device = OOS,
Replace Device FFLink = Active
Delete Device from No No No No Blocks in device = OOS,
Loaded
Device = OOS,
FFLink=Active
Load FFLink with Yes Yes All LM-capable Yes Blocks in related CMs =
Contents OOS,
Device = OOS,
FFLink = N/A
Load FFLink (without No Yes No No FFLink = N/A
contents)
Load CM (from Yes Yes All LM-capable Yes Blocks in CM = OOS
Project)
CM = Inactive,
FFLink = Active,
Device = N/A
Load CM (from No No No Yes Blocks in CM = OOS
Monitor)
CM=Inactive,
FFLink=Active,
Device=N/A
Delete CM from Yes Yes All LM-capable No Blocks in CM = OOS
Loaded
CM=Inactive,
FFLink=Active,
Device=N/A

133
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.8 Loading a Series C FIM4/FIM8 and its links

Following are the considerations for loading a Series C FIM4/FIM8 and its links
• If ALIV appears in the Series C FIM's 4-character, alphanumeric display, you must load the Series C FIM's
personality firmware before proceeding.
• The associated Series C FIM Links are included with a FIM4/FIM8 load even if the selected action is Load
instead of Load with Contents. We suggest just loading the FIM4/FIM8 without all of its contents first to
be sure communications paths are working.

Prerequisites
All Series C FIM components are installed and capable of communicating with the system.

To initiate FIM4/FIM8 load

1 Click the FIM4/FIM8 block icon in the Project tab. On the Controller menu, click Load to call up the Load
dialog.
2 Be sure a check mark appears in the check box for the FIM4/FIM8 listed in the Load Column? Click OK to
initiate the load.
3 Track load status in the Load Progress dialog box that appears.
4 When load is completed, click the Monitoring tab to open it.
5 Confirm that the FIM4/FIM8 icon now appears in the Monitoring tab. Click + plus sign for FIM4/FIM8
icon to open the directory and expose the FFLINK icons.

134 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.9 Matching uncommissioned device to Project device or vice versa

Following are the considerations for matching uncommissioned device to Project device or vice versa
• It is best to match devices before you download the Fieldbus device from Project to the FFLink.
• On the H1 network, if you install a device with an address below 20 (hexadecimal 14), the FIM4/FIM8 will
clear the device's address. The device returns to the link at a temporary address and may be reassigned as
needed.
• If you install a Link Master class device on the H1 network, the FIM4/FIM8 performs the following actions
to protect the network from an unconfigured or incorrectly configured device disturbing or becoming the
Link Master of the segment.
– Clears the link schedule,
– Clears the primary link master flag variable,
– Sets the configured link settings,
– Sets the device class to basic, and
– Restarts the device.
• Refer to Using Optional Safe Handling of New Devices section for more information about adding an
uncommisioned to a loaded Fieldbus link with the optional safe handling function enabled.
• If the device template and capability level of an uncommissioned device and a Project device are same, then
you can match the device.

Prerequisites
• You have installed H1 link segments to provide proper power and conditioning for Fieldbus devices.
• You have completed the previous procedure to load the FIM4/FIM8 and its links.

To match an uncommissioned device to a Project device or vice versa

1 On the Monitoring view, confirm that the applicable FFLink icon is active (green).
• If the FFLink is active (green icon), go to Step 4.
• If the FFLink is inactive (blue icon), go to Step 2.
2 Click the applicable FFLink icon and then click Toggle State icon to toggle the state.
The Change State dialog box appears.
3 Click Yes to initiate FFLink startup.
The FFLink appears as active (green icon).
4 On the Project view, click the FIM4/FIM8 block and the FFLink that has uncommissioned device template.
5 On the Field Devices menu, click Device Match.
The FFLink Parameters form appears with the Device Match Dialog tab selected.
6 Check for the block type matches between listed Uncommissioned Devices and Project Devices in the
Template column and the Capability Level column.
Note:
• If the Template column and the Capability Level column match, then Match from Uncommissioned
Device to Project Device and Match from Project Device to Uncommissioned Device are enabled.
• In the Capability Level column, the capability level of the device is displayed based on the Capability
Level parameter in the DD file.

135
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

Attention
• If the Capability Level parameter is not available at the device level, it displays as zero. Therefore, you have to
manually enter the capability level of the device.
– Ensure to type the correct capability level of the device. If the value is incorrect, then commissioning
errors appear and template or device replacement must be performed to correct the error.
• If you want to change the tag name or address for the devices that are listed under Uncommissioned Devices
or Project Devices, then perform the following:
1. In the Tag or Address column, double-click and type the required values.
2. Press ENTER.
A confirmation message appears before initiating the change in the tag and address in the
Uncommissioned Device to match the Project Device..
3. Click Continue.
• If an uncommissioned device is previously configured through a hand-held communicator or third-party
configuration to contain correct tag and address data, click Match from Uncommissioned Device to Project
Device to preserve the Uncommissioned Device information and change the Project Device information.
• If an uncommissioned device contains factory default data, then click Match from Project Device to
Uncommissioned Device to retain the Project Device information and change the Uncommissioned Device
information.

7 Select the devices to Match from Uncommissioned Device to Project Device or to Match from Project
Device to Uncommissioned Device.

136 www.honeywell.com
 9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.10 Using optional safe handling of new devices

Related topics
“About safe handling option” on page 137
“Enabling and disabling safe handling” on page 137
“Safe handling and previously commissioned devices” on page 137
“Removing power during a safe handling operation” on page 137

9.10.1 About safe handling option

If you enable the safe handling option for the Series C FIM through its configuration form in Control Builder,
the following actions are automatically initiated when you add a new device to a loaded Fieldbus link.
• Clears any existing VCRs configured in the device.
• Clears any existing link schedule.
• Clears the primary link master flag on the device.
• Sets the link settings in the device to the current link settings of the segment.
If required, changes the device to a basic one and restarts the device.

9.10.2 Enabling and disabling safe handling

You enable and disable the safe handling option through the Safe Handling of New Devices Enabled check
box on the Main tab of the FIM4/FIM8 Block's configuration form in Control Builder. The default is selected or
checked check box, which means safe handling is enabled.

9.10.3 Safe handling and previously commissioned devices

The safe handling option does not apply when removing and adding a previously commissioned device to the
Fieldbus link. However, if you remove a commissioned device from one link and add it to another link, the
device is treated as an uncommissioned device and the safe handling option applies. If this same device is later
moved back to its original link, it will appear as an uncommissioned device and will require a reload.

9.10.4 Removing power during a safe handling operation

The safe handling operation can take up to 30 seconds to complete after adding a new device to a link. If you
remove a device while the safe handling operation is in progress, it may have its configuration partially cleared.
Moving a commissioned device to another link and then back to its original link after only 1 to 20 seconds has
expired, may leave the device in a half safe handled state. If the FBAP VCR was cleared, the FIM4/FIM8 and
Control Builder may not be able to talk to the device. If this occurs, Fieldbus blocks will appear gray on the
Monitoring tab. In this case, you will need to delete and reload the device or remove the device from the link
and put it back on another link for at least 30 seconds to allow the safe handling operation to complete.
To avoid partial safe device handling, do not move previously commissioned devices to other links in the
system too quickly.

137
9 LOADING FIM4/FIM8 COMPONENTS ONLINE

9.11 Loading FFLink contents or fieldbus device

Following are the considerations for Loading FFLink contents or fieldbus device
• It is a good idea to load the Fieldbus device before you load the Control Modules containing its associated
function blocks to the CEE or FIM4/FIM8. If you load the Control Module first, you may get an error
message indicating that the parent block is not available.
• If you just want to load a given Fieldbus device, click the device icon and click Controller > Load. We
suggest using FFLINK/Load With Contents so you can load more than one device at a time.
• A Partial Load selection means that the contained or internal block parameters will not be loaded to the
device, which reduces the overall load time. It is generally not necessary to load these types of parameters,
since no connections are made to them.
• If errors are detected during the load, they will be listed and you will be prompted to select whether or not
you want to continue the load with errors. It is a good idea to note the errors and abort the load (close), so
you can go back and correct the errors before completing the load.
• The device's resource and transducer blocks are dedicated to the device and loaded with the device, and can
be viewed in the device directory in the Monitoring tab. The device's other function blocks will not appear
in its directory until the Control Module containing them is loaded to the CEE or FIM4/FIM8, as applicable.

Prerequisites
You have completed the previous procedures to load the FIM4/FIM8 and match Project and Uncommissioned
devices.

CAUTION
If the load generates errors identifying sub schedule problems, you must reconfigure the Link Master capable
device to become a Basic one through Control Builder, and restart the device to initiate the change. Otherwise, if
the Series C FIM fails, the potential for a 'no schedule' condition exists. Since the schedule is cleared from the
Link Master capable device upon the detection of sub schedule load errors, it cannot function as the backup LAS
without a schedule.
Please see the “Checking/changing fieldbus device functional class” on page 171 section for details on
reconfiguring a device as a Basic type.

To initiate a device load

1 In the Project tab, click the desired FFLINK icon. In the Controller menu, click Load With Contents to
open the Load Dialog.
2 Confirm that checks appear in the FFLINK and Device check boxes listed in the Load? column. If you do
not want to load a given device, just click it to remove the check from its check box.
3 Accept the default Partial Load check box selections for the Resource and Transducer blocks for a device.
4 To change the Post Load State for selected components, click the appropriate Post Load State row and
select another state from the list.
5 Click the check boxes to inactivate the Fieldbus devices automatically for the load and to return Fieldbus
devices automatically to post load state after the load.
6 Click OK to Initiate the Load and open Load Dialog to show load progress.
7 Once the load is complete, click the Monitoring tab to open it.
8 Confirm that blocks now appear in given device hierarchy.
9 Repeat Steps 1 to 8 to load another FFLink or device, as required.

138 www.honeywell.com
10 Fieldbus device commissioning

This section outlines a typical process to follow to commission a Fieldbus loop in an Experion system. This
section does not provide detailed procedures for each stage in the process. Please reference appropriate sections
in this document or applicable vendor documentation for detailed information, if required.
The following table lists the topics included in this section. If you are viewing this information online, just click
the topic title to jump to the information location.

Topic
“Getting started” on page 140
“Connecting devices” on page 143
“Checking device” on page 145
“Checking control strategy” on page 146
“Flowchart summary” on page 147

Related topics
“Getting started” on page 140
“Connecting devices” on page 143
“Checking device” on page 145
“Checking control strategy” on page 146
“Flowchart summary” on page 147

139
10 FIELDBUS DEVICE COMMISSIONING

10.1 Getting started

10.1.1 Read this first

The Series C Fieldbus Interface Module (FIM4/FIM8) sets many parameters within a Fieldbus device during its
initial setup and commissioning in an Experion system. While you can change some parameters, such as
calibration ones, when the device is being operated on a workbench or at a location apart from the system, you
must not change certain other parameters. The following table outlines the functions you must consider before
commissioning a device.

For This Function. . . Consider This . . .

Link Settings These parameters can affect whether or not a device can communicate with other
devices on the link, or whether it communicates efficiently and can recover
properly from errors. They must not be changed, by another host device.
If the Experion system notices that these parameters have been changed after a
device has been off the network, the Series C FIM takes the following action:
1. Changes the parameters back.
2. De-commission the device (assuming other parameters have been changed
also).
3. Change a Link-Master-capable device to a Basic device.
To recover, the (now uncommissioned) device must be changed back to a Link-
Master device, if desired, and re-loaded from the Project or Monitoring tab in
Control Builder.
Link Schedule The Link Schedule controls the publication schedule, if no Series C FIM is
available on the link. If the device was moved from another link or to another host
and was loaded with a different schedule, the link schedule is not the current
schedule version number for this link. In this case, the Series C FIM will take the
following action.
1. De-commission the device.
2. Change a Link Master capable device to a Basic device.
To recover, the (now uncommissioned) device must be changed back to a Link-
Master device, if desired, and re-loaded from the Project or Monitoring tab in
Control Builder.
Virtual Communication Relationships The Virtual Communication Relationships (VCRs) are communication
(VCRs) connections that are established for a given link. They should not be re-configured
on another link or by another Host. Otherwise, they will very likely not be
configured correctly and could interfere with communications when the device is
restored to the desired link. When the Series C FIM first encounters a new
uncommissioned device, it will clear its VCRs.
Link-Master Capable A Link-Master-Capable device can take over control of a link. When Series C
FIM first encounters a new uncommissioned device, it checks to see if it is
configured as a Link-Master capable device and re-configures it as a Basic device.
(When the device is commissioned, it can be changed back to Link-Master
capable, since it will be loaded with the correct backup link schedule.)

140 www.honeywell.com
 10 FIELDBUS DEVICE COMMISSIONING

For This Function. . . Consider This . . .

Binding of Fieldbus Devices to the The three most important identification parameters for a Fieldbus device are its:
Experion database
• Device_ID,
• PD_Tag, and
• Link Address.
The Device_ID is required by Fieldbus Foundation specifications to be device-
unique and unchangeable. But, if either the Physical Device Tag (PD_Tag) or the
Link Address is changed while the device is off the network, the device is de-
commissioned and will have to be re-commissioned when it is returned to the link.
If a device is removed from the link and another device is placed on the link at the
same address (second device will have different Device_ID and possibly different
PD_Tag), the original device will appear de-commissioned upon return to the link.
To recover, the (now uncommissioned) device must be re-commissioned or
matched again to its device object and then re-loaded.
Number of Fieldbus Device Sustained stores are intended for parameters such as FF_VAL, RCAS_IN,
parameters to receive periodic TRK_IN_D, and TRK_VAL. Sustained stores should not be used on static
(sustained) stores parameters or parameters stored in non-volatile memory on a device, such as SP.
Performing sustained stores to static or non-volatile parameters may lead to a
shortened lifetime for the EPROM or flash memory in a device. Each Fieldbus
device will behave differently, so it is best to consult the device manual for
information on sustained store limitations.

10.1.2 Initial checks and operations

Stage Function Completed

1 Check and test all physical wire connections and verify correct voltage on H1 segment.
References:
“Selecting and calculating Fieldbus wiring requirements” on page 27
2 Load FIM4/FIM8 block only
References:
“Adding FIM4/FIM8 block to project” on page 64
“Loading a Series C FIM4/FIM8 and its links” on page 134
3 Was FIM4/FIM8 download successful?
NO > Go to Stage 4
YES > Go to Stage 7
4 Is IOTA and Series C FIM powered?
NO > Go to Stage 5
YES > Go to Stage 6
5 Be sure required voltage is present at the power supply and it is turned On.
Replace power supply, if required.
Return to Stage 2.
6 Verify network connections.
Replace Series C FIM, if required.
Return to Stage 2.
7 Measure and establish H1 segment baseline with Fluke Scopemeter and Relcom FTB-3 or
equivalent equipment.

141
10 FIELDBUS DEVICE COMMISSIONING

Stage Function Completed

Go to Stage 8 in the next section Connecting Devices.

142 www.honeywell.com
 10 FIELDBUS DEVICE COMMISSIONING

10.2 Connecting devices

Stage Function Completed

8 Connect the next device.
References:
“Fieldbus network wiring and installation references” on page 21
9 Does device appear on link?
NO > Go to Stage 10
YES > Go to Stage 23 in the next section Checking Devices.
10 Be sure cable is connected to proper segment terminals on IOTA.
References:

11 Connect Relcom Tester and/or Fluke Scopemeter to Link's cable.

12 Is voltage over 9 volts?
NO > Go to Stage 13
YES > Go to Stage 14
13 Test the power supply, check that terminators are Installed properly and check for short circuits.
Return to Stage 9
14 Does proper number of devices appear on tester?
NO > Go to Stage 16
YES > Go to Stage 15
15 Check that proper FFLink is downloaded and that device is connected to proper link.
References:
“Loading a Series C FIM4/FIM8 and its links” on page 134
Return to Stage 9
16 Are noise average and peak under 75 millivolts?
NO > Go to Stage 17
YES > Go to Stage 18
17 Check the integrity of all cable connections, cables and verify the design of the link.
Return to Stage 9
18 Is lowest signal level over 150 millivolts?
NO > Go to Stage 19
YES > Go to Stage 20
19 Insufficient power for device. Check power supply and link design.
Return to Stage 9
20 Is there an addressing issue?
NO > Go to Stage 21
YES > Go to Stage 22
21 Device should be present. Replace the device.
Return to Stage 9

143
10 FIELDBUS DEVICE COMMISSIONING

Stage Function Completed

22 Check if address is in unpolled range, check for too many devices with temporary address.
References:
“Tags, Addresses, and Live List Reference” on page 307
Return to Stage 9

144 www.honeywell.com
 10 FIELDBUS DEVICE COMMISSIONING

10.3 Checking device

Stage Function Completed

23 Does firmware - DD Revision match device revision?
NO > Go to Stage 24
Yes > Go to Stage 25
24 Upgrade firmware or import new DD file
References:
“Upgrading Series C FIM4/FIM8 firmware” on page 56
“Creating a fieldbus device type from vendor DD”
25 Match device.
References:
Matching Uncommissioned Device to Project Device or Vice Versa
26 Load (Partial Load) the new device from Project tab.
References:
“Using optional safe handling of new devices” on page 137
27 Measure and compare H1 segment baseline with Fluke Scopemeter and Relcom FTB-3 or
equivalent equipment.
28 Are measurements within specifications?
NO > Go to Stage 29
YES > Go to Stage 30
29 Identify source of noise or communication problems and repair or replace equipment as
required.
Return to Stage 27
30 Do you need to add more devices on this segment?
NO > Go to Stage 31 in the next section Checking Control Strategy.
YES > Return to Stage 8 in previous section Connecting Devices.

145
10 FIELDBUS DEVICE COMMISSIONING

10.4 Checking control strategy

Stage Function Completed

31 Is control strategy configured?
NO > Go to Stage 32
Yes > Go to Stage 33
32 Configure control strategy.
References:
“Series C FIM4/FIM8 configuration” on page 61
33 Load control strategy to device.
References:
About load operations
34 Are parameters correct?
NO > Go to Stage 35
YES > Go to Stage 36
35 Make required parameter changes on-line to device.
36 Upload device to project.
References:
Identifying Load Interactions for Fieldbus Related Operations

146 www.honeywell.com
 10 FIELDBUS DEVICE COMMISSIONING

10.5 Flowchart summary

The commissioning stages outlined above are summarized in the following flowchart.

147
10 FIELDBUS DEVICE COMMISSIONING

148 www.honeywell.com
11 Series C FIM4/FIM8 redundancy functionality

This section provides information about using a redundant Series C FIM pair. The following table lists the
topics included in this section. If you are viewing this information online, just click the topic title to jump to the
information location.

Topic
“Redundant Series C FIM4/FIM8 overview” on page 150
“Switchover and secondary readiness” on page 151
“Switchover behavior considerations” on page 152
“Failure conditions and switchover” on page 153
“Fieldbus network switchover considerations” on page 154
“Switchover versus fieldbus network activities” on page 155
“Switchover events” on page 156

Related topics
“Redundant Series C FIM4/FIM8 overview” on page 150
“Switchover and secondary readiness” on page 151
“Switchover behavior considerations” on page 152
“Failure conditions and switchover” on page 153
“Fieldbus network switchover considerations” on page 154
“Switchover versus fieldbus network activities” on page 155
“Switchover events” on page 156

149
11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.1 Redundant Series C FIM4/FIM8 overview

If you have a Series C FIM (FIM4/FIM8) redundant Input/Output Termination Assembly (IOTA), you can
implement redundant Series C FIM4/FIM8 operation through a redundant Series C FIM4/FIM8 pair. The
following figure shows a typical hardware configuration for a redundant Series C FIM4/FIM8 pair that includes
a C300 Controller. You do not need the C300 Controller to support Series C FIM redundancy.

Figure 21: Redundant Series C FIM Pair With Redundant C300 Controller.

This is considered a dual redundant system, which is characterized by the following two main redundancy
states.
• Primary - Refers to the Series C FIM executing the assigned control functions.
• Secondary (or Backup) - Refers to the Series C FIM in some state of readiness to assume the responsibilities
of the Primary.

150 www.honeywell.com
 11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.2 Switchover and secondary readiness

A switchover describes the process where a Secondary Series C FIM assumes the Primary state, and the
Primary Series C FIM assumes the appropriate Secondary state of readiness, depending upon what triggered the
switchover. A switchover can be triggered immediately upon the detection of a fault in the Primary or upon the
receipt of an operator command.
The ability of a Secondary Series C FIM to take over the assigned control functions of the Primary depends
upon which one of the following readiness states reflects its current state.

If Secondary Series C FIM State Is . . . Then, the Secondary Series C FIM . . .

Not synchronized Cannot assume the Primary state. This is a state of non-readiness.
Synchronizing Cannot assume the Primary State. In this state, the Secondary Series
C FIM is copying database information from the Primary.
Synchronized Can assume the Primary state upon switchover. In this state, the
database in the Secondary is aligned with the database in the Primary.
The Secondary closely tracks database changes to maintain its
synchronization with the database of the Primary. Otherwise, the
Secondary will revert to a Not Synchronized state.

151
11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.3 Switchover behavior considerations

The following table lists some display and control data behaviors in response to a Series C FIM4/FIM8
switchover action.

For This Series C FIM Related Function . . . The Related Switchover Behavior Is . . .
Fieldbus to Fieldbus Device Communication The 'on-the-wire' control is not affected by a switchover. The new
Primary FIM immediately takes over as a Link Master and resumes
execution of the link schedule.
Control Data for Fieldbus/Experion Control Control data is available immediately after switchover. This
Integration includes data for connections in the Fieldbus to C300 and in the C300
to Fieldbus directions. The FIM may substitute a last known good
value for publication to Fieldbus devices, while network connections
reform to C300 controllers. Substitute value functionality is bounded
to a maximum of five seconds to account for worse case timing.
Display Data Display data may not be available for several seconds during
switchover. Typically, five seconds is the time required to refresh a
display after switchover. Exact behavior of display data during
switchover will be different on a per-configuration and per-device
basis. After a FIM switchover, display clients such as Control Builder
and Station must reform connections to the new primary FIM. The
FIM then processes requests from reconnected clients. It populates
the FIM parameter cache by issuing read requests on the H1 network
for device parameter data. As the read requests complete and the FIM
parameter cache is filled, display traffic resumes. The time to recover
display data is affected by the following things:
• The bandwidth available on the H1 link for unscheduled traffic,
• The number of display requests received by the FIM,
• Use of views within the Fieldbus device, and
• Third-party Fieldbus device behavior, including time required to
reopen client/server VCRs.

152 www.honeywell.com
 11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.4 Failure conditions and switchover

The following table identifies failure conditions that result in a switchover and those that do not.

Attention
When any failure that results in a switchover occurs in a Secondary, the Secondary Series C FIM loses
synchronization.
In addition to the failure conditions, this event is reported as diagnostic notification:
• Loss of view of redundant partner on H1 network (applies to Series C FIM link).
• Loss of private path connection from Primary to Secondary (lonely event).

Failure Conditions That Result in a Switchover Failure Conditions That Do Not Result in a Switchover
Power to Primary Series C FIM fails. One or all H1 cables fail.
Both FTE links to Primary Series C FIM are lost. One or all H1 network conditioners fail.
Primary Series C FIM fails. The 24-Volt power supply for the H1 link fails.

153
11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.5 Fieldbus network switchover considerations

The Series C Fieldbus Interface Module (FIM4/FIM8) is a Link Master device running the link schedule,
performing network maintenance activities, publishing control data and subscribing to control data, listening to
alerts, and so on. All of these activities must be transferred from one module to another during switchover. The
redundant Series C FIM operation accounts for the following key considerations associated with initiating a H1
network switchover.

For this Series C FIM Redundancy Operation . . .

Switchover
Consideration . .
.
Bumpless Assures that Fieldbus devices do not:
Switchover
• Initiate a fault state,
• Remote shed, or
• Mode shed, during switchover.
The new Primary Series C FIM does not publish any data on the network until all switchover actions are
completed and it has good data from the Control Data Access (CDA) server.
Device Index Does not transition the Device Index for the Primary Series C FIM to the Secondary Series C FIM. The
number Device Index stays with the physical Series C FIM.
MAC Does not transition the MAC addresses for the FTE links on the Primary Series C FIM to the Secondary
Addresses Series C FIM. The MAC addresses stay with the physical Series C FIM.
IP Address Does swap IP addresses for Primary and Secondary Series C FIMs during switchover as follows.
• During initial synchronization, Primary and Secondary Series C FIMs exchange their IP addresses
over the private redundancy link. This is for verification purpose only, since the odd-even
convention allows both modules to determine their partner's address based on their own address.
• During switchover or swap, both Primary and Secondary Series C FIMs replace their current IP
address with their partner's IP address. This puts redundant pair into transient state in which peer
modules are temporarily unable to communicate with either one of them, since their address tables
are no longer valid due to the IP address swap.
After IP address swap, both Primary and Secondary Series C FIMs construct Address Resolution
Protocol (ARP) request packets with updated IP-to-Ethernet address mapping and broadcast them on the
network. Upon reception of ARP packets, peer nodes update their address tables.
The swapping of IP addresses is transparent to the higher-level protocols such as Transmission Control
Protocol (TCP) or User Datagram Protocol (UDP).
• TCP packets sent to either Primary or Secondary Series C FIM during switchover will be re-tried.
Once retry limit is exceeded, connection breaks and gets re-established by application based on
updated address information.
• UDP packets sent to either Primary or Secondary Series C FIM during switchover and before client
address table is updated will be lost.

154 www.honeywell.com
 11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.6 Switchover versus fieldbus network activities

The following table summarizes how given Fieldbus network activities behave during a switchover.

Attention
Depending upon the link communication load, number of devices, and type of parameter, fresh viewed data from field
devices may be delayed for up to 20 seconds during a Series C FIM switchover. This does not apply to control data.

If Network Activity Is . . . Then, Behavior During Switchover Is . . .

Link Maintenance Since Secondary Series C FIM link is a backup Link Active Scheduler
(LAS), it resumes network management activities as soon as it detects that
the old Primary Series C FIM is no longer there.
Both Primary and Secondary C FIM links have the same knowledge of
current time. When new Primary takes over as acting Link Master, it also
becomes acting time publisher.
System Management Operations Any System Management operation that is in progress is interrupted. For
example, the new Primary does not know anything about pending change
tag or address operation. As a result, device whose address or tag is being
changed will timeout and abort the operation.
Link Active Scheduler (LAS) The Primary LAS runs the link schedule by telling devices to publish their
data at specific times. The Secondary Series C FIM link is a backup LAS
with a valid copy of the link schedule. During switchover, it skips the
remainder of the current macrocycle and starts running its schedule from
time zero of next macrocycle. Unlike backup LAS devices, the Secondary
FIM has full LAS schedule with Series C FIM publications.
Alert Queued, User Triggered, Unidirectional Both Primary and Secondary Series C FIM links subscribe to alerts from
Multicast (QUU) VCR devices and receive them in parallel. Only the Primary Series C FIM link
reports received alerts through the CDA server to the operator interface.
After switchover, the new Primary Series C FIM starts and the old Primary
Series C FIM stops submitting alerts to the CDA server. The new primary
Series C FIM regenerates its alarms. This action covers whatever alarms
might have been acknowledged just prior to switchover but did not get
submitted to Server as a result of event throttling.
Subscriber Buffered, Network scheduled, Both Primary and Secondary links subscribe to the same data published by
Unidirectional broadcast (BNU) VCR a given device. Secondary has its VCR open and receives publications in
parallel with the Primary. No specific action needs to be taken during
switchover or swap.
Publisher Buffered, Network scheduled, Only acting Primary Series C FIM link can publish data to Fieldbus
Unidirectional broadcast (BNU) VCR devices. Both Primary and Secondary can be configured with the same
publication endpoint connection, but only the Primary link has this
connection open and active at a time. During switchover, the old Primary
closes its connection and consequently stops publishing. The old
Secondary, that is becoming new Primary, opens its connection and
consequently starts publishing.
Client Queued, User triggered, Bi-directional All client-server connections are broken and re-established. This way new
peer-to-peer (QUB) VCR Primary builds fresh connection context.
QUB connections are point-to-point and therefore can only be opened from
the primary.
Series C FIM maintains one Management Information Base (MIB)
connection to a device, one Function Block Application Process (FBAP)
connection and possibly one control connection.

155
11 SERIES C FIM4/FIM8 REDUNDANCY FUNCTIONALITY

11.7 Switchover events

Switchover results in several Experion system events and alarms. All of them are system information or
diagnostics type. No process alarms are generated due to switchover.
Typical events generated during switchover include:
• Connection failure to secondary module alarm
• Switchover event
• Not synchronized alarm
Each of these events appears for Series C FIMs where switchover occurred.

156 www.honeywell.com
12 Series C FIM4/FIM8 operation

This section includes the following topics on information and tasks associated with operating Series C FIM,
FFLinks, and Fieldbus Devices included in control strategies created in Control Builder.

Topic
“Series C FIM4/FIM8 startup” on page 159
“Initiating Series C FIM4/FIM8 shutdown” on page 160
“Series C FIM4/FIM8 IOTA display and LED descriptions” on page 161
“Activating or inactivating FIM4/FIM8 link” on page 167
“Initiating Series C FIM4/FIM8 link segment commands” on page 168
“Activating or inactivating fieldbus block” on page 170
“Checking/changing fieldbus device functional class” on page 171
“Checking live list and commissioning an uncommissioned device” on page 173
“Viewing and optimizing link schedule configuration” on page 174
“Initiating switchover command” on page 179
“Using fieldbus methods manager” on page 180
“Using controller menu functions” on page 184
“Using station detail displays” on page 185
“Using Station event summary display” on page 191

Related topics
“Series C FIM4/FIM8 startup” on page 159
“Initiating Series C FIM4/FIM8 shutdown” on page 160
“Series C FIM4/FIM8 IOTA display and LED descriptions” on page 161
“Control Builder Block icon descriptions” on page 164
“Activating or inactivating FIM4/FIM8 link” on page 167
“Initiating Series C FIM4/FIM8 link segment commands” on page 168
“Activating or inactivating fieldbus block” on page 170
“Checking/changing fieldbus device functional class” on page 171
“Checking live list and commissioning an uncommissioned device” on page 173
“Viewing and optimizing link schedule configuration” on page 174
“Initiating synchronization command” on page 178
“Initiating switchover command” on page 179
“Using fieldbus methods manager” on page 180
“Using controller menu functions” on page 184
“Using station detail displays” on page 185
“Foundation fieldbus detail displays/faceplates” on page 186

157
12 SERIES C FIM4/FIM8 OPERATION

“Using Station event summary display” on page 191

158 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.1 Series C FIM4/FIM8 startup

The following table summarizes the stages the Series C FIM4/FIM8 goes through after power is applied to its
IOTA during startup. The Series C FIM4/FIM8 repeats these stages every time power is cycled Off/On.

Stage Description
1 Power Light Emitting Diode (LED) Lights
2 Executes firmware installed in FLASH memory. The initial firmware boot code is installed at the factory.
3 The Status LED briefly displays all of its colors: RED, GREEN, AMBER. Then, remains solid RED until the
power-on self test (POST) completes.
4 Initiates a series of horizontal and vertical bars, as well as several brightness levels for evaluating the condition of
the 4-character, alphanumeric display. At the end, the Link Status LEDs are blinked in turn.
5 Executes power-on self test to verify that all subsystems are working as intended. Cycles test number codes in the
4-character display to show progress of the test.
(Initialization will halt on the first test that finds an invalid or faulty piece of hardware. The Series C FIM4//FIM8
will display the test number code associated with the detected device failure until it is reset.)
6 Upon successful completion of the power-on self test, displays information about the application image currently
stored through its 4-character display. The status LED should now reflect the true state of its associated hardware.
7 The 4-character display shows -bp- ((BOOTP) until it obtains its IP Address. The display then shows -ts- (Time
Server) until time has been obtained from the NTP Server.
Once its IP Address is known, it negotiates its redundancy role, either Primary or Secondary, with its partner
module, if present. Verifies that the correct Device Index is displayed (#nnn) and that no addressing errors are
detected. The primary module will have the odd IP address while the secondary module will have the odd + 1 IP
address. The odd IP address will follow the primary module during a switchover. The Device Index does not
change during a switchover or any other role change.
Once a device has obtained its IP Address and NTP Server IP Address(es), it retains them until its Device Index is
changed or firmware is reloaded.
(The Series C FIM4/FIM8 will determine if any other module is using the same IP address. If it does find another
module with the same Device Index, it will not join the network but instead transitions to no address state waiting
for new address assignment. If it finds another node with the same IP Address, it will not join the network but
instead transitions to dup address state; it must be reset to recover.)
8 The 4-character display cycles this information: Device Index setting, Link status, followed by Redundancy
status. See the Display and LED Descriptions section for more information about the display and LED
indications.

159
12 SERIES C FIM4/FIM8 OPERATION

12.2 Initiating Series C FIM4/FIM8 shutdown

Use the following procedure to initiate a shutdown command to the Series C FIM4/FIM8, which results in the
Series C FIM4/FIM8 rebooting to its RDY state or boot firmware.

Attention
Shutting down the Series C FIM4/FIM8, interrupts the transfer of data to the Experion system. Be sure your system
can tolerate the lost of live data, while the Series C FIM4/FIM8 is in its RDY state.

1 On the Monitoring tab, double-click the FIM4/FIM8 icon to open the FIM4/FIM8 Block configuration
form.
2 On the Main tab, click Controller Command box and select Shutdown from the list.
3 Click Yes to confirm the action.
4 Wait for the FIM4/FIM8 to reboot to its RDY state.

160 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.3 Series C FIM4/FIM8 IOTA display and LED descriptions

The following illustration and table identify and describe the display and LED indications associated with the 4-
character alphanumeric display on the Series C FIM4/FIM8 and LEDs on the Series C FIM4/FIM8 and IOTA.

Table 5: Display and LEDs on Series C FIM4 and IOTA.

If . . . Is . . . Then, it means that

H1 Activity LED (FIM4/ Off There is no activity on the link.
FIM8)
Blinking Green There is transmission activity on the link
Series C FIM Power LED Off Series C FIM4/FIM8 is not receiving power.
(FIM4/FIM8)
Green Series C FIM4/FIM8 is powered.
Series C FIM Status LED Off (Blanked or Frozen There is a Series C FIM4/FIM8 fault, no cause specified; or
(FIM4/FIM8) Display) hardware failure.
Green Non-redundant or primary Series C FIM4/FIM8 is loaded and
operation is okay.
For redundant operation, does not imply if the module is
synchronized or not.
Blinking Green Non-redundant or primary FIM4/FIM8 is okay, not loaded or
there is a soft failure. This may occur if no database is loaded
to the module or a soft failure condition exists.

161
12 SERIES C FIM4/FIM8 OPERATION

If . . . Is . . . Then, it means that

Amber Secondary Series C FIM4/FIM8 is in the backup or secondary
state and the module is synchronized.
Blinking Amber Secondary Series C FIM4/FIM8 is in the backup or secondary
state and is not synchronized or has a soft failure.
Red Module is running power on self test, or power on self test has
failed.
Blinking Red • Series C FIM4/FIM8 has no IP Address, no role. This
should be a transient condition after power up unless
BOOTP server is not running. Display will indicate
module is not faulted. The module is not on control.
• Series C FIM4/FIM8 is in Alive (ALIV) or Ready (RDY)
state and can accept a firmware download. Application
image is not executing. The module is not on control.
• Series C FIM4/FIM8 is in LOAD state and accepting a
firmware download. Application image is not executing.
The module is not on control.
• Series C FIM4/FIM8 is in the FAIL state. An
unrecoverable error has been logged and the module has
gone off control.
FTE A and/or FTE B LED Off Link integrity signal is present, but no activity. This is
(FIM4/FIM8) unlikely because every node will normally show some activity
over several seconds.
Blinking Green Link integrity signal is present, along with some activity.
Frequency of green LED pulse indicates the amount of
transmit traffic on the FTE link.
Red Link is not connected. No link integrity signal.
4-Character Alphanumeric #nnn It is the Series C FIM's FTE device index, where nnn can be
Display (FIM/FIM8) 001 to 255. This does not change with redundancy role.
X-CE Error during link communications Initialization. Where X
equals 1, 2, 3, or 4 for FIM4 and 1 through 8 for FIM8 links.
X-DE Error during link database initialization. Where X equals 1, 2,
3, or 4 for FIM4 and 1 through 8 for FIM8 links.
X-CI Link is undergoing communications initialization. Where X
equals 1, 2, 3, or 4 for FIM4 and 1 through 8 for FIM8 links.
X-DI Link is undergoing database initialization. Where X equals 1,
2, 3, or 4 for FIM4 and 1 through 8 for FIM8 links.
X-nn Link is currently online with connected devices. Where X
equals 1, 2, 3, or 4 for FIM4 and 1 through 8 for FIM8 links.
In addition, nn equals number of devices on the link from 01
to 16.
BKUP Series C FIM is currently in the Secondary role.
-np- Primary or Secondary Series C FIM is configured for
redundant operation, but a partner module is not physically
present.
nrdn Series C FIM is explicitly configured to be non-redundant.
!syn Redundant Series C FIM pair is not synchronized. Primary or
secondary Series C FIM is configured for redundant operation
and a partner module is physically present. Initial
synchronization has not occurred.
sync Redundant Series C FIM pair is synchronized.

162 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

If . . . Is . . . Then, it means that

XXX% Initial synchronization is in progress. Where XXX can be 000
to 100 to indicate percentage complete.
PRI Series CSeries C FIM is operating as primary in redundant
Series C FIM pair.
SEC Series CSeries C FIM is operating as secondary in redundant
Series C FIM pair.
TXXX Series C FIM is in test mode. Where XXX equals some self
test code.
BOOT Series C FIM is starting up.
ALIV Series C FIM is executing boot firmware. A valid application
image has not been loaded.
LOAD Series C FIM is executing boot firmware. A new boot or
application image is being loaded.
RDY Series C FIM is executing boot firmware. A valid application
image has been loaded.
FAIL Series C FIM has detected a software failure.

163
12 SERIES C FIM4/FIM8 OPERATION

12.4 Control Builder Block icon descriptions

Attention
Communication to the FF link is unavailable due to physical layer disturbances. Hence, you must correct the physical
layer disturbances and then perform a shutdown and startup of the FF link.

Related topics
“FIM4/FIM8 block icons” on page 164
“FIM4/FIM8 link icons” on page 165
“Fieldbus Device icons” on page 165
“Fieldbus block icons” on page 166

12.4.1 FIM4/FIM8 block icons

The following table summarizes the various appearances that a FIM4/FIM8 block icon can assume based on
configuration, view, and current Series C FIM operating state and status.

If Icon is . . . Then, it represents . . . And, Module

State Is. . .
Project Tab
(gray) FIM4/FIM8 configured for non-redundant operation. N/A

(gray/white) FIM4/FIM8 primary configured for redundant operation. N/A

(white/gray) FIM4/FIM8 secondary configured for redundant operation. N/A

Monitoring Tab
(blue) FIM4/FIM8 is non-redundant. Idle

(blue/white) Primary FIM4/FIM8 is synchronized Idle

(blue/yellow) Primary FIM4/FIM8 is not synchronized and partner FIM4/ Idle

FIM8 is visible.
(yellow/blue) Secondary FIM4/FIM8 is not synchronized and partner FIM4/ Backup
FIM8 is visible.
(blue/shadow) Primary FIM4/FIM8 is not synchronized and partner FIM4/ Idle
FIM8 is absent or incompatible.
(green) FIM4/FIM8 is non-redundant Run

(green/white) Primary FIM4/FIM8 is synchronized Run

(white/green) Secondary FIM4/FIM8 is synchronized Backup

(green/yellow) Primary FIM4/FIM8 is not synchronized and partner FIM4 is Run

visible
Primary FIM4/FIM8 is not synchronized and partner FIM4 is Run
(green/shadow) absent or incompatible

(yellow) FIM4/FIM8 is non-redundant No Database

(yellow/white) Primary FIM4/FIM8 is synchronized No Database

(yellow/yellow) Primary FIM4/FIM8 is not synchronized and partner FIM4 is No Database

visible

164 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

If Icon is . . . Then, it represents . . . And, Module

State Is. . .
Primary FIM4/FIM8 is not synchronized and partner FIM4 is No Database
(yellow/shadow) absent or incompatible
Secondary FIM/FIM8 is not synchronized and partner FIM4 is Backup
(shadow/yellow) absent or incompatible

(red) FIM4/FIM8 is non-redundant and not communicating Offnet

(red/white) Primary FIM4/FIM8 is not communicating. Offnet

(white/red) Secondary FIM4/FIM8 is not communicating. Offnet

12.4.2 FIM4/FIM8 link icons

The following table summarizes the various appearances that a FIM4/FIM8 Link block icon can assume based
on view and current FFLink state. FFLink blocks apply only to the primary or non-redundant FIM4/FIM8
block, and do not have matching blocks for secondary FIM4/FIM8.

If Icon is . . . Then, it represents . . .

Project Tab
(gray) FFLink associated with configured non-redundant or primary FIM4/FIM8.
Monitoring Tab
(gray/arrow) Control Builder / Control Data Access (CDA) server is currently establishing
communication to the FFLink.
(blue) FFLink is inactive.

(yellow) FFLink is initializing.

(green) FFLink is active.

(green/asterisks) FFLink is active and uncommissioned devices exist on the H1 network.

(red/black exclamation) Communication to the FFLink is unavailable

(red/white exclamation) Communication to the FFLink is available, but the FFLink is in a failed state.

12.4.3 Fieldbus Device icons

The following table summarizes the various appearances that a Fieldbus device block icon can assume based on
view and current device state. FFLink blocks apply only to the primary or non-redundant FIM4/FIM8 block,
and do not have matching blocks for secondary FIM4/FIM8.

If Icon is . . . Then, it represents . . .

Project Tab
(gray) Device added to Project.
Monitoring Tab
(gray/arrow) Control Builder / Control Data Access (CDA) server is currently establishing
communication to the device.
(green/question mark) Uncommissioned device.

(green) Device is online and is configured as a Basic device.

165
12 SERIES C FIM4/FIM8 OPERATION

If Icon is . . . Then, it represents . . .

(green/green clock) Device is online and is configured as a Link Master device. Green clock means
that the backup LAS in the field device is the same version and is in sync with
FIM4/FIM8 Link. It is important to operate with a green clock, so the Link
Master device has valid backup LAS in case of a FIM4/FIM8 failure.
Device is online and is configured as a Link Master device. A bad link schedule
exists in the device. A Red Clock indicates that either the field device never
received a backup LAS or is not at the same version and is out of sync with
FIM4/FIM8 Link. Such a condition can occur if the backup LAS cannot fit in the
field device (For example, EXPKS_E_CL_SCHED_TOOBIG error seen during
configuration download) or configuration download to the field device was
aborted because of other failures.
(red/black exclamation) Device is offnet. Communications with the device is unavailable.

(red/red exclamation) Communications with the device is available, but the device is in a failed state.
The device is a Basic device.
(red/red exclamation/red clock) Communications with the device is available, but the device is in a failed state.
The device is a Link Master device.

12.4.4 Fieldbus block icons

The following table summarizes the various appearances that a Fieldbus block icon associated with a Fieldbus
device can assume based on view and current block state. The faceplate of the block will vary to reflect the
block type such as Resource, Transducer, Analog Input, and so on.

If Icon is . . . Then, it represents . . .

Project Tab
(gray) Block added to Project.
Monitoring Tab
(gray/arrow) Control Builder / Control Data Access (CDA) server is currently establishing
communication to the block.
(green) Block is active

(blue) Block is inactive

(red/exclamation) Block is offnet. Communications with the block is unavailable.

166 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.5 Activating or inactivating FIM4/FIM8 link

Use the following procedure to change the state of a FIM4/FIM8 H1 Link through the Monitoring tab in
Control Builder.
Following are the considerations for activating or inactivating FIM4/FIM8 link
• Inactivating a FIM4/FIM8 Link essentially shuts downs the H1 Link and the Series C FIM, if all Links are
inactivated, and interrupts the transfer of data to the Experion system. Be sure your system can tolerate the
lost of live data, while the FFLink is inactive.
• All Fieldbus device blocks associated with the inactivated FFLink are also shutdown, including those
contained in Control Modules
• You can also initiate this same function through the corresponding Detail display in Station.

Prerequisites
• You can view FIM4/FIM8 and its Links through the Monitoring tab of Control Builder.

To change FIM4/FIM8 Link state

1 In Monitoring tab, click desired FFLink icon.
2 Click the Toggle State button in the toolbar.
3 In the Change State dialog, click Yes to initiate the state change.
4 Check that the FFLink icon changes from green to blue, when it is inactivated; or from blue to green when
its activated.
5 Repeat this procedure to inactivate or activate a given FFLink as applicable.
6 To inactivate the FIM4/FIM8, use this procedure to inactivate all 4 FFLinks or 8 FF links respectively.

167
12 SERIES C FIM4/FIM8 OPERATION

12.6 Initiating Series C FIM4/FIM8 link segment commands

The FIM4/FIM8 stores configuration data in non-volatile storage (NVS) for retention in case of loss of power,
module restarts and module shutdowns. Each H1 Link block has its own independent NVS log, where changes
in the configuration data are stored. The NVS usage increases as the configuration data changes. The current
NVS usage for each H1 Link is provided as a percentage by the NVSUSED parameter. The H1 Links'NVS logs
can be individually purged and compacted using the SEG Command parameter.
Use the following procedure to issue a startup, shutdown, or purge NVS (non-volatile storage), or Compact
NVS command to a Series C FIM4/FIM8 H1 Link through the Monitoring tab in Control Builder.
Following are the considerations for Initiating Series C FIM4/FIM8 link segment commands
• Shutting down a Series C FIM4/FIM8 Link essentially shuts downs the H1 Link and interrupts the transfer
of data to the Experion system. Be sure your system can tolerate the lost of live data, while the FFLink is
shutdown.
• All Fieldbus device blocks associated with the shutdown FFLink are also shutdown, including those
contained in Control Modules
• You can also initiate this same function through the corresponding Detail display in Station.
• You must shutdown the Series C link before issuing the Purge NVS command.

Prerequisites
• You can view FIM4/FIM8 and its Links through the Monitoring tab of Control Builder.

To use segment commands

1 In Monitoring tab, click plus sign + for FIM4/FIM8 icon to expose its associated Links in tree hierarchy.
2 Right-click desired FFLink icon and select Module Properties from the list to call up the FFLink Block
Parameters form.
3 Click the SEG Command box and select STARTUP, SHUTDOWN, PURGENVS, or COMPACTNVS
from the list to initiate desired FFLink/segment action. Click Yes to confirm the action.
4 Check that the SEG State read-only parameter changes to reflect the current state of the FFLink.
5 Click OK.
6 Repeat this procedure to use segment commands on another FFLink or issue another command on the
selected FFLink, as applicable.

12.6.1 Initiating a PurgeNVS SEG command

The result of a PurgeNVS operation is an NVS log that contains only the H1 Link block settings including the
Publication Method, Schedule Optimization enabled option, and Network Management bus parameters. The
Link Schedule, Agents, VCRs, and other FIM resident device configuration will be removed from the NVS log.
When the FIM4/FIM8 is restarted, the H1 Link block will retain its settings upon startup, but all Fieldbus
devices on the H1 Link will be uncommissioned. To resume schedule execution and control with that link, all
devices and CMs containing function blocks from that link must be reloaded from the Project view. The H1
Link must be DOWN to initiate a PurgeNVS operation.
Note: If a switchover is performed after the PurgeNVS SEG command is initiated but before the Primary FIM4/
FIM8 is restarted, the NVS logs will contain all configuration data such as;
• Link Schedule
• Agents
• VCRs
• FIM resident device configuration

168 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

To initiate a PurgeNVS SEG Command.

1 In the Monitoring view, double-click the H1 Link function block.
The configuration form appears.
2 If the SEG State parameter value of the H1 Link is ONLINE, select SHUTDOWN from the SEG
Command list to shutdown the H1 Link.
3 If the SEG State parameter value of the H1 Link is DOWN, select PURGENVS from the SEG Command
list to initiate a PurgeNVS operation.
4 Click OK.

12.6.2 Initiating a CompactNVS SEG Command

As the NVS usage increases, it may become necessary to compact the NVS log. The result of a CompactNVS
operation is an NVS log that contains all configuration data, using the minimum amount of space in the NVS
log. When the FIM4/FIM8 is restarted, the H1 Link will retain its configuration upon startup, and all Fieldbus
devices on the H1 Link that were previously commissioned will be commissioned upon startup. The
CompactNVS operation may be performed while the H1 Link is ONLINE.

To initiate a CompactNVS SEG Command.

1 In the Monitoring view, double-click the H1 Link function block.
The configuration form appears.
2 In the SEG Command list, select COMPACTNVS to initiate a Compact NVS operation.
3 Click OK.

12.6.3 Automated NVS compaction

A secondary FIM4/FIM8 in a redundant configuration will automatically compact its NVS logs in the following
circumstances.
• On startup of the secondary FIM4/FIM8, if the NVS usage of a NVS log is greater than 70%, that NVS log
will be compacted.
• On a Drop-Sync, if the NVS usage of a NVS log on the secondary is greater than 70%, that NVS log will be
compacted.
Automated NVS compaction does not occur on primary/non-redundant FIM4/FIM8 modules.

169
12 SERIES C FIM4/FIM8 OPERATION

12.7 Activating or inactivating fieldbus block

Following are the considerations for activating or inactivating fieldbus block
• Inactivating a Fieldbus device block interrupts the transfer of data to the Experion system. Be sure your
system can tolerate the lost of live data, while the block is inactive.

Prerequisites
• You can view FIM4/FIM8, its Links, and assigned Fieldbus devices through the Monitoring tab of Control
Builder.

To activate or deactivate a block

1 In Monitoring tab, click plus signs + for FIM4/FIM8, FFLink, and Device icons to expose Fieldbus blocks
in tree hierarchy.
2 Right-click desired Fieldbus block icon and select Activate> or Inactivate>Selected Item(s) from the list.
3 Check that the block icon changes from green to blue, when it is inactivated; or from blue to green when it
is activated.
4 Repeat this procedure to inactivate or activate a given Fieldbus block, as applicable.

170 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.8 Checking/changing fieldbus device functional class

Following are the considerations for Checking/changing fieldbus device functional class
• The Series C FIM is the primary Link Master for all Links. If you designate a device as a backup Link
Master, be sure it has the capacity to handle the Link Schedule. Otherwise, you may have to reset the device
as a Basic type and restart it to restore operation, if the Link Schedule is too large for it to handle.
• You can confirm the change by calling up the device's Parameters form and checking that BASIC appears
as the value for the DL Operational Functional Class parameter on the Network Management (Basic) tab.
• If you change the functional class for a device in the Project tab, be sure you restart the device after it is
loaded from Project for the change to be made in the device.
• You can manually cycle power to the Fieldbus device to restart it.

Prerequisites
• You can view FIM4/FIM8, its Links, and assigned Fieldbus devices through the Monitoring tab of Control
Builder.
• You have logged on with a security level that allows you to make changes in a control strategy.

To change device functional class

1 In Monitoring tab, double-click device icon to open its configuration Parameters form.
2 Click Network Management (LM) tab to open it.
3 Click the arrow button in Boot Operational Function Class box and select BASIC or LINKMASTER
from the list, as applicable.
4 Follow the online Wizard prompts to initiate the change. Click Finish to complete the change.
5 After Fieldbus device restarts, its functional class is changed to BASIC or LINKMASTER as commanded.
6 Be sure the Boot Operational Function Class change is also reflected in configuration form for the Project
version of the device.
7 Click OK to close the form.

Attention
With R400, you can enable/disable the alarm conditions status and configure the non-cache parameters through the
Device Diagnostics tab.

171
12 SERIES C FIM4/FIM8 OPERATION

To configure the non-cache parameters, perform the following steps.

• In the Non-Cache Parameters, click that appears in the text box.
• The Point Picker dialog box appears.
• Select the required blocks and the related parameters that appear in the dialog box.
• Click OK.
• The selected parameter description appears in the corresponding Parameter Description column.

172 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.9 Checking live list and commissioning an uncommissioned device

Use the following procedure to check the link for devices that are added to the Live List as uncommissioned.
Following are the considerations for checking live list and commissioning an uncommissioned device
• If you add an unconfigured Fieldbus device to a live/operating link, it will appear as an uncommissioned
device in the FFLink block hierarchy in the Monitoring tab in Control Builder.
• If you add a device with an address that is below 20 (decimal)/14 (hexadecimal) to the H1 Link, the Series C
FIM4/FIM8 clears the device's address so it can join the Link at a temporary address that can be reassigned
as required.
• If you add an uncommissioned device with a functional class of LINKMASTER to the H1 Link, the Series
C FIM4/FIM8 initiates the following actions to guard the network against incorrect link schedules.
Clears the Link Schedule,
Clears the Primary Link Master Flag Variable,
Sets the configured link settings,
Sets the device functional class to BASIC, and.
Restarts the device.
• It is possible that the uncommissioned device will have an earlier version of the vendor's software (Device
Rev). In this case, the device would appear to have no matching block type even if one exists for the same
device but it is for a different software version. If the vendor supports flash upgrade of its device's firmware,
you can upgrade the device's firmware through the Uncommissioned Devices tab on the Device's
Parameters form in Control Builder. Please see “Upgrading firmware in uncommissioned device” on
page 225 in the next Section Series C FIM4/FIM8 Maintenance for more information.
• A new Link Schedule must be loaded to the Series C FIM4/FIM8 and other Link Master devices anytime
there is a change that invalidates the current Link Schedule, such as adding a device, removing a device, or
making a configuration change.
• A block type must exist before a device can be integrated/commissioned with the system.

Prerequisites
• You can view FIM4/FIM8, its Links, and assigned Fieldbus devices through the Monitoring tab of Control
Builder.

To change uncommissioned device to commissioned one

1 In Monitoring tab, click plus sign + for FIM4/FIM8 icon to expose its associated Links in tree hierarchy.
2 Click the plus sign for the FFLink icon with an asterisks to expose the uncommissioned device icon
.
3 Double-click the uncommissioned device icon to open the FFLink Parameters form with the
Uncommissioned Devices tab open.
4 Click Create Project Database Instance for this Device to launch a commissioning wizard that
automatically steps through the process to commission a device. The process includes creating device Type,
changing tag and/or address, creating Project instance, matching Project to device, and loading device, as
required.
5 Click OK to close the Parameters form.
6 Repeat this procedure for other uncommissioned devices as needed.

173
12 SERIES C FIM4/FIM8 OPERATION

12.10 Viewing and optimizing link schedule configuration

The following table summarizes how to call up a Link schedule configuration for viewing in the control chart
area of the Control Builder application. You can also interact with the natural schedule to optimize it using the
considerations listed below. Or, you can configure the FFLink for the system to provide automatic schedule
optimization as noted in the following procedure.
Following are the considerations to configure link schedule optimization
• The key to optimizing the Link schedule is logically configuring the ORDERINCM parameter for each
block to:
Sequence blocks in a logical order from inputs to outputs and,
Execute non-control blocks after control blocks.
• The following are some general latency related considerations to use as reference for determining the most
logical overall sequencing for your Control Strategy.
Assume that faster loops are more critical and have a higher priority than slower ones on the same link.
Primary or innermost loops are always more critical than secondary or outer loops. The same is true for
lower level loops in multi-level cascades, since the timing requirements for each level become less critical.
Configurations that do not contain an output type block have a much lower priority than any configuration
that does, since these configurations are most likely intended for monitoring only.
Back-Calculation publications have the lowest priority, since they only have to be published before they are
needed in the next execution sequence.
Delay execution of non-control loop auxiliary blocks like integrators through the ORDERINCM parameter
sequencing. If they are created last, delay will occur naturally through the default ORDERINCM parameter
sequencing.

Attention
Loading the LINK with or without contents for the first time will not load the link schedule. However, it loads the
FFLINK Optimization parameters and will not modify the monitor view LINK schedule. LINK schedule gets
loaded only by loading a new FF CM or reloading the existing CM
• See the following procedure to configure the FFLink for automatic schedule optimization.

12.10.1 Calling up Link Schedule

If You Are in the . . . Then, you can And, the Link Schedule Configuration shows. . .
Project Tab Right-click the FFLink icon The block execution and data publications for all Control
and select Open Chart from Modules that are configured in Project and assigned to the
the list. Or, FFLINK or CEE. And, they contain Fieldbus function blocks
that are associated with a device assigned to the given FFLink,
Double-click the FFLink
and/or Experion blocks that participate in Link publications.
icon.
See the Sample Link Schedule configuration display in Project
Figure that follows this table for reference.
Monitoring Tab Same as above. The block execution and data publications for all applicable
Control Modules configured and assigned in Project and
loaded to the FFLINK or CEE. See the Sample Link Schedule
configuration display in Monitoring Figure that follows this
table for reference.

174 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

Figure 22: Sample Link Schedule configuration display in Project.

175
12 SERIES C FIM4/FIM8 OPERATION

Figure 23: Sample Link Schedule configuration display in Monitoring.

12.10.2 Additional Link Schedule terms reference

The following table lists additional terms that appear at the bottom of the link schedule (not shown in figures
above) along with their descriptions.

Term Description
Macrocycle Usage Gain Measures percent reduction in used portion of macrocycle, start to end of last element.
(MUG)

Latency Improvement Measures percent reduction in latency from start of input to end of output
Factor (LIF)
(reduction factor)

176 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

Term Description
Publication Gap Index based on square of gap sizes greater than 18 milliseconds.
Availability Improvement
(PGAI)

12.10.3 Configuring link schedule optimization

Prerequisites
You have completed your control strategy configuration that includes Fieldbus blocks integrated with control
modules in Control Builder.

To configure link schedule optimization

1 In the Project tab, click the plus sign for the FIM4/FIM8 icon to expose its FFLinks in the tree.
2 Right-click the first FFLink icon and select Module Properties to open the FFLINK Block Parameters
form.
3 On the Main tab, click the down-arrow button in the Link Schedule Optimization box and select OPT or
OPT_NOFORCE for automatic link schedule optimization. Otherwise, select NO_OPT to disable link
schedule optimization.
Refer to FFLink Configuration Parameters Reference for more information about the selections.
4 Click the down arrow button in the Sample Skew box and select SKEW or NOSKEW for desired block
execution action.
Refer to FFLink Configuration Parameters Reference for more information about the selections.
5 Repeat Steps 2 to 4 for other FFLinks, as applicable.
6 Click OK to close the form and save the settings.

177
12 SERIES C FIM4/FIM8 OPERATION

12.11 Initiating synchronization command

Use the following procedure to initiate a synchronization command manually to a redundant Series C FIM4/
FIM8 pair.

Prerequisites
You can view active redundant FIM4/FIM8 pair on Monitoring tab in Control Builder.

To command synchronization
1 In the Monitoring tab, double-click the primary FIM4/FIM8 icon to call up its Parameters configuration
form.
2 Click the Redundancy tab to display it.
3 Click Enable Synchronization.
4 Click Yes to confirm the action and issue the synchronize command.
5 Check the Redundancy Status data on the Parameters form and confirm that sync cycles in the primary
Series C FIM's 4-character display.
6 Click OK to close the Parameters form.

178 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.12 Initiating switchover command

You can use the following procedure to initiate a switchover command manually to a redundant Series C FIM4/
FIM8 pair.

Prerequisites
You can view active redundant FIM4/FIM8 pair on Monitoring tab in Control Builder.
The primary and secondary Series C FIM4/FIM8s are synchronized.

To command a switchover
1 In the Monitoring tab, double-click the primary FIM4/FIM8 icon to call up its Parameters configuration
form.
2 Click the Redundancy tab to display it.
3 Click Initiate Switchover.
4 Click Yes to confirm the action and issue the switchover command.
5 Confirm that the Secondary Series C FIM4/FIM8 assumes the Primary role.
6 Click OK to close the Parameters form.

179
12 SERIES C FIM4/FIM8 OPERATION

12.13 Using fieldbus methods manager

Prerequisites
Before you can launch Methods Manager you must:
• Create the block type for a device from its manufacturer's DD files that include methods data using the Type
command in Control Builder.
• Instantiate (create) and load the device block through Control Builder.
• Access the active device block through the Monitoring tab in Control Builder.

To launch Methods Manager

• You can use one of the following action to launch Methods Manager through Control Builder, assuming the
prerequisites have been met.

If You Select . . . Then, . . . And,

Device in Monitoring tab Click Field Devices- > Methods Methods Manager dialog provides a
Manager… selection list that includes all the
blocks associated with the device and
their available methods with the
method description.

To interact with Methods Manager

• The Methods Manager application executes the device's method and prompts users for needed interaction
based on the selected method. The following table lists some possible user prompted actions for reference.
The actual interaction is determined by the selected method.

Tip
• When active, press the Summary button on the Methods Manager dialog to call up a report that shows all
the steps executed during the execution of the selected method up to that point in time.
• When active, press the Show Methods List button to see the list of methods and their descriptions for the
selected device.

Note that some methods in the Methods List, which are derived from newer EDDs, may not be supported in
the current Experion release. These methods will be grayed out and unavailable for execution.

180 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

If Methods Manager Dialog . . . Then, You Are Prompted to . . .

Includes list of available Methods. Select the method to be
invoked and follow the
instructions in the Methods
Manager dialog.

• While using the Fieldbus Methods Manager to execute a method, do not use
Experion applications like Control Builder or Station to change the device/block
parameters for the device on which the methods is running.
• While using the Fieldbus Methods Manager to execute a method, some methods
may display messages that are very specific to a vendor. In this case, please
consult the vendor's user/maintenance manual to verify/validate it.
Shows action in progress. Wait for action to complete
before continuing.

181
12 SERIES C FIM4/FIM8 OPERATION

If Methods Manager Dialog . . . Then, You Are Prompted to . . .

Shows selection from a list. Select desired action by
selecting an option and follow
the instruction given in the
Methods Manager dialog.

Requests user acknowledgement. Follow the instruction given in

the Methods Manager dialog.

Requests user action. Follow the instruction given in

the Methods Manager dialog.

182 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

If Methods Manager Dialog . . . Then, You Are Prompted to . . .

Displays error message or code Note error and follow the
instruction given in the
Methods Manager dialog.

Shows an abort message Wait until the abort sequence

is completed.

183
12 SERIES C FIM4/FIM8 OPERATION

12.14 Using controller menu functions

Many of the Control Builder Controller menu functions designed for use with the Controller and CEE
components also apply for the FIM4/FIM8 and Links components. These include Upload, Update, and
Checkpoint functions. These functions are useful for correcting mismatches that may occur between the
components and the database. Please refer to the Control Building User's Guide for details about a given menu
function.

184 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.15 Using station detail displays

The Experion server Station application includes pre-configured Detail displays for the Series C FIM, Link,
device and Fieldbus function blocks. These displays are the default entries for the Point Detail Page parameter
on the Server Parameters tab of the configuration form. Once you establish communications with a Fieldbus
H1 link you can begin monitoring the status of any component that has been loaded as part of a Control Strategy
to a Series C FIM with points registered in the Experion server. The Detail displays let you quickly view the
component's current state, fault status, and pertinent configuration data.
Please refer to the Operator's Guide for detailed information about calling up, navigating, and viewing Station
displays.

185
12 SERIES C FIM4/FIM8 OPERATION

12.16 Foundation fieldbus detail displays/faceplates

A new set of Detail Displays and faceplates are created for the Foundation Fieldbus control points. The FF
Detail Displays and faceplates are designed to display only the standard FF parameters.
This feature is applicable to the following Foundation Fieldbus control points.
• PID (Proportional Integral Derivative)
• AI (Analog Input)
• DO (Digital Output)
• DI (Digital Input)
• AO (Analog Output)
• MAI (Multiple Analog Input)
Note that the FF Detail Displays and faceplates are not applicable for mixed modes (FF AI -> CEE PID -> FF
AO).
Refer to the following documents for more information:
• HMIWeb Display Building Guide for more information on creating displays.
• Server and Client Configuration Guide for more information on configuring faceplates.

12.16.1 Naming conventions for Detail Displays

You need to follow the conventions such as block name, Point Detail Display, and Group Detail Display to view
the FF Detail Displays.
The following table lists the conventions to be followed to view the FF Detail Displays.

Block name Point detail display Group detail display

AI sysdtlffaia sysdtlffai_fp
AO sysdtlffaoa sysdtlffao_fp
DI sysdtlffdia sysdtlffdi_fp
DO sysdtlffdoa sysdtlffdo_fp
PID sysdtlffpida sysdtlffpid_fp
MAI sysdtlffmaia sysdtlffmai_fp

12.16.2 Detail Displays contents based on FF control points loading

The FF control points can be loaded to FFLINK environment or CEE (C300 or C200) environment. However,
the contents in the Main tab display vary based on whether the point is loaded to the CEE environment or to the
FFLINK.

12.16.3 Tabs of FF Detail Displays

Refer to the Operator's Guide for additional details on using the Station and calling up the displays.
The following table lists the different tabs that appear in FF Detail Displays and a short description of each tab.

186 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

Detail Displays tab name Description

Main Tab Display This page displays the Control Module-related information based on the
following:
• Point is loaded to CEE environment.
• Point is loaded to FFLINK.
Depending on how the point is loaded, some of the group headings and their
related parameters appear on the page accordingly.
For example when the point is loaded in CEE environment, the following
headings appear on the page:
• Execution & Control
• Alarm Enable & Summary
• Assigned Controller
Similarly, when the point is loaded to FFLINK, the following headings appear
on the page:
• Device & Simulation State
• Alarm Summary
• Assigned Module
IO/Status Options Tab Display This page contains the options that you can select for altering the Input and
output block processing and the block processing status.
Alarms Tab Display This page can be used for configuring alarms, trip points and priority/severity.
You can enter a value between 0 - 15 as alarm priority which is the standard
for FF. Based on the priority, the associated alarm is logged in the Alarm
Summary.
Connection Tab Display This page displays the names of the Point Detail Display, Group Detail
Display, and associated display that are associated with the specific block.
Chart Tab Display This page displays the chart display of the loaded block.
Tuning Tab Display This page displays the Out value and Readback values that are plotted with Y-
axis units as %. This page also provides various configurable options for
plotting the trend.
Loop Tune Tab Display This page displays the Out value, SP value, PV value, Readback value that is
plotted with Y-axis units as %. Integral tuning time units are displayed both in
minutes and seconds. The master value is edited in minutes and seconds and
displayed as read-only parameter value and they support upto 2 decimal points.
This page also provides various configurable options for loop tuning.
Set Point This page displays the set point input ranges and set point ramping values.
This page provides various configurable options for status and control.
PV & OP Tab Display This page displays the process variable ranges and its status. This page also
provides various configurable options for control, output ranges, clamping/
filtering values, and track scale.

12.16.4 Detail Displays tabs of the different Foundation Fieldbus blocks

Not all tabs appear for all FF blocks. Use the following table to determine the tabs that appear for each FF
blocks.

FF Blocks PID AI AO DI DO MAI

Versus Tabs
Main X X X X X X
Tuning - - X - - -

187
12 SERIES C FIM4/FIM8 OPERATION

Loop Tune X - - - - -
Alarms X X - - - -
Connection X X X X X X
Chart X X X X X -
I/O status Option - - X X X X
Set Point X - - - - -
PV & OP X - - - - -

The following figure displays a sample FF PID Main tab detail display when the point is loaded in CEE
environment.

Figure 24: FF PID Main Tab Detail Display when loaded in CEE Environment.

The following figure displays a sample FF PID Main tab Detail Display when the point is loaded to FFLINK.

188 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

Figure 25: FF PID Main Tab Detail Display when loaded to FFLINK.

12.16.5 Common functionalities of faceplates

There are a few common functionalities that are applicable to one or more FF point faceplates.
Refer to the Server and Client Configuration Guide for more information on configuring faceplates.
The following table lists the common functionalities and the applicable FF point faceplates.

Functionality Applicable faceplate

Mode Attribute interpretation • sysdtlffai_fp.htm
• systdlffao_fp.htm
• sysdtlffpid_fp.htm
• sysdtlffdi_fp.htm
• sysdtlffdo_fp.htm
• sysdtlffmai_fp.htm
Intermediate EU values • sysdtlffai_fp.htm
• systdlffao_fp.htm
• sysdtlffpid_fp.htm

189
12 SERIES C FIM4/FIM8 OPERATION

Functionality Applicable faceplate

Off Normal Mode Indication on faceplates • sysdtlffai_fp.htm
• systdlffao_fp.htm
• sysdtlffpid_fp.htm
• sysdtlffdi_fp.htm
• sysdtlffdo_fp.htm
• sysdtlmai_fp.htm
PV Alarm Limits • sysdtlffai_fp.htm
13.16.6 • sysdtlffpid_fp.htm
READBACK Value • sysdtlffpid_fp.htm
• sysdtlffao_fp.htm
Auto selection • sysdtlffpid_fp.htm
13.16.7 • sysdtlffao_fp.htm
• sysdtlffai_fp.htm
• sysdtlffmai_fp.htm
• sysdtlffdi_fp.htm
• sysdtlffdo_fp.htm

12.16.6 FF Detail Displays example templates for Control Builder

FF Detail Displays example templates for Control Builder are installed as part of Experion installation. These
templates can be found in the following location: C:\Program Files\Honeywell\Experion PKS\Engineering
Tools\Examples\ FF Blocks.
These example templates are not supported for MAI block as it is not supported as a standard block in the
Control Builder.

Importing FF Detail Displays example templates into Control Builder

You can import FF Detail Displays example templates into Control Builder from the following location: C:
\Program Files\Honeywell\Experion PKS\Engineering Tools\Examples\ FF Blocks.

190 www.honeywell.com
 12 SERIES C FIM4/FIM8 OPERATION

12.17 Using Station event summary display

Like the Detail displays, the Station Alarm and Event Summary displays support the integration of Fieldbus
generated notifications and events. It is integrated with Experion component data and is for the most part self-
explanatory. Use the Event Summary display to get a quick review of recent actions that have been initiated
within the system.

191
12 SERIES C FIM4/FIM8 OPERATION

192 www.honeywell.com
13 Experion PKS Host Registration with Foundation
Fieldbus

Foundation Fieldbus is non-profitable organization consisting of leading process end users and automation
companies. Within the Fieldbus Foundation, end users, manufacturers, universities and research organizations
work together to develop an automation infrastructure that provides process integrity.
Experion is a registered host with Foundation Fieldbus organization (www.Fieldbus.org). The registration of
Experion Host with Foundation Fieldbus provides Experion users the benefits of the following additional
features.

193
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.1 New features

The following new features are supported.
• Conditional evaluation support for Fieldbus function blocks in Control Builder.
• Support for EDDL (Electronic Device Description Language) and visualization constructs.
• Support for Persistent Data Handling.
• Support for EDDL and visualization constructs for FF devices.
• Support for FF devices with Multi-capability feature.
• Advanced diagnostic support for FF devices.
As part of the Experion Host registration with FF, following is a complete list of features supported by
Experion.

Feature Description
Foundation H1 Device Support
H1 Device Address Assignment The capability of setting or clearing the H1 link address of an FF device.
Devices with cleared addresses appear at available temporary addresses. They
are not actually set to those addresses.
Configuration of Link Master Devices The capability to prepare and write (Network Management Information Bus)
NMIB and (System Management Information Bus) SMIB parameters associated
with link mastership.
H1 Physical Device Tag Assignment The capability to set or clear the physical device tag of an FF device.
Convert Link Master to Basic Device The capability to change FF devices from Link Master to Basic class.
H1 Software Download The capability to download device software or firmware code via the H1 link.
Distributed Application Support
Block Tag Configuration The capability to change, write, or clear tags of resource block, transducer
blocks, and function blocks within an FF device.
Block Instantiation The capability to add blocks to and delete blocks from FF devices on the link
using the FB_Action service.
Resource and Transducer Blocks The capability to read and write (if writeable) all parameters in standard and
enhanced resource blocks and all parameters in standard, enhanced, or custom
transducer blocks.
Standard Function Blocks The capability to read and write (if writeable) all standard parameters in
standard and enhanced function blocks.
Enhanced Function Blocks The capability to read and write (if writeable) all manufacturer-specific
parameters of enhanced function blocks.
Custom Function Blocks The capability to read and write (if writeable) all parameters, including
manufacturer-specific parameters, in custom function blocks.
Configuration of scheduled Control The capability to configure a distributed application including PID closed loop
function blocks control across multiple field devices without host-based function blocks.
Function Block Linking and Publication The capability to interconnect output parameters with input parameters between
Scheduling any supported function blocks.
Function Block Execution Scheduling The capability to schedule function blocks.
Foundation Alert Configuration and Handling
Process Alert Configuration and The capability to configure the report VCR for process alert notifications and
Handling display or record the process alert notifications.
Process Alert Management The capability to configure the report VCR for process alert notifications.
Configuration

194 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Feature Description
Process Alert Handling and The capability to confirm and display or record the process alert notifications.
Confirmation
Device Alert Management The capability to configure the report VCR for device alert notifications.
Configuration
Device Alert Handling and The capability to confirm and display or record the device alert notifications.
Confirmation
Multi-bit Alert Support The capability to utilize the multi-bit alarm capability.
Device Description Support
DD Blocks and Parameters • The capability to accept and utilize the definitions of blocks and their
parameters from Version 4 DD files.
• The requirement to support conditionals as restricted by the FF-901
specification.
• The requirement to support devices with multi-capability feature.

DD v4 Methods execution The capability to select and execute any DD method against its associated block.
DD v4 Menus The capability to display and navigate through menus as defined in a DD.
DD v5 Visualizations, Methods The capability to display and navigate through enhanced menus that contain
charts, graphs, images, grids, and so on as defined in a DD. The capability to
select and execute any DD method against its associated block.
The capability to display and navigate through the menus as defined in a DD is
also available at the field device level.
DD v5 Persistent data The capability to persist data as utilized by version 5 DDs.
Capability File Support The capability to import a Capability File for offline configuration.

195
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.2 Conditional support for FF devices

Conditionals are a set of rules that define or affect the parameter attributes like display format, validity,
handling, minimum value, maximum value and so on. When you modify the default value of a parameter, the
other parameter's attribute, which are conditionally affected by this parameter, also changes.
To support Conditional evaluation, the Parameter Definition Editor (PDE) is enhanced in Control Builder.
For more information, see Parameter Definition Editor Reference.

196 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.3 About EDDL

Electronic device Description Language (EDDL) technology is used by major manufacturers to describe the
information that is accessible in devices and it helps to define universal visualization information for the
devices. The EDDL technology for FF Devices in Control Builder appears in the DD View tab. The DD View of
the device and device function blocks are based on the visualization data present in the DD files.
DD View is available in configuration form of Project view, Monitoring view, and in PDE.
For more information, refer to the Parameter Definition Editor Reference.

197
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.4 About DD View tab

The DD View tab is a new tab that appears in the configuration form of the FF blocks and FF devices. In this
tab, you can view parameter values, configure parameter values, visualize graph, charts, and images and execute
methods in monitoring mode only. Hence, you can visualize the complete layout of the EDDL for the selected
FF block and FF devices. This tab appears only for those blocks/FF devices that support EDDL technology.

Figure 26: PDE view

For more information, see Parameter Definition Editor Reference.

On the FF block/FF devices configuration form, DD View tab appears only if the imported DD files have the
EDDL and visualization constructs like menus, charts and so on. On the DD View tab, parameters and its values
appear.

198 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Figure 27: DD View tab of FF blocks

199
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Figure 28: DD View tab of FF devices

Attention
• The DD View tab of an FF device contains parameters/methods of its FF blocks.
• On the Monitoring view, the DD View tab reflects the field values.
• Conditionals cannot be evaluated on the Project and Monitoring views.

Following are some of the considerations for FF blocks and FF devices with DD View.
• The DD View tab appears as the first tab for all the FF blocks and FF devices, which support EDDL
technology.
• The DD View tab consists of two panes, left pane and right pane. The left pane consists of menus to navigate
to the appropriate page and the right pane consists of items like image, charts, graphs, methods, parameters
and so on that appear as page.
• The left pane has an autohide feature so that you can view the contents completely in the right pane.
However, when you hover the cursor on the pane, the hidden pane appears.
• Tool tip appears for all controls and methods that are available in the EDDL features such as menus, charts,
graphs, and so on.
• Tool tip consists of information on parameter name, parameter description and unit if available.
The following table consists of toolbars and its descriptions.

Toolbar Description
To automatically hide the left pane. When you hover the
mouse on the left pane, the hidden pane appears.

200 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Toolbar Description
To navigate towards left of the tabs.

To navigate towards right of the tabs.

To identify button, which consists of methods.

To zoom out

To zoom in

To zoom and view at a fixed point

To copy to clipboard

To save the changes

To print the page

201
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.5 Multi-capability support for FF devices

You can configure a capability level for those FF device templates that support multi-capability levels. The
configured capability level of a device is contained in the DD file and the level is suffixed in the device template
name.
Note: A template represents a single device capability level. However, if you want to import a device with
different capability level, then you have to create one template for each of the capability level.
While importing an FF device DD file, the details of capability levels supported by the device are displayed.
For example, consider to import the device “EJX_0303,” which supports 3 levels of capability. If you import
this device by selecting the capability level as “2,” then it indicates that this device is imported with capability
level “2” and the device appears as “ “EJX_0303_2.”
Note: The capability level of a device is also displayed in the Capability Level column under the Device Match
dialog tab, only if the device supports Capability Level parameter, while matching an uncommissioned device to
a Project device.

202 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.6 About Field Diagnostic support

The Field Diagnostic support for FF devices provides the ability to monitor the device status using the standard
diagnostic parameters.
You can generate alarms, based on the conditions that are configured. These conditions are vendor-defined
aggregations of device diagnostics that are individually generated in a device and displayed in Experion.
Following are the different types of Field Diagnostic parameters.
• MAP: Parameter for enabling alarm detection
• ACTIVE: Parameter for indicating alarms.
• ALM: Parameter for maintaining alarm broadcast record.
• MASK: Parameter for enabling alarm broadcast.
• PRIORITY: Parameter for setting priority for each alarm category.
Following are the Field Diagnostics alarm categories that are available.
• Failure: Output signal is invalid because of a malfunction in the field device or its peripherals.
• Off-Specification: The device operates outside the specified range or an internal diagnostic indicates
deviations from measured values due to internal problems in the device or process characteristics. For
example, bubble formation in flow metering or valve sticking.
• Maintenance: Although the output signal is valid, the wear reserve exhausts or a function is restricted due to
operational conditions. For example, built-up of deposits.
• Check function: Output signal is temporarily invalid due to on-going work on the device.

Figure 29: Field Diagnostics tab with alarm parameters

203
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Figure 30: Field Diagnostics tab with Active parameters

204 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Figure 31: Field Diagnostics tab with Mask parameters

205
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

Figure 32: Field Diagnostics tab with Map parameters

206 www.honeywell.com
 13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.7 Parameter definitions

Following are the various parameters that are available at the device level. These parameter definitions are
similar to all Field Diagnostic categories.
• MAP parameter: This parameter maps conditions to be detected as active for the alarm category. If the alarm
condition occurs, then the alarm record will not be updated unless we have not masked the parameter.
• ACTIVE parameter: This parameter displays the error conditions that are currently indicated as active. The
ACTIVE parameter would indicate issues only If the corresponding MAP bits are ON.
Consider an alarm condition “Network failure.” If you map this parameter, then when the network failure is
detected, the alarm condition will be displayed in the alarm record and the parameter is broadcasted as
active.
• MASK parameter: This parameter allows you to broadcast single or multiple conditions that are active.
Therefore, when you mask an alarm condition, the condition is not broadcasted through the alarm.
• PRIORITY parameter: This parameter allows you to specify the priority of the alarm category. Based on the
priority set, the mapped alarm condition will be broadcasted in Station as an event or alarm.
Field diagnostics alarm priority is similar to Experion Alarm Priority. For more information, see “Fieldbus
versus Experion Alarm Priorities” on page 312
• ALM parameter: This parameter is used primarily to broadcast a change in the associated active conditions,
which are not masked for this alarm category. When a particular alarm condition occurs, then the alarm
details such as, timestamp, subcode and value is displayed in the alarm record.

Considerations
Following are the considerations for configuring diagnostic parameters.
• Using FD_XXX_PRI parameter, you can set the priority of Field Diagnostic alarms of corresponding
category.
• Each condition is evaluated at the device level to generate alarms.
• Each condition can be mapped or not mapped for each category using FD_XXX_MAP parameter.
• If the condition in the ACTIVE parameter is not masked by the corresponding bit in the MASK parameter,
then the condition will be queued for broadcast using the ALM parameter.
• You can view the alarm information such as, alarm status, and the time of alarm generation, values, and sub
code using alarm parameter.
• Each of the categories, share 32 conditions that can be defined by the device.
• An alarm condition is displayed as active, if a particular condition is mapped and the alarm for that
condition is generated in the device.

207
13 EXPERION PKS HOST REGISTRATION WITH FOUNDATION FIELDBUS

13.8 Persistent data handling

For some devices, the condition and performance cannot be determined empirically. For such devices, the
relative performance is the indicator of the device condition and the file constructs of the device blocks helps to
resolve this.

Attention
When creating a device template under the FIM link, a message appears displaying the information that the file
information is lost if the template details are replaced.

The file operations are supported per instance of the device and it is applicable to both Project mode and
Monitoring mode.
For example: If a device block refers to a File_TC_001 then this same file is referred in the Project and
Monitoring modes with the latest values available.

208 www.honeywell.com
14 Series C FIM4/FIM8 maintenance

This section provides information about maintaining the Series C FIM. The following table lists the topics
included in this section. If you are viewing this information online, just click the topic title to jump to the
information location.

Topic
“Periodic checks” on page 211
“Recommended spare parts” on page 212
“Series C FIM4/FIM8 removal and installation under power” on page 213
“Replacing device template with a different one” on page 214
“Replacing failed Series C FIM4 CC- or CU-PFB401” on page 221
“Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401, CC-or CU-TFB411, CC- or CU-TFB402, or CC- or
CU-TFB412” on page 222
“Relocating Series C FIM4/FIM8 or reassigning IP address” on page 224
“Upgrading firmware in uncommissioned device” on page 225
“Replacing a failed device with a like device having the same model name and device revision” on page 226
“Replacing a failed device with a different device using a different block type” on page 227
“Unlike device replacement report” on page 229
“Preparing Fieldbus device for a move or software migration” on page 232
“Using fieldbus device simulate function” on page 234
“Checking fieldbus device calibration” on page 236

Related topics
“Periodic checks” on page 211
“Recommended spare parts” on page 212
“Series C FIM4/FIM8 removal and installation under power” on page 213
“Replacing device template with a different one” on page 214
“Correcting some common UTR errors” on page 220
“Replacing failed Series C FIM4 CC- or CU-PFB401” on page 221
“Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401, CC-or CU-TFB411, CC- or CU-TFB402,
or CC- or CU-TFB412” on page 222
“Relocating Series C FIM4/FIM8 or reassigning IP address” on page 224
“Upgrading firmware in uncommissioned device” on page 225
“Replacing a failed device with a like device having the same model name and device revision” on page 226
“Replacing a failed device with a different device using a different block type” on page 227
“Unlike device replacement report” on page 229
“Changing or clearing tag and/or address of uncommissioned device” on page 231
“Preparing Fieldbus device for a move or software migration” on page 232

209
14 SERIES C FIM4/FIM8 MAINTENANCE

“Using fieldbus device simulate function” on page 234

“Checking fieldbus device calibration” on page 236

210 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.1 Periodic checks

The following table identifies checks that you should make periodically (every 3 to 6 months) to keep the Series
C FIM4/FIM8 in good working condition.

Check . . . Possible Corrective Action . . .

That all segments of the 4-character display and the light If segment or LED is not lit or has dimmed, you must
emitting diodes (LED) on Series C FIM4/FIM8 and IOTA replace the Series C FIM4/FIM8 or IOTA, since front-panel
are working. indicators and LEDs are not field replaceable.
That all connections are secure. Secure connections, as needed.
That cable insulation is not worn or cracked. Replace cables, as required.
That IOTA is secure. Tighten mounting screws.

211
14 SERIES C FIM4/FIM8 MAINTENANCE

14.2 Recommended spare parts

The following table provides a list of parts that you may want to keep on hand for backup.

Part Name Part Number Description Quantity per

10/100
Series C FIM4 CC- or CU-PFB401 Series C Fieldbus Interface Module 1/5

Series C FIM8 CC-PFB801 Series C Fieldbus Interface Module

Non-Red. IOTA (FIM4) CC- or CU-TFB401 Non-Redundant Input Output Terminal Assembly 1/2
Non-Red. IOTA (FIM4) CC- or CU-TFB402 Non-Redundant Input Output Terminal Assembly 1/2
- Supersedes CC/CU-TFB401 in row above.
Red. IOTA (FIM4) CC- or CU-TFB411 Redundant Input Output Terminal Assembly 1/2
Red. IOTA (FIM4) CC- or CU-TFB412 Redundant Input Output Terminal Assembly- 1/2
Supersedes CC/CU-TFB411 in row above.
Red. IOTA (FIM8) CC-TFB811 Redundant Input Output Terminal Assembly
Fuse (FIM4/FIM8) 51506348-341 800 mA, quick-acting fuse on Input Output 4/25
Terminal Assembly
Fuse Holder (FIM4/ 51506443-100 Fuse holder on Input Output Terminal Assembly 2/10
FIM8)
Connector (FIM4/FIM8) 51506471-202 Plug-in connector for H1 link field wiring 4/15
Pwr Conditioner IOTA F660A, or F860 Redundant Power Conditioner Input Output 1/2
(FIM4/FIM8) Terminal Assembly (Optional - order from vendor
MTL-Relcom)

212 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.3 Series C FIM4/FIM8 removal and installation under power

The Series C FIM4/FIM8 has been designed to permit removal and installation under power (RIUP) without
damaging the module or interrupting IOTA communications.
Please review the Removal and Insertion Under Power (RIUP) Function Guidelines in the Control Hardware
Installation Guide before you RIUP any module.

213
14 SERIES C FIM4/FIM8 MAINTENANCE

14.4 Replacing device template with a different one

Use the following procedure to replace one or more instances of the same Fieldbus device type with a different
device type.
Following are the considerations for replacing device template with a different one
• You have created a replacement/different Fieldbus device type in the Library tab of Control Builder.
• The Unlike Template Replacement wizard will guide you through the following replacement operations.
Select device instances to replace,
Select the replacement device type,
Initiate validation of the replacement for each device instance selected,
Initiate replacement of the selected instances, and
Display errors and warnings as appropriate.
• The wizard validates whether the replacement of a certain device instance with the selected device type is
acceptable. Errors and/or warnings may be generated during this operation.
• The wizard performs the replacement of each selected instance with the selected device type. Errors and/or
warnings may be generated during this operation.
• If you are using the Qualification and Version Control System, the wizard automates all required QVCS
operations. In general, the operational requirements of QVCS must be followed, regardless of whether the
user is making changes to the configuration or whether the system makes changes automatically.
• The contents of the original device's resource block are retained when the replacement is completed. Any
transducer blocks in the original device that match those in the replacement device have their contents
retained.
• Fixed function blocks can match with instantiable blocks of the same basic type, and vice-versa. When a
replacement device contains both fixed and instantiable blocks, for the same basic block preference is given
to the fixed block(s) first, and then followed by the instantiable blocks. This allows fixed blocks to be
allocated in the replacement device before instantiable blocks need to be created.

Prerequisites
• You have logged onto Control Builder with sufficient security level to make control strategy changes.
• You have created Fieldbus device types.

To use Unlike Template Replacement wizard to make device replacements

1 All the illustrations used in the following procedure are for example purposes only.
2 In the Project tab, select the Fieldbus device you want to replace. Use CTRL +click to select multiple
devices.
OR
In the Library tab, select the device type to be replaced.
3 In the Device menu, click Unlike Template Replacement to launch the wizard.
(You can also right-click on device and select Unlike Template Replacement from the list.)

214 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

4 Check that all selected devices or instances of selected device type are listed in the Available Controls
column. Select device(s) in the column and click Select to move selected devices to the Selected Controls
column. Or, just click Select All to move all the listed devices to the Selected Controls column.
(Use Remove or Remove All to remove one selected or all devices from the Selected Controls column, as
needed.)
5 On the right side of the dialog, select the Show only Same Device Models or Show all FF Device Types to
tailor what devices are shown in the Tree View and List View tabs below.
6 In the Tree View or List View tab, select the replacement device.

215
14 SERIES C FIM4/FIM8 MAINTENANCE

7 Click Next to call the Validation page.

8 Click Validate to initiate the validation function.

216 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

9 Wait for the validation process to be completed one device at a time. Note any errors or warnings that may
be displayed. Only devices with no errors will be enabled for replacement.
(Click Cancel to exit the operation and start over after making any necessary corrections.)
10 Check the check box in the Select column to select the device for replacement. All devices that passed
validation are automatically selected, and those that failed cannot be selected.

11 If error or warning messages appear in the Validation Results list box, click View Replacement Log to call
up the FF_UTR_Log to review validation results.
12 Click Next to call up the Replace Device page.

217
14 SERIES C FIM4/FIM8 MAINTENANCE

13 Confirm that the devices to be replaced are listed in the Summary list box.
14 Click Replace Device to initiate the replacement function.
15 Wait for the replacement process to be completed sequentially one device at a time. Note any errors or
warnings that may be displayed. Only devices with no errors will be replaced.
(Click Cancel to exit the operation and start over after making any necessary corrections.)
16 Check that the Status for each selected control turns to Replaced, when the function is completed.

218 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

17 If error or warning messages appear in the Unlike Template Replacement Results list box, click View
Replacement Log to call up the FF_UTR_Log to review replacement results.
If the message includes an error code reference, refer to the Control Builder Error Code Reference document
for more information. For example, if the message includes a reference like, [EXPKS_E_CL_INVLCYCST
(4L.101.10110)], the last five digits (10110) represent the error code.
18 Click DONE to close the wizard. If applicable, correct any errors and repeat the procedure.

219
14 SERIES C FIM4/FIM8 MAINTENANCE

14.5 Correcting some common UTR errors

The following table identifies some common errors that may occur during an UTR operation and offers some
suggested corrective action.

If You Encounter This Problem . . . Then, Take This Corrective Action . . .

Device is loaded to Monitoring side of Control Builder Delete the device from Monitoring side. Use the Force
Delete function, if necessary. This may also require the
device's blocks to be deleted from the Control Module on
the Monitoring side.
Device is locked Locate the source of the lock.
Block loss with control connections • Select another Fieldbus device type for replacement,
which can support all blocks that have connections.
• Change the control strategy to eliminate the control
connection(s) to the block that does not match.
Insufficient VCR's • Select another Fieldbus device type that has a sufficient
number of resources.
• Alternatively (although not recommended since the
intended results may be difficult to obtain), the user may
also modify the control strategy to reduce the number of
resources required. This may work, although the user
may have to go through several rounds of trial and error
before eliminating the error.
Insufficient FB Start Entries
Insufficient Link Objects.

220 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.6 Replacing failed Series C FIM4 CC- or CU-PFB401

Use the following procedure as a guide for replacing a failed Series C FIM4/FIM8.

CAUTION We recommend that you proceed with extreme caution whenever replacing any
component in a control system. Be sure the system is offline or in a safe operating mode.
Component replacements may also require corresponding changes in the control strategy
configuration through Control Builder, as well as downloading appropriate data to the
replaced component.

Following are the considerations for replacing failed Series C FIM CC- or CU-PFB401
• You can remove and install the Series C FIM4/FIM8 under power.
• Be sure you take ESD hazard precautions when handling the Series C FIM4/FIM8 and IOTA. See the
“Installation declarations” on page 32 section for more information.

CAUTION Only use a #2 Phillips screw driver to carefully loosen or tighten the long gray plastic
screw on the Module's face. Do not use either a #1 Phillips screw driver or a battery
powered screw driver to remove or install the plastic screw as this can damage the screw
head.

Prerequisites
You have logged onto Control Builder with sufficient security level to make control strategy changes.

To replace failed Series C FIM CC- or CU-PFB401

1 Loosen the screws that hold the Series C FIM4/FIM8 to the IOTA and remove the Series C FIM from its
connector on the IOTA.
(It is not necessary to completely remove the long gray plastic screw located on the module's face.)
2 Install the new Series C FIM4/FIM8 on its connector on the IOTA and tighten the screws.
3 Monitor the front-panel 4-character display to confirm that the Series C FIM receives its IP address and
starts running. If this is a redundant configuration, the Series C FIM starts in a secondary role. See Series C
FIM4/FIM8 Startup for more information.
4 Use the CTool utility to check that the firmware revision of the new Series C FIM4/FIM8 is the correct one
for your application.
• If firmware revision is correct, go to Step 6, if the Series C FIM is non-redundant; or go to Step 5, if it is
redundant.
• If firmware revision is not correct, go to the “Upgrading Series C FIM4/FIM8 firmware” on page 56
section and then return to Step 5, if Series C FIM is redundant; or Step 6, if it is non-redundant.
5 Command the primary Series C FIM to synchronize the secondary Series C FIM though the FIM4 block
parameters form in the Monitoring tab of Control Builder.
6 Load the block from Project tab.

221
14 SERIES C FIM4/FIM8 MAINTENANCE

14.7 Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401, CC-or

CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412
Use the following procedure as a guide to replace a non-redundant or redundant IOTA.
Following are the considerations for replacing IOTA CC-or CU-TFB401, CC-or CU-TFB411, CC- or CU-
TFB402, or CC- or CU-TFB412
• You can replace a non-redundant IOTA with a redundant one, providing that mounting space is available and
the Series C FIM has an odd Device Index number assignment.
• Be sure you take ESD hazard precautions when handling the Series C FIM and IOTA. See the “Installation
declarations” on page 32 section for more information.

CAUTION
This caution is not applicable for Series C Mark II.
• The screws in the 24V + and COM terminals can bind during installation or removal, if the IOTA mounting
screws are fully secured before the 24V/COM screws are secured/removed.
• Only use a #2 Phillips screw driver to carefully loosen or tighten the long gray plastic screw on the Module's
face. Do not use either a #1 Phillips screw driver or a battery powered screw driver to remove or install the
plastic screw as this can damage the screw head.

Prerequisites
• You have reviewed the previous CAUTION note.
• You have logged onto Control Builder with sufficient security level to activate/inactivate components.

To replace replacing IOTA CC-or CU-TFB401, CC-or CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412
1 You may want to inactivate the associated FFLinks through the Monitoring tab in Control Builder first,
since view of the process will be lost while the IOTA is being replaced
2 Record the Device Index number set on the binary coded decimal (BCD) switches on the IOTA.
3 Tag and remove the H1 link connections from connectors on the IOTA.
4 Remove the FTE cables from IOTA connectors.
5 Loosen the screws holding the non-redundant or Primary Series C FIM to the IOTA. Remove the Series C
FIM4/FIM8.
(It is not necessary to completely remove the long gray plastic screw located on the module's face.)
6 If you are replacing a redundant IOTA, loosen the screws holding the Secondary Series C FIM4/FIM8 to the
IOTA. Remove the Series C FIM4/FIM8 and be sure you can identify it as the Secondary Series C FIM4/
FIM8. Otherwise, go to the next Step.
7 Loosen the IOTA mounting screws half way.
8 Remove the screws from the 24V and COM terminals to disconnect the IOTA from the power bus bars.
9 Remove mounting screws, spacers, washers, and remove the IOTA.
• Be sure component side of replacement IOTA is facing up. Secure IOTA to carrier using screws, washers
and spacers provided.
• Insert spacers and washers between bottom of IOTA and top of carrier.
• Only tighten mounting screws half way.
10 Tighten screws in 24V and COM terminals to connect the IOTA to the power bus bars.
11 Fully tighten the mounting screws.
12 Set the BCD switches to the value noted in Step 2.
13 Connect H1 link connections to connectors on IOTA as noted in Step 3.

222 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14 Connect FTE Cables to appropriate connectors on the IOTA.

15 Install non-redundant Series C FIM or Primary Series C FIM on top connector on a redundant IOTA.
Tighten screws to hold Series C FIM to IOTA.
16 If you are replacing a redundant IOTA, install Secondary Series C FIM on lower connector on IOTA.
Tighten screws to hold Series C FIM to IOTA.
17 Check front-panel display to confirm operational state of the Series C FIM.
18 If necessary, load FIM4 block from Project and activate FFLinks in Monitoring mode.

To replace replacing IOTA DC-TFB402 or DC-TFB412

1 You may want to inactivate the associated FFLinks through the Monitoring tab in Control Builder first,
since view of the process will be lost while the IOTA is being replaced
2 Record the Device Index number set on the binary coded decimal (BCD) switches on the IOTA.
3 Tag and remove the H1 link connections from connectors on the IOTA.
4 Remove the FTE cables from IOTA connectors.
5 Loosen the screws holding the non-redundant or Primary Series C FIM to the IOTA. Remove the Series C
FIM4/FIM8.
(It is not necessary to completely remove the long gray plastic screw located on the module's face.)
6 If you are replacing a redundant IOTA, loosen the screws holding the Secondary Series C FIM4/FIM8 to the
IOTA. Remove the Series C FIM4/FIM8 and be sure you can identify it as the Secondary Series C FIM4/
FIM8. Otherwise, go to the next Step.
7 Remove the combo cable to disconnect the IOTA.
8 Loosen the IOTA mounting screws.
9 Remove mounting screws, spacers, washers, and remove the IOTA.
• Be sure component side of replacement IOTA is facing up. Secure IOTA to carrier using screws, washers
and spacers provided.
• Insert spacers and washers between bottom of IOTA and top of carrier.
• Only tighten mounting screws half way.
10 Connect the combo cable to the IOTA.
11 Fully tighten the mounting screws.
12 Set the BCD switches to the value noted in Step 2.
13 Connect H1 link connections to connectors on IOTA as noted in Step 3.
14 Connect FTE Cables to appropriate connectors on the IOTA.
15 Install non-redundant Series C FIM or Primary Series C FIM on top connector on a redundant IOTA.
Tighten screws to hold Series C FIM to IOTA.
16 If you are replacing a redundant IOTA, install Secondary Series C FIM on lower connector on IOTA.
Tighten screws to hold Series C FIM to IOTA.
17 Check front-panel display to confirm operational state of the Series C FIM.
18 If necessary, load FIM4 block from Project and activate FFLinks in Monitoring mode.

223
14 SERIES C FIM4/FIM8 MAINTENANCE

14.8 Relocating Series C FIM4/FIM8 or reassigning IP address

The following procedure outlines how to prepare a Series C FIM4/FIM8 for relocation to another network or
assigning a new device index and IP address.
Following are the considerations for resetting device index and IP address
• You can remove and install the Series C FIM4/FIM8 under power. See the previous Warning before doing
so.
• Be sure you take ESD hazard precautions when handling the Series C FIM4/FIM8 and IOTA. See the
“Installation declarations” on page 32 section for more information.
• The Series C FIM4/FIM8 retains its assigned IP address in non-volatile storage, which means it must be
erased before a new address can be assigned.
• If you are working with a redundant Series C FIM4/FIM8 pair, the device index and IP address will be reset
in both the Primary and Secondary modules. The node number for a device is dynamically assigned. The
primary device in a redundant pair always has an odd node number. The node number is actually the IP
address minus the Base IP Address set through System Preferences in Control Builder. The Device Index
number is set on the Binary Coded Decimal switches on the device's IOTA.
• For a redundant Series C FIM4/FIM8 application, be sure to set the Device Index to be an odd number. The
odd number will be used for the primary Series C FIM and a one (1) will be added to the number to be used
as a device index for the secondary Series C FIM. For example, if you set the Device Index to 17 for the
primary Series C FIM, the Device Index for the secondary Series C FIM would be 18.
• We recommend setting the Device Index for a non-redundant Series C FIM application to an odd number
also, so you can easily upgrade to a redundant Series C FIM application at a later date, if desired.
• After Device Index and IP address are reset, refer to the “Series C FIM4/FIM8 configuration” on page 61
and Loading FIM4/FIM8 Components Online sections in this book to configure and load the associated
function blocks for the reassigned Series C FIM(s).

Prerequisites
• You have logged onto Control Builder with sufficient security level to make control strategy changes.
• Be sure the system is offline or in a safe operating mode.

To reset device index and IP address

1 Remove power from the IOTA containing the non-redundant Series C FIM pair to be reset.

Note
This is not applicable for redundant Series C FIM4/FIM8.

2 Locate the three binary-coded decimal rotary switches on the lower left side of the IOTA.
3 Use a small flat-bladed screwdriver or your thumbnail to set the left-hand switch (100) to zero (0), midddle
switch (10) to zero (0) and the right-hand (1) switch to zero (0).
4 Apply power to the IOTA. Wait for Series C FIM(s) to start up and confirm that 4-character display shows
device index as #000.
5 Remove power from the IOTA.
6 Use a small flat-bladed screwdriver or your thumbnail to set the left-hand switch (100) to the desired most
significant decimal number, middle switch (10) to the desired next most significant decimal number and the
right-hand (1) switch to the desired least significant decimal number. The applicable setting range is 01 to
511.
7 Apply power to the IOTA. Wait for Series C FIM(s) to start up and confirm that 4-character display shows
device index as #nnn. Where nnn equals the Device Index number set on the switches in Step 6. The IP
address is assigned based on the new device index number.

224 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.9 Upgrading firmware in uncommissioned device

Use the following procedure to upgrade the firmware in an uncommissioned device through Control Builder.

CAUTION
Do not upgrade firmware in Honeywell model ST3000 or model STT35F, or Flowserve Logic 1400 devices on a
running Fieldbus link. Be sure to take all devices on the link off control before upgrading firmware in a ST3000,
STT35F, or LX1400 device.

Following are the considerations for initiating Firmware upgrade

If the Load Firmware button is inactive (grayed out) on the Uncommissioned Devices tab, try changing the
device address to a lower number in the 30 to 40 range.

Prerequisites
• You have the vendor supplied upgrade file for the device.
• You are monitoring the FIM4/FIM8 /FFLINK through the Monitoring tab in Control Builder.

To initiate a firmware upgrade

1 Double-click the uncommissioned device icon to open the FFLINK Parameters form with the
Uncommissioned Devices tab open.
2 Click Load Firmware to open the Device Firmware Upgrade dialog.
3 Click Upgrade to open the Open dialog.
• Use the Look In box to navigate to the directory location that includes the vendor's upgrade file.
• Select the file and click Open to initiates the firmware upgrade. This may take a few minutes to
complete.
4 Once the firmware upgrade is completed, wait for the device to rejoin the network. This may take up to three
minutes. Click the close button to close the dialog.
5 See the procedure to commission the device. Otherwise, click OK to close the form.

225
14 SERIES C FIM4/FIM8 MAINTENANCE

14.10 Replacing a failed device with a like device having the same model
name and device revision
Use the following procedure to replace a failed Fieldbus device with a like device having the same Model Name
and Device Revision (DEV_REV).

Tip
A wizard will guide you through the device replacement process when you initiate the action through the device
detail display in Station. In this case, you can ignore the following procedure.

Following are the considerations for replacing like device

• After the procedure, be sure you complete the device load before you return the system to normal operation.
• If you are replacing a device that includes instantiated blocks, you must re-load any Control Module and
Sequential Control Module that include client/server connections to the blocks in the replacement device
from the Monitoring tab before putting the device into operation. See “Replacing failed device that includes
instantiable blocks with like device” on page 122 for more information.

Prerequisites
The system is offline or in a safe operating mode

To replace a like device

1 Disconnect the failed device from the Link. Fieldbus device icon turns red in Monitoring tab.
2 Right-click the failed device icon and select Device Replacement from the list to call up the FFLINK
Block Parameters form with the failed device listed in the bottom half of the Device Replacement Dialog.
• Connect the replacement Fieldbus device to the Link
• Wait for the replacement device to appear as an Uncommissioned Device (UCD) listed in the top half of
the Device Replacement dialog.
• Click the check box to the left of the Tag column for the Replacement Device.
• The Replace the Failed Device with the Uncommissioned Replacement Device button becomes
active.
• Click Replace the Failed Device with Uncommissioned Replacement Device.
• Click Continue to acknowledge Warning prompt.
• If another Warning prompt appears, the replacement device was previously matched to another device
and the previous match will be undone, if you continue. Otherwise, go to the next Step.
• Progress dialog appears to track the status of the replacement.
• Wait for Replacement Device Load Confirmation dialog to appear. Click Continue. The Load Dialog
for replacement device appears. It is normal for an error code (Err xxxx) to appear in the Current State
column for the blocks.
3 Click the check boxes for the automatic state changes near the bottom of the dialog. Click OK. Load dialog
appears to track progress of the load.
4 Once the load is completed, check the Monitoring tab to confirm that the device icon has turned green and
function blocks are inactive (blue) or active (green) per the selected Post Load State.

226 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.11 Replacing a failed device with a different device using a different

block type
Use the following procedure to replace a failed device with a different device using a different block type.

Attention
Starting with R400, you can generate an Unlike Device Replacement Report for an FF device. You can view the
device-related information and the control Modules that would be affected by Unlike Device Replacement.
For more information on Unlike Device Replacement Report, see “Unlike device replacement report” on page 229.

Following are the considerations for replacing different device

• It is a good idea to record the Tag and Address assignments for the failed device before deleting it.
• It is a good idea to print out a parameters and connections report for a CM before you modify it. This will
serve as a convenient configuration reference.
• You must unassign the given Fieldbus block from its associated device before you can delete the device
from Project.
• If you unassign a Fieldbus block that has a RCAS_IN or ROUT_IN connection from a Experion block, be
aware that the VCR that was formed when the connection was made is not removed when the block is
unassigned. To remove this VCR, you must delete the block and then recreate it. The same is true, if you
want to delete the RCAS_IN or ROUT_IN connection and re-wire it to the block's CAS_IN pin.
• Always initiate match from Project Device to UCD for replacement devices.

Prerequisites
• The system is offline or in a safe operating mode
• The template of the replacement device must be added using the device DD files.

To replace a different device

1 Optionally, inactivate any CMs that contain blocks associated with the failed device.
2 Disconnect the failed device from the Link. Device icon turns red in Monitoring tab.
3 In Monitoring tab, locate all Control Modules (CMs) containing Fieldbus blocks associated with the failed
device. The associated Fieldbus block icons will be red.
4 Right-click the CM icon and select Force Delete from the list to open Force Delete dialog
5 Click Delete Selected object(s). Deletion errors are displayed in the list box for the dialog. You can ignore
these, since you know the failed device is off net.
6 Click Close to acknowledge any errors or skip this Step, if no errors are detected.
7 Repeat Steps 4 through 6 for other CMs, as required.
8 Right-click the failed device icon and select Force Delete from the list.
9 Click Delete Selected object(s). Deletes Failed device from the FFLink folder in Monitoring.
10 In the Project tab, right-click on the selected device to select Unlike Template Replacement (UTR).
The Unlike Template Replacement Wizard appears.
11 Check for all the selected devices or instances of device type that are listed in Available Controls.
• Select the device(s) in the column and click Select to move the selected devices to the Selected Controls
column.
Or
• Click Select All to move all the listed devices to the Selected Controls column.

227
14 SERIES C FIM4/FIM8 MAINTENANCE

Attention
Click Remove or Remove All to remove the selected devices or all the selected devices from the Selected
Controls column.

12 On the right pane of the dialog box, click Show only Same Device Models or Show all FF Device Types to
filter the devices in Tree View and List View tabs.
13 In the Tree View or List View tab, select the device template.
14 Click Next.
15 Click Validate.
The validation process starts for one device at a time.
Note: The selected devices must not have any errors to be enabled for replacement of the device.
16 Click Next.
The Replace Device dialog box appears with the list of devices to be replaced.
17 Click Replace Device.
The status of the selected devices changes to 'Replaced'.

Attention
If an error/warning message appears in the Unlike Device Replacement dialog box then click View Replacement
Log to open the FF_UTR_Log to review replacement results.

18 Click Close.
19 Switch back to the Monitoring tab, click the plus sign for FIM4 icon to expose its associated links in tree
hierarchy.
20 Click the plus sign for the FFLink icon with an asterisks to expose the uncommissioned device icon
.
21 Double-click the uncommissioned device icon to open the FFLink Parameters form with the
Uncommissioned Devices tab open.
22 Click Match to call up the Device Match dialog.
23 Click check box to left of Tag column for matching Project Device. Selects project device and activates the
Match buttons.
24 Click Match From Project Device to Uncommissioned Device.
25 Click Continue to acknowledge Warning prompt about Tag/Address changes in UCD.
26 Wait for match to be completed and note that the UCD's Tag and Address now match the Project Device.
Click OK to close the Match dialog.
27 In the Project tab, click FFLINK with new project device and click Controller->Load with Contents to call
up the Load Dialog.
• Ensure that the Load check boxes for components to be loaded are selected. Clear the check box to add/
remove component as applicable.
• Click OK.
28 Wait for load to complete and check that UCD changes to commissioned device, in Monitoring tab.
29 In Project tab, click CEE with reconfigured CM and click Controller->Load With Contents to call up
Load Dialog,
• Ensure that the Load check boxes for components to be loaded are selected. Clear the check box to add/
remove component as applicable.
• Click OK.
30 Wait for the load to complete and check that the CM is restored in Monitoring tab.

228 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.12 Unlike device replacement report

With R400, Unlike Device Replacement (UDR) Report can be generated to view information about the device
to be replaced and the control modules that are affected due to replacement of the failed device.

You can view the following information from the Unlike Device Replacement Report.
• Report identification: The top-level information used to identify device tag, time, and date.
• Device information: The following are the device- related information that is available.

ITEM SOURCE
Model Name VFDMODNAME parameter of Resource block
Device Address ADDR parameter of the device block
Device ID DEV_ID Parameter of the device block
FIM name 'Parent' of FF link
Template Name Device template name from the template library
Honeywell Name VFDVENNAME parameter of Resource block
Device Revision DEV_REV parameter of Resource block
DD Revision DD_REV parameter of Resource block
FF Link Name 'Parent' of device

• General procedure for FF Unlike Device Replacement: This defines a high-level procedure of unlike device
replacement, which consists of some of the pre-replacement and replacement steps.
• Directly affected modules: This section lists all CMs and SCMs that contain references to parent CMs of
device function blocks, but do not directly contain device functions blocks. These modules are listed
because all parent CMs that are deleted from the Monitoring side affect any CM or SCM that are connected.'
The following are the information that are available on the directly affected modules.

229
14 SERIES C FIM4/FIM8 MAINTENANCE

ITEM COLUMN
CM Name 'Affected Control Module'
CM Description (DESC parameter) 'Description'
Assigned To 'Reference end point
(Affected Module)'
Reference end point 'Reference end point
(Affected Module)'
Reference source point 'Reference source point
(To Be Deleted Module)'

• Modules to be deleted: This section consists of a list of Control modules that must be deleted during an
Unlike Device Replacement because they contain function blocks from the device to be replaced.
The following are the information that are available on the modules to be deleted.

ITEM COLUMN
CM Name 'Container Module Name'
CM Description (DESC parameter) 'Description'
Name of the device function block 'Device Function Block'
The controller name in which the CM is 'Controller Name'
contained

• You can export the data in any of the formats such as, MS Word, Excel, Adobe PDF, and so on.
• You can view the first level and second level modules that are affected due to the device replacement.
• You can print the data, which is available in the report generated.
To view Unlike Device Replacement Report, perform the following steps.
1. Right-click on the failed device icon to select Unlike Device Replacement Report.
The report of the failed device that appears consists mainly of the directly affected modules, general
procedure for FF Unlike Device Replacement, and the modules to be deleted.
2. In the Directly Affected Modules table, click Affected Module.
The detailed information about the selected Affected Module appears in a Second Level Affected Modules
tab.

Attention
To view the Main Report, click Main Report tab.

1. In the Modules to be Deleted table, click Container Module Name.

The detailed information about the selected module name appears in a First Level Affected Modules tab.

230 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

14.13 Changing or clearing tag and/or address of uncommissioned

device
Use the following general procedure to change the tag and/or address of a uncommissioned device. You can also
use this procedure to clear the tag name and/or address from a device to re-initialize it.
1 In the Monitoring tab, double-click the uncommissioned device icon to open the FFLINK Parameters
form with the Uncommissioned Devices tab open.
• To change the tag name, key in desired Tag (PD_TAG) name. Usually use the tag name that matches the
one used for the Project device. Press the Enter key or click OK.
• To clear the tag name, highlight it and press DELETE. Click OK.
2 Click Continue to acknowledge Warning prompt and initiate change.
3 Wait for change to complete. Press TAB to move cursor to Address box.
• To change the address, key in desired address and press ENTER.
• To clear the address, highlight it and press DELETE. Click OK.
4 Click Continue to acknowledge Warning prompt and initiate change.
5 Wait for change to complete. Click OK to close the form.
6 Confirm that the tag for the uncommissioned device icon in the Monitoring tab has changed or has been
cleared (NoTag_248).

231
14 SERIES C FIM4/FIM8 MAINTENANCE

14.14 Preparing Fieldbus device for a move or software migration

During migration to R400, EDDL constructs are ignored. Hence, you need to manually import the latest DD
files after migrating to R400. For more information on importing of DD files, see “Creating a fieldbus device
type from vendor DD”.
The process of importing the DD files enables interpreting the EDDL constructs along with Conditionals.

Attention
• The DD files must have the latest EDDL constructs to make use of the additional features, which are supported by
the Experion host.
• There is no limitation on the number of conditionals for the Experion host to support.
• Experion host supports version 1.9 of Device Capability File (.CCF) files.

Use the following procedure to prepare a device before migrating the system to a new software release or
moving the device to another Link.

Attention
If you do not prepare a device as outlined in the following procedure, you may have problems loading a device after it
is moved to another LINK or after the system software has been migrated to a new release.

1 In the Monitoring tab, click + plus sign for FIM4/FIM8, FFLINK, and Device icons to expand directories to
block level.
2 Right-click the Fieldbus block icon and select Inactivate- > Selected Item(s) to call up the Change State
dialog.
3 Click Yes to initiate the action. Check that the function block icon turns Blue.
4 Double-click the Fieldbus block icon to call up the Block Parameters configuration form.
5 On the Process tab, check that the Actual Mode has changed to OOS to confirm that the block is in Out-Of-
Service (OOS) mode.
6 Click OK to close the form.
7 Repeat Steps 2 to 6 for other Fieldbus blocks (if applicable), Transducer, and Resource blocks in the device,
in that order.
8 Device is now ready to be decommissioned and moved to another Link or migrated to a new system
software release.

14.14.1 Migrating Fieldbus device type to a release supporting Enable Block Offnet Diagnostic Alarm
The database can be migrated to R400 release, which supports Block Offnet Diagnostic Alarm parameter. The
Enable Block Offnet Diagnostic Alarm parameter is added to all the Fieldbus Block templates and is available
in control strategies or on Station Detail Displays. However, you must edit the template for each block within
the device for the parameter to appear on the Configuration form.
Perform the following steps to edit the template.
1 Right-click the Fieldbus block in the Library view.
2 Select Edit Type.
3 In the Font box, type OFFNETALM_ENABLED.
4 Select OK.
Perform this procedure for each Fieldbus block if you want the parameter to appear in the configuration
form.

232 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

Attention
You can also create the device type template by selecting device type from the device list. The OverWrite feature
reconfigures the configuration forms to include the 'Enable Block Offnet Diagnostic Alarm' check box.

233
14 SERIES C FIM4/FIM8 MAINTENANCE

14.15 Using fieldbus device simulate function

Some of the standard Fieldbus function blocks support a signal simulation function for testing purposes only.
The following procedure shows the general steps involved in using the simulate function with an Analog Input
block in a Honeywell ST3000 transmitter. You can easily adapt this procedure to any applicable Fieldbus
device.

CAUTION
Only use the simulate function when the system is offline or in a safe operating mode for testing purposes.

Prerequisites
The Fieldbus device is capable of supporting a simulate function.

To use a fieldbus device simulate function

1 Refer to the vendor documentation supplied with the Fieldbus device to determine the location of the
simulate activating jumper or switch on the device.
A switch or jumper is usually included in the device to inhibit accidental activation of the simulate feature.
2 Position the jumper or switch to its simulate enable position.
3 In the Monitoring tab, open the directory for the Fieldbus device icon and double click the Analog Input
function block to call up the Block Parameters form.
4 Click the Maintenance tab.

Attention
You can disable or enable individual block errors in the Function blocks, Transducer blocks, and Resource blocks.
You can enable/disable individual block errors only when block alarm is enabled in the Alarms tab.
Following are some of the considerations for disabling individual block errors.
• For the blocks such as AI block configured in Control Modules, when an inactive block error is disabled and if
the block error turns active, the Alarm Display will not display the alarm and the Event Summary will not
display the alarm event. For the devices only blocks such as, Resource or Transducer blocks, block error alarm
appearance in the System Status Display is affected.
• Regardless of disabling, the individual block error status is displayed on the block's Maintenance tab.
• When an active block error is disabled, the Alarm Display or System Status Display alarm returns to normal,
and Event Summary displays the alarm action as OK.
• In the Alarm Display or System Status Display, when you acknowledge block error alarms that have
returned to normal, the alarms disappear and Event Summary displays the acknowledged alarms.
• When the disable is removed for an active block error, the Alarm Display or System Status Display displays
the alarm as active and Event Summary receives the event for that particular alarm.

5 In the Simulate En/Disable box, click the arrow button and select Simulation Active.
6 Click Yes to confirm the action and initiate the simulate function.
7 Click the arrow button in the Simulate Status box. For this example, select Good from the list.
8 Click Yes to confirm the action and set the Simulate Status to Good.
9 Click in the Simulate Value box and key in 25 and press ENTER.
10 Click Yes to confirm the action and set the Simulate Value to 25.

234 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

Attention
The parameter Enable Block Offnet Diagnostic Alarm appears on the Maintenance tab of Resource blocks,
Transducer blocks, and other function blocks that support block errors. By default, this parameter is disabled,
which means that the Block Offnet Alarm is not reported if a device that contains the block goes off the network.
Before configuring the Enable Block Offnet Diagnostic Alarm parameter, consider the following conditions:
• If you enable the Enable Block Offnet Diagnostic Alarm, the Block Offnet Alarm is reported while the device,
which contains the block, goes offnet.
• If you disable the option while the alarm is active, the alarm returns to normal. Therefore, you can configure
this alarm before loading and it can be changed at runtime while the device is offline. You can silence the
alarm and prevent the report generation.

11 Click OK to close the form.

12 In the Monitoring tab, double-click the Control Module that includes the Analog Input block for the device
with the simulated value to open it in the control chart.
13 Check that OUT VALUE for the Analog Input block is 25 to confirm that simulate value is active. Click the
close button to close the CM.
14 To disable the simulation, repeat Steps 3 to 6 and select Simulation Disabled instead of Simulation Active
in Step 5.
15 Click OK to close the form.
16 Reverse the jumper position set in Step 2 to disable the simulate function in the device.

235
14 SERIES C FIM4/FIM8 MAINTENANCE

14.16 Checking fieldbus device calibration

Please refer to the manufacturer's documentation for the Fieldbus device to determine the recommended
calibration schedules and procedures. The Tune and Other tabs on the Parameters form for a device's
transducer block provide pertinent calibration information, when accessed through the Monitoring tab in
Control Builder. The following illustrations show typical Tune and Other tabs for reference.

Figure 33: Typical Tune tab for Fieldbus device's Transducer block.

236 www.honeywell.com
 14 SERIES C FIM4/FIM8 MAINTENANCE

Figure 34: Typical Other tab for Fieldbus device's Transducer block.

237
14 SERIES C FIM4/FIM8 MAINTENANCE

238 www.honeywell.com
15 Series C FIM4/FIM8 troubleshooting

This section provides information about troubleshooting the Series C FIM4/FIM8. The following table lists the
topics included in this section. If you are viewing this information online, just click the topic title to jump to the
information location.

Topic
“Isolating problems” on page 240
“Fault classifications” on page 241
“Initial checks” on page 242
“Series C FIM4/FIM8 self-test diagnostic codes” on page 245
“Fixing common problems” on page 252
“Getting further assistance” on page 258

Related topics
“Isolating problems” on page 240
“Fault classifications” on page 241
“Initial checks” on page 242
“Series C FIM4/FIM8 self-test diagnostic codes” on page 245
“FIM link communication error” on page 251
“Fixing common problems” on page 252
“Getting further assistance” on page 258

239
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.1 Isolating problems

This section offers some general data about fault classifications, initial checks, and Series C FIM self-test
diagnostic codes that may help you isolate the cause of a problem.
If you have observed a specific symptom and/or identified an error code, go to the Fixing Common Problems
section to see if you can find a matching topic.

240 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.2 Fault classifications

The following table lists some possible ways for classifying faults along with some identifying characteristics.

Fault Classification Characteristics

Hard Failure Failure detected by hardware; operation cannot continue. If the fault does not prevent
software processing the problem, the affected node will be rebooted under software
control into the FAIL State.
• If failure occurs on Primary node, it triggers a switchover to synchronized
Secondary node.
• If failure occurs on Secondary node, it results in loss of synchronization and
reduced availability until the problem is resolved.
• If failure occurs on non-redundant node, it results in loss of control and loss of
view.
Severe Failure Failure detected by software; operation cannot continue. The affected node will be
rebooted under software control into the FAIL State.
The failure scenarios are as listed in the row above for the Hard Failure.
Soft Failure Failure detected by software; operation continues with full control and full view. Soft
failures are alarmed to the operator. FTE will be monitored by the FTE System
Management Tool.
• If failure occurs on Primary node, it does not trigger a switchover to
synchronized Secondary node.
• If failure occurs on Secondary node, it does not result in loss of synchronization.
• If failure occurs on non-redundant node, it does not result in loss of control and
loss of view.
Installation/Startup Failure Detected by software. Node may not become operational.
• This failure does not apply to synchronized Primary node, since installation and
startup must be successful to reach synchronized Primary state.
• If failure occurs on Secondary node, it results in the inability to complete the
initial synchronization and to view the node on the network.
• If failure occurs on non-redundant node, it results in the inability to commence
control and to view the node on the network.
Communication Communication errors between peer nodes and/or I/O devices, including Fault
Tolerant Ethernet Bridge (FTEB), do not cause any node state change.

241
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.3 Initial checks

This section offers some checks that you can make to help isolate the problem. The checks are arranged in no
particular order.

Related topics
“Checking Control Builder error code reference” on page 242
“Checking front panel display and LEDs” on page 242
“Viewing flash log” on page 242
“Viewing release information log” on page 242
“Viewing trace log” on page 243
“Checking version and revision log” on page 243
“Checking server point build log” on page 243
“Checking server point build error log” on page 243
“Checking error log” on page 243
“Viewing link schedule log” on page 243
“Checking Fieldbus library manager log” on page 244
“Using CTool to capture diagnostic data” on page 244

15.3.1 Checking Control Builder error code reference

An indication of a problem may be in the form of an error dialog that includes an error message and possibly an
error code in Control Builder.
The syntax for a typical Control Builder error message is as follows:
Connection to device is not open EPKS_E_CL_NOCONN(6L.101.3326)
In this syntax, the error code is the last four digits in the message or 3326.
Please refer to the Control Builder Error Codes Reference book for applicable error code information.

15.3.2 Checking front panel display and LEDs

Check the Series C FIM 4-character display and Series C FIM/IOTA light emitting diodes (LEDs) indications
and compare results with data in the “Series C FIM4/FIM8 IOTA display and LED descriptions” on page 161
Descriptions section of this book.

15.3.3 Viewing flash log

The Flash.txt log provides a list of firmware updates that have been initiated.
To view the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\system\bin\Flash.txt.

15.3.4 Viewing release information log

The ReleaseInfo.txt log provides a list of Experion software releases that have been installed on the computer.
To view the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\system\bin\ReleaseInfo.txt.

242 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.3.5 Viewing trace log

The TraceLogRs.txt log provides a list of definitions for strings associated with breadcrumbs data for given
hardware components. The breadcrumbs provide a way to trace operations leading up to an event.
To view the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\system\bin\TraceLogRs.txt.

15.3.6 Checking version and revision log

The ver_rev.txt log provides a list of components by model number with software version/revision along with
compatible Experion software release(s).
To check the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\system\bin\ver_rev.txt.

15.3.7 Checking server point build log

The SvrPtBld_servername.txt log provides list of process (CB) points built in the server database.
To check the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\temp\SvrPtBld_servername.txt.

15.3.8 Checking server point build error log

The svrptblderr_servername.txt log provides list of any errors associated with process (CB) points built in the
server database
To check the log, navigate to this file location on the server: C:\Program Files\Honeywell\Experion PKS
\Engineering Tools\temp\svrptblderr_servername.txt.

15.3.9 Checking error log

The Errlog_n.txt log provides a running list of Control Builder detected errors in chronological order. The n
represents any number that is assigned to the most recent log.
To check the log, navigate to this file location on the server: C:\ProgramData\Honeywell\Experion PKS
\ErrLog_n.txt.
Prior to R400, the Errlog_n.txt file was stored in the following location on the server: C:\Documents and
Settings\All Users\Application Data\Honeywell\Experion PKS\Errlog_n.txt.

15.3.10 Viewing link schedule log

The FFLinkSchedule20000nnnPROJECT.txt log provides a description of the link schedule associated with the
given FFLink in Control Builder. The nnn represents the identifying portion of the FFLink block name
configured in Control Builder. The link schedule must be viewed in Control Builder for this log to be generated.
The log includes the following information categories.
• NATURAL SCHEDULE: Shows the execution and publish entries in the schedule by Control Module
(CM) point.
• SCHEDULE STATS: Shows the schedule statistics for the natural schedule.
• FB LIST: Lists the function blocks added to the list of scheduled objects.
• PUB LIST: Lists the connections added to the list of scheduled objects.
• CHAIN LIST: Lists the chains and the elements contained in each chain.

243
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

• OPTIMIZED SCHEDULE: Shows the execution and publish entries in the schedule with the optimized
schedule start times by Control Module (CM) point.
• SCHEDULE STATS: Shows the schedule statistics for the optimized schedule.
• SCHEDULE FACTORS: Shows the schedule factors for the optimized schedule compared to the natural
schedule.
To view the log, navigate to this file location on the server: C:\Documents and Settings\All Users\Application
Data\Honeywell\Experion PKS\FFLinkSchedule20000nnnPROJECT.txt.

15.3.11 Checking Fieldbus library manager log

The FieldbusLibraryManagerLog.txt log provides list of information captured during generation of given
Fieldbus device type from vendor DD file in chronological order.
To check the log, navigate to this file location on the server: C:\Documents and Settings\All Users\Application
Data\Honeywell\Experion PKS\FieldbusLibraryManagerLog.txt.

15.3.12 Using CTool to capture diagnostic data

Please refer to the Using CTool to capture diagnostic data section in the Control Hardware Troubleshooting and
Maintenance Guide for more information.

244 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.4 Series C FIM4/FIM8 self-test diagnostic codes

The following table lists the self-test diagnostic codes that the Series C FIM4/FIM8 steps through upon power
up.

Test Code Target Device(s) Failure Modes Function

T000 Signals start of selftest.
Display Diagnostics
T001 Display Test Bad display, Incorrect Steps through horizontal/vertical bars, then
assembly flashes all segments of the display through
stages of brightness. For this test to work, CPU,
Flash ROM, address bus, data bus, and some
I/O ports must be working. The module status
LED is set to GREEN, OFF, then RED for the
duration of self test.
CPU Diagnostics
T002 CPU Mask Revision Test Obsolete or unexpected This test is done before the ROM tests, because
new, CPU a wrong CPU could appear to work, but might
fail timing tests. The Instruction Cache may be
enabled after this test.
T003 CPU Speed Test Invalid jumper The software-visible hardware jumpers are
configuration verified. This is necessary because the PPC
Timebase and Decrementer run at CPU clock /4.
T004 Miscellaneous Speed Test Register configuration Checks the value of the system clock mode
register to ensure that bus division factor, CPM
division factor, the PLL predivision factor, and
the PLL multiplication factor are correct.
T010 Boot Image Test Bad flash memory, Bad The CRC-32 and other parameters of the boot
instruction cache image in ROM are computed and verified.
Running this test with the Instruction and Data
Cache enabled provides an acceptable SIL-2
cache test because it involves comparing against
a known value. Data cache is disabled after this
test.
T012 First Stuck Interrupt Test Bad wiring, Improper Checks for interrupts stuck on at power-on.
PLD configuration, Clears the interrupt pending register (SIPNR)
Improper FPGA and then re-checks if any interrupts are still
configuration asserted.
T013 Main RAM Initialization None Initializes all main RAM locations with 0 while
error detection functionality is turned off
Main RAM Diagnostics
T020 Main RAM Data Bus Test Stuck high and Stuck low Tests the data bus lines from the CPU to the
data bus lines caused by SDRAM for stuck high and stuck low bus lines.
shorts and unconnected
data lines
T021 Main RAM Address Bus Stuck high and stuck low Tests the address bus lines from the CPU to the
Test address bus lines caused SDRAM for stuck high and stuck low bus lines.
by shorts and
unconnected data lines

245
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Test Code Target Device(s) Failure Modes Function

T022 Main RAM Device Test Bad memory device Confirms that each bit in every memory location
can be set to either a 1 or 0 and can maintain
that value for a period of time. This diagnostics
consists of writing 0 and 0xFFFFFFFF, walking
1s, and walking 0s to all memory locations in
SDRAM.
T030 Main RAM Byte Access Bad memory controller Confirms that Main RAM can support byte-
Test configuration, Faulty sized memory accesses.
wiring between CPU and
SDRAM
T031 MainRAM HalfWord Bad memory controller Confirms that main RAM can support half-word
Access Test configuration, Faulty (16-bit) sized memory access.
wiring between CPU and
SDRAM
T032 Main RAM Word Access Bad memory controller Confirms that main RAM can support word (32-
Test configuration, Faulty bit) sized memory access.
wiring between CPU and
SDRAM
T033 Main RAM Double Word Bad memory controller Confirms that main RAM can support double
Access Test configuration, Faulty word (64-bit) sized memory access.
wiring between CPU and
SDRAM
T038 Main RAM SBE Test Improper EDAC Confirms that the memory controller's error
configuration in BR detection and correction functionality works
and/or MCR register, properly with respect to single bit errors. This
improper wiring from includes ensuring that single bit errors are
CPU to SDRAM corrected and recorded in the TESCR1 register's
ECC1 bit.
T039 Main RAM MBE Test Improper EDAC Confirms that the memory controller's error
configuration in BR detection and correction functionality works
and/or MCR register, properly with respect to double bit errors. This
improper wiring from includes ensuring that double bit errors are
CPU to SDRAM correctly flagged in the TESCR1 register's
ECC2 bit.
Cache Diagnostics
T040 Instruction Cache Test Bad CPU, Instruction Confirms that executing code with instruction
cache not activated cache turned on speeds up execution time.
Significantly, faster execution time will indicate
that the instruction cache works as expected.
T045 Data Cache Test CPU, Data cache is not Confirms that executing code with the data
activated cache turned on speeds up execution time when
there are repeated data accesses to the same
memory location. Significantly faster execution
time will indicate that the data cache works as
expected.
T046 Motorola Data Cache Test Bad CPU, Data cache not Tests the data cache as rigorously as it can be
activated tested. Honeywell wrote the source code for this
test.
EEPROM Diagnostics
T050 EEPROM Read Test Bad wiring between CPU Confirms that we can read from EEPROM.
and EPROM, Invalid port (This does not include validating the contents of
configuration EEPROM.)

246 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Test Code Target Device(s) Failure Modes Function

T051 EEPROM Write Protect Bad wiring between CPU Verifies that the write protect line defaults to the
Test and EPROM,Invalid port protected state
configuration
Thermometer Diagnostics
T052 Thermometer Test Bad wiring from CPU to SPI Digital Thermometers- Verify that data and
thermometers, Bad clock lines can be set to both states. Verify that
thermometers, invalid chip select lines can be set to both states. Read
ambient temperature, temperature from all digital thermometers,
invalid IO port verify acceptable values (acceptable operating
configuration temperature range -10 to +70 degrees C
indicates parts are working).
Miscellaneous Diagnostics
T065 EEPROM Checksum Test Bad EEPROM, Calculates the checksum of the factory data
Unprogrammed stored in EEPROM.
EEPROM, Bad wiring to
CPU
T066 PHY Interface Test Stuck high or low PHY Wiggles MDIO and MDCLK lines.
configuration lines
T067 Second Stuck Interrupt Test Bad FPGA image, faulty Checks for any asserted interrupt lines. Once the
wiring FPGA has been configured there should initially
be no asserted interrupts from the application
board (IRQ1).
Fieldbus Network Number 1 Diagnostics
T110 Communication Controller Bad CPLD image, Bad Writes a set of values to a communication
Data Path interboard connections, controller register in which all the bits are
Invalid memory writeable. The values written will include
controller configuration walking ones and walking zeros on all data bus
bits.
T111 Initialize Communication Bad memory controller Initializes the Fieldbus communication
Controller configuration, Faulty controller by setting up its internal registers with
wiring, Bad a base configuration used during power-on self-
communication controller test. Since this involves writing to the
chip communication controller's registers, this
function implicitly tests the data path from the
host processor to the communication processor
via the local bus. This test is performed on
Fieldbus network number 1.
T112 Communication Controller Bad communication Checks the communication controller's internal
Token Timer controller token timer. This timer is used to indicate the
token holding time remaining.
T113 Communication Controller Bad communication Checks the communication controller's internal
Node Timer controller node timer.
T114 Communication Controller Invalid communication Checks the communication controller's internal
Watch Timer Test controller configuration watch timer. The watch timer expires and
generates an interrupt, if there is no bus activity
after a specified period of time.
T115 Communication Controller Bad communication Checks the communication controller's internal
Gap Timer controller gap timer. The gap timer governs the minimum
amount of time between two transmissions.
T116 FIFO Threshold Interrupt Bad communication Checks the implementation of the FIFO
Generation controller threshold interrupts (TFI and RFI). These
interrupts are generated when the TX and/or RX
FIFOs exceed a specified limit.

247
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Test Code Target Device(s) Failure Modes Function

T117 Communication Controller Bad communication Checks to see that an interrupt generated by the
Interrupt Generation controller interrupt communication controller can be seen by the
aggregation host processor.
T118 Communication Controller Bad communication Puts the communication controller into internal
Loopback controller loopback mode and tests to see that data can be
transmitted and received with internal loopback
on. This test is performed on Fieldbus network
number 1
Fieldbus Network Number 2 Diagnostics
T120 Communication Controller Bad CPLD image, Bad Writes a set of values to a communication
Data Path interboard connections, controller register in which all the bits are
Invalid memory writeable. The values written will include
controller configuration walking ones and walking zeros on all data bus
bits.
T121 Initialize Communication Bad memory controller Initializes the Fieldbus communication
Controller configuration, Faulty controller by setting up its internal registers with
wiring, Bad a base configuration used during power-on self-
communication controller test. Since this involves writing to the
chip communication controller's registers, this
function implicitly tests the data path from the
host processor to the communication processor
via the local bus. This test is performed on
Fieldbus network number 2.
T122 Communication Controller Bad communication Checks the communication controller's internal
Token Timer controller token timer. This timer is used to indicate the
token holding time remaining.
T123 Communication Controller Bad communication Checks the communication controller's internal
Node Timer controller node timer.
T124 Communication Controller Invalid communication Checks the communication controller's internal
Watch Timer Test controller configuration watch timer. The watch timer expires and
generates an interrupt, if there is no bus activity
after a specified period of time.
T125 Communication Controller Bad communication Checks the communication controller's internal
Gap Timer controller gap timer. The gap timer governs the minimum
amount of time between two transmissions.
T126 FIFO Threshold Interrupt Bad communication Checks the implementation of the FIFO
Generation controller threshold interrupts (TFI and RFI). These
interrupts are generated when the TX and/or RX
FIFOs exceed a specified limit.
T127 Communication Controller Bad communication Checks to see that an interrupt generated by the
Interrupt Generation controller interrupt communication controller can be seen by the
aggregation host processor.
T128 Communication Controller Bad communication Puts the communication controller into internal
Loopback controller loopback mode and tests to see that data can be
transmitted and received with internal loopback
on. This test is performed on Fieldbus network
number 2
Fieldbus Network Number 3 Diagnostics
T130 Communication Controller Bad CPLD image, Bad Writes a set of values to a communication
Data Path interboard connections, controller register in which all the bits are
Invalid memory writeable. The values written will include
controller configuration walking ones and walking zeros on all data bus
bits.

248 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Test Code Target Device(s) Failure Modes Function

T131 Initialize Communication Bad memory controller Initializes the Fieldbus communication
Controller configuration, Faulty controller by setting up its internal registers with
wiring, Bad a base configuration used during power-on self-
communication controller test. Since this involves writing to the
chip communication controller's registers, this
function implicitly tests the data path from the
host processor to the communication processor
via the local bus. This test is performed on
Fieldbus network number 3.
T132 Communication Controller Bad communication Checks the communication controller's internal
Token Timer controller token timer. This timer is used to indicate the
token holding time remaining.
T133 Communication Controller Bad communication Checks the communication controller's internal
Node Timer controller node timer.
T134 Communication Controller Invalid communication Checks the communication controller's internal
Watch Timer controller configuration watch timer. The watch timer expires and
generates an interrupt, if there is no bus activity
after a specified period of time.
T135 Communication Controller Bad communication Checks the communication controller's internal
Gap Timer controller gap timer. The gap timer governs the minimum
amount of time between two transmissions.
T136 FIFO Threshold Interrupt Bad communication Checks the implementation of the FIFO
Generation controller threshold interrupts (TFI and RFI). These
interrupts are generated when the TX and/or RX
FIFOs exceed a specified limit.
T137 Communication Controller Bad communication Checks to see that an interrupt generated by the
Interrupt Generation controller interrupt communication controller can be seen by the
aggregation host processor.
T138 Communication Controller Bad communication Puts the communication controller into internal
Loopback controller loopback mode and tests to see that data can be
transmitted and received with internal loopback
on. This test is performed on Fieldbus network
number 3.
Fieldbus Network Number 4 Diagnostics
T140 Communication Controller Bad CPLD image, Bad Writes a set of values to a communication
Data Path interboard connections, controller register in which all the bits are
Invalid memory writeable. The values written will include
controller configuration walking ones and walking zeros on all data bus
bits.
T141 Initialize Communication Bad memory controller Initializes the Fieldbus communication
Controller configuration, Faulty controller by setting up its internal registers with
wiring, Bad a base configuration used during power-on self-
communication controller test. Since this involves writing to the
chip communication controller's registers, this
function implicitly tests the data path from the
host processor to the communication processor
via the local bus. This test is performed on
Fieldbus network number 4.
T142 Communication Controller Bad communication Checks the communication controller's internal
Token Timer controller token timer. This timer is used to indicate the
token holding time remaining.
T143 Communication Controller Bad communication Checks the communication controller's internal
Node Timer controller node timer.

249
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Test Code Target Device(s) Failure Modes Function

T144 Communication Controller Invalid communication Checks the communication controller's internal
Watch Timer controller configuration watch timer. The watch timer expires and
generates an interrupt, if there is no bus activity
after a specified period of time.
T145 Communication Controller Bad communication Checks the communication controller's internal
Gap Timer controller gap timer. The gap timer governs the minimum
amount of time between two transmissions.
T146 FIFO Threshold Interrupt Bad communication Checks the implementation of the FIFO
Generation controller threshold interrupts (TFI and RFI). These
interrupts are generated when the TX and/or RX
FIFOs exceed a specified limit.
T147 Communication Controller Bad communication Checks to see that an interrupt generated by the
Interrupt Generation controller interrupt communication controller can be seen by the
aggregation host processor.
T148 Communication Controller Bad communication Puts the communication controller into internal
Loopback controller loopback mode and tests to see that data can be
transmitted and received with internal loopback
on. This test is performed on Fieldbus network
number 4.
Pre-OS Diagnostics
T400 Application Image Missing Application Checks for valid Application Image stored in
Validation Image, Incomplete load flash memory.
of Application Image,
Bad flash memory
T401 Unused Port Pin Unanticipated usage of Confirms that unused parallel port pins on the
spare port pins CPU can be driven into both high and low
states.
T511 End of POST Diagnostics Confirms that self test is successful and there is
a valid Application Image stored in Flash.

250 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.5 FIM link communication error

FIM link communication error is defined as the failure to communicate with the FF link.

Diagnostic check
• Failure to communicate with the FF link.
• Link state in Control Builder displays as “COMMINITERR” and the Link appears in red color.
• FIM LED display: XX-CE, here “XX” indicates link number and “CE” indicates communication error.

Cause
Physical layer disturbances, such as poor grounding, noise, electrical interference, and so on.

Solution
1. Correct the physical layer disturbances.
2. On the Monitoring view, right-click the FIM link to select Module Properties.
The FFLink Block Parameters Configuration page appears.
3. On the Main tab, click SEG Command box and then select SHUTDOWN from the drop-down list.
4. Click Yes to confirm.
5. Under the SEG Command box, select STARTUP from the drop-down list.
6. Click Yes to confirm.

251
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.6 Fixing common problems

This section identifies some common problems and describes how you might fix them.

Related topics
“Loss of power” on page 252
“Poweron Self-Test Fault” on page 252
“Fatal ECC error” on page 253
“Background Diagnostic failure” on page 253
“No IP address” on page 253
“No time reference” on page 254
“Isolated (lonely) Node” on page 254
“Device Index setting does not match displayed value” on page 255
“Duplicate Device Index setting” on page 255
“Device Index value is zero upon power up” on page 256
“Device reload or replacement fails” on page 256
“Generation of excessive alarms” on page 256
“Alarms not occurring when expected” on page 257
“Connected Fieldbus device is not detected by the FF link” on page 257

15.6.1 Loss of power

The power supply has failed or the main power source has been shut down or is experiencing a brownout or
blackout condition.

Diagnostic Check • The 4-character display on the Series C FIM4/FIM8 and LEDs on the Series C FIM and
the IOTA are off.
• In the Monitoring tab, the FIM4/FIM8 icon turns red.
Cause 1 Main power source has been disconnected or shut down either manually or temporarily by
brownout or blackout condition.
Solution Re-connect the main power source or turn it On or wait for temporary brownout or blackout
condition to pass.
Cause 2 The 24 Vdc power supply failed or power cable has been disconnected or failed.
Solution Replace the 24 Vdc power supply or re-connect/replace the power cable.
Cause 3 Power fuse opens on IOTA.
Solution Replace power fuse.

15.6.2 Poweron Self-Test Fault

The Series C FIM4/FIM8 poweron selftest has detected a fault.

Diagnostic Check A self-test diagnostic code remains on display and the poweron selftest does not continue.
Cause The Series C FIM4/FIM8 power on self test has detected a failure that does not allow
operation to continue.
Solution Try shorting the reset pads on the IOTA to re-start the Series C FIM4/FIM8. If error persists,
replace the Series C FIM4/FIM8. See “Replacing failed Series C FIM4 CC- or CU-PFB401”
on page 221 for details.

252 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.6.3 Fatal ECC error

The Series C FIM4/FIM8 software has detected a fatal Error Checking and Correction (ECC) condition that can
be a multiple-bit error or excessive single bit errors in main Random Access memory (RAM).

Diagnostic Check • The 4-character display on the Series C FIM4/FIM8 displays FAIL.
• In the Monitoring tab, the FIM4/FIM8 icon turns red.
Cause The Series C FIM4/FIM8 software has detected a failure that does not allow operation to
continue. There can be many causes for a failure including hardware, use the Series C
Platform Analyzer to capture a crash block for the device to determine the possible cause
before proceeding.
Solution Try shorting the reset pads on the IOTA to re-start the Series C FIM4/FIM8. If error persists,
replace the Series C FIM4/FIM8. See “Replacing failed Series C FIM4 CC- or CU-PFB401”
on page 221 for details.
Check the Trace log for breadcrumbs that occurred prior to the event. See “Viewing trace
log” on page 243 and “Using CTool to capture diagnostic data” on page 244 for more
information. Provide the results of the trace log to our Solutions Support Center (SSC) for
analysis.

15.6.4 Background Diagnostic failure

The Series C FIM4/FIM8 detects failure in system integrity checks, such as Watch Dog Timer (WDT), error
detection circuits, Field Programmable Gate Array (FPGA) readback, microprocessor static configuration
registers, and Read Only Memory (ROM) checksum.

Diagnostic Check • The 4-character display on the Series C FIM4/FIM8 displays FAIL.
• In the Monitoring tab, the FIM4/FIM8 icon turns red.
Cause The Series C FIM4/FIM8 software has detected a background diagnostic failure that does not
allow operation to continue.
Solution Try recycling power to the Series C8 FIM4/FIM8. If error persists, replace the Series C
FIM4/FIM8. See “Replacing failed Series C FIM4 CC- or CU-PFB401” on page 221 for
details. Check the Trace log for breadcrumbs that occurred prior to the event. See “Viewing
trace log” on page 243 and “Using CTool to capture diagnostic data” on page 244 for more
information. Provide the results of the trace log to our Solutions Support Center (SSC) for
analysis.

15.6.5 No IP address
The Series C FIM4/FIM8 cannot obtain an IP address.

Diagnostic Check The 4-character display on the Series C FIM4/FIM8 displays -bp-.
Cause 1 A valid IP address has not been configured.
Solution Configure a valid IP address through the System Preferences dialog in Control Builder.
Cause 2 The BOOTP server service is not running.
Solution Check that the Experion BOOTP Server service is running through the Services dialog of the
Control Panel application.
Cause 3 The BOOTP server was not re-started after a change in the Device Index or System
Preferences.
Solution Stop and start the Experion BOOTP Server service through the Services dialog of the Control
Panel application.

253
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Cause 4 Communication problems.

Solution Check your FTE network and cables for proper operation.

15.6.6 No time reference

The Series C FIM4/FIM8 cannot obtain a system time reference.

Diagnostic Check The 4-character display on the Series C FIM4/FIM8 displays -ts-.
Cause 1 Valid (S)NTP Server addresses have not been configured.
Solution Configure valid (S)NTP Primary and Secondary Server IP addresses through the System
Preferences dialog in Control Builder.
Cause 2 A prior release version of the BOOTP Server is running.
Solution Be sure that only an R300 Experion PKS BOOTP Server service is running on the servers.
Only the latest BOOTP server can provide all of the necessary information for the current and
prior-release devices.
Cause 3 Not all FTE System Preferences for all Experion clusters have been configured with the same
information.
Solution Check that all FTE System Preferences are configured identically through the System
Preferences dialog in Control Builder.
Cause 4 The designated (S)NTP Servers are not properly configured and operating.
Solution See Setting up time synchronization in the Supplementary Installation Tasks Guide for
information.
Cause 5 The BOOTP Server service on both servers was not re-started after a configuration change.
Solution Re-start the BOOTP Server service on both servers through the Services dialog of the
Control Panel application.
Cause 6 The Windows Time Service on Experion servers was not re-started after NTP server was
enabled.
Solution Be sure the Windows Time Service is running on Experion servers. Normally, NTPSetup
takes care of this.

15.6.7 Isolated (lonely) Node

For redundant Series C FIM4/FIM8 pair, Fault Tolerant Ethernet (FTE) communications with partner and FTE
network are lost.

Diagnostic Check • The Primary Series C FIM4/FIM8 negotiates whether to initiate a switchover or not. If
the Secondary was known to be in better condition than the Primary at the time of fault
determination, then the Primary should fail so the Secondary will switchover. But, the
new Secondary (old Primary) still cannot restore FTE communications.
• The Secondary Series C FIM4/FIM8 should reboot once, in an attempt to restore
communications. The Primary Series C FIM4/FIM8 will be able to report the problem in
the Secondary. If the Secondary cannot restore FTE communications, it would still be
able to resynchronize over the redundancy link and be a partially functional backup.
Cause 1 The Secondary Series C FIM4/FIM8 is defective.
Solution Replace the Secondary Series C FIM4/FIM8 that initiated switchover when fault was
detected. See “Replacing failed Series C FIM4 CC- or CU-PFB401” on page 221 for details.
If Secondary Series C FIM4/FIM8 synchronizes after replacement, the removed Series C
FIM4/FIM8 is defective. Otherwise, go to Cause 2.
Cause 2 The Primary Series C FIM4/FIM8 is defective

254 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Solution Replace the Primary Series C FIM4/FIM8. See “Replacing failed Series C FIM4 CC- or CU-
PFB401” on page 221 for details.
If you can command synchronization after replacement, the removed Series C FIM4/FIM8 is
defective. Otherwise, go to Cause 3.
Cause 3 The redundant IOTA is defective.
Solution Replace the redundant IOTA. See “Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-
TFB401, CC-or CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412” on page 222 for
details.
If the Series C FIM4/FIM8 pair synchronize after IOTA replacement, The removed IOTA is
defective. Other wise, go to Cause 4.
Cause 4 There is a software problem.
Solution Contact our Solution Support Center (SSC).

15.6.8 Device Index setting does not match displayed value

The Device Index number shown in the Series C FIM4/FIM8's 4-character display does not match the value set
on the IOTA's binary-coded decimal rotary switches.

Diagnostic Check May be detected as a soft failure that triggers an alarm for the operator. The Device Index
setting is important only at initial application startup, when the Device Index number is used
to obtain the IP Address. The Device Index and IP Address are saved in non-volatile memory
and reused on subsequent application startups.
Cause 1 Someone changed the setting on the binary-coded decimal rotary switches on the IOTA.
Solution Change binary-coded decimal rotary switches to correct setting. See for more information.
Cause 2 The Primary or non-redundant Series C FIM4/FIM8 is defective
Solution Replace the Primary or non-redundant Series C FIM4/FIM8. See “Replacing failed Series C
FIM4 CC- or CU-PFB401” on page 221 for details.
If Device Index switch setting matches Device Index number in 4-character display upon
Series C FIM4/FIM8 power up, the removed Series C FIM4/FIM8 is defective. Otherwise, go
to Cause 3.
Cause 3 The redundant or non-redundant IOTA is defective.
Solution Replace the IOTA. See “Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401,
CC-or CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412” on page 222 for details.
If Device Index switch setting matches Device Index number in 4-character display upon
Series C FIM4/FIM8 power up, the removed IOTA is defective. Otherwise, go to Cause 4.
Cause 4 There is a software problem.
Solution Contact our Solution Support Center (SSC).

15.6.9 Duplicate Device Index setting

The FTE subsystem detects duplicate Device Index settings in separate nodes.

Diagnostic Check All nodes will stop tracking cable status for the detected duplicate Device Index value.
Communications will continue and will not impact system performance until there is a cable
fault. This fault will also be detected by the FTE System Management Tool.
A duplicate Device Index could cause a duplicate IP Address. In most cases, the duplicate IP
Address would be detected first and prevent the FTE diagnostic messages from being sent.
Cause 1 Have set binary-coded decimal rotary switches on separate IOTA's to same value.

255
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Solution Change binary-coded decimal rotary switches setting on one of the IOTA's to a unique value.
See for more information.

15.6.10 Device Index value is zero upon power up

The Series C FIM4/FIM8 4-character display shows a Device Index value of zero (#000).

Diagnostic Check Be sure binary-coded decimal rotary switches on the IOTA were not intentionally set to zero
to initiate a Device Index/IP Address reset.
Cause 1 Binary-coded decimal rotary switches set to zero.
Solution Change binary-coded decimal rotary switches to correct setting. See for more information.
Cause 2 The Primary or non-redundant Series C FIM4/FIM8 is defective
Solution Replace the Primary or non-redundant Series C FIM4/FIM8. See “Replacing failed Series C
FIM4 CC- or CU-PFB401” on page 221 for details.
If Device Index switch setting matches Device Index number in 4-character display upon
Series C FIM4/FIM8 power up, the removed Series C FIM4/FIM8 is defective. Otherwise, go
to Cause 3.
Cause 3 The redundant or non-redundant IOTA is defective.
Solution Replace the IOTA. See “Replacing IOTA DC-TFB402 or DC-TFB412, CC-or CU-TFB401,
CC-or CU-TFB411, CC- or CU-TFB402, or CC- or CU-TFB412” on page 222 for details.
If Device Index switch setting matches Device Index number in 4-character display upon
Series C FIM4/FIM8 power up, the removed IOTA is defective.

15.6.11 Device reload or replacement fails

The device load goes into infinite loop and the load dialog displays the Validating license message.

Diagnostic Check Be sure at least one VCR is free on the given Fieldbus segment.
Cause Fieldbus segment is configured for maximum VCRs (128).
Solution Delete a Control Module or device from the Monitoring tab in Control Builder to free a VCR.

15.6.12 Generation of excessive alarms

Diagnostic Check Alarms generating more frequently than expected.

Causes • Lack of understanding of device behaviors.
• Improper behavior of device.
• Improper behavior of alarm generation software in the FIM.
Solutions • Confirm the correct bit (s) in the device parameters are set for alarms by confirming
the configuration and viewing the corresponding parameters in the device block.
• Confirm to set the bit(s) based on the condition of the device.
• Check for the device documentation.
• Report to the device vendor.
• Investigate the root condition(s) by eliminating the alarm or change its priority or
criticality.
• To change the advanced alarming configuration at the device template level and then
reload the device(s).This solution is not ideal if the problem is isolated to only one or
few devices as other devices of the same type receives re-configuration when loaded.

256 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.6.13 Alarms not occurring when expected

Diagnostic Check Alarms do not occur when expected.

Causes • Correct bit(s) in the device parameters are set for the alarm.
• Bit(s) not set appropriately, based on the condition of the device.
• Improper behavior of alarm generation software in the FIM.
Solutions • Confirm the correct bit (s) in the device parameters are set for alarms by confirming
the configuration and viewing the corresponding parameters in the device block.
• Confirm to set the bit(s) based on the condition of the device.
• Check for the device documentation.
• Report to the device vendor.
• Investigate the root condition(s) by eliminating the alarm or change its priority or
criticality.
• To change the advanced alarming configuration at the device template level and then
reload the device(s).This solution is not ideal if the problem is isolated to only one or
few devices as other devices of the same type receives re-configuration when loaded.

15.6.14 Connected Fieldbus device is not detected by the FF link

Diagnostic check
Connected Fieldbus device is not detected by the FF link.

Cause
• If the device address provided by the vendor appears outside the range of polled node address. • •
• Slot Time Value might be too low.
• Physical layers issues such as, voltage, signal level, noise, and shield shorts and so on.

Solution
• Increase the Slot Time Value through the Network Management (LM) tab on the FFLink block parameters
configuration form.
• Temporarily set the NUN parameter to zero to see if the device appears on the link, and then restore NUN
after changing the device node address to valid setting
• Check for the physical layer connections as follows.
– Voltage at the device end must not exceed 10 V.
– Cable shield grounded at more than one location or not shielded.
– Screw terminals are not tight/loose wires.
– Only two terminators are used in the segment.
– Noise levels (any AC power cables near Fieldbus cable, loose connection, variable frequency drive,
high-powered equipment turned on/off).
For more detailed information, contact Honeywell TAC.

257
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

15.7 Getting further assistance

Related topics
“Other troubleshooting sources” on page 258
“Guidelines for requesting support” on page 259

15.7.1 Other troubleshooting sources

The following table lists other documents and sections that contain troubleshooting information for other
Experion subsystems.
All of these documents are available on PDF Collection. Some documents are also supplied as part of Station
Help. For documents that can be accessed directly from this page, click on the link, otherwise look for the
document within PDF Collection where RXXX represents the latest release number designation.

Document/Section Comments
Experion RXXX > Reference There is a separate interface reference for each type of
controller other than the Process Controller; for example,
the ASEA Interface Reference.
Most of these references contain an interface-specific
troubleshooting section.
Experion RXXX > Reference > TPS Integration Guide > Troubleshooting an integrated system that uses Experion
Troubleshooting "TPS Integration" option.
Experion RXXX > Reference > Control Builder Error Codes Describes error codes generated from within Control
Reference Builder.
Experion RXXX > Troubleshooting and Maintenance > The main repository for troubleshooting, maintenance and
Control Hardware Troubleshooting and Maintenance Guide repair of Process Controllers.
Experion RXXX > Configuration > DeviceNet Describes error codes generated from DeviceNet Interface
Implementation Guide > Troubleshooting DeviceNet Status Board.
Failures
Experion RXXX > Installation and Upgrades > Fault Troubleshooting FTE bridges.
Tolerant Ethernet Bridge Implementation Guide > Service >
Troubleshooting
Experion RXXX > Installation and Upgrades > Fault Troubleshooting FTE nodes.
Tolerant Ethernet Installation and Service Guide >
Troubleshooting FTE Nodes
Experion RXXX > Reference > Honeywell TDC 3000 Data Troubleshooting TDC 3000 Hiway problems.
Hiway Interface Reference > TDC error codes and
Troubleshooting
Experion RXXX > Configuration > Qualification and Troubleshooting QVCS.
Version Control System User Guide > QVCS
Troubleshooting
Experion RXXX > Operations > SafeView User's Guide > Describes the meaning of SafeView configuration errors.
Appendix D - SafeView Error Messages
Experion RXXX > Reference > Server Scripting Reference Describes the meaning of error messages in the server log
> Server scripting error messages specific to server scripting.
Experion RXXX > Reference > System Management Describes the meaning of System Management
Configuration Guide > Troubleshooting System Configuration errors.
Management

258 www.honeywell.com
 15 SERIES C FIM4/FIM8 TROUBLESHOOTING

Document/Section Comments
Experion RXXX > Reference > System Management Describes the meaning of SES Configuration errors.
Configuration Guide > Troubleshooting SES
Experion RXXX > Reference > System Management Describes the meaning of SPS Configuration errors.
Configuration Guide > Troubleshooting SPS
Experion RXXX > Planning and Design > Planning, Troubleshooting workstation nodes used in Experion and
Installation, and Service for WS360 TPN.

15.7.2 Guidelines for requesting support

If you cannot resolve a problem using this guide, you can request support from your Honeywell Solution
Support Center.
When requesting support, please supply as many relevant details as possible, including:
• Short summary of the problem
• Product Name and release.
• Recent changes, such as upgrades/service packs, to Experion software, Windows or other applications.
• Subsystem and its version/build, if the problem relates to a particular subsystem, such as Station or Quick
Builder. If the problem relates to Display Builder, please specify whether it is HMIWeb Display Builder
(for HMIWeb displays) or Display Builder (for DSP displays).
• Operating system, variant and service pack, for example 'Windows 2000 Server, SP5'.
• Instructions on how to reproduce the problem. If the problem is reproducible, please supply step-by-step
instructions - the more detailed the steps the better.
• Diagnostic package which contains any relevant logs.

259
15 SERIES C FIM4/FIM8 TROUBLESHOOTING

260 www.honeywell.com
16 Fieldbus integration with Experion control
reference

This section provides conceptual type information about the integration of Fieldbus devices with Experion
control functions. The following table lists the topics included in this section. If you are viewing this
information online, just click the topic title to jump to the information location.

Topic
“Series C FIM4/FIM8 handles data integration” on page 263
“About link object” on page 264
“Network management description” on page 265
“System management description” on page 266
“About device objects” on page 267
“About VFD objects” on page 268
“Type creation makes integration possible” on page 269
“Fieldbus device analog input integration” on page 270
“Fieldbus analog input data manipulation” on page 271
“Fieldbus device analog output or PID integration” on page 272
“Fieldbus analog output or PID data manipulation” on page 274
“Fieldbus device discrete input integration” on page 275
“Fieldbus discrete input data manipulation” on page 276
“Fieldbus device discrete output data integration” on page 277
“Fieldbus discrete output data manipulation” on page 278
“Interface connections summary” on page 279
“About SCM parameter interaction” on page 280
“Fieldbus status data details” on page 281
“Fieldbus status indications” on page 282

Related topics
“Series C FIM4/FIM8 handles data integration” on page 263
“About link object” on page 264
“Network management description” on page 265
“System management description” on page 266
“About device objects” on page 267
“About VFD objects” on page 268
“Type creation makes integration possible” on page 269
“Fieldbus device analog input integration” on page 270

261
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

“Fieldbus analog input data manipulation” on page 271

“Fieldbus device analog output or PID integration” on page 272
“Fieldbus analog output or PID data manipulation” on page 274
“Fieldbus device discrete input integration” on page 275
“Fieldbus discrete input data manipulation” on page 276
“Fieldbus device discrete output data integration” on page 277
“Fieldbus discrete output data manipulation” on page 278
“Interface connections summary” on page 279
“About SCM parameter interaction” on page 280
“Fieldbus status data details” on page 281
“Fieldbus status indications” on page 282

262 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.1 Series C FIM4/FIM8 handles data integration

The Series C Fieldbus Interface Module (FIM4/FIM8) functions as a dual network bridge using a dynamic data
cache to facilitate the exchange of data between the control communication network and the Fieldbus H1 links.
It supports both publish/subscribe and client/server communications methods to implement control connections
between Control Builder function blocks and Fieldbus function blocks. The Series C FIM capability includes
converting Control Builder value-status structure to Fieldbus value-status by mapping similar fields to one
another and defaulting others. This means the Experion system can monitor Fieldbus control functions, fully
integrate with control functions, or provide a combination that includes using Fieldbus based control as backup
for selected Experion system control functions.
The Series C FIM uses low and high-priority send queues to make sure that publish/subscribe data normally
used for control is processed before less important display access data. Publish/subscribe requests are placed in
the high-priority send queue and client/server requests are placed in the low one.

263
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.2 About link object

The link object represents one Fieldbus H1 link. It consists of Network Management and System Management
information, along with several application parameters related to link functions such as startup, shutdown, and
diagnostics.

264 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.3 Network management description

Network Management provides the following capabilities for managing the communication system of a
Fieldbus device.
• Loading a Virtual Communication Relationship (VCR) list or single entries in this list; (A VCR represents a
communication channel through the complete communication stack.)
• Configuring the communication stack;
• Loading the Link Schedule;
• Monitoring performance; and
• Monitoring fault detection.
The collection of managed variables is called the Network Management Information Base (NMIB).

265
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.4 System management description

System Management provides the following functions to coordinate the operation of various devices in a
distributed Fieldbus system.
• Assigning node addresses for devices;
• Synchronizing the application clock;
• Distributing application scheduling across the link; and
• Providing support for locating application tags.
It provides the needed facilities for bringing new devices on the link to an operational state and for controlling
the overall system operation. Information, which is used to control system management operation, is organized
as objects stored in the System Management Information Base (SMIB).

266 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.5 About device objects

The device object represents a physical device entity connected to the Fieldbus link. It provides access to the
device's Network Management (NM) and System Management (SM) parameters. The client/server VCR is
configured in the Series C FIM to access the Management Interface Base (MIB) of the device as soon as it joins
the network. The Control Builder does not configure the MIB VCR explicitly. Once the MIB VCR is configured
and opened, Series C FIM retrieves MIB information, SM directory, and NM directory. Knowledge of these
directories allows Series C FIM to transform writes into domain object variables into proper sequence of
domain download operations. The SM directory is also used to determine the number of application VFDs. The
NM directory is key in attempting to configure VCRs to access Function Block Application Process VFDs in
the device.

267
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.6 About VFD objects

The Virtual Field Device object represents an application VFD and provides parameter access to that VFD.
Each physical device may have one or more application VFDs. The Series C FIM attempts to build a client/
server VCR to every VFD in the device, when it is added to the network. If the VCR configuration is successful,
the Series C FIM obtains VFD and resource identification from the device's VFD. During device download, you
can overwrite VCR configuration used to access VFD parameters through the Control Builder application.

268 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.7 Type creation makes integration possible

The Fieldbus device Type function included with Control Builder makes integrating Fieldbus function blocks
with Control Builder ones possible. The Type function reads the manufacturer's DD for the Fieldbus device and
creates a device block type that is stored in the Control Builder Library tab. The device block type includes the
device's Fieldbus function blocks, so it can be configured and integrated with control strategies through Control
Builder.

269
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.8 Fieldbus device analog input integration

A user can functionally 'wire' the output from an Analog Input (AI) function block in a Fieldbus device residing
on an H1 link to the input of a regulatory control type function block contained in a Control Module in the
Experion Control Builder application. The Proportional, Integral, Derivative (PID) function block is a typical
regulatory control type function block.
The following simplified functional diagram shows how the output from an Analog Input function block in a
Fieldbus compliant transmitter is integrated with a PID function block in a Control Module that is assigned and
loaded to the CEE in the Control Processor Module (CPM).

Table 6: Integration of Fieldbus device analog input signal with Control Builder control strategy

270 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.9 Fieldbus analog input data manipulation

When the OUT from the Fieldbus analog input function block is wired to the PV input for a PID function block,
the Control Builder creates a CEE input agent to handle the analog input from the Fieldbus block. The block-
like input agent maps the data structure (DS-65) of the OUT parameter to the Control Builder PV with status
parameter. It interprets the value portion in Fieldbus terms and converts it to Control Builder representation. The
floating-point representation is identical, in most cases, but the Fieldbus +/-infinity value must be converted to a
Control Builder representation.
If the Fieldbus status byte indicates 'BAD', the value must be converted to Not a Number (NaN) for Control
Builder representation. The Fieldbus data quality of good, bad, and uncertain is mapped to the appropriate
Control Builder parameter of PVSTS, PVSTSFL.NORM, PVSTSFL.BAD, or PVSTSFL.UNCER.
The Fieldbus limit indications of no-limit, limited-low, limited-high, and constant are mapped to the same four
indications for Control Builder blocks.
The Fieldbus data sub status indicator maps only the limited number of sub status conditions that have
corresponding Control Builder indications. Note that the handshaking provided by the sub status associated with
Good [cascade] status is not supported from an upstream Fieldbus device. This means that control may not
originate in the field and cascade into the Controller.

271
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.10 Fieldbus device analog output or PID integration

A user can functionally 'wire' the output from a regulatory control type function block contained in a Control
Module in the Control Builder application to the input of an Analog Output (AO) or Proportional, Integral,
Derivative (PID) function block in a Fieldbus device residing on an H1 link. The Proportional, Integral,
Derivative (PID) function block is a typical Control Builder regulatory control type function block.
The following simplified functional diagram shows how the output from a PID function block in a Control
Module that is assigned and loaded to the CEE in the Control Processor Module (CPM) is integrated with an
Analog Output function block in a Fieldbus compliant device.

Table 7: Integration of Fieldbus device analog output signal with Control Builder control strategy

The following simplified functional diagram shows how the output from a PID function block in a Control
Module that is assigned and loaded to the CEE in the Control Processor Module (CPM) is integrated with a
cascaded Proportional, Integral, Derivative function block in a Fieldbus compliant device.

272 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Table 8: Integration of Fieldbus device PID control with Control Builder control strategy

273
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.11 Fieldbus analog output or PID data manipulation

When the Output from the PID function block is wired to the CAS_IN input for a Fieldbus Analog Output or
Proportional, Integral, Derivative function block, the Control Builder automatically creates a CEE output agent
to handle the analog output to the Fieldbus block. The block-like output agent maps the Cont OP with status
parameter to the Fieldbus data structure (DS-65) of the CAS_IN parameter. It interprets the value portion in
Experion terms and converts it to Fieldbus representation. The floating-point representation is identical, in most
cases, but the Experion +/-infinity value must be converted to a Fieldbus representation. If the status of OP is
'BAD', its value must be converted from NaN to zero (0.0) for Fieldbus representation or it may retain its
previous good value, as long as the Fieldbus status byte indicates 'BAD'.

WARNING
The Fieldbus Foundation specifications do not clearly state the expectations of Fieldbus devices for handling Not-
a-Number (NaN) values. This means that some may behave as the user desires and others may not.
If you compute a data type float + status value that uses data structure (DS-65), which includes all Foundation
Fieldbus inputs, outputs and some contained parameters, a resulting NaN value passed outbound through the
Series C FIM sets the status element to BAD and changes the value element from NaN to 0.0 (zero). If you
compute a data type float value, which includes many contained values such as alarm trip points, set points or
output limits, gains, and filter time values, a resulting NaN value that is to be passed outbound through the FIM4/
FIM8 will not be written and usually results in retention of the previous value. If the device would not behave in
the application as you desire, you must add appropriate function blocks or logic to test for and replace the NaN
with an acceptable value.

The CEE output agent also accepts a single BKCAL_OUT parameter with the Fieldbus data structure (DS-65)
and maps it to the BACKCALIN parameter of the PID block in Experion terms.

Attention
The Experion Control Builder application automatically makes the appropriate back calculation connections during
configuration and the connections are 'hidden' in Control Chart views.

Like the Series C FIM, the output agent supports both publish/subscribe and client/server communication
methods. The publish/subscribe method allows the Series C FIM to appear as a Fieldbus device on the H1 link.
The Series C FIM publishes the output (OP) for subscribing Fieldbus device resident blocks such as Analog
Output and Proportional, Integral, Derivative (PID) through their CAS_IN parameter input connection. This
connection is generally used when the downstream control block is in the Cas (cascade) mode. This means that
the Fieldbus block's BKCAL_OUT parameter is published by the downstream block and subscribed to by the
Series C FIM.
The client/server method allows the Series C FIM to appear as a computing device on the H1 link. The Series C
FIM writes the output (OP) to be read by Fieldbus device resident blocks such as Analog Output and
Proportional, Integral, Derivative (PID) through their RCAS_IN parameter input connection. This connection is
generally used when the downstream control block is in the RCas (Remote Cascade) mode. This means that the
Fieldbus block's BKCAL_OUT parameter is written by the downstream block and read by the Series C FIM.
The client/server method also allows the Series C FIM to function in a Direct Digital Control (DDC) mode or
the Remote Out mode in Fieldbus terms. In this case, the Series C FIM writes the output to be read by the
Fieldbus PID block though its ROUT_IN parameter input connection. In turn, the PID block publishes the
ROUT_OUT or back calculation output value for the subscribing Series C FIM.
The Control Builder data quality is converted to Fieldbus data quality. The Control Builder Good indication is
represented as Fieldbus Good (Cascade).
The Control Builder limit indications of no-limit, limited-low, limited-high, and constant are mapped to the
same four indications for Fieldbus.
The Control Builder control initialization indicators map only to the limited number of sub status conditions that
have corresponding indications in Fieldbus Good (Cascade).

274 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.12 Fieldbus device discrete input integration

A user can functionally 'wire' the output from a Discrete Input (DI) function block in a Fieldbus device residing
on an H1 link to the input of a Device Control (DEVCTL) function block or other block with a digital input
contained in a Control Module in the Experion Control Builder application.
The following simplified functional diagram shows how the output from an Discrete Input function block in a
Fieldbus compliant transmitter is integrated with a Device Control (DEVCTL) function block in a Control
Module that is assigned and loaded to the CEE in the Control Processor Module (CPM).

Table 9: Integration of Fieldbus device digital input signal with Control Builder control strategy

275
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.13 Fieldbus discrete input data manipulation

When the OUT from the Fieldbus Discrete Input function block is wired to the DI[n] input for a DEVCTL
function block, the Control Builder creates a CEE discrete input agent to handle the digital input from the
Fieldbus block. The block-like discrete input agent maps the data structure (DS-66) of the OUT parameter to the
Experion DI[n] with status parameter. It interprets the value portion in Fieldbus terms as a Boolean for Discrete
Input (DI) block and as the appropriate multi-state representation for special Fieldbus Device Control (DC)
block. The value is converted and represented in Control Builder at the output.
The discrete input agent accepts inputs from either a published parameter or a client/server read parameter,
depending upon the communication method used.
The Fieldbus data quality of good (cascade), good (non-cascade), bad, and uncertain is mapped to the
appropriate Control Builder parameter for good, bad, and uncertain.

276 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.14 Fieldbus device discrete output data integration

A user can functionally 'wire' the output from a discrete process or control value producing Control Builder
function block like Device Control to the input of a Discrete Output block in a Fieldbus device residing on an
H1 link.
The following simplified functional diagram shows how the output from a Device Control (DEVCTL) function
block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module (CPM) is
integrated with a Discrete Output function block in a Fieldbus compliant device.

Table 10: Integration of Fieldbus device digital output signal with Control Builder control strategy

277
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.15 Fieldbus discrete output data manipulation

When the DO[n] from the Device Control (DEVCTL) function block is wired to the CAS_IN_D input for a
Fieldbus Discrete Output function block, the Control Builder automatically creates a CEE output agent to
handle the discrete output to the Fieldbus block. The block-like output agent maps the Control Builder DO[n]
with status parameter to the Fieldbus data structure (DS-66) of the CAS_IN_D parameter. It interprets the value
portion in Control Builder terms and converts it to Fieldbus representation.
The CEE output agent also accepts a single BKCAL_OUT_D parameter with the Fieldbus data structure
(DS-66) and maps it to the BACKCALIN parameter of the DEVCTL block in Control Builder terms.
It sends the outgoing 'control signal' either to a subscribed parameter or a client/server written parameter
through the CAS_IN_D or RCAS_OUT_D connection. It can optionally receive the backcalculation signal from
either the corresponding published parameter or client/server read parameter.
The Control Builder data quality is converted to Fieldbus data quality. The Control Builder Good indication is
represented as Fieldbus Good (Cascade).
The Control Builder control initialization indicators map only to the limited number of sub status conditions that
have corresponding indications in Fieldbus Good (Cascade).

278 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.16 Interface connections summary

Since the downstream action with the upstream feedback is the same for all Fieldbus blocks, there are
essentially the following six types of interface connections through the FIM4/FIM8.
Analog process value into the FIM4/FIM8.
Discrete process value into the FIM4/FIM8.
Analog process output from the FIM4/FIM8.
Discrete process output from the FIM4/FIM8.
Analog process output from the FIM4/FIM8 with backcalculation feedback.
Discrete process output from the FIM4/FIM8 with backcalculation feedback.
Note that types 5 and 6 support publish/subscribe communications in Cascade mode or client/server
communications in Remote Cascade mode. And, the analog values can also be used in the Remote Out mode.
Fieldbus also supports direct device-to-device (peer-to-peer) publish/subscribe connections independent of the
FIM4/FIM8. The FIM4/FIM8 can also monitor (subscribe to) the data published between the functions blocks
of these Fieldbus devices.

279
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.17 About SCM parameter interaction

Sequential Control Module (SCM) Steps and Transitions can write to any contained parameter of a Fieldbus
function block. The value of a contained parameter can be configured, set by an operator, higher level device, or
calculated. For example, the GRANT_DENY parameter can be used to check access rights, the MODE_BLK
parameter can be used to request mode changes, and the RCAS_IN and RCAS_OUT parameters can be used to
control set points in the Remote Cascade mode.
If the contained parameter has a DS-65 or DS-66 data structure, you must use multiple SCM Step outputs to
write to the different fields in the parameter's data structure. For example, if you use a Step output to write to the
SP parameter of a Fieldbus PID block, when it is in Auto mode, you will need Step outputs for the related
parameter attributes of value, status, sub status and limits, as defined by its structure. A typical SCM write SP
scenario would include the following actions.
• Transition checks if Target MODE of the Fieldbus block is AUTO.
• Step output sets Target MODE to AUTO, if required.
• Step output sets SP value and GOOD (Non Cascade) status.
• Optional Step output to set SP Limits.
• Optional Transition to verify that the value got stored in the Fieldbus device.
The SCM will issue a fail alarm, if the store fails for any reason.

Attention
Avoid SCM configurations that would push a NaN (Not a Number) value as an output to a Fieldbus device. If this is
not possible, be sure to test the field device to observe how it reacts to the possible NaN value.

280 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.18 Fieldbus status data details

According to Fieldbus Foundation specifications, every Fieldbus function block input and output connection
must support a status byte that provides the following status indications.
• Data Quality (usability)
• Bad Data Cause
• Degraded Data Cause
• Limit Conditions
• Cascade Control Initialization, Rejection
• Fault-State Initiation, Indication
• Local Override Indication
• Worst Case Alarm Indication
• Upstream Block Class Identification
The status byte structure consists of a 2-bit quality, most significant bit, field; a 4-bit sub status field; and a 2-bit
limits, least significant bit, field. The following table provides a breakdown of bit assignments for general
reference. The value of the quality field determines the applicable sub status field indication.

Bit Quality Sub status, if Quality field is Limits

BAD UNCERTAIN GOOD (Non- GOOD (Cascade)*
Cascade)*
0 BAD Data Non-Specific Non-Specific Non-Specific Non-Specific No Limits
Quality
1 UNCERTAIN Configuration Last Usable Value Active Block Initialization Low Limit
Data Quality Error Alarm Acknowledge (IA)
2 GOOD (Non- Not Connected Substitute Active Initialization Request High Limit
Cascade) Data Advisory (IR)
Quality Alarm
3 GOOD (Cascade) Device Failure Initial Value Active Critical Not Invited (NI) Constant
Data Quality Alarm
4 Sensor Failure Sensor Conversion Unacknowledg Not Selected (NS)
Not Accurate ed Block
Alarm
5 No Engineering Unit Unacknowledg Do Not Select (DNS)
Communication, Range Violation ed Advisory
with Last Usable Alarm
Value
6 No Sub-Normal Unacknowlege Local Override (LO)
Communication, d Critical
with no Last Alarm
Usable Value
7 Out-Of-Service Fault-State Active
(FSA)
8 Initiate Fault-State
(IFS)

* The Good (non-cascade) sub status is used by output connections for Fieldbus blocks such as Analog Input
and Discrete Input. The Good (cascade) sub status is used by output connections for Fieldbus blocks such as
PID. Both of these sub statuses are converted to the single system data quality of Good.

281
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

16.19 Fieldbus status indications

The following tables include a list of possible display indications associated with a given Fieldbus status and
definitions of related sub statuses.

Fieldbus Status Byte 1-Char 12-Char Independent Status Field

Suffix
Quality Sub status Limits
BAD Non-Specific No Limits B Bad
BAD Non-Specific Low Limit B Bad,LowLimit
BAD Non-Specific High Limit B Bad,HiLimit
BAD Non-Specific Constant B Bad,Constant
BAD Configuration Error No Limits B Bad,Config
BAD Configuration Error Low Limit B Bad,Config,L
BAD Configuration Error High Limit B Bad,Config,H
BAD Configuration Error Constant B Bad,Config,C
BAD Not Connected No Limits B Bad,NotCon
BAD Not Connected Low Limit B Bad,NotCon,L
BAD Not Connected High Limit B Bad,NotCon,H
BAD Not Connected Constant B Bad, NotCon,C
BAD Device Failure No Limits B Bad,DevFail
BAD Device Failure Low Limit B Bad,DevFail,L
BAD Device Failure High Limit B Bad,DevFail,H
BAD Device Failure Constant B Bad,DevFail,C
BAD Sensor Failure No Limits B Bad,SensFail
BAD Sensor Failure Low Limit B Bad,SnFail,L
BAD Sensor Failure High Limit B Bad,SnFail,H
BAD Sensor Failure Constant B Bad,SnFail,C
BAD No Comm, Last No Limits B Bad,LUValue
Usable
BAD No Comm, Last Low Limit B Bad,LUV,L
Usable
BAD No Comm, Last High Limit B Bad,LUV,H
Usable
BAD No Comm, Last Constant B Bad,LUV,C
Usable
BAD No Comm, No Last No Limits B Bad,NoComm
Usable
BAD No Comm, No Last Low Limit B Bad,NoComm,L
Usable
BAD No Comm, No Last High Limit B Bad,NoComm,H
Usable
BAD No Comm, No Last Constant B Bad,NoComm,C
Usable
BAD Out-Of-Service No Limit B Bad,OutSvc

282 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Fieldbus Status Byte 1-Char 12-Char Independent Status Field

Suffix
Quality Sub status Limits
BAD Out-Of-Service Low Limit B Bad,OutSvc,L
BAD Out-Of-Service High Limit B Bad,OutSvc,H
BAD Out-Of Service Constant B Bad,OutSvc,C
UNCERTAIN Non-Specific No Limits U Uncertain
UNCERTAIN Non-Specific Low Limit U Uncertain,L
UNCERTAIN Non-Specific High Limit U Uncertain,H
UNCERTAIN Non-Specific Constant U Uncertain,C
UNCERTAIN Last Usable No Limits U Unc,LastOK
UNCERTAIN Last Usable Low Limit U Unc,LastOK,L
UNCERTAIN Last Usable High Limit U Unc,LastOK,H
UNCERTAIN Last Usable Constant U Unc,LastOK,C
UNCERTAIN Substitute No Limits U Unc,Subst
UNCERTAIN Substitute Low Limit U Unc,Subst,L
UNCERTAIN Substitute High Limit U Unc,Subst,H
UNCERTAIN Substitute Constant U Unc,Subst,C
UNCERTAIN Initial Value No Limits U Unc,Initial
UNCERTAIN Initial Value Low Limits U Unc,Init,L
UNCERTAIN Initial Value High Limits U Unc,Init,H
UNCERTAIN Initial Value Constant U Unc,Init,C
UNCERTAIN Sensor Conversion No Limit U Unc,NotAcc
Not Accurate
UNCERTAIN Sensor Conversion Low Limit U Unc,NotAcc,L
Not Accurate
UNCERTAIN Sensor Conversion High Limit U Unc,NotAcc,H
Not Accurate
UNCERTAIN Sensor Conversion Constant U Unc,NotAcc,C
Not Accurate
UNCERTAIN Engineering Unit No Limits U Unc,Range
Range Violation
UNCERTAIN Engineering Unit Low Limit U Unc,Range,L
Range Violation
UNCERTAIN Engineering Unit High Limit U Unc,Range,H
Range Violation
UNCERTAIN Engineering Unit Constant U Unc,Range,C
Range Violation
UNCERTAIN Sub-Normal No Limits U Unc,SubNorm
UNCERTAIN Sub-Normal Low Limit U Unc,SubNrm,L
UNCERTAIN Sub-Normal High Limit U Unc,SubNrm,H
UNCERTAIN Sub-Normal Constant U Unc,SubNrm,C
GOOD (Non- Non-Specific No Limits <blank> <blank>
Cascade)
GOOD (Non- Non-Specific Low Limit L Low Limit
Cascade)

283
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Fieldbus Status Byte 1-Char 12-Char Independent Status Field

Suffix
Quality Sub status Limits
GOOD (Non- Non-Specific High Limit H High Limit
Cascade)
GOOD (Non- Non-Specific Constant C Constant
Cascade)
GOOD (Non- Active Block Alarm No Limits A Alarm-Block
Cascade)
GOOD (Non- Active Block Alarm Low Limit A Alarm-Blck,L
Cascade)
GOOD (Non- Active Block Alarm High Limit A Alarm-Blck,H
Cascade)
GOOD (Non- Active Block Alarm Constant A Alarm-Blck,C
Cascade)
GOOD (Non- Active Advisory No Limits A Alarm-Advis
Cascade) Alarm
GOOD (Non- Active Advisory Low Limit A Alarm-Advis,L
Cascade) Alarm
GOOD (Non- Active Advisory High Limit A Alarm-Advis,H
Cascade) Alarm
GOOD (Non- Active Advisory Constant A Alarm-Advis,C
Cascade) Alarm
GOOD (Non- Active Critical Alarm No Limits A Alarm-Crit
Cascade)
GOOD (Non- Active Critical Alarm Low Limit A Alarm-Crit,L
Cascade)
GOOD (Non- Active Critical Alarm High Limit A Alarm-Crit,H
Cascade)
GOOD (Non- Active Critical Alarm Constant A Alarm-Crit,C
Cascade)
GOOD (Non- Unacknow-ledged No Limits A Alm-U-Block
Cascade) Block Alarm
GOOD (Non- Unacknow-ledged Low Limit A Alm-U-Blck,L
Cascade) Block Alarm
GOOD (Non- Unacknow-ledged High Limit A Alm-U-Blck,H
Cascade) Block Alarm
GOOD (Non- Unacknow-ledged Constant A Alm-U-Blck,C
Cascade) Block Alarm
GOOD (Non- Unacknow-ledged No Limits A Alm-U-Advis
Cascade) Advisory Alarm
GOOD (Non- Unacknow-ledged Low Limit A Alm-U-Advs,L
Cascade) Advisory Alarm
GOOD (Non- Unacknow-ledged High Limit A Alm-U-Advs,H
Cascade) Advisory Alarm
GOOD (Non- Unacknow-ledged Constant A Alm-U-Advs,C
Cascade) Advisory Alarm
GOOD (Non- Unacknow-ledged No Limits A Alm-U-Crit
Cascade) Critical Alarm

284 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Fieldbus Status Byte 1-Char 12-Char Independent Status Field

Suffix
Quality Sub status Limits
GOOD (Non- Unacknow-ledged Low Limit A Alm-U-Crit,L
Cascade) Critical Alarm
GOOD (Non- Unacknow-ledged High Limit A Alm-U-Crit,H
Cascade) Critical Alarm
GOOD (Non- Unacknow-ledged Constant A Alm-U-Crit,C
Cascade) Critical Alarm
GOOD (Cascade) Non-Specific No Limits <blank> <blank>
GOOD (Cascade) Non-Specific Low Limit L Low Limit
GOOD (Cascade) Non-Specific High Limit H High Limit
GOOD (Cascade) Non-Specific Constant C Constant
GOOD (Cascade) Acknowledge No Limit InitAck
Initialization (IA)
GOOD (Cascade) Acknowledge Low Limit InitAck,L
Initialization (IA)
GOOD (Cascade) Acknowledge High Limit InitAck,H
Initialization (IA)
GOOD (Cascade) Acknowledge Constant InitAck,C
Initialization (IA)
GOOD (Cascade) Request Initialization No Limits R ReqInit
(IR)
GOOD (Cascade) Request Initialization Low Limit R ReqInit,L
(IR)
GOOD (Cascade) Request Initialization High Limit R ReqInit,H
(IR)
GOOD (Cascade) Request Initialization Constant R ReqInit,C
(IR)
GOOD (Cascade) Not Invited (NI) No Limits N NotInvited
GOOD (Cascade) Not Invited (NI) Low Limit N NotInvited,L
GOOD (Cascade) Not Invited (NI) High Limit N NotInvited,H
GOOD (Cascade) Not Invited (NI) Constant N NotInvited,C
GOOD (Cascade) Not Selected (NS) No Limits N NotSelected
GOOD (Cascade) Not Selected (NS) Low Limit N NotSelectd,L
GOOD (Cascade) Not Selected (NS) High Limit N NotSelectd,H
GOOD (Cascade) Not Selected (NS) Constant N NotSelectd,C
GOOD (Cascade) Local Override (LO) No Limits O OverrideLocl
GOOD (Cascade) Local Override (LO) Low Limit O OverrideLc,L
GOOD (Cascade) Local Override (LO) High Limit O OverrideLc,H
GOOD (Cascade) Local Override (LO) Constant O OverrideLc,C
GOOD (Cascade) Fault-State Active No Limits F FaultState
(FSA)
GOOD (Cascade) Fault-State Active Low Limit F FaultState,L
(FSA)
GOOD (Cascade) Fault-State Active High Limit F FaultState,H
(FSA)

285
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Fieldbus Status Byte 1-Char 12-Char Independent Status Field

Suffix
Quality Sub status Limits
GOOD (Cascade) Fault-State Active Constant F FaultState,C
(FSA)
GOOD (Cascade) Initiate Fault-State No Limits <blank> InitFaultSt
(IFS)
GOOD (Cascade) Initiate Fault-State Low Limit L LoLim,InitFS
(IFS)
GOOD (Cascade) Initiate Fault-State High Limit H HiLim,InitFS
(IFS)
GOOD (Cascade) Initiate Fault-State Constant C Const,InitFS
(IFS)

16.19.1 Sub status Definitions for Quality Status

Quality Sub status Description

Bad Non-Specific There is no specific reason why the value is bad. Used for
propagation.
Configuration Error Set if the value is not useful because there is some other
problem with the block, depending on what a specific
manufacturer can detect.
Not Connected Set if this input is required to be connected and is not.
Device Failure Set if the source of the value is affected by a device failure.
Sensor Failure Set it the device can determine this condition. The Limits
define which direction has been exceeded.
No Communication, with last Set if this value had been set by communication, which has
usable value now failed.
No Communication, with no Set if there has never been any communication with this value,
usable value since it was last Out of Service.
Uncertain Non-Specific There is no specific reason why this value is uncertain. Used
for propagation.
Last Usable Value Whatever was writing this value has stopped. (This happens
when one disconnects an input.)
Substitute Set when the value is written when the block is Out of Service.
Initial Value Set when the value of an input parameter is written while the
block is Out of Service.
Sensor Conversion Not Set if the value is at one of the sensor limits. The limits define
Accurate which direction has been exceeded. Also, set if the device can
determine that the sensor has reduced accuracy, in which case
no limits are set.
Engineering Unit Range Set if the value lies outside of the range of values defined for
Violation this parameter. The limits define which direction has been
exceeded.
Sub-Normal Set if value derived from multiple values has less than the
required number of Good sources.
Good (Non-Cascade) Non-Specific There is no specific reason why the value is good. No error or
special condition is associated with this value.
Active Block Alarm Set if the value is good and the block has an active Block
alarm.

286 www.honeywell.com
 16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

Quality Sub status Description

Active Advisory Alarm Set if the value is good and the block has an active alarm with a
priority less than 8.
Active Critical Alarm Set if the value is good and the block has an active alarm with a
priority greater than or equal to 8.
Unacknowledged Block Set if the value is good and the block has an unacknowledged
Alarm Block alarm.
Unacknowledged Advisory Set if the value is good and the block has an unacknowledged
Alarm alarm with a priority of less than 8.
Unacknowledged Critical Set if the value is good and the block has an unacknowledged
Alarm alarm with a priority greater than or equal to 8.
Good (Cascade) Non-Specific There is no specific reason why the value is good. No error or
special condition associated with this value.
Initialization Acknowledge The value is an initialized value from a source (cascade input,
remote-cascade in, and remote-output in parameters).
Initialization Request The value is an initialization value a source (back calculation
input parameter), because the lower loop is broken or the mode
is wrong.
Not Invited The value is from a block, which does not have a target mode
that would use this input. This covers all cases other than Fault
State Active, Local Override, and Not Selected. The target
mode can be the next permitted mode of higher priority in the
case of shedding a supervisory computer.
Not Selected The value is from a Control Selector that has not selected the
corresponding input. This tells the upper block to limit in one
direction, not initialize.
Do Not Select The value is from a block that should not be selected by a
control selection block, due to conditions in or above the block.
As an option, a block may generate this output status if its
actual mode is not Auto or not Cascade.
Local Override The value is from a block that has been overridden by a local
key switch or is a complex AO/DO with interlock logic active.
The failure of normal control must be propagated to a PID
block for alarm and display purposes. This also implies Not
Invited.
Fault State Active The value is from a block that has Fault State active. The
failure of normal control must be propagated to a PID block for
alarm and display purposes. This also implies Not Invited.
Initiate Fault State The value is from a block that wants its downstream output
block to go to Fault State. This is determined by a block option
to initiate Fault State if the status of the primary input and/or
cascade input goes Bad.

287
16 FIELDBUS INTEGRATION WITH EXPERION CONTROL REFERENCE

288 www.honeywell.com
17 Control mode interaction reference

This section provides conceptual type information about Fieldbus block mode interaction with Experion control
modes. The following table lists the topics included in this section. If you are viewing this information online,
just click the topic title to jump to the information location.

Topic
“Fieldbus block modes versus control modes” on page 290
“Control mode priorities and indications” on page 292
“Rotary Switch Model versus Toggle Switch Model” on page 293
“Display indications and mode calculation” on page 294
“Mode change conditions” on page 295
“Access control through GRANT_DENY parameter” on page 297

Related topics
“Fieldbus block modes versus control modes” on page 290
“Control mode priorities and indications” on page 292
“Rotary Switch Model versus Toggle Switch Model” on page 293
“Display indications and mode calculation” on page 294
“Mode change conditions” on page 295
“Access control through GRANT_DENY parameter” on page 297

289
17 CONTROL MODE INTERACTION REFERENCE

17.1 Fieldbus block modes versus control modes

Every Fieldbus function block including Resource and Transducer blocks contain the MODE_BLK parameter.
This structured parameter consists of the Actual, Target, Permitted, and Normal modes. The eight possible
modes are described in the “About modes of operation” on page 322 paragraph in the “Standard Function
Blocks” on page 321 section in this book.
For use within the Experion system, the structure of the MODE_BLK parameter is expanded to add MODE to
the existing Actual, Target, Permitted, and Normal modes as outlined in the following table.

Control Mode Structure Data Type Description

MODE Enumeration Write Only
Experion system style mode enumeration
MAN, AUTO, CAS, NORMAL, BCAS, NONE
MODE.TARGET Enumeration Read/Write
Target mode
OOS, MAN, AUTO, CAS, RCAS, ROUT
MODE.ACTUAL Enumeration Read Only
Actual Mode
OOS, IMAN, LO, MAN, AUTO, CAS, RCAS, ROUT
MODE.PERMITTED Bitstring Read/Write
Permitted mode
MAN, AUTO, CAS, RCAS, ROUT
OOS is always permitted
MODE.NORMAL Enumeration Read/Write
Normal mode
MAN, AUTO, CAS, RCAS, ROUT
OOS is not Normal

The Experion system uses the name MODE instead of MODE_BLK and its enumeration set is identical to that
used in Fieldbus. Mode is a write only parameter and the /FIM8 will reject all reads. The FIM4/FIM8 captures
all writes to MODE and maps valid changes to MODE.TARGET. If the value NORMAL is written to the
MODE.TARGET, the FIM4/FIM8 replaces it with the value from MODE.NORMAL. If a new
MODE.NORMAL value is entered, it is validated against the MODE.PERMITTED values. The OOS mode is
not an acceptable normal mode.
When a new MODE.PERMITTED value is entered, the FIM4/FIM8 forces the OOS mode to be permitted.
Only a user with an access level of Engineer is allowed to put a block into its OOS mode or to return the block
to an operating mode. This means a user must have an access level of Engineer to put a block in Man, Auto,
Cas, Rcas, or Normal, if the blocks current target mode is OOS. When a mode is changed, the FIM4/FIM8
clears the GRANT_DENY.GRANT parameter bits. It is standard Experion system behavior to take a grant back
after an operator changes a mode relative to its mode attribute (MODATTR) parameter.
The following table shows how control modes are mapped to Fieldbus ones.

Control Mode Fieldbus Mode Comment

MAN Man
AUTO Auto
CAS Cas

290 www.honeywell.com
 17 CONTROL MODE INTERACTION REFERENCE

Control Mode Fieldbus Mode Comment

NORMAL Normal When setting as target mode, read MODE.NORMAL value and write to
MODE.TARGET.
BCAS Error! Not used in Fieldbus blocks. Attempt to set to target is illegal.
NONE Error! Not used in Fieldbus blocks. Attempt to set to target is illegal.

291
17 CONTROL MODE INTERACTION REFERENCE

17.2 Control mode priorities and indications

The following table shows the 2-character and 4-character mode indications to be used in operating displays and
lists the mode priorities based on several interpretations. The Priority Order interpretation is based on the Out-
of-Service mode being serviced over all others. The Control Order interpretation is based on the traditional
control engineer's concept that Cascade is a higher mode of operation than Automatic, Automatic is a higher
mode of operation than Manual, and so on. The Dominance Order interpretation is based on Fieldbus
Foundation special rules for modes dominating one another. For example, Out-of-Service dominates over
Manual, Manual dominates over Remote Out, and Remote Out dominates over Remote Cascade. This is
relevant, if multiple mode bits are set in the target (or normal) mode bitstrings.
A block uses the concept of priority to compute an actual mode that is different from the target mode, and to
determine if the particular actual mode allows write access.

Mode Mode Abbreviation Priority Interpretation

2-Char 4-Char Priority Order Control Order Dominance Order
(8=highest) (8=highest) (6=Highest)
Out-of-Service OS OOS 8 1 6
Initialization Manual IM IMan 7 2 -
Local Override LO LO 6 3 -
Manual M Man 5 4 5
Auto A Auto 4 5 1
Cascade C Cas 3 6 2
Remote Cascade RC RCas 2 7 3
Remote Output RO ROut 1 8 4

While every type or block instance does not need to support all eight modes, all eight indicator bits are present
in the database. The mode bit assignments are listed below for reference.

Bit Mode
0 (LSB) = Remote Output (ROut)
1 = Remote Cascade (RCas)
2 = Cascade (Cas)
3 = Automatic (Auto)
4 = Manual (Man)
5 = Local Override (LO)
6 = Initialization Manual (IMan)
7 (MSB) = Out of Service (OOS)

292 www.honeywell.com
 17 CONTROL MODE INTERACTION REFERENCE

17.3 Rotary Switch Model versus Toggle Switch Model

The Fieldbus Foundation supports both the Rotary Switch and the Toggle Switch models of mode operation.
The Rotary Switch model supports only one mode request at a time. For example, an operator can request OOS,
Man, Auto, Cas, RCas, or ROut. It has no memory of previous target modes.
The Toggle Switch model supports more than one mode request at a time. For example, an operator can request
Manual override of Cascade, Manual override of Remote Cascade, and so on.
Experion supports the Rotary Switch model as well as the following two instances of the Toggle Switch model.
• An operator may request the Cas mode at the same time the RCas mode is requested
• An operator may request the Cas mode at the same time the ROut mode is requested
Experion also ignores the following illegal mode combinations as defined by the Fieldbus Foundation.
• If ROut is set, RCas may not be set. If it is set, it will be ignored.
• The Auto and Man bits must always be of opposite states. If neither Auto nor Man or both are set, and the
ROut, RCas, or Cas mode is set, Auto mode will be assumed with Man cleared. Likewise, If neither Auto
nor Man or both are set, and neither ROut, RCas, nor Cas mode is set, Man mode will be assumed with Auto
cleared. For the OOS mode, the Man bit should be set unless it is not permitted. If Man is not permitted, the
Auto bit should be set unless it is not permitted. If neither Auto nor Man is permitted, the OOS bit should be
set.

Attention
An operator needs an access level of ENGR or higher to invoke the OOS mode or to return a block to an in-service
mode.

The Experion system adheres to the following additional rules for setting Fieldbus target mode bits for its
MODE supported subset of combinations.

Fieldbus Rule
Mode
OOS When setting as the target mode, obtain the target mode, preserve the Auto and Man bits, set the OOS bit,
and optionally reset all the other bits. Reject the request, if the access level is not ENGR or higher.
IMan This is a Read Only parameter and cannot be set as the target mode. Never set the IMan as the target mode.
LO This is a Read Only parameter and cannot be set as the target mode. Never set the LO as the target mode.
Man When setting as the target mode, set the Man bit and reset all the other bits. Reject the request, if the
current mode is OOS and the access level is not ENGR or higher.
Auto When setting as the target mode, set the Auto bit and reset all the other bits. Reject the request, if the
current mode is OOS and the access level is not ENGR or higher.
Cas When setting as the target mode, set both Cas and Auto bits and reset all the other bits. Reject the request,
if the current target mode is OOS and the access level is not ENGR or higher.
RCas When setting as the target mode, set both RCas and Auto bits and reset all the other bits. Reject the request,
if the current target mode is OOS and the access level is not ENGR or higher.
ROut When setting as the target mode, set both ROut and Auto bits and reset all the other bits. Reject the request,
if the current target mode is OOS and the access level is not ENGR or higher.
Normal When setting as the target mode, read the MODE.NORMAL value and write to the MODE.TARGET.
Reject the request, if the current target mode is OOS and the access level is not ENGR or higher.

293
17 CONTROL MODE INTERACTION REFERENCE

17.4 Display indications and mode calculation

The Fieldbus mode indications for actual mode and composite actual/target modes will appear in the following
formats on Station displays.

Format Description Examples

a Satisfied in mode a; actual same as OOS, MAN, AUTO, CAS, RCAS, ROUT
target.
a (t) In mode a; not satisfied in higher target MAN (A), CAS (RC), IM (A), LO (CAS), AUTO (M), CAS
mode t. (M)

The block mode calculation of actual mode considers the input parameter status attributes, input values, and
resource state as represented graphically in the figure below.

Figure 35: Block mode calculation summary

294 www.honeywell.com
 17 CONTROL MODE INTERACTION REFERENCE

17.5 Mode change conditions

The following table provides a list of conditions, which will change the mode in order of priority with Good
(Non-Cascade) status on input parameter as the lowest priority.

Input Parameters Status Mode Parameter - Target Attribute Value

Attributes, Inputs Values and
Resource States
Out of Service (OOS) Manual Auto-matic Cascade (CAS) Remote Remote
(MAN) (Auto) Cascade Output
(RCAS) (ROUT)
All input parameters have Good OOS MAN AUTO CAS RCAS ROUT
Status or Uncertain status with
option set to treat Uncertain as
Good.
Remote cascade in has BAD OOS MAN AUTO CAS Shed based ROUT
status. on Shed
Option
Remote out in has BAD status. OOS MAN AUTO CAS RCAS Shed based
on Shed
Option
Cascade input has a status OOS MAN AUTO Shed to next RCAS ROUT
attribute of BAD permitted
mode*
Target mode is RCAS and N/A N/A N/A N/A Actual mode N/A
remote cascade in does not have from last
status of Good - Initialization execution or
Acknowledge; and actual mode AUTO
attribute last execution was not
RCAS.
Target mode is ROUT and N/A N/A N/A N/A N/A Actual mode
remote out in status is not Good from last
- Initialization Acknowledge; execution or
and actual mode attribute last MAN or
execution was not ROUT. mode as
determined
by Shed
Option
Target mode is CAS and cascade N/A N/A N/A Actual mode N/A N/A
input status is not Good - from last
Initialization Acknowledge and execution or
actual mode attribute last AUTO or
execution was not CAS MAN
Status attribute of primary input OOS MAN MAN MAN MAN ROUT
parameter is BAD or Uncertain
with option to treat Uncertain as
BAD and bypass not set
Status attribute of back OOS IMAN IMAN IMAN IMAN IMAN
calculation input parameter is
BAD

295
17 CONTROL MODE INTERACTION REFERENCE

Input Parameters Status Mode Parameter - Target Attribute Value

Attributes, Inputs Values and
Resource States
Out of Service (OOS) Manual Auto-matic Cascade (CAS) Remote Remote
(MAN) (Auto) Cascade Output
(RCAS) (ROUT)
Status attribute of back OOS IMAN IMAN IMAN IMAN IMAN
calculation input parameter
Good - fault state active, local
override, not invited, or
initialization request
Tracking is enabled, track input OOS LO LO LO LO LO
active and track override manual
is Enabled.
Tracking is enabled, initiated OOS MAN LO LO LO LO
and track override manual is
Disabled.
Fault State is active in an output OOS LO LO LO LO LO
function block
If target mode has changed from - MAN or MAN or MAN or MAN or MAN or
OOS to another mode since the evaluated evaluated mode evaluated evaluated evaluated
block was last executed. mode mode mode mode
Resource state as reflected in the OOS OOS OOS OOS OOS OOS
resource block parameter
resource state is Standby.

*Shed to the next lowest priority that is permitted and supported by the available inputs.

296 www.honeywell.com
 17 CONTROL MODE INTERACTION REFERENCE

17.6 Access control through GRANT_DENY parameter

Every Fieldbus function block includes a GRANT_DENY parameter. It allows users to Grant and Deny access
permission to groups of function block parameters by other devices. The following table summarizes the
attributes for the Grant and Deny elements of the parameter.

Element and Bit Attribute Description

GRANT_DENY.GRANT:0 Program Operations Grants permission to higher level device to change the
target mode, set point or output of a block, depending on
block mode.
GRANT_DENY. GRANT:1 Tune Grants permission to higher level device to change tuning
parameters of the block.
GRANT_DENY.GRANT:2 Alarm Grants permission to higher level device to change alarm
parameters of the block
GRANT_DENY.GRANT:3 Local Operations Grants permission to a local operator's panel or hand-held
device to change target mode, set point, or output of the
block, depending on block mode.
GRANT_DENY.DENY:0 Program Operations Turns off Program Operations permission grant.
GRANT_DENY.DENY:1 Tune Turns off Tune permission grant.
GRANT_DENY.DENY:2 Alarm Turns off Alarm permission grant.
GRANT_DENY.DENY:3 Local Operations Turns off Local Operations grant.

The Grant selections are mutually exclusive. If you select Program Operations, the Local Operations selection is
turned off. If Local Operations is selected, neither an operator nor a high level device (program) has the right to
modify a parameter value of the block. Note that access by another function block is always granted and is
independent of GRANT_DENY selections. Also, an operator can always change the MODE of a block with
Program or Local Operations Granted. When an operator changes the MODE, it automatically resets all four
Grants to off.

297
17 CONTROL MODE INTERACTION REFERENCE

298 www.honeywell.com
18 Fieldbus Link Active scheduler and Link Master
functions

This section provides conceptual type information about Fieldbus Link Active Scheduler and Link Master
functions. The following table lists the topics included in this section. If you are viewing this information
online, just click the topic title to jump to the information location.

Topic
Link Active Scheduler (LAS) and Link Master
“Link Schedule” on page 301
“Function block execution schedule” on page 302

All links must have a Link Active Scheduler (LAS). The LAS operates at the data link layer as the bus arbiter
for the link. It provides the following functions.
• Recognizes and adds new devices to the link.
• Removes non-responsive devices from the link
• Distributes Data Link and Link Scheduling time on the link. The data link layer synchronizes the network-
wide Data Link Time. Link scheduling time is a link specific time represented as an offset from Data Link
Time. It is used to indicate when the LAS on each link begins and repeats its schedule. System Management
uses it to synchronize function block execution with the data transfers scheduled by the LAS.
• Polls devices for buffered data at scheduled transmission times.
• Distributes a priority-driven token to devices between scheduled transmissions.
Any device on the link may become the LAS as long as it is capable. The devices that are capable of becoming
the LAS are called Link Master devices. All other devices are referred to as Basic devices.
The FIM4/FIM8 is Link Master capable and supports both primary and backup link schedules. It is designated
as the primary Link Master. It is always assigned the lowest network address.
Upon startup or failure of the existing LAS, the Link Master capable devices on the link bid to become the LAS.
The Link Master that wins the bid begins operating as the LAS immediately upon completion of the bidding
process. The Link Master capable device with the lowest address usually wins the bid. Link Masters that do not
become the LAS act as basic devices when viewed by the LAS. They also act as LAS backups by monitoring
the link for failure of the LAS, and by bidding to become the LAS when a LAS failure is detected.

299
18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

Attention
If the LAS is too large to fit in the active Link Master capable device, the user must reconfigure the device to become
a Basic one through Control Builder, and restart the device to initiate the change.
Most Link Master capable devices can only support one sub schedule and cannot support blocks that are running two
different macrocycles. Each macrocycle includes one sub schedule. Each sub schedule includes sequences that specify
the start time of each element in the sequence. The elements are actual publications that initiate schedule operations.
Devices have predefined limits on the number of sub schedules that can exist per LAS and the number of sequences
that can exist in a sub schedule. If the number of sub schedules and/or sequences in the current schedule (backup LAS)
exceed the Link Master capable device's predefined limits, a load of the device through Control Builder will generate
load errors identifying sub schedule problems. In this case, the user must reconfigure the device to become a Basic
one through Control Builder, and restart the device to initiate the change. Otherwise, if the FIM4/FIM8 fails, the
potential for a 'no schedule' condition exists. Since the schedule is cleared from the Link Master capable device upon
the detection of load errors, it cannot function as the backup LAS without a schedule.

Related topics
“Link Schedule” on page 301
“Function block execution schedule” on page 302
“About using mixed macrocycles on FF Links” on page 304

300 www.honeywell.com
 18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

18.1 Link Schedule

The Link Schedule is the overall schedule for the link. It includes both the link data transfer and the device
function block execution schedules. A Link Schedule is provided for the FIM4/FIM8 interface port for each
link. A backup Link Schedule is provided for all Link Master capable devices on the link.
The link data transfer schedule is derived from the portion of the link schedule that deals with publication of
parameters. The Control Builder (CB) provides a default link schedule of publications and function block
execution phasing based on the function block connections in the user configured control strategy. The basis for
the link schedule is this link's content from all currently loaded Control Modules (CM). Execution phasing is
based solely on function block existence in the CM. Order of execution is based on the order in CM
(ORDERINCM) parameter for each block. Publications are based on inter-device function block connections
and device to Experion system or Experion system to device function block connections. The following
publication rules apply.
• Function block publications appear in the link data transfer schedule in the order specified by their
ORDERINCM parameters. (Duplicate values of ORDERINCM may produce indeterminate ordering of
those blocks involved.)
• If the user changes the sequence of execution order for function blocks in a schedule, the ORDERINCM
parameters of the involved function blocks are appropriately adjusted.
• Publication of each output is scheduled immediately after execution of the function block that produces the
value, considering inter-publication delays and potential conflicts.
• Blocks publish, if their output is connected to an input in another device or the FIM4/FIM8.
• No unneeded time delay is allowed in the default link data transfer schedule.
• The macrocycle is the least common multiple of the execution periods of all the CMs involved in the link
data transfer schedule.
Note that users will be able to add extra time before and after the execution of a Fieldbus function block through
the Pre-execution delay (PREXEGAP) and the Post execution delay (POSTEXEGAP) parameters that appear
on the block configuration forms in Control Builder. This means users can adjust the schedule to achieve such
actions as forcing multiple AI blocks to execute at the same time (even though they must publish serially).

301
18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

18.2 Function block execution schedule

The function block execution schedule is derived from the portion of the link schedule that deals with starting
the execution of each function block or FB_START indications. The link schedule provides only those entries
that pertain to the blocks residing in a given Fieldbus device. While device function blocks may be
synchronized to the link schedule, it is not a Fieldbus Foundation mandated feature. They may run
asynchronously.
The block execution time can be broken into these three phases.
Preprocessing - Snap of parameter values
Execution - Function block outputs are determined
Post processing - Block output values, alarm and associated trend parameters are updated.
Since input parameter values used by a function block must not change during execution, a copy of the input
parameter values is captured or snapped at the beginning of execution. Also, since block outputs to other blocks
must be time coincident, the output values are only updated at the completion of the function block execution.
The block algorithm execution phase is always executed in the following ordered sequence as shown in the
following figure.
Determine the actual mode attribute of the mode parameter. This calculation is based on the target mode and the
status attributes of input parameters.
Calculate the set point, if the Set Point parameter is defined for the function block. The calculation of working
set point is based on the actual mode, set point input parameters such as cascade and remote cascade, and any
backward path input status. Also, the value of the controlled parameter, process variable, may be used for set
point tracking. The resulting set point is shown in the set point parameter.
Execute the control or calculation algorithm to determine the value and status of output parameters in the
forward path. The conditions that determine the status attribute of output parameters. The value attributes of the
block's input parameters and contained parameters, the actual mode and the working set point are used in this
algorithm. Also, where defined by the block profile, some blocks may use the status of selected inputs. In
general, the calculation of actual mode and the use of actual mode in the algorithm accounts for the status of
critical inputs.
Calculate output parameters in the backward path. This phase applies only to output blocks and calculation
blocks designed for use in a cascade path.

Tip
A Fieldbus device whose period of function block execution is an integer factor of the macrocycle of the link will
have a function block execution schedule prepared that has the optimal shorter cycle. For example, if the control
strategy includes a CM with a 2 second period for a temperature loop, a second CM with a 1 second period for a
pressure loop, and a third CM with a 250 millisecond period for a flow loop, a 1 second macrocycle can be
downloaded to the device that contains functions blocks used in the 1 second and 250 ms CMs.

302 www.honeywell.com
 18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

Figure 36: Algorithm execution phase sequence

303
18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

18.3 About using mixed macrocycles on FF Links

18.3.1 About macrocycles

The macrocycle period, which is the period of the overall schedule, is equal to the largest configured FF
execution period from the CMs that contribute to the link. Blocks in the CMs with shorter FF execution periods
will have repeated executions within the overall schedule.

18.3.2 About mixed macrocycles

In Experion, an FF link can have devices for which the function blocks are assigned to different CMs. In
addition, CMs can have individually configured execution periods. This means that a link schedule may be built
using blocks and data publications executing at different rates. This is known as mixed macrocycle.
Although not commonly used, the need for mixed macrocycles may arise in the following scenarios:
• A link must be configured with a large number of devices.
• A link must be configured with devices that support a large number of blocks.
In these scenarios, it is recommended to use a single, relatively slow, macrocycle. However, in some cases it
may be necessary to use slower monitoring blocks on the same link as faster control blocks.

Attention
Using mixed macrocycles increases the risk of mode shed. Honeywell recommends avoiding the use of mixed
macrocycles. However, if the use of mixed-macrocycles in Experion is absolutely necessary or has already been
commissioned, appropriate precautions needs to taken to avoid mode shed.

18.3.3 Scenarios during which mode shed occurs when using mixed macrocycles
When mixed macrocycles are used, the mode shed may occur in the following scenarios:
• The link schedule may pause and restart from the beginning (at the next scheduled macrocycle start time)
during certain events. For example,
the schedule is re-loaded (CM load) or
redundancy switchover has occurred.
• The amount of schedule pause is dependent on when the event occurs, and may include almost the full
schedule period.
• When the schedule is paused, publications cease although block executions continue.
• Blocks that subscribe to these publications count the number of times publication is not received.
• The number of missed publications exceeds the configured stale count limit. This is most likely to happen on
the faster-executing blocks on a mixed-macrocycle link.
Note: The default setting for stale count is 3. However, this is configurable by the user, as required. If the ratio
of fast-to-slow execution rates in a mixed macrocycle is higher than the configured stale count limit, then a
mode shed is likely to occur.
For example, consider the following scenario.
The link schedule contains blocks running at both 500 ms and 2 second periods. This means that the ratio of
execution rates is 4:1.
The stale count limit in all CMs is set to 3.
In such a scenario, if an event occurs that restarts the link schedule, then the faster-executing blocks (blocks
with execution period of 500ms) may miss all of their inputs, depending on exactly when the link schedule was
restarted. In addition, this may result in mode shed and disrupt control.

304 www.honeywell.com
 18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

Attention
If the use of mixed-macrocycles is absolutely necessary or has already been commissioned, you must adhere to the
following guidelines to avoid mode shed.
• For each link with a mixed-macrocycle schedule, calculate the ratio of fast-to-slow execution rates.
• Set the stale count limit for the faster CMs to be slightly higher than this ratio.
For example, if the ratio of execution rate is 4:1, then set the stale count limit to 5.

305
18 FIELDBUS LINK ACTIVE SCHEDULER AND LINK MASTER FUNCTIONS

306 www.honeywell.com
19 Tags, Addresses, and Live List Reference

This section provides conceptual type information about Fieldbus tags, addresses, and live list functions. The
following table lists the topics included in this section. If you are viewing this information online, just click the
topic title to jump to the information location.

Topic
“Tag and address assignments” on page 308
“About Fieldbus address assignments in Control Builder” on page 309
“Live list and uncommissioned devices” on page 310

Related topics
“Tag and address assignments” on page 308
“About Fieldbus address assignments in Control Builder” on page 309
“Live list and uncommissioned devices” on page 310

307
19 TAGS, ADDRESSES, AND LIVE LIST REFERENCE

19.1 Tag and address assignments

Before a Fieldbus device can actively join a network it must be assigned a name and data link address. Device
names are system specific identifiers called physical device tags (PD_TAG).
The PD_TAGs may be assigned by the vendor or through the System Management Kernel (SMK), normally in
an off-line configuration environment so devices without tags are kept off the operational network.
The SMK for devices without tags are set to the Uncommissioned state and connected to the bus at one of four
default device addresses. The Data Link Layer specifies these default addresses as non-visitor node addresses.
The following figure shows the general allocation of data link layer addresses to field devices.

Figure 37: Summary of address allocations for Fieldbus devices

Attention
• Temporary devices such as handheld interfaces are not assigned tags or addresses. They join the network through
one of four data link visitor addresses reserved for them in the data link layer protocol.
• Note that the Experion system will show address assignments in Decimal notation rather than Hexadecimal in
Control Builder configuration forms and Station displays. The address range in Decimal is 0 to 255 and 0 to FF in
Hexadecimal.

308 www.honeywell.com
 19 TAGS, ADDRESSES, AND LIVE LIST REFERENCE

19.2 About Fieldbus address assignments in Control Builder

The Fieldbus Interface Module will be given 16 as its assigned address. The preferred address range for
Fieldbus devices is 20 to 40 decimal (14 to 28 hexadecimal). This provides the most optimized default network
range where the first unused node address (FUN) is 41decimal (29 hexadecimal) and the number of unused
addresses (NUN) is 206. We recommend that the Fieldbus device designated as the backup Link Master be
given 21decimal (15 hexadecimal) as its assigned address.

309
19 TAGS, ADDRESSES, AND LIVE LIST REFERENCE

19.3 Live list and uncommissioned devices

FOUNDATION Fieldbus defines a live list as a 32-byte bitstring (256 bits) where each bit represents an
address of the Fieldbus network. A set bit at a particular bit number means that a device is present at that
address. The LAS of the network owns the live list and maintains it as part of its operation.
The FIM4/FIM8 constantly monitors the live list for each Fieldbus link connected to it. When the LAS for the
link recognizes a new device at a default address, it adds it to its live list according to the data link layer
procedures. The FIM4/FIM8 detects the change in the live list and makes a connection to the new
uncommissioned device. It gathers the following information from the device to be passed to Control Builder.

Name Description Data Type Access

PdTag Physical Device Tag 32-byte string Read/Write
Address Device Address Unsigned8 Read/Write
DevID Globally unique Device Identifier 32-byte string Read Only
Honeywell Honeywell name string 32-byte string Read Only
ModelName Model Name string 32-byte string Read Only
Rev Application Revision 32-byte string Read Only
ManufID Manufacturer Identifier Unsigned32 Read Only
DevType Device Type code Unsigned16 Read Only
DevRev Device Revision Unsigned8 Read Only
DdRev DD Revision Unsigned8 Read Only
Capability Level Device Capability Level Unsigned8 Read Only

Control Builder uses the device information to create an item in its Monitoring tree to represent the new
uncommissioned device on the given link. Users can now view and configure pertinent information for the
uncommissioned device through appropriate Link block and device block configuration forms in Control
Builder.

Tip
The FIM4/FIM8 must be configured and loaded through Control Builder before you can view it and its links
through the Monitoring tab of Control Builder.

310 www.honeywell.com
20 Notification Scheme Reference

This section provides conceptual type information about how Fieldbus alarms relate to Experion system alarms.
The following table lists the topics included in this section. If you are viewing this information online, just click
the topic title to jump to the information location.

Topic
“Fieldbus versus Experion Alarm Priorities” on page 312
“Advanced Alarming” on page 312

Related topics
“Fieldbus versus Experion Alarm Priorities” on page 312
“Fieldbus Alarm Conditions” on page 314

311
20 NOTIFICATION SCHEME REFERENCE

20.1 Fieldbus versus Experion Alarm Priorities

The Fieldbus alarms will be closely integrated with the existing Experion notification system. The Experion
server will handle FIM4/FIM8 alarms in the same way it handles Control Processor ones. But, the Fieldbus
devices themselves own their alarm data and generate the alarms, clears, and events. Function blocks that
support alarming also allow each different alarm condition to be disabled. It is always good to check that the
disables are set appropriately.
Fieldbus devices use 0 to 15 as numeric priorities for alarm reporting. Priority 0 clears any alarm status, clearing
reports and preventing new ones from being issued. Priority 1 clears any alarm reports and prevents new ones
from being issued, but allows the alarm status to continue to be observed in the ALARM_SUM and alarm
object status. Priorities 2 through 7 are considered advisory and priorities 8 through 15 are considered critical in
Fieldbus. Experion alarms use Journal, Low, High and Urgent as priorities with a sub-priority of 0 to 255. The
following table shows how Fieldbus priorities are mapped to Experion priorities and severities.

Fieldbus Alarm Priority Experion Alarm Priority Experion Alarm Severity

0 (Can never be seen by FIM4/FIM8 or above) (Can never be seen by FIM4/FIM8 or above)
1 (Can never be seen by FIM4/FIM8 or above) (Can never be seen by FIM4/FIM8 or above)
2 Journal 2
BLOCK_ERR bit 14 (Event System Only)
(power-up)
BLOCK_ERR bit 15 (Out-
of-Service)
2 System Level Diagnostic (High) 2
All other bitstring
indications:
(BLOCK_ERR bits 0-13,
XD_ERROR bits 16-25)
2 (User selected) Journal 2
3 Low 3
4 Low 4
5 Low 5
6 Low 6
7 Low 7
8 High 8
9 High 9
10 High 10
11 High 11
12 Urgent 12
13 Urgent 13
14 Urgent 14
15 Urgent 15

20.1.1 Advanced Alarming

FF devices are configured with a feature of configuring diagnostic parameters to generate alarms. The alarms
that are generated are based on the status of these parameters in a device. Individual bits in these strings are

312 www.honeywell.com
 20 NOTIFICATION SCHEME REFERENCE

selected and configured as a condition to generate the alarms. Therefore, the conditions that are used for
generating manufacturer-specific alarms are contained in bitstring parameters of FF Transducer blocks and
Resource blocks. FIM monitors all the parameters in the condition to generate corresponding alarms, which are
activated.
Note: You can configure alarm conditions and save in the ERDB.
Considerations
Following are some of the considerations for configuring diagnostic parameters.
• Each condition is associated with at most 5 parameters of a device.
• You can select any combination of available bits.
• Different conditions can utilize the same or different parameters/bits.
• You can enable and disable the conditions at the template level and device level from both Project and
Monitoring modes.

313
20 NOTIFICATION SCHEME REFERENCE

20.2 Fieldbus Alarm Conditions

Fieldbus devices provide both process and device related alarms. The process alarms are associated with process
variable conditions and they are reported as process alarms into the Experion system. The device alarms are
associated with actual device conditions or processes within the block as indicated by BLOCK_ERR and
XD_ERROR bitstring alarms. These alarms are reported as device or system alarms into the Experion
notification system. The following table summarizes the possible Fieldbus alarm enumerations and lists the
alarm/event type identification to be used in the alarm summary and event summary displays in Station.

Attention
Only the first alarm in an overlapping series of alarms associated with BLOCK_ERR and XD_ERROR bitstring
alarms is reported due to a flaw in the Fieldbus Foundation Specifications regarding the alert state machine. This has
been reported to the Fieldbus Foundation through their Action Request system and the Foundation has agreed to
permit future devices to issue alerts on changes to the status of any element of these bitstring alarms.
If no more than one of the bits is set at a time, the alarms are reported and cleared properly

Tip
Fieldbus alarm functions do not support rate of change (ROC) alarms. ROC alarms can only be generated in
applications that use Control Builder Data Acquisition blocks for input signal conditioning.

Enumeration Description Alarm/Event Type

UNDEF Undefended Alarm No Action
LO Low Limit Alarm PVLO
HI High Limit Alarm PVHI
LO LO Critical Low Limit Alarm PVLOLO
HI HI Critical High Limit Alarm PVHIHI
DV LO Deviation Low Alarm DEVLO
DV HI Deviation High Alarm DEVHI
DISC Standard Discrete Alarm OFFNORM
DISC Standard Discrete Alarm CHNGOFST
DISC DevCtl Fail Alarm FBDCFAIL
DISC DevCtl Accept Alarm FBDCACC
DISC DevCtl Ignore Alarm FBDCIGN
BLOCK BLOCK_ERR: 0 (Other (LSB) FFOTHER
(Unspecified Error)
BLOCK BLOCK_ERR: 1 (Block Configuration Error) FFBLKCFG
(Block Config Error)
BLOCK BLOCK_ERR: 2 (Link Configuration Error) FFLNKCFG
(Link Config Error)
BLOCK BLOCK_ERR: 3 (Simulate Active) FFSIMACT
(Simulation Activ)
BLOCK BLOCK_ERR: 4 (Local Override) FFLO
(Local Override)
BLOCK BLOCK_ERR: 5 (Dev Fault State Set) FFFLSAFE
(Device Fault State)

314 www.honeywell.com
 20 NOTIFICATION SCHEME REFERENCE

Enumeration Description Alarm/Event Type

BLOCK BLOCK_ERR: 6 (Dev Needs Maintenance Soon) FFDEVNMS
(Maintain Device Soon)
BLOCK BLOCK_ERR: 7 (I/P Failure or PV BAD Status) FFINFL
(Device Input Failure)
BLOCK BLOCK_ERR: 8 (O/P Failure) FFOUTFL
(Device Output Fail)
BLOCK BLOCK_ERR: 9 (Memory Failure) FFMEMFL
(Memory Failure)
BLOCK BLOCK_ERR: 10 (Lost Static Data) FFLSTDTA
(Static Data Lost)
BLOCK BLOCK_ERR: 11 (Lost NV Data) FFLNVDTA
(Non-Vol Data Lost)
BLOCK BLOCK_ERR: 12 (Readback Check Failed) FFRBCKFL
(Readback Check Fail)
BLOCK BLOCK_ERR: 13 (Dev Needs Maintenance Soon) FFDEVNMS
(Maintain Device Now)
BLOCK BLOCK_ERR: 14 (Power Up) FFPWRUP
(Powered-Up)
BLOCK BLOCK_ERR: 15 (Out-Of-Service) FFOOS
(Out-Of-Service)
BLOCK XD_ERROR: 16 (Unspecified Error) TBUNSPEC
(Unspecified TB Error)
BLOCK XD_ERROR: 17 (General Error) TBGENRAL
(General Error)
BLOCK XD_ERROR: 18 (Calibration Error) TBCALERR
(Calibration Error)
BLOCK XD_ERROR: 19 (Configuration Error) TBCFGERR
(Configuration Error)
BLOCK XD_ERROR: 20 (Electronics Failure) TBELECFL
(Electronics Failure)
BLOCK XD_ERROR: 21 (Mechanical Failure) TBMECHFL
(Mechanical Failure)
BLOCK XD_ERROR: 22 (I/O Failure) TBIOFL
(I/O Failure)
BLOCK XD_ERROR: 23 (Data Integrity Error) TBDTAERR
(Data Integrity Error)
BLOCK XD_ERROR: 24 (Software Error) TBSWERR
(Software Error)
BLOCK XD_ERROR: 25 (Algorithm Error) TBALGERR
(Algorithm Error)
UPDATE TB Static Data Update Event TBSTCHNG

315
20 NOTIFICATION SCHEME REFERENCE

Enumeration Description Alarm/Event Type

UPDATE FB Static Data Update Event FBSTCHNG
(Static Revision)
WRITE Write Protect Change Alarm RBWPCHNG
(Write Lock)
UPDATE Link Object Update Event FBLOCHNG
(Link Object Changed)
UPDATE Trend Object Update Event No Action

20.2.1 Loading alarm conditions

After configuring the alarm conditions, you must load the saved conditions to the FIM. Conditions are loaded
only after loading the device. For more information on loading the conditions, see “Loading a Series C FIM4/
FIM8 and its links” on page 134

Attention
• Before loading, turn off the device blocks as it can affect the execution of associated control strategies.
• When you perform device like replacement, advanced alarming conditions are also loaded from Project mode
configuration when the device is loaded.
• When you change the device's template with an unlike template replacement, all advanced alarm configuration
settings are loaded from the replacement template.
• When you commission the device using Commission Without Reconfiguration, the device automatically loads the
settings from the selected device template. However, if there are multiple templates that match the device profile
and revision information, you must select the template before commissioning.

20.2.2 Alarm server operation

User defined conditions are configured to generate the System Alarm.
System Alarm: System alarms appear in the System Status Display. The alarm attributes are set as follows:

Attribute Value
Source Device tag
Condition DIAG
Priority User specified (Low, High, Urgent)
Severity Set to '00'
Description The name of the condition configured
Criticality User specified criticality (Failed, Maintenance, Check,
OffSpec)

316 www.honeywell.com
21 Fieldbus Technology Overview

This section provides an overview of Foundation Fieldbus technology concepts. The following table lists the
topics included in this section. If you are viewing this information online, just click the topic title to jump to the
information location.

Topic
“Open communications architecture” on page 318
“Communication layer description” on page 319
Standard Function Blocks
“Device Descriptions and Block Parameters” on page 344

Related topics
“Open communications architecture” on page 318
“Communication layer description” on page 319
“Standard Function Blocks” on page 321
“Device Descriptions and Block Parameters” on page 344

317
21 FIELDBUS TECHNOLOGY OVERVIEW

21.1 Open communications architecture

Foundation Fieldbus is an enabling technology for dynamically integrating dedicated field devices with
digitally based control systems. It defines how all 'smart' field devices are to communicate with other devices in
the control network. The technology is based upon the International Standards Organization's Open System
Interconnection (OSI) model for layered communications.
As shown in the following figure, OSI layer 1 is the Physical Layer, OSI layer 2 is the Data Link Layer, and
OSI layer 7 is the application layer or the Fieldbus Message Specification. A Fieldbus Access Sublayer maps
the Fieldbus Message Specification onto the Data Link Layer. Fieldbus does not use OSI layers 3 to 6, and
layers 2 and 7 form the Communication Stack. Also, the OSI model does not define a User Application, but the
Fieldbus Foundation does.

Figure 38: OSI versus Fieldbus communication model.

318 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.2 Communication layer description

The following table provides a summarized description of the communication layers that make up the
Foundation Fieldbus. The Fieldbus Foundation maintains a complete library of detailed reference
specifications including a Technical Overview and Wiring and Installation Guides.
Please refer to “Fieldbus network wiring and installation references” on page 21 for a list of available
documents or visit the Fieldbus Foundation web site http://www.Fieldbus.org/ for additional details and
ordering data.

Layer Functional Description Associated Terms

Physical Defines the transmission medium for Fieldbus signals and the message H1, 31.25 kbit/s signal rate
conversion tasks to/from the Communication Stack.
H1 Link
Based on the Manchester Biphase-L Encoding technique, so a Foundation
H1 Segment
Fieldbus (FF) device interprets a positive transition in the middle of a bit
time as logical '0' and a negative transition as logical '1'. HSE, High Speed Ethernet
Complies with existing International Electrotechnical Commission (IEC
1158-2) and the Instrumentation, Systems, and Automation Society (ISA
S50.02) physical layer standards. And, it can be used with existing 4 to
20mA wiring.
Data Link Defines how messages are transmitted on a multi-drop network. It uses a Compel Data (CD)
(DLL) deterministic centralized bus scheduler called a Link Active Scheduler message
(LAS) to manage access to the Fieldbus. It controls scheduled and
Pass Token (PT) message
unscheduled communications on the Fieldbus in a publish/subscribe
environment. Time Distribution (TD)
message
Identifies device types as Basic Device, Link Master, or Bridge. A Link
Master device type can become a Link Active Scheduler (LAS) for the Live List
network. Link Active Scheduler
(LAS)
Fieldbus Defines the types of services used to pass information to the Fieldbus Virtual Communication
Access Message Specification layer. The types of services are defined as Virtual Relationship (VCR)
Sublayer (FAS) Communication Relationships (VCR).
The VCR types are Client/Server, Report Distribution, and Publisher/
Subscriber. The Client/Server type handles all operator messages. The
Report Distribution type handles event notification and trend reports. The
Publisher/Subscriber type handles the publishing of User Application
function block data on the network.
Fieldbus Defines how Fieldbus devices exchange User Application messages across Object Dictionary (OD)
Message the Fieldbus using a set of standard message formats. It uses object
Virtual Field Device
Specification descriptions that are stored in an object dictionary (OD) to facilitate data
(VFD)
(FMS) communication. The OD also includes descriptions for standard data types
such as floating point, integer, Boolean, and bitstring. Network Management
Information Base (NMIB)
A Virtual Field Device (VFD) mirrors local device data described in the
OD. A physical device may have more than one VFD. System Management
Information Base (SMIB)
Provides these communication services to standardize the way the User
Applications such as function blocks communicate over the Fieldbus -
Context Management, Object Dictionary, Variable Access, Event, Upload/
Download, and Program Invocation.
Uses a formal syntax description language called Abstract Syntax Notation
1 (ASN-1) to format FMS messages and applies special behavioral rules for
certain types of objects.

319
21 FIELDBUS TECHNOLOGY OVERVIEW

User Defines blocks to represent different types of application functions. The Resource block
Application or three types of blocks are the Resource block, the Function block, and the
Function block
Function Block Transducer block. See the illustration that follows this table.
Application Transducer block
The Resource block is used to describe characteristics of the Fieldbus device
Process
such as the device name, manufacturer, and serial number. Each Fieldbus Link Objects
(FBAP)
device requires one Resource block. Trend Objects
The Function block is used to define the specific characteristics of the Alert Objects
process control function. The Fieldbus Foundation provides a set of pre-
defined function blocks. A single Fieldbus device can include many View Objects
Function blocks to achieve the desired control functionality. See the next View 1 - Operation
section Standard Function Blocks for more information. Dynamic
The Transducer block is used to interface Function blocks with local input/ View 2 - Operation Static
output devices. They read sensors and command outputs, and contain
information such as calibration date and sensor type. One Transducer block View 3 - All Dynamic
is usually included for each input or output Function block. View 4 - Other Static
These associated objects are also defined in the User Application: Link
Objects, Trend Objects, Alert Objects, and View Objects. They provide
linking between internal Function block inputs and outputs, trending of
Function block parameters, reporting of alarms and events, viewing of
predefined block parameter sets through one of four defined views.
The four defined views are View 1 - Operation Dynamic, View 2 -
Operation Static, View 3 - All Dynamic, and View 4 - Other Static.

Figure 39: User Application (or Function Block Application Process) based on blocks.

320 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.3 Standard Function Blocks

WARNING
• The Fieldbus Foundation specifications do not clearly state the expectations of Fieldbus devices for handling
Not-a-Number (NaN) values. This means that some may behave as the user desires and others may not.
• If you compute a data type float + status value that uses data structure (DS-65), which includes all
Foundation Fieldbus inputs, outputs and some contained parameters, a resulting NaN value passed outbound
through the FIM4/FIM8 sets the status element to BAD and changes the value element from NaN to 0.0
(zero). If you compute a data type float value, which includes many contained values such as alarm trip points,
set points or output limits, gains, and filter time values, a resulting NaN value that is to be passed outbound
through the FIM4/FIM8 will not be written and usually results in retention of the previous value. If the device
would not behave in the application as you desire, you must add appropriate function blocks or logic to test for
and replace the NaN with an acceptable value.

21.3.1 Blocks for basic control functionality

The key to Fieldbus interoperability is the User Application or Function Block Application Process (FBAP) that
defines standard function blocks that can reside in field devices and be interconnected as a distributed process
control system. A function block is a named entity that has inputs, outputs, and parameters. It performs certain
functions that operate on its inputs and produce outputs in accordance with its assigned parameters. The
Fieldbus Foundation Function Blocks are similar in nature to the Function Blocks used to build control
strategies in the Control Builder application in the Experion system.
The Fieldbus Foundation provides the standard Function Blocks listed below for basic control functionality.
They also support additional blocks for more complex applications. Please refer to the applicable Fieldbus
Foundation specification for more information about these additional blocks.

Function Block Abbreviation Class

Analog Input AI Input
Analog Output AO Output
Bias/Gain BG Control
Control Selector CS Control
Discrete Input DI Input
Discrete Output DO Output
Manual Loader ML Control
Proportional/Derivative PD Control
Proportional/Integral/Derivative PID Control
Ratio RA Control

Function blocks make it possible to build a control loop using Fieldbus devices that include the appropriate
Function block types. For example, a pressure transmitter that contains an Analog Input and Proportional/
Integral/Derivative blocks can be used with a valve containing an Analog Output block to form a control loop,
as shown in the following figure.

321
21 FIELDBUS TECHNOLOGY OVERVIEW

Figure 40: Using Function Blocks in Fieldbus devices to form a control loop.

21.3.2 About modes of operation

Every Function block includes a mode parameter with configured permitted modes. This structured parameter is
composed of the actual mode, the target mode, the permitted mode, and the normal mode. The normal mode is
the desired operating mode. The actual mode reflects the mode used during block execution. The target mode
may be set and monitored through the mode parameter. The permitted mode defines the allowable target mode
settings. The following table provides a summary of the available modes of operation and their effect on
operation.

Mode Abbreviation Operation Effect

Out of Service OOS The block is not being evaluated. The output is maintained at the
last value, an assigned fault state value -last value or configured
fault state value. Set Point is maintained at last value.
Initialization Manual IMan The block output is being set in response to the back-calculation
input parameter status. When status is no path to the final output
element, control blocks must initialize to provide for bumpless
transfer, when the condition clears. The Set Point may be
maintained or initialized to the Process Variable parameter value.
Local Override LO Applies to control and output blocks that support a track input
parameter. Also, manufacturers may provide a local lockout switch
on the device to enable the Local Override mode. The block output
is being set to track the value of the track input parameter. The
algorithm must initialize to avoid a bump, when the mode switches
back to the target mode. The Set Point may be maintained or
initialized to the Process Variable parameter value.
Manual Man The block is not being calculated, although it may be limited. The
operator directly sets it through an interface device. The algorithm
must initialize to avoid a bump, when the mode switches. The Set
Point may be maintained, initialized to the Process Variable
parameter value, or initialized to the Set Point value associated with
the previous (retained) target mode. .

322 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Mode Abbreviation Operation Effect

Automatic Auto The block's normal algorithm uses a local Set Point value to
determine the primary output. An operator may set the value of the
Set Point through an interface device.
Cascade Cas The block's normal algorithm uses a Set Point value fed through the
Cascade input parameter from another block to determine the
primary output value.
Remote-Cascade RCas The block's Set Point is being set by a Control Application running
on an interface device through the remote-cascade in parameter.
The block's normal algorithm uses this Set Point to determine the
primary output value. The block maintains a remote-cascade out
parameter to support initialization of the control application, when
the block mode is not remote-cascade.
Remote-Out ROut The block's output is being set by a Control Application running on
an interface device through the remote-output in parameter. The
algorithm must initialize to avoid a bump, when the mode switches.
The block maintains a remote-output out parameter to support
initialization of the Control Application, when the block mode is
not remote-output. The Set Point may be maintained or initialized
to the Process Variable parameter value.

21.3.3 Analog Input block

Figure 41: Functional schematic for Analog Input function block.

Description The AI function block takes the input data from a Transducer block and calculates an
output to be fed to other Fieldbus function blocks. A functional schematic of the block is
shown in the previous illustration for reference.
Function Notes • Supports Out of Service (OOS), Manual (Man), and Automatic (Auto) modes.
• The XD_SCALE units code must match the channel units code, or the block will
remain in OOS mode after being configured.
• The OUT_SCALE is normally the same as the transducer, unless the L_TYPE is set
to Indirect or Ind Sqr Root, then the OUT_SCALE determines the conversion from
FIELD_VAL to the output.
• If the mode is Auto, the PV is the value the block puts in OUT.
• If the mode is Man, an operator can write a value to OUT.
• The SIMULATE parameter is for testing purposes only and always initializes in the
disabled state.

323
21 FIELDBUS TECHNOLOGY OVERVIEW

Equation Options • FIELD_VAL = 100 x (channel value - EU@0%) / (EU@100% - EU@0%)

[XD_SCALE]
• Direct: PV = channel value
• Indirect : PV = (FIELD_VAL / 100) x (EU@100% - EU@0%) + EU@0%
[OUT_SCALE]
• Ind Sqr Root: PV = sqrt(FIELD_VAL / 100) x (EU@100% - EU@0%) + EU@0%
[OUT_SCALE]
Parameters ACK_OPTION LO_LIM
ALARM_HYS LO_LO_ALM
ALARM_SUM LO_LO_LIM
ALERT_KEY LO_LO_PRI
BLOCK_ALM LO_PRI
BLOCK_ERR LOW_CUT
BLOCK_ERR.DISABLED MODE_BLK
CHANNEL OUT
FIELD_VAL OUT_SCALE
GRANT_DENY PV
HI_ALM PV_FTIME
HI_HI_ALM SIMULATE
HI_HI_LIM ST_REV
HI_HI_PRI STATUS_OPTS
HI_LIM STRATEGY
HI_PRI TAG_DESC
IO_OPTS UPDATE_EVT
L_TYPE XD_SCALE
LO_ALM
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

324 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.3.4 Analog Output block

Figure 42: Functional schematic for Analog Output function block.

Description The Analog Output function block converts the set point (SP) value to a number that can
be used by the hardware associated with the CHANNEL selection. A functional
schematic of the block is shown in the previous illustration for reference.
Function Notes • Can use either the Set point (SP) value after limiting or the Process Variable (PV)
value for the BKCAL_OUT value.
• Supports Out of Service (OOS), Local Override (LO), Manual (Man), Automatic
(Auto), Cascade (Cas), and Remote Cascade (RCas) modes.
• The conversion of Set point (SP) to percent of span is based on the PV_SCALE
range.
• The conversion of the percent of span to a compatible value for the hardware is
based on the XD_SCALE range.
• Use the Increase to Close Option in IO_OPTS to invert the span.
• Use the Cascade mode to transfer the output of another block to the Set point of the
AO block.
• If the hardware, such as a valve positioner, supports a readback value, run this value
backwards through the XD scaling to act as the PV for this block. If this is not
supported, READBACK is generated from OUT.
• In the Man mode, an operator can write a value to OUT. A manufacturer must put
operational limits in the Transducer, where an operator cannot access them, to
permit the Man mode. If Man mode is not permitted, it must be supported as a
transition mode for exiting the OOS mode
• The SIMULATE parameter is for testing purposes only and always initializes in the
disabled state.
Equation Options • Temp = (SP - EU@0%) / (EU@100% - EU@0%) [PV_SCALE]
• OUT = Temp x (EU@100% - EU@0%) + EU@0% [XD_SCALE]
• Temp = (READBACK - EU@0%) / (EU@100% - EU@0%) [XD_SCALE]
• PV = Temp x (EU@100% - EU@0%) + EU@0% [PV_SCALE]

325
21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ALERT_KEY RCAS_OUT

BKCAL_OUT READBACK
BLOCK_ALM SHED_OPT
BLOCK_ERR SIMULATE
BLOCK_ERR.DISABLED SP
CAS_IN SP_HI_LIM
CHANNEL SP_LO_LIM
FSTATE_TIME SP_RATE_DN
FSTATE_VAL SP_RATE_UP
GRANT_DENY ST_REV
IO_OPTS STATUS_OPTS
MODE_BLK STRATEGY
OUT TAG_DESC
PV UPDATE_EVT
PV_SCALE XD_SCALE
RCAS_IN
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

21.3.5 Bias/Gain block

Figure 43: Functional schematic for Bias/Gain function block.

326 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Description The Bias/Gain function block can be used for biased external feedforward control or to
set several unit controllers, such as boiler masters, from one controller output, such as a
plant master. A functional schematic of the block is shown in the previous illustration
for reference.
Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan) Local Override (LO),
Manual (Man), Automatic (Auto), Cascade (Cas), and Remote Cascade (RCas)
modes.
• The output supports the track algorithm.
• The Balance Ramp option is supported.
• The CONTROL_OPTS selection Act on IR determines whether initialization
requests are to be passed on or acted on locally by changing the BIAS value.
• If the Act on IR option is false, a status of Not Invited (NI) or Initialization Request
(IR) at BKCAL_IN will be passed to BKCAL_OUT. The BKCAL_OUT value will
be calculated from the value of BKCAL_IN adjusted for SP and GAIN, as
determined by the control or process status of IN_1. When the upstream block sends
an Initialization Acknowledge (IA) status, this block will send IA status, since its
output will now be nearly equal to the value of BKCAL_IN.
• If the Act on IR option is true, a status of NI or IR at BKCAL_IN results in an
adjustment to SP to balance OUT to the value of BKCAL_IN. The IA status can be
sent as soon as IR is detected. BKCAL_OUT will not request initialization.
• The TRK_VAL input brings in an external value or uses a constant. The
TRK_SCALE values convert the TRK_VAL to a percent of output span value. If the
CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true, the
converted TRK_VAL replaces the output (OUT), when the block is in Automatic,
Cascade, or Remote Cascade mode. The CONTROL_OPTS Track in Manual
selection must be true for this to occur in Manual mode. If the actual mode is OOS
or IMan, the track request is ignored.
• If the TRK_VAL replaces the OUT, its status becomes Locked Out with Limits set
to Constant. The actual mode goes to LO. The status of RCAS_OUT goes to Not
Invited (NI), if not already there.
• If the status of TRK_IN_D is Bad, its last usable value will be maintained and acted
upon. If the device restarts, losing the last usable value, it will be set to false.
• If the status of TRK_VAL is Bad, the last usable value will be used. If there is no
last usable value, the present value of the OUT will be used.
Equation Options • In Automatic mode: OUT = (IN_1 + SP) x GAIN
• If IN_1 has Non-Cascade status: BKCAL_OUT = (BKCAL_IN / GAIN) - IN_1
• If IN_1 has Cascade status: BKCAL_OUT = (BKCAL_IN / GAIN) - SP

327
21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ALERT_KEY RCAS_IN

BAL_TIME RCAS_OUT
BKCAL_IN SHED_OPT
BKCAL_OUT SP
BLOCK_ALM SP_HI_LIM
BLOCK_ERR SP_LO_LIM
BLOCK_ERR.DISABLED SP_RATE_DN
CAS_IN SP_RATE_UP
CONTROL_OPTS ST_REV
GAIN STATUS_OPTS
GRANT_DENY STRATEGY
IN_1 TAG_DESC
MODE_BLK TRK_IN_D
OUT TRK_SCALE
OUT_HI_LIM TRK_VAL
OUT_LO_LIM UPDATE_EVT
OUT_SCALE
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

21.3.6 Control Selector block

Figure 44: Functional schematic for Control Selector function block.

Description The Control Selector function block accepts input from up to three control signals and
selects one for output based on the SEL_TYPE setting of High, Middle, or Low. A
functional schematic of the block is shown in the previous illustration for reference.

328 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Function Notes • All inputs must have the same scaling as OUT, since any one can be selected for
OUT.
• Supports Out of Service (OOS), Initialization Manual (IMan) Local Override (LO),
Manual (Man), and Automatic (Auto) modes.
• If an input has a sub-status of Do Not Select, it will not be selected.
• Three separate back calculation outputs (BKCAL_SEL_1, 2, 3) are available - one
for each input (SEL_1, 2, 3).
• The status will identify those inputs that are not selected. Control signals that are not
selected are limited in one direction only as determined by the SEL_TYPE
selection.
• The value of each BKCAL_SEL_1, 2, 3 output is the same as OUT. The limits of
back calculation outputs corresponding to not-selected inputs will be high for a low
selection, low for a high selection, or one of each for a middle selection.
• If the status of an input is Bad, it is not eligible for selection. If the status of an input
is Uncertain, it is treated as Bad unless the STATUS_OPTS selection is Use
Uncertain as Good.
• When all inputs are Bad, the actual mode goes to Manual. This condition will set
Initiate Fault State (IFS) in the output status, if the STATUS_OPTS setting is IFS if
BAD IN.
• If SEL_TYPE selection is Middle and only two inputs are good, the higher input
will be selected.
• If the status of BKCAL_IN is Not Invited (NI) or Initialization Request (IR), it is
passed back on all three back calculation outputs. This causes all initializable inputs
to initialize to the BKCAL_IN value. Otherwise, if the status of BKCAL_IN is not
normal, it is passed back on the BKCAL_SEL_N, where N is the number of the
selected input. The back calculation outputs for not-selected inputs just have the Not
Selected status with the appropriate high or low limit set.
• When the mode is Manual, no input is selected. All three back calculation outputs
will have a Not Invited status and Constant limits, with a value equal to OUT.
Parameters ALERT_KEY OUT_LO_LIM
BKCAL_IN OUT_SCALE
BKCAL_SEL_1 SEL_1
BKCAL_SEL_2 SEL_2
BKCAL_SEL_3 SEL_3
BLOCK_ALM SEL_TYPE
BLOCK_ERR ST_REV
BLOCK_ERR.DISABLED STATUS_OPTS
GRANT_DENY STRATEGY
MODE_BLK TAG_DESC
OUT UPDATE_EVT
OUT_HI_LIM
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

329
21 FIELDBUS TECHNOLOGY OVERVIEW

21.3.7 Discrete Input block

Figure 45: Functional schematic for Discrete Input function block.

Description The Discrete Input function block takes the discrete input data from a selected
Transducer block channel and provides it as an output for other Fieldbus function
blocks. A functional schematic of the block is shown in the previous illustration for
reference.
Function Notes • Supports Out of Service (OOS), Manual (Man), and Automatic (Auto) modes.
• The FIELD_VAL_D represents the true ON/OFF state of the value from the
Transducer, using XD_STATE.
• Use the IO_OPTS Invert selection to do a Boolean NOT function between the field
value and the output.
• Use the PV_FTIME to set the time that the input must be in one state before it gets
passed to the PV_D.
• The PV_D is always the value that the block places in OUT_D, when the mode is
Automatic.
• In Manual mode, if allowed, an operator can write a value to OUT_D.
• The SIMULATE_D parameter is for testing purposes only and always initializes in
the disabled state.

330 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ACK_OPTION MODE_BLK

ALARM_SUM OUT_D
ALERT_KEY OUT_STATE
BLOCK_ALM PV_D
BLOCK_ERR PV_FTIME
BLOCK_ERR.DISABLED SIMULATE_D
CHANNEL ST_REV
DISC_ALM STATUS_OPTS
DISC_LIM STRATEGY
DISC_PRI TAG_DESC
FIELD_VAL_D UPDATE_EVT
GRANT_DENY XD_STATE
IO_OPTS
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

21.3.8 Discrete Output block

Figure 46: Functional schematic for Discrete Output function block.

Description The Discrete Output function block converts the value in SP_D to something useful for
the hardware linked to the CHANNEL selection. A functional schematic of the block is
shown in the previous illustration for reference.

331
21 FIELDBUS TECHNOLOGY OVERVIEW

Function Notes • Supports Out of Service (OOS), Local Override (LO), Manual (Man), Automatic
(Auto), Cascade (Cas), and Remote Cascade (RCas) modes.
• The Set point (SP_D) supports the full cascade sub-function.
• Use the Cascade mode to transfer the output of another block to the Set point
(SP_D) of the DO block.
• Use the IO_OPTS Invert selection to do a Boolean NOT function between the field
value and the output.
• Use the IO_OPTS Invert selection to do a Boolean NOT function between the SP_D
and the output.
• If the hardware supports a readback value, it is used for READBACK_D, and, after
accounting for the IO_OPTS Invert selection, acts as the PV_D for this block. If this
is not supported, READBACK is generated from OUT_D.
• In the Man mode, an operator can force the output, in a programmable logic
controller sense. If Man mode is not permitted, it must be supported as a transition
mode for exiting the OOS mode
• The SIMULATE_D parameter is for testing purposes only and always initializes in
the disabled state.
Parameters ALERT_KEY PV_STATE
BKCAL_OUT_D RCAS_IN_D
BLOCK_ALM RCAS_OUT_D
BLOCK_ERR READBACK_D
BLOCK_ERR.DISABLED SHED_OPT
CAS_IN_D SIMULATE_D
CHANNEL SP_D
FSTATE_TIME ST_REV
FSTATE_VAL_D STATUS_OPTS
GRANT_DENY STRATEGY
IO_OPTS TAG_DESC
MODE_BLK UPDATE_EVT
OUT_D XD_STATE
PV_D
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

332 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.3.9 Manual Loader block

Figure 47: Functional schematic for Manual Loader function block.

Description The Manual Loader function block output is not set by the block's algorithm. An
operator can set its output in the Manual mode or a program in the Remote-Out mode. A
functional schematic of the block is shown in the previous illustration for reference.
Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan), Local Override (LO),
Manual (Man), and Remote-Out (ROut) modes.
• Accepts output from an AI block as its input (IN) to get a PV filtered by
PV_FTIME.
• The block's algorithm uses value and status for alarming only.
• If selected, the STATUS_OPTS of IFS if BAD IN will work.
• The BKCAL_IN value and status can force balancing of the output.
• The TRK_VAL input brings in an external value or uses a constant. The
TRK_SCALE values convert the TRK_VAL to a percent of output span value. If the
CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true, the
converted TRK_VAL replaces the output (OUT), when the block is in Remote-Out
(ROut) mode. The CONTROL_OPTS Track in Manual selection must be true for
this to occur in Manual mode. If the actual mode is OOS or IMan, the track request
is ignored.
• If the TRK_VAL replaces the OUT, its status becomes Locked Out with Limits set
to Constant. The actual mode goes to LO. The status of ROUT_OUT goes to Not
Invited (NI), if not already there.
• If the status of TRK_IN_D is Bad, its last usable value will be maintained and acted
upon. If the device restarts, losing the last usable value, it will be set to false.
• If the status of TRK_VAL is Bad, the last usable value will be used. If there is no
last usable value, the present value of the OUT will be used.

333
21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ACK_OPTION LO-LO_PRI

ALARM_HYS MODE_BLK
ALARM_SUM OUT
ALERT_KEY OUT_HI_LIM
BKCAL_IN OUT_LO_LIM
BLOCK_ALM OUT_SCALE
BLOCK_ERR PV
BLOCK_ERR.DISABLED PV_FTIME
CONTROL_OPTS PV_SCALE
GRANT_DENY ROUT_IN
HI_ALM ROUT_OUT
HI_HI_ALM SHED_OPT
HI_HI_LIM ST_REV
HI_HI_PRI STATUS_OPTS
HI_LIM STRATEGY
HI_PRI TAG_DESC
IN TRK_IN_D
LO_ALM TRK_SCALE
LO_LIM TRK_VAL
LO_LO_ALM UPDATE_EVT
LO_LO_LIM
LO_PRI
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

334 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.3.10 Proportional/Derivative block

Figure 48: Functional schematic for Proportional/Derivative function block.

Description The Proportional/Derivative function block provides classic two-mode control function
for processes that handle their own integration. When the Process Variable deviates
from the Set point, the PD function acts upon the error to move the output in a direction
to correct the deviation. PD blocks support cascade applications to compensate for the
difference in process time constants of a primary and secondary process measurement.
A functional schematic of the block is shown in the previous illustration for reference

335
21 FIELDBUS TECHNOLOGY OVERVIEW

Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan), Local Override (LO),
Manual (Man), Automatic (Auto), Cascade (Cas), Remote Cascade (RCas) and
Remote-Out (ROut) modes.
• The input (IN) passes through a filter with a time constant (PV_FTIME). The
filtered value becomes the Process Variable (PV) to be used with the Set point (SP)
in the block's algorithm.
• The full cascade SP sub-function is used, with rate and absolute limits. Additional
control options are available to have the SP value track the PV value, when the
block's actual mode is IMan, LO, Man, or ROut. Limits do not cause SP-PV
tracking.
• A BYPASS switch function is available for operators to use, when secondary
cascade controllers have a bad PV and the Bypass Enable (LSB) CONTROL_OPTS
is ON. The Bypass Enable option is required, since some control schemes may
become unstable when BYPASS is ON. An operator can only set the BYPASS
switch, when the block is in the Man or OOS mode. While BYPASS is ON, the SP
value, in percent of range, is passed directly to the target output, and the value of
OUT is used for BKCAL_OUT. When block mode switches to Cascade, the
upstream block is requested to initialize to the value of OUT. Upon transition to
bypass OFF, the upstream block is requested to initialize to the PV value, regardless
of the Use PV for BKCAL_OUT CONTROL_OPTS status.
• The tuning constant used for the Proportional term is GAIN and RATE is used for
the Derivative term. Some controllers use the inverse values of Proportional Band
and repeats per minutes for their tuning constants. Users can choose which tuning
constants they want to display.
• Use the Balance Ramp CONTROL_OPTS to maintain the BIAS value, when the
block is in Manual (Man) mode. An internal value follows the actual value required
to maintain balance. When block mode changes to Automatic (Auto), the internal
value ramps to zero contribution in BAL_TIME seconds. If Balance Ramp option is
OFF or not used, the BIAS value immediately changes to follow the changes to the
input or output, when the block is in Man mode.
• Use the Act on IR CONTROL_OPTS to select whether to ignore initialization
requests or act on them by changing the BIAS. If this option is ON, a status of Not
Invited (NI) or Initialization Request (IR) at BKCAL_IN causes the BIAS term to
be adjusted to balance OUT to the value of BKCAL_IN.
• Use the Direct Acting CONTROL_OPTS to define how a change in PV relative to
the SP affects the output. When Direct Acting is ON, the output increases when the
PV exceeds the SP. When Direct Acting is OFF, the output decreases when the PV
exceeds the SP. Be sure this option is set correctly and never changed while in the
Automatic mode, since it makes the difference between positive and negative
feedback. This option setting also affects the calculation of the limit states for
BKCAL_OUT.
• This block includes a Feed Forward algorithm. It accepts a value that is proportional
to some disturbance in the control loop as its FF_VAL input. The FF_SCALE values
convert the FF_VAL to a percent of output span value. The converted value is
multiplied by the FF_GAIN and added to the target output of the block's algorithm.
If the status of FF_VAL is Bad, the last usable value will be used to prevent a bump
in the output. When the status returns to Good, the block adjusts its BIAS term to
maintain the previous output.
• The TRK_VAL input brings in an external value or uses a constant. The
TRK_SCALE values convert the TRK_VAL to a percent of output span value. If the
CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true, the
converted TRK_VAL replaces the output (OUT), when the block is in Automatic
(Auto), Cascade (Cas), Remote Cascade (RCas), or Remote-Out (ROut) mode. The
CONTROL_OPTS Track in Manual selection must be true for this to occur in
Manual mode. If the actual mode is OOS or IMan, the track request is ignored.
• If the TRK_VAL replaces the OUT, its status becomes Locked Out with Limits set
to Constant. The actual mode goes to LO. The status of BKCAL_OUT, RCAS_OUT
and ROUT_OUT goes to Not Invited (NI), if not already there.

336 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

• If the status of TRK_IN_D is Bad, its last usable value will be maintained and acted
upon. If the device restarts, losing the last usable value, it will be set to false.
• If the status of TRK_VAL is Bad, the last usable value will be used. If there is no
last usable value, the present value of the OUT will be used.
• Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after
limiting in Cas or RCas mode.
• Use the Use PV for BKCAL_OUT CONTROL_OPTS to the PV value for the
BKCAL_OUT value.
Parameters ACK_OPTION LO_LIM
ALARM_HYS LO_LO_ALM
ALARM_SUM LO_LO_LIM
ALERT_KEY LO_LO_PRI
BAL_TIME LO_PRI
BIAS MODE_BLK
BKCAL_HYS OUT
BKCAL_IN OUT_HI_LIM
BKCAL_OUT OUT_LO_LIM
BLOCK_ALM OUT_SCALE
BLOCK_ERR PV
BLOCK_ERR.DISABLED PV_FTIME
BYPASS PV_SCALE
CAS_IN RATE
CONTROL_OPTS RCAS_IN
DV_HI_ALM RCAS_OUT
DV_HI_LIM ROUT_IN
DV_HI_PRI ROUT_OUT
DV_LO_ALM SHED_OPT
DV_LO_LIM SP
DV_LO_PRI SP_HI_LIM
FF_GAIN SP_LO_LIM
FF_SCALE SP_RATE_DN
FF_VAL SP_RATE_UP
GAIN ST_REV
GRANT_DENY STATUS_OPTS
HI_ALM STRATEGY
HI_HI_ALM TAG_DESC
HI_HI_LIM TRK_IN_D
HI_HI_PRI TRK_SCALE
HI_LIM TRK_VAL
HI_PRI UPDATE_EVT
IN
LO_ALM

337
21 FIELDBUS TECHNOLOGY OVERVIEW

Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

21.3.11 Proportional/Integral/Derivative block

Figure 49: Functional schematic for Proportional/Integral/Derivative function block.

Description The Proportional/Integral/Derivative function block provides classic three-mode control

function for closed-loop control applications. When the Process Variable deviates from
the Set point, the PID function acts upon the error to move the output in a direction to
correct the deviation. PID blocks support cascade applications to compensate for the
difference in process time constants of a primary and secondary process measurement.
A functional schematic of the block is shown in the previous illustration for reference.

338 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan), Local Override (LO),
Manual (Man), Automatic (Auto), Cascade (Cas), Remote Cascade (RCas) and
Remote-Out (ROut) modes.
• The input (IN) passes through a filter with a time constant (PV_FTIME). The
filtered value becomes the Process Variable (PV) to be used with the Set point (SP)
in the block's algorithm. A PID algorithm will not integrate, if the limit status of the
input (IN) is constant.
• The full cascade SP sub-function is used, with rate and absolute limits. Additional
control options are available to have the SP value track the PV value, when the
block's actual mode is IMan, LO, Man, or ROut. Limits do not cause SP-PV
tracking.
• A BYPASS switch function is available for operators to use, when secondary
cascade controllers have a bad PV and the Bypass Enable (LSB) CONTROL_OPTS
is ON. The Bypass Enable option is required, since some control schemes may
become unstable when BYPASS is ON. An operator can only set the BYPASS
switch, when the block is in the Man or OOS mode. While BYPASS is ON, the SP
value, in percent of range, is passed directly to the target output, and the value of
OUT is used for BKCAL_OUT. When block mode switches to Cascade, the
upstream block is requested to initialize to the value of OUT. Upon transition to
bypass OFF, the upstream block is requested to initialize to the PV value, regardless
of the Use PV for BKCAL_OUT CONTROL_OPTS status.
• The tuning constant used for the Proportional term is GAIN, RESET is used for the
Integral term, and RATE is used for the Derivative term. Both RESET and RATE
are time constants expressed in seconds. Some controllers use the inverse values of
Proportional Band and repeats per minutes for their tuning constants. Users can
choose which tuning constants they want to display.
• Use the Direct Acting CONTROL_OPTS to define how a change in PV relative to
the SP affects the output. When Direct Acting is ON, the output increases when the
PV exceeds the SP. When Direct Acting is OFF, the output decreases when the PV
exceeds the SP. Be sure this option is set correctly and never changed while in the
Automatic mode, since it makes the difference between positive and negative
feedback. This option setting also affects the calculation of the limit states for
BKCAL_OUT.
• This block includes a Feed Forward algorithm. It accepts a value that is proportional
to some disturbance in the control loop as its FF_VAL input. The FF_SCALE values
convert the FF_VAL to a percent of output span value. The converted value is
multiplied by the FF_GAIN and added to the target output of the block's algorithm.
If the status of FF_VAL is Bad, the last usable value will be used to prevent a bump
in the output. When the status returns to Good, the block adjusts its Integral
(RESET) term to maintain the previous output.
• The TRK_VAL input brings in an external value or uses a constant. The
TRK_SCALE values convert the TRK_VAL to a percent of output span value. If the
CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true, the
converted TRK_VAL replaces the output (OUT), when the block is in Automatic
(Auto), Cascade (Cas), Remote Cascade (RCas), or Remote-Out (ROut) mode. The
CONTROL_OPTS Track in Manual selection must be true for this to occur in
Manual mode. If the actual mode is OOS or IMan, the track request is ignored.
• If the TRK_VAL replaces the OUT, its status becomes Locked Out with Limits set
to Constant. The actual mode goes to LO. The status of BKCAL_OUT, RCAS_OUT
and ROUT_OUT goes to Not Invited (NI), if not already there.
• If the status of TRK_IN_D is Bad, its last usable value will be maintained and acted
upon. If the device restarts, losing the last usable value, it will be set to false.
• If the status of TRK_VAL is Bad, the last usable value will be used. If there is no
last usable value, the present value of the OUT will be used.
• Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after
limiting in Cas or RCas mode.
• Use the Use PV for BKCAL_OUT CONTROL_OPTS to the PV value for the
BKCAL_OUT value.

339
21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ACK_OPTION LO_LO_ALM

ALARM_HYS LO_LO_LIM
ALARM_SUM LO_LO_PRI
ALERT_KEY LO_PRI
BAL_TIME MODE_BLK
BKCAL_HYS OUT
BKCAL_IN OUT_HI_LIM
BKCAL_OUT OUT_LO_LIM
BLOCK_ALM OUT_SCALE
BLOCK_ERR PV
BLOCK_ERR.DISABLED PV_FTIME
BYPASS PV_SCALE
CAS_IN RATE
CONTROL_OPTS RCAS_IN
DV_HI_ALM RCAS_OUT
DV_HI_LIM RESET
DV_HI_PRI ROUT_IN
DV_LO_ALM ROUT_OUT
DV_LO_LIM SHED_OPT
DV_LO_PRI SP
FF_GAIN SP_HI_LIM
FF_SCALE SP_LO_LIM
FF_VAL SP_RATE_DN
GAIN SP_RATE_UP
GRANT_DENY ST_REV
HI_ALM STATUS_OPTS
HI_HI_ALM STRATEGY
HI_HI_LIM TAG_DESC
HI_HI_PRI TRK_IN_D
HI_LIM TRK_SCALE
HI_PRI TRK_VAL
IN UPDATE_EVT
LO_ALM
LO_LIM
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

340 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

21.3.12 Ratio block

Figure 50: Functional schematic for Ratio function block.

Description The Ratio function block set point is the ratio of its output to its input. A ratio set point
of 0.5 produces an output that is one half of its input. The input (IN_1) is either a wild
flow or the output of a blend-pacing controller. The output can be used as the set point
for a secondary flow controller. An input (IN) from the secondary measurement is used
to calculate the actual ratio, which is displayed as the PV. A functional schematic of the
block is shown in the previous illustration for reference.

341
21 FIELDBUS TECHNOLOGY OVERVIEW

Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan), Local Override (LO),
Manual (Man), Automatic (Auto), Cascade (Cas), and Remote Cascade (RCas)
modes.
• The input 1 (IN_1) value to be ratioed passes through a filter with a time constant of
RA_FTIME. The filtered value is multiplied by the Set point (SP) and GAIN to
become the target output. The GAIN controls the number of zeros in the SP display.
• The input (IN) value is the actual value of the ratioed variable and it passes through
a filter with a time constant of PV_FTIME. The filtered IN value is divided by the
filtered IN_1 value and the GAIN to become the PV. The units of IN are not PV, but
OUT. The units of IN_1 are OUT units divided by PV units.
• The full cascade SP sub-function is used, with rate and absolute limits. Additional
control options are available to have the SP value track the PV value, when the
block's actual mode is IMan, LO, Man, or ROut. Limits do not cause SP-PV
tracking.
• Use the Act on IR CONTROL_OPTS to select whether to pass initialization
requests or act on them locally by changing the SP value. If this option is OFF or to
pass, a status of Not Invited (NI) or Initialization Request (IR) at BKCAL_IN will
be passed to BKCAL_OUT. The BKCAL_OUT value will be calculated from the
value of BKCALC_IN divided by GAIN and IN_1. When the upstream block sends
Initialization Acknowledge (IA) status, the block sends the IA status, since its
output will now be nearly identical to the value BKCAL_IN. If this option is ON or
to act, a status of NI or IR at BKCAL_IN adjusts the SP to balance the output to the
value of BKCAL_IN. The IA status is sent as soon as IR is detected. The
BKCAL_OUT will not request initialization.
• Use the Balance Ramp CONTROL_OPTS to maintain the ratio SP value, when the
block is in Manual (Man) mode. An internal value follows the actual value required
to maintain balance. When block mode changes to Automatic (Auto), the internal
value ramps to zero contribution in BAL_TIME seconds. If Balance Ramp option is
OFF or not used, the ratio SP value immediately changes to follow the changes to
the input or output, when the block is in Man mode.
• The TRK_VAL input brings in an external value or uses a constant. The
TRK_SCALE values convert the TRK_VAL to a percent of output span value. If the
CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true, the
converted TRK_VAL replaces the output (OUT), when the block is in Automatic
(Auto), Cascade (Cas), or Remote Cascade (RCas) mode. The CONTROL_OPTS
Track in Manual selection must be true for this to occur in Manual mode. If the
actual mode is OOS or IMan, the track request is ignored.
• If the TRK_VAL replaces the OUT, its status becomes Locked Out with Limits set
to Constant. The actual mode goes to LO. The status of BKCAL_OUT, and
RCAS_OUT goes to Not Invited (NI), if not already there.
• If the status of TRK_IN_D is Bad, its last usable value will be maintained and acted
upon. If the device restarts, losing the last usable value, it will be set to false.
• If the status of TRK_VAL is Bad, the last usable value will be used. If there is no
last usable value, the present value of the OUT will be used.
• Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after
limiting in Cas or RCas mode.
• Use the 'Use PV for BKCAL_OUT' CONTROL_OPTS to the PV value for the
BKCAL_OUT value.
Equation Options • If Auto mode, OUT = IN_1 (filtered) x SP x GAIN
• PV = IN (filtered) / IN_1 (filtered) / GAIN
• If IN_1 has non-cascade status, BKCAL_OUT = BKCAL_IN / GAIN / IN_1
(filtered)
• If IN_1 has cascade status, BKCAL_OUT = BKCAL_IN / GAIN / SP

342 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Parameters ACK_OPTION LO_LO_ALM

ALARM_HYS LO_LO_LIM
ALARM_SUM LO_LO_PRI
ALERT_KEY LO_PRI
BAL_TIME MODE_BLK
BKCAL_IN OUT
BKCAL_OUT OUT_HI_LIM
BLOCK_ALM OUT_LO_LIM
BLOCK_ERR OUT_SCALE
BLOCK_ERR.DISABLED PV
CAS_IN PV_FTIME
CONTROL_OPTS PV_SCALE
DV_HI_ALM RA_FTIME
DV_HI_LIM RCAS_IN
DV_HI_PRI RCAS_OUT
DV_LO_ALM SHED_OPT
DV_LO_LIM SP
DV_LO_PRI SP_HI_LIM
GAIN SP_LO_LIM
GRANT_DENY SP_RATE_DN
HI_ALM SP_RATE_UP
HI_HI_ALM ST_REV
HI_HI_LIM STATUS_OPTS
HI_HI_PRI STRATEGY
HI_LIM TAG_DESC
HI_PRI TRK_IN_D
IN TRK_SCALE
IN_1 TRK_VAL
LO_ALM UPDATE_EVT
LO_LIM
Reference Refer to the “Standard Function Block Parameters Reference” on page 347 section in
this book for definitions of each parameter.

343
21 FIELDBUS TECHNOLOGY OVERVIEW

21.4 Device Descriptions and Block Parameters

21.4.1 About Device Descriptions

Device Descriptions (DD) are critical to the interoperability of Fieldbus devices. They define the data needed to
establish communications between different Fieldbus devices from multiple vendors with control system hosts.
The DD provides an extended description of each object in the User Application Virtual Field Device (VFD).
The Fieldbus Foundation provides Device Descriptions for all standard Function Blocks and Transducer Blocks
on a CD-ROM and on its web site. Manufacturer's may provide an 'Incremental' DD that references the standard
DDs and describes manufacturer specific features such as calibration and diagnostic procedures added to their
devices.

21.4.2 Device Description Language

The Device Description Language (DDL) is a structured text language used to write a DDL source file. A DDL
source file describes each device function, parameter, and special feature as well as how a field device can
interact with a host application and other field devices. A completed DDL source file is converted into a binary
formatted DD output file. The DD output file information can be provided in object form in the device itself, or
on a removable storage media delivered with the device. A field device's Object Dictionary (OD) can be
transferred from a device to a host using standard Fieldbus Message Specification services.

21.4.3 Device Description infrastructure

The Fieldbus Foundation defines a four-level infrastructure for Device Descriptions for the sake of consistency.
See the following illustration for a graphical representation of the DD infrastructure.

Figure 51: Device Descriptions infrastructure.

Level 1 consists of Universal Parameters that define common attributes such as Tag, Revision, and Mode. All
blocks must include Universal Parameters.

344 www.honeywell.com
 21 FIELDBUS TECHNOLOGY OVERVIEW

Level 2 consists of Function Block Parameters that define parameters for all standard Function Blocks including
the standard Resource Block.
Level 3 consists of Transducer Block Parameters that define parameters for the standard Transducer block. In
some cases, the Transducer Block specification may add parameters to the standard Resource Block.
The first three levels are the Device Descriptions provided by the Fieldbus Foundation.
Level 4 is the Manufacturer Specific Parameters that define the parameters a manufacturer has added to the
standard Function Block and Transducer Block parameters. These added parameters will be included in the DD
supplied by the manufacturer.

345
21 FIELDBUS TECHNOLOGY OVERVIEW

346 www.honeywell.com
22 Standard Function Block Parameters Reference

This section provides definitions for some Fieldbus standard function block parameters for convenient
reference.

Related topics
“ACK_OPTION” on page 351
“ALARM_HYS” on page 352
“ALARM_SUM” on page 353
“ALERT_KEY” on page 354
“BAL_TIME” on page 355
“BIAS” on page 356
“BKCAL_HYS” on page 357
“BKCAL_IN” on page 358
“BKCAL_OUT” on page 359
“BKCAL_OUT_D” on page 360
“BKCAL_SEL_1” on page 361
“BKCAL_SEL_2” on page 362
“BKCAL_SEL_3” on page 363
“BLOCK_ALM” on page 364
“BLOCK_ERR” on page 365
“BLOCK_ERR.DISABLED” on page 366
“BYPASS” on page 367
“CAS_IN” on page 368
“CAS_IN_D” on page 369
“CHANNEL” on page 370
“CLR_FSTATE” on page 371
“CONFIRM_TIME” on page 372
“CONTROL_OPTS” on page 373
“CYCLE_SEL” on page 374
“CYCLE_TYPE” on page 375
“DEV_REV” on page 376
“DEV_TYPE” on page 377
“DD_RESOURCE” on page 378
“DD_REV” on page 379
“DISC_ALM” on page 380
“DISC_LIM” on page 381
“DISC_PRI” on page 382
“DV_HI_ALM” on page 383
“DV_HI_LIM” on page 384
“DV_HI_PRI” on page 385

347
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

“DV_LO_ALM” on page 386

“DV_LO_LIM” on page 387
“DV_LO_PRI” on page 388
“FAULT_STATE” on page 389
“FEATURES” on page 390
“FEATURE_SEL” on page 391
“FF_GAIN” on page 392
“FF_SCALE” on page 393
“FF_VAL” on page 394
“FIELD_VAL” on page 395
“FIELD_VAL_D” on page 396
“FREE_SPACE” on page 397
“FREE_TIME” on page 398
“FSTATE_TIME” on page 399
“FSTATE_VAL” on page 400
“FSTATE_VAL_D” on page 401
“GAIN” on page 402
“GRANT_DENY” on page 403
“HARD_TYPES” on page 404
“HI_ALM” on page 405
“HI_HI_ALM” on page 406
“HI_HI_LIM” on page 407
“HI_HI_PRI” on page 408
“HI_LIM” on page 409
“HI_PRI” on page 410
“IO_OPTS” on page 411
“IN” on page 412
“IN_1” on page 413
“LIM_Notify” on page 414
“L_TYPE” on page 415
“LO_ALM” on page 416
“LO_LIM” on page 417
“LO_LO_ALM” on page 418
“LO_LO_LIM” on page 419
“LO_LO_PRI” on page 420
“LO_PRI” on page 421
“LOW_CUT” on page 422
“MANUFAC_ID” on page 423
“MAX_NOTIFY” on page 424
“MEMORY_SIZE” on page 425
“MIN_CYCLE_T” on page 426
“MODE_BLK” on page 427
“NV_CYCLE_T” on page 428
“OFFNETALM_ENABLED” on page 429
“OUT” on page 430
“OUT_D” on page 431
“OUT_HI_LIM” on page 432
“OUT_LO_LIM” on page 433

348 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

“OUT_SCALE” on page 434

“OUT_STATE” on page 435
“PV” on page 436
“PV_D” on page 437
“PV_FTIME” on page 438
“PV_SCALE” on page 439
“PV_STATE” on page 440
“RA_FTIME” on page 441
“RATE” on page 442
“RCAS_IN” on page 443
“RCAS_IN_D” on page 444
“RCAS_OUT” on page 445
“RCAS_OUT_D” on page 446
“READBACK” on page 447
“READBACK_D” on page 448
“RESET” on page 449
“RESTART” on page 450
“ROUT_IN” on page 451
“ROUT_OUT” on page 452
“RS_STATE” on page 453
“SEL_1” on page 454
“SEL_2” on page 455
“SEL_3” on page 456
“SEL_TYPE” on page 457
“SET_FSTATE” on page 458
“SHED_OPT” on page 459
“SHED_RCAS” on page 460
“SHED_ROUT” on page 461
“SIMULATE” on page 462
“SIMULATE_D” on page 463
“SP” on page 464
“SP_D” on page 465
“SP_HI_LIM” on page 466
“SP_LO_LIM” on page 467
“SP_RATE_DN” on page 468
“SP_RATE-UP” on page 469
“ST_REV” on page 470
“STATUS_OPTS” on page 471
“STRATEGY” on page 472
“TAG_DESC” on page 473
“TEST_RW” on page 474
“TRK_IN_D” on page 475
“TRK_SCALE” on page 476
“TRK_VAL” on page 477
“UPDATE_EVT” on page 478
“WRITE_ALM” on page 479
“WRITE_LOCK” on page 480
“WRITE_PRI” on page 481

349
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

“XD_SCALE” on page 482

“XD_STATE” on page 483

350 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.1 ACK_OPTION

Classification Simple Variable

Description Selects whether alarms associated with the block will be automatically acknowledged.
FF Data Type Bit String
Range 1: Unacknowledged
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0
All function blocks that support alarming, such as AI, PID, and DI, provide an option to
support operator acknowledgement status stored in the device or stored in the control
system's alarm server. Experion systems support operator acknowledgement stored in the
server to provide alarm acknowledgement operation consistent with the rest of Experion
components, particularly with respect to multiple console independence of alarm
acknowledgement. Therefore the Fieldbus parameter ACK_OPTION is always
automatically set by Experion systems to ones for supported alarms, and the parameter is
generally hidden to avoid confusion.

351
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.2 ALARM_HYS

Classification Simple Variable

Description Defines the amount of change a PV value must attain within the alarm limits before the
alarm condition clears.
FF Data Type Float
Range 0 to 50 percent of PV span
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0.5 percent

352 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.3 ALARM_SUM

Classification Record
Description Detects the current alert status, unacknowledged states, and disable states of the alarms
associated with the block
FF Data Type DS-74
Range
Usage C/Alarm Summary
Length 8
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks The data type summarizes 16 alerts using the following 4 elements.
• 1 Current
• 2 Unacknowledged
• 3 Unreported
• 4 Disabled

353
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.4 ALERT_KEY

Classification Simple Variable

Description The identification number of the plant unit. This data may be used in the host for sorting
alarms.
FF Data Type Unsigned 8
Range 1 to 255
Usage C/Alert Key
Length 1
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

354 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.5 BAL_TIME

Classification Simple Variable

Description Specifies the time in seconds for the internal working value of Bias or Ratio to return to
the operator set value.
In PID block, specifies the time constant to be used to move the integral term to obtain
balance, when the output is limited and the mode is Auto, Cas, or RCas.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

355
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.6 BIAS

Classification Simple Variable

Description Specifies the Bias value in engineering units to be used in computing the function block
output
FF Data Type Float
Range OUT_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Normally, the operator has permission to write these values, but PROGRAM or LOCAL
remove the permission and grant it to a supervisory computer or a local control panel.

356 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.7 BKCAL_HYS

Classification Simple Variable

Description Defines the amount of change an output value must attain from the limit before the limit
status is turned OFF.
FF Data Type Float
Range 0 to 50 percent of output span
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0.5 percent

357
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.8 BKCAL_IN

Classification Record
Description The value and status from a lower block's BKCAL_OUT that is used to prevent reset
windup and to initialize the control loop.
FF Data Type DS-65
Range
Usage I/Back-Calculation Input
Length 5
Valid Views VIEW_3
Storage Non-Volatile
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

358 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.9 BKCAL_OUT

Classification Record
Description The value and status required by an upper block's BKCAL_IN so the upper block may
prevent reset windup and provide bumpless transfer to closed loop control.
FF Data Type DS-65
Range
Usage O/Back Calculation Output
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

359
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.10 BKCAL_OUT_D

Classification Record
Description The output value and status provided to an upstream discrete block that is used to provide
bumpless transfer for closed loop control.
FF Data Type DS-66
Range
Usage O/Back Calculation Output
Length 2
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

360 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.11 BKCAL_SEL_1

Classification Record
Description The selector output value and status associated with SEL_1 input that is provided to
BKCAL_IN of the block connected to SEL_1 to prevent reset windup.
FF Data Type DS-65
Range
Usage O/Back Calculation Output
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

361
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.12 BKCAL_SEL_2

Classification Record
Description The selector output value and status associated with SEL_2 input that is provided to
BKCAL_IN of the block connected to SEL_2 to prevent reset windup.
FF Data Type DS-65
Range
Usage O/Back Calculation Output
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

362 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.13 BKCAL_SEL_3

Classification Record
Description The selector output value and status associated with SEL_3 input that is provided to
BKCAL_IN of the block connected to SEL_3 to prevent reset windup.
FF Data Type DS-65
Range
Usage O/Back Calculation Output
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

363
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.14 BLOCK_ALM

Classification Record
Description The block alarm is used for all configuration, hardware, connection failure, or system
problems in the block. The cause of the alarm is entered in the sub-code field. The first
alarm to become active will set the Active status in the Status attribute. As soon as the
Unreported status is cleared by the alarm-reporting task, another block alarm may be
reported without clearing the Active status, if the sub-code has changed.
FF Data Type DS-72
Range
Usage C/Alarm
Length 13
Valid Views
Storage Dynamic
Remarks The data type describes discrete alarms using the following five elements:
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

364 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.15 BLOCK_ERR

Classification Simple Variable

Description Reflects the error status associated with the hardware or software components associated
with a block. It is a bit string that can show multiple errors.
FF Data Type Bit String
Range
Usage C/Block Error
Length 2
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks

365
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.16 BLOCK_ERR.DISABLED

Classification
Description Enables you to disable individual block errors.
FF Data Type Bitstring
Range
Usage C/Contained
Length
Valid Views Dynamic
Storage
Remarks • For the blocks such as AI block configured in Control Modules, when an inactive
block error is disabled and if the block error turns active, the Alarm Display will not
display the alarm and the Event Summary will not display the alarm event. For the
devices only blocks such as, Resource or Transducer blocks, block error alarm
appearance in the Alarm Display or System Status Display is affected.
• Regardless of disabling, the individual block error status is displayed on the block's
Maintenance tab.
• When an active block error is disabled, the Alarm or Display or System Status
Display alarm returns to normal, and Event Summary displays the alarm action as
OK.
• In the Alarm Display or System Status Display, when you acknowledge block error
alarms that have returned to normal, the alarms disappear and Event Summary
displays the acknowledged alarms.
• When the disable is removed for an active block error, the Alarm Display or System
Status Display displays the alarm as active and Event Summary receives the event
for that particular alarm.
Note: This is not a Fieldbus block parameter. It is a Honeywell parameter, which is stored
internally on the FIM but appears to reside on the Fieldbus block template.

366 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.17 BYPASS

Classification Simple Variable

Description Provides the means to bypass the normal control algorithm. When BYPASS is On, the set
point value is directly transferred to the output. To prevent a bump upon BYPASS
switching, the set point automatically initializes to the output value or process variable
and sets the path broken flag for one execution.
FF Data Type Unsigned 8
Range 1: Off
2: On
Usage C/Contained
Length 1
Valid Views VIEW_2
Storage Static
Remarks Initial value is 0.

367
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.18 CAS_IN

Classification Record
Description Represents the remote set point value that must come from another Fieldbus block or a
distributed control system (DCS) block through a defined link.
FF Data Type DS-65
Range
Usage I/Cascade Input
Length 5
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

368 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.19 CAS_IN_D

Classification Record
Description Represents the remote set point value for a discrete block that must come from another
Fieldbus block or a distributed control system (DCS) block through a defined link.
FF Data Type DS-66
Range
Usage I/Cascade Input
Length 2
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

369
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.20 CHANNEL

Classification Simple Variable

Description The number of the logical hardware channel that is connected to this I/O block. It defines
the transducer used to connect to the physical world.
FF Data Type Unsigned 16
Range 1 to Manufacturer Limit
Usage C/Channel
Length 2
Valid Views VIEW_4
Storage Static
Remarks The initial value is 0.

370 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.21 CLR_FSTATE

Classification Simple Variable

Description Serves as a switch to reset/clear the device fault state after the fault condition is cleared.
FF Data Type Unsigned 8
Range 1: Off
2: Clear
Usage C/Contained
Length 1
Valid Views
Storage Dynamic
Remarks The operator can control PROGRAM or LOCAL access to these values.

371
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.22 CONFIRM_TIME

Classification Simple Variable

Description Defines the time between retries of alert reports.
FF Data Type Unsigned 32
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks The initial value is 32000 milliseconds.

372 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.23 CONTROL_OPTS

Classification Simple Variable

Description Represents bit string for control options to alter the calculations done in an applicable
function block.
FF Data Type Bit String
Range
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks See the following Table 2 for a list of the control options by bit and applicable function
block.

Table 11: CONTROL_OPTS Bit Selections

Bit Meaning Function Block

BG CS ML PD PID RA
0 Bypass Enable (LSB) X X
1 SP-PV Track in Man X X X
2 SP-PV Track in ROut X X
3 SP-PV Track in LO or IMan X X X
4 SP Track retained target X X X X
5 Direct Acting X X
6 Balance Ramp X X X
7 Track Enable X X X X X
8 Track in Manual X X X X X
9 Use PV for BKCAL_OUT X X X
10 Act on IR X X X
11 Use percent for IN_1 X X
12 Obey SP limits if Cas or RCas X X X X
13 No OUT limits in Manual X X X X X X
14 Reserved
15 Reserved

373
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.24 CYCLE_SEL

Classification Simple Variable

Description A bit string to identify the block execution method selected for this resource.
FF Data Type Bit String
Range
Usage C/Contained
Length 2
Valid Views VIEW_2
Storage Static
Remarks Changing this parameter may be fatal to communication.

374 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.25 CYCLE_TYPE

Classification Simple Variable

Description A bit string to identify the block execution methods available for this resource.
FF Data Type Bit String
Range Set by Manufacturer
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Read Only

375
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.26 DEV_REV

Classification Simple Variable

Description Identifies the manufacturer revision number associated with the resource. An interface
device uses it to locate the DD file for the resource.
FF Data Type Unsigned 8
Range Set by manufacturer
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks Read Only

376 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.27 DEV_TYPE

Classification Simple Variable

Description Identifies the manufacturer's model number associated with the resource. An interface
device uses it to locate the DD file for the resource.
FF Data Type Unsigned 16
Range Set by manufacturer
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Read Only

377
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.28 DD_RESOURCE

Classification Simple Variable

Description Identifies the tag of the resource that contains the Device Description for this resource.
FF Data Type Visible String
Range
Usage C/DD Resource
Length 32
Valid Views
Storage Static
Remarks Read Only

378 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.29 DD_REV

Classification Simple Variable

Description Identifies the revision of the Device Description associated with the resource so an
interface device can locate the DD file for the resource.
FF Data Type Unsigned 8
Range
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks Read Only

379
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.30 DISC_ALM

Classification Record
Description Identifies the status and time stamp associated with the discrete alarm.
FF Data Type DS-72
Range
Usage C/Alarm
Length 13
Valid Views
Storage Dynamic
Remarks Read Only
The data type consists of data that describes discrete alarms. It uses the following five
elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

380 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.31 DISC_LIM

Classification Simple Variable

Description Identifies state of discrete input that will generate an alarm.
FF Data Type Unsigned 8
Range PV state
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks

381
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.32 DISC_PRI

Classification Simple Variable

Description Identifies the priority of the discrete alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks

382 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.33 DV_HI_ALM

Classification Record
Description Identifies the status and time stamp associated with the high deviation alarm.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

383
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.34 DV_HI_LIM

Classification Simple Variable

Description Defines the high deviation alarm limit setting in engineering units.
FF Data Type Float
Range 0 to PV Span, + infinity
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is + infinity

384 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.35 DV_HI_PRI

Classification Simple Variable

Description Defines priority of the high deviation alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

385
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.36 DV_LO_ALM

Classification Record
Description Identifies the status and time stamp associated with the low deviation alarm.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

386 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.37 DV_LO_LIM

Classification Simple Variable

Description Defines the low deviation alarm limit setting in engineering units.
FF Data Type Float
Range - infinity , - PV Span to 0,
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is - infinity

387
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.38 DV_LO_PRI

Classification Simple Variable

Description Defines priority of the low deviation alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

388 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.39 FAULT_STATE

Classification Simple Variable

Description Condition set by loss of communication to an output block, failure promoted to an output
block or a physical contact. When the fault state action is active, the output function
blocks will perform their FSTATE action
FF Data Type Unsigned 8
Range 1: Clear
2: Active
Usage C/Contained
Length 1
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only

389
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.40 FEATURES

Classification Simple Variable

Description Bit string that identifies the supported resource block options.
FF Data Type Bit String
Range Set by manufacturer
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Read Only

390 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.41 FEATURE_SEL

Classification Simple Variable

Description Bit string that identifies the selected resource block options.
FF Data Type Bit String
Range
Usage C/Contained
Length 2
Valid Views VIEW_2
Storage Static
Remarks This parameter must have the Reports bit set (FEATURE_SEL[1]). Without it, the
device never issues any alarm notifications.

391
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.42 FF_GAIN

Classification Simple Variable

Description Defines the gain value used to multiply the feed-forward signal before it is added to the
calculated control output.
FF Data Type Float
Range
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

392 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.43 FF_SCALE

Classification Record
Description Defines the feed-forward input high and low scale values, engineering units code, and
number of digits to the right of the decimal.
FF Data Type DS-68
Range 0-100 percent
Usage C/Scaling
Length 11
Valid Views VIEW_4
Storage Static
Remarks The Data type consists of data that describes floating point values for display purposes. It
uses the following four elements.
• 1 Engineering Units at 100 percent
• 2 Engineering Units at 0 percent
• 3 Units Index
• 4 Decimal Point

393
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.44 FF_VAL

Classification Record
Description Represents the feed-forward value.
FF Data Type DS-65
Range
Usage I/Input
Length 5
Valid Views VIEW_3
Storage Non-Volatile
Remarks Read Only
The Data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

394 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.45 FIELD_VAL

Classification Record
Description Represents the raw value from the field device in percent of transducer span, with a status
reflecting the transducer condition, before signal characterization (L_TYPE) or filtering
(PV_FTIME).
FF Data Type DS-65
Range
Usage C/Contained
Length 5
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The Data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

395
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.46 FIELD_VAL_D

Classification Record
Description Represents the raw value of a field device discrete input with a status reflecting the
transducer condition.
FF Data Type DS-66
Range
Usage C/Contained
Length 2
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

396 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.47 FREE_SPACE

Classification Simple Variable

Description Identifies the percent of memory available for further configuration. Zero in a
preconfigured resource.
FF Data Type Float
Range 0 - 100 percent
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Dynamic
Remarks Read Only

397
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.48 FREE_TIME

Classification Simple Variable

Description Identifies the percent of block processing time that is free to process additional blocks.
FF Data Type Float
Range 0 - 100 percent
Usage C/Contained
Length 4
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only

398 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.49 FSTATE_TIME

Classification Simple Variable

Description Represents the reaction time in seconds from the detection of a failure at the output block
remote set point to the output block action, if the condition still exists.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

399
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.50 FSTATE_VAL

Classification Simple Variable

Description Defines the preset analog set point to use when a failure occurs. Value is ignored, if the
IO_OPTS Fault state to value option is false.
FF Data Type Float
Range PV_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

400 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.51 FSTATE_VAL_D

Classification Simple Variable

Description Defines the preset discrete set point to use when a failure occurs. Value is ignored, if the
IO_OPTS Fault state to value option is false.
FF Data Type Unsigned 8
Range
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks

401
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.52 GAIN

Classification Simple Variable

Description Represents dimensionless gain used by several different algorithms.
FF Data Type Float
Range
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

402 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.53 GRANT_DENY

Classification Record
Description Defines options for controlling access of host computer or local control panels to the
block's operating, tuning, and alarm parameters.
FF Data Type DS-70
Range
Usage C/Access Permission
Length 2
Valid Views VIEW_2
Storage Non-Volatile
Remarks The data type consists of access control flags for access to block parameters. It uses the
following two elements.
• 1 Grant
• 2 Deny

403
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.54 HARD_TYPES

Classification Simple Variable

Description Identifies types of hardware that are available as channel numbers on this resource.
FF Data Type Bit String
Range Set by manufacturer
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Read Only

404 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.55 HI_ALM

Classification Record
Description Identifies the status and time stamp associated with the high alarm.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

405
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.56 HI_HI_ALM

Classification Record
Description Identifies the status and time stamp associated with the high alarm.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

406 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.57 HI_HI_LIM

Classification Simple Variable

Description Defines the high high alarm limit setting in engineering units.
FF Data Type Float
Range PV_SCALE, + infinity
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is + infinity

407
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.58 HI_HI_PRI

Classification Simple Variable

Description Defines priority of the high high alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

408 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.59 HI_LIM

Classification Simple Variable

Description Defines the high alarm limit setting in engineering units.
FF Data Type Float
Range PV_SCALE, + infinity
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is + infinity

409
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.60 HI_PRI

Classification Simple Variable

Description Defines priority of the high alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks Initial value is 0

410 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.61 IO_OPTS

Classification Simple Variable

Description Identifies user-selectable options for altering the Input and Output block processing.
FF Data Type Bit String
Range
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks See the following Table 3 for a list of the control options by bit and applicable function
block.

Table 12: IO_OPTS Bit Selections

Bit Meaning Function Block

AI DI AO DO
0 Invert X X
1 SP-PV Track in Man X X
2 Reserved
3 SP-PV Track in LO or IMan X X
4 SP Track retained target X X
5 Increase to close X
6 Fault state to value X X
7 Use Fault state value to restart X X
8 Target to Man if fault state activated X X
9 Use PV for BKCAL_OUT X X
10 Low Cutoff X
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved

411
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.62 IN

Classification Record
Description Represents the primary input value of the block. Blocks that filter the input to get the PV
require this parameter.
FF Data Type DS-65
Range
Usage I/Primary Input
Length 5
Valid Views VIEW_3
Storage Non-Volatile
Remarks Read Only
The Data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

412 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.63 IN_1

Classification Record
Description Represents the auxiliary input value to the block. It is used for values other than the PV.
FF Data Type DS-65
Range
Usage I/Input
Length 5
Valid Views VIEW_3
Storage Non-Volatile
Remarks Read Only
The Data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

413
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.64 LIM_Notify

Classification Simple Variable

Description Defines the maximum number of unconfirmed alert notify messages allowed.
FF Data Type Unsigned 8
Range 0 to MAX_NOTIFY
Usage C/Contained
Length 1
Valid Views VIEW_2
Storage Static
Remarks Initial value is MAX_NOTIFY.
This parameter describes the number of alerts that the device can send out at the same
time. A setting of zero results in never transmitting any alarm notifications. It must be set
greater than zero for alarming to work.

414 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.65 L_TYPE

Classification Simple Variable

Description Determines whether the values passed by the Transducer block to the Analog Input block
may be used directly (DIRECT) or, if the value is in different units, must be converted
linearly (indirectly); or with square root (Ind Sqr Root), using the input range defined by
the transducer and associated output range.
FF Data Type Unsigned 8
Range 1. Direct
2. Indirect
3. Ind Sqr Root
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks

415
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.66 LO_ALM

Classification Record
Description Represents the status of the low alarm and its associated time stamp.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

416 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.67 LO_LIM

Classification Simple Variable

Description Defines the setting for the low alarm in engineering units.
FF Data Type Float
Range - Infinity, PV_SCALE
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is - Infinity

417
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.68 LO_LO_ALM

Classification Record
Description Represents the status of the low low alarm and its associated time stamp.
FF Data Type DS-71
Range
Usage C/Alarm
Length 16
Valid Views
Storage Dynamic
Remarks Read Only
The Data type consists of data that describes floating point alarms. It uses the following
five elements.
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

418 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.69 LO_LO_LIM

Classification Simple Variable

Description Defines the setting for the low low alarm in engineering units.
FF Data Type Float
Range - Infinity, PV_SCALE
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Initial value is - Infinity

419
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.70 LO_LO_PRI

Classification Simple Variable

Description Represents the priority of the low low alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks

420 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.71 LO_PRI

Classification Simple Variable

Description Represents the priority of the low alarm.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks

421
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.72 LOW_CUT

Classification Simple Variable

Description Represents the limit used for the flow sensor input processing by the Analog Input block,
if the Low Cutoff selection is chosen in IO_OPTS. If the calculated PV falls below this
limit, the PV value is set to zero (0).
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks This function may be used to eliminate noise near zero from a flow sensor.

422 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.73 MANUFAC_ID

Classification Simple Variable

Description Defines the manufacturer's identification number. An interface device uses this number to
locate the DD file for the resource.
FF Data Type Unsigned 32
Range Set by manufacturer
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Read Only

423
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.74 MAX_NOTIFY

Classification Simple Variable

Description Defines the maximum number of unconfirmed notify messages possible.
FF Data Type Unsigned 8
Range Set by manufacturer
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks Read Only

424 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.75 MEMORY_SIZE

Classification Simple Variable

Description Represents the available configuration memory in the empty resource.
FF Data Type Unsigned 16
Range Set by manufacturer
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks Read Only

425
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.76 MIN_CYCLE_T

Classification Simple Variable

Description Defines the time duration of the shortest cycle interval that the resource can support.
FF Data Type Unsigned 32
Range Set by manufacturer
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks Read Only

426 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.77 MODE_BLK

Classification Record
Description Represents the mode record of the block. Contains the Actual, Target, Permitted, and
Normal modes.
FF Data Type DS-69
Range
Usage C/Mode
Length 4
Valid Views VIEW_1, VIEW_3
Storage Mix
Remarks Normally, the operator has permission to write these values, but PROGRAM or LOCAL
remove that permission and grant it to a supervisory computer or a local control panel.
This block has a mixture of storage types. Static for modes Normal and Permitted, Non-
Volatile for Target mode, and Dynamic for Actual mode.
The data type consists of bit strings for Actual, Target Permitted and Normal modes. It
uses the following four elements.
• 1 Target
• 2 Actual
• 3 Permitted
• 4 Normal

427
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.78 NV_CYCLE_T

Classification Simple Variable

Description Defines interval between writing copies of Non-Volatile (NV) parameters to NV memory.
Zero means never.
FF Data Type Unsigned 32
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks Ready Only

428 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.79 OFFNETALM_ENABLED

Classification Simple Variable

Description Represents enabling or disabling the Block Offnet Diagnostic Alarm. By default, this is
disabled.
FF Data Type Bit String
Range Enable
Disable
Usage Device Offnet Process Alarm
Length
Valid Views
Storage Dynamic
Remarks This is not a Fieldbus block parameter. It is a Honeywell parameter, which is stored
internally on the FIM but appears to reside on the Fieldbus block template.

429
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.80 OUT

Classification Record
Description Represents the primary analog value calculated as a result of executing the function.
FF Data Type DS-65
Range OUT_SCALE +/- 10 percent
Usage O/Primary Output
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Normally, the operator has permission to write this value, but PROGRAM or LOCAL
remove that permission and grant it to a supervisory computer or a local control panel.
The Data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

430 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.81 OUT_D

Classification Record
Description Represents the primary discrete value calculated as a result of executing the function.
FF Data Type DS-66
Range OUT_STATE
Usage O/Primary Output
Length 2
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Normally, the operator has permission to write this value, but PROGRAM or LOCAL
remove that permission and grant it to a supervisory computer or a local control panel.
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

431
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.82 OUT_HI_LIM

Classification Simple Variable

Description Defines the maximum output value limit in all modes, unless the CONTROL_OPTS
selection No Out limits in Manual is chosen.
FF Data Type Float
Range OUT_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks Initial value is 100.

432 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.83 OUT_LO_LIM

Classification Simple Variable

Description Defines the minimum output value limit in all modes, unless the CONTROL_OPTS
selection No Out limits in Manual is chosen.
FF Data Type Float
Range OUT_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks Initial value is 0.

433
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.84 OUT_SCALE

Classification Record
Description Defines the high and low scale values, engineering units code, and number of digits to the
right of the decimal point to be used in displaying the OUT parameter and parameters
that have the same scaling as OUT.
FF Data Type DS-68
Range
Usage C/Scaling
Length 11
Valid Views VIEW_2
Storage Static
Remarks The Data type consists of data that describes floating point values for display purposes. It
uses the following four elements.
• 1 Engineering Units at 100 percent
• 2 Engineering Units at 0 percent
• 3 Units Index
• 4 Decimal Point

434 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.85 OUT_STATE

Classification Simple Variable

Description Represents the index to the text describing the states of a discrete output.
FF Data Type Unsigned 16
Range
Usage C/Contained
Length 2
Valid Views VIEW_2
Storage Static
Remarks

435
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.86 PV

Classification Record
Description Represents either the primary analog value for use in executing the function, or a process
value associated with it. It may also be calculated from the READBACK value of an
Analog Output block.
FF Data Type DS-65
Range
Usage C/Process Variable
Length 5
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

436 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.87 PV_D

Classification Record
Description Represents either the primary discrete value for use in executing the function, or a
process value associated with it. It may also be calculated from the READBACK_D
value of a Discrete Output block.
FF Data Type DS-66
Range
Usage C/Process Variable
Length 2
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

437
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.88 PV_FTIME

Classification Simple Variable

Description Defines the time constant of a single exponential filter for the Process Variable in
seconds.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

438 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.89 PV_SCALE

Classification Record
Description Defines the high and low scale values, engineering units code, and number of digits to the
right of the decimal point to be used in displaying the PV parameter and parameters that
have the same scaling as PV.
FF Data Type DS-68
Range
Usage C/Scaling
Length 11
Valid Views VIEW_2
Storage Static
Remarks The Data type consists of data that describes floating point values for display purposes. It
uses the following four elements.
• 1 Engineering Units at 100 percent
• 2 Engineering Units at 0 percent
• 3 Units Index
• 4 Decimal Point

439
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.90 PV_STATE

Classification Simple Variable

Description Defines the index to the text describing the states of a discrete PV.
FF Data Type Unsigned 16
Range
Usage C/Contained
Length 2
Valid Views VIEW_2
Storage Static
Remarks

440 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.91 RA_FTIME

Classification Simple Variable

Description Defines the time constant of a single exponential filter for the value to be ratioed in
seconds.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

441
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.92 RATE

Classification Simple Variable

Description Defines the derivative time constant in seconds.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

442 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.93 RCAS_IN

Classification Record
Description Represents target set point and status provided by a supervisory host to the analog control
or output block.
FF Data Type DS-65
Range
Usage C/Remote-Cascade In
Length 5
Valid Views VIEW_3
Storage Non-Volatile
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

443
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.94 RCAS_IN_D

Classification Record
Description Represents target set point and status provided by a supervisory host to the analog control
or output block.
FF Data Type DS-66
Range
Usage C/Remote-Cascade In
Length 2
Valid Views VIEW_3
Storage Non-Volatile
Remarks The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

444 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.95 RCAS_OUT

Classification Record
Description Represents block set point and status after ramping. It serves as input to a supervisory
host for back calculation that allows action to be taken under limiting conditions or mode
change.
FF Data Type DS-65
Range
Usage C/Remote-Cascade Out
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

445
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.96 RCAS_OUT_D

Classification Record
Description Represents block set point and status. It serves as input to a supervisory host for back
calculation that allows action to be taken under limiting conditions or mode change.
FF Data Type DS-66
Range
Usage C/Remote-Cascade Out
Length 2
Valid Views VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

446 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.97 READBACK

Classification Record
Description Represents the 'readback' of the actual continuous valve or other actuator position in
transducer units.
FF Data Type DS-65
Range
Usage C/Contained
Length 5
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

447
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.98 READBACK_D

Classification Record
Description Represents the 'readback' of the actual discrete valve or other actuator position in the
transducer state.
FF Data Type DS-66
Range
Usage C/Contained
Length 2
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

448 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.99 RESET

Classification Simple Variable

Description Represents the Integral time constant in seconds. It is the inverse of repeats per minute.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks

449
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.100 RESTART

Classification Simple Variable

Description Allows a manual restart to be initiated. The following degrees of restart are possible.
• 1: Run
• 2: Restart Resource
• 3: Restart with Defaults
• 4: Restart Processor
FF Data Type Unsigned 8
Range 1: Run
2: Restart Resource
3: Restart with Defaults
4: Restart Processor
Usage C/Contained
Length 1
Valid Views
Storage Dynamic
Remarks Changing this parameter, may be fatal to communication.
Note that the Restart with Defaults function restarts the Fieldbus device with factory
default values instead of Experion ones. To restore Experion default values, re-load the
device block through Control Builder with associated blocks set for Full instead of
Partial Load.

450 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.101 ROUT_IN

Classification Record
Description Represents target output and status provided by a host to a control block for use as the
block's output in ROUT mode.
FF Data Type DS-65
Range
Usage C/Remote-Output In
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

451
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.102 ROUT_OUT

Classification Record
Description Represents block output and status. It serves as input to a host for back calculation in
ROut mode that allows action to be taken under limited conditions or mode change
FF Data Type DS-65
Range
Usage C/Remote-Output Out
Length 5
Valid Views VIEW_3
Storage Dynamic
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

452 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.103 RS_STATE

Classification Simple Variable

Description Defines the state of the function block application state machine.
FF Data Type Unsigned 8
Range 1. Start/Restart
2. Initialization
3. On-Line Linking
4. On-Line
5. Standby
6. Failure
Usage C/Resource State
Length 1
Valid Views VIEW_1, VIEW_3
Storage Dynamic
Remarks Read Only

453
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.104 SEL_1

Classification Record
Description Represents first input value to the selector.
FF Data Type DS-65
Range
Usage I/Cascade Input
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

454 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.105 SEL_2

Classification Record
Description Represents second input value to the selector.
FF Data Type DS-65
Range
Usage I/Cascade Input
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

455
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.106 SEL_3

Classification Record
Description Represents third input value to the selector.
FF Data Type DS-65
Range
Usage I/Cascade Input
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

456 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.107 SEL_TYPE

Classification Simple Variable

Description Defines the type of selector action as High, Medium, or Low.
FF Data Type Unsigned 8
Range 1: High
2: Low
3: Medium
Usage C/Contained
Length 1
Valid Views VIEW_4
Storage Static
Remarks

457
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.108 SET_FSTATE

Classification Simple Variable

Description Allows the fault state condition to be manually initiated by selecting Set.
FF Data Type Unsigned 8
Range 1: Off
2: Set
Usage C/Contained
Length 1
Valid Views
Storage Dynamic
Remarks The operator can control PROGRAM or LOCAL access to this value.

458 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.109 SHED_OPT

Classification Simple Variable

Description Defines action to be taken on remote control device timeout.
FF Data Type Unsigned 8
Range 1: Normal Shed, normal return -See Note 1 in Remarks
2: Normal Shed, no return - See Note 2 in Remarks
3: Shed to Auto, normal return
4: Shed to Auto, no return - See Note 3 in Remarks
5: Shed to Manual, normal return
6: Shed to Manual, no return - See Note 4 in Remarks
7: Shed to Retained target, normal return (Not used in Experion)
8: Shed to Retained target, no return ((Not used in Experion)
Usage C/Shed Option
Length 1
Valid Views VIEW_4
Storage Static
Remarks Note 1: Actual mode changes to the next lowest priority non-remote mode permitted but
returns to the target remote mode, when the remote computer completes the initialization
handshake.
Note 2: Target mode changes to the next lowest priority non-remote mode permitted. The
target remote mode is lost, so there is no return to it.
Note 3: Target mode changes to Auto on detection of a shed condition.
Note 4: Target mode changes to Man on detection of a shed condition.

459
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.110 SHED_RCAS

Classification Simple Variable

Description Defines timeout in milliseconds for computer writes to function block RCas locations.
FF Data Type Unsigned 32
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks

460 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.111 SHED_ROUT

Classification Simple Variable

Description Defines timeout in milliseconds for computer writes to function block ROut locations.
FF Data Type Unsigned 32
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks

461
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.112 SIMULATE

Classification Record
Description Allows the transducer analog input or output to the block to be manually supplied, when
SIMULATE is enabled. When SIMULATE is disabled, the simulate value and status
track the actual value and status.
FF Data Type DS-82
Range
Usage C/Simulate
Length 11
Valid Views
Storage Dynamic
Remarks The data type consists of simulate and transducer floating point value and status and a
simulate enable/disable discrete. It uses the following five elements.
1: Simulate Status
2:Simulate Value
3: Transducer Status
4: Transducer Value
5: Simulate Enable/Disable

462 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.113 SIMULATE_D

Classification Record
Description Allows the transducer discrete input or output to the block to be manually supplied, when
SIMULATE is enabled. When SIMULATE is disabled, the simulate value and status
track the actual value and status.
FF Data Type DS-83
Range
Usage C/Simulate
Length 5
Valid Views
Storage Dynamic
Remarks The data type consists of a simulate and transducer discrete value and status and a
simulate enable/disable discrete. It uses the following five elements.
1: Simulate Status
2:Simulate Value
3: Transducer Status
4: Transducer Value
5: Simulate Enable/Disable

463
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.114 SP

Classification Record
Description Defines the set point of any analog block.
FF Data Type DS-65
Range PV_SCALE +/- 10 percent
Usage C/Set point
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks SP (SP_D) is normally written by an operator occasionally while in Auto mode. It is not
intended to be written as a cascade setpoint input. Instead, a connection to CAS_IN is
intended to provide a value into SP (SP_D) when in Cas mode and a write into RCAS_IN
is intended to provide a value into SP (SP_D) when in RCas mode. However, SP (SP_D)
may be updated when operating in ROut mode in order to provide a reasonable setpoint,
if failing from ROut to Auto mode upon a failure of the ROUT_IN update.
The data type consists of the value and status of floating point parameters that are Inputs
or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

464 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.115 SP_D

Classification Record
Description Defines the set point of any discrete block.
FF Data Type DS-66
Range PV_STATE
Usage C/Set point
Length 2
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks SP (SP_D) is normally written by an operator occasionally while in Auto mode. It is not
intended to be written as a cascade setpoint input. Instead, a connection to CAS_IN is
intended to provide a value into SP (SP_D) when in Cas mode and a write into RCAS_IN
is intended to provide a value into SP (SP_D) when in RCas mode. However, SP (SP_D)
may be updated when operating in ROut mode in order to provide a reasonable setpoint,
if failing from ROut to Auto mode upon a failure of the ROUT_IN update.
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

465
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.116 SP_HI_LIM

Classification Simple Variable

Description Defines the high limit for set point entry.
FF Data Type Float
Range PV_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks Initial value is 100 percent

466 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.117 SP_LO_LIM

Classification Simple Variable

Description Defines the low limit for set point entry.
FF Data Type Float
Range PV_SCALE +/- 10 percent
Usage C/Contained
Length 4
Valid Views VIEW_2
Storage Static
Remarks Initial value is zero (0)

467
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.118 SP_RATE_DN

Classification Simple Variable

Description Defines the downward ramp rate in PV units per second for set point changes to invoke
action in the Auto mode.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks If the ramp rate is set to zero or the block is not in Auto mode, the set point change is
invoked immediately.

468 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.119 SP_RATE-UP

Classification Simple Variable

Description Defines the upward ramp rate in PV units per second for set point changes to invoke
action in the Auto mode.
FF Data Type Float
Range Positive
Usage C/Contained
Length 4
Valid Views VIEW_4
Storage Static
Remarks If the ramp rate is set to zero or the block is not in Auto mode, the set point change is
invoked immediately.

469
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.120 ST_REV

Classification Simple Variable

Description Defines the revision level of the static data associated with the function block. The
revision value is incremented each time a static parameter value in the block is changed.
FF Data Type Unsigned 16
Range
Usage C/Static Revision
Length 2
Valid Views VIEW_1, VIEW_2, VIEW_3, VIEW_4
Storage Static
Remarks Read Only

470 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.121 STATUS_OPTS

Classification Simple Variable

Description Defines user-selectable options for the block processing of status.
FF Data Type Bit String
Range
Usage C/Contained
Length 2
Valid Views VIEW_4
Storage Static
Remarks See the following Table 4 for a list of the control options by bit and applicable function
block.

Table 13: STATUS_OPTS Bit Selections

Bit Meaning Function Block

AI DI AO DO ML BG CS PD PID RA
0 IFS if BAD IN X X X X X X
1 IFS if BAD CAS_IN X X X X X X
2 Use Uncertain as Good X X X X X X
3 Propagate Failure Forward X X
4 Propagate Failure Backward X X X X
5 Target to Manual if BAD IN X X
6 Uncertain if Limited X
7 BAD if Limited X
8 Uncertain if Man Mode X X X X
9 Do not select if not Auto mode X X X X
10 Do not select if not Cas mode X X
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved

471
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.122 STRATEGY

Classification Simple Variable

Description Assists in grouping blocks. This data is not checked or processed by the block.
FF Data Type Unsigned 16
Range
Usage C/Strategy
Length 2
Valid Views VIEW_4
Storage Static
Remarks

472 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.123 TAG_DESC

Classification Simple Variable

Description Serves as user defined description of the block.
FF Data Type Octet String
Range
Usage C/Tag Description
Length 32
Valid Views
Storage Static
Remarks Initial value is 32 space characters

473
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.124 TEST_RW

Classification Record
Description Defines read/write test parameter.
FF Data Type DS-85
Range
Usage C/Test
Length 112
Valid Views
Storage Dynamic
Remarks The data type consists of function block test read/write data. It uses the following 15
elements.
• 1 Value 1 (Boolean)
• 2 Value 2 (Integer 8)
• 3 Value 3 (Integer 16)
• 4 Value 4 (Integer 32)
• 5 Value 5 (Unsigned 8)
• 6 Value 6 (Unsigned 16)
• 7 Value 7 (Unsigned 32)
• 8 Value 8 (Floating Point)
• 9 Value 9 (Visible String)
• 10 Value 10 (Octet String)
• 11 Value 11 (Date)
• 12 Value 12 (Time of Day)
• 13 Value 13 (Time Difference)
• 14 Value 14 (Bit String)
• 15 Value 15 (Time Value)

474 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.125 TRK_IN_D

Classification Record
Description Represents the discrete input for initiation of the external tracking function.
FF Data Type DS-66
Range
Usage I/Input
Length 2
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only
The data type consists of the value and status of discrete value parameters. It uses the
following two elements.
• 1 Status
• 2 Value

475
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.126 TRK_SCALE

Classification Record
Description Defines the high and low scale values, engineering units code, and number of digits to the
right of the decimal point associated with TRK_VAL.
FF Data Type DS-68
Range
Usage C/Scaling
Length 11
Valid Views VIEW_4
Storage Static
Remarks The Data type consists of data that describes floating point values for display purposes. It
uses the following four elements.
• 1 Engineering Units at 100 percent
• 2 Engineering Units at 0 percent
• 3 Units Index
• 4 Decimal Point

476 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.127 TRK_VAL

Classification Record
Description Represents the input value for external tracking.
FF Data Type DS-65
Range
Usage I/Input
Length 5
Valid Views VIEW_1, VIEW_3
Storage Non-Volatile
Remarks Read Only The data type consists of the value and status of floating point parameters that
are Inputs or Outputs. It uses the following two elements.
• 1 Status
• 2 Value

477
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.128 UPDATE_EVT

Classification Record
Description Represents an alert generated by any change to the static data.
FF Data Type DS-73
Range
Usage C/Event Update
Length 1, 4
Valid Views
Storage Dynamic
Remarks Read Only
The data type consists of data that describes a static revision alarm. It uses the following
five elements.
• 1 Unacknowledged
• 2 Update State
• 3 Time Stamp
• 4 Static Revision
• 5 Relative Index

478 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.129 WRITE_ALM

Classification Record
Description Represents alert that is generated if the write lock is cleared.
FF Data Type DS-72
Range
Usage C/Alarm
Length 1, 3
Valid Views
Storage Dynamic
Remarks Read Only
The data type describes discrete alarms using the following five elements:
• 1 Unacknowledged
• 2 Alarm State
• 3 Time Stamp
• 4 Subcode
• 5 Value

479
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.130 WRITE_LOCK

Classification Simple Variable

Description Used to disallow writes from anywhere, except to unlock/clear this parameter, when it is
locked/set. Inputs will continue to read.
FF Data Type Unsigned 8
Range 1: Unlocked
2: Locked
Usage C/Contained
Length 1
Valid Views VIEW_2
Storage Static
Remarks The operator can control PROGRAM and LOCAL access to this value.

480 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.131 WRITE_PRI

Classification Simple Variable

Description Defines the priority of the alarm generated by clearing the WRITE_LOCK.
FF Data Type Unsigned 8
Range 0 to 63
Usage C/Alert Priority
Length 1
Valid Views VIEW_4
Storage Static
Remarks

481
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.132 XD_SCALE

Classification Record
Description Defines the high and low scale values, engineering units code, and number of digits to the
right of the decimal point used with a specified channel value obtained from the
Transducer.
FF Data Type DS-68
Range
Usage C/Scaling
Length 11
Valid Views VIEW_2
Storage Static
Remarks The Data type consists of data that describes floating point values for display purposes. It
uses the following four elements.
• 1 Engineering Units at 100 percent
• 2 Engineering Units at 0 percent
• 3 Units Index
• 4 Decimal Point

482 www.honeywell.com
 22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

22.133 XD_STATE

Cla Simple Variable

ssifi
cati
on
Des Represents index to the text describing the states of a discrete for the value obtained from the Transducer.
crip
tion
FF Unsigned 16
Dat
a
Typ
e
Ran
ge
Usa C/Contained
ge
Len 2
gth
Vali VIEW_2
d
Vie
ws
Stor Static
age
Re
mar
ks

483
22 STANDARD FUNCTION BLOCK PARAMETERS REFERENCE

484 www.honeywell.com
23 Glossary of Fieldbus Terms

The following table lists some Fieldbus terms and abbreviations for general reference.

Term Abbreviation Description

Application Process AP
Capability File The Capability file contains some or all of the given Fieldbus device's
information that can be read from a device online. It consists of both
resource information (what the device can potentially do) and value
information (how the device should actually be set up).
Common File Format CFF The format of a Capability file is a readable text document based on a
Windows Initialization (INI) file type.
Connection Manager A Fieldbus Foundation service to manage connection information about
device types, devices, and blocks that are actively communicating with a
host application.
Data Link Entity DLE
Data Link Layer DLL Defined in ISO 7498
Data Link Layer DLME
Management Entity
Data Link Protocol Data DLPDU
Unit
Device Description DD A binary file (*.ff0) that provides the definition for parameters in the
FBAP of a device. For example, what Function Blocks a device contains,
and what parameters are in those blocks.

485
23 GLOSSARY OF FIELDBUS TERMS

Term Abbreviation Description

Device Description Item DD Item Item is a fundamental concept of the Device Description Language (DDL).
It makes up the description of the device and can be any of the following
constructs:
• Array*
• Block*
• Collection
• Domain
• Edit Display
• Item Array
• Menu
• Method
• Program
• Record*
• Refresh Relation
• Response Code
• Variable*
• Variable List*
• WAO Relation
* These items are of the most interest to Block Type templates.
Device Description DDL The language that vendors use to define their device's Function blocks and
Language parameters.
Device Description Object DDO The suffix name for incremental DD binary files supplied by vendors that
are to be converted to full and complete DD binary files by the Fieldbus
Foundation Synthesizer.
Device Description Service DDS A software library developed by the Fieldbus Foundation that provides a
generic access to a DD.
DD Synthesizer A tool supplied by the Fieldbus Foundation. It combines incremental DDs,
with unresolved references, with Fieldbus Foundation standard DDs to
produce a complete/full DD that can be used with DDS.
Enhanced Device EDD A newer version of the binary file (*.ff5) that provides the definition for
Description parameters in the FBAP of a device. For example, what Function Blocks a
device contains, and what parameters are in those blocks.
Enhanced Device EDDL The language that vendors use to define their device's Function blocks and
Description Language parameters.
Fieldbus Access Sublayer FAS
Fieldbus Foundation FFO or FF5 The suffix name for the complete/full DD binary file.
Object
Fieldbus Foundation A Fieldbus Foundation tool that converts an ASCII text file written in
Tokenizer conformance with the Device Description Language specification into a
DD binary file.
Fieldbus Message FMS
Specification
H1 Fieldbus Segment An independent electrical environment consisting of wire, terminators and
a power source per IEC 61158-1/ISA S50.1 for supporting Fieldbus
devices.
H1 Fieldbus Link The logical medium by which H1 Fieldbus devices are interconnected. It is
composed of one or more physical segments interconnected by bus
Repeaters or Couplers. All of the devices on a link share a common
schedule, which is administered by that link's current LAS.

486 www.honeywell.com
 23 GLOSSARY OF FIELDBUS TERMS

Term Abbreviation Description

Immediate Response IRRD
Recovery Delay
International Organization ISO
For Standardization
Link Active Scheduler LAS A Link bus scheduler that maintains a list of transmission times for all data
buffers in all devices that need to be periodically transmitted. Only one
Link Master (LM) device on an H1 Fieldbus Link can be functioning as
that link's LAS.
Medium Attachment Unit MAU For wire media MAU = transceiver.
Medium Dependent MDS
Sublayer
Network Management NMA
Agent
Object Dictionary OD Contains the Object Descriptions for communication objects such as
DataType, DataTypeStructureDescription, and SimpleVariable.
Open Systems OSI
Interconnection
Pass Token Data Link PT DLPDU
Protocol Data Unit
Physical Layer PhL
Physical Layer Overhead PhLO
Physical Layer Protocol PhPDU
Data Unit
Production Rules The grammar, in BNF format, used to describe a language. The Common
File Format used to construct the Resource file follows specific production
rules.
Release Directory A directory structure used to store the DD and related files. Each
manufacturer has a directory name that is the registered manufacturer ID
number. There is a directory for each device type that a manufacturer
produces under their ID directory.
Resource File The part of the Capability file that is supplied by the manufacturer. It
describes the communication profile, device capacity, internal record
address assignments, and certain default values for a field device. A
Capability file that has only this content is often called a Resource file.
Standard Dictionary A Fieldbus Foundation file that contains standard strings and
enumerations. A compressed form of the file is called the IMPORT.DCT
and it is used by the Type function in Control Builder.
Symbol File SYM Contains symbolic names that were used in the DDL file for the FBAP of
the device. It is produced by the Fieldbus Foundation Tokenizer.
System Management SMK
Kernel
System Management SMKP
Kernel Protocol
Virtual Communications VCR Sets up communications for host to talk to a device. It acts like a speed
Relationship dialer to provide for the transfer of data between applications.
FOUNDATION Fieldbus describes these three types of VCRs:
• Publish/Subscribe
• Client/Server
• Source/Sink

487
23 GLOSSARY OF FIELDBUS TERMS

Term Abbreviation Description

Virtual Field Device VFD The management or FBAP section of a device that is addressable by a
VFD tag.

488 www.honeywell.com
24 Notices

Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of Honeywell
International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.

Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention
of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third party
materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses,
notices, restrictions and obligations, if any, may be found in the materials accompanying the product, in the
documents or files accompanying such third party materials, in a file named third_party_licenses on the media
containing the product, or at http://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
[email protected]
Use this email address to provide feedback, or to report errors and omissions in the documentation. For
immediate help with a technical problem, contact your local Honeywell Process Solutions Customer Contact
Center (CCC) or Honeywell Technical Assistance Center (TAC).

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be
exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.
To report a potential security vulnerability against any Honeywell product, please follow the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
• Send an email to [email protected].
or

489
24 NOTICES

• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical
Assistance Center (TAC) listed in the “Support” section of this document.

Support
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find your
local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/
Pages/default.aspx.

Training classes
Honeywell holds technical training classes about Experion PKS. These classes are taught by experts in the field
of process control systems. For more information about these classes, contact your Honeywell representative, or
see http://www.automationcollege.com.

490 www.honeywell.com