5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.

com
B0400FD
REV D

™ I/A Series®
FOUNDATION  fieldbus H1 Communication
Interface Modules (FBM220/FBM221)
User’s Guide
October 5, 2004

http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Invensys, Foxboro, FoxCAE, FoxDraw, FoxView, and I/A Series are trademarks of Invensys plc, its subsidiaries,
and affiliates.
FOUNDATION is a trademark of The Fieldbus Foundation.
NI-FBUS is a registered trademark of National Instruments Corporation.
Relcom is a trademark of Relcom Technologies Limited.
 Windows NT is a registered trademark of Microsoft Corporation.
UNIX is a trademark of the X-Open Company.
Solaris is a trademark of Sun Microsystems, Inc.
 All other brand names may be trademarks of their respective owners.

Copyright 2001-2004 Invensys Systems, Inc.

 All rights reserved

http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Contents 
Figures................................................................................................................................... vii

Tables..................................................................................................................................... ix 

Preface.................................................................................................................................... xi
 Who This Book Is For ............................................................................................................. xi
 What You Should Know .......................................................................................................... xi
Revision Information ............................................................................................................... xi
Reference Documents .............................................................................................................. xi
I/A Series Documents .......................................................................................................... xi
 FOUNDATION Fieldbus Documents ............................................................................. xii

1. Introduction...................................................................................................................... 1
Glossary of Terms ..................................................................................................................... 2

2. Quick-Start Example ......................................................................................................... 5

3. Product Application ........................................................................................................ 13

Functional and Environmental Constraints ............................................................................. 13
Field Device Configuration Requirements .............................................................................. 13
Topologies .............................................................................................................................. 14
Bus Length Calculations ..................................................................................................... 14
Bus Power Supply .............................................................................................................. 15
Bus Power Calculations ...................................................................................................... 15
Intrinsic Safety Considerations ........................................................................................... 15
Control Loop Execution Time ................................................................................................ 16

4. Installation ...................................................................................................................... 17
FOUNDATION Fieldbus Cable Connections ....................................................................... 18

Power Connections ................................................................................................................. 20

5. Configuration Information.............................................................................................. 23
H1 Field Device Parameters .................................................................................................... 23
H1 Transmitter LAS/LM Disabling Procedure ................................................................... 27
Block Interconnections ........................................................................................................... 28
Configuration Procedures ....................................................................................................... 31
Block Processing ..................................................................................................................... 32

iii
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Contents

DCI Block Functions .............................................................................................................. 33

Periodic/Change-Driven Execution .................................................................................... 33
 Auto/Manual Mode Operation .......................................................................................... 33
Simulation Mode ............................................................................................................... 33
Time Stamping .................................................................................................................. 33
Signal Conditioning and Linear Scaling ............................................................................. 33
Input Limiting ................................................................................................................... 33
Confirmed Outputs ............................................................................................................ 34
Output Clamping .............................................................................................................. 34
Output Initialization .......................................................................................................... 34
Cascade Initialization ......................................................................................................... 34
Fail-Safe Actions ................................................................................................................. 35
Heartbeat Message Handling .............................................................................................. 36
Control Schemes Using DCI Blocks ....................................................................................... 37
DCI Block Parameter Mapping .............................................................................................. 40
Function Block Parameter Status Mapping ............................................................................. 40

DCI Block Status

Parameter (BLKSTA)
Status ............................................................................................. 40
........................................................................................................ 41

6. Process Operator Displays............................................................................................... 43

Block Detail Displays .............................................................................................................. 43
ECB200 Block Detail Display ............................................................................................ 44
ECB200 Faceplate ......................................................................................................... 45
ECB200 Primary Data .................................................................................................. 45
ECB201 Block Detail Display ................................................................................................. 46
ECB201 Faceplate ......................................................................................................... 47

ECB201 Primary Data .................................................................................................. 47

7. Maintenance.................................................................................................................... 49
System Management Displays ................................................................................................. 49
FBM220/221 Equipment Information Display .................................................................. 49
FBM220/221 Equipment Change Display ......................................................................... 49
H1 Field Device Equipment Information Display .............................................................. 49
H1 Field Device Equipment Change Display ..................................................................... 51
LED Indicators ....................................................................................................................... 51

 Appendix A. Control Loop Performance ............................................................................. 55

Macrocycle Architecture .......................................................................................................... 55
Macrocycle Schedule Algorithm .............................................................................................. 57
BPC/Macrocycle Phasing ........................................................................................................ 57
Typical Control Loop Timing ................................................................................................. 58
Maximum Performance Control Loops ................................................................................... 59
Macrocycle Period ................................................................................................................... 59

iv
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
 Contents B0400FD – Rev D

Index .................................................................................................................................... 61

v
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Contents

vi
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Figures 
1-1. FBM220/221 and Associated Foundation Fieldbus Elements ........................................ 1
2-1. Typical Fieldbus H1/Foxboro I/A Series Integration Process ......................................... 5
2-2. Typical Overview ICC Display for a Control Processor 60 ........................................... 8
2-3. Typical ECB200 (Parent) Editing Display .................................................................... 9
2-4. Typical ECB201 (Child) Editing Display ................................................................... 10
2-5. Typical DCI Block Editing Display ............................................................................ 11
4-1. FBM220/221 and Termination Assembly Installation ................................................ 17
4-2. TA Foundation Fieldbus Cable Connections .............................................................. 19
4-3. TA Component Locations (Covers Removed) ............................................................. 20
4-4. TA Foundation Fieldbus Power Connections .............................................................. 21
4-5. Installation of Ferrite Cores in Power Cables ............................................................... 22
5-1. ECB Hierarchy ........................................................................................................... 28
5-2. Block/DCI Block Functional Relationships ................................................................. 29
5-3. Typical User-Configured Block Interconnections ........................................................ 30
5-4. Simple Cascade Configuration .................................................................................... 37
5-5. Supervisory Control Configuration ............................................................................. 38
5-6. Embedded MVC Control Configuration .................................................................... 39
6-1. ECB200 Block Detail Display ..................................................................................... 44
6-2. ECB201 Block Detail Display ..................................................................................... 46
7-1. Typical H1 Field Device Equipment Information Display (1 of 2) ............................. 50
7-2. Typical H1 Field Device Equipment Information Display (2 of 2) ............................. 50
7-3. Typical H1 Field Device Equipment Change Display ................................................. 51
7-4. FBM221 LED Status Indicators .................................................................................. 53
 A-1. Link Timing Diagram ................................................................................................. 55
 A-2. BPC/Macrocycle Phasing ............................................................................................ 57

vii
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Figures

viii
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Tables 
5-1. FBM220/221 Maximum Configuration Specifications ............................................... 23
5-2. Transducer Block Parameters ...................................................................................... 24
5-3. Resource Block Parameters .......................................................................................... 24
5-4. Analog Input (AI) Block Parameters ............................................................................ 25
5-5. Analog Output (AO) Block Parameters ....................................................................... 25
5-6. Discrete Input (DI) Block Parameters ......................................................................... 26
5-7. Discrete Output (DO) Block Parameters .................................................................... 26
5-8. Key Parameters ............................................................................................................ 31
5-9. DCI Block Parameter Mapping .................................................................................. 40
5-10. DCI Parameter Status Mapping .................................................................................. 40
5-11. DCI Parameter Status Mapping .................................................................................. 41
7-1. LED Status for FBM Operating Modes ...................................................................... 52
7-2. LED Status for FBM Hardware Diagnostics Failure .................................................... 52

ix
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Tables

x
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Preface 
This document describes the FOUNDATION™  fieldbus H1 Communication Interface Module
(FBM220 or FBM221). For detailed device configuration information refer to FoxCAE™ V5.0
Supplement for F OUNDATION  fieldbus H1 Support (B0400DE).

Who This Book Is For

This book is intended for the use of process control engineers and operators, instrument and
maintenance engineers, and other qualified and authorized personnel involved in setting up and
configuring, and maintaining I/A Series® equipment to provide a FOUNDATION fieldbus H1
interface.

What
Prior toYou Should
using this Know
book, you should be generally familiar with the I/A Series system and with
DIN Rail Mounted FBM Subsystem User’s Guide  (B0400FA). Detailed information for the various
I/A Series software and hardware elements is found in the reference documents listed below.

Revision Information
For this release of the document the following changes have been made:
Chapter 4 “Installation” 
♦ Revised Figure 4-1, Figure 4-4, and Figure 4-5 to reflect correct ferrite core installa-
tion. Also updated supporting text for these figures.
♦ Updated the part number for clamp-on ferrite cores from BF162YH to BF162YG.
 Appendix A “Control Loop Performance”
♦ Section rewritten.

Reference Documents
The following documents provide additional and related information.

I/A Series Documents

♦ F OUNDATION  fieldbus H1 Communication Interface Module (FBM220/221) 
(PSS 21H-2Z20 B4)
♦ FBM220/221 Termination Assembly – F OUNDATION  fieldbus Communication 
(PSS 21H-2W5 B4)
♦ DIN Rail Mounted FBM Subsystem User’s Guide  (B0400FA)
♦ Control Processor 60 and Control Processor 60S Installation and Maintenance
(B0400FB)

xi
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Preface

♦ Control Processor 60 (CP60) Sizing Guidelines and Spreadsheet (B0400BK)

♦ Integrated Control Block Descriptions  (B0193AX)
♦ Integrated Control Software Concepts  (B0193AW)
♦ Integrated Control Configurator  (B0193AV)
♦ System Definition: A Step-by Step-Procedure  (B0193WQ and associated on-line Help)
♦
Process Operations and Displays  (B0193MM)
♦ System Management Displays  (B0193JC and associated on-line Help)
♦ System Equipment Installation  (B0193AC)
♦ Software Installation (Solaris™ Platform)  (B0193JG)
♦ Computer Aided Engineering for I/A Series Control Station Databases, FoxCAE
Version 4.0  (B0193MR)
♦ FoxDraw™ (B0193WG)
♦ FoxView™ (B0193WH)
♦ Grouped Object Editor for Displays  (B0193DV)
♦ FoxCAE V5.0 Supplement for F OUNDATION  fieldbus H1 Support (B0400DE).

 FOUNDATION Fieldbus Documents
NOTE
The two NI-FBUS® documents listed below – NI-FBUS Configurator User Manual
(Part No. 321423-01), and Getting Started with Your AT-FBUS and NI-FBUS
Software for Windows NT ®  (Part No. 321014C-01) – are included with the
NI-FBUS software package. Most of the other FOUNDATION fieldbus documents
listed can be obtained by contacting the Fieldbus FOUNDATION organization at

www.fieldbus.org .
♦ FD-043, Technical Overview, F OUNDATION  fieldbus 
♦  AG-140, Wiring and Installation, 31.25 kbits/s Voltage Mode Wire Medium, Application
Guide 
♦ 321423B-01, NI-FBUS Configurator User Manual 
♦ 321014C-01, Getting Started with Your AT-FBUS and NI-FBUS Software for
Windows NT 
♦  AG-163, 31.25 kbits/s Intrinsically Safe Systems, Application Guide 
♦  – 
FF-890, Function Block Application Process  Part 1
♦ FF-891, Function Block Application Process  –  Part 2 
♦ IEC 1158-2: 1993, Fieldbus Standard for Use in Industrial Control Systems  –  Part 2:
Physical Layer Specification and Service Definition 
♦ ISA-S50.02-1992, Fieldbus Standard for Use in Industrial Control Systems  –  Part 2:
Physical Layer Specification and Service Definition 

xii
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
 Preface B0400FD – Rev D

♦ dS50.02, Part 2 [Draft Standard] 1995, Fieldbus Standard for Use in Industrial Control
Systems –  Part 2: Physical Layer Specification and Service Definition, Amendment to
Clause 22 (Formerly Clause 11 and Clause 24) 
♦ ISA-RP12.6, Wiring Practices for Hazardous (Classified) Locations Instrumentation
Part I: Intrinsic Safety, Recommended Practice 
♦ FF-816, Fieldbus F OUNDATION  Physical Layer Profile Specification.

xiii
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Preface

xiv
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

1. Introduction 
This chapter provides an overview of the FBM220 and FBM221, and the network
configuration in which they used.
The FOUNDATION fieldbus H1 Communication Interface Modules (FBM220/FBM221) pro-
vide channel isolated digital communications to/from FOUNDATION fieldbus field devices over
twisted-pair wires at 31.25 Kbps. FBM220 supports one H1 communication segment (channel)
and FBM221 supports four.
The FOUNDATION fieldbus is an all digital, serial, two-way communication system which inter-
connects field devices, such as transmitters and actuators, with host controllers. FBM220/221,
together with a Fieldbus Communications Module (FCM), provides a communication interface
between the I/A Series control station (typically, a Control Processor 60) and the field devices in
the FOUNDATION fieldbus topology. Figure 1-1 shows the relationship between the various
equipment elements.

To Additional, Similar
I/A Series Equipment Groupings
Control Station (if applicable)
(Fault-Tolerant)
10Base2 (10 Mbps)
F F Ethernet Trunk Fieldbus
C C 2 Mbps (redundant)
M M Module Fieldbus
To Additional FBMs
(if applicable)

FBM Up to 120 FBMs per

220/221 I/A Series Control Station

From optionally
redundant dc TA Termination
power sources Assembly FOUNDATION Fieldbus
(See Note) (Typical Topology)

Terminator* Terminator

NOTE: The Termination Assembly contains a dc-to-dc

converter and a bus terminator. The bus terminator is Field Devices
used to terminate the FOUNDATION fieldbus when the
FBM220/221 is located at the end of the bus segment.
*A separate bus terminator (shown in dashed lines) is used when the FBM220/221 is located
mid point on the bus segment.
Figure 1-1. FBM220/221 and Associated FOUNDATION Fieldbus Elements

