0% found this document useful (0 votes)

669 views560 pages

Series A Fieldbus Interface Module User Guide

honeywell

Uploaded by

Thush Thushanth

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

669 views560 pages

Series A Fieldbus Interface Module User Guide

honeywell

Uploaded by

Thush Thushanth

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 560

Honeywell Process Solutions

Experion PKS

Series A Fieldbus Interface

Module
User's Guide
EP-DCX166
R400
July 2010

Release R400
Honeywell

Downloaded from www.Manualslib.com manuals search engine

Notices and Trademarks

While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell
International Inc.
Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA
1-800 822-7673

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

About This Document

Provides guidelines and procedures for interfacing fieldbus devices with an Experion system. It
includes module installation, configuration, operation, maintenance, and FOUNDATION
Fieldbus reference data.

Release Information
Document Name
Series A Fieldbus Interface Module User's
Guide - figd

Document ID

Release
Number

Publication
Date

EP-DCX166

R400

July 2010

Document Category
Purpose

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

iii

Support and Other Contacts

United States and Canada
Contact:
Phone:

Fascimile:
Mail:

Honeywell Solution Support Center

1-800-822-7673
Calls are answered by dispatcher between 6:00 am and 4:00 pm
Mountain Standard Time. Emergency calls outside normal working hours
are received by an answering service and returned within one hour.
1-973-455-5000
Honeywell TAC, MS L17
1860 W. Garden Lane
Phoenix, AZ, 85027 USA

Europe, Middle East, and Africa (EMEA)

Contact:
Phone:
Fascimile:
Mail:

Honeywell TAC-EMEA
+32-2-728-2345
+32-2-728-2696
TAC-BE02
Hermes Plaza
Hermeslaan, 1H
B-1831 Diegem, Belgium

Contact:
Phone:

Honeywell Global TAC Pacific

1300-364-822 (toll free within Australia)
+61-8-9362-9559 (outside Australia)
+61-8-9362-9564
Honeywell Limited Australia
5 Kitchener Way
Burswood 6100, Western Australia
GTAC@honeywell.com

Pacific

Fascimile:
Mail:

Email:

India
Contact:
Phone:
Fascimile:
Mail:

Email:

Honeywell Global TAC India

+91-20- 6603-9400
+91-20- 6603-9800
Honeywell Automation India Ltd
56 and 57, Hadapsar Industrial Estate
Hadapsar, Pune 411 013, India
Global-TAC-India@honeywell.com

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Support and Other Contacts

Korea
Contact:
Phone:
Fascimile:
Mail:

+65-6580-3500
+65-6580-3501
+65-6445-3033
Honeywell Private Limited
Honeywell Building
17, Changi Business Park Central 1
Singapore 486073
GTAC-SEA@honeywell.com

Taiwan
Contact:
Phone:
Fascimile:
Mail:

Email:

R400
July 2010

Honeywell Global TAC Taiwan

+886-7-536-2567
+886-7-536-2039
Honeywell Taiwan Ltd.
17F-1, No. 260, Jhongshan 2nd Road.
Cianjhen District
Kaohsiung, Taiwan, ROC
Global-TAC-Taiwan@honeywell.com

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

Support and Other Contacts

Japan
Contact:
Phone:
Fascimile:
Mail:

Email:

Honeywell Global TAC Japan

+81-3-6730-7160
+81-3-6730-7228
Honeywell Japan Inc.
New Pier Takeshiba, South Tower Building,
20th Floor, 1-16-1 Kaigan, Minato-ku,
Tokyo 105-0022, Japan
Global-TAC-JapanJA25@honeywell.com

Elsewhere
Call your nearest Honeywell office.

World Wide Web

Honeywell Solution Support Online:
http://www.honeywell.com/ps

Training Classes
Honeywell Automation College:
http://www.automationcollege.com

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Symbol Definitions

Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol

Definition
ATTENTION: Identifies information that requires special
consideration.

TIP: Identifies advice or hints for the user, often in terms of

performing a task.
REFERENCE -EXTERNAL: Identifies an additional source of
information outside of the bookset.
REFERENCE - INTERNAL: Identifies an additional source of
information within the bookset.

CAUTION

Indicates a situation which, if not avoided, may result in equipment

or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.
CAUTION: Indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.
WARNING: Indicates a potentially hazardous situation, which, if not
avoided, could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

vii

Symbol Definitions

Symbol

Definition
WARNING, Risk of electrical shock: Potential shock hazard where
HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or
60 VDC may be accessible.
ESD HAZARD: Danger of an electro-static discharge to which
equipment may be sensitive. Observe precautions for handling
electrostatic sensitive devices.
Protective Earth (PE) terminal: Provided for connection of the
protective earth (green or green/yellow) supply system conductor.

Functional earth terminal: Used for non-safety purposes such as

noise immunity improvement. NOTE: This connection shall be
bonded to Protective Earth at the source of supply in accordance
with national local electrical code requirements.
Earth Ground: Functional earth connection. NOTE: This
connection shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.
Chassis Ground: Identifies a connection to the chassis or frame of
the equipment shall be bonded to Protective Earth at the source of
supply in accordance with national and local electrical code
requirements.

viii

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Contents
1.

INTRODUCTION ..........................................................................23
1.1

Where to look for information...................................................................... 23

Contents guide .....................................................................................................................23

1.2

Conventions................................................................................................... 24

Terms and type representations...........................................................................................24

WHAT IS FIELDBUS?..................................................................27
2.1

Fieldbus Organization .................................................................................. 27

About the Fieldbus Foundation ............................................................................................27

Want more information? .......................................................................................................27

2.2

Fieldbus Technology .................................................................................... 27

Reference.............................................................................................................................27

2.3

Fieldbus Terms.............................................................................................. 27

Description ...........................................................................................................................27

FIELDBUS INTEGRATION WITH EXPERION SYSTEM .............33

3.1

Overview ........................................................................................................ 33

Background ..........................................................................................................................33
CIOM-A FIM versus Series C FIM........................................................................................33
Non-Redundant Fieldbus integrated architecture for CIOM-A FIM.......................................34
Redundant Fieldbus integrated architecture for CIOM-A FIM ..............................................35
Fieldbus Interface Module (FIM) - the key to integration ......................................................37
Redundancy Module - the key to redundant operation.........................................................37
Control Builder serves as common configuration tool ..........................................................37
Parameter Definition Editor serves as key interoperability tool ............................................39
Parameter Definition Editor supports Fieldbus Methods ......................................................40
Station provides centralized operator interface ....................................................................41

3.2

Control Integration........................................................................................ 42

FIM handles data integration................................................................................................42

About link object...................................................................................................................42
Network Management description........................................................................................42
System Management description .........................................................................................43
About device objects ............................................................................................................43
About VFD objects ...............................................................................................................43
Type creation makes integration possible ............................................................................44
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

Contents

Fieldbus device Analog Input integration............................................................................. 44

Fieldbus Analog Input data manipulation ............................................................................ 45
Fieldbus device Analog Output or PID integration............................................................... 46
Fieldbus Analog Output or PID data manipulation............................................................... 48
Fieldbus device Discrete Input integration........................................................................... 50
Fieldbus Discrete Input data manipulation .......................................................................... 51
Fieldbus device Discrete Output data integration ................................................................ 52
Fieldbus Discrete Output data manipulation........................................................................ 53
Interface Connections Summary ......................................................................................... 54
A word about SCM parameter interaction ........................................................................... 54
Fieldbus status data details ................................................................................................. 55
Fieldbus status indications .................................................................................................. 57

3.3

Control Mode Interaction ..............................................................................57

Fieldbus block modes versus control modes....................................................................... 57

Control mode priorities and indications ............................................................................... 59
Rotary Switch Model versus Toggle Switch Model.............................................................. 61
Display indications and mode calculation............................................................................ 62
Access control through GRANT_DENY parameter ............................................................. 63

3.4

Link and Block Schedules ............................................................................64

Link Active Scheduler (LAS) and Link Master ..................................................................... 64

Link Schedule...................................................................................................................... 66
Function block execution schedule...................................................................................... 67

3.5

Tags, Addresses, and Live List....................................................................69

Tag and address assignments ............................................................................................ 69

A word about fieldbus address assignments in Control Builder........................................... 70
Live List and Uncommissioned Devices .............................................................................. 70

3.6

Notification Scheme ......................................................................................71

Fieldbus versus Experion Alarm Priorities ........................................................................... 71

Advanced Alarming ............................................................................................................. 73
Fieldbus Alarm Conditions .................................................................................................. 73
Loading alarm conditions .................................................................................................... 77
Alarm server operation ........................................................................................................ 77

3.7

CIOM-A FIM Redundancy Functionality ......................................................78

About CIOM-A FIM redundancy .......................................................................................... 78

CIOM-A FIM versus C200 CPM redundancy....................................................................... 79
Switchover and Secondary readiness ................................................................................. 80
Switchover behavior considerations .................................................................................... 81
Failure conditions and switchover ....................................................................................... 82
Fieldbus network switchover considerations ....................................................................... 83
Switchover versus fieldbus network activities...................................................................... 84
Switchover events ............................................................................................................... 86

3.8

Block Instantiation Support..........................................................................86

About instantiable blocks..................................................................................................... 86

Control Builder supports block instantiation ........................................................................ 86
x

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Contents

Instantiable block implementation considerations ................................................................87

INSTALLATION ...........................................................................99
4.1

Planning Considerations.............................................................................. 99

Experion system references.................................................................................................99

Installation declaration .........................................................................................................99
CIOM-A FIM and I/O module allowance...............................................................................99
CIOM-A FIM only chassis configuration considerations .....................................................100
Fieldbus component references .........................................................................................101
Fieldbus network references ..............................................................................................102
Fieldbus wiring selection and calculation ...........................................................................103
Intrinsically safe applications..............................................................................................104

4.2

Installing CIOM-A Fieldbus Interface Module TC-FFIF01 ........................ 104

Front View ..........................................................................................................................104

Inserting module in chassis ................................................................................................105
Connecting RTP cable to module.......................................................................................107
Loading FIM firmware ........................................................................................................108

4.3
Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TCFFSP02 .................................................................................................................... 109
Front view...........................................................................................................................109
Mounting on a DIN rail .......................................................................................................110
Mounting Dimensions.........................................................................................................111
Wiring .................................................................................................................................112

CONFIGURATION .....................................................................117
5.1

Before You Start .......................................................................................... 117

What do you know about Control Builder? .........................................................................117

Do you know how to configure a Control Processor Module? ............................................117
Can you configure a Control Module?................................................................................117
Are you familiar with your system architecture? .................................................................117
Do you understand and have experience with fieldbus? ....................................................117
Are you Ready? .................................................................................................................118

5.2

Non-Experion Interface Precautions......................................................... 118

5.3

Free VCR Recommendation....................................................................... 119

5.4

Configuring Fieldbus Components In a Control Strategy ...................... 120

About control strategy configuration...................................................................................120

Example Application and Control Strategy for Procedural Reference ................................120
Configuration considerations only for redundant CIOM-A FIM applications .......................122
Adding CIOM-A FIM block to Project .................................................................................123
Checking link configuration ................................................................................................133
Creating a Fieldbus device type from vendor DD...............................................................141
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

Contents

Editing device block parameters........................................................................................ 145

Adding a fieldbus device to Project ................................................................................... 146
Assigning a device to a Link in Project .............................................................................. 151
Checking device configuration........................................................................................... 154
Making fieldbus block template and assigning function block to device ............................ 164
Creating Control Module for sample PID loop - Optional................................................... 172

5.5

Loading Components Online......................................................................202

About load operations ....................................................................................................... 202

About Load Dialog box ...................................................................................................... 204
Load order guidelines........................................................................................................ 205
General load considerations.............................................................................................. 206
Fieldbus device states....................................................................................................... 206
Fieldbus device matching rules ......................................................................................... 207
Loading a CIOM-A FIM and its Links................................................................................. 208
Matching uncommissioned device to project device or vice versa .................................... 211
Loading Link contents or fieldbus device........................................................................... 219

5.6

Configuring Advanced Alarming ...............................................................225

Overview ........................................................................................................................... 225

Opening the Configuration dialog box ............................................................................... 226
Configuring/creating a condition ........................................................................................ 227
Managing the conditions ................................................................................................... 230
Enabling or disabling a condition....................................................................................... 230
Assigning criticalities and priorities.................................................................................... 232
Editing an existing condition .............................................................................................. 233

5.7

Block Offnet Diagnostic Alarm...................................................................234

Behavior of the Block Offnet and Device Offnet System alarms in various communication loss
scenarios ........................................................................................................................... 235
Behavior of the Block Offnet and Device Offnet System alarms in various operational
scenarios ........................................................................................................................... 236

5.8

Configuring non-cache parameters...........................................................238

5.9

Summary ......................................................................................................240

OPERATION.............................................................................. 243
6.1

Monitoring Fieldbus Functions Through Station Displays .....................243

Using Station Detail displays ............................................................................................. 243

6.2

Foundation Fieldbus Detail Displays/Faceplates.....................................244

Detail Displays contents based on FF control points loading ............................................ 245

Naming conventions for Detail Displays ............................................................................ 245
Tabs of FF Detail Displays ................................................................................................ 246
Detail Displays tabs of the different Foundation Fieldbus blocks....................................... 247
Common functionalities of faceplates................................................................................ 250
FF Detail Displays example templates for Control Builder ................................................ 252
xii

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Contents

Using Station Event Summary display ...............................................................................252

6.3

Monitoring Fieldbus Functions Through Monitoring Tab....................... 253

Inactivating/Activating a Link ..............................................................................................253

Monitoring/Interacting with given component/block............................................................256
Checking/changing fieldbus device functional class...........................................................257
Checking live list and interacting with uncommissioned devices........................................264
Viewing and optimizing Link schedule configuration ..........................................................267
CheckingCIOM-A FIM redundancy status and initiating manual switchover ......................273
Using Controller menu functions ........................................................................................275

FIELDBUS DEVICE COMMISSIONING.....................................277

7.1

Getting Started ............................................................................................ 277

Read this first .....................................................................................................................277

Initial checks and operations ..............................................................................................279

7.2

Connecting Devices.................................................................................... 280

7.3

Checking Device.......................................................................................... 282

7.4

Checking Control Strategy......................................................................... 283

7.5

Flowchart Summary.................................................................................... 284

MAINTENANCE, CHECKOUT, AND CALIBRATION................287

8.1

Adding, Removing and Replacing Components...................................... 287

About removal and insertion under power (RIUP)..............................................................287

General procedure .............................................................................................................287
Guidelines for adding fieldbus device to "live"/operating Link ............................................288
Using optional safe handling of new devices......................................................................289
Replacing a failed device with a like device having the same model name and device revision
...........................................................................................................................................290
Replacing a failed device with a different device using a different block type ....................297

8.2

Unlike Device Replacement Report........................................................... 317

8.3

Replacing Device Template with a Different One .................................... 320

Prerequisites ......................................................................................................................320
Considerations ...................................................................................................................321
Using Unlike Template Replacement wizard to make device replacements ......................321

8.4

Correcting Some Common UTR errors..................................................... 328

8.5

Upgrading Firmware in Uncommissioned Device ................................... 328

8.6

Changing or Clearing Tag and/or Address of Uncommissioned Device332

8.7

Using Fieldbus Device Simulate Function ............................................... 334

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

xiii

Contents

8.8

Preparing Fieldbus Device for a Move or Software Migration ................343

Migrating Fieldbus device type to a release supporting Enable Block Offnet Diagnostic Alarm
.......................................................................................................................................... 347

8.9

Interpreting Component LED Indications .................................................348

CIOM-A FIM LED indications ............................................................................................ 348

8.10

FIM Self-Test Diagnostic Codes .............................................................349

8.11

Checking Fieldbus Device Calibration...................................................358

8.12

Using Fieldbus Methods Manager..........................................................359

Prerequisites ..................................................................................................................... 359

Launching Methods Manager ............................................................................................ 360
Interacting with Methods Manager .................................................................................... 360

EXPERION PKS HOST REGISTRATION ................................. 365

9.1

Overview .......................................................................................................365

New features ..................................................................................................................... 365

Conditional support for FF devices.................................................................................... 367
EDDL................................................................................................................................. 368
DD View tab ...................................................................................................................... 368
Following are some of the considerations for FF blocks with DD View. ............................ 373
Persistent data handling.................................................................................................... 375

10.

APPENDIX A ............................................................................. 377

10.1

Fieldbus Technology ...............................................................................377

Open communications architecture ................................................................................... 377

Communication layer description ...................................................................................... 378

10.2

Standard Function Blocks.......................................................................381

Overview ........................................................................................................................... 383

About modes of operation ................................................................................................. 384
Analog Input block............................................................................................................. 386
Analog Output block .......................................................................................................... 388
Bias/Gain block ................................................................................................................. 390
Control Selector block ....................................................................................................... 393
Discrete Input block........................................................................................................... 396
Discrete Output block ........................................................................................................ 397
Manual Loader block ......................................................................................................... 400
Proportional/Derivative block............................................................................................. 402
Ratio block ........................................................................................................................ 412

10.3

Device Descriptions and Block Parameters..........................................416

About Device Descriptions ................................................................................................ 416

Device Description Language ........................................................................................... 416
Device Description infrastructure....................................................................................... 416
xiv

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Contents

Block parameter definitions ................................................................................................417

10.4

Fieldbus Foundation Documents........................................................... 418

Reference Data ..................................................................................................................418

Downloaded from www.Manualslib.com manuals search engine

xvii

Contents

12.1

Fieldbus Status Display Indications ......................................................495

12.2

Substatus Definitions for Quality Status ...............................................502

13.

APPENDIX D ............................................................................. 507

13.1

14.

Mode Change Conditions........................................................................507

APPENDIX E ............................................................................. 511

14.1

Fieldbus Wiring Considerations.............................................................511

Fieldbus topologies ........................................................................................................... 511

Power Conditioning ........................................................................................................... 512
Power distribution.............................................................................................................. 513
Signal degradation limitations............................................................................................ 513
Cable guidelines summary ................................................................................................ 514
Cable Attenuation.............................................................................................................. 515
Signal distortion versus capacitance ................................................................................. 515
Attenuation calculation summary....................................................................................... 516
Cable test .......................................................................................................................... 516

15.

APPENDIX F.............................................................................. 517

15.1

16.

About Parameter Definition Editor for Fieldbus Device Block............517

APPENDIX G ............................................................................. 519

16.1

Loading CIOM-A FIM firmware................................................................519

Checking CIOM-A FIM firmware status ............................................................................. 519

Checking firmware version ................................................................................................ 520
Loading Boot code ............................................................................................................ 525
Loading Personality image ................................................................................................ 529

17.

APPENDIX H ............................................................................. 533

17.1

Important Functional Considerations ....................................................533

General ............................................................................................................................. 533

18.

APPENDIX I............................................................................... 539

18.1

Link Parameters Reference.....................................................................539

Background ....................................................................................................................... 539

More detailed information.................................................................................................. 540

xviii

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Contents

18.2

Description ............................................................................................... 540

Parameters for Link Configuration in Project Mode............................................................540

Parameters for Link Configuration in Monitor Mode ...........................................................551
Some term abbreviations ...................................................................................................555

19.

APPENDIX J ..............................................................................557

19.1

Load Interactions for Fieldbus Related Operations............................. 557

Summary............................................................................................................................557

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

1. Introduction
1.1

Where to look for information

Contents guide
Read this section,

If you,

What is Fieldbus? - Fieldbus Organization

Have no idea what the Fieldbus Foundation

TM
is or what constitutes the FOUNDATION
Fieldbus technology. This section lists some
common fieldbus terms for reference. It also
references, which includes descriptions of
some standard fieldbus function blocks and
describes the role of Device Descriptions and
block parameters for general reference.

Fieldbus Integration With Experion

System - Control Integration

Want some insight on what functional

relationships result from the integration of
fieldbus devices with an Experion system. The
information in this section will be helpful
background for planning and configuring your
control strategy.

Installation - Planning Considerations

Will be responsible for setting up the hardware

infrastructure to support fieldbus devices. This
section identifies the things you should
consider before installing any equipment and
provides detailed procedures for how to install
the Fieldbus Interface Module (FIM) and its
companion Remote Termination Panel (RTP).

Configuration- Configuring Fieldbus

Components In a Control Strategy

Will be configuring the control strategy through

Control Builder. This section provides detailed
procedures for including fieldbus functional
components in your overall control strategy. It
includes creating hardware blocks, making
block types, associating blocks, assigning
modules, assigning devices, and loading
components

Operation - Monitoring Fieldbus Functions

Through Monitoring Tab

Will be monitoring system operation. This

section provides an overview of functions you
can monitor through Station displays and the
Monitoring tab in Control Builder.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

1. Introduction
1.2. Conventions

Read this section,

If you,

Fieldbus Device Commissioning - Getting

Started

Will be commissioning the fieldbus loop. This

section provides a suggested process to follow
for fieldbus device commissioning.

Maintenance, Checkout, and Calibration Adding, Removing and Replacing

Components

Will be responsible for maintaining and trouble

shooting system operation. This section
provides information about replacing
components, upgrading firmware in
uncommissioned devices, and checking device
calibration.

1.2

Conventions

Terms and type representations

The following table summarizes the terms and type representation conventions used in
this Guide.
Term/Type
Representation

Meaning

Example

Click

Click left mouse button once.

(Assumes cursor is positioned on
object or selection.)

Click the Browse button.

Double-click

Click left mouse button twice in quick

succession. (Assumes cursor is
positioned on object or selection.)

Double click the Station

icon.

Drag

Press and hold left mouse button

while dragging cursor to new screen
location and then release the button.
(Assumes cursor is positioned on
object or selection to be moved.)

Drag the PID function

block onto the Control
Drawing.

Right-click

Click right mouse button once.

(Assumes cursor is positioned on
object or selection.)

Right-click the AND

function block.

<F1>

Keys to be pressed are shown in

angle brackets.

Press <F1> to view the

online Help.

Keys to be pressed together are

shown with a plus sign.

Press <Ctrl>+<C> to
close the window.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

1. Introduction
1.2. Conventions

R400
July 2010

File->New

Shows menu selection as menu name

followed by menu selection

Click File->New to start

new drawing.

>D:\setup.exe<

Data to be keyed in at prompt or in an

entry field.

Key in this path location

>D:\setup.exe<.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

1. Introduction
1.2. Conventions

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

2. What is Fieldbus?
2.1

Fieldbus Organization

About the Fieldbus Foundation

The Fieldbus Foundation is a not-for-profit corporation made up of over 160 leading
suppliers and customers of process control and manufacturing automation products.
Since its inception in 1994, it is totally dedicated to developing one standard, "open,"
interoperable field communication model known as FOUNDATION Fieldbus. Honeywell
is a founding and supporting member of the foundation.
Want more information?
If you have Internet access, please visit the Fieldbus Foundation web site at
http://www.fieldbus.org/ for more information. Alternatively, their mail address is:
9005 Mountain Ridge Drive
Bowie Building - Suite 190
Austin, Texas 78759-5316 USA

2.2

Fieldbus Technology

Reference
REFERENCE - INTERNAL
Please refer to Appendix A, if you are interested in more information about
this topic.

2.3

Fieldbus Terms

Description
The following table lists some fieldbus terms and abbreviations for general reference.
Term

Abbreviation

Capability File

R400
July 2010

Description
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).

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

2. What is Fieldbus?
2.3. Fieldbus Terms

Term

Abbreviation
CFF

Common File
Format
Connection
Manager

The format of a Capability file is a readable text

document based on a Windows Initialization (INI) file
type.
A Fieldbus Foundation service to manage connection
information about device types, devices, and blocks
that are actively communicating with a host
application.

Device Description

Description

A binary file 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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

2. What is Fieldbus?
2.3. Fieldbus Terms

Term

Abbreviation

Device Description
Item

DD Item

Description
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
Language

DDL

The language that vendors use to define their device's

Function blocks and 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

2. What is Fieldbus?
2.3. Fieldbus Terms

Term

Abbreviation

DD Synthesizer

Description
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
Description

EDD

A newer version of the binary file (*.ff5) 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.

Enhanced Device
Description
Language

EDDL

The language that vendors use to define their device's

Function blocks and parameters.

Fieldbus Foundation
Object

FFO or FF5

The suffix name for the complete/full DD binary file.

Fieldbus Foundation
Tokenizer

A Fieldbus Foundation tool that converts an ASCII text

file written in conformance with the Device Description
Language specification into a DD binary file.

H1 Fieldbus
Segment

An independent electrical environment consisting of

wire, terminators and a power source per IEC 611581/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.

Object Dictionary

Contains the Object Descriptions for communication

objects such as DataType,
DataTypeStructureDescription, and SimpleVariable.

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

2. What is Fieldbus?
2.3. Fieldbus Terms

Term

Abbreviation

Description

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.

Virtual
Communications
Relationship

VCR

Sets up communications for host to talk to a device. It

acts like a speed dialer to provide for the transfer of
data between applications. FOUNDATION Fieldbus
describes these three types of VCRs:
Publish/Subscribe
Client/Server
Source/Sink

Virtual Field Device

R400
July 2010

VFD

The management or FBAP section of a device that is

addressable by a VFD tag.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

2. What is Fieldbus?
2.3. Fieldbus Terms

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.1

Overview

Background
The following table summarizes the major areas of enhancement that were key to
bringing Fieldbus into the Experion system.
Area

Accomplishment

Connection of Foundation Fieldbus

devices to the Experion system.

Integrate fieldbus devices on an H1 link

with the Supervisory level ControlNet
and/or the I/O ControlNet network.

Configuration of Foundation Fieldbus

devices through the Experion system.

Integrate configuration of fieldbus

devices through the Control Builder
application.

Integration of Foundation Fieldbus

Devices process, maintenance, and
alarm data with notification and display
functions in the Experion system.

Integrate data from fieldbus devices into

Detail, Group, Trend, Maintenance, and
Alarm displays through the Station
application as well as the Monitoring tab
of the Control Builder application.

CIOM-A FIM versus Series C FIM

The Series C Fieldbus Interface Module (FIM4) is designed to complement the C300
Controller and Fault Tolerant Ethernet (FTE) communications within Experion R300
systems or later. While the Series C FIM is functionally equivalent to the Chassis I/OSeries A (CIOM-A) FIM, its physical design, including mounting and wiring
requirements, is drastically different. Please refer to the Series C FIM User's Guide for
information that is specific to integrating fieldbus through a Series C FIM.
ATTENTION
The topology and hardware related details in this document are based on
using a CIOM-A FIM to provide fieldbus integration. The functional details
related to control integration and standard fieldbus functions are applicable to
both CIOM-A and Series C FIMs.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.1. Overview

Non-Redundant Fieldbus integrated architecture for CIOM-A FIM

The following figure shows a typical non-redundant fieldbus architecture using a CIOMA Fieldbus Interface Module (FIM) in a non-redundant C200 Controller and a remote I/O
chassis configuration. The FIM serves as the communication gateway between the
Supervisory ControlNet and/or I/O ControlNet network and the Foundation Fieldbus H1
communications medium. It includes a Remote Termination Panel (RTP) for connecting
and powering up to two fieldbus H1 links.
Ethernet (TCP/IP)

Redundant
Servers

Station

Supervisory ControlNet/Ethernet

Redundant
Controllers

FIM

Non-Redundant
Controller
I/O ControlNet

I/O ControlNet

FIM
24Vdc
(Optional)

Remote
I/O Chassis

Remote
Termination
Panel

Remote
I/O Chassis

H1 Link 2

24Vdc
Conditioned

24Vdc
(Optional)

Remote
Termination
Panel

PT
PT

H1 Link 1
24Vdc
Conditioned

H1 Link 1

PT
H1 Link 2

FOUNDATION Fieldbus Compliant Devices

FOUNDATION Fieldbus
Compliant Devices

Notes:
FIM = Fieldbus Interface Module
Only ControlNet is available as redundant media.

24Vdc
Conditioned

Figure 1 Sample system architecture for non-redundant Fieldbus

integration for CIOM-A FIM.
34

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.1. Overview

Redundant Fieldbus integrated architecture for CIOM-A FIM

The following figure shows a sample redundant fieldbus architecture using a pair of
CIOM-A Fieldbus Interface Modules (FIMs) and Redundancy Modules (RMs) in a
redundant C200 Controller and a redundant remote I/O chassis configuration. The FIM
serves as the communication gateway between the Supervisory ControlNet and/or I/O
ControlNet network and the Foundation Fieldbus H1 communications medium. It
includes a redundant Remote Termination Panel (RTP) for connecting and powering up
to two fieldbus H1 links. The illustration in the following figure is for example purposes
only to show the possible architectural variations for a redundant fieldbus application.
ATTENTION
No chassis I/O modules are permitted in a remote I/O chassis pair configured
for redundant fieldbus support. Only redundancy compliant modules can be
used in a Redundant Chassis Pair configuration. The same is true for the
redundant Controller chassis.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.1. Overview

Ethernet (TCP/IP)

Redundant
Servers

Station

Supervisory ControlNet
RM

FIM

CPM

Non-Redundant
Controller

Redundant
Controllers

I/O ControlNet
RM

FIM

Redundant
Remote
I/O Chassis

Remote
I/O Chassis
24Vdc
(Optional)

24Vdc
(Optional)
Redundant
Remote
Termination
Panel

H1 Link 2

24Vdc
Conditioned

Redundant
Remote
Termination
Panel

PT
H1 Link 1

H1 Link 2

PT
H1 Link 1
24Vdc
Conditioned

PT
FOUNDATION Fieldbus Compliant Devices

24Vdc
Conditioned

PT
24Vdc
Conditioned

FOUNDATION Fieldbus
Compliant Devices

Notes:
CPM = Control Processor Module
FIM = Fieldbus Interface Module
RM = Redundancy Module
Only ControlNet is available as redundant media.

Figure 3 Project tab in Control Builder has new icons for fieldbus
components.
Parameter Definition Editor serves as key interoperability tool
The Parameter Definition Editor (PDE) lets you edit the parameter attributes for a given
function block associated with a fieldbus device block type residing in the Control
Builder Library tab. The following figure shows a typical Parameter Definition Editor
view.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.1. Overview

Figure 4 Typical Parameter Definition Editor view for selected fieldbus

device block
Parameter Definition Editor supports Fieldbus Methods
The Parameter Definition Editor also retrieves any method code that manufactures
include in their Device Description (DD) files. The PDE includes a dedicated Methods
tab so you can easily see if the selected device block includes methods data. The
following figure shows a typical Methods tab view for a device block that includes
methods data.
TIP
Methods are usually associated with a device's Transducer and/or Resource
blocks.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.1. Overview

Figure 5 Sample Fieldbus Methods view in Parameter Definition Editor.

Station provides centralized operator interface
The Station application includes Detail Displays dedicated to the configured FIM,
associated H1 Links, fieldbus device, and associated fieldbus function blocks. They
provide access to the same parameters that are accessible through the control charts and
configuration forms in the Monitoring tab of Control Builder. This includes manufacturer
specific parameters, where applicable.
The reporting of alarm conditions and retrieval of process data for inclusion in group,
trend, history, and schematic displays is closely integrated with the system's existing
notification management system. The existing access authorization levels apply and will
take precedence over fieldbus restrictions specified in Device Descriptions.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

3.2

Control Integration

FIM handles data integration

The Fieldbus Interface Module 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. 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 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.
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.
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).

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

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).
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 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, FIM retrieves MIB information, SM directory, and NM
directory. Knowledge of these directories allows 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.
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
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 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

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.
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).

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

CM
PV

PID

CPM/CEE

OP
OP

AOC

FIM

Fieldbus
Device

FIM

Analog
Input
Transducer

OUT

AOC = Analog Output Channel

CEE = Control Execution Environment
CM = Control Module
CPM = Control Processor Module
FIM = Fieldbus Interface Module
OP = Output
PID = Proportional, Integral, Derivative
PV = Process Variable

Figure 6 Integration of fieldbus device analog input signal with Control

Builder control strategy
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
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

uncertain is mapped to the appropriate Control Builder parameter of PVSTS,

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

CM
AIC
PV
P1

CPM/CEE

BACKCALIN

PID

DACQ

RCAS_IN

FIM

CAS_IN

FIM

Fieldbus
Device
CAS_IN
RCAS_IN

Analog
Output

BKCAL_OUT
RCAS_OUT
OUT
Transducer

Figure 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.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

CM
AIC
PV
P1

CPM/CEE

BACKCALIN

PID

DACQ

RCAS_IN

FIM

CAS_IN

FIM

Fieldbus
Device

BKCAL_OUT

CAS_IN

Transducer

Analog
Input

RCAS_OUT
OUT

RCAS_IN
OUT

ROUT_IN

PID

ROUT_OUT

CAS_IN

BKCAL_IN
RCAS_IN

Analog
Output

TRK_IN_D

BKCAL_OUT
RCAS_OUT
OUT
Transducer

TRK_VAL
FF_VAL

AIC = Analog Input Channel

BACKCALIN = Back Calculation Input
BKCAL_IN = Back Calculation Input
BKCAL_OUT = Back Calculation Output
CAS_IN = Cascade Input

CEE = Control Execution Environment

CM = Control Module
CPM = Control Processor Module
DACQ = Data Acquistion
FIM = Fieldbus Interface Module

OP = Output
PID = Proportional, Integral, Derivative
PV = Process Variable
RCAS_IN = Remote Cascade Input
RCAS_OUT = Remote Cascade Output
ROUT_OUT = Remote Out Output

Figure 8 Integration of fieldbus device PID control with Control Builder

control strategy
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
48

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

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 (DS65), which includes all FOUNDATION Fieldbus inputs, outputs and some
contained parameters, a resulting NaN value passed outbound through the
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 FIM 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 FIM, the output agent supports both publish/subscribe and client/server
communication methods. The publish/subscribe method allows the FIM to appear as a
fieldbus device on the H1 link. The 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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

means that the fieldbus block's BKCAL_OUT parameter is published by the downstream
block and subscribed to by the FIM.
The client/server method allows the FIM to appear as a computing device on the H1 link.
The 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
FIM.
The client/server method also allows the FIM to function in a Direct Digital Control
(DDC) mode or the Remote Out mode in fieldbus terms. In this case, the 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 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
substatus conditions that have corresponding indications in fieldbus Good (Cascade).
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).

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

CM
DI[1]

Device
Control

CPM/CEE

DO[1]
SO

DOC

FIM

Fieldbus
Device

FIM

Digital
Input
Transducer

OUT

CEE = Control Execution Environment

CM = Control Module
CPM = Control Processor Module
FIM = Fieldbus Interface Module
DOC = Digital Output Channel

Figure 9 Integration of fieldbus device digital input signal with Control

