B0750be L

Foxboro Evo™
Process Automation System
Implementing PROFIBUS
Networks in Foxboro Evo
Control Software Applications
*B0750BE* *L*
B0750BE
Rev L
October 4, 2016
All rights reserved. No part of this documentation shall be
reproduced, stored in a retrieval system, or transmitted by any means,
electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of the Schneider Electric
Systems USA, Inc. No copyright or patent liability is assumed with
respect to the use of the information contained herein. Although
precautions have been taken in the preparation of this documentation,
the publisher and the author assume no responsibility for errors or
omissions. Neither is any liability assumed for damages resulting
from the use of the information contained herein.
The information in this documentation is subject to change without
notice and does not represent a commitment on the part of Schneider
Electric Systems USA, Inc. The software described in this
documentation is furnished under a license or nondisclosure
agreement. This software may be used or copied only in accordance
with the terms of these agreements.
© 2006-2017 Schneider Electric. All Rights Reserved.
Trademarks
Schneider Electric, Invensys, ArchestrA, Foxboro, Foxboro Evo,
FoxView, I/A Series, InFusion, and InTouch are trademarks of
Schneider Electric SE, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
iii
Contents
Safety Information..............................................xi
Before You Begin .............................................xiii

About This Book ................................................................................. xiii
Revision Information ....................................................................... xiii
Reference Documents...................................................................... xiii
Software Installation ............................................................................ xv
Foxboro Evo Control Editors and Field Device Editor Setup .......... xv
CHAPTER 1: Introduction...................................1
System Architecture ............................................................................... 1
Foxboro Evo Hardware .......................................................................... 2
FBM222.............................................................................................. 2
Control Processors .............................................................................. 4
Field Terminations .............................................................................. 4
Example Configurations ..................................................................... 5
Foxboro Evo Control Software .............................................................. 7
FBM ECBs ......................................................................................... 7
Device Templates and Device ECBs .................................................. 7
Distributed Control Interface (DCI) Blocks ....................................... 7
Foxboro Evo Control Editors ................................................................. 8
FBM222 Editor................................................................................... 9
Field Device Editor............................................................................11
Field Device Manager ...................................................................... 12
Using the Manufacturer’s DTM ....................................................... 14
Operator Displays................................................................................. 15
System Manager ............................................................................... 16
Implementation Sequence .................................................................... 18
CHAPTER 2: Planning the Network .................19

PROFIBUS Paradigm .......................................................................... 20
PROFIBUS Devices............................................................................. 21
GSD Files ......................................................................................... 22
Device Addresses ............................................................................. 23
Supported Baud Rates ...................................................................... 24
DP Devices ....................................................................................... 25
Modular Devices............................................................................... 26
PROFIBUS-PA Devices ................................................................... 29
DP/PA Interface ................................................................................ 29
FBM222 PROFIBUS Network Connections ....................................... 33
Maximum Number of Devices ......................................................... 34
Implementing PROFIBUS Networks in Foxboro Evo Control Software Applications – B0750BE Rev L
iv Contents
Intrinsic Safety...................................................................................35
Multimaster Configurations ..............................................................35
The PROFIBUS Network .....................................................................35
Extending the Network......................................................................38
Media Redundancy ...............................................................................41
CHAPTER 3: Security .......................................45

Introduction...........................................................................................45
Enabling Security..................................................................................49
Setting Up Users ...................................................................................50
Modifying Roles ...................................................................................52
CHAPTER 4: Installing and Configuring the

FBM222 ..............................................................55
FBM Installation ...................................................................................55
Redundant FBMs, Single Networks ..................................................56
Connection to the PROFIBUS Networks ..........................................57
Installing for Media Layer Redundancy............................................58
Replacing an FBM223.......................................................................59
System Configuration for the FBM222 ................................................59
Adding the FBM222 .............................................................................60
Naming FBMs ...................................................................................63
Importing an FBM223 Configuration ...................................................65
Setting Bus Parameters .........................................................................67
Adding Graphics and Document Links .............................................75
Setting ECB200/202 Parameters...........................................................77
Deploying the FBM ..............................................................................81
Modifying a Deployed FBM .............................................................85
FBM Manager .......................................................................................86
Auto Online .......................................................................................86
FBM Manager Toolbar ......................................................................87
Context Menu ....................................................................................91
Use of Color in FBM Manager Displays...........................................92
FBM222 Diagnostics Tab..................................................................92
Live Lists ...........................................................................................94
CHAPTER 5: Creating Device Templates ......101

Introduction.........................................................................................101
Locating GSD Files.............................................................................103
Setting Up a Project Folder .................................................................104
Creating a Device Template ................................................................105
Associating a GSD File with a Template ............................................106
Associating a DTM with the Template ...............................................109
Contents v
Template Not Bound to a GSD File.................................................110

Template Already Associated with a GSD ......................................114
Running FDT v1.2.x and v2.0 DTMs in Separate Processes from
ArchestrA IDE.....................................................................................117
Enabling FDT v1.2.x and v2.0 DTMs To Run in Separate Processes
from ArchestrA IDE ........................................................................117
Disabling FDT v1.2.x and v2.0 DTMs To Run in Separate Processes
from ArchestrA IDE ........................................................................119
Switching to DTM-Based Module Definition.................................... 120
Changing GSD Information ............................................................... 124
Editing a Device Template: General Tab ........................................... 127
Object Information ......................................................................... 128
GSD Information ............................................................................ 129
Device Instances ............................................................................. 129
Managing Device Templates .............................................................. 130
Move the Template to Another Toolset Folder............................... 130
Derive New Templates ................................................................... 130
Create Instances .............................................................................. 131
Rename the Template ..................................................................... 132
Delete Templates ............................................................................ 132
Export the Template........................................................................ 133
CHAPTER 6: Defining the Network................139

Adding Slave Devices to an FBM...................................................... 140
Creating and Assigning a Single Device ........................................ 141
Creating and Assigning Multiple Devices...................................... 142
Importing an FBM223 Device Configuration.................................... 144
Modifying a Device Configuration .................................................... 145
Editing Device ECBs ......................................................................... 148
Reviewing Device Properties ......................................................... 149
Commissioning Devices..................................................................... 154
Updating Deployed Devices............................................................... 161
Exporting Device Configurations....................................................... 162
Organizing Devices by Plant Units .................................................... 165
Creating Plant Units........................................................................ 166
Assigning Plant Units ..................................................................... 167
Associating Devices ....................................................................... 168
CHAPTER 7: Configuring Devices.................171

Locking and Inheritance..................................................................... 171
Editing Device Bus Settings............................................................... 175
Selecting Device Modules.................................................................. 177
Modular Devices............................................................................. 178
Configuration Data ......................................................................... 180
Compact Devices ............................................................................ 181
vi Contents
Soft Modules ...................................................................................182

Configuring User Parameters..............................................................183
Defining I/O Points .............................................................................185
Defining Input and Output Parameters............................................188
Editing Diagnostic Messages and Parameters.................................198
Defining DPV1 Parameters .............................................................203
Configuration Using the Manufacturer’s DTM ..................................207
Gateway DTMs in the Vendor DTM Tab ........................................208
CHAPTER 8: Field Device Manager ...............217

Overview .............................................................................................217
Auto Online Option .........................................................................218
Field Device Manager Toolbar ........................................................219
Error Monitor...................................................................................219
Note Pad ..........................................................................................221
Field Device Manager Tabs.............................................................222
Use of Color in Field Device Manager Displays.............................223
Identification Tab ................................................................................223
Input and Output Tabs.........................................................................227
Diagnostic Tab ....................................................................................229
Watch Tab............................................................................................232
Configuration Data Tab.......................................................................237
Device Parameter (DPV1) Tab............................................................238
Compare Tab .......................................................................................240
Customize Tab.....................................................................................242
Setting Up Parameter Groups..........................................................243
Creating New Tabs ..........................................................................245
Setting Access Permissions .............................................................247
Setting Up Downloads.....................................................................249
CHAPTER 9: Control Configuration ..............253

PROFIBUS IO ....................................................................................255
I/O Timing .......................................................................................255
PROFIBUS/DCI Block Data Conversions......................................258
PROFIBUS DCI Block Usage ........................................................261
Point Configuration String Syntax ......................................................261
PA Status Handling..........................................................................265
Setting Up a Control Strategy .............................................................268
Creating the Control Compound and Strategy ................................268
Making the Field Connections ........................................................271
DCI RIN Block................................................................................278
DCI ROUT Block............................................................................282
Configuring Input DCI Blocks............................................................286
Analog Inputs ..................................................................................286
Digital Inputs ...................................................................................291
Contents vii
Configuring Output DCI Blocks ........................................................ 294

Analog Outputs............................................................................... 294
Digital Outputs ............................................................................... 297
DCI Block Data Types ....................................................................... 300
Using the Extended Data Type........................................................... 302
Using the Packed Bits Format............................................................ 303
Reading Diagnostic Data.................................................................... 304
Slave Diagnostics Details ............................................................... 304
Acyclic Data Exchange ...................................................................... 308
Acyclic Master Class 2 Read and Write Requests.......................... 308
PROFIBUS Live List.......................................................................311
Programming Sync and Freeze Actions ............................................. 312
CHAPTER 10: Configuration Examples ........315

PA Transmitter.................................................................................... 315
PA Positioner ...................................................................................... 318
Slave Device Module Selection...................................................... 318
Discrete PA Valve Controller ............................................................. 326
Slave Device Module Selection...................................................... 326
Foxboro Evo Device Configuration ............................................... 329
DP Motor Starter ................................................................................ 333
CHAPTER 11: Instrument Workshop

System .............................................................337
Workshop System Configuration ....................................................... 337
Setting up the Galaxy for a Workshop System ............................... 339
Importing to the Workshop System.................................................... 340
Configuring the Communication DTM.............................................. 343
Using the Vendor Communication DTM ........................................... 347
Configuring Devices in the Instrument Shop ................................. 349
CHAPTER 12: Change Tracking.....................351

Introduction ........................................................................................ 352
FDT Audit Trail .............................................................................. 353
Changing FBM222 Settings ............................................................... 353
Change Tracking for the FBM Manager tab ...................................... 354
Change Tracking for PROFIBUS Devices......................................... 355
General, Bus Settings, Modules and Data Definition Tabs ............ 355
Defined Parameters......................................................................... 357
Downloads from DTMs.................................................................. 358
Device Commissioning ...................................................................... 359
viii Contents
CHAPTER 13: System Management ..............361

FBM222 LED Indicators ....................................................................362
Identifying Modules in a Redundant Pair ...........................................364
System Manager..................................................................................365
FBM and Device Symbols ..............................................................366
FBM222 Equipment Information........................................................368
Redundant FBM222 General Tab....................................................368
Non-Redundant FBM222 General Tab ...........................................375
FBM222 Equipment Change Actions .................................................380
Managing Device Alarms................................................................381
Managing Cable Alarms..................................................................382
Go Online and Go Offline ...............................................................382
Download ........................................................................................383
DB Download..................................................................................384
EEPROM Update ............................................................................384
Switch Roles....................................................................................386
Enabling and Disabling Ports ..........................................................387
Device Display in the Connections Tab ..............................................387
Device Information Displays ..............................................................389
Equipment Status.............................................................................390
Equipment Information ...................................................................391
Device Equipment Change Actions ....................................................397
Responding to System Alarms............................................................398
FBM Displays in Foxboro Evo Control HMI .....................................400
ECB200/202 Faceplate....................................................................401
ECB200/202 Detail View ................................................................403
Device ECB Displays in Foxboro Evo Control HMI .........................408
ECB201 Faceplate ...........................................................................408
ECB201 Detail View .......................................................................410
FBM Displays in FoxView .................................................................415
Device ECB Displays in FoxView......................................................421
APPENDIX A: FBM223 Configurations..........429

Existing Configurations ......................................................................429
Adding an FBM223 ............................................................................429
Setting Up a Slave Device Type .........................................................433
Adding a Device Instance ...................................................................435
Control Configuration .........................................................................437
Download ............................................................................................438
APPENDIX B: FBM223 to FBM222 Upgrade

Procedure ........................................................439
Hardware Upgrade ..............................................................................439
Contents ix
Migrating FBM223 Database............................................................. 439

Upgrade with Integrated Control Configurator.................................. 440
Configuring a New ECB200........................................................... 440
Configuring a New ECB201........................................................... 441
Migrating DCI Blocks .................................................................... 442
System Management....................................................................... 442
Migrating Newer Slave Devices..................................................... 443
DCI Block Syntax Options ............................................................. 443
Upgrade with I/A Series Configuration Component (IACC)............. 443
Upgrade with Foxboro Evo Control Software ................................... 446
Creating a New ECB200/202 ......................................................... 446
Creating a Slave Device ECB201................................................... 447
APPENDIX C: DPV1 User Parameters ...........451

DPV1 Parameters and Configuration................................................. 451
Index ................................................................457
x Contents
Safety Information
Important Information
Read these instructions carefully and look at the equipment to
become familiar with the device before trying to install, operate, ser-
vice, or maintain it. The following special messages may appear
throughout this manual or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies
a procedure.
The addition of either symbol to a "Danger" or

"Warning" safety label indicates that an electrical
hazard exists which will result in personal injury if
the instructions are not followed.
This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety messages
that follow this symbol to avoid possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and main-
tained only by qualified personnel. No responsibility is assumed by
Schneider Electric for any consequences arising out of the use of this
material.
A qualified person is one who has skills and knowledge related to the con-
struction, installation, and operation of electrical equipment and has
received safety training to recognize and avoid the hazards involved.
xiii
Before You Begin
About This Book

This document describes how to configure and maintain PROFIBUS devices
using the Field Device Manager in the Foxboro® Evo™ Control Editors
(hereinafter referred to as Control Editors), part of the Foxboro Evo Control
Software (hereinafter referred to as the Control Software).
The Field Device Manager enables management of PROFIBUS devices,
including definition of device templates, device configuration and
commissioning, and tuning and maintenance.
The document also covers installation of the devices using the redundant
FBM222, development of control strategies in the Control Editors using
distributed control interface (DCI) blocks, and operator and system
management displays.
Revision Information
For this revision of this document (B0750BE, Rev. L), these changes were
made:
Global
• Rewrote all safety messages.
• Updated terminology to meet safety standards.
Chapter 3, “Security”
• Added the SafetyInstrumentEngineer user role to “Introduction” on
page 45.
Chapter 5, “Creating Device Templates”
• Added “Running FDT v1.2.x and v2.0 DTMs in Separate Processes from
ArchestrA IDE” on page 117.
Reference Documents
Refer to these Foxboro Evo Control Software documents for specific
information about the Foxboro Evo Control Editors:
• Block Configurator User’s Guide (B0750AH)
• Bulk Data Editor User’s Guide (B0750AF)
• Hardware Configuration User’s Guide (B0750BB)
• Control Database Deployment User’s Guide (B0750AJ)
xiv Before You Begin
• Foxboro Evo™ Process Automation System Deployment Guide

(B0750BA)
• Framer and Alarm Management User’s Guide (B0750AR)
• Control HMI Application User’s Guide (B0750AQ)
• Window Construction User’s Guide (B0750AS)
• Foxboro Evo Control Software Installation Guide (B0750RA)
• Strategy Editor User’s Guide (B0750AN)
• System Manager (B0750AP)
Refer to these system documents for additional information on Foxboro
stations and control software:
• Control Processor 270 (CP270) and Field Control Processor 280 (CP280)
Integrated Control Software Concepts (B0700AG)
• Standard and Compact 200 Series Subsystem User's Guide (B0400FA)
• FoxView™ (B0700FC)
• Field Control Processor 280 (FCP280) User's Guide (B0700FW)
• Field Control Processor 280 (FCP280) Sizing Guidelines and Excel®
Workbook (B0700FY)
• Field Control Processor 270 (FCP270) User’s Guide (B0700AR)
• Field Control Processor 270 (FCP270) Sizing Guidelines and Excel
Workbook (B0700AV)
• Z-Module Control Processor 270 (ZCP270) User's Guide (B0700AN)
• Z-Module Control Processor 270 (ZCP270) Sizing Guidelines and Excel
Workbook (B0700AW)
• Integrated Control Block Descriptions (B0193AX)
• PROFIBUS-DP™ Communication Interface Module (FBM223) User’s
Guide (B0400FE)
Refer to FoxCTS Change Tracking Software Configuration and Administration
Guide (B0193VV) for information on setting up and using FoxCTS.
These documents are available on the Foxboro Evo Electronic Documentation
media (K0174MA). The latest revisions of each document are also available
through our Global Customer Support at https://pasupport.schneider-
electric.com.
This is a partial listing of the documents available at the PROFIBUS website
(http://www.profibus.com):
• PROFIBUS Specification (FMS, DP, PA)
• Installation Guideline for PROFIBUS-FMS/DP
• PROFIBUS Interconnection Technology
See also:
• Ronald W. Mitchell. PROFIBUS – A Pocket Guide. Research Triangle,
NC: ISA-The Instrumentation, Systems, and Automation Society, 2004
Before You Begin xv
• Christian Diedrich and Thomas Bangemann, et al. PROFIBUS PA,

Instrumentation Technology for the Process Industry. Essen, Germany:
Oldenbourg Industrieverlag, 2007
• SIMATIC NET PROFIBUS Networks, Siemens, Document Number
6GK1970-5CA20-0AA1.
Software Installation
Foxboro Evo Control Editors and Field Device

Editor Setup
Refer to these documents for information on installing and setting up the
Control Editors and Field Device Manager:
(B0750BA)
• Foxboro Evo Control Software Installation Guide (B0750RA, Rev. R or
later)
Note The PROFIBUS Support needs to be installed on the server (Galaxy

Repository) and the client workstation in order to use the editors for the
FBM222 and PROFIBUS slave devices on the client workstation.
Note The Control Editors are applications built over the ArchestrA®
Integrated Development Environment (IDE). In this document and in the
software some functions are referred as IDE functions, others are called the
Control Editors functions.
xvi Before You Begin
1
C H A P T E R 1
Introduction
This chapter describes Foxboro Evo Control Software (hereinafter referred to

as the Control Software) support for PROFIBUS networks including device
configuration using the Field Device Editor.
Contents
• System Architecture
• Foxboro Evo Hardware
• Foxboro Evo Control Software
• Foxboro Evo Control Editors
• Operator Displays
System Architecture
The Control Software offers the optionally redundant FBM222 to connect
PROFIBUS slave devices with the advanced Field Control Processor (FCP280
or FCP270) operating on The Mesh control network, a 100-megabit switched
network. The FBMs and the FCP280s need to be installed in connected
baseplates. The FBMs and the FCP270s can be installed in the same baseplate
or connected baseplates. The baseplates and connecting cables form a
redundant 2 Mbit module fieldbus.
Optionally, the FBM222 can be installed in a DIN rail mounted FBM
subsystem and connected through an FCM100Et or an FCM100E and The
Mesh Network to the Z-Module Control Processor 270 (ZCP270).
The FCP280, FCP270, ZCP270, and the FBM222 support a set of Distributed
Control Interface (DCI) blocks that integrate the I/O signals from PROFIBUS
slave devices using digital bus communication.
The Foxboro hardware and Foxboro Evo Control Core Services (hereinafter
referred to as the Control Core Services) control database are configured in the
Control Editors. The Control Software graphical editors and template libraries
enable rapid configuration of application objects including the DCI blocks and
templates for PROFIBUS device types. The Field Device Editor for
PROFIBUS enables editing of device parameters at the template and instance
levels based on the General Slave Device (GSD) files supplied by the device
manufacturers or on the manufacturers’ Device Type Manager (DTM). The
Control Editors provide life-cycle maintenance for slave devices connected to
2 1. Introduction
the Foxboro Evo Process Automation System (hereinafter referred to as the

system), including:
• Development and maintenance of the device database
• Integration of the PROFIBUS slave devices into the control database
using the DCI blocks
• Start-up diagnostics and device maintenance
• Connections to historian, asset management, and change-tracking
applications.
Foxboro Evo Hardware
FBM222
The Redundant PROFIBUS Communication Interface Module (FBM222)
provides an interface between the control system and PROFIBUS slave
devices, including motor drives, I/O modules, and PA device link/couplers and
field devices.
The FBM222 operates on:
• A workstation with I/A Series software v8.4.1-v8.8 or Control Core
Services v9.0 or higher (which needs Foxboro Control Software v3.0-v4.x
or Foxboro Evo Control Software v5.0 or higher), or
• A non-Foxboro workstation with InFusion® software v1.1-v2.x, Foxboro
Control Software v3.x-v4.x, or Foxboro Evo Control Software v5.0 or
higher.
However, use of Field Device Manager with the FBM222 needs I/A Series
software v8.4.2-v8.8 or Control Core Services v9.0 or higher and InFusion
ECS software v1.2-v2.x, Foxboro Control Software v3.x-v4.x, or Foxboro Evo
Control Software v5.0 or higher.
The FBM222 (Figure 1-1) provides two PROFIBUS links and supports up to
125 slave devices per port for a total of 250 devices per FBM222.
Physical PROFIBUS wiring is in accordance with Electronic Industrial
Association (EIA) standard RS-485.
1. Introduction 3
FBM228/FBM222 Redundant
Adapter (P0922RK)
FBM222 Termination
Assembly P0926TH Redundant FBM222
Figure 1-1. Redundant FBM222 and DIN Rail Mounted Termination

Assembly
The FBM222 communicates with the PROFIBUS I/O devices on a

master/slave basis. As a master, the FBM222 initiates each data
communication exchange. The slave devices can only acknowledge received
messages, or send messages to the master when requested to do so.
Key features of the FBM222 are:
• Integrates PROFIBUS-DP and PROFIBUS-PA slave devices into the
control system
• Conforms to the PROFIBUS – DP Specification IEC61158 Part 3
• Supports up to 250 slave devices (125 per port) with entire 244 byte data
transfer in a redundant or non-redundant FBM222 configuration
• Maximizes uptime by providing redundant termination assemblies, hot
swapping redundant FBM modules along with fully redundant
communication between the FBM222 and fault-tolerant control processors
• Propagates the PROFIBUS-PA device value and status to the Control Core
Services control block
• Provides a user-selectable status parameter for input data as well as read-
back values for output data
• Features both Class 1 and Class 2 Master functionality and can co-exist
with third-party Class 1 and Class 2 Masters in a multimaster environment
• Supports the existing FBM223 Termination Assembly to preserve
installed wiring and cable infrastructure allowing an upgrade from an
FBM223 to an FBM222
• Provides two galvanically isolated PROFIBUS channels
• Suitable for installation in Class 1, Division 2 and Zone 2 locations.
4 1. Introduction
Control Processors
The FBM222 can be used with the FCP280, FCP270, or ZCP270. In these
cases, you can implement a fully redundant interface with no single point of
detected failure between the field terminations and the control process
including the module fieldbus and trunk fieldbus, the FBMs, and the
PROFIBUS network.
FCP280 or FCP270
The configurations in Figure 1-2 and Figure 1-3 include FBM222s that are
installed in a baseplate cabled to an adjacent baseplate in which the fault-
tolerant Field Control Processor 280 (FCP280) are mounted. (FBM222s
connect with the FCP270s in a similar manner.) The baseplates and cabling
provide a 2 Mbit local fieldbus connecting the FBMs and the control processor.
Each pair of FBMs is connected to the PROFIBUS networks through a
termination assembly. The cable from the termination assembly is plugged into
the redundant adapter immediately below the two FBMs. There are many
variations on this setup. For example, the FCP270 and the FBM222s can be
installed in the same 4-position or 8-position baseplate. (The FCP280s need to
be installed in their own dedicated two-position baseplates.)
Refer to the Standard and Compact 200 Series Subsystem User's Guide
(B0400FA) for a description of the various mounting and installation options.
ZCP270
When the FBM222 provides the PROFIBUS interface for a Z-Module Control
Processor (ZCP270), the FBMs are installed in a DIN rail mounted FBM
subsystem. The modules are connected to the ZCP270 via FCM100Et or
FCM100E Fieldbus Communication Modules (FCMs) installed in the
subsystem and a 100-Mbit switched Ethernet trunk fieldbus. There are several
different baseplate configurations for the FBM subsystem, and a variety of
ways of connecting the subsystem to ZCP270. Refer to the Standard and
Compact 200 Series Subsystem User's Guide (B0400FA) for a description of
the various mounting, installation, and networking options.
Field Terminations
Field I/O signals connect to the FBM222 through a DIN rail mounted FBM222
Active Termination Assembly (TA) (P0926TH).
The TA and its associated termination cable provide feed-through connection
between PROFIBUS compliant field devices and the FBM222. The P0926TH
is constructed of a polypropylene material; a version of the TA using
polyamide (RH926TJ (supersedes P0926TJ)) is also available.
The DIN rail mounted TA connects to the Modular Baseplate by means of a
removable termination cable. The cable is available in a variety of lengths, up
to 30 meters (98 feet), allowing the TA to be mounted either in the enclosure
with the FBM or in an adjacent enclosure. The cable length is not included in
determining the maximum network cable length.
1. Introduction 5
The TA accepts two standard PROFIBUS Sub-D connectors, one for each port.
When the TA is at the end of the segment, a switch in the connector is used to
enable the network termination. When the termination is at mid-segment, the
switch is used to disable the network termination.
The FBM222 also supports the FBM223 Passive Termination Assembly
(P0917SY), enabling FBM223 owners to upgrade to the redundant PROFIBUS
communication interface without replacing the TAs and associated field
wiring. When the FBM223 TA is used, the TA cable length needs to be
included twice in determining the maximum network length.
Example Configurations
Single PROFIBUS Networks

There are multiple ways to connect FBM222s installed as a redundant pair to a
PROFIBUS network. When the PROFIBUS segments are single networks as
shown in Figure 1-2, an FBM228/FBM222 Redundant Adapter (P0922RK)
connects a single termination cable to the redundant pair. The other end of the
cable is plugged into a termination assembly, which provides connections for
the two network segments.
Connection to The MESH Control Network
Redundant 2 Mbps
Module Fieldbus
Redundant FBM222 Pair
Fault Tolerant
Field Control Processor
FCP280 FBM228/FBM222
Redundant Adapter
(P0922RK)
Termination assembly
P0926TH
Port for other
segment
One of two PROFIBUS networks

up to 31 slave devices per un-extended segment
T
Figure 1-2. Redundant Interface with a Single PROFIBUS Network
6 1. Introduction
Dual Media Networks

When the segments include dual media, two TAs are connected through
termination cables and the FBM222 Redundant Adapter - Dual Network
(P0926XM). The TAs in turn are connected to each network by third-party
redundant link modules, such as the ABB™ Redundant Link Module
(RLM01) or the Siemens® Optical Link Module (OLM). The network can
have dual-point devices if they are compatible with the corresponding
redundant link module. Refer to “Media Redundancy” on page 41 for
additional information on the design and operation of dual media networks
using these products.
Redundant 2 Mbps
Module Fieldbus
Fault Tolerant FBM222 Redundant

Field Control Processor Adapter -Dual Network
FCP280 (P0926XM)
Termination Termination
assembly assembly
P0926TH P0926TH
Port for other Port for other
segment segment
Third-party Third-party
redundant redundant
link module link module
A B A B
A
T T
Dual Media Network
B
T T
Third-party
redundant
link modules
One of two PROFIBUS dual media

segments of up to 31 dual-port and single-port
slave devices per un-expanded segment
1. Introduction 7
Figure 1-3. Redundant Interface with a Dual Media Network
Migration from the FBM223

The FBM222 supports the TA (P0917SY) and associated termination cable
used to connect the FBM223 to PROFIBUS networks, enabling an upgrade
from FBM223 to the redundant FBM222 without disruption to the installed
slave devices and network wiring.
Appendix A, “FBM223 Configurations” describes the Control Software
support for the FBM223.
Foxboro Evo Control Software

Input to and output from the PROFIBUS slave devices are integrated into the
control system through Equipment Control Blocks (ECBs) that represent the
FBM222 and the slave devices, and Distributed Control Interface (DCI) blocks
that map to the device data.
Refer to Integrated Control Block Descriptions (B0193AX) for information on
block operation and parameters.
FBM ECBs
When an FBM222 is added to the control configuration in the Control Editors,
an ECB200 is created to represent the FBM. If the FBM is then configured as a
redundant pair, the ECB is changed to an ECB202.
Device Templates and Device ECBs

One of the first steps in configuring a PROFIBUS network is to define the
slave devices that you need to install on the network. A device is defined by
importing the manufacturer-supplied GSD file that describes the device and
version into a template in the Control Editors. Alternatively, a device can be
defined by associating the device manufacturer’s DTM with the template, in
which case the GSD information is extracted from the DTM.
As each PROFIBUS slave device is added to the FBM, an ECB201 is created
from the appropriate device template.
The ECB201 points to its parent ECB200/202 to identify the FBM222, holds
the port number and network address of the device, and provides information
about the device’s configured modules.
Distributed Control Interface (DCI) Blocks

There are 17 different DCI block types in the Foxboro Evo system that can be
used to connect control blocks to PROFIBUS device data. Table 1-1 lists the
8 1. Introduction
blocks available for each data and I/O type, including those DCI blocks that
provide multiple inputs or outputs.
Table 1-1. Data Types Supported by DCI Blocks
DCI Block Data Types

BIN, BINR Boolean, Channel bit
IIN, IINR Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended,
Diagnostic
PAKIN, PAKINR Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended,
Diagnostic
RIN, RINR Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended,
Diagnostic
STRIN Real, Diagnostic
BOUT, BOUTR Boolean, Channel bit
IOUT Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended
PAKOUT Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended
PLSOUT Boolean, Channel bit
ROUT, ROUTR Float, Boolean, Unsigned Integer, Signed Integer, Real, Packed, Extended
STROUT Real
The IO module ID (IOM_ID) parameter in the DCI block contains the path
name of the slave device ECB, and the point number parameter (PNT_NO, for
example) specifies the portion of the slave device data that is to be processed
by the block.
The DCI block can be configured to perform these tasks:
• Map to data in the cyclic device data
• Combine an input value with a user-defined status parameter
• Combine an output value with a user-defined read-back parameter
• Get a live list of devices connected to the FBM
• Control Sync and Freeze operations
• Read and write acyclic device parameters.
Configuration of the DCI blocks is covered in “Control Configuration” on
page 253.
Foxboro Evo Control Editors

The Control Editors, which are implemented in the ArchestrA Integrated
Development Environment (IDE), provides graphical and menu-driven editors
for defining system hardware and building control loops. Figure 1-4 shows an
analog PID loop being constructed in the Strategy Editor from application
object templates in the Template Toolbox, in this case the RIN and ROUT
blocks and the PIDA control block. The blocks are added to the strategy by
dragging the templates from the toolbox and dropping them in the Strategy
Editor. The blocks are then connected by dragging the cursor from a source
1. Introduction 9
parameter in one block to the sink parameter in another. Other Control Editors
editors are used to configure the blocks and compounds, connect the DCI
blocks to the slave devices, and deploy the completed strategy to the control
processor.
The Control Editors also offers a wide range of options in developing control
applications from libraries of re-usable engineering, including strategy
templates, custom compound and block definitions, and bulk generation of
control and device configurations.
Figure 1-4. Developing a Control Strategy in Foxboro Evo Control

Editors
The Control Editors provide a link to FoxCTS Change Tracking software

(FoxCTS) so you can automatically record control configuration changes for
OSHA 1910 and 21 CFR Part 11 compliance. Refer to Chapter 12, “Change
Tracking” and to Control Database Deployment User’s Guide (B0750AJ) for
additional information on the Control Editors change tracking.
FBM222 Editor
One of the Control Editors is used to set up the FBM222 as either a single
module or redundant pair, and configure master-specific communications
parameters for each FBM222 port.
10 1. Introduction
Figure 1-5 shows configuration of an FBM222’s bus parameters such as the

station’s address, and the data transfer rate and other master settings.
Figure 1-5. Setting FBM222 Bus Parameters
The editor’s FBM Manager tab contains a communication DTM that

provides online diagnostics of the FBM222 and its communications with
the attached devices, and a live list for each of the two PROFIBUS ports
(Figure 1-6). The live lists provide identification data uploaded from the
devices, additional device diagnostics, and the ability to change the
address of devices that support remote address setting.
1. Introduction 11
Figure 1-6. Live List for an FBM222 Port
Field Device Editor

The Field Device Editor enables editing of device configurations in both the
device template and individual devices. Editing at the template level provides a
convenient way to implement project standards across the devices, while
editing of individual device instances provides the flexibility to adjust device
performance before and after startup.
The editor presents configuration choices based on the information extracted
from the GSD. Figure 1-7 shows modules being configured for a remote I/O
device to match the modules that are physically installed in the device.
When a device is derived from a template, the configuration choices made in
the template are copied to the device, providing a starting point for setting up
the device. You can lock certain settings and device parameters values in the
template such that they cannot be modified in the derived devices. Subsequent
changes to these locked parameters in the template are propagated to the
devices already created from the template. Unlocked parameters can be
changed in the device and do not inherit changes made to the template. See
“Locking and Inheritance” on page 171 for further details.
12 1. Introduction
Figure 1-7. Selecting Modules for a Device
The Field Device Editor Data Definition tab is used to define parameters for
input and output data, device diagnostic data, and, if the device supports DPV1
functions, DPV1 device data. The tab also enables editing of diagnostic
messages.
The parameters defined in this tab are used in the Field Device Manager for
online access to the device data, and in various Control Editors device
browsers to facilitate connection of DCI blocks to the appropriate device data.
Field Device Manager

The editor’s Field Device Manager tab contains a universal PROFIBUS
Device Type Manager (DTM) that enables online access to each device for
viewing I/O data, diagnostics, and uploading and downloading of DPV1
device parameters. Field Device Manager includes:
• Standard tabs for viewing input and output parameters and diagnostic
messages
• Watch tab that provides history for up to eight parameters using a data
table and a trend display
1. Introduction 13
• Configuration Data tab that compares the connected device with its
configuration in the Control Editors
• Tabs for configuring DPV1 device parameters, aligning device values with
the database values in the Control Editors, and monitoring the parameters
using a data table and a trend display (Figure 1-8).
Figure 1-8. Device Parameter (DPV1) Tab
You can customize the Field Device Manager displays, selecting which
parameters are to be displayed and the rate at which data is uploaded from the
device.
Field Device Manager also includes tools for creating and editing custom
displays, specifying access permissions to functions and parameters, and
setting up download for DPV1 device parameters.
14 1. Introduction
Using the Manufacturer’s DTM

In some instances, you may want to use a DTM supplied by the device
manufacturer for device configuration and online access, in which case you
can associate the device template with the vendor’s DTM instead of
associating the template with the GSD file. The GSD information is extracted
from the DTM and bound to the template.
When a DTM is associated with the device template, the DTM is available in
the Vendor DTM tab in Field Device Editor. Figure 1-9 shows the DTM for a
positioner opened in the Vendor DTM tab. The manufacturer’s software can be
used for configuration and tuning of the device, download and upload of DPV1
device parameters, and diagnostics and maintenance. Work done in the Vendor
DTM tab is saved with the device database in the Galaxy.You can select this
tab or Field Device Manager tab to use either the device manufacturer’s DTM
or the universal PROFIBUS DTM built into Field Device Manager.
Figure 1-9. Vendor DTM Tab
Note Manufacturer-supplied DTMs may vary in their full compliance with

PROFIBUS and FDT specifications. Please confirm the applicability of each
vendor-supplied DTMs for your project
Refer to “Associating a DTM with the Template” on page 109 and

“Configuration Using the Manufacturer’s DTM” on page 207 for information
on using vendor DTMs.
1. Introduction 15
Operator Displays
Two options are available for block displays to monitor control blocks and
ECBs: FoxView™ and the Foxboro Evo Control HMI (hereinafter referred to
as the Control HMI).
DCI block displays in these applications enable you to view the values and
status from the slave devices and acknowledge process alarms. Figure 1-10
shows a Control HMI faceplate and trend for ROUT block, which outputs a set
point to a slave device.
Figure 1-10. RIN Faceplate and Trend in Foxboro Evo Control HMI
FBM222 and device ECB displays show the current status and configuration of
the master and slave devices, and enable you to respond to detected error
conditions associated with devices. Figure 1-11 is a FoxView detail display for
an ECB201 for an Acromag discrete I/O module.
16 1. Introduction
Figure 1-11. FoxView Device ECB Detail Display
See “System Management” on page 361 for additional information about ECB
displays in FoxView software and the Control HMI.
System Manager
Use the System Manager to monitor FBM222 and device ECBs, respond to
system alarms and troubleshoot slave devices.
When an FBM222 is selected, System Manager provides these tools for
monitoring and changing equipment status:
• Status and Equipment Information tables in the General tab in the
Information pane
• A display of the attached slave devices indicating the segment to which
they are attached
• Status of connected slave devices in the Information pane Connections tab
• Context menu of equipment change actions, including bringing the
module online and offline, and acknowledging device alarms.
1. Introduction 17
When one of the attached slave devices is selected, System Manager provides
these tools for monitoring and changing equipment status:
• Status and configuration information in the General Tab in the Information
pane (Figure 1-12).
• Context menu of equipment change actions including enabling/disabling
communications between the device and the FBM, inhibiting/enabling
device alarms, and acknowledging device alarms.
Figure 1-12. Equipment Status and Information for a Slave Device
In addition, the System Manager Accessories pane displays alarms, messages,

equipment for which alarms are inhibited, a watch list for system counters, and
system monitor logs. The Accessories pane also features a search tab for
finding and navigating to devices and other equipment. For detailed
information on System Manager features, refer to System Manager
(B0750AP).
PROFIBUS related System Manager features are covered in “System
Management” on page 361.
18 1. Introduction
Implementation Sequence
This section suggests a schedule of actions for implementing a PROFIBUS
network on a control system using the FBM222 and the Control Editors
resources. The steps outlined in Figure 1-13 assume that the Foxboro Evo
Control workstation and the host control processor have been configured,
installed and brought online.
Start
1 9
Develop Device List; Validate the FBM222
Acquire GSD files, DTMs master bus settings
2 10
Install FBM222 Create compound and
and Termination
and TAsAssembly strategy; add DCI blocks
3 Connect DCI blocks 11

Configure FBM222 and set to device ECBs;
modules
masterand
busbus
parameters
parameters specify points
4 12
Deploy FBM222 Redeploy control processor
to the control processor
5 13
LoadLoad
GSDall GSD
files files
(and DTMs) Install devices on the
on the
onInFusion workstation
the workstation PROFIBUS network
6 14
Create device templates; Bring the devices online
edit device parameters using System Manager
7 15
Review sizing guidelines Verify DCI block operation
and estimating spreadsheets using block displays
8 End
Add devices to the FBM;
configure their modules
Figure 1-13. Typical Implementation Sequence
Note You can import GSD information into a device template by associating
the template with the GSD file or by associating the template with a DTM
provided by the device manufacturer. You can edit then the template and its
derived devices with Field Device Editor and/or an associated vendor DTM.
19
C H A P T E R 2
Planning the Network
The FBM222 features two ports for connecting PROFIBUS networks. Each
network can support up to 32 devices on an un-expanded segment. Either or
both segments can be expanded through the use of repeaters to support a total
of 125 devices per port for a total of 250 per FBM222. (See “Maximum
Number of Devices” on page 34 for a description of what is included in the
device count). The two networks operate independently of one another, and
can be set to operate at different baud rates and connect various mixes of
PROFIBUS-DP and PROFIBUS-PA devices.
This chapter provides general information about PROFIBUS devices and
network topologies to assist in planning integration of a PROFIBUS network
into the control system. Refer to these documents for sizing information:
Workbook (B0700FY)
Workbook (B0700AV)
Workbook (B0700AW).
These sizing spreadsheets include worksheets for determining the number of
maximum inputs and outputs. Each workbook includes a separate spreadsheet
for estimating FBM222 loading.
As part of your planning effort, you also need to review the Control Software
and PROFIBUS reference material listed in “Revision Information” on
page xiii, as well as the manufacturer’s documentation for each device to be
deployed in the application.
Contents
• PROFIBUS Paradigm
• PROFIBUS Devices
• FBM222 PROFIBUS Network Connections
• The PROFIBUS Network
• Media Redundancy
20 2. Planning the Network
PROFIBUS Paradigm
Figure 2-1 is an example PROFIBUS application, in which a Programmable
Logic Controller (PLC) acts as the Master with a communications bus
connecting a range of slave devices to that master. In this architecture, the
slaves are parameterized through the Master and the communications/control
functions are master/slave direct.
Figure 2-1. PROFIBUS Master/Slave Architecture
Figure 2-2 shows the integration of a PROFIBUS network into a control

system. Here, the FBM222 serves as the Master to the connected slaves.
However, the architecture is extended by the introduction of a Foxboro Evo
Control Core Services workstation and a control processor (CP) connected
over The Mesh network. The workstation acts as the user interface (HMI) and
the CP host, while the CP communicates with the FBM222 to pass data to/from
field devices through the FBM222. The Mesh Network connects the
workstation and CP to other control system resources including workstations
with the Control Editors and Field Device Editor for PROFIBUS. This
extended architecture introduces a certain measure of implementation
complexity, but also enables significant gains in application capabilities.
2. Planning the Network 21
Foxboro Evo Control

Control Core Services
workstation provides
workstation (WSTA70)
configuration support
is the CP host
The MESH Network
Field Control FBM222 is a PROFIBUS master and

Processor Module
redundant interface to the
(FCP280) fieldbus
distributed control system
Figure 2-2. Foxboro Evo Control Core Services PROFIBUS

Architecture
In this architecture the FBM222 assumes the role of a true PROFIBUS Master,
cyclically exchanging data with its slave devices independent of the Basic
Processing Cycle (BPC) of the CP.
Note With a redundant FBM222, the control processor can access the FBM
data in a BPC of 500 ms. Do not configure the control processor for a faster
BPC if using a redundant FBM222. With a non-redundant FBM222, the BPC
can be as fast as 100 ms.
Master/Slave communication is asynchronous to the CP’s block processing

interval.
The FBM accepts data from its slaves and writes data to its slaves, while
concurrently accepting data from the CP and writing data to the CP. The FBM
acts as an interposing master between the CP and PROFIBUS slave devices.
In this architecture, it is the workstation that is the ultimate repository of the
configuration data for CP-resident DCI interface blocks, FBM configuration
data, and much of the device configuration data necessary for correct device
operation.
PROFIBUS Devices
In the previous chapter, the first step in a project implementing a PROFIBUS
network in the Control Editors is to build a device list that is used during
device and control configuration and during installation of the devices on the
network. Such a list could include the device manufacturer, model number and
revision, PROFIBUS identification number and serial number, and planned
location and function. The list needs to include the elements, which is used
(and updated) during setup of the device in the Control Editors and actual
physical installation on the PROFIBUS network:
• Device Tag
• GSD File, and DTM

• Baud Rate
• Modules
• FBM222 Host and Port Number
• Network Address
Note You can import GSD information into a device template by associating
the template with the GSD file or by associating the template with a DTM
provided by the device manufacturer. You can then edit the template and its
derived devices with Field Device Editor and/or an associated vendor DTM.
GSD Files
The capabilities of each PROFIBUS device model is described in the General
Slave Data (GSD) file supplied by the device manufacturer.
A general description of GSD files, including examples, can be found at
http://www.Profibus.com. The files can usually be downloaded in a
compressed folder from the manufacturer’s web site, and then extracted to a
temporary folder.
GSD files, which you can open with a text editor such as Notepad, use a
keyword format. The portion of the GSD for an Acromag device in Figure 2-3
indicates the data transfer rates supported by the device, the maximum station
response delay (MaxTsdr) at each baud rate, and support for various operating
modes.
Figure 2-3. Sample GSD File
Device Addresses
Each PROFIBUS master and each slave device need a unique address on the
network served by the FBM222 port. The range for address on each port is 0 to
125. The low end of the range needs to be used for master devices (including
the FBM222).
The addresses reserved for master stations are defined in each master device.
Stations with an address in that range are involved in token-passing, devices
outside the range are excluded. It is recommended that the single-digit
addresses on each segment be reserved for master devices, and that slaves be
assigned in the range 10 to 125.
In a multimaster environment, the master stations need to have different
addresses in the same master station range.
Each module in a redundant FBM222 is assigned a unique address. The
address selected during configuration of the module is applied to the module
acting as the PROFIBUS master and the next higher address is applied to the
module tracking the master to be ready to take over in the event of a detected
failure in the first module. Thus for example, if you assign 1 to a redundant
FBM, that address is used by the master module and 2 is used by the tracker
and is not available for any other station or device.
The address assigned to a slave during network configuration has to match the
address configured in the device itself. Device manufacturers provide a variety
of ways to set the address including rotary dials that set the address in decimal,
dials that set the address value in hexadecimal, and dip switches.
Note Some devices can only be set to an address in the range 0 to 99.
Finally, many vendors provide for the facility for setting the slave device
address from a PROFIBUS master through the Set Slave Address command.
For these devices, you can change the address using the Live List tab in the
FBM Manager (refer to “FBM Manager” on page 86) or the InFusion
Commissioning Wizard (as described in “Commissioning Devices” on
page 154).
A PROFIBUS-PA device may or may not need a unique address depending on
whether its gateway to the DP network is a transparent coupler, in which case
the device needs an address, or a non-transparent coupler, in which case the
coupler itself is assigned an address and the linked PA devices are treated as
modules at that address. See “DP/PA Interface” on page 29.
The Field Device Editor has an automatic address assignment option in which
a device is assigned the next available address on the port starting with a user-
specified number. This option can be disabled if the addresses have already
been set in the devices (see “Adding Slave Devices to an FBM” on page 140).
Supported Baud Rates

The FBM222 supports PROFIBUS data transfer rates from 9.6 Kbaud to
12 Mbaud, as do many, but not every slave device. In fact, many devices are
limited to 1.5 Mbaud.
The baud rate is set separately for each of the two PROFIBUS ports (as
described in “Setting Bus Parameters” on page 67). The master needs to
operate at a rate supported by all its devices served by the port (i.e. the baud
rate of all the devices and the master must match). You need to verify the
supported baud rates for each DP slave device and the DP interface of each
DP/PA coupler used on the network.
Some slave devices need that the baud rate be manually set with a rotary dial,
DIP, or similar switch. Other devices automatically detect and adopt the baud
rate on the DP network, as indicated by Auto_baud_supp=1 in their GSD
files.
In addition to determining a rate that is supported by the devices on the
segment, you need to also balance the network speed versus the maximum
length of the segment, as shown in Table 2-1.
Table 2-1. Maximum PROFIBUS Bus Segment Length
Data Transfer Rate (Kbit/s) Maximum Segment Length (m)

9.6 1000
19.2 1000
Table 2-1. Maximum PROFIBUS Bus Segment Length (Continued)
Data Transfer Rate (Kbit/s) Maximum Segment Length (m)

45.45 1000
93.75 1000
187.5 1000
500 400
1500 200
3000 100
6000 100
12000 100
Refer to “The PROFIBUS Network” on page 35 for additional information on
segment length.
DP Devices
At the physical layer, slave devices are divided into two broad classes:
PROFIBUS-DP devices and PROFIBUS-PA devices. Their physical interfaces
are quite different (RS-485 versus MBP-IS) and a gateway is needed for a PA
slave device to communicate with a master over the DP network. However,
once that link is made, both device types use the same protocol for data
exchange.
PROFIBUS DP devices are further divided into Compact and Modular
devices.
Compact Devices
Compact devices, such as the Acromag 981PB-2012 in Figure 2-4, have a
fixed I/O functionality. The 981PB-2012, for example, accepts 12 digital
inputs and has no other capabilities that can be altered by configuration. The
GSD file (Acro06F3.GSD) for this device contains the keyword
(Modular_Station = 0) that indicates that it is a compact device.
Figure 2-4. Acromag 981PB-2012 (12DI)
Modular Devices
The more significant group of commercially available PROFIBUS devices is
the large family of modular devices, identified in their GSD files with the
keyword Modular_Station = 1.
This family in turn has a number of different device types, the major groups of
which are presented here.
Remote I/O Systems

There are currently more than 50 vendors with one or more remote I/O system
offerings and many of these vendors have multiple offerings to cover the high
and low ends of the market.
A remote I/O system needs only one address on the PROFIBUS network. The
FBM222 communicates with the connected I/O devices as modules at the one
address.
Note When sizing the system and the network, remember that while only
adding one to the device count, a remote I/O system potentially adds hundreds
of I/O connections to the control processor.
Figure 2-5 shows configuration of the WAGO 750-333 remote I/O system
using the Field Device Editor. The upper pane on the Configuration Data tab
lists the available modules as extracted from the GSD file. You can select the
description that matches the physical module that is installed (or to be
installed) in a specific slot and clicks Add. The module description is added to
the next available row in the Configured Modules pane in the lower half of the
tab. In Figure 2-5, a module has been added that provides two ±10V analog
inputs for differential measurement to slot 5. Each entry in the Configured
Modules pane needs to match the physical I/O modules in the remote I/O
system. There are no empty slots between modules. Connectors on the sides of
the abutting modules create the bus on which the modules communicate with
the head module.
Figure 2-5. Identifying Modules Installed in a Remote I/O Device
Refer to the device documentation for specific details of the conventions used
for configuration data for a given I/O system.
The User Parameters page (Figure 2-6) enables the specification of parameters
for the selected modules if support for such configuration is provided in the
GSD file. Configuration of modular devices is described in detail in “Selecting
Device Modules” on page 177.
Figure 2-6. Selecting User Parameters for a Module
Other Modular Devices

Many PROFIBUS DP devices characterized as modular devices have no
hardware slots that are filled as a part of the configuration process. Rather,
software-based modules, or soft modules, are used to determine what and how
much data is passed to/from the master/slave.
For example, the AUMATIC drive manufactured by AUMA is representative
of a number of devices used as quarter-turn or multiple turn electric actuators
for large control valves requiring rotary motion and a great deal of torque. The
AUMATIC drive has a total of 35 soft modules, providing a wide range of I/O
options that can be specified.
Keep in mind that many higher-end devices make frequent use of this soft
module construct. You need to read the device documentation to help ensure
that you understand the use of the module options to gain the desired
communications behavior.
PROFIBUS-PA Devices
PROFIBUS PA is an extension to the PROFIBUS specification that enables the
introduction of FOUNDATION fieldbus like devices into the broad mix of slave
devices. Indeed, the physical layer of PA is identical to FOUNDATION fieldbus
allowing the direct use of FOUNDATION fieldbus wiring components. From a
slave device perspective, PROFIBUS-PA supports standard devices as well as
intrinsically safe devices, and a broader range of conventional field
instrumentation such as transmitters and positioners, although with far less
selection than is found with FOUNDATION fieldbus.
Refer to these documents for a more thorough description of PROFIBUS-PA:
• PROFIBUS – A Pocket Guide by Ronald W. Mitchell
• PROFIBUS PA by Christian Diedrich and Thomas Bangemann
• SIMATIC NET PROFIBUS Networks, Siemens, Document Number
6GK1970-5CA20-0AA1.
DP/PA Interface
When planning the use of PA slave devices, you need to consider these points:
• Devices to handle the translation of the PROFIBUS-DP protocol to/from
the PROFIBUS-PA protocol. These gateways fall into two broad classes:
transparent and non-transparent.
• The usage of status as a part of the data exchange between master and
slave. The FBM222 supports extensive use of the PA status construct to
enhance PA slave device integration into a control system.
• PA devices are modular and at least some devices support more than one
module concurrently.
• Some PA devices need a third-party tool, or the FDT-enabled technology
provided by the FDM package, for a higher level configuration of the
device. These tools are built around DPV1 acyclic data exchange.
However, many devices enable the total configuration of the device,
calibration, and other device maintenance tasks through push buttons,
keypads, LCD displays and other controls.
• The wiring topology options of PROFIBUS-PA are much different from
PROFIBUS-DP and essentially the same as FOUNDATION fieldbus. Keep
this in mind when laying out the topology of the entire plant.
• PA devices are bus-powered and while this opens some opportunities,
intrinsic safety can become a serious concern in certain plant
environments.
Once a PA device is successfully linked to a DP network, the configuration of
the device is similar to DP devices with soft modules. Figure 2-7 is the
Configuration tab for a typical PROFIBUS-PA positioner. In terms of I/O
configuration, this device is defined as a modular device, even though it has no
physical modules that are inserted into slots. Instead, the device has a number
of soft modules that can be used to configure the positioner, and the module
selection has a significant affect on the operational behavior of the positioner
within a closed control loop.
Figure 2-7. PA Positioner Configuration Data
In Figure 2-7, the soft module SP+READBACK+POS_D+CHECKBACK has

to be inserted into slot 1, the recommended option to be used with PA
positioners as described in Chapter 10, “Configuration Examples”. Like many
other soft module devices, slot 1 is the only available slot in the device.
Couplers
As was noted, the DP and PA protocols are dissimilar, requiring a “gateway”
for protocol translation. This section presents two examples of what is
commercially available, a transparent coupler and a non-transparent coupler.
Pepperl & Fuchs SK3

The SK-3 is Pepperl & Fuchs™’ latest commercial offering for integrating
PROFIBUS-PA into a PROFIBUS system. Figure 2-8 shows the component
parts of this device: the DP gateway, four modular power supplies (one for
each of the four PA segments supported by the device) and a plug-in diagnostic
module that acts as a device on the DP segment.
Connectors for
redundant power
sources
DP Gateway Power
modules
Diagnostic
module
Address
PA segment
DIP switches
connectors
Figure 2-8. Pepperl & Fuchs SK-3 (Simplex)
This coupler is transparent, that is, each of the PROFIBUS PA slave modules
appears to the master as a unique slave, each requiring a unique address, which
is set on the PA device. However, the diagnostic module (and the gateway for
that matter) also exist on the DP segment with its own unique address. The DIP
switches in the lower left corner are used for setting the diagnostic module’s
address.
The set of connectors in the upper right corner provide redundant power
connections. The row of four connectors underneath the power supply modules
provide connection points for the four PA segments the coupler supports.
The SK-3 has a duplex variant that provides for dual gateways and for dual
power supplies for the four PA segments; however, the diagnostic module is
still simplex.
Siemens DP/PA Link

The Siemens IM 157 is an example of a a non-transparent DP/PA coupler. The
device consists of a head module hosting up to five DP/PA couplers, which act
as I/O modules, providing the physical interface to multiple PA field devices
such as transmitters and positioners, as well as bus power to these field
devices. As shown in Figure 2-9, each coupler is capable of connecting up to
31 PA devices. The couplers are available in intrinsically safe and non-
intrinsically-safe variants.
DP
Master
DP Network
PA/ PA/ PA/ PA/ PA/

Head
DP DP DP DP DP
Up to Five DP/PA Couplers
Up to 31 PA Devices Per Coupler
Figure 2-9. Siemens DP/PA Link
What differentiates the IM 157 is its ability to act as a smart head module.
When the IM 157 is in data exchange with its DP master, only the address of
the head module appears in communications with the master. The head module
maintains a database of the PA devices connected to it through the daisy-
chained couplers. The head module disassembles the telegrams sent to it from
the master and then communicates the appropriate data to the PA field devices.
This scheme allows the DP master to handle many more PA devices without
having to resort to the use of repeaters. Additionally, the head module can
handle DP data transfer rates up to 12 Mbaud, so that in a segment of mixed
devices, PA and DP, DP baud rates are not limited by the PA interface device.
Setting up the Siemens PA Link device is much like setting up a modular
remote I/O device. The IM 157 needs you to set the address of the head module
using DIP switches.
As with other modular slave devices, the head module has a GSD file
(SIEM8052.GSD), which contains a number of modules available for setting
up the parameterization and configuration telegrams. Each of these modules is
essentially the modules excerpted from a wide range of PA field devices which
are brought together in the GSD file for the IM 157. Figure 2-10 shows the
Modules tab for an IM 157 in which an Endress and Hauser TMT 184
temperature transmitter is being selected as a module. The module is
delineated with begin and end lines, which needs to be selected to bracket the
PA device within the configuration of the IM 157.
Figure 2-10. IM 157 Configuration Example
Note The configuration of two modules are associated with a E&H TT184 PA
temperature transmitter, and that the configuration of the temperature and
display modules includes the begin and end lines. These delimiters are vital to
correct operation of the IM 157 as a head module. Set up of an IM 157 is
described in Chapter 10, “Configuration Examples”.
FBM222 PROFIBUS Network Connections

Generally, the two FBM222s are installed in adjacent odd/even slots in a
baseplate to provide redundancy at the FBM level. To finish the marriage of
the FBM modules, an FBM228/FBM222 Redundant Adapter (p/n P0922RK)
is plugged into the baseplate connectors just under the FBMs.
The redundant adapter provides electrical/communication connections
between the respective FBMs. Without this communication with one another,
the FBMs will not marry, and cannot participate in the FBM redundancy
scheme.
The redundant adapter also provides a point of connection for the Type 1 cable
that ties the FBM pair to the FBM222 Termination Assembly (p/n P0926TH).
The termination assembly provides two Sub-D connectors. These are for Port 1
and Port 2, respectively.
Note This termination assembly provides power for a PROFIBUS terminator,

but does not provide the actual terminating network. The termination is
provided by a switched terminator on the PROFIBUS Sub-D connector. Of
course, the limitation of this termination assembly is that it only provides a
single point of connection for the respective segments. The options to provide
cable or media redundancy are noted in the “Media Redundancy” on page 41.
Figure 2-11 shows the component parts relative to one another. This is the
point of departure for other cabling options.
Redundant 2 Mbps
Module Fieldbus
Fault Tolerant FBM228/FBM222

Field Control Processor Redundant Adapter
FCP280 (P0922RK)
Termination assembly
Port 1 P0926TH
Port 2
One of two PROFIBUS networks

up to 31 slave devices per un-extended segment
T
Figure 2-11. Typical FBM222 Connections
Note A single FBM222 can be installed in the baseplate and connected to the
termination assembly with a T1 cable if redundancy at the FBM level is not
needed.
The typical FBM222 installation offers redundancy at the FBM level in the
physical layer hierarchy, but provides no redundancy at the media layer. While
not a concern for most installations, it may be desirable to provide media layer
redundancy, which involves use of a different redundancy adapter and the
networking options described in “Media Redundancy” on page 41.
Maximum Number of Devices

Each FBM222 port supports a network of 125 devices. This device count
includes:
• FBM222 modules (each module in the redundant pair counts as a device)
• Other PROFIBUS masters if the network is a multimaster network (refer
to“Multimaster Configurations”on page 35)
• PROFIBUS-DP slave devices
• PA couplers, but not the PA devices they connect (refer to “DP/PA
Interface” on page 29)
• Repeaters used to extend the network beyond the first segment (refer to
“Extending the Network” on page 38).
Intrinsic Safety
The FBM222 does not offer intrinsically safe operation. However, intrinsic
safety can be achieved through the use of barriers (such as those manufactured
by the Pepperl & Fuchs Company). For additional information on designing an
intrinsically safe network, refer to the documentation offered by the
PROFIBUS organization.
Note The FBM222 and its associated TA are suitable for installation in Class
1, Division 2 and Zone 2 locations.
Multimaster Configurations
The FBM222 can operate in a multimaster network, in which the second
master station can be another FBM222 or a third-party station. Each master is
given control of the network bus for a time needed to finish one cycle of data
exchanges with its assigned slave devices. It then sends a token message to the
next master which now completes a communication cycle with its slave
devices before passing the token. A master only communicates with the slave
devices when it holds the token and only with its own slave devices.
The masters need to have different addresses with the same master station
range defined in each master configuration. See “Setting Bus Parameters” on
page 67 for information on setting the master station range and the master
station address.
Another requirement is that the same target token rotation time (labeled TTR in
some Control Editors) be configured in each master and that this period be
sufficient for each master to complete its cyclic data exchange. One way to
help ensure that there is ample time is to use the configuration tool for each
master to calculate its target token rotation time. Then manually enter the sum
of the times in the master stations in the bus settings for each station.
The PROFIBUS Network

This section describes various options for setting up a single-media
PROFIBUS network connected to a Sub-D connector on the FBM222 TA. The
network can be populated with the DP and PA devices (through a DP/PA
coupler) discussed earlier in this chapter.
The options covered in this section focus on the most common media and
topologies used PROFIBUS applications. However, PROFIBUS vendors have
provided products that allow the deployment of PROFIBUS with a wide range
of media including copper, optical fiber, infrared and wireless. For additional
information on other media, review the PROFIBUS documents listed in
“Revision Information” on page xiii, especially SIMATIC NET PROFIBUS
Networks, Siemens Document Number 6GK1970-5CA20-0AA1 (Section 2).
The primary media for PROFIBUS installations is RS-485 using shielded
twisted pair copper. RS-485 is a multi-drop network that supports 32 loads (or
devices with an RS-485 transceiver chip) per segment. In its basic

configuration, the devices are a master such as the FBM222 and up to 31 slave
devices daisy-chained in a linear network with terminations set in the Sub-D
connector at the device at each end (top of Figure 2-12).
Note The boxes labeled Slave can represent a compact DP device, a modular
DP device such as a remote I/O subsystem, or a PA gateway.
The middle diagram in Figure 2-12 includes two variations: Placement of the
master device at mid-segment and the use of an active termination device (see
“Active Terminators” on page 38). The diagram at the bottom of Figure 2-12
shows an un-expanded segment with two master devices, the FBM222 and a
third-party device. With two masters, the maximum number of slave devices
on an un-expanded segment is reduced to 30.
= Termination On
Master
Up to 31 Slave Devices
Slave Slave Slave Slave Slave Slave
Un-expanded Network
= Termination On
Master
Up to 31 Slave Devices Active

termination
device
Slave Slave Slave Slave Slave
FBM222 at Mid-segment
= Termination On
Multimaster Multimaster
FBM222 third-party
Up to 30 Slave Devices
Multimaster Network
Figure 2-12. Variations on a Basic DP Network
Sub-D Connectors
A basic physical layer DP components is the Sub-D connector, which is
available from a broad range of vendors. This 9-pin connector is designed to
allow removal of a device from the segment without interruption to the
network.
Most connectors include a termination resistor in the connector and a slide

switch for turning the resistor on and off (Figure 2-13). When the switch is in
the on position, the connector sources power from the connected device to
operate the termination circuity. The FBM222 Termination Assembly
(P0926TH) is an component, providing power to the termination circuitry in
the Sub-D connector. The switch enables you to temporarily end a segment at a
particular device to isolate a detected network problem.
The pair of connectors in Figure 2-13 have been prepared for use at the end of
a segment, that is, they have only a single (inbound) cable. The connectors in
Figure 2-14 have been prepared for a device to be installed at mid-segment and
thus have both inbound and outbound cable connections. The clear covers on
these connectors allow you to verify that the wires in each cable are properly
connected.
Termination
Switch
Figure 2-13. Sub-D Connectors Prepared for a Segment End
Termination
Switch
Figure 2-14. Sub-D Connectors Prepared for Mid-Segment
The use of the Siemens FastConnect connectors is highly recommended, as

they use insulation displacement technology similar to that used by telephone
installers. These connectors, when used with the appropriate cable and
stripping tool, allow cables to be made up very quickly.
M12 (EuroFast)
For projects that must meet NEMA 4/IP65 or NEMA 6/IP67 requirements,
M12 or EuroFast connectors must be used. These are a 5-pin screw-on type
connector. A family of these connectors is available from Turck.
Active Terminators
The typical PROFIBUS segment is a daisy chain of devices, with devices
strung out along the length of a cable. The cable can be terminated at each end
with a Sub-D Connector that provides terminating resistors, in which case the
connected device supplies the DC power for the termination circuitry.
However, removal of this device removes the DC power to the terminating
network, increasing the potential of detected communication errors.
Solve this by using an active terminator at the end of the segment (see the
middle diagram in Figure 2-12). This active device is powered with 24 volts
DC (just like any other PROFIBUS device) and serves the purpose of
providing the terminating network independent of the other devices on the
segment.
Extending the Network

One of the primary tools in the PROFIBUS network engineer’s toolbox is the
repeater. With this hardware, you can:
• Exceed the length limitations of a segment for a given baud rate
• Exceed the 32 device limit
• Build branch segments
• Connect up to 125 stations per FBM222 port
Keep in mind that PROFIBUS repeaters both reshape the inbound signal and
refresh the voltage level. Additionally, the repeater provides galvanic isolation
between its respective segments.
Figure 2-15 shows the use of repeaters to daisy-chain additional segments to
overcome the 32-device limitation.
= Termination On
Master
Up to 31 Devices
Un-expanded Network
Master
Up to 30 Devices
Slave Slave Slave Slave Slave Repeater

Segment 1 in Expanded Network
Up to 30 Devices
Slave Slave Slave Slave Slave Repeater

Up to 31 Devices
Slave Slave Slave Slave Slave
Figure 2-15. Expanding a Network with Repeaters
In this daisy-chaining of segments, the repeater counts as a device even though

it does not need an address. In the strictly linear topology of Figure 2-15, up to
nine repeaters can be used. The termination switch is also enabled at the
repeater for each of its two segments.
Repeaters can also be used for branching as shown in Figure 2-16, in which
case there is a limit of nine repeaters per path.
Master
Slave Slave Repeater Slave Slave Slave Slave
Slave Slave Repeater Repeater Slave Slave Slave
Slave Slave Repeater

Fiber
Optic
Optical Cable Optical
Link Link Slave
Master Master
Figure 2-16. Using Repeaters for Network Branching
Repeaters can be used to overcome distance limitations that can be imposed by

the baud rate selected for segment operation. Table 2-2 shows the maximum
distances that can be spanned on a copper segment as a function of baud rate.
Table 2-2. Distance as a Function of Baud Rate
Data Transfer Rate (Kbaud) Length (m)

9.6 1000
19.2 1000
45.45 1000
93.75 1000
187.5 1000
500 400
1500 200
3000 100
6000 100
12000 100
Figure 2-16 illustrates some of the means that can be employed to overcome
the distance limitations that higher baud rates can engender. At the top of the
diagram, repeaters are daisy chained solely to extend cable length.
The center of the diagram shows repeaters used to add segments as network
branches. As noted previously, no more than nine repeaters can be allowed in
one linear segment. However, this is not the limitation as regards the number of
repeaters that can exist in the network of slave devices that are connected to the
master. So a repeater essentially provides the facility of creating a branch off

the segment to adapt to the topology of the plant unit operations.
Finally, the box in the lower right of the diagram represents an optical repeater,
which connects a high-performance glass fiber segment that can be up to a
kilometer long while supporting data transfer rates of 12 Mbaud, removing
distance as a roadblock for a typical plant.
Media Redundancy
The typical FBM222 installation described earlier in the chapter (“FBM222
PROFIBUS Network Connections” on page 33) offers redundancy at the FBM
level in the physical layer hierarchy, but provides no redundancy at the media
layer. While this is not a concern for most installations, media redundancy may
be desirable in others. This section provides a description of the underlying
implementation of media layer redundancy employing redundant FBM222s.
Figure 2-17 shows the primary elements of a typical redundant media
deployment. The FBM222 Redundant Adapter - Dual Network (P0926XM)
provides connections for two independent Type 1 cables, one connecting the
Main module to a TA (P0926TH), the other connecting the Backup FBM to its
TA.
Note In this arrangement no communication path exists between the FBMs

either through the baseplate or through the Redundant Adapter. Keep in mind
that while the adapter provides no FBM interconnection, it is needed to finish
the correct wiring.
In Figure 2-17, connections are shown from the respective Port 1 Sub-D
connectors on the TAs to a PROFIBUS splitter/combiner. This device allows
the connections from Port 1 to be split on the other side of the
splitter/combiner. Hence, the A ports of the splitter/combiner have been
connected together as have the respective B ports.
Connection to The Foxboro Evo Control Network
Redundant 2 Mbps
Module Fieldbus
Fault Tolerant
Field Control Processor FBM222 Redundant
FCP280 Adapter -Dual Network
(P0926XM)
Termination Termination
assembly assembly
P0926TH P0926TH
Third-party Third-party
redundant redundant
link module link module
A B A B
A
T T
Dual Media Network
B
T T
Third-party
redundant
link modules
One of two PROFIBUS dual media

segments of up to 31 dual-port and single-port
slave devices per un-expanded segment
Figure 2-17. Media Layer Redundancy Schematic
The connections shown in Figure 2-17 and the use of the splitter/combiner
provide the necessary elements not only for media redundancy but also to
interconnect the FBMs for redundant operation. The use of the
splitter/combiner has taken Port 1 of the FBM pair and provided at the A and B
ports of the splitter/combiner redundant media segments that field devices can
be connected to. Communication is available by default on the A or B port
even if one of the ports were to fail.
A pair of FBM222s appear in a bus trace as two masters. Close inspection of
segment traffic reveals token passing between the FBMs and other messages.
With the connections as shown in Figure 2-17, this communication can occur
as the splitter/combiner is bi-directional. Any variant of this concept has to be
deployed with the use of a splitter/combiner that provides support for this
scheme. If you do not provide a splitter/combiner, it may appear to provide full
media redundancy but may not provide FBM redundancy support.
Note While the schematic has been drawn with splitter/combiner at the end of
the media elements, in general no such restriction need apply. The FBM and
splitter/combiner could be in the middle of the media segments.
This scheme relies on third-party PROFIBUS splitter/combiners. A number of

such devices have been tested with the FBM222, some using copper, others
fiber optic cable. An extensive description of these configurations is beyond
the scope of this document. Contact your Schneider Electric representative for
additional information on various media redundancy schemes.
45
C H A P T E R 3
Security
This chapter describes the pre-configured user roles and their access privileges
in Field Device Manager software. The chapter, which is intended for the
Control Editors Administrator, describes how to add users and assign them to
various FDT roles, which govern the users’ ability to access the slave device
configurations and download DPV1 device parameters.
Contents
• Introduction
• Enabling Security
• Setting Up Users
• Modifying Roles
Introduction
The Control Editors use ArchestrA Galaxy-based security services to
authenticate users and control their access to various functions and object
attributes.
When you create a Galaxy for the Control Editors, the database has no security
restrictions. There are two users: Administrator and DefaultUser, both of
which have full access to all IDE and System Management Console (SMC)
functions, as well as permissions to acknowledge alarms and set parameters.
Neither user is assigned a password.
Implementing security in the Control Editors involves:
• Enabling Galaxy-based authentication of users
• Adding users and assigning passwords
• Assigning one or more roles to each user
• Modifying the Control Editors supplied roles by granting or denying
access to various IDE, SMC or Operational permissions
• Creating new roles and security groups.
Refer to the “Working with Security” topic in IDE Help for additional
information on security administration, including authentication modes and
modifying permissions for a user role.
46 3. Security
When Field Device Manager for PROFIBUS is installed with Control Editors,
four Field Device Technology (FDT) roles are added to the ArchestrA security
scheme. Initially there are no restrictions on any of these roles, but they can be
set up to match the FDT security model:
• Planning Engineer is the an inclusive role with access to all functions
except modifying access permissions.
• Maintenance is similar to the Planning group except that it does not
include the ability to make permanent changes to device templates.
• Operator has a limited set of permissions appropriate for the plant
operator role.
• Observer is essentially a view-only user.
In addition, two FDT user role modifiers are defined:
• The FDT Administrator role modifier has all the privileges of the
Planning Engineer and the ability to enable and disable security, modify
user access permissions for device types and instances.
• The OEM Service role modifier gives the user full privileges with respect
to a specific DTM, and needs two authentications: one from Field Device
Manager and one from the device or DTM. OEM Service is not currently
used in Field Device Manager for PROFIBUS.
Finally, a new non-FDT user role has been added:
• The SafetyInstrumentEngineer has the ability to modify user access
permissions and all modification tasks for safety HART field device
templates and instances. For details on this role, refer to “User Roles and
Safety HART Field Devices” in Using HART Instrumentation with the
Foxboro Evo Process Automation System (B0750CM).
These roles and modifiers only apply within Field Device Manager. When a
GSD is bound to a device template, the Planning, Maintenance, Operator, and
Observer roles are granted or denied access to each function and parameter in
the resulting DTMs. Figure 3-1 shows how access permissions for a slave
device are allocated to the four roles.
The Set Permissions dialog box includes three tables specifying access to
parameters, screens (that is, tabbed pages and windows within Field Device
Manager), and functions respectively for the Observer, Operator, Maintenance
and Planning roles.
For example, with the permissions being set in Figure 3-1 users assigned to
Maintenance, Observer and Planning can change documents links on the
Identification tab for the device, while Observers have read-only access to this
function. The permissions are modified, if necessary, during setup of the user
interface in each device template, as described in “Setting Access Permissions”
on page 247.
A user with the FDT Administrator modifier can use the Set Permissions
dialog box to modify the default permissions in the device template or an
individual device instance.
3. Security 47
Figure 3-1. Setting Access Permissions for a Resource Block
The four Field Device Manager roles are assigned these priorities:
Priority Role
1 (highest priority) Planning Engineer
2 Maintenance
3 Operator
4 (lowest priority) Observer
When a user is assigned to more than one Field Device Manager role, the role
with the highest priority is applied and the others are ignored. Thus, for
example, if a user is assigned to both the Maintenance and Observer roles, the
Maintenance role controls the user’s access to the device.
A user with the FTD Administrator modifier role configures the user names
and passwords, and assigns them to roles, including the four Field Device
Manager specific groups.
Note It is recommended that at least one Field Device Manager user be

assigned the Planning Engineer role and be given FDT Administrator
privileges.
48 3. Security
Note The permissions are only enforced when the device is opened in Field
Device Manager. When the device is opened using the manufacturer’s DTM,
access is controlled by the vendor’s DTM.
The FDT roles are used by default in Field Device Manager. However, their
application varies depending on whether security is enabled. The roles are
applied as follows:
• When security is enabled, a user needs to log into Control Editors with a
user name and password configured in the selected Galaxy, and within
Field Device Manager, the user is granted these access rights and
permissions:
• Access to the device templates and instances according the highest
priority role assigned to the user
• Ability to modify the security configuration and set permissions in the
device templates if the user has the FDT Administrator modifier
• Observer permissions for all functions if the user is not assigned to
one of the four FDT roles and does not have the Administrator
modifier.
• When security is not enabled, the user’s identity is not authenticated and
within Field Device Manager, the user is granted these permissions:
• Planning Engineer permissions to access the device templates and
instances
• The FDT Administrator modifier enabling the user to set permissions
within a device template for access to any parameter.
3. Security 49
Enabling Security
To enable Galaxy-based security:
1. Verify that no other user is connected to the Galaxy which you want to
help secure.
2. Start ArchestrA IDE and select the Galaxy.
3. Choose Galaxy > Configure > Security from the IDE main menu to open
the Configure Security dialog box (Figure 3-2).
Figure 3-2. Set Authentication Mode to Galaxy
4. Click the radio button for Galaxy in the Authentication Mode group, and
click OK.
A dialog box prompts you to log in by entering a user name and password
(Figure 3-3).
Figure 3-3. Change User Dialog Box
5. Enter Administrator in User name, leave the Password field blank

(because no password has been assigned at this point), and click OK.
50 3. Security
You can now add user names and passwords, assign the users to FDT roles
(and other roles in the Control Editors) and modify specific permissions
granted to various roles.
Setting Up Users
This section describes how to add users, set passwords and assign the users to
FDT roles. In these examples, Galaxy-based authentication has been enabled,
the user has logged in as Administrator.
To set up users:
1. Choose Galaxy > Configure > Security from the IDE main menu to open
the Configure Security dialog box (Figure 3-2).
2. Click the Users tab in the Configure Security dialog box (Figure 3-4).
A table at the top of the tab lists the currently configured users (initially
Administrator and DefaultUser). When a user is selected, the Change
password button is active and the table in the lower part of the tab lists the
roles that have been assigned to the selected user.
3. Click above the user list to add a user to the next available row in
the table, type a name in the User field, and press Enter.
4. Click Change Password, enter a password in the New Password and
Confirm New Password fields, and click OK.
The Associated Roles table shows that the Default role is automatically
assigned to the new user. The user needs to be assigned to this role, which
gives the user the IDE, SMC, and Operational permissions.You can
modify Default permissions in the Roles tab (Figure 3-4). However, you
cannot assign Field Device Manager permissions to the Default or
Administrator roles. Assign FDT roles to the user by clicking the
checkboxes in the Associated Roles tables.
In Figure 3-4, the new user is being assigned to the FDT Administrator
modifier, which will enable the user to change security setting within Field
Device Manager, and the FDT Planning role, which gives access to most
Field Device Manager functions.
3. Security 51
Figure 3-4. Adding a New User
5. Assign passwords to Administrator and DefaultUser.
52 3. Security
Modifying Roles
The Roles tab (Figure 3-5) lists the already defined roles in the Control Editors
and Field Device Manager: Administrator, Default, and the four FDT roles and
two FDT modifiers.
Figure 3-5. Roles Tab
If you are not planning to modify the Default role, it is not necessary to grant
any General or Operational permissions to the FDT roles, as the users already
have the permissions. However, if you restrict the Default role, you need to
enable the appropriate FDT roles to perform such functions as creating
templates and objects in the Control Editors, and acknowledging alarms.
Alternatively, you can allocate the access permissions by creating new roles
and assigning them to individual users.
To modify the permissions assigned to a role:
1. Click the Roles tab and select the role in the Roles available list to display
the already permitted access in the General Permissions and Operation
Permissions boxes on the right.
2. Expand the nodes in the permissions boxes to view access within each
category.
3. Check or uncheck boxes to enable or deny the access.
3. Security 53
You can add roles to the Galaxy configuration for general use in the Control
Editors, SMC, and the control system. However, you cannot define new roles
for use within Field Device Manager.
To add a role to the Galaxy configuration:
1. Click above the roles list to add a role user to the next available row
in the table, type a name in the Role field, and press Enter.
2. Check boxes in the General and Operational Permissions data trees to
enable access to the listed functions.
54 3. Security
55
C H A P T E R 4
Installing and Configuring the

FBM222
This chapter covers installation of the FBM222 and connection to the

PROFIBUS networks at the termination assembly, configuration of the FBMs
in the Control Editors, and deployment to control processors.
As slave devices are added to the network configuration, you may need to
return to the FBM’s master bus settings page in the Field Device Editor, to
validate the settings given the attached devices and make adjustments. If
adjustments are made after the FBM222 has been installed and its equipment
control block (ECB) deployed, you need to redeploy the ECB to implement the
changes in the field.
Configuration of the FBM222 can take place before or after physical
installation of the module.
Contents
• FBM Installation
• System Configuration for the FBM222
• Adding the FBM222
• Importing an FBM223 Configuration
• Setting Bus Parameters
• Setting ECB200/202 Parameters
• Deploying the FBM
• FBM Manager
FBM Installation
FBM222s can be installed in a baseplate with its host FCP270, or FCM100Et,
or in a separate Schneider Electric two-, four-, or eight-position baseplate.
(When used with the FCP280, it needs to be installed on a separate baseplate.)
The modules can be installed in any of the baseplates described in Standard
and Compact 200 Series Subsystem User's Guide (B0400FA), including the
earlier models P0914XA and P0914XB.
56 4. Installing and Configuring the FBM222
Refer to B0400FA for detailed information on installation of the baseplates, the

FCP280, FCP270, and FCM100Et, and power supplies.
Redundant FBMs, Single Networks

When used as a redundant pair, the FBM222s are installed in adjacent
baseplate positions with the main module installed in an odd-numbered slot
and its backup placed in the next higher-numbered slot (1 and 2, 3 and 4, and
so on). One of these redundant adapter modules is plugged into the adjacent T1
cable connectors:
• The FBM228/222 Redundant Adapter (P0922RK) when single networks
are to be attached to the FBM222 ports. This adapter module is placed on
the two baseplate termination cable connectors to provide a single
connection for the cable from a single termination assembly (Figure 4-1).
Termination Cable (T1)
FBM228/FBM222 Redundant
Adapter (P0922RK)
FBM222 Termination
Assembly P0926TH Redundant FBM222
Figure 4-1. Redundant FBM222 and TA for a Single Network
• The FBM222 Redundant Adapter - Dual Networks (P0926XM) when the

dual networks are to be attached to the FBM222 ports. This adapter
module is placed on the two baseplate termination cable connectors to
provides connections for the cables from two termination assembly
(Figure 4-2).
Termination Cable (T1)
FBM222 Redundant Adapter

Dual Network (P0926XM)
FBM222 Termination
Assemblies P0926TH
Redundant FBM222
Figure 4-2. Redundant FBM222 and TAs for Dual Networks
4. Installing and Configuring the FBM222 57
Note The redundant adapter needs to be installed before the FBM222s are
powered up because the FBMs detect the presence of the redundant adapter
only at power-up.
Install each non-redundant FBM222 in an available slot on the baseplate, and

connect the Type 1 cable from the termination assembly to the I/O connector
whose position number matches the position number of the module.
The FBM222s are connected through a Type 1 termination cable and one of
two DIN rail mounted termination assemblies:
• P0926TH, which is constructed of a PVC material and helps secure
devices in operation in temperatures up to 50° C
• RH926TJ (supersedes P0926TJ), which is designed for use in NEMA-4
cabinets and is rated helps secure devices in operation in temperatures up
to 70° C
NOTICE
POTENTIAL EQUIPMENT DAMAGE
Only a PROFIBUS termination assembly P0926TH, RH926TJ

(supersedes P0926TJ), or P0917SY) should be connected to the I/O
connector associated with an FBM222 slot; no other type of assembly
is allowed. If the FBM222 is installed in a slot with an I/O connector
attached to an incorrect termination assembly, performance issues
may occur.
Failure to follow these instructions can result in equipment

damage.
Each of these assemblies consists of a T1 cable connector and two 9-pin Sub-D
connectors for connecting the PROFIBUS networks.
A Type 1 cable from the termination is plugged into the redundant adapter or
single connector.
At the baseplate, the cable is plugged into either the redundant adapter or an
I/O connector. The other end of the cable is plugged into one of the termination
assembly types. For the available T1 cables, refer to the tables “LSZH
Termination Cable Types and Part Numbers” and “Polyurethane/PVC
Termination Cable Types and Part Numbers” in Standard and Compact 200
Series Subsystem User's Guide (B0400FA).
Connection to the PROFIBUS Networks

To connect the FBM222 to the PROFIBUS network:
1. Mount the FBM222 TA (P0926TH) to a DIN rail and use the T1 cable to
connect the TA to the redundant adapter or I/O connection on the
baseplate.
The TA accepts two 9-pin Sub-D connectors to connect network segments

for each FBM222 port. The connectors are marked Channel 1 and Channel
2, respectively. Either or both ports can be at the end of a segment.
2. Prepare Sub-D connectors according to the manufacturer’s instructions.
When the port is at the end of a segment:
a. Prepare a Sub-D connector with single cable attached to the terminals
marked for the inbound cable.
b. Turn the termination switch on the connector to On.
The FBM222 TA is an active device and will provide dc power for the
termination circuitry in the connector.
When the port is not at the end of a segment:
a. Prepare a Sub-D connector with two cables (inbound and outbound)
attached.
b. Turn the termination switch on the connector to Off.
3. Continue building the network segment using the Sub-D connectors to
daisy chain the slave devices.
“The PROFIBUS Network” on page 35 provides general information on
RS-485 copper media, Sub-D connectors, and using repeaters to extend
the network and/or change network topology. Refer also to the device
manufacturers’ documentation and to Installation Guideline for
PROFIBUS-FMS/DP (available on the PROFIBUS website
http://www.profibus.com).
In addition to the suggested reference documents mentioned here, it is also
necessary to observe the specific installation instructions from the
suppliers of the slave devices and to comply with the relevant guidelines
to help protect operators.
Installing for Media Layer Redundancy

This section provides general instructions for creating a network that includes
third-party PROFIBUS splitter/combiners. A number of such devices have
been tested with the FBM222, some using copper, others fiber optic cable.
Description covering the details of these configurations is beyond the scope of
this document. Contact your Schneider Electric representative for additional
information on various media redundancy schemes.
Note Before implementing media layer redundancy, you need to understand

how these networks support redundancy at the FBM level, evaluate the cost of
full media and FBM redundancy in light of the project requirements, and
thoroughly test the network design before deployment.
To connect a redundant FBM222 to a dual media network:

1. Plug the FBM222 Redundant Adapter - Dual Network (P0926XM) over
the two I/O connectors for the two slots occupied by the FBMs.
Do not use the FBM228/FBM222 Redundant Adapter (P0922RK).

2. Mount two FBM222 TAs on DIN rails in appropriate locations to connect
to the splitter/combiners.
3. Use a T1 cable to connect each TA to the redundancy adapter.
4. Prepare two cables with a Sub-D connector at each end and connect the
TAs to the splitter/combiners.
• On the ABB Redundant Link Module (RLM01), plug the Sub-D
connector into the 9-pin receptacle marked M.
• On the Siemens Optical Link Module (OLM), plug the connector into
the receptacle marked CH1.
5. Verify that the splitter/combiners used in one dual network are connected
to the same ports on the TAs.
6. Finish the network installation as instructed in the link module and slave
manufacturers’ documentations.
Replacing an FBM223
Several options are available when migrating from an FBM223:
• Replace the FBM223 with a single FBM222 and reuse the existing
termination assembly (P0917SY).
• Install a redundant FBM222 and connect the pair to the existing
termination assembly using the FBM228/FBM222 Redundant Adapter.
• Replace the FBM and termination assembly.
The advantage of the first two options is that they preserve more of the original
investment and needs no change to the network cabling. However, the newer
termination assembly (P0926TH) provides two main advantages:
• The TA extends the maximum distance for each segment, as the length of
the T1 cable is not included in the calculation of maximum segment
length. With the FBM223 TA (P0917SY) twice the T1 cable length is
included in the calculation.
• With the FBM223 TA (P0917SY), the FBM is part of the network. If the
FBM (or pair for redundant FBMs) is removed, the entire PROFIBUS
network is disabled. With the FBM222 TA (P0926TH), the PROFIBUS
network is not disabled when the FBM is removed. This allows
multimaster networks to continue at least partial operation when the
FBM222 is removed from its baseplate.
System Configuration for the FBM222

System configuration of the FBM222 in the Control Editors consists of
creating an equipment control block for the FBM, assigning the module to the
control processor or FCM, and editing the master bus settings for each port.
The configuration can be accomplished before or after the physical installation
of the FBM.
When both the installation and system configuration are done, the FBM is
deployed to the Control Core Services network, that is, the ECBs are
downloaded to the control processor, and the module can be brought online.
The instructions in the remainder of the chapter assume that the host control
processor has already been defined and assigned to an equipment unit in the
Control Editors. The examples in the chapter involve the addition of an
FBM222 to FCP001, a fault tolerant FCP280 or FCP270 assigned to
equipment unit Equip_Unit_001, as shown in the Control Editors Deployment
view in Figure 4-3. The control processor and equipment unit have not been
deployed.
Figure 4-3. Example FCP270
Refer to these Control Software documents for information on configuring and

deploying the control system hardware:
(B0750BA).
Adding the FBM222

There are multiple ways to add an FBM222 to the Galaxy configuration, as
described in Hardware Configuration User’s Guide (B0750BB). The method
used in this section facilitates coordination of the tag that identifies the module
in the Control Editors and the letterbug used in the Foxboro Evo system.
To add an FBM222 to the Galaxy database, proceed as follows:
1. Expand InFusion Hardware > InFusion Module > 200-Series in the
Template Toolbox to display the template for the FBM.
2. Drag $FBM222 to the Network view and drop it on any blank space in the
view (Figure 4-4).
Figure 4-4. Adding an FBM222 to the Galaxy
The specified FBM is displayed under the Unassigned Hardware Folder

with a default name such as F00001. This name is the IDE tag and it needs
to be unique among the objects in the Galaxy.
The FBM is created as non-redundant module. No further configuration is
needed for single FBMs.
3. Perform these steps for a redundant FBM:
a. Double-click the FBM in the Network view to open it in the FBM
Editor.
b. Select D in the Redundant field in the editor’s Hardware tab
(Figure 4-5).
c. Click in the FBM Editor to save the changes, close the editor,
and check the module in.
Choose S (single) for

a non-redundant FBM
Choose D (dual) for
a redundant FBM pair
Figure 4-5. Editing an FBM Configuration
Changing the IDE Tag

When the FBM is opened in one of the Control Editors, the IDE tag is
displayed in the title bar. The IDE tag can be changed only when the FBM is
unassigned.
When you assign the FBM to an FCP280 or FCP270 or an FCM, the module is
assigned a contained name, which is the name used in the control system.
Before deploying an FBM or any blocks that use the module’s ECB, verify that
the contained name matches the FBM’s actual six-character module identifier
(letterbug).
When the FBM is assigned to a control processor, the contained name is copied
from the IDE tag. You can then change the name to match the letterbug.
However, the IDE tag remains the same, and the tag used in the Control Editors
will not match the contained name.
To avoid confusion, you may want to change the IDE tag to match the letterbug
before assigning the FBM to a control processor. If the eventual letterbug is not
known until after the assignment, you can temporarily unassign the FBM,
change the IDE tag, and then re-assign the FBM to the control processor, at
which point the contained name is derived from the new IDE tag.
To change the IDE tag:
1. Expand the Unassigned Hardware folder in the Network view to display
the FBM, right-click the object, and choose Rename from the context
menu to make the name editable.
2. Type a new name according to the naming rules described in “Naming
FBMs” on page 63 and press Enter.
To change the contained name without changing the IDE tag:
1. Expand the Galaxy name in the Network view to display the host control
processor (or FCM) to display the FBM, right-click the object, and choose
Rename Contained Name from the context menu to open the dialog box
shown in Figure 4-6.
Figure 4-6. Changing the Contained Name
2. Enter the letterbug (according to the naming rules described in “Naming

FBMs” on page 63) in the New Contained Name field, and click OK.
Naming FBMs
This section describes naming rules when the FBM is assigned to an FCP280
or FCP270 and when it is assigned to an FCM.
For FBMs Attached to an FCP280 or FCP270

For FBMs attached to an FCP280 or FCP270, these rules apply:
• The resultant letterbug needs to be unique relative to the devices
connected to the FCP280 or FCP270.
• The first four characters in the letterbug can be any combination of letters,
numbers, and the underscore character.
• The fifth character is the number of the baseplate on which the module is
mounted:
• 1, 2 or 3 for the baseplates daisy-chained to an FCP270 baseplate with
more than two slots
• 0, 1, 2 or 3 for the baseplates daisy-chained to a two-position FCP280
or FCP270 baseplate
• 0 when the FBM is mounted on a four-position baseplate with the

FCP270
• 1 through F for the baseplates daisy-chained to an FCP280 or
FEM100.
Note Multiple two- and four-position baseplates can be combined to form a

single logical baseplate. The baseplate and module identities are set with
switches on the individual baseplates, as described in “FBM Installation” on
page 55.
• For non-redundant FBM222s, the sixth character is the slot number

(1 through 8) on the baseplate.
• For a redundant FBM222 pair, the sixth character is a letter indicating the
two slots used:
A for slots 1 and 2
B for slots 3 and 4
C for slots 5 and 6
D for slots 7 and 8.
For example, the letterbug CP330B indicates a redundant FBM222 pair
installed in slots 3 and 4 on the same 4-position baseplate as the modules’
host FCP280 or FCP270s.
Refer to Standard and Compact 200 Series Subsystem User's Guide
(B0400FA) for additional details and examples.
For FBMs Connected to a ZCP270 through an FCM

For FBMs that are connected to a ZCP270 through an FCM, these naming
rules apply:
• The first four characters need to be the same as the first four characters in
the letterbug of the host FCM.
• The fifth character is the number of the baseplate on which the module is
mounted:
• 0 for the baseplate with the FCM100 (by convention the FCM
baseplate is usually 0)
• 1, 2 or 3 for the baseplates daisy-chained to baseplate 0
• 0, 1, 2 or 3 for the baseplates daisy-chained to an FCM in a two-
position baseplate.
Note Multiple two- and four-position baseplates can be combined to form a

single logical baseplate. The baseplate and module identities are set with
switches on the individual baseplates, as described in “FBM Installation” on
page 55.
• For non-redundant FBM222s, the sixth character is the slot number

(1 through 8) on the baseplate.
• For a redundant FBM222 pair, the sixth character is a letter indicating the
two slots used:
A for slots 1 and 2

B for slots 3 and 4
C for slots 5 and 6
D for slots 7 and 8.
For example, FCM60B would be the letterbug for a redundant FBM222
pair installed in slots 3 and 4 on the same 8-position baseplate as the
modules’ host FCM whose letterbug is FCM600. Refer to Standard and
Compact 200 Series Subsystem User's Guide (B0400FA) for additional
details and examples.
Note The FBM’s ECB is deployed when the host control processor is
deployed or redeployed to the control processor. If the FBM letterbug needs to
be changed after its ECB has been deployed, you need to first undeploy the
ECB, change the module name, and then redeploy the ECB.
Importing an FBM223 Configuration

Note This section described one method of migrating FBM223 configurations
to the FBM222 configuration. A second method is described in Bulk Data
Editor User’s Guide (B0750AF) by which configuration data for FBM223s
and their assigned PROFIBUS slave devices are imported into a bulk data
object to generate FBM and device instances in the Control Editors. The
import can be from a SaveAll disk or an IACC Export file. Importing the
configuration data into a bulk data object can also facilitate the migration of
PROFIBUS devices from an FBM223 to an FBM222.
Note Appendix A, “FBM223 Configurations” describes the Control Software

The configurator for the FBM223 saved the FBM settings to a separate port
configuration file, which was then downloaded to FBM223. The default name
and extension for this file were the FBM letterbug and .PMA. The file was
stored in the /usr/fox/sp/files/devices directory or d:\usr\fox\sp\files\devices
folder on the configurator’s host workstation.
You can import this file into the Field Device Editor when migrating from the
FBM223 to the FBM222 to capture the settings used with the older FBM.
To import an FBM223 configuration:
1. Double-click the FBM in the Network View to open it in the Field Device
Editor, and click the Bus Settings tab.
2. Right-click anywhere in the Bus tab and select Import FBM223
Configuration from the context menu (Figure 4-7).
Figure 4-7. Importing an FBM223 Configuration
3. Use the modified Open dialog box to browse for and select the
configuration file (usually letterbug.PMA) and click Open.
The bus parameters are set as they were in the FBM223 with the exception
of the Master Station address as described below. The bus parameters can
be edited as described in “Setting Bus Parameters” on page 67.
The FBM222 Bus Settings configurator does not allow setting the FBM222
Master Station Address to 0. Address 0 is reserved for a secondary master
(MSAC2 master) on the bus. The FBM223 FBMPortConfigurator allowed
setting the Master Station Address to 0.
During import of a FBM223 PMA file, the Master Station Address is set to 1,
in case it was set to 0 previous to the import.
Note If this change (Master Station Address had to be changed from 0 to 1)

during the PMA file import results in an address conflict with a slave, it might
be necessary to change either the FBM Master Station Address or the address
of the conflicting slave. Be aware that a redundant FBM222 pair occupies two
successive addresses, for example, 1 and 2.
Note Before a changed Master Station Address is downloaded into the

FBM222, it is needed to disable the affected Port in the System Manager. The
FBM222 unlocks the slaves during the Port Disable step. After the download,
enable the port in the System Manager again.
In addition to creating an ECB for the new FBM, you need to perform these
steps:
• Remove the FBM223 ECB from the host control processor’s ECB
compound (or other compound if the ECB was moved).
• Create PROFIBUS slave devices, which in turn creates ECB201s. Try to
use to the same IDE tags (ECB names) to minimize editing of the DCI
blocks that use slave devices.
• Review the IOM_ID parameter of each DCI block that processed data
from the devices attached to the FBM223. There is no need to change the
point number parameters (such as PNT_NO). However, you may want to
revise them to take advantage of the extended point configuration syntax
supported by the FBM222 (“Point Configuration String Syntax” on
page 261).
Setting Bus Parameters

To configure FBM222 bus parameters:
1. Double-click the FBM in the Network View to open it in the Field Device
Editor, and click the Bus Settings tab (Figure 4-8).
Figure 4-8. Setting FBM Bus Parameters
Bus parameters are set for each port; port 1 is displayed when the tab is
selected. The Configure pull-down list at the top of the tab is used to
select either Port1 or Port2.
By default the Use Port option is checked and the port is enabled.
• Uncheck the option box to disable the port.
When the option is not checked, the parameter fields in the tab are grayed
out, indicating that they cannot be edited. However, the values are
maintained, and displayed when the port is enabled.
2. Click Use Port if the option box is not already checked.
3. Change the default values in the FBM Settings group as needed.
The FBM Settings Parameters are described in Table 4-1.
Table 4-1. FBM222 Settings Group
Field Description
Master Station Address Enter the PROFIBUS network address for the FBM222. The range is 1 to
124 for a redundant FBM, and 1 to 125 for a non-redundant FBM. It is
advisable for the address to be set to 1 (the default), so that the FBM has
an address lower than any slave device on the network.
When configuring a redundant FBM222, this field determines the address
for the module in the Master role; the module in the Tracker role is
automatically assigned the next higher number.
Note Master in this context refers to the operational mode of the module
in relation to the other module in the redundant pair. This is Master versus
Tracker, not PROFIBUS Master versus slave device. In a redundant pair,
one module acts as Master, performing the FBM functions, while the
other module is in the Tracker role, ready to assume the Master role if a
problem is detected with the other module.
The FBM222 supports multimaster configurations, in which case each

FBM222 module and third-party master needs to have a unique address
on the network served by this port. If the masters are redundant pairs,
assign an odd number for each Master Station Address.
Highest Station Address Specify the highest address that can be assigned to a slave address. The
range is Master Station Address + 1 to 125. Stations with an address
higher than this limit are not involved in token passing.
It is a good practice to reserve single-digit network addresses for the
Master Stations and Class 2 configurators, and assign slave device
addresses in the range 10 to 125.
Table 4-1. FBM222 Settings Group (Continued)
Field Description
Min Slave Interval Set the time in milliseconds that the FBM needs to wait between two
consecutive polls of the same device. The purpose of this interval is to
help ensure that function requests from the FBM can be handled by the
slave device. The range is 32 ms to 655350 ms. The default is 125 ms.
(Entering any value below 32 results in the interval being set to 32 ms.)
The value should be greater than or equal to the Minimum Slave Interval
parameter of the slowest device on the network. However, the interval for
most slave devices is 100 microseconds, and thus the FBM222 default of
125 ms is more than sufficient. The slave device interval is specified in
Min_Slave_Interval in the GSD file. Refer to “Modifying a Device
Configuration” on page 145 for information on setting the slave device
parameter.
Min Slave Interval also needs to be smaller than or equal to the watchdog
timeout set for the slave devices.
Data Control Time Set the range of time allowed for a data exchange between the FBM and a
slave device. The range is 10 ms to 655350 ms. The default is 1500 ms.
The value needs to be greater than or equal to six times the Watchdog
time of the slowest device on the network. Refer to “Modifying a Device
Configuration” on page 145 for information on setting the slave device
parameter.
When Field Device Editor validates the FBM222 configuration (the
Validate button is active once the slave devices have been added to the
port), it displays a system message if the Data Control Time is less than
six times the watchdog time of the slowest device on the port.
The precision for Data Control Time is 10 ms, and the value you enter is
rounded up to the nearest allowed value.
The key bus parameter for the port is the data transfer rate at which its
network operates. The Baud Rate pull-down list includes rates that are
supported by the FBM222 and a majority of PROFIBUS-DP slave
devices. However, some devices may limit your selection. For example,
some slave devices operate at a fixed baud rate, while others only support
relatively slow rates.
Note Before setting the baud rate, refer to the device manufacturer’s
documentation for each device that will be attached to the port. A single device
can limit the entire segment.
The Segment Coupler pull-down list at the top of the FBM222 Bus
Parameters group includes settings for three Pepperl+Fuchs couplers:
SK1, SK2 and SK3. The SK1’s PA interface operates a fixed rate, while
the interface for the SK2 and SK3 can operate in the range 45.45 Kbaud
to12 Mbaud. When one of these is selected, the Baud Rate pull-down list
is enumerated accordingly.
4. Use the Segment Coupler pull-down to select None or one of the three
P+F couplers.
5. Set the network speed using the Baud Rate pull-down list, and then click
Default to set the remaining parameters in the group to the defaults for the
selected speed.
These additional bus parameters are described in Table 4-2. These can be
modified at this time or adjusted later to respond to specific requirements
once the network is in operation.
In most cases, the parameters do not need to be modified once they have
been set to the defaults for the selected baud rate.
Note The unit for time-related parameters is either ms or TBit, that is, the time
needed to transmit a bit at the selected baud rate. For example, 1 Tbit at 12
Mbaud = 1bit/(12,000,000 bit/sec) = 83 nsec.
Table 4-2. FBM222 Bus Parameters Group
Field Description
Max Retry Limit Specify the number of times the FBM re-attempts to communicate with a
slave before determining there is a detected communications failure.
GAP Update Factor This read-only field shows the number of token rounds between GAP
Maintenance cycles. This value has to be set to 1.
Slot Time Set the maximum value of the wait time in TBits for a slave device to
respond to a transaction request. The range is 37 to 16383.
Min Station Delay Enter the minimum value of time in TBits that the FBM needs to wait
Response Time before generating a reply frame. The range is 11 to 1023.
(MinTSDR)
The FBM222 sends this time to each slave device during startup of the
device to help ensure that the device does not respond to requests too
quickly.
Refer to “Modifying a Device Configuration” on page 145 for
information on setting the slave device parameter.
Max Station Delay Specify the maximum value of time in TBits that the FBM needs to wait
Response Time for a slave to process a request and respond. The range is 37 to 65535.
(MaxTSDR) The value must be greater than largest Maximum TSDR configured for
any slave on the port. Refer to “Modifying a Device Configuration” on
page 145 for information on setting the slave device parameter.
Setup Time (TSET) Set the time in TBits between an event such as a timer being interrupted
and the FBM’s response to the event. The range is 1 to 494.
Quiet Time (TQUI) Enter the time in TBits the FBM needs to wait after transmitting a frame
before enabling its receiver. The range is 0 to 493. The value needs to be
less than Min Station Delay Response (Min TSDR).
Table 4-2. FBM222 Bus Parameters Group (Continued)
Field Description
Target Rotation Time Set the anticipated time in TBits for one token round on the segment,
(TTR) allowing for both high and low priority transactions, detected errors and
GAP maintenance. The range is 256 to 16777215.
In a multimaster environment, each master must be configured for the
same target rotation time, and that time must be sufficient for all master
stations to complete all their cyclic data exchange tasks. One method for
setting this time is to determine the target rotation time for each master as
if it were the sole master on the network, and then enter the sum of the
the individual times as the target rotation time for all the masters.
See “Optimization” on page 73 for information on determining an
optimal Target Rotation Time.
Estimated Scan Time This read-only field is set to the Min. Slave Interval in ms.
Validation
The Validate button in the Bus Parameters group becomes active when slave
devices are added to the FBM222 configuration.
Validation checks the port configuration to verify these points:
• The FBM222 and the PROFIBUS devices on the port each have a unique
address in the range 1 to 125.
• Max Station Delay Time (MaxTSDR) is less than Time Slot (TSL).
• Min Station Delay Time (MinTSDR) is greater than Quiet Time (TQUI).
• The number of slaves on port is less than the number defined by
Max_Slaves_supp in the FBM222 GSD file.
• The baud rate configured for FBM222 port is supported by the
PROFIBUS devices on the port.
• Max Station Delay Time (MaxTSDR) is equal to or greater than the
maxTSDR from the GSD file of each PROFIBUS device on the port.
• Min Slave Interval is less than or equal to the configured watchdog
timeout for each of the associated PROFIBUS devices.
• Min Slave Interval is less than or equal to the Min_Slave_Interval
specified in the GSD file of the slowest associated PROFIBUS device on
the port.
• Data Control Timeout configured for FBM222 port is equal to or greater
than six times the configured watchdog timeout for each of the associated
PROFIBUS devices.
Note Maximum input length and maximum output length for PROFIBUS
devices are not configurable and are set to 244, so validations for these
parameters are ignored. Poll timeout for FBM222 is not configurable and is set
to 0.
Validation is performed each time you check in one of the devices or the
FBM222. System messages are shown in the FBM222 Validation dialog box
(Figure 4-9). A device cannot be deployed if it (or one of its devices) has
detected validation errors.
To validate the bus setting for a port on demand:
1. Click Validate to verify that the port configuration is consistent with the
devices that are configured in the Galaxy, that addresses are unique and
within range, and so on.
Detected validation errors are displayed in the Validation Messages dialog
box (Figure 4-9).
2. Click OK to close the dialog box, edit the settings for the listed device,
and run the validation again.
Figure 4-9. Configuration Errors Detected During Validation
Optimization
The Calculate TTR button in the Bus Parameters group, which becomes
active when slave devices are added to the FBM222 port configuration,
enables you to determine an optimal Target Rotation Time (TTR).
To optimize Target Rotation Time:
1. Click Calculate TTR.
Field Device Editor calculates a minimum TTR given the baud rate,
number of devices and number of bytes of I/O, and displays the results in a
list in the Optimize Timing dialog box. In Figure 4-10, the calculated
minimum TTR is 4518 Tbit.
Calculated Ttr
plus
Delta Ttr
equals
Recommended Ttr
Figure 4-10. Recommended Target Rotation Time
The Control Editors add the calculated TTR to a user-set Delta Ttr
(657800 in Figure 4-10) to determine the Recommended Ttr.
The recommended time in Figure 4-10 is for a port on which there are
only two devices and 20 bytes of I/O data, and thus the Recommended
target rotation time (min Ttr) of 4518 Tbit is well below the default time
for the baud rate (100000 Tbit). If the calculated Recommended target
rotation time plus the Delta Ttr is smaller than the default for the baud
rate, the Recommended Ttr is set to the default.
2. Adjust the recommended time if desired by changing the Recommended
Ttr value directly.
3. Click OK to set Target Rotation Time to the displayed Recommended Ttr
and return to the Bus Settings tab (or click Cancel to close the dialog box
without changing Target Rotation Time).
Note Re-calculate Target Rotation Time each time you add devices to a
port or make a change to existing devices that results in increased I/O.
Optimizing Ttr for a Multimaster Network

The Optimize timing dialog box provides Calculated data for a mono master
system, as shown in Figure 4-10. For a multimaster system where two or more
PROFIBUS masters are connected to the segment and performs cyclic data
exchange, the time for each master needs to be added to the target rotation
time. For each master, increase the Delta Ttr by the calculated rotation time for
each of the other masters.
Checking the FBM222 In

To finish the configuration of the FBM222:
1. Use the Configure pull-down list to select Port2, and configure the bus
parameters for that network if it is to be used or uncheck the Use Port
option if the port is not to be used at this time.
2. Click the FBM Manager tab to configure graphics and document links as
described in “Adding Graphics and Document Links” on page 75, or click
in the FBM Editor title bar to save the changes, close the editor, and
check the FBM222 in.
The Control Editors validate the bus setting for the FBM222 and lists any
detected errors in the Output view and the Properties dialog box for the
FBM222. The FBM222 cannot be deployed until the detected errors are
fixed.
Note Refer to “Modifying a Deployed FBM” on page 85 for information on

changing the bus settings in an FBM222 that has already been deployed.
Adding Graphics and Document Links

The FBM Manager is a communication Device Type Manager (DTM) that
provides online diagnostics for the FBM222, a live list display for each
PROFIBUS port, and an identification page with user-configured links to
application notes, drawings, specification sheets and other resources. The tab
also includes a notepad for collecting diagnostics, troubleshooting tips and
other operator information.
Before the FBM222 is deployed and after deployment when it is offline, the
diagnostics and live list tabs are blank. This section describes use of the FBM
Manager during configuration of the FBM to add graphics and document links
to the Identification page. See “FBM Manager” on page 86 for information on
FBM Manager in online mode.
To add graphics and document links to the Identification page:
1. Click the FBM Manager tab to load the communication DTM and display
the FBM Manager Identification tab (Figure 4-19).
The black and white cube icon on the right end of the FBM Manager
toolbar indicates that the FBM is offline and that the other tabs – FBM
Diagnostics, Port1 Live List and Port2 Live List – are empty.
FBM Manager Toolbar
Figure 4-11. Selecting a Document Link for an FBM222
The area at the top of the tab identifies the FBM’s type, letterbug and host
control processor, and provides a description of the FBM type.
Use the Links and Graphics list boxes on left side of the Identification tab to
give users access to documents and illustrations with specifications, plant
standards, troubleshooting tips, or other useful information.
The linked documents can include Acrobat® Reader PDFs, Microsoft Word®
documents, spreadsheets, or help files. When selected, a linked document
opens in a separate window in its native application. Windows® displays a
dialog box for selecting a program if the file’s native application is not
available.
The graphics can include bitmaps, JPEGs, and images in other common
graphics formats. When selected, the image is displayed in the pane to the right
of the Graphics and Links boxes.
Figure 4-11 shows links and graphics configured for an FBM222 (PROF01).
The FBM Manager does not store copies of the files with the device
information, but only the entire path name and an alias for each file reference.
The files themselves need to be maintained in a shared drive that is commonly
accessible to the Foxboro Evo Control workstations accessing the FBM. The
file needs to be specified using a network path (for example,
\\Profibus\Docs\Standards\SCL_FBM222.doc in Figure 4-11).
The files references are automatically included in Galaxy backups and exports
of the template. However, the files themselves are not included and need to be
backed up separately.
The tools at the top of each box enable you to edit an existing file selection,
delete a link or image, and select a new file. The Link instructions that follow
also apply to the Graphics box.
To configure a link:
1. Click the Add button above the Links box to open the Select File dialog
box (Figure 4-12).
2. Click to right of the first field in the dialog box to browse for and
select the file using a Windows Open dialog box.
The first field in the File Select dialog box shows the path name of the file.
The Alias field shows how the file will be named on the FBM
Identification tab.
3. Enter a new name in the Alias field if desired.
4. Click OK.
The selected alias is displayed in the Links list box.
5. Double-click the alias to test the link.
To change a link:
1. Select the link and click the Edit button above the Links list box to open
the Select File dialog box.
2. Change the path and/or alias, and click OK.
To delete a link:
• Select the link and click the Delete button above the Links list box.
Setting ECB200/202 Parameters

When you add an FBM222 to the Galaxy, the Control Editors create an
equipment control block (ECB200). If the FBM is then defined as a redundant
pair, the block is changed to an ECB202.
When you assign the FBM to an FCP280, FCP270, or an FCM100, the Control
Editors place the ECB in the control processor’s ECB compound
(FCP001_ECB for the example control processor).
The ECB200/202 parameters are configured with the default values from the
block definition. For example, Failsafe operation is disabled and the sampling
rate (PERIOD parameter) is set to 1 - 0.5 sec|0.5 sec.
Note Most of the ECB200/202 parameters are set properly by default. The
Failsafe parameters are likely to change, based on the requirements of the
process.
To review or modify the configuration of an ECB for an FBM222:

1. Right-click the FBM222 in the Network view and choose Open Related
ECB from the context menu.
The Control Editors open the containing compound in the Control
Software Block Configurator, displays the ECBs tab, and selects the FBM
ECB in a table on the left side of the tab (PROF01 in Figure 4-12).
You can also access the ECB by double-clicking the containing compound
(usually the control processor’s ECB compound, FCP001_ECB in the
example), and then selecting the ECBs tab in the Block Configurator.
Additional information about editing compounds and ECBs can be found
in Block Configurator User’s Guide(B0750AH).
Figure 4-12. Editing an FBM222 ECB
The tabbed pages on the right include controls for editing the selected
ECB.
2. Review and, if necessary, modify Block Sampling Rate (PERIOD) and

Block Phase Number (PHASE) in the General tab.
In most cases, the ECB PERIOD and PHASE need to be 1 and 0,
respectively, so that the ECB runs with every Basic Processing Cycle
(BPC) of the host control processor. This helps ensure that the
corresponding DCI blocks also run with the correct PERIOD and PHASE.
Note With a redundant FBM222, the control processor can access the
FBM data in a 500-ms BPC. With a non-redundant FBM222, the BPC can
be as fast as 100 ms.
3. Click the FBM tab (Figure 4-13) and modify the parameters described in
Table 4-3.
Figure 4-13. FBM Tab in the ECB Editor
Table 4-3. FBM Tab Parameters for the ECB200/202
Parameter Description
Device Identifier This read-only field displays the FBM’s contained name, the name that is
downloaded to the control processor, as described in “Naming FBMs” on
page 63.
Hardware Type These two fields were set to 222 when the FBM was derived from the
Software Type FBM222 template.
Port Existence This parameter is set when Port 1 and Port 2 are enabled or disabled in the
Bus Settings tab in the Control Editors Device Editor (see “Setting Bus
Parameters” on page 67). This read-only field can have the these values:
• 3 when both ports are enabled
• 2 when only Port 2 is enabled
• 1 when only Port 1 is enabled
• 0 when neither port is enabled
Failsafe Enable When Failsafe is enabled for a port, the FBM initiates whatever Failsafe
action is configured in the devices on that segment if communication is
interrupted between the FBM and the control processor for longer than the
time specified in Failsafe Delay (or FSDLAY).
Use the drop down list for Failsafe Enable (or FSENAB) to select one of
these options:
• 0 to disable failsafe logic for devices on both ports. This is the default
setting.
• 1 to enable failsafe logic for devices on Port 1 only.
• 3 to enable failsafe logic for devices on both ports. We recommend this
setting.
• 4 to enable failsafe logic for devices on Port 1 only, and disable
communication on the port once the failsafe actions have been taken.
• 6 to enable failsafe logic for devices on both ports, and disable
communication on both ports once the failsafe actions have been taken.
We recommend that the configuration is Failsafe Enable = 3 Enable failsafe
for both ports (PROFIBUS only).
Failsafe Delay When Failsafe is enabled for a port, the FBM initiates whatever Failsafe
action is configured in the devices on that segment if communication is
interrupted between the FBM and the control processor for longer than the
time specified (in 10-msec increments) in Failsafe Delay (or FSDLAY).
We recommend that the configuration is Failsafe Delay = 1000, which sets
the delay to 10 seconds.
The System Configuration parameter is not used with the FBM222.
Table 4-3. FBM Tab Parameters for the ECB200/202 (Continued)
System Option With the System Option (or SYSOPT) parameter, you can enable or disable
System Alarming and/or System Messaging as follows:
• Leave the parameter value set to 0 to enable both the alarm features. We
recommend this setting.
• Enter 1 to disable system alarming but enable system messaging.
• Enter 2 to enable system alarming but disable system messaging.
• Enter 3 to disable both system alarming and system messaging.
The File Identifier, Watchdog Timer and Software File ID fields can be ignored, as these
parameters are not used by the FBM222.
4. Review and, if necessary, modify the settings on the History and Security
tabs.
Refer to Block Configurator User’s Guide (B0750AH) for additional
information on configuring ECBs and ECB compounds.
5. Click in the Block Configurator title bar to save the changes, close
the editor, and check the ECB and ECB compound in.
Deploying the FBM

The next step is to deploy the FBM222, that is, download the ECB200/202 to
the host control processor. The host control processor and its equipment unit
needs to be already deployed, or be deployed with the FBM222 (as is the case
with the example system in this chapter).
The steps for deploying an FBM are briefly noted below. Refer to the Control
Database Deployment User’s Guide (B0750AJ) for more detailed instructions
on deploying hardware configurations.
The Control Editors validate the FBM222 bus settings each time the object is
checked in and stores the detected validation errors with the object. The
detected validation errors are displayed in the FBM222’s Properties dialog
box. The FBM222 cannot be deployed if it has any detected validation errors.
Fix the detected validation errors before deployment:
1. Right-click the FBM222 in the Network view, choose Properties from the
context menu and click Errors/Warnings in the Properties dialog box to
display any detected validation errors.
2. Fix any detected errors in the Bus Settings tab for the FBM222 and/or the
attached devices.
3. Validate the FBM222 configuration.
This is done when you close the FBM editor and check the FBM222 in.
You can also validate the FBM222 by right-clicking on the FBM in the
Network view and choosing Validate from the context menu.
To deploy the FBM:

1. Expand the Galaxy name in the Deployment view to display the FBM, its
host control processor and the equipment unit to which they are assigned.
2. Right-click the equipment unit and choose Deploy from the context menu
to open the Deploy dialog box.
3. Click + to the left of the equipment unit and other nodes to expand the
display and view the contained objects to be deployed (Figure 4-14).
Figure 4-14. Deploying an Equipment Unit
4. Select the equipment unit and click Add Cascade to move the items to the
Objects to be processed pane on the right, and then click Prepare All to
verify that the items can be deployed successfully (Figure 4-14).
Figure 4-15. Equipment Unit, FCP270 and FBM222 Can Be Deployed

(FCP280 Deployed in Similar Manner)
5. Fix any detected errors identified in the Deploy dialog box.

6. Click Deploy when the objects have passed the preparation.
The Deploy dialog box shows the actions taken in the deployment, and
lists detected errors (Figure 4-16). These messages are also shown in the
Output view.
Figure 4-16. Deployment Actions and Detected Error Messages
7. Click Close when the dialog box indicates that the deployment is done.
Going Online
The section briefly describes use of the System Manager to bring the FBM222
online. Refer to “System Management” on page 361 and to System Manager
(B0750AP) for additional information on System Manager displays and

functions.
To bring the FBM222 online:
1. Start System Manager on the workstation if it is not already operating.
2. Expand the system monitor domain in the Navigation pane to display the
control processor and its attached FBMs and FCMs.
Figure 4-17 shows two system monitor domains expanded in the
Navigation pane, each with an FCP280 or FCP270, which in turn has been
expanded to show its Primary FBM and the attached FBMs.
3. Select the host control processor and review its status and equipment
information in the Information pane General tab to verify that the control
processor is online.
System Monitor
Control Processor
Primary ECB
FBM222
Figure 4-17. FBM222 and Host Control Processor in the Navigation

Pane
4. If the control processor is a ZCP270, select the FCM that connects the
FBMs to the control processor to display the equipment status in the
Information pane to verify that the module is online.
5. Right-click the FBM (PROF01 in Figure 4-17), choose Go Online from
the context menu and respond to the prompts in the Go Online dialog box:
If the FBM222 is a non-redundant module:
• Enter a comment if prompted, and click OK.
If the FBM222 is a redundant pair:
• Click the checkboxes for Main and Backup, enter a comment if
prompted, and click OK.
6. Observe the FBM equipment status in the General Information pane.
Modifying a Deployed FBM

If you need to change bus settings on an FBM222 that has already been
deployed, you need to redeploy the FBM after making the changes in the Field
Device Editor.
Note Validate the configuration for the effected port before re-deploying the
FBM222 ECB.
Note 1) Selecting Upload/Download in the Control Editors’ Deployment

Utilities does not support selective upload of the port settings (to the FDATA1
through FDATA4 parameters) from a PROFIBUS device or its host FBM222.
2) The dialog box does support selective downloads of the FDATA1 through
FDATA4 parameters to PROFIBUS device and the host FBM.
3) The FDATA1 through FDATA4 parameters contain the PROFIBUS
configuration data. These parameters cannot be seen as separate parameters.
You need to deploy all the parameters to help ensure a consistent and valid
PROFIBUS configuration.
Certain changes can be implemented dynamically, while others need that the
FBM222 be taken offline. These bus parameters can be changed dynamically:
• Highest Station Address
• Min Slave Interval
• Max Retry Limit
• Slot Time
• Max Station Delay Response Time
• Target Rotation Time
For changes to the other bus settings or to any other FBM222 parameter, you
need to perform an orderly shutdown of the FBM and the PROFIBUS network
using the System Manager commands described in “FBM222 Equipment
Change Actions” on page 380.
To change an FBM222 configuration:
1. Edit the bus parameters for each port in the Field Device Editor as needed
(see “Setting Bus Parameters” on page 67).
2. Click Validate for each port to verify that the bus settings are appropriate
given its attached PROFIBUS slave devices.
3. Edit the ECB200/202 parameters in the Block Configurator as needed (see
“Setting ECB200/202 Parameters” on page 77).
4. Close both editors and verify that the FBM is checked in.
5. Use System Manager to take the FBM222 off line (see “Go Online and Go
Offline” on page 382).
6. Right-click the FBM222 in the Control Editors’ Network view and choose
Deploy from the context menu.
The Deploy dialog box will identify which ECBs have changed since their
last deployment.
7. Use the dialog box to select the FBM222 ECB, prepare the block for
deployment, and download it to the control processor.
8. Use System Manager to restart the FBM222 (see “Download” on
page 383).
9. Monitor the FBM and its attached devices in the System Manager
Information pane and Accessories panel.
FBM Manager
The FBM Manager contains a communication DTM that provides online
diagnostics for the FBM222 and a live list display for each PROFIBUS port.
The FBM Manager also includes an identification page with user-configured
links to application notes, drawings, specification sheets and other resources,
as described in “Adding Graphics and Document Links” on page 75, and a
note pad for collecting diagnostics, troubleshooting tips and other operator
information.
Note The Instrument Workshop version of Field Device Manager uses a

third-party communication DTM instead of the editor’s built-in DTM, which is
designed for the FBM222 and the control processor. Configuration and use of a
third-party communication DTM is covered in “Configuring the
Communication DTM” on page 343.
Auto Online
The FBM Manager can be set to go online automatically when the
communication DTM is loaded. If the Auto Online option is not enabled, FBM
Manager starts in offline mode and displays a Go Online button. The Auto
Online feature and the Go Online button are only active when the FBM is
deployed.
To enable or disable Auto Online:
1. Choose Tools > User Preferences from the IDE main menu.
2. Check or uncheck the Auto Online box in the User Preferences dialog box
(Figure 4-18) to enable or disable the feature, and click OK.
The preference is implemented the next time you open the FBM Manager
or Field Device Manager.
This button is shown when

Auto Online is disabled
Check this box to enable

Auto Online
Figure 4-18. Setting the Auto Online Option
FBM Manager Toolbar

To access the FBM Manager:
1. Double-click the FBM222 in the Network view to open the module in the
Control Editors and click the FBM Manager tab.
When the DTM is loaded, the FBM Manager opens to Identification, the
first of four tabbed pages (Figure 4-19).
2. Click Go Online if the button is displayed at the top of the FBM Manager
tab.
The area at the top of the tab identifies the FBM’s type, letterbug and host
control processor, and provides a description of the FBM type. The
remainder of the tab provides user-configured links to graphics and
documents, as described in “Adding Graphics and Document Links” on
page 75.
FBM Manager toolbar
Figure 4-19. FBM222 Identification Tab
Table 4-4 describes the buttons in the upper right corner of the FBM Manager.
These tools are available for the tabs.
Table 4-4. FBM Manager Icons
Icon Description
Opens the Notes window for the module.
Starts HTML help for the FBM Manager.
Table 4-4. FBM Manager Icons (Continued)
Icon Description
The yellow exclamation point on an orange triangle
indicates detected error messages in the Output view and
the Error Monitor (Figure 4-20).
The icon is black and grey when there is no message
available or the messages have been acknowledged, that is,
cleared from the monitor.
The multi-colored cube indicates that the FBM222 is
online. The cube tumbles when the FBM is communicating
with the PROFIBUS network.
The cube is displayed in gray scale when the FBM is
offline.
Error Monitor
A yellow exclamation point on an orange triangle in the upper right corner of
the FBM Manager tab alerts you that there is a least one unacknowledged error
detected in the FBM’s communication with the slave devices.
To view and acknowledge detected error conditions:
1. Click to display the Error Monitor (Figure 4-20).
The monitor displays a table of the messages with the columns described
in Table 4-5.
Table 4-5. Messages in the Error Monitor
Column Description
Time Gives the date and time of the message
Error Indicates the severity level of the message: Error, Warning
or Informational
Source Identifies where the error was detected: Internal, Session
Manager, ATM Server, and so on
Description States the nature of the detected problem
Operation Describes what the FBM222 was doing when the error was
Name detected
2. Check or clear the three Options boxes in the lower left corner of the
monitor and the click Refresh to select the kind of messages to be
displayed.
For example, you can clear the Warning and Informational check boxes
and click Refresh to display only detected Errors. Filtering messages from
the display does not clear the messages.
The messages are not maintained in the Error Monitor after the FBM
Manager is closed.
3. To save the messages:
a. Click Copy to Clipboard to place the messages on the Windows
clipboard in a tab-delimited format.
b. Open a text editor or spreadsheet application, and paste the message

text into the document or worksheet.
c. Print and/or save the file.
4. Click Clear to acknowledge the detected error conditions and remove the
messages from the monitor.
The Error Monitor icon changes to black and white.
5. Click Close to close the window but maintain the messages until the FBM
Manager is closed.
Click this button to copy

Click this button to display
messages to the clipboard
the latest messages in the
to document activity
monitor
Click this button to clear

all messages from the
Check the type of messages Error Monitor
to be included
Figure 4-20. Error Monitor Opened for an FBM222
FBM Note Pad

The graphics and document links provide general information about FBM222s,
while the Notes feature enables you to record information about the specific
module, including detected error messages, adjustments made to the
PROFIBUS networks, and so on.
To record information about the FBM222:
1. Click Notes in the FBM Manager toolbar.
2. Type the comments in the Notes window and/or use Ctlr+V to paste in
text copied to the clipboard from the Error Monitor or other sources
(Figure 4-21).
Figure 4-21. Note Pad for an FBM222
3. Click Save keep the changes and click Close to exit the Notes window.
Context Menu
Right-click on any tab in the FBM Manager for a context menu that includes
these choices:
• Configure displays the FBM Manager Identification tab.
• Associate Vendor Communication DTM opens a dialog box for
selecting a third-party PROFIBUS communication DTM to be used
instead of the communication DTM built into the FBM Manager. Vendor
communication DTMs are used in instrument workshop systems, not in a
control room system. See “Configuring the Communication DTM” on
page 343 for details.
Use of Color in FBM Manager Displays

Table 4-6 describes the use of background colors in parameter value fields in
the FBM Manager to indicate various states.
Table 4-6. Use of Fill Colors in Field Device Manager

A white background indicates that the value has been
successfully uploaded from the device.
A cyan value field indicates that the value is no longer being

read from the device.
Cyan is the fill color for the last retrieved values when the
FBM goes from online to offline.
When FBM Manager is displaying a Live List tab, and the
FBM222 goes offline, cyan is fill color for the entries in the
tab.
When FBM Manager is displaying a Live List tab, if an
individual device goes from the Connected state to
Disconnected, cyan is used for the devices’s Ident No field as
the identification number cannot be read from the device.
Cyan is also used for the Vendor and Model fields, which are
mapped to the identification number in the DevLiveList.xml
file, as these attributes are not retrieved from the file. (See
Table 4-8 on page 96 for a description of the live list fields
and DevLiveList.xml.)
Red indicates that there has been a detected failure to upload
the value.
When a Live List is displaying values from the port and a
device becomes disconnected, red is used in the device’s
Connected field on the next update. The field then returns to
white after subsequent updates.
Note If you are not able to distinguish between colors in the Field Device
Manager displays, contact your Schneider Electric Systems representative for
information on enabling the software to use symbols as state indicators.
FBM222 Diagnostics Tab

The FBM Diagnostics tab (Figure 4-22) displays counters for communications
events and detected errors, and provides tools for advanced troubleshooting.
Schneider Electric service representative may ask for specific counters from
this page to resolve a detected problem.
To display the counters:
1. Click the Go Online button if it is displayed and then click the
Diagnostics tab.
The tab consists of a table with the five sets of counters (described in
Table 4-7) and subsets for the main and backup modules.
The counters are maintained by the FBM222 to measure communication

activity and detected errors. The Help String column provides a brief
description of each counter. A high value for a counter in this tab or other
diagnostic displays does not necessarily indicate a detected problem.
Table 4-7. FBM222 Diagnostics Counters
Counter Type Description

HSCC Channel A High Speed Communication Controller
HSCC Channel B counters deal with base-layer communication
between the control processor and the FBM
through Channel A and Channel B.
HDLC High Level Data Link Communications
counters deal with communications activity
between the FBM and the host FCP280,
FCP270, or FCM
PIO Bus A Process Input Output counters deal with
PIO Bus B communication on the two channels of the
module fieldbus between the FBM222 and the
host FCP280, FCP270, or FCM.
DCI Distributed Control Interface counters
measure traffic between the FBM and the
attached devices resulting from DCI
connections specified in the control database
Redundancy Interface Redundancy counters measure traffic between
Redundancy Channel A modules in a redundant pair.
Redundancy Channel B
When the tab is first displayed (and FBM Manager is in online mode), the
FBM Manager uploads the counter values from the FBM222, and then
repeats the upload at a user-set interval.
2. Click Modify Update Time, specify the update interval in the Modify
Update Time dialog box (Figure 4-22), and click OK.
The interval needs to be in the range of 10 seconds (the default) to 120
seconds. This rate is independent of the interval specified for each of the
Live List tabs.
Figure 4-22. FBM Diagnostic Tab
If the FBM goes offline while the Diagnostic tab is displayed, the Value
fields turn cyan to indicate that the counters are not being updated. The
date and time above the table indicate when the counters were last read
from the FBM.
3. Click + to the left of a set label to expand the display; click - to the left of
the set label to collapse the display and hide the individual counters.
4. Click one of the buttons in the Reset Counters group to reset the counters
in the selected category or to reset the counters maintained by the
FBM222.
Live Lists
The Port1 Live List (Figure 4-23) and the Port2 Live List tabs identify the
devices on the respective ports, and display addresses, current status and
device information. The tabs also enables you to check the communications
between the FBM and a selected device, and to modify device addresses.
The live lists include the devices that are physically connected to the port,
whether or not they have been configured in the Control Editors and deployed
to the FBM. The list also includes device configurations that have been
deployed, but for which there are no devices with the same address physically
connected to the port.
Note If the Master Station Address for an FBM222 has been modified in the
Bus Settings tab, the change needs to be deployed to the FBM222 before
opening the Live List in the FBM Manager. Otherwise, the live list request will
fail for the corresponding port.
To access the live list for an FBM222 port:

1. Click either Port1 Live List or Port2 Live List.
The editor displays the Live List tab for the port; the multi-colored cube
icon on upper right corner of the window rotates as the FBM queries the
segment and builds the live list table. The FBM Manager refreshes this
display at a user-set interval.
2. Click Modify Update Time, specify the update interval in the Modify
Update Time dialog box (Figure 4-22), and click OK.
The interval needs to be in the range of 10 seconds (the default) to 120
seconds. This rate is independent of the intervals specified for the
Diagnostics tab and for the other Live List tab.
These buttons are active only when

a device is selected in the live list
Figure 4-23. Live List for an FBM222 Port
Fill colors in the live lists and the associated dialog boxes indicate the status of
communications between the FBM and the device:
• White indicates that the information is being read from the FBM and the
attached device.
• Cyan indicates the field is not being updated because the device or the
FBM is offline.
• Red indicates a communication interruption.
The Device Count above the list represents the number of connected devices
that are responding to the FBM. The count does not include any device
configuration for which there is no connected device with a matching address.
Table 4-8 describes the fields in the live list tables.
Table 4-8. Live List Fields
Field Description
Address Unique address for the device is shown in both decimal and
hexadecimal. The address is read from the connected
devices on port and from the device configurations that
have been deployed to the FBM
Ident No. PROFIBUS ID, read from the device, identifies the device
type
Master/Slave The device at the address is either a Master or Slave
State Status of the device can be Configured, Not Configured,
or Active
Connected Indicates whether a device with address is physically
connected to the PROFIBUS network
Vendor The identification number, which is retrieved from the
Model device, is mapped to the Vendor and Model in the local file
DevLiveList.xml, thus supplying manufacturer and model
names for these two fields. This sample from the file shows
the mapping for identification number 55697.
The file contains mappings for a majority of the devices.

The Vendor and Model fields are blank when the device is
not included in DevLiveList.xml.
The file is in the folder PBDPV1Pthru, which is located in
the path specified in the XMLFoxFDTPath registry entry.
You can map additional identification numbers to vendor
and model names by opening the file in a text editor, such
as Notepad, and adding entries in the form shown above, or
using the DeviceDetailXMLGenereator utility, which
extracts the information from the device’s GSD file.
The program is located in a folder of the same name
under ..\Program Files\Invensys\InFusion\Profibus
Support.
Comparing a Configuration with the Installed Device

For additional information about a device:
1. Click the tab for the appropriate port live list, select the device in the list
and click Details to display the Device Details dialog box (Figure 4-24).
Figure 4-24. Device Details Dialog Box
The dialog box compares the device configuration downloaded from the
Control Editors to the FBM (Configured device column) with the information
read from the actual device (Connected device). Which fields are read from
the device depends on whether the slave is PA device, Identification &
Maintenance Profile (I&M), or other device (Table 4-9).
Table 4-9. Device Details Dialog Box
Connected: Read from the

Field Configured: Read from the FBM Device
Tag The device tag, or contained name, is The tag is read from connected PA
only shown in the Configured Device and I&M devices. Blank for the other
column devices
Address Configured address from the FBM The network address of the connected
device
Ident No PROFIBUS ID Number is read from PROFIBUS ID Number is read from
the device configuration the connected device
Manufacturer ID Vendor name read from the device Read from connected PA and I&M
configuration devices. Blank for the other devices
Product Name Product name read from the device Read from PA devices. Blank for the
configuration other devices
Order ID Order ID is read from device Read from I&M devices. Blank for
configuration the other devices
Hardware Revision Read from the FBM if present in the Read from connected PA and I&M
Software Revision device configuration devices. Blank for the other devices
Serial Number
2. Click OK to close the dialog box.
Checking Slave Communication

To check the communication between the FBM222 and a specific device:
1. Click the tab for the appropriate port live list and select the device in the
grid.
2. Click the Comm. Diagnostics button below the list to display the Slave
Communication Diagnostics dialog box (Figure 4-25).
Figure 4-25. Slave Communication Diagnostic Dialog Box
Table 4-10 describes the fields in the dialog box.
Table 4-10. Slave Communication Diagnostics
Fields Description
Current state of the slave 1 indicates that the device is engaged in
(Activated/Deactivated) data exchange with the FBM; 0 indicates
that the device is inactive
Number of C2 connections Number of clients with Class 2
established to the slave connections to the device, including the
FBM; other clients are from within the
Control Editors
Number of Diagnostic messages Number of diagnostic messages received
received for the slave from the device
Number of Acyclic Read/Write Number of Class 2 read/write requests
requests for the slave sent to the slave device
Number of C2 Abort indications Number of times the Class 2 connection
received for the slave to the device has been aborted
3. Click OK to close the dialog box.
Changing a Device Address

The live list tabs enable you to change the network address of a slave device, if
the device supports remote address changes. The action changes the address in
the device, but not in the Galaxy.
To change an address:
1. Click the tab for the appropriate port live list and select the device in the
grid.
2. Click the Change Address button below the list to display the Change
Device Address dialog box (Figure 4-25).
Figure 4-26. Changing a Slave Device Address
3. Use the pull-down list in the New Address field to select from addresses
which are not occupied by the connected devices.
4. Click Change to implement the change and close the dialog box.
FBM Manager displays a message as to whether the change was
successful.
101
C H A P T E R 5
Creating Device Templates
This chapter describes how to define device types and manage device
templates within a Galaxy.
Contents
• Introduction
• Locating GSD Files
• Setting Up a Project Folder
• Creating a Device Template
• Associating a GSD File with a Template
• Associating a DTM with the Template
• Switching to DTM-Based Module Definition
• Changing GSD Information
• Editing a Device Template: General Tab
• Managing Device Templates
Introduction
One of the first steps in setting up a PROFIBUS application in the Control
Editors is to define the types of devices to be deployed in the project. Each
device type is an ArchestrA application object template that is bound to a
specific General Slave Data (GSD) file. The manufacturer-supplied GSD file
describes the PROFIBUS characteristics of the device such as supported baud
rates, available plug-in modules, and I/O configurations.
PROFIBUS device templates are created from a base template ($Profibus)
located in the Control Editors’ Template Toolbox. The first-generation
templates are referred to as base derived templates.
The template is then opened in the Field Device Editor and GSD information is
entered into the template using one of these methods:
• Associating the template with a GSD file as described on page 106
• Associating the template with the device manufacturer’s DTM as
discussed on page 109.
102 5. Creating Device Templates
The device values can be edited at the template level and in the individual
devices derived from the template.
Once a type is defined, multiple instances of the type can be added to an
FBM222 to create the PROFIBUS network. The device values as configured in
the template are copied to the instances.
Certain parameters values can be locked in the template so that they cannot be
changed in the device instances derived from the template. When a locked
parameter is changed in the template, the new value is propagated to the device
instance. This inheritance feature is described in greater detail in “Locking and
Inheritance” on page 171.
Application-specific device types can be derived from a single device
template. These derived templates copy the parameter values from the base
derived template, while application-specific items can be set in the derived
device types.
The Control Editors Derivation view in Figure 5-1 shows four device instances
and their defining templates:
• ACR001 and ACR002 were derived from the $ACR_12DI, a base derived
template.
• DEV001 is a positioner derived from the template $SRD991.
• DEV002 is a positioner derived from the application-specific template
$SRD991_001, which in turn was derived from $SRD991.
Note The device instances are marked with a gold square to indicate that they
have not yet been deployed.
5. Creating Device Templates 103
Base device
template
Base derived
template
Instance from
a base derived
template
Derived
template
Instance from
a derived
template
Figure 5-1. Templates Derived from $Profibus
Locating GSD Files

The Control Editors create the device type by extracting information from the
GSD file (or that could be extracted from the manufacturer’s DTM). To
identify the correct GSD file, you need the device’s PROFIBUS Identification
Number, a four-digit hexadecimal number that uniquely identifies the
manufacturer and the device. The PROFIBUS ID is by default the last four
characters of the GSD file name.
The GSD file extension is either *.gsd (for general slave default, which is
usually an English language file) or one of the these language-specific
extensions:
*.gse for English *.gsi for Italian
*.gsf for French *.gsp for Portuguese
*.gsg for German *.gss for Spanish
A general description of GSD files, including examples, can be found at

http://www.Profibus.com. The files themselves can usually be downloaded in a
compressed folder from the manufacturer’s web site, and then extracted to a
temporary folder. Once the GSD data has been bound to a device template, the
original device file is no longer needed by the Control Editors. The directory
can be located anywhere on the workstation used to define the device type.
Setting Up a Project Folder

Device types are derived from a base template ($Profibus) in the Template
Toolbox. The template is located in the Profibus toolset folder under InFusion
Hardware > InFusion Devices (Figure 5-2).
Note Use the base template $DEV_ECB201 under Generic Devices when
creating device templates for use with the FBM223.
When a device type is derived, the new template ($Profibus_001 in

Figure 5-2) is located in the same toolset folder as the parent template.
However, any template (including the base templates) can be moved to another
folder in the Template Toolbox, including user-defined project folders, which
may also contain strategy templates, bulk data objects, and other resources.
You can, for example, create a folder for each manufacturer, or organize the
device types by application.
To set up a toolset folder:
1. Right-click a folder or the Galaxy name at the top of Template Toolbox
and choose New Toolset from the context menu.
The new folder is placed under the selected node with a default name such
as NewToolset_001. An edit box surrounds the name indicating that it can
be changed now.
2. Press Enter to accept the default name, or type a new name and press
Enter.
3. Drag device types and other templates to the folder.
Base device
template
User-defined
toolsets
Figure 5-2. Location of the PROFIBUS Device Base Template
Note You cannot copy device templates, only move them. You can also drag
the toolset to another location in the Template Toolbox, rename the folder, and
delete the folder (if it is empty and it is a user-defined toolset).
Creating a Device Template

To define a base derived template:
1. Expand InFusion Hardware > InFusion Devices > Profibus in the
Template Toolbox to display the base device template ($Profibus) and
templates derived from it.
2. Right-click $Profibus and choose New > Derived Template from the
context menu to create a new base derived template.
The new template is placed in the Profibus folder with a default name such
as $Profibus_001. The name is enclosed in a box indicating that you can
rename it now.
3. Press Enter to accept the default name for now.
The Control Editors rename the template when it is bound to a GSD,

which is done with one of these methods:
• Associating the GSD file with the template, as described in the next
section
• Associating a vendor-supplied device DTM with the template (in
which case the GSD information is extracted from the DTM), as
discussed in “Associating a DTM with the Template” on page 109.
Associating a GSD File with a Template

To bind a GSD file to a device template:
1. Double-click the template in the Template Toolbox ($Profibus_001 in
Figure 5-3) to open template in the Field Device Editor.
Before the template is bound to a GSD file, the editor shows only the
General tab.
2. Click Associate GSD in the General Information group at the top of the
tab to open the Select GSD File dialog box (Figure 5-3).
The Object Information group also includes the Associate DTM button,
which is described in “Associating a DTM with the Template” on
page 109 and the Export GSD button, which is explained in “Changing
GSD Information” on page 124. The Export GSD button is inactive at this
point because the template does not yet contain GSD information.
3. Use the dialog box to browse for and select the GSD file (*.gs*) for the
device, and then click OK.
Figure 5-3 shows the selection of the GSD file for an Acromag discrete
I/O module that provides 12 digital inputs.
Figure 5-3. Selecting a GSD File
The editor displays the Device Type Tag dialog box (Figure 5-4), which
shows the device manufacturer, model and revision from the GSD file, and
allows you to modify a suggested tag for the device template. The
suggested tag is created from elements in the GSD file. If necessary, Field
Device Editor appends numbers to the suggested name to help ensure that
the tag is unique among the object tags in the Galaxy.
This tag is only used in the Control Editors and is not downloaded to the
control processor. The tag can be changed later in the Template Toolbox as
described in “Rename the Template” on page 132.
Figure 5-4. Device Type Tag Dialog Box
4. Modify the suggested tag and click OK to return to the Field Device
Editor (Figure 5-5).
The Field Device Editor now displays these tabs:
• General identifies the device type and GSD, and provides tools for
naming the device instances created from the template.
• Bus Settings is used to edit device communication parameters such as
minimum response delays, mode selection, and the watchdog timer.
• Modules defines the modules and user parameters to be used in the
slave device.
• Data Definition specifies the I/O points of the PROFIBUS slave
device.
• Field Device Manager contains the universal PROFIBUS device
type manager (DTM) for online access to device instances. At the
template level, the tab is used to configure links to documents and
drawings, and to customize the user interface by adding and
modifying tab pages, setting access permissions and specifying
download lists.
Figure 5-5. General Tab after Association of a GSD File
The Associate GSD button in the Object Information group remains

active, enabling you to change the GSD information in the template.
Note Updating the GSD Information in the template is not intended to

change the basic characteristics of a device. It only allows changes that are
needed to connect a PA device to the PROFIBUS network.
If device parameter changes, such as module definitions, are made in the
template, it will cascade these changes to the instance definitions. It is
good practice to use the templates for the standard configuration of
network-related parameters.
The Associate DTM button also remains active, providing the option of
using a DTM from the device manufacturer for certain configuration and
maintenance tasks.
The Export GSD button becomes active now that the template contains
GSD information from the associated file.
In Figure 5-5, the radio buttons for selecting a tool for module definition
are read-only as GSD is the only choice because there is no vendor DTM
associated with the device template.
5. Specify the instance naming rules as described in “Editing a Device
Template: General Tab” on page 127.
6. Set other device parameters as discussed in Chapter 7, “Configuring
Devices” and Chapter 8, “Field Device Manager”.
The values configured in the template are copied to each device created
from the template. Refer to “Locking and Inheritance” on page 171 for
information on how changes to the device template affect the instances
created from the template.
7. Click in the Field Device Editor title bar to close the editor, save
changes to the device template, and check the template in.
8. Enter a comment and click Close in the Check In dialog box, if the dialog
box is presented.
The Control Editors rename the template as specified in the Device Type
Tag dialog box. Figure 5-6 shows the newly created template in the
Template Toolbox. The template tag has been shortened to Acr_12DI.
Figure 5-6. New Base Derived Template
Associating a DTM with the Template

In some instances, you may want to use a DTM supplied by the device
manufacturer for device configuration and online access, in which case you
can associate the template with the vendor’s DTM instead of associating the
template with the GSD file. The GSD information is extracted from the DTM
and bound to the template.
You can also associate the DTM with a template that has already been bound to
a GSD file. When you do so, the Field Device Editor presents a comparison of
the identification data from the two sources (Figure 5-12 on page 115). This
allows you to check if the vendor DTM fits the template which is already
defined by the associated GSD file. In this case, the GSD file information
extracted from the DTM does not replace the already associated GSD file. The
GSD information from the vendor DTM can be saved to a file using the Save
New GSD File button in the Comparison of GSD Information dialog box.
Note Manufacturer-supplied DTMs may vary in their full compliance with

PROFIBUS and FDT specifications. Please confirm the applicability of each
vendor-supplied DTMs for your project.
Note If you plan to use the Control Editors link to FoxCTS software to track
changes to deployed slave device configurations, verify that the DTM includes
the optional audit trail interface defined in the FDT standard. See Chapter 12,
“Change Tracking” for details.
Before you begin:

• Install the device DTM on each server and client workstation that uses the
DTM.
• When installing a DTM on a workstation, install the software on the D:
drive, not on the C: drive.
• Review the system requirements for each DTM. Some DTMs cannot be
installed on a server with Windows Server 2003.
Template Not Bound to a GSD File

This section describes associating a DTM with a template that has not been
bound to a GSD file. In this case, the Field Device Editor extracts the GSD
information from the DTM and binds it to the template, and selects the DTM as
the tool for configuring modules and user parameters.
To associate the manufacturer’s DTM with the device template:
1. Double-click the device template in the Template Toolbox if the object is
not already open in the Field Device Editor.
General is the only tab displayed as the template has not yet been bound to
a GSD file or DTM.
2. Click Associate DTM to open the Vendor Device Type Selection dialog
box (Figure 5-7).
Figure 5-7. Vendor Device Type Selection Dialog Box
The dialog box displays the PROFIBUS device DTMs installed on the
workstation as listed in a locally stored catalog. The browser displays a
Warning dialog box (Figure 5-7) if a DTM was installed or uninstalled
since the last time the catalog was refreshed. (The dialog box is displayed
if an error is detected during a scan process. Check the Do not Show...
option in the dialog box to avoid display of the system message with this
kind of detected errors.)
3. Click OK to return to the browser, and then click Refresh to update the
catalog.
Another dialog box shows the progress of the update (Figure 5-8).
Figure 5-8. Refresh Information Dialog Box
4. Select the DTM and click Details to display additional information about
the DTM (Figure 5-9)
Figure 5-9. Details Dialog Box for a Device DTM
Table 5-1 lists the information shown in the dialog box.
Table 5-1. DTM Details
Field Description
Name Name of the selected DTM
ProgId Program and class IDs of the objects that implement the DTM
ClassId
DeviceName Name of the supported device
DtmType The type of DTM needs to be Device DTM.
Other possible types are: Communications DTM, Module
DTM, and Block Type Manager (BTM)
IconPath Location of the program icons
Languages Lists the languages supported by the DTM
Manufacturer Device manufacturer
Required Specifies the protocols needed by a downstream DTM, if any
Protocols
Table 5-1. DTM Details (Continued)
Field Description
Supported List protocols supported by individual channel objects in the
Protocols DTM
XML Snippet The XML snippet may be too long for the entire snippet to
displayed in the dialog box.
• Use the Save XML button to save the snippet to a file so
that the entire snippet can be viewed in a separate
browser window or text editor.
The button opens a Windows Save As dialog box.
5. Click the appropriate DTM and click the Select button.
The editor displays the Device Type Tag dialog box (Figure 5-10), which
shows the device manufacturer, model and version from the GSD
information in the DTM, and allows you to modify a suggested tag for the
device template. This tag is only used in the Control Editors and is not
downloaded to the control system. The tag can be changed later in the
Template Toolbox as described in “Rename the Template” on page 132.
Figure 5-10. Device Type Tag Dialog Box
6. Modify the suggested tag and click OK to return to the Field Device
Editor (Figure 5-5).
The Field Device Editor now displays the these tabs:
• General identifies the device type and GSD, and provides tools for
naming the device instances created from the template.
• Bus Settings is used to edit device communication parameters such as
minimum response delays, mode selection, and the watchdog timer.
• Data Definition displays I/O parameters and diagnostic messages
defined in the DTM. The tab enables you to change some of the
attributes of the supplied parameters, and enables you to define new
parameters and messages.
• Field Device Manager contains the universal PROFIBUS device

type manager (DTM) for online access to device instances. At the
template level, the tab is used to configure links to documents and
drawings, and to customize the user interface by adding and
modifying tab pages, setting access permissions and specifying
download lists.
• Vendor DTM contains the user interface for the associated DTM.
The DTM will provide module

definition and user parameter
selection. These radio buttons
are read-only.
Figure 5-11. General Tab After Association of a Vendor DTM
Template Already Associated with a GSD

This section describes association of a DTM with a template that is already
bound to a GSD file.
To associate the manufacturer’s DTM with the device template:
not already open in the Field Device Editor, and click the General tab.
Field Device Editor displays the General, Bus Settings, Modules, Data
Definition and Field Device Manager tabs (as shown in Figure 5-5 on
page 108), and GSD is selected for the Use Module Definition from
option.
2. Click Associate DTM to open the Vendor Device Type Selection dialog
box (Figure 5-7).
3. Review the listed DTMs and select the appropriate DTM as described on
page 111 through page 113.
When you click the Select button, Field Device Editor displays a dialog
box comparing the identification data from the DTM with that in the
already associated GSD file (Figure 5-12).
Figure 5-12. Comparison of GSD Identification Information Dialog Box
4. Click Save New GSD File to open a Windows Save As dialog box and
save the GSD information from the DTM to a separate file.
5. Click Associate DTM to associate the template with the DTM and return
to the Field Device Editor (Figure 5-13).
The Vendor DTM tab is added to the Field Device Editor, but the Modules
tab remains, as the associated GSD file is still the selected method for
configuring modules and user parameters.
The Modules tab still provides

module definition and user
parameter selection. The DTM
radio button is active.
Figure 5-13. Modules and Vendor DTM Tabs
The Associate GSD button in the Object Information group remains

active, enabling you to change the GSD information in template.
Note Updating the GSD Information in the template is not intended to

change the basic characteristics of a device. It only allows changes that are
needed to connect a PA device to the PROFIBUS network.
If device parameter changes, such as module definitions, are made in the
template, it will cascade these changes to the instance definitions. It is
good practice to use the templates for the standard configuration of
network-related parameters.
The DTM radio button to the right of Use Module Definition from is
now enabled, giving you the option of using the device manufacturer’s
DTM for module and user parameter selection, as described in the
“Switching to DTM-Based Module Definition” on page 120.
Note Once you select DTM for Module Definition, you cannot select
back to GSD again, that is, using the Modules tab.
6. Set the device parameters using the selected tools.
changes to the device template and check in the template.
box is presented.
Running FDT v1.2.x and v2.0 DTMs in Separate

Processes from ArchestrA IDE
In FDM 4.0 and later, you can run Field Device Tool (FDT) v1.2.x and v2.0
DTMs independently from ArchestrA IDE if desired. This functionality can be
enabled or disabled as needed.
Running the DTM as a separate process from the ArchestrA IDE may cause a
reduction in performance due to the need of inter-process communication.
Running the DTMs as a separate process from the ArchestrA IDE will provide
additional protection to the system from detected issues with third party
DTMs.
Enabling FDT v1.2.x and v2.0 DTMs To Run in

Separate Processes from ArchestrA IDE
Proceed as follows:
1. From the ArchestrA IDE main menu, select Tools > User Preferences to
open the User Preferences dialog box, shown in Figure 5-14.
2. To enable FDT v1.2.x DTMs to run in separate processes from ArchestrA
IDE, check the Run FDT 1.2.x DTMs in a separate process check box.
To enable FDT v2.0 DTMs to run in separate processes from ArchestrA
IDE, check the Run FDT 2.0 DTMs in a separate process check box.
Note By default, the Run FDT 1.2.x DTMs in a separate process checkbox
will be checked, and Run FDT 2.0 DTMs in a separate process option
checkbox will be unchecked on the workstation as shown in Figure 5-14.
Figure 5-14. User Preferences for Field Device Manager - Enabling

DTMs in a Separate Process
3. If you selected the Run FDT 1.2.x DTMs in a separate process check
box, the Run FDT 1.2.x DTMs in a separate process dialog box appears.
Click OK to close it.
Figure 5-15. Run FDT 1.2.x DTMs in a separate process Dialog Box -
Enabling
If you selected the Run FDT 2.0 DTMs in a separate process check box,
the Run FDT 2.0 DTMs in a separate process dialog box appears. Click
OK to close it.
Figure 5-16. Run FDT 2.0 DTMs in a separate process Dialog Box -
Enabling
4. In the User Preferences dialog box, click OK.

5. To apply this change, close ArchestrA IDE, and then re-open it.
Disabling FDT v1.2.x and v2.0 DTMs To Run in

Separate Processes from ArchestrA IDE
Proceed as follows:
1. From the ArchestrA IDE main menu, select Tools > User Preferences to
open the User Preferences dialog box, shown in Figure 5-14.
2. To disable FDT v1.2.x DTMs from running in separate processes from
ArchestrA IDE, uncheck the Run FDT 1.2.x DTMs in a separate
process check box.
To disable FDT v2.0 DTMs from running in separate processes from
ArchestrA IDE, uncheck the Run FDT 2.0 DTMs in a separate process
check box.
3. If you deselected the Run FDT 1.2.x DTMs in a separate process check
box, the Run FDT 1.2.x DTMs in a separate process dialog box appears.
Figure 5-17. Run FDT 1.2.x DTMs in a separate process Dialog Box -
Disabling
If you deselected the Run FDT 2.0 DTMs in a separate process check
box, the Run FDT 2.0 DTMs in a separate process dialog box appears.
Figure 5-18. Run FDT 2.0 DTMs in a separate process Dialog Box -
Disabling
4. In the User Preferences dialog box, click OK.

5. To apply this change, close ArchestrA IDE, and then re-open it.
Switching to DTM-Based Module Definition

After you associate a device manufacturer’s DTM with a device template that
was already associated with a GSD file, Field Device Editor provides the
option of using the DTM for module configuration rather than using the
Modules tab in the Field Device Editor.
Note Once you choose the DTM for module definition, you cannot go back to
using the GSD-based tools in the Modules tab.
The choice is made in the base derived template only, and the change is
inherited by the templates and instances derived from the base derived
template. The Use Module Definition From radio buttons are visible, but not
active, in the device instances and derived templates to indicate which module
definition tools are being used.
To go to the DTM for module definition:
1. Double-click the template in the Template Toolbox if the object is not
already opened in the Field Device Editor, and click the Vendor DTM tab.
The Compare button is displayed in the upper left corner of the tab when
the GSD is selected for the Use Module Definition From option.
2. Click Compare to display the Compare Configuration dialog box
(Figure 5-19)
The Device Config data tab in the dialog box compares the currently
configured modules with the default configuration in the vendor DTM.
The grey fill color indicates where there are differences between the two
sources.
Figure 5-19. Comparing Configuration Data
3. Click the radio button for Binary, Hexadecimal or Decimal to select the
display format.
4. Click the User Parameters Data tab to view a similar comparison for
user parameter configuration.
5. Click Close to return to Field Device Editor, and then click in the
Field Device Editor title bar to close the editor, save changes to the device
template, and check the template in.
6. Perform these steps for each device instance derived from the template
that you have deployed and that is working successfully:
a. Double-click the device in the Network view to open it in the Field
Device Editor and click the Vendor DTM tab.
b. Click the Compare button to identify differences between the GSD-
based configuration and the configuration contained in the DTM.
c. Use the Vendor DTM to change the module and user parameter
selections to match the GSD-based configuration.
d. Check the Compare Configuration dialog box to verify that the
configurations match (Figure 5-20).
Figure 5-20. DTM-based Configuration Matches GSD-based

Configuration
e. Click in the Field Device Editor title bar to close the editor, save
changes to the device and check the instance in.
Note After the transition, the old configuration of the modules and
parameters is deleted in the derived templates and instances, and is
replaced by the instance-specific vendor DTM configuration in each

derived object.
7. Re-open to the base derived template in Field Device Editor.

8. Click the DTM radio to the right of Use Module Definition from to select
modules and configure user parameters using the device manufacturer’s
user interface.
Field Device Editor displays a system message that the module and
parameter selections made in the Modules tab are deleted from the
template, and from the templates and instances derived from this base
derived template (Figure 5-21).
• Click Continue to clear the configuration and start over with the new
editor.
• Click Cancel to maintain the existing configuration.
Figure 5-21. Switching to DTM-Based Module Definition Confirmation

Message
changes to the device template and check the template in.
box is presented.
Changing GSD Information

Sometimes it is necessary to replace the delivered GSD file with a different
one. At other times, it may be necessary to modify the GSD information for a
certain installation or device. For example, when a PA device is used with a
Pepperl + Fuchs SK2 or SK3 segment coupler, changes to the supported baud
rates in GSD file are needed to allow transparent configuration.
In the first case, you can use the Associate GSD button in the Object
Information Group on the General tab to import the new GSD file.
In the second case, you can click the Export GSD button in the Object
Information Group on the General tab to save the current GSD information to a
separate file, edit the file, and then import the revised GSD file into the
template using the Associate GSD button.
Note Field Device Editor does not allow association of the new GSD file if
the file does not contain the modules that are defined in the already associated
GSD file. The association of a new GSD file does not support GSD file
changes that would change the basic characteristics of a device.
To edit the GSD information in a device template:

not already open in the Field Device Editor, and then click the General
tab.
2. Click Export GSD to open the Export GSD File dialog box, specify a file
name (but not extension) and location, and click Save (Figure 5-22).
Figure 5-22. Exporting GSD Information to a File
3. Open the saved export file in a text editor such as Notepad or Wordpad,
and edit and save the file.
4. Click the General tab in the Field Device Editor, click Associate GSD to
open the Select GSD File dialog box (Figure 5-3 on page 106), use the
dialog box to browse for and select the modified file, and click Open.
Field Device Editor parses the GSD file and verifies that the GSD file can
be used by the editor. If the validation is not successful, the import is not
performed and a system message identifies the parsing error detected.
A dialog box (Figure 5-23) displays the identification information of both
GSD files, including vendor, device model, PROFIBUS ID number,
device revision and GSD revision. The dialog box prompts you to replace
the existing GSD file with the new GSD file, or cancel the action to
maintain the existing GSD information.
Figure 5-23. Comparing GSD Files
5. Review the comparison and click Replace GSD file to proceed with the
import (or click Cancel to maintain the existing GSD information).
The editor checks for conflicts between the updated GSD and the existing
configuration, and lists them in the final dialog box (Figure 5-24).
Note Field Device Editor does not allow association of the new GSD file if
the file does not contain the modules that are defined in the already associated
GSD file.
Figure 5-24. Dialog Box Identifying Conflicts
6. Perform one of these steps after reviewing the message confirming the
conflict:
• Click Back to return to the identification comparison (Figure 5-23).

• Click Finish to clear the GSD information from the template, and
bind the new GSD file to the template and its derived instances.
The Finish button is disabled (Figure 5-24) if the new file does not
contain the entire set of modules that are defined in the already
associated GSD file.
• Click Cancel to stop the process and maintain the existing GSD
information.
Editing a Device Template: General Tab

Field Device Editor can be used for most device configuration tasks both at the
template level and device level. The common configuration tasks are covered
in Chapter 7, “Configuring Devices” and Chapter 8, “Field Device Manager”.
This section describes the tasks done at the template level.
To edit a device template:
• Double-click the template in the Template Toolbox to open it in the Field
Device Editor.
The editor opens to the General tab (Figure 5-25).
The General tab is divided into three groups: Object Information, GSD
Information, and Device Instances.
Figure 5-25. General Tab for a Device Template
Object Information
The Object Information group provides a read-only display of the template
name and its defining template ($Profibus in the case of a base derived
template).
The three buttons below these field are used for binding GSD information to
the template:
Associate GSD Imports a GSD file into the device template.
Associate DTM Associates the template with a DTM specifically
designed for the device.
Export GSD Stores the current GSD information to a separate file.
The file can be edited and then imported into the same or
a different template.
These buttons are not displayed for derived templates and device instances.
The Use Module Definition From radio buttons indicate which editor is being
used for module and user parameter selection:
• GSD when modules and user parameters are configured in the Modules
tab using the general purpose DPV0 editor and the GSD file.
• DTM when modules and user parameters are defined using the device
manufacturer’s user interface, which is opened in the Vendor DTM tab.
See “Switching to DTM-Based Module Definition” on page 120 for
information about changing the module definition method.
GSD Information
GSD Information is a read-only display of model and version information
extracted from the GSD file or the DTM.
• Click in the group title bar to hide the GSD Information fields.
• Click in the title bar to display all the GSD Information fields.
Device Instances
The Device Instances group provides tools for specifying the default names for
instances derived from the template. When an instance is created, the Control
Editors append an incremental number to the string specified in Mask Prefix to
create the name for the instance. DEV is the default prefix.
In addition to providing a unique tag for the device within the Control Editors,
the mask and number supply a default value for the Name (NAME), the Device
Identifier (DEV_ID) and Device Name (DVNAME) parameters in the device
equipment control block (ECB201), which is downloaded to the control
processor during device deployment. These names are not used in the device
itself.
To specify instance naming:
1. Enter a base name in Mask Prefix.
The prefix can be 1 to 9 characters long and consist of letters, numbers and
the _ character. The name needs to include at least one letter. Use _ instead
of spaces.
2. Use the pull-down list in Number of Digits to specify the length of the
number that will be added to the prefix.
The range of number of digits is between 3 and t 12,minus the number of
characters in Mask Prefix.
Mask Preview shows the name of the next instance (ADI001 in
Figure 5-25 on page 128) to be derived from this template. If the name
already exists in the Galaxy, the Control Editors use the next available
number in the range.
3. Click the other tabs in the Field Device Editor to set the device attributes
at the template level.
changes to the device template and check the template in.
Managing Device Templates

Once a template has been derived and bound to a GSD, you can take any of
these actions in the Template Toolbox to use and manage the template.
Move the Template to Another Toolset Folder

You can drag the template to any other location in the Template Toolbox. See
“Setting Up a Project Folder” on page 104 for information on creating custom
folders.
Derive New Templates

To derive a new template from a base derived template:
1. Right-click the template and choose New > Derived Template from the
context menu.
The new template is displayed under the parent template. Its tag consists
of the name of the parent template plus a numeric suffix such as _001 or
_002.
2. Press Enter to accept the default name, or type a new tag and press Enter.
The tag needs to be unique within the Galaxy. Use any combination of
letters, numbers, and the # and _ characters. The tag needs to include at
least one letter and be at least two characters long. The length of the tag is
up to 32 characters not including the $. Use _ for spaces. Do not type $ as
this prefix is automatically added to the templates.
The derived template copies the configuration settings from the parent
template.
3. Double-click the new template to open it in the Field Device Editor.
Figure 5-26 shows the template $SRD991_001, which was derived from
$SRD991, opened in the editor. There is no Associate GSD or Associate
DTM button as that choice was made in the defining template and the
derived template is bound to the same GSD data as $SRD911. The Use
Module Definition from radio buttons are read-only.
Figure 5-26. Derived Template Opened in the Field Device Editor
4. Set application-specific values in the template, and then click in the

title bar to close the editor, save changes to the device template and check
the template in.
Create Instances
Do any of these to create instances of a template from the Template Toolbox:
• Right-click the template and choose New > Instance from the context
menu to place the new instance in the Unassigned Hardware folder in the
Network view.
• Drag the template to Network view and drop it on a port (to add the device
to that port) or the host FBM (to add it to the FBM’s Port 1).
• Drag the template to Network view and drop it on any empty space to add
an instance to the Unassigned Hardware folder for later assignment.
Refer to “Adding Slave Devices to an FBM” on page 140 for additional
information on creating and assigning devices.
Rename the Template

To rename the template:
1. Right-click the template and choose Rename from the context menu to
make the tagname editable.
2. Type over the name and press Enter.
The name needs to be unique within the Galaxy. Use any combination of
letters, numbers, and the # and _ characters. The tag needs to include at
least one letter and be at least two characters long. The length of the tag is
up to 32 characters not including the $. Use _ instead of spaces. Do not
type $ as this prefix is automatically added to the templates.
Delete Templates
A template can be deleted if it is checked in and there are no other objects
derived from it.
To delete templates:
1. Click the first template to be deleted, and then press Ctrl as you click
additional templates.
2. Perform one of these steps:
• Right-click the selection and choose Delete from the context menu.
• Press Delete.
Note The Delete dialog box indicates which templates can be deleted. In
Figure 5-27 for example, the base derived templates $Acr_12DI and $SRD991
cannot be deleted as other templates and instances have been derived from
them. However, $PF_FD0_VC#1_2 can be deleted as it has no derived
children.
3. Click Yes to remove the items that can be deleted; click No to cancel the
entire action.
Figure 5-27. Delete Dialog Box
Export the Template

You can export PROFIBUS device templates to another Galaxy, including one
in an instrument shop system, if the PROFIBUS Support package is installed
on the Galaxy’s server and clients.
To export templates for use in another Galaxy:
1. Click the first template to be exported, and then press Ctrl as you click
additional templates.
2. Right-click the selection and choose Export > Export Automation
Objects (Figure 5-28) from the context menu to open the Export
Automation Objects dialog box.
Figure 5-28. Exporting Device Templates
In Figure 5-28, two templates are being exported:

• $SIEMENS_PA_Linker is a base derived template.
• The template $SRD911_001 was derived from $SRD911.
The export file automatically includes the templates from which these
devices types were derived, including the base template $Profibus.
3. Specify a file name and destination folder in the dialog box, and click
Save (Figure 5-28).
Figure 5-29. Export Automation Objects Dialog Box
The dialog box shows the progress of the export and lists any detected
errors (Figure 5-30). The detected errors are also displayed in the Output
view.
• Choose View > Output View from the IDE main menu if the Output
view is not already shown.
Figure 5-30. Export Complete
Note In Figure 5-30 four objects were exported: the two selected objects and
their defining templates ($SRD991 and $Profibus).
4. Click Close when the Export Automation Objects dialog box indicates
that the objects have been exported.
5. Go to the Galaxy where the templates are re-used.
6. Choose Galaxy > Import > Automation Objects from the IDE main
menu, select the export file (SIEMENS_PA_LINKER.aqPKG in the
example) in the Import dialog box, and click Open.
7. Specify in the Import Preference dialog box (Figure 5-31) how you want
the Control Editors to handle version and name conflicts.
The Control Editors will not import an object that has the same name and
type as an object already in the Galaxy. The Object Name Conflict group
deals with objects that have the same name but not the same type.
Figure 5-31. Import Preferences Dialog Box
8. Click OK to start the import.

The dialog box shows the progress of the import and lists any detected
errors (Figure 5-32). The detected errors are also displayed in the Output
view.
Figure 5-32. Import Complete
Note InFigure 5-32, Control Editors skipped $Profibus, as the base template
already existed in the new Galaxy database.
9. Click Close when the Import dialog box indicates that the objects have
been imported.
139
C H A P T E R 6
Defining the Network
Once the host FBM222 and the slave device templates have been defined in the
Galaxy, you can begin configuring the PROFIBUS network by adding
instances of the device templates to either or both ports on the FBM222.
The devices are displayed in the Control Editors’ Network view under the
assigned port or in the Unassigned Host folder. A device can be renamed, re-
assigned or deleted as necessary using the device’s context menu in the
Network view.
Double-click the device in the Network view to open it in the Field Device
Editor to perform these configuration tasks:
• Set the device PROFIBUS network address and enter optional device
information such as part number and serial number, as described in this
chapter. This configuration work is only done at the device level.
The other configuration tasks can be performed in the defining template or
the device instance. These actions are described in Chapter 7,
“Configuring Devices” and Chapter 8, “Field Device Manager”.
• Edit bus settings, and then open the host FBM222 in the Field Device
Editor to validate the master bus settings for each port given the devices
that have been added to it. See “Editing Device Bus Settings” on
page 175.
• Select modules, configure user parameters, and define I/O points. This
work is accomplished either with the Modules and Data Definition tabs in
the Field Device Editor or with the device manufacturer’s user interface in
the Vendor DTM tab. See “Selecting Device Modules” on page 177.
• Select parameters, add graphics and documents links, create new tabs and
otherwise customize displays in the Field Device Manager for later online
monitoring and diagnostics. See “Field Device Manager” on page 217.
When you add a device to the Galaxy database, the Control Editors create an
equipment control block (ECB201), which identifies the device within the
Control Core Services software. The ECB needs to be deployed to the Control
Core Services control processor before device data can be read from and
written to the control scheme. This chapter also covers editing and deployment
of the ECB.
The Control Editors Devices application view organizes the slave devices in
user-defined folders called Plant Units that represent areas, processes or other
plant-specific categories. The optional Devices view is described at the end of
this chapter.
140 6. Defining the Network
Contents
• Adding Slave Devices to an FBM
• Importing an FBM223 Device Configuration
• Modifying a Device Configuration
• Editing Device ECBs
• Commissioning Devices
• Updating Deployed Devices
• Exporting Device Configurations
• Organizing Devices by Plant Units
Adding Slave Devices to an FBM

There are multiple ways in the Control Editors to create a device, as described
in greater detail in Hardware Configuration User’s Guide (B0750BB). These
methods add a device to the Unassigned Hardware folder in the Network
view:
• Choose New > Instance from the context menu of a device template in the
Template Toolbox or the Derivation view.
• Drag the template from the Template Toolbox or the Derivation view and
drop it in the Devices view.
• Drag the template from the Template Toolbox or the Derivation view and
drop it in an open area in the Network view.
The device needs to be assigned to a specific port on an FBM222 in the
Network view. See “Assigning Devices” on page 153.
You can also create and assign devices in one step by using one of the two
methods illustrated in this chapter.
Automatic Address Assignment

Before adding the slave devices, consider whether you want to use the
automatic address assignment option in the Control Editors. When the option is
selected, the Control Editors fill in the device address (DVOPTS parameter in
the device ECB) with the next available address on the selected port starting
with a user-specified base number.
The automatic address assignment supplies a default address for the device; the
address can be changed using the Field Device Editor to match the actual
address to be used on the network.
This feature may not be that helpful if many of the devices on the proposed
network needs a fixed address, or the addresses have already been set
according to an instrument list. See “Device Addresses” on page 23 for
information on setting device addresses.
6. Defining the Network 141
To enable automatic address assignment:

1. Choose Tools > User Preferences from the IDE main menu to open the
User Preferences dialog box.
2. Click the Profibus tab in the dialog box (Figure 6-1) and check the box for
Automatic Address Assignment.
Figure 6-1. Setting Automatic Address Assignment
3. Enter the first address using the Lowest Slave Address pull-down list, and
click OK to set the option and close the dialog box.
Note We recommend that the starting slave address be at least 10,

reserving the address range 0 to 9 for master stations such as the FBM222
and third-party Class 2 Master configurators.
Creating and Assigning a Single Device

To add a single device to a specific FBM222 port:
1. Expand the FBM222 in the Network view to display its ports and the
devices already assigned to them.
2. Drag a device template from the Template Toolbox or Derivation View
and drop it on the port (Figure 6-2).
The device is added to the port and named according to the prefix mask
and numbering specified in the template. The action also creates a device
equipment control block (ECB201) to represent the device in the control
database and assigns the block to the station’s ECB compound
(FCP001_ECB in the example).
Figure 6-2. Drag the Template to the Port in the Network View
Creating and Assigning Multiple Devices

Note The sequence described in this section enables the addition of multiple
devices of the same or different types in a single pass. We recommend that you
add only a few devices at a time, as shown in the example, to help ensure that
each device is correctly assigned.
To add one or more devices of the same or different type to a PROFIBUS port:
1. Expand the FBM222 in the Network view to display its PROFIBUS ports
and the devices already assigned to them.
2. Right-click the port and choose New Profibus Device from the port’s
context menu to open the Bulk Create dialog box (Figure 6-3).
Figure 6-3. Adding Multiple Devices to a Segment
The dialog box lists only templates for devices that are supported by the
FBM222.
3. Select a device template by clicking its check box.
A 1 appears in the quantity column on the right. At this point you can
increase the count and/or select other device types.
4. Specify additional devices, if necessary.
The selections in Figure 6-3 add two Wago remote I/O systems and one
Siemens DP/PA link coupler to port 1 on PROF01.
5. Click OK to close the dialog box and add the devices.
A message box advises you to wait as the devices are created and
assigned.
The devices are added to the port and named according to the prefix mask
and numbering specified in their respective templates. The action also
creates ECB201s to represent the devices in the control database and
assigns the blocks to the station’s ECB compound (FCP001_ECB in the
example).
Importing an FBM223 Device Configuration

The configurator for slave devices for the FBM223 saved the device settings to
a separate device configuration file, which was then downloaded to the
FBM223. The default name and extension for this file were the device
identification number from the GSD file and .PSL. The device files were
stored in the /usr/fox/sp/files/devices directory or d:\usr\fox\sp\files\devices
folder on the configurator’s host workstation.
Note Appendix A, “FBM223 Configurations” describes the Control Software

You can import a device file into the Field Device Editor when migrating from
the FBM223 to the FBM222 to capture the settings used with the older FBM.
To import an FBM223 device configuration:
1. Create a device template and import the same GSD file that was used in
the configuration of the device for use with the FBM223.
2. Create an instance of the template and assign it to the FBM222.
Try to use the same ECB names to minimize editing of the DCI blocks that
use slave devices.
3. Double-click the device in the Network View to open it in the Field
Device Editor, and click the Bus Settings tab.
4. Right-click anywhere in the Bus Settings tab and select Import FBM223
Configuration from the context menu (Figure 6-4).
Figure 6-4. Importing an FBM223 Device Configuration
5. Use the modified Open dialog box to browse for and select the
configuration file (usually device identifier.PSL) and click Open.
The device parameters are set as they were in the FBM223. They can now
be edited as described in “Modifying a Device Configuration” on
page 145.
Note You can also import a device configuration into a device template
by choosing Import FBM223 Configuration from the context menu in
the Bus Settings tab for the template.
When migrating slave devices from an FBM223, you need to perform these
steps:
• Remove the device ECBs from the host control processor’s ECB
compound (or other compound if the ECB was moved).
• Review the IOM_ID parameter of each DCI block that processed data
from the devices attached to the FBM223. The point number parameters
(such as PNT_NO) does not need to be changed. However, you may want
to revise them to take advantage of the extended point configuration
syntax supported by the FBM222 (“Point Configuration String Syntax” on
page 261).
Modifying a Device Configuration

The parameter values established in the device template are copied to each
device instance created from the defining template, providing a means for
consistent application of plant or project standards. However, each instance
needs to be opened in the Field Device Editor to assign a network address to
the device and to edit the device parameters to meet the requirements of the
actual application.
To modify a device configuration:
1. Double-click the slave device in the Network view to open the device in
the Field Device Editor.
The editor displays the General tab (Figure 6-5).
Click this button

to display GSD
information supplied
by the device template
Device information
can be entered here
Hyperlinks to the host

control processor and
FBM configurations,
and the device ECB
Figure 6-5. General Tab for a Device
2. Click in the GSD Information or Device Information title bar to hide

the section; click in the GSD Information or Device Information title
bar to display the information.
3. Edit the parameters in the Device Information fields.
Entering the device’s serial number, hardware revision and software
revision is optional.
Field Device Manager can read these parameters from a connected device
that supports Identification & Maintenance Profile (I&M) or PA
PROFIBUS Profile. Information in these fields is deployed to the
FBM222 and is displayed in the device’s Equipment Information display
in System Manager (see “Device Information Displays” on page 389).
4. Use the pull-down list in the Control Information group to set the network
address.
The list shows only available addresses on the port. The list excludes
addresses lower than the Lowest Slave Address set in the User
Preferences dialog box (Figure 6-1 on page 141) and addresses taken by
other slave devices on the port.
Note The address selected in Field Device Editor must match the address set
in the device itself.
The remaining fields in the Control Information group are read-only

device information and hyperlinks to related Control Editors (Table 6-1).
Table 6-1. General Tab Control Information Group
Field Description
Port FBM222 port to which the device is assigned (1 or 2), or
0 when the device is unassigned.
You can change the assignment in the Network view by
selecting a command from the device’s context menu, or
by dragging the device to another FBM222 port or the
Unassigned Hardware Folder, as described in
“Assigning Devices” on page 153.
Control Processor Name of the host control processor.
• Click this hyperlink to open the CP in the Hardware
Editor.
The IO Assignment tab in the Hardware Editor can be
used to edit connections between the device and DCI
blocks in the control strategies.
See “Making the Field Connections” on page 271 for
use of this tab and other tools in the Control Editors for
making I/O connections.
FBM Name of the host FBM222.
• Click this hyperlink to open the FBM in the Field
Device Editor to check the master bus setting
configured for the FBM.
See “Setting Bus Parameters” on page 67 for
information on using the Bus Settings tab for the FBM.
Table 6-1. General Tab Control Information Group (Continued)
Field Description
ECB201 Path name of the device ECB. The containing
compound is usually the control processor’s ECB
compound (FCP001_ECB in Figure 6-5).
• Click this link to open the compound in the Block
Configurator, where the device ECB can be located
and edited on the ECBs tab.
See “Editing Device ECBs” on page 148 for
information editing the device ECB.
Plant Unit Plant Unit where you can find this device.
Slave devices may be associated with a user-defined
plant unit in the Control Editors Devices view to
organize devices by plant-specific information.
See “Organizing Devices by Plant Units” on page 165
for information on setting up and using plant units.
The next steps are to review and modify the device configuration as described
in “Configuring Devices” on page 171 and to customize the Field Device
Manager tab displays for the device, as described in “Field Device Manager”
on page 217.
When you have completed configuration of the device:
• Click in the Field Device Editor title bar to close the editor, save
changes to the slave device and check the device in.
Editing Device ECBs

When you add a slave device to the Galaxy, the Control Editors create an
ECB201 to represent the device in the Control Core Services control database.
When the host FBM is assigned to a control processor, the Control Editors
assign the newly created device ECB to the control processor’s ECB
compound (FCP001_ECB in Figure 6-6, for example). The device ECB can
be assigned to the control compound that contains the DCI blocks that
reference the device (“Creating the Control Compound and Strategy” on
page 268).
Figure 6-6. ECB Compound in the Deployment View
Reviewing Device Properties

When a device is added to the FBM222, the ECB201 is fully configured and
ready for use. However, you need to review ECB parameters using the Control
Software Block Configurator.
To review and modify the configuration of a device ECB:
1. Right-click the device in the Network view and choose Open Related
ECB from the context menu.
The Control Editors open the containing compound in the Block
Configurator, switches to the ECBs tab, and selects the device ECB in the
table on the left side of the tab (Figure 6-7).
You can also open the containing compound in the Block Configurator by
performing one of these steps:
• Double-click the device in the Control Editors Network view (if it is
not already open in the Field Device Editor) and click the ECB 201
hyperlink on the General tab (Figure 6-5).
• Expand the host control processor in the Deployment view to display
its compounds and double-click the containing compound
(FCP001_ECB in Figure 6-6).
When the device ECB is selected on the left side of the ECBs tab (RIO002
in Figure 6-7), its properties are displayed in the editor to the right.
Figure 6-7. Editing a Device ECB, General Tab
The General tab displays read-only block information and editable fields
including Block Description and the sampling parameters.
Block Sample Time (PERIOD parameter) and Block Phase Number
(PHASE) need to be the same as those for the parent ECB200/202 (that is,
the ECB for the host FBM222). See “Setting ECB200/202 Parameters” on
page 77.
2. Click the FBM tab and review the parameters on that tab (Figure 6-8).
Figure 6-8. Editing a Device ECB, FBM Tab
Table 6-2 describes the parameters on the FBM tab.
Table 6-2. FBM Tab Parameters
Device The Device Identifier (DEV_ID) parameter specifies how the device is identified in
Identifier system management displays and block detail displays. DEV_ID is an alphanumeric
string up to six characters long. Initially, the name is the first six characters of the
device tag supplied by the device template (see “Editing a Device Template: General
Tab” on page 127 for information on specifying device instance names).
If this truncation would result in duplicate device identifiers, you can change the
parameter value so that the device is clearly identified in the system management
displays. The displays are described in “System Management” on page 361.
Table 6-2. FBM Tab Parameters (Continued)
Hardware These fields display read-only information based on the ECB for the parent
Type FBM222. Both types should be 222.
Software
Type
Port Number Port number is a read-only field that identifies the FBM222 port to which this device
has been assigned. The port can be changed in the Network view using the device’s
context menu or a drag-and-drop move. See “Assigning Devices” on page 153.
The File Identifier field is not used by devices attached to an FBM222.
Parent ECB This read-only field shows the entire path name of the ECB200 or ECB202 of the
host FBM222.
Device Leave the Device Address (DVADDR) parameter blank. When the device goes
Address online, the FBM222 reads the actual network address from the device and displays
the address in this field, allowing you to verify that the actual address matches the
configured address shown in Device Options.
Device Name The device name (DVNAME) parameter is the name of the device ECB; it is used to
address the device in the control software. Initially, the name is copied from the IDE
device tag, which is created from the naming scheme in the device template.
When a device is unassigned, you can change the IDE tag by right-clicking the
device in the Network view and choosing Rename from the context menu. The new
name is copied to the DVNAME parameter when the device is assigned to an
FBM222 port.
After the device is assigned to an FBM222 port, you can change the Device Name
by right-clicking the device in the Network view and choosing Rename Contained
Name from the context menu. The action changes the ECB DVNAME and NAME
parameters to match the contained name. It does not change the IDE tag, which is
displayed in the title bar when the device is opened in Field Device Editor.
Device The Device Options (DVOPTS) parameter holds the address of the device on the
Options PROFIBUS port, as specified in the Field Device Editor General tab. The address
may have been automatically assigned by the Field Device Editor or imported from
an FBM223 device configuration.
This is a read-only field. The device’s address can be edited in the Field Device
Editor General tab to help ensure that the configuration agrees with the address set in
the physical device.
Device Type Device type (DEVTYP) is a configurable 32-character parameter used to describe
the device in system management displays and block detail displays.
The Software File ID, Manufacturer Identifier, Version Number and Error Alarm Option parameters
are not used with PROFIBUS slave devices. Leave these fields blank.
3. Review and, if necessary, modify the settings on the History and Security
tabs.
Refer to Block Configurator User’s Guide (B0750AH) for additional
information on configuring ECBs and ECB compounds.
4. Click in the Block Configurator title bar to save the changes, close
the editor, and check the ECB and containing compound in.
Assigning Devices
When device instances are created, they are assigned to a specific FBM222
port, or to the Unassigned Hardware folder in the Network view. Each device
can be re-assigned with a selection from the device’s context menu in the
Network or Devices view, or with a drag-and-drop move.
To assign a device to a port using the device context menu:
1. Right-click the device in the Network view and choose Assign To from
the context menu to open the Assign To dialog box (Figure 6-9).
Figure 6-9. Assign To Dialog Box
2. Use the pull-down list in the Scope field to narrow the list of available
FBMs as follows:
• Select the blank space at the top of the menu for the FBMs in the
Galaxy, including unassigned FBMs.
• Select All Controllers (the selection in Figure 6-9) for the FBMs that
are currently assigned to a control processor.
• Select a controller to choose from its assigned FBMs.
3. Pull down the list in the Assign To field and choose an FBM within the
selected scope.
The FBMs are identified using this format:
IDE Tag [Contained name, that is, letterbug] (Equipment template)
4. Choose a port from the pull-down list (Port 1 in Figure 6-10), select the
address from the Address pull-down list, and click Assign.
Figure 6-10. Selecting a PROFIBUS Port
To assign a device using drag-and-drop:

1. Expand the display of the new host FBM222 to show its PROFIBUS
network ports and the attached devices.
2. Select the device to be moved, drag it to the new FBM and drop it on the
desired port.
If you drop the device on the FBM itself, the device is assigned to Port 1.
Perform one of these steps to move a PROFIBUS device to the Unassigned
Hardware folder:
• Right-click the device in the Network view and choose Unassign from the
context menu.
• Drag the device from its current location in the Network view and drop it
on the Unassigned Hardware node at the top of the Network view.
Commissioning Devices
When a slave device is installed on the network and is otherwise ready to be
placed into service, you can use the Commissioning Wizard to perform one or
more of these actions:
• Change the Address of a connected device if the address of the connected
device does not match the configured address in the Galaxy and if the
device supports remote address changes.
• Deploy the Device, that is, download the device ECB to the control
processor and the FBM. The ECB needs to be downloaded before the
device can be used in the control scheme.
You can also deploy the device by including the device in a deployment of
the FBM or the host control processor, as described in “Deploying the
FBM” on page 81.
• Download Vendor DTM Data, downloading configuration data from an
associated vendor DTM to a DPV1 device.
The Commissioning Wizard can download DTM data for a non-gateway
DTM and a root gateway DTM, but not to a device configured under a
gateway DTM.
• Download a child DTM by opening the DTM in the Vendor DTM tab
and selecting the download function from the DTM’s context menu.
If you did not use a DTM to configure the device, you can download the
configuration data using Field Device Manager. See “Device Parameter
(DPV1) Tab” on page 238.
• Upload Vendor DTM Data, aligning the configuration data in the
associated vendor DTM and the Galaxy with the configuration data in the
connected DPV1 device.
The Commissioning Wizard can upload configuration data from a non-
gateway DTM and a root gateway DTM, but not from a device configured
under a gateway DTM.
• Upload configuration data from a child DTM by opening the DTM in
the Vendor DTM tab and choosing the upload function from the
DTM’s context menu.
If you did not use a DTM to configure the device, you can upload the
configuration data to the Galaxy using Field Device Manager. See “Device
Parameter (DPV1) Tab” on page 238.
• Enable Communications to bring the device online to the control system
and start cyclic data exchange between the FBM and the device.
You can also enable (and disable) communications by selecting the
equipment change action in System Manager, as described in “Device
Equipment Change Actions” on page 397.
Before commissioning devices, you may want to set two Commissioning
Wizard defaults:
• Deploy Device to have this option selected by default if the device has not
already been deployed
• Enable Communications to have this option selected by default if the
device is not already online.
To set the Commissioning Wizard preferences:
1. Choose Tools > User Preferences from the IDE main menu and click the
Profibus Commissioning tab in the User Preferences dialog box
(Figure 6-11).
Figure 6-11. Setting Commissioning Preferences
2. Click either or both checkboxes to set the default selections.

3. Set preferences in the other two tabs if necessary, and then click OK to
apply the changes and close the dialog box (or click Cancel to close the
dialog box without changing any user preferences).
You can change the preferences at any time.
To place a PROFIBUS slave device in service:
1. Verify that the device is installed on the correct FBM222 port and that the
FBM is online.
See “Live Lists” on page 94 for information on checking FBM
communications with devices on each port.
2. Right-click the device in the Network or Devices view and choose

Commission Device from the context menu to start Commissioning
Wizard.
The Configured Device/GSD Information at the top of the wizard shows
configured network address and other information from the General tab in
Field Device Editor (Figure 6-12).
3. Wait while the Commissioning Wizard builds a live list of the FBM222
port and selects a connected device with the same address and same
PROFIBUS ID number.
The wizard displays the address and PROFIBUS ID of that device in the
Matching Devices pane.
Figure 6-12. Commissioning Wizard Showing Matching Device
If a match is not found, the wizard identifies the devices connected to the
port that:
• Have the same PROFIBUS ID
• Have addresses that are not configured in the Galaxy for this port
• Are not active, that is, they are not involved in cyclic data exchange.
It then displays the device with lowest address among these near matches.
If no near match is found, the wizard displays the devices that are
connected to port, that are not active and that have an address that is not
configured in the Galaxy.
4. Select the matching device and click Get Device Details to display
additional information that has been uploaded from the device.
Table 6-3 describes the information available in the Matching Devices
pane.
Table 6-3. Matching Device Details
Field Description
Address Address of the connected device on the FBM222 port
Ident No PROFIBUS ID number of the connected device
State • The status of the device can be: : Connected: The
device address is not configured in the Galaxy for
this port. The device is inactive, that is, not involved
in data exchange.
• Configured: The device address is configured in
the Galaxy for this port. The device is inactive, that
is, not involved in data exchange.
• Active: The device is connected, configured and in
cyclic data exchange with the FBM222
Vendor Manufacturer and model names are displayed if they are
Model mapped in the DeviceList.xml file
Order ID Read from connected PA and I&M devices, if the

Software Revision information is available in the devices. Blank for the
other devices.
Hardware Revision
This information is only displayed for the selected
Serial Number
device when you click Get Device Details.
If you select a device with an unconfigured address, the wizard changes

the address to that shown in Configure Device/GSD Information pane if
the device supports remote address change. Otherwise, you need to
manually change the address on the device itself (see “Device Addresses”
on page 23).
• Click Refresh after manually changing an address to have the wizard
build a new live list and select the matching device.
• Click Cancel to exit wizard without making any changes.
5. Click the Show All Devices button at the bottom of the wizard to list the
network address and PROFIBUS ID of the devices on the port.
The button label changes to Show Matching Device (Figure 6-12).
Figure 6-13. Commissioning Wizard Lists All Devices on the Port
6. Select the matching device or a device in the Show All Devices list, and
click Next to choose commissioning actions on the next wizard page
(Figure 7).
Figure 6-14. Selecting Commissioning Actions, Warning Dialog Box
7. Click the appropriate checkboxes in Commissioning Actions to choose

the options for this device.
In Figure 6-14 the user has selected Deploy Device and Enable
Communications, the two options available for this device configured in
Field Device Editor with an associated GSD file.
8. Click Start and then click Yes in the Warning dialog box (above the Finish
and Start buttons in Figure 6-14).
If you are tracking changes to the control database using the Control
Editors’ link to FoxCTS software, the Change Tracking dialog box
prompts you to enter a reason for the download (Figure 6-15). The Control
Editors do not proceed with the commissioning actions until you make an
entry in the dialog box. See Chapter 12, “Change Tracking” for details.
Figure 6-15. Reason Dialog Box for DTM Audit Trail Events
• Enter a reason in the dialog box and click OK.

When the wizard continues, the green progress bar and messages in the
pane in the lower portion of the wizard show the progress of the
commissioning actions (Figure 6-16). Detected error messages, if any, are
displayed in this pane and in the Output view.
The wizard starts with a remote address change if the target device has an
unconfigured address, and then executes the selected options in their left-
to-right order in the Commissioning Actions pane.
• Click Stop to stop the current action (if possible) and cancel
execution of the remaining actions.
If wizard cannot execute an action, the next steps are not executed, at
which point you can:
• Click Cancel to close the wizard without any further action.
• Click Back to return to the first wizard page to change the target
device and/or commissioning actions.
Figure 6-16. Commissioning Wizard Shows Completed Actions
9. Click Finish when the wizard indicates that commissioning actions have
been completed successfully (Figure 6-16).
Updating Deployed Devices

If you modify a device in the Control Editors (using either the Field Device
Editor or the Block Configurator) after the device has been deployed, you need
to redeploy the device ECB to implement the change.
Note Redeployment of a device may cause a bump in communications with

the device and possibly in the control scheme associated with the associated
device. You need to make such dynamic deployments only in non-mission
critical systems.
Note 1) Selective Upload/Download in the Control Editors’ Deployment

Utilities does not support selective upload of the port settings (to the FDATA1
through FDATA4 parameters) from a PROFIBUS device or its host FBM222.
2) The dialog box does support selective downloads of the FDATA1 through
FDATA4 parameters to PROFIBUS device and the host FBM. The FDATA1
through FDATA4 parameters contain the PROFIBUS configuration data.
3) These parameters cannot be seen as separate parameters. Deploy all of the
parameters to help ensure a consistent and valid PROFIBUS configuration.
To redeploy the device ECB:

1. Verify that the device is checked in.
2. Right-click the ECB compound that contains the device ECB, and choose
Deploy from the context menu.
3. Use the Deploy dialog to select the device ECB and prepare it for
deployment.
4. Click Deploy when the Object Preparation Result pane indicates the
object can be deployed.
If you are tracking changes to the control database using the Control
Editors link to FoxCTS software, the Change Tracking dialog box prompts
you to enter a reason for the deployment (Figure 6-15 on page 160). The
Control Editors do not proceed with the deployment until you make an
entry in the dialog box. See Chapter 12, “Change Tracking” for details.
Exporting Device Configurations

Use the Export Automation Objects function in IDE to export a device
configuration to another Galaxy. The export file automatically contains the
device’s defining template. The export also contains information about the I/O
connections to DCI blocks. During import of a device instance, the I/O
connections to DCI blocks are restored wherever possible. If the DCI block has
been assigned to another device or FBM, the value is not touched.
You can export PROFIBUS devices to any Galaxy, including one in an
instrument shop system, if the PROFIBUS Support package is installed on the
Galaxy’s server and clients.
To export device configurations:
1. Expand the Galaxy name in the Network view or Devices view to display
the devices to be exported, click the first one and then press Ctrl as you
click additional devices for the export.
2. Right-click the selection and choose Export > Automation Objects from
the context menu to open the Export Automation Objects dialog box
(Figure 6-17).
Figure 6-17. Exporting a Device Configuration
3. Use the dialog box to select a destination folder and a file name (but not a
file extension), and click Save.
The dialog box shows the progress of the export and lists detected errors
(Figure 6-18). The detected errors are also displayed in the Output view.
Figure 6-18. Export Complete
that the objects have been exported (Figure 6-18).
5. Switch to the Galaxy where the device configurations are to be re-used,

and choose Galaxy > Import > Automation Objects from the IDE main
menu to open the Import dialog box (Figure 6-19).
Figure 6-19. Selecting a File for Import
6. Use the dialog box to browse for and select the export file, and then click
Open.
7. Specify in the Import Preference dialog box (Figure 6-20) how you want
the Control Editors to handle version and name conflicts.
The Control Editors do not import an object that has the same name and
type as an object already in the Galaxy. The Object Name Conflict group
deals with objects that have the same name but not the same type.
Figure 6-20. Import Preferences Dialog Box
8. Click OK to start the import.

The dialog box shows the progress of the import and lists detected errors
(Figure 6-21). The detected errors are also displayed in the Output view.
Figure 6-21. Import Complete
Note In Figure 6-21, the Control Editors imported the devices and their
defining templates, but skipped $Profibus, as the base template already existed
in the new Galaxy.
9. Click Close when the Import dialog box indicates that the objects have
been imported.
10. Open each host control processor for the imported devices in the
Hardware Editor and click the IO Assignment tab to determine which I/O
connections to DCI blocks have been made as part of the import and
which connections need additional editing.
Organizing Devices by Plant Units

Use the Devices view to organize the slave devices in user-defined folders
called Plant Units, which can represent locations, processes or other plant-
specific categories. Plant units can be nested in other plant units to create a
hierarchy of device locations and characteristics. For example, you can have a
folder that includes the transmitters in a specific plant area, and that folder can
contain separate folders for each manufacturer, technology or role in the
process. Such a hierarchy of plant units can make it easier to locate a specific
device in a Galaxy containing hundreds of field devices of various kinds.
The field devices defined in the Galaxy, including PROFIBUS slave devices
and FOUNDATION fieldbus H1 devices, are displayed in the Devices view.
From each device’s context menu in the Devices view, you can perform many
of the functions available in the Network view, including opening the device or
its ECB in the appropriate editor, and renaming and reassigning the device.
When devices are added to the Galaxy, they are placed in the Unassociated
Devices folder at the top of the Devices view. You can then associate the
devices with a plant unit.
There is no need to use the Devices view. Plant unit information is not used in
configuration of the control database and is not deployed to the control
database.
Creating Plant Units

To add a plant unit:
1. Expand InFusion Support in the Template Toolbox to display the support
object templates.
• Right-click $Plant_Unit and choose New > Instance from the
context menu to add a top-level plant unit to the Devices View.
• Drag $Plant_Unit to the Devices View and drop it on an empty space
to create a top-level plant unit (Figure 6-22).
• Drag $Plant_Unit to the Devices View and drop it on an existing
plant unit to place the new unit under the selected node.
The new object is displayed in the Devices view with a default name such
as Plant_Unit_001, and is enclosed in a rectangle indicating that the name
can be changed now.
Top-level plant unit

Nested plant unit
Drop the plant unit template

on an open space to add a
top-level plant unit
Figure 6-22. Adding a Plant Unit
3. Press Enter to accept the default name, or type a new name and press
Enter.
The plant unit can be renamed at any time:
• Right-click the plant unit, choose Rename from the context menu,
type a new name, and press Enter.
Assigning Plant Units

Plant units can be assigned to other plant units creating a hierarchy of folders
of up to nine levels.
To assign a plant unit to another unit using the context menu:
1. Right-click plant unit in the Devices and choose Assign To from the
context menu to open the Assign To dialog box (Figure 6-9).
Figure 6-23. Assign To Dialog Box
plant units as follows:
• Select All Plant Units for the units in the Galaxy.
• Select a plant unit to choose from its assigned units.
3. Pull down the list in the Assign To field and choose a unit from within the
selected scope.
The plant units are identified using this format:
Name [IDE tag] (Plant Unit template)
4. Click Assign.
To assign a unit using drag-and-drop move:
1. Expand the display in the Devices view to display the new host plant unit.
2. Select the plant unit to be moved and drag it to the new location.
Perform one of these steps to convert a nested plant unit to a top-level unit:
• Right-click the plant unit and choose Unassign from the context menu.
• Drag the plant unit from its current location and drop it on the Galaxy
name at the top of the Devices view.
Associating Devices
When devices are first created, they are placed in the Unassociated Devices
folder at the top of the Devices view. They can then be added to a plant unit
using the device’s context menu or with a drag-and-drop move.
To move a slave device to a plant unit using the device’s context menu:
1. Right-click the device in the Devices view and choose Associate from the
context menu to open the Associate Device dialog box (Figure 6-24).
Figure 6-24. Associate Device Dialog Box
plant units as follows:
• Select All Plant Units to include both top-level and nested plant
units.
• Select a plant unit to choose from its assigned units.
3. Pull down the list in the Assign To field and choose a plant unit from
within the selected scope.
The plant units are identified using this format:
Name [IDE tag] (Plant Unit template)
4. Click OK.
To associate a device using drag-and-drop:
1. Expand the Devices view display to show the target plant unit.
2. Select the device to be moved and drag it to the new location
(Figure 6-25).
Drag the device and

drop it on a plant unit
to associate the device
with the unit
Figure 6-25. Moving a Device to a Plant Unit
Perform one of these steps to move a slave device to the Unassociated Devices
folder:
• Right-click the device in the Devices view and choose Unassociate from
the context menu.
• Drag the device from its current location in the Devices view and drop it
on the Unassociated Hardware node at the top of the Devices view.
171
C H A P T E R 7
Configuring Devices
The Field Device Editor can be used either at the template level or at the device
instance level to configure bus settings, select modules, configure user
parameters, and define I/O data. “Creating Device Templates” on page 101
describes configuration tasks that are performed only on the template level,
while “Defining the Network” on page 139 covers configuration that is done
only for individual devices.
Note Unless otherwise noted, the term device in this chapter applies to both
device templates and device instances.
This chapters describes three Field Device Editor tabs: Bus Settings, Modules,
and Data Definition (which comprise a DPV0 configurator). The Bus Settings
and Data Definition tabs are available by default in Field Device Editor. The
Modules tab is shown only when the Use Module Definition from option is
set to GSD. It is not visible when the option is set to DTM, as module are
selected and user parameters configured with the device manufacturer’s user
interface in the Vendor DTM tab.
Contents
• Locking and Inheritance
• Editing Device Bus Settings
• Selecting Device Modules
• Configuring User Parameters
• Defining I/O Points
• Configuration Using the Manufacturer’s DTM
Locking and Inheritance

When a device instance is created from a device template, values set in the
template are copied to the device. Certain attributes can be locked in the
template so that they cannot be changed in the derived instances. When
changes are made in the template to these locked attributes, the new values are
propagated to the devices that have already been derived from the template.
Field Device Editor displays a padlock icon to the right of the value field for
every lockable attribute, or at the top of an editing panel to indicate the locked
status of the item being configured.
172 7. Configuring Devices
The padlock enables you to specify the parameter’s locked status. Table 7-1
describes how the icon indicates whether the parameter is locked by the device
template, and when changes in the parent definition are propagated to the
templates and instances derived from the parent template.
Table 7-1. Locked Status Icons
Icon Description
The green open padlock is used in device templates (both base
derived templates and derived templates) to indicate that the value
is unlocked and can be changed in this template and instances
derived from it.
• Click the icon to lock the parameter.
A grey open padlock is used in device instances to indicate that
the value is unlocked and can be changed in this instance, but the
locked status cannot be changed.
The Locked by Me closed padlock is used in device templates to
indicate that the value is locked by the current object.
When a value is locked, the parameter cannot be changed in any
template or instance derived from the template.
When a value is locked, any change made to the parameter is
propagated to the templates and instances derived from the
template.
• Click the icon to unlock the value.
The Locked by Parent grey double-padlock icon indicates the field
is locked by a parent object and cannot be changed. Changes made
to the parameter in the parent object are propagated to this device.
The grey padlock with a question mark indicates that the
parameter or object cannot be locked because its container is
unlocked. For example, you cannot lock a parameter definition if
the parameter refers to a module whose selection is not locked.
When a device type is created, the lockable parameters are Unlocked. You can
unlock and lock parameters individually as you set their values in the template.
One approach is to leave everything unlocked at the beginning of a project to
facilitate finding what fits each device type, and then to set and lock key
parameters in the device template to standardize the configuration across the
devices derived from the template.
Figure 7-1 shows bus settings configured in a device template
($WAGO_750_333 on the left) and the Bus Settings tab for a slave device
derived from the template (RIO004 on the right.)
Note InFigure 7-1 the Watchdog setting has been locked in the defining
template ( ) and therefore cannot be changed ( ) in RIO004. On the other
hand, the Mode Support and Group settings are unlocked ( ) in
$WAGO_750_333 and thus can be modified ( ) in RIO004.
7. Configuring Devices 173
Watchdog settings cannot be changed
Mode Support and Groups can be changed
Figure 7-1. Locked and Unlocked Values
Some of the objects for which inheritance is supported have a contained-in

relationship. For example, a module may contain user parameters, defined I/O
parameters and diagnostic messages. You can only lock contained objects if the
container (for example, the module) is locked. If the container is unlocked, the
contained objects cannot be locked ( ).
Other objects have a reference relationship. For example, an input parameter
may reference another parameter such as a status parameter. The referenced
parameter needs to be locked first. Thus, in a locked parameter it is not
possible to create a reference to an unlocked parameter, and if a locked
parameter gets unlocked the references to it in other locked parameters are
deleted.
In the PROFIBUS device template, the default setting is unlocked for attributes
and objects that support inheritance. Changes to the template attributes are
local and are not be propagated down to the already derived objects. You need
to lock the attribute in the template to propagate an attribute change down to
the derived objects.
When a change is made to a locked attribute or to the locked status of an
attribute, the derived objects are marked with a detected status error flag as
shown by the x on the device icon ( ) in the application views, indicating that
the object needs to be updated before it can be deployed.
To view the detected errors:
• Right-click the object and choose Properties from context menu and click
the Errors/Warnings tab in the Properties dialog box (Figure 7-2).
Figure 7-2. Validation of Detected Errors in the Properties Dialog Box
There are two ways to achieve the inheritance update and clear the validation
error detected flag: Pull and Push.
Pull Method
To update the objects one at a time:
1. Double-click the device in one of the applications views to open the object
in the Field Device Editor.
The Output view displays a message such as Inheritance update is done.
Please save changes when the device is opened in the editor.
2. Make other change to the device as needed, and then click in the title
bar to close the editor, save changes to the device and check the device in.
Push Method
To update the derived devices and templates at one time:
1. Expand the display of the template in the Derivation view to show the
objects that inherit the changes from the defining template.
2. Right-click the template and choose Push Inheritance from the context
menu.
Depending on the number of derived objects, the Push method may need a
noticeable amount of time to finish.
Which ever method is used, if a device is already deployed, it needs to be
redeployed to implement the inherited change.
Editing Device Bus Settings

Use the Bus Settings tab (Figure 7-3) to define how the slave device
communicates with the FBM222 master. The parameters displayed in the Bus
Settings tab are based on the features described in the device’s GSD file. For
example, the DPV1 group in Figure 7-3 is only displayed if the slave device
supports DPV1 features (DPV1_slave = 1 in the GSD file).
Refer to Appendix C, “DPV1 User Parameters” for the details about dealing
with DPV1 parameters and configuration.
To set the bus parameters in a device:
1. Click the Bus Settings tab.
Figure 7-3. Setting Bus Parameters
Note The unit for time-related parameters is either ms or TBit, that is, the
time needed to transmit a bit at the selected baud rate. For example, 1 Tbit
at 12 Mbaud = 1bit/(12,000,000 bit/sec) = 83 nsec.
2. Set the parameters as described in Table 7-2.
3. When the parameters have been set, click another tab in the Field Device
Editor, or click in the title bar to close the editor, save changes to the
device and check the device in.
Table 7-2. Common Bus Tab Fields
Field Description
Min Station Delay Specify the minimum time in TBits the device needs to wait before generating
Response Time a response after a transaction request from the FBM222 master. The range is
(MinTSDR) 11 (the default) to 225.
Watchdog When enabled, the watchdog timer is started each time the slave device
receives a communication from the FBM222. If the specified time expires
without another communication, the slave automatically switches its outputs
to the fail-safe state (as defined in the device).
By default the watchdog timer is disabled.
• Click the checkbox to enable the watchdog timer and specify the
Timeout period in milliseconds.
Note For some DPV1 devices, the time base for the watchdog timer can be
set to 1 ms using a checkbox in the Watchdog group (Figure 7-3). Before
selecting this option, review the GSD file for the device to verify that the
device supports the option (WD_Base_1ms_support = 1).
If the parameter time base for this device is 10 ms, the range is 0 to 650250.
If the parameter time base for this device is 1 ms, the range is 0 to 65025.
The default is 3000 milliseconds.
Note Verify that the watchdog interval is not set so low as to cause
inappropriate tripping. We recommend 3000 ms for devices to be connected
to a redundant FBM222.
Mode Support Use the checkboxes in this group to enable or disable two global functions:
• Freeze: On receiving a Freeze command, the slave device reads its input
into a buffer. On the next read request from the FBM, the device sends
the contents of the buffer, and ignores any changes in the data since the
freeze command.
• Sync: On receiving a Sync command, the previously transmitted output
values are transferred to the output ports. The output values transferred
by data exchange are stored and not transferred to the output ports until
another Sync command follows or the sync mode is switched off.
Sync and Freeze commands are configured in DCI blocks as described in
“Programming Sync and Freeze Actions” on page 312.
The options cannot be selected if support for the functions is not shown in the
device’s GSD file.
When enabled, the device responds to sync and freeze commands sent by the
FBM to one, several, or all the slave devices on the port (see “Groups” on
page 177).
Table 7-2. Common Bus Tab Fields (Continued)
Field Description
Device Failure Click the Enable checkbox to configure the FBM222 to disable
Timeout communications with this device if the device is disconnected for longer than
a specified period, and then specify the Timeout period in seconds. The range
is 1 to 240 seconds (the default). If the option is not checked or the value is 0,
communication remains enabled and the FBM brings the device online when
it is re-connected.
Note When this option is checked for a new device, the device does not
automatically go online when it is connected to the FBM. Enable
communications with the device using System Manager (as described in
“Device Equipment Change Actions” on page 397).
Groups Check one or more of the numbered boxes to assign the device to groups that
the FBM uses for global commands such as Sync and Freeze. Uncheck a box
to exclude the device from the group.
See “Programming Sync and Freeze Actions” on page 312 for information on
use of the groups.
Enable DPV1
Note This check box needs to remain cleared, as it enables certain DPV1
features that are not supported in this version of the Field Device Editor.
Click the checkbox to enable DPV1 functions.

DPV1 Response Set the time in milliseconds. The range is the C2_Response_Timeout from
Timeout the GSD file (the default) to 655350 milliseconds.
The DPV1 Response Timeout needs to be greater than the
C2_Response_Timeout from the device’s GSD file.
Failsafe Leave this check box cleared.
Selecting Device Modules

The Modules tab contains two tab pages for configuring devices with plug-in
modules, and displaying the fixed I/O configuration of compact devices:
• Configuration Data (Figure 7-4, Figure 7-6 and Figure 7-7) identifies the
modules to be used.
• User Parameters (Figure 7-8) enables selection of device and module
parameters specified in the device’s GSD file.
The Modules tab is shown when GSD is selected for the Use Module
Definition from option on the General tab.
This section discusses the Modules tab for modular DP devices, and then
describes the tab for compact devices and devices with soft modules.
Modular Devices
To configure I/O for a modular device:
1. Click the Modules tab in the Field Device Editor.
Figure 7-4 shows modules being selected for a Wago 750-333 remote I/O
system. The list at the top of the tab shows the modules that can be
plugged into this device. The list, derived from the device’s GSD file,
includes a description of the I/O provided by the module, the number of
input bytes, the number of output bytes, the configuration data for the
module, and, in some cases, specific slots that can or cannot be used.
Figure 7-4. Selecting Modules for a Remote I/O System
With the device in Figure 7-4, the module descriptions that start with * are
dummy modules that can be used as placeholders when a module has been
removed so that you do not need to modify the point number
configurations in the DCI blocks that access the other modules in the
device.
2. Select the description in the list that matches the module that is be
installed in slot 1, and click the Add/Replace button in the lower right of
the tab.
The module is inserted in the first available row (in this case slot 1) in
Configured Modules list in the lower half of the tab.
3. Select and add other modules to match the modules that are or will be
installed in the device.
As you add modules, the editor updates the fields at the bottom of the page
that compare the maximum and actual length of the input and output data,
and maximum and actual number of modules. Many devices, such as the
one in Figure 7-4, do not allow empty slots in the device configuration,
just as there cannot be gaps in the actual device, where connectors on the
sides of each module create the bus over which the modules communicate.
The bus structure in some other modular devices allows empty slots
between modules. Refer to the documentation for individual devices for
module configuration rules.
4. Review the slot assignments and verify that they match the modules as
they are to be installed in the slave device.
Note If the modules are not in the correct order or they do not match the
types in the device, the FBM222 is unable to correctly exchange data with
the device.
5. Correct any mismatches between the Configured Modules list and the
installed modules by selecting a module in the list and performing any one
these steps:
• Press or on the right to move the module up or down in the list.
• Select a different module in the Available Modules list and click
Add/Replace to change the module description for the slot.
• Click Remove to delete the module from the slot.
Note You can multi-select rows in the Configured Modules list using
Shift+click or Ctrl+click to remove modules, but not to replace or move
them.
Note If you replace or remove a module, any parameter selection or data

definition related to the module is deleted from the device configuration.
6. Click the Lock/Unlock button to the right of the Configured Modules list
to toggle the locked attribute of the selected module.
When the module is locked in the template ( is displayed to the left of
the module in the Configured Modules list), the module selection cannot
be changed in the derived devices( ). When the module is unlocked in
the template ( ), the module selection can be changed in the derived
devices ( ).
Note You need to lock the module in order to lock user parameter
selections and I/O parameters definitions.
Configuration Data
As you add modules, the editor configures the I/O data portion of the telegrams
that the FBM222 and the device use in cyclic data exchange.
To review the data configuration:
1. Click Show Config to display the module’s configuration details in the
Config Data dialog box (Figure 7-5).
The dialog box lists the modules in the selected order, and under each
module, displays the byte numbers and configuration data within each
byte.
2. Click to the left of the module name to hide its configuration details;
click to the left of the module name to expand the display and show the
configuration details.
3. Click the radio button at the bottom of the dialog box to view the data in
Binary, Hexadecimal or Decimal format.
Figure 7-5. Config Data Dialog Box
4. Click the OK to close the Config Data dialog box.
Compact Devices
The Modules tab for a compact device (Figure 7-6) displays the device itself as
the only selectable module, and slot 1 in the Configured Modules list as the
only available slot. The device needs to be added to the slot to finish the device
configuration.
To configure the I/O for a compact device:
1. Select the device in the Available Modules list and click Add/Replace.
2. Click the Lock/Unlock button to the right of the Configured Modules list
to toggle the locked attribute of the device.
When the device selection is locked in the template ( is displayed to the
left of the device in the Configured Modules list), the selection cannot be
changed in the derived devices. When the device is unlocked in the
template ( ), the module selection can be changed in the derived devices.
• Lock the device selection if you plan to lock the user parameter or
data definitions for the device.
3. Click Show Config to review the configured data.
Figure 7-6. I/O Configuration for a Compact Device
Soft Modules
PA devices and some modular DP slave devices allow you to select a software-
based module, or soft module, to configure the device I/O. Figure 7-7 shows
the Modules tab for a PA positioner where a soft module has just been selected
from the Available Modules list to replace the already configured soft module.
A dialog box prompts that swapping the module removes any parameters
defined for the original module.
Note In Figure 7-7 the possible slots listed for each module in Available
Modules is 1, and that the Configured Modules list only shows Slot No. 1.
Figure 7-7. Soft Module Being Changed for a PA Positioner
Configuring User Parameters

Many device vendors have incorporated various user-selectable features for the
device and/or the device modules. These can include device startup actions,
diagnostic channels, failsafe actions, indications of the installed status, and so
on. The user-settable parameters are listed in the device’s GSD file and
displayed on the User Parameters tab within the Modules tab.
Note Refer to the manufacturer’s documentation for the device to fully

understand how the parameters affect operation of the device and the modules.
Field Device Editor contains no help for these parameters other than the brief
descriptions contained in the GSD file.
To configure these additional device features:

1. Click the User Parameters tab (Figure 7-8).
The Module table in the top left of the tab lists the device (or the head
module) and the configured modules by slot number and module
description.
2. Select the device or one of the configured modules to list the settable
parameters and their current values in the Module Parameters table to the
right.
Individual parameter selections can be locked in a device template only if
the module is locked. The icons in Figure 7-8 indicate that locking is
not available for the module parameters because the module itself is not
locked.
3. Select a parameter in Module Parameters.
The editor displays a control such as a pull-down list (as in Figure 7-8) or
editable field below the table for specifying the parameter value.
In Figure 7-8, the user is enabling a diagnostic channel, the second of three
features of the fourth module.
Figure 7-8. User Parameters for a Module in a Remote I/O Device
4. Set the value and then edit other parameters and modules as needed.
The User Param Data group at the bottom of the tab shows the
configuration data for the selectable parameters. The Edit button opens a
dialog box for editing this data directly instead of using the controls at the
top of the tab (Figure 7-9). The dialog box is similar to the Config Data
dialog box opened from the Configuration Data tab (Figure 7-5), except
that the parameter values can be edited.
We do not recommend editing

parameters using the User Param
Data dialog box for users.
Figure 7-9. User Param Data Dialog Box
5. Check the Add DPV1 Bytes option at the bottom of the tab to add three
bytes for DPV1 data to the configured data if the user parameter data from
the GSD file does not already provide these bytes.
This option is displayed only if the GSD file indicates DPV1 support
(DPV1_slave = 1).
6. When the modules have been configured, click another tab in the Field
Device Editor, or click in the Field Device Editor title bar to save the
configuration, close the editor and check the device in.
Defining I/O Points

Use the Data Definition tab to create parameters based on the I/O data in the
modules that were selected in the Modules tab. The tab enables you to name
and describe a data point provided by a device or module, and then specify the
data type and other attributes.
If the device manufacturer’s DTM has been associated with the device
template, the Data Definition tab displays the parameters that are defined in the
DTM. The Data Definition tab enables you to change some attributes of these
supplied parameters, as well as add new parameters.
The parameters have two uses:
• Parameters defined in this tab can be selected in Field Device Manager for
online display of device I/O and diagnostics, including watch screens and
trend displays. Setup of the Field Device Manager displays is covered in
“Field Device Manager” on page 217.
• These named parameters facilitate making I/O connections when you

configure DCI blocks in the Control Editors. The parameters are shown in
various browsers, where they can be selected to automatically complete
the Point Configuration String in the DCI block point parameter.
In Figure 7-10 for example, the user has just connected a RIN block to a
parameter defined for an RTD module in a remote IO system. When a
device is selected in the FBMs pane in the upper left (RIO002 in the
example), the device’s parameters are listed in the PROFIBUS
DataDefinitions tab in the lower part of the tab. The connection was made
by dragging the RIN_1 block from the Blocks pane on the right and
dropping it on the target parameter (NW7_1, a 2-byte signed integer).
Figure 7-10. Connecting I/O Using a PROFIBUS Parameter
The Connection field for PROFIBUS parameter then lists the path to the
block parameter (COMPND_001.Strategy_001.RIN_1.PNT_NO). The
Blocks pane shows the connected device (RIO002) and Point
Configuration String (6S2) that is inserted into the PNT_NO based on the
module configuration and the parameter attributes. The 6 specifies an
offset of 6 bytes in the input data stream and S2 specifies a two-byte
signed integer. Refer to “Point Configuration String Syntax” on page 261
for a detailed description of the elements of the Point Configuration
String.
Once this IO connection is made, the PROFIBUS parameter remains

associated with the DCI block:
• Changes to the parameter’s data type, byte position, and other
attributes changes the Point Configuration String in the associated
block.
• Deleting the PROFIBUS parameter clears the IOM_ID and point
number parameters in the associated DCI blocks.
Use for DCI Assignment Option

To use a parameter in Field Device Manager displays and associate the
parameter with DCI blocks, you must enable the parameter Use for DCI
Assignment attribute by clicking its checkbox in the Data Definition tab. You
cannot uncheck the box until you unassociate the DCI blocks that reference the
parameter for their IOM_ID and point number parameters.
To unassociate from DCI blocks:
1. Open the host control processor in the Hardware Editor and click the IO
Assignment tab (Figure 7-10).
2. Select the device in the FBMs pane to display its parameters in the
PROFIBUS DataDefinitions tab.
3. Right-click the parameter and choose Find IO Connection from the
context menu to select the associated DCI block in the Blocks pane.
4. Right-click the parameter and choose Unassign IO Connection from the
context menu to empty the IOM_ID and point number parameters in the
referenced DCI block.
Note Input parameters may have more than one DCI block association.
Defining and Validating Parameters

To configure I/O points:
1. Verify that you have selected the modules that provide the data for the
parameter values, and then click Data Definition to go back to the tab
(Figure 7-12).
Data Definition includes four tab pages for defining various types of
parameters: Input, Output, Diagnostics, and, if the device supports
DPV1 functions, Device Parameter (DPV1).
In general, the tabs consist of a list box on the left where you add and
remove parameters, and an editing panel to the right where you can set the
parameter attributes using pull-down lists and manually entering names
and descriptions.
When you click another tab, Field Device Editor validates the
configuration and identifies any detected errors such as two output
parameters configured to write to the same data (Figure 7-11). The Error
dialog box prompts you to fix detected errors before leaving the tab.
Figure 7-11. Detected Error Message Displayed When Switching Tabs
2. Select the tab for the parameter type and define the parameters as
described in the next three sections.
Defining Input and Output Parameters

The Input and Output tabs in Data Definition have the same format and
functions. Procedures described below for the Input tab apply to the Output
tab, and vice versa.
Table 7-3 describes the parameter attributes as they are used in the Data
Definition tab to configure input and output parameters.
Table 7-3. Parameter Attributes in the Data Definition Tab
Attribute Description
Name Enter an alphanumeric string that uniquely identifies parameter within the
module, or accept the supplied parameter name. Do not leave the field blank.
Use for DCI Check this option to make the parameter available in Field Device Manager
Assignment displays and the PROFIBUS DataDefinitions tab in various device browsers
in the Control Editors used to make field connections.
Table 7-3. Parameter Attributes in the Data Definition Tab (Continued)
Data Type Choose a data type from the pull-down list:
• Signed Integer 8, 16, 24, 32: Intel Format
• Unsigned Integer 8, 16, 24, 32: Intel Format
• Extended Format: Special format that selects bits from one or more bytes
in the data stream
• Packed Bits: Selects a range of contiguous bits from up to four bytes
• Boolean
• Floating Point: Standard Control Editors real format
• Channel Bit: Single bit within a byte
• Raw: Raw data from the data stream in the integer value. Data length is 8
bits to 640 bits in 8-bit increments
These additional data types are available for PA devices:
• PA Signed Integer 8, 16, 24, 32: Intel format signed integer with PA
status value
• PA Unsigned Integer 8, 16, 24, 32: Intel format unsigned integer with PA
status value
See “PA Status Handling” on page 265 for information on PA status.
Byte Position Select the starting byte within the module. This position is converted to an
offset in the device’s input or output data stream when the parameter is used
to construct the Point Configuration String.
Bit Position Specify the starting bit within Byte Position for Extended Format, Packed
Bits, and Channel Bit data types.
For the other data types, Bit Position is automatically set to 0 and cannot be
edited.
Bit Length Specify the data length in bits for Extended Format, Packed Bits and Raw
data types.
For Raw data types, Bit Length ranges from 8 bits to 640 bits in eight-bit
increments.
For the other data types, Bit Length is determined automatically and cannot
be edited.
Sign Bit Position Enter the bit position of the sign when the parameter uses the Extended
Format data type.
Leave blank if the value is unsigned or the sign is to be determined one’s
complement or two’s complement.
Table 7-3. Parameter Attributes in the Data Definition Tab (Continued)
Swapping Swapping changes the order in which bytes are processed within a multi-byte
parameter.
A byte-swapping scheme based on the data length is the default selection for
signed and unsigned integer, and floating point parameters. For example, the
default byte-swapping for an Unsigned Integer 24 parameter is
Byte0_Byte1_Byte2. The default swapping for these data type provides the
proper interpretation of the data.
See “DCI Block Data Types” on page 300 for additional information on byte
swapping.
Complement Select OnesComplement or TwosComplement to identify the signing
method to be used in an Extended Format parameter instead of a sign bit.
Select NoComplement if the value is to be unsigned or if there is an entry in
the Sign Bit field.
Units Enter a character string to identify the unit of measure.
Lower Range The data range is determined by the data type and cannot be edited. Field
Upper Range Device Manager uses the range to set the minimum and maximum value axis
in trend displays (see “Watch Tab” on page 232).
Status Parameter Input tab only
Good Status Mask These attributes specify value-status handling for certain DP devices that
provide a custom value status. Do not use for PA devices. Refer to “Custom
Status Handling” on page 193.
Readback Parameter Output tab only
Use this field to select a readback value to confirm the output to the device, as
described in “Readback Parameter” on page 194.
Description Use this optional character string to identify the function of the parameter for
Field Device Manager displays.
To configure input parameters:

1. Click the Input tab within Data Definition if the tab is not already
displayed.
The pane in upper left corner shows the input modules configured for the
device.
2. Click to the left of the module name to view the parameters already
defined for the module’s input data.
When you select a module or one of its parameters, the module’s data
structure is shown in the Input Data Structure pane in the lower left.
3. Select a module and click Add to insert a parameter below the module in
the data tree and to display the parameter’s attributes in the editing panel
to the right.
The locked status icon at the top of the panel indicates whether the
attributes can be edited ( or ) or if the attributes are locked in the
defining template ( ), as described in “Locking and Inheritance” on
page 171. In Figure 7-12, at the top of the editing panel indicates that
the definition cannot be locked because the module selection is not locked.
4. Change the tag in the Name field to something that is more meaningful.
5. Click the Use For DCI Assignment checkbox in the upper right corner of
the editing panel if you are going to use this parameter to configure DCI
blocks (see Chapter 9, “Control Configuration” for information on
connecting the DCI blocks to the parameter).
Note The Use for DCI Assignment needs to be checked for the parameter
to be available for display in Field Device Manager and for connection to
DCI blocks.
6. Refer to the device documentation for a description of the data types

supported by the module, and make a selection from the Data Type pull-
down list.
In Figure 7-12, the selected module provides a two-byte signed analog
input from each of four RTDs. A parameter is being configured for the
third input. The selected data type is a 16-bit signed integer.
Based on the data type selected, the other fields in the editing panel are
enabled or disabled, and selections available for each field are adjusted to
match the type. For example, with the selection of the 16 bit integer, byte
swapping is defaulted to Byte0_Byte 1. The only other choice is No
Swapping.
7. Specify the source of the parameter within the input data stream from the
module by entering the start of the data (relative to the module) in
BytePosition and number of bits in Bit Length.
For some data types you must also enter the starting BitPosition within
the specified byte.
The selection of SignedInteger 16 in Figure 7-12 set Bit Length to 16.
8. Edit the other parameter attributes, including entering an optional
description of the parameter in the final field.
Figure 7-12. Data Definition Tab
9. Click Report to display a table of the input parameters defined for the
device.
For each input parameter, the report lists the module, the parameter name
and attributes, and the Point Configuration String that is inserted into the
point number parameter of the DCI block. For example, the highlighted
parameter in Figure 7-13 will result in the Point Configuration String
12S2, where 12 is the offset with the input data stream from the device and
S2 specifies that the data is a two-byte signed integer.
Note The byte position is relative to inputs from the device, not the module
inputs.
Resulting Point
Configuration String
Figure 7-13. Report Shows Input Parameters Configured for the Device
Custom Status Handling

Some device manufacturers have implemented a status for input from DP
slaves, similar to the standard value status used in PA slave devices. Typically,
this status utilizes a byte appended to a value within the cyclic input data
stream. When used, this status is device-specific and vendor-defined.
The Input tab in Data Definition enables you to take advantage of the custom
status byte by defining a separate status parameter that, when referenced by an
input parameter, adds the custom status to the value.
To use a custom status with an input value:
1. Refer to the device documentation for the location and interpretation of
the custom status.
2. Create an input parameter that identifies the location of the status (relative
to the module) and the data type of the status.
These rules apply:
• The status parameter needs to be defined as type packed bits (P),
unsigned integer (U) or channel bit (C) only.
• The status needs to be located in the cyclic input of the module.
• Byte swapping (W0 – W3) options are NOT supported for the status
parameter.
• A status parameter need not reference another status parameter.
3. Select the input parameter that contains the value to which the status is
appended, and use the drop down list in Status Parameter to select the
custom status parameter.
4. Specify in the Good Status Mask field how the status is to be evaluated:
The syntax labels bits from right to left, 0 being the lowest bit. At least one
bit needs to be defined. It is the lowest bit going from right to left.
Undefined bits are treated as “don’t care.”
• Enter a 1 or 0 in a bit position to specify how that bit position is to be
evaluated. Only those bit positions with a 1 or 0 are used for
mask/status match evaluation.
• Enter a dash (-) if the bit position is to be ignored and it is lower than
an evaluated position. Bit positions higher than the evaluated
positions do not need to defined. Leaving the higher bits undefined
may be necessary to stay with the 32-character limit to the Point
Configuration String.
For example, the status parameter is a one-byte unsigned integer
appended to a two-byte value from the DP slave device. The status is
set to GOOD when bit 1 is set (1) and bit 2 is not (0). Other bits are
ignored.
Bit Position 7 6 5 4 3 2 1 0
Mask (fully defined) – – – – – 0 1 –
Mask (minimum definition) 0 1 –
The fully defined entry in Good Status Mask for status is:
-----01-
The minimally defined entry in Good Status Mask for status is:
01-
The status byte is decoded from right to left, 0 being the lowest bit.
Only those bit positions with a 1 or 0 are used for mask/status match
evaluation. In the example, the value is GOOD if bit 1 = 1 and bit 2 =
0. Bit 0 and bits 3 through 7 are not considered.
Note The status byte (or whatever bytes are used for the definition of
status) is used only for GOOD/BAD evaluation. The status bytes are not
considered to be part of the actual point number value that has been
defined in input parameter.
The definition of PNT_NO value and DCI status is ultimately vendor- and
device-specific, and no generalizations can be made about the use of this
custom status syntax.
Readback Parameter
The DCI output blocks provide confirmed outputs by reading back the value
that is written to the device. A confirmed output contains two components: a
request value and a readback value. The request value is changed by the
control system and sent to the field device, and the readback value is the value
read back each cycle from the FBM222. In the ROUT block for instance, the
request value is made available for diagnostic purposes as parameter OUTQ.
The readback value is shown as the parameter OUT.
The purpose of the confirmed output is to help ensure that an output is not
displayed to the user until that new value has been driven down as close to the
device as possible, and then read back to verify that the value has been written.
With the FBM222, the confirmed write can go to the device and read back
from the device’s actual value (such as the actual valve stem position, not the
commanded position) providing the device is capable of supporting a true
readback parameter and the DCI block has been properly configured.
This true confirmed write provides two main advantages:
• You can readily determine from the block default detail display
differences between the commanded value to the device and its present
position (PV), and quickly identify detected issues in device operation.
• If the device goes to a failsafe position, the question by default is, “How
does the control scheme connected to the device have a sense of PV as the
failsafe condition clears?” With readback of PV, no ambiguity exists, the
control scheme recovers at the PV of the device, and thus there is no bump
during failsafe recovery.
You can specify a readback value to confirm the output if the device provides
such a value in its input data stream. If the value is not available, the FBM222
confirms that it has sent the output to the device, but not that the device has
implemented the change.
Many PA devices already have a readback parameter defined in the device, and
you can define the readback as an input parameter using the same data type.
The readback value can be any other data point from the same device,
including data from the cyclic data stream and acyclic parameters.
Creating Parameters from the Data Structure

When you select a module in the Input Parameters or Output Parameters pane
that module’s data structure is displayed in the Data Structure pane in the lower
left.
For devices with GSD version 5.0 and later, the Data Structure pane displays
the data area names, as shown for the analog input module selected in
Figure 7-14, if data areas are defined for the module. The example module
provides a floating point value starting at byte 0 and a one-byte signed integer
(byte 4). If the selected module does not have data area definitions, the input or
output bytes available within the module are listed as they are in Figure 7-12.
You can create a parameter from the Data Structure pane, as shown in the
example in Figure 7-14.
To create the example input parameter:
1. Select the module (M1 AI_1_CH2) to display its structure in the Input
Data Structure pane in the lower left.
2. Select the desired data area name (0-FloatingPoint) and click the Create
Parameter button at the bottom of the pane.
The parameter is added to the module with attributes set according to the
data area description in the GSD. In Figure 7-14 for example, the new
parameter is defined as a floating point value starting a byte 0. The other
parameter attributes are defaults for the data type. If the second data area
name had been selected, the new parameter would be the data type
SignedInteger 8 with a BytePosition of 4.
If there is no data area definitions in the Data Structure pane:
• Select the desired byte position and click the Create Parameter
button at the bottom of the pane.
The parameter is added to module with a default name consisting of
the selected byte and numeric suffix (0_Byte_001 or 4_Byte_001 for
examples). The default data type is SignedInteger 8 with the Byte
Position selected in the Data Structure pane.
3. Set the parameter attributes using the tools in the editing pane.
Figure 7-14. Floating Point Parameter Defined Using the Data Area
Name
Copying Parameters
You can create additional parameters using the context menu in the Input
Parameters or Output Parameters pane to copy parameter definitions to another
module. The sequence in Figure 7-15 shows the creation of an analog output
parameter by copying a parameter in the module in slot 8 and pasting it to a
similar module in slot 9.
To add an output parameter by copying:
1. Right-click the original parameter in the Output Parameters pane and
choose Copy from the context menu.
2. Right-click another module with the same output data structure and
choose Paste from the context menu.
The parameter is added under the selected module.
You can also paste the parameter to the same module, in which case a
numerical suffix is added to the name of the new parameter to distinguish
it from the original (6-Byte_001_001 versus 6-Byte_001 for example).
3. Modify the parameter attributes using the tools in the editing pane.
If replicating an output parameter in the same module, you need to change
the Byte Position value to avoid having two parameters write to the same
data.
Figure 7-15. Copying Parameters
Deleting Input and Output Parameters

Deleting a parameter that is associated with a DCI block clears the I/O
connection from the block, that is, empties the block’s ECB identifier
(IOM_ID, IOM_IDn) and point number (PNT_NO, for example) parameters.
You cannot delete a parameter that is associated with a DCI block that is
deployed. You need to first undeploy the associated blocks.
To delete an input or output parameter:
• Select the parameter in the Input or Output Parameters pane and click the
Delete button below the list.
Editing Diagnostic Messages and Parameters

The Diagnostic tab within Data Definition (Figure 7-16) enables you to edit
diagnostic messages and parameters as follows:
• Edit device-specific diagnostic messages extracted from the GSD file. The
Diagnostic Messages pane in Figure 7-16 shows eight messages (Areas 16
through 23) defined in the GSD for the example remote I/O and sourced
from channel-related bytes in the diagnostic. These diagnostic messages
are displayed in the Field Device Manager Diagnostic tab when their
respective bits are set.
• Configure new diagnostic messages based on the device diagnostics
(either standard six bytes or manufacturer-defined diagnostics) or a DPV1
parameter. These messages are also displayed in the Field Device Manager
Diagnostics tab when their respective data value matches the Value
specified in the message definition.
• Parameterize any diagnostic message so that the diagnostic can be added
to other tab pages in Field Device Manager such as Input, Watch or a
custom tab. Diagnostic parameters can also be connected to DCI blocks
for display on the Control HMI screens and/or integration into a control
scheme.
• Create diagnostic parameters sourced from device or module diagnostics,
or DPV1 device parameters.
Diagnostic Messages
To edit diagnostic messages:
1. Click the Diagnostic tab within the Data Definition tab.
The Diagnostic Messages pane in the upper left lists the currently
configured messages.
2. Select any one of the messages extracted from the GSD to display the
message attributes in the editing panel to the right.
attributes can be edited ( or ) or if the attributes are locked in the
page 171.
The Name, Status, Category, Description and Actions fields are displayed
in the Field Device Manager Diagnostics tab, along with a time stamp,
when the specified diagnostic data equals the Value field.
For the vendor-defined messages, you can change the message name, and
enter a description of the diagnostic condition and recommended action.
We do not recommend other changes to the message attributes.
Figure 7-16. Defining Diagnostic Messages and Parameters
To create a new message:

1. Click the Add button below the Diagnostic Messages list.
A default message name such as DiagnosticMessage_001 is added to the
list of messages.
2. Edit the message attributes as described in Table 7-4.
Table 7-4. Diagnostic Messages Attributes
Field Description
Area Use this optional field to identify the area or bits that
diagnostic message uses.
Name Enter a message text as you want it to appear in Field
Device Manager.
Source Use the pull-down list to select Diag Data or one of the
DPV1 parameters configured for this device.
If the selected DPV1 parameter is deleted from the
configuration, the diagnostic message will be removed also.
See “Defining DPV1 Parameters” on page 203.
Table 7-4. Diagnostic Messages Attributes (Continued)
Field Description
Diag Part Select Device, Device Channel, or one of the configured
device modules from the pull-down list. This field is
inactive when the Source is a DPV1 parameter.
First Bit Enter the first bit in the specified diagnostic data or
parameter.
Last Bit Enter the last bit in the source data. The range is Starting
Bit to Starting Bit + 16.
Value The diagnostic message is generated when the specified
data matches Value.
For example, the message selected in Figure 7-16 is
generated when bit 17 in the specified diagnostic part is set
to 1.
Status Use the pull-down list to select the status to be displayed in
Field Device Manager:
• OK
• Out-of-Specification
• Maintenance Request
• Failure
Category Choose a category for the diagnostic condition:
• Process
• Communication
• Device Error
Description Enter a description of the condition and a recommended
Action action for the diagnostic condition.
FBM Eval Select Error or Warning from the pull-down list to have
the FBM222 to acquire the diagnostic data for status
evaluation. If the value at the defined position matches the
value in the message configuration, the FBM generates the
error or warning. This field is active only when the source is
Diag Data and the Diag Part is device. The default value for
FBM Eval is None.
3. Add and define other messages.
You can also add a message by copying and editing an existing message. For
example, you can copy a detected error message based on diagnostic bit, and
change the bit to 0 and the Status to OK for a message that indicates normal
operation.
To add a message by copying:
1. Right-click the message to be replicated and choose Copy from the
context menu.
2. Right-click anywhere in the Diagnostic Messages pane and choose Paste

from the context menu to add the message to the end of the list.
The message name will consist of the original message name and a
numeric suffix such as _001 or _002.
3. Edit the message attributes to create a different message.
Diagnostic Parameters
You can create a diagnostic parameter for use in Field Device Manager and/or
connection to a DCI block by either parameterizing a diagnostic message or
adding the parameter using the tools in the Diagnostic Parameters group.
To create diagnostic parameters:
• Select a message in the Diagnostic Messages pane and click Create
Parameter below the list to add a parameter with the same name and
the same data as the message.
• Click Add in the Diagnostic Parameters pane.
• Right-click any existing parameter, choose Copy from the context
menu, and then right-click anywhere in the Diagnostic Parameter list
and choose Paste from the context menu.
2. Select the parameter in the list to display its attributes in the editing panel
to the right.
attribute can be edited ( or ) or if the attributes are locked in the
page 171.
3. Check the Use for DCI Assignment option to allow connection of this
parameter to DCI blocks for use in a control strategy or in Control Core
Services displays.
DCI blocks.
4. Edit the parameter attributes as described in Table 7-5.

Usually parameters created from diagnostic messages do not need further
editing.
Table 7-5. Diagnostic Parameter Attributes
Field Description
Name Change the default name if desired. The name needs to be unique among the
parameters defined for the device. This field cannot be empty.
in the Control Editors used to make field connections.
Table 7-5. Diagnostic Parameter Attributes (Continued)
Field Description
Data Type Select a data type from the pull-down list:
in the data stream
• Boolean
Note The FBM222 supports I/O assignment to DCI blocks of parameters

with the boolean, integer and raw data types only. Diagnostic parameters with
the data type extended format, packed bits, floating point, and channel bit are
not available for I/O assignment to a DCI block. However, Field Device
Manager displays diagnostic parameters of the formats.
Byte Position Identify the portion of the data stream by entering the byte position, bit
Bit Position position and number of bits in the data.
Bit Length Selection of the data type determines which of these fields need an entry.
parameter.
swapping.
Description Enter an optional description of the parameter to identify it in Field Device
Manager displays.
Deleting Messages and Parameters

The Delete buttons in the Diagnostic Message group and Diagnostic
Parameters group remove the selected message or parameter from the
configuration.
If a parameter was created from a diagnostic message, the parameter remains
when the message is deleted.
When a module is deleted from the device configuration, the messages and
parameters sourced from the module are deleted also.
Deleting a parameter that is associated with a DCI block clears the I/O
connection from the block, that is, empties the block’s ECB identifier
Defining DPV1 Parameters

Data Definition displays the Device Parameter (DPV1) tab when the device’s
GSD indicates support for DPV1 functions. Device parameters are read and
written to during acyclic data communications. Refer to the device and module
documentation for the DPV1 data available.
To define device parameters:
1. Click the Device Parameter (DPV1) tab within Data Definition if the tab
is not already displayed.
The pane on the left shows the device parameters already configured for
the device. When you select a parameter in this list, the editing panel on
the right displays the parameter’s attributes (Figure 7-17).
2. Click Add to append a new parameter to the list using a default name such
as DeviceParameter_001 or DeviceParameter_002.
The editing panel to the right displays the default attribute values for the
new parameter.
3. Click the Use For DCI Assignment checkbox in the upper right corner of
the editing panel if you are going to use this parameter to configure DCI
blocks (see Chapter 9, “Control Configuration” for information on
connecting the DCI blocks to the parameter).
DCI blocks.
Figure 7-17. Defining DPV1 Parameters
4. Edit the device attributes as described in Table 7-6.
Table 7-6. Device Parameter Attributes
Field Description
Name Change the default name to a tag that is more useful in identifying the data.
The name needs to be unique among all device parameters. The field cannot
be empty.
in Control Editors used to make field connections.
Table 7-6. Device Parameter Attributes (Continued)
Field Description
Data Type Choose a data type from the pull-down list:
in the data stream
• Boolean
Byte Position Select the starting byte within the DPV1 parameter identified by slot and
index.
Bit Position Specify the starting bit within Byte Position for Extended Format, Boolean,
Raw and Channel Bit data types.
For the other data types, Bit Position is automatically set to 0 and cannot be
edited.
Bit Length Specify the data length in bits for Extended Format, Packed Bits and Raw
data types.
For Raw data types, the Bit Length ranges from 8 bits to 640 bits in eight-bit
increments.
For the other data types, Bit Length is determined automatically and cannot
be edited.
Sign Bit Position Enter the bit position of the sign when the parameter uses the Extended
Format data type.
Leave blank if the value is unsigned or the sign is to be determined one’s
complement or two’s complement.
parameter.
swapping.
Complement Select OnesComplement or TwosComplement to identify the signing
method to be used in an Extended Format parameter instead of a sign bit.
Select NoComplement if the value is to be unsigned or if there is an entry in
the Sign Bit field.
Table 7-6. Device Parameter Attributes (Continued)
Field Description
Slot Enter the slot number for the device. The slot number is used in the
destination device to address the desired data block.
Refer to the device documentation for the information:
• Meaning and usage of the DPV1 parameter
• Whether the parameter is read-only or read-write
• Slot and index to read or write the parameter
The range for this field is 0 to 225.
Index Enter the index of the data block within the Slot, as specified in the device
documentation. The range for this field is 0 to 225.
Access Choose the type of user access for this parameter:
• Read
• Write
• Read/Write
The parameter needs to be writable in order to download the parameter using
Field Device Manager.
The Write and read/Write attributes can be selected only if the parameter in
the device is writable.
Description Enter a parameter description for use in Field Device Manager displays.
Description is optional.
You can also add a parameter by copying and editing an existing parameter.
To add parameter by copying:
1. Right-click the parameter to be replicated and choose Copy from the
context menu.
2. Right-click anywhere in the Device Parameters list and choose Paste from
the context menu to add the parameter to the end of the list.
The parameter name consists of the original parameter name and a number
such as _001 or _002.
3. Edit the parameter attributes to create a different parameter.
No two parameters can write to the same data.
Deleting DPV1 Device Parameters

Deleting a DPV1 device parameter that is associated with a DCI block clears
the I/O connection from the block, that is, empties the block’s ECB identifier
To delete a DPV1 device parameter:

• Select the parameter in the parameter in the list on the left side of the
Device Parameter (DPV1) tab and click the Delete button below the list.
Configuration Using the Manufacturer’s DTM

When you associate the device manufacturer’s DTM associated with a base
derived template, Field Device Editor displays the DTM in the Vendor DTM
tab for the template and each device (template or instance) created from the
base derived template.
In online mode, the Vendor DTM tab enables you to directly view and edit
parameters on the device. In offline mode, you can use the tab to pre-configure
device parameters. For device templates, the DTM is always offline.
You can go back and forth freely between the manufacturer’s DTM and the
universal PROFIBUS DTM in Field Device Manager by clicking the Vendor
DTM tab and the Field Device Manager tab, respectively.
The first time you activate a DTM, the Vendor DTM tab displays the default
screen for the DTM (Figure 7-18 is the default screen for a DTM for an
SRD991 positioner). Thereafter, you can select different functions and displays
of the vendor DTM. Refer to the DTM documentation for information on using
the interface.
Figure 7-18. Vendor DTM Tab
The screen layout of the Vendor DTM tab depends on the type of the
associated Vendor DTM. In Figure 7-18 for example, the associated DTM is
not a gateway DTM, and thus shows the nine tabs of this one DTM.
The gateway DTM in Figure 7-19 includes a DTM tree on the left for selecting
a DTM and an editing area on the right for interacting with the selected DTM.
DTMs have not yet been added to this gateway.
Figure 7-19. Gateway DTM in the Vendor DTM Tab
Gateway DTMs in the Vendor DTM Tab

A gateway DTM and module DTMs are used to model the structure of a remote
I/O system and the individual modules configured in the system. The gateway
DTM is associated with the based derived template for the remote I/O device,
and can be accessed in the Vendor DTM tab for the template and derived
devices. The gateway DTM serves as the device type manager for the main
device and as the host for DTMs that are used to configure and manage each
module to be installed. Connecting module DTMs to private protocol channels
of the device DTM allows the definition of the modules.
Some remote I/O modules allow connecting HART® devices to the module
channels. Field Device Editor also allows you to define this substructure by
connecting HART DTMs to the module DTM channels.
Field Device Editor also support creation a three-level DTM hierarchy in
which some module DTMs are also gateways and host other module DTMs.
The definition of the sub-structure underneath a device can be done on the

device template level and/or on the instance level.
Adding a DTM to a Gateway DTM

To add a DTM to a gateway DTM:
1. Click the Vendor DTM tab in the Field Device Editor, if the gateway
DTM is not already displayed.
2. Select the gateway DTM in the gateway tree on the left, and click Add
DTM below the DTM tree to open the Vendor Device Type Selection
dialog box (Figure 7-20).
Add DTM is only displayed for gateway DTMs.
The Vendor Device Type Selection dialog box lists only those DTMs that
can be connected to the selected gateway DTM.
When the HART device can connect to the selected gateway DTM, the
Add HART Device dialog box appears, as shown in Figure 7-21. This
dialog box allows you to add a HART Device to the selected gateway
DTM.
Figure 7-21. Add HART Device Dialog Box
3. For the Vendor Device Type Selection dialog box, proceed as follows:
a. Select a DTM in the list and click Details to display a dialog box with
additional information about the DTM.
b. Click Close in the Details dialog box to return to the Vendor Device
Type Selection dialog box.
c. Choose the desired DTM in the list and click Select in Vendor Device
Type Selection dialog box.
d. The Field Device Editor displays the Select Channel dialog box to
choose the channel to connect the new DTM with the gateway DTM
(Figure 7-22).
Figure 7-22. Select Channel Dialog Box
e. Select a channel and click Add.

The dialog box closes and the DTM is displayed under the gateway DTM
in the data tree as:
[channel name] <tag name> DTM device type name
For example, [Slot 6] <LB-4X05> FB 4205 HART Analog Output (4) in
Figure 7-24.
4. For the Add HART Device dialog box, proceed as follows:
a. Select a HART Template in the list and click Add.
b. The Field Device Editor displays the Select Channel dialog box to
choose the channel to connect the new HART instance with the
gateway DTM.
c. Select a channel and click Add.
The dialog box closes and the HART instance is displayed under the gateway
DTM in the data tree as:
[channel name] <tag name> HART device template name
Figure 7-23. Select Channel Dialog Box for HART Devices
To add a device DTM to a gateway:

1. Click the second-level gateway DTM in the DTM tree, and click Add to
open the Vendor Device Type Selection dialog box (Figure 7-24).
Add is active if the selected DTM is also a gateway DTM to which you
can add another DTM. Only DTMs compatible with the gateway DTM are
shown in the dialog box.
Note HART templates are displayed if the FDM for HART is installed
and the device to be added is a HART device. HART templates are also
displayed for selection if the gateway DTM allows adding HART devices.
2. Click the desired device DTM in the list, and click Add.
The dialog box closes and the selected device DTM is added under the
second-level gateway DTM in the DTMs tree.
Figure 7-24. Adding a Device DTM to a Second-Level Gateway
3. Double-click the newly added device DTM to open it in the editing pane
to the right.
The Vendor DTM tab shows the default display for the user interface.
Figure 7-25. Device DTM Opened in the Vendor DTM Tab
4. Right-click within the DTM display for a context menu of DTM functions.
The menu is dynamically constructed using the DTM interface, and is thus
specific to the device and DTM.
For DTMs that are added under a gateway DTM, you can also invoke the
context menu by right-clicking on the DTM name in the DTM tree on the
left.
Changes made to the device or gateway configuration are saved when you
select another DTM, or exit the Field Device Editor.
5. When you have finished configuration of the device, click in the

Field Device Editor title bar to close the editor, save changes to the device
and check in the devices.
Note After the changes are checked in, the HART instances that have been
added are displayed in the Network view underneath the PROFIBUS device
instance. The PROFIBUS Editor supports several levels of children (nested
communication) with HART device instances underneath. The HART
instances appear in the Network view in this format:
[Parent_channelname].<childLevel1_tagname>.<child1_channelname>.
<ChildLevel2_tagname>.<child2_channelname>.<HARTdevice_tagname>
For example, the name for the HART SRD991 device connected to Channel 1
of an LB4102 HART analog output module located in Slot8 of LB remote IO is
displayed in the network view as: Slot8.LB4102.
Channel1.SRD991[$SRD991].
Deleting a Module DTM

You can delete a DTM within the sub-structure, but you cannot delete the root
gateway DTM.
To delete a DTM from the tree view structure:
1. Select the DTM and press the Delete DTM button.
2. Click OK to delete the selected DTM (or click Cancel to keep the selected
DTM).
217
C H A P T E R 8
Field Device Manager
The Field Device Manager tab in the Field Device Editor contains a universal
PROFIBUS device DTM which you can use for online access to device data,
diagnostics and configuration of DPV1 parameters. The tab also provides links
to documents and pictures, and a note pad for recording information about the
device type or a specific device.
This chapter describes how to select parameters for Field Device Manager
displays and otherwise customize the user interface for a device. Typically,
these tasks are performed offline during device configuration, but can be done
after deployment when the Field Device Manager is online to the physical
device. The setup work can also be done at the template level to provide the
same custom features for the devices derived from the same template.
Note Unless otherwise noted, the term device in this chapter applies to both
device templates and device instances.
Contents
• Overview
• Input and Output Tabs
• Diagnostic Tab
• Watch Tab
• Configuration Data Tab
• Device Parameter (DPV1) Tab
• Compare Tab
• Customize Tab
Overview
To access the Field Device Manager:
1. Double-click the device in the Network view or the device template in the
Template Toolbox to open the object in the Field Device Editor.
2. Click the Field Device Manager tab.
A dialog box advises you to wait while the universal PROFIBUS DTM is
loaded. The editor then displays the Identification tab (Figure 8-1).
218 8. Field Device Manager
Auto Online Option

The Field Device Manager can be set to go online automatically when the
DTM is loaded.
• If the Auto Online option is enabled, the DTM goes online to the device
and the Go Offline button is enabled.
• If the Auto Online option is not enabled, Field Device Manager starts in
offline mode and the Go Online button is enabled.
If the device has not yet been deployed, the Go Online and Go Offline buttons
in the top right are disabled, as is the case when you open a device template in
Online/Offline buttons
Field Device Manager Toolbar
Check this box to enable

Auto Online
Figure 8-1. Enabling the AutoOnline Option
To enable or disable Auto Online:

1. Choose Tools > User Preferences from the IDE main menu.
8. Field Device Manager 219
2. Check or uncheck the Auto Online box in the User Preferences dialog box
(Figure 8-1) to enable or disable the feature, and click OK.
The preference is implemented the next time you open the Field Device
Manager or the FBM Manager.
Field Device Manager Toolbar

Table 8-1 describes the buttons in the upper right corner of the Field Device
Manager. These tools are available for these tabs.
Table 8-1. Field Device Manager Icons
Icon Description
The multi-colored cube indicates that the device is online.
The cube tumbles when the FBM is communicating with
the device.
The cube is displayed in grayscale when the device is
offline.
The yellow exclamation point on an orange triangle
indicates that there are detected error messages in the Error
Monitor (Figure 8-2).
The icon is black and grey when no detected errors are
reported in the Error Monitor or the messages have been
acknowledged, that is, cleared from the monitor.
Starts HTML help for the Field Device Editor.
Opens the Notes window for the device. Notes entered for a
template are copied to the devices that are derived from the
template.
This icon is displayed when the slave device is online and
the host FBM is performing cyclic data exchange with the
device.
This icon shows the progress of an upload from the
device or a download to the device.
Error Monitor
A yellow exclamation point on an orange triangle in the right corner of the
Field Device Manager tab alerts you that there is a least one unacknowledged
error detected in the FBM’s communication with the device.
To view and acknowledge detected error conditions:
1. Click to display the Error Monitor (Figure 8-2).
The monitor consists of a table of the messages with the columns

described in Table 8-2.
Table 8-2. Messages in the Error Monitor
Column Description
TimeStamp Date and time when the detected error occurred
Parameter Parameter name and sub-name, and index and sub-index or
slot and index
Description Text supplied by Field Device Manager
Error The message type can be Error, Warning or Information
Operation Indicates whether the detected error is for a Read, Write,
Name Connect or Disconnect operation
2. Check or un-check the three Options boxes in the lower left corner of the
monitor and the click Refresh to select the kind of messages to be
displayed.
For example, you can un-check Warning and Information and click
Refresh to display only Errors. Filtering messages from the display does
not clear the messages.
The messages are not maintained in the Error Monitor after the Field
Device Manager is closed.
3. Perform these steps to save the messages:
a. Click Copy to Clipboard to place the messages on the Windows
clipboard in a tab-delimited format.
b. Open a text editor or spreadsheet application, and paste the message
text into the document or worksheet.
c. Print and/or save the file.
4. Click Clear to acknowledge the detected error conditions and remove the
messages from the monitor.
The Error Monitor icon changes to black and white.
5. Click Close to close the window but maintain the messages until the Field
Device Manager is closed.
Click this button to copy

messages to the clipboard
to document activity Click this button to clear
all messages from the
Error Monitor
Check the type of messages
to be included
Figure 8-2. Error Monitor
Note Pad
Graphics and Links on the Identification tab provide general information about
device type, while the Notes feature enables you to record information about
the specific device, including detected error messages, adjustments made to the
PROFIBUS networks, and so on.
To record information about the device:
1. Click Notes in the Field Device Manager toolbar.
2. Type the comments in the Notes window (Figure 8-3) and/or use Ctlr+V
to paste in text copied to the clipboard from the Error Monitor or other
sources.
Figure 8-3. Note Pad for a PROFIBUS Device
3. Click Save to keep the changes and click to close the Notes window.
Field Device Manager Tabs

Field Device Manager includes these standard tab pages:
• Identification displays information about the specific device including
the device manufacturer and type, hardware and software versions, and so
on. The tab also provides user-configured links to images and documents
that provide technical support.
• Input and Output provide real-time displays of the parameters defined in
the Data Definition tab (or the Vendor DTM if the parameters were
configured with the device manufacturer’s device DTM).
• Diagnostics displays diagnostic messages specified in the GSD and those
which you define in Data Definition tab based on either device diagnostics
or DPV1 device parameters. Definition of messages is discussed in
“Diagnostic Tab” on page 229.
• Watch allows you to track I/O parameters using a data table and a trend
display.
• Configuration Data, which is displayed only when the Field Device
Manager is online to the device, compares the configuration data in the
device with the data set in the Galaxy.
• Customize provides tools for adding custom tabs and parameter groups,
setting access permissions for Field Device Manager displays and
functions based on the user’s log-in information, and setting up downloads
for DPV1 device parameters.
Field Device Manager also displays these tabs for devices that support DPV1
functions:
• Device Parameter (DPV1) displays selected device parameters in a grid
format and a trend display. The tab enables you to upload and download
parameters that are defined as writable. The Device Parameter (DPV1) tab
is only shown if the device GSD indicates support for DPV1 functions.
• Compare enables you to identify differences between DPV1 device
parameter values in the Galaxy and the values read from the device, and
then reconcile the two sources by either uploading or downloading
selected parameters.
The Tab Configuration dialog box, which is accessed from the Customize tab,
enables addition of other tabs using one of three formats: Input/Output,
Watch and Configuration. The Configuration selection provides the format
and functions of the Device Parameter (DPV1) tab.
Whether a tab is visible and enabled depends on the FDT roles assigned to the
user and the access specified for those roles in the Set Permissions dialog box.
Refer to “Security” on page 45 and “Setting Access Permissions” on page 247
for additional information on user access to Field Device Manager tabs.
Use of Color in Field Device Manager Displays

Table 8-3 describes the use of background colors in parameter value fields in
the Field Device Manager to indicate various states.
Table 8-3. Use of Fill Colors in Field Device Manager

A light gray background in a database value indicates an
initial value, one that has not been changed in the Galaxy and
has not been downloaded to the device.
Values in the Galaxy data set are displayed in yellow when
they have been changed, but not yet downloaded to the
device.
A white background indicates that the value in the Galaxy
matches the value in the device, such as when a parameter
has been successfully downloaded to the device.
A cyan value field indicates that the value has not yet been
read from the device or from the Galaxy. This is generally a
temporary condition.
Red indicates that there has been a detected failure to
download the value. For example, when a parameter is
locked in the device template, the value cannot be
downloaded. The value is displayed on a red background
when a download is attempted. Detected errors are displayed
in the Control Editors Output view.
Magenta indicates that there has been a detected failure to
upload the value. For example, when a parameter is locked in
the defining template, the value cannot be changed by an
upload. The device value is displayed on a magenta
background when an upload is attempted. Detected errors are
displayed in the Control Editors’ Output view.
A gray background is used to indicate a read-only value.
Note If you are not able to distinguish between colors in the Field Device
Manager displays, contact your Schneider Electric Process Systems
representative for information on enabling the software to use symbols as state
indicators.
Identification Tab
Figure 8-4 is an example of the Field Device Manager Identification tab. The
device has not yet been deployed, and a document link is being added to those
already specified for the tab.
Figure 8-4. Setting Up a Document Link on the Identification Tab
Field Device Manager provides device identification data in the upper part of
the tab, and controls for graphics and documents links in the lower left. The
selected graphics file is displayed to the right of the controls; linked documents
are opened in a separate window.
Identification Data
When the device is offline, the identification data is taken from the device
configuration in the Galaxy, which includes data extracted from the GSD file
(such as Tag) and entered in the General tab for the device (such as Address).
When the device is offline, the information is labeled GSD data, as shown in
Figure 8-4.
When the device is online the Identification data is uploaded from the device,
and the information is labeled Device data. If the uploaded data differs from
the data in the Galaxy, Field Device Manager prompts you to update the
Device Information fields in the General tab. The device information is

downloaded to the FBM222 when the device ECB is deployed, and is available
for System Manager displays.
Table 8-4 describes the GSD data and Device data fields.
Table 8-4. Device Data in the Identification Tab
GSD data Device data

Field when the device is offline when the device is online
Tag Device tag read from the GSD file The tag is read from connected PA
when the template is bound to GSD and I&M devices. Blank for other
file and is displayed as Device Model devices
Name in the GSD Information in the
General tab.
Address Configured address read from the The network address of the connected
device configuration in Galaxy device
Ident No PROFIBUS ID Number is read from PROFIBUS ID Number uploaded
the device configuration in the Galaxy from the connected device
Manufacturer ID Vendor name read from the device Read from connected PA and I&M
configuration devices. Blank for other devices
Product Name Read from the device configuration in Read from PA devices. Blank for
the Galaxy. This information can be other devices
uploaded from the device when the
device goes online
Order ID Initially blank. This information can Read from I&M devices. Blank for
be save to the configuration if it is other devices
uploaded from the device when it
goes online
Hardware Revision Read from the device configuration in Read from connected PA and I&M
Software Revision the Galaxy. This information can be devices. Blank for other devices
uploaded from the device when the
Serial Number device goes online
Graphics and Links

Use the Graphics and Links controls in the Identification tab to give users
access to documents and illustrations with specifications, plant standards,
troubleshooting tips, or other useful information.
The Graphics pane provides tools for configuring references to graphics files
and displays the already configured file references. When you double-click on
a file name, the picture is displayed in the pane to the right of the Graphics and
Links controls. The linked graphics files can include bitmaps, JPEGs, and
images in other common graphics formats.
The Links pane in the lower left provides tools for configuring document links
and displays the links already configured. When you double-click on a link, the
document is opened up in a separate window. The linked documents can
include Adobe Acrobat® Reader PDFs, Word documents, spreadsheets, or
help files. When selected, a linked document opens in a separate window in its
native application. Windows displays a dialog box for selecting a program if

the file’s native application is not available.
Figure 8-4 shows two graphics file references and three document links
already configured for RIO002 and a fourth document being selected in the
Add Link dialog box.
Field Device Manager does not store copies of the files with the device
information, but only the entire path name and an alias for each file reference.
The files themselves need to be maintained in a shared drive that is commonly
accessible to the Foxboro Evo Control workstations that accesses the device.
The file needs to be specified using a network path (for example,
\\Atibazar2\... in Figure 8-4).
The files references are automatically included in Galaxy backups and exports
of the template; however, the files themselves are not included and should be
backed up separately.
The padlock icon to the left of each graphics file and document link indicates
wether the file reference can be changed or is locked in the device’s defining
template and therefore cannot be changed (see “Locking and Inheritance” on
page 171). In Figure 8-4, for example:
• The document Wago750-333 data sheet was configured and locked in the
device template and cannot be changed ( ) in RIO002.
• The link TS641_Modules was also configured in the template, but was
not locked. It can be modified ( ) in RIO002.
• NW7_IO has been configured in the device and can therefore be modified
( ).
The tools at the top of each pane enable you to edit an existing file selection,
delete a link or image, and select a new file. The commands are also available
in a context menu for each pane. The Links instructions that follow also apply
to the Graphics pane.
To configure a document link:
1. Click the Add button above the Links box to open the Select File dialog
box (Figure 8-4).
2. Click to right of the first field in the dialog box to browse for and
select the file using a Windows Open dialog box.
The first field in the File Select dialog box shows the entire path name of
the file. The Alias field shows how the file is named on the Device
Identification tab.
3. Enter a new name in the Alias field if desired.
4. Click OK.
The selected alias is listed in the Links pane.
5. Double-click the alias to test the link.
To change a link:
1. Select the link and click the Edit button above the Links list to open the
Select File dialog box.
2. Change the path and/or alias, and click OK.
To delete a link:
• Select the link and click the Remove button above the Links list box.
Input and Output Tabs

The Input tab (Figure 8-5) and the Output tab display the parameter name,
device value, status and parameter description for selected input parameters
and output parameters, respectively.
The selected parameters are organized by module.
• Click to the left of a module or device name to display its parameters.
• Click to collapse the module or device display and hide the parameters.
The parameters are defined in the Field Device Editor Data Definition tab (see
“Defining Input and Output Parameters” on page 188).
Figure 8-5. Input Tab with Raw Data Dialog Box
When Field Device Manager is online to the device, the DeviceValue and
StatusValue fields are updated at a user-configured interval. The default
interval is 10 seconds.
• Click Raw Data in the lower left corner of the tab to open a dialog box
showing the raw data from the input or output cyclic data stream
(Figure 8-5).
When the Field Device Manager is started for the first time for a device
template, the Input and Output tabs show the parameters already defined for
the device. After this point, new parameters are not automatically added to the
tabs as they are defined. However, you can add the newly defined parameters
using the Update Parameters dialog box, as well as remove parameters and
change the update period.
When you create a device instance or derive a template, the Control Editors
copy the tab setups from the defining template to the instance or derived
template. Each tab setup can be locked in the template so that it cannot be
modified in the device instances and that changes at the template level are
inherited by the devices already created from the template.
To add parameters and set the update period:
1. Click the Customize button in the lower right corner of the tab to open the
Customize Parameters dialog box.
Figure 8-6 shows the dialog box for an Input tab. The Customize
Parameters dialog boxes for the Output tab and the custom tabs using the
Input/Output format are identical to one shown in Figure 8-6.
Figure 8-6. Selecting Parameters for an Input Tab
The list on the left is the pool of parameters from which you can select
parameters for inclusion in the Tab Parameters list on the right. You can
narrow the list by selecting a parameter group. Parameters groups are user-
defined subsets of the parameters configured for the device. See “Setting
Up Parameter Groups” on page 243 for information on creating these
groups.
2. Use the Show pull-down list to select All or a parameter group for the
Parameter Pool.
3. Select parameters in the pool and click on the right to add them to the
Tab Parameters list.
Use Shift+click to select a group of contiguous parameters; use
Ctrl+click to select non-contiguous parameters.
4. Select parameters in the Tab Parameters list and click to exclude them
from the tab.
Note You can also add a parameter to the tab by double-clicking the
parameter in the parameter pool. Likewise, you can remove a parameter
from the tab by double-clicking the parameter in the Tab Parameters list.
5. Enter the update interval in seconds in the Update period box in the lower
right corner or use the spinner buttons to increase or decrease the period.
The range is 1 to 120 seconds.
6. Click OK to apply the selection, set the rate and close the dialog box (or
click Cancel to close the dialog box without changing the tab).
Diagnostic Tab
The Diagnostics tab (Figure 8-7) displays messages that show diagnostic status
of the device and status changes. The messages include those specified in the
GSD file, as well as user-defined messages. Diagnostic messages are defined
in Field Device Editor Data Definition tab (see “Editing Diagnostic Messages
and Parameters” on page 198).
Field Device Manager begins accumulating the messages when it goes online
to the device and the Diagnostics tab is displayed. Field Device Manager scans
for the messages at a rate configured for the tab, and displays the timestamp in
bold if the message was included in the latest scan.
When you go to another tab, Field Device Manager stops retrieving messages,
but keeps the messages already received. The message data is retained until the
buffer reaches a specified number of messages, at which point the oldest
message is discarded as each new one is received.
Field Device Manager discards the messages when Field Device Manager is
closed.
The background color for each message identifies the user-defined status of the
message as shown in Table 8-5.
Figure 8-7. Customizing the Diagnostic Tab
Table 8-5 describes the information displayed in the tab.
Table 8-5. Field Device Manager Diagnostic Tab
Column Description
Timestamp The latest time when the Field Device Manager received the message. When
Field Device Manager receives a particular message for the first time, the
message is displayed on the first available row in the tab. When the same
message is received again, the timestamp is updated and displayed in bold. If
the timestamp for a message is not in bold, the message was not found in the
latest update.
Name The message text as configured in the Data Definition tab.
Table 8-5. Field Device Manager Diagnostic Tab (Continued)
Column Description
Status User-selected status for message:
• OK (green)
• Out-of-Specification (yellow)
• Maintenance Request (blue)
• Failure (red)
• Warning (orange)
Category User-selected diagnostic condition:
• Process
• Communication
• Device Error
Description A description of the condition and a recommended action for the diagnostic
Action condition, as configured in the Data Definition tab.
The messages can be sorted according to the data in any of the columns.
• Click a column head to sort the rows on the column.
• Click the column head a second time to reverse the sort order.
Three buttons in the lower left corner are active when the Field Device
Manager is online to the device:
• Click Raw Data to open a dialog box showing the raw diagnostic data
from the device (Figure 8-7, left side).
• Click Refresh to retrieve the current messages. Use Refresh for on-
demand retrieval when the update rate is 0.
• Click Clear All to empty the message buffer and remove the messages
from the display.
Customizing the Diagnostic tab involves specifying the update period and the
size of the message buffer.
To customize the Diagnostics tab:
1. Click Customize button in the lower right corner of the tab to open the
Customize Parameters for Diagnostics dialog box (Figure 8-7, right side).
The locked status icon at the top of the dialog box indicates whether the
specifications can be edited ( or ) or the specifications are locked in
the defining template ( ), as described in “Locking and Inheritance” on
page 171.
2. Specify the refresh rate (in seconds) for the display in Update period.
The range is 1 to 120 seconds. The default is 10 seconds. Enter 0 if you
want the display to be updated only when you click Refresh.
3. Enter the maximum number of messages that can be stored in the message
buffer for this device.
When the maximum number is reached, the oldest message is deleted as

each new message is received. This number represents the maximum
number of unique messages that are stored. When Field Device Manager
receives a message already in the buffer, it only updates the timestamp for
the message; the message count is not increased. The range for the buffer
is 1 to 1000. The default is 100 entries.
4. Click OK to apply the changes and close the dialog box (or click Cancel
to close the dialog box while leaving the update period and buffer size
unchanged).
Watch Tab
Use the Watch tab (Figure 8-8) to monitor up to eight different parameters. The
tab consists of two sections:
• A data table in the upper portion with up to eight columns representing the
selected parameters and each row displaying the value read from the
device at the timestamp in the left column. When the grid is filled, the
values scroll up to display the next reading.
• A trend display in lower portion of the tab provides a trace for each
parameter value, with the time on the x-axis and scales for the values on
the y-axis. The traces build from the right, with the oldest value scrolling
out of view when the traces reach the left edge of the display. Separate
scales are shown for each parameter in the same color that was selected for
the trace.
You can select up to eight parameters with an analog value for display in the
Watch tab. The values are updated at a user-set interval and stored in a buffer,
which allows you to display earlier values in both the grid and trend using the
scroll buttons in the lower left corner of the tab. The number of data points
stored in the buffer is user-set.
In addition to the configuring the standard tab, you can create custom Watch
tabs which have the same functions and format of the standard tab. See
“Creating New Tabs” on page 245.
Figure 8-8. Field Device Manager Watch Tab
To select parameters for a Watch tab:

1. Open the device in Field Device Manager, click Watch to display the tab,
and click the Customize button in the lower right corner to open the
Customize Parameters for Watch tab dialog box (Figure 8-9).
The locked status icon at the top of the dialog box indicates whether the
specifications can be edited ( or ) or if they are locked in the defining
template ( ), as described in “Locking and Inheritance” on page 171.
As with dialog boxes for customizing the Input and Outputs tabs, this
dialog box displays a parameter pool on the left and the selected
parameters on the right.
2. Use the Show pull-down list to choose All (parameters defined for the
device) or one of the user-defined parameter groups to populate the
parameter pool.
3. Select parameters in the pool and click on the right to add them to the
Watch Parameters list.

You can add only eight parameters to the Watch Parameters list.
4. Select parameters in the Watch Parameters list and click to exclude

them from the tab.
Figure 8-9. Customizing the Watch Tab
5. Edit the display attributes for each parameter in the Watch Parameters grid
as described in Table 8-6.
Table 8-6. Watch Parameter Display Attributes
Y axis Choose the location of the trend scale (y-axis) for the
parameter, one of the four positions on the left or one of the
four on the right. Y0_left is the left edge of the trend area,
Y1_left is positioned to the left of Y0_left, and so on.
Color Use the pull-down list to choose the color of the trace and
its y-axis scale.
Min Specify the lowest value displayed, if you are not enabling
Auto min.
Max Specify the highest value displayed, if you are not enabling
Auto max.
Auto min Check the box to have Field Device Manager automatically
determine the minimum of the y-axis scale based on the
parameter attributes.
Title Enter a title for the parameter’s y-axis scale.
Auto max Check the box to have Field Device Manager automatically
determine the limit of the y-axis scale based on the
parameter attributes.
Axis Thickness Set the thickness (in points) for the y-axis scale. The range
is 1 (the default) to 5.
Line Thickness Set the thickness (in points) for the trace. The range is 1 (the
default) to 5.
Show Labels Check the box to display the parameter value on the trace at
each tick mark.
6. Use the controls in the X Scale group to specify how points are displayed
and stored (Table 8-7).
Table 8-7. X-Axis Controls
Field Description
Refresh interval Specify the rate in milliseconds at which the values are read
from the device to update the grid and trend display. The
range for the interval is 1 to 120000 ms; the default is
10000 ms (10 seconds). Enter 0 to disable periodic
updating and retrieve current values when you click the
Refresh button.
Absolute time Check the box to have the timestamp be the time of day;
display uncheck the box to display the time relative to the start of
the Watch.
Table 8-7. X-Axis Controls (Continued)
Field Description
Display range Specify the time interval (in milliseconds) represented by
the ticks on the x-axis. The range 1 to 120000 ms. The
default is 10000, that is, the ticks represent 10 second
intervals.
Max Display Enter the number of ticks to specify how many data points
Buffer are maintained in the buffer. The range is 5 to 1000000.
When set to the default of 5 and when the display range is
set to the default 10000 ms, the buffer holds 50 seconds
worth of data.
7. Click OK to apply the changes made and return to the Watch tab (or click
Cancel to close the dialog box without applying the changes).
To monitor the selected parameters:
1. Click the Go Online button if Field Device Manager is not already online
to the device.
Field Device Manager reads the selected values from the device and
displays the data in the top row of the data table and begins the trace on the
right side of the trend. Field Device Manager repeats the upload at the
user-specified interval, adding new time-stamped rows to the data table
and building the trace to the left.
2. Click in the display control buttons to start the trend.

The button changes to a Pause button ( ).
3. Drag the border between the data table and the trend up or down to
increase or decrease the height of the trend display.
4. Click on trace to show the line label; click the line a second time to hide
the label.
5. Use the scroll buttons in the lower left corner of the trend to view older
data values that have scrolled out of view:
• Click to show the oldest values in the history.
• Click to scroll the trend one tick mark to the left to view earlier
data.
• Click to scroll the trend one tick mark to the right to view more
current data.
• Click to show the latest trend values.
Configuration Data Tab

The Configuration Data tab (Figure 8-10), which is visible when the Field
Device Manager is online to the device, compares the device configuration in
the Control Editors with the configuration data in the device.
When the tab is selected Field Device Manager reads the module configuration
data from the Galaxy and displays the values in the Instance Configuration
column on the left and uploads the configuration data from the device and
displays those values in the Device Configuration column on the right.
The fill color of a row changes to dark green when the values differ.
Radio buttons below the compared data allow selection of Bin (binary),
Hexadecimal and Decimal display formats.
To compare the module configuration in the Galaxy with the device
configuration:
1. Click Go Online if Field Device Manager is not already online with the
device.
2. Click the Configuration Data tab to compare the configuration data from
both sources.
Figure 8-10. Field Device Manager Configuration Data Tab
3. Click one of the three radio buttons in the bottom left to select the format
of the data: Bin, Hexadecimal or Decimal.
The display does not automatically refresh at a specific interval.
4. Click Refresh to re-read the configuration data from the device and the
Galaxy.
Device Parameter (DPV1) Tab

The Device Parameter (DPV1) tab provides two displays of selected DPV1
device parameters:
• Configuration Area in the upper portion of the screen shows the name,
value, lock status and description of the selected parameters in a format
similar to that of the Input and Output tabs.
The Configuration area only shows device parameters that are defined in
the Data Definition tab. If a vendor DTM is associated with the device, use
the DTM to configure the DPV1 device parameters.
Buttons at bottom of the Configuration area enable you to upload values
from the device and download changed parameters to the device. You
download only those parameters whose Access attribute is either Write or
Read/Write.
Caution Refer to the device documentation for information on the use of its
DPV1 parameters before configuring and downloading the parameters.
• Watch Area in the lower portion of the tab shows a history of the selected
values with a trend display on the left and a data table on the right. The
functions and customizing of this area are the same as those for the Watch
tab described on page 242.
To resize the trend and data table:
• Drag the top edge of the Watch Area up or down to adjust the height
of the trend and data table.
• Drag the border between the trend and data table to the right or left to
adjust the width of the two displays.
Parameter selection for the two areas are independent of each other.
Configuration Area
Drag the line up or down

to change the height of
the Watch area
Watch Area
Drag this border right

or left to change the
trend width
Figure 8-11. Device Parameter (DPV1) Tab
Table 8-8 describes the functions buttons in the two areas on the Device
Parameter (DPV1) tab.
Table 8-8. Device Parameter (DPV1) Tab Buttons
Button Description
Configuration Area
Upload All Uploads the values of DPV1 device parameters from the device, updating the
DPV1 parameters that have read/write access and that are unlocked or locked
by the device. Parameters that are locked in a defining template are not
updated.
Table 8-8. Device Parameter (DPV1) Tab Buttons (Continued)
Button Description
Download Downloads the values of parameters selected in the tab to the device. The
parameters need to have read/write access to be downloaded.
If you are tracking changes to the control database using the Control Editors
link to FoxCTS software, the Change Tracking dialog box prompts you to
enter a reason for the download. The Control Editors do not proceed with the
download until you make an entry in the dialog box. See Chapter 12, “Change
Tracking” for details. To finish the download:
Download All Downloads the DPV1 device parameters that are on the device’s Download
list (see “Setting Up Downloads” on page 249).
Customize Opens the Customize Parameters for Device Parameter (DPV1) dialog box
for adding parameters. The dialog box has the same parameter selection tools
as the customize dialog boxes opened from the Input and Output tabs.
However, it does not include the controls for the input interval.
Watch Area
Refresh Reads the parameter values from the device.
Trend Controls Scrolls the trend display to show different segments of the history, as
described for the Watch tab on page 242.
Customize Opens the Customize Parameters dialog box for Watch Area of the Device
Parameter (DPV1) tab. The dialog box is the same as that used for
customizing the Watch tab; see “Watch Tab” on page 232.
Parameters selected for the Watch area can different from those selected for
the Configuration area.
Compare Tab
The Compare tab (Figure 8-12) displays the DPV1 device parameter values in
the Galaxy and values read from the device so that you can align the two data
sets.
Field Device Manager displays the tab if the device supports DPV1 functions
and if the user is assigned to a role that has read/write access to DPV1 device
parameter values.
When the Compare tab is selected for the first time in the current Field Device
Manager session, the device value fields display * on a cyan background
indicating that the values have not yet been uploaded from the device. The
gauge in the Field Device Manager toolbar show the progress of upload.
When the upload is done, Field Device Manager compares the parameter value
in the Galaxy with the uploaded value from the device. If the values agree for a
particular parameter, the fill color for the value fields is white. If the values
differ, the fill color is a dark green.
To align the two data sets:

1. Click Go Online if Field Device Manager is not already online to the
device.
2. Click the Compare tab, and choose All (DPV1 device parameters) or one
of the parameter groups from the Show pull-down list to select parameters
for the tab.
Only DPV1 device parameters are added to the display.
3. Wait for the Progress gauge ( ) to fill with green

indicating that the upload is done.
4. Click Differences Only to show only those instances where the device
does not agree with the Galaxy.
You can also focus the display by selecting rows and clicking Selection
Only.
5. Select those parameters you want to change, and click Upload Sel to align
the Galaxy with the device values or click Download Sel to align the
device with the configuration in the Galaxy.
Only writable parameters are downloaded to the device.
Figure 8-12. Field Device Manager Compare Tab
Customize Tab
The Customize tab (Figure 8-13) includes four buttons to access tools for
customizing the Field Device Manager displays for a device or device
template:
• Group Parameters for defining and modifying parameter groups that
facilitate selection of parameters for standard and custom tabs
• Define Tabs for setting up a custom tab, and modifying the parameter
selection and update period for an existing tab
• Set Permissions to configure user access to Field Device Manager
displays and functions based on the user’s login information
• Setup Download that specifies which DPV1 parameters are to be
downloaded to the slave device.
Figure 8-13. Field Device Manager Customize Tab
Setting Up Parameter Groups

When you customize a tab, you select parameters from a pool of the
parameters that were configured on the Data Definition tab for the device. You
can narrow that pool by selecting a parameter group from a pull-down list
located in the lower left corner of the tab.
Field Device Manager comes with four suggested parameters groups: Inputs,
Outputs, Device Parameters, and Diagnostics. Initially, these groups contain
parameters that are defined in the corresponding tab in Data Definition. You
change the parameter selection using the Group Parameters dialog box
(Figure 8-14), which also enables you to set up your own groups (such as RTD
or Positioner Diagnostics) or to remove a group.
To define parameter groups for the device:
1. Click the Customize tab if it is not already selected and click the Group
Parameters button to open the Group Parameters dialog box
(Figure 8-14).
Figure 8-14. Adding Parameters to a Group
2. Select the group to be populated using the Group pull-down list.

The padlock icon to the right of the group selection box indicates whether
the group configuration is locked in a defining template or if it can be
changed in this template or device. See “Locking and Inheritance” on
page 171.
3. Select parameters in the Parameter pool on the left and click to add
them to the Selected Parameters list.
You can also add a parameter by double-clicking the parameter name.
4. Select parameters in the Selected Parameter list and click to exclude

them from the list.
You can also remove a parameter by double-clicking the parameter name
in the Selected Parameters list.
5. Click the Add Group button at the top of the dialog box to open the Add
Group dialog box (Figure 8-15).
The dialog lists the already configured groups. You can delete any of these
by selecting the group name and clicking the Remove button at the bottom
of the dialog box.
a. To rename any group in the list: Click the group name.
b. Click the name a second time.
The name appears in blue indicating that the name can be edited.
c. Edit the name and press Enter.
6. Click the Add Group button to place a default group name (New Group,
New Group1, and so on) in the first available row in the dialog box.
7. Select and rename the new group.
8. Make other changes to the group list.
9. Click OK to apply the changes and close the dialog box, and then click
OK if a Warning dialog box prompts you to commit the changes to the
group (Figure 8-15, right side).
Figure 8-15. Renaming a Custom Parameter Group
10. Select parameters for the new group, and then click OK to close the Group
Parameters dialog box and return to the Customize tab.
Creating New Tabs

To create a new tab page for a device:
1. Click the Customize tab if it is not already selected, and click Define
Tabs to open the Tab Configuration window (Figure 8-16).
The window includes a table showing parameter group usage by the
standard and custom tabs configured for the device.
The Group Name column includes the four standard parameter groups
Inputs, Outputs, Device and Diagnostics, plus any user-configured groups
(RTD, New Group1 and New Group2 in Figure 8-16). See “Setting Up
Parameter Groups” on page 243 for information on creating a parameter
group.
The Details button below each tab name opens the Customize Parameters
dialog box for the tab type.
Figure 8-16. Tab Configuration Dialog Box
Note There are two columns for the Device Parameter (DPV1) tab, one
for the Configuration area, the other for the Watch area. Each of these
parts has its own Customize Parameters dialog box. See Figure 8-11 on
page 239 for an example of the two part layout.
2. Click Add Tab at the top of the Tab Configuration dialog box to open the
Add Tab dialog box (Figure 8-17).
Figure 8-17. Setting Up a New Tab
The dialog box lists the existing tabs and their type:
• Input/Output for tabs with the format and functions described in
“Input and Output Tabs” on page 227
• Watch using the model discussed in “Watch Tab” on page 232
• Configuration to use the features and two-part layout of the Device
Parameter (DPV1) tab described on page 238.
Each of these types provides a model for setting up the new tab.
3. Click Add Tab to insert a default name such as New Tab or New Tab1 in
the next available row in the dialog box, and use the pull-down list in the
Tab Type field to select the tab features and format.
In Figure 8-17, the user is selecting Watch tab type as the model for the
new tab.
4. Click the default name twice to make the field editable, change the name
and press Enter.
At this point you can add other custom tabs or edit the ones already
defined.
• Select any custom tab and click Remove to help eliminate the tab
from the device configuration.
• Select any custom tab and rename it using the method as described.
You can rename or remove a custom tab at any time, but you cannot
rename or delete a standard Field Device Manager tab.
5. Click OK in the Add tab dialog box to return to the Tab Configuration
window.
6. Click the Details button for the new tab to open the Customize Parameters
dialog box, add parameters, and otherwise configure the tab.
7. Click OK to apply the changes, close the Customize Parameters dialog
box, and return to the Tab Configuration dialog box.
Note If you add a tab with the Configuration type, that is, the Device
Parameter (DPV1) format, the new tab is displayed in two columns in the
Tab Configuration window. The Configuration and Watch areas need to be
customized separately.
8. Click Close in the Tab Configuration dialog box to return to the Field
Device Manager Customize tab.
Setting Access Permissions

The Set Permissions window enables you to restrict access to specific
parameters and Field Device Manager functions and displays based on the user
log-in information. The access permissions are enforced when security is
enabled, as described in “Security” on page 45. Normally, only a user with the
Administrator role can access the Set Permissions window.
To change user access to a device type:
1. If security is enabled, log into the Control Editors and open the Galaxy as
a user with FDT Administrator privileges.
2. Double-click the device template in the Template Toolbox or the device in
the Network view to open the object in the Field Device Editor, and then
click the Field Device Manager tab.
3. Go to the Customize tab, and then click the Set Permissions button on the
tab to open the Set Permissions dialog box for the device (Figure 8-18).
Permissions can be locked

in the device template.
Select the access setting

from the pull-down list.
Modified settings are

displayed in yellow
until they are saved
(when you click OK).
Select the access setting

from the pull-down list.
Click OK to save changes

and close the dialog box.
Figure 8-18. Setting Access Permissions in a Device Template
The dialog box includes three tables:

• Parameters listing the parameters that are configured for the device.
Access choices in this table are ReadWrite (for DPV1 device
parameters that are defined as read/write parameters), ReadOnly and
Hidden.
• Screens, that is, Field Device Manager tabs, including customer-
defined tabs, and parameter groups. Choices in this table are Hidden,
Disabled and Enabled.
• GUI Functions, including customizing tabs and downloading
parameters to the device. Choices in this table are Hidden, ReadOnly
and ReadWrite.
Columns in the table display the permissions granted to the four FDT roles
used in Field Device Manager.
Permissions that have been modified are displayed on a yellow field until
you exit the dialog box (either saving the changes by clicking OK or
discarding them by clicking Cancel).
4. Use the pull-down lists in a cell to define the access to the category for the
FDT role.
5. Make other changes as needed, and then click OK the in bottom right
corner to close the dialog box and return to the Customize tab.
Setting Up Downloads
• The Setup Downloads button is available on the Customize tab for device
templates and device instances. The function enables specification of
Parameters that are to be downloaded
• The order in which they are downloaded
• Pauses between the download of individual parameters
• Whether to upload parameters at the completion of a download.
The Download dialog box (Figure 8-19) is used to configure two lists:
• The Writable parameter list is selected from a pool of available
parameters for the device. These parameters are downloaded only if the
parameter value has been changed in the Galaxy (the Database Value field
is yellow). They are not downloaded as part of device commissioning or a
Download All command unless they are also included in the Download
List.
The Writable parameter list is also used to determine the order and
timing of parameter downloads.
• Download List, selected from the Writable Parameter list, specifies
parameters that are included by default in downloads initiated when the
Download All button is selected from the Device Parameter (DPV1) tab
and when the device is commissioned (refer to “Commissioning Devices”
on page 154).
To review and set up downloads for a device:
1. Select the Field Device Manager tab if it is not already open and click the
Customize tab.
2. Click Setup Downloads to open the Customize Device Parameters for
Download dialog box (Figure 8-19).
The dialog box consists of three lists: the Parameter Pool on the left, the
Writable Parameters list in center, and the Download list on the right.
The Parameter Pool includes the read-write parameters in the device
configuration. Many of theses parameters probably use the default values
and inclusion in the list may make downloads unnecessarily long. Thus,
the Writable Parameter and Download Lists are initially empty.
Download Setup can be locked

device template
This cell sets the wait

Click this button to add
period between the previous
the selected writable
parameter download and
parameter to the
this parameter
Download List
Click this button to add Click this button to add
selected parameters to selected parameters to Click this button to
Writable parameters List Writable parameters List remove the selected
parameter from the
Use these buttons to Download List
move the selected
parameter up or down
in the order in which
the parameters are
downloaded to the
device
Figure 8-19. Setting Up Downloads
3. Use the pull-down list in the Show field below the Parameter Pool list to
select All writable, or one of these subsets:
• Inputs writable
• Outputs writable
• Device Parameters writable
• Diagnostics writable.
4. Select parameters in the Parameter Pool list on the left and click to add
them to the Writable Parameter List.
5. Select parameters in the Writable Parameter List in the center of the dialog
box and click on the right to add them to the Download List.
Parameters cannot be added to the Download List directly from the
Parameter Pool.
6. Select a different group in the Show field to add parameters to the
Writable List from a different pool.
7. Select parameters in the Download List and click to exclude them

from the list; select parameters in the Writable Parameter List and click
to exclude them from the downloads.
8. Change the download order by selecting parameters in the Writable
Parameter List and clicking (earlier) or on the right side of the list.
Ctrl+click to select non-contiguous parameters. Multi-selected
parameters maintain their downloaded order relative to one another as
they are moved up or down as a group.
Refer to the device manufacturer’s documentation for recommended
download sequences, and for delays that need to be specified after
download of a parameter that needs the device to perform recalculations.
9. Specify the recommended delay in seconds for individual parameters in
the Wait column in Writable parameters.
10. Check or un-check the Upload after Download option in the lower left
corner the dialog box.
This option updates the Galaxy with values from the device to cover those
cases where a downloaded parameter changes other parameters in the
device that were not downloaded. The uploaded value is not written to the
Galaxy device database if the parameter is locked by the parent device
template.
253
C H A P T E R 9
Control Configuration
The chapter covers the procedures for setting up a control strategy in the
Control Editors that includes DCI blocks to access data from the PROFIBUS
network. The focus of this chapter is the Point Configuration String that is
used in the DCI blocks to identify the portion of the input and output data to be
processed by the block. The string, which is entered in the block’s point
number parameter, is also used to specify the type of connection (cyclic or
acyclic), the data type to be used by the DCI block in converting data, and
other options for selecting and formatting the data. Figure 9-1 shows the block
RIN_1 in the Control Software Strategy Editor. The Point Configuration String
in the PNT_NO parameter (X6S2) specifies an analog input from the device
identified in the block’s IOM_ID parameter (RIO004). The string specifies a
cyclic data connection (X) with an offset of six bytes (6) in the input data and a
data length of two bytes (2). The data type is signed integer (S).
ECB compound and device ECB
Point Configuration String
Figure 9-1. RIN Block Connection to Device Input Data
The Control Editors provide two basic ways of configuring the ECB identifier
and Point Configuration String:
• Open the block in the Block Configurator and manually enter the ECB
path name and Point Configuration String
• Use one of these browsers to reference the slave device and one of its
defined I/O parameters:
• ECB Connection Browser opened from the Block Configurator
• Device Browser in the Strategy Editor
• IO Assignment tab for the host control processor
Each of these browsers displays a PROFIBUS DataDefinitions tab when a
PROFIBUS slave device is selected in the browser’s Devices/FBMs pane.
The tab lists the parameters that are defined for the device in the Data
Definitions tab (or the vendor DTM). When a parameter is selected, the
path name of the device ECB is inserted into IOM_ID parameter and the
parameter attributes are used to construct the Point Configuration String.
254 9. Control Configuration
A majority of the examples in the chapter deal with cyclic data exchange.
However, acyclic data exchange, and the Freeze and Sync commands, are
covered at the end of the chapter.
The chapter begins with some general considerations, such as bus timing, in
setting up a control strategy integrating PROFIBUS devices, and continues
with a description of the Point Configuration String syntax. Then, there are
instructions for adding a DCI block to a control strategy and linking it to a
PROFIBUS device (configuring the IOM_ID parameter) and entering the Point
Configuration String. Use of the Point Configuration String is shown with
multiple examples involving a remote I/O system. Chapter 10, “Configuration
Examples” presents examples using other devices.
Refer to these Foxboro Evo Control Software documents for detailed
instructions on using the Control Editors:
• Block Configurator User’s Guide (B0750AH)
• Bulk Data Editor User’s Guide (B0750AF)
• Control Database Deployment User’s Guide (B0750AJ)
• Strategy Editor User’s Guide (B0750AN).
Refer to these Control Core Services documents for detailed information on
compounds and blocks, including the DCI blocks:
• Control Processor 270 (CP270) and Field Control Processor 280 (CP280)
Integrated Control Software Concepts (B0700AG)
• Integrated Control Block Descriptions (B0193AX)
Refer to these documents:
Workbook (B0700FY)
Workbook (B0700AV)
Workbook (B0700AW).
These sizing spreadsheets include worksheets for determining the limit on the
number of inputs and outputs. Each workbook includes a separate spreadsheet
for estimating FBM222 loading.
Contents
• PROFIBUS IO
• Point Configuration String Syntax
• Setting Up a Control Strategy
• Configuring Input DCI Blocks
• Configuring Output DCI Blocks
• DCI Block Data Types
• Using the Extended Data Type
9. Control Configuration 255
• Using the Packed Bits Format

• Reading Diagnostic Data
• Acyclic Data Exchange
• Programming Sync and Freeze Actions
PROFIBUS IO
The section covers the exchange of data between the FBM and its hosting
Control Processor, where DCI blocks are used to transform the data types used
in PROFIBUS data exchange telegrams into DCI parameter data types
appropriate to the application.
As described in “PROFIBUS Paradigm” on page 20, the FBM222 is
interposed into the PROFIBUS architecture. PROFIBUS telegrams are
exchanged between the FBM and connected slave devices in a cycle
determined by the FBM’s master bus settings. The CP communicates with the
FBM at its basic BPC. The CP reads data from the FBM’s data buffers and DCI
blocks are used to perform data transforms, make the data available to other
CP-resident blocks, and provide a human and operational interface to the user.
I/O Timing
When planning a PROFIBUS network on a Foxboro Evo system, it is
necessary to keep in mind the asynchronous relationship of the various
operating cycles:
• CP communication with the FBM222 versus the FBM’s communication
with the slave devices
• Cyclic data exchange on port 1 versus cyclic data exchange on port 2
• PROFIBUS-DP network speed versus the PROFIBUS-PA segment data
transfer rate
BPC Versus Cyclic Data Exchange Interval

Signal processing between the CP and the FBM is asynchronous to the cyclic
data exchange between the FBM and the slave devices. Most CPs run at a 500
ms interval, and thus generally speaking the I/O bus is scanned once per 500
ms and data written back on the I/O bus in that same interval, with some
latency. The two FBM222 ports generally execute at intervals of 125 ms. (We
recommend a default cycle time of 125 ms.) The asynchronous operation is
unlikely to have any application significance.
Note With a redundant FBM222, the control processor can access the FBM
data in 500-ms BPC. Do not configure the control processor for a faster BPC if
using a redundant FBM222. With a non-redundant FBM222, the BPC can be
as fast as 100 ms.
Port 1 Versus Port 2

In addition to the CP’s BPC being asynchronous to the FBM’s data exchange
cycles, the intervals for the two ports are likely to be different, depending upon
the number of connected devices, the data transfer rate, and other segment-
specific factors, and neither data exchange cycle is synchronized to the CP’s
processing cycle.
PROFIBUS-PA Considerations
As described in “DP/PA Interface” on page 29, the communication protocols
for PROFIBUS-PA and PROFIBUS-DP are different, requiring a translation
gateway, or segment coupler, to enable a PROFIBUS-DP master, such as the
FBM222, to communicate with a PA slave.
Keep in mind that bus speed for PROFIBUS-PA is fixed at 31.25 Kbaud
compared to PROFIBUS-DP speeds of up to 12 Mbaud.
With transparent couplers, such as the Pepperl & Fuchs SK-1 and SK-3
discussed in “Couplers” on page 30, each PA device appears to the master as a
unique slave device with a unique address. A bus trace of the communications
shows cyclic data exchange between the master and the PA slave devices on a
per device basis.
With non-transparent translation devices, such as the Siemens Link Coupler
described in “Siemens DP/PA Link” on page 31, the coupler has a DP address,
and the communications from master to PA slave device are with the translator.
The coupler in turn communicates with the PA slave devices as though it were
a PA master. A bus trace on the DP side of this non-transparent device reveals
cyclic data exchange containing telegrams in which data from the PA devices
is concatenated into a single read message and a single write message per data
exchange cycle. While this results in improved communication efficiency as
compared to the per PA device data exchanges with transparent couplers, you
need to parse these long efficient telegrams to extract the information to and
from the PA devices.
Use of a transparent versus non-transparent PA coupler can have a substantial,
perceived performance difference. On the PA side of this device, bus
communication is running at 31.25 Kbaud. At these speeds the typical PA
device might take 10 to 15 ms to update a value to and from the coupler. On a
loaded PA segment, tens of milliseconds is needed to finish a data cycle to the
connected PA devices. Asynchronous to this PA communication is the
communication on the DP side with the FBM master communicating to the
translation device.
Communication on the PA side of the translator is essentially gated by the
31.25 Kbaud bus speed and the number of PA devices connected to the coupler.
On the DP side, communication speed is gated by the type of coupler
(transparent or non-transparent) and DP baud rate.
With a non-transparent coupler, the DP communication (both read and write)
of the master to coupler takes less than a millisecond independent of baud rate.
For example, if 30 PA devices are connected to a Siemens Linker, the entire
transaction between master and the slave Linker takes less than a millisecond.
However, that the Linker can only provide refreshed PA device data on the DP
bus at the asynchronous PA cycle rates that is running far slower than this sub
one-millisecond exchange. If the data transfer rate on the DP side of the

coupler is every 10 ms, the data from a given PA device only changes every
300 ms or so.
For a transparent coupler, cyclic data exchange from FBM222 master to PA
slaves appears to be quite different, as each PA device is treated uniquely in a
cyclic data exchange cycle. The exchange between the FBM master and, for
example, 30 PA devices needs time to finish 30 individual exchanges.
Particularly at lower baud rates, this total cycle time to finish these exchanges
can be substantial.
In one test, 13 PA devices (a mix of transmitters and positioners) were
connected to an FBM222 through the transparent P&F SK-3. Figure 9-2
graphs total cycle time as a function of DP baud rate. The time needed to
process the PA devices turns out to be a strong function of baud rate. At a
nominal 500 Kbaud, total wire time is less than 10 ms for these 13 devices. As
this scales quite linearly, connecting 30 PA devices to an SK-3 would take
about 20 ms to process the cyclic exchange.
ms
Kbaud
Figure 9-2. PA Cycle Time Versus Baud Rate
With the non-transparent coupler, the data is not necessarily telling the entire
story. This translation device has the same fundamental PA bus limitations as
before. So while data can be turned around very quickly on the DP bus, fresh
data from the PA devices is made available much more slowly than Figure 9-2
might imply.
Setting this concern aside, the Figure 9-2 also provides useful data with respect
to the use of certain commercially available transparent couplers. The concern
is not the slow PA bus speed, but rather the DP cyclic data exchange cycle time
consumed by the translation device at these lower baud rates. We recommend a
PA translation device capable of operation at 500 KBaud (or above) such as the
SK-3 or the Siemens Linker. Failsafe Considerations
The Point Configuration String syntax supports device readback and this
capability works directly into a failsafe solution.
PA Devices
One of the primary objectives of the FBM222 development program was to
provide a means to fully integrate a PROFIBUS-PA positioner into the control
system. The key to this integration facility was to provide a means of reading
back the actual valve stem position, the READBACK parameter status, as well
as failsafe status from the device. The results of this integration effort and
recommendations to the end user are documented in an example in “PA
Positioner” on page 318. This functionality is enabled in the Point
Configuration String for the PNT_NO parameter of the Control Core Services’
ROUT block.
PROFIBUS-PA transmitters also support a limited failsafe facility, as
described in “DCI RIN Block” on page 278.
DP Devices
A number of vendors have implemented a failsafe feature as user parameter for
compact DP devices or modules in a modular DP device. You can select the
feature during configuration of the device in the Field Device Editor User
Param tab (“Configuring User Parameters” on page 183).
The parameter Behavior at CPU Stop, defines the operation in a failsafe
situation, with these options:
• De-energize (clear) the output
• Select a substitute value defined in another user parameter
• Hold the last output value received from the master.
The main points are summarized below:
• Slave device failsafe behavior is optional and is ultimately determined by
the device vendor’s design, not by the FBM222.
• For DP devices, failsafe behavior is determined at configuration time, with
options provided by the device vendor, not Schneider Electric.
• Slave device initialization on failsafe recovery is limited for non-PA
devices. If this is a detected application issue, considerable care in
database design is urged. Initialization must be taken on a case-by-case
basis, and is almost wholly a detected slave device issue.
PROFIBUS/DCI Block Data Conversions

DCI block usage with PROFIBUS slave devices is rooted in the cyclic data
exchange between the FBM master and its connected slave devices. The
master and slaves employ data exchange telegrams, which provide a compact
means of exchanging a considerable amount of data at high speed but with the
complication of having to extract data from the exchange telegram in a form
useful to the control system.
Figure 9-3 shows the Configured Modules pane in the Field Device Editor for
a WAGO remote I/O system (RIO002). The Output and Input bytes for the
modules are listed in separate columns, as the columns represent the order of
bytes in the write and read data exchange telegrams, respectively.
Figure 9-3. Example Remote I/O System Configured Modules
Figure 9-4 is a PROFIBUS bus trace that captures a typical data exchange
between the FBM222 master and the remote I/O system.
Figure 9-4. Typical Data Exchange
The exchange cycle consists of nine bytes being written to the slave (output)
and 14 bytes being read (input). How the bytes are to be interpreted is based on
the device configuration (which matches how this remote I/O system had its
I/O modules physically slotted into its chassis).
The total number of bytes needed for data exchange in each direction is shown
in the bus trace Datalen column (Figure 9-4).
With the information from Figure 9-3 you can interpret the output telegram to
know which bytes are being used by which I/O module, then consult the device
documentation to see how the bytes are formatted.
The FBM-to-device request message writes data to two modules: the 750-530
8 DO module in one byte and then the 750-460 four-channel AO module in
eight bytes (Figure 9-5).
0F 19 99 33 32 4C CC 66 65
8DO 4AO
Figure 9-5. Output Telegram Parsing Example
The device-to-FBM response message includes 14 bytes of input from four

modules, starting with one byte (containing two digital inputs) from the 750-
400 and ending with four analog inputs of two bytes each from the 750-460
(Figure 9-6)
01 03 00 00 00 00 OE 69 FA 9D OE 96 0E 8A
2DI 1DI 2AI 4AI
Figure 9-6. Input Telegram Parsing Example
Telegram to DCI Block Parameter Conversion

The next step is to determine the data type that is specific to that device or
module, and select a DCI block that supports the data type and provides the
proper conversion.
For example, according to the documentation for the 750-559 4 AO module,
each of the 4 channels is capable of 0 to 10 V dc output. The module uses a
two-byte signed integer as its D/A converter input. Four ROUT blocks can be
used to drive each of the four channels of this analog output module, while a
single PAKOUT block can be used to drive the eight digital outputs in the
module in slot 5 (750-530).

DCI blocks support a number of different data types, most of which are
familiar types such as Float, but a few are special. Table 9-1 lists each type and
the single letter code used to specify the type in Point String Configuration
(discussed later on page 261).
Table 9-1. DCI Block Data Types
Code Data Type Description

F Standard IEEE Floating Point
B Boolean
U Unsigned Integer, Intel Format
S Signed Integer, Intel Format
R Raw, unformatted octets, byte stream of one or multiple bytes
without interpretation
P Packed Bits is a special format that processes selected contiguous
bits from up to four bytes (see “Using the Packed Bits Format” on
page 303)
C Channel Bit, a single bit in the selected byte
Table 9-1. DCI Block Data Types (Continued)

E Extended, a special format that selects contiguous from up to four
bytes (see “Using the Extended Data Type” on page 302)
D Diagnostic, read data from diagnostic stream, as described in
“Reading Diagnostic Data” on page 304
PROFIBUS DCI Block Usage

Table 9-2 shows the data types that each DCI block supports. While the block
may support a given Control Core Services data type, that data type may not
necessarily be a good application choice, as described in subsequent sections.
The selection of a data type may imply data conversion within the DCI block,
but it is necessary that the data conversions are performed exclusively within
the DCI blocks so as to unload the FBM from this conversion task.
Table 9-2. Data Types Supported by DCI Blocks
Data Type
DCI Block F B U S R P C E D
BIN  
BINR  
IIN and        
IINR
PAKIN and        
PAKINR
RIN        
RINR        
STRIN  
BOUT  
BOUTR  
IOUT       
PAKOUT       
PLSOUT  
ROUT       
ROUTR       
STROUT 
Point Configuration String Syntax

The connection between a DCI block and the slave device is specified by
entering the path name of the device ECB in the IOM_ID parameter in the DCI
block. The data to be written to or read from a device module is contained in
the block’s point parameter. Each DCI block contains one or more such
parameters variously named, as listed in Table 9-3.
These parameters are references to data that is to be extracted from, or inserted

into, a data exchange telegram (or a slave device address in the case of certain
acyclic data exchanges, as described in “Acyclic Data Exchange” on
page 308).
Table 9-3. DCI Block Point Parameters
Block Block Point Parameters

BIN PNT_NO
BINR BI1_PT, BI2_PT, BI3_PT
BOUT PNT_NO, INI_PT
BOUTR CO1_PT, CO2_PT, CO3_PT
IIN PNT_NO
IINR II1_PT, II2_PT, II3_PT
IOUT PNT_NO, INI_PT
PAKIN PKINGP
PAKINR PK1_PT, PK2_PT, PK3_PT
PAKOUT PKCOGP
PLSOUT CO1_PT, CO2_PT, INI_PT
RIN PNT_NO
RINR RI1_PT, RI2_PT, RI3_PT
STRIN PNT_NO
STROUT PNT_NO
ROUT PNT_NO, INI_PT
ROUTR RO1_PT, RO2_PT, RO3_PT, INI_PT
This section describes the Point Configuration String, that is, the syntax used
with these point parameters to define the portion of the data in the exchange
telegram to be processed by the block and how that data is to be handled.
Note The syntax presented here includes that used with the FBM223 plus the
extensions developed for the FBM222.
In general, the functionality of the Point Configuration String provides for:

• Implicit handling of PA device parameter status
• Specification of cyclic or acyclic data
• Optional readback point for output parameters (only for certain devices)
• Optional status for input parameters
The general form of the string field is:
Point Configuration String
The string specifies the connection type, starting point and data length in
the input or output data, the data type and other formatting as shown in
Figure 9-7 and described in this section. The string is also used to access a
standard value and status from PA devices. Figure 9-7 shows the format of
the Point Configuration String.
<Status><CXN Type><Address><Data type><No. bytes (or Channel bit no.)>

[<Swap>] [<ext>]
Where Address is either <offset> for CXN Type X, or <Slot:Index> for CXN Type A.
Figure 9-7. Point Configuration String
Point Configuration String < Readback Point Configuration String

The delimiter < indicates the start of a string that specifies a readback
point value. The readback value can be any other data point from the same
device, including data from the cyclic data stream and acyclic parameters.
The syntax for the readback is the same as that used in the Point
Point Configuration String $ Status Point Configuration String
The delimiter $ indicates the start of a string that reads a vendor-defined
custom status from the device or module. The optional Status Point
Configuration String creates a test mask using a specific syntax described
in “Custom Status Handling” on page 267. This string is not used to access
a standard PA Status.
Data and format constraints for this string are:
• <Status> is only supported for cyclic data exchange with PA devices.
• <Offset> range does not exceed the range minus the number of data bytes
requested.
• Leading zeros or spaces before <CXN Type> are ignored.
• An unidentified <Offset> or <CXN Type> results in an invalid point
address error detected
Table 9-4 shows the coding for the various string elements.
Table 9-4. Point Configuration String Definition
Element Coding Definitions

<Status> Indicates that the parameter has a PROFIBUS-PA profile status byte associated
with it in the input or output data stream. The FBM automatically transforms the
PA status to Control Core Services status and vice versa according to the
transforms shown in Table 9-5. <Status> can only be used for connection type
Cyclic Data (X).
H – An 8-bit PROFIBUS-PA status byte immediately follows the data point in the
input or output stream.
Omitting the <Status> fields defaults to using no PA profile status parameter.
<CXN Type> Identifies the connection type for the DCI connection as either:
A – Acyclic DPV1 data access
X – Cyclic data access
Omitting the CXN Type defaults to X.
Table 9-4. Point Configuration String Definition (Continued)

<Offset> Byte offset of the desired data in the byte stream transferred with the
corresponding device. Range is 0 to maximum byte-package size.
Omitting the offset defaults to 0.
<Slot:Index> Data address for DPV1 type acyclic (A) data. Range is 0 to 255 for both Slot and
Index. Used with CXN Type A only.
<Data Type> D = Diagnostic Read data from diagnostic stream
S = Signed Integer Intel® format
U = Unsigned integer Intel format
E = Extended * Special format
B = Boolean
F = Floating point Standard IEEE real format
R = Raw Octets
C = Channel bit Single bit within a byte
P = Packed bits * Special format
<Number of D, R = 4, 3, 2 and 1 byte(s) or 1 to 80 byte if STRIN/STROUT block
bytes>
S, U = 4, 3, 2 and 1 byte(s)
with byte
constraints E, P = 4, 3, 2 and 1 byte(s)
B = 1 byte
F = 4 bytes
C = Single bit within byte; index to number 1-8
<Swap> W0: No swapping
W1: Byte swapping for
[optional]
2 byte values:
[byte 1 | byte 0] swapped to [byte 0 | byte 1]
3 byte values:
[byte 2 | byte 1 | byte 0] swapped to [byte 0 | byte 1 | byte 2]
4 byte values:
[byte 3 | byte 2 | byte 1 | byte 0] swapped to [byte 0 | byte 1 | byte 2 | byte 3]
W2: Byte swapping for 4 byte values:
W3: Word swapping for 4 byte values:
Omitting the Swap defaults to
W0 for types R, P and D.
W1 for types S, U, E and F.
Swapping for the E and P-type is done for inputs before bit-masking, for outputs
after bit-masking.
* <ext> * Special format for data type E <ext> is [<Snumber>][<Cnumber>]<LxHy>
* Special format for data type P <ext> is <LxHy>
Table 9-4. Point Configuration String Definition (Continued)

<Snumber> Sign bit, identified by S and a position number of the bit. The bit count starts
[optional] with 1.
Position number = 0 indicates no sign bit, that is, unsigned (or with the sign
determined by one’s complement or two’s complement).
Omitting the sign bit indicates no sign bit
<Cnumber> Complement identified by C and a number with these meanings:
[optional]
0 = no complement, that is, unsigned or signed using a sign bit
1 = one's complement
2 = two's complement
Omitting the complement indicates no complement (= unsigned)
<LxHy> Selected bits are identified by the starting bit position L, followed by the ending
bit position H.
Bit count starts with bit 1.
Example: L2H15 = value bits are 2 through 15
Examples:
X6S2 This string in the PNT_NO parameter of a DCI RIN block
specifies a two-byte signed integer (S2) starting with the seventh
byte (offset of 6) in the input data stream during cyclic data
exchange with the PROFIBUS slave device. See “DP Devices”
on page 286 for the entire description of this I/O connection.
HX0F4 This string in a RIN block PNT_NO parameter acquires a four-
byte floating point value (F4) and status (H) from a PROFIBUS-
PA device. The first four bytes of the input data stream provide
the value (offset is 0) and the fifth byte in the input data stream is
the value status, as described “PA Devices” on page 288.
0R2W1 Specifies a two-byte raw value (R2) in the PKCOGP parameter
of a PAKOUT block in which the order of the two bytes is
reversed (W1), as used in the example on “Swapping Used with
Digital Output” on page 298. Without A or X specified, the string
defaults to cyclic data exchange (X).
A0:8R1 The string in the PKING parameter of a PAKIN block specifies
input of a one-byte raw value (R1) during acyclic data exchange
(A). The location of the data is slot 0, index 8 (0:8) per the device
documentation. See “Acyclic Master Class 2 Read and Write
Requests” on page 308 for details on this example.
PA Status Handling
PROFIBUS-PA devices support a parameter value status that is similar in
format to the value status provided by FOUNDATION fieldbus H1 devices.
When H is specified in the Point Configuration String for cyclic access to a PA
device, the status is read bit-for-bit into the DCI block VALSTS parameter.
Table 9-5 shows this value status utilization by transforming PA status to DCI
status.
Table 9-5. PA Status to Control Core Services Status Transforms
PA Status Meaning FBM222 Transformation

Bad Value (BAD) Parameter value is Transmitter/sensor failure detected,
Bad valve/actuator failure detected, I/O diagnostic
(Bit 0)
failure detected, or device failure detected
PA Parameter Status:
Bits 6-7: Quality = 0 (Bad)
Out-of-Service (OOS) Parameter value is FBM222-to-PA communications failure
unavailable detected
(Bit 1)
Bits 6-7: Quality = 0 (Bad) and Bits 2-5:
Substages = 7 (Out-of-Service)
or
Actuator Status = Offline
Uncertain (ERR) Parameter value is PA Parameter Status:
questionable
(Bit 2) Bits 6-7: Quality = 1 (Uncertain)
Disconnected (DSC) Parameter is not Device not configured/not connected,
connected parameter not defined/not connected
(Bit 3)
Bits 6-7: Quality = 0 (Bad) and
Bits 2-5: Substatus = 1 (Config Error) or 2 (Not
Connected)
Limited High (LHI) Parameter cannot be PA Parameter Status:
increased or
(Bit 4) Bits 0-1: Limits = 2 (High) or 3 (Constant)
incremented
(outputs only) or
(Bits 6-7: Quality = 2 or 3 (Good) and Bits 2-5:
Substatus = 3 (NI))
Limited Low (LLO) Parameter cannot be PA Parameter Status:
decreased or
(Bit 5) Bits 0-1: Limits = 1 (Low) or 3 (Constant)
decremented
(outputs only) or
Bits 6-7: Quality = 2 or 3 (Good) and Bits 2-5:
Substatus = 3 (NI)
Initialize Request (IR) Parameter needs to PA Parameter Status:
be initialized to its
(Bit 6) Bits 6-7: Quality = 2 or 3 (Good) and Bits 2-5:
readback value
Substatus = 2 (IR)
(outputs only)
Table 9-5. PA Status to Control Core Services Status Transforms (Continued)
PA Status Meaning FBM222 Transformation

Local Override (LO) Parameter is being PA Parameter Status:
changed locally
(Bit 7) Bits 6-7: Quality = 3 (Good cascade) and Bits
(outputs only)
2-5: Substatus = 6 (LO)
Failsafe (FS) Parameter is in its
Failsafe state
(Bit 8)
(outputs only)
PA Value Status Parameter Status PA Parameter Status: Bits 0-7
(Bits 8-15)
Note This facility is limited to PROFIBUS-PA devices.
Custom Status Handling

The Point Configuration String also offers a free form of status more suited to
the vendor-defined status used by some DP slave devices. Typically, this status
utilizes a byte appended to a value within the cyclic data exchange telegram.
The custom status handling option in the syntax allows you to set a mask for
the status byte so that if the status value is equal to the mask, the two-byte
Control Core Services Status value is tagged DCI GOOD. If a match does not
exist, the two-byte Control Core Services Status value is set to DCI BAD.
Unlike the PA construct, which supports other DCI status states, this construct
is limited to BAD.
For example, a one-byte status word is appended to a two-byte value from the
DP slave device. The syntax is presented in this example:
0U2 $ 2U1:-----01-
or
0U2 $ 2U1:01-
The example is decoded from left to right. 0U2 denotes that the point number
value is a two-byte unsigned integer with a 0 offset. This is the value that the
DCI block extracts from the cyclic data exchange telegram. It declares DCI
BAD if a status mask mismatch is determined.
The $ acts as a delimiter in the syntax. (The spaces are not needed but can be
used for format clarity.) The syntax to the right of the $ defines the mask. 2U1
specifies the use of a one-byte unsigned integer with offset 2 as the status byte
to be read from the telegram. The fields to the right of the colon delimiter
define the status test mask:
Bit Position 7 6 5 4 3 2 1 0
Mask (fully defined) – – – – – 0 1 –
Mask (minimum definition) 0 1 –
The syntax labels bits from right to left, 0 being the lowest bit. The mask need
not be completely defined, bit for bit. However, we recommend that you define
the entire mask. At least one bit needs to be defined that will be the lowest bit
going from right to left. Undefined bits are treated as “don’t care.”
Enter a dash (–) in each bit position that is not to be considered in determining
a mask/status byte match. Enter a 1 or 0 in a bit position to specify how that bit
position is to be evaluated. Only those bit positions with a 1 or 0 are used for
mask/status match evaluation. In the example, the value is GOOD if bit 1 = 1
and bit 2 = 0. Bit 0 and bits 3 through 7 are not considered.
The status byte (or whatever bytes are used for the definition of status) is used
only for GOOD/BAD evaluation. The status bytes are not considered to be part
of the actual point number value that has been defined in the syntax to the left
of the $ delimiter.
• The status parameter should be defined as type packed bits (P), unsigned
integer (U) or channel bit (C) only.
• At least one bit of the lower bits must be defined.
• The length of the point configuration string is up to 32 characters (use the
minimum definition to save characters).
• A status parameter must not reference another status parameter.
• The status must be in the same module as the value.
• Byte swapping (W0 – W3) options are NOT supported for the status
parameter.
• This construct is limited to cyclic data exchange usage, input values (that
is, data being read into the FBM222 master) read by a DCI block.
The definition of PNT_NO value and DCI status is ultimately vendor- and
device-specific, and no generalizations can be made about the use of this
custom status syntax.
Setting Up a Control Strategy

The control software in these instructions uses only base compound, strategy,
and block templates. However, the Control Editors provide a versatile array of
tools for creating templates of strategies that can be quickly replicated and
deployed to the runtime system, as described in Strategy Editor User’s Guide
(B0750AN).
Creating the Control Compound and Strategy

The first step is to create a control compound, and assign it to a control
processor that hosts the FBM222 and the slave devices. The control processor
and FBM222 used in these examples are FCP001 and PROF01, respectively.
FCP001 is assigned to the equipment unit Equip_Unit_001 (as shown in the
Deployment and Network views in Figure 9-8).
Figure 9-8. Example FBM222 and Host Control Processor
To add the control compound to the host control processor:

1. Right-click the control processor in the Deployment view (FCP001 in the
example), choose New > Compound from the context menu, click
$COMPND in the Bulk Create dialog box, and click OK.
The new compound is added underneath the control processor with a
default name such as COMPND_001.
2. Type an new name over default name and press Enter, or press Enter to
accept the default (as is done in the example).
To create the strategy and add DCI blocks:
1. Expand FCP001 in the Deployment view to display its compounds, right-
click COMPND_001, and choose New > Strategy from the context menu
to display the Bulk Create dialog box.
2. Click the checkbox for the base strategy template ($Strategy) in the dialog
box, and click OK.
This action adds a strategy instance with a default name such as
Strategy_001 under the compound in the Deployment view.
3. Press Enter to accept the default name.
4. Double-click Strategy_001 in the Deployment View to open the instance
in the Strategy Editor.
5. Add a RIN block to the strategy by dragging $RIN from the Template
Toolbox and dropping it on the drawing canvas in the Strategy tab.
6. Drag $PIDA and then $ROUT from the Template Toolbox and drop them
on the drawing canvas in the Strategy tab to add the control block PIDA_1
and the output DCI block ROUT_1.
The block execution order within the strategy is initially determined by the
order in which the blocks were added to the strategy. The order is
indicated by the numeral on the upper right side of each block appearance
object. Refer to Strategy Editor User’s Guide (B0750AN) for information
on setting execution order within the strategy.
7. Arrange the blocks as shown in Figure 9-9.
Figure 9-9. Adding an ROUT Block to the Strategy
The next step is to connect the blocks within the strategy, which involves
dragging a line from the source parameter in one block to the sink
parameter in the other block. See Strategy Editor User’s Guide
(B0750AN) for details on drawing the connections and modifying the
appearance of the strategy.
8. Make the block connections as shown in Figure 9-10:
• RIN_1:MEAS to PIDA_1.MEAS
• PIDA_1.OUT to ROUT_1.MEAS
• ROUT_1.BCALCO to PIDA_1.BCALCI
Figure 9-10. Block Connections
9. Click to close the editor, save changes to the strategy, and check it in.
Making the Field Connections

Before configuring the DCI blocks, link the blocks to the PROFIBUS slave
devices (as represented by their respective ECB201s), and specify the portion
of the device data exchange to be processed by the DCI block. You can do so
by manually entering the IOM_ID and Point Configuration String in their
respective DCI block parameters, or by using one of these browsers to
reference the PROFIBUS slave device and one of its defined parameters:
• Strategy Editor Device Browser (as described on page 271)
• ECB Connection Browser (as described on page 274)
• IO Assignment tab for the host control processor (as described on
page 276).
Using the Strategy Editor Device Browser

The Strategy Editor Device Browser can be used to set the ECB Identifier and
Point Number fields for DCI blocks that have a single point number (BIN, IIN,
RIN, PAKIN, PAKOUT, STRIN, and STROUT; see Table 9-3).
In this sequence, the Strategy Editor Device Browser is used to connect the
RIN block in the Strategy_0001 to a device ECB and reference a device
parameter to set the Point Configuration String.
To make a field connection:
1. Double-click the strategy in the Deployment view if it is not already
opened in the Strategy Editor.
2. Choose View > Device Browser from the left end of the Strategy Editor
toolbar to open the Device Browser dialog box (Figure 9-11).
Note The browser is not available if any block in the strategy is opened
in the Block Configurator.
Figure 9-11. Strategy Editor Device Browser
3. Expand the host control processor and FBM222 in the Devices data tree at
the top of the dialog box to display the host FBM’s ports and attached
devices.
4. Select the device to be connected (RIO002 in Figure 9-11) to display its
defined parameters in the PROFIBUS DataDefinitions tab in the lower
half of the dialog box.
5. Drag the block to be connected from the Strategy tab to the browser and
drop it in the Connection field for the target parameter.
If the connection is valid, that is, there is no prior assignment and the types
match, the Connection field displays the compound, strategy and Control
Core Services block and parameter that is linked to the device
(COMPND_001.Strategy_001.RIN_1.PNT_NO in Figure 9-11).
6. Select another device in the Devices window to display its parameters and
link other blocks in the strategy.
To disconnect a device from a DCI block:
• Right-click the connection in the PROFIBUS DataDefinitions tab and
choose Unassign IO Connection from the context menu.
7. Click Close in the dialog box to close the Device Browser.
The connected device and the Point Configuration String are displayed in
the block in the Strategy Editor (Figure 9-12).
Figure 9-12. Block Displays the Device and Point Configuration String
If no parameter is defined for the target data:

1. Open the browser, select the device, and click the IO Connections tab.
2. Drag the block to be connected into the Device Browser and drop in an
empty area in the IO Connections tab.
The block parameter path is inserted into a Connection field.
3. Double-click the newly made connection to open the NewPNT NO dialog
box, enter the Point Configuration String in the Channel field and click
OK in the dialog box.
Refer to“Point Configuration String Syntax” on page 261.
The Point Configuration String is displayed in the Channel column for the
connection.
You can also use the NewPNTNO dialog box to change an existing Point
4. Click Close in the Device Browser to return to the Strategy tab.
Figure 9-13. Device Browser and NewPNTNO Field Dialog Box
Using the ECB Connection Browser

To connect a DCI block to a device using the ECB Connection Browser:
1. Double-click the strategy in the Deployment view if it is not already
opened in the Strategy Editor.
2. Double-click the DCI block (ROUT_1 in the example) in the Strategy tab
to open the block in the Block Configurator, and click the Inputs tab or
Outputs tab (as in the example).
3. Click to the right of the ECB Identifier field to open the browser
(Figure 9-14).
Figure 9-14. ECB Connection Browser for a ROUT Block
4. Expand the host control processor and FBM in the FBMs data tree at the
top of the dialog box to display the FBM’s ports and attached devices.
5. Select the slave device (RIO002 in Figure 9-14) to display its defined
parameters in the PROFIBUS DataDefinitions tab in the lower half of the
browser.
6. Select the target parameter and click OK.
The dialog box closes, and the compound and device ECB name are
inserted into the ECB Identifier field and the Point Configuration String is
inserted into the Point Number field.
If there is no parameter defined for the target data:
a. Select the device in the FBMs pane and click OK to close the
browser.
The device ECB path is inserted into the ECB Identifier field in the
Inputs or Outputs tab.
b. Enter the Point Configuration String in the Point Number field using
the syntax described in “Point Configuration String Syntax” on
page 261.
At this point, you can specify the scaling parameters in the Output tab.
7. Review and set the DCI block parameters, and then click in the Block
Configurator title bar to close the editor, save changes to the block and
return to the Strategy Editor.
Using the IO Assignment Tab

Field connections can also be made from the IO Assignment tab when the host
control processor is opened in the Hardware Editor.
To connect DCI blocks in the example strategy to device parameters:
1. Double-click the FCP001 in the Deployment view to open the control
processor in the Hardware Editor, and click the I/O Assignment tab
(Figure 9-15).
Figure 9-15. Making I/O Assignments
2. Expand the FBMs data tree on the left and select the slave device
(RIO002).
When a PROFIBUS slave device is selected, the PROFIBUS
DataDefinitions displays the device’s defined parameters.
3. Expand COMPND_001 > Strategy_001 in the Blocks data tree on the

right to display the blocks to be connected.
• Click to the left of a block name to view specific parameters that
can be connected.
RIN_1 has only one connectable parameter (PNT_NO), and thus the
block display does not need to be expanded.
ROUT_1 has two connectable parameters (INI_PT and PNT_NO)
and therefore needs to be expanded to select the correct parameter.
4. Drag the DCI block or block parameter to the Profibus DataDefinitions
tab and drop it in the Connection field for the target parameter.
In the PROFIBUS DataDefinitions tab, the Connection field for the slave
device parameter now holds the path name of the DCI block parameter
(COMPND_001.Strategy_001.ROUT_1.PNT_NO for the parameter
NW7_OUT1).
The Blocks tab now lists the connected slave device and the Point
Configuration String for each DCI block or block parameter. For example
(RIO002,1S2) is the result of connecting ROUT_1 to the NW7_OUT1
device parameter.
5. Make other changes to the control processor configuration as needed, and
click to close the editor, save changes to the control processor and
check it in.
If no parameter is defined for the target data:
1. Open the IO Assignment tab, select the device, and click the IO
Connections tab.
2. Drag the DCI block or DCI block parameter to be connected into
IO Connections and drop it in an empty area in the tab.
The DCI block parameter path is inserted into the Connection field.
3. Double-click the newly made connection to open the NewPNT NO dialog
box (Figure 9-16), enter the Point Configuration String in the Channel
field and click OK in the dialog box.
Refer to“Point Configuration String Syntax” on page 261.
The Point Configuration String is displayed in the IO Connections tab
Channel column for the connection.
You can also use the NewPNTNO dialog box to change an existing Point
4. Make other changes to the control processor configuration as needed, and
click to close the editor, save changes to the control processor and
check it in.
Figure 9-16. IO Assignment Tab and NewPNTNO Field Dialog Box
DCI RIN Block

This section “DCI RIN Block” and the next section “DCI ROUT Block” on
page 282 cover certain enhancements to the DCI blocks with I/A Series
software v8.4-v8.8 or Control Core Services v9.0 or later that are specific to
PROFIBUS. The RIN and ROUT are called out as these are the blocks that is
frequently used in a PROFIBUS-PA context and the features of these blocks
mesh well with the PROFIBUS-PA analog input (AI) and analog output (AO)
device function blocks.
Failsafe
While it may seem strange to discuss the subject of PROFIBUS AI block
failsafe within the context of the DCI RIN block, this background material sets
a context for the logic functionality of the block.
The implementation of PROFIBUS failsafe within the PA AI function block

begins with the parameter definitions in Table 9-6.
Table 9-6. PA AI Block Failsafe Parameters
FSAFE_TYPE Defines reaction of device if a fault is detected. The
calculated ACTUAL MODE remains in AUTO.
0 = The current measured value with the BAD status
is forwarded as the OUT value
1 = If the status of the measured value goes BAD, the
last valid measured value is used for OUT with status
UNCERTAIN_LAST_USEABLE_VALUE.
2 = If the status of the measured value goes BAD, the
value of OUT is set equal to FSAFE_VALUE with a
status of UNCERTAIN_SUBSTITUTE_VALUE.
FSAFE_VALUE Default value for the OUT parameter, if sensor or sensor
electronic fault is detected. This parameter has the same
units as OUT.
Figure 9-17 shows the Failsafe construct in the data flow resulting in the output
of the AI block. These parameters (FSAFE_TYPE and FSAFE_VALUE) are
utilized in a detected fault condition with the value of OUT being determined
by the user-selected option of FSAFE_TYPE.
AIFB_PV_FTIME
AIFB_OUT_SCALE 100% AIFB_HI_HI_LIM

AIFB_OUT_SCALE 0% AIFB_HI_LIM
AIFB_OUT_SCALE UnitCode AIFB_LO_LO_LIM
AIFB_LO_LIM
AIFB_ALARM_HYS
EU
AIFB_OUT
LIMIT0
Check
STATUS
OUTPUT SCALING Calculation
FAILSAFE
(OUT_SCALE)
AFIB_FSAFE_TYTPE
AIFB_FSAFE_VALUE
AFIB_TARGET
MODE
Figure 9-17. PROFIBUS-PA AI Block Failsafe
Keep in mind that while a Failsafe functionality is supported, when the failsafe
condition is asserted, no explicit failsafe indication is provided by the status
byte of the OUT value nor by the device diagnostics. However, you can see
other indications of a detected fault condition both in OUT status and through
device diagnostics. Neither the RIN block’s BLKSTA parameter nor its
VALSTS parameter provide an indication of a failsafe condition, as the device
does not provide this status information. This situation is much different for
devices based on the PROFIBUS-PA AO function block.
BLKSTA
Table 9-7 shows the mapping of the RIN block’s BLKSTA parameter. If the
status of the PROFIBUS-PA device’s AI block OUT parameter goes BAD, bit
12 of the associated RIN block BLKSTA parameter is set.
Table 9-7. RIN Block BLKSTA Parameter
Bit Numbera Boolean Connection

(0 to 31) Name Description When True (B32 to B1)
8 FBM Bad Status of ECB BLKSTA.B24
11 MA Block is in Auto mode BLKSTA.B21
12 BIO BAD I/O BLKSTA.B20
14 UDEF Block Undefined BLKSTA.B18
15 ON Compound is on BLKSTA.B17
20 LCK Workstation locked BLKSTA.B12
23 DCI Enhanced DCI block (FCP280 or BLKSTA.B9
CP270 Only)
a. Bit 0 is the least significant bit (starting from the right).
VALSTS
It was noted that the point number syntax has been extended so that a PA user
can cause the PA AI block’s OUT parameter status to be read into the DCI RIN
block. This status byte is mapped bit for bit into the DCI RIN block’s VALSTS
parameter so that you can use the VALSTS parameter value within the
application.
Note Review the documentation provided by the device vendor carefully for
subtleties in the implementation of PA status for the specific device. Small
differences from device to device have been found and are likely so if you are
planning on using one it is necessary to determine if the device supports the
desired function.
Scaling
One of the frequently asked questions regarding the use of the DCI RIN block
in a PROFIBUS context is how to scale the block such that the value from the
slave device is transformed into a value in engineering units in the Object
Manager. The example presented here is from a real world example using a
4-20 ma anemometer (wind speed, 0-100 MPH) and a Turck Excom current
input (4-20 ma) I/O module.
The device is linear with a scale of zero to 100 MPH over the 4 to 20 mA
range. The Turck I/O module is similarly linear. For 4 ma into the module, the
two byte unsigned integer from the slave would produce a value of 0xFA0, or
4000 decimal. For a 20 mA signal into the module, the two-byte unsigned
integer would produce a value of 0x4E20, or 20000 decimal.
To convert a hex value to decimal and scale the value:
1. Set the syntax of the RIN block PNT_NO parameter to: <offset>U2.
were U is used for an unsigned integer, and 2 for the two bytes used by this
module for representing the value of current (ma).
The relationship between the independent variable (the integer value of
current as converted by the I/O module) to the dependent variable (MPH)
is illustrated in Figure 9-18.
Figure 9-18. Example Scaling
2. Calculate the slope and intercept using the equation y=mx+b to determine
the MGAIN and MBIAS terms of the RIN block.
m=100/16000=0.00625
b=y-mx
b=100-(0.00625x20000) = -25.0
3. Set MGAIN is 0.00625 and MBIAS is set to -25.0.
Note The SCI parameter value is set to zero.
4. Verify the value by noting that at midrange the value of current (mA)
would be 12 mA which would convert to an integer value of 12000.
Substituting in the equation:
y = (0.00625 x 12000) -25.0 = 50.0 MPH (the mid range value)
DCI ROUT Block
Failsafe
The failsafe construct within the PROFIBUS-PA AO function block is quite a
bit more complex than that for the AI block. The subject is introduced by a
review of the pertinent parameters of the PA AO block as it relates to failsafe.
While from an implementation perspective the failsafe facility was designed
primarily to deal with communications failures between master and slave, this
is not the entire range of the facility. These facilities are covered in this section.
Depending on the process application, you can set FSAFE_TYPE for the
desired failsafe behavior (Table 9-8). These parameter values are not set
through the value entry in the ROUT DCI block. Rather these values are set
using either Field Device Manager or the manufacturer’s DTM.
Table 9-8. PA AO Block Failsafe Parameters
FSAFE_TYPE Defines the reaction of the positioner for detected failure
in communication after exceeding the FSAFE_TIME. The
operation mode during Failsafe is by default AUTO. One
of three actions can be specified:
0 = Safety position: De-aeration of the actuator. For a
single acting actuator the spring defines the moving
direction.
1 = Hold last value: The last received valid setpoint is
to be used and consequently the actual valve position
will be kept.
2 = Target Value: The position defined by
FSAFE_VALUE is reached.
FSAFE_VALUE Float parameter that defines the target position in percent
when FSAFE_TYPE is configured to Target value and
Failsafe will be performed after the FSAFE_TIME.
FSAFE_TIME Float parameter for the time in seconds the positioner
tolerates not receiving a valid setpoint until the behavior
defined in FSAFE_TYPE will be performed.
To develop a better understanding of the total failsafe construct an

understanding of the module to be used for the DCI ROUT block needs to be
developed. A PROFIBUS-PA positioner is defined as a Modular device. While
it has no hardware slots, it does offer a number of modules as configuration
options for the device. For optimal device functionality in a Control Core
Services environment, we recommend you to select the option:
SP+READBACK+POS_D+CHECKBACK
The result of this configuration option is better understood if the format of the
Output and Input data are presented.
Output Data
The format of output data unit is shown in this table.
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5
SP (Value, IEEE float) Status
The first four bytes of the output (that is, master to slave device) is the setpoint
to the slave device’s AO function block. The last byte is a status value
associated with the value of SP. The five bytes are written together in the data
exchange to the slave. For the SP value to have the desired operational effect
on the slave, the status value in Byte 5 needs to be equal to 0x80. This is
explained in the material below relating to the PROFIBUS-PA AO device
function block.
Generally speaking, the SP value is scaled 0 to 100%, with 0% being the SP to
drive the actuator/valve fully closed. A SP of 100% drives the actuator/valve to
its fully open position. In most cases, commercially available positioners allow
you to characterize the SP/position relationship to effect equal percentage or
fast open functionality.
Input Data
The format of input data unit is shown in this table.
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10
READBACK (Value, IEEE float) Status POS_D Status CHKBK CHKBK CHKBK
The recommended module selection provides for a good deal of information to

be brought back to the master through the data exchange telegram. The first
four bytes of the input (slave device to master) provide the value of the
READBACK parameter, which is the actual control valve stem position. This
value is the data brought back to the master for utilization if a mismatch occurs
between SP and actual READBACK. Byte 5 of the input is the status of the
value READBACK. The parameter POS_D provides a discrete representation
of actual control valve stem position.
Table 9-9 gives position information as a function of the POS_D value.
Table 9-9. POS_D Interpretation
Actual Position POS_D

Not Initialized 0
Closed 1
Open 2
Intermediate 3
Byte 7 of the input DU is the status for POS_D.

Bytes 8-10 are the value of the parameter CHECKBACK.
Keeping the above in mind, the balance of the failsafe facilities can be
examined. The setpoint value (SP) to the PA AO block contains both value and
status. For the SP value to be effective, the status needs to be written and is
normally 0x80. However, provision has been made in the PROFIBUS-PA
profile that if the setpoint status written is 0xA0, the PA AO block will go to
failsafe after the expiration of FSAFE_TIME. This feature is further supported

by the DCI ROUT block and these details are illustrated by way of example in
“PA Positioner” on page 318.
Ideally, when failsafe is asserted in the AO block this would have been
indicated in the status value of READBACK. While not supported in that
parameter, a bit in the CHECKBACK parameter is made available, hence the
selection of the recommended module. In the implementation of the ROUT
block interfaced to a PA AO block, the CHKBK failsafe bit is mapped to the
DCI ROUT BLKSTA parameter. This in turn is used in the default detail
display of ROUT.
DCI ROUT Block Functionality

As with the other members of the DCI block family, the ROUT block has been
upgraded significantly as of Release 8.4. The primary area of focus was
alarming, however the block and the FBM222 have been more tightly coupled
in support of PROFIBUS-PA positioners.
A completely worked out example of the use of the ROUT block with a
positioner is presented in “PA Positioner” on page 318, which presents the
extensions to PNT_NO syntax that cover the use of function block status and
READBACK. However, it is necessary to understand the functionality of the
ROUT block from a block perspective. The ROUT block, coupled with the
FBM222 and the PA AO block, provides support for the use of SETFS and
mapping from the PA AO block CHECKBACK parameter, the confirmation
that the device is in failsafe. The ROUT block supports the SETFS block,
which enables you to force the slave device into failsafe. This parameter is not
supported by the FBM223, but is now supported by the FBM222.
BLKSTA
Table 9-10 shows the ROUT block uses the BLKSTA parameter. For the
failsafe bit to function properly, you need to use the module:
“PA Positioner” on page 318 covers other recommendations for proper
positioner operation.
Table 9-10. ROUT Block BLKSTA Parameter

3 LO Local override BLKSTA.B29
6 TRK Device Initializing BLKSTA.B26
7 HLD Block Output Holding BLKSTA.B25
8 FBM FBM failure detected BLKSTA.B24
11 MA Block is in Auto mode BKKSTA.B21
14 UDEF Block is undefined BLKSTA.B18
15 ON Compound is on BLKSTA.B17
20 LCK Access Locked BLKSTA.B12
22 OUTOPT option is set BLKSTA.B10
Table 9-10. ROUT Block BLKSTA Parameter (Continued)

23 DCI Enhance DCI block (FCP280 or CP270 BLKSTA.B9
Only)
24 FS Fail-Safe Active BLKSTA.B8
a. Bit 0 is the least significant bit (starting from the right).
VALSTS
READBACK status is mapped bit-for-bit into the ROUT block parameter
VALSTS. However, for a given state of the positioner, different devices are
going to exhibit different status behavior. “PA Positioner” on page 318
includes notes with respect to these different behaviors in the device.
ROUT Block Initialization

The PROFIBUS-PA AO function block does not support the FOUNDATION
fieldbus IR/ACK handshake in a manner that would have allowed an
initialization scheme as used in the DCI AO block. While that was not realized,
if you implement the recommended module, the ROUT block initializes the
present value of the valve position, which need to cover most applications.
Confirmed Outputs
The ROUT block OUT parameter is a confirmed output. A confirmed output
contains two components: a request value and a readback value. The request
value is changed by the system and sent to the field device, and the readback
value is the value read back each cycle from the FBM222. In the ROUT block,
the request value is made available for diagnostic purposes as parameter
OUTQ. The readback value is shown as the parameter OUT.
The purpose of the confirmed output is to help ensure that an output is not
displayed to you until that new value has been driven down as close to the
device as possible, and then read back to verify that the value has been written.
Generally speaking, the closest possible level is the FBM. However, with the
FBM222, the confirmed write can go way down to the device and read back
from the device’s actual value (such as the actual valve stem position, not the
commanded position) providing the device is capable of supporting a true
readback parameter and the DCI block has been properly configured.
This true confirmed write provides two main advantages:
• You can readily determine from the block default detail display
differences between the commanded value to the device and its present
position (PV), and quickly detect improper device operation.
• If the device goes to a failsafe position, the question by default is, “How
does the control scheme connected to the device have a sense of PV as the
failsafe condition clears?” With readback of PV, no ambiguity exists, the
control scheme recovers at the PV of the device, and thus there is no bump
during failsafe recovery.
Configuring Input DCI Blocks
Analog Inputs
This section describes configuration of DCI blocks for analog input from DP
and PA devices.
DP Devices
A typical PROFIBUS remote I/O system is likely to contain many analog input
modules for current, voltage, temperature, and so on. In this example, the Point
Configuration String is constructed to read the output of the first of four analog
inputs from the module 750-460 (selected in Figure 9-19).
The documentation for the 750-460 indicates that module provides analog data
from four RTD channels as signed integers in eight bytes (data type S). This
example is representative of the DCI block configuration for a typical analog
input point. Usually, DP devices support analog input points as two-byte
signed integers.
Figure 9-19. Example Four-Channel RTD Module
To configure access to the first channel in the example module:

1. Select the appropriate input DCI block that supports signed integer (as
shown in Table 9-2) and add the block to the strategy.
We recommend the RIN block for this example and other analog inputs.
2. Specify the device ECB in the RIN block IOM_ID parameter
(PROF01_ECB.RIO002).
Note In the Configured Modules pane in Figure 9-19 there are six bytes in the
input data before the start of the eight bytes from the selected module. Thus,
the offset for the data for the first channel in the module is 6. With a data length
of 2 for each channel, the offsets for channels 2, 3 and 4 are 8, 10 and 12,
respectively.
3. Enter the string X6S2 (described in Table 9-11) in the RIN block
PNT_NO parameter.
Table 9-11. Point Configuration String for First Channel in Module

750-460
Element Entry Description

<Status> Status is not specified as the module is a DP slave
device.
<CXN Type> X The point is being configured for cyclic data
exchange. If the CNX Type were to be omitted this
would be the default. It is suggested you specify this
field to lend clarity to database entries.
<Offset or 6 Offset is determined by the number of bytes ahead of
S:I> the module and channel in the input data.
<Data Type> S From the device documentation for this RTD I/O
module it has been determined that temperature is
presented as a signed integer.
<No. Bytes 2 From the device documentation it is known that the
(or CBN)> signed integer is two bytes long.
[<Swap>] No swapping is needed
[<ext>] As the data type being used is S, no extension entry is
needed
4. Set the input scaling parameters in the RIN block.

Table 9-12 shows the scaling parameter values that are appropriate for this
example.
Table 9-12. Example Scaling Parameters
Parameter Value Description

SCI 0 With the RIN block using data type S for signed
integer, the block performs the conversion to a real
value and no SCI is needed.
MGAIN 0.1 See “Scaling” on page 280.
MBIAS 0.0 The RIN block default.
HSCI1 400.0 The high scale value for the RIN blocks bar graph
for its detail default display
LSCI1 0.0 The low scale value for the RIN blocks bar graph for
its detail default display
EI1 DEG The device provides temperature in degrees C
C
5. Configure the other RIN block parameters to meet application

requirements, referring to the RIN block chapter in Integrated Block
Control Descriptions B0193AX).
PA Devices
PROFIBUS-PA, while not offering as broad a spectrum of product as
PROFIBUS-DP, does offer a number of more traditional field devices such as
pressure, temperature and flow transmitters, and control valve positioners.
Integrating a PA transmitter into a control system is much like integrating a DP
slave device with a few additional considerations.
Again the DCI RIN block is recommended. For the PA transmitter, the
telegram between master and slave can be remarkably simple (Figure 9-20).
Figure 9-20. Transmitter Pressure Value and Status
Bytes 0 to 3 are the value of pressure and byte 4 is the status byte. From the
device documentation it is known that the value is presented as an IEEE float.
The Point Configuration string is HX0F4, as shown in Table 9-13.
Table 9-13. Point Configuration String for a PA Transmitter
Field Entry Description

<Status> H H is used as the device is a PA device. This helps
ensure that PA status is utilized in block operation
<CXN X X is used as communication with a PA transmitter’s AI
Type> block OUT parameter is through cyclic data exchange
<Offset or 0 0 is used for offset as the float begins at byte 0
S:I>
<Data F The value is an IEEE floating point number
Type>
<No. Bytes 4 Specifies the four bytes of the float
(or CBN)>
[<Swap>] No swapping needed
[<ext>] As the data type being used is F, no extension entry is
needed
As with the DP device example, additional RIN block parameters are needed to
finish the slave device integration. For all PA transmitters the value being read
is in IEEE floating point format. This means that this value is in engineering
units and the actual range of this float is determined by device calibration.
In this example, the slave pressure transmitter was scaled -1 to 4 BAR, so that
the range of values from this device are in this span and you do not need to
provide any further scaling. TheLSCI1 and HSCI1 can be manipulated at will
without affecting the zero and span of the device, enabling you to zero
suppress the default detail display bar graph.
Table 9-14. Example RIN Block Configuration for Input from a PA

Transmitter
Parameter Value Description

IOM_ID PROF01_ECB:PA000 The ECB compound and device ECB
1
PNT_NO HX0F4 See Table 9-13
SCI 0 As the RIN block is using Data Type
F (for float) the block performs the
conversion to a real value and no SCI
is needed
MGAIN 1.0 The RIN block default
MBIAS 0.0 The RIN block default
HSCI1 4.0 The high scale value for the RIN
block’s bar graph for its detail default
display
LSCI1 -1.0 The low scale value for the RIN
blocks bar graph for its detail default
display
EI1 BAR The device provides the pressure
reading in bars.
With H for <Status> in the point configuration string, the DCI block acquires a
status from the device in addition to the floating point value. As noted in “PA
Status Handling” on page 265, the PROFIBUS-PA value status is decoded by
the system and presented as the DCI block status.
Consult the device documentation with respect to status, as there are variations
in the way various vendors implement status. Table 9-15 is a general
presentation of PROFIBUS-PA status.
Table 9-15. PROFIBUS-PA Status Construct
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Quality Quality SubStatus Limits
See Table 9-16 See Table 9-17 through Table 9-20
Table 9-16. PROFIBUS-PA Quality Construct
7 6 5 4 3 2 1 0 Meaning

0 0 See Table 9-17 Bad
0 1 See Table 9-18 Uncertain
1 0 See Table 9-19 Good (non Cascade)
1 1 See Table 9-20 Good (Cascade)
Table 9-17. PA Quality SubStatus When Quality = BAD
7 6 5 4 3 2 1 0 Meaning

0 0 0 0 0 0 Non-Specific
0 0 0 0 0 1 Configuration Error
0 0 0 0 1 0 Not Connected
0 0 0 0 1 1 Device Failure detected
0 0 0 1 0 1 No communication, last usable value
0 0 0 1 1 0 No communication, no usable value
0 0 0 1 1 1 OOS
Table 9-18. PA Quality SubStatus When Quality = Uncertain
7 6 5 4 3 2 1 0 Meaning

0 1 0 0 0 1 Last usable value
0 1 0 0 1 0 Substitute-set
Table 9-19. PA Quality SubStatus When Quality = Good NonCascade
7 6 5 4 3 2 1 0 Meaning

1 0 0 0 0 0 OK
1 0 0 0 1 0 Active Advisory Alarm
1 0 0 0 1 1 Active Critical Alarm
1 0 1 0 0 0 Initiate Failsafe
Table 9-20. PA Quality SubStatus When Quality = Good (Cascade)
7 6 5 4 3 2 1 0 Meaning

1 1 0 0 0 0 OK
1 1 0 0 0 1 Init Ack
1 1 0 0 1 0 Init Request
1 1 0 0 1 1 Not Invited
1 1 0 1 1 0 Local Override
1 1 1 0 0 0 Initiate Failsafe
Digital Inputs
A typical PROFIBUS remote I/O system is likely to contain many digital input
modules for use with their values embedded in byte streams. This section
provides examples of how the Point Configuration String is used to extract the
data from the byte stream and get the value into the Object Manager through a
DCI block.
Figure 9-21 shows a two-channel digital input module (750-400) selected in
the Configured Modules for the remote I/O system RIO002.
Figure 9-21. Digital Input Module
To configure access to the module in the example:

1. Select the appropriate DCI block or blocks to extract the data from the
module as unformatted raw data (see Table 9-2), and then add blocks to
the strategy.
Use of a single PAKIN block rather than two BIN blocks results in fewer
blocks being used for data exchange. PAKIN presents significant
efficiencies with modules or compact devices that use multiple digital
input channels.
2. Specify the device ECB in the PAKIN block IOM_ID parameter
(PROF01_ECB.RIO002 in the example).
Note The one byte containing the two inputs from the 750-400 is the first byte
in the input stream and thus the offset is 0.
3. Specify the point number as X0R1 in the PAKIN block PKINGP

parameter, as described in Table 9-21.
Table 9-21. Point Configuration String Elements for Digital Input

<Status> Status is blank as the module is a DP slave device.
<CXN Type> X X is used as communication is with a DP slave in
cyclic data exchange
<Offset or S:I> 0 0 is used for offset as the raw value begins at byte 0
<Data Type> R R is entered for data type raw
<No. Bytes (or 1 This two-channel DI module only needs 1 byte for
CBN)> data exchange.
[<ext>] As the data type being used is R, no extension entry
is needed
We generally recommend that the PAKIN block be used for digital inputs
because of the efficiency of this block as it can support up to 32 bits (4 bytes)
of data. However, the use of PAKIN blocks does come at the cost of a certain
amount of complexity. Hopefully the examples provided here helps minimize
the confusion and assist you with respect to the trade-offs involved.
The PAKIN block has two configuration parameters which needs to be
considered:
• PAKCIN holds the input from the device as processed by the block.
• PKIOPT specifies whether the bit order in the input stream (1 through 32)
is maintained (the default) or inverted (32 through 1) in an end-to-end
swap.
Figure 9-22 shows the default display for the example PAKIN block with
PKIOPT defaulted and PKINGP set to X0R1. The value from the module is
0x01.
Figure 9-22. PAKIN Default Detail Display Faceplate
The faceplate displays what is documented in the control processor as a

Boolean connection in the lower part of the screen that shows boxes labeled 1
through 32. For the input byte being 0x01 the Boolean connection B01 is high.
If a connection were made to DP:X_7541D.PAKCIN.B01 the Boolean value

would be TRUE.
However, the faceplate shows a displayed value of PAKCIN of 0x80000000,
because the PAKIN block takes the Boolean connection order and treats B01 as
bit 32 of a 32 bit construct and Boolean connection B32. We recommend that
you ignore the PAKCIN value display, use a PKIOPT of 1 (default), and
interpret the input from the device as 1 to 32 Boolean connections. If you adopt
this convention, fanned out connections to other blocks are more readily
debugged as the connections in the control database are made from B01
through B32.
PKIOPT and Switch Option

Another example is presented to show how the Point Configuration String can
affect processing and display of the value to facilitate monitoring of device
operation.
Figure 9-23 is a bus trace that captures a data exchange for a ProfiDrive
device.
Figure 9-23. ProfiDrive Telegrams
The response telegram from the slave device contains four bytes. The first two
bytes (13 37 hex) contain a status word from the device and the last two bytes
contain the actual drive rpm (4E 20).
The device documentation arranges the explanation of the 16 status bits in the
order shown in the table. The values in the second row are the byte string 13 37
hex in the form suggested by the vendor documentation.
Status Word – Bit Layout

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 0 0 1 0 0 1 1 0 0 1 1 0 1 1 1
The intent is to have bit 0 when set TRUE cause Boolean connection B01 go
TRUE. While you need to adjust for the 0-1 discrepancy, the PAKIN at least
provides a display of the bits of the respective bytes that makes it easier to
recognize device status by visual inspection.
To more closely accommodate the vendor format in the PAKIN to display the
Status word:
• Set the PKINGP parameter to XOR2W1, where W1 inverts the order of
the two bytes, but not the bit order within the bytes.
Figure 9-24 shows the resultant status word display.
Figure 9-24. PAKIN Status Word Display
While the PAKCIN value provides no utility, the Boolean connection display
mimics the bit pattern extracted from the telegram data unit (13 37 hex). And
further, with the PAKIN block in service, you can bit-pick from the Boolean
connection values to fan these out into control schemes and operator displays.
Configuring Output DCI Blocks

The section covers construction of the point configuration strings for outputs
from the system to the slave devices. The output values are determined by the
CP-resident control blocks and directed to the FBM222 through ROUT blocks
and other output-type DCI blocks. The FBM222 in turn writes the outputs to
the target devices and modules in cyclic data exchange.
Analog Outputs
This section provides examples of outputs to DP device modules and to PA
devices.
DP Devices
PROFIBUS-DP devices that support analog outputs range from compact
devices that provide a few current or voltage outputs to more feature-rich I/O
modules that are inserted into a remote I/O system and may support both inputs
and outputs.
The example in this section is the four-channel output module (750-559)
selected in the Configured Modules pane for the remote I/O system RIO002 in
Figure 9-25.
Figure 9-25. Example Four-channel Analog Output Module
The documentation for the 750-559 indicates that each of its four channels is
capable of 0-10 V dc output, and that the module uses a two-byte signed
integer as its D/A converter input.
To configure output to channel 1 of the 750-559 in the example:
1. Select the appropriate output-type DCI for signed integers (as listed in
Table 9-2) and add the block to the strategy.
We recommend the ROUT block for interfacing the channels of an analog
output module such as the 750-559.
2. Set the block IOM_ID parameter to PROF01_ECB:RIO002, the device
ECB for the remote I/O system.
Note The 750-559 follows a one-byte output in the output data (Figure 9-25),
and that data for each channel in the module is a 2-byte signed integer.
3. Set the OUT parameter to X1S2, as described Table 9-22.
Table 9-22. Point Configuration String for an Analog Output

device.
<CXN X The point is being configured for cyclic
Type> communication from FBM to the slave device.
<Offset or 1 The offset is determined by the order of the module
S:I> within the devices output data and the channel within
the module.
Table 9-22. Point Configuration String for an Analog Output

<Data S Signed integer for the output channel, as indicated in
Type> the device documentation
<No. Bytes 2 The data for each channel is two bytes per the device
(or CBN)> documentation.
[<ext>] As the data type being used is S, no extension entry is
needed
Usually, the PROFIBUS-DP analog outputs are handled as signed
integers, and are based on an entire range of output values between 0 to
32767, or -32768 to 32767 (to cover a ± range). For the 750-559 in the
example:
• 0 V dc is a signed integer value of 0
• 10 V dc is a signed inter value of 32767
The ROUT block can handle this range with its Signal Conditioning
Output parameter (SCO). The ROUT block supports a number of signal
condition indices, but these two are frequently used.
• SCO = 51: Linear (-32768 to 32767) x = (y - LSCO1) *
65535/(HSCO1-LSCO1) - 32768
• SCO = 52: Linear (0 to 32767) x = (y - LSCO1) * 32767/(HSCO1-
LSCO1)
So in this example, if the LSCO1 parameter is set to 0 and HSCO1 is 10, if
the parameter MEAS reads a value of 10, the output of the ROUT block is
32767 (integer) or 7F FF hex, and the voltage output of the I/O module
would be full scale or 10 V dc.
4. Set the scaling parameters as shown in Table 9-3.
Table 9-23. ROUT Block Configuration Parameters
Parameter Entry Description

SCO 52 From above
GAIN 1.0 The ROUT block default
BIAS 0.0 The ROUT block default
HSCO1 10.0 The high scale value for the ROUT block’s bar
graph for its detail default display
LSCO1 0.0 The low scale value for the ROUT block’s bar
graph for its detail default display
EI1 Volts To match the device output
Note The ROUT block parameters can be used for scaling purposes if
you want to change LSCO1 and HSCO1.
5. Refer to Integrated Control Block Description (B0193AX) for information

configuring the remaining ROUT parameters.
PA Devices
For an example of analog output to a PROFIBUS-PA device see “PA
Positioner” on page 318.
Digital Outputs
DP Devices
The eight-channel output module (750-530) selected in the Configured
Modules pane for the remote I/O system RIO002 in Figure 9-25 provides an
example of how to configure output to a multi-channel digital output module.
Figure 9-26. Example Eight-Channel Digital Output Module
The WAGO 750-530 is quite typical of PROFIBUS discrete output devices. It

supports 8 channels, each capable of driving 24 v dc up to a 0.5 amp load,
supporting a wide variety of field components such as relays. The relationship
between the byte written to the module and the module’s output channels is
shown in the table:
Bit 7 6 5 4 3 2 1 0
Channel 8 7 6 5 4 3 2 1
To configure output to the example module:

1. Select the appropriate output type DCI block for digital outputs (as listed
in Table 9-2) and add the block to the strategy.
We recommend the PAKOUT block is generally recommended for digital
outputs because the block’s output parameter (PAKCO) supports 32 bits, a
more efficient block use than configuring multiple blocks (in this case,
eight BOUT blocks).
2. Set the block IOM_ID parameter to PROF01_ECB:RIO002, the device

ECB for the remote I/O system.
Note The 750-530’s single byte of output data is the first byte in the output
data (Figure 9-25), and that the channels are bits 1 through 8, respectively.
3. Set the PKCOGP parameter to X0R1, as described Table 9-24.
Table 9-24. Example Point Configuration String for Digital Output
Element Entry Description

device.
<CXN Type> X X is entered as the communication from FBM to
the slave device utilizes cyclic data exchange.
<Offset or S:I> 0 0 is entered as this is the offset to get to the first
byte of interest within the telegram to “address”
the channel of interest.
<Data Type> R R is entered as in this example the use of type
Raw is appropriate
<No. Bytes (or 1 1 is entered as the vendor documentation
CBN)> indicates the use of 1 byte to support the 8 DO
channels
[<ext>] As the data type being used is R, no extension
entry is needed
Figure 9-27 is the default display for the PAKOUT driving the module.
Figure 9-27. PAKOUT Default Detail Display
The display shows a value of 0xF0000000 hex for the PAKCO parameter.
Given the PKCOGP setting of X0R1, the PAKOUT block is only driving one
byte, that is, eight independent bits, whereas the block can accommodate up to
four bytes. The value display of PAKCO labels of 0 through 7 as 1 through 8.
Swapping Used with Digital Output

One more digital output example is presented in the context of a PROFIBUS
variable speed drive that fits the ProfiDrive specification. Figure 9-28 shows
the data exchange between master and slave device. The values displayed here
are normal with the drive setpoint at optimum speed (100%).
Figure 9-28. ProfiDrive Telegrams
The first two output bytes (04 FF) contain the drive permissives, that is, the
bits that need to be set for drive operation. The user guide for this drive
provides the documentation for these two bytes as:
Control Word
bit bit bit bit
15 8 7 0
To more closely align the PAKOUT bit pattern (1-32) to the layout of the
Control Word, this Point Configuration String is suggested:
X0R2W1
The W1 syntax swaps the two bytes of PAKCO. With this swap, if bit 1 of
PAKCO is set high, bit 0 (as labeled in the documentation) of the control word
is set. So except for the 0-1 offset, the PAKOUT bit display shows the setting
of the bits in the Control Word.
Figure 9-29 shows the default detail display for the PAKOUT using the swap
option in the syntax for PKOCGP.
Figure 9-29. PAKOUT Default Detail Display
The bit pattern shown in Figure 9-29 results in the setting 04 FF hex in the first
two bytes of the telegram to the slave device. The value of PAKCO shown in
the display does not match. However, the bit patterns closely align, making it
easier to visualize what bits in the control word are being set.
PA Devices
The PROFIBUS-PA market does not provide many examples of discrete
output devices. However, Pepperl & Fuchs markets a discrete valve controller,
which is described in an extended example in “Discrete PA Valve Controller”
on page 326.

The swap example in “Digital Inputs” on page 291 presented data in a format
that made visualization of a device status more closely match the presentation
in the vendor’s documentation.
The data types S, U, F, and E provide for an implicit swap. For floats, signed
and unsigned integers this implicit swapping makes it easier to convert
telegram byte data to reals.
Figure 9-30 shows a cyclic data exchange between an FBM222 and a PA
pressure transmitter. To bring the value and status from this device into a RIN
block, the PNT_NO parameter is set to HX0F4. The swap option is not used,
but that an implicit swapping exists to arrange byte order suitable for
conversion by the RIN DCI block.
Figure 9-30. Data Exchange with a PA Transmitter
The readback value from a device is a 32-bit integer by default whereas the
transferred data (value sent to the device) depends on the number of bytes as
specified in the data type.
IIN, IOUT, PAKOUT and PAKIN values are 32-bit integers, consisting of 32
single bits:
• Bit 1 is the low order bit of the integer value.
• Bit 32 is the high order bit of the integer value.
A PAKOUT or IOUT value has 32 bits, but you can send fewer bits to a device,
and you can adjust the readback value to the limits which are used by the
device. The limits are valid for the PAKOUT and IOUT blocks and depend on
the point type:
• Unsigned Integers (U) and Signed Integers (S)
The values are limited to the maximum and minimum integer values for
the chosen number of bits. Any value lower than the minimum is set to the
minimum and any value higher than the maximum is set to the maximum.
For example:
• U2 values can only be in the range 0 to 65535; any negative value is
set to zero, any value higher than 65535 is set to 65535.
• S1 values can only be in the range -128 to +127; any value lower than
-128 is set to -128, any value higher than +127 is set to +127.
• Raw Bytes (R)
The FBM222 copies the specified bits from the integer value, and sets to 0
those bits that are not to be transferred.
For example:
• R1 sends only the lowest 8 bits, bits 9 to 32 are set to 0.
• R3 sends only the lowest 24 bits, bits 25 to 32 are set to 0.
• Packed Bits (P)
The values are limited to the maximum and minimum integer values for
the chosen number of bits. Any value lower than the minimum is set to the
minimum and any value higher than the maximum is set to the maximum.
For example
• P1 values can only be in the range -128 to +127; any value lower than
-128 is set to -128, any value higher than +127 is set to +127.
There are two different types of interpretation of an integer value:
• Numerical when the data type is an unsigned integer (U) or a signed
integer (S)
• Bit-wise when the data type is raw unformatted (R) or packed bits (P)
The integer can make up multiple combinations:
1. U-type/S-type (numerical interpretation).
Numerical value restricted to its maximum/minimum limits.
2. R-type and P-type (bit-wise interpretation).
Bit array, the unused bits cleared.
3. R-type (numerical value to bit array).
You need to translate among:
• Numerical value, translated to a bit array
• Unused bits of the bit array cleared and transferred
• Resulting bit array re-translated to a numerical readback value.
The commonly used combinations are numerical and bit-wise.
For example:
• If you specify 0P1 for PAKOUT, the PAKOUT can contain -128 to +127,
but the value is treated as a 32-bit entity (not an 8-bit entity). Specifically,
-128 is 0xFFFFFF80 (not 0x80000000 or 0x00000080). In this example
0P1 the value is limited to -128 to +127, both for the readback value and
the transferred value:
The 32-bit readback value is 0XFFFFFF80...0X0000007F (-128 to +127)
The transferred value is 1 byte (the low order byte) 0x80 to 0x7f (which is
also, -128 to +127).
Using the Extended Data Type

The Extended data type (E) enables you to extract bits from one to four bytes.
When the type is E, three extensions can be used to define the bits to be read or
written to:
• S and a position number indicate the sign bit in a signed integer. S0
specifies that there is no sign. Omitting the modifier defaults to S0.
• C and a number specify the complement, as follows:
C0 specifies no complement (= unsigned). Omitting the modifier defaults
to C0.
C1 specifies one’s complement.
C2 indicates two’s complement.
• LxHy defines the range of bits where x is the starting bit position and y is
the ending bit position.
For example, the string X0E2S3L4H14 in an IIN block PNT_NO is used to
specify a sequence of bits in the input data from a slave device. The elements
of the strings are shown in Table 9-25.
Table 9-25. Point Configuration String for Data Type E Example

<Status> Status is left blank as the module is a DP slave
device
<CXN Type> X The communication is with a DP slave in cyclic
data exchange
<Offset or S:I> 0 There is no offset as the data begins with the
low-order byte
<Data Type> E The data type is Extension
<No. Bytes (or 2 Data length is 2 because the bits are from the
CBN)> first two bytes
extensions Extensions define the bits to be included:
<Sn> S3 Bit 3 contains the sign
<Cn> - No Complement is specified
<LxHy> L4H14 The data range is bit 4 to bit 14, a total of 11 bits
Figure 9-31 shows how the entry parses the data.
IIN Block with PNT_NO = X0E2S3L4H14

DCI Connection (in FBM)
PROFIBUS Data I/O Stream
4 3 2 1
1 8 7 6 5 4 3 2 1
(High Byte) (Low Byte) 2 16 15 14 13 12 11 10 9
3
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Figure 9-31. Data Type E Examples
It is not unusual for vendors to use bits within a telegram byte as bit
enumerations. The syntax gives you the flexibility to parse bits. While this
flexibility is offered, you need to use as few DCI blocks per segment as
possible to minimize PIO bus load.
Using the Packed Bits Format

The Packed Bits (P) data type selects single contiguous bits from up to four
bytes. This format is the same as the Extended Format except that Packed Bits
does not have the arguments for sign (S) and complement (C).
The bits are identified in the Point Configuration String by the modifiers L for
starting bit position and H for ending bit position.
For example, the packed bits format is used with two PAKOUT blocks to
concatenate two bit strings into one and insert the string into the output data
unit. The PKCOGP parameters in the two PAKOUT blocks are set as follows:
X0P1L1H2
X0P1L3H4
The elements of the two strings are shown in Table 9-26 and the mappings are
shown in Figure 9-32.
Table 9-26. Point Configuration String for Data Type E Examples

<Status> Status is left blank as the module is a DP slave
device
<CXN Type> X X is used as communication is with a DP slave in
cyclic data exchange
<Offset or S:I> 0 There is no offset as the data begins with the low-
order byte
<Data Type> P P is entered for packed bits
<No. Bytes (or 1 Data length is 1 because the bits are from within the
CBN)> first byte
Table 9-26. Point Configuration String for Data Type E Examples

[<Swap>] - No swapping is needed
extensions L1H2 In the first string the first two bits are selected
<LxHy> L3H4 In the second string the selection starts with bit 3
and ends with bit 4
PAKOUT Block with PKCOGP = X0P1L1H2

and
PAKOUT Block with PKCOGP = X0P1L3H4
DCI Connection (in FBM) PROFIBUS Data I/O Stream

4 3 2 1
1 8 7 6 5 4 3 2 1
(High Byte) (Low Byte)
2
3
8 7 6 5 4 3 2 1
DCI Connection (in FBM)

1 8 7 6 5 4 3 2 1
2
3
Figure 9-32. Data Type P Example
Reading Diagnostic Data

Type D (diagnostic type) makes it possible to bring a diagnostic into the Object
Manager.
Slave Diagnostics Details

During a data exchange between the FBM222 and a slave device, the device
indicates if it has a diagnostic condition. The FBM222 responds to the
indication by sending a Get Diagnostics request. The Get Diagnostic response
from the slave can use a variety of formats, but at a minimum starts with six
bytes of the standard PROFIBUS diagnostics.
Figure 9-33 is a PROFIBUS trace of a slave response to a Get Diagnostic
request, in which the slave sends only the needed diagnostic data.
Figure 9-33. Slave Device Response to Get Diagnostic Request
Standard Diagnostics
Every slave device needs to support a standard six-byte diagnostic telegram.
This data unit contains a generalized set of data useful for determining detected
faults in a startup mode. Table 9-27 shows how these mandatory six bytes are
used.
Table 9-27. Bit Definition for the Standard Diagnostic Bytes
Byte Bita Meaning When Set

1 0 Slave device does not exist (set by the master if the
master receives no response)
1 Station not ready for data exchange
2 I/O configuration is not supported by the slave
3 Slave has extended diagnostic data
4 Parameter function not supported
5 Invalid slave response (set by the master)
6 Parameter assignment wrong
7 Slave controlled by another master
2 0 Slave waiting for parameters
1 Static diagnostic flag
2 Always set
3 Watchdog is On
4 Slave is in Freeze Mode
5 Slave is in Sync Mode
6 Reserved (0 by default)
7 Slave is not being polled
3 0-6 Reserved
7 There are more than 238 bytes of diagnostic data to report
4 0-7 Address of the controlling PROFIBUS master
5&6 - PROFIBUS ID of the slave device
a. In each byte, bit 0 is the least significant and bit 7 is the most significant bit.
Table 9-28. Interpreting the First Two Bytes of the Standard Diagnostics
Values Interpretation Action

00 04 Slave device is happy and in data exchange; Slave just reports everything is OK.
the Watchdog is OFF
Check the master address in byte 4 in the
diagnostics.
Table 9-28. Interpreting the First Two Bytes of the Standard Diagnostics (Continued)
00 06 Slave device has static diagnostic, but is in Try to reset the device or check the device
data exchange. The FBM222 requests only documentation for possible reasons
diagnostics until bit byte 1, bit 6 is reset
00 0C Slave device is OK and in data exchange; Slave just reports everything is OK.
the Watchdog is ON
Check the master address in byte 4 in the
diagnostics.
02 04 Slave has not yet received I/O configuration Check whether the master has sent the
from the FBM222, or the slave is not ready configuration, otherwise check next cycles
for a configuration check; the Watchdog is
OFF
02 05 Slave is not ready because it has not yet Wait until FBM222 has sent a
received parameterization from the parameterization telegram
FBM222
02 07 Slave has static diagnostic and needs to be Wait until Master has sent a
parameterized and configured parameterization telegram and a
configuration telegram
02 0C Slave has not yet received configuration Check whether the master has sent a
from the FBM222, or the slave is not ready configuration telegram. Otherwise, check
for a configuration check; the Watchdog is next cycles
ON
06 05 Slave has received an incorrect Check the configuration telegram and
configuration request or an output data compare the configuration data and length
telegram with wrong length with the expected (real) data
08 04 Slave has extended diagnostic data and is in Check the extended diagnostic data
data exchange mode. The watchdog is
deactivated
08 0C Slave has extended diagnostic data and is in Check the extended diagnostic data
in data exchange mode. The watchdog is on
0A 05 Slave has extended diagnostic data and has Wait until FBM has sent parameterization
not yet received parameterization and and configuration telegrams. Then check
configuration from the FBM222 the extended diagnostics if the extended
diagnostics (byte 1, bit 3) is still set
0E 05 Slave has received an incorrect Check the configuration telegram
configuration telegram and has extended
diagnostics
12 05 If this bit is set, it is an indication that one Check the set parameter telegram and
or more of the listed functions are not whether the slave supports the requested
supported: function
• The Sync bit is set in parameterization
telegram but the device does not
support Sync mode
• The Freeze bit is set in
parameterization telegram but the
device does not support Freeze mode
• Reserved bits are set in
parameterization telegram
Table 9-28. Interpreting the First Two Bytes of the Standard Diagnostics (Continued)
42 05 • There is a parameterization fault Check the set parameter telegram and
detected if any one of these occurs: whether the slave supports the requested
Incorrect profibus ID function
• An invalid watchdog factor (=00)
• Incorrect device parameter
52 05 The parameterization telegram includes an Check the set parameter telegram and
incorrect device parameter and request for whether the slave supports the requested
functions not supported by the device function
Extended Diagnostics
The device vendor may also use extended diagnostics to provide more detected
fault detail to the master. The extended diagnostic data is presented as three
blocks of data:
• Device-Related Diagnostics
The device-related portion of the telegram is essentially “free form”; the
device manufacturer determines the meaning of the bits and bytes.
• Identifier-Module Related Diagnostics
This portion of the extended diagnostic telegram is used for detected fault
identification of modular devices. This part of the telegram follows a fixed
PROFIBUS format.
• Channel-Related Diagnostics
A portion of the extended diagnostic telegram is used to identify module
channel-related detected faults. This portion of the telegram also follows a
fixed PROFIBUS format.
These three blocks can be presented in any order after the standard diagnostics
and can vary in length. The first byte of each block, however, identifies the
type of diagnostic and length of the block.
Consult the device documentation to determine how the manufacturer uses the
extended diagnostic with the specific device type.
You can use the DCI blocks listed in Table 9-29 to read the standard
diagnostics.
Table 9-29. Data Type D Examples
Possible Number Possible

DCI Block of Bytes Swapping Comment
PAKIN D1 No Receives 1 binary byte
PAKIN D2,D3 W1 Receives 2 or 3 binary bytes
PAKIN D4 W1, W2, W3 Receives 4 binary bytes
IIN D1 No Receives 1-byte integer
IIN D2, D3 W1 Receives 2- or 3-byte integer
IIN D4 W1, W2, W3 Receives 4-byte integer
Table 9-29. Data Type D Examples (Continued)
Possible Number Possible

DCI Block of Bytes Swapping Comment
RIN D4 W1, W2, W3 Receives 4-byte float
STRIN D1 TO D80 No Receives 1 to 80 character string
Figure 9-34 is the faceplate for a PAKIN block configured to read the first two
bytes of the standard diagnostic data unit. The Point configuration string in the
PKINGP is 0D2W1.
Figure 9-34. Data Type D Example
The byte swapping (W1) makes possible the direct display. To achieve this
display that the PAKIN block PKIOPT parameter needs to be set to 3 rather
than the default value of 1. Of course, you may elect to build a custom display
and in this case some other syntax.
Acyclic Data Exchange

This section describes two types of acyclic communication that can be
configured for an FBM222 master and its slave devices:
• Acyclic Master Class 2 read and write requests
• PROFIBUS Live List
Acyclic Master Class 2 Read and Write Requests

The FBM222 supports Master Class 2 acyclic communication defined in
PROFIBUS-DPV1 as extensions to the PROFIBUS standard. These read and
write requests are accomplished between the normal cyclic request and
response message exchange, and are used to read and set various device-
specific parameters. Although acyclic communication can be used to access
process values, cyclic communication should be used instead.
Acyclic communication is used by engineering tools to configure certain high-

end DP and PA devices. The FBM222 support for acyclic communication is
not meant to replace such devices, but rather to enable you to
programmatically access individual device parameters. For example, if
supported by the individual devices, acyclic communications can write

changes to the devices’ timeout periods when certain process conditions apply.
As with cyclic communications, the system access is through the DCI blocks.
Input DCI blocks access the data on a periodic basis as specified in the block’s
UPDPER parameter. Output DCI blocks access the data on a change-driven
basis.
Note Vendor documentation of the device-specific parameters is necessary

for properly using acyclic communication to access the device parameters.
Figure 9-35 shows input being configured for acyclic data exchange between a
DCI PAKIN block (COMPND_002:WAGO) and the head module in a
WAGO 750-333 remote I/O system.
Figure 9-35. Acyclic Communication PAKIN Configuration
The device ECB path name (FCP002_ECB:X_7541) has been entered in the
ECB Identifier field (IOM_ID parameter), and the Point Number
Configuration (A0:8R1) is entered in the Packed Input Group Address field
(PKINGP parameter). The elements of the point configuration are shown in
Table 9-30.
Table 9-30. Point Configuration String for Head Module

<Status> Status is only supported in cyclic data exchange with a PA device
<CXN Type> A Specifies acyclic data exchange
<Offset or S:I> 0:8 Slot 0 in this case indicates the 750-333 head module; index is 8, per
the device documentation
<Data Type> R Specifies that the data type is raw, unformatted data
<No. Bytes (or 1 Specifies that 1 byte is transferred by this read operation; the data
CBN)> length was determined from vendor documentation
Table 9-30. Point Configuration String for Head Module (Continued)

[<ext>] As the data type being used is R, no extension entry is needed
The Packed Input Option (PKIOPT) parameter is set to 3 to properly arrange

the data bytes of the value PAKCIN.
The value of UPDPER sets the polling interval, in milliseconds, of the FBM
master to the slave device.
The resulting DCI PAKIN block FoxView display in Figure 9-36 shows the
configuration parameters and the value of PAKCIN, 0x4D.
Figure 9-36. Acyclic Communication PAKIN FoxView Display
With PKIOPT set to 3, the block performs a bit reversal of the one byte being
read in from the device into the four-byte buffer of the block. With this option,
PAKCIN reads 00 00 00 4D which may prove more readable.
The grid portion of the Faceplate does not show bit position but rather the
Boolean values. The input 00 00 00 4D is converted to a bit representation
(00000000|00000000|00000000|01001101) where bit one is set. In the grid
display this is shown as B32. The syntax to retrieve this bit from PAKCIN is
COMPND_001:WAGO.PAKCIN.B32.
PROFIBUS Live List

For startup or test phases, the FBM222 provides special variables that allow
you to get a list of the devices connected to a port. Table 9-31 lists the DCI
blocks that you can build to verify which device addresses are alive on the
PROFIBUS network.
Table 9-31. PROFIBUS Live List
Block Parameter Identifier Description

BOUT PNT_NO PORT0LIVELIST Port 0 Trigger, every time the output
changes the live list for port 0 is updated.
PAKIN PKINGP PORT0LIVELIST0 Live list of port 0 for addresses 0 to 31, bit
1 = address 0, bit 2 = address 1 and so forth.
1 = address 32, bit 2 = address 33 and so
forth.
forth.
PAKIN PKINGP PORT0LIVELIST3 Live list of port 0 for addresses 96 to 125,
bit 1 = address 96, bit 2 = address 97 and so
forth.
BOUT PNT_NO PORT1LIVELIST Port 1 Trigger, every time the output
changes the live list for port 1 is updated.
1 = address 0, bit 2 = address 1 and so forth.
forth.
forth.
PAKIN PKINGP PORT1LIVELIST3 Live list of port 1 for addresses 96 to 125,
bit 1 = address 96, bit 2 = address 97 and so
forth.
Note Use live list function temporarily for only startup or testing purposes, as
these functions burden the PROFIBUS network with additional traffic.
The four PAKIN block detail displays in Figure 9-37 provide a live list of a
segment of slave devices and three masters (address 0, 1-2, and 100). These
PAKIN blocks can now be bit-picked to drive a custom graphic.
Addresses Addresses
0 to 31 32 to 63
Addresses Addresses
64 to 95 96 to 125
Figure 9-37. Live List Displays
Note These PAKIN blocks generate considerable PIO bus and PROFIBUS
traffic, and needs to be used primarily for temporary situations.
Programming Sync and Freeze Actions

On command from the control system, the FBM222 sends Sync and Freeze
commands to a group of devices or the devices on the specified port. The Sync
and Freeze action can be programmed using the IOUT DCI block.
Sync is an acyclic command sent to a group of output devices that forces them
to immediately process the last output received from the FBM222 and hold
that output while continuing to receive cyclic data. On receiving another Sync
command, the devices in the group process the last output received. The
devices hold the new output until receiving another Sync command or an
Unsync command. The function allows the simultaneous implementation of a
single output received by devices in the group over several processing cycles.
Freeze is an acyclic command sent to a group of input devices that forces them
to immediately the freeze the input images they send back to the FBM222. The
devices continue sending that image with each cyclic communication until
receiving another Freeze command, at which point they freeze the image to the
now current value, or until receiving an Unfreeze command.
To process a Sync or Freeze command:
• The device needs to support the command. The GSD file includes
Sync_Mode_support = 1 or Freeze_Mode_support = 1, respectively.
• The device needs to have the mode enabled in its device configuration.
Both modes are enabled for the modular device shown in Figure 9-38.
• The device needs to be assigned to the group specified in the Sync
command. For example, the input modules in the device in Figure 9-38
responds to a Freeze command sent to Group 1 or Group 3 (or to the
devices on the segment if Group 0 is specified).
Figure 9-38. Sync and Freeze Modes Enabled
The IOUT block is configured as follows for Sync and Freeze commands:
• The ECB Identifier (IOM_ID parameter) points to the FBM222’s ECB,
not a device ECB. For example, in Figure 9-39 the command is sent to
FCP001_ECB:PROF01.
Note If you use the ECB Browser to make this I/O assignment, a dialog
box prompts that the connection is not supported. You can ignore this
system message, and the ECB path name is inserted into the ECB
Identifier field.
• The Point Number (PNT_NO parameter) syntax identifies the port,

command and group:
PORT<0 or 1><SYNC or FREEZE><Group>
where 0 is used for Port 1 and 1 for Port 2.
and Group is 1 through 8 to send the command to a specific group, or 0 to
send to the devices on the segment.
Examples of the syntax are shown on Table 9-32.
Table 9-32. Sync and Freeze Command Examples
Point Number Description

PORT0SYNC6 Sync command sent to devices in group 6 on port 1
PORT1FREEZE2 Freeze command sent to devices in group 2 on port 2
PORT0SYNC0 Sync command sent to the devices on port 1
PORT1SYNC3 Sync command sent to devices in group 3 on port 2
(see Figure 9-39)
The Sync or Freeze command is sent when the LOUT parameter in the IOUT
block transitions from zero to a non-zero number or from a non-zero number to
any other non-zero number.
The Unsync or Unfreeze command is sent when the LOUT parameter in the
IOUT block transitions to from a non-zero number to zero.
Figure 9-39. Example Sync Command Configuration
315
C H A P T E R 1 0
Configuration Examples
The configuration examples in Chapter 9, “Control Configuration” dealt

mostly with a remote I/O system. This chapter provides additional
configuration examples using other device types.
Contents
• PA Transmitter
• PA Positioner
• Discrete PA Valve Controller
• DP Motor Starter
PA Transmitter
This section describes the integration of a simple PROFIBUS-PA transmitter
into a control system. The example device is a Siemens SITRANS P DSIII
pressure transmitter. Like majority PA transmitters, the DSIII has a number of
module options as shown in Figure 10-1. The Output module has been selected
in this example. The module provides the measured absolute pressure as a
floating point value (4 bytes) plus a status byte.
316 10. Configuration Examples
Figure 10-1. DSIII Device Configuration
Depending on the selected slave device, a number of different modules may be

offered. However, the primary measurement is generally formatted as follows:
OUT (Value, IEEE float) Status
The transmitter was factory-calibrated for -1 to 4 bars. As the pressure value is

presented to the FBM222 as an IEEE float, the negative value can be dealt with
by the DCI RIN block.
The device’s OUT parameter has an associated status, which is described in
“PA Status Handling” on page 265.
Device Parameterization
As shown in Figure 10-2, parameterization of this device is relatively simple:
only the first seven standard parameterization bytes are needed, and only a
single byte (0x94) is needed for device configuration.
10. Configuration Examples 317
Figure 10-2. Transmitter Parameterization
With parameterization done, the master and transmitter begins data exchange.
Figure 10-3 is an excerpt of a PROFIBUS bus trace showing the request from
the FBM222 followed by the response data from the transmitter.
Figure 10-3. Transmitter Pressure Value and Status
Higher Level Device Configuration

As with most PA field devices, configuration is a two-tier operation, with the
lower-level configuration handled through the basic PROFIBUS
parameterization scheme as shown in Figure 10-2, and higher level
configuration using the vendor’s DTM integrated into Field Device Editor,
keypad entry or a vendor-specific tools to change the factory calibration.
Refer to “Configuration Using the Manufacturer’s DTM” on page 207.
Keypad
The DSIII’s built-in keypad and related LCD display can be used for a number
of device maintenance and configuration purposes. As the DUT is a pressure
transmitter, the keypad use is optimized for performing zero and spans, but this
usage is by no means exclusive.
Foxboro Evo Configuration

The transmitter is integrated into the control database through a DCI RIN
block, which provides considerable functionality with the PA transmitter.
Table 10-1 describes key parameters for this example.
Table 10-1. RIN Block Parameter Settings for PA Transmitter
IOM_ID ECB Identifier is a configurable string that specifies the path
name of the ECB201 for transmitter.
PNT_NO The suggested Point Configuration String for this example is:
HX0F4. This syntax enables the FBM to implicitly read the
OUT and OUT status of the device AI block without further
configuration.
SCI Set to 0, as factory-calibrated PA transmitter provides in its
OUT value the measured value in properly scaled
engineering units. It would be unusual to use a non-zero SCI.
Table 10-1. RIN Block Parameter Settings for PA Transmitter
HSCI1 These two scaling parameters for the RIN block default detail
and display bar indicators and trend graph can be manipulated for
LSCI1 display zero and span suppression. These parameter values
are completely independent of the device’s scaling
parameters.
EI1 This parameter allows you to set an engineering unit string
for default detail display purposes. This string is completely
independent of the engineering unit of the slave device and
changing the EU1 string value has no scaling implications.
VALSTS With H specified in the Point Configuration String, the status
of the PA AI block OUT parameter is mapped to the RIN
block VALSTS parameter bit for bit. The status bits are
described in Table 9-17 through Table 9-20 starting on
page 290.
PA Positioner
This section covers the integration of a PROFIBUS-PA positioner into the
control system.
Slave Device Module Selection

Integrating a PROFIBUS-PA Positioner into the control system needs a
combination of the correct configuration of the device, the related DCI ROUT
block, and ECBs. A PROFIBUS-PA positioner is a modular device, with
software-based modules as configuration options (Figure 10-4). For optimum
device functionality in a control system environment, select:
Figure 10-4. Module Selected for a PA Positioner
The PA specification uses a function block model to describe the

characteristics and functions of various devices including positioners. The PA
analog output (AO) block provides the device with the value specified by the
control system. The block has a state machine, with modes of OOS, MAN,
AUTO, and RCAS. As no known commercially available PA device fully
supports the RCAS mode, no further documentation of this mode is provided.
The PA AO block defaults to an AUTO mode, so you can virtually ignore the
state machine unless you are using a higher level Class 2 Master tool to
perform configuration or calibration.
With the AO block in the AUTO mode, the SP value as written by the FBM222
master becomes the effective setpoint of this block, the value to which the
positioner drives the actuator’s actual position (the AO block READBACK
parameter). That is, the AO block drives the actuator until the value of
READBACK equals the SP value.
The first four bytes of the output data unit (master to slave device) provide the
setpoint to the slave device AO function block (Table 10-2). The last byte is a
status value associated with the value of SP. The five bytes are written together
in the data exchange to the slave. For the SP value to have the desired
operational effect on the slave, the status value in byte 5 needs to be equal to
0x80. This will be explained in the material below relating to the PROFIBUS-
PA slave AO function block.
Table 10-2. PA Positioner Output Data Unit

SP (Value, IEEE float) status
Generally speaking, the SP value is scaled 0 to 100%, with 0% being the SP to

drive the actuator/valve fully closed. A SP of 100% drives the actuator/valve to
its fully open position. In most cases, commercially available positioners allow
you to characterize the SP/position relationship to effect equal percentage or
fast-open functionality.
Table 10-3 shows the format of the input data unit.
Table 10-3. PA Positioner Input Data Unit

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 Byte 10
READBACK (Value, IEEE float) Status POS_D Status CHKBK CHKBK CHKBK
The suggested module selection provides for a good deal of information to be

brought back from the slave device to the master through the data exchange
telegram:
• The first four bytes of the input provide the value of the device AO
function block READBACK parameter, the actual control valve stem
position, to be compared with the SP.
• Byte 5 of the input is the status of the READBACK value.
• The parameter POS_D provides a discrete representation of actual control
valve stem position (Table 10-4).
Table 10-4. POS_D Interpretations
Actual Position POS_D

Not Initialized 0
Closed 1
Open 2
Intermediate 3
• Byte 7 of the input data is the status for POS_D.

• Bytes 8 through 10 is the value of the parameter CHECKBACK.
Checkback
The configuration option selected causes the parameter CHECKBACK to be
made a part of the input data. Table 10-5 shows how the bits are used in the
three checkback bytes.
Table 10-5. Bit Definition for the Checkback Bytes
Byte Bita Meaning When Bit is Set

1 0 The device is in Failsafe state
1 The device has received a request to go into Local
mode (a local pushbutton has been pressed)
2 The device is in Local mode
3 Binary input set
4 Control difference is out of limit
5-7 Reserved
2 0-1 Reserved
2 There has been a change in the device’s static
configuration. The bit is set for ten seconds after the
change
3 The readback is in simulation mode
4-5 Reserved
6 The positioner is inactive
7 Reserved
3 0 The device’s travel sum limit or cycle counter has been
exceeded
1-7 Reserved or unused
a. In each byte, bit 0 is the least significant bit and bit 7 is the most significant bit.
Status
Much like FOUNDATION fieldbus, PROFIBUS-PA uses a status construct to
provide additional information within cyclic data exchange data units. For
example, the PA AO block READBACK parameter has a status byte
associated with its floating point number. A readback status value of 80 (0x80)
indicates that the cascade is in a “good” state.
The PA Status is described in Table 9-17 through Table 9-20 starting on
page 290. Table 10-6 shows how bits 0 through 1 are used for limits for a PA
positioner.
Table 10-6. PA Positioner Status Bit Definition for Limits

Bit 1 Bit 0 Limits
0 0 OK
0 1 Low Limited
1 0 High Limited
1 1 Constant (OOS, MAN, or LO mode)
It is necessary to review the use of status in the SP context. The value of SP

(the floating point number) needs a suitable status value for the PA AO block
to treat the SP value as being a valid parameter. This configuration is taken
care of by the extended Point Configuration String (HX0F4 < HX0F4) with
the ROUT block to drive the PA device AO SP.

Generally speaking, the low level device configuration is quite straightforward
as the module to be selected for the PA positioner is in effect predetermined to
function properly in a control system environment. However, the
parameterization leading to cyclic data exchange is only a part of the overall
device configuration for a PA positioner. You need to be able to calibrate the
device to the actuator (linear or rotary) and perform other device setup
functions. Majority of the PA positioners in the market allow you to perform
these tasks through the vendor’s DTM, a local keypad and/or through a high-
level tool based on a Class 2 Master interface.
When the tasks are performed with the manufacturer’s DTM integrated into
Field Device Manager, the calibration data is with the device configuration in
the Galaxy. Refer to “Configuration Using the Manufacturer’s DTM” on
page 207.
Keypad
In most cases, the device vendor provides a keypad and LCD display for
performing device setup/maintenance tasks. The keystroke sequence,
information displayed, and setup regimen are unique to the vendor’s offering
and the device documentation needs to be consulted to effectively use the
offered functionality. Refer to the manufacturer’s documentation for details.
Foxboro Evo Control Core Services

Configuration
This section covers the necessary configuration data to integrate a PA
positioner, which includes configuration of selected parameters for the master
FBM222 ECB200/220, the slave device ECB201, and a DCI ROUT block.
FBM and Device ECBs

We recommend setting the failsafe parameters in the FBM222 ECB. See
“Setting ECB200/202 Parameters” on page 77 for instructions on editing the
FBM ECB.
Table 10-7 describes the Failsafe Enable (FSENAB) and Failsafe Delay
(FSDLAY) parameters, which needs to be set to integrate the device into the
Control Core Services failsafe functionality.
Table 10-7. FBM Tab Parameters for the ECB200/202
Failsafe Enable When Failsafe is enabled for a port, the FBM initiates whatever Failsafe
(FSENAB) action is configured in the devices on that segment if communication is
interrupted between the FBM and the control processor for longer than
the time specified in Failsafe Delay (or FSDLAY).
Use the pull-down list for Failsafe Enable (or FSENAB) to select one of
these options:
• 0 to disable failsafe logic for devices on both ports. This is the
default setting.
• 3 to enable failsafe logic for devices on both ports. We recommend
this setting.4 to enable failsafe logic for devices on Port 1 only, and
disable communication on the port once the failsafe actions have
been taken.
• 6 to enable failsafe logic for devices on both ports, and disable
communication on both ports once the failsafe actions have been
taken.
We recommend the configuration Failsafe Enable = 3 Enable failsafe
for both ports (PROFIBUS only).
Failsafe Delay When Failsafe is enabled for a port, the FBM initiates whatever Failsafe
(FSDLAY) action is configured in the devices on that segment communication is
interrupted between the FBM and the control processor for a longer time
than the time specified (in 10-msec increments) in Failsafe Delay (or
FSDLAY).
We recommend the configuration Failsafe Delay = 1000, which sets the
delay to 10 seconds.
For a PA positioner no unique detected configuration issues exist for the

device’s ECB201.
ROUT Block
Table 10-8 lists the ROUT block parameters that must be configured for
interfacing with the example PA positioner and the selected module.
Table 10-8. ROUT Block Parameters for Integrating a PA Positioner
IOM_ID ECB Identifier is a configurable string that specifies the path name of the ECB201
for the positioner.
PNT_NO We recommend Point Configuration String for this example HX0F4 < HX0F4.
This syntax enables the FBM to write implicitly to the SP and SP status of the
device’s AO block without further bookkeeping on your part. In addition, the
syntax provides for an implicit read of READBACK and status. Both SP and
READBACK are supported (0F4) by 4 byte IEEE floats.
ERROPT Error Option specifies the conditions under which MEAS is considered to have bad
status. It is used in determining whether there has been a bad-to-good transition of
MEAS.
If ERROPT = 1, MEAS is considered bad if it’s status word indicates Bad, Out-of-
Service, or Not On Scan. (If it is Not On Scan, the source of the connection has
been deleted or is in a nonexistent compound, or there has been a peer-to-peer
failure detected.)
If ERROPT = 2, MEAS is considered Bad in any of the above situations. It is also
considered Bad if the Error bit in the status of MEAS is True.
FSOPT Fail-Safe Option specifies the fail-safe conditions and action to be taken in an FBM
for an output point in a ROUT BLOCK:
Bit 0: 1 = assert fail-safe if input/measurement error. The ERROPT needs to be
configured nonzero for this option to take effect. Bit 1: 1 = set/clear fail-safe when
SETFS input is set/cleared.
Bit 2: 1 = assert fail-safe if control processor-to-FBM communication is lost (FBM
option). This option is enabled only if fail-safe is enabled at the FBM level through
the FSENAB parameter in the ECB200 or ECB202.
FSOUT The parameter FSOUT stores the failsafe value the ROUT block uses when in a
failsafe condition. Keep in mind that this value is not written to the device nor is it
read from the device.
Note Verify that the failsafe value in the device AO block and the failsafe value in
the ROUT block are identical.
OUTOPT Output Feedback Option is a configurable Boolean that specifies whether a

feedback signal of an analog output device exists. If OUTOPT=1, this feedback
signal is provided in the OUTFBK parameter.
We recommend that the setting is OUTOPT=1.
VALSTS The ROUT block supports the PROFIBUS-PA status with VALSTS. Mapping to
VALSTS is bit for bit (“PA Status Handling” on page 265).
Failsafe Considerations
To finish the configuration for the Failsafe support, you need to set device AO
block parameters listed in Table 10-9. These options are set to the values
appropriate to the application of the positioner in the process environment.
Table 10-9. PA AO Block Failsafe Parameters
FSTATE_TIME Specifies the time that the device waits without an update
of a new SP until the behavior defined by FSTATE_TYPE
is initiated.
FSTATE_TYPE Three options are provided:
• Exhaust the positioner resulting in the actuator
opening or closing using spring action
• Hold last value.
• Use the position specified in FSAFE_VALUE as the
failsafe position.
Note Mode during failsafe operation is AUTO
FSAFE_VALUE Noted as above.
Table 10-10 describes different Failsafe cases.
Table 10-10. Failsafe Scenarios
Event Response
SETFS The ROUT block supports the parameter SETFS. This
enables you to create a control scheme that would cause
the PA positioner to go to its Failsafe condition on
demand. When SETFS is set to TRUE, the status of SP
goes from 0x80 to 0xA0. This change of status results in
the slave device going Failsafe. This change in state is
confirmed by the CHECKBACK value (01 00 00).
Note The FSAFE_VALUE parameter is not sourced

from the ROUT block FSOUT parameter.
Compound OFF If you turn off the compound within which the ROUT
block is functioning, the ROUT block asserts Failsafe by
changing the SP status to 0xA0. The result is the same as
SETFS.
ROUT MEAS When the ROUT MEAS parameter status is BAD, the
Goes BAD ROUT block asserts Failsafe by changing the SP status
to 0xA0. The result is the same as SETFS.
Interrupt the PIO When the FBM loses communication with the Control
Bus Processor, the FBM asserts Failsafe to the device by
writing a status value of 0xA0 to the device AO block SP
parameter.
Table 10-10. Failsafe Scenarios (Continued)
Event Response
Interrupt the In this case the device is no longer receiving any
Communication to telegrams from the master. The device goes through its
the PA Device own internal Failsafe sequence independent of the
Coupler FBM222 master.
Interrupt Device With power removed from the device, device detected
Bus Power failure mode becomes purely a function of the device as
it is powered down.
Operation
Changing the ROUT block mode from AUTO to MAN opens the control loop
and allows the operator to manipulate the SP being written to the positioner by
changing the ROUT block OUT parameter value.
The positioner’s AO block starts in Auto mode and continues to operate in
Auto even when the Control Core Services ROUT block changes to Manual
mode.
Note The mode of the positioner’s AO block needs to be AUTO for it to

receive the set point from the ROUT block. Any change of mode opens the
control loop that contains the device and render the failsafe inoperative.
Discrete PA Valve Controller

This example for a PROFIBUS-PA discrete valve controller is the Pepperl &
Fuchs FD0-VC-EX.PA, which is a discrete implementation of a PA positioner.
Slave Device Module Selection

The module selected for this positioner (Figure 10-5) is similar to that selected
for the PA positoner, and it provides the maximum functional return as
integrated into the system:
SP_D+RB_D+CB_D
Figure 10-5. Discrete PA Positioner Module Selection
The SP_D parameter is the setpoint to the device’s DO block (the discrete
analog of the positioner’s AO block) as a discrete value with a status byte. The
RB_D parameter is the readback from the device as a discrete value with a
status byte. Finally, CB_D parameter is the checkback value as a discrete
value. This table shows the module’s mapping to the device DO block output
data:
Byte 1 Byte 2
SP_D status
If the value of SP_D is zero, this is interpreted as the SP target being Closed.
Any non-zero value of SP_D is interpreted as the SP target being Open. See
“PA Positioner” on page 318 for status definition.
The table shows the mapping of the device DO block input data:

RB_D status CB_D
Status is of the parameter RB_D. The format of RB_D and CB_D are covered
below.
The PROFIBUS-PA Slave DO Function Block

The PROFIBUS-PA DO function block construct is similar to an FOUNDATION
fieldbus DO block. The block does have a state machine, with modes of OOS,
MAN, AUTO, and RCAS. As no known commercially available device fully
supports the RCAS mode, no further documentation of this mode is provided.
Fortunately, the PA DO block defaults to an AUTO mode, and you can
virtually ignore the state machine unless the use of a higher level Class 2
Master tool is desired to perform configuration and/or calibration.
SP_D
With the DO block in the AUTO (default) mode, the SP_D value as written by
the master becomes the effective (Open, Close) setpoint of this block. Just as
with the PA AO block, the status parameter for SP_D needs to be equal to 0x80
for the DO block to act upon the effective setpoint value. And just like the PA
AO block, if a SP_D status of 0xA0 is written to the device’s DO block, it is
interpreted by the device as a command to go to failsafe.
RB_D
The RB_D provides readback to the master from this slave.
Bit Feedback meaning

0+1 Valve Position 0=unknown, 1=Closed, 2=Open, 3=Intermediate Position
Refer to the device documentation for definition of the other bits in RB_D
byte.
RB_D has a status using the PROFIBUS status construct.
CB_D
CB_D is the analog to the PA AO block’s CHECKBACK parameter. While
CB_D uses the same three bytes as CHECKBACK, the format is quite
different. As the device integration scheme uses only Byte 1, only this byte of
CB_D is documented. You are urged to consult the P&F documentation for
these bytes as they contain a great deal of device diagnostic information that
would be very useful as a device troubleshooting tool. The Byte 1 format is:
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Unused Lead Short Lead Section Unused Unused Unused Failsafe
Break 8.7
Bit 0: If set 1, the device is in the FAILSAFE state

Bit 4: See Section 8.7 of the P&F User Guide for this device.
Bit 0 is used as a part of the Failsafe scheme for this device as documented in
“Device Parameterization” on page 316.
Device Parameterization
The bus trace in Figure 10-6 captures the sequence leading to cyclic data
exchange. Note that the Set Parameters telegram only uses the seven standard
parameters. The Check Config request matches the configuration required to
support the module being used for this slave device.
Figure 10-6. Valve Coupler Parameterization
After a period of time the FBM and slave device move into cyclic data
exchange as can be seen in the bus trace excerpt in Figure 10-7. Note the value
of SP_D is 00 (Closed) and the status of SP_D is 0x80. With the slave device’s
DO block in Auto, and the status Good, the slave device honors this target
setpoint value.
Figure 10-7. Valve Coupler Data Exchange
The value of RB_D is 0x05 or 101 binary. Decoding bits 0 and 1 (01) indicates
the slave device is in its Closed position. The CB_D parameter reads 00 00 00.
This indicates that the slave device is not in its Failsafe mode.

This particular device does not offer a keypad and LCD for setup purposes.
However, Pepperl & Fuchs does provide a DTM, which can be associated with
While on the surface a fairly simple device, the P&F Valve Coupler offers
quite a number of capabilities that support its use as an isolation valve operator.
You are urged to carefully review and understand the accompanying slave
device documentation. Getting optimum utilization from this device needs
careful device configuration.
Foxboro Evo Device Configuration

The configuration in the system closely parallels the configuration of a
PROFIBUS-PA positioner. Indeed, for the ECB200/202 and the ECB201 the
considerations are exactly the same.
We strongly recommend the BOUT block to interface with the controller. For
correct positioner behavior in a Control Core Services environment follow the
BOUT parameter guidelines in Table 10-11.
Table 10-11. BOUT Parameters for Discrete PA Positioner
IOM_ID ECB Identifier is a configurable string that specifies the path
name of the ECB201 for positioner.
PNT_NO We recommend this syntax: H0C1<H0C2.
This Point Configuration String enables the FBM to write
implicitly to the SP_D and SP_D status of the device’s DO
block without further bookkeeping on your part. In addition
the syntax provides for an implicit read of RB_D and status.
ERROPT Error Option specifies the conditions under which the IN
parameter is considered to have bad status. It is used in
determining whether there has been a bad-to-good transition
of IN.
• If ERROPT = 1, IN is considered bad if its status word
indicates Bad, Out-of-Service, or Not On Scan. (If it is
Not On Scan, then the source of the connection has
been deleted or is in a nonexistent compound, or there
has been a peer-to-peer failure detected.)
• If ERROPT = 2, IN is considered Bad in any of the
above situations. It is also considered Bad if the Error
bit in the status of MEAS is True.
FSOPT Fail-Safe Option is a configurable option that specifies the
fail-safe conditions and action to be taken in an FBM for an
output point in a BOUT block:
• Bit 0: 1 = assert fail-safe if input/measurement error.
The ERROPT needs to be configured nonzero for this
option to take effect.
• Bit 1: 1 = set/clear fail-safe when SETFS input is
set/cleared.
• Bit 2: 1 = assert fail-safe if control processor-to-FBM
communication is lost (FBM option). This option is
enabled only if fail-safe is enabled at the FBM level
through the FSENAB parameter in ECB200 or
ECB202.
Table 10-11. BOUT Parameters for Discrete PA Positioner (Continued)
FSCOUT The parameter FSCOUT stores the failsafe value the BOUT
block uses when in a failsafe condition.
Note Keep in mind that this value is not written to the

device nor is it read from the device. Verify that the failsafe
value in the device DO block and the failsafe value in the
BOUT block are identical.
VALSTS The BOUT block supports the PROFIBUS-PA status with

VALSTS parameter. Mapping to VALSTS is bit for bit, and
these status bits are quite similar to FOUNDATION fieldbus
AO blocks.
Failsafe Considerations
You must specify certain failsafe options for the slave device’s DO block
(Table 10-12).
Table 10-12. PA DO Device Function Block Failsafe Parameters

FAILSAFE Defines the device behavior on failsafe; the options are:
MODE
• Use the Failsafe Default Value
• Use Last Valid Setpoint
• Go to the Valve Mechanical Safety Position
FAILSAFE TIME Specifies the time in seconds that the device waits
without an update of a new SP_D until the behavior
defined by FSTATE_TYPE is initiated.
FAILSAFE The failsafe value is either OPEN or CLOSE.
DEFAULT
VALUE
These values need to be set using a high-level configuration tool such as the
vendor’s DTM associated with Field Device Manager.
As with the PA positioner, the valve controller has a number of failsafe cases
(Table 10-13).
Table 10-13. Discrete PA Valve Failsafe Scenarios
Event Description
SETFS The BOUT block supports the parameter SETFS,
enabling you to create a control scheme that would
cause the valve controller to go to its Failsafe
condition on demand.
The trace in Figure 10-8 shows the result of SETFS
being set TRUE.
In the frame number 2738 the status of SP_D goes
from 0x80 to 0xA0. This change of status results in
the slave device going Failsafe. Also, in frame
number 3088 this change in state is confirmed by the
CHECKBACK value (01 00 00).
The FAILSAFE DEFAULT VALUE parameter is not
sourced from the BOUT block FSCOUT parameter.
So when a valve controller goes into Failsafe it uses
the value stored in the slave device (if so configured).
Compound OFF If you turn off the compound within which the BOUT
block is functioning, the BOUT block asserts Failsafe
by changing the SP_D status to 0xA0. The result is
the same as SETFS.
BOUT IN goes BAD When the BOUT IN parameter status is BAD, the
BOUT block asserts Failsafe by changing the SP
status to 0xA0. The result is the same as SETFS.
Interrupt the PIO Bus In this scenario the FBM loses communication with
the Control Processor. The FBM asserts Failsafe to
the device by writing a status value of 0xA0 to the
device’s SP.
Interrupt the In this case the device is no longer receiving any
Communications to telegrams from the master. The device goes through
the PA Device its own internal Failsafe sequence independent of the
Coupler FBM master.
Interrupt Device Bus With power removed from the device, device
Power detected failure mode becomes purely a function of
the device as it is “powered down”.
Figure 10-8. SETFS with a BOUT Block
Operation
Changing the BOUT block mode from AUTO to MAN opens the control loop
and allows the operator to manipulate the SP being written to the positioner by
changing the BOUT block OUT parameter value.
The positioner’s DO block starts in Auto mode and continues to operate in
Auto even when the Control Core Services BOUT block changes to Manual
mode.
Note The mode of the positioner’s DO block needs to be AUTO for it to

receive the set point from the BOUT block. Any change of mode opens the
control loop with this device in it.
DP Motor Starter
The motor starter example in this section involves integration of the Siemens
SIMOCODE Pro configurable motor starter. In addition to being an I/O device,
the device has its own set of configurable functions. While it is not possible to
cover these facilities here, an example is provided using this device as a direct
starter that provides you with a sense of how this device can be used.
Figure 10-9 shows the form factor of the device. Generally, equipment
connected to the device include:
• Current/voltage measuring module
• Motor temperature measurement (thermistor)
• Separate operator panel
• Depending upon application, other analog and digital measurement

modules.
Figure 10-9. Siemens SIMOCODE Pro
The functional power of this device is derived from its internal block structure.
The device has a number of function blocks that can be interconnected through
a configuration tool. For the example shown, the configuration tool used was
SIMOCODE ES. This tool was installed on a laptop and connected to the slave
device through a serial link.
Figure 10-10 is a screen capture of the SIMOCODE ES user interface. The
right side of the screen shows numerous options beyond that of a Direct Starter.
The interconnection of function blocks within the device is greatly simplified
by using a standard configuration like the Direct Starter chosen for the
example. This selection makes virtually the connections that are needed,
greatly reducing the configuration effort. Once finished, the configuration file
is downloaded to the device through the serial link, completing data transfer.
The device’s address can also be completed by use of the ES tool. Additionally,
you can customize the starter functionality by editing function block
interconnections.
Figure 10-10. SIMOCODE ES
The function selection (in this case Direct Starter) also fixes the format for
cyclic data exchange. The SIMOCODE User Guide has an appendix that
documents the format for data inputs and outputs for each starter type. As the
SIMOCODE is a modular PROFIBUS device it does support two module
types, Basic Type 1 and 2. For the example presented here, the module selected
was a Basic Type 2. This module uses four input bytes and two output bytes.
The formats of these bytes are documented in the SIMOCODE User Guide.
337
C H A P T E R 1 1
Instrument Workshop
System
This chapter deals with setting up a new device in the instrument shop using
the Control Editors with Field Device Workshop installed on a standalone, off-
platform workstation (the workshop system).
The instrument database created in the Control Editors can be imported to the
workshop system to prepare the slave devices for connection to the process.
Devices are connected to the workshop system with a third-party PROFIBUS
interface card or an Ethernet-PROFIBUS gateway device, and a third-party
communication DTM for this interface. The workshop system does not use the
FBM Manager’s built-in communication DTM.
Once connected, Field Device Manager can be used to set the device’s address
to match the device address in the Galaxy database.
The workshop system can also be used to analyze failed devices using the
Field Device Editor and an associated vendor DTM.
Contents
• Workshop System Configuration
• Importing to the Workshop System
• Configuring the Communication DTM
• Using the Vendor Communication DTM
Workshop System Configuration

Refer to these Control Software documents for information on system
requirements and installation of the Control Editors:
(B0750BA)
• Foxboro Evo Control Software Installation Guide (B0750RA)
338 11. Instrument Workshop System
The workshop system includes these hardware and software components:

• Standalone workstation running Windows XP® (or Windows Server®
2003) and capable of running InFusion v1.2 or Foxboro Control Software
v3.0-v4.x or Foxboro Evo Control Software v5.0 or later.
See Foxboro Evo™ Process Automation System Deployment Guide
(B0750BA) for system requirements.
• Third-party PROFIBUS interface card such as the Softing™ AG
PB-PRO1-PCI or the Brad Communications™ SST™-PBMS-PCI, or an
Ethernet-PROFIBUS gateway, such as the Softing FG-100.
• This equipment and related software needs to be purchased from the
respective vendors.
• Follow the manufacturer’s instructions for installing the hardware.
• FDT compliant communication DTM for the interface card or gateway.
Note If you plan to use the Control Editors link to FoxCTS software to
track changes to deployed slave device configurations, verify that the
communication DTM includes the optional audit trail interface defined in
the FDT standard. See Chapter 12, “Change Tracking” for details.
• The Control Editors installed using the Standalone Configurator

predefined configuration. This configuration includes a Galaxy repository
and the Control Software client, but no Control Core Services software.
• Foxboro Evo Control Software PROFIBUS Support Instrument
Workshop.
The “Foxboro PROFIBUS Instrument Workshop” CD installs this
component. Refer to Foxboro Evo Control Software Installation Guide
(B0750RA) for the installation instructions for information.
Note The PROFIBUS Support needs to be installed on the server (Galaxy

Repository) and the client workstation in order to use the editors for the
FBM222 and PROFIBUS slave devices on the client workstation.
Note The Control Editors are applications built on the ArchestrA® Integrated
Development Environment (IDE). In this document and in the software some
functions are referred as IDE functions, others are called the Control Editors
functions.
11. Instrument Workshop System 339
Setting up the Galaxy for a Workshop System

The workshop system uses a separate Galaxy repository to maintain FBM222
and slave device configurations. The are three approaches to setting up this
Galaxy:
• Create a backup of the control room system Galaxy and restore the backup
to the instrument shop system. By replicating the entire Galaxy, the
instrument shop will benefit from having access to a variety of device-
related objects. For example, it may be easier to locate a specific device
among a large number of instruments using the plant unit associations in
the Devices view (described in “Organizing Devices by Plant Units” on
page 165).
a. Follow the procedure outlined in Foxboro Evo™ Process Automation
System Deployment Guide (B0750BA) for replicating a Galaxy in a
Standalone Configurator using the Backup and Restore functions in
System Management Console.
b. Verify that the workshop system users are assigned the appropriate
FDT roles given the security scheme configured in the replicated
Galaxy.
• Do these to import only those objects that are needed for preparing the
devices:
a. Define a new Galaxy on the workshop system as described in the
“Getting Started with IDE” topic in IDE Help.
b. Configure security for the new Galaxy as described in “Security” on
page 45.
If security is enabled, users need to be assigned the Maintenance or
Planning Engineer role to be able to commission and calibrate the
devices. If security is not enabled, users are granted Planning
Engineer permissions, which provide the access typically needed for
instrument shop functions.
c. Load the FBM222 and slave device configurations using the Export
and Import Automation Objects functions (described in “Importing to
the Workshop System” on page 340).
It is not necessary to import other objects such as control processors,
equipment units and strategies if the instrument shop system is to be
used exclusively for instrument preparation.
• Start with an empty Galaxy on the workshop system, create (or import) the
device templates, and then derive the device instances and host FBM222s.
We do not recommend this option because of the difficulty of coordinating
two separate device databases. However, it does allow instrument
preparation to begin before the control room Galaxy is completed. The
device and FBM data can be exported to the control room system.
Importing to the Workshop System

Use the IDE automation objects export/import functions to import the device
configurations to the workshop system.
Note To prepare slave devices using the workshop system, the devices need
to be assigned to an FBM222, and the FBM222 and devices need to be in the
workshop Galaxy. The FBM does not need to be assigned to a control
processor or an equipment unit.
To export device configurations to an instrument shop system:

1. Open the control room system, selecting the appropriate Galaxy, and
verify the devices, their host FBM222 and their defining templates are
checked in.
2. Right-click the host FBM222 in the Network view and choose Export >
Automation Objects from the context menu.
3. Use the Export Automation Objects dialog box to specify the destination
folder and, if desired, a file name other than the FBM name (F00001 in
Figure 11-1).
Do not change the file type, Galaxy export/import files (*.aqPKG).
Figure 11-1. IDE Export Automation Objects Dialog Box
4. Click Save to launch the export.

The Export Automation Objects dialog box displays the individual steps in
the export process as it completes them (Figure 11-2). In addition to
exporting the FBM and attached devices, the Control Editors export the
object’s defining templates including the devices’ defining templates
($SRD991_090201 and $Profibus in the case of DEV002 in Figure 11-2).
Figure 11-2. Foxboro Evo Control Editors Export Automation Objects

Dialog Box
that the export has been completed successfully.
6. Use the appropriate media to transport the export file (*.aqPKG) to the
workshop computer.
7. Check the properties of the export file after loading it on the workshop
computer, and un-check the Read only attribute if necessary.
8. Start the Control Editors on the workshop computer.
Be careful to open the correct Galaxy database if you are maintaining
multiple Galaxies on the workshop computer.
9. Choose Galaxy > Import > Automation Objects from the main menu
and use the Import dialog box to browse for and select the files to be
imported (Figure 11-3).
Figure 11-3. Selecting Files for Import
Note More than one file can be imported and each file may contain more than
one object.
10. Click Open and then specify in the Import Preferences dialog box how
you want the Control Editors to handle version and naming conflicts
(Figure 11-4).
Figure 11-4. Specifying Import Preferences
The Control Editors need that each object have a unique tag within the
Galaxy, even when the objects are of two different types. If an object in
the export file has the same tag and the same type as an object in the
Galaxy, it is not imported. If an object in the export file has the same tag
but not the same type as an object in the Galaxy, the object is handled
according to the options selected in the Object Name Conflict group.
11. Click OK to launch the import.
The Import dialog box displays the individual steps in the import process
as it completes them (Figure 11-5).
12. Click Close when the dialog box indicates that the import is done.
Figure 11-5. Import Dialog Box
Configuring the Communication DTM

In a control room system, the FBM Manager and Field Device Manager
communicate with the PROFIBUS devices using a communication DTM
specifically designed for the FBM222 and the control system. In a workshop
system, the FBM Manager and Field Device Manager communicate with the
PROFIBUS slave devices through a third-party communication DTM and a
PROFIBUS interface card such as the Softing™ AG PB-PRO1-PCI or the
Brad Communications™ SST™-PBMS-PCI. Therefore, the first need is to
replace the FBM222 communication DTM with a third-party communication
DTM using the Associate Vendor DTM Communication Function. You need to
make this change in each FBM instance that hosts a PROFIBUS device to be
worked on in the instrument shop.
To associate a communication DTM with an FBM222:
1. Double-click the FBM222 in the Network view if the FBM is not already
opened in the Hardware Editor.
2. Click the FBM Manager tab and wait for the FBM Manager to load.
3. Right-click anywhere in the Identification tab and choose Associate
Vendor Communication DTM from the context menu (Figure 11-6).
Figure 11-6. FBM Manager Context Menu
The Vendor Device Type Selection dialog box displays the PROFIBUS
communication DTMs installed on the workstation as listed in a locally
stored catalog. The browser also displays a Warning dialog box
(Figure 11-7) if a DTM was installed or uninstalled since the last time the
catalog was refreshed. (The dialog box is displayed if there was a detected
error during a previous scan for DTMs. Check the Do not show... option
in the dialog box to avoid display of the system message with this kind of
detected errors.)
4. Click OK to return to the browser, and then click Refresh to update the
catalog.
Another dialog box shows the progress of the update (Figure 11-8).
Figure 11-8. Refresh Information Dialog Box
5. Click Close when the scan has been completed to display the available
communication DTMs in the Vendor Device Type Selection dialog box.
6. Select a communication DTM and click Details to display additional
information about the DTM (Figure 11-9)
Figure 11-9. Details Dialog Box for a Communication DTM
Table 11-1 lists the information shown in the Details dialog box.
Table 11-1. Communication DTM Details
Field Description
Name Name of the selected DTM
ProgId Program and class IDs of the objects that implement the DTM
ClassId
DeviceName Name of the supported device
DtmType The type of DTM needs to be CommDTM.
Other possible types are: Device DTM, Module DTM, and
Block Type Manager (BTM)
IconPath Location of the program icons
Languages Languages supported by the DTM
Manufacturer Device manufacturer
Supported Protocols supported for device DTMs
Protocols
XML Snippet The XML snippet may be too long for the entire snippet to
displayed in the dialog box.
• Use the Save XML button to save the snippet to a file so
that the entire snippet can be viewed in a separate
browser window or text editor.
The button opens a Windows Save As dialog box.
7. Click Close in the Details dialog box.

8. Choose the appropriate DTM and click the Select button.
The browser closes and the Hardware Editor displays the associated DTM
in the Vendor Comm. DTM tab instead of the FBM Manager tab
(Figure 11-10).
Figure 11-10. Vendor Comm. DTM Tab
9. Configure the vendor communication DTM for use with the installed
PROFIBUS interface card, as described in the user manuals for the
interface card and the DTM.
10. Click in the FBM Editor to save the changes, close the editor, and
check the module in.
The associated communication DTM and configuration settings are saved
with the FBM222 in the Galaxy. After a communication DTM is
associated with the FBM and its configuration is stored in the database,
the Field Device Editor uses the communication DTM to establish
connection with the PROFIBUS devices.
Using the Vendor Communication DTM

When a third-party communication DTM is associated with the FBM222 in a
workshop system, the Field Device Editor and the FBM Editor use the DTM to
communicate with the connected devices.
• Refer to the vendor’s documentation for information on using the
interface.
To use the vendor communication DTM:

1. Double-click the FBM222 in the Deployment view or the Network view if
the FBM is not already opened in the Hardware Editor.
2. Click the Vendor Comm. DTM, and wait for the DTM to load.
The DTM is displayed as shown in (Figure 11-11.)
Figure 11-11. Vendor Comm. DTM Tab with Context Menu
3. Right-click anywhere in the tab to display a context menu that includes the
context menu for the software (above the line in Figure 11-11) and two
Hardware Editor commands (below the line):
• Associate Vendor Communication DTM opens the Selection dialog
box so you select a different communication DTM.
Note If you associate a new vendor DTM, configuration data from the first
DTM is removed.
• Use FBM222 Communication DTM to switch to the FBM222

communication DTM. This allow use of Field Device Manager in the
instrument shop, but only in offline mode.
4. Click Go Online in the upper right corner of the tab to bring the vendor
communication DTM online to the connected PROFIBUS interface
device.
The Auto-Online feature is not supported in the Vendor Comm. DTM tab.
5. Check the communication with the vendor communication DTM, and

configure the PROFIBUS interface if necessary.
6. Click in the FBM Editor title bar to save the changes, close the editor,
and check the FBM222 in.
Configuring Devices in the Instrument Shop

You can use the instrument shop system to prepare a PROFIBUS slave device
once the vendor communication DTM has been associated with the parent
FBM222 and the PROFIBUS interface device has been configured.
To configure a PROFIBUS slave device:
1. Double-click the PROFIBUS device in the Network or Devices view to
open the device in Field Device Editor and communicate with the device
using the vendor communication DTM.
• The FBM222 allows distinguishing between devices that are

connected to Port 1 and Port 2. This is not possible when using a
vendor communication DTM. You can only establish connection to
devices physically connected to the one specific port. We recommend
that you use a PROFIBUS interface card that has only one port.
• When a vendor communication DTM is selected, the Field Device
Manager does not go online, because the Field Device Manager uses
functionality that is only available with the FBM222’s
communication DTM. Only associated vendor DTMs can be used for
field devices in the workshop mode.
2. Click the Vendor DTM tab in Field Device Editor and edit the device
configuration as described in “Configuration Using the Manufacturer’s
DTM” on page 207.
351
C H A P T E R 1 2
Change Tracking
The Control Software enables you to track the changes made to a baselined
project that affect the configuration or operational settings of the system for
OSHA 1910 and 21 CFR Part 11 compliance. The Control Editors do so by
providing a link to a FoxCTS Change Tracking System (FoxCTS) application
and automatically passing change data to FoxCTS each time one of these
occurs:
• Deployment of configuration data to a control processor and FBM
• Download of configuration data to the FBM or to a device from FBM
Manager in a control room system
• Download of configuration data to a device from a third-party
communication DTM in an instrument workshop system
• Download of DPV1 device parameters from Field Device Manager or
from an associated Vendor DTM
• Download of configuration data as part of device commissioning.
Refer to Control Database Deployment User’s Guide (B0750AJ) for
information on enabling change tracking in the Control Editors and a
description of tracking of control database deployments. This chapter describes
the PROFIBUS specific changes that are tracked by the Control Editors and
communicated to the FoxCTS application.
Refer to FoxCTS Change Tracking Software Configuration and Maintenance
Guide (B0193VV) for information on configuring and using FoxCTS.
Contents
• Introduction
• Changing FBM222 Settings
• Change Tracking for the FBM Manager tab
• Change Tracking for PROFIBUS Devices
• Device Commissioning
352 12. Change Tracking
Introduction
The Control Editors change tracking sends a deployment/download event file
to the FoxCTS server that is monitoring the affected control processor each
time you make one of these changes:
• Deploy or undeploy a compound or block, as described in Control
Database Deployment User’s Guide (B0750AJ)
• Download changes to an FBM or PROFIBUS slave device using a device
type manager (DTM) in a Control Editors editor, as discussed in this
chapter.
When the Control Editors change tracking is enabled, the tools display the
Change Tracking dialog box each time you initiate a deployment or download
(Figure 12-1).
You need to enter a reason for the configuration change to enable the OK
button and continue with the download to the FBM or device.
Figure 12-1. Reason Dialog Box for DTM Audit Trail Events
By default the check box for Don’t show dialog again is checked. If this
option is checked, the Reason dialog box is displayed only once for a specific
DTM during an editing session, and the reported changes have the same reason
text.
When the deployment is done, the FoxCTS Transfer Service on the Galaxy
server, creates a deployment event file with this information:
• Affected control processor and compounds
• New parameter values
• Originating Foxboro Evo Control workstation
• Time and type of deployment
• Reason for the deployment as given by user in the Reason dialog box
(Figure 12-1).
The service sends the deployment event file to the FoxCTS server monitoring
the affected control processors, as configured in the Control Core Services’
12. Change Tracking 353
System Monitor host workstation. The transfer service maintains the file until
it receives verification of receipt from the FoxCTS server.
The FoxCTS Transfer Monitor service, which operates on the Galaxy server
and client workstations, alerts you when a transfer to the FoxCTS server has
not been successful within a user-specified period.
FDT Audit Trail

The Control Editors FBM and device editors, and associated Vendor DTMs,
are based on the Field Device Technology (FDT) standard, which defines an
optional audit trail interface that allows tracking of changes in the DTMs. The
FBM222 communication DTM in the FBM Manager and the universal
PROFIBUS DTM in Field Device Manager use this audit trail interface to
provide change information to FoxCTS.
Some, device manufacturers support the audit trail interface in their DTMs. If
you want to track the changes to the PROFIBUS slave devices, verify that the
third-party DTMs that you select for use with the Control Editors support the
optional audit trail interface, including:
• Device manufacturers’ DTMs associated with various device types and
accessed from the Vendor DTM tab in the Field Device Editor (see
Chapter 5, “Creating Device Templates” for information on associating a
vendor DTM with a device template)
• The third-party PROFIBUS communication DTM in a workshop system
(see Chapter 11, “Instrument Workshop System” for information on
selecting and configuring the communication DTM).
The remaining sections in this chapter detail the PROFIBUS specific content
of deployment event files sent to the FoxCTS server when you initiate a
change to an FBM222 or the attached PROFIBUS slave devices.
Changing FBM222 Settings

The changes you make to an FBM222 configuration using the Hardware,
Software and Bus Settings tab in the Field Device Editor (described in Chapter
4, “Installing and Configuring the FBM222”) are propagated into the FBM’s
corresponding equipment control block (ECB200 or ECB202). The changed
parameters are transferred to FoxCTS when you deploy the ECBs.
Table 12-1 shows the mapping between the names in the Bus Settings tab and
the corresponding parameter names in FoxCTS.
Table 12-1. Mapping of FBM222 Bus Settings to FoxCTS Parameters
FoxCTS
Parameter FBM222 Bus Settings in Field Device Editor
FILENAME File name (internal parameter, not visible in Bus Settings tab)
P1VALID Port1 valid (Use Port check box for port 1)
P1:MSA Port1: Master Station Address
P1:HAS Port1: Highest Station Address
Table 12-1. Mapping of FBM222 Bus Settings to FoxCTS Parameters (Continued)
FoxCTS
Parameter FBM222 Bus Settings in Field Device Editor
P1:BAUD Port1: Baud Rate
P1:TQUIT Port1: Quiet Time
P1:TSL Port1: Slot Time
P1:MINTSDR Port1: Min Station Delay Response Time
P1:MAXTSDR Port1: Max Station Delay Response Time
P1:TSET Port1: Setup Time
P1:TTR Port1: Target Rotation Time
P1:MRL Port1: Max Retry Limit
P1:MSI Port1: Min Slave Interval
P1:DCT Port1: Data Control Time
P1:EAF Port1: error action flag (internal parameter, not visible in Bus Settings tab)
P2VALID Port2 valid (Use Port check box for port 2)
P2:MSA Port2: Master Station Address
P2:HSA Port2: Highest Station Address
P2:BAUD Port2: Baud Rate
P2:TQUIT Port2: Quiet Time
P2:TSL Port2: Slot Time
P2:MINTSDR Port2: Min Station Delay Response Time
P2:MAXTSDR Port2: Max Station Delay Response Time
P2:TSET Port2: Setup Time
P2:TTR Port2: Target Rotation Time
P2:MRL Port2: Max Retry Limit
P2:MSI Port2: Min Slave Interval
P2:DCT Port2: Data Control Time
P2:EAF Port2: error action flag (internal parameter, not visible in Bus Settings tab)
Change Tracking for the FBM Manager tab

When you use the FBM Manager in a control room system to change the
address of a PROFIBUS device or to clear the device communication counters
in the FBM222 (refer to “FBM Manager” on page 86), the FBM222
communication DTM provides the change information to the FoxCTS server
via the audit trail interface.
In the instrument workshop system a Vendor Communication DTM is used to
configure the communication interface (see “Configuring the Communication
DTM” on page 343). If the Vendor Communication DTM supports the audit
trail interface the reported audit trail information is forwarded to the change
tracking system.
Table 12-2 lists the parameters in FoxCTS that identify the source of the
change.
Table 12-2. Identifying the Download Source
DEVTYPE FBM222 for the FBM222 Communications DTM in a control
room system, or Vendor Interface for Vendor
Communication DTM in instrument workshop system.
DTMTag Identifies the DTM that downloaded the change:
• <tagname>[FBM DTM] for FBM Manager, Field
Device Manager tab in a control room system
• <tagname>[VDTM] for FBM Manager, Field Device
Manager tab in an instrument workshop system
FDT:NAME Indicates the affected port when you change the address of a
device in the FBM Manager live list display, and the new
address is displayed in the change tracking system: PORT 1
DEVICE ADDRESS or PORT 2 DEVICE ADDRESS;
otherwise, blank
Change Tracking for PROFIBUS Devices

PROFIBUS device instances represent devices which are connected to the
PROFIBUS network. Changes made to an instance configuration in Field
Device Editor are tracked in FoxCTS when the changes are deployed or
downloaded to the control processor.
Changes in PROFIBUS device templates are not tracked, including changes to
locked data. However, the changes are tracked when the locked data is
inherited by the instances and the changes are deployed or downloaded.
General, Bus Settings, Modules and Data

Definition Tabs
The data in the PROFIBUS device instance cause updates in the corresponding
ECB201 block:
• General tab: GSD Information and Device Information group box data
(“Modifying a Device Configuration” on page 145)
• Modules tab: Configuration Data and User Parameters definition
(“Selecting Device Modules” on page 177)
If the Vendor DTM is used for the module definition, any change in the
vendor DTM that results in changes in the Module Configuration and User
Parameters data is propagated to the corresponding ECB201 parameter
(“Configuration Using the Manufacturer’s DTM” on page 207).
• Data Definition, Diagnostic tab: In the Diagnostic Messages group
selection of Error or Warning for the FBM Eval field (“Editing Diagnostic
Messages and Parameters” on page 198) is deployed to the FBM222. The
FBM222 generates an error or warning indication for a device if the value

for the diagnostic message is true.
During the deployment of the ECB201, the changed parameters are transferred
to the change tracking system.
Table 12-3 shows the configuration data in the PROFIBUS editor and the
corresponding parameter names in the FoxCTS.
Table 12-3. Mapping of PROFIBUS Editor Data to Change Tracking Parameters
FoxCTS
Parameter Configuration Editor Data
FILENAME File name (internal parameter, not visible in the editor)
VENDORNAME Vendor Name (General tab – GSD Information group)
MODELNAME Device Model Name (General tab – GSD Information group)
GSDREV GSD Revision (General tab – GSD Information group)
GROUP Groups (Bus Settings tab)
WDTMOUT Watchdog Timeout (Bus Settings tab)
SYNCMODE Sync Mode (Bus Settings tab)
FREZMODE Freeze Mode (Bus Settings tab)
WDENABLE Watchdog Enable (Bus Settings tab)
MINTSDR Min Station Delay Response Time (Bus Settings tab)
FSSUPP Failsafe support (Bus Settings tab)
DPV1SUPP DPV1 support (internal parameter)
DPV1DTSUPP DPV1 data types support (internal parameter)
DPV1ENABLE DPV1 – Enable (Bus Settings tab)
FSENABLE Failsafe (Bus Settings tab)
WD1MS Watchdog time base in 1ms (Bus Settings tab)
IMSUPP I & M Profile support (internal parameter)
C2STMOUT DPV1 Response Timeout (Bus Settings tab)
DDCTMOUT Device Failure Timeout (Bus Settings tab)
API API parameter (internal parameter)
SCL Security level parameter (internal parameter)
HWREV Hardware revision (General tab – Device Information group)
SWREV Software revision (General tab – Device Information group)
SRLNO Serial Number (General tab – Device Information group)
PRDID Part Number (General tab – Device Information group)
I/PBYTES Actual Input Length (Modules – Configuration Data tab)
O/PBYTES Actual Output Length (Modules – Configuration Data tab)
MC_LEN Configured Modules Length (Modules – Configuration Data tab)
MC_D1 …MC_Dn Module configuration data bytes. This byte stream are split into multiple
parameters each representing five bytes based on the number of bytes
(Modules – Configuration Data – Config Data dialog box)
UP_LEN User Param Data (Length) (Modules – User Parameters tab)
Table 12-3. Mapping of PROFIBUS Editor Data to Change Tracking Parameters
FoxCTS
Parameter Configuration Editor Data
UP_D1…UP_Dn User Parameter data bytes, this byte stream are split into multiple parameters
each representing 5 bytes based on the number of bytes (Modules – User
Parameters tab - User Param Data)
DM:UD1…DM:UD Device module user parameter data bytes. This byte stream is split into
n multiple parameters each representing five bytes based on the number of
bytes (Modules – User Parameters tab – User Param Data Dialog)
M1 First module name (Modules – Configuration Data tab – Configured
Modules)
M1:UD1… First module user parameter data bytes. This byte stream is split into multiple
M1:UDn parameters each representing five bytes based on the number of bytes
(Modules – User Parameters tab – User Param Data Dialog)
M1:UP1 Value of first module's first user parameter (Modules – User Parameters tab –
Module Parameters)
M1:UPn Value of first module's nth user parameter Modules – User Parameters tab –
Module Parameters)
Mn Nth module name (Modules – Configuration Data tab – Configured Modules)
Mn:UD1… Nth module User parameter data bytes. This byte stream is split into multiple
Mn:UDn parameters each representing five bytes based on the number of bytes
(Modules – User Parameters tab – User Param Data Dialog)
Mn:UP1 Value of first module's first user parameter (Modules – User Parameters tab –
Module Parameters)
Mn:UPn Value of first module's nth user parameter (Modules – User Parameters tab –
Module Parameters)
SM_NO Number of one-byte device status masks (internal parameter). The device
status masks with the same action (Error or Warning) are grouped into one-
byte pieces.
SM1:OFF Byte offset of first device status mask (Data Definition – Diagnostic tab -
Diagnostic Messages group - FBM Eval)
SM1:MSK Mask of first device status mask (Data Definition – Diagnostic tab -
SM1:ACT Action of first device status mask (Data Definition – Diagnostic tab -
SMn:OFF Byte Offset of nth device status mask (Data Definition – Diagnostic tab -
SMn:MSK Mask of nth device status mask (Data Definition – Diagnostic tab -
SMn:ACT Action of nth device status mask (Data Definition – Diagnostic tab -
Defined Parameters
Parameters defined in the Data Definition tab (“Defining I/O Points” on
page 185) are associated with DCI blocks during DCI Assignment as part of
control configuration (“Control Configuration” on page 253). Any subsequent

changes in these parameters are reflected in the associated DCI blocks and
tracked by FoxCTS when the modified DCI blocks are deployed.
Downloads from DTMs

The Universal PROFIBUS DTM in Field Device Manager enables download
of DPV1 device parameters to a slave device if no Vendor DTM is associated
with the device object, as described in “Device Parameter (DPV1) Tab” on
page 238. These changes are tracked by the Universal PROFIBUS DTM when
change tracking is enabled in the Control Editors.
If a Vendor DTM is associated with the device, the DPV1 device parameters in
the PROFIBUS universal DTM are read-only, as the Vendor DTM is used to
configure the device. If the Vendor DTM supports the audit trail interface, the
reported audit trail information is forwarded to FoxCTS.
Note Use of the FDT audit trail interface is optional. Some vendor DTMs
deliver audit trail logs.
Note Only FDT audit trail events of type AuditTrailVariableEvent and

AudiTrailFunctionEvent are captured from the DTMs to generate change
tracking information.
The content of the audit trail logs is generated by the DTMs and is therefore
DTM-specific (for example, how parameters are named and when audit trail
logs are generated).
Some vendor DTMs deliver audit trail logs not only when parameters are
downloaded to the device but also during other changes in the DTM such as
offline configuration, upload of parameters, and addition of child modules.
The change tracking information generated by the DTMs includes the
parameter settings listed in Table 12-4.
Table 12-4. Identifying DPV1 Device Parameter Downloads
FoxCTS
DDVER PROFIBUS identification number of the device
CFFVER Address of the device
DEVTYPE Device model name
DTMTag DTM that downloaded the changes:
• <tagname>[UDTM] for Field Device Manager
• <tagname>[VDTM] for a Vendor DTM
• <DTMTagname>[VDTM] for a child DTM in the DTM
tree view.
Note For child DTMs in the DTM tree view such as device DTMs underneath
a remote-I/O DTM, you need to give each child DTM (child module or device)
a unique DTM tag to allow the identification of the DTM.
Device Commissioning
The Control Editors support commissioning of PROFIBUS device instances
through a commissioning wizard (see “Commissioning Devices” on page 154).
As a part of commissioning, you can select several actions which cause
change-tracking entries:
• Deploy the ECB201 for PROFIBUS slave device being commissioned. In
this case, the block parameters are transferred to FoxCTS.
• Set the address of the physical device of the slave device being
commissioned. This address change is tracked.
• Download device data using the vendor DTM associated with the device.
These changes are tracked if the vendor DTM supports the audit trail
events.
361
C H A P T E R 1 3
System Management
This chapter covers tools available for maintaining the FM222 and connected
slave devices, including the FBM222 LED indicators, ECB displays in the
Control HMI and FoxView software, and equipment change actions and status
displays in the System Manager.
Contents
• FBM222 LED Indicators
• Identifying Modules in a Redundant Pair
• System Manager
• FBM222 Equipment Information
• FBM222 Equipment Change Actions
• Device Display in the Connections Tab
• Device Information Displays
• Device Equipment Change Actions
• Responding to System Alarms
• FBM Displays in Foxboro Evo Control HMI
• Device ECB Displays in Foxboro Evo Control HMI
• FBM Displays in FoxView
• Device ECB Displays in FoxView
362 13. System Management
NOTICE
When replacing failed FBMs with replacement modules, you need to

verify that you are replacing the failed module with the same module
type and that the replacement module is installed in the same slot as
the failed module. If you do not make these checks, the replacement
modules may suffer performance interruptions or damage.

damage.
NOTICE
Only a PROFIBUS termination assembly P0926TH, RH926TJ

(supersedes P0926TJ), or P0917SY) needs to be connected to the I/O
connector associated with a FBM222’s slot; no other type of assembly
is allowed. If the FBM222 is installed in a slot with an I/O connector
attached to an incorrect termination assembly, performance
interruption may occur.

damage.
FBM222 LED Indicators

Light-emitting diodes (LEDs) on the front of the FBM222 provide indications
of the module’s operational status, its current role as either the Master or
Tracker module, and the communication activity on each of its PROFIBUS
segments (Figure 13-1).
13. System Management 363
Green LED indicates the FBM is operational.

Red indicates a hardware failure detected.
Amber LED indicates the FBM’s role as
either Master or Tracker.
Amber LEDs indicate FBM is managing
communication activity on the segments.
Figure 13-1. FBM222 Front Panel
Table 13-1 shows how the indicators behave during various operational states
on a redundant FBM222 pair. Table 13-2 provides similar information for a
non-redundant module.
Table 13-1. Redundant FBM222 LED Indicators
Operational Operational
Status Status Master/Tracker Link Active
Operational Mode Green Red Amber Amber
Starting Up/Downloading FLASH ON OFF OFF
Hardware Fail OFF ON OFF OFF
Operational - Master Role ON OFF Master: ON FLASH
Tracker: OFF
Operational - Tracker Role ON OFF Master: OFF ON
Tracker: ON
EEPROM Update FLASH FLASH OFF OFF
OFFLINE ON ON Master: OFF ON
Tracker: ON
(depends on role)
Table 13-2. Non-Redundant FBM222 LED Indicators
Operational Operational
Status Status Master/Tracker Link Active
Operational Mode Green Red Amber Amber
Starting Up/Downloading FLASH ON OFF OFF
Hardware Fail OFF ON OFF OFF
EEPROM Update FLASH FLASH OFF OFF
OFFLINE ON ON OFF ON
Operational ON OFF OFF FLASH
For both redundant and non-redundant FBM222s, each of the two amber Link
Active LEDs blinks when there is PROFIBUS activity on its segment.
Identifying Modules in a Redundant Pair

In the ECB detail displays and in System Manager displays, the modules in a
redundant pair are labeled Main and Backup according to their positions on
the baseplate. The Main module by default has the lower baseplate address,
and is installed in an odd-numbered slot. The Backup module in the pair is in
the adjacent, higher-numbered position. Either module can perform the Master
role.
Note When a redundant pair is installed on a Schneider Electric baseplate, a

redundant adapter (p/n P0926XM or P0922RK) also needs to be installed for
the modules to be recognized by System Manager as a redundant pair.
Figure 13-2 shows two redundant pairs mounted in an 8-position horizontal

baseplate. The Main module in the pair identified with the letterbug FCM31C
is in slot 5; the Backup module in this pair is to the right in slot 6. The other
FBM pair in the example is FCM31D, installed in slots 7 and 8. In the ECB
detail displays and System Manager displays for this pair, Main is the module
in slot 7 and Backup is the module in slot 8.
Slot 5 Slot 6 Slot 7 Slot 8
Main Backup Main Backup
FCM31C FCM31D
Figure 13-2. Main Versus Backup Modules
System Manager
The System Manager obtains current and historical information about the
system and displays the control processor, the FBM222s and other equipment
in a data tree referred to as the Navigation pane, which can be arranged either
by system monitor domain or by network switches.
The layout of the System Manager window is shown in Figure 13-3.
Main Menu
Toolbar with
Hierarchy Navigation
Navigation Pane
Information Pane
Accessories Pane
Status Bar
Figure 13-3. System Manager Window
When an FBM222 is selected in the Navigation pane, System Manager

provides these tools for monitoring and changing equipment status:
• Status and Equipment Information in the Information pane, as described in
“FBM222 Equipment Information” on page 368.
• A display of the attached PROFIBUS slave devices indicating the port
through which they are connected.
Click to the left of the FBM or double-click the module name, to
display the slave devices assigned to it. Click to the left of any
expanded equipment, or double-click the equipment name, to collapse the
display and hide the attached devices.
• Status of connected slave devices in the Information pane Connections tab
(“Device Display in the Connections Tab” on page 387).
• Context menu of equipment change actions (see “FBM222 Equipment
Change Actions” on page 380). The actions can also be selected from the
System Manager main menu.
When a PROFIBUS slave device is selected in the Navigation pane, System

Manager provides these tools for monitoring and changing equipment status:
• Status and configuration information in the General Tab in the Information
pane (described in “Device Information Displays” on page 389).
• Context menu of equipment change actions (see “Device Equipment
Change Actions” on page 397). The actions can also be selected from the
System Manager main menu.
In addition, the System Manager Accessories pane displays messages, alarms,
equipment for which alarms are inhibited, a watch list for system counters, and
system monitor logs. The Accessories pane also features a Search tab for
finding and navigating to devices and other equipment. For detailed
information on System Manager features, refer to System Manager
(B0750AP).
FBM and Device Symbols

FBMs are depicted in the Navigation pane by the icon attached either to
the Primary ECB of a control processor or to an FCM (when the control
processor is a ZCP270). The same icon is used for both redundant and non-
redundant FBMs.
The slave devices are shown under the FBM and are represented by the
icon. The device names are prefixed with <P1> or <P2> to identify the
segment (or port) on which the device is operating (Figure 13-4).
This FBM222 is connected

directly to an FCP280 or FCP270 (FCP100)
over the module fieldbus. Click the
plus sign to show the slave devices.
Slave devices (shown with port

numbers) can be selected for
equipment change actions, and status
and information displays
Status of the selected FBM222
is displayed in the General
tab in the Information pane
Figure 13-4. FBMs and Attached Devices in the Navigation Pane
A symbol attached to the upper left corner of the FBM or device icon indicates
an adverse condition with the equipment (Table 13-3). The status of alarms
associated with the FBM and attached devices is indicated by a symbol on the
lower left side of the equipment icon.
• Choose Help > Legend from the System Manager main menu to identify
the equipment health and alarm status symbols.
Table 13-3. Status and Alarm Symbols
Symbol Condition
The question mark on a blue background indicates the equipment
is offline.
The symbol attached to an FBM indicates a detected error

condition such as a detected failure of an attached slave device.
The X on a red background indicates that the FBM or the device

has failed.
The question mark on a gray background indicates that the status

of the equipment is unknown. There is no status response from
the system monitor. This symbol is not used with the slave
devices.
The asterisk is placed on the lower left corner of the equipment
icon to indicate an unacknowledged system alarm. For an
FBM222, the alarm condition could be with the FBM itself or one
of the attached devices.
If Flashing is enabled in the System Manager configuration, the
equipment name blinks until the alarm is acknowledged.
This symbol attached to the lower left corner of an FBM or a
device indicates that alarms from the equipment are inhibited.
Labels attached to the right side of the FBM indicate the state of
communications between the FBM and the control processor or FCM
(Table 13-4).
Table 13-4. Symbols for Cable Use and Detected Faults
Symbol Condition
A red label to the right of the FBM indicates a communication
interruption between the FBM and the control processor or
FCM in one of the module fieldbus channels. The letters
indicate whether the detected problem is in channel A or B, or
in both channels (AB).
A label attached to the bottom right corner of the FBM icon

indicates whether cable alarms are inhibited for channel A
(InA), channel B (In B), or both A and B (InAB).
Cable alarms can be inhibited and enabled for an individual
FBM using the FBM’s context menu in the Navigation pane
(see “Managing Cable Alarms” on page 382).
FBM222 Equipment Information

When an FBM222 is selected in the Navigation pane, the Information pane
contains two tab pages:
• General tab, which includes the Equipment Status and Equipment
Information tables.
Figure 13-5 through Figure 13-8 show the General tab components for a
redundant FBM222; Figure 13-9 through Figure 13-12 shows the display
for a non-redundant FBM222.
• Connections tab, which displays the attached devices, their device types,
and status (see “Device Display in the Connections Tab” on page 387).
Redundant FBM222 General Tab

When you select a redundant FBM222 in the Navigation pane, tables in the
General tab display status and equipment information for each module in the
pair (Figure 13-5 through Figure 13-8). In the tables, Main refers to the
module with the lower baseplate position number, and Backup refers to the
module installed in the adjacent slot and configured with the higher baseplate
position number (see “Identifying Modules in a Redundant Pair” on page 364).
Equipment Status
Figure 13-5 is an example of the Equipment Status display for a redundant
FBM222.
Figure 13-5. Redundant FBM222 Equipment Status
Table 13-5 describes the fields in the Equipment Status display.
Table 13-5. Equipment Status Fields for a Redundant FBM222
Field Description
Name FBM letterbug name
Type Equipment control block type: ECB 202 for redundant FBM222
Main Run Mode Run mode status of each module, either Online or Offline
Backup Run Mode
• See “Go Online and Go Offline” on page 382
Table 13-5. Equipment Status Fields for a Redundant FBM222 (Continued)
Field Description
Main EE Updating Yes if the module is currently executing an EEPROM update; otherwise,
Backup EE Updating No
• Wait for the operation to finish. See “EEPROM Update” on
page 384
• If the operation does not finish, take the module offline and then go
online followed by a Download to cancel the EEPROM update
action
Failed Acknowledged Indicates whether a detected failure that has been reported has been
State Acknowledged or Not Acknowledged
• See “Managing Device Alarms” on page 381
Failed State State of the FBM as reported by CP is either Failed or Not Failed
Alarming State Indicates whether reporting of system alarms is Enabled or Inhibited
for this FBM
• See “Managing Device Alarms” on page 381 for information on
inhibiting alarms
Warning Condition Yes if this FBM has a detected fault condition, otherwise, No
• Check the Configuration section (Figure 13-6) and the
Miscellaneous section (Figure 13-8) in the General tab for details
Devices Attached Yes if slave devices are attached to this FBM; otherwise, No
Failed Devices Attached Yes if any failed devices are attached; otherwise, No
• Click the Connections tab (Figure 13-18) to display the status of the
attached slave devices
Last Cable Access Indicates state of communications between the control processor or FCM
and this FBM:
Both Cables Okay
Cable A Failed
Cable B Failed
Failed Devices Yes if the failed devices that are attached have been acknowledged;
Acknowledged otherwise, No
• Acknowledge failed devices, as described in “Device Equipment
Change Actions” on page 397
General Equipment Information

Figure 13-6 is an example of the General section in the Equipment Information
display for a redundant FBM222.
Figure 13-6. Redundant FBM222 General Information
Table 13-6 describes the fields in the General section.
Table 13-6. General Equipment Information Fields for a Redundant FBM222
Field Description
Compound:Block Compound and block name for the ECB202 for the FBM
FBM Type FBM type by default is Profibus Master
Hardware Type Hardware by default is 222
Software Type Software by default is 222
Main Hardware Part Number Part number of each module
Backup Hardware Part Number
Main Hardware Revision Hardware revision of each module
Backup Hardware Revision
Main Manufacture Date Date of manufacture of each module
Backup Manufacture Date
Main Serial Number Manufacturing serial number of each module
Backup Serial Number
Main Software Revision Revision level of the software operating in each module. In
Backup Software Revision Figure 13-6, the Main and Backup software revisions match as
both are 1.05 222, where the 1 to the left of the decimal is the
version number, 05 to the right of the decimal is the revision, and
222 is the FBM type.
Main EEPROM Revision EEPROM revision of the FBM boot loader in each module
Backup EEPROM Revision
Profibus Ident Number PROFIBUS ID Number for the FBM222; by default is 0x0AD5
Configuration Status
Figure 13-7 is an example of the Configuration Status section in the Equipment
Information display for a redundant FBM222.
Figure 13-7. Redundant FBM222 Configuration Status
Table 13-7 describes the Configuration Status fields.
Table 13-7. Configuration Status Fields for a Redundant FBM222
Field Description
Main Mode Each module’s current mode:
Backup Mode Master
Tracker
Not Operational
Offline
Port 1 Baudrate Configured baudrate for Ports 1 and 2 on both modules
Port 2 Baudrate
Main Port 1 Address PROFIBUS address for Ports 1 and 2 on each module. Main and
Backup Port 1 Address backup needs to match for each port.
Main Port 2 Address
Backup Port 2 Address
Table 13-7. Configuration Status Fields for a Redundant FBM222 (Continued)
Field Description
Main Port 1 State Current mode and status of each module for its two PROFIBUS
Backup Port 1 State network ports:
Main Port 2 State Operate
Backup Port 2 State Clear
Stop
Off Line
Main Port 1 Current mode and status of each module for its two PROFIBUS
Backup Port 1 network ports:
Main Port 2 Enabled, OK
Backup Port 2 Disabled, OK
Enabled, Failed
Disabled, Failed
Main Port 1 I/O Load Communication Overrun if the module cannot finish an I/O
Backup Port 1 I/O Load cycle on the port within the configured cycle time, otherwise, OK
Main Port 2 I/O Load
Backup Port 2 I/O Load
• Review sizing guidelines
• Adjust network load or modify bus timing parameters. See
“Setting Bus Parameters” on page 67.
Main Power 1 Fault if the module is not receiving power from power supply 1 or
Backup Power 1 2, otherwise OK
Main Power 2
Backup Power 2
• Check wiring and replace power supply if necessary.
Main Port Configuration Failed if there is an invalid PROFIBUS bus parameter set reported
Backup Port Configuration by the FBM, otherwise, OK
• Review the PROFIBUS configurations
Main Fieldbus Comm Fault if one or both PROFIBUS ports has failed for the module
Backup Fieldbus Comm (usually caused by excessive noise), otherwise, OK
• Check resistors on the network
Main Live List Mismatch Fault if the module (usually the Tracker) reports that its live list
Backup Live List Mismatch for a port does not match that of the other module, otherwise, OK
• Download the current Tracker module (see “Download” on
page 383)
Main HDLC Bus Fault if the module reports communication interruption with the
Backup HDLC Bus CP, otherwise, OK
• Check cables
• Power cycle the module
• Replace the module if necessary
Main HDLC Rx Fault if the module did not receive (Rx) or send (Tx) data in
Backup HDLC Rx communications with the CP, otherwise, OK
Main HDLC Tx
Backup HDLC Tx
• Check cables
Field Description
Main Interlink Fault if the interlink communications between the modules is not
Backup Interlink established successfully, otherwise, OK
• Verify that the redundant adapter is properly seated
• Replace the module if needed
Main Interlink Rx Fault if there was detected failure to receive from (Rx) or send
Backup Interlink Rx data to (Tx) the other module (usually reported for the Tracker),
Main Interlink Tx otherwise, OK
Backup Interlink Tx
Main Slot Conflict Fault if the module could not read its slot number from the
Backup Slot Conflict baseplate, otherwise, OK
• Check the actual module placement, and verify that is
properly seated
Main Redundancy Sync Fault indicates a temporary condition with the module attempting
Backup Redundancy Sync to sync with the Master database
Main Version Mismatch Fault if the FBM222 software version or revision does not match
Backup Version Mismatch the version or revision in the other module, otherwise, OK
Main Revision Mismatch
In Figure 13-6, the Main and Backup software revisions match as
Backup Revision Mismatch
both are 1.05 222, where the 1 to the left of the decimal is the
version number, 05 to the right of the decimal is the revision, and
222 is the FBM type.
• Only the version numbers need to match. We recommend that
the revision numbers also match.Reload the software on the
module as described in “EEPROM Update” on page 384.
• Perform the EEPROM on both modules if necessary.
Main Non-Spec Fatal Fault if there was a non-specific error detected that stops the
Backup Non-Spec Fatal module from operating properly, otherwise, OK
• Power cycle the module.
• Replace the module if the detected fault persists.
Field Description
Main Non-Spec Non-Fatal Fault if there was a non-specific detected fault in the module, but
Backup Non-Spec Non-Fatal the module continues to operate properly, otherwise, OK
The FBM may be overloaded, or there may be an acyclic overrun.
• Check for system messages in the Accessories pane Messages
tab
• Adjust network load or modify bus timing parameters. See
“Setting Bus Parameters” on page 67
• Power cycle the module when practical
Main Red Role Conflict Fault if both modules are attempting to become the Master,
Backup Red Role Conflict otherwise, OK
Fault is caused by multiple conditions.
• Remove the Backup module to enable the Main module to
take the Master role, and the re-insert the Backup module
Main Partner in Live List Fault if the module cannot detect the other module on one or both
Backup Partner in Live List PROFIBUS ports, otherwise, OK
• Verify that redundant adapter is properly seated
• Power cycle module
• Replace adapter and/or module if the detected failure persists
Main Time Synchronized Fault if the module is not synchronized to the control processor
Backup Time Synchronized time, otherwise, OK
The module needs to automatically synchronize. This field is used
by Schneider Electric service personnel
Last Download Failed if the deployment of the FBM222 is unsuccessful,
otherwise, OK
• Redeploy the FBM from the Control Editors
• Replace module if the detected failure persists
DCI Ready Indicates the ready state of the FBM as either Yes or No
Configuration Data Status of the ECB Configuration:
OK
Config Error
HW Type Mismatch
SW Type Mismatch
• Review and correct ECB configuration errors detected. See
“Setting ECB200/202 Parameters” on page 77
Miscellaneous Information
Figure 13-8 is an example of the Miscellaneous section in the Equipment
Information display for a redundant FBM222.
Figure 13-8. Redundant FBM222 Miscellaneous Information
Table 13-8 describes the fields in the Miscellaneous display.
Table 13-8. Miscellaneous Equipment Information Fields for a Redundant FBM222
Field Description
Main PIO Bus Logical Address Logical address of each module on the PIO/HDLC bus
Backup PIO Bus Logical Address
Main Slot Number Baseplate slot number for the module
Backup Slot Number
PIO Bus Logical Address Shared FBM logical address on the PIO/HDLC bus
Bus ID Identity of the FCM when the control processor is a
ZCP270; 0 when the control processor is an FCP280 or
FCP270
Error Log Count Diagnostic count used by Schneider Electric service
personnel
Non-Redundant FBM222 General Tab

The General tab for a non-redundant FBM222 includes an Equipment Status
display (Figure 13-9) and a three-part Equipment Information display
(Figure 13-10 through Figure 13-12).
Equipment Status
Figure 13-9 is the Equipment Status display for a non-redundant FBM222.
Figure 13-9. Equipment Status for a Non-Redundant FBM222
Table 13-9 describes the fields in the Equipment Status section for a non-
redundant FBM222.
Table 13-9. Equipment Status Fields for a Non-Redundant FBM222
Field Description
Name FBM Letterbug
Type ECB 200 for non-redundant FBM222
Run Mode Run mode status of FBM, either Online or Offline
Failed State Fail state of FBM as reported by CP, either Failed or Not Failed
Failed Acknowledged Indicates whether a detected failure is Acknowledged or Not
State Acknowledged
Alarming State Indicates whether reporting and printing of system alarms is Enabled or
Inhibited for this FBM
Devices Attached Yes if PROFIBUS slave devices are attached to the FBM; otherwise, No
Warning Condition Yes if this FBM has a detected fault condition, otherwise, No
• Check the Configuration and Miscellaneous sections in the General tab
for details
Last Cable Access Indicates state of communication between the control processor or FCM and
this FBM:
Both Cables Okay
Cable A Failed
Cable B Failed
Failed Devices Yes if any failed devices are attached; otherwise, No
Attached
• Click the Connections tab to review status of connected PROFIBUS
devices
EEPROM Updating Yes indicates the module is currently executing an EEPROM update,
otherwise, No
• Wait for the operation to finish
• If the operation does not finish, take the FBM offline and then go online
followed by a Download to cancel the EEPROM update action
• See “FBM222 Equipment Change Actions” on page 380
Failed Devices Yes if the failed devices that are attached have been acknowledged;
Acknowledged otherwise, No
• Acknowledge failed devices, as described in “Responding to System
Alarms” on page 398.
General Information
Figure 13-10 is an example of the General section of the Equipment
Information display for a non-redundant FBM222.
Figure 13-10. General Equipment Information for a Non-Redundant

FBM222
Table 13-10 describes the fields in the General section for a non-redundant
FBM222.
Table 13-10. General Information for a Non-Redundant FBM222
Field Description
Compound:Block Compound and block name for the ECB200
FBM Type FBM type Profibus Master by default
Hardware Type Hardware type222 by default
Software Type Software type222 by default
Hardware Part Hardware part number
EEPROM Revision EEPROM revision of the boot loader
Hardware Revision Hardware revision number
Software Revision FBM software revision. In Figure 13-10, the revision is 1.05 222, where
the 1 to the left of the decimal is the version number, 05 to the right of the
decimal is the revision, and 222 is the FBM type.
Manufacture Date Date of manufacture
Serial Number FBM manufacturing serial number
Profibus Ident Number PROFIBUS ID number for the FBM2220x0AD5 by default
Figure 13-11 is an example of the Configuration Status section in the
Equipment Information display for a non-redundant FBM222.
Figure 13-11. Configuration Status for a Non-Redundant FBM222
Table 13-11 describes the fields in the Configuration Status section for a non-
redundant FBM222.
Table 13-11. Configuration Status for a Non-Redundant FBM222
Field Description
Port 1 Baudrate Configured baudrate for each port
Port 2 Baudrate
• See “Setting Bus Parameters” on page 67
Port 1 Address Configured station address for each port.
Port 2 Address
• See “Setting Bus Parameters” on page 67
Port 1 State Current mode and status of the module for its two PROFIBUS network
Port 2 State ports:
Operate
Clear
Stop
Offline
Port 1 Current mode and status of the module for each PROFIBUS network port:
Port 2 Enabled, OK
Disabled, OK
Enabled, Failed
Disabled, Failed
• Check PROFIBUS cables and FBM
Port 1 I/O Load Communication Overrun if the FBM cannot finish an I/O cycle on the
Port 2 I/O Load port within the configured cycle time, otherwise, OK
• Check sizing guidelines
• Adjust network load or modify bus timing parameters. See “Setting
Bus Parameters” on page 67
Power 1 Failed if the FBM is not receiving power from power supply 1 or 2;
Power 2 otherwise OK
• Check wiring, replace power supply.
Table 13-11. Configuration Status for a Non-Redundant FBM222 (Continued)
Field Description
Port Configuration Failed if there is an invalid PROFIBUS bus parameter set reported by the
FBM; otherwise, OK
• Check the bus settings as described in “Setting Bus Parameters” on
page 67
Time Synchronized Failed if the module is not synchronized to the control processor time,
otherwise, OK
The module needs to automatically synchronize. If it does not, power
cycle the FBM
Non-Spec Fatal Failed if there is a non-specific error detected that is stopping the FBM
from operating properly, otherwise, OK
Detected failure can be caused by excessive noise on bus.
• Check resistors
• Power cycle the FBM
• Replace FBM if the detected failure persists
Non-Spec Non-Fatal Failed if there is a temporary, non-specific, non-fatal condition, otherwise,
OK
The FBM may be overloaded.
• Check for system messages in the Messages tab Accessories pane
• Adjust network load or modify bus timing parameters. See “Setting
Bus Parameters” on page 67
Last Download Failed if the deployment of the FBM222 has failed, otherwise, OK
• Redeploy the FBM from the Control Editors
Profibus Comm Failed if one or both PROFIBUS ports have failed (probably caused by
excessive noise on the PROFIBUS segment), otherwise, OK
• Check termination resistors
Configuration Data Status of the ECB Configuration:
OK
Config Error
HW Mismatch
SW Mismatch
• Review and correct ECB Configuration. See “Setting ECB200/202
Parameters” on page 77
DCI Ready Indicates the Ready state of the FBM as Yes or No
• Check FBM Configuration
Miscellaneous Information
Figure 13-12 is an example of the Miscellaneous section of the Equipment
Information display for a non-redundant FBM222.
Figure 13-12. Miscellaneous Equipment Information for a Non-

Redundant FBM222
Table 13-12 describes the fields in the Miscellaneous section for a non-
redundant FBM222.
Table 13-12. Miscellaneous Information for a Non-Redundant FBM222
Field Description
PIO Bus Logical Address FBM logical address on the PIO/HDLC bus
Slot Number Baseplate slot number for the module
Bus ID Identity of the FCM when the CP is a ZCP270. 0 when the CP is
an FCP280 or FCP270
Error Log Count Diagnostic count used by Schneider Electric service personnel
FBM222 Equipment Change Actions

When an FBM is selected in the Navigation pane, these equipment change
actions are available from the FBM’s context menu and from the Actions >
Equipment Change submenu pulled down from the System Manager main
menu:
• Acknowledge Device when there is an unacknowledged alarm
• Inhibit Device Alarming or Enable Device Alarming
• Go Online when a non-redundant FBM or at least one module in a
redundant pair is offline
• Go Offline when a non-redundant FBM or at least one module in a
redundant pair is online
• Download to restart the FBM
• DB Download (not used with the FBM222)
• EEPROM Update
• Switch Roles on a redundant FBM222
• Disable Port 1 or Enable Port 1
• Disable Port 2 or Enable Port 2
• Inhibit PIO Bus Cable A Alarms or Enable PIO Bus Cable A Alarms
• Inhibit PIO Bus Cable B Alarms or Enable PIO Bus Cable B Alarms
Note If you modify the FBM222 bus settings you need to redeploy the FBM
and then restart the FBM using the Download equipment change action in
order to implement the changes.
Managing Device Alarms
Acknowledge Device Alarms

There are multiple ways to acknowledge system alarms associated with an
FBM222 or its attached devices:
• Use the Alarms tab in the Accessories pane to identify and acknowledge
individual alarms.
• Right-click the FBM222 in the Navigation pane and choose Acknowledge
Device from the context menu to acknowledge all alarms for the selected
FBM.
• Acknowledge the alarms in the FBM’s system monitor domain by
selecting the system monitor in the Navigation pane and perform one of
these steps:
• Choose Actions > Acknowledge Smon Domain from the main
menu.
• Click in the System Manager toolbar.
• Right-click the system monitor and choose Acknowledge Smon
Domain from the context menu.
Inhibit Device Alarms

You can inhibit alarms for an FBM and its attached devices so that no alarm
conditions are reported to the system monitor.
To inhibit device alarms, perform one of these steps:
• Right-click the FBM in the Navigation pane and choose Inhibit Device
Alarming from the context menu.
• Select a device in the Accessories pane Alarms tab and click in the tab
toolbar.
The FBM icon is marked with the symbol to indicate that alarms are
being inhibited.
To re-enable device alarms:
• Right-click the FBM in the Navigation pane and choose Enable Device
Alarming.
Managing Cable Alarms

There are multiple ways to acknowledge cable alarms associated with an
FBM222 or its attached devices:
• Use the Alarms tab in the Accessories pane to identify and acknowledge
individual alarms.
• Choose Actions > Acknowledge Cable Alarms from the System
Manager main menu or click in the System Manager toolbar to
acknowledge the cable alarms including those associated with the selected
FBM.
You can inhibit the cable alarms on either or both cables/busses connecting the
FBM to its host station.
To inhibit cable alarms:
• Right-click the FBM and choose Inhibit PIO Bus Cable A Alarms or
Inhibit PIO Bus Cable B Alarms from the context menu.
A symbol ( , or ) attached to the lower right corner of the
FBM icon indicates which cables have alarms inhibited.
To re-enable the alarms:
• Right-click the FBM in the Navigation pane and choose the appropriate
command from the context menu:
Enable PIO Bus Cable A Alarms
Enable PIO Bus Cable B Alarms
Go Online and Go Offline

When a non-redundant FBM is selected, Go Online and Go Offline are
mutually exclusive. The Go Offline command is active only when the FBM is
online, and the Go Online command is active only when the module is offline.
For a redundant FBM222 pair, the Go Online and Go Offline commands are
active when at least one of the modules is in the opposite state. When you click
one of the commands, System Manager displays the current operational state
of each module in the confirmation dialog box.
To place a non-redundant FBM online:
1. Select the FBM in the Navigation pane and choose Go Online from the
context menu.
Depending on how System Manager is configured on the workstation, a
Go Online dialog box may prompt you to confirm the action and, if also
needed by the configuration, note why the action is being taken
(Figure 13-13).
Figure 13-13. Go-Online Dialog Boxes for a Non-Redundant FBM222
2. Enter a reason for the action (if prompted), and click OK.
To place a redundant FBM222 online:
1. Select the FBM in the Navigation pane and choose Go Online from the
context menu.
A dialog box prompts you to select the module to go online. Figure 13-14
shows the dialog box with and without the text box for entering a reason.
Figure 13-14. Go Online Dialog Boxes for Redundant FBMs
2. Click the check box for Main and/or Backup.

3. Enter the reason for the mode change (if prompted), and click OK.
When a non-redundant FBM or at least one module in a redundant pair is
online, the FBM’s context menu includes the Go Offline command, which
works the same way as the Go Online command.
Download
Download resets the FBM, loading the FBM’s control configuration from the
control processor and then bringing the FBM back online. The FBM re-
establishes connections with the slave devices and reschedules the data
exchange. It may take several minutes before the connections are re-
established.
To download an FBM222’s control configuration to the module:
1. Right-click the FBM in the Navigation pane and choose Download from
the context menu.
A dialog box prompts you to confirm the action. The dialog box shows the
current state of each module, either Online or Offline. For redundant
FBMs, the dialog box also prompts you to select which modules to update:
Main, Backup or both (Figure 13-15).
Figure 13-15. Download Dialog Boxes for a Redundant FBM
2. Check the box for one or both modules if the FBM is a redundant pair.
3. Enter a reason for the download if prompted.
4. Click OK.
The system displays a message indicating the result of the action for each
downloaded FBM. If the download is successful, the FBM goes online. If
there is any detected error, the module remains offline, and System
Manager displays a message in the Messages tab in the Accessories pane.
DB Download
The DB Download equipment change action is not used with the FBM222.
EEPROM Update
The EEPROM Update action copies the FBM222 software from the host
workstation to the module’s flash memory and restarts the module.
For a non-redundant FBM, an EEPROM update causes the module to restart
and re-establish communications with the connected devices. It may take
several minutes to regain data exchange between the devices and the control
blocks. For a redundant FBM pair, the EEPROM update can be accomplished
without interrupting service, if the new image has the same version number as
that currently in the FBM.
Note You can perform an online update for a revision within the same version
(from 2.1 to 2.2, for example) but not to implement a new version (from 2.1 to
3.0, for example). Version updates need to be done offline.
It is advised that you use this action only after an official Schneider Electric
software release.
To update the software in a non-redundant FBM222:

1. Right-click the FBM in the Navigation pane and choose EEPROM
Update from the context menu.
Depending on how System Manager is configured on the workstation, an
EEPROM Update dialog box may prompt you to confirm the action and, if
needed by the configuration, note why the action is being taken.
2. Observe the Run Mode field (Figure 13-9) in the Information pane
General tab to see when the FBM is returned to Online.
The update is done when the FBM is back online. The system displays a
message indicating that the device is back online. If the update action is
not successful, a failure detected message is shown in the Messages tab.
3. Check the software version and revision numbers in the Equipment
Information tables (1.05 222 in Figure 13-10) and review the Messages
tab in the Accessories pane to verify success of the update.
To update the operating system in a redundant FBM222:
1. Right-click the FBM in the Navigation pane and choose EEPROM
Update from the context menu.
A dialog box prompts you to select which modules to update: Main or
Backup, or both (Figure 13-16).
Figure 13-16. EEPROM Update Dialog Box for a Redundant FBM
If you update the software one module at a time, the FBM will remain in
control. Use this option to update to a new revision number within the
same version (2.1 to 2.2, for example, but not 2.1 to 3.0). When you
update one module in a redundant pair, the other module assumes the
Master role.
If you select both Main and Backup, control is lost. We recommend this
option when updating to a new version number.
2. Click the check box for Main or Backup, or both.
3. Enter a reason for the update if prompted.
4. Click OK.
5. Observe the Run Mode field (Figure 13-5) in the Information pane
General tab to see when the FBM222 is returned to Online.
The update is finished when the module is back online. The system
displays a message indicating that the device is back online. If the update
action is unsuccessful, the System Manager displays a message in the
Messages tab.
6. Check the software version and revision numbers in the Equipment
Information tables (Figure 13-6) and review the Messages tab in the
Accessories pane to verify success of the update.
Switch Roles
The Switch Roles command for a redundant FBM222 causes the module
playing the Tracker role to assume control from the module performing the
Master role. The current role assignments are shown in the Information pane
General tab when the FBM is selected. The modules are identified as Main and
Backup as described in “Identifying Modules in a Redundant Pair” on
page 364.
When both modules are online, you can assign the Master role to either.
To switch the module roles for a redundant FBM:
1. Right-click the FBM in the Navigation pane and choose Switch Roles
from the context menu.
The Switch Roles dialog box displays the operating mode for each module
(Figure 13-17).
Figure 13-17. Switch Roles Dialog Boxes
If one of the modules is offline:

• Click Cancel, use the Go Online command to bring the module back
online, and then choose Switch Roles again.
2. Click OK in the dialog box to effect the switch.
System Manager displays a message in the Messages tab indicating the
result of the switch action.
Enabling and Disabling Ports

Two pairs of equipment change actions allow you to stop or restart
communications on each of the two PROFIBUS ports. When the port is
enabled the disable command is displayed in the context menu for the
FBM222. Similarly, when a port is disabled the enable command is shown in
the menu.
Disabling a port only stops communication; it does not change any of the bus
settings for that port.
You can use these equipment change actions to resolve detected problems on
one network segment while maintaining data exchange on the other.
Device Display in the Connections Tab

In addition to using the display in the Navigation pane, you can review the
status of devices attached to an FBM222 in the Connections tab for the FBM.
The tab allows you to enable and disable communications between the FBM
and selected devices, as well as navigate to the Information tab for a selected
device.
Enabling communications in this context means bringing the device ECB
online to the control system and enabling the control processor to make DCI
connections with the device. The action does not affect the ability of Field
Device Manager to communicate with the device.
To display a list of the devices attached to an FBM222:
1. Select the FBM in the Navigation pane and click the Connections tab in
the Information pane.
The Connections tab lists the attached field devices by name, type, status,
run mode, and detected failure mode (Figure 13-18). The Connections tab
uses the same symbols that are used in the Navigation pane to mark the
operational status and the alarm state of the devices:
• on the upper left corner of the icon when the device is offline
• on the upper left corner of the icon when the device has failed
• attached to the lower left corner when there is an unacknowledged
alarm
• attached to the lower left corner when alarms from the device are
inhibited.
Enable Communications and Disable Communications buttons open
dialog boxes for applying these equipment change actions to all or
selected devices.
Figure 13-18. Connections Tab for an FBM222

2. Click any column header to sort the rows on the values in that column;
click the column header a second time to reverse the sort order.
3. Drag a column header right or left to rearrange the column order; drag the
right edge of column to the right or left to adjust the column width.
4. Double-click a device name, or right-click the name and choose
Navigate to <device name> (Navigate to <P1>DEV005 in Figure 13-18)
to go to the selected device.
The device is selected in the Navigation pane and its status and
information are displayed in the Information pane.
To enable communications between the control system and the slave devices:
1. Click Enable Communications to open a dialog box that lists the devices
that are currently offline (Figure 13-19, left).
• Click OK in the dialog box if the devices attached to the FBM are
already online (Figure 13-19, right).
Figure 13-19. Enable Communications Dialog Box
2. Click the checkboxes of the device ECBs you want to bring online, or
click Check All to select all devices, and then click Start.
The dialog boxes closes and the Status and Run Mode for the devices are
updated as the devices come online.
The Disable Communications button opens a similar dialog box for taking
devices offline.
The Enable Communications and Disable Communications equipment change
actions are also available from the context menu of individual devices in the
Navigation pane (see “Device Equipment Change Actions” on page 397).
Device Information Displays

Perform one of these steps to display detailed status and equipment
information for a PROFIBUS slave device:
• Select the device in the Navigation pane.
• Right-click the device listed in the Connections tab for the FBM222 in the
Information pane, and choose Navigate to <device name> from the
context menu.
The Information pane displays the General tab for the device, which includes
an Equipment Status display and a three-part Equipment Information display
(Figure 13-20).
Figure 13-20. Device Equipment Status
Equipment Status
Figure 13-21 is an example of the Equipment Status display for a slave device.
Figure 13-21. Equipment Status Display for a PROFIBUS Slave Device
Table 13-13 describes the items in the Equipment Status display for a slave
device.
Table 13-13. Equipment Status for a PROFIBUS Slave Device
Field Description
Name The ECB 201 Device ID (DEV_ID) parameter as configured in the Control
Editors
Type ECB type by default is DEV 222 ECB 201
Run Mode Mode of device: Online or Offline. Online is the normal mode
• To bring the device online, use the Enable Communications command
described in “Device Equipment Change Actions” on page 397
Device State The state of the device is Failed or Not Failed, as reported by the FBM
Failed Acknowledged Indicates whether there is an unacknowledged system alarm associated with
State the device: either Acknowledged or Not Acknowledged
• See “Device Equipment Change Actions” on page 397 for information
on acknowledging and inhibiting device alarms.
Alarming State Indicates whether system alarms are being reported and printed: Enabled or
Disabled
on inhibiting and enabling alarm reporting
Warning Condition Indicates whether the FBM has reported a Warning condition for this
device: Yes or No
• Review the Equipment Information display for further details.
Equipment Information
General Information
Figure 13-22 is an example of the General section of the Equipment
Information display for slave device.
Figure 13-22. General Information for a PROFIBUS Slave Device
Table 13-14 describes General section for a slave device.
Table 13-14. General Information for a PROFIBUS Slave Device
Field Description
Compound:Block Compound and block name for the device ECB
Fieldbus Type Profibus (by default)
Table 13-14. General Information for a PROFIBUS Slave Device (Continued)
Field Description
Device Name Name of the slave device from the DVNAME parameter of the ECB201
Device Address Address on the PROFIBUS segment
Device Part Number Device part number entered in the General tab in the Field Device Editor
(see “Exporting Device Configurations” on page 162)
Port Number PROFIBUS port, 1 or 2
Hardware Type Hardware type of the host FBM222 (by default)
Software Type Software type of the host FBM222 (by default)
Hardware Revision Device information entered in the General tab in the Field Device Editor
Software Revision (see “Modifying a Device Configuration” on page 145)
Manufacturer Device information extracted from the GSD file
Serial Number Device information entered in the General tab in the Field Device Editor
(see “Modifying a Device Configuration” on page 145)
Profibus Ident Number The device’s PROFIBUS ID number, extracted from the GSD file
Figure 13-23 is an example of the Configuration Status section of the
Equipment Information display for slave device.
Figure 13-23. Configuration Status for a PROFIBUS Slave Device
Table 13-15 describes Configuration Status fields for a slave device.
Table 13-15. Configuration Status for a PROFIBUS Slave Device
Field Description
Device Status Failed if the device has failed; otherwise, OK
• Check the device configuration
• Refer to the manufacturer’s documentation for troubleshooting
Device Enabled Yes if device is enabled: otherwise, No
on the Enable Communications command
Data Status Fault if the device data has been set to BAD/OOS because of an update
timeout; otherwise, OK
DPV1 Enabled Yes if the PROFIBUS-DPV1 parameters are enabled (see “Editing Device
ECBs” on page 148); otherwise, No
Table 13-15. Configuration Status for a PROFIBUS Slave Device (Continued)
Field Description
Unresolved Error if the FBM was unable to establish communication with the device;
Connection otherwise, OK
• Verify that the configured port and address match the actual location of
the device
• Power cycle the device
• Refer to the device documentation
Sync Mode Enabled Yes if Sync Mode has been enabled in the device configuration (see “Editing
Device ECBs” on page 148); otherwise, No
Last Download Fault if the device configuration was not accepted; otherwise, OK
• Check the device configuration
• Redeploy the device from the Control Editors
Freeze Mode Yes if Freeze Mode has been enabled in the device configuration (see
Enabled “Editing Device ECBs” on page 148); otherwise, No
DCI Ready Indicates the ready state of the DCI task in the FBM: Yes or No
Watchdog Enabled Yes if the watchdog timer has been enabled in the device configuration (see
“Editing Device ECBs” on page 148); otherwise, No
Diagnostic Information for a Slave Device

During startup of a PROFIBUS device, the FBM222 sends Get Diagnostics
requests to the device to determine when it is ready for cyclic data exchange.
The Get Diagnostic response can use a variety of formats, but at a minimum
starts with six bytes of the PROFIBUS standard diagnostics. When the device
is ready, that is, it has been parameterized and the I/O configuration is correct,
the FBM222 stops sending the Get Diagnostics request, but maintains the latest
diagnostics data sent by device.
If an error is detected in the device during normal data exchange, the device
indicates that it has a diagnostic condition. The FBM222 responds to the
indication by sending a Get Diagnostics request. The Get Diagnostic response
can use a variety of formats, but at a minimum starts with six bytes of the
PROFIBUS standard diagnostics.
The Field Device Diagnostics section of the Equipment Information display
(Figure 13-24) reports the standard diagnostics, and provides a starting point
for troubleshooting device problems detected. With the exception of Master
Address, each field is a condition reported by the slave device.
Figure 13-24. Diagnostic Information from a Slave Device
Additional information can be extracted from the standard diagnostics or the

other diagnostics formats as described in “Reading Diagnostic Data” on
page 304.
Table 13-16 describes the fields in this section, including the source bit in the
diagnostics and the meaning of the bit when set.
Note Some of the suggested remedies in Table 13-16 involve redeploying the
device ECBs. Redeployment of a device may cause a bump in communications
with the device and possibly in the control scheme associated with the
associated device. You need to make such dynamic deployments only in non-
mission critical systems.
Table 13-16. Field Device Diagnostic Information
Standard PROFIBUS
Field Description Diagnostic
Configuration Yes if the downloaded configuration does not Byte 1, bit 2 --
Mismatch match the physical device; otherwise, No Configuration Fault
• Modify the device configuration in the
Control Editors and redeploy to the device
ECB
Device Ready No if the address in the device is not available; Byte 1, bit 1 -- Station
otherwise, Yes Not Ready For Data
Exchange
• Check device cable and power connections
• Verify the port assignment and configured
address matches the device’s segment and the
address set in the device
Configuration Yes if the slave data needs to parameterized; Byte 1, bit 2 --
Request otherwise, No Configuration Fault
• Wait several cycles for the FBM222 to finish
parameterization.
• Check the device configuration in the Control
Editors and redeploy the device is necessary
Device Activated No when the slave device has been deactivated; Byte 2, bit 7 -- Slave is
otherwise, Yes Deactivated
• Check device cable and power connections
Configuration Yes if the slave did not accept the last parameter Byte 1, bit 6 --
Parameter Fault data from the FBM222; otherwise, No Prm_Fault
• Revise the device configuration in the Control
Editors and redeploy the device
Table 13-16. Field Device Diagnostic Information (Continued)
Standard PROFIBUS
Field Description Diagnostic
Function Supported No if configured function is not supported by the Byte 1, Bit 4 -- Slave
device; otherwise, Yes Device Does Not
Support Parameter
• Check to see if the Sync or Freeze option is set
Function
in the device configuration, but not supported
by the device
• Check to see if a reserved bit is set in
parameterization telegram
Device Locked Yes if the slave is locked, that is, controlled by Byte 1, Bit 7 -- Slave is
another master; otherwise, No Locked
• Delete the device configuration in the other
master
Recognized by No if the device did not respond to the latest Byte 1, bit 0 -- Station
Master request from the FBM222; otherwise, Yes Non Existent (Set by
Master on No Response)
• Check cable and power connections
Extended Diagnostic Yes if there is more diagnostic data that can fit into Byte 3, bit 7 --
Overflow the diagnostic data area (either the device send Diagnostic Overflow
buffer or the FBM222 receive buffer); otherwise,
No
• Refer to the device documentation for format
of extended diagnostics
Valid Response No if the device response to the latest FBM222 Byte 1, bit 5 -- Invalid
request was not valid; otherwise, Yes Slave Response (Set by
Master On Invalid
• Modify the device configuration in the
Response)
Control Editors and redeploy to the device
ECB
Extended Yes if the device has extended diagnostics to report Byte 1, bit 3 -- Slave Has
Diagnostics Exist a detected error; otherwise No Extended Diagnostic
• Refer to the device documentation for format Data
of extended diagnostics.
Master Address Network address of the Master set in the Byte 4, bits 0 to 7
PROFIBUS device
FBM Internal Errors

Figure 13-25 is an example of the FBM Internal Errors section of the
Equipment Information display for slave device.
Figure 13-25. FBM Internal Errors for a PROFIBUS Slave Device
Table 13-17 describes internal errors detected in the FBM222 communication

with the slave device.
In some cases, the detected problem can be resolved by power cycling the
device or disabling communications to the device and then enabling
communications to return it to service.
If resetting the device does not take care of the detected problem, modify the
device configuration in the Control Editors and redeploy the device to the
control processor.
associated device. You need to make such dynamic deployments only in non-
Table 13-17. FBM Internal Errors Affecting a Slave Device
Field Description
DCI C2 Initiate Fault if a Class 2 initiate request failed; otherwise, OK
Channel Data Length Error if the configured length for channel-specific data is less than the
minimum or greater than the maximum length for the channel; otherwise,
OK
• Modify the device configuration in the Control Editors and redeploy
the device
DCI C2 Read Fault if a Class 2 read request failed; otherwise, OK
Table 13-17. FBM Internal Errors Affecting a Slave Device (Continued)
Field Description
Diagnostic Length Error if the configured length for diagnostic data is less than the
minimum or greater than the maximum length for standard diagnostic
data; otherwise, OK
the device
DCI C2 Write Fault if a Class 2 write request failed; otherwise, OK
Extended Parameter Error if the configured length for extended parameter does not match the
Length extended parameter length; otherwise, OK
the device
Configuration Data Error if there are detected errors in the device configuration; otherwise,
OK
• Reset the device with Disable/Enable Communications as described
on page 397
• Modify the device configuration
Parameter Set Length Error if the length of the parameter set command is invalid; otherwise,
OK
the device
User Parameter Data Error if the user parameters configured for the device are not supported
by the device; otherwise, OK
the device
Parameter Data Length Error if the length of the parameterized data does not fit the installed
device; otherwise, OK
the device
Device Memory Error if the slave device does not have sufficient memory for the request
data; otherwise, OK
the device
Device Equipment Change Actions

These commands are available from the context menu of a slave device:
• Acknowledge Device when there is an unacknowledged alarm.
• Inhibit Device Alarming (when alarms are enabled) to disable

communication of alarms generated by the device.
System Manager marks any unacknowledged alarm from the device as
acknowledged, and places the symbol next to the bottom left corner of
the device icon to indicate that alarms are being inhibited.
• Enable Device Alarming (when alarms are inhibited) to re-enable
communication of alarms generated by the device.
System Manager clears the symbol from the bottom left corner of the
device icon.
• Enable Communications (when the device ECB is offline) to enable
communications between the FBM and the device.
A dialog box prompts you to confirm the action (Figure 13-26).
Figure 13-26. Enable Communications Dialog Box
Use this command to bring a device online.

• Disable Communications (when the device ECB is online) to disable
communications between the FBM and the device, taking the device
offline.
A dialog box (similar to the one in Figure 13-26) prompts you to confirm
the action.
The Enable Communications and Disable Communications are also
available from the Connections tab for the host FBM, where the
commands can be applied to multiple devices, as described in “Device
Display in the Connections Tab” on page 387.
Responding to System Alarms

Use System Manager to respond to system alarms involving PROFIBUS
devices, applying the resources described in this chapter to begin
troubleshooting and then, if necessary, open the Control Editors and the device
configuration using the Field Device Editor.
To respond to a system alarm:
1. Click the red system alarm indicator in the display application to start
System Manager if it is not already open:
• Click in the toolbar at the top of the Control HMI
window.
or
• Click in the FoxView Alarm bar.

2. Use the Alarms tab to identify the source of the alarm and to select the
equipment:
• Choose View > Accessories if the Accessories pane is not already
displayed in the lower portion of the System Manager window.
• Click the Alarms tab in the Accessories pane to display the current
alarms and their acknowledge status (Figure 13-27).
The tab identifies the source of each alarm by the equipment’s system
monitor domain and host equipment, and displays an alarm message
such as Device offline.
• Click a column header in the tab to sort the rows based on data in the
column; click the column a second time to reverse the sort order.
The rows can be sorted on any column. For example, the table in
Figure 13-27 has been sorted to list the unacknowledged alarms at the
top.
Figure 13-27. Alarm Selected in the Accessories Pane Alarms Tab
• Use the buttons in the Alarms tab toolbar to acknowledge or inhibit

alarms as appropriate. The Alarms tab toolbar includes these buttons:
Refreshes the display to include the most recent alarms.
Acknowledges all system alarms, including cable alarms.
Acknowledges the selected alarm.
Inhibits alarms from the selected device. Clicking this

button is equivalent to selecting the equipment in the
Navigation pane and choosing Inhibit Alarming, Inhibit
Device Alarming or Inhibit PIO Bus Cable A/B Alarms
from the context menu.
Opens the Page Setup dialog box from which you can
format and preview a printed report of the tab contents.
Opens the Page Setup dialog box from which you can
format and print a report of the tab contents.
Outputs the contents of the tab to a file.
3. Expand the device’s system monitor domain (identified in the Alarms tab
Source column), and host control processor and FBM222 (identified in the
Name column).
4. Select the FBM and click the Connections tab in the Information pane on
the right side of the screen.
The tab lists the status of the devices attached to the FBM.
5. Double-click the device in the tab to navigate to the equipment and display
its status and configuration in the Information pane.
6. Refer to Table 13-14 through Table 13-17 when reviewing the information
displayed in the tab.
FBM Displays in Foxboro Evo Control HMI

The Control HMI provides standard faceplate and detail views for the FBM
and device equipment control blocks. Use the ECB200/202 and ECB201
displays to obtain configuration, status and system alarm information about the
FBM222 and its attached devices. Refer to Control HMI Application User’s
Guide (B0750AQ) for instructions on using the Control HMI. Similar displays
are also available in FoxView software, as described in “FBM Displays in
FoxView” on page 415.
To access the faceplate for an FBM222 equipment control block (either
ECB200 or ECB202):
1. Choose Start > Programs > Invensys > InFusion View > View and
Alarm Server if the Control HMI is not already opened.
2. Choose Tools > Block Select from the Control HMI main menu, expand
control processor and then select its ECB compound in the Station View,
and double-click the FBM’s ECB in the table to the right (Figure 13-28).
Figure 13-28. Block Select Dialog Box
3. Go back to the Control HMI, which now includes the faceplate for the
ECB200/202 (Figure 13-29).
ECB200/202 Faceplate
The ECB200/202 faceplate includes these items:
• Header information identifying the parent compound (FCP100_ECB in
Figure 13-30) and ECB name (22FB1A), and the block’s DEV_ID,
HWTYPE, and SWTYPE parameters.
Refer to Integrated Control Block Descriptions (B0193AX) for a detailed
description of ECB200 and ECB202 parameters.
• The SYSTEM alarm indicator when there is a system alarm associated
with the FBM or one of its connected slave devices. There are no process
alarms associated with the FBM.
• Two columns of indicators showing the current operating status of the
ECB and the FBM.
• The current operating status of the ECB and its communication link to the
FBM (OPSTAT parameter).
• The button for selecting a detailed view of the ECB and FBM
configuration and status.
The button displays the Trend window, but the window is empty as
the Trend function is not available with the FBM.
SYSTEM is displayed
on a red background to
the right of DEV_ID when
there is a system alarm
associated with the FBM
or one of its devices.
Click this button for a

detailed view of the ECB
Figure 13-29. ECB202 Faceplate
The ECB STATUS display in the faceplate indicates operational states of the
ECB200/202 (above the bold line Table 13-18) and detected error conditions
(below the line) when they apply.
Table 13-18. ECB STATUS Indicators
Status Description
ECB ON or The ECB compound state is either on or off
ECB OFF
DEV READY or The FBM readiness is either ready or not ready
NOT READY
ON SCAN or The ECB scan state is either on scan or off scan
OFF SCAN
DEV FAIL There was a hardware failure in the FBM
DEV SHUTDWN The FBM is not operating
COMM FAIL There is a communication interruption between the
FBM and the CP
UNDEF Unresolved configuration problem detected in the
ECB
The FBM STATUS display in the faceplate, which is derived from the
FBMSTS parameter, indicates operational states of the FBM222 (above the
bold line Table 13-19) and detected error conditions (below the line) when they
apply.
Table 13-19. FBM STATUS Indicators
Status Description
DCI READY or The DCI configuration in the FBM is ready or not
NOT READY ready
ONLINE or The FBM is either online or offline
OFFLINE
Table 13-19. FBM STATUS Indicators (Continued)
Status Description
FBM OK or The FBM state is either OK, that is, operating and
FBM FAIL communicating with the CP, or failed
DLOAD FAIL There was a problem detected with initialization of the
FBM
UNRESOLVED The CP reports that there is an unresolved connection
to the FBM
ECB200/202 Detail View

For more detailed information about the ECB200/202:
1. Click in the lower left corner of the faceplate to access the block’s
detail view (Figure 13-30).
The detail view for an ECB200 includes two sets of pages, which are
selected with the CONFG and DIAG buttons on the upper right.
The detail view for an ECB202 includes three sets of pages, which are
selected with the CONFG, MDIAG and BDIAG buttons on the upper
right.
CONFG contains two

selectable pages: BLOCK
and FS (Failsafe)
The MDIAG button and
BDIAG button display
device diagnostic messages
for the Main and Backup
modules, respectively.
There is a single DIAG
button for an ECB200
Click this button to refresh
the display.
Figure 13-30. Configuration Pages in the ECB202 Detail View
2. Click CONFG and then one of the buttons on the lower left to select a
page in the set:
• BLOCK for key configuration parameters such as the ECB’s Period
and Phase, enabled alarms service (SYSOPT) and configuration
errors (ERCODE).
ERCODE detects an unresolved configuration problem that has
caused the ECB to be declared undefined (UNDEF is displayed in the
ECB STATUS in the faceplate). See Integrated Control Block
Descriptions (B0193AX) for an explanation of the codes.
• FS to determine whether failsafe is enabled (FSENAB) and to display
the configured failsafe delay timer (FSDLAY).
• PORT for a non-redundant FBM (ECB200) to see which ports are
enabled.
• MPORT and BPORT for a redundant FBM (ECB202) to see which

ports are enabled on the Main and Backup modules, respectively.
Figure 13-31 show the four configuration pages for a redundant FBM222
(22FB1A).
Figure 13-31. Configuration Pages in the ECB202 Detail View
3. Click the FBM INFO button on one of the port or diagnostic pages for a
pop-up display of the FBM type (as in detail view in the lower right of
Figure 13-31).
FILE INFO is not used with the FBM222.
4. Click DIAG for a non-redundant FBM222 to view faults detected by the
CP or FBM.
5. Click MDIAG or BDIAG for a redundant FBM222 to view faults
detected by the CP or FBM relating to the Main or Backup module (Pwr 1
in Figure 13-32).
Each detected fault indicator is displayed in a set position on a page when
the bit is set in one of the ECB’s diagnostic parameters.
Figure 13-32. Diagnostic Pages in the ECB202 Detail View
Table 13-20 lists the diagnostic messages that may be displayed on the
Control HMI DIAG page for a non-redundant FBM222 and on the
MDIAG and BDIAG pages for the Main and Backup modules in a
redundant FBM222.
Table 13-20. Diagnostic Messages for an FBM222
Message Page Description

HDLC Bus MDIAG The module reports that communication with the CP
BDIAG has been disrupted.
• Check cables
InterLink MDIAG The interlink communications between the modules
BDIAG has been disrupted.
• Verify that the redundant adapter is properly
seated
HDLC Rcvr, MDIAG The communications between the module and the CP
HDLC Xmtr BDIAG did not receive (Rcvr) or send data (Xmtr).
• Check cables
COMM DIAG One or both PROFIBUS ports have failed for the
MDIAG module (usually caused by excessive noise).
BDIAG
Table 13-20. Diagnostic Messages for an FBM222 (Continued)

Slot MDIAG A module was not able to read its slot number from the
BDIAG baseplate.
• Check the actual module placement, and verify
that is properly seated
Power 1 Fault, DIAG The module is not receiving power from power supply
Power 2 Fault 1 or power supply 2.
Pwr 1, MDIAG • Check wiring; replace power supply if necessary
Pwr 2 BDIAG
Init DIAG This is a temporary condition as the module is
MDIAG attempting to synchronize with the Master database.
BDIAG
Fatal DIAG There was a non-specific error detected that stops the
MDIAG module from operating properly.
BDIAG
• Replace the module if the fault persists
Non Fatal DIAG There was a non-specific fault in the module, possibly
MDIAG because the FBM is overloaded, or there was an
BDIAG acyclic overrun, but the module continues to operate
properly.
• Check for system messages in the Messages tab in
System Manager
• Adjust network load or modify bus timing
parameters. See “Setting Bus Parameters” on
page 67
Param Set DIAG There is a problem detected with the ECB
MDIAG configuration, such as a hardware or software
BDIAG mismatch.
• Review and correct ECB configuration errors
detected (“Setting ECB200/202 Parameters” on
page 77)

Version, MDIAG The FBM222 software version or revision does not
Rev BDIAG match the version or revision in the other module.
The software version is shown in General section of
the FBM’s System Manager Equipment Information
page (see Figure 13-6 and Figure 13-10). In
Figure 13-6, the Main and Backup software revisions
match as both are 1.05 222, where the 1 to the left of
the decimal is the version number, 05 to the right of
the decimal is the revision, and 222 is the FBM type.
Note Only the version numbers match. But we

strongly recommend that the revision numbers also
match.
• Reload the software on the module as described in

“EEPROM Update” on page 384
• Perform the EEPROM on both modules if
necessary
Role MDIAG Both modules are attempting to become the Master.
BDIAG This detected fault is caused by multiple conditions.
• Remove one of the modules so that the other
module assumes the Master role, and then re-
insert the module
Live List MDIAG The module reports that its live list for a port does not
BDIAG match that of the other module.
• Download the current Tracker module (see
“Download” on page 383)
Partner MDIAG The module cannot detect the other module on one or
BDIAG both PROFIBUS ports.
• Replace adapter and/or module if detected failure
persists
Time Sync DIAG The module is not synchronized to the control
MDIAG processor time. The module need to automatically
BDIAG synchronize. This field is used by Schneider Electric
service personnel.

Cyclic Ovr DIAG The module cannot finish an I/O cycle on port 1 within
MDIAG the configured cycle time.
BDIAG
page 67
Acyclic Ovr DIAG The module cannot finish an I/O cycle on port 2 within
MDIAG the configured cycle time.
BDIAG
page 67
Note An acyclic overrun on either port is currently

reported with the Non Fatal message in the Control
HMI.
6. Click in the lower left corner of the detail view to return to the
faceplate.
Device ECB Displays in Foxboro Evo Control

HMI
The Control HMI displays for a device equipment control block (ECB201) are
similar to those for an ECB200/202.
To display status and configuration of an ECB201 using the Control HMI:
1. Choose Start > Programs > Invensys > InFusion View > View and
Alarm Server if the Control HMI is not already opened.
2. Choose Tools > Block Select from the Control HMI main menu, expand
the ECB compound in the Block View tab, and select the ECB.
The ECB may be in the control processor ECB compound or in the control
compound that contains the DCI blocks that access the device.
3. Go back to the Control HMI, where the faceplate for the device ECB is
added to the viewer.
ECB201 Faceplate
The ECB201 faceplate includes these items:
• Header information identifying the parent compound and ECB name
(FCP100_ECB.DEV003 and FCP100_ECB.DEV004 in Figure 13-33),
and the block’s DEV_ID, SWTYPE, and HWTYPE parameters. Refer to
Integrated Control Block Descriptions (B0193AX) for a detailed

description of ECB201 parameters.
• The SYSTEM alarm indicator when there is a system alarm associated
with the device. There are no process alarms associated with the device
ECB.
• Two columns of messages that show the current operating status of the
ECB and the device.
• The current operating status of the ECB and its communication link to the
FBM (OPSTAT parameter).
• The button for selecting the detail view with the device ECB
configuration and status.
The button displays the Trend window, but the window is empty as
the Trend function is not available with the device ECB.
Click this button for the

ECB detail views
SYSTEM is displayed
on a red background to
the right of DEV_ID
when there is a system
alarm associated with
the device
Figure 13-33. Two ECB201 Faceplates
• Click to refresh the display.

The ECB STATUS display in the faceplate, which is derived from the
ECBSTA parameter, indicates operational states of the ECB201 (above the
bold line Table 13-21) and detected error conditions (below the line) when they
apply.
Table 13-21. ECB Status Indicators
Status Description
ECB ON or Indicates whether the ECB compound is ON or OFF
ECB OFF
DEV READY or Shows whether the device is ready for data exchange
NOT READY
ON SCAN or Indicates whether the ECB is on scan or off scan
OFF SCAN
DEV FAIL There was a hardware failure in the device
DEV SHUTDWN The device is not operating
COMM FAIL There is a problem detected with communications
between the FBM and the CP
UNDEF The ECB has an unresolved configuration problem
detected
The DEV STATUS display in the faceplate indicates operational states of the
ECB201 (above the bold line Table 13-22) and detected error conditions
Table 13-22. DEV STATUS Indicators
Status Description
DCI READY or Indicates whether the DCI configuration in the FBM is
NOT READY ready
DEV ENABLD or Indicate whether the device is online or offline
DEV DISABLD
DEV OK or Shows whether the host FBM is operating and
DEV FAIL communicating with the control processor
FBM
UNRESOLVED There is an unresolved connection to the device
ECB201 Detail View

For more detailed information about the ECB201:
1. Click in the lower left corner of the faceplate to access the block’s
detail view.
Figure 13-34 shows detail displays for four PROFIBUS slave device
ECBs.
Click this button

for an overlay
with additional
device information
See Table 13-24 for

BLKERR messages
Overlay displayed
when you click
See Table 13-25 for
DEV INFO
DIAG1 messages
Figure 13-34. Detail Views for Four ECB201s
The detail view includes three pages, which are selected with the CONFG,
BLKERR, and DIAG1 buttons on the upper right. (DIAG2 is not used
with PROFIBUS devices)
2. Click CONFG to view configured ECB parameters (Table 13-23, above
the bold line).
3. Click the DEV INFO button on any of the pages for a pop-up display of
additional block parameters (Table 13-23, below the bold line).
Table 13-23. ECB Parameters in the ECB201 Detail View
Parameters Description
TYPE Equipment control block type, by default is ECB201
PERIOD ECB’s execution time base
PHASE Configured execution phase for the ECB
ERCODE The ECB201 error code detects an unresolved
configuration problem that has caused the ECB to be
declared undefined (UNDEF is displayed in the ECB
STATUS in the faceplate). See Integrated Control
Block Descriptions (B0193AX) for an explanation of
the codes
PORTNO User-configured port number for the device’s network
connection; either 1 or 2
Table 13-23. ECB Parameters in the ECB201 Detail View (Continued)
DVNAME Name used to identify the device in the control
configuration
VERNUM Reserved
MODLID User-configured model description (see“Modifying a
Device Configuration” on page 145)
DVADDR Network address set in the device
DVOPTS User-configured address of the slave device
DVTYPE Device type if extracted from the GSD file
MANFTR Device manufacturer if extracted from the GSD file
PARENT Compound and name of the parent ECB200/202, that
is, the ECB of the FBM222 to which the device is
connected.
4. Click BLKERR to list messages derived from the first two bytes of the
standard PROFIBUS slave diagnostics (as described in “Reading
Diagnostic Data” on page 304).
Table 13-24 describes these messages along with the source bit in the
standard PROFIBUS diagnostics and the meaning when the bit is set, as
described in the PROFIBUS standard. Bit 0 is the least significant bit in
each byte; bit 7 is the most significant bit. See also “Diagnostic
Information for a Slave Device” on page 393.
Table 13-24. Diagnostic Messages for an ECB201: BLKERR Page
Foxboro Evo
Control HMI Standard PROFIBUS
Message Description Diagnostic
Address A device could not be found at the configured Byte 1, Bit 0 -- Slave
address and port Non Existent
Dev Not Ready The device did not respond to communications Byte 1, bit 1 -- Station
from the FBM222 Not Ready For Data
Exchange
Cnfg MisMatch One or more parameters configured for the device Byte 1, Bit 2 --
are not supported by the device model Configuration Fault
Table 13-24. Diagnostic Messages for an ECB201: BLKERR Page (Continued)
Foxboro Evo
Control HMI Standard PROFIBUS
Param Fault The slave device did not accept the last parameter Byte 1, Bit 6 --
data from the FBM222 Prm_Fault
Dev Locked The slave device is controlled by another Byte 1, Bit 7 -- Slave is
PROFIBUS master. Locked
master
Cnfg Request The device data needs to be parameterized Byte 2, Bit 0 -- Slave
Needs to Be
• Wait for the FBM222 to finish
Parameterized
parameterization
Watchdog The DPV1 watchdog timer has been enabled for Byte 2, Bit 3 -- Response
this device. Monitoring/Watchdog
ON
• See “Editing Device ECBs” on page 148
Freeze Mode Freeze mode is enabled. This field is not sourced
from the PROFIBUS
• See “Programming Sync and Freeze Actions”
diagnostics
on page 312
Sync Mode Sync mode is enabled. This field is not sourced
from the PROFIBUS
diagnostics
on page 312
Dev Deactivated The device is shutdown or disconnected from the Byte 2, Bit 7 -- Slave is
PROFIBUS network Deactivated
• Check the field connections, power
5. Click DIAG1 to view faults detected by the FBM.

Each detected fault indicator is displayed in a set position on a page when
a specific bit is set in one of the ECB’s diagnostic parameters.
Table 13-25 describes the messages that can be displayed on the DIAG1
page.
Table 13-25. Diagnostic Messages for an ECB201: DIAG1 Page
Foxboro Evo
Control HMI Description
Alarm Active Reserved
Prm Set Length The length of the parameter set command is invalid.
• Modify the device configuration in the Control Editors and redeploy the
device
Diag Length The configured length for diagnostic data is less than the minimum or greater
than the maximum length for standard diagnostic data.
Alarm Length Reserved
Table 13-25. Diagnostic Messages for an ECB201: DIAG1 Page (Continued)
Foxboro Evo
Control HMI Description
Ch Data Length The configured length for channel-specific data is less than the minimum or
greater than the maximum length for the channel.
Param Data Length The configured length of the parameterized data does not fit the installed
device.
• Review and modify the device configuration in the Control Editors, and
redeploy the device
Ext Param Length The configured length for an extended parameter does not match the extended
parameter length
Point Bad/OOS The device data has been set to BAD/OOS because of an update timeout
Config Data There are detected errors in the device configuration.
• Reset the device with Disable/Enable Communications
• Modify the device configuration (“Editing Device ECBs” on page 148)
Dev Memory The slave device does not have sufficient memory for the requested data.
device
Invalid Param The device response to the latest FBM222 request was not valid.
DPV1 PROFIBUS-DPV1 parameters are enabled (see “Editing Device ECBs” on
page 148)
DCI C2 Initiate A Class 2 initiate request failed
DCI C2 Read A Class 2 read request failed
DCI C2 Write A Class 2 write request failed
6. Click to refresh the display.
7. Click in the lower left corner of the detail view to return to the
faceplate.
FBM Displays in FoxView

ECB detail displays in FoxView software enable you to make a quick check on
the health of a module or device using standard FoxView software features.
For more information on detail displays, refer to FoxView (B0700FC).
To display a module ECB:
1. Use FoxSelect to locate the control processor and its ECB compound.
2. Expand the display and select the module ECB for the FBM222
(Figure 13-35).
Figure 13-35. Block Select Dialog Box
FoxView displays the ECB detail display, an ECB202 for a redundant FBM or
an ECB200 for a non-redundant FBM. Figure 13-36 is a FoxView detail
display for an ECB202 for a redundant FBM222.
Faceplate
Alarm Summary Overlay Buttons
FBM Information
ECB Information
Figure 13-36. ECB202 Detail Display in FoxView
The same layout is used for both ECB types. Starting in the upper right section
of the FoxView window, the display includes:
• Faceplate with status indicators
• FBM Information display
• ECB information section
• Alarm summary
• Overlay buttons
Alarm summary is not used in the ECB200/202 display; there are no process
alarms associated with ECBs.
FBM ECB Faceplate

The faceplate, the upper right quadrant, includes header information
identifying the ECB (22FB1A in Figure 13-36) and its parent compound
(FCP001_ECB), and the device ID and hardware and software type of the host
FBM222.
SYSTEM is displayed on a red background in the faceplate when there is a
system alarm associated with the FBM or one of the connected slave devices.
• Click in the FoxView Alarm bar to go to the System Manager

to acknowledge and resolve the alarm.
The ECB Status display in the faceplate indicates operational states of the
ECB200/202 (above the bold line Table 13-26) and detected error conditions
Table 13-26. FBM222 ECB Status Indicators in FoxView Software
Status Description
ECB ON or The ECB compound (FCP100_ECB in Figure 13-29)
ECB OFF is either ON or OFF
ON SCAN or The FBM ECB is either on scan or off scan
OFF SCAN
DEV READY or The FBM is either ready or not ready to exchange data
NOT READY with the attached devices
DEV SHTDWN The FBM is not operating
DEV FAIL There was a hardware failure detected in the FBM
UNDEF The ECB has an unresolved configuration problem
detected
between the FBM and the CP
The FBM Status display in the faceplate is derived from the FBMSTS. The
display indicates operational states of the FBM222 (above the bold line
Table 13-27) and detected error conditions (below the line) when they apply.
Table 13-27. FBM Status Indicators
Status Description
DCI READY or The DCI configuration in the FBM is ready
NOT READY
FBM OK or The FBM is OK, that is, operating and communicating
FBM FAIL with the CP, or failed
ONLINE or The FBM is online or offline
OFFLINE
FBM
UNRESLVD The control processor reports that there is an
unresolved connection to the FBM
FBM Information
The FBM Information section in the lower right quadrant provides operational
and configuration information about the FBM222, including the module type
and the status of the two PROFIBUS ports.
For redundant FBM222s, the display indicates which module (Main Processor
or Backup Processor) is the Master and which is the Tracker, and for each
module, the display indicates which ports are enabled. See the description of
the terms Main and Backup in “Identifying Modules in a Redundant Pair” on

page 364.
For non-redundant FBMs, the area between the FBM Information and ECB
Information shows which ports are enabled (Figure 13-37).
Figure 13-37. ECB and FBM Information for an ECB200
ECB Information
The ECB Information section in the lower left quadrant includes key
configuration parameters (Table 13-28).
Table 13-28. ECB200/202 Information in a FoxView Detail Display
TYPE ECB type is either ECB200 for a non-redundant FBM222 or
ECB202 for a redundant FBM222
PERIOD Scanning frequency set for the ECB
PHASE BPC phase in which the ECB is scanned
OPSTAT Operational status of the ECB and its communication link to
the FBM
SYSOPT System Option parameter specifies whether system alarming
and/or messaging are to be disabled
SYSCFG System Configuration parameter is not used in the FBM222
FSENAB Failsafe is either ENABLED or DISABLED
port Shows which of the two PROFIBUS ports are enabled
comm
FSDLAY Failsafe Delay set for the FBM
See “Setting ECB200/202 Parameters” on page 77 for a description of the

parameters.
Overlay Buttons
Overlay buttons in the upper right quadrant include PREV DISP and DIAG.
• PREV DISP returns the previously selected block detail display to the
FoxView window.
• The DIAG button is active only when there are errors detected to be
displayed on the diagnostic overlay. Table 13-29 describes the messages
that can be displayed in the overlay.
Table 13-29. Diagnostics Overlay for an FBM222
Message Description
HDLC Bus Fault The module reports that communications with the CP has been disrupted.
• Check cables
Interlink Fault The interlink communications between the modules has been disrupted.
HDLC Receive The communications between the module and the CP was not able to receive
Fault, or send data.
HDLC Transmit
Fault
• Check cables
Fieldbus Comm One or both PROFIBUS ports has failed for the module (usually caused by
Fault excessive noise).
Slot Conflict A module was not able to read its slot number from the baseplate.
• Check the actual module placement, and verify that is properly seated
Power 1 Fault, The module is not receiving power from power supply 1 or 2.
Power 2 Fault
• Check wiring; replace power supply if necessary
Not Initialized This is a temporary condition as the module is attempting to synchronize with
the Master database.
Non-Specific Fatal There was a non-specific error detected that stops the module from operating
Fault properly.
• Replace the module if the detected fault persists
Table 13-29. Diagnostics Overlay for an FBM222 (Continued)
Message Description
Non-Specific There was a non-specific fault in the module, possibly because the FBM is
Non-Fatal Fault overloaded, or there was an acyclic overrun, but the module continues to
operate properly.
• Check for system messages in the Messages tab in System Manager
• Adjust network load or modify bus timing parameters. See “Setting Bus
Invalid Bus There is a problem detected with the ECB configuration, such as a hardware
Parameter Set or software mismatch.
• Review and correct ECB configuration errors detected (“Setting
ECB200/202 Parameters” on page 77)
Version Mismatch, The FBM222 software version or revision does not match the version or
Revision Mismatch revision in the other module.
The software version is shown in General section of the FBM’s System
Manager Equipment Information page (see Figure 13-6 and Figure 13-10). In
Figure 13-6, the Main and Backup software revisions match as both are
1.05 222, where the 1 to the left of the decimal is the version number, 05 to
the right of the decimal is the revision, and 222 is the FBM type.
Note Only the version numbers need to match. But we strongly recommend
that the revision numbers also match.
• Reload the software on the module as described in “EEPROM Update”

on page 384
• Perform the EEPROM on both modules if necessary
Role Conflict Both modules are attempting to become the Master. This detected fault is
caused by multiple conditions.
• Remove one of the modules so that the other module assumes the Master
role, and then re-insert the module
Live List Mismatch The module reports that its live list for a port does not match that of the other
module.
• Download the current Tracker module (see “Download” on page 383)
Partner Not in Live The module cannot detect the other module on one or both PROFIBUS ports.
List
• Replace adapter and/or module if the detected failure persists
Time Not In Sync The module is not synchronized to the control processor time. The module
needs to automatically synchronize. This field is used by Schneider Electric
service personnel
Table 13-29. Diagnostics Overlay for an FBM222 (Continued)
Message Description
Cyclic Data Overrun The module cannot finish an I/O cycle on port 1 within the configured cycle
time.
Acyclic Data The module cannot finish an I/O cycle on port 2 within the configured cycle
Overrun time.
Note An acyclic overrun on either port is currently reported with a Non-

Specific Non-Fatal Fault message in the FoxView DIAG overlay.
Device ECB Displays in FoxView

The FoxView detail display for a slave device equipment control block
(ECB201) is similar to the ECB200/202 display, except that it displays ECB
and device status information rather than ECB and FBM status (Figure 13-38).
Faceplate
Alarm Summary
Overlay Buttons
ECB Configuration
Device Messages
Figure 13-38. ECB201 Detail Display
Starting in the upper right corner of the window, the display consists of the
ECB201 faceplate, ECB configuration information and a device messages box,
alarm summary (which is not used with device ECBs), and overlay buttons.
ECB201 Faceplate
The faceplate in the upper right corner of the display gives the compound
(FCP002_ECB in Figure 13-36) and name of the device ECB (X_FF9F), the
device ID, and the hardware and software type of the host FBM.
SYSTEM is displayed on a red background in the faceplate when there is a
system alarm associated with the device.
• Click in the FoxView Alarm Bar to go back to System
Manager to acknowledge and resolve the alarm.
Two message panels in the faceplate show the operational status of the ECB
and the device, as described in Table 13-30 and Table 13-31, respectively. The
messages apply if the message text is displayed in black.
Table 13-30. FoxView Device ECB Status Indicators
Status Description
ECB ON or The ECB compound is ON
ECB OFF
ON SCAN or The ECB is on scan
OFF SCAN
DEV READY or The device is ready
NOT READY
DEV SHTDWN The device is not operating
DEV FAIL There was a hardware failure detected in the device
UNDEF The ECB has detected an unresolved configuration
problem
between the FBM and the control processor
Table 13-31. FoxView Device Status Indicators
Status Description
DCI READY or Whether the DCI configuration in the FBM is ready
NOT READY
DEV ENABLD or Whether the device is online.
DEV DISBLD
DEV FAIL The device is not operating and communicating with the
FBM
device
UNRESLVD There is an unresolved connection to the device
ECB Configuration
Table 13-32 describes the ECB201 parameters displayed in the lower half of
the FoxView window. For information on setting these parameters, refer to
“Editing Device ECBs” on page 148.
Table 13-32. ECB Configuration
TYPE Equipment control block type is ECB20, by default
PERIOD ECB’s execution time base
PHASE Configured execution phase for the ECB
OPSTAT Operational status of the device ECB
PORTNO User-configured port number for the device’s network
connection; either 1 or 2
Table 13-32. ECB Configuration (Continued)
DVNAME Name used to identify the device in the control
configuration
VERNUM Reserved
FILEID, FILREV These fields are not used with devices attached to an
FBM222
MODLID User-configured model description (see“Modifying a
Device Configuration” on page 145)
DVADDR Network address set in the device
DVOPTS User-configured address of the slave device
DVTYPE Device type if extracted from the GSD file
MANFTR Device manufacturer if extracted from the GSD file
PARENT Compound and name of the parent ECB200/202, that
is, the ECB of the FBM222 to which the device is
connected
Device Messages
The area in the lower left is used for displaying detected errors and status
information derived from the first two bytes of the standard PROFIBUS slave
diagnostics (as described in “Reading Diagnostic Data” on page 304).
Table 13-33 describes these messages, along with the source bit in the standard
PROFIBUS diagnostics for each field and the meaning when the bit is set
according to the PROFIBUS standard. Bit 0 is the least significant bit in each
byte; bit 7 is the most significant bit.
associated device. You should make such dynamic deployments only in non-
See also “Diagnostic Information for a Slave Device” on page 393.
Table 13-33. Diagnostic Messages for an ECB201: BLOCK_ERRORS
Standard PROFIBUS
Address Non- A device could not be found at the configured Byte 1, Bit 0 -- Slave
Existent address and port Non Existent
Device Not Ready The device did not respond to communications Byte 1, bit 1 -- Station
from the FBM222 Not Ready For Data
Exchange
Configuration One or more parameters configured for the device Byte 1, Bit 2 --
Mismatch are not support by the device model Configuration Fault
Configuration The slave device did not accept the last parameter Byte 1, Bit 6 --
Parameter Fault data from the FBM222 Prm_Fault
Device Locked The slave device is controlled by another Byte 1, Bit 7 -- Slave is
PROFIBUS master Locked
master
Configuration The device data needs to be parameterized Byte 2, Bit 0 -- Slave
Request Needs to Be
• Wait for the FBM222 to finish
Parameterized
parameterization
Watchdog Enabled The DPV1 watchdog timer has been enabled for Byte 2, Bit 3 -- Response
this device. Monitoring/Watchdog
ON
• See “Editing Device ECBs” on page 148
Freeze Mode Freeze mode is enabled. This field is not sourced
Enabled from the PROFIBUS
diagnostics
on page 312
Table 13-33. Diagnostic Messages for an ECB201: BLOCK_ERRORS (Continued)
Standard PROFIBUS
Sync Mode Enabled Sync mode is enabled. This field is not sourced
from the PROFIBUS
diagnostics
on page 312
Device Deactivated The device is shutdown or disconnected from the Byte 2, Bit 7 -- Slave is
PROFIBUS network Deactivated
• Check the field connections, power.
Diagnostic Overlay
Additional diagnostic messages are available on the Device Diagnostics
overlay, which you can access by clicking the DIAG1 button in the upper left
corner of the overlay buttons section.
Each detected fault indicator is displayed in a set position on the overlay when
a specific bit is set in one of the ECB’s diagnostic parameters. The messages
that can be displayed are shown in Figure 13-39 and described in Table 13-25.
Figure 13-39. Device Diagnostics Overlay for a Slave Device
associated device. You should make such dynamic deployments only in non-
Table 13-34. Device Diagnostics Overlay Messages
Message Description
Alarm Active Reserved
Parameter Set The length of the parameter set command is invalid.
Length
device
Table 13-34. Device Diagnostics Overlay Messages (Continued)
Message Description
Diagnostic Length The configured length for diagnostic data is less than the minimum or greater
than the maximum length for standard diagnostic data.
Alarm Length Reserved
Channel Data The configured length for channel-specific data is less than the minimum or
Length greater than the maximum length for the channel.
Parameter Data The configured length of the parameterized data does not fit the installed
Length device.
• Review and modify the device configuration in the Control Editors, and
redeploy the device
Extended Parameter The configured length for an extended parameter does not match the extended
Length parameter length
Point Bad/OOS The device data has been set to BAD/OOS because of an update timeout
Configuration Data There are errors detected in the device configuration.
• Reset the device with Disable/Enable Communications
• Modify the device configuration (“Editing Device ECBs” on page 148)
Device Memory The slave device does not have sufficient memory for the requested data.
device
Invalid Parameter The device response to the most recent FBM222 request was not valid.
DPV1 PROFIBUS-DPV1 parameters are enabled (see “Editing Device ECBs” on
page 148)
DCI Class 2 Initiate A Class 2 initiate request failed
DCI Class 2 Read A Class 2 read request failed
DCI Class 2 Write A Class 2 write request failed
429
A P P E N D I X A
FBM223 Configurations
This appendix outlines the configuration support provided by the Control

Editors for the FBM223 PROFIBUS-DP™ Communication Interface Module
and attached slave devices.
I/A Series® PROFIBUS-DP™ Communication Interface Module (FBM223)
User’s Guide (B0400FE) describes configuration of the FBM223 and attached
PROFIBUS slave device using the Control Core Services’ Integrated Control
Configuration (ICC) and PROFIBUS master port and device configuration
editors. The Control Editors provide equivalent functionality as described in
this appendix.
Contents
• Existing Configurations
• Adding an FBM223
• Setting Up a Slave Device Type
• Adding a Device Instance
• Control Configuration
• Download
Existing Configurations
Existing FBM223 and slave device configurations can be imported from a
Control Core Services SaveAll or IACC Export file into a bulk data object. The
imported data can be used to generate comparable configurations in the Galaxy
or to migrate the devices to the FBM222. For details, see Bulk Data Editor
User’s Guide (B0750AF).
Adding an FBM223
For a new FBM223, you derive the instance from the template $FBM223
using a drag-and-drop move or selecting the template from the Bulk Create
dialog box (Figure A-1), similar to way in which an FBM222 is added to the
Galaxy.
430 A. FBM223 Configurations
Figure A-1. Adding an FBM223 to an FCP270 (Similar for FCP280)
Unlike the FBM222, bus settings for the FBM223 master are configured in a
separate port master file (*.PMA) using the FBM Port Configuration utility,
which you access from the Control HMI.
To configure the FBM223 port settings:
1. Start the Control HMI if it is not already opened and choose Tools >
Configure > Profibus Port from the main menu to display the FBM Port
Configuration utility (Figure A-2).
A. FBM223 Configurations 431
Figure A-2. FBM Port Configurator Window
Once opened, the editor operates exactly as documented in I/A Series®

PROFIBUS-DP™ Communication Interface Module (FBM223) User’s
Guide (B0400FE).
2. Use the dialog box to set up the PMA file for the FBM, and edit the port
configuration (Figure A-3 and Figure A-4).
Figure A-3. DP Master Configuration, Identification
Figure A-4. DP Master Configuration, Settings and Bus Parameters
3. Edit the FBM’s ECB200 in the Control Editors to link the port master file
to the FBM223:
a. Expand the host control processor node in the Deployment view,
double-click the ECB compound to open it in the Block Configurator,
and then click the ECBs tab in the editor.
b. Select the FBM ECB in the listing on the left to open it in the editing
pane to the right, and then click the FBM tab in the editor.
c. Insert the *.PMA file name in the ECB’s File Identifier field
(Figure A-5).
Figure A-5. Editing the FBM ECB
d. Edit other ECB parameters are needed, referring to I/A Series®

PROFIBUS-DP™ Communication Interface Module (FBM223)
User’s Guide (B0400FE).
e. Click in the Block Configurator title bar to close the editor, save
changes to the compound and ECBs, and check the objects in.
Setting Up a Slave Device Type

PROFIBUS slave device types are defined using the Slave Device
Configuration utility, which produces a configuration file (*.PSL) for each
device type based on the device’s GSD file. You invoke this editor from the
Control HMI.
To set up a PROFIBUS slave device type:
1. Start the Control HMI if it is not already opened and choose Tools >
Configure > Profibus Slave from the main menu to display the Slave
Device Configurator window (Figure A-6).
Figure A-6. Slave Device Configuration Window
Once opened, the editor operates exactly as documented in I/A Series®

PROFIBUS-DP™ Communication Interface Module (FBM223) User’s
Guide (B0400FE).
2. Choose File > New from the configurator main menu, use the Open dialog
box to browse for and select the appropriate GSD file (Figure A-7), and
then click Open to define the new device with the selected GSD.
Figure A-7. Selecting a GSD File
3. Enter a name in the Slave Device File Name dialog box (Figure A-8, left)
and click OK.
4. Select the new configuration file in the Slave Device Types dialog
(Figure A-8, right) and click Change View.
Figure A-8. Naming the Device Type
5. Choose Edit from the Slave Device Types main menu to display a multi-
tab device editor (Figure A-9 and Figure A-10).
Figure A-9. DP Slave Configuration, Identification and Parameters
6. Configure the device as described in Chapter 6 “FBM223 Port and Slave

Configuration” in I/A Series® PROFIBUS-DP™ Communication
Interface Module (FBM223) User’s Guide (B0400FE).
Figure A-10. DP Slave Configuration, Configuration Data and User

Parameters
Adding a Device Instance

To create a device instance:
1. Right-click the host FBM223 in the Network view, choose New > Device
from the context menu to open the Bulk Create dialog box (Figure A-11).
2. Click the check box for $DEV_ECB201 in the dialog box, enter a
quantity if creating more than one device instance, and click OK.
Figure A-11. Adding a PROFIBUS Salve Device to an FCP270 (Similar

for FCP280)
3. Right-click the new device, choose Rename Contained Name from the
context menu, enter the new name in the dialog box, and click OK.
4. Edit the device’s ECB201 in the Control Editors to link the device type file
to the device:
a. Expand the host control processor node in the Deployment view,
double-click the ECB compound to open it in the Block Configurator,
and then click the ECBs tab in the editor.
b. Select the device ECB in the listing on the left to open it in the editing
pane to the right, and then click the FBM tab in the editor.
c. Insert the *.PSL file name in the ECB’s File Identifier field
(Figure A-5).
d. Edit other ECB parameters are needed, referring to I/A Series®
PROFIBUS-DP™ Communication Interface Module (FBM223)
User’s Guide (B0400FE).
e. Click in the Block Configurator title bar to close the editor, save
changes to the compound and ECBs, and check the objects in.
Figure A-12. Editing the Slave Device ECB
Control Configuration
For control schemes involving an FBM223, you set up compounds and
strategies in the Control Editors much as you would for compounds and
strategies using an FBM222 (see “Control Configuration” on page 253).
However, there are two key differences:
• Field Device Manager does not support creation of parameters for devices
attached to an FBM223. Thus, when configuring the point number
parameter for a DCI block, you need to manually enter the Point
Configuration String instead of using a browser to reference a parameter
set up in Field Device Manager.
• The FBM223 uses a subset of the Point Configuration String syntax
described in this document for the FBM222. Refer to Chapter 5, “Control
Block Configuration Information” in I/A Series® PROFIBUS-DP™
Communication Interface Module (FBM223) User’s Guide (B0400FE) for
a description of the supported syntax.
Download
The Deploy function downloads the FBM223 and device ECBs to the control
processor. Bring the FBM and slave devices online using System Manager.
Refer to Chapter 8, “Maintenance” in I/A Series® PROFIBUS-DP™
instructions for the equivalent SMDH commands.
439
A P P E N D I X B
FBM223 to FBM222 Upgrade

Procedure
This appendix describes how to upgrade a system with an FBM223 to replace

it with an FBM222. This is the preferable upgrade path for legacy PROFIBUS
systems that used the FBM223.
Contents
• Hardware Upgrade
• Migrating FBM223 Database
• Upgrade with Integrated Control Configurator
• Upgrade with I/A Series Configuration Component (IACC)
• Upgrade with Foxboro Evo Control Software
Hardware Upgrade
The legacy FBM223 can be removed from its existing baseplate and a single
FBM222 can be plugged into its slot. The FBM223’s existing Type 1
termination cable and termination assembly can be retained for use with the
FBM222. Refer to “Polyurethane Termination Cables and Part Numbers” and
“Low Smoke Zero Halogen (LSZH) Termination Cables and Part Numbers” in
Standard and Compact 200 Series Subsystem User's Guide (B0400FA) for
details on these cables.
No further hardware changes are needed.
Migrating FBM223 Database

In an FBM223 to FBM222 upgrade, the FBM223’s database and the
PROFIBUS slave devices connected to that FBM223 needs to be migrated for
use with the FBM222.
The FBM223’s database is arranged in a hierarchical fashion as follows:
• FBM223’s ECB200 and its related port configuration file (*.PMA).
Refer to “Saving the Port Configuration File” in PROFIBUS-DP™
440 B. FBM223 to FBM222 Upgrade Procedure

more information on this file.
• The Slave Device’s ECB201, its related slave device configuration
file (*.PSL), and its GSD file.
Refer to “Saving the Slave Device Configuration Files” and “GSD
Files” in B0400FE for details on these files.
• The DCI blocks used to integrate PROFIBUS slave device real-
time data into the control processor.
These utilities create the FBM’s port configuration file and the slave device
configuration file:
• ProfibusPort - The PROFIBUS FBM223 port configuration file
• ProfibusSlave - The slave device configuration file
These files contain configuration data essential to the correct operation of the
FBM (as a PROFIBUS Master) and its PROFIBUS slave devices. For details
on creating these files, refer to PROFIBUS-DP™ Communication Interface
Module (FBM223) User’s Guide (B0400FE). These files are used for the three
versions of the upgrade (described in this appendix).
The upgrade can be performed with any of the Foxboro Evo control
configurators as described in these sections:
• Upgrade with Integrated Control Configurator
• “Upgrade with I/A Series Configuration Component (IACC)” on page 443
• “Upgrade with Foxboro Evo Control Software” on page 446
Upgrade with Integrated Control Configurator

The upgrade can be performed with the Integrated Control Configurator (ICC),
utilizing the existing FBM223 infrastructure, and existing port configuration
file and slave device configuration file. These subsections detail the changes
that need to be made for this upgrade process when using the ICC.
Configuring a New ECB200

To configure the new ECB200, proceed as follows:
1. In ICC, open the FBM223’s ECB200 and record the values of every
parameter (either in a spreadsheet or with screenshots), so that you can
input them into the FBM222’s new ECB200.
However, be aware that, for the FBM222’s ECB200, the HWTYPE and
SWTYPE parameters are “222” and cannot be edited. You will be
updating every ECB200 parameter other than these two.
2. Delete the FBM223’s ECB200.
3. Create a new ECB200 for the FBM222 in ICC.
4. Input the values of the parameters you recorded in step 1 into this new
ECB200, with the exception of the HWTYPE and SWTYPE parameters.
The new ECB200 can use the FBM223’s port configuration file (*.PMA)
as is (as indicated in the FILEID parameter).
B. FBM223 to FBM222 Upgrade Procedure 441
Figure B-1 shows an example of this new ECB200 for the FBM222.
Figure B-1. Equivalent ECB200 for an FBM222
For more information on performing these tasks in the ICC, refer to Integrated
Control Configurator (B0193AV).
Configuring a New ECB201

To configure the new ECB200, proceed as follows:
1. In ICC, open the ECB201 for each FBM223’s slave device and record the
values of every parameter (either in a spreadsheet or with screenshots), so
that you can input each into the FBM222’s new ECB201s.
However, be aware that, for the FBM222’s ECB201s, the HWTYPE and
SWTYPE parameters are “222” and cannot be edited. You will be
updating every ECB201 parameter other than these two.
2. Delete the FBM223’s slave device ECB201s.
3. Be aware that the slave devices need not be reconfigured. The slave device
configuration file is identified for the ECB201 in the FILEID parameter.
This assumes this file is ported over directly without change.
However, if you want to edit the file before assigning it to a new ECB201,
use the ProfibusSlave tool, discussed in PROFIBUS-DP™
Communication Interface Module (FBM223) User’s Guide (B0400FE),
and save it for use with the same FILEID connection.
4. For each slave device, create a new ECB201 for the FBM222 in ICC.
5. Input the values of the parameters you recorded in step 1 into these new
ECB201s, with the exception of the HWTYPE and SWTYPE parameters.
The new ECB201s use the same slave device configuration files (*.PSL)
as the FBM223’s slave devices (as indicated in the FILEID parameter).
Figure B-2 shows a typical ECB201 for a FBM222 slave device.
Figure B-2. Equivalent ECB201 for an FBM222’s Slave Device
Migrating DCI Blocks

When a FBM223 database was constructed, certain DCI blocks (e.g., PAKIN)
were used to pull slave device data into the control processor. If you have no
additional slave device data requirements, this FBM223 database can be used
with the FBM222 with no changes. Reassign these blocks from the FBM223 to
the FBM222 in ICC.
The FBM222 does support significantly more DCI block syntax options than
the FBM223. This is discussed in “DCI Block Syntax Options” on page 443.
System Management
The Foxboro Evo system management applications (System Manager, SMDH,
ICC, etc.) will view the FBM222 with the same operational characteristics as
the FBM223.
From an operational perspective, the FBM222 and FBM223 in an ICC
environment are identical.
Migrating Newer Slave Devices

Be aware that the FBM223 ProfibusSlave tool does not support newer slave
devices using V41 and V5 GSD files.
Note If your system uses these, a workaround is needed. Log in to the

Global Customer Support website (https://pasupport.schneider-
electric.com) or contact your local Foxboro representative and request
SOL2544.
Be aware that generated slave device configuration file (*.PSL) can be used
with either a FBM223 or a FBM222.
DCI Block Syntax Options

If you want to take advantage of the additional DCI block syntax options
available to the FBM222, refer to “Point Configuration String Syntax” on
page 261.
These options do not need Foxboro Evo Control Software to take advantage of
them.
Upgrade with I/A Series Configuration

Component (IACC)
You can integrate FBM222s into your system with minimal effort when using
the I/A Series Configuration Component (IACC) familiar with these tools:
• ProfibusPort utility - for details of its operation, refer to PROFIBUS-DP™
Communication Interface Module (FBM223) User’s Guide (B0400FE)
• ProfibusSlave utility - for details of its operation, refer to B0400FE.
• IACC Configurator - for details of its operation, refer to I/A Series
Configuration Component (IACC) User's Guide (B0700FE)
In this example, a PROFIBUS FBM and a PROFIBUS slave device are
integrated with a CP270 using IACC. An FBM222 and a slave device are
connected to a CP270, configured, and brought online.
Before proceeding, help ensure that you record the parameter fields from the
FBM223’s ECB and slave device ECBs, in a spreadsheet or through screen
capture.
The initial step is creating an ECB for the FBM222. In Figure B-3 that IACC
supports the creation of an ECB for a FBM222 running single (ECB200) or
redundant (ECB202). In the selection in this figure, the “1” after “FBM222 -
ProfiBus Interface” indicates the FBM is set to “single” mode.
1. QF1187552 for I/A Series software from v8.3 to v8.4.4 added support for
GDS V4.0. Later versions of Foxboro Evo and I/A Series software support
GDS V4.0 files.
Figure B-3. Creating a FBM222’s ECB200
For an FBM222 running in single mode, an ECB200 is created by the IACC

editor (see Figure B-4), which you can edit and then download to the control
processor. Note the similarity of Figure B-4 to Figure B-1 on page 441.
In this implementation, IACC uses the ProfibusPort tool to create a port
configuration file (*.PMA). The name of the created file needs to be added in
the ECB as the value of the FileID parameter (see Figure B-4 below). Once
edited, the ECB is downloaded (with the Download button in Figure B-4) and
brought online through the System Manager, as described in “Go Online and
Go Offline” under “Equipment Change Actions” in System Manager
(B0750AP)
Figure B-4. Editing a FBM222 ECB200
The next step in this example is to create an ECB201 for a slave device. In
IACC, right-click the FBM222’s ECB200 or ECB202, and select New Child
ECB, as shown in Figure B-5. This ECB201 is created and related directly to
the FBM222’s ECB.
Figure B-5. Creating a Child ECB
Editing this slave device ECB201 in the same manner as the FBM222’s ECB.
Double-click the ECB201 in IACC, and the Properties dialog box appears,
similar to Figure B-6. Enter the slave devices address (Dvopts), the port of the
FBM the device is connected to (Portno), and the slave configuration file
(Fileid - the device PSL file). This file is created by the ProfibusSlave utility.
Figure B-6. Editing a Slave Device ECB201
When the ECB201 has been downloaded (through the Download button), the
ECB201 will appear in the System Manager. Perform a DB Download
operation from System Manager for the ECB201, as described in “DB
Download” in System Manager (B0750AP), to send the slave data to the
FBM222. The slave device can now be set online as described in “Enabling
and Disabling Communications for Multiple Devices (FBM222 and
FBM228)” in System Manager (B0750AP).
Be aware that after communications are enabled between the FBM222 and its
slave devices, if you perform a bus trace (e.g., using a tool such as ProfiTrace)
on the segment, entire cyclic data exchange is shown.
Upgrade with Foxboro Evo Control Software

Performing this FBM223-to-FBM222 upgrade with the Foxboro Evo Control
Software is more complex than the previous methods, and if you are unfamiliar
with the Control Software, it is recommended that you use one of the previous
methods. If you want to use the Control Software, this section provides some
tips to minimize the upgrade effort.
Before proceeding, verify that you record all parameter fields from the
FBM223’s ECB and slave device ECBs, through spreadsheet or screen capture.
Note For instructions on importing a SaveAll configuration file into the

Control Software, refer to the chapter “Importing Bulk Data” in Bulk Data
Editor User's Guide (B0750AF).
Creating a New ECB200/202

To create a new ECB for the FBM222, open the Foxboro Evo Control
Software. In the Template Toolbox, select the FBM222 template as shown in
Figure B-7. Right-click the FBM222 template, and select New > Instance.
Figure B-7. FBM222 ECB Template
This instance can now be assigned to the control processor host. Then, right-
click the FBM222 instance, and select Open Related ECB. The parameters
are shown as presented in Figure B-8.
Figure B-8. FBM222 ECB Parameters
In this pane, add the FBM223’s port configuration file (*.PMA) to the
FBM222’s File Identifier parameter. You can input the same bus settings used
by the FBM223 into this ECB.
Creating a Slave Device ECB201

Before you can create an FBM222’s slave device ECB201, you need to create a
PROFIBUS slave device template. In the Template Toolbox, right-click the
$Profibus object as shown in Figure B-9, and select New > Derived Template.
Figure B-9. Creating a PROFIBUS Slave Template
The $Profibus_001 object appears, as shown in Figure B-10. Double-click

$Profibus_001 to open the pane shown on the right in Figure B-10.
Figure B-10. Associating a GSD File with the Template
In this pane, click Associate GSD to open a dialog box which allows you to
select a GSD file. When you locate the appropriate GSD file, select Open >
OK. Then save the created template.
When a slave device template is created, it appears in the Derivation window
as shown in Figure B-11:
Note $Acromag_Inc_973PB#A
Right-click the new template and select New > Instance to create a new
instance from this template that will become a slave device.
In the figure above, X_6FF is created as an instance of a slave device. Assign

the instance to an FBM222. Then right-click this instance and select Open
Related ECB to open the pane shown in Figure B-11. Manually enter the
existing slave device configuration file (*.PSL) to overwrite the GSD
configuration. The pane allows you to edit the File Identifier parameter to add
the slave device configuration file.
Figure B-11. Creating the ECB201
This creates a slave device ECB201 and allows you to use a previously created
slave device configuration file (*.PSL). This reuse of a slave device’s
configuration file is not needed. However, reusing it is a useful shortcut in the
Control Software.
Bring the FBM222’s ECB online through the System Manager, as described in
“Go Online and Go Offline” under “Equipment Change Actions” in System
Manager (B0750AP)
When the ECB201 has been downloaded (through the Download button), the
ECB201 will appear in the System Manager. Perform a DB Download
operation from System Manager for the ECB201, as described in “DB
Download” in System Manager (B0750AP), to send the slave data to the
FBM222. The slave device can now be set online as described in “Enabling
and Disabling Communications for Multiple Devices (FBM222 and
FBM228)” in System Manager (B0750AP).
451
A P P E N D I X C
DPV1 User Parameters
This appendix provides a test case to explain the configuration options

available for DPV1 device parameters.
Contents
• DPV1 Parameters and Configuration.
DPV1 Parameters and Configuration

The slave device GSD files have undergone multiple revisions along with
PROFIBUS, to support the enhancements made in this protocol.
As per Revision 3, three bytes were added to the User Parameter for DPV1
support.
This test case describes the enhancements made in FBM222, v2.11. It also
describes the DPV1 related issues detected in FBM222 and the resolutions for
those detected issues.
This test case references a P&F SK-3 slave device which is used for PA slave
device integration. The SK-3 device supports DPV1, and when equipped with
a diagnostic module, provides information about PA segment health in
cyclic data exchange.
Figure C-1displays an excerpt from the GSD file of SK-3 device.
452 C. DPV1 User Parameters
Figure C-1. Sample GSD File for P&F SK-3 Slave Device
The user parameter for this particular device is the concatenation of these data
constants (highlighted in Figure C-1):
The GSD file provides a set of default values that appear when the slave device
is presented in the Control Editors. You can edit the default values to suit the
application.
The default values are displayed in the Control Editors pane as shown in
Figure C-2. The User Param Data pane shows the same concatenation of the
data constants in hexadecimal notation.
C. DPV1 User Parameters 453
Figure C-2. User Parameters Data
The User Param Data is downloaded to the slave device’s ECB. However,
when using v2.10 and earlier versions of the FBM222 IOM image, an error is
detected on enabling communication for this slave device. You can reproduce
the detected error by running a trace with a tool such as ProfiTrace. The Set
Parameters request from a trace is displayed below.
The data above indicates seven (reading left to right) standard parameter bytes,
three DPV1 bytes, followed by configuration bytes.
Note As per the data downloaded to the FBM (see Figure C-1), DPV1 bytes
need to read 00 00 08. However, due to incorrect processing of the DPV1
bytes, the values get overwritten by 00 00 00, though they are displayed
correctly in the Control Editors.
The format of the user parameters DPV1 bytes is set into the context of the Set
Parameters request as follows (Figure C-3):
Figure C-3. Set Parameters Request
The data unit for the request includes these seven mandatory or standard bytes:
The next three DPV1 bytes are formatted as displayed below (Figure ):
Figure C-4. Formatting of DPV1 Bytes
C. DPV1 User Parameters 455
In SK-3, the three DPV1 bytes are:
For this example, Octet 10 has bit 3 (PRM Struct) set. While the function of the
bit is unclear, if this bit is not set, the device does not transition to data
exchange.
The three DPV1 bytes are overwritten by 00 00 00 even though they are
correctly downloaded into a slave device’s ECB. For most DPV1 devices, this
has no effect as the device’s GSD file is typically filled by 00 00 00.
The issue detected has been resolved in FBM229 IOM v2.11. The DPV1 bytes
displayed in the Control Software as user parameter data are the values used in
a Set Parameters request.
Though Octet 8 option bits can be configured by users, the effect of the
configuration is not displayed in the User Parameters tab.
The bits of Octet 8 are described as follows:
• Octet 8 - bit 2 WD_Base_1ms_supp: (D starting with GSD_Revision 3)
The DP-Slave supports the time base of one millisecond for the watchdog.
Type: Boolean (1: True)
• Octet 8 - Bit 6 Fail_Safe: (D starting with GSD_Revision 1)
It is specified here whether the DP slave accepts a data message without
data instead of a data message with data = 0 in the CLEAR mode of the
DP master (Class 1). The PROFIBUS DP master sets the outputs to zero if
it is in the CLEAR mode. You can specify the pre-assignments of the
outputs.
Example:
Fail_Safe=1: The slave accepts a data message without data in the CLEAR
mode
• Octet 8 - Bit 7 DP-V1_Slave: (D starting with GSD_Revision 3)
True, if the device uses DP-V1 functionality. This keyword is an
extension to Station_Type and indicates if the slave operates as a standard
DP- or DP-Slave with extended functionality.
The support of the several DP-V1 functionalities is defined in these
function specific keywords.
As an example, Figure C-5 displays the entries for the above keywords in the
GSD file of P&F SK-3 device.
Figure C-5. Sample Octet 8 Entries in a GSD File
Figure C-6 displays the Control Editors options resulting from the Octet 8
values. From a tools perspective, these options are mutually independent and
any one or all can be set. When you select one of these options, the
corresponding Octet 8 bit is set in the user parameters data.
Figure C-6. General Tab Page
Though the bits of Octet 8 are set in a trace of the Set Parameters request, the
Control Software tool does not display the bits in the User Parameters tab.
Do not use these options unless it is needed by some application.
If you use the device’s options, these bits are set in Octet 8 of the DPV1 bytes.
Index
Symbols mapping of FBM222 bus setting to FoxCTS
$Profibus 104 parameters 353
tracking changes from the FBM Manager 354
A tracking changes to defined parameters and
access permissions in Field Device Manager 247 associated DCI blocks 357
active terminators 38 tracking commissioning actions 359
acyclic data exchange 308 tracking downloads from DTMs 358
acyclic Master Class 2 read and write closed padlock icon 172
requests 308 colors
adding users 50 use of color in Field Device Manager
alarms
displays 223
FBM222 381
commissioning devices 154
responding to device alarms 398
communication DTM
analog outputs 294 associating a communication DTM with the
application-specific device templates 130
FBM 343
Assign To dialog box 153
assigning compact devices
devices 153 Modules tab 181
plant units 167 overview 25
Associate Device dialog box 168 Compare tab
Auto Online option in Field Device Field Device Manager 240
Manager 218 Config Data dialog box
automatic address assignment 140 displaying User Parameters 183
for a device module 180
B Configuration area
base template for Profibus devices 104 Device Parameter (DPV1) 238
baud rates 24 configuration data 180
bit definition for the standard diagnostic Configuration Data tab
bytes 305 Field Device Manager 237
BLKSTA parameter configuring input DCI Blocks 286
RIN block 280 configuring input from a PA transmitter 315
ROUT block 284 configuring output DCI blocks 294
Block Sample Time and Block Phase configuring output to a discrete PA valve
ECB200/202 77 controller 326
ECB201 150 configuring output to a PA Positioner 318
Bulk Create dialog box configuring output to DP motor starter 333
devices 142 confirmed outputs 194
bus settings 67 confirmed outputs in DCI blocks 285
for an FBM223 429 connection type field in the Point Configuration
String 263
Bus Settings tab
Connections tab in System Manager 387
editing slave devices 175
contained name 63
control configuration 253
C
Control Processor
cable alarms editing devices in the Field Device Editor 147
FBM222 382
control processor 4
change tracking 355 control software
FDT audit trail interface 353 overview 7
link to FoxCTS 351 control strategies
457
B0750BE – Rev L Index
setting up a control compound and custom status handling 267

strategy 268 data conversion 258
creating device templates 105 data types 260, 300
creating device templates from another I/O assignments 271
template 130 making the field connections in Foxboro Evo
creating devices 139 Control Editors 271
creating instances of a device template 131 overview 7
custom status handling 193 PA status handling 265
custom tabs in Field Device Manager 245 Profibus live list 311
Customize tab
Profibus usage 261
Field Device Manager 242
deploying devices 154
CXN Type field in the Point Configuration
deploying FBM222s 81
String 263
device
D creating and assigning a device from the
Data Control Time in the FBM222 bus Template Toolbox 141
settings 70 Device Address
Data Definition tab 185 when editing an ECB201 152
copying input and output parameters 197 Device Failure Timeout
creating input and output parameters from the editing devices in the Field Device Editor 177
data structure 195 Device Identifier 80
custom status handling 193 when editing an ECB201 151
defining and validating parameters 187 device Information page
Links and Graphics 76
defining DPV1 parameters 203
device inheritance updates
Diagnostic tab 198
pull method 174
Input and Output tabs 188
push method 174
parameter attributes 188
Device Name
Use for DCI Assignment option 187 when editing an ECB201 152
Data Definition tabs Device Options
Reports dialog box for the Input and Output when editing an ECB201 152
tabs 188 Device Parameter (DPV1)
data transfer rates 24 Configuration and Watch areas 238
Data Type field in the Point Configuration Device Parameter (DPV1) tab 203
String 264 deleting parameter 206
data types
DPV1 device parameters 204
parameter attributes 204
DB Download 384
DCI blocks device templates
acyclic data exchange 308 associating a DTM with a template 109
adding a block to a strategy 268 associating a DTM with a template already
analog inputs 286 associated with a GSD 114
configuring analog inputs 286 associating a GSD file with a template 106
configuring digital inputs 291 changing GSD information 124
configuring input from a PA transmitter 315 context menu in the Template Toolbox 130
configuring output to a discrete PA valve creating templates 105
controller 326 deleting templates 132
configuring output to a PA Positioner 318 deriving device templates from another
configuring output to DP motor starter 333 template 130
configuring outputs 294 Device Type dialog box 106
confirmed outputs 285 editing templates 127
458
Index B0750BE – Rev L
exporting a device template to another DP devices 25

galaxy 133 DPV1 device parameter attributes 204
moving a template to project folder 130 editing bus settings 175
overview 101 editing device configurations 145
renaming 132 equipment change actions in System
switching to DTM-based module Manager 397
definition 120 exporting a device configuration to another
Device Type galaxy 162
when editing an ECB201 152 GSD files 22
Device Type dialog box 106 importing device configuration from an
devices 387 FBM223 144
adding a device to an FBM223 435 name in the ECB201 configuration 152
adding devices to an FBM222 139 number of devices per segment 35
address in the ECB201 configuration 152 remote address change 154
addresses 23 remote I/O systems 26
assigning devices to an FBM222 153 responding to System Alarms 398
associating devices with a plant unit 165 selecting module 177
automatic address assignment 140 soft modules 28
baud rates 24 status and equipment information displays in
commissioning 154 System Manager 389
configuration using the manufacturer’s updating deployed devices 161
DTM 207 user parameters 183
copying input and output parameters 197 Devices view in Foxboro Evo Control
creating device instances 55, 139, 171 Editors 165
creating input and output parameters from the diagnostic information a slave device in System
data structure 195 Manager 393
creating multiple and assigning multiple diagnostic messages 198
devices 142 attributes 199
data exchange telegrams 258 deleting messages 202
defining device parameters 185 diagnostic messages for an ECB200/202 in
defining device templates in Foxboro Evo Foxboro Evo Control HMI and
Control Editors 105 FoxView 405
defining diagnostic parameters 201 diagnostic messages for an ECB201 in Foxboro
Evo Control HMI and FoxView 412,
defining diagnostic parameters and diagnostic
413, 425, 426
messages 198 diagnostic parameters 198
defining input and output parameters 188 attributes 201
deleting DPV1 device parameter deleting parameters 202
attributes 206 Diagnostic tab
deleting input and output parameters 197 Field Device Manager 229
deploying devices using the Commissioning Diagnostic tab in Data Definition 198
Wizard 154 DIC blocks
device address in the ECB201 Point Configuration String syntax 261
configuration 152 digital inputs 291
diagnostic information in System digital outputs 297
Manager 393 double padlock icon 172
diagnostic messages 198 Download
display configuration data for a module 180 FBM222 383
downloading DTM configuration data using download setup in Field Device Manager 249
the Commissioning Wizard 154 DP devices
459
configuring output to DP motor starter 333 diagnostic messages in FoxView and Foxboro
Failsafe support 258 Evo Control HMI 412, 413, 425,
DP/PA interface 29 426
DPV1 editing devices in the Field Device Editor 148
parameters and configuration 451 Foxboro Evo Control HMI detail
user parameters 451 displays 410
DPV1 Device Parameters Foxboro Evo Control HMI faceplates 408
Compare tab in Field Device Manager 240 FoxView detail displays 421
DPV1 device parameters EEPROM Update
downloading and uploading using Field FBM222 384
Device Manager 238 enable communications 154
DPV1 parameters 238 enabling and disabling Profibus ports 387
defining parameters in the Data Definition equipment change actions in System Manager for
tab 203 slave devices 397
setting up downloads in Field Device Error Monitor
Manager 249 Field Device Manager 219
DPV1 parameters and configuration 451 EuroFast connectors 38
DPV1 user parameters 451 example configurations 5
DTMs exporting
associating a communication DTM with the device configuration 162
FBM 343 device templates 133
associating a DTM with a device Extended data type (E) 302
template 109 Extended Diagnostics 307
associating a DTM with a template already
associated with a GSD 114 F
changing the communication DTM 347 Failsafe
in control configuration 258
configuration using the manufacturer’s
PA positioner 282
DTM 207
PA transmitter 278
configuring gateway DTMs 208
with a PA positioner 325
deleting a module DTM 215
Failsafe Delay 80, 323
downloading and uploading configuration
Failsafe Enable 80, 323
data using the Commissioning FBM
Wizard 154 editing devices in the Field Device Editor 147
universal Profibus DTM in Field Device FBM Editor
Manager 217 Vendor Comm DTM tab 347
FBM Internal Errors display for a device in
E System Manager 396
ECB Connection Browser 274 FBM222
ECB200/202 adding slave devices 140
configuring ECBs 77 alarms 381
detail displays 400 bus settings 67
diagnostic messages Foxboro Evo Control cable alarms 382
HMI and FoxView 405 DB Download 384
Foxboro Evo Control HMI detail deployment to the Foxboro Evo Control Core
displays 403 Services 81
Foxboro Evo Control HMI faceplates 401 EEPROM Update 384
setting parameters in Foxboro Evo Control enabling and disabling Profibus ports 387
Editors 77 equipment change actions in System
ECB201 Manager 380
460
Go On-Line / Go Off-Line equipment change Identification tab 223

actions in System Manager 382 Input and Output tabs 227
installation and configuration 55 Notes button and window 221
naming FBMs 63 parameter groups 243
overview 2 setting access permissions 247
Profibus network connections 33 setting up downloads 249
restarting the FBM with the Download tabs 222
equipment change action 383 toolbar 219
Switch Roles 386 use of color in Field Device Manager
system configuration 59 displays 223
System Manager displays 365 Watch tab 232
FBM223 fieldbus
adding a slave device to an FBM223 435 defining the fieldbus 55, 139, 171
adding an FBM223 429 File Identifier
control configuration 437 when editing an ECB201 152
Foxboro Evo Control Editors support for Foxboro Evo Control Editors 8
FBM223 configuration 429 Devices view 165
migrating slave device configuration to an Foxboro Evo Control HMI
FBM222 application 144 ECB200/202 detail displays 403
migration to FBM222 7, 59 ECB200/202 faceplates 401
setting up slave device types for devices ECB201 detail displays 410
attached to an FBM223 433 ECB201 faceplates 408
FCP270 4 Foxboro Evo Hardware 2
FCP280 4 FoxCTS
FDT Foxboro Evo Control Editors support for
Audit Trail interface 353 change tracking 351
FDT roles as used in Field Device identifying DTMs for downloads from the
Manager 247 FBM Manager 354
Field Device Editor mapping of FBM222 bus setting to FoxCTS
Bus Settings tab for an FBM222 67 parameters 353
Data Definition tab 185 tracking changes to defined parameters and
editing device templates 127 associated DCI blocks 357
editing slave devices 145 tracking commissioning actions 359
Field Device Manager tab 217 tracking downloads from DTMs 358
General tab for slave devices 145 tracking Profibus device configuration
Modules tab for a device 177 changes 355
overview 11 FoxView
setting user parameters for a device 183 ECB201 detail displays 421
Vendor DTM tab 207 Freeze actions 312
Field Device Manager 217 Freeze mode 176
Auto Online option 218 FSDLAY 80, 323
Compare tab 240 FSENAB 80, 323
Configuration Data tab 237
G
custom tabs 245
GAP Update Factor when editing FBM222 bus
Customize tab 242 settings 71
Device Parameter (DPV1) tab 238 gateway DTMs
Diagnostic tab 229 deleting a module DTM 215
Error Monitor 219 gateway DTMs in the Vendor DTM tab 208
Graphics and Links 225 General tab
461
editing slave devices 145 inputs

Global Customer Support xiv custom status handling 193
Go On-Line / Go Off-Line in System Manager installation
FBM222 382 FBM222 55
graphics IEE and Field Device Editor software xv
Field Device Manager 225 Integrated Development Environment (IDE) xv
Graphics on the device Information page 76 Intrinsic Safety 35
Groups IO Assignment Tab 276
editing devices in the Field Device Editor 177 IOUT block used to program Sync and Freeze
GSD files 103 actions 312
associating a GSD file with a device
template 106 L
changing GSD information in a device Links on the device Information page 76
template 124 links to documents
GSD data in the Field Device Manager Field Device Manager 225
Identification tab 224 locked status icons 172
locking and inheritance 171
use in Profibus 22
M
H
Maintenance user group 46
Hardware Type Master Station Address 69
when editing an ECB200/202 80 Max Retry Limit 71
when editing an ECB201 152 Max Station Delay Response Time
Highest Station Address in bus settings for an (MaxTSDR) 71
FBM222 69 media redundancy 41, 58
hyperlinks in the General tabs for a slave migration to FBM222 7
device 145 Min Slave Interval 70
Min Station Delay Response Time (Min TSDR)
I when editing devices in the Field Device
I/O timing 255 Editor 176
IDE xv Min Station Delay Response Time (MinTSDR)
identification data in Field Device Manager 224 when editing an FBM222 bus settings in the
Identification tab in Field Device Manager 223
Field Device Editor 71
Image Update
FBMs 384 Mode Support
editing devices in the Field Device Editor 176
implementation sequence 18
importing modular devices
binding a GSD file to a device template 105 overview 25
device configuration 162 selecting a soft module in Field Device Editor
device configurations from an FBM223 144 Modules tab 182
device configurations to a workshop selecting modules for a device in the Field
system 340 Device Editor 177
device templates 133 module configuration
switching to DTM-based module
importing files into device templates 103
inheritance 171 definition 120
input parameters 188 Modules tab
data types 188 for a compact device 181
deleting parameters 197 for a device with soft modules 182
Input tab multimaster configurations 35
Field Device Manager 227 setting target rotation time 72
Input tab in Data Definition 188
462
N when editing an ECB201 152

naming PERIOD and PHASE parameters
device templates 105 ECB200/202 77
FBM222s 63 ECB201 150
renaming a device template 132 PKIOPT 293
networks planning the network 19
bus length versus baud rate 24 Planning user group 46
extending networks 38 Plant Unit
terminations 36 editing devices in the Field Device Editor 148
non-transparent segment couplers 31 Plant Units 165
Notes button and window PMA file 429
Field Device Manager 221 Point Configuration String
Number of bytes field in the Point Configuration Diagnostic type (D) 304
String 264 Extended data type (E) 302
for devices attached to an FBM223 437
O Packed bits format (P) 303
Observer user group 46 Port
Offset field in the Point Configuration editing devices in the Field Device Editor 147
String 264 port configuration for an FBM223 429
open padlock icon 172 Port Existence 80
operator displays Port Number
overview 15 when editing an ECB201 152
output parameters 188 Profibus devices
data types 188 overview 21
deleting parameters 197 Profibus diagnostics
Output tab extended diagnostic formats 307
Field Device Manager 227 standard diagnostics bit definition 304
Output tab in Data Definition 188 Profibus Live List 311
Profibus networks 35
P dual media 41, 58
PA devices installing a single-media network 56
configuring analog inputs 288 Profibus PA
configuring input from a PA transmitter 315 timing 256
configuring output to a discrete PA valve PROFIBUS paradigm 20
controller 326 Profibus-PA devices
configuring output to a PA Positioner 318 overview 29
Failsafe support 258 programming Sync and Freeze actions with an
overview 29 IOUT block 312
status 265 DCI blocks 312
value status 288 project folders in the Template Toolbox 104,
PA positioner 130
recommended module selection 282 PSL file for a device attached to an FBM223 433
Packed bits format 303
padlock icons 171 Q
parameter attributes in the Data Definition question mark on a padlock icon 172
tab 188 Quiet Time (TQUI) in bus settings for an
parameter groups in Field Device Manager 243 FBM222 71
parameters and configuration
DPV1 451 R
Parent ECB readback parameter
output parameters 194
463
reading diagnostic data 304 Strategy Editor Device Browse 271

redundant adapters 33, 56 Sub-D connectors 36
reference documents xiii swap option
referencing a readback parameter 194 implicit byte-swapping with signed and
remote I/O systems 26 unsigned integers, floats and
repeaters 38 extended data types 300
Reports dialog box in Data Definition Input and used with digital outputs 298
Output tabs 188 Swap option in the Point Configuration
RIN block String 264
BLKSTA parameter 280 swapping in parameter definition 188
Profibus usage 278 switch option 293
scaling 280 Switch Roles
VALSTS parameter 280 FBM222 386
ROUT block Sync actions 312
BLKSTA parameter 284 Sync mode 176
confirmed outputs 285 SYSOPT
Profibus usage 282 ECB200/202 81
VALSTS parameter 285 system architecture 1
system configuration
S FBM222 59
security slave devices 139
adding users 50 System Manager displays
setting access permissions in Field Device Connections tab 387
Manager 247 FBM222 365
when using the device manufacturer’s slave devices 389
DTM 48 System Option
segment couplers 29 ECB200/202 81
bus settings for an FBM222 67
Pepperl & Fuchs SK3 30 T
Siemens DP/PA Link 31 tabs in Field Device Manager 222
transparent versus non-transparent 256 Target Rotation Time (TTR) 72
segment length 35 TAs 33
segments overview 4
extending segments 38 termination assemblies 4, 56
Setup Time (TSET) 71 terminations
Siemens DP/PA Link 31 active terminators 38
single media networks 33 in Sub-D connectors 35
slave device tracking Profibus device configuration
adding a device to an FBM223 435 changes 355
slave devices transparent segment couplers 30
configuration for an FBM223 433 Type 1 cable 57
creating new device template 105
U
Slot Time 71
Use for DCI Assignment option 187
Software File ID
Use Module Definition From
when editing an ECB201 152
switching from GSD to DTM 120
Software Type
user parameters
when editing an ECB200/202 80
DPV1 451
when editing an ECB201 152
User Parameters tab in the Field Device
Status field in the Point Configuration Editor 183
String 263 User Preferences dialog box 140
464
B0750BE – Rev L
V
validating bus settings for an FBM222 67
validating parameters 187
validation error flags 171
VALSTS parameter
RIN block 280
ROUT block 285
Vendor Comm DTM tab 347
Vendor DTM tab 207
gateway DTMs 208
W
Watch area
Device Parameter (DPV1) 238
Watch tab
Watchdog
editing devices in the Field Device Editor 176
workshop system
associating a communication DTM with the FBM 343
setup 337, 429
Z
ZCP270 4
465
Schneider Electric Systems USA, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424
https://pasupport.schneider-electric.com

B0750be L

Uploaded by

Copyright:

Available Formats

B0750be L

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B0750be L

Uploaded by

Copyright:

Available Formats

Foxboro Evo™

Process Automation System

© 2006-2017 Schneider Electric. All Rights Reserved.

Before You Begin .............................................xiii

CHAPTER 2: Planning the Network .................19

CHAPTER 3: Security .......................................45

CHAPTER 4: Installing and Configuring the

CHAPTER 5: Creating Device Templates ......101

Template Not Bound to a GSD File.................................................110

CHAPTER 6: Defining the Network................139

CHAPTER 7: Configuring Devices.................171

Soft Modules ...................................................................................182

CHAPTER 8: Field Device Manager ...............217

CHAPTER 9: Control Configuration ..............253

Configuring Output DCI Blocks ........................................................ 294

CHAPTER 10: Configuration Examples ........315

CHAPTER 11: Instrument Workshop

CHAPTER 12: Change Tracking.....................351

CHAPTER 13: System Management ..............361

APPENDIX A: FBM223 Configurations..........429

APPENDIX B: FBM223 to FBM222 Upgrade

Migrating FBM223 Database............................................................. 439

APPENDIX C: DPV1 User Parameters ...........451

The addition of either symbol to a "Danger" or

This is the safety alert symbol. It is used to alert you to

Before You Begin

About This Book

• Foxboro Evo™ Process Automation System Deployment Guide

• Christian Diedrich and Thomas Bangemann, et al. PROFIBUS PA,

Foxboro Evo Control Editors and Field Device

Note The PROFIBUS Support needs to be installed on the server (Galaxy

This chapter describes Foxboro Evo Control Software (hereinafter referred to

the Foxboro Evo Process Automation System (hereinafter referred to as the

Foxboro Evo Hardware

Figure 1-1. Redundant FBM222 and DIN Rail Mounted Termination

The FBM222 communicates with the PROFIBUS I/O devices on a

Single PROFIBUS Networks

Connection to The MESH Control Network

Redundant FBM222 Pair

One of two PROFIBUS networks

Figure 1-2. Redundant Interface with a Single PROFIBUS Network

Dual Media Networks

Connection to The MESH Control Network

Redundant FBM222 Pair

Fault Tolerant FBM222 Redundant

One of two PROFIBUS dual media

Figure 1-3. Redundant Interface with a Dual Media Network

Migration from the FBM223

Foxboro Evo Control Software

Device Templates and Device ECBs

Distributed Control Interface (DCI) Blocks

Table 1-1. Data Types Supported by DCI Blocks

DCI Block Data Types

Foxboro Evo Control Editors

Figure 1-4. Developing a Control Strategy in Foxboro Evo Control

The Control Editors provide a link to FoxCTS Change Tracking software

Figure 1-5 shows configuration of an FBM222’s bus parameters such as the

Figure 1-5. Setting FBM222 Bus Parameters

The editor’s FBM Manager tab contains a communication DTM that