B0400FDREV DI/A Series

FOUNDATION fieldbus H1 CommunicationInterface Modules (FBM220/FBM221)

Users Guide

October 5, 2004

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

Contents

Figures................................................................................................................................... vii

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

Preface.................................................................................................................................... xi

Who This Book Is For ............................................................................................................. xi

What You Should Know .......................................................................................................... xi

Revision Information ............................................................................................................... xi

Reference Documents .............................................................................................................. xiI/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 .............................................................................................................................. 14Bus Length Calculations ..................................................................................................... 14Bus Power Supply .............................................................................................................. 15Bus Power Calculations ...................................................................................................... 15Intrinsic 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 .................................................................................................... 23H1 Transmitter LAS/LM Disabling Procedure ................................................................... 27

Block Interconnections ........................................................................................................... 28

Configuration Procedures ....................................................................................................... 31

Block Processing ..................................................................................................................... 32iii

B0400FD Rev D Contents DCI Block Functions .............................................................................................................. 33Periodic/Change-Driven Execution .................................................................................... 33Auto/Manual Mode Operation .......................................................................................... 33Simulation Mode ............................................................................................................... 33Time Stamping .................................................................................................................. 33Signal Conditioning and Linear Scaling ............................................................................. 33Input Limiting ................................................................................................................... 33Confirmed Outputs ............................................................................................................ 34Output Clamping .............................................................................................................. 34Output Initialization .......................................................................................................... 34Cascade Initialization ......................................................................................................... 34Fail-Safe Actions ................................................................................................................. 35Heartbeat Message Handling .............................................................................................. 36

Control Schemes Using DCI Blocks ....................................................................................... 37

DCI Block Parameter Mapping .............................................................................................. 40

Function Block Parameter Status Mapping ............................................................................. 40DCI Block Status (BLKSTA) ............................................................................................. 40DCI Parameter Status ........................................................................................................ 41

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

Block Detail Displays .............................................................................................................. 43ECB200 Block Detail Display ............................................................................................ 44

ECB200 Faceplate ......................................................................................................... 45ECB200 Primary Data .................................................................................................. 45

ECB201 Block Detail Display ................................................................................................. 46ECB201 Faceplate ......................................................................................................... 47ECB201 Primary Data .................................................................................................. 47

7. Maintenance.................................................................................................................... 49

System Management Displays ................................................................................................. 49FBM220/221 Equipment Information Display .................................................................. 49FBM220/221 Equipment Change Display ......................................................................... 49H1 Field Device Equipment Information Display .............................................................. 49H1 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 ................................................................................................................... 59iv

Contents B0400FD Rev D Index .................................................................................................................................... 61v

B0400FD Rev D Contents vi

Figures

1-1. FBM220/221 and Associated Foundation Fieldbus Elements ........................................ 12-1. Typical Fieldbus H1/Foxboro I/A Series Integration Process ......................................... 52-2. Typical Overview ICC Display for a Control Processor 60 ........................................... 82-3. Typical ECB200 (Parent) Editing Display .................................................................... 92-4. Typical ECB201 (Child) Editing Display ................................................................... 102-5. Typical DCI Block Editing Display ............................................................................ 114-1. FBM220/221 and Termination Assembly Installation ................................................ 174-2. TA Foundation Fieldbus Cable Connections .............................................................. 194-3. TA Component Locations (Covers Removed) ............................................................. 204-4. TA Foundation Fieldbus Power Connections .............................................................. 214-5. Installation of Ferrite Cores in Power Cables ............................................................... 225-1. ECB Hierarchy ........................................................................................................... 285-2. Block/DCI Block Functional Relationships ................................................................. 295-3. Typical User-Configured Block Interconnections ........................................................ 305-4. Simple Cascade Configuration .................................................................................... 375-5. Supervisory Control Configuration ............................................................................. 385-6. Embedded MVC Control Configuration .................................................................... 396-1. ECB200 Block Detail Display ..................................................................................... 446-2. ECB201 Block Detail Display ..................................................................................... 467-1. Typical H1 Field Device Equipment Information Display (1 of 2) ............................. 507-2. Typical H1 Field Device Equipment Information Display (2 of 2) ............................. 507-3. Typical H1 Field Device Equipment Change Display ................................................. 517-4. FBM221 LED Status Indicators .................................................................................. 53A-1. Link Timing Diagram ................................................................................................. 55A-2. BPC/Macrocycle Phasing ............................................................................................ 57vii