Builder control strategy
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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

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.
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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

CM
DIC
Device
Control

PVFL

CPM/CEE

BACKCALIN

DI[1]
DO[1]

RCAS_IN

FIM

CAS_IN

FIM

Fieldbus
Device
CAS_IN_D
RCAS_IN_D

Digital
Output

BKCAL_OUT_D
RCAS_OUT_D
OUT_D
Transducer

BACKCALIN = Back Calculation Input

BKCAL_OUT_D = Back Calculation Output Discrete
CAS_IN_D = Cascade Input Discrete
CEE = Control Execution Environment
CM = Control Module
CPM = Control Processor Module

DIC = Digital Input Channel

FIM = Fieldbus Interface Module
OP = Output
PVFL = Process Variable Flag
RCAS_IN_D = Remote Cascade Input Discrete
RCAS_OUT_D = Remote Cascade Output Discrete

Figure 10 Integration of fieldbus device digital output signal with Control

Builder control strategy
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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

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
substatus conditions that have corresponding indications in fieldbus Good (Cascade).
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
FIM.
a)

Analog process value into the FIM.

Discrete process value into the FIM.

Analog process output from the FIM.

Discrete process output from the FIM.

Analog process output from the FIM with backcalculation feedback.

Discrete process output from the FIM 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 FIM. The FIM can also monitor (subscribe to) the data
published between the functions blocks of these fieldbus devices.
A word 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
54

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.2. Control Integration

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, substatus 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.

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.2. Control Integration

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
substatus 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 substatus field indication.
Bit

Quality

Substatus, if Quality field is

Limits

BAD

UNCERTAIN

GOOD
(NonCascade)*

GOOD
(Cascade)*

BAD Data
Quality

NonSpecific

Non-Specific

NonSpecific

No Limits

UNCERTAI
N Data
Quality

Configuration Error

Last Usable
Value

Active Block
Alarm

Initialization
Acknowledge (IA)

Low Limit

GOOD
(NonCascade)
Data
Quality

Not
Connected

Substitute

Active
Advisory
Alarm

Initialization
Request
(IR)

High
Limit

GOOD
(Cascade)
Data
Quality

Device
Failure

Initial Value

Active
Critical
Alarm

Not Invited
(NI)

Constant

Sensor
Failure

Sensor
Conversion
Not Accurate

Unacknowledged Block
Alarm

Not
Selected
(NS)

No Communication,
with Last
Usable
Value

Engineering
Unit Range
Violation

Unacknowledged
Advisory
Alarm

Do Not
Select
(DNS)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

Bit

Quality

Substatus, if Quality field is

Limits

BAD

UNCERTAIN

GOOD
(NonCascade)*

GOOD
(Cascade)*

No Communication,
with no
Last
Usable
Value

Sub-Normal

Unacknowleged Critical
Alarm

Local
Override
(LO)

Out-OfService

Fault-State
Active
(FSA)
Initiate
Fault-State
(IFS)

* The Good (non-cascade) substatus is used by output connections for fieldbus blocks
such as Analog Input and Discrete Input. The Good (cascade) substatus is used by output
connections for fieldbus blocks such as PID. Both of these substatuses are converted to
the single system data quality of Good.
Fieldbus status indications
REFERENCE - INTERNAL
Please refer to Fieldbus Status Display Indications in Appendix C for list of
possible display indications associated with a given fieldbus status and
definitions of related substatuses.

3.3

Control Mode Interaction

Fieldbus block modes versus control modes

Every fieldbus function block including Resource and Transducer blocks contain the
MODE_BLK parameter. This structured parameter consists of the Actual, Target,
Permitted, and Normal modes. The eight possible modes are described in the About
modes of operation paragraph in the Standard Function Blocks section of Appendix A.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

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.
Data Type

Control Mode
Structure
MODE

Enumeration

Description
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 FIM will
reject all reads. The FIM captures all writes to MODE and maps valid changes to
MODE.TARGET. If the value NORMAL is written to the MODE.TARGET, the FIM
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 FIM 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 FIM clears the
58

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

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

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.

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
2-Char

R400
July 2010

4-Char

Priority Interpretation
Priority
Order
(8=highest)

Control
Order
(8=highest)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

Dominance
Order
(6=Highest)

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

Mode Abbreviation

Mode

Priority Interpretation

2-Char

4-Char

Priority
Order
(8=highest)

Control
Order
(8=highest)

Dominance
Order
(6=Highest)

Out-of-Service

OOS

Initialization
Manual

IMan

Local Override

Manual

Man

Auto

Cascade

Cas

Remote Cascade

RCas

Remote Output

ROut

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)

Remote Cascade (RCas)

Cascade (Cas)

Automatic (Auto)

Manual (Man)

Local Override (LO)

Initialization Manual (IMan)

7 (MSB)

Out of Service (OOS)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

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
Mode
OOS

R400
July 2010

Rule
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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

Rule

Fieldbus
Mode
IMan

This is a Read Only parameter and cannot be set as the target mode.
Never set the IMan as the target mode.

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.

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

Satisfied in mode a;
actual same as target.

OOS, MAN, AUTO, CAS, RCAS, ROUT

a (t)

In mode a; not satisfied in

higher target mode t.

MAN (A), CAS (RC), IM (A), LO (CAS),

AUTO (M), CAS (M)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.3. Control Mode Interaction

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.

Target Mode

Determine
Host Timeout

Mode

Actual Mode
and Target

Remote Cascade
Remote Out
Actual and Target
Mode Calculation

Shed Option
Cascade
Primary Input
Back Calculation Input
Resource State
Block Specific Inputs

Figure 11 Block mode calculation summary

REFERENCE - INTERNAL
Please refer to Mode Change Conditions in Appendix D for list of conditions,
which will change the mode in order of priority with Good (Non-Cascade)
status on input parameter as the lowest priority.

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

R400
July 2010

Attribute

Description

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.4. Link and Block Schedules

Element and Bit

GRANT_DENY.GRANT:0

Attribute

Description

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.
The GRANT_DENY parameter will not track the mode of an associated SCM.

3.4

Link and Block Schedules

Link Active Scheduler (LAS) and Link Master

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.
64

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.4. Link and Block Schedules

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 FIM 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.4. Link and Block Schedules

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 subschedule and
cannot support blocks that are running two different macrocycles. Each
macrocycle includes one subschedule. Each subschedule 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 subschedules that can exist per LAS
and the number of sequences that can exist in a subschedule. If the number
of subschedules 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
subschedule 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 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 load errors, it cannot function as the backup
LAS without a schedule.

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 FIM 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 interdevice 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.)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.4. Link and Block Schedules

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 FIM.
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).
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.
1.

Preprocessing - Snap of parameter values

Execution - Function block outputs are determined

Postprocessing - 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.4. Link and Block Schedules

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.5. Tags, Addresses, and Live List

Cascade
Remote Cascade

2
Target
Mode

Mode
Calculation

Actual
Mode

Set Point
Calculation

Set Point

Remote Out

Back Calculation

Out
Calculation

Primary Input

Primary Output

Block Specific
Parameters
SP & OUT

Output 4
Parameters In
Backward Path

Remote Cascade Out

Back Calculation Out
Remote Out Out

Figure 12 Algorithm execution phase sequence

3.5

Tags, Addresses, and Live List

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.5. Tags, Addresses, and Live List

First Unused
Node Address
V(FUN)
Node
Addresses:
Hexadecimal 0
Decimal 0

10
16

Standard, Global,
and Flat Node
Addresses

Non-Visitor addresses,
used as default
addresses for devices
requiring address
assignments

Number of
Unused Node
Addresses
V(NUN)

X
X

Usable
Addresses

Y
Y

F8
248

Visitor addresses
used for temporary
(handheld) devices

FB FC
251 252

FF
255

Usable Addresses

Figure 13 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.

A word 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 41 decimal (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 21 decimal (15 hexadecimal) as its assigned address.
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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

The FIM constantly monitors the live list for each fieldbus link connected to it. When the
LAS for the link recognizes a new device at a default address, it adds it to its live list
according to the data link layer procedures. The FIM detects the change in the live list
and makes a connection to the new uncommissioned device. It gathers the following
information from the device to be passed to Control Builder.
Name

Description

Data Type

Access

PdTag

Physical Device Tag

32-byte string

Read/Write

Address

Device Address

Unsigned16

Read Only

DevRev

Device Revision

Unsigned8

Read Only

DdRev

DD Revision

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 FIM must be configured and loaded through Control Builder before you
can view it and its links through the Monitoring tab of Control Builder.

3.6

Notification Scheme

Fieldbus versus Experion Alarm Priorities

The fieldbus alarms will be closely integrated with the existing Experion notification
system. The Experion Server will handle FIM alarms in the same way it handles Control
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

Processor ones. But, the fieldbus devices themselves own their alarm data and generate
the alarms, clears, and events.
Fieldbus devices use 0 to 15 as numeric priorities for alarm reporting. 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

(Can never be seen by

(High)

2 (User selected)

Journal

Low

High

All other bitstring

indications:
(BLOCK_ERR bits 0-13,
XD_ERROR bits 16-25)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

Fieldbus Alarm Priority

Experion Alarm Priority

Experion Alarm Severity

High

Urgent

Advanced Alarming
Prior to R400, diagnostic alarms were not supported.
With R400, FF devices are configured with a feature of configuring alarm conditions on
diagnostic parameters. The alarms that are generated are based on the status of these
parameters in a device. Individual bits in these strings are selected and configured as a
condition to generate the alarms. Therefore, the conditions that are used for generating
manufacturer-specific alarms are contained in bit string parameters of FF Transducer
blocks and Resource blocks. FIM monitors all the parameters in the condition to generate
corresponding alarms, which are activated with conditions and attached to the H1
connection.
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.
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
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

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

Low Limit Alarm

PVLO

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

Enumeration

Description

BLOCK

BLOCK_ERR: 14 (Power Up)

FFPWRUP
(Powered-Up)

BLOCK

BLOCK_ERR: 15 (Out-Of-Service)

FBSTCHNG
(Static Revision)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.6. Notification Scheme

Enumeration

Description

Alarm/Event Type

WRITE

Write Protect Change Alarm

RBWPCHNG
(Write Lock)

UPDATE

Link Object Update Event

FBLOCHNG
(Link Object
Changed)

UPDATE

Trend Object Update Event

No Action

Loading alarm conditions

After configuring the alarm conditions, you must load the saved conditions to the FIM.
Conditions are loaded only after loading only during loading the device. For more
information on loading the conditions, see Loading a CIOM-A FIM and its Links.
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 devices 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.

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
Source
R400
July 2010

Value
Device tag

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

3.7

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)

CIOM-A FIM Redundancy Functionality

About CIOM-A FIM redundancy

If you have redundancy compliant hardware, you can implement redundant Series A FIM
operation through a Redundant Chassis Pair (RCP). A RCP consists of two chassis that
include identical redundancy compliant modules in matching slot positions within their
given chassis. The following figure shows a typical hardware configuration for a RCP
that includes a C200 Control Processor Module (CPM). The RCP does not need CPMs to
support FIM redundancy. It does need one pair of Redundancy Modules (RMs) though.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

Figure 14 Typical RCP setup in 10-slot chassis.

CIOM-A FIM versus C200 CPM redundancy
Both the CIOM-A FIM and the C200 CPM or Controller redundancy use Redundancy
Modules in a Redundant Chassis Pair (RCP) configuration to provide redundant
functionality. The RCP does this by providing a pair of chassis, so a component failure in
one chassis switches the handling of the assigned functions to the other chassis. This is
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

considered a dual redundant system, which is characterized by the following two main
redundancy states.
Primary - Refers to the chassis executing the assigned control functions.
Secondary - Refers to the chassis in some state of readiness to assume the
responsibilities of the Primary.
REFERENCE - INTERNAL
Please refer to the Controller Redundancy Functionality section in the Control
Builder Components Theory for more information about C200 Controller
redundancy.

Switchover and Secondary readiness

A switchover describes the process where a Secondary chassis assumes the Primary state,
and the Primary chassis 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 chassis 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 Chassis State is . . .

Then, the Secondary Chassis . . .

Disqualified

Cannot assume the Primary state. This is a

state of non-readiness.

Synchronizing

Cannot assume the Primary State. In this state,

the Secondary chassis 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 Disqualified state.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

Switchover behavior considerations

The following table lists some display and control data behaviors in response to a CIOMA FIM switchover action.
For This CIOM-A FIM Related
Function . . .

R400
July 2010

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
Integration

Control data is available immediately after

switchover. This includes data for connections
in the fieldbus to C200 and in the C200 to
fieldbus directions. The FIM may substitute a
last known good value for publication to
fieldbus devices, while network connections
reform to C200 controller. Substitute value
functionality is bounded to a maximum of five
seconds to account for worse case timing.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

For This CIOM-A FIM Related

Function . . .
Display Data

The Related Switchover Behavior Is . . .

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.

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 chassis/FIM loses synchronization.
In addition to the failure conditions, these events are reported as diagnostic
notifications:
Loss of view of redundant partner on H1 network (applies to FIM link).

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

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 chassis fails.

One or both H1 cables fail.

Integrated Control Protocol (ICP)

backplane in primary chassis fails

One or both H1 network conditioners fail.

Any module in Primary chassis fails.

The 24-Volt power supply fails.

Both ControlNet drop cables to Primary

ControlNet module are lost.
Primary FIM fails.
Primary FIM's connection to Redundant
Remote Terminal Panel fails.
Primary RM fails.

Fieldbus network switchover considerations

The CIOM-A Fieldbus Interface Module (FIM) 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 FIM operation
accounts for the following key considerations associated with initiating a H1 network
switchover.
For this Switchover Consideration . . .
Bumpless Switchover

FIM Redundancy Operation . . .

Assures that fieldbus devices do not:
Initiate a fault state,
Remote shed, or
Mode shed, during switchover.
The new Primary 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

For this Switchover Consideration . . .

Online Address Swap

FIM Redundancy Operation . . .

Swaps network addresses between
Primary and Secondary FIM links. The
link addresses are 16 for the Primary FIM
and 17 for the Secondary FIM. During
switchover or swap, the Secondary FIM
becomes the Primary FIM and assumes
address 16, while the Primary FIM
becomes the Secondary FIM and
assumes address 17 or is Disqualified.
The Primary FIM continues Link Master
operations.

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 CIOM-A FIM chassis switchover. This does not apply to
control data.

If Network Activity Is . . .
Link Maintenance

Then, Behavior During Switchover Is . . .

Since Secondary FIM link is a backup Link Active
Scheduler (LAS), it resumes network management
activities as soon as it detects that the old Primary
FIM is no longer there.
Both Primary and Secondary 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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.7. CIOM-A FIM Redundancy Functionality

If Network Activity Is . . .

Then, Behavior During Switchover Is . . .

Link Active Scheduler (LAS)

The Primary LAS runs the link schedule by telling

devices to publish their data at specific times. The
Secondary 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 FIM
publications.

Alert Queued, User Triggered,

Unidirectional Multicast (QUU)
VCR

Both Primary and Secondary FIM links subscribe to

alerts from devices and receive them in parallel.
Only the Primary FIM link reports received alerts
through the CDA server to the operator interface.
After switchover, the new Primary FIM starts and
the old Primary FIM stops submitting alerts to the
CDA server. The new primary 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, Unidirectional
broadcast (BNU) VCR

Both Primary and Secondary links subscribe to the

same data published by 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, Unidirectional
broadcast (BNU) VCR

Only acting Primary FIM link can publish data to

fieldbus 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 peer-to-peer
(QUB) VCR

All client-server connections are broken and reestablished. This way new Primary builds fresh
connection context.
QUB connections are point-to-point and therefore
can only be opened from the primary.
FIM maintains one Management Information Base

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

If Network Activity Is . . .

Then, Behavior During Switchover Is . . .

(MIB) connection to a device, one Function Block
Application Process (FBAP) connection and
possibly one control connection.

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
Chassis ID of primary and secondary events
Not synchronized alarm
Each of these events appears for every module in a chassis where switchover occurred.

3.8

Block Instantiation Support

About instantiable blocks

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).
REFERENCE - INTERNAL
Please refer to Appendix A for more information about Fieldbus Technology
in general and the Standard Function Blocks.

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.
86

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

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.

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.

Instantiable block implementation considerations

The following table summarizes 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 the remainder of this
document that are tailored to fieldbus devices with only fixed function blocks including
resource and transducer blocks.
Then,

If you want
to . . .

R400
July 2010

Notes and References

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

Notes and References

Open corresponding device

hierarchy in Library tab.

Drag the instantiable block onto

the given device icon in the
Project.

Default name of instantiated

block may be appended with
a letter. For example, a block
with default name I_AI
becomes I_AIA.

Key in desired name for the block

or accept the default in the open
Name New Function Block(s)
dialog.

Click Finish to close the dialog

and add the block to the device
hierarchy in Project as shown in
the following illustration.

If you want
to . . .
Add an
instantiable
block to
device in
Project tab.

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.
See Adding a fieldbus device
to Project for reference.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .
Check
instantiated
block
configurati
on in
Project tab.

R400
July 2010

Notes and References

Right-click device block and

select Configure Module
Parameters from shortcut menu.

The Instantiation tab only

appears if the device
supports Block Instantiation.

Click Block Instantiation tab.

Check Block Template Type

column for list of instantiated
blocks in device.

See Checking device

configuration for reference

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .

Notes and References

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .
Optionally,
check
instantiated
block
resource
usage.

Right-click device block and

select Configure Module
Parameters from shortcut menu.

Click Block Instantiation tab.

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.

R400
July 2010

In Resource Statistics grid, check

Limit and Used columns to view
resource allocations against
assigned limits.

Notes and References

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .

Notes and References

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .

Notes and References

Add
instantiated
block to
CM.

See Adding blocks to CM for sample

loop for reference.

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 here.

Instantiate
an
instantiable
block in a
physical
device.

Load the configured device from

Project containing the desired number
of function blocks as outlined in the
next row.

Block instantiation in a
physical device only
occurs during a load.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .
Load
Project
device to
physical
device.

m) See Load order guidelines for

reference.

Notes and References

The existing load order,
FIM/Link load, and device
match functions also apply
for devices with instantiable
blocks.

See Loading a FIM and its Links

for reference.

See Matching uncommissioned

device to project device or vice
versa for reference.

Right-click device icon and select

Load from short cut menu.

Review information on Load

dialog for load details and any
warning messages identifying preload considerations.

See About Load Dialog box

for general information.

Click OK button to initiate the load

and monitor Load Progress dialog
for load related activities.

See Loading Link contents

or fieldbus device for general
device load procedure.

Upon successful device load,

open device icon in Monitor tab to
view block hierarchy. Only
transducer and resource blocks
appear in the device hierarchy
after an initial load.

Right-click device icon and select

Upload from the shortcut menu.
Click Continue to load device data
into the Monitor database.

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.

Device load from Project

synchronizes the contents of
the project device with the
physical device and
instantiates applicable
instantiable blocks in the
physical device.

After loading a device from

Project or Monitor tab, the
physical device function
block contents matches that
of the corresponding Project
or Monitor device. This
means necessary blocks will
be instantiated and
unnecessary Blocks will be
removed or de-instantiated.

A physical device may go offline while its instantiable blocks are

being instantiated through a device load.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .

Notes and References

ATTENTION
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.
Deinstantiate
(delete) an
instantiated
block from
Project tab.

Open device icon hierarchy in

Project tab.

Right-click applicable instantiated

block icon in hierarchy and select
delete from the shortcut menu.

w) Click Continue button to initiate

action and track progress in
Delete dialog.

Deinstantiate
(delete) an
instantiated
block from
physical
device

Upon successful deletion the

instantiated block icon is removed
form the device hierarchy.

You cannot delete an instantiated

block directly from a physical
device.

You must first delete the CM from

Monitor, unassign or delete the
instantiated block from CM in
Project tab, and then delete the
block as noted in the row above.

aa) Load device from Project to resynchronize contents with

physical device.

You cannot delete an

instantiated block that is
contained in a Control
Module unless you unassign or delete the block
from the CM first.
Also, you cannot delete an
Instantiable block from
Project, if it is loaded and
viewable in the Monitor tab.

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.
Deleting a block from
Monitor tab, does not deinstantiate a block in a
device. Only a load of a
device will achieve this.

bb) Load reconfigured CM.

cc) Right-click device icon and select
Upload from the shortcut menu.
Click Continue to load device data
into the Monitor database.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

If you want
to . . .

Then,

Notes and References

Replace
failed
device with
like device

dd) See Replacing a failed device

with a like device having the same
model name and device revision
for general replacement
procedure.

A device replacement can

cause changes in a device's
block layout, since the
Object Dictionary (OD) index
for an instantiated block can
change.

ee) 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.
ff)

You must put a Sequential

Control Module in the proper
state (Idle) before you can
inactivate it.

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Then,

If you want
to . . .

R400
July 2010

Notes and References

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

3. Fieldbus Integration With Experion System

3.8. Block Instantiation Support

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.1

Planning Considerations

Experion system references

Please refer to the following Knowledge Builder publications for general planning details
and installation considerations for the Experion system in general. For the sake of
brevity, this Guide does not repeat the applicable general guidelines, considerations,
cautions, etc. that are covered in these other Guides.
Planning Guide
ControlNet Installation Guide
Control Hardware Installation Guide
If this is a new Experion system installation, we recommend that you familiarize yourself
with the contents of these publications before you install any Experion system
equipment.
Installation declaration
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 supplied as "open equipment" that is intended to be
mounted on a sub-panel within an enclosure. The suitability of the enclosure
and installed system shall be acceptable to the local "authority having
jurisdiction," as defined in the NEC, or "authorized person" as defined in the
CEC.

CIOM-A FIM and I/O module allowance

Be sure your Experion System fieldbus and I/O requirements do not exceed the
capacities listed in the Software Change Notice (SCN) supplied with the system. The
following table is provided as a quick unofficial reference only for general planning
purposes. In terms of processing allocations, the CIOM-A FIM is the equivalent of three
I/O modules. A pair of redundant CIOM-A FIMs in a Redundant Chassis Pair still count
as two individual FIMs for system capacity calculations, so 50 pairs or 100 FIMs is still
the total allowed per Server.
Component

R400
July 2010

Total Per
Controller

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

Total Per
Server
99

4. Installation
4.1. Planning Considerations

Component

Total Per
Controller

Total Per
Server

Maximum number of CIOM-A FIMs plus I/O

modules divided by three (including local and
remote chassis I/O and rail I/O).

100

Maximum number of H1 links (independent LAS)

200

Maximum number of fieldbus devices*

672

3,000

*Each H1 link is capable of supporting up to 16 devices. This number may vary

depending on the dynamics of the link.
CIOM-A FIM only chassis configuration considerations
If your architecture includes chassis that will only contain CIOM-A FIMs, be aware that
the physical construction of the different chassis sizes may result in blank or unused
single slots. The following table lists the maximum number of CIOM-A FIMs that can be
installed in a given size chassis with the resultant number of blank slots, assuming that a
ControlNet module is mounted in the chassis' first slot (0). Reduce the maximum number
by one for redundant CIOM-A FIM applications, since a Redundancy Module must be
mounted in the chassis as well.
If Chassis size is . . .

Then, Maximum
Number of CIOM-A FIMs
is . . .

And, Number of Blank

Single Slots is . . .

4-Slot*

7-Slot

10-Slot

13-Slot

*A 4-slot chassis is not suitable for use in redundant CIOM-A FIM applications.
Note that the number of FIMs that can be installed in a chassis depends on the available
slots and power. Also, you must consider the CNIs and RMs. For example, a remote I/O
chassis will support a CNI, RM and up to 6 FIMs (power limit) and a C200 Controller
chassis will support a CNI, C200, RM and up to 4 FIMs.

100

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.1. Planning Considerations

Fieldbus component references

The following table identifies the hardware and software components available for
integrating fieldbus devices with an Experion system using CIOM-A FIMs.
Component

Honeywell Model
Number

Fieldbus Interface
Module (CIOM-A
FIM)

Double-wide module mounts in

Supervisory or Remote I/O chassis.
Serves as a "gateway" between the
Experion system and H1 fieldbus links.

TC-FFIF01

Remote
Termination Panel
(RTP), Unpowered

Provides physical connection to the H1

Link and the FIM. Can be mounted on a
DIN rail

TC-FFRU01

GI/IS, Remote
Termination Panel
(RTP), Powered

Same as above but designed for use in

hazardous areas.

TC-FFRP02

Redundant
Remote
Termination Panel
(RRTP),
Unpowered

Provides physical connection to the H1

Link and the FIMs in a Redundant Chassis
Pair. Can be mounted on a DIN rail

TC-FFSU01

Redundant GI/IS,
Remote
Termination Panel
(RTP), Powered

Same as above but designed for use in

hazardous areas.

TC-FFSP02

RTP cable

Connects RTP to FIM and is available in

these lengths:

Fieldbus Device
Usage Licenses

R400
July 2010

Description

3 ft (1 m)

TC-FFC010

8 ft (2.5 m)

TC-FFC025

16 ft (5 m)

TC-FFC050

33 ft (10 m)

TC-FFC100

Software support for these maximum

number of FIMs:
5

TC-FFLI01

TC-FFLI02

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

101

4. Installation
4.1. Planning Considerations

Component

Fieldbus Device
Usage Licenses
Expansions

Description

Honeywell Model
Number

TC-FFLI03

TC-FFLI04

TC-FFLI05

TC-FFLI06

TC-FFLI07

100

TC-FFLI08

Upgrade current usage license as follows:

from 5 to 10

TC-FFLU02

from 10 to 20

TC-FFLU03

from 20 to 35

TC-FFLU04

from 35 to 50

TC-FFLU05

from 50 to 65

TC-FFLU06

from 65 to 80

TC-FFLU07

from 80 to 100

TC-FFLU08

Fieldbus network 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 FIM and its
companion Remote Termination Panel (RTP).

102

Publication Number/Title

Scope

Source

AG-140 / Wiring and

Installation 31.25 kbit/s,
Voltage Mode, Wire
Medium Application Guide

Overview of what you

need to know to wire,
power, and layout network
components

Fieldbus Foundation
9005 Mountain Ridge
Drive
Bowie Building - Suite 190
Austin, Texas 78759-5316
USA

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.1. Planning Considerations

Publication Number/Title

Scope

Source

http://www.fieldbus.org/
AG-163 / 31.25 kbit/s
Intrinsically Safe Systems
Application Guide

Complements the
previous document,
introduces you to the
principles of intrinsic
safety, and outlines how
to apply approved devices
in a hazardous area.

Fieldbus Foundation
9005 Mountain Ridge
Drive
Bowie Building - Suite 190
Austin, Texas 78759-5316
USA

http://www.fieldbus.org/
AG-180 / Engineering
Guide and Intrinsically
Safe Systems Combo

A general comprehensive
reference.

Fieldbus Foundation
9005 Mountain Ridge
Drive
Bowie Building - Suite 190
Austin, Texas 78759-5316
USA

http://www.fieldbus.org/
Fieldbus wiring selection and calculation
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
impact the overall performance of a fieldbus network.
Honeywell offers a tool called the Fieldbus Wiring Calculator to assist users in
calculating the performance characteristics of a planned fieldbus segment. You only have
to visit our website http://www.acs.honeywell.com/ to download a free copy of the
Fieldbus Wiring Calculator tool.
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 Design and Installation Guide for
downloading.
REFERENCE - INTERNAL
Please refer to Fieldbus Wiring Considerations in Appendix E for a
condensed overview of fieldbus wiring considerations provided for convenient
reference. This information does overlap some information that is found in
other data references as well.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

103

4. Installation
4.2. Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Intrinsically safe applications

The fieldbus Remote Termination Panel (RTP) model TC-FFRP02 is approved as
Intrinsically Safe (IS) for use in Division 1 (Zones 0 and 1) hazardous areas. It accepts
nominal 24 Vdc input from an external power supply to provide bus power for fieldbus
devices in IS applications. This RTP provides Galvanic Isolation between the field wiring
and the RTP.
Be sure you take the reduced current limit of 80 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.

4.2 Installing CIOM-A Fieldbus Interface Module TCFFIF01

Front View

4-Character
Display

1-01

Link 1 LED
Link 2 LED
OK LED

RTP Cable
Connector

104

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.2. Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Figure 15 Double-Wide CIOM-A Fieldbus Interface Module TC-FFIF01

Inserting module in chassis
Use the following procedure to insert the CIOM-A FIM into the chassis. This procedure
assumes that this is the initial installation of a CIOM-A FIM in an unpowered chassis.
ESD HAZARD
Electrostatic discharge can damage integrated circuits or semiconductors if
you touch backplane connector pins. Follow these guidelines when you
handle a module:
Touch a grounded object to discharge static potential,
Wear an approved wrist-strap grounding device,
Do not touch the backplane connector or connector pins,
Do not touch circuit components inside the module,
If available, use a static safe workstation,
When not in use, keep the module in its static shield box or bag.

Step

Action

Position the module at the desired chassis slots location. For example, slots 1
and 2.
(Remember that slot numbering is zero-based and the left most slot is
number "0".)

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

105

4. Installation
4.2. Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Step
2

Action
Align the module's circuit board with the top and bottom chassis guides.

Top chassis guide

alignment

Printed circuit
board

Bottom chassis
guide alignment

106

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.2. Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Step

Action

Slide the module into the chassis until the module tabs "click" into position.

For redundant CIOM-A FIM applications, repeat Steps 1 to 3 to install

companion FIM in matching slots in the second chassis of the Redundant
Chassis Pair.

Go to the next procedure Connecting RTP cable to module.

Connecting RTP cable to module

Use the following procedure to connect the RTP cable to the CIOM-A FIM. This
procedure assumes that the CIOM-A FIM is installed in an unpowered chassis.
Step
1

R400
July 2010

Action
Be sure the cable is long enough to reach the DIN rail mounted RTP.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

107

4. Installation
4.2. Installing CIOM-A Fieldbus Interface Module TC-FFIF01

Step

Action
If Cable Number is:

Then, Cable Length is:

TC-FFC010

1 m (3 ft)

TC-FFC025

2.5 m (8 ft)

TC-FFC050

5 m (16 ft)

TC-FFC100

10 m (33 ft)

Align the right-hand cable plug on the RTP cable with the RTP connector
available through a cutout in the CIOM-A FIM door, and fully seat the RTP
cable plug into the connector.

Route the cable to the RTP.

Repeat Steps 1 to 3 for each CIOM-A FIM, as required.

Go to the next procedure Loading FIM firmware, if required.

Loading FIM firmware

ATTENTION
If the FIM is not installed and pre-configured by the factory, users must load
the FIM's firmware to make it fully operational. This is also true for any
replacement FIM ordered separately from the factory.

Once the Control hardware is installed and system communications are established, refer
to Loading FIM firmware in Appendix G for a procedure to update the FIM's firmware.
The procedure for loading the FIM's firmware is similar to the one used for loading the
CPM's personality image.
TIP
The boot and personality image files are fimboot.nvs and fimrex.nvs,
respectively, and they are at this directory location: c:\Program
Files\Honeywell\Experion PKS\Engineering Tools\system\firmware\FIM

108

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

4.3 Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or

RRTP TC-FFSU01/TC-FFSP02
Front view

RTP CABLE

FB+

FB-

SHIELD
7

SEGMENT #1

FB+
FB-

FB+

FB-

FB+
FBJ9

J10

SEGMENT #2

SHIELD

Figure 16 RTP model TC-FFRU01 is unpowered and can be used in

Division 2 hazardous locations; model TC-FFRP02 is powered and can be
used to power fieldbus devices in Intrinsically Safe applications.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

109

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

RTP CABLE

FB+
14

SHLD
FB-

SEGMENT
#1

SHLD
FB+
FBJ6

RTP CABLE

1
14

FB+
SHLD

FBSEGMENT
#2

SHLD
FB+
FBJ8

+ - + -

+ -

J9 J10 J11 J12

Figure 17 Redundant RTP model TC-FFSU01 is unpowered and can be

used in Division 2 hazardous locations; model TC-FFSP02 is powered and
can be used to power fieldbus devices in Intrinsically Safe applications.
Mounting on a DIN rail
ATTENTION
You are responsible for obtaining and mounting the 35 x 7.5 mm metal,
top hat rails (DIN EN50022) to be used for mounting the Remote
Termination Panel (RTP).
We recommend that you mount the RTP in an enclosure.

Use the following procedure to mount the RTP on the user supplied DIN rail.
Step

110

Action

Orient the RTP so the top of the unit is over the top of the DIN rail.

Slightly rotate the RTP to slip its top mounting flange on the top of the DIN
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Step

Action
rail.

Press the RTP down flush with the DIN rail so it snaps into place, securing
the RTP to the rail.

Go to the next procedure Wiring.

Mounting Dimensions
Reference:

Inches
Millimeters

Hole Size:
0.156
3.96
0.425
10.8

5.6
142.2
RTP CABLE

4.75
120.7
14

4.10
104.2

FB-

SEGMENT #2

FB+

FB-

SHIELD

FB+

FB-

SEGMENT #1
FB+

FB-

SHIELD

FB+

J10

6
152.4

0.225
5.7

Models TC-FFRU01 and TC-FFRP02

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

111

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Hole Size:
0.156
3.96
0.425
10.8
RTP CABLE

RTP CABLE

6.98
177.3
J2

J9 J10 J11 J12

+ -

4.10
104.2

FB+

SEGMENT
#2
FB-

SHLD

FB-

SHLD

FB+

FB-

SEGMENT
#1

SHLD

FB+

+ - + -

+ -

4.75
120.7

7.5
190.5

0.225
5.7

Models TC-FFSU01 and TC-FFSP02

Wiring
WARNING
Use only Fieldbus approved components with the RTP, so the intrinsically
safe values of the bus system are not exceeded.
Do not use the RTP in an intrinsically safe environment after it has been
exposed to non-intrinsically safe signals.

ATTENTION
The power requirement for the TC-FFRP02 is 24 Vdc at 270 mA.

Use the following procedure to make wiring connections to the RTP.

112

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Step

Action

Be sure the enclosure is connected to a protective earth ground using #8

AWG solid copper wire. There should be metal to metal contact between the
grounding bus bar and the enclosure as well as the DIN rails

RTP model TC-FFRU01 or (RRTP model TC-FFSU01): Observing polarity,

connect the positive (+) lead for the fieldbus H1 link 1 cable to terminal J2-1
(J5-1) or J2-2 (J5-2) FB+ and the negative (-) lead to J2-4 (J5-4) or J2-5 (J55) FB-. Connect the cable shield to terminal J2-6 (J5-6) SHIELD or to the bus
bar in the enclosure. See the following wiring schematic for TC-FFRU01 or
TC-FFSU01 for reference.
RTP model TC-FFRP02 or RRTP Model TC-FFSP02: Observing polarity,
connect the positive (+) lead for the fieldbus H1 link 1 cable to terminal 2 FB+
and the negative (-) lead to 1 FB- on the GI/IS power supply at location J3.
Connect the cable shield to the bus bar in the enclosure. See the following
wiring schematic for TC-FFRP02 for reference.