The FBM220/221 mounts on a baseplate along with other DIN rail mounted FBMs, and con-
nects to its associated termination assembly (TA) by means of a cable. As illustrated in Figure 1-1,
FBM220/221 receives and processes signals to/from the FOUNDATION fieldbus via the TA, and
communicates with the I/A Series CP60 via the FCM(s).

1
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 1. Introduction

In addition to FOUNDATION fieldbus wire connection points, the TA contains a dc-to-dc

converter, and a bus terminator for each channel (one for each H1 bus segment). The dc-to-dc
converter converts 24 V dc power from an external source (a user-supplied power supply, or one
of the existing rack-mounted DIN rail subsystem power supplies) to isolated 30 V dc power
required by the FOUNDATION fieldbus field devices.
The bus terminator in the TA is used when the FBM220/221 is located at the end point on the

FOUNDATION
or  fieldbus
out) and local segment.
powering of the Switches located
bus (on/off) on aon
perthe TA provide
channel forsegment)
(per bus terminator selection (in
basis.
FBM220/221 allows for the use of multi-vendor H1 (FOUNDATION fieldbus certified) devices.
Together with other elements of the I/A Series system, FBM220/221 provides proven I/A Series
control, alarming, trending, and display capabilities.

Glossary of Terms
The following terminology relates directly to the FBM220/221 and its associated equipment. For
a glossary of terms relating to F OUNDATION fieldbus installation, refer to FOUNDATION fieldbus
document AG-140, Wiring and Installation, 31.25 kbits/s Voltage Mode Wire Medium, Application
Guide.

Baseplate The baseplate provides mounting for DIN rail mounted FBMs and FCMs
(see Figure 4-1 on page 17). Its eight mounting positions can accommo-
date up to eight FBMs, or a combination of FBMs and FCMs. The base-
plate also provides the necessary connectors for dc power, the I/A Series
Module Fieldbus, and termination cables.

Control Station This is any I/A Series module that effects process control via the I/A Series
Ethernet trunk Fieldbus. An example is the Control Processor 60 (CP60).
The control station controls process variables using algorithms contained
in functional control blocks configured by on-site process engineers to
implement the desired control strategies.

DCI Distributed Control Interface (DCI) control blocks  –  BIN (Binary

Input)  BOUT (Binary Output), RIN (Real Input), and ROUT (Real
,

Output)  –  are I/A Series control blocks used to interface with H1

FOUNDATION fieldbus field devices using digital communications.

DIN Rail Mounted FBM Subsystem

The DIN rail mounted FBM subsystem provides a high-speed communi-
cation interface between the host control processor (for example an
I/A Series control station) and field I/O sensors and actuators. DIN rail
mounted devices, which include FBMs, FCMs and supporting cables and
connectors, mount on a baseplate which, in turn, mounts on a DIN rail.
The DIN rail mounted FBM subsystem is described in detail in the DIN
Rail Mounted FBM Subsystem User’s Guide  (B0400FA).

ECB An Equipment Control Block, created for each FBM and external field
device, provides a “holding place” for the software data associated with
that FBM or external field device.

2
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
1. Introduction B0400FD – Rev D

FBM Fieldbus Modules provide the interface between process sensors/actuators

and the Fieldbus in a standard I/A Series system. FBM220/221 is one of
many types of FBMs offered as part of the I/A Series system.

FCM The Fieldbus Communications Module is an interface which allows the

FBM220/221 (and other I/A Series DIN rail mounted FBMs) to commu-
nicate with the control station via the I/A Series 10 Mbps Ethernet trunk
Fieldbus. It converts the 10 Mbps Ethernet signals used by the control sta-
tion to 2 Mbps signals used by the FBM220/221, and vice versa.

Fieldbus With regard to the I/A Series system, this term applies in general to two
specific buses: the I/A Series 10 Mbps Ethernet trunk Fieldbus and the
I/A Series 2 Mbps Module Fieldbus. (Figure 1-1 shows how these buses
are used in the I/A Series communication network.) With regard to the
FOUNDATION fieldbus, the term fieldbus applies to the H1
FOUNDATION fieldbus used in conjunction with the FBM220/221.

FoxCAE Computer-Aided Engineering software, part of the Foxboro I/A Series sys-
tem, is used to configure control strategies.
H1 This is a 31.25 Kbps wire media (“Heap 1”) as defined by Part 2 of
IEC 61158 and ISA SP50.

LAS The Link Active Scheduler is a software functional unit controlling com-
munications in the Data Link Layer of the FOUNDATION fieldbus imple-
mentation of IEC 61158 and ISA SP50.

Letterbug This is an identifier for I/A Series control devices, particularly for Fieldbus
Modules (FBMs).

Macrocycle This is the repeating cycle of periodic and aperiodic communications in

the Data Link Layer of the FOUNDATION fieldbus implementation of
IEC 61158 and ISA SP50.

Parameter This is a named element in the data structure of a function block, ECB, or
I/A Series control block.

TA The Termination Assembly provides a means of attaching the

FBM220/221 to the H1 FOUNDATION fieldbus. As described previously,
the TA also provides the necessary power conversion for powering H1
field devices on the FOUNDATION fieldbus.

3
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 1. Introduction

4
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

2. Quick-Start Example 
This chapter provides an example configuration, which provides most of the information you
need to get your I/A Series system and F OUNDATION  fieldbus subsystem up and running in the
shortest possible time.
Figure 2-1 outlines a typical integration sequence for configuring combined I/A Series and
FOUNDATION fieldbus equipment. Following this figure is the procedure, whose steps are keyed
to the figure.

Start

7
Enable
1 4
Create H1 Device
Configure H1
Devices and Edit Communication
FBM220/221
Off-line
ECB
8
Create
2 5 DCI Blocks
Install
Place for All
I/A Series
FBM220/221 Device Points
System and
On-Line
H1 Bus
9
Verify H1
3 6 Device Data
Attach H1 Create
and Edit on the Block
Devices Detail Displays
to H1 Bus H1 Device
ECBs

End

Figure 2-1. Typical Fieldbus H1/Foxboro I/A Series Integration Process

NOTE
1. This procedure assumes that you are familiar with I/A Series system concepts,
FOUNDATION fieldbus concepts.
2. For more comprehensive information on installing and configuring the
FBM220/221 and its associated FOUNDATION fieldbus equipment, refer to the sub-
sequent chapters of this document.

5
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 2. Quick-Start Example

1. Configure the H1 field devices. Device configuration can be achieved in a number of

different ways. It is advised that devices be configured prior to installation in the field
to insure proper operation of the device. Device database information may be stored
 within Foxboro FoxCAE software to insure proper synchronization with the control
database. Online configuration via FoxCAE - I/A - FBM220/221 is detailed in Fox- 
CAE V5.0 Supplement for FOUNDATION fieldbus H1 Support (B0400DE).

a. If using
card andaassociated
personal computer interface,
software in install NT
the Windows the device configurator
based personal interface
computer per
instructions provided with the configurator. [NI-FBUS documents include
NI-FBUS Configurator User Manual (Part No. 321423-01), and Getting Started
with Your AT-FBUS and NI-FBUS Software for Windows NT (Part No.
321014C-01)].
b. Connect the FOUNDATION fieldbus network (H1 field devices) to the personal
computer containing the device configurator (refer to the H1 device user’s manual
for connection instructions). The connections are typically made using a
Relcom™ type termination block.
c.  At the Windows NT-based personal computer, and in accordance with instruc-
tions in the associated device configurator user documents, perform the following
operations:
♦ Configure the device configurator. For the interface port settings, change the
listed parameters, if required. Default parameters for the NI-FBUS configura-
tor and FBM220/221 interface are:
Parameter NI-FBUS FBM220/221
T1 0x40000 0x75300
T2 0x40000 0x2BF200
T3 0x30000 0x15F900

♦ Configure the device configurator network communication parameters by

entering the following parameters:
SLOT_TIME 8
PER_DLPDUPHL_OVERHEAD 6
MAX_RESPONSE_DELAY 10
FIRST_UNPOLLED_NODE_ID 37
THIS_LINK 0
MIN_INTER_PSU_DELAY 16

NUM_CONSEC_UNPOLLED_NOD 186
PREAMBLE_EXTENSION 2
POST_TRANS_GAP_EXTENSION 1
MAX_INTER_CHAN_SIGNAL_SKE 0
TIME_SYNC_CLASS1 4
1.
The FBM220/221 uses a TIME_SYNC_CLASS value of
5.

6
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
2. Quick-Start Example B0400FD – Rev D

♦ Download the device descriptor files (for example *.ffo and *.sym) for each
device into the device configurator. Place them in the appropriate manufac-
turer’s subdirectory in the personal computer.
♦ Start the device configurator.
d. Referring to the device parameter configuration tables presented under “H1 Field
Device Parameters” on page 23, use the device configurator to set the device block
parameters, taking note of the following:
♦ Before setting the device block parameters, select a unique tag (label)1 and
device address for the device. The device address must be higher (in order)
than the FBM device address, and must be in the range of 17 to 36 (decimal)
(11 to 24 hexadecimal). Enter the tag and address using the device
configurator.
♦ In addition to the settings listed under “H1 Field Device Parameters” on
page 23, for each block (resource, transducer, or function block) enter a
unique tag (using the device configurator) to define the block.
♦ The transducer block parameters are, for the most part, not writable. How-
ever, they must agree with the ranges selected for the function blocks. If they
are not in agreement, the values can be modified by making changes in the
function blocks.
♦ For each transmitter in the H1 FOUNDATION Fieldbus subsystem, you
must ensure that the backup Link Active Scheduler (LAS) and Link Master
(LM) capabilities (if present) are disabled. For specific instructions, refer to
“H1 Transmitter LAS/LM Disabling Procedure” on page 27.
e.  When H1 field device configuration is complete, disconnect the personal com-
puter from the devices.
2. Install the I/A Series system and FOUNDATION fieldbus H1 bus.
a. Install the major elements of the I/A Series system equipment as described in
System Equipment Installation  (B0193AC).
b. Install the FBM220/221, and its associated baseplate, FCM(s), and TA as
described in the DIN Rail Mounted FBM Subsystem User’s Guide  (B0400FA), and
under “Installation” on page 17 of this user guide.
c. Perform the system definition by referring to the “Configuration Information”
section of DIN Rail Mounted FBM Subsystem User’s Guide  (B0400FA).
d. Install the I/A Series software by referring to Software Installation  (B0193JG) or
Software Installation (Windows NT)  (B0400JG).
e. Make the H1 bus connections to the TA as described under “FOUNDATION
Fieldbus Cable Connections” on page 18 of this document. Also, make the power
connections to the TA as described under “Power Connections” on page 20.
3.  Attach the H1 field devices to the H1 bus.
Refer to the user guides for the devices in question and make the H1 bus connections
to the field devices that were configured off-line in Step 1.

1. For clarity, it is recommended that the device tag be the same as the NAME parameter of the associ-
ated ECB201.

7
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 2. Quick-Start Example

NOTE
It may be desirable at this point to attach the NI-FBUS monitor to the H1 bus for
troubleshooting or monitoring functions.

4. Create and edit the FBM220/221 ECB (ECB200).

NOTE
In this procedure, I/A Series Integrated Control Configurator (ICC) is used for con-
trol configuration. As an alternative, FoxCAE 4.0 can be used for this operation [refer
to Computer Aided Engineering for I/A Series Control Station Databases, FoxCAE
Version 4.0  (B0193MR)].

 Access the ICC and proceed as follows. [Refer to Integrated Control Configurator  
(B0193AV) for detailed instructions.]
a. On the ICC overview display for the CP60 in question (see Figure 2-2), select the
compound for the CP60, and then select View Blocks/ECBs in this Compound.

Figure 2-2. Typical Overview ICC Display for a Control Processor 60

b. On the display that appears in response to Step a, select  Insert New Block/ECB.
 An ECB “build” display appears, which allows you to build the ECB200 by enter-
ing (and editing) the required parameters. [Refer to Integrated Control Block
Descriptions  (B0193AX) for the parameter definitions.] Figure 2-3 shows a com-
pleted ECB200 “build” (editing) display.
c. Select Done at the bottom of the display when all required parameters are set.

8
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
2. Quick-Start Example B0400FD – Rev D

Key parameter:
Contains the name
used by the control
station to access
this ECB.

Key parameter:
Contains the letterbug of

the associated FBM.

Figure 2-3. Typical ECB200 (Parent) Editing Display

5. Place the FBM220/221 on-line.

 At the I/A Series system:
a.  Access the I/A Series System Management displays. [For detailed information,
refer to System Management Displays  (B0193JC) and/or the associated System
Management on-line Help].
b. Select the FBM220/221 ECB on the System Management displays, and click on
the Equipment Change button.
c. On the Equipment Change window for the FBM220/221, select GO ON-LINE.
6. Create and edit H1 device ECBs.
Create and edit the H1 device ECBs (ECB201s) in a manner similar to that for the
ECB200 (in Step 4). Refer to Integrated Control Block Descriptions  (B0193AX) for the
parameter definitions. Refer to the completed ECB201 editing display shown in
Figure 2-4, and the following NOTE.

NOTE
In the example shown in Figure 2-4, the PARENT parameter is entered as a full
path name: CP6SG5_ECB:SLOT06. As an alternative, an abbreviated form can be
used. For example, in this editing display:
 SLOT06 can be used, provided that the parent ECB (the ECB200) resides in the
 PRIMARY_ECB compound (CP6SG5_ECB), or
:SLOT06 can be used if the child ECB is to reside in the current compound (the
 same compound as the parent ECB).

9
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 2. Quick-Start Example

Key parameter: Configured with

name of FBM220 (parent) ECB.
(See note in text.)

Key parameter:
Contains the PD tag-
name of the field device
associated with this ECB.

Figure 2-4. Typical ECB201 (Child) Editing Display

7. Enable H1 device communication.

Enable communication between the FBM220/221 and the H1 device by accessing the
I/A Series System Management displays and proceeding as follows:
a. Select the FBM220/221 module on the System Management displays.
b. Select an H1 field device associated with the FBM220/221, and click on the
Equipment Change button.
c. On the Equipment Change window for the H1 field device, select ENABLE
COMMUNICATIONS.
d. Repeat for each additional H1 field device.

NOTE
Throughout this text, the term “DCI control blocks” (Distributed Control Interface
blocks) refers to a specific set of I/A Series control blocks used to interface the
I/A Series system with FOUNDATION fieldbus H1 field devices using digital com-
munications. The DCI control blocks include the following:
 - BIN (Binary Input)
 - BOUT (Binary Output)
 - RIN (Real Input)
 - ROUT (Real Output).
 Additional information is provided in Chapter 5 “Configuration Information”.

10
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
2. Quick-Start Example B0400FD – Rev D

8. Create DCI blocks for all device points.

The DCI blocks are created in the same general manner as the ECBs (see Steps 5
and 6). For detailed instructions, refer to Integrated Control Configurator  (B0193AV).
For parameter definitions, refer to Integrated Control Block Descriptions   (B0193AX).
 A completed DCI block editing display is shown in Figure 2-5.

Key parameter:
Indicates process
variable connected
to this block.

Key parameter:
Contains the pathname of the
ECB201 associated with the
field parameter to be accessed*.

*Once configured, the IOM_ID parameter cannot be readily changed. To change

the IOM_ID
base. parameter, you operation
(A “Delete/Undelete” must delete
willthe
notblock andthis
perform re-enter it into the data
function.)
Figure 2-5. Typical DCI Block Editing Display

9. Verify H1 device data on the block detail displays.

To do this, access the I/A Series FoxSelect compound/block overview utility. [Refer to
Process Operations and Displays  (B0193MM) for details.] Access the block detail dis-
play for each DCI block created, and confirm its data.
 You are now ready to configure the necessary compounds and blocks for the desired
control scheme. Refer to the following documents to perform these operations:
♦
DIN Rail Mounted FBM Subsystem User’s Guide  (B0400FA)
♦ Integrated Control Software Concepts  (B0193AW)
♦ Integrated Control Block Descriptions   (B0193AX).

11
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 2. Quick-Start Example

12
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

3. Product Application 
This chapter addresses various requirements and constraints relating to the connection of the
FBM220/221 to the F OUNDATION  Fieldbus, and its operation in conjunction with the CP60
and the H1 field devices.
 When planning for installation and operation of the FBM220/221 and the associated
FOUNDATION fieldbus network, the following factors must be considered:
♦ FBM220/221 functional and environmental constraints
♦ Field device configuration requirements
♦ Topologies –  which FOUNDATION fieldbus H1 topologies can be used, their charac-
teristics, and how they are powered.
♦ Control loop execution time.

Functional and Environmental Constraints

NOTE
The FBM220/221 serves as the Link Active Scheduler for the H1 bus and does not
support the simultaneous presence of any device which also attempts to act as the
LAS. Communication errors may result if another LAS is added to the bus. Exam-
ples would include both the National Instruments NI-FBUS Dialog System and
Fieldbus Configuration System.

FBM220/221
and I/A Series is designed
Fieldbus for use with theModules
Communication Control (FCMs).
ProcessorIt60connects
(CP60)toI/Athe
Series control
FCM(s) via station
a
2 Mbps Module Fieldbus, and coexists on this fieldbus with other Fieldbus Modules (FBMs).
Version 6.3 (or higher) I/A Series software is required for FBM220/221 operation.
Refer to the following documents for functional and environmental specifications relating to the
FBM220/221 modules and the associated TAs:
♦ F OUNDATION  fieldbus H1 Communication Interface Module (FBM220/221)
(PSS 21H-2Z20 B4)
♦ FBM220/221 TA – F OUNDATION  fieldbus Communication (PSS 21H-2W5 B4).

Field Device Configuration Requirements

 As used with the FBM220/221 in various FOUNDATION fieldbus topologies, block support in the
H1 field devices is limited to the AI, AO, DI, and DO function blocks. Also, in these
FBM220/221 based topologies, individual H1 devices cannot be configured to exchange data
among their AI, AO, DI, and DO function blocks. (Thus, closed-loop peer-to-peer control at the
H1 device level is not supported.)

13
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 3. Product Application

Prior to configuring ECBs and control blocks at the CP60 level, the H1 field device function
blocks must be configured in accordance with instructions contained in their respective device
user manuals. However, when configuring the function blocks in these devices, there are several
constraints which must be observed. Refer to “H1 Field Device Parameters” on page 23 for spe-
cific information.

Topologies
The FBM220/221 supports all of the various FOUNDATION fieldbus topologies. These topolo-
gies can be physically wired with the FBM220/221 placed at any location on the fieldbus.
 A FOUNDATION fieldbus system is made up of one or more segments. Each segment typically
contains several active field devices, with terminators located at the ends of the segment. Power for
the bus-powered devices is optionally derived from an I/A Series equipment power supply located
in the enclosure that houses the FBM220 or FBM221 (see Chapter 4). With this powering con-
figuration, dc-to-dc power conversion is performed at the TA(s) (see Figure 1-1). The user must
supply the power wiring to the TA.
Specific information on the various types of topologies and their implementation are beyond the
scope of this document. However, there are specific factors to be considered regarding the use of
FBM220/221 in conjunction with the FOUNDATION fieldbus:
♦  Allowable bus length
♦ Bus power supply requirements
♦ Bus power calculations
♦ Intrinsic safety.
These factors are addressed in the following subsections of this chapter.
For specific information on equipment (cabling, and so forth) used in the F OUNDATION fieldbus
topologies, refer to FOUNDATION fieldbus document AG-140, Wiring and Installation,
31.25 kbits/s Voltage Mode Wire Medium, Application Guide. For additional information on field-
bus implementation, refer to the listing of FOUNDATION fieldbus documents in the Preface
(page xii).

Bus Length Calculations

For a given FOUNDATION fieldbus topology, the bus length calculation is based on the following:
♦ Length of the trunk 
♦ Number of spurs
♦ Lengths of the spurs
♦
Type(s) of cable used
♦ The possible use of repeaters.
For detailed information, refer to FOUNDATION fieldbus document AG-140, Wiring and Installa- 
tion, 31.25 kbits/s Voltage Mode Wire Medium, Application Guide.

14
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
3. Product Application B0400FD – Rev D

NOTE
 As indicated in the IEC fieldbus standard, there are many rules regarding cable
lengths, cable types, terminators, and so on. However, only a few rules are absolute
(and those rules are identified in the FOUNDATION fieldbus document AG-140).
FOUNDATION fieldbus, like most digital communication schemes, is subject to per-
formance variations based on a large number of factors. Not all of these factors are
likely to be “worst case” simultaneously.

Bus Power Supply

 As indicated in Figure 1-1 (on page 1), power is supplied to the FOUNDATION fieldbus (and all
of its field devices) by a FOUNDATION fieldbus power converter built into the TA. The output
voltage of this power supply (to the FOUNDATION fieldbus) is 30 V dc (± 6%) @ 300 mA. The
power input source to the F OUNDATION fieldbus power supply (input to the TA) is user-selected,
and must be 24 V dc and have an output wattage capable of supplying all field devices on the bus
(see “Bus Power Calculations” below). An available source optionally used for this purpose is the
24 V dc power used to supply the baseplates in the DIN rail module subsystem rack (wiring to TA
supplied by user).

Bus Power Calculations

The FOUNDATION fieldbus power calculations are made based on the following factors:
♦ Power supply voltage (as described above, this is 30 V dc at the output of the TA)
♦ The resistance of each cable section
♦ The location of the power supply (TA) on the network 
♦ The power consumption of each device (considering worst-case inrush current and
lift-off voltage), and its location on the network.
For detailed information, refer to FOUNDATION fieldbus document AG-140, Wiring and Installa- 
tion, 31.25 kbits/s Voltage Mode Wire Medium, Application Guide.

Intrinsic Safety Considerations

The current FBM220/221 product, of itself, does not offer intrinsically safe operation. However,
intrinsic safety can be achieved through the use of barriers (such as those manufactured by the
Peperrel & Fuchs company) strategically designed into the FOUNDATION fieldbus network. For
additional information on designing an intrinsically safe network, refer to the FOUNDATION
fieldbus document AG-163, Application Guide for Intrinsic Safety .

NOTE
Field wiring from the TA to the H1 device(s) is not Class 1, Division 2 certified.

15
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 3. Product Application

Control Loop Execution Time

Control loop execution time calculations are used by process engineers for loop timing purposes.
Control loop execution time is a function of the FBM’s H1 macrocycle and the control processor’s
basic processing cycle (BPC). (The H1 Macrocycle and BPC operate asychronously.) Appendix A
“Control Loop Performance” describes how the H1 macrocycle is established by the
FBM220/221, and how loop execution time is derived using the H1 macrocycle calculation (and
BPC) figures.

16
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

4. Installation 
This chapter provides installation information for the FBM220/221 and its associated
termination assembly (TA) 
 A typical FBM220/221 installation is shown in Figure 4-1.

Clamp-On Ferrite Core

Fieldbus Communications
Modules (2)
Baseplate

 ®   ®   ®   ®   ® 

OperationalStatus  OperationalStatus  OperationalStatus  OperationalStatus  OperationalStatus 

Link Active  Link Active  Link Active  Fieldbus  Tx  Rx  Fieldbus  Tx  Rx 

Ethernet  Tx  Rx  Ethernet  Tx  Rx 

Module FBM220
ChannelIsolatedBaseplateI.D.
1 Communication,
No.
H11 2
FBM220
ChannelIsolated
1 Communication, H1
FBM220
ChannelIsolated
1 Communication, H1
FCM10E
Communication
10 Mbps Coaxial Ethernet to
FCM10E
Communication
10 Mbps Coaxial Ethernet to

Fieldbus
FieldbusFoundation
0 ON ON FieldbusFoundation FieldbusFoundation 2 Mbps Fieldbus 2 Mbps Fieldbus
P0917HA 1 OFF ON P0917HA P0917HA P0914YM P0914YM
2 ON OFF
3  ® 
OFF OFF  ®   ®   ®   ® 

FCM Identification

LeftModule RightModule

Termination
Cable
 ® 
P0914ZM UserDefined

nal  St at us
O pe   r at i o 

e 
Li nk  Ac t i v 

    8
 0     8
      I
       7
 A      0        N      P
 m 
 0     6        U      T
 2        5     0
 0  -      0
      4
 1,      0
 0      0        3
 2
 M       2
 B
 F      0
      1
     0

       P
      i     +
       P        i    -
      i     +        i
       P        i    -
      i     +        i
       P        i    -
      i     +        i
       P        i    -
      i
       P        i
    +
   -
       i
 C   L
      i     +        i
 C  8   L  +
 C   7 0
       P        i    -
      i     +        i

 C  0 6 0
       P
      i     +
       i
       i
   -
  L  +
       i    -
       i
 C   5   L  +
 C  0 4 0  +
 C  0  3
 C  0  2
 0  1
  B
  B  0 8
  N  -
  N
  N
  N  -
 -
Fieldbus
  B  0  7
  B  06
20
 -

FBMl Is2olated Module
  B  0 5
  B  0 4
  B  0 3
  B  0 2
 0 1
 A
 A  0 8 Channe unication, H1
m
 A  0  7 1 Com ation
 A
 A  06
 A  0 4
 3
 A  0
 0 5

Clamp-On P0917H
s Found
Fieldbu A
  ®  (FBM220/221)
 A  0 2
 0 1

Termination Ferrite Cores

Assembly

Figure 4-1. FBM220/221 and Termination Assembly Installation

 As shown in Figure 4-1, FBM220 or FBM221 mounts on the baseplate, and the termination
assembly (TA) connects to the baseplate by means of a Type 1 termination cable.
The part numbers of the FBM220 and FBM221 and the associated TAs are as follows:

FBM FBM P/N TA P/N

FBM220 P0917HA P0917RF
FBM221 P0917HB P0917RG

17
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 4. Installation

The termination cable (connecting between the TA and the baseplate) is available in the following
lengths:
0.5 m – P0916DA 
1.0 m – P0916DB
3.0 m – P0916DC
5.0 m – P0916DD

10.0 m
15.0 m–– P0916DF
P0916DE
20.0 m – P0916DG
25.0 m – P0916DH
30.0 m – P0916DJ
For FBM and TA installation instructions, refer to DIN Rail Mounted FBM Subsystem User’s
Guide  (B0400FA). In addition, for this product offering (FBM220/221), clamp-on ferrite cores
(EMI filters, Foxboro P/N BF162YG, supplied with the Termination Assembly) must be used as
follows:
♦  A single ferrite core for each baseplate must be installed on the Module Fieldbus cable
(Figure 4-1 on page 17). Install the ferrite core (packaged with the FBM220/221) on
the Module Fieldbus cable in close proximity to the baseplate cable connector (on the
baseplate containing the FBM220/221), as shown in Figure 4-1.
♦ Two ferrite cores must be installed on the termination cable. Install the two ferrite
cores (packaged with the FBM220/221) in close proximity to the termination cable
connector on the baseplate, as shown in Figure 4-1.
♦ Two ferrite cores must be installed on each pair of power input wires connecting to
the TA. Refer to “Power Connections” on page 20 for details.
♦ Ensure that the cable clamp is fully closed. The metal cores must be in direct contact
on each side of the ferrite and with each other to work correctly.

FOUNDATION Fieldbus Cable Connections

NOTE
For general information on FOUNDATION fieldbus cabling and topologies, refer to
FOUNDATION fieldbus document AG-140, Wiring and Installation, 31.25 kbits/s Volt- 
age Mode Wire Medium, Application Guide.

Make the FOUNDATION fieldbus cable connections in accordance with the labels provided on the
TA (see Figure 4-2). As indicated on the labels for the two types of TAs, FBM220 has one com-
munication channel, and FBM221 has four.
Note that, for each channel, dual connection terminals are provided for each cable connection
(that is, two 0+ points, two 0- points, and two sh points). This allows the FBM220/221 to be
located mid-bus, which requires two cable connections at each point for signal feed-through.

18
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
4. Installation B0400FD – Rev D

The FOUNDATION fieldbus cabling must be configured such that one of the signal wires has a
positive (+) voltage and the other a negative (-). Cables available from FOUNDATION fieldbus
cable manufacturers use the following color code:
+ = Orange
- = Blue
Cabling from other manufactures (with different color coding) may be used, provided the polarity
of the two signal wires is kept consistent throughout the cable network.
 
End-Bus Connection Mid-Bus Connection
FBM221, Foundation Fieldbus FBM221, Foundation Fieldbus
01 02 03 04 01 02 03 04

C C
O O
Label M
M
M
M
U U
N N
I I
C C
A A
T T
I I
O O
N N

o+ o+ o+ o+ o+ o+ o+ o+
o- o- o- o- o- o- o- o-
sh sh sh sh sh sh sh sh
Signal
Connection C C NOTE:
Points: FBM221 TA (shown)
C = o+ B B has four channels;
B = o- FBM220 TA has one
A = Shield A A channel.

To H1 To H1 To H1
Field Field Field
Devices Devices Devices
Figure 4-2. TA FOUNDATION Fieldbus Cable Connections

In addition to the cable connections, switches are provided (see Figure 4-3) to allow you to select
bus termination (in or out) and local powering of the bus (on/off). The switches are provided in
pairs, one pair for each channel. To access the switches, remove the component box covers by
squeezing the sides of the cover just below the cutout, and lifting it from the TA.
For each pair of switches, the left switch controls powering of the bus from the TA (isolated 30 V
dc power on/off ), and the right switch controls bus termination selection (terminating resistor
in/out). To switch the local power (from the TA) on, depress the upper part of the left switch. To

use the terminating resistor built into the TA, depress the upper part of the right switch.

19
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 4. Installation

Channel 1 switch pair:

1 2 1 - Power converter powering of fieldbus segment (on/off)*
2 - Terminating resistor (in/out)*
OFF Channel 2, 3, and 4 switch pairs (on FBM221 TA,
P0917RG) operate in a similar fashion.

Termination dc to dc
Cable Power Converter
Connector (1 of 4)

CABLE TYPE 1 C
 ® 
PRI SEC
Fieldbus Connections for
B +
Connections FBM IDENTIFICATION
Incoming Source
24 V Power**
A -

FBM220 TA (P0917RF) or FBM221 TA (P0917RG), covers removed.

* Press upper part of Switch 1 to enable power converter (on).
Press upper part of Switch 2 to use terminating resistor.
** Alternately, power to the H1 segment can be supplied other than via the TA.

Figure 4-3. TA Component Locations (Covers Removed)

Power Connections
Make the power connections in accordance with the labels provided on the TA (see Figure 4-4).
Provision is made for connecting redundant 24 V power sources, marked Primary and Secondary
on the label. (Redundancy control is provided internal to the TA, by diode ORing of the two
24 V inputs.) Extra 24 V + and - connection terminals are provided to allow for the possibility of
daisy-chaining of power connections, or for the possibility of using additional power supplies for
load sharing.

NOTE
1. If you choose to use a power converter other than that contained in the TA, it is
not necessary to supply power to the TA.
2. The dc-to-dc converters in the TAs support short circuit protection.

20
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
4. Installation B0400FD – Rev D

Install the clamp-on ferrite cores (Foxboro P/N BF162YG, packaged with the termination assem-
bly) on the power wires (see Figure 4-4 and Figure 4-5).
The power connections to the TA can originate from any 24 V dc source. Depending on specific
system requirements, the 24 V power supplies in the DIN rail FBM subsystem enclosures (those
used to power the baseplates) may be used, or additional power supplies can be attached the DIN
rail holding the TAs.

For information regarding on/off selection of the isolated power to the bus (using the TA
switches) refer to “FOUNDATION Fieldbus Cable Connections” on page 18. For information
on power supply loading, refer to “Bus Power Calculations” on page 15.
 

FBM220 - 2 Switches
FBM221 - 8 Switches

1 - Power Supply
2 - Terminating Resistor

1 2

OFF
Labeled
Cover
WARNING
For installation details see
document B0400FD

Primary Secondary
24 Vdc 24 Vdc
RETURN RETURN

+
2 Clamp-On Ferrite Cores
24 V
- (BF162 YG)*

From 24 V Secondary Power

Supply (if Required by Application)

From 24 V Primary Power Supply

* See next figure for

2 Clamp-On Ferrite Cores installation instructions.
(BF162 YG)*

Figure 4-4. TA FOUNDATION Fieldbus Power Connections

21
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 4. Installation

Install in close proximity

[approx. 50 mm (2 in)] to
connectors on TA

Nylon Cable Tie

(User Supplied)*

To 24 V
To TA
Power Supply

Nylon Cable Tie 2 Clamp-On Ferrite Cores

(User Supplied)* (EMI Filter) BF162YH

* The use of nylon cable ties (positioned as shown) is

recommended to keep the ferrite cores in place on the cable.

Figure 4-5. Installation of Ferrite Cores in Power Cables

22
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

5. Configuration Information 
This chapter provides information necessary for configuring the FBM220/221 and its
associated H1 device function blocks and DCI control blocks. This information is intended for
use with the Quick-Start Example presented in Chapter 2.
 With regard to the FBM220/221 and its associated equipment, configuration involves configur-
ing the H1 device function blocks, the associated DCI control blocks, and the ECBs representing
the FBM220/221 and H1 field devices. This chapter contains listings of the required parameter
settings for the H1 field devices, and related configuration information. For procedural informa-
tion, refer to Chapter 2 “Quick-Start Example”; for information on setting the ECB and DCI
block parameters, refer to Integrated Control Block Descriptions   (B0193AX).
Table 5-1 shows the maximum number of H1 devices/point connects allowed per FBM220/221.

Table 5-1. FBM220/221 Maximum Configuration Specifications

FBM Maximum Number  Maximum Number of 

Type of H1 Devices Allowed  Point Connects Allowed 
FBM220 16 24*
FBM221 32 (8 per port) 64 total per FBM (16 per port)*
*Note: Each analog or discrete output requires two point connects, one for the output and one
for the readback.

H1 Field Device Parameters

The H1 field device function blocks are configured off-line. (Neither the I/A Series control sta-
tion nor the FBM220/221 is involved in this process.) Table 5-2 through Table 5-7 list typical
parameters and required parameter settings for configuring the H1 device blocks. (This informa-
tion is referenced in the Quick-Start example in Chapter 2.) For additional information, refer to
the user manuals for the devices, and the following FOUNDATION fieldbus documents:
FF-890-1.3 Function Block Application Process  –  Part 1
FF-891-1.4 Function Block Application Process  –  Part 2.

NOTE
1. Before setting the device block parameters, a unique tag (label) and address must
be entered for the device. Refer to the procedure on page 7 for additional
information.
2. The terminology used in the following tables reflects that used in document
FF-891-1.4 Function Block Application Process  –  Part 2. The terminology used in con-
 junction with your device configurator may differ.

23
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

Table 5-2. Transducer Block Parameters

Required Settings
Parameters* (for I/A Series Operation) Notes
MODE_BLK
  PERMITTED (See “Notes” column.) For PERMITTED mode, ensure that
  TARGET Auto OOS, MAN, and AUTO are selectable
  NORMAL Auto from the list of possible values.
TARGET_ERROR**
  DESCRIPTION Blank Blank means “No Error” condition.
BLOCK_ERROR 0X0000 “No Error” condition.
*The parameters listed are example parameters, which generally apply to pressure transmitters.
 See NOTE on p. 23 regarding the terminology used.
**The TARGET_ERROR parameter applies only to Foxboro pressure transmitters.

Table 5-3. Resource Block Parameters

Required Settings
Parameters* (for I/A Series Operation) Notes
MODE_BLK
  PERMITTED MODE Auto, Out-of-Service Required
  TARGET MODE Auto Required
FEATURE_SEL
  Octet Text Strings ASCII ISO 646/2375 compliant

  Reports Option Not supported; do not use Disables Alert Reports.

  Fault State Partially supported (see “Notes” col- Supports Fail-safe detection at the
umn) device level upon loss of communica-
tion between the field device and
FBM220/221.
Fail-safe logic using the
SET_FSTATE/ CLR_FSTATE param-
eters is not supported.

Write Lock Not supported; do not use Disables Write Lock

Direct Write to Output Hdwr. Not supported; do not use

GRANT_DENY Not supported; do not use

SHED_RCAS Not supported; do not use
SHED_ROUT Not supported; do not use
*The parameters listed are example parameters, which are generally applicable to most H1 devices.

See NOTE on page 23 regarding the terminology used.

24
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

Table 5-4. Analog Input (AI) Block Parameters

Required Settings
Parameters* (for I/A Series Operation) Notes
MODE_BLK
  PERMITTED Auto, Out-of- Service Required
  TARGET Auto Required
SIMULATE Not supported; do not use Use SIMOPT in CP60 RIN block.
OUT_SCALE
 EU@100% Same value as the HSCI1 in CP60
  RIN block (not enforced by I/A).
EU@0% Same value as the LSCI1 in CP60
RIN block (not enforced by I/A).
GRANT_DENY Not supported; do not use
IO_OPTS
 Bit 10: Low cutoff Yes/No User option; no constraint.
STATUS_OPTS
  Bit 3: Propagate Fail Forward Yes Option required.
Bit 6: Uncertain if Limited Yes/No User option; no constraint.
  Bit 7: Bad if Limited Yes/No User option; no constraint.
*The parameters listed are example parameters, which are generally applicable to most H1 devices.
See NOTE on page 23 regarding the terminology used.

Note: Bit 0 is the least significant, low-order bit.

Table 5-5. Analog Output (AO) Block Parameters

Required Settings
Parameters* (for I/A Series Operation) Notes
MODE_BLK

   TARGET
PERMITTED Cascade,
Cascade, Auto,
Auto Out-of-Service Required
Required for
for normal
normal operation.
operation.
SIMULATE Not supported; do not use Use the SIMOPT in CP60 ROUT
block.
PV_SCALE
 EU@100% Same value as the HSCO1 in CP60
ROUT block (not enforced by I/A)
 EU@0% Same value as the LSCO1 in CP60
  ROUT block (not enforced by I/A)
GRANT_DENY Not supported; do not use
IO_OPTS**
  Bit 1: SP-PV Track in Manual Not supported; do not use
Bit 3: SP-PV Track in LO Yes Option required.
  Bit 4: SP Track retained target Not supported; do not use
  Bit 5: Increase to Close Not supported; do not use Use the REVOPT in CP ROUT
  block.
Bit 6: FS to Value Yes/No No constraint; see note below.
  Bit 7: Use FS value on Restart Yes/No No constraint; see note below.
  Bit 8: Target to Man if FS Asserted Not supported; do not use
  Bit 9: Use PV for BKCAL_OUT Yes/No If this option is used, the OUTOPT
option in the CP60 ROUT block
must also be set (not enforced by
I/A).

25
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

Table 5-5. Analog Output (AO) Block Parameters (Continued)

Required Settings
Parameters* (for I/A Series Operation) Notes
STATUS_OPTS
  Bit 4: Propagate Fail Backward Yes Option required.
SP_RATE_DN 0 Value of 0 is required.

SP_RATE_UP 0 Value of 0 is required.

SP_HI_LIM Same value as the HSCO1 in CP60 Use CLPOPT with HOLIM in CP
ROUT block (not enforced by I/A) ROUT block.
SP_LO_LIM Same value as the LSCO1 in CP60 Use CLPOPT with LOLIM in CP
ROUT block (not enforced by I/A) ROUT block.
SHED_OPT Set to 1 (normal shed, normal return) Option required.
FSTATE_TIME No constraints See Note below.
*The parameters listed are example parameters, which are generally applicable to most H1 devices.
See NOTE on page 23 regarding the terminology used.
Notes:
1. Bit 0 is the least significant, low-order bit.
2. The Fault State action (IO_OPTs Bit 6) requires the FSTATE_TIME parameter to be configured in the AO function
block. FSTATE_TIME is not settable by FBM220/221. In addition, the Fault State option in the FEATURES_SEL
parameter must be configured in the Resource block.

Table 5-6. Discrete Input (DI) Block Parameters

Required Settings
Parameters* (for I/A Series Operation) Notes
MODE_BLK
  PERMITTED Auto, Out-of-Service Required.
  TARGET Auto Required.
SIMULATE_D Not supported; do not use. Use the SIMOPT in CP60 BIN block.
GRANT_DENY Not supported; do not use.
IO_OPTS
 Bit 0: Invert Yes/No User option; no constraint.
STATUS_OPTS
  Bit 3: Propagate Fault Forward Yes Option required.
*The parameters listed are example parameters, which are generally applicable to most H1 devices.
See NOTE on page 23 regarding the terminology used.
Note: Bit 0 is the least significant, low-order bit.

Table 5-7. Discrete Output (DO) Block Parameters

Required Settings

Parameters* (for I/A Series Operation) Notes

MODE_BLK
  PERMITTED Cascade, Auto, Out-of-Service Required for normal operation.
  TARGET Cascade, Auto Required for normal operation.
SIMULATE_D Not supported; do not use Use SIMOPT in CP60 BOUT
block.
GRANT_DENY Not supported; do not use

26
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

Table 5-7. Discrete Output (DO) Block Parameters (Continued)

Required Settings
Parameters* (for I/A Series Operation) Notes
IO_OPTS
  Bit 0: Invert Yes/No User option; no constraint
  Bit 1: SP-PV Track in Manual Not supported; do not use
Bit 3: SP-PV Track in LO Yes Option required.
  Bit 4: SP Track retained target Not supported; do not use
  Bit 6: FS to Value Yes/No No constraint; see note below.
  Bit 7: Use FS value on Restart Yes/No No constraint; see note below.
  Bit 8: Target to Man if FS Asserted Not supported; do not use
  Bit 9: Use PV for BKCAL_OUT Not supported; do not use
STATUS_OPTS
  Bit 4: Propagate Fault Backward Yes Option required.
SHED_OPT Set to1 (normal shed, normal return) Option required.
FSTATE_TIME No constraints See note below.
*The parameters listed are example parameters, which are generally applicable to most H1 devices.
See NOTE on page 23 regarding the terminology used.
Notes:
1. Bit 0 is the least significant, low-order bit.
2. The Fault State action (IO_OPTs Bit 6) requires the FSTATE_TIME parameter to be configured in the DO function
block. FSTATE_TIME is not settable by FBM220/221. In addition, the Fault State option in the FEATURES_SEL
parameter must be configured in the Resource block.

H1 Transmitter LAS/LM Disabling Procedure

NOTE
This procedure is referenced as part of the “Quick-Start Example” in Chapter 2.
(See the last bulleted item on page 7.)

For proper operation of any transmitter in the H1 FOUNDATION Fieldbus subsystem, it is

necessary to disable the backup Link Active Scheduler (LAS) and Link Master (LM) capabilities
in each transmitter. This must be done to prevent a transmitter from replacing the FBM220/221
as Link Active Scheduler and/or Link Master on the Foundation Fieldbus network should the
FBM220/221 become disabled (or be physically removed). This procedure only applies to trans-
mitters that have backup LAS or LM capability, and in which this capability is enabled. Also, the
procedure assumes that the NI-FBUS (National Instruments-Fieldbus) Configurator is being used
to configure the transmitter. (For other H1 device configurators, refer to the associated user
guide.)
First, determine whether or not the LAS or LM feature is, in fact, enabled for the subject
transmitter: In the NI-FBUS Configurator Project Window observe the icons representing the
transmitters. If an icon has the letters LM (in red) appearing immediately above it, the LAS or LM
capability is enabled. If LM does not appear above the icon, these capabilities are either disabled or
not present in the transmitter.
To disable the LAS or LM capability in a transmitter, proceed as follows:
1. In the NI-FBUS Configurator application Project Window screen, with the transmit-
ter icon and associated blocks displayed, right-click on the blank space within the
 window and select Advanced View  . The display for the transmitter under configura-
tion now shows an FB branch and an MIB (Management Information Base) branch,
each labeled with blue lettering.

27
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

2. Expand the MIB branch by clicking on the + box associated with it.

3. Scroll down to the Boot_Operat_Functional_Class parameter, which is second from
the bottom in the list.
4. Double-click on the Boot_Operat_Functional_Class parameter, opening the MIB win-
dow with the Boot_Operat_Functional_Class parameter selected. (Note: If this trans-
mitter does not have backup LAS or LM capability enabled, this parameter will not
appear in the window. In this case, disregard this LAS/LM disabling procedure and
continue with configuration of the remaining transmitters.)
5. Change the Boot_Operat_Functional_Class parameter value from 2 to 1 and click on
Write Changes. LAS/LM capability is now disabled.
6. Close the MIB  window by clicking on the “x” box in the upper-right corner. Right-
click on a blank space in the Project Window, and click on Advanced View  to uncheck
this view. The original tree should now be displayed (the same as when the transmitter
 was first displayed on the Project Window). Note, however, that LM still appears over
the transmitter icon.
7. Disconnect power from the transmitter and reconnect it. When the transmitter icon
now appears, the LM no longer exists (for this transmitter) indicating that the capabil-
ity has been disabled.

Block Interconnections
In order for process control operations to be performed, equipment control blocks (ECBs), DCI
control blocks, and other I/A Series control blocks (for control scheme implementation) must be
created and configured by you. Figure 5-1 shows the required ECBs and illustrates the par-
ent/child relationship that exists between the H1 device ECBs (ECB201s) and the FBM220/221
ECB (ECB200).

I/A Series
Control Station

ECB110
(FCM)

ECB200
(FBM220/221)

ECB201 ECB201
(H1 Device) (H1 Device)

Figure 5-1. ECB Hierarchy

 As indicated in Figure 5-1, an ECB200 must be configured for the FBM220/221, and for each
H1 field device associated with the FBM220/221, a child ECB201 must be configured and con-
nected to the (parent) ECB200. Each parent ECB200 can support any number of child ECB201

28
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

blocks, subject only to the availability of I/A Series control station memory. The ECB200 and
ECB201 parameters are defined in Integrated Control Block Descriptions   (B0193AX).
Figure 5-2 shows the general flow of data between the field device function blocks and the DCI
blocks, and illustrates the one-to-one functional relationship that exists between these two block
types.

Function Blocks, I/A Series Control Software

Inside Field Devices
(See Note) DCI Blocks
AI
.OUT RIN

AO
.CAS_IN
ROUT
.BKCAL_OUT FBM220/221 To/from other
(Interface
Signal blocks
etc.) in (PIDA,
the
DI Control) control scheme
.OUT_D BIN

DO
.CAS_IN_D
BOUT
.BKCAL_OUT_D

NOTE:
A field device may contain multiple function blocks, which can be accessed via multiple
associated DCI control blocks.
Figure 5-2. Block/DCI Block Functional Relationships

Figure 5-3 shows the user-configured connections between the various blocks in a typical control
system. In this figure, two AI function blocks in the same H1 field device are accessed by corre-
sponding RIN DCI blocks. Configuration for other types of function blocks (AO, DI, and DO)
and corresponding DCI blocks (ROUT, BIN, and BOUT) is similar (similar interconnections
between blocks).

29
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

ECB200 ECB201

Name SLOT03 Name PT_100

Dev_ID SLOT03 Parent :SLOT03
Por tex 0= por t 1 Dev_ID PT_100
DevAddr Not Used
Dev Name PT_100 RIN #1
H1 Device Name PT_100
AI Block #1 IOMID CP6SG5_ECB:PT_100
PNT_No PT_100A1
PD_Tag*
Function Block Tag*

RIN #2

Name TT_100
IOMID CP6SG5_ECB:PT_100
AI Block #2
PNT_No TT_100A1
PD_Tag*
Function Block Tag*

* Syntax must conform to that used in the Foxboro ICC or FoxCAE

configurator, regarding upper/lower case, character string length, etc.

Figure 5-3. Typical User-Configured Block Interconnections

The DCI blocks provide device resident parameter access for the I/A Series control station. As
indicated in Figure 5-2, for each AI, AO, DI, or DO device function block that is to be interfaced

to the I/Ablock.
ECB201 SeriesThe
system,
RINa and
DCIBINblock mustconnect
blocks be configured and connected
to the primary output to the appropriate
parameters of AI and
DI function blocks (respectively) in the H1 field devices. Likewise, the ROUT and BOUT blocks
connect to the primary input parameters of AO and DO function blocks (respectively) in the H1
field devices.

NOTE
Connection of duplicate RIN blocks to the same device AI block is not supported.

Parameter access between the FBM220/221 and the H1 devices is accomplished by the
FBM220/221 through the H1 publish/subscribe data transfer mechanism, which is described in
 Appendix A “Control Loop Performance”.
Table 5-8 lists key parameters, which specify the linkages between blocks/ECBs or contain the
required transferable values.

30
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

Table 5-8. Key Parameters

Block/ECB Parameter Usage Typical Syntax

AI, AO, DI, and DO OUT, OUT_D Contain values (analog, digital) to be N/A
function blocks accessed from the external device.
CAS_IN, Contain values (analog, digital) trans- N/A

CAS_IN_D ferred to the field device.

AO and DO function BKCAL_OUT, Provide read-back values (analog, N/A
blocks BKCAL_OUT_D digital) and associated status; used
for output confirmation purposes.
ECB201 PARENT Contains the user-configured path- :SLOT03
name of the ECB200 (FBM220/221) (See Note below)
hosting this field device.
DVNAME Contains the user-configured PD tag- PT_100
name of the field device associated
with this ECB201. Used by the
FBM220/221 to validate the identity
of the field device when the device
connection is made. NOTE: Lower-

case letters for

not allowed andthis
special characters
parameter.
ECB200 NAME A user-configured name used by the SLOT03
control station to access this ECB.
DEV_ID User-configured letterbug of the FBM. SLOT03
It is copied into the DEV_ID parame- (See Note below)
ter of each DCI I/O block connected
to this ECB200.
BIN, BOUT, RIN, IOMID Contains the user-configured path- CP6SG5_ECB:PT_100
ROUT name of the ECB201 (device ECB)
associated with the field parameter to
be accessed by this block.
PNT_NO Contains the Function Block Tag in PT_100AI
the external device with which the
DCI block input/output is to be associ-
ated.
BOUT, ROUT INI_PT A configurable string that specifies <Function Block Name>.OUT_D
the point address of an optional Bool-
ean input connection in the BOUT or
ROUT block. If INI_PT is used, the
block output tracks the readback
value when the input Boolean value is
set.
NOTE: The first four characters of the FBM letterbug (SLOT) are created per user preference; the
last two (05) reflect the physical position of the FBM (and its associated baseplate). Refer to DIN
Rail Mounted FBM Subsystem User’s Guide  (B0400FA) for additional information.

Configuration Procedures
Procedures for configuring the subsystem ECBs and control blocks are covered in Steps 4 through
9 of the Quick Start Example in Chapter 2. These steps involve creating and editing the required
ECBs, creating DCI blocks for all device points, and creating the necessary control blocks (PID,
and so forth) for closed-loop control. The ECB200 and ECB201 parameters and parameters for
all control blocks (including DCI blocks) are defined in Integrated Control Block Descriptions
(B0193AX).

31
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

Block Processing
The following is an overview of block processing (and data read/write) operations.

NOTE
Scheduling of block processing depends on the period/phase of the ECB or control
block. For proper operation, you must synchronize the associated ECB and control
block processing, if required, by configuring these parameters appropriately.

Processing of the ECBs and control blocks is performed in three general phases.
1. ECBs scheduled to be processed are executed to read fresh inputs:

 When a parent or child ECB is processed, its DCI linked list is examined. For each
DCI block ready to be run in that BPC, its DCI connection requests are added to a
read list for that ECB.

 When the read list is complete, a Read_Data message is sent to the FBM220/221 to
retrieve the current data contained in the DCI connection records in the FBM. (If
necessary, multiple messages are used to retrieve all data required by the DCI blocks
for that BPC). All read list data is moved into the DCI connection records in the DCI
blocks as it is retrieved.
2. Control blocks scheduled to be processed are executed.

 When all ECBs have been processed, the control blocks are processed. When the DCI
blocks are processed, all DCI connection data is processed. During this processing, the
DCI blocks set write request flags in the DCI connection records for any outputs that
need to be written to the field devices.

3. ECBs scheduled to be processed, and containing fresh outputs to be written, are exe-
cuted.

 When all control blocks have been processed, the ECBs are processed once again to
drive the field outputs that have been changed in that BPC, in the control output
blocks. When a DCI parent or child ECB is processed, its linked list is examined once
again. For each DCI connection record with a pending write request flag, a write list is
generated.

 When the write list is complete, a Write_Data message is sent to the FBM220/221 to
 write the current output data contained in the DCI connection records in the control
station. (If necessary, multiple messages are used to write all data requested by the
DCI blocks for that BPC).

32
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

DCI Block Functions

Some key DCI block functions that can be selected by parameter settings are described in the fol-
lowing paragraphs. (For more specific information on these functions, refer to the RIN, ROUT,
BIN and BOUT DCI block descriptions in Integrated Control Block Descriptions   (B0193AX).

Periodic/Change-Driven Execution
 All DCI blocks are executed periodically according to their PERIOD/PHASE parameter configu-
ration. The ROUT and BOUT blocks normally set write requests to the FBM only when the out-
put value changes. If the secondary loop timer (SECTIM) is configured nonzero, write requests
are also set if the timer expires between output changes.

Auto/Manual Mode Operation

 All DCI blocks support the auto/manual mode of operation. This allows the operator to manually
substitute the inputs in the BIN and RIN blocks, and to manually drive the BOUT and ROUT
outputs.

Simulation Mode
The simulation mode is supported in all DCI blocks. When the SIMOPT parameter is set, the
DCI connections are not used. In the BIN and RIN blocks, the input is provided by a separate,
configurable input parameter. In the BOUT and ROUT blocks, confirmation of the output value
change is simulated automatically.

Time Stamping
 All DCI block field input and field output value parameters are time stamped. A separate time
stamp parameter, TSTAMP, is provided in each DCI block for this purpose. The timestamp is
provided by the FBM220/221 for input parameters and by the I/A Series control station for out-
put parameters. It is updated when the input value is changed in the FBM220/221, and when the
output value is changed in the I/A Series control station.
 When simulation mode is used, all time stamps are provided by the control station.

Signal Conditioning and Linear Scaling

Signal conditioning and linear scaling of analog inputs/outputs can be configured in the RIN and
ROUT blocks. The SCI and SCO parameters can be used to specify any of the standard signal
conditioning algorithms supported by the I/A Series control station, except thermocouple and
RTD conversions. For a description of the SCI conditioning algorithms, refer to the appendix
associated with the RIN block [in Integrated Control Block Descriptions  (B0193AX)]. For a

description ofDescriptions 
Control Block the SCO conditioning algorithms, refer to the ROUT block [also in Integrated
  (B0193AX)].

Input Limiting
The input values of the RIN block are constrained by the engineering range (HSCI1/LSCI1) con-
figured in the block. If the input value is out-of-range, it is clamped to the high/low range value,
and the corresponding LHI/LLO status bit is set in the value record.

33
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

Confirmed Outputs
The outputs of the BOUT and ROUT blocks are confirmed by a readback of the actual function
block value. When an output is changed by I/A Series in either of these blocks, it is stored in a
request location that is part of the output value record in the block. [In I/A Series terminology,
this type of output is referred to as a “Shadow” output and is reflected in the Shadow status bit
(Bit 12) in the value record.] The actual output value of the DCI block is not updated until con-
firmation of the requested change at the field device is received.
The request value is written to the FBM220/221, which publishes this value as the CAS_IN (or
CAS_IN_D) input to the field device during the next H1 function block macrocycle. When the
 AO (or DO) function block runs, it uses the published value and stores it into its BKCAL_OUT
(or BKCAL_OUT_D) output parameter. This value is then published back to the FBM220/221
by the field device. The FBM220/221 then updates the readback value in the DCI output con-
nection record with this value.
On the next BOUT (or ROUT) block cycle, the block output value is updated in the I/A Series
control station with the readback value from the FBM220/221, thus completing confirmation of
the change.

Output Clamping
The output value of the ROUT block is constrained by the limit values (HOLIM/LOLIM) con-
figured in the block. The limit values are constrained by the engineering range (HSCO1/LSCO1)
configured in the block. If the output value exceeds its limiting constraints, it is clamped to the
high/low value, and the corresponding LHI/ LLO status bit is set in the value record.

Output Initialization
The output value of a BOUT or ROUT block initializes to the readback value in each of the fol-
lowing cases:
♦
 When the compound containing the block is turned on
♦  When the block is installed and runs its first cycle
♦  When control station/FBM communication recovers from a failure condition
♦  When the Initialization Input (INI_PT), if used, is set
♦  When the DCI connection record indicates an Initialization Request (IR), Local
Override (LO), Not Invited (NI), or Open Loop (LHI and LLO) condition in the AO
(or DO) function block in the field device.
The readback value contains the most recent value of the BKCAL_OUT (or BKCAL_OUT_D)
parameter in the AO (or DO) function block.

Cascade Initialization
Upstream logic in a cascade is initialized by a BOUT or ROUT block in each of the following
cases:
♦  When the DCI block initializes
♦  When the DCI block mode changes from Manual to Auto mode
♦  When the DCI connection record indicates an Initialization Request (IR) from the
 AO (or DO) function block in the field device

34
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

♦  When control station/FBM communication recovers from a failure condition

♦  When the readback value transitions from Bad and/or Out-of-Service status to Good
status
♦  When the Initialization Input (INI_PT), if used, is cleared.

Fail-Safe Actions
Fail-safe actions are performed in accordance with specific parameters set in ECB200, and in the
ROUT and BOUT DCI blocks. In ECB200, the following parameters control fail-safe actions:
♦ FSENAB – Fail-Safe Enable, when true, activates the FSDLAY timer to detect a com-
munication failure from the control station, and start fail-safe action in the FBM. The
FSENAB setting is downloaded to the FBM220/221 when the FBM220/221 is
rebooted. It is used by the FBM220/221 to enable/disable the logic to assert fail-safe
action when a loss of control station communication is detected, or when a control
station fail-safe request is received.
♦ FSDLAY – Fail-Safe Delay is a communications fail timer. When enabled by
FSENAB, it specifies the length of time (in units of 0.01 seconds) that the FBM can
be without communication from the control station before taking fail-safe action. If
the Fail-Safe On Commfail bit is set in the FSOPTN parameter of the output control
block (ROUT or BOUT), the FBM sets the Initialize Fail-safe bit in the status of the
OUT parameter of the associated AO function block. When this value is next received
by the connected device, the device asserts fail-safe and drives its output to the fail-safe
value.

For example, the default value of 1000 in FSDLAY causes the FBM to wait 10 sec-
onds between read/write messages before going to the Fail-safe state (provided
FSENAB is configured true).
In the ROUT and BOUT DCI blocks, the following parameters control fail-safe actions:
♦ FSOPTN – Fail-safe Option is a configurable option that specifies the fail-safe condi-
tions and action to be taken in the FBM for an output point in a ROUT block:
♦  Assert fail-safe if input/measurement error.
♦ Set/clear fail-safe when SETFS input is set/cleared.
♦  Assert fail-safe if control station-to-FBM communication failure was detected by
the FBM.
Combinations of these conditions for fail-safe can be specified.
♦ SETFS – Set Fail-safe Request is a settable Boolean parameter that requests fail-safe
action to be set/reset by the FBM and/or field device for the specific output value of
the ROUT/BOUT block.
♦ FSOUT – Fail-safe Real Output (ROUT block only) specifies the real fail-safe value
that is to be used by the external device when any condition specified in FSOPTN
exists.
♦ FSCOUT – Fail-safe Boolean Output (BOUT block only) specifies the binary fail-
safe value that is to be used by the external device when any condition specified in
FSOPTN exists.

35
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

The fail-safe options configured in the DCI output blocks are downloaded into the FBM220/221
 when the DCI output connection is established. If any of the FSOPTN fail-safe options are set,
the FBM220/221 writes the fail-safe value to the AO (or DO) function block in the field device.
Fail-safe action can be triggered automatically for each output when loss of control station com-
munication is detected by the FBM220/221. If FSENAB is set, and if the Assert fail-safe if
control station to FBM communication failure option in FSOPTN is set, the FBM220/221

initializes
from a fail-safe
the control timerwhen
station for that
theconnection
FBM220/221to the Fail-Safe Delay
is rebooted. (FSDLAY)
The fail-safe timervalue downloaded
counts down
between receipt of Read_Data  and Write_Data messages. When either message is received for an
output connection, its fail-safe timer is reset to the FSDLAY value. If the fail-safe timer expires,
FBM220/221 sets the Initialize Fault State (IFS) status bit of the OUT (or OUT_D) parameter
in its AO (or DO) function block connected to the CAS_IN (or CAS_IN_D) parameter of the
 AO (or DO) function block in the field device. When the FBM220/221 next publishes this out-
put value to the field device, the field device asserts fail-safe by driving the AO (or DO) output to
the fail-safe value specified by FSOUT/FSCOUT in the function block.
Fail-safe action can also be triggered by either of two events in a BOUT or ROUT block: when
the fail-safe request parameter (SETFS) is toggled or, if the error option (EROPT) is configured,
 when the status of the primary input in the block goes bad (or becomes good). When either event
occurs, a Write_Data message is sent to the FBM220/221, with the Fail-safe Request bit set (or
cleared) cleared in the message. If FSENAB is set, and if the Set/clear fail-safe when SETFS
input is set/cleared option in FSOPTN is set, the FBM220/221 sets the Initialize Fault State
(IFS) status bit of the OUT parameter in its AO function block connected to the CAS_IN (or
CAS_IN_D) parameter of the AO (or DO) function block in the field device. When
FBM220/221 next publishes this output value to the field device, the field device asserts fail-safe
by driving the AO (or DO) output to the fail-safe value specified by FSOUT/FSCOUT in the
function block.
 When communication with the I/A Series control station is restored, the fail-safe timers are auto-
matically reset to full value by the first Read Data (or Write Data) message to each connection. If
the fail-safe had been previously asserted by a request from the control station, and the fail-safe
condition still exists in the control station, the Write Data message causes the IFS status bit to
remain set in the function block. Otherwise, the Write Data message causes the IFS status bit to
be cleared.

Heartbeat Message Handling

The CP60 sends a heartbeat message to the FBM220/221 every basic processing cycle (BPC) con-
figured in the I/A Series control station. This message provides the mechanism to support the fol-
lowing functions:
♦ Synchronization of the FBM220/221 time and date with the I/A Series system time
and date
♦ Time stamping of H1 device function block data.
The existing heartbeat message contains the latest I/A Series system date and time, maintained by
the I/A Series control station. The format of this field is a single, 6-byte integer containing the rel-
ative time since Jan.1, 1970 (the so-called UNIX ® time base) in 10 millisecond increments. This
time is updated in the control station periodically by the I/A Series system timekeeper.

36
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

The FBM220/221 converts this field into an appropriate date and time required by the field
devices. The FBM220/221 then uses this time to reset the time base used to provide the millisec-
onds-since-midnight time stamp of data received from the H1 field devices.

Control Schemes Using DCI Blocks

Thestandard
the DCI blocks can functions,
control be integrated
the into many
control different
station I/A Series
supports Securecontrol schemes.
Supervisory In addition
Control (SSC) to
and Embedded Multi-Variable Control (MVC) of loops connected to F OUNDATION fieldbus H1
 AI/AO function blocks. Examples of simple cascade, SSC, and MVC control configurations using
DCI blocks are illustrated in Figure 5-4, Figure 5-5, and Figure 5-6.

PARENT ECB200 
(FBM220/221) 

CHILD ECB201 CHILD ECB201 CHILD ECB201

(H1 Transmitter)  (H1 Transmitter)  (H1 Positioner) 

PARENT PARENT PARENT

RIN Block  PIDA Block 

IOM_ID
(1) PNT_NO
MEAS MEAS
MEALM  SPT
RINP OUT
Block  (2)
BCALCI
MEAS

RIN Block 
IOM_ID PIDA Block  ROUT Block 
(1) PNT_NO IOM_ID
MEAS MEAS PNT_NO (1)
MEALM  RSP
RINP Block  (2) BCALCO
OUT MEAS OUT
MEAS BCALCI BCALCO

MEALM 
Notes: Block (2)
(1) PNT_NO = <Function Block Tag Name>.<Parameter>
(2) MEALM blocks are used to perform BAD alarming. MEAS
Figure 5-4. Simple Cascade Configuration

37
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

PARENT ECB200 
(FBM220/221) 

CHILD ECB201 CHILD ECB201 CHILD ECB201

(H1 Transmitter)  (H1 Transmitter)  (H1 Positioner) 
PARENT PARENT PARENT

RIN Block  PIDA Block 

IOM_ID
(1) PNT_NO
MEAS MEAS
MEALM  SPT
RINP OUT
Block (2)
BCALCI
MEAS

RIN Block 
IOM_ID PIDA Block  ROUT Block 
(1) PNT_NO IOM_ID
MEAS MEAS PNT_NO (1)
MEALM  RSP
RINP Block (2) BCALCO
OUT MEAS OUT
MEAS BCALCI BCALCO
SUP_IN
SUPBCO
MEALM 
Block (2)
MEAS

Supervisory Control SOLARIS/NT WORKSTATION

Application
Notes:
(1) PNT_NO = <Function Block Tag Name>.<Parameter>
(2) MEALM blocks are used to perform BAD alarming.

Figure 5-5. Supervisory Control Configuration

38
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

PARENT ECB200 
(FBM220/221) 

CHILD ECB201 CHILD ECB201 CHILD ECB201

(H1 Transmitter)  (H1 Transmitter)  (H1 Positioner) 
PARENT PARENT PARENT

RIN Block  PIDA Block 

IOM_ID
(1) PNT_NO
MEAS MEAS
MEALM  SPT
RINP OUT
Block (2)
BCALCI
MEAS

RINIOM_ID
Block  PIDA Block  ROUT Block 
(1) PNT_NO IOM_ID
MEAS MEAS PNT_NO (1)
MEALM  RSP
RINP Block (2) BCALCO
OUT MEAS OUT
MEAS BCALCI BCALCO
SUP_IN
SUPBCO
MVL Block1
MEALM 
Block (2)
MVOUT
BCALCI MEAS
MVC Block 
MVL1
MVL2 MVL Block2 

MVLn
MVL Blockn 

Notes:
(1) PNT_NO = <Function Block Tag Name>.<Parameter>
(2) MEALM blocks are used to perform
BAD alarming.

Figure 5-6. Embedded MVC Control Configuration

39
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

DCI Block Parameter Mapping

Table 5-9 shows how the I/A Series parameters associated with the BIN, BOUT, RIN, and
ROUT blocks are mapped with the device function block parameters.

Table 5-9. DCI Block Parameter Mapping

I/A Series Device Function

DCI Block  Parameter  Block Parameter 
BIN CIN   ←OUT_D value
CIN.status   ←OUT_D status
VALSTS   ←OUT_D status
BOUT COUT   →CAS_IN_D value
COUT.status   ←BKCAL_OUT_D status
(readback value)   ←BKCAL_OUT_D value
(initialize value)   ←BKCAL_OUT_D value
VALSTS   ←BKCAL_OUT_D status
RIN MEAS   ←OUT value
MEAS.status   ←OUT status
VALSTS   ←OUT status
ROUT OUT   →CAS_IN value
OUT.status   ←BKCAL_OUT status
(readback value)   ←BKCAL_OUT value
(initialize value)   ←BKCAL_OUT value
VALSTS   ←BKCAL_OUT status

Function Block Parameter Status Mapping

The following paragraphs describe how the device function block parameter status is transformed
into equivalent DCI Block Status (BLKSTA) and DCI Parameter Status for presentation to the
I/A Series control station.

DCI Block Status (BLKSTA)

Table 5-10 shows how the device function block parameter status is transformed into equivalent
DCI Block Status (BLKSTA) bits.

Table 5-10. DCI Parameter Status Mapping

DCI Block Status (BLKSTA Device Function Block Parameter Status

Local Override (LO) Bits 6-7: Quality = 2 or 3 (Good) and
(Bit 3) Bits 2-5: Substatus = 6 (LO)

40
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
5. Configuration Information B0400FD – Rev D

DCI Parameter Status

Table 5-11 shows how the device function block parameter status is transformed into equivalent
DCI Parameter Status (for example, value record status for MEAS in a RIN block).

Table 5-11. DCI Parameter Status Mapping

DCI Parameter Status* Device Function Block Parameter Status

Out-of-Service (OOS) Compound is off, or
(Bit 11) DCI connection not made, or
Control Station - FBM220/221 communications
failure, or:
Bits 6-7: Quality = 0 (Bad), and
Bits 2-5: Substatus = 7 (Out of Service), or
1 (Config. Error), or 2 (Not Connected)
Bad Value (BAD) Control Station - FBM220/221 communications
(Bit 8) failure, or:

Error (ERR) Bits

Bits 6-7:
6-7: Quality
Quality == 0
1 (Bad)
(Uncertain)
(Bit 15)
Limited High (LHI) Parameter is clamped high by the control station, or:
(Bit 13) Bits 0-1: Limits = 2 (High) or 3 (Constant),
or
Bits 6-7: Quality = 2 or 3 (Good), and  
Bits 2-5: Substatus = 3 (NI) or 6 (LO)
Limited Low (LLO) Parameter is clamped low by the control station, or:
(Bit 14) Bits 0-1: Limits = 1 (Low) or 3 (Constant),
or
Bits 6-7: Quality = 2 or 3 (Good), and  
Bits 2-5: Substatus = 3 (NI) or 6 (LO)
Fail-safe (FS) Bits 6-7: Quality = 2 or 3 (Good), and  
(Bit 4) Bits 2-5: Substatus = 7 (FSA)
*Standard I/A Series status bits (used with all blocks)

41
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 5. Configuration Information

42
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

6. Process Operator Displays 

This chapter provides references for information on the process operator displays used with the
I/A Series system (and thus with the FBM220/221).
The I/A Series system provides the following types of displays for performance of process control
operations:
♦ Select Screen Display (compound and block overview display)
♦ Group Displays
♦ User-Generated Displays
♦ Block Detail Displays
♦ Compound Detail Displays
♦ Station Displays.

For information on how these displays are used, refer to Process Operations and Displays  
(B0193MM).

Block Detail Displays

Two ECBs, ECB200 and ECB201, relate to the FBM220/221 and their associated H1 devices.
The block detail displays for these ECBs are described in the following subsections. To access the
block detail displays, use the system’s Display Manager utility. Select the appropriate compound
and then the ECB.

43
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 6. Process Operator Displays

ECB200 Block Detail Display

ECB Description

Compound Name
ECB Name
DEV_ID FOX_12
(FBM Status 1)
(FBM Status 2)
(FBM Status 3)
(FBM Status 4)
(FBM Status 5)
HWTYPE
SWTYPE
ECB Faceplate
(see text)

Primary Data (see text)

Figure 6-1. ECB200 Block Detail Display

44
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
6. Process Operator Displays B0400FD – Rev D

ECB200 Faceplate 
ECB Description ECB200’s description as configured in the DESCRP
parameter.
Compound Name Name of the compound that holds the ECB200.
ECB Name ECB200’s name as configured in the NAME parameter.

DEV_ID Device
DEV_ID Identification
parameter). (the text configured for the ECB200’s
FBM Status (line 1) DCI READY or DCI NOT READY – The FBM is ready or not
ready for operation.
FBM Status (line 2) FBM FAILED – The FBM is inoperable.
FBM Status (line 3) FBM OFF-LINE – The FBM has been switched off-line using
the SMDH display, or has never been placed on-line.
FBM Status (line 4) DB DOWNLOAD FAIL – A failure occurred during a recent DB
download operation. Not used with FBM220/221.
FBM Status (line 5) UNRESOLVED  – A failure occurred whose source is unknown.

Potential exists for recovery from failure.

HWTYPE Hardware Type is configured based on the type of connected
FBM:
For FBM220, HWTYPE = 220
For FBM221, HWTYPE = 221
SWTYPE Software Type (same as HWTYPE):
For FBM220, SWTYPE = 220
For FBM221, SWTYPE = 221

ECB200 Primary Data 

The
eters,ECB200 primary
which are data,
described indisplayed
IntegratedinControl
the lower part
Block of Figure 6-1,
Descriptions  consists of ECB200 param-
(B0193AX).

45
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 6. Process Operator Displays

ECB201 Block Detail Display

ECB Description

Compound Name

ECB Name
DEV_ID FOX_19
(Device Status 1)
(Device Status 2)
(Device Status 3)
(Device Status 4)
(Device Status 5)
HWTYPE
SWTYPE
ECB Faceplate
(see text)

Primary Data (see text)

Figure 6-2. ECB201 Block Detail Display

46
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
6. Process Operator Displays B0400FD – Rev D

ECB201 Faceplate 
ECB Description ECB201’s description as configured in the DESCRP parameter.
Compound Name Name of the compound that holds ECB201.
ECB Name ECB201’s name as configured in the NAME parameter.
DEV_ID Device Identification (the text configured for the ECB201’s

Device Status (line 1) DEV_ID parameter).

DCI READY or DCI NOT READY – The device is ready or not ready for
operation.
Device Status (line 2) DEVICE FAILED – The device is inoperable.
Device Status (line 3) DISABLED – Communication to the device has been disabled.
Device Status (line 4) DB DOWNLOAD FAIL – A failure occurred during a recent DB down-
load operation. Not used with FBM220/221.
Device Status (line 5) UNRESOLVED – A failure occurred whose source is unknown. Poten-
tial exists for recovery from failure.
HWTYPE Hardware type (same as for parent ECB200):
 For FBM220, HWTYPE = 220
 For FBM221, HWTYPE = 221
SWTYPE Software type (same as for parent ECB200):
 For FBM220, SWTYPE = 220
 For FBM221, SWTYPE = 221

ECB201 Primary Data 

The ECB201 primary data, displayed in the lower part of Figure 6-2, consists of ECB201 param-
eters, which are described in Integrated Control Block Descriptions   (B0193AX).

47
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 6. Process Operator Displays

48
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

7. Maintenance 
This chapter provides maintenance information for the FBM220/221.

NOTE
In general, maintenance includes periodic inspection and cleaning, checking the
status of LED indicators, and checking for loose cable connections.

System Management Displays

The System Management Display Handler (SMDH) obtains current and historical information
about the system and displays this information in System Management displays. With regard to
FBM220/221 and the associated H1 field devices, the SMDH provides the following displays:
♦
 A Fieldbus level display (PIO Network), which shows the control station (control pro-
cessor), FCM(s), and any other Fieldbus devices.
♦  A module Fieldbus level display (PIO Sub-Network), which shows the selected FCM
and associated FBMs and H1 field devices.
♦ Detailed equipment change (EQUIP CHG) and equipment information (EQUIP
INFO) displays for each FBM and associated H1 field devices.
For detailed information on the use of the System Management Displays, refer to System Manage- 
ment Displays   (B0193JC).

FBM220/221 Equipment Information Display

The Equipment Information display for the FBM220/221 is the same as for other FBMs in the
DIN rail mounted subsystem. Refer to DIN Rail Mounted FBM Subsystem User’s Guide  
(B0400FA).

FBM220/221 Equipment Change Display

The Equipment Change display for the FBM220/221 is the same as for other FBMs in the DIN
rail mounted subsystem, except a DB DOWNLOAD control has been added. DB DOWN-
LOAD downloads an FBM220/221 configuration file containing link communications informa-
tion for up to 4 H1 ports supported by the FBM220/221.

H1 Field Device Equipment Information Display

 An example of an H1 field device Equipment Information display is shown in Figure 7-1 and
Figure 7-2. For the most part, this display is the same as the Equipment Information Display for
the FBM220/221. However the following additional text fields appear on the H1 field device
Equipment Information display:

49
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 7. Maintenance

Currently
Selected
H1 Device

Figure 7-1. Typical H1 Field Device Equipment Information Display (1 of 2)

Currently
Selected
H1 Device

Figure 7-2. Typical H1 Field Device Equipment Information Display (2 of 2)

50
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
7. Maintenance B0400FD – Rev D

♦ COMMUNICATIONS –  Indicates the state (enabled/disabled) of communications

to/from the FOUNDATION fieldbus H1 field devices (used to mainly to assist in
troubleshooting).
♦ EE UPDATE STATE –  Indicates the current state of the EE Update function.

H1 Field Device Equipment Change Display

 An example of an H1 field device Equipment Change display is shown in Figure 7-3. The follow-
ing controls are active for this display:
♦ ENABLE/DISABLE COMMUNICATIONS  –  Logically connects/disconnects H1
device from FBM220/221 (used mainly to assist in troubleshooting H1 network
problems).
♦ INHIBIT DEVICE ALARMING  –  Provides for inhibiting of the device alarm func-
tion (used mainly to assist in troubleshooting H1 network problems).
♦ DB DOWNLOAD –  Reserved for future use.

Figure 7-3. Typical H1 Field Device Equipment Change Display

LED Indicators
LED indicators at the front of the FBM220 and FBM221 indicate the operational status of these
devices and any associated communications activity (see Figure 7-4). The on/off and flashing
states of the LEDs indicate the FBM operating modes as shown in Table 7-1, and any detected
FBM hardware diagnostic failure conditions as shown in Table 7-2.

51
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 7. Maintenance

If any hardware diagnostic failure condition is detected, the red and green LEDs first blink an
eight-digit pattern of detailed diagnostic information, repeat once, and then settle into an end-
lessly repeating pattern in which the red LED remains on while the green LED blinks the error
code shown in Table 7-2.

Table 7-1. LED Status for FBM Operating Modes

Red  Green  Amber 

LED LED LED Mode
ON ON OFF   Start-up – Power is first applied to the FBM and boot-up
(including boot-up hardware diagnostics) is being implemented.
If boot-up is not completed due to a hardware failure, refer to
Table 7-2 for the failed hardware component.
Once boot-up is successfully completed, this LED combination
indicates that the FBM is in Off-line mode.
OFF ON ON   On-line – Start command has been issued by the I/A Series con-
trol station, causing transition from off-line to on-line.
FLASH* FLASH* OFF Image Download  – FBM is off-line and software image is being
 
downloaded to the FBM.
ON ON FLASH   Image Flashing  – FBM is off-line, the software image has been
downloaded to the FBM, and image flashing is being imple-
mented.
*The flash duty cycle is 1/2 second ON and 1/2 second OFF. The red and green LEDs flash
alternately.

Table 7-2. LED Status for FBM Hardware Diagnostics Failure

Red   Amber 
LED Green LED LED Hardware Test Failed  
ON 1 blink per ten-second cycle OFF Low Memory RAM test failure
ON 2 blinks per ten-second cycle OFF High Memory RAM test failure
ON 3 blinks per ten-second cycle OFF Timer test failure
ON 4 blinks per ten-second cycle OFF DMA test failure
ON 5 blinks per ten-second cycle OFF HDLC communications test failure
ON 7 blinks per ten-second cycle OFF ROM checksum failure
ON 12 blinks per ten-second cycle OFF FieldBus (Find1) communications controller

52
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
7. Maintenance B0400FD – Rev D

 ® 
Indicate FBM operating/diagnostic
status (See related tables in this
Operational Status  chapter.)
Link Active 03 01

04 02  

Indicate FOUNDATION fieldbus
communications activity associated
with this FBM (See Note.)

FBM221
Channel Isolated
4 Communication, H1
Fieldbus Foundation
P0917HB NOTE:
 ®  FBM220 is similar in apearance, but
contains only one Link Active indicator.

Figure 7-4. FBM221 LED Status Indicators

53
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D 7. Maintenance

54
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Appendix A. Control Loop

Performance 
This appendix provides a description of the constructs that support FOUNDATION fieldbus
execution in an I/A Series system environment.
The introduction of F OUNDATION fieldbus has implications for closed loop control. The factors
that influence control loop performance are presented in the sections:
♦ Macrocycle Architecture (presentation of the component parts and their relationship
on a macrocycle timeline)
♦ Schedule Algorithm (how the macrocycle schedule is computed)
♦ BPC/Macrocycle Phasing
♦ Typical Control Loop Timing 
♦ Maximum Performance Control Loops

Macrocycle Architecture
The execution of data transfer on a given H1 segment is prescribed by a unique schedule for that
segment. In I/A Series systems, the schedule for a given segment is established by the
FBM220/221. The architecture of this schedule includes the:
♦ Component parts of a schedule
♦ Typical ordering of these parts
♦
Timing implications of different applications.

First Macrocycle Second Macrocycle

Max device First Macrocycle Completed
execution time Second Macrocycle Initiated

5: AO_1 5: AO_1

4: FB AI_3 4: FB AI_3
4: FB AI_2 4: FB AI_2
4: FB AI_1 4: FB AI_1

3: FB AO_1 FBM 3: FB AO_1

FB2
2: FB AI_2 2: FB AI_2
2: FB AI_1 2: FB AI_1
FBM
1: FB AI_2 FB1 FBM 1: FB AI_2
1: FB AI_1 CD CD2 1: FB AI_1
CD
CD
CD
CD
CD
CD FBM
T=0 CD
CD CD CD1 CD
CD

Device Compel Data, and

Device FB Execution 100 Spare time for overhead
FBM FB execution, and
milliseconds communication
FBM Compel Data

Figure A-1. Link Timing Diagram

55
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Appendix A. Control Loop Performance

The component parts of a typical macrocycle shown schematically in Figure A-1 are:

♦ Device Function Block execution -- All device function block executions are front-
ended to the beginning of the macro cycle schedule and includes both input and out-
put function blocks. Some devices may have multiple function blocks and these are
scheduled to run sequentially within the device with a 100 ms gap between each
block. Note that all devices are scheduled to run concurrently.
♦
 A 100 ms dwell time -- This provides a safety margin for the completion of the last
device function block execution and the beginning of the segment compel data
transactions.
♦ Segment compel data transactions -- During this period of time, the FBM issues com-
mands to get data from input devices and also executes its own Function Blocks to
communicate new setpoints to device output blocks.
♦ Spare time -- Generally, some pad is introduced into the schedule to allow for house-
keeping and client/server communications. At the end of this period, the next set of
compel data transactions (in the next macrocycle) begins.
Macrocycle execution is based on the set of rules described below:
1. Schedule all connected (through DCI Connections) FF Function Blocks in H1 Field
Devices on the link for execution (Device FB Execution in Figure A-1). Only include
Function Blocks for ENABLEd devices.
2. Function blocks in the same device are separated by 100 milliseconds to avoid over-
lapping execution.
3. Insert 100 milliseconds to ensure some margin of safety between the completion of
the execution of the last Device FB and the first Compel Data (CD) on the H1 bus.
4. Schedule a CD for each one of the scheduled Field Device Function Blocks. This
action causes all input points to be published to the FBM (Device Compel Data in
Figure A-1).
5. After the last Compel Data to field Devices FB, the FBM Function Blocks and Com-
pel Data to the FBM are scheduled. (FBM FB Execution and FBM Compel Data in
Figure A-1).

NOTE
Only output points require FBM 220/221 function block execution. This phase
ensures publication of output setpoints to output type Field Devices.

6. Finally, add some spare time for overhead communication. This overhead includes FF
H1 basic communication for bus management as well as client/server communica-
tion.

NOTE
The spare time extends from the completion of the last FBM Compel Data to the
first Field Device Compel Data in the next Macrocycle.

56
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
Appendix A. Control Loop Performance B0400FD – Rev D

Macrocycle Schedule Algorithm

The following example is presented to illustrate the creation of a schedule. This schedule creation
references Figure A-1.

NOTE
The time period labeled Device FB Execution is dominated by the execution of the
three function blocks for device 4. If the execution period of these blocks is 40 ms,
the FBM will allow 320 ms (recall the 100 ms pad between respective FB) for this
Device FB Execution time period.

 Adding 100 ms brings the schedule period to 420 ms to the beginning of the Compel Data phase
of the schedule.
The FBM allows 25 ms for each respective CD. Each device AI block requires one compel data
for the FBM to get data from the transmitter. Each output device requires two compel datas: one
to get feedback from the device AO block and the other for the FBM to write data (CAS_IN or
CAS_IN_D) to the device function block. In the example with seven AI blocks and 2 output
devices, a total of eleven CDs are required in the schedule, or 275 ms. Add the 420 ms to the
beginning of the Compel Data phase which brings the total to 695 ms.
The schedule algorithm now tests for adequate Spare Time. Note that in Figure A-1, Spare Time
is the sum of the Device FB Execution time, the 100 ms buffer, and any time scheduled between
the end of the Compel Data phase and the beginning of the Device FB Execution phase. This
Spare Time sum is shown schematically on Figure A-1 on the right hand side of the time axis. The
schedule algorithm tests to see if this Spare Time sum is greater than 50% of the Compel Data
phase time period. In the cited example, the Spare Time is 420 ms. 50% of 275 ms is about
137ms. Therefore, the Spare Time is well in excess of the 50% minimum, so this test is passed.
The schedule algorithm then determines if the computed macrocycle is less than the user specified
or default minimum macrocycle period. If the 1010 ms default is utilized with the example
shown, the schedule that would result would be the greater of 1010 ms or the computed 695 ms,
or 1010 ms. While this results in a fairly conservative schedule, this is generally appropriate for
most segments.

BPC/Macrocycle Phasing
 With regards to macrocycle formulation, the material presented in the previous section focuses on
the creation of a schedule intra-FBM. This section deals with the CP-FBM inter-relationships. It
is important for the user to keep in mind that a simple single input, single output control loop
involves passing data between a number of sources and sinks and that these data transfers are not
instantaneous.

BPC

Macrocycle

Figure A-2. BPC/Macrocycle Phasing

Figure A-2 illustrates some of the issues. The schematic represents the asynchronous nature of the
Control Processor BPC (the frequency at which the CP processes control blocks) and the macro-

57
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Appendix A. Control Loop Performance

cycle execution period. Generally speaking, these frequencies are not the same or synchronized to
one another. As a result, communications between elements of a control loop have latencies that
must be understood, as these have an effect (although generally modest) on control loop perfor-
mance.
To gain a better understanding, a single input, single output (SISO) loop is examined to trace the
data transactions during a single loop execution. The PID block in the CP is processed once each

BPC.due
ever, ThetoPID
the block processes
latencies as itsbus
of the H1 measurement the most recent
and the asynchronous naturepiece of macrocycle
of the data available.
andHow-
BPC,
this piece of measurement data is delayed.
Similarly, when the PID block computes an output, some period of time passes before:
♦ The FBM writes a new value to a positioners AO block setpoint.
♦ The AO block of the positioner is processed and the new value causes the control
valve to make a regulatory move.
If you trace control loop propagation, it consists of the following elements:
♦  A transmitter processes a new piece of transducer data when its AI block is processed.
♦ The FBM issues a compel data to get this value to make it available to the Control
Processor.
♦ The Control Processor executes a PID algorithm using this measurement and pro-
duces an output value to write to the FBM.
♦ The FBM writes this value to the devices AO block.
♦ The device processes this position setpoint value to effect a valve position change.
The time lapse from measurement change to valve position movement is primarily a factor of seg-
ment macrocycle period. This macrocycle period is a function of the number of devices that are
connected to a given segment. To provide a better sense of the total loop execution time, an exam-
ple is provided in “Typical Control Loop Timing” on page 58.

Typical Control Loop Timing

To give the user a feeling for a typical control loop total execution time, an I/A Series control loop
 was constructed utilizing a RIN, PIDA, and ROUT block. In addition, a FOUNDATION field-
bus transmitter and output device were connected to these blocks to create a closed loop. This
loop was created such that measurement perturbations could be introduced to excite the closed
loop and make measurements of the delta time between measurement changes and valve action.
To better understand the result, the following salient features of the 2.16 iom221 image need to
be considered:
♦
The default
can be editedminimum macrocycle
by the end for a given
user, the example segment
cited in this issubsection
1010 ms. uses
Whilethethis value
default
value.
♦ The delay between respective Function Blocks in the same H1 device is 100
milliseconds.
♦ Time delay between completion of last FB execution and first CD is 100 milliseconds.
♦ The minimum slot of contiguous free time on the FF H1 segment is 100
milliseconds.

58
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
Appendix A. Control Loop Performance B0400FD – Rev D

♦ Identical to version 2.15, the macrocycle used is rounded to the next 10-millisecond
value. For example, a calculated macrocycle of 603 milliseconds is rounded up to 610.
In addition, all even multiples of 100 milliseconds are avoided to prevent cases where
the CP BPC and the macrocycle line up over multiple macrocycles.
 While these constructs provide stable and robust FBM operation, they tend to contribute to con-
trol loop latencies.

In the control loop described above, by accepting the default macrocycle minimum of 1010 ms,
the measured turnaround period for a change in the process measurement to a measured change
in valve position is just over 3000 ms1. This turnaround period provides acceptable control per-
formance for many applications; however, for some more demanding applications, faster loop
turnaround times are desirable. See “Maximum Performance Control Loops” on page 59.

Maximum Performance Control Loops

The primary contributor to total control loop execution time is the macrocycle period, typically a
default of approximately one second. For those applications that demand the shortest possible
loop execution times, version 2.16 of iom221 image provides an editable minimum macrocycle
time. Setting this minimum value to some low value forces the FBM to create a “minimum” mac-
rocycle. The macrocycle period becomes dependent on the number of segment-connected devices
and the execution time of the device function (AI and AO) blocks.
For example, the control loop presented in the previous subsection was moved to a segment con-
sisting only of a single transmitter and a single output device. The minimum macrocycle was set
to 100 ms. The FBM created a macrocycle that was timed to be 280 ms, which is the order of
magnitude for a minimum macrocycle for a single input and single output on a segment.
However, what is even more dramatic is the impact of this macrocycle period on loop perfor-
mance. For example, the elapsed time from a change in the process measurement to a new set-
point value presented to the positioner is about 600 ms. Compare this to the nearly 3000 ms in
the case of a 1010 ms macrocycle.
NOTE
For these shorter macrocycle control loops, the performance of the positioner
becomes a significant issue. Significant differences have been seen in various devices
 with respect to their servo response (time required from setpoint change to the actu-
ator settling to final value) performance.

Macrocycle Period
The FBM220/221 Version 2.16 has been modified to support a settable minimum Macrocycle.
Default minimum Macrocycle has been pre-configured to approximately one second. Minimum
Macrocycle can be modified using FoxCAE. Note that the minimum Macrocycle is stored in
FBM non-volatile memory, and will therefore be preserved through a reset or power cycle of the
FBM220/221. If the FBM is replaced however, the minimum Macrocycle has to be restored using
FoxCAE.

1. This time period changes slightly depending on the number of devices on the segment.

59
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Appendix A. Control Loop Performance

The FBM220/221 calculates the FF H1 LAS schedule using a minimum Macrocycle duration
 which limits the minimum FF cycle time for updates of FF data. Previous version of the
FBM220/221 had a hard coded value that could not be changed. Version 2.16 of the
FBM220/221 has been updated to allow for configuration of the minimum Macrocycle. The
value is stored in non-volatile RAM.
The minimum Macrocycle is changed by editing the MACROCYCLE_DURATION field, using

the “MIB”
required pull down menu
modification selection
to FoxCAE in the this
to enable “CPediting
Database” in FoxCAE
facility 5.0inand
is covered later.
Quick FixThe
QF1003077.
For additional information, refer to Control Processor 60 (CP60) Sizing Guidelines and Excel Work- 
book  (B0400BK).

60
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com

Index 
A
 Actuators 1
 Algorithm, macrocycle schedule 57
 Architecture, macrocycle 55
 Auto/manual mode 33

B 
Baseplate 2
Block Detail displays 11, 43
Block Interconnections 28
Block parameters
 AI 25
 AO 25
DI 26
DO 26
resource 24
transducer 24
Block processing 32
BPC/Macrocycle phasing 57

C 
Calculations, power 14
Clamp-on ferrite core 21
Compound Detail displays 43
Configuration information 23
Control loop execution time 55
Control loop performance 55
Control schemes 37
Control station 2

D 
DCI 2
DCI block functions 33
DCI parameter status 41
dc-to-dc power converter 2, 14
Device configurator 6
Device data verification 11
Device function blocks 29
Device parameters, H1 23
Distributed Control Interface 2

E 
ECB 2, 28

61
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Index

EMI filter 21
Equipment Change display 49, 51
Equipment Change function 9
Equipment Control Block 2, 28
Equipment Information display 49
Execution time, control loop 13

F 
Fail-safe actions 35
FBM 3
FCM 3, 13
Ferrite core 21
Fieldbus 3
Fieldbus Communications Module 3, 13
Fieldbus Module 3
FoxCAE 3, 8
Function block 7, 13
DCI 23
device 23, 29
Function block parameters
 AI 25
 AO 25
DI 26
DO 26

G 
Glossary 2
Group displays 43

H 
H1 3
H1 device parameters 23
Heartbeat message 36

I 
I/A Series control station 2
ICC 8
IEC fieldbus standard 15
Indicators, LED 51
Input limiting 33
Installation
FBM 7
I/A Series equipment 7
TA 7
Integrated Control Configurator 8
Intrinsic safety 14

62
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
 Index B0400FD – Rev D

L
Label, TA 20
LAS 3
LED indicators 51
Letterbug 3, 31
Linear scaling 33
Link Active Scheduler 3

M 
Macrocycle 3
Macrocycle architecture 55
Macrocycle execution 56
Macrocycle schedule algorithm 57
Maintenance 49
Mapping 
DCI block parameter 40
function block parameter 40

N 
NI-FBUS 6
NI-FBUS monitor 8

O 
Output confirmation 34
Output initialization 34

P 
Parameter 3
Parameters
DCI block 7
function block 7
Performance
control loop 55
Periodic/change-driven execution 33
Phasing, BPC/Macrocycle 57
Port settings, device configurator 6
Power calculations 14
Power connections 20
Power supply 2, 14, 15
Process operator displays 43
Product application 13
Publish/subscribe function 30

Q 
Quick-start example 5

63
http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules
5/17/2018 FOUNDATION fieldbusH1Communication InterfaceModules-slidepdf.com
B0400FD – Rev D Index

R 
Redundancy, power 20
Reference documents xi
Repeater 14
Revision information xi

S 
Select screen display 43
Signal conditioning 33
Simulation mode 33
SMDH 49
Spur 14
Station displays 43
Switches, TA 2
System Management displays 9, 49

T 
TA 3
Tag, device 23
Termination Assembly 3
Time stamping 33
Topology 1, 13, 14
Transmitters 1
Trunk length 14

U 
User-generated displays 43

33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America 
 www.foxboro.com
Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your local Foxboro representative.
Facsimile: 1-508-549-4999
Printed in U.S.A. 1004

http://slidepdf.com/reader/full/foundation-fieldbus-h1-communication-interface-modules