B0400FD Rev D Figures viii

Tables

5-1. FBM220/221 Maximum Configuration Specifications ............................................... 235-2. Transducer Block Parameters ...................................................................................... 245-3. Resource Block Parameters .......................................................................................... 245-4. Analog Input (AI) Block Parameters ............................................................................ 255-5. Analog Output (AO) Block Parameters ....................................................................... 255-6. Discrete Input (DI) Block Parameters ......................................................................... 265-7. Discrete Output (DO) Block Parameters .................................................................... 265-8. Key Parameters ............................................................................................................ 315-9. DCI Block Parameter Mapping .................................................................................. 405-10. DCI Parameter Status Mapping .................................................................................. 405-11. DCI Parameter Status Mapping .................................................................................. 417-1. LED Status for FBM Operating Modes ...................................................................... 527-2. LED Status for FBM Hardware Diagnostics Failure .................................................... 52ix

B0400FD Rev D Tables x

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 FOUNDATION fieldbus H1 Support (B0400DE).

Who This Book Is ForThis 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 You Should KnowPrior to using this book, you should be generally familiar with the I/A Series system and with DIN Rail Mounted FBM Subsystem Users Guide (B0400FA). Detailed information for the various I/A Series software and hardware elements is found in the reference documents listed below.

Revision InformationFor 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 DocumentsThe following documents provide additional and related information.

I/A Series Documents FOUNDATION fieldbus H1 Communication Interface Module (FBM220/221)

(PSS 21H-2Z20 B4)

FBM220/221 Termination Assembly FOUNDATION fieldbus Communication(PSS 21H-2W5 B4)

DIN Rail Mounted FBM Subsystem Users Guide (B0400FA)

Control Processor 60 and Control Processor 60S Installation and Maintenance (B0400FB)xi

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 FOUNDATION fieldbus H1 Support (B0400DE).

FOUNDATION Fieldbus Documents

NOTEThe 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, FOUNDATION 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 Definitionxii

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 FOUNDATION Physical Layer Profile Specification.xiii

B0400FD Rev D Preface xiv

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.

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

FBM220/221

2 Mbps Module Fieldbus

TerminationAssembly

Field Devices

TA

Terminator* Terminator

To Additional, Similar Equipment Groupings(if applicable)

FCM

FCM

10Base2 (10 Mbps)Ethernet Trunk Fieldbus(redundant)

I/A SeriesControl Station(Fault-Tolerant)

FOUNDATION Fieldbus(Typical Topology)

To Additional FBMs(if applicable)

(See Note)

NOTE: The Termination Assembly contains a dc-to-dcconverter and a bus terminator. The bus terminator isused to terminate the FOUNDATION fieldbus when theFBM220/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 locatedmid point on the bus segment.

From optionallyredundant dc

power sources

Up to 120 FBMs perI/A Series Control Station1

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 fieldbus segment. Switches located on the TA provide for terminator selection (in or out) and local powering of the bus (on/off ) on a per channel (per bus segment) 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 TermsThe following terminology relates directly to the FBM220/221 and its associated equipment. For a glossary of terms relating to FOUNDATION 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 Users 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

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

B0400FD Rev D 1. Introduction 4

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

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

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

Start

Configure H1DevicesOff-line

1

InstallI/A Series

System andH1 Bus

2

4Create

and EditFBM220/221

ECB

Createand Edit

H1 DeviceECBs

6

EnableH1 Device

Communication

7

CreateDCI Blocks

for AllDevice Points