RTP model TC-FFRU01 or RRTP model TC-FFSU01: Observing polarity,

connect the positive (+) lead for the fieldbus H1 link 2 cable to terminal J7-1
or J7-2 FB+ and the negative (-) lead to J7-4 or J7-5 FB-. Connect the cable
shield to terminal J7-6 SHIELD or to the bus bar in the enclosure.
RTP model TC-FFRP02 or (RRTP model TC-FFSP02): Observing polarity,
connect the positive (+) lead for the fieldbus H1 link 2 cable to terminal 2 FB+
and the negative (-) lead to 1 FB- on the GI/IS power supply at location J8
(J4). Connect the cable shield to the bus bar in the enclosure.

Connect the plug on the RTP cable from the CIOM-A FIM to the RTP
Cable connector J1 on the RTP model TC-FFRU01 or TC-FFRP02 for
non-redundant application or RRTP model TC-FFSU01 or TC-FFSP02
for redundant application.
For redundant CIOM-A FIM applications, connect the plug on the RTP
cable from the matching CIOM-A FIM in the Redundant Chassis Pair to
the RTP Cable connector J2 on the RRTP model TC-FFSU01 or TCFFSP02.

RTP model TC-FFRP02: Observing polarity, connect the positive (+) lead for
the 24 Vdc power supply cable to terminal J10-2 V+ and the negative (-) lead
to J10-1 V-.
RRTP model TC-FFSP02: Observing polarity, connect the positive (+) lead
for the 24 Vdc power supply cable for link 1 to terminal J9-1 + and the
negative (-) lead to J9-2 -. Connect positive lead for the 24 Vdc power supply
for link 2 to terminal J10-1 + and the negative (-) lead to J10-2 -.

R400
July 2010

Go to the next section Configuration to include the CIOM-A FIM and fieldbus
devices in the configured control strategy.
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

113

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Field Wiring

14
13
12
11
10
9
8
7

Segment 1

FB+

Field Devices

2.2 uF

IMU
14
13
12
11
10
9
8
7

J7
J8

1
2
3
FB4
5
SHIELD
6
FB+

HHC

FB-

FB+

Field Devices

10 Ohm

J5*

Segment 2
T

JP1

1
2
3
FB4
5
SHIELD
6
FB+

HHC

FIM
TC-FFIF01

Fieldbus RTP TC-FFRU01

JP2
10 Ohm

2.2 uF

J9*

FB-

HHC = Handheld Communicator

IMU = Integrated Medium Attached Unit (MAU)
* The mating connector for J5 and J9 is Honeywell part number 51190691-102
or Wiedmuller part number 150186.

Figure 18 Simplified wiring schematic for RTP model TC-FFRU01,

unpowered. Users must provide conditioned 24 Vdc power for the Links Not shown
114

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Field Wiring

14
13
12
11
10
9
8
7

Segment 1

FB+

Field Devices

2.2 uF

10 Ohm

14
13
12
11
10
9
8
7

IMU

2.2 uF

FIM
TC-FFIF01
JP2

1
2
3
FB4
5
SHIELD
6
FB+

HHC

FB-

FB+

Field Devices

10 Ohm

J5*

Segment 2
T

JP1

1
2
3
FB4
5
SHIELD
6
FB+

HHC

FIM
TC-FFIF01

Fieldbus RRTP TC-FFXXXX

J11

J9*

IMU

FB-

J11

HHC = Handheld Communicator

IMU = Integrated Medium Attached Unit (MAU)
* The mating connector for J5 and J9 is Honeywell part number 51190691-102
or Wiedmuller part number 150186.

Figure 19 Simplified wiring schematic for RRTP model TC-FFXXXX,

unpowered. Users must provide conditioned 24 Vdc power for the Links Not shown

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

115

4. Installation
4.3. Installing Fieldbus RTP TC-FFRU01/TC-FFRP02 or RRTP TC-FFSU01/TC-FFSP02

Field Wiring
Hazardous Area

FIM
TC-FFIF01

Fieldbus RTP TC-FFRP02

GI/IS Power Supply

HHC

+
+

6
5
4
3
2
1

Internal
Terminator

I
MTL4053

Segment 1

14
13
12
11
10
9
8 +
7 -

Terminator
Enable Jumper

10 Ohm

2.2 uF

Field Devices

IMU

GI/IS Power Supply

HHC

+
+

6
5
4
3
2
1

Internal
Terminator

I
MTL4053

Segment 2

14
13
12
11
10
9
8 +
7 -

Terminator
Enable Jumper

10 Ohm

2.2 uF

Field Devices

J10
To Local MRG

VVertical
Bus Bar

V+

24 Vdc
Power Supply

HHC = Handheld Communicator

IMU = Integrated Medium Attached Unit (MAU)

Figure 20 Simplified wiring schematic for RTP model TC-FFRP02, powered.

Users must provide 24 Vdc power supply for the GI/IS power supplies

116

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.1

Before You Start

What do you know about Control Builder?

If your answer to this question is nothing, please read at least the Starting Control
Builder section in the Control Building Guide in Knowledge Builder. This section shows
you how to launch the application.
You can skip this section, if you have used Control Builder before.
Do you know how to configure a Control Processor Module?
If your answer to this question is no, please read the Creating a CPM and CEE section
in the Control Building Guide in Knowledge Builder. This section shows you how to
create a Control Processor Module (CPM) and its associated Control Execution
Environment (CEE).
You can skip this section, if you have configured a CPM/CEE before.
Can you configure a Control Module?
If your answer to this question is no, please read at least the Creating and Saving a
Control Module section in Knowledge Builder. This section shows you how to create a
Control Module (CM) and insert and connect function blocks.
You can skip this section, if you have configured a CM before.
Are you familiar with your system architecture?
To complete the configuration data for certain components, you must know the planned
or current location of the associated hardware components in your Experion system
architecture. This includes the chassis slot location for any given C200 CPM and CIOMA FIM. We suggest that you create a simple diagram that outlines the location of
components in your system showing slot locations and communication addresses for
reference during configuration.
Do you understand and have experience with fieldbus?
How successful you are at implementing a fieldbus system will depend largely on how
well you understand and/or are familiar with this relatively new technology. If you are
new to fieldbus, we suggest that you seek at least some overview level training before
trying to implement a fieldbus system.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

117

5. Configuration
5.2. Non-Experion Interface Precautions

Are you Ready?

Once you have addressed all the questions in this section, you are ready to move on to
the next section Configuring Fieldbus Components. At this point, you should have at
least a working knowledge of the Control Builder application.

5.2

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

118

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.3. Free VCR Recommendation

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.

5.3

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, 64 per segment for
Series A 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

119

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

5.4 Configuring Fieldbus Components In a Control

Strategy
About control strategy configuration
You use the Control Builder application to configure a process Control Strategy using
predefined function blocks. Since Fieldbus Foundation components have been
functionally integrated with the Experion system, the Control Builder includes fieldbus
related Function Blocks for easy integration of fieldbus functions within the overall
Control Strategy.
The Control Builder includes a New->Type command on the File menu. The Type
command lets you create block types for fieldbus devices based on the vendor supplied
Design Description (DD). This means each fieldbus device has an associated block type
for viewing and defining the configurable attributes of its fieldbus function blocks. These
attributes include naming and identifying the component's location within the network as
well as setting device and channel specific parameters, as applicable.
ATTENTION
The following information is only intended as a supplement to the Control
Building Guide and does not repeat the basic functionality details for 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.
Please refer to the previous section Before You Start for general control
building data references.

Example Application and Control Strategy for Procedural Reference

The following figure shows a process feed and recycle line application being controlled
through an Experion control strategy loaded in a Control Process Module (CPM) and
associated Control Execution Environment (CEE). This sample application and control
strategy will be used for reference to illustrate the applicability of functions in the
following procedures

120

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

CPM/
CEE

FIM

Surge Tank
T-106

2000 Gallons
SP = 50%
HI=70% HIHI=85%
LO=25% LOLO=15%

ST3000FF
Smart Pressure
Transmitter

Recycle
Feed
100
gal/min
Nominal

Logix 1400
Valve Positioner

Recycle Pump
Shut Off at LOLO
Restart at 35%

CPM/CEE
CM102
DI
L
LL

FTRIG

DEVCTL

IOM
DI

IOM
DO

Feedback

Command

Interlocks

Figure 21 Sample Application and Control Strategy Integrating Fieldbus

Devices with an Experion System.
The application involves controlling the level of a 2000 gallon surge tank with a steadystate 100 gallon per minute (gal/min) process feed and recycle line. A fieldbus approved
ST3000FF smart pressure transmitter is being used to monitor the level in the surge tank.
A fieldbus approved Logix 1400 valve positioner is being used to regulate the control
valve in the process feed line.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

121

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

The following are some pertinent characteristics about this application and the
corresponding Experion control strategy for reference.
The goal is to recycle the process fluid back to the process with a minimum swing in
the recycle feed rate.
The tank level set point (SP) is 50 percent.
The tank level low (LO) alarm is 25 percent and the low-low (LOLO) alarm is 15
percent.
The tank level high (HI) alarm is 70 percent and the high-high (HIHI) alarm is 85
percent.
The Experion control strategy includes a tank level Control Module (CM) named
CM101 and a pump control CM named CM102.
The CM101 includes an Experion Proportional, Integral, Derivative (PID) function
block configured to operate as a Proportional and Integral (PI) two-mode controller.
The tuning for the PI controller is "loose" to allow some swing in the level of fluid in
the tank.
The CM101 includes an Experion Data Acquisition (DATAACQ) function block to
provide the alarm flags for the LO, LOLO, HI, and HIHI tank level alarms.
The CM101 includes a fieldbus Analog Input (AI) function block to integrate the
tank level indicating signal from the ST3000FF smart pressure transmitter with the
control strategy. It includes a fieldbus Analog Output (AO) function block to
integrate the Logix 1400 Valve Positioner with the PI controller output from the
control strategy.
The CM102 includes an Experion Device Control (DEVCTL) function block to
control the recycle pump through corresponding Discrete Input and Discrete Output
Input/Output Module function blocks. It also includes links to the LO and LOLO
alarm flags for the DATAACQ block in CM101 for device safety override and
output override interlocks, respectively.
The recycle pump is to be restarted at 35 percent.

Configuration considerations only for redundant CIOM-A FIM applications

Observe the following considerations when configuring fieldbus devices with redundant
CIOM-A FIM applications.
122

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

ATTENTION
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 CIOM-A FIMs, we recommend that you
assign the device to address 40 (decimal).
Do not assign addresses below 30 to any backup Link Master devices

If Control Module
FFPERIOD Is . . .

Then, Be Sure
STALECOUNT Value
Is at Least . . .

And, Device Resource Block SHED_RCAS

and SHED_ROUT Values Are at Least . . .

250 milliseconds

5 seconds

500 milliseconds

5 seconds

1 second

5 seconds

2 seconds

5 seconds

4 seconds

5 seconds

Adding CIOM-A FIM block to Project

Use the following procedure to add a CIOM-A Fieldbus Interface Module (FIM) block to
the Project tab in Control Builder. This also adds two Link blocks for the two H1 fieldbus
links that can be associated with this FIM. This procedure assumes the Control Builder
application is running.
TIP
You can configure a CIOM-A FIM block in the Control Builder Project tab
without the CIOM-A FIM hardware being installed. However, it is good idea to
have the communications driver and hardware that is going to be used for the
system installed, configured, and running. The CIOM-A FIM needs the name
of the communications driver specified on its configuration form to complete
its configuration data. Like the C200 CPM, the CIOM-A FIM represents a
hardware module and the block configuration specifies the communication
path to the hardware.

Step

R400
July 2010

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

123

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
1

124

Action
Click File-> New->Interface Modules>FIM - Fieldbus Interface Module.

Result
Calls up the CIOM-A FIM block
parameters configuration form Main tab
with Name field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

TIP
If your system will include multiple FIMs, we suggest that you adopt a more structured
syntax for naming them. For example, use the MAC ID for the Supervisory ControlNet
module and the CIOM-A FIM's slot location in the chassis to form a meaningful suffix.
For the CIOM-A FIM used in this procedure, the suggested name would be FIM0105.
2

Key in >FIM0105< for this example.

Press <Tab>.

Moves cursor to the Network Name field

and highlights it.

Note that Control Builder automatically

assigns a name with a unique suffix. You
can enter a name of your choice
consisting of up to 16 characters. The
only rule is that it must be unique within
the system.
3

Be sure the communications medium

your Experion system is using appears in
the Network Name field. If it doesn't, use
the field's dropdown list to select it.
ControlNet is the default selection. Press
<Tab>.

Moves cursor to the Driver Name field

and highlights it.

TIP
Communications Driver must be installed and running before it will appear as a
selection in the dropdown menu for this field.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

125

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Be sure the correct communications

driver name appears in the Driver Name
field. If it doesn't, select the correct one
from the field's dropdown list. Press
<Tab>.

126

button to select the Supervisory

Click
Mac Address set in the ControlNet
module connected to the Supervisory
network. Use 01 for this example. Press
<Tab>.

button to select the Slot

Click
number where the ControlNet Module
connected to the Supervisory network is
installed. Use 00 for this example. Press
<Tab>.

Result
Moves cursor to Supervisory MAC
Address field.

Moves cursor to Supervisory Slot

Number field.

Moves cursor to the Module Slot Number

field.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
7

Action
button to select slot number
Click
where CIOM-A FIM is installed from
dropdown list. Use slot 05 for this
example. Press <Tab>.

Result
Moves cursor to the Remote Chassis
checkbox .

(Remember that chassis slot numbering

is zero-based from left to right.)

R400
July 2010

If CIOM-A FIM is located in a Remote I/O

Chassis, click this box to select it.
Otherwise, skip this Step, press <Tab>,
and go to the Result column in Step 12.
Skip the step for this example.
button to select address of the
Click
ControlNet Network module in the
Supervisory chassis that is connected to
the ControlNet Network module (Uplink)
in the Remote I/O Chassis. Use 04 for
this example. Press <Tab>.

Enables Remote Chassis selection fields.

Moves cursor to DownLink Slot Number

entry field and highlights it.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

127

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
10

Action
button to select slot number
Click
where downlink ControlNet Module is
installed from dropdown list. Use slot 04
for this example. Press <Tab>.

Result
Moves cursor to UpLink MAC Address
field.

(Remember that chassis slot numbering

is zero-based from left to right.)

128

button to select address of the

Click
ControlNet Network module in the
Remote I/O chassis that is connected to
the ControlNet Network module
(Downlink) in the Supervisory Chassis.
Use 05 for this example. Press <Tab>.

Moves cursor to UpLink Slot Number

field.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
12

Action
button to select slot number
Click
where uplink ControlNet Module is
installed from dropdown list. Use slot 00
for this example. Press <Tab> twice.

Result
Moves cursor to This controller is
redundant field.

(Remember that chassis slot numbering

is zero-based from left to right.)

Click check box to add check mark, if this

CIOM-A FIM is part of a Redundant
Chassis Pair. Leave check box blank, if
CIOM-A FIM is part of a non-redundant
chassis configuration. Press <Tab>.

If box is checked, default name for

seconday CIOM-A FIM appears in
Secondary Name field. Go to Next
Step.

If box is blank, moves cursor to

Item Name field. Go to Step 15.
14

Only valid when CIOM-A FIM is

redundant. Key in desired name for
secondary CIOM-A FIM or accept default
that is assigned name with SEC
appended. Press <Tab>.

See second bullet in row above.

Key in the name of the Entity that this

object will be associated with in the
Enterprise Model Builder hierarchy.
Press <Tab>.

Moves cursor to the FIM Command field.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

129

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
16

Action
Only valid when CIOM-A FIM is
loaded and communicating with the
system. Lets you select Shutdown
action for the CIOM-A FIM.

Result
This completes Main Tab configuration
entries.

You can also select the check box

to Suppress H1 Power Alarm and/or
key in a Device Drop Off Link Alarm
Delay value in seconds.
17

Click the Statistics Tab.

You can only view the data in fields on

this tab in the Monitoring tab of Control
Builder, when the CIOM-A FIM/LINK is
loaded and communicating with the
system. Click the Server History Tab.

130

Calls up the Statistics Tab.

Calls up the Server History Tab.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

ATTENTION
We have intentionally skipped the Version tab, since it is not required to complete the
configuration and it is only valid with the Version Control System license option.
19

Key in desired control level value or

accept the default value. Click the Server
Displays tab.

Calls up the Server Displays tab.

ATTENTION
We have intentionally skipped the History Configuration grid, Server Scripting Editor,
Associated Display, Trend grid and Group grid entries, since they are not required to
complete the configuration. Of course, you can enter this data later using the on-line
help or appropriate Knowledge Builder document for reference. Have also skipped the
Identification, Dependencies, and Template Defining tabs that are only valid with the
Template license option.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

131

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
20

132

Action
Click the OK button.

Result
This completes the configuration entries,
closes the form, and adds the CIOM-A
FIM icon to the Project tab. The CIOM-A
FIM also includes icons for the two H1
fieldbus links that it can support. The first
view that follows is for a non-redundant
CIOM-A FIM application and the second is
for a redundant CIOM-A FIM application.
The second view is in a system with the
Hierarchical Building license option set for
Assignment View. These views are for
example purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

TIP
While Control Builder does assign a name with a unique suffix number for each Link,
we suggest that you adopt a more structured syntax for naming them. For example,
use the Link number (1 or 2, plus the MAC ID and Slot number suffix used for the
associated CIOM-A FIM. For the Links used in this procedure, the suggested names
would be LINK10105 and LINK20105.

134

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >LINK10105< for this example.

Or, key in a unique name of your own
consisting of up to 16 characters. Press
<Tab>.

Moves cursor to the Item Name field.

Key in the name of the Entity that this

object will be associated with in the
Enterprise Model Builder hierarchy.
Press <Tab>.

Moves cursor to the Description field.

ATTENTION
Some parameters on this tab are not available, since they are only active in the
Monitoring tab after the FIM/LINK is loaded and communicating with the system.
4

Key in desired descriptive text of up to 24

characters. This text will appear in
applicable detail and group displays
associated with this block. Press <Tab>.

Moves cursor to Link Optimization field.

Click the arrow button and select desired

option from the list. Press <Tab>.

Moves cursor to Sample Skew field.

Click the arrow button and select whether

Skew is enabled or not. Click the System
Management tab.

Calls up the System Management tab.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

135

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

ATTENTION
We recommend that you do not change the default value settings for the active
parameters on this form unless you are familiar with tuning the performance of fieldbus
links. The grayed out parameters are only accessible in the Monitoring tab with the
FIM/LINK communicating with the system.
Please refer to Link Parameters Reference in Appendix I for a more detailed
description of the user configurable LINK parameters in both the Project and Monitor
modes.

136

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
7

Action
Press <Tab>.

Result
Moves cursor to the Step Timer Preset
(T1) field and highlights it.

TIP
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.

Accept default value for Step Time

Preset (T1) parameter or key in a new
value. This is the preset value for the
System Management step timer. The
default value is 15. 0000s. Press <Tab>.

Moves cursor to the Preset Set Addr Seq

Timer (T2) field and highlights it.

Accept the default value for the Preset

Set Addr Seq Timer (T2) parameter 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. Press <Tab>.

Moves cursor to the Preset Set Addr Wait

Timer (T3) field and highlights it.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

137

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Accept the default value for the Preset

Set Addr Wait Timer (T3) parameter or
key in a new value. This is the preset
value for the SM set address wait timer.
The default value is 45. 0000s. Click the
Network Management (LM) tab.

Calls up the Network Management (LM)

tab.

ATTENTION
The remaining parameters on the System Management tab and the Network
Management (Basic) tab are read only and provided for monitoring purposes only.

138

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

The CIOM-A FIM is the primary

LINKMASTER for the Link. We
recommend that you accept the default
values for the parameters on this tab,
and revisit this tab in the Monitoring tab,
when the FIM/LINK is communicating
with the system. Click the Server History
tab.

Calls up the Server History tab.

ATTENTION
The parameters on the Statistics tab are read only and provided for monitoring
purposes only. The Uncommissioned Devices tab is for use in Monitoring mode with
FIM/LINK communicating with devices. The Version tab is only valid with the Version
Control System license option and is read only in the Project mode.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

139

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
12

Action
Key in desired control level value or
accept the default value. Click Server
Displays tab.

Result
Calls up the Server Displays tab.

140

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Click the OK button.

Result
This completes the configuration entries,
closes the form, and adds the data to the
database.

(Note that the system will generate an

error message detailing any problems with
the data entered and display it at this time,
so you can correct the errors before
closing the form.)
14

Repeat this procedure for Link 2 and use

LINK20105 as the link name.

This completes the procedure. Go to the

next section Making a fieldbus device
Type from vendor DD.

Return to Step 1.

Creating a Fieldbus device type from vendor DD

Use the following procedures to make a fieldbus device block type using the Type
function included with Control Builder and vendor supplied Device Description (DD)
files or Enhanced Device Description (EDD) files. This procedure assumes that Control
Builder is running and you have appropriate access level to create a control strategy.
TIP
You must have the Device Description (DD) files or Enhanced Device
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

141

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

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. You can skip
this procedure, if a block for the given device type already exists in the
Control Builder Library database.
The DD files are normally stored in a directory called Release. This directory
must include these three files:
The *.FFO file is the DD binary, or *.FF5 file is the EDD binary file
The *.SYM file is the device symbol file
The *.CFF file is the device capability file.

ATTENTION
With R400, Experion supports DD files and EDD files and continues to
process the DD to create a device block type in the Control Builder library

Step
1

Action
On the File menu, click New->Type->Fieldbus Device.

2
In the Select Device Type dialog box, Click
DD file location in the Device DD Files box.

to browse for the applicable

Or
In Device List box, click the device you want to add to the Control Builder
Library.

142

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Click OK.
A dialog box appears displaying information about the DD version files which
are equal to or more than version 5.

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
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

143

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action
type.
or
Click OverWrite to overwrite the device type to continue.

Click OK to acknowledge the version of DD files.

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

Click OK to import the DD files. Monitor progress through the Opening

Device Vendor Files, Creating Definition Files, and Importing the Block
Type to ERDB progress dialog boxes that open in succession.
A dialog box appears displaying information about upgrading Knowledge
Builder to the latest version.

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.
6

Click OK to acknowledge upgrading the Knowledge Builder to the latest

TIP
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.
You can find definitions for many of the standard fieldbus function blocks in
Standard Function Block Parameters in Appendix B in this document.
Vendors also supply a text file that includes definitions for each function block
used in their device.
4

Click the close button on upper right-hand corner of the PDE to close it.

If prompted to save changes, click the Yes button to save edits or the No
button to cancel them.

Repeat the procedure for other device blocks, as required.

This completes the procedure.

Adding a fieldbus device to Project

Use either method 1 or method 2 procedure that follows to add a fieldbus device from a
Library tab directory to the Project tab. This procedure assumes that Control Builder is
running and you have made block types for the fieldbus devices that will be used in your
application, using the Type command in Control Builder.
TIP
If a FIM and its associated Links exist in the Project tab, you can drag and
drop a fieldbus device type from a directory in the Library tab directly to a
Link. The following procedure adds a fieldbus device to the Project tab and
then shows how to assign it to a Link through the Assignment dialog box in
the next procedure. Once a device is assigned to a Link, it represents a
matching physical device that is to reside on the given Link.

Method 1: Drag and Drop

Step

146

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

R400
July 2010

Step

Action

Result

sign in front of the

Click
applicable vendor type directory
in the Library tab.

Expands directory tree to show stored

device block types. The following
illustration shows an open Honeywell
directory for example purposes only.

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

147

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >ST101< for this

example or key in a new name
consisting of up to 16
characters. Click Finish.

Device instance with given name is

created in Project tab. The following
illustration is for example purposes only.

ATTENTION
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 for reference.
4

Repeat this procedure to add

other devices or go to the next
procedure Assigning a device to
a Link in Project.

Method 2: File Menu

Step

148

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Click File->New->Devices>FLOWSERVE->Lx1400FF_0502 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.
The FLOWSERVE and LX1400FF
selections are shown for example
purposes only.)

R400
July 2010

Result
Calls up the Block Parameters
configuration form with Name field
highlighted

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

149

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

TIP
We suggest that you wait to check all block configuration parameters until after the
device is assigned to a Link.

150

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >LX102< for this example or key

in a desired name consisting of up to 16
characters. Click OK.

Closes form and creates device instance

with given name in Project tab. The
illustration below is for example purposes
only.

(Note that the symbol simply indicates

that the component has not been loaded
to the controller.)

ATTENTION
Devices created in Project tab automatically include only their fixed, transducer, and
resource function blocks. If the device block type includes instantiable blocks, you
must drag and drop the instantiable block from the device type in library to the device
icon in the Project tab to instantiate (create) it in the device in Project. See
Instantiable block implementation considerations for reference.
3

Repeat this procedure to add other

Honeywell

Downloaded from www.Manualslib.com manuals search engine

153

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
4

Action
Repeat Step 3 for device LX102.

Result
Device is added to the Assigned Devices
list box with the assign state icon.

TIP
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.
5

Click Close.

Repeat the procedure to assign other

devices or go to the next section
Checking device configuration

Closes the dialog box.

Checking device configuration

Use the following procedure to check the configuration of a selected fieldbus device in
the Project tab. This procedure assumes that the device has been assigned to a Link.

154

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

TIP
While the device has been assigned to a link, this is still "offline" configuration
of a matching physical device that is to be connected to this Link.
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.
In 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.
So, 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 this configuration form
matches the device name configured in the device.

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.

Step

R400
July 2010

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

155

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
1

156

Action
Double-click the device icon in the
Project tab.

Result
Calls up the parameter configuration
dialog box with Tag Name (NAME) field
highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Accept the assigned name or key in a

new one of up to 16 characters. Must be
unique within the system. Press <Tab>.

Moves cursor to the Item Name (Item

Name) field.

Key in the name of the Entity that this

object will be associated with in the
Enterprise Model Builder hierarchy.
Press <Tab>.

Moves cursor to the Description (DESC)

field.

R400
July 2010

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

157

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Key in desired description for the link

consisting of up to 59 characters or leave
it blank. Press <Tab>

Result
Moves cursor to the Device Network
Node Address (ADDR) field and
highlights it.

TIP
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 is (NUN) is 206. We recommend that the fieldbus device designated as the
backup Link Master be given 21decimal (15 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.
5
6

Accept the default or key in the device's

current address assignment.
Continue button to the right
Click the
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.)

158

Click the System Management tab.

Calls up the System Management tab

form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

ATTENTION
The Device Identification field is blank until the Project device is matched to an
uncommissioned device. It is shown in the Main tab illustration for example
purposes only.
The Physical Device Tag (PD_TAG) and Device State (DEVSTATE) parameters
on the Main tab are grayed out, since they are only active in the Monitoring tab
after the FIM/LINK/DEVICE is loaded and communicating with the system.
We recommend that you do not change the default value settings for the active
parameters on the System Management form unless you are familiar with tuning
the performance of fieldbus links. In most cases, the parameter values will mirror
those configured for the Link. The grayed out parameters are only accessible in the
Monitoring tab with the FIM/LINK communicating with the system.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

159

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Press <Tab>.

Moves cursor to the Step Timer Preset

(T1) field and highlights it.

Accept default value for Step Time

Preset (T1) parameter or key in a new
value. This is the preset value for the
System Management step timer. The
default value is 15. 0000s. Press <Tab>.

Moves cursor to the Preset Set Addr Seq

Timer (T2) field and highlights it.

Accept the default value for the Preset

Set Addr Seq Timer (T2) parameter 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. Press <Tab>.

Moves cursor to the Preset Set Addr Wait

Timer (T3) field and highlights it.

Accept the default value for the Preset

Set Addr Wait Timer (T3) parameter or
key in a new value. This is the preset
value for the SM set address wait timer.
The default value is 45. 0000s. Click the
Network Management (LM) tab.

Calls up the Network Management (LM)

tab.

ATTENTION
The remaining parameters on the System Management tab and the Network
Management (Basic) tab are read only and provided for monitoring purposes only.

160

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

We recommend that you accept the

default values for the parameters on this
tab, and revisit this tab in the Monitoring
mode, when the FIM/LINK is
communicating with the system. Click the
Server History tab.

Result

Calls up the Server History tab.

ATTENTION
The Version tab is only valid with the Version Control System license option and is
read only in the Project mode.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

161

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

162

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
13

Action
Key in desired control level value or
accept the default value. Click Server
Displays tab.

Result
Calls up the Server Displays tab.

Click the OK button.

This completes the configuration entries,

closes the form, and adds the data to
database.
(Note that the system will generate an
error message detailing any problems with
the data entered and display it at this time,
so you can correct the errors before
closing the form.)

Repeat this procedure for another

Device, as required.

Go to the next section Creating a Control

Module for sample PID loop.

R400
July 2010

Return to Step 1.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

163

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Making fieldbus block template and assigning function block to device

The following procedure outlines the steps for making user template for a function block
in the Fieldbus Library in Project, adding the block to an instantiated Control Module in
Project, and assigning the block to a fieldbus 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. The illustrations in this
procedure are for example purposes only.
Step

Action

Result

In Project mode, click Library tab, click +

sign for FIELDBUS, and click AI block
icon.

Selects fieldbus Analog Input (AI) block

in the FIELDBUS Library.

Click Templates->Make Template.

Calls up AI Block configuration form.

164

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Fill in configuration data in the

appropriate fields on the applicable
configuration form tab. Use the online
help for reference.

Configure the block for operation in your

application.

Click the OK button.

Closes the AI Block configuration form

and adds the configured AI block as a
template under its assigned name in the
USER Library.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

165

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

166

In Project view, select and double-click

an instantiated Control Module
(User_1_1) that is to contain the AI_6
block template.

Opens the Control Module (CM) in the

chart.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

R400
July 2010

Drag and drop the AI_6 block icon from

the USER Library to the open User_1_1
Control Module in the chart.

Adds the AI_6 block to the CM.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

167

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Right-click the AI-6 block.

Continuation from Step 9 or 10

The AI_6 block is assigned to the

selected device as noted on the face of
the block. .

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

171

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

This completes the procedure.

Go to the next section Creating a Control

Module for sample PID loop for more
information on configuring a Control
Strategy.

Creating Control Module for sample PID loop - Optional

The following procedures are optional tutorials on creating a CM to provide the PID
control loop function for the example application shown in the previous Sample
Application figure. They provide a general reference for including fieldbus function
blocks with Experion function blocks in a control strategy. This procedure assumes that
Control Builder is running and that you have added the Control Processor (CPM)/Control
Execution Environment (CEE) block to the Project tab. Also, the following fieldbus
components have been created in the Project tab, using the previous procedures in this
section.
FIM named FIM0105
172

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Associated Links named LINK10105 and LINK20105

Honeywell pressure transmitter named ST101 and assigned to LINK10105
Flowserve valve controller named LX102 and assigned to LINK10105
TIP
The following procedure is really intended for users who have never used
Control Builder before. If you have used Control Builder to build Experion
control strategies, you will find adding fieldbus function blocks is intuitive,
since it is the same as adding Experion function blocks.
Also, the procedures are abbreviated in some cases in the interest of brevity.
Once you get the "feel" of using Control Builder, it is more efficient to interact
directly with the application and use the online help to find an answer to a
question about a function or an entry.

Creating Control Module in Project

Step
1

R400
July 2010

Action
In Library tab, click
System directory.

plus sign for

Result
Opens System directory.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

173

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
2

Action
Double-click the CONTROLMODULE
icon
. Or, if you are using the
Hierarchical Building option, right-click
the icon and select Instantiate in the
menu.

174

Click Edit-> Module Properties.

Result
Opens new Control Module with default
name CMxx in chart window to be added
to Project tab. Where "xx" equals unique
incremental number.

Opens Control Module Block Parameters

form with Name field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >CM101<. Click in Item Name

field.

Moves cursor to the Item Name field.

Key in the name of the Entity that this

object will be associated with in the
Enterprise Model Builder hierarchy.
Press <Tab>.

Moves cursor to the Description field.

Key in >Surge Tank Control Loop<.

Press <Tab>.

Moves cursor to the Eng. Units field.

Key in >Percent<. Press <Tab>.

Moves cursor to Keyword field

Key in >Recycle<. Press <Tab>.

Moves cursor to Enable Alarming Option

check box.

Accept the default alarm enabled

selection - box checked. Press <Tab>.

Moves cursor to Execution Order in CEE

field and highlights it.

ATTENTION
The Execution Order in CEE parameter only applies to contained Experion function
blocks in CM's that are assigned to a CEE. It has no affect on contained fieldbus
blocks and it is disabled, if the CM is assigned to a Link.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

175

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
9

Action
Key in >30<. Press <Tab>.

Result
Moves cursor to the Execution Period
field and highlights it.

(The smaller the number the earlier the

module executes in the cycle.)
10

Accept the default value DEFAULT. (It

equals 1000ms for a 50ms CEE or
200ms for a 5ms CEE.) Press <Tab>.

Moves cursor to the Execution Phase

field and highlights it.

Press <Tab> four times to skip the

Sequential Control Module fields, since
they don't apply for this example.

Moves cursor to the Execution Order in

Link field and highlights it.

ATTENTION
The Execution Order in Link parameter only applies to contained fieldbus blocks. It
combines with the block's Execution Order in CM parameter to determine how the
fieldbus block participates in the Link Schedule.
Likewise, the FF Execution Period parameter only applies to contained fieldbus blocks.
It determines how the fieldbus blocks participate in the Link Schedule.
12

Accept the default value 10. Press

<Tab>.

Moves cursor to the FF Execution Period

field and highlights it.

(The smaller the number the sooner the

device is polled on the link.)

176

Accept the default value 1S. Press

<Tab>.

Moves cursor to the Stale Count field and

highlights it.

Accept the default value 2. Press <Tab>.

Moves cursor to the OK button.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

ATTENTION
For this example, we will just accept the default configuration values for the
parameters on the other tabs. The applicability of other tabs depends on whether you
are using the Hierarchical Building, Template, and/or Version Control system option(s).
Click the Parent Asset field and key in the name of the Parent that includes the entity
that this Control Module will be associated with in the Enterprise Model Builder
hierarchy. If you do not use the Enterprise Model Builder to construct a control
hierarchy for your process and you previously defined Areas of control, the name you
assigned for the control area (SCANAREA) will be used as the name for the Parent
Asset (PARENTASSET).
15

Click the OK button.

In Library tab, click

DATAACQ directory.

to CM101 chart.

plus sign for

Result
Adds FF AI block to CM101 chart.

Opens directory.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

179

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Adds DATAACQ block to CM101 chart.

Drag DATAACQ block
CM101 chart.

180

In Library tab, click the

the REGCTL directory.

plus sign for

Opens directory.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

6
Drag PID block

R400
July 2010

to CM101

Adds PID block to CM101 chart.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

181

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
7

Action
In Project tab, click
device LX102.

Result

plus sign for

Adds FF AO block to CM101 chart.

Drag the AO block
chart.

182

Opens directory.

to CM101

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

This completes the addition of blocks to

the CM for the sample loop. Go to the
next procedure Configuring AI block for
sample loop.

Result

Configuring AI block for sample loop

Step
1

R400
July 2010

Action
In CM101 chart, double-click the AI
block.

Result
Opens the AI Block Parameters form with
Name (Name) field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

183

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >AI_LEVEL<. Press <Tab>.

Moves cursor to the Description field.

Key in >Input for Tank 106 Level<. Press

<Tab>.

Moves cursor to the Execution Order in

CM field and highlights it.

ATTENTION
The Execution Order in CM parameter defines the order of execution and publication
for all blocks contained in the CM. For contained fieldbus blocks, this parameter
combines with the CM's Execution Order in Link parameter to determine how the
fieldbus block participates in the Link Schedule.

TIP
You can use the Pre-execution delay (PREXEGAP) and the Post execution delay
(POSTEXEGAP) parameters to add extra time before and after the execution of the
block. This lets you adjust the schedule to achieve such actions as forcing multiple AI
blocks to execute at the same time (even though they must publish serially).
4

Accept the default value 10. Press <Tab>

three times.

Moves cursor to Tag Description field

and highlights it.

(The smaller the number the sooner the

block executes within the CM cycle.)

184

Key in desired Block Tag Description

consisting of up to 32 characters. Press
<Tab>.

Moves cursor to Mode/Normal selection.

Accept default selection - AUTO. Press

<Tab>.

Moves cursor to the Grant/Program

selection.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Click checkbox to grant Program

Operations for this example. Click the OK
button

Closes Block Parameter form and stores

the configuration entries.

ATTENTION
For this example, we will skip the other tabs on the Block Parameters form, since a
DATAACQ block will be used for alarm purposes. Please feel free to practice entering
data in the other tabs, using the online Help for support.
8

This completes the AI block configuration

for the sample loop. Go to the next
procedure Configuring DATAACQ block
for sample loop.

Configuring DATAACQ block for sample loop

Step

Action

In CM101 chart, double-click DATAACQ

block.

R400
July 2010

Result
Opens DATAACQ Block Parameters
form with Name field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

185

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >DATAACQ_101<. Press <Tab>.

Moves cursor to Description field.

Key in >Level Input Conditioning<. Press

<Tab>.

Moves cursor to Eng. Units field.

Key in >Percent<. Press <Tab>.

Moves cursor to Execution Order in CM

field and highlights it.

Accept the default value 20. Click Alarms

tab.

Opens Alarms tab form.

ATTENTION
For this example, we will accept the default values for the other parameters on the
Main tab. These values are okay for the sample loop. Please feel free to practice
entering data in the other fields, using the online Help for support.

186

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
6

Action
Sequentially press <Tab> until the PV
High field is highlighted. Key in >70<.
Press <Tab>.

7
button to open dropdown menu
Click
and select HIGH. Press <Tab>.

Result
Moves cursor to Priority field and
highlights it.

Moves cursor to Severity field and

highlights it.

Key in >8<. Press <Tab>.

Moves cursor to PV Low field and

highlights it.

Key in >25<. Press <Tab>.

Moves cursor to Priority field and

highlights it.

10
button to open dropdown menu
Click
and select HIGH. Press <Tab>.

R400
July 2010

Key in >8<. Press <Tab>.

Moves cursor to Severity field and

highlights it.

Moves cursor to PV Low Low field and

highlights it.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

187

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
12

Action
Key in >15<. Press <Tab>.

13
button to open dropdown menu
Click
and select URGENT. Press <Tab>.

Result
Moves cursor to Priority field and
highlights it.

Moves cursor to Severity field and

highlights it.

Key in >15<. Press <Tab>.

Moves cursor to next field. Double click

PV High High field to highlight it.

Key in >85<. Press <Tab>.

Moves cursor to Priority field and

highlights it.

16
button to open dropdown menu
Click
and select URGENT. Press <Tab>.

Moves cursor to Severity field and

highlights it.

ATTENTION
For this example, we will accept the default values for the other parameters on the
Alarms tab. These values are okay for the sample loop. Please feel free to practice
entering data in the other fields, using the online Help for support.

188

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
17

Action
Key in >15<. Click Block Pins tab.

Scroll the Parameters list box to

find PVLLALM.FL. Click it.

Result
Opens Block Pins tab form.

Adds PVLLAM.FL as visible block output

pin.

Check that the Pin Position is

Output and Top/Bottom. Click the
Add button.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

189

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step
19

Action
Find PVLOALM.FL in the
Parameters list box. Click it.

Result
Adds PVLOALM.FL as visible block
output pin.

Check that the Pin Position is

Output and Top/Bottom. Click the
Add button.

190

Click PV in Output - Bottom list box. Click

the Remove button.

Removes PV from list box.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Scroll the Parameters list box to

find PV. Click it.

Result
Adds PV as visible block output pin on
the right-hand side of the block.

Click Left/Right in Pin/Position box.

Click the Add button.

Click the OK button.

Closes the Block Parameters form and

stores the configuration entries.

ATTENTION
For this example, we will accept the default values for the other parameters on the
Block Pins tab as well as the remaining tabs. These values are okay for the sample
loop. Please feel free to practice entering data in the other tabs, using the online Help
for support.
23

This completes the DATAACQ block

configuration. Go to the next procedure
Configuring PID block for sample loop.

Configuring PID block for sample loop

Step

Action

In CM101 chart, double-click PIDA block.

R400
July 2010

Result
Opens PID Block Parameters form with
Name field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

191

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >PID_101<. Press <Tab>.

Moves cursor to Description field.

Key in >Recycle Loop Controller<. Press

<Tab>.

Moves cursor to Engineering Units field.

Key in >Percent<. Press <Tab> six times.

Moves cursor to Normal Mode field and

highlights it.

ATTENTION
For this example, we will accept the default values for the skipped parameters on this
tab. These values are okay for the sample loop. Please feel free to practice entering
data in the other fields, using the online Help for support.
5
button to open dropdown menu
Click
and select AUTO. Press <Tab>.

192

Moves cursor to Normal Mode Attribute

field and highlights it.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

6
button to open dropdown menu
Click
and select NORMAL. Click the Algorithm
tab.

Result

Opens the Algorithm tab form with

Control Equation Type highlighted.

(Please see previous Attention note

about skipped parameters.)
7

Accept the default value EQA. Press

<Tab>.

Moves cursor to Selected Control Action

option.

Click DIRECT to select it. Click the Set

Point tab.

Opens the Set Point tab form with SP

field highlighted.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

193

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

(Please see previous Attention note

about skipped parameters.)
9

Key in >50<. Click the OK button.

Closes the Block Parameters form and

stores the configuration entries.
(Please see previous Attention note
about skipped parameters.)

This completes the PID block

configuration for the sample loop. Go to
the next procedure Configuring AO block
for sample loop.

Configuring AO block for sample loop

Step
1

194

Action
In CM101 chart, double-click the AO
function block

Result
Opens the AO Block Parameters form
with Name field highlighted.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

Key in >AO_FLOW<. Press <Tab>.

Moves cursor to Description field.

Key in >Flow Control Output<. Click the

OK button.

Closes the Block Parameters form and

stores the configuration entries.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

195

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

ATTENTION
For this example, we will accept the default values for the other parameters on the
Process tab as well as the remaining tabs. These values are okay for the sample loop.
Please feel free to practice entering data in the other tabs, using the online Help for
support.
4

This completes the AO block

configuration for the sample loop. Go to
the next procedure Wiring blocks in
CM101 for sample loop.

Wiring blocks in CM101 for sample loop

Step

Action

Result

In CM101 chart, double-click the

OUT_VALUE pin on the AI_LEVEL block.

Pin is highlighted and cursor shape

changes to cross-hairs
.

Move cursor so it is aligned on the P1 pin

for the DATAACQ block and click.

Wire is drawn between the pins, P1 pin is

highlighted, and cursor reverts to its
normal shape.

Repeat Steps 1 and 2 to wire these other

pins together. Be sure to add vertices
where required by clicking in the desired
path to the final pin.

See the following figure for a view of

completed CM101 with all blocks wired.

DATAACQ_101 PV -> PID_101 PV

PID_101 OP -> AO_FLOW
CAS_IN.VALUE
4

196

This completes the wiring of the blocks in

CM101. Close the CM101 chart and click
Yes to save changes. Go to the next
procedure Adding parameter connections
for sample loop interlocks.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Figure 22 Completed CM101 for sample loop

Adding parameter connectors for sample loop interlocks
This procedure assumes that a CM named CM102 will be created for the pump control
loop in the example application. The CM102 will include a standard Device Control
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

197

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

block and Discrete I/O Channel blocks to start and stop the pump as shown in the
following figure.

Figure 23 Sample CM with Device Control block for pump control in

sample loop.
Step

198

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

Action

Result

With CM102 chart open, click the

parameter connector button in the
toolbar.

Cursor shape changes to cross-hairs

Click SI pin on DEVCTL block. Doubleclick area adjacent to pin.

Parameter connection box appears.

R400
July 2010

Click button

Scroll in the Point Names list box to find

CM101 DATAACQ_101. Click point.

Opens the Point Selector dialog box.

Populates the Parameters list box with

applicable parameters related to the
point.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

199

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Step

200

Action

Result

Scroll in the Parameters list box to find

parameter PVLLALM.FL. Click
PVLLALM.FL.

Parameter is inserted into the parameter

Selected Item field.

Click the Select button.

Parameter name is inserted into the

parameter connection box.

Click IN pin on FTRIGA block. Doubleclick area adjacent to pin.

Parameter connection box appears.

Repeat Steps 3 to 6 to select parameter

CM101.DATAACQ_101.PVLOALM.FL
for this connection box.

See the following figure for a completed

CM102 with parameter connections.

Close Point Selector dialog box. This

completes the addition of parameter
connections for sample loop interlocks
and the CM creation tutorial. Go to the
next section Loading Components
Online.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.4. Configuring Fieldbus Components In a Control Strategy

Figure 24 Completed CM102 with parameter connections for sample loop

interlocks.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

201

5. Configuration
5.5. Loading Components Online

5.5

Loading Components Online

About load operations

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.
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.

202

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

ERDB
IOM
FB

Associated
With

CM1
AIC1

Load with
Contents
IOM
FB
Assigned
To

Load

CEE FB

PID1
Associated
With

AOC1

Assigned
To

CPM Slot 01
FIM Slot 05

CN 01

CPM
FB
IOMs

LINK1
FB

Assigned
To

FD
FB

Associated
With

CM2
FF AIC2
FF
PID2

Load
H1 Link 1

Remote
Termination
Panel

FIM
FB

Load with
Contents

FD
FB

Associated
With

FF AOC2

LINK2
FB

FOUNDATION Fieldbus Compliant Devices

Notes:
CM = Control Module
CN = ControlNet Module
CPM = Control Processor Module

FB = Function Block
FIM = Fieldbus Interface Module
IOM = Input/Output Module

Figure 25 Overview of load operations used to initiate components online.

REFERENCE - INTERNAL
Please refer to Load Interactions for Fieldbus Related Operations in Appendix
J for more information.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

203

5. Configuration
5.5. Loading Components Online

About Load Dialog box

The following figure shows a sample Load Dialog box invoked for a load with contents
operation for a CIOM-A FIM. It provides a brief description of the dialog box features
for quick reference.
The load operation is still an offline function. The Load Dialog box
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.

Lists components
to be loaded

Chance to
select partial
load, if
applicable

Shows
current
state of
component

Specifies state
component
must be in
during load

Specifies state
component will
assume after
load is completed

Individual checkboxes
let you edit list of
components to be
loaded
Can select
another state
from dropdown
menu for this
field

Shaded area flags

components in
Active State

Components in
Active state are
flagged

Select whether or
not component is
to be automatically
put into Inactive/
Out-Of-Service state
for the load
Select whether or not component is
to be automatically put into selected
Post Load State after the load

Figure 26 Load Dialog box provides more load choices.

204

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

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

CPM/CEE*

FIM/LINK

Check for Uncommissioned fieldbus

devices and initiate match function, as
applicable

Fieldbus Device

IOM*

CM or SCM*

Typical Loaded Icon in

Monitoring Tab

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

205

5. Configuration
5.5. Loading Components Online

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 FIM.

Be sure ALIV does not appear in the LED display

on the front of the FIM. If it does, you must first load
the FIM's personality firmware using the NTOOLS
utility supplied with Experion Engineering Tools.

A CM that contains only

fieldbus function blocks.

We recommend that CMs containing only fieldbus

function blocks be assigned and loaded to the
appropriate FIM LINK. They will only take up
unnecessary memory and execution time in the
CEE. .

A CM that contains both

Experion and fieldbus
function blocks.

Be sure CMs that contain Experion function blocks

are assigned and loaded 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 link 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.

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
Uninitialized

206

System Management Services

SM_IDENTIFY
SET_PD_TAG (Clear = False)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

SMK State

System Management Services

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 fully operational.
Fieldbus device matching rules
The CIOM-A 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.

R400
July 2010

Then, the matching rule is . . .

If the Device
ID is . . .

And, the Device

State Is . . .

Specified.

Uninitialized

The device ID (DEV_ID) must match. If the

desired physical device tag (PD_TAG) and
node address (ADDR) are available, FIM 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, FIM will assign it to the device.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

207

5. Configuration
5.5. Loading Components Online

If the Device
ID is . . .

Not specified.

Then, the matching rule is . . .

And, the Device

State Is . . .
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.

Initialized

The physical device tag (PD_TAG) must match.

If the desired node address (ADDR) is not in
use, FIM 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.

Loading a CIOM-A FIM and its Links

The following procedure outlines the typical steps used to "load" a CIOM-A FIM
through the Project tab in Control Builder. It assumes that the FIM and its associated
RTP are installed and capable of communicating with the system.
TIP
If present, it is a good idea to load the CPM and its CEE first to verify the
supervisory communications path.

Step

Action

Check that the OK LED on the front of

the CIOM-A FIM is flashing and the
numbers 1 and 2 are sequencing in the
left-hand LED on its front panel display.

208

Result
Confirms that the designated CIOM-A
FIM is operating.
(If ALIV appears in the CIOM-A FIM's
front panel display, you must load the
CIOM-A FIM's personality firmware
before proceeding.)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Step
2

Action
Click the CIOM-A FIM block icon in the
Project tab.

Result
Opens the Load Dialog box.

Click Controller->Load.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

209

5. Configuration
5.5. Loading Components Online

Step

Action

Result

TIP
The associated CIOM-A FIM Links are included with a CIOM-A FIM load even if the
selected action is Load instead of Load with Contents. We suggest just loading the
CIOM-A FIM without all of its contents first to be sure communications paths are
working.
3

Be sure a check appears in the checkbox

for the CIOM-A FIM listed in the Load?
column.

Load Progress dialog box appears. The

following illustration is for example
purposes only.

Click the OK button.

210

When load is complete, click Monitoring

tab.

Opens Monitoring tab.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Step

Action

Result
Opens directory and exposes LINK icons.

Confirm that CIOM-A FIM icon now

appears in Monitoring tab. Click
sign for CIOM-A FIM icon.

plus

This completes CIOM-A FIM load. Go to

the next section Matching
uncommissioned device to project device
or vice versa.

Matching uncommissioned device to project device or vice versa

TIP
If you are running R210 or greater software, the FIM will detect when an
uncommissioned (new) device is added to the link, prepare it for joining the
link, and define the device as an uncommissioned Basic device. In this case,
you can skip the following procedure.

Use the following procedure to initiate the device matching function to conveniently
match uncommissioned fieldbus devices with their counterpart devices in the Project tab
or project devices. It is best to match devices before you download the fieldbus device
from Project to the Link.
Step

Action

If Link is inactive (blue icon), go to Step

Result
Link must be active to detect
uncomminssioned devices on it.

If Link is active (green icon), go to Step 6.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

211

5. Configuration
5.5. Loading Components Online

Step
2

Action
Click the Link 1 icon.

Selects Link 1.

Calls up the Change State dialog box.

Click the

212

Result

toggle state button.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Step

Action

Result

Click the Yes button.

Initiates Link startup. CIOM-A FIM icon

turns green and LINK icon turns yellow.

Wait for LINK 1 to startup and icon to turn

green.

LINK 1 is now active and detects any

uncommissioned devices
to it.

connected

TIP
If a connected fieldbus device is not being detected by the link, try increasing the Slot
Time value through the LINK Block Parameters configuration form. With Link icon
selected, click Edit>Configure Module Properties, click the Network Management (LM)
tab, select the Slot Time field (default value is 8), key in 10, press <Enter>, click OK,
wait for the value to change, and click OK to close the form.
6

R400
July 2010

On the Project tab,click Field Devices>Device Match.

Calls up Link Parameters form with

Device Matching Dialog tab selected. The
following illustration is for example
purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

213

5. Configuration
5.5. Loading Components Online

Step

Action

Check for block type matches between

Initiates Tag and Address change in the

Uncommissioned Device to match the
Project Device. Dialog box appears to
show progress of the change. This may
take several minutes to complete.

When operation is completed, confirm

that Tag and Address assignments for
the selected Uncommissioned Device
and Project Device now match.

The match operation was a success. The

following illustration is for example
purposes only.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

217

5. Configuration
5.5. Loading Components Online

Step

Action

Result

TIP
After matching an uncommissioned device to a project device, it is a good idea to
right-click the device icon and select Upload from the popup menu and click Continue
to load device data into the Monitor database. Then, right-click the device icon and
select Update to Project from the popup menu and click Continue to synchronize the
data in the Project database with the Monitor database.

218

Repeat Steps 6 to 10 for another device

or repeat this procedure for LINK 2, as
required.

Return to appropriate Step in this

procedure.

Click the OK button.

Closes the dialog.

Go to the next section Loading Link

contents or fieldbus device to download
the Project Device to the
Uncommissioned Device

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Loading Link contents or fieldbus device

Use the following procedure to load Link contents or fieldbus devices. It assumes that the
CIOM-A FIM has been loaded and the fieldbus devices are installed and powered on the
Links.
TIP
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 FIM. If you
load the Control Module first, you may get an error message indicating that
the "parent" block is not available.

Step
1

Action
In Project tab, click the desired LINK
icon.

Result
Opens the Load Dialog box.

Click Controller->Load With Contents.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

219

5. Configuration
5.5. Loading Components Online

Step

Action

Result

TIP
If you just want to load a fieldbus device, click the device icon and click Controller>Load. We suggest using LINK/Load With Contents so you can load more than one
device at a time.

220

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Step

Action

Confirm that checkmarks appear in the

LINK and Device checkboxes listed in the
Load? column.

Result
Identify what components are to be
loaded.

(If you do not want to load a given

device, just click it to remove the check
mark from its check box.)

TIP
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.
3

R400
July 2010

Accept the default Partial Load selection

for the Resource and Transducer blocks
for a device.

Confirm Partial Load for Resource and

Transducer blocks that remain dedicated
to the device.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

221

5. Configuration
5.5. Loading Components Online

Step

222

Action

Result

To change the Post Load State for

selected components, click the
appropriate Post Load State row.

Opens the dropdown menu to select

another state, as applicable.

Click the checkboxes to automatically

inactivate the fieldbus devices for the
load and to automatically return fieldbus
devices to post load state after the load.

Initiates automatic toggle state function

during and after the load operation.

Click the OK button.

Initiates "Load" and opens Load Dialog

box to show load progress. This
illustration is for example purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.5. Loading Components Online

Step

Action

Result

TIP
If errors are detected, 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 following illustration is for example purposes only and the errors listed are
not typical.

If the load generates errors identifying subschedule 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
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 subschedule load errors, it cannot function as the backup LAS without a
schedule.
Please see the
Checking/changing fieldbus device functional class section for details on
reconfiguring a device as a Basic type.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

223

5. Configuration
5.5. Loading Components Online

Step
7

Action
Once the load is complete, click
Monitoring tab.

Result
Opens Monitoring to view loaded devices
in LINK directory. This illustration is for
example purposes only.

TIP
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 FIM, as applicable.
8

224

Repeat Steps 1 to 7 to load another Link

or device, as required. This completes
the LINK/fieldbus device load. Go to the
next Section Operation for information on
monitoring fieldbus devices.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.6. Configuring Advanced Alarming

5.6

Configuring Advanced Alarming

Overview
With R400, 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.
Considerations
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 EPKS.
You can assign criticalities after the device specific conditions are created to
generate the alarms.
Conditions are associated with one or more diagnostic parameters to generate alarm.
The alarm server tracks diagnostic alarms similar to other system 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.
Enabling or disabling status of a condition can be performed 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

225

5. Configuration
5.6. Configuring Advanced Alarming

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.

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.
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.
To open the Configuration dialog box from FF device template/device instance, perform
the following steps.
Step
1

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

ATTENTION
You cannot generate default values for configuring alarm conditions from
the DD as it is 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
226

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.6. Configuring Advanced Alarming

the Configuration dialog box.

Configuring/creating a condition
To configure a condition, perform the following steps.
Step

Action

From the Configure Advanced Alarming dialog box, click Condition

Listing tab.

Click New.
The Condition Configuration dialog box appears.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

227

5. Configuration
5.6. Configuring Advanced Alarming

Step

Action

Type a name for a condition in 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
information to provide a valid name.
An error message appears when you want to configure more
than 32 conditions.
Click OK to continue.
4
228

The default values for Alarm Criticality and Priority are Failed and Urgent
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.6. Configuring Advanced Alarming

Step

Action
respectively.
From the Alarm Criticality tab, select the appropriate criticality for the
condition.

From the Priority tab, select the appropriate priority for the condition.

ATTENTION
Each condition is configured with a priority, which manages
the condition reported to Experion system.
A condition can generate a Journal event only or an alarm with
low, high or urgent priority.
6

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:
a)

Select a parameter from the list and the list of available bits are
available.

Select one or more bits from the list, the summary of all the selections for
the condition appears as a tree view.

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.
A message appears displaying the information to clear all the
configuration information selected for the condition. Click Yes to
continue.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

229

5. Configuration
5.6. Configuring Advanced Alarming

Step
7

Action
Click Save.

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

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.
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 disabled 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
230

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.6. Configuring Advanced Alarming

what was set is retained on the device instance.

To enable/disable a condition, perform the following steps.

Step

Action

From the Configure Advanced Alarming dialog box, click Condition

Listing tab.

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.

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

ATTENTION
The conditions can be enabled/disabled in the Device
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

231

5. Configuration
5.6. Configuring Advanced Alarming

Step

Action
Diagnostics tab in the configuration form of FF devices from
Project /Monitoring modes.
In the Project mode, the conditions which are enabled or
disabled are saved in the ERDB and not saved in the devices
until the device is loaded.
To enable/disable a condition in Project mode, perform the
following steps:
a)

Right-click the device instance to select Module

Properties.
The configuration form appears.

Click the Device Diagnostics tab.

Under the Alarm Conditions Status, select or clear

the check box to enable/disable the conditions.

In the Monitoring mode, the conditions that are modified apply

to the devices and are not saved in the ERDB. Therefore, to
save the modified conditions in the ERDB, perform the following
steps.
a)

Click Upload.

Click Update to Project.

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.

232

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.6. Configuring Advanced Alarming

Editing an existing condition

To edit an existing condition, perform the following steps.
Step

Action

From the Configure Advanced Alarming dialog box, click Condition

Listing tab.

Double-click a condition.
Or
Click a condition and Click Edit.
The Condition Configuration dialog box appears.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

233

5. Configuration
5.7. Block Offnet Diagnostic Alarm

Step

Action

Perform through steps 4 to 7 of the section Configuring/creating a condition.

ATTENTION
You can delete an alarm condition, based on the required alarms to be
generated.
To delete a condition in the Condition Listing tab

5.7

Select the condition to click Delete.

Click Yes to confirm the deletion of the selected condition or

press Delete on the keyboard.

Block Offnet Diagnostic Alarm

In R400 and later, a 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

234

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.7. Block Offnet Diagnostic Alarm

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.

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.
Behavior of Block Offnet Alarm

Behavior of Device Offnet System

Alarm

Block Offnet Alarm is not reported

for each loaded function block in
the device.

Device Offnet System Alarm is not

reported for the device.

Loss of
communication
between an FF
device and FIM

A high-priority Block Offnet Alarm

is reported for only those loaded
function blocks in the device,
which are configured to report the
Block Offnet Alarm.

A high-priority Device Offnet

System Alarm is reported for the
device.

Communication
resumes between an
FF Device and FIM

Previously reported Block Offnet

Alarms change from Active to
Returned to Normal in the Alarm

The Device Offnet System Alarm

changes from Active to Returned
to Normal in the System Alarm

Communication loss
scenario
Loss of
communication
between C300 and
FIM
(This condition
occurs if both the
FTE cables are
disconnected.)

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

235

5. Configuration
5.7. Block Offnet Diagnostic Alarm

Communication loss
scenario

Behavior of Block Offnet Alarm

Summary Display.

Behavior of Device Offnet System

Alarm
Summary Display.

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

Inactivating a
Fieldbus Link when
the device is online.

A Block Offnet Alarm is not

reported for each loaded function
block.

A high-priority Device Offnet

System Alarm is reported for the
device.

Inactivating a
Fieldbus Link when
the device is off the
network.

Previously reported Block Offnet

Alarms changes from Active to
Disabled in the Alarm Summary.

A high-priority Device Offnet

System Alarm is reported for the
device.

Activating a Fieldbus
Link.

Previously reported Offnet Alarms

changes to Disabled when the
Link is inactivated in the Alarm
Summary. When activated, these
alarms are regenerated to
indicate the current condition of
the alarm.

Previously reported Offnet Alarms

changes to Disabled when the
Link is inactivated in the Alarm
Summary. When activated, these
alarms are regenerated to indicate
the current condition of the alarm.

If the Offnet condition does not

exist, the previously reported
alarms remain in the Alarm
Summary as Disabled.

Behavior of Device Offnet System

Alarm

If the Offnet condition does not

exist, the previously reported
alarms remain in the Alarm
Summary as Disabled.

Activating or
Inactivating a CM
containing a FF
function block.

Changing the EXECSTATE

parameter value has no effect on
the alarms reported by Fieldbus
blocks.

Changing the EXECSTATE

parameter value has no effect on
the alarms reported by Fieldbus
blocks.

Changing the state

Changing the state of a CEE

236

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.7. Block Offnet Diagnostic Alarm

Scenario

Behavior of Block Offnet Alarm

Behavior of Device Offnet System

Alarm

of a CEE containing
a FF function block
to Idle or Run..

containing Control Modules,

which contain Fieldbus blocks,
has no effect on the alarms
reported by the Fieldbus blocks.

containing Control Modules, which

in turn contain Fieldbus blocks, has
no effect on the alarms reported by
the Fieldbus blocks.

Deleting a Device,
Link, FIM or CM
containing an FF
function block

No alarms are reported for device

offnet conditions.

No alarms are reported for device

offnet conditions.

Enabling the
reporting of the Block
Offnet Diagnostic
Alarm for an
individual FF function
block when the
device is online.

A change event is logged in the

Event Summary indicating
OFFNETALM_ENABLED is set to
ON.

(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 the Block
Offnet Diagnostic
Alarm for an
individual FF function
block when the
device is off the
network.

A high-priority Block Offnet Alarm

is reported for that function block.
A change event is logged in the
Event Summary indicating
OFFNETALM_ENABLED is set to
ON.

A high-priority Device Offnet

System Alarm is reported for the
device, when the device goes
offnet. There is no change in the
system alarm.

(The precondition is
that the Block Offnet
Diagnostic Alarm is
configured not to be
reported for the
function block, when
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

237

5. Configuration
5.8. Configuring non-cache parameters

Scenario

Behavior of Block Offnet Alarm

Behavior of Device Offnet System

Alarm

the device goes off

the network.)
Disabling the
reporting of the Block
Offnet Diagnostic
Alarm for an
individual FF function
block when the
device is online.

A change event is logged in the

Event Summary indicating
OFFNETALM_ENABLED is set to
OFF.

Disabling the
reporting of the Block
Offnet Diagnostic
Alarm for an
individual FF function
block when the
device is off the
network.

The previously reported Block

Offnet Alarm for that function
block changes from Active to
Disabled in the Alarm Summary.

5.8

There is no change to the Device

Offnet System Alarm.

A change event is logged in the

Event Summary indicating
OFFNETALM_ENABLED is set to
OFF.

Configuring non-cache parameters

To configure non-cache parameters, perform the following steps.
WARNING
The non-cache capability bypasses the normal data-acquisition optimizations
which are implemented by FIM. Configuring or monitoring the non-cache
parameters can lead to performance degradation or visible anomalies
Therefore, you must configure non-cache parameters under special
circumstances recommended by Honeywell, Inc. or device vendors.

Step
1

Action
On the Project mode, right-click the device instance to select Module
Properties.
The configuration form appears.

238

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

5. Configuration
5.8. Configuring non-cache parameters

Step
2

Action
Click the Device Diagnostics tab.

In the Non-Cache Parameters, click

that appears in the text box.

The Point Picker dialog box appears.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

243

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

Figure 27 Typical FIM Detail display in Station.

REFERENCE - INTERNAL
Please refer to the Operator's Guide for detailed information about calling up,
navigating, and viewing Station displays.

6.2

Foundation Fieldbus Detail Displays/Faceplates

With R311.2, a new set of Detail Displays and faceplates are created for the Foundation
Fieldbus control points. These displays provide clarity between the Fieldbus and CEE
controls. These displays are HMIWEB displays. The FF Detail Displays and faceplates
are designed to display only the standard FF parameters. The FF vendor-specific
parameters are not displayed.
This feature is applicable to the following Foundation Fieldbus control points.
PID (Proportional Integral Derivative)

244

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

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).
REFERENCE - INTERNAL
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.

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.
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

sysdtlffaia

sysdtlffai_fp

sysdtlffaoa

sysdtlffao_fp

sysdtlffdia

sysdtlffdi_fp

sysdtlffdoa

sysdtlffdo_fp

PID

sysdtlffpida

sysdtlffpid_fp

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

245

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

MAI

sysdtlffmaia

sysdtlffmai_fp

Tabs of FF Detail Displays

The FF Detail Displays are associated with different tabs. When you click a specific tab,
its associated .htm page is loaded.
REFERENCE INTERNAL
Refer to the Experion 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.
Detail Displays tab name
Main Tab Display

Description
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

246

This page contains the options that you can select for
altering the Input and output block processing and the

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

Detail Displays tab name

Description

Display

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. The corresponding alarm priority values are
mapped using system acronym table and are
indicated to adjacent numeric values. 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.

Detail Displays tabs of the different Foundation Fieldbus blocks

The Detail Displays of the FF blocks do not display all the display tabs. Not all tabs
appear for all FF blocks. Use the following table to determine the tabs that appear for
each FF blocks.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

247

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

FF Blocks

PID

MAI

Main

Tuning

Loop Tuning

Alarms

Connection

Chart

I/O status Option

Set Point

PV & OP

Versus Tabs

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

248

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

Figure 28 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

249

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

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

Common functionalities of faceplates
There are a few common functionalities that are applicable to one or more FF point
faceplates.
REFERENCE - INTERNAL
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
250

Applicable faceplate

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

Functionality
Mode Attribute interpretation

Applicable faceplate
sysdtlffai_fp.htm
systdlffao_fp.htm
sysdtlffpid_fp.htm
sysdtlffdi_fp.htm
sysdtkffdo_fp.htm
sysdtlffmai_fp.htm

Intermediate EU values

sysdtlffai_fp.htm
systdlffao_fp.htm
sysdtlffpid_fp.htm

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
sysdtlffpid_fp.htm

READBACK Value

sysdtlffpid_fp.htm
sysdtlffao_fp.htm

Auto selection

sysdtlffpid_fp.htm
sysdtlffao_fp.htm
sysdtlffai_fp.htm
sysdtlffmai_fp.htm
sysdtlffdi_fp.htm
sysdtlffdo_fp.htm

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

251

6. Operation
6.2. Foundation Fieldbus Detail Displays/Faceplates

FF Detail Displays example templates for Control Builder

FF Detail Displays example templates for Control Builder are installed as part of
Experion installation. These examples 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.
Using Station Event Summary display
Like the Detail displays, the 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. The following illustration shows a typical
Event Summary display that includes FIM, Link, and Device indications. Use this display
to get a quick review of recent actions that have been initiated within the system.

Figure 30 Event Summary display includes fieldbus related details.

252

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

6.3 Monitoring Fieldbus Functions Through Monitoring

Tab
Inactivating/Activating a Link
Use the following procedure to inactivate/activate a fieldbus Link through the Monitoring
tab in Control Builder.
ATTENTION
Inactivating a fieldbus Link essentially shuts downs the Link and the CIOM-A
FIM, if both 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 link is inactive.

TIP
You can initiate this same function through the corresponding Detail display
in Station.

Step

Action

In Monitoring tab, click LINK icon.

Click the Toggle State button
the toolbar.

R400
July 2010

Result
Opens Change State dialog box.
in

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

253

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

TIP
You can also initiate a Link shutdown through the SEG Command field on the Link
Parameters form in Monitoring. Just click Edit->Configure Module Properties to call up
the Link Block Parameters form, select SHUTDOWN from the dropdown menu for the
SEG Command field, and click Yes to acknowledge the action. You can also confirm
the current state of the link through the SEG State field. (Note that all associated
fieldbus device blocks are also shutdown, including those contained in Control
Modules.)
2

254

Click the Yes button.

Initiates state change. The LINK icon

changes from green to blue. This
illustration is for example purposes only.
The CIOM-A FIM is only inactivated
when both Links are inactivated.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

With LINK icon selected, click the Toggle

State button

R400
July 2010

Result
Opens Change State dialog box.

in the toolbar.

Click the Yes button.

Initiates state change. The icon changes

from blue to green. This may take a few
seconds. This illustration is for example
purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

255

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

TIP
You can inactivate/activate a selected fieldbus function block by right-clicking the
function block and selecting inactivate or activate the selected Item.