8

Attach H1Devices

to H1 Bus

3Verify H1

Device Dataon the Block

Detail Displays

9

End

5Place

FBM220/221On-Line5

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 a personal computer interface, install the device configurator interface card and associated software in the Windows NT based personal 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 users 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:

Configure the device configurator network communication parameters by entering the following parameters:

Parameter NI-FBUS FBM220/221

T1 0x40000 0x75300

T2 0x40000 0x2BF200

T3 0x30000 0x15F900

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

1. The FBM220/221 uses a TIME_SYNC_CLASS value of 5.

46

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-turers 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 Users 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 Users 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

B0400FD Rev D 2. Quick-Start Example NOTEIt 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).

NOTEIn 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

2. Quick-Start Example B0400FD Rev D 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.

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

Key parameter:Contains the nameused by the controlstation to accessthis ECB.

Key parameter:Contains the letterbug ofthe associated FBM.9

B0400FD Rev D 2. Quick-Start Example 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.

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

name of FBM220 (parent) ECB.Key parameter: Configured with

Contains the PD tag-Key parameter:

name of the field deviceassociated with this ECB.

(See note in text.)10

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.

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 Users Guide (B0400FA)

Integrated Control Software Concepts (B0193AW)

Integrated Control Block Descriptions (B0193AX).

Key parameter:Indicates process

Contains the pathname of the

variable connectedto this block.

Key parameter:

ECB201 associated with the field parameter to be accessed*.

*Once configured, the IOM_ID parameter cannot be readily changed. To changethe IOM_ID parameter, you must delete the block and re-enter it into the database. (A Delete/Undelete operation will not perform this function.)11

B0400FD Rev D 2. Quick-Start Example 12

3. Product Application

This chapter addresses various requirements and constraints relating to the connection of the FBM220/221 to the FOUNDATION 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

NOTEThe 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 is designed for use with the Control Processor 60 (CP60) I/A Series control station and I/A Series Fieldbus Communication Modules (FCMs). It connects to the FCM(s) via 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:

FOUNDATION fieldbus H1 Communication Interface Module (FBM220/221) (PSS 21H-2Z20 B4)

FBM220/221 TA FOUNDATION fieldbus Communication (PSS 21H-2W5 B4).

Field Device Configuration RequirementsAs 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

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.

TopologiesThe 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 FOUNDATION 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 CalculationsFor 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

3. Product Application B0400FD Rev D NOTEAs 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 SupplyAs 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 FOUNDATION 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 CalculationsThe 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 ConsiderationsThe 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.

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

B0400FD Rev D 3. Product Application Control Loop Execution TimeControl loop execution time calculations are used by process engineers for loop timing purposes. Control loop execution time is a function of the FBMs H1 macrocycle and the control processors 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

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.

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

L+

L+

L+

L+

N-

N-

N-

N-

B01B02B03B04B05B06B07B08

A01A02A03A04A05A06A07A08

C01C02C03C04C05C06C07C08iPi+i-

i+i-i+i-i+i-i+i-i+i-i+i-

i+i-iPi

PiPiPi

PiP

iP

IN P U T

8

FBM201

, 0-2

0mA

0102

0304 0

5 0607 0

8

TerminationAssembly

TerminationCable

Fieldbus CommunicationsModules (2)Baseplate

Clamp-On Ferrite Core

ModuleFieldbus

FieldbusModule(FBM220/221) Clamp-On

Ferrite Cores

1ONOFFONOFF

2ONONOFFOFF

No.0123

Baseplate I. D.

Operational Status

FBM220Channel Isolated1 Communication, H1Fieldbus FoundationP0917HA

Operational Status

FBM220Channel Isolated1 Communication, H1Fieldbus FoundationP0917HA

Link ActiveLink Active

Operational Status

FBM220Channel Isolated1 Communication, H1Fieldbus FoundationP0917HA

Operational Status

FCM10ECommunication10 Mbps Coaxial Ethernet to2 Mbps FieldbusP0914YM