This completes the inactivate/activate

function.

Monitoring/Interacting with given component/block

Once you download a CIOM-A FIM and its contents, you can use the Monitoring tab to
interact with the components including the function blocks in the fieldbus devices.
You simply double-click the desired component/block icon in the Link/Device tree
menus under the CIOM-A FIM icon to call up the associated Configuration form. Click
the given tab to view the current status of the related fieldbus data. Both the CIOM-A
FIM and LINK function blocks must be active to view on-line data. The data can be
viewed either by name or parameter reference by not checking or checking the Show
Parameter Names checkbox at the bottom of each tab.

256

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

REFERENCE - INTERNAL
Please refer to the Control Building Guide sections in On-Line Monitoring
Using Control Builder for detailed information:
Setting the CEE Inactive
Setting I/O Active
Setting I/O Inactive
Changing Parameters while Monitoring

Checking/changing fieldbus device functional class

TIP
If you are running R210 or greater software, an online wizard will be launched
when you try to change the functional class of a device. In this case, follow
the instructions in the wizard instead of the steps in the following procedure.

Use the following procedure to check and change, if necessary, the functional class of the
fieldbus device. The illustrations used are for example purposes only and may differ from
the actual forms that appear in your system.
Step
1

R400
July 2010

Action
In Monitoring tab, double-click device
icon.

Result
Opens device configuration Parameters
form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

257

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

258

Action

Click Network Management (LM) tab.

Result

Opens Network Management (LM) tab.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

R400
July 2010

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

259

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

ATTENTION
With R400, Device Diagnostics tab is added to enable/disable the alarm conditions
status and configure the non-cache parameters.

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 appear in the dialog
box.

Click OK.
The selected parameter description appears in the corresponding
Parameter Description column.

260

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step
3

Action
Press <Tab> twice.

Result
Moves cursor to the Boot Operational
Function Class

TIP
The FIM is the primary Link Master for both 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.
4
button in the field
If applicable, click
and select BASIC from the dropdown
menu.

Initiates online change value prompt.

Click the Yes button to acknowledge the

change.

Functional boot class changes to BASIC.

Click the OK button to close the

Parameters form.

Return to Control Builder application.

Double-click the Resource block icon

Calls up Resource Block Parameters

form.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

261

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

262

Action

Click the Other tab.

Result

Calls up the Other tab.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

9
button in the User Restart field
Click
and select Restart processor from the
list.

R400
July 2010

Result

Initiates online change value prompt.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

263

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

TIP
The alternative to a restart is manually cycling power to the fieldbus device.
10

Click Yes to restart the fieldbus device.

Fieldbus device operational class

changes to Basic after restart.

TIP
You can confirm the change by calling up the device's Parameters form and checking
that BASIC appears in the DL Operational Functional Class field on the Network
Management (Basic) tab.
11

This completes the procedure. Repeat

the procedure for another device, as
applicable.

Checking live list and interacting with uncommissioned devices

Use the following procedure to check the link for devices that are added to the Live List
as uncommissioned. The illustrations used are for example purposes only and may differ
from the actual forms that appear in your system.
CAUTION
Be sure you review the Guidelines for adding fieldbus device to
"live"/operating Link in the next section before adding an uncommissioned
fieldbus device to an in-service Link.

Step
1

Action
Check the Link icon for the presence of
an asterisk

264

Result

An asterisk signals that an

uncommissioned device has been added
to the link.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

Click the

for the Link icon.

Opens the Link directory tree. This

illustration is for example purposes only.

Double-click the uncommissioned device

Opens the LINK Parameters form with

the Uncommissioned Devices tab open.

icon

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

265

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Check the Uncommissioned devices list

box for these details about the device.
Tag
Address
Range
Device ID
Template
Vendor
Model Name
Device Rev
DD Rev

266

Result

Determine if a block type already exists

for the device in the Control Builder
Library. It will be specified in the
Template column.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step

Action

Result

TIP
It may be a good idea to record the device's Tag name and Device ID for future
reference.
5

If a block type does exist, go to the

previous configuration procedures to
create, assign, configure, match, and
load the device.

A block type must exist before a device

can be integrated with the system. The
illustration is for example purposes only.

If a block type does not exist, create

one using the vendor's DD files as
described in Creating a Fieldbus
device type from vendor DD in the
previous Configuration section.

TIP
It is possible that the uncommissioned device may 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 this tab. Please see Upgrading Firmware in
Uncommissioned Device the next Section Maintenance, Checkout and Calibration for
more information.
A new Link Schedule must be loaded to the FIM and other LinkMaster 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.
6

Click the OK button to close the form.

This completes the check for

uncommissioned devices.

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 Link for the system to provide automatic schedule optimization as noted in
the following procedure.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

267

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Prerequisites
You have completed your control strategy configuration that includes fieldbus blocks
integrated with control modules in Control Builder.
Considerations
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.
See the following procedure to configure the FFLink for automatic schedule
optimization.
Calling up Link Schedule
If You Are in the . . .

268

Then, you can

And, the Link Schedule Configuration

shows. . .

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

If You Are in the . . .

Project Tab

Then, you can

And, the Link Schedule Configuration

shows. . .

Right-click the Link

icon and select Open
Chart from the list.
Or,

The block execution and data publications for

all Control Modules that are configured in
Project and assigned to the LINK or CEE. And,
they contain fieldbus function blocks that are
associated with a device assigned to the given
Link, and/or Experion blocks that participate in
Link publications. See the Sample Link
Schedule configuration display in Project
Figure that follows this table for reference.

Double-click the Link

icon.

Monitoring Tab

R400
July 2010

Same as above.

The block execution and data publications for

all applicable Control Modules configured and
assigned in Project and loaded to the LINK or
CEE. See the Sample Link Schedule
configuration display in Monitoring Figure that
follows this table for reference.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

269

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Figure 31 Sample Link Schedule configuration display in Project.

270

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Figure 32 Sample Link Schedule configuration display in Monitoring.

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 (MUG)

R400
July 2010

Measures percent reduction in used portion of macrocycle, start to end

of last element.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

271

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Term

Description

MUG = 1

optimized used portion length

100%

natural used portion length

Latency Improvement
Factor (LIF)
(reduction factor)

Measures percent reduction in latency from start of input to end of output

Publication Gap
Availability
Improvement (PGAI)

Index based on square of gap sizes greater than 18 milliseconds.

LIF = 1

optimized loop length

100%

natural loop length

PGAI = 1

(sum of squares of lengths of

natural qualifying pub gaps)

(sum of squares of lengths of 100%

optimized qualifying pub gaps)

To configure link schedule optimization

Step

Action

In the Project tab, click the plus sign for the FIM icon to expose its Links in
the tree.

Right-click the first LINK icon and select Module Properties to open the
LINK Block Parameters form.

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 Parameters for Link Configuration in Project Mode for more
information about the selections.

Click the down arrow button in the Sample Skew box and select SKEW or
NOSKEW for desired block execution action.
Refer to Parameters for Link Configuration in Project Mode for more
information about the selections.

272

Repeat Steps 2 to 4 for other Links, as applicable.

Click the OK button to close the form and save the settings.
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab

Step
7

Action
This completes the procedure.

REFERENCE - INTERNAL
Please refer to Link Schedule and Function block execution schedule in this
document for additional schedule information.

CheckingCIOM-A FIM redundancy status and initiating manual switchover

You monitor redundant CIOM-A FIM status and initiate a manual switchover through
the Redundancy Module configuration form in Monitoring mode the same as you would
for a redundant Control Processor Module (CPM). The following illustration shows a
typical Summary tab for a Redundancy Module as viewed in Monitoring mode for
reference.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

7.1

Getting Started

Read this first

The CIOM-A Fieldbus Interface Module (FIM) 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. . .

R400
July 2010

Consider This . . .

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

277

7. Fieldbus Device Commissioning

7.1. Getting Started

For This Function. . .

Link Settings

Consider This . . .
These parameters can effect 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 should never be changed, especially by another host
device.
If the Experion system notices that these parameters have been
changed after a device has been off the network, the FIM takes
the following action:
c)

Changes the parameters back.

De-commission the device (assuming other parameters

have been changed also).

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 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 FIM will take the following action.
f)

De-commission the device.

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 (VCRs)

278

The Virtual Communication Relationships (VCRs) are

communication 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 FIM first encounters a
new uncommissioned device, it will clear its VCRs.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

7. Fieldbus Device Commissioning

7.1. Getting Started

For This Function. . .

Consider This . . .

Link-Master Capable

A Link-Master-Capable device can take over control of a link.

When 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.)

Binding of Fieldbus Devices

to the Experion database

The three most important identification parameters for a

fieldbus device are its:
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 decommissioned 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 recommissioned or matched again to its device object and then
re-loaded.

Initial checks and operations

Stage
1

Funtion

Completed

Check and test all physical wire connections and verify correct
voltage on H1 segment.
References:
Fieldbus wiring selection and calculation

Load FIM block only.

References:

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

279

7. Fieldbus Device Commissioning

7.2. Connecting Devices

Stage

Funtion

Completed

Adding CIOM-A FIM block to Project

Loading a CIOM-A FIM and its Links
3

Was FIM download successful?

NO > Go to Stage 4
YES > Go to Stage 7

Is chassis and CIOM-A FIM powered?

NO > Go to Stage 5
YES > Go to Stage 6

Be sure required voltage is present at the power supply and it is

turned On.
Replace power supply, if required.
Return to Stage 2.

Verify network connections.

Replace FIM, if required.
Return to Stage 2.

Measure and establish H1 segment baseline with Fluke

Scopemeter and Relcom FTB-3 or equivalent equipment.
Go to Stage 8 in the next section Connecting Devices

7.2

Connecting Devices
Stage
8

Funtion

Completed

Connect the next device.

References:
Wiring

Does device appear on link?

NO > Go to Stage 10

280

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

7. Fieldbus Device Commissioning

7.2. Connecting Devices

Stage

Funtion

Completed

YES > Go to Stage 23 in the next section Checking Devices.

Be sure cable is connected to proper segment terminals on RTP

and that the RTP to CIOM-A FIM cable is connected to proper
CIOM-A FIM.
References:
Connecting RTP cable to module
Wiring

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

cable.

Is voltage over 9 volts?

NO > Go to Stage 13
YES > Go to Stage 14

Test the power supply, check that terminators are Installed

properly and check for short circuits.
Return to Stage 9

Does proper number of devices appear on tester?

NO > Go to Stage 16
YES > Go to Stage 15

Check that proper Link is downloaded and that device is

connected to proper link.
References:
Loading a CIOM-A FIM and its Links
Return to Stage 9

Are noise average and peak under 75 millivolts?

NO > Go to Stage 17
YES > Go to Stage 18

R400
July 2010

Check the integrity of all cable connections, cables and verify the
design of the link.
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

281

7. Fieldbus Device Commissioning

7.3. Checking Device

Stage

Funtion

Completed

Return to Stage 9
18

Is lowest signal level over 150 millivolts?

NO > Go to Stage 19
YES > Go to Stage 20

Insufficient power for device. Check power supply and link

design.
Return to Stage 9

Is there an addressing issue?

NO > Go to Stage 21
YES > Go to Stage 22

Device should be present. Replace the device.

Return to Stage 9

Check if address is in unpolled range, check for too many

devices with temporary address.
References:
Tags, Addresses, and Live List
Return to Stage 9

7.3

Checking Device
Stage
23

Funtion

Completed

Does firmware - DD Revision match device revision?

NO > Go to Stage 24
Yes > Go to Stage 25

Upgrade firmware or import new DD file

References:
Replacing Device Template with a Different One

282

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

7. Fieldbus Device Commissioning

7.4. Checking Control Strategy

Stage

Funtion

Completed

Making a fieldbus device type from vendor DD

Match device.
If you are running software version R210 or greater, a wizard is
provided to guide you through the steps for matching an
uncomisisioned device.
References:
Matching uncommissioned device to project device or vice versa

Load (Partial Load) the new device from Project tab.

References:
Loading Link contents or fieldbus device

Measure and compare H1 segment baseline with Fluke

Scopemeter and Relcom FTB-3 or equivalent equipment.

Are measurements within specifications?

NO > Go to Stage 29
YES > Go to Stage 30

Identify source of noise or communication problems and repair or

replace equipment as required.
Return to Stage 27

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.

7.4

Checking Control Strategy

Stage
31

Funtion

Completed

Is control strategy configured?

NO > Go to Stage 32

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

283

7. Fieldbus Device Commissioning

7.5. Flowchart Summary

Stage

Funtion

Completed

Yes > Go to Stage 33

Configure control strategy.

References:
About control strategy configuration

Load control strategy to device.

References:
About load operations

Are parameters correct?

NO > Go to Stage 35
YES > Go to Stage 36

Make required parameter changes on-line to device.

References:
Monitoring/Interacting with given component/block

Upload device to project.

References:
Load Interactions for Fieldbus Related Operations
This completes the commissioning process.
The commissioning process is summarized in the following
flowchart.

7.5

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

284

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

7. Fieldbus Device Commissioning

7.5. Flowchart Summary

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

285

7. Fieldbus Device Commissioning

7.5. Flowchart Summary

286

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1

Adding, Removing and Replacing Components

About removal and insertion under power (RIUP)

REFERENCE - INTERNAL
Please review the Removal and Insertion Under Power (RIUP) Function
Guidelines in the Control Hardware Installation Guide before you RIUP any
module.

The removal of the CIOM-A FIM results in the loss of communications with both H1
fieldbus links.
The removal of an individual fieldbus device only breaks communications with that
device.
General procedure
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.

The direct replacement of a CIOM-A FIM of the same kind is just a matter of turning
OFF the chassis power supply, disconnecting the RTP cable, removing the existing
component, installing a new one in its place, connecting the RTP cable, and turning on
chassis power supply. You may also have to load its "personality" image firmware before
it can become fully operational. Must also reload the CIOM-A FIM from the Project tab
in Control Builder to restore operation.
If you are adding a fieldbus device, observe the following Guidelines for adding fieldbus
device to "live"/operating Link, if the Link is in-service, follow the installation
instructions for the component and then configure it through Control Builder to integrate
it with your control strategy. See the previous procedure for Checking live list and
interacting with uncommissioned devices for more information about including a device
in the system.
If you are removing and/or replacing a fieldbus device, proceed with extreme caution.
You may have to delete, restore, and/or create all hardware connections and the control
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

287

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

strategy database configuration through the Control Builder. You may also have to create
a new block type for the device and/or upgrade the device's firmware. Please refer to the
Replacing a failed device with a like device having the same model name and device
revision or Replacing a failed device with a different device using a different block type
section for more details.
Guidelines for adding fieldbus device to "live"/operating Link
CAUTION
Be sure to observe the following guidelines when adding a fieldbus device
that is Link Master capable to a "live"/operating Link to avoid possible loss of
control and view.
In Experion R300.1 or greater, you can choose to enable the safe handling
option for the CIOM-A FIM instead. See the following Using optional safe
handling for new devices section for more information.

The following guidelines are provided to avoid a rare operating circumstance where a
newly added uncommissioned fieldbus device takes over the Link Active Scheduler role
due to a CIOM-A FIM failure. Since this uncommissioned fieldbus device has not been
loaded with the proper backup link schedule, it will render the link inoperative by
disrupting the periodic publication of device data over the link.
Assign and configure the appropriate block type for the new fieldbus device to the
Link in Project.
Configure the fieldbus device function blocks into the Control Strategy in Project.
Set the address for the device in the range of 248 to 251 decimal or clear the device's
address setting, so it assumes a default address in the high range when it is added to
the Link.
Inactivate the CEE and its CMs to put the CPM in its IDLE mode while the
uncommissioned fieldbus device is commissioned and loaded with the proper link
schedule.
Add the fieldbus device to the link, use the match function through the Monitoring
tab in Control Builder to match the device with its block type, and load the device
from Project.
Load the Control Strategy to CEE from Project.
Activate the CEE and its CMs to put the CPM in its RUN mode.

288

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

REFERENCE - INTERNAL
Please refer to the previous Configuration section for more details about
pertinent configure/load actions noted in the Guidelines above. See the
Fieldbus Integration With Experion System section for general reference
information about the LAS and addresses.

Using optional safe handling of new devices

If you enable the safe handling option for the Series A 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.
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 FIM Block's configuration form in
Control Builder. The default is selected or checked check box, which means safe
handling is enabled.
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.
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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

289

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

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 FIM 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.
Replacing a failed device with a like device having the same model name and
device revision
TIP
If you are running R210 or greater software, 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.

Use the following procedure to replace a failed fieldbus device with a like device having
the same Model Name and Device Revision (DEV_REV). The procedure assumes the
system is offline or in a safe operating mode. The illustrations used are for example
purposes only and may differ from the actual forms that appear in your system
Step

290

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

Disconnect the failed device from the

Link.

Fieldbus device icon turns red in

Monitoring tab.

Right-click the failed device icon.

Opens shortcut menu.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

291

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step
3

292

Action
Select Device Replacement.

Result
Calls up the LINK Block Parameters form
with the failed device listed in the bottom
half of the Device Replacement Dialog.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

TIP
If you did not disconnect the failed device in Step 1, the following message prompt
appears instead of the Device Replacement Dialog telling you to do so before you can
proceed. In this case, repeat Steps 2 and 3.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

293

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

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 checkbox 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 the "Replace the Failed Device with

Uncommissioned Replacement Device"
button.

Warning prompt asks if you want to

continue.

294

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Click the Continue button.

Result

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 result in the next
Step.

Click the Continue button.

Progress dialog appears to track the

status of the replacement.

Wait for Replacement Device Load

Confirmation dialog to appear. Click the
Continue button.

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

295

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

TIP
If you elect to Cancel the load at this time, 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 Monitor tab before putting the device
into operation. See Instantiable block implementation considerations for more
information.

296

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

Click the checkboxes for the automatic

state changes near the bottom of the
dialog box. Click the OK button.

Load dialog appears to track progress of

the load.

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.

Return to normal operation.

This completes the device replacement procedure.

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. This procedure assumes the system is offline or in a safe operating
mode. The illustrations used are for example purposes only and may differ from the
actual forms that appear in your system
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.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

297

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

For more information on Unlike Device Replacement Report, see Unlike

Device Replacement Report.

Step

Action

Optionally, inactivate any CMs that

contain blocks associated with the failed
device.

CM icons are blue.

Disconnect the failed device from the

Link.

Device icon turns red in Monitoring tab.

298

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

In Monitoring tab, locate all Control

Modules (CMs) containing fieldbus
function blocks associated with the failed
device.

R400
July 2010

Result
The associated fieldbus block icons will
be red.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

299

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

300

Action

Result

Right-click the CM and select Force

Delete from the popup
menu.

Opens Force Delete dialog.

Click the Delete Selected object(s)

button.

Deletion errors are displayed in the list

box for the dialog. You can ignore these,
since you know the failed device is off
net.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Click the Close button to acknowledge

any errors or skip this Step, if no errors
are detected.

Repeat Steps 4 to 6 for other CMs, as

required.

Result
Deletes CM (pidloop) from CEE folder
along with fieldbus block (FFAI101) from
device (ST101) in Monitoring tab, for this
example.

TIP
It is a good idea to record the Tag and Address assignments for the failed device
before deleting it.
8

Right-click the failed device icon and

select Force Delete from the popup
menu.

Opens Force Delete dialog.

Click the Delete Selected object(s)

button.

Deletes Failed device from the Link folder

in Monitoring.

In Project tab, double-click the CM

(pidloop) that was deleted from the
Monitoring tab.

Opens CM in control chart.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

301

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

TIP
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.

302

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

Right-click the fieldbus function block and

select Function Block Unassign from the
popup menu.

Unassigns Fieldbus block (FFAI101) from

device (ST101), for this example.

TIP
You must unassign the given fieldbus block from its associated device before you can
delete the device from Project.

ATTENTION
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.
12

Repeat Step 11 for other blocks, if

required.

Click

Click the Yes button.

R400
July 2010

button.

Opens Save prompt.

Closes chart and saves changes to CM.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

303

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

304

Action

Result

Repeat Steps 10 to 14 for other CMs, if

required.

In Project tab, right-click failed device

icon and select Delete from popup menu.

Opens the Delete Selected object(s)

dialog.

Click the Delete Selected object(s)

button.

Device (ST101) is deleted from the LINK

folder, for this example.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

In Library tab, drag and drop block type

for replacement device from applicable
vendor directory to open area in Project
tab.

R400
July 2010

Result
Opens Name New Function Block(s)
dialog.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

305

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

306

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step
19

Action
Key in tag name of failed device in the
Destination column and click the Finish
button.

20
Click the device icon and click the
assign button in the toolbar.

R400
July 2010

Result
Device icon appears in Project tab.

Calls up the Execution Environment

Assignment dialog box.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

307

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

With Devices tab open and device

(ST101) selected, click the Assign button.

Assigns device (ST101) to LINK

(LINK10105), for this example.

Click the Close button.

Closes the dialog.

308

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step
23

Action

Result

Click
to open the FIM, LINK and
Device directories in Project tab.

Expands directories to show contents.

Double-click the device (ST101) icon.

Opens Device Block Parameters form.

Check that the Device Network Node

Address entry matches the address for
the failed device. If required, key in
matching address. Click Ok to close
form.

Address for the replacement device

matches the address assignment of the
failed device.

In Project tab, double-click CM (pidloop)

that contains unassigned function block
for failed device.

Opens CM in control chart.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

309

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Right-click fieldbus block (FFAI101) and

select Function Block Assign from popup
menu.

Opens the Function Block Assignment

Dialog.

Click the checkbox for Device Name

ST101 and click the Assign button.

Assigns block FFAI101 to new device

ST101, for this example.

310

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Repeat Steps 27 and 28 for other blocks,

if required.

Click

Click the Yes button.

Closes chart and saves CM changes.

Connect the replacement fieldbus device

to the Link.

Device (ST102) appears as an

uncommissioned device (UCD) icon

close button.

Result

Opens Save Prompt.

in the LINK folder in the

Monitoring tab.
33

R400
July 2010

Double-click the UCD icon.

Calls up the LINK Block Parameters

Uncommissioned Devices form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

311

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

Click the Match button.

Calls up the Device Match dialog.

Click checkbox to left of Tag column for

matching Project Device (ST101).

Selects project device and activates the

Match buttons.

TIP
Always initiate match from Project Device to UCD for replacement devices.

312

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Result

Click the Match From Project Device to

Uncommissioned Device button.

Opens Warning prompt about

Tag/Address changes in UCD.

Click the Continue button.

Progress dialog appears to track status

of function.

Wait for match to be completed and note

that the UCD's Tag and Address now
match the Project Device. Click the OK
button.

Closes the Match dialog.

In Project tab, click LINK with new project

device (ST101) and click Controller>Load with Contents.

Calls up the Load Dialog.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

313

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Be sure Load checkboxes for

components to be loaded include a
check mark. Click checkbox to
add/remove component as
applicable.

Result

Load With Contents dialog appears to

track progress of the load.

Click the OK button.

314

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Wait for load to complete and check that

UCD changes to commissioned device,
in Monitoring tab.

In Project tab, click CEE with

reconfigured CM and click Controller>Load With Contents.

R400
July 2010

Result

Calls up Load Dialog.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

315

8. Maintenance, Checkout, and Calibration

8.1. Adding, Removing and Replacing Components

Step

Action

Be sure Load checkboxes for

components to be loaded include a
check mark. Click checkbox to
add/remove component as
applicable.

Result

Load With Contents dialog appears to

track progress of the load.

Click the OK button.

316

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.2. Unlike Device Replacement Report

Step

Action

Wait for the load to complete and check

that the CM is restored in Monitoring tab.

Result
Return to normal operation.

TIP
It is a good idea to do an Upload followed by an Update to Project for the fieldbus
device and the CMs after a replacement procedure.
45

8.2

This completes the device replacement

with different block type procedure.

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

317

8. Maintenance, Checkout, and Calibration

8.2. Unlike Device Replacement Report

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

318

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

Vendor 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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.2. Unlike Device Replacement Report

General procedure for FF Unlike Device Replacement: This defines a high-level

procedure of unlike device replacement, which consists of some of the prereplacement 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.
ITEM

COLUMN

CM Name

Affected Control Module

CM Description (DESC
parameter)

Description

Assigned To

Reference end point

(Affected Module)

Reference end point

(Affected Module)

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

R400
July 2010

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

Controller Name

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

319

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

the CM is 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.
Step
1

Action
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.

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.
3

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.

8.3

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.

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Considerations
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.
Using Unlike Template Replacement wizard to make device replacements
All the illustrations used in the following procedure are for example purposes only.

R400
July 2010

Step

Action

In the Project tab, select the fieldbus device you want to replace. Use CTRL
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

321

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

Action
+click to select multiple devices.
OR
In the Library tab, select the device type to be replaced.

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.)

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
the Select button to move selected devices to the Selected Controls
column. Or, just click the Select All button to move all the listed devices to
the Selected Controls column.
(Use the Remove or Remove All button to remove one selected or all
devices from the Selected Controls column, as needed.)

322

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

R400
July 2010

Action

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.

In the Tree View or List View tab, select the replacement device.

Click the Next button to call the Validation page.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

323

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

Action

Click the Validate button to initiate the validation function.

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 the Cancel button to exit the operation and start over after making any
necessary corrections.)

324

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

R400
July 2010

Action

If error or warning messages appear in the Validation Results list box, click
the View Replacement Log button to call up the FF_UTR_Log to review
validation results.

Click the Next button to call up the Replace Device page.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

325

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

Action

Confirm that the devices to be replaced are listed in the Summary list box.

Click the Replace Device button to initiate the replacement function.

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 the Cancel button to exit the operation and start over after making any
necessary corrections.)

326

Check that the Status for each selected control turns to Replaced, when the
function is completed.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.3. Replacing Device Template with a Different One

Step

Action

If error or warning messages appear in the Unlike Template Replacement

Results list box, click the View Replacement Log button 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.

R400
July 2010

Click the DONE button to close the wizard. If applicable, correct any errors
and repeat the procedure.

The completes the procedure, go to the next section.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

327

8. Maintenance, Checkout, and Calibration

8.4. Correcting Some Common UTR errors

8.4

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.
Select another fieldbus device type that
has a sufficient number of resources.

Insufficient VCR's
Insufficient FB Start Entries
Insufficient Link Objects.

8.5

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.

Upgrading Firmware in Uncommissioned Device

Use the following procedure to upgrade the firmware in an uncommissioned device
through Control Builder. This procedure assumes that you have the vendor supplied
upgrade file for the device. It also assumes that you are monitoring the FIM/LINK
through the Monitoring tab in 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

328

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.5. Upgrading Firmware in Uncommissioned Device

devices on the link off control before upgrading firmware in a ST3000,

STT35F, or LX1400 device.

Step

Action

Result

Double-click the uncommissioned device

Opens the LINK Parameters form with

the Uncommissioned Devices tab open.
This illustration is for example purposes
only.

icon

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

329

8. Maintenance, Checkout, and Calibration

8.5. Upgrading Firmware in Uncommissioned Device

Step

330

Action

Result

Click the Load Firmware button

Opens the Device Firmware Upgrade

dialog box. This illustration is for example
purposes only.

Click the Upgrade button.

Opens the Open dialog box. This

illustration is for example purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.5. Upgrading Firmware in Uncommissioned Device

Step
4

Action
Use the Look In field to navigate to
the directory location that includes
the vendor's upgrade file.

Result
Initiates the firmware upgrade. This may
take a few minutes to complete.

Select the file and click Open.

Once the firmware upgrade is completed,

wait for the device to rejoin the network.
This may take up to three minutes. Click

Closes the dialog box and returns to Link

Parameters form.

the close button

Check the Templates column in the form

to see if there is an existing block type in
the Library that matches the upgraded
version of the device.

The system automatically compares the

device with block types stored in the
database to find a match.

If a block type does exist, use

procedures in the previous
Configuration section to initiate a
device match and include the device
in the Control Strategy.

Include the fieldbus device in the control

strategy and the Link Schedule.

If a block type does not exist, create

one using the vendor's DD files as
described in Creating a Fieldbus
device type from vendor DD in the
previous Configuration section.
8

R400
July 2010

This completes the firmware upgrade.

Click the OK button.

Closes the LINK Parameters form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

331

8. Maintenance, Checkout, and Calibration

8.6. Changing or Clearing Tag and/or Address of Uncommissioned Device

8.6 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.
Step

Action

Result

Double-click the uncommissioned device

Opens the LINK Parameters form with

the Uncommissioned Devices tab open.
This illustration is for example purposes
only.

icon

332

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.6. Changing or Clearing Tag and/or Address of Uncommissioned Device

Step
2

Action
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. Use ST102 for this example.
Press <Enter> or click the OK
button.

Result
Warning prompt asks for confirmation of
change.

To clear the tag name, just highlight

it and press <Delete>. Click the OK
button.
3

Click the Continue button.

Initiates change and opens progress

tracking dialog box to show status of the
change.

Wait for change to complete. Press

<Tab>.

Moves cursor to the Address field.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

333

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

Action

Result

To change the address, key in

desired address. Use 24 for this
example. Press <Enter>.

Warning prompt asks for confirmation of

change.

To clear the address, just highlight

it and press <Delete>. Click the OK
button.
6

Click the Continue button.

Initiates change and opens progress

tracking dialog box to show status of the
change.

Wait for change to complete. Click the Ok

button.

Closes the Link Parameter form.

Confirm that the tag for the

uncommissioned device icon in the
Monitoring tab has changed or has been
cleared (NoTag_248). This completes the
tag and address changes for the
uncommissioned device

8.7

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. All
the illustrations used in the procedure are for example purposes only. You can easily
adapt this procedure to any applicable fieldbus device.
Only use the simulate function when the system is offline or in a safe
operating mode for testing purposes.

334

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

Action

Result

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.

Position the jumper or switch to its

simulate enable position.

You can now activate the function

through the Monitoring tab in Control
Builder.

In Monitoring tab, open the directory for

the fieldbus device icon and double click
the Analog Input function block.

Calls up the Block Parameters form.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

335

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

336

Action

Click the Maintenance tab.

Result

Opens the Maintenance form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

R400
July 2010

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

337

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

Action

Result

ATTENTION
With R400, you can disable or enable individual block errors. This is applicable for
Function blocks, Transducer blocks, and Resource blocks and only when block alarm
is enabled in 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 Alarm Display or System Status Display is affected.
Regardless of disabling, the individual block error status is displayed on the blocks
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
6

338

Press <Tab> four times.

Click the
Active.

button and select Simulate

Moves cursor to Simulate En/Disable

field.
Opens Change Online Value
confirmation dialog.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step
7

Action
Click Yes.

Click the
button in the Simulate
Status field.

Result
Initiates the simulate function. Check that
the Simulation Active button is ON in the
Block Errors (Blk Alarm) list on the form.

Opens drop-down menu.

For this example, select Good from the

menu.

Opens Change Online Value

confirmation dialog.

Click Yes.

Sets Simulate Status to Good.

Press <Tab>.

Moves cursor to the Simulate Value field.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

339

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

Action

Result

Key in >25< and press <Enter>.

Opens Change Online Value

confirmation dialog.

Click Yes.

Sets Simulate Value to 25.

ATTENTION
With R400, 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.
14

340

Click the OK button.

Closes the Block Parameters form.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step
15

R400
July 2010

Action
In Monitoring tab, double-click pidloop
icon, for this example only.

Result
Opens pidloop control chart.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

341

8. Maintenance, Checkout, and Calibration

8.7. Using Fieldbus Device Simulate Function

Step

Action

Check that the AI.FF OUT.VALUE is 25.

Confirm that simulate value is active.

Close pidloop control chart. Double-click

the AI.FF block icon.

Calls up the Block Parameters form.

On Maintenance tab, press <Tab> four

times.

Moves cursor to Simulate En/Disable

field.

342

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.8. Preparing Fieldbus Device for a Move or Software Migration

Step

Action

Click the
Disabled.

button and select Simulate

Result
Opens Change Online Value
confirmation dialog.

Click Yes.

Disables the simulate function and

returns the fieldbus device to normal
operation.

Click the OK button.

Closes the Block Parameter form.

This completes the simulate function

example procedure.

8.8 Preparing Fieldbus Device for a Move or Software

Migration
During migration to R400, EDDL constructs are ignored. Therefore, 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. All the illustrations used in the
procedure are for example purposes only.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

343

8. Maintenance, Checkout, and Calibration

8.8. Preparing Fieldbus Device for a Move or Software Migration

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.

Step

Action

symbol
In the Monitoring mode, click
for FIM, LINK, and Device icons.

Displays the FIM menu tree.

Right-click the function block icon.

Calls up the popup menu.

344

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.8. Preparing Fieldbus Device for a Move or Software Migration

Step

Action

Result

Select Inactivate->Selected Item.

Calls up the Change State dialog.

Click the Yes button.

Initiates the action. Check that the

function block icon turns Blue.

Double-click the function block icon.

Calls up the Block Parameters

configuration form.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

345

8. Maintenance, Checkout, and Calibration

8.8. Preparing Fieldbus Device for a Move or Software Migration

Step

Action

On the Process tab, check that the Actual

Mode has changed to OOS.

Confirms that the block is in Out-OfService (OOS) mode.

Click the OK button.

Closes Block Parameters form.

346

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.8. Preparing Fieldbus Device for a Move or Software Migration

Step

Action

Result

Repeat Steps 2 to 7 for other function (if

applicable), Transducer, and Resource
blocks in the device, in that order.

Confirm that all device blocks are in OutOf-Service mode.

This completes the procedure.

Device is now ready to be

decommissioned and moved to another
Link or migrated to a new system
software release.

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.
Step

Action

Right-click the Fieldbus block in the Library view.

Select Edit Type.

In the Font box, type OFFNETALM_ENABLED.

Select OK.
Perform this procedure for each Fieldbus block if you want the parameter to
appear in the configuration form.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

347

8. Maintenance, Checkout, and Calibration

8.9. Interpreting Component LED Indications

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.

8.9

Interpreting Component LED Indications

CIOM-A FIM LED indications

As shown in the illustration below, the CIOM-A FIM has one four-character display and
three two-color LEDs on its front panel. From left to right, the LEDs provide Link 1
status, Link 2 status, and module health status, respectively. The following table
summarizes some typical indications for reference.

4-Character
Display

1-01

Link 1 Status LED

Module Health LED

Link 2 Status LED

Figure 33 FIM front panel indicators.

Table 1 CIOM-AFIM LED Interpretations
If Module Health
LED is . . .

And, 4-Character
Display shows . . .

Then, FIM is . . .

Flashing Red/Green

TEST

Running its self-test.

Flashing Red/Off

LOAD

In the midst of a firmware load sequence.