Tx

Tx

Rx

Rx

Fieldbus

Ethernet

Operational Status

FCM10ECommunication10 Mbps Coaxial Ethernet to2 Mbps FieldbusP0914YM

Tx

Tx

Rx

Rx

Fieldbus

Ethernet

FCM Identification

P0914ZM

Left Module

User Defined

Right Module

Operational Status

Link Active

FBM220Channel I

solated

1 Communication, H

1

Fieldbus Foundatio

n

P0917HA

Link Active17

B0400FD Rev D 4. Installation The termination cable (connecting between the TA and the baseplate) is available in the following lengths:

0.5 m P0916DA1.0 m P0916DB3.0 m P0916DC5.0 m P0916DD10.0 m P0916DE15.0 m P0916DF20.0 m P0916DG25.0 m P0916DH30.0 m P0916DJ

For FBM and TA installation instructions, refer to DIN Rail Mounted FBM Subsystem Users 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

NOTEFor 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

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.

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.

NOTE:FBM221 TA (shown)has four channels;FBM220 TA has onechannel.

SignalConnectionPoints:

C = o+B = o-A = Shield

C

A

B

COMMUNICATION

FBM221, Foundation Fieldbus04030201

o+o+o+o+o-o-o-o-shshshsh

C

A

B

COMMUNICATION

FBM221, Foundation Fieldbus04030201

o+o+o+o+o-o-o-o-shshshsh

Label

To H1Field

Devices

To H1FieldDevices

To H1Field

Devices

End-Bus Connection Mid-Bus Connection19

B0400FD Rev D 4. Installation Figure 4-3. TA Component Locations (Covers Removed)

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

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

FBM IDENTIFICATION

CABLE TYPE 1 PRI SEC

OFF

1 2

C

B

A -24 V

+

Channel 1 switch pair:1 - Power converter powering of fieldbus segment (on/off)*2 - Terminating resistor (in/out)*

Channel 2, 3, and 4 switch pairs (on FBM221 TA,P0917RG) operate in a similar fashion.

FBM220 TA (P0917RF) or FBM221 TA (P0917RG), covers removed.* Press upper part of Switch 1 to enable power converter (on).

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

dc to dcPower Converter(1 of 4)

Connections forIncoming SourcePower**

TerminationCable

Connector

FieldbusConnections20

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.

Figure 4-4. TA FOUNDATION Fieldbus Power Connections

+

24 V-

SecondaryPrimary24 Vdc24 VdcRETURNRETURN

1 2

OFF

1 - Power Supply2 - Terminating Resistor

FBM220 - 2 SwitchesFBM221 - 8 Switches

WARNINGFor installation details seedocument B0400FD

From 24 V Secondary PowerSupply (if Required by Application)

2 Clamp-On Ferrite Cores(BF162 YG)*

2 Clamp-On Ferrite Cores(BF162 YG)*

* See next figure forinstallation instructions.

LabeledCover

From 24 V Primary Power Supply21

B0400FD Rev D 4. Installation

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

2 Clamp-On Ferrite Cores(EMI Filter) BF162YHNylon Cable Tie(User Supplied)*

* The use of nylon cable ties (positioned as shown) isrecommended to keep the ferrite cores in place on the cable.

Nylon Cable Tie(User Supplied)*

To 24 VPower SupplyTo TA

Install in close proximity[approx. 50 mm (2 in)] toconnectors on TA22

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.

H1 Field Device ParametersThe 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.

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

Table 5-1. FBM220/221 Maximum Configuration Specifications

FBMType

Maximum Numberof H1 Devices Allowed

Maximum Number ofPoint 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.23

B0400FD Rev D 5. Configuration Information Table 5-2. Transducer Block Parameters

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

MODE_BLK PERMITTED TARGET NORMAL

(See Notes column.)AutoAuto

For PERMITTED mode, ensure thatOOS, MAN, and AUTO are selectablefrom 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

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

MODE_BLK PERMITTED MODE TARGET MODE

Auto, Out-of-ServiceAuto

RequiredRequired

FEATURE_SEL Octet Text Strings

Reports Option

Fault State

Write Lock

Direct Write to Output Hdwr.

ASCII

Not supported; do not use

Partially supported (see Notes col-umn)

Not supported; do not use

Not supported; do not use

ISO 646/2375 compliant

Disables Alert Reports.

Supports Fail-safe detection at the 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.

Disables Write Lock

GRANT_DENY Not supported; do not useSHED_RCAS Not supported; do not useSHED_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

5. Configuration Information B0400FD Rev D Table 5-4. Analog Input (AI) Block Parameters

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

MODE_BLK PERMITTED TARGET

Auto, Out-of- ServiceAuto

RequiredRequired

SIMULATE Not supported; do not use Use SIMOPT in CP60 RIN block.OUT_SCALE EU@100%

EU@0%

Same value as the HSCI1 in CP60 RIN block (not enforced by I/A).Same value as the LSCI1 in CP60 RIN block (not enforced by I/A).

GRANT_DENY Not supported; do not useIO_OPTS Bit 10: Low cutoff Yes/No User option; no constraint.STATUS_OPTS Bit 3: Propagate Fail Forward Bit 6: Uncertain if Limited Bit 7: Bad if Limited

YesYes/NoYes/No

Option required.User option; no constraint.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

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

MODE_BLK PERMITTED TARGET

Cascade, Auto, Out-of-ServiceCascade, Auto

Required for normal operation.Required for normal operation.

SIMULATE Not supported; do not use Use the SIMOPT in CP60 ROUT block.

PV_SCALE EU@100%

EU@0%

Same value as the HSCO1 in CP60ROUT block (not enforced by I/A)Same value as the LSCO1 in CP60 ROUT block (not enforced by I/A)

GRANT_DENY Not supported; do not useIO_OPTS** Bit 1: SP-PV Track in Manual Bit 3: SP-PV Track in LO Bit 4: SP Track retained target Bit 5: Increase to Close

Bit 6: FS to Value Bit 7: Use FS value on Restart Bit 8: Target to Man if FS Asserted Bit 9: Use PV for BKCAL_OUT

Not supported; do not use YesNot supported; do not use Not supported; do not use

Yes/NoYes/NoNot supported; do not use Yes/No

Option required.

Use the REVOPT in CP ROUT block.No constraint; see note below.No constraint; see note below.

If this option is used, the OUTOPT option in the CP60 ROUT block must also be set (not enforced by I/A).25

B0400FD Rev D 5. Configuration Information 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

ROUT block (not enforced by I/A)Use CLPOPT with HOLIM in CP ROUT block.

SP_LO_LIM Same value as the LSCO1 in CP60 ROUT block (not enforced by I/A)

Use CLPOPT with LOLIM in CP 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_SELparameter must be configured in the Resource block.

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

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

MODE_BLK PERMITTED TARGET

Auto, Out-of-ServiceAuto

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

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

MODE_BLK PERMITTED TARGET

Cascade, Auto, Out-of-ServiceCascade, Auto

Required for normal operation.Required for normal operation.

SIMULATE_D Not supported; do not use Use SIMOPT in CP60 BOUT block.

GRANT_DENY Not supported; do not use

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

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

5. Configuration Information B0400FD Rev D H1 Transmitter LAS/LM Disabling Procedure

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

IO_OPTS Bit 0: Invert Bit 1: SP-PV Track in Manual Bit 3: SP-PV Track in LO Bit 4: SP Track retained target Bit 6: FS to Value Bit 7: Use FS value on Restart Bit 8: Target to Man if FS Asserted Bit 9: Use PV for BKCAL_OUT

Yes/NoNot supported; do not useYesNot supported; do not useYes/NoYes/NoNot supported; do not useNot supported; do not use

User option; no constraint

Option required.

No constraint; see note below. No constraint; see note below.

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_SELparameter must be configured in the Resource block.

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

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

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

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