Flashing Green/Off
or Solid Green

BOOT

Initiating its startup or boot sequence.

Flashing Green/Off

ALIV

in its ALIVE state and ready for its Personality

Image load.

348

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

If Module Health
LED is . . .

Then, FIM is . . .

And, 4-Character
Display shows . . .
RDY

In its READY state and ready for its Boot

image load.

Solid or Flashing
Green

Alternating link states

as noted in the
following rows.

Operating normally. If solid green, there are

Experion Control Data Access (CDA)
connections to the FIM.

If Link 1 or Link 2
LED is . . .

And, 4-Character
Display shows* . . .

Off or Flashing Red

X- - -

Down/offline.

Flashing Green

X - FW

Loading firmware.

Flashing Red

X - FE

Having a firmware load error.

X - CE

Having a communications initialization error.

X - DE

Having a database initialization error.

X - CI

Initializing communications with fieldbus

devices.

X - DI

Initializing database.

X - YY

Communicating with fieldbus devices.

Flashing Green or
Off

Then, LINK is . . .

*Display alternates between Link 1 and Link 2 in two second intervals. The X is either 1
or 2 for the respective Link and YY equals the number of fieldbus devices present on a
given Link.

8.10 FIM Self-Test Diagnostic Codes

The following table lists the self-test diagnostic codes that the FIM steps through upon
power up. If FIM hangs on a test code during power up, cycle power to reboot the FIM.
If error persists, replace the FIM.
Test Code

Target Device(s)

T000

Failure Modes

Function
Signals start of the selftest.

Display Diagnostics
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

349

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code
T001

Target Device(s)
Display Test

Failure Modes

Function

Bad display,
Incorrect assembly

Steps through horizontal/vertical

bars, then 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
LEDs turn RED, then GREEN, and
then turn OFF. The health LED
remains RED for the duration of
the self test.

CPU Diagnostics
T002

860 Initialization
Test

CPU

The 860 system interface unit and

memory controller are changed
from the power-up defaults to the
product values.

T003

CPU Mask Revision

Test

Bad, Obsolete, or
unexpected new,
CPU

This test is done before the ROM

tests, because a wrong CPU could
appear to work, but might fail
timing tests. The Instruction Cache
is enabled after this test.

T010

Boot Image
Checksum Test

Bad flash memory,

CPU, RAM (only if
fault first time after
load)

Computes and verifies the

checksum of the boot image in
ROM.

RAM and Parity Diagnostics

(The RAM hardware functional tests use the dedicated RAM test area, an error left here by a
power cycle will not cause a subsequent RAM flush.)
T020

Main RAM Data

Test

CPU

Checks RAM consistency to make

sure both RAM chips have the
same parity, burst, and so on
configuration.

T021

Lower RAM Word

Access Test

RAM, CPU

Verifies that word patterns can be

written and read back as bytes,
half-words, words, misaligned
words.

350

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

T030

RAM Parity Sweep

Test

Parity errors force

destructive testing
of RAM

Reads RAM until the end or a

parity error is detected.

T031

RAM Parity Sweep

Time Test

Instruction cache,
RAM, Oscillator

Checks the reasonableness of the

time needed to perform the
previous test (T030). (The time is
not measured if a parity error is
detected and memory is flushed.

T032

RAM Memory
Retention Test

Reset circuit

The magic numbers are checked

to see if the data in RAM may still
be valid. In the absence of parity
errors, RAM is considered valid at
boot level. It passes test, bumps

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

351

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Function
power cycle counter and skips
destructive test and flush.

T033

RAM Destructive
Unique Address
Test

CPU, RAM

Verifies all addresses are unique.

Runs with data parity enabled and
fatal.

T034

RAM Destructive
Pattern Test

CPU, RAM

Checks address and data lines by

writing a non-repeating pattern
over the whole memory, then
verifying it. Runs with data parity
enabled and fatal. Multiple passes
for better coverage.

T040

Flash Configuration
Test

CPU, Flash, UPM

The Flash version/revision is read

and any UPM or configuration
changes made. Requires the use
of RAM because flash is not in
read mdoe.

T044

860 Internal RAM

Unique Address
Test

CPU

T045

860 Internal RAM

Pattern Test

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Function
correctly. Only uses the memory
test area, so just shows that the
data cache is enabled and at least
partially functional.

T056

CPU D-Cache
Burst RAM Wrap
Test

CPU, RAM, UPMB

Verify that the RAM burst wraps

on address modulus 4. Perform on
both RAM chips. Only uses the
memory test area.

T057

CPU D-Cache
Integrity Test

CPU

The checksum of the boot code is

repeated with Data Cache
enabled. The test is timed. If the
data cache is not working
properly, the checksum will fail or
the test will take too long.

Hardware Status Register and System Control Diagnostics

T060

WDT Pending Test

CPU, PLD

Verifies that the watch dog timer

timeout pending signal is not
asserted.

T061

DC_FAIL Pending
Test

CPU, PLD

Verifies that the backplane

DC_FAIL pending signal is not
asserted.

T062

Struck IRQ0 Test

CPU, PLD, pullup

Verifies the IRQ0 is not asserted.

If it is asserted, fails in this test, if
WDT Pending and DC_FAIL
Pending are not asserted.

T063

Stuck ICP Timer

Interrupt Test

CPU, PLD, pullup,

ICP ASIC

Verifies that the ICP timer interrupt

IRQ2 is not asserted.

T064

Stuck ICP Comm

Interrupt Test

CPU, PLD, pullup,

ICP ASIC

Verifies that the ICP comm.

Interrupt IRQ3 is not asserted.

T065

SYS_FAIL Assert
Test

CPU, PLD,
Backplane, other
modules

Verifies that SYS_FAIL status is

not stuck . This means it is not
asserted for longer than a to be
determined period necessary to
accommodate other modules'
tests.

T068

Stuck IRQ7

CPU, PLD

Verifies that interrupt from

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

353

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Interrupt Test

Function
daughterboard is not asserted.

ICP ASIC and Shared RAM Diagnostics

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Function

T110

ICP RAM
Destructive Pattern
Test

RAM, PLD, CPU,

buffers

Checks address and data lines by

writing a non-repeating pattern
over the whole memory, then
verifying it. Multiple patterns are
used for better coverage.

T111

ICP ASIC Register

Access Test

ICP ASIC, PLD

ASIC-RAM
interface

The hardware setup parameters

having been written to the ASIC
some time earlier, access to the
ICP ASIC registers is verified, and
the error register is verified as
zero. The ECHO_REV operation
is used to make the ASIC write its
version register to a designated
location in shared RAM. This
value is saved in RAM. The rest of
shared RAM is verified to make
sure that only the designated
location was written.

T112

ICP ASIC Unique

Address Echo Test

ICP ASIC, PLD

ASIC-RAM
interface

Correct access to the ICP shared

RAM from the ASIC is verified
through the Echo test by asking
the ASIC to write each location's
address at the address. This test
is performed once for the address
and once for the complement of
the address. Coverage is not 100
percent because only the 17 LS
address bits are supported by the
ASIC.

T113

ICP Bus Lock Test

ICP ASIC, PlD,

CPU

Verify that the ICP ASIC can be

locked out of its shared RAM by
the CPU. This is accomplished
with the ASIC Echo_REV test by :

R400
July 2010

Locking the bus,

Telling the ASIC to write a

specified address,

Looking at the address to see

that it did not change,

Unlocking the bus, and

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

355

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Function
e)

Looking at the address to see

that it changed and the
correct data was written.

T114

ICP Clock Run Test

ICP ASIC, PLD,

ICP Oscillator

Verify that ICP ASIC timer register

changes.

T115

ICP Clock Compare

Test

CPU, Oscillator,
PLD, ICP ASIC,
ICP Oscillator

Check the ASIC clock against the

CPU clock to make sure they are
running at the same relative rates.
The ICP ASIC read timer
command is used to write the
internal timer to shared RAM
where it is read by the CPU.

T116

ICP ASIC Timer

Interrupt Test

CPU, PLD, ICP

ASIC

The ICP ASIC timer interrupt is

enabled and a timer started to
allow it to generate an interrupt on
IRQ2. The ASIC timer is disabled
after the test.

T118

ICP RAM Test

CPU, PLD, ICP

ASIC

A different set of pattern tests from

zero up and verify, and from -1
down and verify; for byte,
halfword, word.

Fieldbus Interface Module Diagnostics

T120

FPGA Load Test

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.10. FIM Self-Test Diagnostic Codes

Test Code

Target Device(s)

Failure Modes

Function
detected on each byte lane of the
upper RAM segment.

T125

Lower RAM Access

Test

FPGA, CPU, RAM

Verifies that lower RAM segment

can be accessed as 16-bit values.
Verifies that RAM can be written as
8-bit values and read as 16-bit
values and vice versa. Verifies that
aligned and misaligned halfwords
and words can be written and read.

T126

Upper RAM Access

Test

FPGA, CPU, RAM

Verifies that upper RAM segment

T127

RAM Unique
Address Test

FPGA, CPU, RAM

Verifies that each address can be

accessed uniquely. Runs with data
parity enabled and fatal.

T128

RAM Destructive
Pattern Test

FPGA, CPU, RAM

Checks address and data lines by

writing a non-repeating pattern over
the whole memory (upper and
lower segments), then verifying it.
Runs with data parity enabled and
fatal. Multiple patterns are used for
better coverage.

Missing
Application Image,
Incomplete load of
Application Image,
Bad flash memory

Checks for valid Application Image

stored in flash memory.

Pre-OS Diagnostics
T150

Application Image
Validation

T255

End of POST
Diagnostics

R400
July 2010

Confirms that self test is

successful and there is a valid
Application Image stored in Flash.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

357

8. Maintenance, Checkout, and Calibration

8.11. Checking Fieldbus Device Calibration

8.11 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 34 Typical Tune tab for fieldbus device's Transducer block.

358

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

Figure 35 Typical Other tab for fieldbus device's Transducer block.

8.12 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.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

359

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

Access the active device block through the Monitoring tab in Control Builder.
Launching Methods Manager
You can use one of the following actions to launch Methods Manager through Control
Builder, assuming the prerequisites have been met.
If You Select . . .
Device in Monitoring tab

Then, . . .
Click Field Devices->
Methods Manager

And,
Methods Manager dialog
provides a selection list
that includes all the blocks
associated with the device
and their available
methods with the method
description.

Interacting 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.
If Methods Manager Dialog . . .

360

Then, You Are Prompted

to . . .

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

If Methods Manager Dialog . . .

Includes list of available Methods.

Then, You Are Prompted

to . . .
Select the method to be
invoked and follow the
instructions in the Methods
Manager dialog.

ATTENTION
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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

361

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

If Methods Manager Dialog . . .

Then, You Are Prompted

to . . .

Shows action in progress.

Wait for action to complete

before continuing.

Shows selection from a list.

Select desired action by

selecting an option and
follow the instruction given
in the Methods Manager
dialog.

362

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

If Methods Manager Dialog . . .

Then, You Are Prompted

to . . .

Requests user acknowledgement.

Follow the instruction

given in the Methods
Manager dialog.

Requests user action.

Follow the instruction

given in the Methods
Manager dialog.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

363

8. Maintenance, Checkout, and Calibration

8.12. Using Fieldbus Methods Manager

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.

364

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

9. Experion PKS Host Registration

9.1

Overview
With R400, Experion PKS is a registered host with Foundation Fieldbus organization
(www.fieldbus.org). This registration process enables the users of Experion to benefit
from the additional features that are added as part of the registration.
The 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.

New features
The following new features are supported in EPKS R400.
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
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

R400
July 2010

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

365

9. Experion PKS Host Registration

9.1. Overview

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 function blocks

The capability to configure a distributed application

including PID closed loop control across multiple field
devices without host-based function blocks.

Function Block Linking and

Publication Scheduling

The capability to interconnect output parameters with

input parameters between any supported function
blocks.

Function Block Execution

Scheduling

The capability to schedule function blocks.

Foundation Alert Configuration and Handling

366

Process Alert Configuration

and Handling

The capability to configure the report VCR for process

alert notifications and display or record the process
alert notifications.

Process Alert Management

Configuration

The capability to configure the report VCR for process

alert notifications.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

9. Experion PKS Host Registration

9.1. Overview

Process Alert Handling and

Confirmation

The capability to confirm and display or record the

process alert notifications.

Device Alert Management

Configuration

The capability to configure the report VCR for device

alert notifications.

Device Alert Handling and

Confirmation

The capability to confirm and display or record the

device alert notifications.

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.
With R400, this includes the requirement to support
conditionals as restricted by the FF-901 specification.

DD v4 Methods execution

The capability to select and execute any DD method

against its associated block.

DD v4 Menus
(with R400)

The capability to display and navigate through menus

as defined in a DD.

DD v5 Visualizations,
Methods
(with R400)

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.

DD v5 Persistent data
(with R400)

The capability to persist data as utilized by version 5

DDs.

Capability File Support

The capability to import a Capability File for offline

configuration.

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 parameters 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.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

367

9. Experion PKS Host Registration

9.1. Overview

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 mode, Monitoring mode, and in
PDE.
For more information, refer to the Parameter Definition Editor Reference.
DD View tab
The DD View tab is a new tab that appears in the configuration form of the FF blocks. In
this tab, you can view parameter values, configure parameter values, visualize graph,
charts, images and execute methods in monitoring mode only. Hence, you can visualize
the the complete layout of the EDDL for the selected FF block. This tab appears only for
those blocks that support EDDL technology.

For more information, see Parameter Definition Editor Reference.

368

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

9. Experion PKS Host Registration

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

375

9. Experion PKS Host Registration

9.1. Overview

376

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.1 Fieldbus Technology
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.
Fieldbus Model
OSI Model

User Application

Fieldbus Message
Specification

Application Layer

Presentation Layer

Session Layer

Transport Layer

Network Layer

Data Link Layer

Physical Layer

Fieldbus Access
Sublayer

Communication
Stack

Physical Layer

Figure 36 OSI versus Fieldbus communication model.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

377

10. Appendix A
10.1. Fieldbus Technology

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.
REFERENCE - INTERNAL
Please refer to
Fieldbus network references 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

Physical

Defines the transmission medium for fieldbus

signals and the message conversion tasks
to/from the Communication Stack.
Based on the Manchester Biphase-L Encoding
technique, so a FOUNDATION Fieldbus (FF)
device interprets a positive transition in the
middle of a bit time as logical "0" and a
negative transition as logical "1".

Associated Terms
H1, 31.25 kbit/s
signal rate
H1 Link
H1 Segment
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 (DLL)

Defines how messages are transmitted on a

multi-drop network. It uses a deterministic
centralized bus scheduler called a Link Active
Scheduler (LAS) to manage access to the
fieldbus. It controls scheduled and unscheduled
communications on the fieldbus in a
publish/subscribe environment.
Identifies device types as Basic Device, Link
Master, or Bridge. A Link Master device type
can become a Link Active Scheduler (LAS) for
the network.

378

Compel Data (CD)

message
Pass Token (PT)
message
Time Distribution
(TD) message
Live List
Link Active Scheduler
(LAS)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.1. Fieldbus Technology

Layer

Functional Description

Fieldbus Access
Sublayer (FAS)

Defines the types of services used to pass

information to the Fieldbus Message
Specification layer. The types of services are
defined as Virtual Communication
Relationships (VCR).

Associated Terms
Virtual
Communication
Relationship (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 Message
Specification (FMS)

Defines how fieldbus devices exchange User

Application messages across the fieldbus
using a set of standard message formats. It
uses object descriptions that are stored in an
object dictionary (OD) to facilitate data
communication. The OD also includes
descriptions for standard data types such as
floating point, integer, Boolean, and bitstring.
A Virtual Field Device (VFD) mirrors local
device data described in the OD. A physical
device may have more than one VFD.
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.

Object Dictionary
(OD)
Virtual Field Device
(VFD)
Network
Management
Information Base
(NMIB)
System Management
Information Base
(SMIB)

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

379

10. Appendix A
10.1. Fieldbus Technology

Layer

Functional Description

User Application or
Function Block
Application Process
(FBAP)

Defines blocks to represent different types of

application functions. The three types of blocks
are the Resource block, the Function block,
and the Transducer block. See the illustration
that follows this table.
The Resource block is used to describe
characteristics of the fieldbus device such as
the device name, manufacturer, and serial
number. Each fieldbus device requires one
Resource block.

Associated Terms
Resource block
Function block
Transducer block
Link Objects
Trend Objects
Alert Objects
View Objects

The Function block is used to define the

specific characteristics of the process control
function. The Fieldbus Foundation provides a
set of pre-defined function blocks. A single
fieldbus device can include many Function
blocks to achieve the desired control
functionality. See the next section Standard
Function Blocks for more information.
The Transducer block is used to interface
Function blocks with local input/output devices.
They read sensors and command outputs, and
contain information such as calibration date
and sensor type. One Transducer block is
usually included for each input or output
Function block.

View 1 - Operation
Dynamic
View 2 - Operation
Static
View 3 - All Dynamic
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.

380

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Fieldbus Foundation
Defined Blocks

User Application

Resource
Block

Transducer
Block

Function
Block

Communication
Stack

Physical Layer

Fieldbus

Figure 37 User Application (or Function Block Application Process) based

on blocks.

10.2 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 (DS65), which includes all FOUNDATION Fieldbus inputs, outputs and some
contained parameters, a resulting NaN value passed outbound through the
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 FIM will not be written and usually results in retention of
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

381

10. Appendix A
10.2. Standard Function Blocks

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.

382

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Overview
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

Input

Analog Output

Output

Bias/Gain

Control

Control Selector

Control

Discrete Input

Input

Discrete Output

Output

Manual Loader

Control

Proportional/Derivative

Control

Proportional/Integral/Derivative

PID

Control

Ratio

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

383

10. Appendix A
10.2. Standard Function Blocks

Fieldbus

AI Block
PID Block

AO Block

Device 1
Device 2
Figure 38 Using Function Blocks in fieldbus devices to form a control
loop.
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

384

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Mode

Abbreviation

Operation Effect
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.

R400
July 2010

Local Override

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. .

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 remotecascade out parameter to support

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

385

10. Appendix A
10.2. Standard Function Blocks

Mode

Abbreviation

Operation Effect
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.

Analog Input block

Transducer

CHANNEL

Simulate
SIMULATE

Convert
L_TYPE
LOW_CUT
XD_SCALE
OUT_SCALE

OUT

Filter
PV_FTIME

Output

OUT

FIELD_VAL
Mode
SHED_OPT

Alarms
HI/LO

Figure 39 Functional schematic for Analog Input function block.

386

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Description

Function Notes

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.
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.

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]

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

387

10. Appendix A
10.2. Standard Function Blocks

Parameters

ACK_OPTION
ALARM_HYS
ALARM_SUM
ALERT_KEY
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CHANNEL
FIELD_VAL
GRANT_DENY
HI_ALM
HI_HI_ALM
HI_HI_LIM
HI_HI_PRI
HI_LIM
HI_PRI
IO_OPTS
L_TYPE
LO_ALM

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

LO_LIM
LO_LO_ALM
LO_LO_LIM
LO_LO_PRI
LO_PRI
LOW_CUT
MODE_BLK
OUT
OUT_SCALE
PV
PV_FTIME
SIMULATE
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
UPDATE_EVT
XD_SCALE

Analog Output block

BKCAL_OUT
CAS_IN

OUT
RCAS_OUT

RCAS_IN

Transducer

BKCAL_OUT
RCAS_OUT
CAS_IN
RCAS_IN

Setpoint
SP_RATE_DN
SP_RATE_UP
SP_HI_LIM
SP_LO_LIM

SP
Mode
SHED_OPT

388

Output

Out Convert
PV_SCALE
XD_SCALE

PV Convert
XD_SCALE
PV_SCALE

PV
Fault State
FSTATE_TIME
FSTATE_VAL

OUT

Simulate
SIMULATE

READBACK

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

CHANNEL

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Figure 40 Functional schematic for Analog Output function block.

Description

Function Notes

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.
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

R400
July 2010

Temp = (SP - EU@0%) / (EU@100% - EU@0%)

[PV_SCALE]

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

389

10. Appendix A
10.2. Standard Function Blocks

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]
Parameters

ALERT_KEY
BKCAL_OUT
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CAS_IN
CHANNEL
FSTATE_TIME
FSTATE_VAL
GRANT_DENY
IO_OPTS
MODE_BLK
OUT
PV
PV_SCALE
RCAS_IN

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

RCAS_OUT
READBACK
SHED_OPT
SIMULATE
SP
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP_RATE_UP
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
UPDATE_EVT
XD_SCALE

Bias/Gain block

390

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

IN_1
BKCAL_IN
BKCAL_OUT

CAS_IN
RCAS_IN
TRK_IN_C

OUT
RCAS_OUT

TRK_VAL

BKCAL_IN

BKCAL_OUT
RCAS_OUT
CAS_IN
RCAS_IN

Setpoint
SP_RATE_DN
SP_RATE_UP
SP_HI_LIM
SP_LO_LIM

Bias & Gain

GAIN

Output
OUT_HI_LIM
OUT_LO_LIM
BAL_TIME

OUT

IN_1
Mode
SHED_OPT

Output Track
TRK_SCALE

TRK_IN_D
TRK_VAL

Figure 41 Functional schematic for Bias/Gain function block.

Description

Function Notes

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.
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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

391

10. Appendix A
10.2. Standard Function Blocks

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.

392

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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

Parameters

ALERT_KEY
BAL_TIME
BKCAL_IN
BKCAL_OUT
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CAS_IN
CONTROL_OPTS
GAIN
GRANT_DENY
IN_1
MODE_BLK
OUT
OUT_HI_LIM
OUT_LO_LIM
OUT_SCALE

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

RCAS_IN
RCAS_OUT
SHED_OPT
SP
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP_RATE_UP
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
TRK_IN_D
TRK_SCALE
TRK_VAL
UPDATE_EVT

Control Selector block

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

393

10. Appendix A
10.2. Standard Function Blocks

SEL_1
SEL_2
SEL_3
BKCAL_IN

OUT
BKCAL_SEL_1

BKCAL_SEL_2
BKCAL_SEL_3

BKCAL_IN

SEL_1

Selection
SEL_TYPE

SEL_2

Output
OUT_HI_LIM
OUT_LO_LIM

OUT

SEL_3
Back Calc
Mode

BKCAL_SEL_1
BKCAL_SEL_2
BKCAL_SEL_3

Figure 42 Functional schematic for Control Selector function block.

Description

Function Notes

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.
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

394

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

395

10. Appendix A
10.2. Standard Function Blocks

Parameters

ALERT_KEY
BKCAL_IN
BKCAL_SEL_1
BKCAL_SEL_2
BKCAL_SEL_3
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
GRANT_DENY
MODE_BLK
OUT
OUT_HI_LIM

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

OUT_LO_LIM
OUT_SCALE
SEL_1
SEL_2
SEL_3
SEL_TYPE
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
UPDATE_EVT

Discrete Input block

Transducer

CHANNEL

Simulate
SIMULATE_D

OUT

Optional
Invert

Filter
PV_FTIME

PV_D
Output

OUT_D

FIELD_VAL_D

Mode
SHED_OPT

Alarms
DISC

Figure 43 Functional schematic for Discrete Input function block.

Description
396

The Discrete Input function block takes the discrete input

data from a selected Transducer block channel and

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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.

Parameters

ACK_OPTION
ALARM_SUM
ALERT_KEY
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CHANNEL
DISC_ALM
DISC_LIM
DISC_PRI
FIELD_VAL_D
GRANT_DENY
IO_OPTS

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

MODE_BLK
OUT_D
OUT_STATE
PV_D
PV_FTIME
SIMULATE_D
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
UPDATE_EVT
XD_STATE

Discrete Output block

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

397

10. Appendix A
10.2. Standard Function Blocks

BKCAL_OUT_D
CAS_IN_D

OUT_D
RCAS_OUT_D

RCAS_IN_D

Transducer

BKCAL_OUT_D
RCAS_OUT_D
CAS_IN_D

Setpoint

Optional
Invert

Output

OUT_D

RCAS_IN_D
SP_D
Mode
SHED_OPT

Optional
Invert

PV_D
Fault State
FSTATE_TIME
FSTATE_VAL_D

Simulate
SIMULATE_D

CHANNEL

READBACK_D

Figure 44 Functional schematic for Discrete Output function block.

Description

398

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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 subfunction.
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.

R400
July 2010

Parameters

ALERT_KEY
BKCAL_OUT_D
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CAS_IN_D
CHANNEL
FSTATE_TIME
FSTATE_VAL_D
GRANT_DENY
IO_OPTS
MODE_BLK
OUT_D
PV_D

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

PV_STATE
RCAS_IN_D
RCAS_OUT_D
READBACK_D
SHED_OPT
SIMULATE_D
SP_D
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
UPDATE_EVT
XD_STATE

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

399

10. Appendix A
10.2. Standard Function Blocks

Manual Loader block

IN
BKCAL_IN

ROUT_IN

OUT
ROUT_OUT

TRK_IN_D
TRK_VAL

BKCAL_IN
ROUT_OUT

ROUT_IN
IN

Output
OUT_HI_LIM
OUT_LO_LIM

Filter
PV_FTIME
PV

OUT

Alarm
HI/LO
Mode
SHED_OPT

Output Track
TRK_SCALE

TRK_IN_D
TRK_VAL

Figure 45 Functional schematic for Manual Loader function block.

Description

400

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

401

10. Appendix A
10.2. Standard Function Blocks

Parameters

ACK_OPTION
ALARM_HYS
ALARM_SUM
ALERT_KEY
BKCAL_IN
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CONTROL_OPTS
GRANT_DENY
HI_ALM
HI_HI_ALM
HI_HI_LIM
HI_HI_PRI
HI_LIM
HI_PRI
IN
LO_ALM
LO_LIM
LO_LO_ALM
LO_LO_LIM
LO_PRI

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

LO-LO_PRI
MODE_BLK
OUT
OUT_HI_LIM
OUT_LO_LIM
OUT_SCALE
PV
PV_FTIME
PV_SCALE
ROUT_IN
ROUT_OUT
SHED_OPT
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
TRK_IN_D
TRK_SCALE
TRK_VAL
UPDATE_EVT

Proportional/Derivative block

402

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

IN
BKCAL_IN
CAS_IN
RCAS_IN

BKCAL_OUT

OUT
RCAS_OUT

ROUT_IN
TRK_IN_D
TRK_VAL
FF_VAL

ROUT_OUT

BKCAL_OUT
RCAS_OUT
Setpoint
SP_RATE_DN
SP_RATE_UP
SP_HI_LIM
SP_LO_LIM

CAS_IN
RCAS_IN

SP
Filter
PV_FTIME

Mode
SHED_OPT

Bypass
BYPASS
Control
GAIN
BIAS
BAL_TIME
RATE

FF_VAL

BKCAL_IN
ROUT_IN

Feed Forward
FF_SCALE
FF_GAIN

Output
OUT_HI_LIM
OUT_LO_LIM

ROUT_OUT

OUT

Status
BKCAL_HYS

PV
Alarm
HI/LO
DEV

Output Track
TRK_SCALE

TRK_IN_D
TRK_VAL

Figure 46 Functional schematic for Proportional/Derivative function block.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

403

10. Appendix A
10.2. Standard Function Blocks

Description

Function Notes

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
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.

404

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Use the Balance Ramp CONTROL_OPTS to maintain

Downloaded from www.Manualslib.com manuals search engine

407

10. Appendix A
10.2. Standard Function Blocks

IN
BKCAL_IN
CAS_IN
RCAS_IN

BKCAL_OUT

PID

OUT
RCAS_OUT

ROUT_IN
TRK_IN_D
TRK_VAL
FF_VAL

ROUT_OUT

BKCAL_OUT
RCAS_OUT
CAS_IN
RCAS_IN

Setpoint
SP_RATE_DN
SP_RATE_UP
SP_HI_LIM
SP_LO_LIM
SP

Filter
PV_FTIME
Mode
SHED_OPT

Bypass
BYPASS
Control
GAIN
RESET
BAL_TIME
RATE

FF_VAL

BKCAL_IN
ROUT_IN

Feed Forward
FF_SCALE
FF_GAIN

Output
OUT_HI_LIM
OUT_LO_LIM

ROUT_OUT

OUT

Status
BKCAL_HYS

PV
Alarm
HI/LO
DEV

Output Track
TRK_SCALE

TRK_IN_D
TRK_VAL

Figure 47 Functional schematic for Proportional/Integral/Derivative

function block.

408

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Description

Function Notes

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.
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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

409

10. Appendix A
10.2. Standard Function Blocks

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.
410

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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

R400
July 2010

ACK_OPTION
ALARM_HYS
ALARM_SUM
ALERT_KEY
BAL_TIME
BKCAL_HYS
BKCAL_IN
BKCAL_OUT
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
BYPASS
CAS_IN
CONTROL_OPTS
DV_HI_ALM
DV_HI_LIM
DV_HI_PRI
DV_LO_ALM
DV_LO_LIM
DV_LO_PRI
FF_GAIN
FF_SCALE
FF_VAL
GAIN
GRANT_DENY
HI_ALM
HI_HI_ALM
HI_HI_LIM
HI_HI_PRI
HI_LIM
HI_PRI
IN
LO_ALM
LO_LIM

LO_LO_ALM
LO_LO_LIM
LO_LO_PRI
LO_PRI
MODE_BLK
OUT
OUT_HI_LIM
OUT_LO_LIM
OUT_SCALE
PV
PV_FTIME
PV_SCALE
RATE
RCAS_IN
RCAS_OUT
RESET
ROUT_IN
ROUT_OUT
SHED_OPT
SP
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP_RATE_UP
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
TRK_IN_D
TRK_SCALE
TRK_VAL
UPDATE_EVT

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

411

10. Appendix A
10.2. Standard Function Blocks

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

Ratio block
IN
IN_1
BKCAL_IN

BKCAL_OUT

CAS_IN
RCAS_IN

OUT
RCAS_OUT

TRK_IN_D
TRK_VAL

BKCAL_OUT
RCAS_OUT
CAS_IN
RCAS_IN

Setpoint
SP_RATE_DN
SP_RATE_UP
SP_HI_LIM
SP_LO_LIM

IN_1

Filter
RA_FTIME

Filter
PV_FTIME
Mode
SHED_OPT

BKCAL_IN
Ratio
GAIN

Calc PV
GAIN

Output
OUT_HI_LIM
OUT_LO_LIM
BAL_TIME

OUT

Alarm
HI/LO
DEV

Output Track
TRK_SCALE

TRK_IN_D
TRK_VAL

Figure 48 Functional schematic for Ratio function block.

412

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

Description

Function Notes

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.
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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

413

10. Appendix A
10.2. Standard Function Blocks

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.

414

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.2. Standard Function Blocks

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

R400
July 2010

Parameters

ACK_OPTION
ALARM_HYS
ALARM_SUM
ALERT_KEY
BAL_TIME
BKCAL_IN
BKCAL_OUT
BLOCK_ALM
BLOCK_ERR
BLOCK_ERR.DISABLED
CAS_IN
CONTROL_OPTS
DV_HI_ALM
DV_HI_LIM
DV_HI_PRI
DV_LO_ALM
DV_LO_LIM
DV_LO_PRI
GAIN
GRANT_DENY
HI_ALM
HI_HI_ALM
HI_HI_LIM
HI_HI_PRI
HI_LIM
HI_PRI
IN
IN_1
LO_ALM
LO_LIM

Reference

Refer to Standard Function Block Parameters in Appendix

B for definitions of each parameter.

LO_LO_ALM
LO_LO_LIM
LO_LO_PRI
LO_PRI
MODE_BLK
OUT
OUT_HI_LIM
OUT_LO_LIM
OUT_SCALE
PV
PV_FTIME
PV_SCALE
RA_FTIME
RCAS_IN
RCAS_OUT
SHED_OPT
SP
SP_HI_LIM
SP_LO_LIM
SP_RATE_DN
SP_RATE_UP
ST_REV
STATUS_OPTS
STRATEGY
TAG_DESC
TRK_IN_D
TRK_SCALE
TRK_VAL
UPDATE_EVT

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

415

10. Appendix A
10.3. Device Descriptions and Block Parameters

10.3 Device Descriptions and Block Parameters

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.
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.
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.

416

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

10. Appendix A
10.3. Device Descriptions and Block Parameters

Level 1:
Universal
Parameters

Defined by
Fieldbus Foundation
Specification
Level 2:
Function
Block
Parameters

RESOURCE

Level 3:
Transducer
Block
Parameters

PID

TEMP

FLOW

Level 4:
Manufacturer
Specific
Parameters

Defined by
Manufacturer

Resource
Block

Transducer
Block

Function
Block

Figure 49 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.
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.
Block parameter definitions

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

417

10. Appendix A
10.4. Fieldbus Foundation Documents

REFERENCE - INTERNAL
Refer to Standard Function Block Parameters in Appendix B for definitions of
block parameters for reference.

10.4 Fieldbus Foundation Documents

Reference Data
Document Number

418

Description

AG-140

31.25 kbit/s Voltage Mode, Wire Medium Wiring and

Installation Application Guide

AG-163

31.25 kbit/s Intrinsically Safe Systems Application Guide

AG-180

Fieldbus Installation and Planning Guide

FD-043

Technical Overview

Final Specifications

Please contact the Fieldbus Foundation for information

about availability of current specifications.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1 Standard Function Block Parameters
ACK_OPTION
Classification

Simple Variable

Description

Selects whether alarms associated with the block will be

automatically acknowledged.

FF Data Type

Bit String

Range

1: Unacknowledge

Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0.5 percent

ALARM_SUM
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

419

11. Appendix B
11.1. Standard Function Block Parameters

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

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

ALERT_KEY

420

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

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

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.

BIAS

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

421

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0.5 percent

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

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

422

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

R400
July 2010

Usage

O/Back Calculation Output

Length

Valid Views

VIEW_3

Storage

Dynamic

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

423

11. Appendix B
11.1. Standard Function Block Parameters

Remarks

The data type consists of the value and status of discrete

value parameters. It uses the following two elements.
1 Status
2 Value

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

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

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
424

O/Back Calculation Output

Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Length

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

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

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

BLOCK_ALM

R400
July 2010

Classification

Record

Description

The block alarm is used for all configuration, hardware,

connection failure, or system problems in the block. The

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

425

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

426

Usage

C/Block Error

Length

Valid Views

VIEW_1, VIEW_3

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Storage

Dynamic

Remarks

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 blocks 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

427

11. Appendix B
11.1. Standard Function Block Parameters

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.

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

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is 0.

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

CAS_IN

Range

428

Usage

I/Cascade Input

Length

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

CHANNEL

R400
July 2010

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