Control Station

(FCM)ECB110

(FBM220/221)ECB200

(H1 Device)ECB201

(H1 Device)ECB201

I/A Series28

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.

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

.OUTAI

RIN

To/from otherblocks (PIDA,control scheme

.CAS_INAO

.OUT_DDI

DO

(See Note)Function Blocks, I/A Series Control Software

ROUT

BIN

BOUT

etc.) in the

.CAS_IN_D

DCI BlocksInside Field Devices

.BKCAL_OUT_D

.BKCAL_OUT FBM220/221(InterfaceControl)Signal

NOTE:A field device may contain multiple function blocks, which can be accessed via multipleassociated DCI control blocks.29

B0400FD Rev D 5. Configuration Information 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/A Series system, a DCI block must be configured and connected to the appropriate ECB201 block. The RIN and BIN blocks connect to the primary output 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.

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

ECB201

Name PT_100Parent :SLOT03Dev_ID PT_100DevAddr Not UsedDev Name PT_100 RIN #1

Name PT_100IOMID CP6SG5_ECB:PT_100PNT_No PT_100A1

RIN #2

Name TT_100IOMID CP6SG5_ECB:PT_100PNT_No TT_100A1

ECB200

Name SLOT03Dev_ID SLOT03Portex 0= port 1

AI Block #1

H1 Device

PD_Tag*Function Block Tag*

AI Block #2

PD_Tag*Function Block Tag*

* Syntax must conform to that used in the Foxboro ICC or FoxCAEconfigurator, regarding upper/lower case, character string length, etc.30

5. Configuration Information B0400FD Rev D Configuration ProceduresProcedures 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).

Table 5-8. Key Parameters

Block/ECB Parameter Usage Typical SyntaxAI, AO, DI, and DO function blocks

OUT, OUT_D Contain values (analog, digital) to be accessed from the external device.

N/A

CAS_IN, CAS_IN_D

Contain values (analog, digital) trans-ferred to the field device.

N/A

AO and DO function blocks

BKCAL_OUT, BKCAL_OUT_D

Provide read-back values (analog, digital) and associated status; used for output confirmation purposes.

N/A

ECB201 PARENT Contains the user-configured path-name of the ECB200 (FBM220/221) hosting this field device.

:SLOT03(See Note below)

DVNAME Contains the user-configured PD tag-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 and special characters not allowed for this parameter.

PT_100

ECB200 NAME A user-configured name used by the control station to access this ECB.

SLOT03

DEV_ID User-configured letterbug of the FBM. It is copied into the DEV_ID parame-ter of each DCI I/O block connected to this ECB200.

SLOT03(See Note below)

BIN, BOUT, RIN, ROUT

IOMID Contains the user-configured path-name of the ECB201 (device ECB) associated with the field parameter to be accessed by this block.

CP6SG5_ECB:PT_100

PNT_NO Contains the Function Block Tag in the external device with which the DCI block input/output is to be associ-ated.

PT_100AI

BOUT, ROUT INI_PT A configurable string that specifies 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.

.OUT_D

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 Users Guide (B0400FA) for additional information.31

B0400FD Rev D 5. Configuration Information Block ProcessingThe following is an overview of block processing (and data read/write) operations.

NOTEScheduling 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

5. Configuration Information B0400FD Rev D DCI Block FunctionsSome 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 ExecutionAll 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 OperationAll 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 ModeThe 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 StampingAll 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 ScalingSignal 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 of the SCO conditioning algorithms, refer to the ROUT block [also in Integrated Control Block Descriptions (B0193AX)].

Input LimitingThe 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

B0400FD Rev D 5. Configuration Information Confirmed OutputsThe 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 ClampingThe 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 InitializationThe 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 InitializationUpstream 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 device34

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

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 a fail-safe timer for that connection to the Fail-Safe Delay (FSDLAY) value downloaded from the control station when the FBM220/221 is rebooted. The fail-safe timer 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 HandlingThe 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

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 B