429

11. Appendix B
11.1. Standard Function Block Parameters

Range

1 to Manufacturer Limit

Usage

C/Channel

Length

Valid Views

VIEW_4

Storage

Static

Remarks

The initial value is 0.

CLR_FSTATE
Classification

Simple Variable

Description

Serves as a switch to reset/clear the device fault state state

after the fault condition is cleared.

FF Data Type

Unsigned 8

Range

1: Off
2: Clear

Usage

C/Contained

Length

Valid Views
Storage

Dynamic

Remarks

The operator can control PROGRAM or LOCAL access to

these values.

CONFIRM_TIME

430

Classification

Simple Variable

Description

Defines the time between retries of alert reports.

FF Data Type

Unsigned 32

Range

Positive
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Remarks

The initial value is 32000 milliseconds.

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

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 2 CONTROL_OPTS Bit Selections

Bit

Meaning

Function Block
BG

PID

Bypass Enable (LSB)

SP-PV Track in Man

SP-PV Track in ROut

SP-PV Track in LO or IMan

SP Track retained target

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

431

11. Appendix B
11.1. Standard Function Block Parameters

Bit

Function Block

Meaning
BG

PD
X

PID

Direct Acting

Balance Ramp

Track Enable

Track in Manual

Use PV for BKCAL_OUT

Act on IR

Use percent for IN_1

Obey SP limits if Cas or RCas

No OUT limits in Manual

Reserved

X
X

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

Valid Views

VIEW_2

Storage

Static

Remarks

Changing this parameter may be fatal to communication.

CYCLE_TYPE
432

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

DEV_TYPE

R400
July 2010

Classification

Simple Variable

Description

Identifies the manufacturer's model number associated with

the resource. An interface device uses it to locate the DD

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

433

11. Appendix B
11.1. Standard Function Block Parameters

file for the resource.

FF Data Type

Unsigned 16

Range

Set by manufacturer

Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

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

Valid Views
Storage

Static

Remarks

Read Only

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

DD_REV

434

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Range
Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

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

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

DISC_LIM

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

435

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

Valid Views

VIEW_4

Storage

Static

Remarks

DV_HI_ALM
Classification

Record

Description

Identifies the status and time stamp associated with the

high deviation alarm.

FF Data Type

DS-71

Range
436

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Usage

C/Alarm

Length

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is + infinity

DV_HI_PRI
Classification

R400
July 2010

Simple Variable

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

437

11. Appendix B
11.1. Standard Function Block Parameters

Description

Defines priority of the high deviation alarm.

FF Data Type

Unsigned 8

Range

0 to 63

Usage

C/Alert Priority

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

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

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

438

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is - infinity

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

FAULT_STATE

R400
July 2010

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

439

11. Appendix B
11.1. Standard Function Block Parameters

blocks will perform their FSTATE action

FF Data Type

Unsigned 8

Range

1: Clear
2: Active

Usage

C/Contained

Length

Valid Views

VIEW_1, VIEW_3

Storage

Non-Volatile

Remarks

Read Only

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

FEATURE_SEL
Classification

Simple Variable

Description

Bit string that identifies the selected resource block options.

FF Data Type

Bit String

Range

440

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Remarks

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

Valid Views

VIEW_4

Storage

Static

Remarks

FF_SCALE

R400
July 2010

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

Valid Views

VIEW_4

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

441

11. Appendix B
11.1. Standard Function Block Parameters

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

FF_VAL
Classification

Record

Description

Represents the feed-forward value.

FF Data Type

DS-65

Range
Usage

I/Input

Length

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

FIELD_VAL
Classification

442

Record

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

Valid Views

VIEW_1, VIEW_3

Storage

Dynamic

Remarks

Read Only
The data type consists of the value and status of discrete

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

443

11. Appendix B
11.1. Standard Function Block Parameters

value parameters. It uses the following two elements.

1 Status
2 Value

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

Valid Views

VIEW_2

Storage

Dynamic

Remarks

Read Only

FREE_TIME

444

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

Valid Views

VIEW_1, VIEW_3

Storage

Dynamic

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Remarks

Read Only

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

Valid Views

VIEW_4

Storage

Static

Remarks
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

445

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

GAIN
Classification

Simple Variable

Description

Represents dimensionless gain used by several different

algorithms.

FF Data Type

Float

Range
Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

GRANT_DENY

446

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

HI_ALM

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

447

11. Appendix B
11.1. Standard Function Block Parameters

Classification

Record

Description

Identifies the status and time stamp associated with the

high alarm.

FF Data Type

DS-71

Range
Usage

C/Alarm

Length

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

HI_HI_ALM
Classification

Record

Description

Identifies the status and time stamp associated with the

high high alarm.

FF Data Type

DS-71

Range
Usage

C/Alarm

Length

Valid Views
Storage
448

Dynamic

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is + infinity

HI_HI_PRI

R400
July 2010

Classification

Simple Variable

Description

Defines priority of the high high alarm.

FF Data Type

Unsigned 8

Range

0 to 63

Usage

C/Alert Priority

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

449

11. Appendix B
11.1. Standard Function Block Parameters

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is + infinity

Classification

Simple Variable

Description

Defines priority of the high alarm.

FF Data Type

Unsigned 8

Range

0 to 63

Usage

C/Alert Priority

Length

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is 0

HI_LIM

HI_PRI

450

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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 3 IO_OPTS Bit Selections

Bit

Meaning

Function Block
AI

Invert

SP-PV Track in Man

Reserved

DO
X

SP-PV Track in LO or IMan

SP Track retained target

Increase to close

Fault state to value

Use Fault state value to restart

Target to Man if fault state activated

Use PV for BKCAL_OUT

Low Cutoff

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

451

11. Appendix B
11.1. Standard Function Block Parameters

Bit

Function Block

Meaning
AI

Reserved

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

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

IN_1

452

Classification

Record

Description

Represents the auxiliary input value to the block. It is used

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

for values other than the PV.

FF Data Type

DS-65

Range
Usage

I/Input

Length

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

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

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is MAX_NOTIFY

Classification

Simple Variable

L_TYPE

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

453

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

Valid Views
Storage

454

Dynamic

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is - Infinity

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

R400
July 2010

C/Alarm

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

455

11. Appendix B
11.1. Standard Function Block Parameters

Length

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

Initial value is - Infinity

LO_LO_PRI

456

Classification

Simple Variable

Description

Represents the priority of the low low alarm.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

FF Data Type

Unsigned 8

Range

0 to 63

Usage

C/Alert Priority

Length

Valid Views

VIEW_4

Storage

Static

Remarks

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

Valid Views

VIEW_4

Storage

Static

Remarks

LOW_CUT

R400
July 2010

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

457

11. Appendix B
11.1. Standard Function Block Parameters

Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

This function may be used to eliminate noise near zero

from a flow sensor.

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

MAX_NOTIFY

458

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

MIN_CYCLE_T

R400
July 2010

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

Valid Views

VIEW_4

Storage

Static

Remarks

Read Only

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

459

11. Appendix B
11.1. Standard Function Block Parameters

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

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

NV_CYCLE_T

460

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Range

Positive

Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Remarks

Ready Only

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.

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

OUT

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

461

11. Appendix B
11.1. Standard Function Block Parameters

Usage

O/Primary Output

Length

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

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

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

462

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is 100.

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

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is 0.

OUT_SCALE

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

463

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

464

Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Remarks

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

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

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
R400
July 2010

C/Process Variable
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

465

11. Appendix B
11.1. Standard Function Block Parameters

Length

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

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
466

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Usage

C/Scaling

Length

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

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

Valid Views

VIEW_2

Storage

Static

Remarks

RA_FTIME

R400
July 2010

Classification

Simple Variable

Description

Defines the time constant of a single exponential filter for

the value to be ratioed in seconds.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

467

11. Appendix B
11.1. Standard Function Block Parameters

FF Data Type

Float

Range

Positive

Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

RATE
Classification

Simple Variable

Description

Defines the derivative time constant in seconds.

FF Data Type

Float

Range

Positive

Usage

C/Contained

Length

Valid Views

VIEW_4

Storage

Static

Remarks

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

468

Usage

C/Remote-Cascade In

Length

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

RCAS_OUT

R400
July 2010

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

469

11. Appendix B
11.1. Standard Function Block Parameters

Range
Usage

C/Remote-Cascade Out

Length

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

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

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

470

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

R400
July 2010

Usage

C/Contained

Length

Valid Views

VIEW_1, VIEW_3

Storage

Dynamic

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

471

11. Appendix B
11.1. Standard Function Block Parameters

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

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

472

FF Data Type

Unsigned 8

Range

1: Run
Experion PKS Series A Fieldbus Interface Module User's Guide
Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

2: Restart Resource
3: Restart with Defaults
4: Restart Processor
Usage

C/Contained

Length

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.

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

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

473

11. Appendix B
11.1. Standard Function Block Parameters

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

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

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

474

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

6: Failure
Usage

C/Resource State

Length

Valid Views

VIEW_1, VIEW_3

Storage

Dynamic

Remarks

Read Only

Classification

Record

Description

Represents first input value to the selector.

FF Data Type

DS-65

SEL_1

Range
Usage

I/Cascade Input

Length

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

SEL_2

R400
July 2010

Classification

Record

Description

Represents second input value to the selector.

FF Data Type

DS-65

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

475

11. Appendix B
11.1. Standard Function Block Parameters

Range
Usage

I/Cascade Input

Length

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

SEL_3
Classification

Record

Description

Represents third input value to the selector.

FF Data Type

DS-65

Range
Usage

I/Cascade Input

Length

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

476

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

Valid Views

R400
July 2010

Storage

Dynamic

Remarks

The operator can control PROGRAM or LOCAL access to

this value.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

477

11. Appendix B
11.1. Standard Function Block Parameters

SHED_OPT
Classification
Description

Simple Variable
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

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.

SHED_RCAS
Classification
478

Simple Variable

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Description

Defines timeout in milliseconds for computer writes to

function block RCas locations.

FF Data Type

Unsigned 32

Range

Positive

Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Remarks

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

Valid Views

VIEW_2

Storage

Static

Remarks

SIMULATE

R400
July 2010

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

479

11. Appendix B
11.1. Standard Function Block Parameters

FF Data Type

DS-82

Range
Usage

C/Simulate

Length

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

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

Valid Views

480

Storage

Dynamic

Remarks

The data type consists of a simulate and transducer

discrete value and status and a simulate enable/disable

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

discrete. It uses the following five elements.

1: Simulate Status
2:Simulate Value
3: Transducer Status
4: Transducer Value
5: Simulate Enable/Disable

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

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

481

11. Appendix B
11.1. Standard Function Block Parameters

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

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

SP_HI_LIM

482

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is 100 percent

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

Valid Views

VIEW_2

Storage

Static

Remarks

Initial value is zero (0)

SP_RATE_DN

R400
July 2010

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

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

483

11. Appendix B
11.1. Standard Function Block Parameters

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

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.

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

ST_REV

Range
Usage

C/Static Revision

Length

Valid Views

VIEW_1, VIEW_2, VIEW_3, VIEW_4

Storage

Static

Remarks

Read Only

STATUS_OPTS
Classification
484

Simple Variable

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Description

Defines user-selectable options for the block processing of

status.

FF Data Type

Bit String

Range
Usage

C/Contained

Length

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 4 STATUS_OPTS Bit Selections

Bit

Meaning

Function Block
AI

IFS if BAD IN

IFS if BAD CAS_IN

Use Uncertain as
Good

Propagate Failure
Forward

Propagate Failure
Backward

Target to Manual if
BAD IN

Uncertain if Limited

BAD if Limited

Uncertain if Man
Mode

Do not select if not

R400
July 2010

PID

X
X

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

X
X

X
485

11. Appendix B
11.1. Standard Function Block Parameters

Bit

Function Block

Meaning
AI

PID

Auto mode
10

Do not select if not

Cas mode

Reserved

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

Valid Views

VIEW_4

Storage

Static

Remarks

TAG_DESC

486

Classification

Simple Variable

Description

Serves as user defined description of the block.

FF Data Type

Octet String

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Range
Usage

C/Tag Description

Length

Valid Views
Storage

Static

Remarks

Initial value is 32 space characters

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)

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

487

11. Appendix B
11.1. Standard Function Block Parameters

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)

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

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

TRK_SCALE

488

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

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

Range
Usage

C/Scaling

Length

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

TRK_VAL
Classification

Record

Description

Represents the input value for external tracking.

FF Data Type

DS-65

Range
Usage

I/Input

Length

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

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

489

11. Appendix B
11.1. Standard Function Block Parameters

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

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
490

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

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

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

Valid Views

VIEW_2

Storage

Static

Remarks

The operator can control PROGRAM and LOCAL access to

this value.

WRITE_PRI

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

491

11. Appendix B
11.1. Standard Function Block Parameters

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

Valid Views

VIEW_4

Storage

Static

Remarks

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

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

492

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

11. Appendix B
11.1. Standard Function Block Parameters

3 Units Index
4 Decimal Point

XD_STATE
Classification

Simple Variable

Description

Represents index to the text describing the states of a

discrete for the value obtained from the Transducer.

FF Data Type

Unsigned 16

Range
Usage

C/Contained

Length

Valid Views

VIEW_2

Storage

Static

Remarks

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

493

11. Appendix B
11.1. Standard Function Block Parameters

494

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.1 Fieldbus Status Display Indications
Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

BAD

Non-Specific

No Limits

Bad

BAD

Non-Specific

Low Limit

Bad,LowLimit

BAD

Non-Specific

High Limit

Bad,HiLimit

BAD

Non-Specific

Constant

Bad,Constant

BAD

Configuration
Error

No Limits

Bad,Config

BAD

Configuration
Error

Low Limit

Bad,Config,L

BAD

Configuration
Error

High Limit

Bad,Config,H

BAD

Configuration
Error

Constant

Bad,Config,C

BAD

Not Connected

No Limits

Bad,NotCon

BAD

Not Connected

Low Limit

Bad,NotCon,L

BAD

Not Connected

High Limit

Bad,NotCon,H

BAD

Not Connected

Constant

Bad, NotCon,C

BAD

Device Failure

No Limits

Bad,DevFail

BAD

Device Failure

Low Limit

Bad,DevFail,L

BAD

Device Failure

High Limit

Bad,DevFail,H

BAD

Device Failure

Constant

Bad,DevFail,C

BAD

Sensor Failure

No Limits

Bad,SensFail

BAD

Sensor Failure

Low Limit

Bad,SnFail,L

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

495

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

BAD

Sensor Failure

High Limit

Bad,SnFail,H

BAD

Sensor Failure

Constant

Bad,SnFail,C

BAD

No Comm,
Last Usable

No Limits

Bad,LUValue

BAD

No Comm,
Last Usable

Low Limit

Bad,LUV,L

BAD

No Comm,
Last Usable

High Limit

Bad,LUV,H

BAD

No Comm,
Last Usable

Constant

Bad,LUV,C

BAD

No Comm, No
Last Usable

No Limits

Bad,NoComm

BAD

No Comm, No
Last Usable

Low Limit

Bad,NoComm,L

BAD

No Comm, No
Last Usable

High Limit

Bad,NoComm,H

BAD

No Comm, No
Last Usable

Constant

Bad,NoComm,C

BAD

Out-Of-Service

No Limit

Bad,OutSvc

BAD

Out-Of-Service

Low Limit

Bad,OutSvc,L

BAD

Out-Of-Service

High Limit

Bad,OutSvc,H

BAD

Out-Of Service

Constant

Bad,OutSvc,C

UNCERTAIN

Non-Specific

No Limits

Uncertain

UNCERTAIN

Non-Specific

Low Limit

Uncertain,L

UNCERTAIN

Non-Specific

High Limit

Uncertain,H

UNCERTAIN

Non-Specific

Constant

Uncertain,C

UNCERTAIN

Last Usable

No Limits

Unc,LastOK

496

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

UNCERTAIN

Last Usable

Low Limit

Unc,LastOK,L

UNCERTAIN

Last Usable

High Limit

Unc,LastOK,H

UNCERTAIN

Last Usable

Constant

Unc,LastOK,C

UNCERTAIN

Substitute

No Limits

Unc,Subst

UNCERTAIN

Substitute

Low Limit

Unc,Subst,L

UNCERTAIN

Substitute

High Limit

Unc,Subst,H

UNCERTAIN

Substitute

Constant

Unc,Subst,C

UNCERTAIN

Initial Value

No Limits

Unc,Initial

UNCERTAIN

Initial Value

Low Limits

Unc,Init,L

UNCERTAIN

Initial Value

High Limits

Unc,Init,H

UNCERTAIN

Initial Value

Constant

Unc,Init,C

UNCERTAIN

Sensor
Conversion Not
Accurate

No Limit

Unc,NotAcc

UNCERTAIN

Sensor
Conversion Not
Accurate

Low Limit

Unc,NotAcc,L

UNCERTAIN

Sensor
Conversion Not
Accurate

High Limit

Unc,NotAcc,H

UNCERTAIN

Sensor
Conversion Not
Accurate

Constant

Unc,NotAcc,C

UNCERTAIN

Engineering
Unit Range
Violation

No Limits

Unc,Range

UNCERTAIN

Engineering
Unit Range
Violation

Low Limit

Unc,Range,L

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

497

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

UNCERTAIN

Engineering
Unit Range
Violation

High Limit

Unc,Range,H

UNCERTAIN

Engineering
Unit Range
Violation

Constant

Unc,Range,C

UNCERTAIN

Sub-Normal

No Limits

Unc,SubNorm

UNCERTAIN

Sub-Normal

Low Limit

Unc,SubNrm,L

UNCERTAIN

Sub-Normal

High Limit

Unc,SubNrm,H

UNCERTAIN

Sub-Normal

Constant

Unc,SubNrm,C

GOOD (NonCascade)

Non-Specific

No Limits

<blank>

GOOD (NonCascade)

Non-Specific

Low Limit

GOOD (NonCascade)

Non-Specific

High Limit

GOOD (NonCascade)

Non-Specific

Constant

GOOD (NonCascade)

Active Block
Alarm

No Limits

Alarm-Block

GOOD (NonCascade)

Active Block
Alarm

Low Limit

Alarm-Blck,L

GOOD (NonCascade)

Active Block
Alarm

High Limit

Alarm-Blck,H

GOOD (NonCascade)

Active Block
Alarm

Constant

Alarm-Blck,C

GOOD (NonCascade)

Active Advisory
Alarm

No Limits

Alarm-Advis

GOOD (NonCascade)

Active Advisory
Alarm

Low Limit

Alarm-Advis,L

498

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

GOOD (NonCascade)

Active Advisory
Alarm

High Limit

Alarm-Advis,H

GOOD (NonCascade)

Active Advisory
Alarm

Constant

Alarm-Advis,C

GOOD (NonCascade)

Active Critical
Alarm

No Limits

Alarm-Crit

GOOD (NonCascade)

Active Critical
Alarm

Low Limit

Alarm-Crit,L

GOOD (NonCascade)

Active Critical
Alarm

High Limit

Alarm-Crit,H

GOOD (NonCascade)

Active Critical
Alarm

Constant

Alarm-Crit,C

GOOD (NonCascade)

Unacknowledged Block
Alarm

No Limits

Alm-U-Block

GOOD (NonCascade)

Unacknowledged Block
Alarm

Low Limit

Alm-U-Blck,L

GOOD (NonCascade)

Unacknowledged Block
Alarm

High Limit

Alm-U-Blck,H

GOOD (NonCascade)

Unacknowledged Block
Alarm

Constant

Alm-U-Blck,C

GOOD (NonCascade)

Unacknowledged
Advisory Alarm

No Limits

Alm-U-Advis

GOOD (NonCascade)

Unacknowledged
Advisory Alarm

Low Limit

Alm-U-Advs,L

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

499

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

GOOD (NonCascade)

Unacknowledged
Advisory Alarm

High Limit

Alm-U-Advs,H

GOOD (NonCascade)

Unacknowledged
Advisory Alarm

Constant

Alm-U-Advs,C

GOOD (NonCascade)

Unacknowledged Critical
Alarm

No Limits

Alm-U-Crit

GOOD (NonCascade)

Unacknowledged Critical
Alarm

Low Limit

Alm-U-Crit,L

GOOD (NonCascade)

Unacknowledged Critical
Alarm

High Limit

Alm-U-Crit,H

GOOD (NonCascade)

Unacknowledged Critical
Alarm

Constant

Alm-U-Crit,C

GOOD
(Cascade)

Non-Specific

No Limits

<blank>

GOOD
(Cascade)

Non-Specific

Low Limit

GOOD
(Cascade)

Non-Specific

High Limit

GOOD
(Cascade)

Non-Specific

Constant

GOOD
(Cascade)

Acknowledge
Initialization
(IA)

No Limit

InitAck

GOOD
(Cascade)

Acknowledge
Initialization
(IA)

Low Limit

InitAck,L

500

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.1. Fieldbus Status Display Indications

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

GOOD
(Cascade)

Acknowledge
Initialization
(IA)

High Limit

InitAck,H

GOOD
(Cascade)

Acknowledge
Initialization
(IA)

Constant

InitAck,C

GOOD
(Cascade)

Request
Initialization
(IR)

No Limits

ReqInit

GOOD
(Cascade)

Request
Initialization
(IR)

Low Limit

ReqInit,L

GOOD
(Cascade)

Request
Initialization
(IR)

High Limit

ReqInit,H

GOOD
(Cascade)

Request
Initialization
(IR)

Constant

ReqInit,C

GOOD
(Cascade)

Not Invited (NI)

No Limits

NotInvited

GOOD
(Cascade)

Not Invited (NI)

Low Limit

NotInvited,L

GOOD
(Cascade)

Not Invited (NI)

High Limit

NotInvited,H

GOOD
(Cascade)

Not Invited (NI)

Constant

NotInvited,C

GOOD
(Cascade)

Not Selected
(NS)

No Limits

NotSelected

GOOD
(Cascade)

Not Selected
(NS)

Low Limit

NotSelectd,L

GOOD
(Cascade)

Not Selected
(NS)

High Limit

NotSelectd,H

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

501

12. Appendix C
12.2. Substatus Definitions for Quality Status

Fieldbus Status Byte

1-Char
Suffix

12-Char Independent
Status Field

Quality

Substatus

Limits

GOOD
(Cascade)

Not Selected
(NS)

Constant

NotSelectd,C

GOOD
(Cascade)

Local Override
(LO)

No Limits

OverrideLocl

GOOD
(Cascade)

Local Override
(LO)

Low Limit

OverrideLc,L

GOOD
(Cascade)

Local Override
(LO)

High Limit

OverrideLc,H

GOOD
(Cascade)

Local Override
(LO)

Constant

OverrideLc,C

GOOD
(Cascade)

Fault-State
Active (FSA)

No Limits

FaultState

GOOD
(Cascade)

Fault-State
Active (FSA)

Low Limit

FaultState,L

GOOD
(Cascade)

Fault-State
Active (FSA)

High Limit

FaultState,H

GOOD
(Cascade)

Fault-State
Active (FSA)

Constant

FaultState,C

GOOD
(Cascade)

Initiate FaultState (IFS)

No Limits

<blank>

InitFaultSt

GOOD
(Cascade)

Initiate FaultState (IFS)

Low Limit

LoLim,InitFS

GOOD
(Cascade)

Initiate FaultState (IFS)

High Limit

HiLim,InitFS

GOOD
(Cascade)

Initiate FaultState (IFS)

Constant

Const,InitFS

12.2 Substatus Definitions for Quality Status

Quality
502

Substatus

Description

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.2. Substatus Definitions for Quality Status

Quality

Substatus

Bad

Uncertain

R400
July 2010

Description

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 usable value

Set if this value had been set by

communication, which has now failed.

No Communication,
with no usable value

Set if there has never been any

communication with this value, since it was last
Out of Service.

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 a configurer 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 Accurate

Set if the value is at one of the sensor limits.

The limits define 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 Violation

Set if the value lies outside of the range of

values defined for this parameter. The limits
define which direction has been exceeded.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

503

12. Appendix C
12.2. Substatus Definitions for Quality Status

Quality

Substatus

Good (NonCascade)

Good (Cascade)

504

Description

Sub-Normal

Set if value derived from multiple values has

less than the required number of Good
sources.

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.

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 Alarm

Set if the value is good and the block has an

unacknowledged Block alarm.

Unacknowledged
Advisory Alarm

Set if the value is good and the block has an

unacknowledged alarm with a priority of less
than 8.

Unacknowledged
Critical Alarm

Set if the value is good and the block has an

unacknowledged alarm with a priority greater
than or equal to 8.

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

12. Appendix C
12.2. Substatus Definitions for Quality Status

Quality

R400
July 2010

Substatus

Description

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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

505

12. Appendix C
12.2. Substatus Definitions for Quality Status

506

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

13. Appendix D
13.1 Mode Change Conditions
Input Parameters
Status Attributes,
Inputs Values and
Resource States

Mode Parameter - Target Attribute Value

Out of
Service
(OOS)

Manual
(MAN)

Automatic
(Auto)

Cascade
(CAS)

Remote
Cascade
(RCAS)

Remote
Output
(ROUT)

All input parameters

have Good Status or
Uncertain status with
option set to treat
Uncertain as Good.

OOS

MAN

AUTO

CAS

RCAS

ROUT

Remote cascade in
has BAD status.

OOS

MAN

AUTO

CAS

Shed
based on
Shed
Option

ROUT

Remote out in has

BAD status.

OOS

MAN

AUTO

CAS

RCAS

Shed
based on
Shed
Option

Cascade input has a

status attribute of BAD

OOS

MAN

ROUT

Status attribute of
back calculation input
parameter is BAD

OOS

IMAN

Status attribute of
back calculation input
parameter Good - fault
state active, local
override, not invited, or
initialization request

OOS

IMAN

Tracking is enabled,
track input active and
track override manual
is Enabled.

OOS

Tracking is enabled,
initiated and track
override manual is
Disabled.

OOS

MAN

Fault State is active in

an output function
block

OOS

If target mode has

changed from OOS to
another mode since
the block was last
executed.

MAN or
evaluate
d mode

MAN or
evaluated
mode

MAN or
evaluate
d mode

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

13. Appendix D
13.1. Mode Change Conditions

Input Parameters
Status Attributes,
Inputs Values and
Resource States
Resource state as
reflected in the
resource block
parameter resource
state is Standby.

Mode Parameter - Target Attribute Value

Out of
Service
(OOS)
OOS

Manual
(MAN)
OOS

Automatic
(Auto)
OOS

Cascade
(CAS)
OOS

Remote
Cascade
(RCAS)
OOS

Remote
Output
(ROUT)
OOS

*Shed to the next lowest priority that is permitted and supported by the available inputs.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

509

13. Appendix D
13.1. Mode Change Conditions

510

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

14. Appendix E
14.1 Fieldbus Wiring Considerations
Fieldbus topologies
The following figure illustrates the Spur, Daisy Chain, and Tree type wiring topologies
that can be used to connect fieldbus devices to one another and a host.
Spurs
(Unterminated)
FD

Control Room
Spur Topology
Reguires layout design
Requires taps
Difficult to change

Junction Box
and Terminator

Terminator

Host

Home Run Cable (Trunk)

I.S.
Barrier
(Optional)
FD

Junction Box
and Terminator

Terminator

Daisy Chain Topology

Requires layout design
Difficult to change
Difficult to maintain

Host

I.S.
Barrier
(Optional)

Tree Topology
Conforms to present
practices
Wiring savings are
realized only in
home run cable

Junction Box
and Terminator

Terminator

Host

FD
Home Run Cable (Trunk)

I.S.
Barrier
(Optional)

Figure 50 Overview of fieldbus wiring topologies

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

511

14. Appendix E
14.1. Fieldbus Wiring Considerations

Power Conditioning
If an ordinary power supply were to be used to power the Fieldbus, the power supply
would absorb signals on the cable because it would try to maintain a constant voltage
level. For this reason, an ordinary power supply has to be conditioned for Fieldbus. This
is done by putting an inductor between the power supply and the Fieldbus wiring. The
inductor lets the DC power onto the wiring but prevents signals from going into the
power supply.
The inductor together with the capacitors in the terminators forms a circuit that can "ring"
and disrupt the signals. A resistor is placed in series with the inductor to stop this ringing.
This combination of components is a power conditioner.

In practice, a real inductor is not used but an electronic equivalent. The electronic
inductor circuit has the added advantage of limiting the current provided to the network
segment if the cable is shorted.
The voltage supplied to the Fieldbus cable can be as high as 32 V. The voltage at any
device can be as low as 9 V for the device to operate correctly. A typical Fieldbus device
takes about 20 mA of current from the cable. The Fieldbus is configured so that one of
the wires has a (+) voltage, the other wire has a (-) voltage and the shield is grounded.

A cable with the orange wire as plus and the blue wire as minus is shown above. This
type of cable is available from Fieldbus cable manufacturers. Other cables or existing
plant wiring conventions may be different. Regardless of the color convention, keep the
1
sense of Fieldbus polarity consistent throughout the plant. 1 "

RELCOM inc., Fieldbus Wiring Design and Installation Guide (2221 Yew Street,
Forest Grove, OR 97116) p. 5. Reprinted by permission.

512

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

14. Appendix E
14.1. Fieldbus Wiring Considerations

Power distribution
The number of devices on a fieldbus segment is limited by Ohm's law:
E=IxR
Where:
E = The voltage of the dc power supply
I = The amount of current in amperes drawn by each device
R = The resistance of the cable in ohms
For example, Assume that the characteristics of the segment are a power supply output of
20Vdc, 18 AWG cable with a resistance of 22 ohms per kilometer (3281 feet), and a
"home run" (trunk) cable that is 1 km (3,281 ft) long. This results in a combined
resistance of 44 ohms for both wires.
If each device at the "chickenfoot" draws 20mA and needs a minimum of 9Vdc, the cable
can use up to 11Vdc (20 - 9 = 11) and the total current that can be supplied at the
chickenfoot is 250mA (11Vdc/44 ohms = 250mA). This means the maximum number of
bus-powered devices that can be used at this example chickenfoot is 12 (250mA/20mA =
12 devices).
Be sure to check the fieldbus device specifications to determine the power requirements,
since they can vary by device type and manufacturer. For example, Honeywell's smart
pressure transmitter ST3000 and smart temperature transmitter STT350 require 18mA at
9Vdc and Flowserve's Logix 1400 digital positioner/controller requires 23mA at 9Vdc.
Test the power carrying capability of the fieldbus cable by connecting the wires together
at one end of the cable and measuring the resistance across the wires at the other end with
an ohmmeter.
Signal degradation limitations
One approach to minimizing signal distortion is to apply "rules of thumb" that suggest
how long a fieldbus cable can be and still get adequate signal quality. This is based on
published Fieldbus Foundation wiring guidelines.
The following table lists limits for some possible fieldbus cable types listed in the order
of usage preference with 1 being preferred.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

513

14. Appendix E
14.1. Fieldbus Wiring Considerations

Preference
Type

Description

Distance
(Meters/Feet)

Resistance
(Ohms per
km)

Attenuation
dB per km

#18 AWG, shielded, twisted

pair

1900/6233

#22 AWG, multiple-twisted,

pairs with overall shield

1200/3937

#26 AWG, multiple-twisted,

pairs without shield

400/1312

132

#16 AWG, multiple

conductor, no twisted pairs
with overall shield

200/656

Another rule of thumb based on Fieldbus Foundation published guidelines is for the
length of spurs and how many devices can be on various lengths of cable as listed in the
following table.
Number of Devices

Maximum Spur Length (Meter/Feet)

1 to 12

120/394

13 to 14

90/295

15 to 18

60/197

19 to 24

30/98

25 to 32

No spurs allowed

ATTENTION
The spur length limitations are for spurs with one device each. Please refer to
the Fieldbus Foundation AG-140 Wiring and Installation Guide for rules on
multiple devices per spur.

Cable guidelines summary

Total cable length is the sum of trunk and spur lengths. If different cable preference types
are used, apportion each type against its limit and be sure the total is less than one (1).

514

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

14. Appendix E
14.1. Fieldbus Wiring Considerations

For example, if the 500m (1640ft) trunk cable is preferred type 1 cable and the spurs are
100m (328ft) preferred type 2 cable, the total cable equals 0.35 (500/1900 + 100/1200 =
0.35).
Cable Attenuation
Signals attenuate or get smaller as they travel though cables. Attenuation is measured in
decibels (dB) based on the following formula.
dB = 20 log (V1/V2)
Where:
V1 = Amplitude of Transmitted Signal in Volts
V2 = Amplitude of Received Signal in Volts
Cables have attenuation ratings for a given frequency. The frequency of interest for
fieldbus is 39 kHz. The preferred type 1 cable for fieldbus has an attenuation of 3 dB/km.
A fieldbus device can transmit a signal as low as 0.75 volts peak-to-peak and detect a
signal as small as 0.15 volts peak-to-peak. This means that the cable can attenuate the
signal by 14 dB (20 log (0.75/.015) = 14 dB).
Based on using the preferred type 1 cable a fieldbus cable run could be up to 4.6 km
(15091 ft) long, as determined from this formula.
14 dB / 3 dB/km = 4.6 km
A shorter cable will have proportionately less attenuation.
For example, a preferred type 1 cable that is 500 m (1640 ft) long would have an
attenuation of 1.5 dB.
Signal distortion versus capacitance
Other factors such as varying characteristic impedance, spur connection reflections, and
capacitive unbalance between the wires and shield can distort signals as they travel
though the cable. This means an ideal signal transmission that is within fieldbus
specifications can arrive at the other end of the cable as a distorted signal.
In addition to cable attenuation, calculations for determining the maximum fieldbus cable
length must also use the following guidelines to calculate signal distortion due to spurs.
Each spur is converted to an equivalent capacitance.
All spurs are assumed to be at the extreme end of the trunk.
R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

515

14. Appendix E
14.1. Fieldbus Wiring Considerations

R400
July 2010

16. Appendix G
16.1 Loading CIOM-A FIM firmware
ATTENTION
If the CIOM-A FIM is not installed and pre-configured by the factory, users
must load the CIOM-A FIM's firmware to make it fully operational. This is also
true for any replacement CIOM-A FIM ordered separately from the factory.

Use the following procedures to check and load the CIOM-A FIM firmware, if required.
TIP
If you have updated firmware in a Control Processor Module (CPM), you will
find that this procedure is almost identical.

Checking CIOM-A FIM firmware status

Step
1

R400
July 2010

Action
Flip the switch on the Chassis
power supply to the ON
position.

Result
Applies power to the chassis and
installed modules initiate their "boot"
routines.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

519

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

click Run.

Opens the Run dialog box.

If you have a ControlNet supervisory

network, key in >ntools -u -c<.

Opens the Network Tools utility.

R400
July 2010

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

521

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Result

Click the OK button to acknowledge the

message prompt.

Ntools begins scanning the network for

installed components. Detected nodes
will appear under the Desktop directory.
This illustration is for example purposes
only.

Click the Resume button

toolbar.

522

Click the node icon.

in the

If this is the first time Ntools has been

used on the system, the Settings dialog
box opens. Otherwise, see the next
Result row and skip to Step 6.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Just enter appropriate data about the

local and remote chassis configurations
in your system on the given tabs and
click the OK button.

R400
July 2010

Result

Graphic representation of the chassis for

the selected node appears in the Detail
pane. This illustration is for example
purposes only.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

523

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

524

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Check the boot version (BV) and

application (personality) version (AV)
listed on the face of the CIOM-A FIM
(FFIF01) module graphic. This
illustration is for example purposes only.

If firmware versions are correct (green),

click NetworkTools->Exit to close the
utility and quit this procedure.

Result
If the version numbers shown are colored
green, they are the correct ones for your
current system software version. If they
are colored red, they need to be updated.

If firmware versions are wrong (red), go

to the next procedure Loading Boot
code to continue.

Loading Boot code

This procedure assumes that you have launched Ntools and determined that the CIOM-A
FIM firmware needs to be updated.
Step

R400
July 2010

Action

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

525

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Result

Click the CIOM-A FIM (FFIF01) graphic

in the Detail pane.

A red box appears around the graphic to

show that it is selected. This illustration is
for example purposes only.

2
Click the Flash button

526

in the toolbar.

Opens Warning! Use Extreme Care

message box.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Click the Yes button to acknowledge that

the system is Offline.

Opens Please Confirm Changes

message box.

Click the Yes button to acknowledge that

it is okay to shutdown the CIOM-A FIM.

Initiates shutdown and reboot of the

CIOM-A FIM and calls up the Open
dialog box. This illustration is for example
purposes only.

R400
July 2010

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

527

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step
5

Action
In the Look in field, click the
button to navigate to this directory
location c:\Program
Files\Honeywell\Experion\Enginee
ring Tools\system\firmware\FIM, if
required.

Result
Opens Please Confirm Changes
message box. This illustration is for
example purposes only.

Open appropriate release version

folder and click fimboot.nvs file so it
appears in the File name field. Click
the Open button.

528

Click the Yes button to acknowledge that

you want to proceed with the update.
(Note that RDY should appear in the FIM
display)

Initiates firmware load. LOAD

appears in the CIOM-A FIM display.
Progress of the load is tracked in
the status bar.

Wait for the load to complete and the

CIOM-A FIM to reboot to its RDY state.

NetworkTools message box appears.

Click the OK button to acknowledge that

the update completed with no errors.

Wait for the Ntools to complete its next

scan.

Check that the updated boot version (BV)

now appears on the CIOM-A FIM graphic
in green.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Result

Go to the next procedure Loading

Personality image to continue the
firmware update.

Loading Personality image

This procedure assumes that you have just completed the previous procedure or the
CIOM-A FIM has started up in the ALIV mode.
Step

Action

With CIOM-A FIM graphic still selected,

click

R400
July 2010

button.

Result
Opens Warning! Use Extreme Care
message box.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

529

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Result

Click the Yes button to acknowledge that

system is still Offline. .

Opens the Open dialog box. This

illustration is for example purposes only.

In the Look in field, click the

button to navigate to this directory
location c:\Program
Files\Honeywell\Experion\Enginee
ring Tools\system\firmware\FIM, if
required.

Opens the Please Confirm Changes

dialog box.

Click fimrex.nvs file so it appears

in the File name field. Click the Open
button.
4

Click the Yes button to acknowledge that

you want to proceed with the update.

Initiates the firmware load. LOAD

appears in the CIOM-A FIM display.
Progress of the load is tracked in
the status bar.

530

Wait for load to complete and the CIOMA FIM to reboot to its normal run state.

NetworkTools message box appears.

Click the OK button to acknowledge that

the update completed with no errors.

Wait for Ntools to complete its next scan.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

16. Appendix G
16.1. Loading CIOM-A FIM firmware

Step

Action

Check that the updated application

(Personality) version (AV) now appears
on the CIOM-A FIM graphic in green.

This completes the CIOM-A FIM firmware

update.

R400
July 2010

Result

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

531

16. Appendix G
16.1. Loading CIOM-A FIM firmware

532

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

17. Appendix H
17.1 Important Functional Considerations
The following tables lists some functional considerations to keep in mind when
integrating fieldbus with an Experion system.
General
Function

Indication

Consideration

Fieldbus device with

previous address
assignment is added
to a Link. .

Potential to lose Link

Schedule, if FIM fails
before "uncommissioned"
device is "commissioned".

Always remove the address from a

used fieldbus device before you store
it.

Adding Link Master

capable device to
operating Link.

Potential for LM capable

device to assume LAS role
using empty or incorrect
Link Schedule.

See the Guidelines for adding fieldbus

device to "live"/operating Link in the
Maintenance, Checkout, and
Calibration section of this document.

Link Slot Time setting

is 8 or less.

A new uncommissioned
device may not appear in
the Link directory in the
Monitoring tab.

Change the default Slot Time setting to

10 on the Link Block Parameters form
in Control Builder.

Using automatic
inactivate/activate
function in Load
Dialog box in Control
Builder

A component is
automatically inactivated
during the load and then
returned 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.

Fieldbus device
designated as
"backup" Link Master
cannot handle the
Link Schedule. (Also,
see the next row.)

Device icon turns yellow

(LM without schedule) or
red (bad communications).

R400
July 2010

(If an uncommissioned device does not

appear, try increasing the Slot Time
value by one and cycling power to the
FIM. Repeat this action, as required.)

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

533

17. Appendix H
17.1. Important Functional Considerations

Function

Indication

Schedule exceeds
Fieldbus Link Master
capable device's
predefined limits for
subschedules and/or
sequences.

Load errors identifying

subschedule problems.

Changing Load
Destination (LD)
attributes.

The Load Destination

attribute is automatically
set to NOLOAD or LOAD
for manufacturer-specific
parameters. Users can
edit Load Destination
attributes for parameters
through the Vendor tab in
the Parameter Definition
Editor (PDE).

Device icon turns yellow

(LM without schedule) or
red (bad communications).

Consideration
Most Link Master capable devices can
only support one subschedule and
cannot support blocks that are running
two different macrocycles. If the
number of subschedules 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 subschedule problems. In
this case, you must reconfigure the
device to become a Basic one through
Control Builder, and restart the device
to initiate the change.
A NOLOAD attribute means that the
associated parameter will never be
loaded to or uploaded from the actual
device. A LOAD attribute means that
the associated parameter will be
loaded to the actual device unless
"Partial Load" is selected when
loading.
Do a Partial Load followed by an
upload and update to save and
preserve the pre-configured values in a
device. Future loads can then be full
loads (Partial Load not selected).
Alternatively, do a full load (Partial
Load is not selected) to load preconfigure values in the Project copy
(Control Builder) to a device, but only if
the parameter LD attribute is LOAD.
Factory-set calibration parameters that
should not be overwritten should be set
to "NOLOAD".

534

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

17. Appendix H
17.1. Important Functional Considerations

Function

Indication

Consideration

Preserve factory
calibration in fieldbus
device.

Fieldbus device is
supplied as Factory
Calibrated.

Calibration parameters should have a

load destination of NOLOAD. Always
initiate device match as
Uncommissioned Device to Project
Device. Use "partial load" when
loading fieldbus blocks. After device
load, do an Upload followed by an
Update to Project to get information
into the Monitor database.

Using Restart with

Defaults to restart a
fieldbus device
through the
RESTART parameter
on the Other tab of its
Resource block
configuration form.

Configuration error
notification for an
associated block, such as
an Analog Input block.

Reload the device block from Project

tab with associated blocks set for Full
instead of Partial Load to restore
Experion default values. For example,
the ALERT_KEY parameter value is
set to 2 or 1.

Unassigning Fieldbus
block with RCAS_IN
or ROUT_IN
connection from a
Experion Block. Or,
deleting RCAS_IN or
ROUT_IN connection
from Fieldbus block
and re-wiring it to
block's CAS_IN pin.

The control VCR formed

when the RCAS_IN or
ROUT_IN connection was
made is not removed.

R400
July 2010

A Restart with Defaults function

restarts the device with factory default
values instead of Experion ones.
To remove this VCR, you must delete
the Fieldbus block and then recreate it.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

535

17. Appendix H
17.1. Important Functional Considerations

Function

Indication

Migrating to new
system software
release or moving a
device to another
Link.

Device is active and its

block icons are green.

Consideration
Before starting a software migration or
a device move, prepare a device by
putting its blocks in their Out-OfService (OOS) mode in the following
order.
Function Block(s)
Transducer Block(s)
Resource Block
See the section
Preparing Fieldbus Device for a Move
or Software Migration in this document
for more details.

Using Sequential
Control Module output
to push a NaN value
to a fieldbus device.

FIM will block write of NaN

value to fieldbus device
and SCM will indicate a
failure at that step.

Configure SCM so that it will not

attempt to push a NaN (Not-a-Number)
value as an output to a fieldbus device.

Fieldbus device
receives value with
status from a
Experion function
block.

If NaN value is delivered

to FIM for output, status
will be set to BAD and
value will be changed to
0.0 when sent to fieldbus
device.

Be sure to understand the device's

reaction to receiving 0.0 value with
BAD status in configured situation.

Fieldbus device
receives value without
status from a
Experion function
block for use as float.

No status byte
accompanies float data
type (such as is used by
limits, gains, tuning
parameters, etc.). FIM will
block write of NaN value to
fieldbus device. Last
successfully written value
will probably be retained
by the device.

If the device's behavior in the situation

is not acceptable, configure the
Experion logic to prevent it from
attempting to send NaN to the fieldbus
device.

Fieldbus device
receives value without
status from a
Experion function
block for use as value
with status.

If NaN value is delivered

to FIM for output, status
will be set to BAD and
value will be changed to
0.0 when sent to fieldbus
device.

Be sure to understand the device's

reaction to receiving 0.0 value with
BAD status in configured situation.

536

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

17. Appendix H
17.1. Important Functional Considerations

Function

Indication

Incoming Analog
value with status from
fieldbus device to
Experion function
block

R400
July 2010

A BAD status from

fieldbus device does not
force Experion function
block value to NaN.

Consideration
FOUNDATION Fieldbus devices may
show the last good value when the
current value is indicated as BAD via
the status. This is Not consistent with
normal Experion system operation.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

537

17. Appendix H
17.1. Important Functional Considerations

538

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.1 Link Parameters Reference
Background
The architecture of the Fieldbus communications entity is based on the ISO OSI
Reference model, but it includes only three layers as shown in the following illustration.

Network
Mgmt Agent

Device Aps

SMK

DIR OD

VCRs
Application
Layer

SMKP
FMS

FMS

Via
ALME

FAS
Data Link
Layer

DL-SAP/CEPs

DL-SAPs Only

Data Link Upper Level Functions

Via
DLME

Data Link Media Access Functions

NMIB
PH - SAP
Physical Medium Independent
Physical
Layer

Via
PLME

Physical Medium Dependent

MAU

Physical Medium

MAU

Physical Medium

Figure 51 Communications entity architecture.

The layer protocols provide Virtual Communication Relationships (VCRs), which are
communication channels between applications. The Fieldbus Message Specification
(FMS) provides VCR application-messaging services, such as reading and writing
variables. Some device Applications Processes (APs) may access the Fieldbus Access
Sublayer (FAS) directly rather than use the FMS. The System Management Kernel

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

539

18. Appendix I
18.2. Description

(SMK) also has direct access to the data link layer when communicating through its
System Management Kernel Protocol (SMKP).
The Fieldbus physical layer consists of the physical medium and the signaling protocol
used to transmit data. All fieldbus devices contain at least one physical layer entity, as
does each port in a bridge device.
Physical layer protocols provide the data link layer protocol the ability to send and
receive data independent of the physical medium type.
More detailed information
It is beyond the scope of this document to provide detailed information about the key
components of the FOUNDATION Fieldbus system architecture. This information is
provided in Fieldbus Foundation specifications. Please visit their website for more
information http://www.fieldbus.org/.

18.2 Description
Parameters for Link Configuration in Project Mode
The following table summarizes the parameters that are user configurable through the
LINK Block configuration form in the Project Mode. These parameters let you uniquely
identify the Link component in the control strategy and tune the performance of Link
communications. Only the Link parameters that are user configurable are listed.
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 Link. 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.
Tab
Main

540

Parameter

Default Value

Name
(NAME)

LINKxxx

Description
(DESC)

Blank

(Where xxx
equals a valid
number)

Description
User defined name starting with
a letter and consisting of up to
16 characters that must be
unique within the system.
User defined descriptive text
consisting of up to 132
characters.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

Parameter
Link Schedule
Optimization
(SCHDOPTIMIZE)

Default Value
OPT

Description
Specifies if the link schedule is
to be automatically optimized or
not.
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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

541

18. Appendix I
18.2. Description

Tab

Parameter
Sample Skew
(SAMPLESKEW)

Default Value
SKEW

Description
Determines when input blocks
will execute.
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
Management

Step Timer Preset

(T1)

15.0000s

Specifies the preset time for the

System Management step timer
in seconds. The default value is
specified by the
communications profile for the
application area.
This is an intersequence 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
(T2)

01:30.0000s

Specifies the preset value for

the System Management set
address sequence timer in
seconds. The default value is
specified by the
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.

542

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

Parameter
Preset Addr Wait
Timer
(T3)

Default Value
45.0000s

Description
Specifies the preset value for
the set address wait timer in
seconds. The default value is
specified by the
communications profile for the
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
Management
(LM)

R400
July 2010

Def Min Token

Delegation Time
(LMINFREC.DMDT)

Defines the default minimum

amount of local link capacity
that the LAS allocates to a
single Pass Token Data Link
Protocol Data Unit (PT DLPDU)
sent to the Data Link Entity
(DLE). Its range is 32 to 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

(LMINFREC.DTHT)

280

Defines the default initial

amount of local link capacity
that the LAS DLE allocates to
each DLE, in one cycle of
"circulating the token", 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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

543

18. Appendix I
18.2. Description

Tab

544

Parameter

Default Value

Description

Target Token Rotation

Time
(LMINFREC.TTRT)

60000

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 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 subfield 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

Time
(LMINFREC.LTHT)

334

Specifies the initial amount of local

link capacity that the LAS DLE
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 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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

R400
July 2010

Parameter

Default Value

Description

Time Distribution
Period
(LMINFREC.TDP)

5000

Determines the minimum

frequency of time distribution on
the local link. Its initial value is
the minimum value required for
the link's time synchronization
class and its range is 5
milliseconds to 55 seconds. The
unit is one millisecond.

LAS DB Status
Distribution Period
(LMINFREC.LDP)

5000

This parameter is used by the

LAS to determine the time
between two successive
distributions of the LAS'
database by means of the LAS
database status SPDUs sent on
the local link. Its range is 100
milliseconds to 55 seconds. The
unit is one millisecond.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

545

18. Appendix I
18.2. Description

Tab

Parameter
Slot Time
(LMLSTREC.ST)

Default Value
8

Description
Indicates the configured slot
time value. It is a fundamental
link parameter with multiple
uses. Each Link Master DLE
connected to the link uses Slottime to determine how long that
DLE monitors the link for
inactivity before sending a
CLAIM LAS (CL) DLPDU. Slottime 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.

546

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

R400
July 2010

Parameter

Default Value

Description

DLPdu Physical Layer

Overhead
(LMLSTREC.PHLO)

Indicates the configured Data

Link Protocol Data Units
(DLPDU) Physical Layer
Overhead (PhLO) value. The
DLE uses it to account for the
Physical Layer induced delay
between the end of the last
octet 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

(LMLSTREC.MRD)

Indicates the configured

maximum response delay value.
It is a measure, in units of one
slot time, greater than the worstcase period of 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
(LMLSTREC.FUN)

Indicates the first unused node

address value. It is the first node
address of a series of
consecutive node addresses,
which are to be 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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

547

18. Appendix I
18.2. Description

Tab

548

Parameter

Default Value

Description

This Link
(LMLSTREC.TL)

This parameter is a two-octet

primary identifier for the local
link, within the extended link,
whose values are constrained.
The DLE uses it to record the
local link ID. Its default
uninitialized 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
(LMLSTREC.MID)

Specifies the minimum duration

for an interval of nontransmission that a DLE
provides after either receiving or
transmitting a DLPDU. It 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 Unpolled
(LMLSTREC.NUN)

196

Specifies the number of

consecutive unused node
addresses, which are 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 value is 196

Preamble Extension
(LMLSTREC.PMBEXT
N)

Specifies an extension period

for the preamble. A preamble is
transmitted at the beginning of
each Physical Layer Protocol
Data Unit (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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

R400
July 2010

Parameter

Default Value

Description

Post Trans Gap

Extension
(LMLSTREC.PTGEXT
N)

Specifies an extension to the

minimum period during which a
subsequent transmission shall
not commence after
transmission of a 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 Skew
(LMLSTREC.MXICSS
W)

Defines the maximum accepted

differential delay between any
two 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
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.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

549

18. Appendix I
18.2. Description

Tab

Server
Parameters

550

Parameter

Default Value

Description

Time Sync Class

(LMLSTREC.TIMSCL
S)

10ms

Specifies one of the time

synchronization classes. The
DLE uses it to record the Link's
time synchronization class and
to determine the 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.

Point Detail Page

sysDtlLink.dsp

By default, a Display template is

already entered into the Point
Detail Page field (for example,
sysDtlLink.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 the name
built into the detail display that is
supplied as a template.

Associated Display

Blank

Enter the name of the Server

Associated Display to be
associated with this function
block.

Group Detail Page

sysgrpLink.dsp

By default, a Display template is

already entered into the Group
Detail Page field (for example,
sysgrpLink.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 the name
built into the detail display that is
supplied as a template.

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

Device
Diagnostics

Maintenance
tab

Parameter

Default Value

Description

Control Level

200

Indicate the Server Control

Level to be associated with this
function block.

Condition Name

Blank

This grid element displays all

the names of advanced alarm
conditions configured on the
selected device.

Enable

TRUE

This grid element displays

current advanced alarm
condition status. Uncheck box
mean that the configured
condition is disabled. Check
mean that the condition is
enabled.

Parameter Name

None

This grid element displays the

selected parameter name
(Transducer/Resource) of the
device, chosen for the nocache. This can be configurable
on project side.

Parameter Description

This grid element displays the

selected parameters
description.

Enable Block Offnet

Diagnostic Alarm

This parameter is used for

enabling or disabling the Block
Offnet Diagnostic Alarm. By
default, this parameter is
disabled.

(OFFNETALM_ENAB
LED)

Parameters for Link Configuration in Monitor Mode

The following table lists the Link configuration parameters that become active in the
Monitoring mode in addition to those listed above for the Project mode. We suggest that
you evaluate the impact of any parameter value change on Link operation before
changing another parameter.
Please note that not all parameters can be changed in the Monitoring mode. For example,
you cannot change any of the parameters on the Server Parameters tab in the Monitoring
mode.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

551

18. Appendix I
18.2. Description

ATTENTION
If fieldbus devices connected to the Link do not appear as uncommissioned
device icons in the Link Folder, increase the Slot Time (LMLSTREC.ST)
value to 10. If an uncommissioned device does not appear, try increasing the
Slot Time value by one and cycling power to the FIM. Repeat this action, as
required.
Note that the Fieldbus profile specifies a Slot Time setting of 8. Some older
fieldbus devices may not meet the Fieldbus profile requirements. This means
that the default Slot Time setting of 8 must be changed to accommodate the
actual setting in the fieldbus device.

Tab
Main

Parameter
Enable MAU
Loopback
(LOOPBACK)

Default Value
Disabled
(No Check
mark)

Description
Determines whether or not the
Medium Attachment Unit (MAU)
Loopback function for the FIM is
enabled. A check mark in the
check box means that the
LOOPBACK function is enabled.
A blank check box means that
the LOOPBACK function is not
enabled. The default value is a
blank check box or the
LOOPBACK function is not
enabled.
When LOOPBACK is enabled, it
disables the final output stage of
the MAU transmit circuit,
connects the output of the
previous stage of the MAU
transmit circuit to the MAU
receive circuit, and disconnects
the MAU receive circuit from the
medium. The state of the
Loopback Enable shall not
change while the MAU is
transmitting or receiving.
This is a confirmation service of
local significance only, which
provides a device with the
facility to test the integrity and
functionality of the Physical
Layer circuitry, excluding the

552

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

Parameter

Default Value

Description
medium.

Network
Management
(LM)

Acting Primary Link

Master
(ACTINGLM)

Check Mark

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.

Primary Link Master

(PRIM_LM_FLG)

Check Mark

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 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.

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

553

18. Appendix I
18.2. Description

Tab

Parameter

Default Value

Description
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.

Boot Operational
Function Class
(BOOT_OPER)

554

LINKMASTER

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.

Specifies the Operational

Function Class that the device
assumes when it is powered up.
The class selections are Basic,
Link Master, and Bridge. The
FIM is the Primary Link Master

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

18. Appendix I
18.2. Description

Tab

Parameter

Default Value

Description
for both Links.

Some term abbreviations

The following abbreviations are listed for reference.
AP

Application Process

DLE

Data Link Entity

DLL

Data Link Layer - Defined in ISO 7498

DLME

Data Link Layer Management Entity

DLPDU

Data Link Protocol Data Unit

FAS

Fieldbus Access Sublayer

FIM

Fieldbus Interface Module

FMS

Fieldbus Message Specification

IRRD

Immediate Response Recovery Delay

ISO

International Organization For Standardization

LAS

Link Active Scheduler

MAU

Medium Attachment Unit - For wire media MAU = transceiver

MDS

Medium Dependent Sublayer

NMA

Network Management Agent

OSI

Open Systems Interconnection

PhL

Physical Layer

PhLO

Physical Layer Overhead

PhPDU

Physical Layer Protocol Data Unit

R400
July 2010

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

555

18. Appendix I
18.2. Description

556

PT DLPDU

Pass Token Data Link Protocol Data Unit

SMK

System Management Kernel

SMKP

System Management Kernel Protocol

VCR

Virtual Communications Relationship

Experion PKS Series A Fieldbus Interface Module User's Guide

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

19. Appendix J
19.1 Load Interactions for Fieldbus Related Operations
Summary
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
Schedules

Load
Schedule
into FIM's
Link

Load LM
Schedules
into
LM-Capable
Devices

Load
Used
Function
Blocks

State Required
for Operation

Load Device
or
Replace Device

This device
only, if LMcapable

Yes

Blocks in device
= OOS,
Device = OOS,
Link = Active

Delete Device
from Loaded

Honeywell

Downloaded from www.Manualslib.com manuals search engine

R400
July 2010

Downloaded from www.Manualslib.com manuals search engine

Honeywell Process Solutions

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA

Downloaded from www.Manualslib.com manuals search engine

Lab Ubiquity of Bacteria
86% (7)
Lab Ubiquity of Bacteria
8 pages
EPKS Overview Evolution
No ratings yet
EPKS Overview Evolution
14 pages
Rosa 2000
No ratings yet
Rosa 2000
21 pages
Control Builder Components Reference PDF Free
No ratings yet
Control Builder Components Reference PDF Free
368 pages
UX Design
100% (4)
UX Design
96 pages
Safety and Security Roadshow 2012 Safety Systems PDF
No ratings yet
Safety and Security Roadshow 2012 Safety Systems PDF
26 pages
AM Algorithm Engineering Data AM09601 PDF
100% (1)
AM Algorithm Engineering Data AM09601 PDF
171 pages
HPM - Specification and Technical Data
No ratings yet
HPM - Specification and Technical Data
48 pages
Series C Fieldbus Interface Module Users Guide EPDOC X125 en 432
No ratings yet
Series C Fieldbus Interface Module Users Guide EPDOC X125 en 432
490 pages
Honeywell Tps Manuals
0% (2)
Honeywell Tps Manuals
2 pages
Isolated Foundation Calculation (ACI 318M-95) : Input Data
100% (1)
Isolated Foundation Calculation (ACI 318M-95) : Input Data
5 pages
Control Fire
No ratings yet
Control Fire
34 pages
Honeywell RC500 Switch Users Guide
No ratings yet
Honeywell RC500 Switch Users Guide
38 pages
Application Control Environment Users Guide EP-DCX306
100% (1)
Application Control Environment Users Guide EP-DCX306
94 pages
Dictionary EP-DCX126 PDF
No ratings yet
Dictionary EP-DCX126 PDF
134 pages
Honeywell EMEA12 DeGroot Safety Manager
No ratings yet
Honeywell EMEA12 DeGroot Safety Manager
41 pages
Getting Started With Experion PKS PDF
0% (1)
Getting Started With Experion PKS PDF
34 pages
Overview of Experion HS R430: Superior, Flexible, and Efficient !!
No ratings yet
Overview of Experion HS R430: Superior, Flexible, and Efficient !!
10 pages
UserGd Axs4iccp 132095
100% (1)
UserGd Axs4iccp 132095
233 pages
5.3. - FTE Bridge Configuring
No ratings yet
5.3. - FTE Bridge Configuring
10 pages
Device Level Ring (DLR) Supervisor Reports A Rapid Fault - Restore Cycle
No ratings yet
Device Level Ring (DLR) Supervisor Reports A Rapid Fault - Restore Cycle
5 pages
Experion CEE-based Controllers and I/O: Doc EP03-290-400
No ratings yet
Experion CEE-based Controllers and I/O: Doc EP03-290-400
43 pages
PKS - TDC 3000 Customer Resource Manual: Tps LCN Recovery Guidelines
No ratings yet
PKS - TDC 3000 Customer Resource Manual: Tps LCN Recovery Guidelines
7 pages
FSC To Safety Manager Migration Solution Note
No ratings yet
FSC To Safety Manager Migration Solution Note
2 pages
PMT Hps FDM Troubleshooting Guide Ep FDM 12440
No ratings yet
PMT Hps FDM Troubleshooting Guide Ep FDM 12440
130 pages
PlantPAx HMI Security Configuration
No ratings yet
PlantPAx HMI Security Configuration
1 page
Experion PKS: Fundamentals - Server & Controller Engineering (R431)
No ratings yet
Experion PKS: Fundamentals - Server & Controller Engineering (R431)
2 pages
06 PlantPAx Distributed Control System
No ratings yet
06 PlantPAx Distributed Control System
128 pages
Installation and Setup: Alarm and Event Analysis
No ratings yet
Installation and Setup: Alarm and Event Analysis
107 pages
Controledge Hc900 Control Designer Software User Guide: Honeywell Process Solutions
No ratings yet
Controledge Hc900 Control Designer Software User Guide: Honeywell Process Solutions
326 pages
Experion Site Planning Guide EPDCX686
67% (3)
Experion Site Planning Guide EPDCX686
132 pages
OPC UA Client Interface Reference
No ratings yet
OPC UA Client Interface Reference
54 pages
Johan School, Honeywell: Safety Systems Alarms, Events and Sequence of Events (SOE)
No ratings yet
Johan School, Honeywell: Safety Systems Alarms, Events and Sequence of Events (SOE)
52 pages
Hon EMEA16 Bastone Experion PKS Orion
No ratings yet
Hon EMEA16 Bastone Experion PKS Orion
43 pages
Honeywell Experion I/O Pin
No ratings yet
Honeywell Experion I/O Pin
7 pages
EP-DSX223-210 System Integration Overview and Planning Guide
No ratings yet
EP-DSX223-210 System Integration Overview and Planning Guide
38 pages
Whitepaper Experion ControlEdgePLC Integration PDF
No ratings yet
Whitepaper Experion ControlEdgePLC Integration PDF
9 pages
Experion ACE
No ratings yet
Experion ACE
3 pages
Trusted Maintenance Training Manual (Rev. 3 - 0)
No ratings yet
Trusted Maintenance Training Manual (Rev. 3 - 0)
170 pages
3BSE036351R5011 CIO AC800M HWOp
No ratings yet
3BSE036351R5011 CIO AC800M HWOp
336 pages
13 - 4551 - I - 2 Safety Manager Experion PKS Integration - CDA
No ratings yet
13 - 4551 - I - 2 Safety Manager Experion PKS Integration - CDA
56 pages
CL Server Users Guide EP-DCX706
No ratings yet
CL Server Users Guide EP-DCX706
66 pages
Hardware Installation Guide EXDOC X269 en 110
No ratings yet
Hardware Installation Guide EXDOC X269 en 110
48 pages
Safety Manager SC EC List V1.8
No ratings yet
Safety Manager SC EC List V1.8
19 pages
Safety Manager FDU Solution Note
No ratings yet
Safety Manager FDU Solution Note
2 pages
SCADA Intouch Connection
No ratings yet
SCADA Intouch Connection
19 pages
01 - 04R201 - 1 - CEE Controller Architecture
No ratings yet
01 - 04R201 - 1 - CEE Controller Architecture
54 pages
TPS Process Network R688.2: Software Change Notice
No ratings yet
TPS Process Network R688.2: Software Change Notice
46 pages
MasterLogic 200catalog
No ratings yet
MasterLogic 200catalog
88 pages
Mkted2140504en Esx Control Expert
No ratings yet
Mkted2140504en Esx Control Expert
50 pages
LCN Guidelines Implementation Troubleshooting and Service LC09610 PDF
100% (1)
LCN Guidelines Implementation Troubleshooting and Service LC09610 PDF
314 pages
R310.2 Support Software Change Notice
No ratings yet
R310.2 Support Software Change Notice
166 pages
Experion LCN Tech Spec PDF
100% (1)
Experion LCN Tech Spec PDF
27 pages
LCN Planning
No ratings yet
LCN Planning
268 pages
3BSE027630-510 en S800 I O DTM 5.3
No ratings yet
3BSE027630-510 en S800 I O DTM 5.3
184 pages
Application Development Guide EP-DSXX16
No ratings yet
Application Development Guide EP-DSXX16
522 pages
Proces rm200 - en P
No ratings yet
Proces rm200 - en P
538 pages
Control Building Users Guide EPDOC-XX19-En-410
No ratings yet
Control Building Users Guide EPDOC-XX19-En-410
1,198 pages
Control Hardware Planning Guide EPDOC-XX23-En-410
No ratings yet
Control Hardware Planning Guide EPDOC-XX23-En-410
570 pages
Ethernet Implementation Guide EPDOC XX34 en 410
No ratings yet
Ethernet Implementation Guide EPDOC XX34 en 410
42 pages
EPDCX145 - Serial Interface Module Implementation Guide
No ratings yet
EPDCX145 - Serial Interface Module Implementation Guide
136 pages
Application Control Environment Users Guide EPDOC-XXX4-En-410
No ratings yet
Application Control Environment Users Guide EPDOC-XXX4-En-410
96 pages
Control Builder Components - Ref
No ratings yet
Control Builder Components - Ref
256 pages
Control Builder Error Codes Reference EPDOC-XX17-En-410
No ratings yet
Control Builder Error Codes Reference EPDOC-XX17-En-410
1,424 pages
ARAGON72 Clifford Algebra
100% (1)
ARAGON72 Clifford Algebra
12 pages
PAGO ASSESSMENT. Seminar 2. 2022
No ratings yet
PAGO ASSESSMENT. Seminar 2. 2022
26 pages
IELTS Listening Task Type 3 (Plan, Map, Diagram Labelling) Activity - Teacher's Notes
No ratings yet
IELTS Listening Task Type 3 (Plan, Map, Diagram Labelling) Activity - Teacher's Notes
5 pages
University of Agricultural Sciences, Dharwad
No ratings yet
University of Agricultural Sciences, Dharwad
4 pages
Piping Welding Notes For Beginners Piping and Welding QAQC
100% (3)
Piping Welding Notes For Beginners Piping and Welding QAQC
38 pages
Day 1 Instructional Practice Debrief
No ratings yet
Day 1 Instructional Practice Debrief
8 pages
All Questions Are Compulsory. This Question Paper Contains 7 Questions
No ratings yet
All Questions Are Compulsory. This Question Paper Contains 7 Questions
16 pages
The Planets in The Houses of Your Birth Chart
100% (1)
The Planets in The Houses of Your Birth Chart
15 pages
Introduction To Rocket Propulsion
No ratings yet
Introduction To Rocket Propulsion
2 pages
Quantum Reading PDF
No ratings yet
Quantum Reading PDF
9 pages
Ice Shields and Climate Change - Robin Grayson
No ratings yet
Ice Shields and Climate Change - Robin Grayson
25 pages
Essay Writing Rubric: Criteria Category 4 Excellent 3 Good 2 Fair 1 Poor Use of Conventions
No ratings yet
Essay Writing Rubric: Criteria Category 4 Excellent 3 Good 2 Fair 1 Poor Use of Conventions
3 pages
Spatial Multicriteria Analysis Using A G
No ratings yet
Spatial Multicriteria Analysis Using A G
16 pages
SITHIND002 Bigyan S Assessment Task 1
No ratings yet
SITHIND002 Bigyan S Assessment Task 1
19 pages
Kuhan CV PDF
No ratings yet
Kuhan CV PDF
2 pages
1) Sapiens - A Brief History of Humankind by Yuval Noah Harari - Summary
No ratings yet
1) Sapiens - A Brief History of Humankind by Yuval Noah Harari - Summary
13 pages
E-CAT35WWE18 BattleTech Dig Defend or Die
67% (3)
E-CAT35WWE18 BattleTech Dig Defend or Die
15 pages
Colreg Guide - Deni̇zde Çatişmayi Önleme Klavuzu
100% (10)
Colreg Guide - Deni̇zde Çatişmayi Önleme Klavuzu
29 pages
Inter and Intra As Say Coefficients of Variability
No ratings yet
Inter and Intra As Say Coefficients of Variability
4 pages
GML
No ratings yet
GML
24 pages
This Study Resource Was: CEE30005 Tutorial 2 - Solution
No ratings yet
This Study Resource Was: CEE30005 Tutorial 2 - Solution
3 pages
Mac 2023-std 6-Maths
No ratings yet
Mac 2023-std 6-Maths
3 pages
3bd35dc1d08c02564fc24a4fc8cf9c48 (1)
No ratings yet
3bd35dc1d08c02564fc24a4fc8cf9c48 (1)
30 pages
What Are Real Life Examples of Deontological Ethics?: 9 Answers
No ratings yet
What Are Real Life Examples of Deontological Ethics?: 9 Answers
2 pages
Book Worm Final
No ratings yet
Book Worm Final
5 pages
Introduction To Communication (PPT) 2
No ratings yet
Introduction To Communication (PPT) 2
16 pages