IndustrialIT

800xA - Device Management

FOUNDATION Fieldbus
System Version 4.1

Configuration
 IndustrialIT
800xA - Device Management
FOUNDATION Fieldbus
System Version 4.1

Configuration
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.

This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.

Copyright © 2003-2005 by ABB.

All rights reserved.

Release: May 2005

Document number: 3BDD012902R4101

TRADEMARKS
Registrations and trademarks used in this document include:

Windows Registered trademark of Microsoft Corporation.

FOUNDATION Fieldbus Trademark of Fieldbus Foundation.

xxxx IT All names in the form of xxxx IT (e.g. Industrial IT)

are Trademarks of ABB.
 TABLE OF CONTENTS

About This Book

General ............................................................................................................................17
Use of Warning, Caution, Information, and Tip Icons ....................................................17
Document Conventions ...................................................................................................18
Terminology.....................................................................................................................19
Related Documentation ...................................................................................................31

Section 1 - Introduction
Product Overview ............................................................................................................33
Fieldbus Builder FOUNDATION Fieldbus..........................................................33
OPC Server FOUNDATION Fieldbus .................................................................34
FOUNDATION Fieldbus Device Integration Library..........................................34

Section 2 - Technical Overview FOUNDATION Fieldbus

ISO/OSI Reference Model ..............................................................................................38
Physical Layer .................................................................................................................39
Communication Stack .....................................................................................................40
Data Link Layer ...................................................................................................40
Application Layer.................................................................................................41
User Application..............................................................................................................41
Network Management .....................................................................................................44
System Management .......................................................................................................45
Object Dictionary ............................................................................................................45
Device Descriptions.........................................................................................................46

3BDD012902R4101 5
Table of Contents

Section 3 - Step by Step

Prerequisites and Requirements ...................................................................................... 47
Target Group.................................................................................................................... 47
Step 1: Synchronize the FF Library ................................................................................ 47
Step 2: Creation of an HSE Subnet ................................................................................. 49
Step 3: Configuration of an FF Application.................................................................... 55
Step 4: Loading of the FF Application............................................................................ 63
Step 4a: Precommissioning.................................................................................. 64
Step 4b: Commissioning ...................................................................................... 67
Step 5: Using FF Data in Controller Application and Operations .................................. 73
For use in the AC 800M....................................................................................... 73
For use in Operations and Asset Optimization .................................................... 75

Section 4 - Integration in Plant Explorer

Basic Principles of the Integration in Plant Explorer ...................................................... 77
Object Types in Plant Explorer ....................................................................................... 80
H1 and HSE Device Library ................................................................................ 81
FF Block Library ................................................................................................. 81
Edit FF Libraries ............................................................................................................. 81
Edit FF Libraries in Fieldbus Builder FF............................................................. 81
Upload FF Libraries to the Plant Explorer Workplace ........................................ 82
Configure HSE Subnet .................................................................................................... 82
Create HSE Subnet in the Plant Explorer Workplace .......................................... 82
Update FF Libraries for the HSE Subnet (Library Update)................................. 84
Configure HSE Subnet in Fieldbus Builder FF ................................................... 85
Upload HSE Subnet to the Plant Explorer Workplace......................................... 85
Navigation ....................................................................................................................... 86
Navigating to the FF Libraries ............................................................................. 86
Navigating to the HSE Subnet ............................................................................. 87
Navigating to a Selected FF Instance Object ....................................................... 87
Aspects of Fieldbus Builder FF in the Plant Explorer .................................................... 87
FF Management ................................................................................................... 89

6 3BDD012902R4101
 Table of Contents

FF Upload.............................................................................................................89
FF Device Info .....................................................................................................93
OPC Data Source Definition ................................................................................93
Control Connection ..............................................................................................95
Audit Trail .......................................................................................................................96
Security Definition ..........................................................................................................96
Advanced Management of FF Libraries ..........................................................................97
FF Library Merge .................................................................................................97
System Backup and Import/Export .................................................................................99

Section 5 - System Configuration

General Instructions.......................................................................................................101
FF Object Editor ............................................................................................................102
Call up FF Object Editor ....................................................................................102
General Description of the FF Object Editor .....................................................102
Interface of the FF Object Editor .......................................................................103
Operating Modes ................................................................................................103
General Functions of the FF Object Editor ........................................................104
Representation in the FF Object Editor Structure ..............................................110
Configuration of an FF Network ........................................................................112
Working with Templates................................................................................................112
Create Template..................................................................................................113
Archive Template ...............................................................................................115
Use Template......................................................................................................115
Tag List ..........................................................................................................................116
General Description of the Tag List ...................................................................116
Edit Tag List .......................................................................................................118
Cross References ...........................................................................................................129
Project Editor.................................................................................................................130
Call up Project Editor.........................................................................................130
General Description of the Project Editor ..........................................................131
Documentation ..............................................................................................................134
General Description of the Documentation........................................................134

3BDD012902R4101 7
Table of Contents

Documentation Management ............................................................................ 134

Create Drawing Header / Footer ........................................................................ 136
Basic Editing Steps ............................................................................................ 143
Compile Documentation Job ............................................................................. 145
Documentation Scope ........................................................................................ 147
Print out Documentation .................................................................................... 150
Comment Editing ............................................................................................... 152

Section 6 - Configuring an FF Network

System Structure ........................................................................................................... 155
FF Network with Interface to an IEC 61131 Controller .................................... 155
FF Network without Interface to an IEC 61131 Controller ............................... 161
FF Libraries ................................................................................................................... 161
Block Library ..................................................................................................... 162
H1 Device Library ............................................................................................. 163
HSE Device Library........................................................................................... 164
Expanding FF Libraries................................................................................................. 165
Importing H1 Field Devices............................................................................... 165
Importing HSE Devices ..................................................................................... 169
Assigning Bitmaps ............................................................................................. 170
Inserting FF Objects ...................................................................................................... 172
Insert HSE Subnet Object .................................................................................. 172
Insert HSE Host Object (HSEHostCI860)......................................................... 173
Insert Linking Device Module (HSE Device Instance Object).......................... 173
Insert H1 Link Object ........................................................................................ 173
Insert H1 Schedule Object ................................................................................. 174
Insert FF Application Object ............................................................................. 174
Insert H1 Device Instance Object ...................................................................... 174
Insert OPC Gateway Object............................................................................... 174
View of FF Object Instances ......................................................................................... 175
Detail View of the HSE Subnet Object.............................................................. 175
Detail View of the HSE Device Instance Object ............................................... 176
Detail View of the HSE Host Object ................................................................. 177

8 3BDD012902R4101
 Table of Contents

Detail View of the H1 Link Object ....................................................................178

Detail View of the H1 Schedule Object .............................................................180
Detail View of the FF Application Object .........................................................181
Detail View of the H1 Device Instance Object ..................................................182

Section 7 - Parameter Settings

HSE Device Library Object...........................................................................................185
H1 Device Library Object .............................................................................................186
FF Block Library Object ...............................................................................................187
FF Block Class Object...................................................................................................188
Initial Instance Parameters Tab ..........................................................................188
Block Info Tab....................................................................................................193
Managing Parameter Value Sets.........................................................................194
H1 Device Class Object:................................................................................................197
Device Info Tab ..................................................................................................198
Download Adjustment Tab.................................................................................199
Capabilities File Tab...........................................................................................200
Device Description Tab ......................................................................................202
VCR Info Tab .....................................................................................................203
Block Info Tab....................................................................................................204
Context Menu.....................................................................................................204
HSE Device Class Object ..............................................................................................205
Device Info Tab ..................................................................................................206
Capabilities File Tab...........................................................................................207
VCR Info Tab .....................................................................................................208
Revisions Tab .....................................................................................................209
Context Menu.....................................................................................................209
FF Network Object ........................................................................................................210
HSE Subnet Object........................................................................................................210
FF Signals Tab....................................................................................................210
HSE Subnet Settings Tab ...................................................................................211
HSE Host Object, HSEHostCI860 ................................................................................216
Communication Tab ...........................................................................................216

3BDD012902R4101 9
Table of Contents

Published/Subscribed Tab .................................................................................. 217

HSE Device Instance Object ......................................................................................... 219
Communication Tab........................................................................................... 219
H1 Link Object.............................................................................................................. 221
H1 Settings Tab.................................................................................................. 221
H1 Schedule Object....................................................................................................... 231
FF Application Object................................................................................................... 232
H1 Device Instance Object............................................................................................ 233
FF Block Instance Object.............................................................................................. 234
Parameters Tab................................................................................................... 236
Function Block Info Tab .................................................................................... 243
Network Configuration.................................................................................................. 244

Section 8 - OPC Server FOUNDATION Fieldbus

General Description ...................................................................................................... 247
Overview of the Functionality of OPC Server FF......................................................... 248
System Structure ................................................................................................ 248
Data Transfer...................................................................................................... 250
Tool Routing ...................................................................................................... 250
Browser Interface............................................................................................... 251
OPC Server Redundancy ................................................................................... 251
Resources, Maximum Values and Performance ................................................ 252
Configuration with Fieldbus Builder FF ....................................................................... 253
OPC Server FF................................................................................................... 253
Insertion of an OPC Server ................................................................................ 253
Network Configuration ...................................................................................... 255
Enabling of Tags for OPC Access ..................................................................... 260
Enabling Parameters of the FF Blocks for OPC Access.................................... 261
Parameters of the Hardware Objects.................................................................. 264
Starting the Communication .............................................................................. 264
Loading Project Data into OPC Server.............................................................. 264
Addressing of the Data ...................................................................................... 265
Data Types of the OPC Items............................................................................. 266

10 3BDD012902R4101
 Table of Contents

Version Check ....................................................................................................268

Tools for Error Diagnosis ..............................................................................................269
Trace Dialog of the OPC Server.........................................................................269
System Monitor for OPC ...................................................................................273
OPC Client.....................................................................................................................276
OPC-relevant Parameters ...................................................................................276

Section 9 - Dialog Editor for FF Blocks

General Description.......................................................................................................277
Operation of the Dialog Editor ......................................................................................277
Elements of the Dialog Editor .......................................................................................281

Section 10 - FF Signals
FF Signal List ................................................................................................................288
Call FF Signal List .............................................................................................288
Structure of the FF Signal List ...........................................................................289
Edit List Entries..................................................................................................292
Block Editing .....................................................................................................293
Create New FF Signal in an FF Application ......................................................295
Mapping of FF Signals to Channels for the HSE Host Object......................................296
Call List of Signal-Channel Mapping ................................................................296
Structure of the Published/Subscribed Tab ........................................................297
Configure Signal-Channel-Mapping ..................................................................299
Delete Signal-Channel-Mapping........................................................................300

Section 11 - FF Application Editor

FF Application...............................................................................................................301
Create FF Application ........................................................................................302
Edit FF Application............................................................................................303
Configuration Interface of the FF Application Editor ...................................................303
Structure of the Configuration Interface ............................................................303
Changing the Defaults........................................................................................306
Description of the FF Application Elements .................................................................307

3BDD012902R4101 11
Table of Contents

Signal Flow Lines .............................................................................................. 307

FF Signal Symbols............................................................................................. 307
FF Function Blocks............................................................................................ 309
Comments .......................................................................................................... 311
Set Parameters for the FF Application Elements .......................................................... 311
FF Signals .......................................................................................................... 311
FF Function Blocks............................................................................................ 312
Comments .......................................................................................................... 314
Editing an FF Application ............................................................................................. 314
Drawing Signal Flow Lines ............................................................................... 314
Adding an FF Signal to an FF Application........................................................ 317
Modifying an FF Signal in an FF Application................................................... 318
Adding an FF Function Block ........................................................................... 318
Assigning an FF Function Block to a Device .................................................... 320
Inserting Columns and Rows ............................................................................. 320
Block Operations ............................................................................................... 322
FF Signal List and Tag List ........................................................................................... 327
FF Signal List..................................................................................................... 327
Tag List .......................................................................................................... 327
Cross References ........................................................................................................... 327
General Processing Functions ....................................................................................... 328
Save FF Application........................................................................................... 328
Document FF Application ................................................................................. 328
Setting FF Application parameters .................................................................... 328
End FF Application Editing ............................................................................... 329
Producing Hard Copy ........................................................................................ 329
Check FF Application Elements ........................................................................ 330
Delete FF Application........................................................................................ 330
Copy and Paste FF Application ......................................................................... 330
Data Exchange ................................................................................................... 331

Section 12 - Schedule Editor

H1 Schedule .................................................................................................................. 333

12 3BDD012902R4101
 Table of Contents

Schedule Editor Interface ..............................................................................................333

Structure of the Graphical Display.....................................................................334
Change Defaults .................................................................................................335
Edit H1 Schedule ...........................................................................................................336
Reserve Communication Time for Client/Server Communication ....................336
Move Block ........................................................................................................338
Optimize H1 Schedule .......................................................................................339
Save H1 Schedule...............................................................................................340

Section 13 - Commissioning FF Objects

General Description of Commissioning .......................................................................341
Start Commissioning ..........................................................................................341
Commissioning Interface ...................................................................................343
Display and Write Online Values .......................................................................343
Display During Commissioning ....................................................................................343
HSE Subnet Object ............................................................................................344
HSE Device Instance Object ..............................................................................345
HSE Host Object ................................................................................................345
H1 Link Object...................................................................................................347
FF Application Object........................................................................................347
H1 Device Instance Object.................................................................................349
Status Displays for the Objects ..........................................................................350
H1 Device Assignment Dialog...........................................................................355
Download Dialog ...............................................................................................360
Commissioning of an FF Network ................................................................................374
Phase 1: Precommissioning................................................................................376
Precommissioning Options ................................................................................378
Phase 2: Loading ................................................................................................379
Phase 3: Online Parameter Settings ...................................................................379
Display Subscribers on the HSE Subnet ............................................................382
Replacing FF Devices....................................................................................................383
Replacing an FF Linking Device .......................................................................383
Replacing an H1 Device.....................................................................................385

3BDD012902R4101 13
Table of Contents

Section 14 - FF Device Integration Library

Overview ....................................................................................................................... 387
Functionality ...................................................................................................... 388
Prerequisites and Requirements......................................................................... 389
Device-Type-Specific Product Documentation ............................................................. 391
Connection to Asset Optimization ................................................................................ 392
Asset Monitoring ............................................................................................... 392
CMMS Connectivity .......................................................................................... 394
Additional Aspects of LD 800HSE............................................................................... 395
Asset Monitor and Diagnostics Faceplate.......................................................... 395
FWeb Server Aspects ......................................................................................... 402

Appendix A - Configuration Rules

Appendix B - Documentation Settings

Document Types............................................................................................................ 407
Description of the Fields or Contents............................................................................ 408
Field Names in the Drawing Footer / Header................................................................ 409
Variables for Drawing Footer/ Header Inscriptions ...................................................... 412
Fonts, National Languages and Bitmaps in the Drawing Footer / Header.................... 414
Using Fonts in the Drawing Footer.................................................................... 415
Using Fonts in the Drawing Header................................................................... 415
Presetting the Field Contents and Titles........................................................................ 416

Appendix C - Diagnostic Data

Pre-defined Items of the Hardware Objects .................................................................. 417
HSE Device........................................................................................................ 417
H1 Link .......................................................................................................... 418
H1 Device (H1 Field Device) ............................................................................ 421
Description of the Live List Data .................................................................................. 425
HSE Device........................................................................................................ 425
H1 Link .......................................................................................................... 427
H1 Device (H1 Field Device) ............................................................................ 428

14 3BDD012902R4101
 Table of Contents

Appendix D - OPC Keyword Tracing

Structure of Trace Entries..............................................................................................431
Logging of the Keyword Setting ...................................................................................432
Logged Functions ..........................................................................................................432
Keyword: Alarms and Events.............................................................................432
Keyword: Common Functionality......................................................................433
Keyword: DAL ...................................................................................................433
Keyword: DMS ..................................................................................................434
Keyword: Fieldbus .............................................................................................434
Keyword: Group Functionality ..........................................................................435
Keyword: Item Functionality .............................................................................435
Keyword: OPC Data Access Automation 1.0 Interfaces....................................436
Keyword: OPC Data Access Custom Interfaces ................................................437
Keyword: Server Functionality ..........................................................................439
Examples of Applications..............................................................................................439
Which Values are Sent to the OPC Client by the OPC Server? .........................439
Which OPC Items are Handled in the OPC Groups?.........................................440
Which Parameters are Requested by the Client? ...............................................440
Which Client Connections have Existed since when to the OPC Server? .........441

Index

3BDD012902R4101 15
Table of Contents

16 3BDD012902R4101
 About This Book

General
This manual describes the configuration and commisioning for the FOUNDATION
Fieldbus Device Integration, i.e. Fieldbus Builder FF , OPC Server FF and FF
Device Integration Library.

Use of Warning, Caution, Information, and Tip Icons

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.

Warning icon indicates the presence of a hazard which could result in personal
injury.

Caution icon indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard which could
result in corruption of software or damage to equipment/property.

Information icon alerts the reader to pertinent facts and conditions.

Tip icon indicates advice on, for example, how to design your project or how to
use a certain function

3BDD012902R4101 17
Document Conventions About This Book

Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.

Document Conventions
The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
• System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.

18 3BDD012902R4101
About This Book Terminology

You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name

Terminology
You should familiarise yourself with the following list of terms which refer to the
product FOUNDATION Fieldbus Device Integration.

Term Description
Aspect An aspect is the description of properties of an Aspect
Object. Some examples of aspects are name, function
plan, control logic and graphics.
Aspect Object A computer representation of real objects such as
pumps and valves or a number of virtual objects such as
service or object type. An Aspect Object is described by
its aspects and organised in structures.
Component Object Definition programming interface to allow for the creation
Model (COM) of components for use in integrating custom applications
or to allow diverse components to interact.
Distributed COM Remote Procedure Calls to enable distributed
(DCOM) component objects to communicate with each other.
EngineerIT The umbrella term for a number of products for the
engineering of process plants.
Fieldbus Builder FF The 800xA system extension that owns and stores all
(FBB FF) FOUNDATION Fieldbus relevant data and the business
logic belonging to it. The FBB FF exposes its objects
through an automation interface.
FOUNDATION Fieldbus Bi-directional communications protocol used for
(FF) communications among field instrumentation and control
systems.

3BDD012902R4101 19
Terminology About This Book

Term Description
IndustrialIT Industriai IT is ABB’s solution for business processes. It
allows seamless integration of systems for plant
automation, plant optimisation and common business
processes at run time.
OLE for Process Control OPC is based on the Microsoft COM/DCOM technology.
(OPC) DCOM permits data exchange across computer
boundaries.
OPC Server FF OPC Server FF makes data from FOUNDATION
Fieldbus devices available to any OPC Clients.
Plant Explorer Used to browse and search the structures of the plant
and to create Aspect Objects.
Process Portal A (PPA) A collection of software that forms the basis for an
Industrial IT system, and provides the development and
execution environment for Industrial IT.

You should familiarise yourself with the following list of terms which refer to the
FOUNDATION Fieldbus terminolgy.

Term Description
Application Process Application Process (AP) is a term defined by the
(AP) International Standards Organization (ISO) Open
Systems Interconnect (OSI) Reference Model (RM), ISO
7498, to describe the portion of a distributed application
that is resident in a single device. The term has been
adapted for the fieldbus environment to describe entities
within devices that perform a related set of functions,
such as function block processing, network
management, and system management. Please refer to
Function Block Application Process (FBAP).
Basic Device A Basic Device is any H1 field device not having the
capability to control communications on an H1 fieldbus
segment. A Basic Device is neither a Link Master (and
therefore not capable of taking the LAS role) nor an H1
Bridge.

20 3BDD012902R4101
About This Book Terminology

Term Description
Bridge Please refer to H1 Bridge.
Capabilities File A Capabilities File describes the communication objects
in a fieldbus device. A configuration device can use
Device Description (DD) Files and Capabilities Files to
configure a fieldbus system without having the fieldbus
devices online. The Capabilities File describes field
device contents that are visible from the network but
cannot be changed by configuration.
Communications Stack A set of layer protocols that operate together in a device
to provide communication services to its users. A
complete FOUNDATION Fieldbus communications stack
includes all layer protocols, the Network Management
Agent, and the System Management Kernel.
Compel Data DLL term used in the context of H1 publisher/subscriber
communication.
Connector A Connector is a coupling device used to connect the
wire medium to a fieldbus device or to another segment
of wire.
Control Loop A Control Loop is a connected group of Function Blocks
(FBs) including a feedback connection that execute at a
specified rate within a fieldbus device or distributed
across the fieldbus network.
Coupler A Coupler is a physical interface between a Trunk and
Spur, or a Trunk and a device.
Custom Function Block The Fieldbus Foundation has released specifications for
21 types of standard function blocks. A manufacturer can
implement additional custom types of blocks, which do
not base on the standard blocks.

3BDD012902R4101 21
Terminology About This Book

Term Description
Data Link Layer (DLL) The Data Link Layer (DLL) controls transmission of
messages onto the fieldbus, and manages access to the
fieldbus through the Link Active Scheduler (LAS). The
DLL used by FOUNDATION Fieldbus is defined in IEC
61158 and ISA S50. It includes Publisher/Subscriber,
Client/Server and Source/Sink communication services.
Device Description (DD) A Device Description (DD) provides an extended
description of each object in the Virtual Field Device
(VFD), and includes information needed for a control
system or host to understand the meaning of data in the
VFD.
Enhanced Function The Fieldbus Foundation has released specifications for
Block 21 types of standard function blocks. A manufacturer can
enhance these block types by adding proprietary
parameters and functionality, but the parameters and
algorithms defined in the standard block have to remain
unchanged.
FF Network A FOUNDATION Fieldbus network is comprised of one
or more HSE subnets and/or one or more H1 links all
interconnected
Fieldbus A Fieldbus is a digital, two-way, multi-drop
communication link among intelligent measurement and
control devices. It serves as a Local Area Network (LAN)
for advanced process control, remote input/output and
high speed factory automation applications.
Fieldbus Access The Fieldbus Access Sublayer (FAS) maps the Fieldbus
Sublayer (FAS) Message Specification (FMS) onto the Data Link Layer
(DLL).
Fieldbus Builder FF The application that owns and stores all fieldbus relevant
Application data and the business logic belonging to it. The FBB FF
exposes its objects through an automation interface. It
has no own graphical user interface, but runs in the
background.

22 3BDD012902R4101
About This Book Terminology

Term Description
Fieldbus Builder FF The complete product, consisting of the Fieldbus Builder
Product (FBB FF) FF Application and its supporting aspect system, as an
800xA system extension.
Fieldbus Messaging The Fieldbus Messaging Specification (FMS) contains
Specification (FMS) definitions of Application Layer services in
FOUNDATION Fieldbus. The FMS specifies services
and message formats for accessing Function Block (FB)
parameters, as well as Object Dictionary (OD)
descriptions for those parameters defined in the Virtual
Field Device (VFD). FMS is derived from the
Manufacturing Messaging Specification (MMS).
Flexible Function Block A Flexible Function Block (FB) is similar to a Standard
FB, except that the function of the block, the order and
definition of the block parameters, and the time required
to execute the block are determined by an application-
specific algorithm created by a programming tool.
Flexible Function Blocks (FFBs) are typically used for
control of discrete processes and for hybrid (batch)
processes. A Programmable Logic Controller (PLC) can
be modeled as a Flexible Function Block device.
Forwarding The action taken when receiving a message on one
network segment (HSE or H1) with a destination
address of another segment and sending it on or in the
direction of the destination segment.
FOUNDATION Fieldbus Please refer to FF Network.
Network
Function Block (FB) Function Blocks (FBs) are built into fieldbus devices as
needed to achieve the desired control functionality. A
Function Block can be of type standard, enhanced or
custom type.
Function Block The Function Block Application Diagram includes
Application Diagram function blocks and signal linkages between them.
(FBAD)

3BDD012902R4101 23
Terminology About This Book

Term Description
Function Block A Function Block Application Process (FBAP) is that part
Application Process in the software of a device which contains the Function
(FBAP) Blocks and executes the Function Block Application. The
FBAP is organized as separate VFD.
H1 H1 is a term used to describe a FOUNDATION Fieldbus
network operating at 31.25 kbit/second.
H1 Bridge A device connected to multiple H1 links whose data link
layer performs forwarding and republishing between and
among the links. An H1 bridge may be contained in a
linking device.
H1 Field Device An H1 Field Device is a fieldbus device connected
directly to an H1 fieldbus. Typical H1 Field Devices are
valves and transmitters.
H1 Link An H1 link interconnects one or more H1 Devices.
Please refer to Link
H1 Repeater An H1 Repeater is an active, bus-powered or non-bus-
powered device used to extend the range over which
signals can be correctly transmitted and received for a
given medium. A maximum of four Repeaters and/or
active Couplers can be used between any two devices
on an H1 fieldbus network.
High Speed Ethernet High Speed Ethernet (HSE) is the Fieldbus Foundation's
(HSE) backbone network typically running at, but not being
limited to 100 Mbit/second.
Host Device Generic term for devices connected to an FF network
and communicating with FF devices by use of FF H1 or
HSE protocols. Typical examples are configurators, OPC
servers or DCS/PLC systems.
HSE Device Any FOUNDATION Fieldbus device type connected
directly to HSE Media. Examples include Linking
Devices, I/O Gateway Devices, and HSE Field Devices.

24 3BDD012902R4101
About This Book Terminology

Term Description
HSE Field Device An HSE Field Device is a fieldbus device connected
directly to a High Speed Ethernet (HSE) fieldbus. Typical
HSE Field Devices are HSE Linking Devices and HSE
Field Devices running Function Blocks (FBs).
HSE Linking Device HSE Linking Devices interconnect one or more H1 links
to an HSE subnet. Linking devices provide for access
between HSE devices and H1 devices and for access
between H1 devices interconnected by an HSE network.
A linking device may also contain an H1 bridge that
provides for H1 to H1 communications between bridged
H1 links.
HSE Subnet HSE Subnets are IP networks. They are permitted to
contain bridges, but not routers.
The HSE Subnet is used to qualify the Link Id. The
combination of the HSE Subnet and the Link Id is unique
across all HSE Subnets of a system.
An HSE subnet consists of one or more HSE devices
connected via Ethernet.
HSE devices on a subnet may be interconnected with
standard switches.
Multiple HSE subnets may be interconnected using
standard routers.
Input/Output (I/O) An Input/Output (I/O) Subsystem Interface is a device
Subsystem Interface used to connect other types of communications
protocols to a fieldbus Segment or Segments.
Interchangeability Interchangeability is the capability to substitute a device
from one manufacturer with that of another manufacturer
on a fieldbus network without loss of functionality or
degree of integration.
Interoperability Interoperability is the capability of a device from one
manufacturer to interact with that of another
manufacturer on a fieldbus network without loss of
functionality or degree of integration.

3BDD012902R4101 25
Terminology About This Book

Term Description
Link A Link is the logical medium by which H1 Fieldbus
devices are interconnected. It is composed of one or
more physical segments interconnected by bus
Repeaters or Couplers. All of the devices on a link share
a common schedule which is administered by that link's
current LAS. In FOUNDATION Fieldbus, the term link is
only used on H1 (H1 link), not on HSE (Please refer to
HSE subnet).
Link Active Scheduler A Link Active Scheduler (LAS) is a deterministic,
(LAS) centralized bus scheduler that maintains a list of
transmission times for all data buffers in all devices that
need to be cyclically transmitted. At one point in time
only one Link Master (LM) device on an H1 fieldbus Link
can function as that link's LAS.
Link Master (LM) A Link Master (LM) is an H1 device containing Link
Active Scheduler (LAS) functionality, thus having the
ability to control communications on an H1 Link. There
must be at least one LM on any H1 Link; only one of the
LM devices will take the LAS role.
Link Object A Link Object contains information to link Function Block
(FB) Input/Output (I/O) parameters in the same device
and between different devices. The Link Object links
directly to a Virtual Communications Relationship (VCR)
or another Function Block Input/Output parameter. It is
also called Linkage Object.
Linkage Object Please refer to Link Object.
Linking Device Please refer to HSE Linking Device.
Macrocyle Please refer to Schedule.
Multiple Input/Output Multiple Input/Output Function Blocks increase the
Function Block efficiency in handling a large amount of signals by
combining more than one Input or Output into one
Function Block.

26 3BDD012902R4101
About This Book Terminology

Term Description
Network Management Network Management (NM) permits FOUNDATION
(NM) Network Manager (NMgr, Host) entities to conduct
management operations over the network by using
Network Management Agents (NMAs) in the devices.
Each Network Management Agent (NMA) is responsible
for managing the communications within a device. The
NMgr and NMA communicate through use of the
Fieldbus Messaging Specification (FMS) and Virtual
Communications Relationship (VCR).
Network Management Please refer to Network Management.
Agent (NMA)
Network Management The NMA VFD contains network and system
Information Base management information bases (NMIB and SMIB) for
(NMIB) the device. The NMIB contains objects related to device
Network Management.
Object Dictionary An Object Dictionary (OD) contains all Function Block
(FB), Resource Block (RB) and Transducer Block (TB)
parameters used in a device. Through these parameters,
the blocks may be accessed over the fieldbus network.
Physical Device (PD) The term references the real field device as opposed to
a Virtual Field Device (VFD).
Physical Layer The Physical Layer receives messages from the
Communications Stack and converts the messages into
physical signals on the fieldbus transmission medium,
and vice-versa.
Repeater Please refer to H1 Repeater.
Republishing The action taken when subscribing to data on one
network segment (UDP or H1) and publishing it on
another.
Resource Block (RB) A Resource Block (RB) describes characteristics of the
fieldbus device such as the device name, manufacturer
and serial number. There is only one Resource Block
(RB) in a device.

3BDD012902R4101 27
Terminology About This Book

Term Description
Schedule A Schedule defines when Function Blocks execute (FB
schedule) and when data and status is published on the
bus (LAS schedule). The LAS schedule together with all
device FB schedules forms the macro cycle of an H1
link.
Segment A Segment is a section of an H1 fieldbus that is
terminated in its characteristic impedance. Segments
can be linked by Repeaters to form a longer H1 fieldbus.
Each Segment can include up to 32 H1 devices.
Splice A Splice is an H1 Spur measuring less than 1 m (3.28 ft.)
in length.
Spur A Spur is an H1 branch line connecting to the Trunk that
is a final circuit. A Spur can vary in length from 1 m (3.28
ft.) to 120 m (394 ft.).
Standard Function Standard Function Blocks (FBs) are built into fieldbus
Block (FB) devices as needed to achieve the desired control
functionality. Automation functions provided by Standard
FBs include Analog Input (AI), Analog Output (AO) and
Proportional/Integral/Derivative (PID) control. The
Fieldbus Foundation has released specifications for 21
types of Standard FBs. There can be many types of FBs
in a device. The order and definition of Standard FB
parameters are fixed and defined by the specifications.
Enhanced Function Blocks are Standard FBs with
additional vendor specific parameters, i.e. derived from
Standard FBs. Custom Function Blocks are vendor
specific FBs that are not derived from Standard FBs.
Switch A Switch is standard Ethernet equipment used to
interconnect multiple High Speed Ethernet (HSE)
devices such as HSE Linking Devices and HSE Field
Devices to form a larger HSE Subnet.

28 3BDD012902R4101
About This Book Terminology

Term Description
System Management System Management (SM) synchronizes execution of
(SM) Function Blocks (FBs) and the communication of
Function Block (FB) parameters on the fieldbus, and
handles publication of the time of day to all devices,
automatic assignment of device addresses, and
searching for parameter names or "tags" on the fieldbus.
System Management The NMA VFD contains network and system
Information Base management information bases (NMIB and SMIB) for
(SMIB) the device. This SMIB contain objects related device
System Management.
Terminator A Terminator is an impedance-matching module used at
or near each end of a transmission line. Only two
Terminators can be used on a single H1 segment.
Transducer Block (TB) A Transducer Block (TB) decouples Function Blocks
(FBs) from the local Input/Output (I/O) functions required
to read sensors and command output hardware.
Transducer Blocks (TBs) contain information such as
calibration date and sensor type. There is usually one
TB channel for each input or output of a Function Block
(FB).
Transmit Control The well known internet transport protocol for
Protocol (TCP) connection- oriented reliable communication is typically
used in the HSE protocol stack for the Client/Server
FMS communication services, e.g. In Configuration
download.
Transmitter A Transmitter is an active fieldbus device containing
circuitry which applies a digital signal on the bus.
"Transmitter" is also often used as a generic term for
input field devices (e.g. Temperature transmitter) as
opposed to "valve" for output field devices.
Trunk A Trunk is the main communication highway between
devices on an H1 fieldbus network. The Trunk acts as a
source of main supply to Spurs on the network.

3BDD012902R4101 29
Terminology About This Book

Term Description
User Application The User Application is based on "blocks," including
Resource Blocks (RBs), Function Blocks (FBs) and
Transducer Blocks (TBs), which represent different types
of application functions.
User Datagram Protocol The well known internet transport protocol for
(UDP) connectionless, fast communication is used in the HSE
protocol stack as the main transport mechanism,
especially for Publisher/Subscriber communication and
other multicast communication services. TCP is typically
used for more reliable Client/Server communication.
User Layer The User Layer provides scheduling of Function Blocks
(FBs), as well as Device Descriptions (DDs) which allow
the host system to communicate with devices without the
need for custom programming.
Virtual Communication Configured application layer communication channels
Relationship (VCR) that provide for the transfer of data between applications.
FOUNDATION Fieldbus describes three types of VCRs:
1. Publisher/Subscriber (Process Data exchange)
2. Client/Server (Parameter access)
3. Source/Sink (Alerts, Reports)
Virtual Field Device A Virtual Field Device (VFD) is used to remotely view
(VFD) local device data described in the object dictionary. A
typical device will have at least two Virtual Field Devices
(VFDs): The Network Management Agent (NMA VFD)
that can be viewed as the operating system of the field
device, and the Function Block Application Process
(FBAP VFD) that can be viewed as the User application
running on the Operating system.

30 3BDD012902R4101
About This Book Related Documentation

Related Documentation
The following is a listing of documentation related to 800xA - FOUNDATION
Fieldbus.

Title Description
800xA - System This manual describes how to install software
System Version 4.1 for the Industrial IT 800xA System. It covers the
Installation core and optional products for the 800xA
3BSE034678 System.

800xA - System This manual describes how to set up the

System Version 4.1 Industrial IT 800xA System. It covers the core
Post Installation Setup and optional products for the 800xA System.
3BUA000156
800xA - Fieldbus This manual describes faceplates for standard
FOUNDATION Fieldbus Device FF function blocks processed in the field
Integration devices.
System Version 4.1
Operation
3BDD011776
800xA - Device Management This document provides information not
FOUNDATION Fieldbus contained in the ordinary manuals, sales
System Version 4.1 information or other types of product
Release Notes information for the product FOUNDATION
3BDD012905 Fieldbus Device Integration which consists of
the components Fieldbus Builder FF, OPC
Server FF, and FF Device Integration Library. It
describes known software or documentation
problems and errors that were discovered at
too late a date to be included in the current
user instructions.

3BDD012902R4101 31
Related Documentation About This Book

Title Description
800xA - Control and I/O This document describes the configuration of
FOUNDATION Fieldbus HSE Control Builder M control applications with
System Version 4.1 FOUNDATION Fieldbus HSE using the CI860
Engineering and Configuration module along with HSE linking devices and
3BDD012903 Fieldbus Builder FOUNDATION Fieldbus as FF
configuration tool.
Field IT This manual describes the hardware
FOUNDATION Fieldbus Linking installation, configuration, and handling of the
Device FOUNDATION Fieldbus Linking Device LD
LD 800HSE 800HSE in detail. The reader should have a
User Instructions basic understanding of the FOUNDATION
3BDD011677 Fieldbus system architecture and
communications protocol.
Field IT This document provides information not
FOUNDATION Fieldbus Linking contained in the ordinary manuals, sales
Device information or other types of product
LD 800HSE information for the Linking Device LD 800HSE.
Release Notes It describes known software or documentation
3BDD011679 problems and errors that were discovered at
too late a date to be included in the current
user instructions.
Industrial Ethernet: A Pocket How to Plan, Install, and Maintain TCP/IP
Guide Ethernet Networks: The Basic Reference
Publisher: ISA - The Guide for Automation and Process Control
Instrumentation, Systems, and Engineers.
Automation Society, May 2002
ISBN: 1556177887
Foundation Fieldbus: A Pocket Summary of background information, tips,
Guide tricks, and items to note when installing,
Publisher: ISA - The maintaining, or trouble-shooting.
Instrumentation, Systems, and
Automation Society, July 2002
ISBN: 1556177755

32 3BDD012902R4101
 Section 1 Introduction

Product Overview
FOUNDATION Fieldbus provides an open standard for process automation
applications and is supported by all the major control and automation product
manufacturers. It consists of a low-speed bus (H1) designed for the interconnection
of “field” equipment such as sensors, actuators, and I/O, and a high-speed bus
(HSE, High Speed Ethernet) allowing optimization of network design and
integration of high speed controllers (such as PLC or DCS), H1 subsystems (via
linking devices), data servers and workstations. FOUNDATION Fieldbus provides
built-in capability to distribute the control application across the network.
FOUNDATION Fieldbus Device Integration integrates the FOUNDATION Fieldbus
architecture and field devices into Industrial IT 800xA environment. It consists of
these main components:
• Fieldbus Builder FOUNDATION Fieldbus
• OPC Server FOUNDATION Fieldbus
• FOUNDATION Fieldbus Device Integration Library

Fieldbus Builder FOUNDATION Fieldbus

The FOUNDATION Fieldbus network and application configuration is done by the
Fieldbus Builder FOUNDATION Fieldbus. It acts as an integrated application
within the Industrial IT 800xA environment. The main tasks are:
• Managing the FOUNDATION Fieldbus network
• Creating FF Applications running on H1 links
• Parameterization of field devices

3BDD012902R4101 33
OPC Server FOUNDATION Fieldbus Section 1 Introduction

• Generation of H1 schedules and configuration data for Link Active Scheduler

(LAS)
• Managing device and function block libraries (this includes expanding the set
of devices that is provided by the FF Device Integration Library via import of
Device Description files and Capabilities files)
• Download and commissioning
• Network and device diagnosis
• Configuration of OPC Server FOUNDATION Fieldbus

OPC Server FOUNDATION Fieldbus

The OPC Server FOUNDATION Fieldbus makes data from FOUNDATION Field-
bus devices available to any desired OPC Client of the 800xA system. As a result
visualization packages which have an OPC Client interface, e.g. Process Portal or
Asset Monitors, can access data of the connected field devices. The OPC Server FF
is configured by Fieldbus Builder FF.

FOUNDATION Fieldbus Device Integration Library

For easy integration of FOUNDATION Fieldbus devices into the Industrial IT
800xA environment a predefined Field Device Library for FOUNDATION Fieldbus
devices is provided.1
Device types provided with this library are available for immediate use in Fieldbus
Builder FF as well as in Plant Explorer.
In Fieldbus Builder FF these device types are present in the H1 and HSE device
libraries and therefore need not be imported using Device Description and
Capabilities files. Device-type-specific graphical representations (bitmaps) are
provided. Furthermore the block library in Fieldbus Builder FF contains the
standard function blocks specified by the Fieldbus Foundation and additional blocks
that are provided by those device types included in the FF Device Integration
Library. For frequently used blocks, both specific parameter input dialogs and
predefined block-type-specific parameter value sets are provided.

1. Note that using the full scope of the FOUNDATION Fieldbus Device Integration Library requires the Optimize
IT Asset Optimization software to be installed and licensed.

34 3BDD012902R4101
Section 1 Introduction FOUNDATION Fieldbus Device Integration Library

In Plant Explorer device type objects are provided. Each object has been pre-tested
with a set of aspects:
• Product Documentation
• Asset Monitoring
• Maintenance Management (CMMS Connectivity)
• Function Block Faceplates

Product Documentation
Product documentation is directly available at the device object. Key product data
are bundled in convenient electronic format. Thereby documents like Data Sheet,
Installation, Configuration, and Operation Manual as well as Maintenance &
Service Manual are accessible via mouse click.

Asset Monitoring
Asset Monitor, Asset Reporter and Asset Viewer acquire and analyse asset status and
condition information. They notify operators and maintenance personnel when an
abnormal condition calls for maintenance action.

Maintenance Management
CMMS Connectivity provides the seamless integration of the Computerized
Maintenance Management Systems (CMMS) Maximo into the Industrial IT system
environment. Asset related maintenance information is accessed via standard, pre-
configured CMMS views allowing for the quick and efficient assessment of
maintenance needs and status.

Function Block Faceplates

Furthermore faceplates are provided for a set of frequently used function blocks. A
faceplate is the graphical user interface for the operator to the specific process
function (analog/discrete input/output monitoring, PID controller, etc.). Thereby

3BDD012902R4101 35
FOUNDATION Fieldbus Device Integration Library Section 1 Introduction

after configuration and download, the right faceplate is immediately available for
operation of functions distributed in the FF subsystem.
The object types in the Device Integration Package are created by ABB and tested
for use in the 800xA system. ABB created these object types based on data
provided by individual device vendors (e.g. DDs, Device specific DTMs and
Asset Monitor behavior specifications), which ABB relies on as accurately
reflecting the actual device specification and behavior. Therefore, ABB cannot
assume liability for events that are caused by devices that are not functioning
according to Fieldbus Standards, or device specifications, or for events that are
caused by mismatches between the device behavior and the input data provided
by the device vendor.

36 3BDD012902R4101
 Section 2 Technical Overview
FOUNDATION Fieldbus

FOUNDATION Fieldbus (FF) is a fieldbus protocol based on international

standards and designed for applications in the manufacturing industry, process
automation and buildings automation. The guidelines for this fieldbus standard are
published by the Fieldbus Foundation.
FF defines two communication profiles, H1 and HSE. The H1 profile, with a
transmission rate of 31.25 kilobits per second, is preferably used for direct
communication between field devices in one link (H1 link). The HSE profile, which
is based on standard Ethernet and typically features a transmission rate of 100
megabits per second, serves first and foremost as a powerful backbone for the
connection between H1 links. The devices that are already available on the market
and support the HSE profile are FF linking devices. They serve as a gateway
between the field devices on the H1 links and the HSE backbone. FOUNDATION
Fieldbus Device Integration supports the ABB Linking Device LD 800HSE.
A FOUNDATION Fieldbus network (FF network) is linked with the IEC 61131
controller via a FOUNDATION Fieldbus HSE communication interface module
CI860 in the AC 800M; this module is installed as an HSE host on the powerful
HSE subnet.
The following overview relates to the H1 communication profile. More detailed
information on the HSE profile can be found in the FF specifications. The
fundamental concepts behind HSE are explained in the FF specifications:
• FF-581, System Architecture.
• FF-941, HSE Profile.

3BDD012902R4101 37
ISO/OSI Reference Model Section 2 Technical Overview FOUNDATION Fieldbus

ISO/OSI Reference Model

The FF specification for the H1 communication profile is based on the International
Standard Organization’s Open Systems Interconnection (ISO/OSI) Reference
Model ISO 7498 (Open Systems Interconnection Model standard) and consists of
the following three functional components:
• the Physical Layer.
• the communication "stack“.
• the User Application (user layer).
Each layer contributes a proportion of the messages sent on the fieldbus (refer to
Figure 1).

ISO/OSI Reference Model* Fieldbus Foundation model

OSI layer User application User application

FMS
Application layer 7
FAS

Presentation layer 6
Communication
Session layer 5 "stack"
Transport layer 4

Network layer 3

Data link layer 2 DLL

Physical layer 1 Physical layer Physical layer

*The "User application" is not defined in the OSI reference model.

Figure 1. ISO/OSI Reference Model

The fieldbus system is a LAN which has to exchange data at high speed, thereby
only the OSI layers 1, 2 and 7 are implemented. The Physical Layer corresponds to
OSI layer 1, which receives coded messages from the overlaid layers and converts
them to physical signals on the transmission medium and vice versa. The
communication stack corresponds to layers 2 and 7 of the OSI reference model. The

38 3BDD012902R4101
Section 2 Technical Overview FOUNDATION Fieldbus Physical Layer

OSI layer 7 (Application Layer) codes and decodes the commands from the User
Application. The OSI layer 2 (Data Link Layer) controls via layer 1 (Physical
Layer) the sending of messages over the fieldbus. This layer also controls the access
rights to the fieldbus through a deterministic central bus scheduler, the Link Active
Scheduler (LAS).
The comprehensive specification of a Standard User Application based on function
blocks and device descriptions (DD) ensures the compatibility between FF devices
from different manufacturers.

Physical Layer
FF H1 uses bus physics complying with IEC 61158-2 and ISA S50.02 Part 2.
The Physical Layer defines two different versions of power supplies for a twisted
pair cable. In the one version the field devices obtain their power via the fieldbus.
This version supports low-power devices for use in intrinsically safe areas. The
second version provides field devices with an external power supply.
Characteristic data of the bus physics (cable type A):
• Transmission rate: 31.25 kilobits per second.
• Topology: Bus or tree.
• Power supply via the bus: optional.
• Intrinsic safety: optional.
• Number of devices: 2 - 32 (intrinsic safety and/or power supply via the bus
reduces this number).
• Cable type: twisted pair cable.
• Max. cable length: 1900 m.

3BDD012902R4101 39
Communication Stack Section 2 Technical Overview FOUNDATION Fieldbus

Communication Stack
Data Link Layer
Three types of devices are defined on the level of the Data Link Layer (DLL):
• Basic device.
• Link Master.
• Bridge.
Link masters are capable of taking over the role of the Link Active Scheduler
(LAS), which basic devices are not able to do. Bridges are used for connecting
individual fieldbuses to larger networks.
The LAS controls data traffic on the FOUNDATION Fieldbus. Therefore the LAS
has a list of the transmission times of all data for cyclic transmission in all devices.
Each time data transmission becomes necessary, the LAS first sends a message to
the device. The device distributes the data using a broadcast on the bus (publisher).
All other devices on the bus can receive this data (subscribers). In addition to this
cyclical data traffic, acyclical data traffic is also possible for reading and writing
parameters.
The LAS maintains a list (the Live List) of all devices present on the bus. New
devices can be added to, and existing devices removed from the bus anytime. If
changes occur the Live List is updated automatically.
The LAS is also responsible for the time synchronization on the fieldbus. Therefore
it periodically broadcasts time distribution messages. It is important that the time is
set exactly the same in all devices, because both the cyclical data traffic and the
cyclical processing of function blocks within the User Application are based on a
common time.

40 3BDD012902R4101
Section 2 Technical Overview FOUNDATION Fieldbus Application Layer

Application Layer
The Fieldbus Access Sublayer (FAS), as a component of the Application Layer,
provides various connection types.
• Publisher/Subscriber: Used for a buffered 1-to-m communication. Buffered
means that only the most recent data is available on the network. New data
overwrites the old data. This connection type is used by the field devices for
the cyclical time-controlled publishing of function block inputs and outputs.
The control loop signals exchanged between the field devices, for example, use
this connection type.
• Client/Server: Used for a user-initiated, non-cyclical 1-to-1 communication
between devices. Typical examples of this connection type are communication
setpoint changes, user acknowledgements of messages and the downloading or
reading back of device configuration data.
• Report Distribution: Used for a user application-initiated, non-cyclical 1-to-n
communication. For example, following a request by the LAS a device with a
configured trend report will send the trend report to the group address defined
for the purpose. Another typical use of this connection type is the sending of
process alarms to the operator consoles.
Fieldbus Message Specification (FMS), as the highest-level component in the
Application Layer, represents the interface to the User Application. The FMS
services allow the User Application to communicate over the fieldbus using a
standard set of message formats. The data items transferred over the fieldbus are
described by object descriptions, which are compiled in an object dictionary (OD).
The Virtual Field Device (VFD) makes the local field device data that is described
in the object dictionary available for communication via the fieldbus. The VFD is
the external view of the local data in a field device.

User Application
Above OSI layer 7 (Application Layer) FF specifies a Standard User Application
based on the concept of function blocks. This allows an automation task to be
distributed to several FF devices. For this purpose, the Standard User Application
defines the Function Block Application Process (FBAP). Using resource blocks
(RB), function blocks (FB) and transducer blocks (TB) the automation task to be

3BDD012902R4101 41
User Application Section 2 Technical Overview FOUNDATION Fieldbus

carried out is described. Additionally, the User Application also defines network
management and system management.
To configure the function block application process, Fieldbus Builder FF uses the
FF Application, which is produced with the help of the FF Application Editor.
Refer to Section 11, FF Application Editor.
• Resource blocks: Describe general features of the device (device name,
manufacturer ID, device type, serial number etc.). There is only one resource
block in a device.
• Function blocks: Provide processing functions (analog input, PID controller,
analog output etc.) within the field devices. Inputs and outputs of function
blocks can be linked via the fieldbus. The time at which each function block is
to be executed is specified exactly.
The Fieldbus Foundation defines the function blocks, known as the FF Standard and
Advanced Function Blocks, shown in Table 1:

Table 1. FF Standard and Advanced Function Blocks

AAL Analog Alarm

AI Analog Input
AO Analog Output
AR Arithmetic Function
BG Bias/Gain
CS Control Selector
DC Device Control
DI Discrete Input
DO Discrete Output
DT Dead Time
IS Input Selector
IT Integrator

42 3BDD012902R4101
Section 2 Technical Overview FOUNDATION Fieldbus User Application

Table 1. FF Standard and Advanced Function Blocks

LL Lead Lag
ML Manual Loader
OS Output Splitter
PD PD Control
PID PID Control
RA Ratio
SC Signal Characterizer
SPG Setpoint Ramp Generator
TMR Timer

• Transducer blocks: Decouple the function blocks from local input/output

functions of the sensor and actuator hardware. They contain, for example,
information on calibration and sensor type. There is normally one transducer
block for each input or output function block.
Additionally, the following objects are defined in the Standard User Application:
• Link objects: Define the links between inputs and outputs of function blocks
both within a field device and via the fieldbus.
• Trend objects: Allow trend values for function block parameters to be logged
locally. Other field devices or host applications can access them.
• Alarm objects: Allow alarms and events to be reported.
• View objects: Pre-defined groupings of function block parameters for use in a
Human System Interface (HSI).
The Standard User Application defines the Virtual Field Device (VFD) as a model
used for describing the data and response of an automation device from the point of
view of a partner in communication. A VFD contains all objects and object
descriptions of a User Application that can be accessed by other bus subscribers.

3BDD012902R4101 43
Network Management Section 2 Technical Overview FOUNDATION Fieldbus

A real FF device contains at least two Virtual Field Devices:

• Function Block Application: Includes the objects and object descriptions in
the User Application that are visible over the bus network. These are
essentially the function blocks and their parameters.
• Management VFD: Includes the corresponding network and system
management objects. The network and system management functions are
described below.

Network Management
FF network management can be subdivided into three areas:
• In the context of configuration management, communication parameters are
initialized and modified.
• Performance management captures data for describing the performance of
device communication.
• Fault management supports fault detection, fault location and fault correction.
The following specific tasks are carried out by network management:
• Loading the list of communication links.
• Configuring the communication stack.
• Loading the LAS.
• Monitoring the performance of device communication.
• Detecting communication errors.
An FF network has at least one network manager, who coordinates the network
management tasks of the whole system. Each field device also has a network
management agent who manages the communication stack within the device. A
network management agent carries out commands issued by the network manager,
and can report events and status changes to the network manager. The network
management objects and object descriptions that are required for data exchange are
contained in the management VFD.

44 3BDD012902R4101
Section 2 Technical Overview FOUNDATION Fieldbus System Management

System Management
System management coordinates the operation of the various field devices in a
distributed fieldbus system.
The following specific tasks are carried out by system management:
• Assignment of the device address.
• Address resolution for user application tags.
• Synchronization of the application time. The application time is the basis for
time-stamping the process values on the device level.
• Time control of a distributed user application across a link.
• Commissioning of a new device on the bus.
• Monitoring of the operation of the entire system.
The system management objects and object descriptions that are required for data
exchange are contained in the management VFD.

Object Dictionary
In order to achieve a standard definition and usage of all the objects of a field device
that are visible through the fieldbus network, descriptions of these objects are
compiled in the object dictionary of the VFD. Each VFD contains exactly one
object dictionary. The object dictionary of the Function Block Application VFD
includes object descriptions of all the function block, resource block and transducer
block parameters of a device. An object description of this type contains, for
example, the specification of data type and length of a parameter.
An object dictionary can be read online from the field device. The manufacturer of
the device also supplies the object dictionaries in a form known as capabilities files
on a data medium (floppy disk, CD-ROM). Fieldbus Builder FF is based on these
capabilities files. The reading of the object dictionaries from the field device is not
supported at present.
There are also the files known as value files. A value file contains information about
the configuration of an individual field device, which can change after the
distribution. Unlike a capabilities file, a value file can be written to. It can be

3BDD012902R4101 45
Device Descriptions Section 2 Technical Overview FOUNDATION Fieldbus

generated by reading the configuration data from the field device. Value files are
not currently supported by Fieldbus Builder FF.

Device Descriptions
Along with the object descriptions, the device descriptions also form an important
supplementary tool for ensuring the interoperability of FF devices. The device
description contains an extended description for each object in the VFD which goes
beyond the content of the object description. The device description includes
information required by an automation system or a host in order to understand the
meaning of the data in the VFD. This information includes, for example, the names
of function block parameters which a host can utilize for the display, or help texts
for the various objects of the device that are visible over the bus network.
The device description is written in a standardized programming language, the
Device Description Language (DDL) and subsequently converted to a machine-
readable form by a program, the Tokenizer. This form of the device description is
referred to as Device Description (DD).
The Fieldbus Foundation provides DDs for the standard function blocks and for
transducer blocks. The device manufacturers supply DDs with their field devices.
These refer to the standard DDs of the Fieldbus Foundation and, where appropriate,
complement them with manufacturer-specific features. The DDs from the device
manufacturers are supplied on data medium (floppy disk, CD-ROM), or may
optionally be read directly from the field device.
Fieldbus Builder FF offers the facility to evaluate DD files from the device
manufacturers. The reading of a DD from the field device is not supported at
present.

46 3BDD012902R4101
 Section 3 Step by Step

Prerequisites and Requirements

The following requirements must be met, in order to be able to carry out the actions
described in this section.
• An 800xA system has been created and started.
• The following system extensions have been added:
– AC 800M/C Connect,
– Fieldbus Builder FF.
– FF Device Integration Library - Basics
• The Plant Explorer Workplace has been started.
• The user has Configure and Download permissions.

Target Group
This section addresses users, who are familiar with FOUNDATION Fieldbus and
are acquainted with the parameter setting of the FF devices used. It describes the
configuration and the commissioning of an FF Application by means of Fieldbus
Builder FF.

Step 1: Synchronize the FF Library

The presence of an FF library is the basis for working with Fieldbus Builder FF. An
FF library is a constituent part of the product FOUNDATION Fieldbus Device
Integration. After initial creation of an 800xA system and after every modification

3BDD012902R4101 47
Step 1: Synchronize the FF Library Section 3 Step by Step

of the FF library the library must be uploaded to PPA. The library is said to be
synchronized then.
To make sure that the FF library is synchronized, change to the Plant Explorer
Workplace Object Type Structure, select the FFUpload Aspect, and open the Library
Upload tab. If the FF library is synchronized already - indicated by a green traffic
light symbol as shown in Figure 2 - proceed with Step 2: Creation of an HSE Subnet
on page 49. If the FF library is not synchronized - indicated by a red traffic light
symbol as shown in Figure 3 - start the FF library upload by means of Upload FF
Library. After the upload has been concluded successfully, the synchronized state
is indicated by a green traffic light (refer to Figure 2).

Figure 2. Upload Successful - FF Library Synchronized

48 3BDD012902R4101
Section 3 Step by Step Step 2: Creation of an HSE Subnet

Figure 3. Upload required

Step 2: Creation of an HSE Subnet

An FF network consists of at least one HSE subnet and any number of H1 links.
HSE linking devices, HSEHostCI860 Devices and OPC Server FF can be connected
to the HSE subnet. HSE linking devices connect the H1 links to the HSE subnet.
The H1 devices are connected to the H1 link. HSEHostCI860 objects are used for
the configuration of the data exchange between the FF Network and an AC 800M
controller. OPC Servers FF are used for communication of 800xA objects with the
FF network.
An HSE subnet is created in the Plant Explorer Control Structure and edited by
means of Fieldbus Builder FF. To create an HSE subnet, select the Root object and
insert a new object with New Object. Select the HSE Subnet object and define a

3BDD012902R4101 49
Step 2: Creation of an HSE Subnet Section 3 Step by Step

name for the object (refer to Figure 4). Insert the object by means of Create. The

Figure 4. Selection of the HSE Subnet

data has already been transferred in the following dialog. Check the settings and

50 3BDD012902R4101
Section 3 Step by Step Step 2: Creation of an HSE Subnet

confirm them with OK (refer to Figure 5).

Figure 5. HSE Subnet Reference

You have thereby created a new HSE subnet for Fieldbus Builder FF. To configure
the HSE subnet the type informations from the FF Library will be used. For this the
data in the FF Library have to be transferred to the HSE Subnet.
A library update is required to transfer the FF devices data from the FF Library to
the HSE subnet.
To do this, select the FFUpload aspect in the newly created HSE Subnet object. Start
the update in the Library Update tab by means of Update Library. The data for the
FF device and block classes contained in the FF Library is transferred to the HSE
Subnet.
Select the FFUpload aspect in the HSE Subnet object. Start the Fieldbus Builder by
means of Open Subnet in Fieldbus Builder FF in the HSE Subnet Reference tab.

3BDD012902R4101 51
Step 2: Creation of an HSE Subnet Section 3 Step by Step

Fieldbus Builder FF starts with an empty HSE subnet. Now configure your desired
FF network by inserting objects in the sub-level from an object by means of Edit >
Insert as per Table 2.

Table 2. Structuring of the FF objects

FF Object FF object types of the subordinate level

FF Network HSE Subnet
OPC Server FF (GWY)
HSE Subnet Linking Device Module
HSE Host CI860 (HSEHostCI860)
HSE Linking Device H1 Link
H1 Link H1 Schedule
H1 Devices
H1 Schedule FF Applic’n (FF Application)

H1 Link and H1 Schedule are always inserted together.

An HSE subnet with all the FF objects listed in Table 2 is shown in the example in
Figure 6.

Figure 6. Example of a Configured H1 Link

After the FF devices have been inserted into the FF Application, their parameters
must be set.

52 3BDD012902R4101
Section 3 Step by Step Step 2: Creation of an HSE Subnet

Define the IP addresses and network settings for all stations in the HSE Subnet:
• HSE Linking Device
Select the HSE linking device object > Edit > Parameters.
• HSEHostCI860 Device
Select the HSEHostCI860 object > Edit > Parameters.
• OPC Server FF
Tools > Network > Select the OPC Server FF and press Edit. Input Resource
ID (as you inserted during installation of the OPC Server FF) and IP address (in
Client Server network) of the PC that runs the OPC Server FF.
Some H1 devices do not display any function blocks after the insertion. These are
H1 devices with instantiable function blocks, into which the required number of
different block types can be inserted. Open the context menu in the graphic view of
the H1 device > Create Function Block. All the available block types are displayed
in the following dialog (refer to Figure 7). Select a block and insert it in the H1
device with Create. The number of created instances is displayed in the Created
Instances column and the available number of function blocks for each type is
displayed in the Available Instances column.

Figure 7. Instantiation of Function Blocks

3BDD012902R4101 53
Step 2: Creation of an HSE Subnet Section 3 Step by Step

It is normally necessary to customize the settings of the H1 Link after the H1

devices have been inserted. To do this, select the H1 Link object and open the
parameter dialog by means of Edit > Parameters. Now press the Proposal button.
The H1 settings of the H1 devices connected to the H1 link are customized by this
means. Close the dialog with OK.
After all the FF objects have been edited, check the whole project for plausibility by
means of Tools > Check whole project. After the logical error checking has been
carried out, the Plausibility Check Error List is displayed. In the list, a
differentiation is made between errors, warnings and information. Errors must be
remedied for a successful plausibility check. The engineering status comprising the
logical error checking status and the commissioning status is indicated in the tree.
Here, stands for a plausible element, for a plausible element which has not yet
been loaded, for a plausible element which has not yet been precommissioned,
for a plausible element for which download information has not yet been
generated, and indicates an element which has not yet been checked for logical
errors or which has an error (refer to Figure 8).

Figure 8. HSE Subnet which has been partially checked for logical errors

After a successful check for plausibility, store the HSE Subnet by means of FF
Object editor > Save and close Fieldbus Builder FF.
Change to the Plant Explorer Workplace Control Structure, select the FFUpload
aspect in the HSE Subnet object and open the HSE Subnet Upload tab. After
changes have been made to the HSE Subnet, HSE Subnet and Upload have different

54 3BDD012902R4101
Section 3 Step by Step Step 3: Configuration of an FF Application

time-stamps. This is also indicated by the red traffic light. Start the HSE Subnet
upload by means of Upload HSE Subnet. After the upload has been concluded,
HSE Subnet and Upload have the same time-stamp. This is indicated by the green
traffic light (refer to Figure 9). The objects configured in Fieldbus Builder FF are
mirrored by the upload to the Control Structure in the Plant Explorer.

Figure 9. Upload of completed HSE Subnet

Step 3: Configuration of an FF Application

FF blocks are linked together in an FF Application, in order to execute the desired
automation function. In the following example, a simple control loop is configured
in FF devices, which is controlled by means of an external set point from the
AC 800M controller.

3BDD012902R4101 55
Step 3: Configuration of an FF Application Section 3 Step by Step

Select an FF Application object in the Plant Explorer Control Structure (refer to

Figure 10).

Figure 10. Selection of the FF Application

Select the FF Management Aspect and start Fieldbus Builder FF with Show Object
in Fieldbus Builder FF (refer to Figure 11).

Figure 11. FF Management Aspect

Fieldbus Builder FF opens the FF Application Editor for the selected object. The
editor starts with an empty canvas. The function blocks are placed on the canvas of
the editor and connected to each other.

56 3BDD012902R4101
Section 3 Step by Step Step 3: Configuration of an FF Application

To insert a function block, switch to Link View in the lower part of the editor. All
the H1 devices of the H1 link are displayed with their function blocks in the Link
View (refer to Figure 12).

Figure 12. Link View

Select a function block and place it on the canvas with the left mouse button held
down. For the example, use an analog input (AI), a controller block (PID) and an
analog output (AO) as shown in Figure 13. After insertion, give the function blocks

Figure 13. Function blocks

a tag name by selecting the function block and opening the parameter dialog by
means of Edit > Parameters. Enter the tag name in the Name field and close the
dialog by means of OK.
FF signals are used for the connection to the AC 800M controller. Insert an FF
signal by means of FF Application > Signal (read) and place it on the canvas (refer

3BDD012902R4101 57
Step 3: Configuration of an FF Application Section 3 Step by Step

to Figure 14). End the insert mode with a right mouse click. Open the signal dialog

Figure 14. FF signals

by double clicking the FF signal frame. Define a name (in the example
FIC1201_SP) for the FF signal. Check the settings in the following dialog
• Data Type: Analog; Discrete or Bitstring,
• Usage: H1 local; HSE + H1 or HSE + H1 (LP), slow cycle
and conclude it with OK. For the example, select the Analog data type and the HSE
+ H1 usage. Insert another FF signal by means of FF Application > Signal (write)
and configure it accordingly.
The data type bitstring is not supported by the HSEHostCI860 object.

Now connect the function blocks and FF signals as shown in Figure 15. To do this,
hold down the CTRL key and drag the connecting lines with the left mouse button
held down.
If the Shift key is pressed in addition to the left mouse button and the CTRL key,
the course of the signal line is automatically defined by Fieldbus Builder FF.

58 3BDD012902R4101
Section 3 Step by Step Step 3: Configuration of an FF Application

Figure 15. FF Application

Please note that the FF PID control loop requires a feedback from the FF AO
block. In the example, the BKCAL_OUT of the FF AO block is fed back to the
BKCAL_IN of the FF PID block. The same applies for the master controller in
the AC 800M controller.
In the example, the external set point from the AC 800M controller is
communicated to the FF block by means of FF signal FIC1201_SP. The FF Signal
FIC1201_BKCAL is used for feedback to the AC 800M controller.
After the function blocks have been inserted into the FF Application, their
parameters must be set. To do this, open the parameter dialog of a function block by

3BDD012902R4101 59
Step 3: Configuration of an FF Application Section 3 Step by Step

double clicking the block in the FF Applic’n object or in the H1 device object (refer
to Figure 16).

Figure 16. Standard Dialog

If block-specific dialogs are in existence, they should be used for the parameter
definition. In principle, check the following parameters during the parameter
definition:
• ALERT_KEY
The value of the ALERT_KEY must be in the range 1 .. 255.
• MODE_BLK
The mode parameter consists of several parts. The Target mode defines the

60 3BDD012902R4101
Section 3 Step by Step Step 3: Configuration of an FF Application

mode of operation which the block should adopt. The modes of operation into
which the block can be switched via the Target mode are specified by means of
the Permitted Mode. The Actual mode shows the current mode of the block.
The following modes of operation should be set for the block types (refer to
Table 3).

Table 3. Recommended modes of operation for FF blocks

Block type Recommended mode of operation

Resource Block Auto
Transducer Block Auto
Analog input (AI) Auto
PID Controller Block Man, Auto or Cas(1)
Analog Output (AO) Cas
(1) Dependent on the functionality of the controller.

For the Cascade mode, Auto and Cas are to be set in the target mode at the same
time.
• Scaling
Customize the scaling of the individual blocks to the requirements of your
process.
It is not required to fill in all parameters initially in the parameter dialog of a
function block. Fields may be left blank to maintain parameters as they are in the
device initially.
The HSEHostCI860 object must be configured for data exchange with the AC 800M
controller. An FF host can access all FF signals which were defined by the
HSE + H1 usage. Select the HSEHostCI860 object and open the parameter dialog
with Edit > Parameters. Select the Published/Subscribed tab. Insert a new channel
via the context menu by means of Create Component. Define
• Data type: Analog (DS-65) or Discrete (DS-66) and
• Direction: FF -> IEC61131 - from the FF device to the AC 800M or IEC61131
-> FF - in the opposite direction

3BDD012902R4101 61
Step 3: Configuration of an FF Application Section 3 Step by Step

for the channel. Select the FF signal field and open the Signal Selection Dialog by
means of the F2 key. Select the desired FF signal and transfer it to the
HSEHostCI860 object by means of OK. The configuration of the HSEHostCI860
object for the above example can be seen in Figure 17. Repeat this for all FF signals

Figure 17. Example of an HSEHostCI860 configuration

which you wish to use in programs in the AC 800M controller. The thus defined
channels of the CI860 module can be assigned with I/O variables in Control
Builder M.
A schedule which includes the time sequence of the function blocks and
communications from FF signals is automatically generated on storage of the FF
Applic’n object. The contents of the schedule are based on the created FF
Application and the performance specifications of the H1 devices used. To display,

62 3BDD012902R4101
Section 3 Step by Step Step 4: Loading of the FF Application

select the H1 Schedule object (refer to Figure 18). For experienced users, there is
the possibility of moving the individual blocks in the schedule manually.

Figure 18. Example of a schedule

After the FF Applications have been created, check the whole project for
plausibility by means of Tools > Check whole project and correct any errors which
occurred. After a successful check for plausibility, store the HSE subnet by means
of FF Object editor > Save and close Fieldbus Builder FF.
Change to the Plant Explorer Workplace Control Structure. Select the FFUpload
Aspect in the HSE Subnet object and open the HSE Subnet Upload tab. After
changes have been made to the HSE Subnet, HSE Subnet and Upload have different
time-stamps. Start the HSE Subnet upload by means of Upload HSE Subnet. After
the upload has been concluded, HSE Subnet and Upload have the same time-stamp.
The configuration of the FF network with the FF Application has now been
completed. The configured data must now be distributed to the connected devices.

Step 4: Loading of the FF Application

Once it has been loaded, the data of the FF Application is distributed over the FF
network.
The FF Application is loaded in two steps. In the first step, the precommissioning, a
device assignment between the configured devices and the devices which are
actually present is carried out. Basic settings are written to the devices.

3BDD012902R4101 63
Step 4a: Precommissioning Section 3 Step by Step

In the second step, the commissioning, the data of the FF Application is loaded into
the individual devices.

Step 4a: Precommissioning

The precommissioning is different for linking devices and H1 devices.
During the precommissioning of a linking device the tag name is written and the
configured H1 links are activated. For H1 devices, the tag name is written to the
device and the bus address set. The device ID is read out of the device and stored in
the Fieldbus Builder FF database. As a result, the device can subsequently be
detected. The configured blocks are loaded into H1 devices with instantiable
function blocks.

Precommissioning of a Linking Device

For the precommissioning, select a linking device object in the Plant Explorer
Workplace Control Structure. Select the FF Management Aspect and start Fieldbus
Builder FF with Show Object in Fieldbus Builder FF.
Switch Fieldbus Builder FF into the commissioning mode by means of FF Object
editor > Commissioning. Status information for the individual objects is displayed
in the commissioning mode.
Open the Write Linking Device Settings dialog by means of Object > Linking
device initialization and address assignment... and start the precommissioning of
the linking device by means of Start (refer to Figure 19).
It is recommended to execute the function Linking device initialization and
address assignment only for initial precommissioning of a newly inserted
linking device, as executing this function on an operating linking device stops all
HSE republishing and cyclical communication on all H1 links of that linking
device as well as client/server communication to the linking device and the
devices on the H1 links. Please refer to Precommissioning of Linking Devices on
page 376 for details.

64 3BDD012902R4101
Section 3 Step by Step Step 4a: Precommissioning

Figure 19. Precommissioning of Linking Device Successfully Concluded

Precommissioning of H1 Devices
After the linking device settings have been successfully written, select an H1 link of
the linking device.

3BDD012902R4101 65
Step 4a: Precommissioning Section 3 Step by Step

Open the Live List by means of Object > Live list.... The live list is divided into two
sections (refer to Figure 20). The H1 devices actually present in the H1 link are

Figure 20. Device Assignment

listed in the left-hand section. The right-hand section contains a list of the
configured H1 devices. Select an actual H1 device in the left-hand section and use
the mouse to drag it to the configured H1 device in the right-hand section which
contains the configured data for the actual H1 device.
The tag name is written to the H1 device and the bus address of the H1 device set
during the device assignment. The device ID is read out of the H1 device and stored
in the Fieldbus Builder FF database.
You can also carry out the device assignment by selecting an H1 device and
opening the H1 Live List by means of Object > Assign device.... Select the H1
device to be assigned from the list and start the device assignment with Assign.

66 3BDD012902R4101
Section 3 Step by Step Step 4b: Commissioning

Repeat this process for all H1 devices in the H1 link and for further H1 links and
linking devices if required.
In the case of a device type with several revisions in the same plant, the device
assignment has to be started via the context menu of the device instance. Refer to
Assignment of a Single H1 Device on page 359 for a description of this dialog.

Step 4b: Commissioning

After all the requisite FF devices have been assigned, the FF Application can be
loaded into the individual FF devices.
Select the HSE Subnet and open the download dialog with Object > Download...
(refer to Figure 21).

Figure 21. Download Dialog

3BDD012902R4101 67
Step 4b: Commissioning Section 3 Step by Step

After the on-line version check has completed, the commissioning status displayed
in the tree structure of the download dialog indicates, which objects will be loaded.
Refer to Table 4 for the meaning of the different symbols.

Table 4. Commissioning Status

• Version check has not yet been carried out for this object.

• The object will not be loaded. The loaded configuration data are
current.
• In case of a collapsed branch below this object, none of the objects in
the collapsed branch will be loaded. The loaded configuration data for
these objects are current.
• Loading is necessary for at least one object in the collapsed branch.
• Specific commissioning statuses for the object and all objects in the
collapsed branch can be displayed by expanding the branch.
• Only changed configuration data are loaded into the object
(incremental download).
• Only changed configuration data are loaded into the object
(incremental download).
• For an H1 link: The link active scheduler (LAS) is stopped during the
download, i.e. the application is interrupted.
• For an H1 device: The resource block is stopped. As a result, all of the
blocks in the device switch to Out of Service mode.
• The object is loaded with all configuration data (full download).

• The object is loaded with all configuration data (full download).

• For an H1 link: The link active scheduler (LAS) is stopped during the
download, i.e. the application is interrupted.
• For an H1 device: The resource block is stopped. As a result, all of the
blocks in the device switch to Out of Service mode.
• Although configuration of the block (i. e. block parameters) has
changed, block parameters are not loaded because the download
option Load changed block parameters is not selected.

68 3BDD012902R4101
Section 3 Step by Step Step 4b: Commissioning

Table 4. Commissioning Status

• The physical device cannot be reached on the bus.

• Precommissioning action is required for the object. Details should be

taken from the text in the download tree.

The default setting for the download options - none of the download options
selected - will result in an incremental download without stopping LAS or H1 link
and not changing parameter settings as they are in the devices unless the
configuration changes made have such an impact on the link and function block
application that they can only be loaded with briefly interrupting the application.
Necessary interrupts are indicated as described above.
It is strongly recommended to keep the download options with the default
settings. The non-default options are only intended for users with in-depth FF
knowledge capable of judging the impact of the different options depending on
the respective status the application is in.
Start the download by means of Start Download. In a separate window the progress
of the loading operation and any errors that may occur are displayed (refer to
Figure 22). All the configured data is loaded to the H1 devices and the linking
device during the download. After successful completion of the download, indicated

3BDD012902R4101 69
Step 4b: Commissioning Section 3 Step by Step

by the text “Total error count: 0; Download finished”, press the Close button to
close the progress windows as well as the download dialog.

Figure 22. Load Parameters

To load the OPC server, select the OPC Server FF object and start the download
with Object > Download.... The settings for the OPC Server FF are loaded into the
latter by this means.
After the FF Application and the OPC Server FF have been successfully
downloaded, online data are available from the devices.

70 3BDD012902R4101
Section 3 Step by Step Step 4b: Commissioning

Select an FF Applic’n object. If the mouse cursor is held down on a block pin or an
FF signal line, the current values are displayed (refer to Figure 23).

Figure 23. Online data

3BDD012902R4101 71
Step 4b: Commissioning Section 3 Step by Step

Online data for the block parameters is also displayed in the commissioning mode.
To do this, open the parameter dialog of a function block by double clicking the
block in the FF Applic’n object or in the H1 device object (refer to Figure 24).

Figure 24. Online parameters

The yellow background of individual values indicates a difference between the real
value in the H1 device and the configured value in the Fieldbus Builder FF database.
For the commissioning of your FF Application, compare the Actual and Target
mode of the individual blocks. Actual and Target mode can differ from each
other, dependent on the signal statuses at the inputs of a block.
In this case, check the cause, e.g. a sensor not connected to the device.

72 3BDD012902R4101
Section 3 Step by Step Step 5: Using FF Data in Controller Application and Operations

Values of individual parameters can be changed by changing the value in the value
field. The button bar is toggled as a result. The new value is written to the H1 device
by means of Write and the value is written to the H1 device and the Fieldbus
Builder FF database by means of Correct.
Current values in the H1 device which are not in the Fieldbus Builder FF database
(highlighted with yellow background) can be loaded into the database. For this,
mark one or more lines in the parameter dialog. Open the context menu and start the
transfer of the data by means of Upload marked.

Step 5: Using FF Data in Controller Application and

Operations
For use in the AC 800M
To transfer FF signals entered in the HSEHostCI860 object in Fieldbus Builder FF,
this object needs to be assigned to the appropriate CI860 Hardware object as created
with Control Builder M.
In this connection, define the requisite hardware in a Control Network in the Plant
Explorer Workplace Control Structure. Follow the appropriate manual. Select a
CI860 object and insert an object with Insert Object. Select the HSEHostCI860

3BDD012902R4101 73
Step 5: Using FF Data in Controller Application and Operations Section 3 Step by Step

object in an HSE subnet in the following dialog and confirm the insertion with
Insert (refer to Figure 25).

Figure 25. Insertion of an HSEHostCI860 object

Figure 26 shows the inserted HSEHostCI860 object.

Figure 26. Example of an HSEHostCI860 object in a control network

74 3BDD012902R4101
Section 3 Step by Step For use in Operations and Asset Optimization

Select the CI860 object in the Control Structure and change to Control Builder M.
Open the hardware editor via the context menu by means of Editor (see Figure 27).

Figure 27. Hardware editor of the CI860 object

The FF signals assigned in Fieldbus Builder FF are displayed in the Connections tab
in the Protocol Info column. I/O variables which can be used in the programs and
control modules of Control Builder M can be assigned to the channels in the
Variable column.

For use in Operations and Asset Optimization

After upload of the FF configuration and download of the FF devices and the
OPC Server FF, online data from the FF devices are available in the block objects in
Plant Explorer. Prerequisites are the specification of the OPC Access for the
respective classes in Fieldbus Builder FF and the correct configuration of the OPC
Data Source Definition aspect at the HSE Subnet object in the Control Structure of
Plant Explorer.
Close Fieldbus Builder FF before uploading the HSE Subnet configuration to
Plant Explorer.
The data for the FF objects is available in the Control Connection Aspect. Graphics,
faceplates, trends, archives, among others, can access this data. Please use the
respective manuals to configure these applications.

3BDD012902R4101 75
For use in Operations and Asset Optimization Section 3 Step by Step

76 3BDD012902R4101
 Section 4 Integration in Plant Explorer

Basic Principles of the Integration in Plant Explorer

The correlations indicated in the following are described to promote the
understanding of individual processing sequences for the configuration of an HSE
subnet. The complete workflow for the configuration of an HSE subnet is not
described here. You will find this in Section 3, Step by Step.
The configuration of an HSE subnet typically begins in Plant Explorer with the
insertion of an HSE Subnet object in the Control Structure. Further configuration of
the HSE subnet is done in the Fieldbus Builder FF. After the configuration data of
the HSE Subnet has been uploaded to the Plant Explorer Workplace, the configured
objects appear in the Control Structure.
The Fieldbus Builder FF is switched to from the Object Type Structure in order to
edit the libraries. The editing of the libraries, e.g. the import of a new device or the
change of block class parameters, is executed in Fieldbus Builder FF. After the
changed library contents have been uploaded to the Plant Explorer Workplace, the
changes appear in the Object Type Structure.
If the 800xA system includes several HSE subnets, these are configured by various
instances of Fieldbus Builder FF. All Fieldbus Builder FF instances and the Plant
Explorer Workplace work with the same FF libraries.
Before editing an HSE subnet in Fieldbus Builder FF, it must be ensured that the
latest library data is used. In this connection, a library update may be required. This
is initiated in the FF Upload Aspect of the HSE Subnet object.

3BDD012902R4101 77
 Section 4 Integration in Plant Explorer

Figure 28 shows the processing steps listed in Table 5 by means of which the library
and configuration data is synchronized in Process Portal A (PPA) / the Plant
Explorer Workplace and the Fieldbus Builder FF instances.

Plant Explorer Fieldbus Builder FF

Object Type Structure

Object Types
A
FF Libraries FF Libraries
Upload
FF HSE Device Library FF HSE Device Library
FF H1 Device Library
ABB
FF H1 Device Library
ABB
FF Libraries
ABB 600T ABB 600T
FF Block Library B1 FF Block Library
ce

Lib
rary
feren

Upd
ate
ct Re

Control Structure
Root
C1 FF Network
Obje

HSE Subnet HSE Subnet

ABB LD800HSE Upload ABB LD800HSE
H1 Link H1 Link HSE Subnet 1
H1 Schedule H1 Schedule
FF Application FF Application
ABB 600T ABB 600T
Lib

Bn
ra
ry
U
pd
ate

HSE Subnet
Cn FF Network
HSE Subnet
ABB LD800HSE ABB LD800HSE
Upload
H1 Link H1 Link HSE Subnet n
H1 Schedule H1 Schedule
FF Application FF Application
ABB 600T ABB 600T

Figure 28. Synchronization of the FF Libraries and HSE Subnets

78 3BDD012902R4101
Section 4 Integration in Plant Explorer

Table 5. Upload and Library Update

Step Description
Uploading of FF libraries to the Plant Explorer Workplace:
• Required: after editing the FF libraries in Fieldbus Builder FF.
• Prerequisite: a successful plausibility check has been executed
and the FF libraries saved after editing in Fieldbus Builder FF.
A
• Call: Object Type Structure > FF Libraries > Aspect: FF Upload
> Tab: Library Upload, refer to Upload FF Libraries to the Plant
Explorer Workplace on page 82.
• Final state: FF libraries have been synchronized.
Update FF libraries for HSE Subnet [i] (Library Update):
• Required: before editing HSE Subnet [i] in Fieldbus Builder FF
if the FF libraries have been edited after the last library update.
• Prerequisite: FF libraries in the Plant Explorer Workplace have
been synchronized.
B1..n
• Call: Control Structure > HSE Subnet [i] > Aspect: FF Upload >
Tab: Library Update, refer to Update FF Libraries for the HSE
Subnet (Library Update) on page 84.
• Final state: FF libraries for HSE Subnet [i] have been
synchronized.
Uploading HSE Subnet [i] to the Plant Explorer Workplace:
• Required: after HSE Subnet [i] has been edited in Fieldbus
Builder FF.
• Prerequisite: a successful plausibility check has been executed
and the changes saved after HSE Subnet [i] was edited in
C1..n
Fieldbus Builder FF.
• Call: Control Structure > HSE Subnet [i] > Aspect: FF Upload >
Tab: HSE Subnet Upload, refer to Upload HSE Subnet to the
Plant Explorer Workplace on page 85.
• Final state: HSE Subnet [i] has been synchronized.

The following typical workflow results:

1. Edit FF libraries in Fieldbus Builder FF.

3BDD012902R4101 79
Object Types in Plant Explorer Section 4 Integration in Plant Explorer

2. Upload FF libraries to the the Plant Explorer Workplace; step A.

3. Create HSE Subnet [i] in the Plant Explorer Workplace.
4. Update FF libraries for HSE Subnet [i] (Library Update); step Bi.
5. Configure HSE Subnet [i] in Fieldbus Builder FF.
6. Upload HSE subnet [i] to the Plant Explorer Workplace; step Ci.

Object Types in Plant Explorer

Additional object types which allow the configuration of FF networks are made
available to the Plant Explorer Workplace by the Fieldbus Builder FF system
extension. These object types are combined in the Object Type Structure of the Plant
Explorer under the object type group FF libraries. Refer to Figure 29.

Figure 29. Object Type Group FF Libraries

The new object types represent the FF libraries FF H1 and FF HSE device library,
FF block library with its devices and block classes as well as the basic objects used
in Fieldbus Builder FF for the configuration of an HSE subnet.

80 3BDD012902R4101
Section 4 Integration in Plant Explorer H1 and HSE Device Library

H1 and HSE Device Library

The structure of the FF device libraries in the Object Type Structure of the Plant
Explorer corresponds to the structure of these libraries in Fieldbus Builder FF. Refer
to H1 Device Library on page 163 and HSE Device Library on page 164.

FF Block Library
The structure of the FF block library in the Object Type Structure of the Plant
Explorer essentially differs from the structure of this library in Fieldbus Builder FF
in one point. In the Plant Explorer, an object type group for the function block type,
under which both the corresponding standard function block type and the vendor-
specific function block types are arranged, takes the place of a standard function
block in the block library of the Fieldbus Builder FF. For further details refer to
Block Library on page 162.

Edit FF Libraries
The following requirements must have been met to be able to carry out the work
steps for editing the FF libraries described in this section:
• An 800xA system has been created and started.
• The system extension Fieldbus Builder FF has been inserted.
These work steps, which are described in detail in the following, are to be carried
out:
1. Edit FF libraries in Fieldbus Builder FF.
2. Upload FF libraries to the Plant Explorer Workplace.

Edit FF Libraries in Fieldbus Builder FF

Switch to Fieldbus Builder FF to edit the FF libraries, carry out the required
processing steps there, check the FF libraries for logical errors and save:
1. Object Type Structure > FF Libraries Object Type Group
2. Aspect: FF Upload > Tab: Library Reference
3. Open Library in Fieldbus Builder FF

3BDD012902R4101 81
Upload FF Libraries to the Plant Explorer Workplace Section 4 Integration in Plant Explorer

4. Carry out the required processing steps in the FF libraries in Fieldbus Builder
FF; refer to FF Libraries on page 161.
5. Check the libraries for plausibility and store in Fieldbus Builder FF.
6. Exit Fieldbus Builder FF.

Upload FF Libraries to the Plant Explorer Workplace

1. Object Type Structure > FF Libraries Object Type Group
2. Aspect: FF Upload > Tab: Library Upload
3. Upload FF Library
After a successful upload, the green traffic light symbol indicates that the FF
libraries have been synchronized.

Configure HSE Subnet

The following requirements must have been met to be able to carry out the work
steps for the configuration of an HSE subnet described in this section:
• An 800xA system has been created and started.
• The system extension Fieldbus Builder FF has been inserted.
• The FF libraries have been synchronized; refer to Edit FF Libraries on page 81.
These work steps, which are described in detail in the following, are to be carried
out:
1. Create HSE Subnet in the Plant Explorer Workplace.
2. Update FF libraries for the HSE Subnet (Library Update).
3. Configure HSE Subnet in Fieldbus Builder FF.
4. Upload HSE Subnet to the Plant Explorer Workplace.

Create HSE Subnet in the Plant Explorer Workplace

1. Control Structure > Context menu of the root object > New Object...
2. Select the object type HSE Subnet, refer to Figure 30.

82 3BDD012902R4101
Section 4 Integration in Plant Explorer Create HSE Subnet in the Plant Explorer Workplace

Figure 30. Create a New HSE Subnet Object

3. Enter the name of the HSE Subnet object, refer to Figure 31.

3BDD012902R4101 83
Update FF Libraries for the HSE Subnet (Library Update) Section 4 Integration in Plant Explorer

Figure 31. FF HSE Subnet Reference

4. Create
5. Enter the name of the HSE Subnet reference or use the default name > OK

The name of the HSE Subnet reference should be identical with the name of the
HSE Subnet object. The name assigned to the HSE Subnet reference during
creation of the HSE Subnet should be subsequently changed only by experienced
users.

Update FF Libraries for the HSE Subnet (Library Update)

1. Control Structure > HSE Subnet object > Aspect: FF Upload
2. Tab: Library Update; refer to Library Update Tab on page 91.
3. Update Library

84 3BDD012902R4101
Section 4 Integration in Plant Explorer Configure HSE Subnet in Fieldbus Builder FF

After a successful library update, the green traffic light symbol indicates that the FF
libraries for this subnet have been synchronized.

Configure HSE Subnet in Fieldbus Builder FF

Switch to Fieldbus Builder FF for configuration of the HSE Subnet (refer to
Section 6, Configuring an FF Network), carry out the required configuration there,
check this for logical errors and store:
1. Control Structure > HSE Subnet object > Aspect: FF Upload
2. Tab: HSE Subnet Reference
3. Open Subnet in Fieldbus Builder FF
4. Configure the HSE Subnet in Fieldbus Builder FF; refer to Section 6,
Configuring an FF Network.
5. Check for plausibility and save the configuration in Fieldbus Builder FF.
6. Exit Fieldbus Builder FF.

Upload HSE Subnet to the Plant Explorer Workplace

1. Control Structure > HSE Subnet object > Aspect: FF Upload
2. Tab: HSE Subnet Upload
3. Upload HSE Subnet
After a successful upload, the green traffic light symbol indicates that the HSE
Subnet has been synchronized. In the Control Structure, the objects of the HSE
subnet configured in Fieldbus Builder FF appear below the HSE Subnet object.
Refer to Figure 32. The hierarchical arrangement of the FF objects in the Control
Structure corresponds to the arrangement in the FF Object Editor structure of
Fieldbus Builder FF. The FF blocks are also displayed in the Control Structure. In
this connection, a block is displayed at two points in the Control Structure:
• below the H1 Device and
• below the FF Application.

3BDD012902R4101 85
Navigation Section 4 Integration in Plant Explorer

Figure 32. HSE Subnet in the Control Structure

Navigation
The various possibilities for navigation between the Plant Explorer Workplace and
Fieldbus Builder FF are presented in the following.

Navigating to the FF Libraries

Proceeding from the Object Type Structure in the Plant Explorer Workplace,
navigate to the FF Libraries in Fieldbus Builder FF:

86 3BDD012902R4101
Section 4 Integration in Plant Explorer Navigating to the HSE Subnet

1. Object Type Structure > FF Libraries, Object Type Group

2. Aspect: FF Upload > Tab: Library Reference, refer to HSE Subnet Reference
Tab on page 90.
3. Open Library in Fieldbus Builder FF
You return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

Navigating to the HSE Subnet

Proceeding from the Control Structure in the Plant Explorer Workplace, navigate to
the HSE Subnet in Fieldbus Builder FF:
1. Control Structure > Select HSE Subnet object > Aspect: FF Upload
2. Tab: HSE Subnet Reference, refer to HSE Subnet Reference Tab on page 90.
3. Open Subnet in Fieldbus Builder FF
You return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

Navigating to a Selected FF Instance Object

Navigate from a selected FF object in the Control Structure of Plant Explorer
Workplace to this object in Fieldbus Builder FF:
1. Control Structure > Select FF object > Aspect: FF Management, refer to FF
Management on page 89.
2. Show Object in Fieldbus Builder FF
You return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

Aspects of Fieldbus Builder FF in the Plant Explorer

Table 6 shows the aspects made available in the Plant Explorer Workplace by the
system extension Fieldbus Builder FF and the objects in the Control Structure in

3BDD012902R4101 87
Aspects of Fieldbus Builder FF in the Plant Explorer Section 4 Integration in Plant Explorer

which these aspects are present. These aspects are presented in the following
sections.

Table 6. Aspects of Fieldbus Builder FF

Aspects of Fieldbus Builder FF

OPC Data Source Definition

Control Connection
FF Management

FF Device Info
FF Upload

HSE Subnet X X X
HSE Device X X X
(ABB LD800HSE)
H1 Link X X
H1 Schedule X
FF Application X
FF Block X X
H1 Device X X X
HSE Host CI860 X

88 3BDD012902R4101
Section 4 Integration in Plant Explorer FF Management

FF Management

Figure 33. FF Management Aspect

All FF objects in the Control Structure have the FF Management aspect. This aspect
allows direct navigation to the respective object in Fieldbus Builder FF. Refer to
Figure 33.

FF Upload
The aspect is based on the HSE Subnet object in the Control Structure for the
following description of the tabs of the FF Upload aspect.
The FF libraries object type group also has an FF Upload aspect. Here the data
applies in a general sense. Refer to Upload FF Libraries to the Plant Explorer
Workplace on page 82 for the use of the FF Upload aspect for FF libraries.

3BDD012902R4101 89
FF Upload Section 4 Integration in Plant Explorer

HSE Subnet Reference Tab

This tab allows navigation to this HSE Subnet in Fieldbus Builder FF. It furthermore
shows the HSE Subnet reference and the synchronization status of the HSE Subnet
comprising configuration data and libraries. Refer to Figure 34 and Table 7.

Figure 34. HSE Subnet Reference Tab

Table 7. HSE Subnet Reference Tab

Dialog element Description

Open Subnet in This HSE Subnet is branched to in Fieldbus Builder FF;
Fieldbus Builder FF refer to Navigating to the HSE Subnet on page 87.
Modify The name of the HSE Subnet reference is changed.

The name of the HSE Subnet reference should be identical with the name of the
HSE Subnet object. The name assigned to the HSE Subnet reference during
creation of the HSE Subnet should be subsequently changed only by experienced
users.

90 3BDD012902R4101
Section 4 Integration in Plant Explorer FF Upload

Library Update Tab

This tab shows the synchronization status of the FF libraries for the HSE Subnet.
Refer to Figure 35 and Table 8.

Figure 35. Library Update Tab

Table 8. Library Update Tab

Dialog element Description

Update Library The FF libraries for the HSE Subnet are updated. Refer
to Update FF Libraries for the HSE Subnet (Library
Update) on page 84 and Basic Principles of the
Integration in Plant Explorer on page 77.

A red traffic light symbol indicates that the FF libraries for this HSE Subnet have
not been synchronized. The information text states the steps required to reach the
synchronized status.

3BDD012902R4101 91
FF Upload Section 4 Integration in Plant Explorer

HSE Subnet Upload Tab

This tab shows the synchronization status of the HSE Subnet. Refer to Figure 36
and Table 9.

Figure 36. HSE Subnet Upload Tab

Table 9. HSE Subnet Upload Tab

Dialog element Description

Upload HSE Subnet The HSE subnet is synchronized. Refer to Upload HSE
Subnet to the Plant Explorer Workplace on page 85 and
Basic Principles of the Integration in Plant Explorer on
page 77.

Upload Logger Tab

This tab shows the actions logged during the upload. Refer to Figure 37.
If an HSE subnet upload fails, you will find details here.

92 3BDD012902R4101
Section 4 Integration in Plant Explorer FF Device Info

Figure 37. Upload Logger Tab

FF Device Info
FF Device Info aspect shows data of the FF device, e.g. Manufaturer ID, Device
Type ID, DD Revision and Device Revision. The data are registered with the Upload
into the aspect.

OPC Data Source Definition

During upload of the HSE Subnet to Plant Explorer, the configured OPC Server FF
is inserted into the Plant Explorer Service Structure:
Service Structure > OpcDA_Connector, Service > HSE Subnet-
<subnet_name>, Service Group > HSE ServiceProvider-<subnet_name>,
Service Provider
In case of redundant OPC Servers FF, two Service Providers are listed beneath the
Service Group.
Subsequently the uploader inserts the reference to the OPC Server FF in the Plant
Explorer Service Structure into the OPC Data Source Definition aspect of the HSE
Subnet in the Control Structure. These data are shown in the Connectivity tab and
the OPC Configuration tab of the OPC Data Source Definition aspect. With the link

3BDD012902R4101 93
OPC Data Source Definition Section 4 Integration in Plant Explorer

of an OPC Server FF to an HSE Subnet, on-line data from FF devices in the HSE
Subnet are accessible by Plant Explorer.
In case of redundant OPC Servers FF do not allow both OPC servers to work in
parallel in order not to overload the H1 links, as these have only a restricted
bandwidth. For these purposes uncheck the checkbox Allow parallel
redundancy in the Special Configuration tab of the Service Group:
• Service Structure > OpcDA_Connector, Service > HSE Subnet-
<subnet_name>, Service Group > Service Group Definition aspect > Special
Configuration tab
• Uncheck Allow parallel redundancy checkbox.
For the change to take effect, it is necessary to restart the HSE Service Provider:
• Service Structure > OpcDA_Connector, Service > HSE Subnet-
<subnet_name>, Service Group > HSE Service Provider-<subnet_name>,
Service Provider> Service Provider Definition aspect > Configuration tab
• Uncheck Enabled checkbox and press Apply
• Check Enabled checkbox and press Apply
• Verify that the Current state returns to Service.
Furthermore configure affinitiy for all services which use the OPC Server FF in a
way that ensures, that all clients predictively select the same Connectivity
Server node as provider (from a pair of redundant Connectivity Server nodes
running OPC Server FF). For details on configuration of affinity refer to 800xA -
System, Post Installation Setup (3BUA000156R4101).
It is recommended not to disable the OpcDA_Connector service for the HSE
subnet. Disabling this service may interrupt communication between Fieldbus
Builder FF and the HSE subnet.

94 3BDD012902R4101
Section 4 Integration in Plant Explorer Control Connection

Control Connection

Figure 38. Property View Tab

All FF blocks and hardware objects are transferred to Plant Explorer by uploading
the HSE Subnet.
In the Control Connection aspect of each object, all parameters whose values can be
accessed via the OPC Server are listed in the Property View tab. Refer to Figure 38.
• For the FF blocks, these are all the parameters, for which the OPC access was
configured in the associated object class. The online data of these parameters
can be accessed via the OPC Server of the field instruments.
• The pre-defined OPC items are listed for the instances of the object types HSE
Linking Device, H1 Link and H1 Device. The values of these parameters can
be read via the OPC Server.
For defining OPC Items refer to Enabling Parameters of the FF Blocks for OPC
Access on page 261.
Other aspects, e.g. the Faceplate aspect, can access data of the FF devices via these
Control Connection aspects.

3BDD012902R4101 95
Audit Trail Section 4 Integration in Plant Explorer

Audit Trail
Fieldbus Builder FF generates messages which can be logged in the Audit Trail Log
for the following events:
• Saving the project
• Changing the operating mode
• Start Download
• Abortion of the download by the user
• Ending the download
• Error or information during download
• Writing or correcting online parameters
• Too little space on the storage medium for application data
• General events
To record the messages generated by Fieldbus Builder FF in the Audit Trail Log,
enable Audit Trail in the Plant Explorer and select the following Audit Event
classes:
• AuditEvent_System
• AuditEvent_ConfigurationChanged
• AuditEvent_OperatorAction.

Security Definition
Various privileges (Permissions) are required in the Plant Explorer Workplace for
working in the configuration and commissioning operating modes of Fieldbus
Builder FF. Refer to Table 10.

Table 10. Requisite Privileges for the Operating Modes of Fieldbus Builder FF

Operating mode of FBB FF Requisite privilege in Plant Explorer

Configuration Configure
Commissioning Download

96 3BDD012902R4101
Section 4 Integration in Plant Explorer Advanced Management of FF Libraries

Advanced Management of FF Libraries

FF Library Merge
In general a merge of two FF libraries is performed when executing one of the
following actions:
• Import FF Library from another system into an existing system.
• Import HSE Subnet from another system into an existing system.
• Add FF Device Integration Library to default and user FF library.
• System synchronization.
This section describes the underlying mechanisms for an FF library merge,
considering as example the import of an HSE Subnet from another system.
You will find these basic principles of an FF library merge:
• On import of FF object types the imported FF object types will finally
overwrite the existing ones.
• There is a certain step in the workflow where aspects of the existing FF object
types can be preserved.

3BDD012902R4101 97
FF Library Merge Section 4 Integration in Plant Explorer

Example Workflow: Import HSE Subnet from another System

For importing an HSE Subnet from another system to the current system, carry out
the following steps. Refer to Figure 39.

Figure 39. Import HSE Subnet from another System

• Step 1: Export an HSE Subnet with dependencies (this includes the FF Library)
from the source system (System 2).
• Step 2: Import the AFW file to the target system (System 1).
• Step 3: Run Upload FF Library to move duplicate object types to the
duplicate structure.
• Step 4: Move additional aspects from the object types in the duplicate folder to
the corresponding object types in the FF device type folder.
• Step 5: Run Update Library on all HSE Subnets.
• Step 6: Run Upload HSE Subnet on all HSE Subnets.

98 3BDD012902R4101
Section 4 Integration in Plant Explorer System Backup and Import/Export

The FF library merge is completed, when the FF Library is uploaded, all HSE
Subnet library information is updated, and all HSE Subnets are uploaded.

Explanation to the Example Workflow

• System 1 and System 2 contain a common device type X created each by
separate CFF import.
• HSE Subnet export out of System 2 (refer to Step 1) takes also FF object type
information.
• Import into System 1 (refer to Step 2) creates duplicate FF object type X, also
located in the FF device type folder.
• Duringe the next FF Library upload (refer to Step 3) , duplicate FF object types
are moved to the duplicate folder. Thereby the existing FF object type in the
system with its aspects is moved to the duplicate folder, whereas the imported
FF object type with its aspects stays in FF device type folder.
• Now the user can move the additional aspects from the FF object type X in the
duplicate folder onto the FF object type X in the FF device type folder to
preserve these aspects (refer to Step 4).
• During the next HSE Subnet upload (refer to Step 6), that is performed after the
FF Library update, the object type of the instance is changed from that in the
duplicate folder to that in the FF device type folder.
• During the next FF Library upload further unused FF object types from the
duplicate folder are removed.

System Backup and Import/Export

Using the system’s Backup or Import/Export function it is strongly recommended to
close all Fieldbus Builder FF instances in the system when running a backup or
performing an import/export.

3BDD012902R4101 99
System Backup and Import/Export Section 4 Integration in Plant Explorer

100 3BDD012902R4101
 Section 5 System Configuration

General Instructions
In a Fieldbus Builder FF project, precisely one HSE subnet can be configured.
Configuration can be done offline, i. e. no HSE or H1 devices need to be physically
connected. During system configuration the structure of the hardware used (H1 and
HSE devices as well as OPC Gateway Stations) is set up and the functionality of the
application configured. In a subsequent commissioning phase, configuration data is
loaded into the devices and stations.
One system of the 800xA System can contain several HSE subnets. In this case,
several Fieldbus Builder FF projects are combined in the system of the 800xA
System. Each of the HSE subnets is configured in its own Fieldbus Builder FF
project and commissioned.
All operations in the Fieldbus Builder FF can be performed both with the mouse and
with the keyboard. For operation with the mouse, the most important and most
frequently used functions are also available via toolbars and context menus. Both
the buttons of the toolbar and the contents of the context menus depend on the
current editing status of the project.
With the buttons of the toolbar, general, i.e. cross-object functions are triggered, the
functions of the context menu refer to the object currently being edited. Context
menus are called up with the right mouse button.
General settings such as IP address and resource ID that have been assigned during
installation of the product may be viewed or changed calling up the Configure
window via the start menu:
Start > Programs > ABB Industrial IT 800xA > Device Mgmt - FF > Configure
For a description of the dialogs refer to the “Industrial IT, 800xA - Fieldbus,
FOUNDATION Fieldbus Device Integration, Installation” (3BDD012901)
document.

3BDD012902R4101 101
FF Object Editor Section 5 System Configuration

FF Object Editor
Call up FF Object Editor
After calling up the Fieldbus Builder FF from the Plant Explorer, one finds oneself
in the FF Object Editor.
The FF Object Editor can be called up from other tools of the Fieldbus Builder FF
via the menu item > Tools > FF Object Editor.

General Description of the FF Object Editor

The FF Object Editor provides two standard views:
• The tree view in the left area of the window is chiefly for the configuration of
the structure of the HSE subnet and navigation. The tree structure displayed is
shown as FF Object Editor structure.
• The detail view shows a detailed representation of the object selected in the
tree view with additional information.
Underneath the tree view, a further work area can be overlaid, in which either the FF
libraries or the template pool are displayed.
• The FF libraries contain the types of device and module useable in the project.
• The template pool enables management of configured FF structures and FF
object parameter settings that are intended for reuse.
For details, refer to FF Libraries on page 161 and Working with Templates on
page 112.
Apart from setting up the communication connection, the configuration of the
hardware also serves the purpose of documentation and monitoring. Thus, a
comparison may be drawn between what has actually been installed and what has
been configured. Objects which are unavailable are indicated in colour in the
commissioning mode of the FF Object Editor.

102 3BDD012902R4101
Section 5 System Configuration Interface of the FF Object Editor

Interface of the FF Object Editor

Tree View
All objects in the FF network are displayed in the tree view of the FF Object Editor.
Under the HSE Subnet object, further hierarchical levels are inserted down to the
H1 devices. For details of the FF network configuration, refer to System Structure
on page 155.
The allocation of names for the individual objects takes place automatically so that
the user does not have to allocate them himself. The names may be modified
subsequently.

Detail View
The detail view of the FF Object Editor differs according to the object selected and
shows a detailed display of the object with information such as e.g. manufacturer,
device type, bus address. In on-line mode additional status information and
diagnostic information is displayed here.

Operating Modes
The Fieldbus Builder FOUNDATION Fieldbus can be operated in two operating
modes. In the configuration mode, the HSE subnet is configured and documented.
These steps may take place offline. This means that there does not need to be any
system hardware for the entire configuration of the HSE subnet.
The second operating mode is commissioning. By selecting commissioning
communication connections with the devices on the HSE subnet and the subordinate
H1 links are automatically set up.
To change the operating mode, select:
• FF Object editor > Commissioning to change to commissioning mode
or
• FF Object editor > Configuration to change to configuration mode.

3BDD012902R4101 103
General Functions of the FF Object Editor Section 5 System Configuration

Change Background Color of Tree View

By default the background colors of the tree view in configuration and
commissioning mode are white. The background colors may be customized as
follows:
1. Options > Tree Colors
2. Select operating mode whose tree view background color is to be changed.
3. Select desired color.

General Functions of the FF Object Editor

Context Menu
The context menu provides a context-related choice of currently available functions.
1. Select an object from the tree or detail view.
2. Press down right mouse button.

Figure 40. Context Menu in the FF Object Editor

Insert
1. Select position.

104 3BDD012902R4101
Section 5 System Configuration General Functions of the FF Object Editor

2. Edit > Insert ...

New objects can be inserted in the selected position context-sensitively.
For details re configuration of an FF network, refer to System Structure on
page 155.

Cut
1. Select object that is to be cut out.
2. Edit > Cut
The selected objects are cut out and saved in the Windows clipboard. From there,
they can be reinserted using Paste.

Copy
1. Select object that is to be copied.
2. Edit > Copy
The selected objects are saved in the Windows clipboard. From there they can be
inserted as often as desired using Paste.

Paste Contents (Paste)

The objects selected previously using Cut or Copy can be reinserted as soon as a
place of destination has been determined.
1. Select position at which the contents of the clipboard is to be inserted.
2. Edit > Paste

Delete
1. Select object.
2. Edit > Delete
The selected objects are deleted from the object structure.

3BDD012902R4101 105
General Functions of the FF Object Editor Section 5 System Configuration

Search
Edit > Search
The text to be searched for is internally supplemented with an * at the beginning
and an * at the end. Wildcards cannot be used.
The search function is case sensitive!

Block Export
In order to reuse parts of the configuration of the FF network in another subnet, a
block of objects or an object with all subordinate objects can be exported.
1. Select block/object.
2. Edit > Export block...
3. Specify file name of the export file (*.hwm).

Block Import
After importing, a window is displayed with the objects which are on the clipboard.
One node respectively may be selected and inserted at the desired place.
Meanwhile, the objects remain on the clipboard and can be copied again.
1. Edit > Import block...
2. Select object.
3. Drag to the place of destination pressing down the left mouse button.

106 3BDD012902R4101
Section 5 System Configuration General Functions of the FF Object Editor

Display Clipboard
The dialog field in Figure 41 shows the objects on the clipboard. One node
respectively may be selected and inserted at the desired place. Meanwhile, the
objects remain on the clipboard and can be reinserted.

Figure 41. Contents of the Clipboard

1. View > Clipboard viewer

2. Select object.
3. Drag to the place of destination pressing down the left mouse button.

Templates/Libraries
Underneath the tree view, a further work area may be overlaid in which either the
FF libraries or the template pool are displayed. The FF libraries contain the device
and block types useable in the project. The template pool enables management of

3BDD012902R4101 107
General Functions of the FF Object Editor Section 5 System Configuration

configured FF structures and FF object parameter settings that are intended for
reuse.
To overlay the Templates/Libraries work area, select > View >
Templates/Libraries.
For details, refer to FF Libraries on page 161 and Working with Templates on
page 112.

Check whole Project for Plausibility

Tools > Check whole project...
Download information is generated for all active objects in the project. The objects
with the parameter entries undergo a plausibility check and are examined for errors,
omitted entries and contradictions. The errors are listed in a window and can then be
recovered. As a result the engineering status displayed at the object in the FF Object
Editor structure is updated. Refer to Representation in the FF Object Editor Structure
on page 110.

Check Subtree for Plausibility

Tools > Check subtree...
Only the selected object and objects underneath undergo a check for plausibility.
A check for plausibility is also provided in parameter dialogs and detail views
and then refers to the respective selected object.

Network Configuration
Tools > Network....
The central Network Configuration dialog allows to enter or revise the IP settings
for the nodes on the HSE subnet as well as the IP address and ressource ID of the

108 3BDD012902R4101
Section 5 System Configuration General Functions of the FF Object Editor

nodes in the Client/Server network that run the OPC Server FF for this HSE subnet.
Refer to Figure 42.

Figure 42. Central Network Configuration

For a detailed description of the network parameters refer to the section on

parameter settings for the corresponding object:
• HSE Subnet (Subnet Mask, Default Gateway): HSE Subnet Settings Tab on
page 211.
• HSE Host CI860: Communication Tab on page 216.
• Linking Device LD 800HSE: Communication Tab on page 219.
• OPC Server FF: Network Configuration on page 255.

3BDD012902R4101 109
Representation in the FF Object Editor Structure Section 5 System Configuration

Display Version Information

Version information about Fieldbus Builder FF can be called up via the menu item
> Help > About. Figure 43 shows the About Box. The dialog elements are
described in Table 11.

Figure 43. About Box

Table 11. About Box

Dialog element Description

License information The currently installed licenses are listed.
System Information Installation on the Fieldbus Builder FOUNDATION
Fieldbus PC is checked and the result listed.

Representation in the FF Object Editor Structure

For each FF object in the FF Object Editor structure, the following states are
displayed:
• Display status: described by the form of the object node.
+ The branch is collapsed, there are further branches.
- The branch is expanded.
. There is no further branching.

110 3BDD012902R4101
Section 5 System Configuration Representation in the FF Object Editor Structure

• Engineering status: described by the status display on the right of the object
icon. Table 12 shows the engineering status for a single object. If a collapsed
branch exists underneath the object, the status display is supplemented by the
information provided in Table 13 on the objects in the collapsed branch.

Table 12. Engineering Status for a Single Object

• The object must be checked for plausibility; it has not yet been checked
or it has been checked with errors.
• The object has been checked for plausibility with no errors.

• The object has been checked for plausibility with no errors.

• Precommissioning of the object is necessary.
• The object has been checked for plausibility with no errors.
• Loading the object is necessary.
• The object has been checked for plausibility with no errors.
• Download information must be generated.
• Loading the object may be necessary.
•Generate download information by selecting Tools > Check
whole project

Table 13. Additional Status Information with Collapsed Branch

• Precommissioning is necessary for at least one object in the collapsed

branch.
• At least one object in the collapsed branch must be loaded. This is only
displayed if precommissioning has been done for all objects in the
collapsed branch.

3BDD012902R4101 111
Configuration of an FF Network Section 5 System Configuration

The indication in the engineering status, whether precommissioning or loading is

required is based on configuration and commissioning actions executed and
remembered by Fieldbus Builder FF. From this it follows that changes applied
while by-passing Fieldbus Builder FF are not indicated here. Refer to the
commissioning status indicated in the Download dialog in commissioning mode
to get online status information. Refer to Elements of the Download Dialog on
page 362.

Configuration of an FF Network
For details for configuration of an FF network, refer to System Structure on
page 155.

Working with Templates

Configured FF structures and FF objects that are intended for reuse can be
organized in a Template Manager. Fully configured FF Application objects, for
instance, can be stored as templates in the Template Manager. This enables a pool of
frequently used applications to be set up and managed in the form of FF Application
templates. An FF Application template contains all the interconnections and
parameters for the FF function blocks. The FF function blocks in an FF Application
template are not yet assigned to a device.
The applications that are intended for reuse should use the standard function
blocks defined in the FF specifications FF-891 to FF-893. Since these standard
function blocks are supported by most device types, this results in a large degree
of independence from the field devices used in the project.
Once an FF Application template has been added to the FF Object Editor structure
of a specific project the FF function blocks must be assigned to the device instances
used in the project.
Configured branches of trees from the FF Object Editor structure can be stored in
the Template Manager as well as FF Application templates.
Stored templates can be used in the current project or exported for use in other
projects.
The Template Manager can be displayed in a sub-window of the FF Object Editor,
refer to Figure 44. To show / hide this sub-window:

112 3BDD012902R4101
Section 5 System Configuration Create Template

1. View > Templates/Libraries

2. Select Templates tab.

Figure 44. Template Manager

A selected template can be moved to its destination position by dragging it with

the mouse while holding down the left button. When the left mouse button is
released a copy of the template is created automatically (drag and drop).

Create Template
Templates can be created from ready-configured hardware objects or new templates
can be set up.

3BDD012902R4101 113
Create Template Section 5 System Configuration

Store a Ready-Configured Object as a Template

A branch of a tree that has already been fully configured in the FF Object Editor
structure or an individual FF object is stored as a template for reuse.
1. Select FF object in the FF Object Editor structure.
2. Edit > Copy
3. Select node Templates in the templates directory.
4. Edit > Paste
The selected FF object is added to the Template Manager along with any
subordinate objects it may have. If subordinate objects are not to be stored in the
Template Manager they can be deleted:
1. Select FF object in the Template Manager.
2. Edit > Delete
This method can be used to store an FF Application which has already been tested
so that it can be reused.
If an individual FF Application object is stored as a template, any device
assignments that may exist are deleted.
An FF Application template can only be edited to a very limited extent in the
Template Manager since the FF Application Editor is not available.

Create New Template

A new FF object is added as a template to the Template Manager.
1. Context menu for the template object in the Template Manager.
2. Insert
3. Select object from the object list.
4. Click OK
Once the FF object has been created, parameters can be defined in the templates
directory. After this has been done the template is available for reuse.
An FF Application template can only be edited to a very limited extent in the
Template Manager since the FF Application Editor is not available.

114 3BDD012902R4101
Section 5 System Configuration Archive Template

Archive Template
Templates can be exported and imported for the purposes of archival and exchange
with other projects. When templates are exported they are stored in an internal
system format.

Export Template
1. Select template.
2. Edit > Export block...
3. Enter file name for template file.

Import Template
1. Edit > Import block...
2. Select archived template file.
3. Open (show contents of clipboard viewer)
4. Select template object.
5. Insert object by using Drag and Drop.

Use Template
An FF object or a branch of a tree of FF objects is copied from the Template
Manager to the hardware tree.
1. Select FF object in the templates directory.
2. Edit > Copy
3. Select suitable target node in the hardware tree.
4. Edit > Insert...
The selected FF object from the template pool is added to the FF Object Editor
structure along with any subordinate objects it may have.
This method can be employed to use an application which has already been tested
(FF Application template) in the configuration of a project. Once an FF Application

3BDD012902R4101 115
Tag List Section 5 System Configuration

template has been added to the FF Object Editor structure of a specific project the
FF function blocks must be assigned to the device instances used in the project.

Tag List
General Description of the Tag List
The objects configured in the FF Object Editor structure are managed in the Tag
List and made available to the user.
This list is automatically generated or modified during the configuration of an HSE-
subnet.
Search criteria can be defined and activated. Both the total number as well as the
number of currently displayed entries in the list are displayed in the status line. This
makes it possible to identify how many tags comply with the active search criteria,
e.g. certain block types or gateway accesses.

Call up the Tag List

To call up the Tag List, select > Tools > Tag list. Refer to Figure 45.

Figure 45. Call up the Tag List

116 3BDD012902R4101
Section 5 System Configuration Tag List

Structure of the Tag List

The Tag List contains all the blocks mentioned in the project. The structure is
shown in Figure 46 and Table 14.

Figure 46. Structure of the Tag List

Table 14. Structure of the Tag List

Column description Description

Name Name of the tag, 16 characters max.
T Object type of the tag:
• S Standard tag.
This is a tag of the FF Object Editor structure.
Furthermore, all entries not used are indicated by
‚S’.
• T Template tag.
This is a tag from the template pool or from an FF
library.
Short text Short text of the tag, 12 characters max.
Long text Long text of the tag, 30 characters max.
Type name Abbreviations of the block type.

3BDD012902R4101 117
Edit Tag List Section 5 System Configuration

Table 14. Structure of the Tag List

Column description Description

L Library type
• S Standard library.
• X Extended library (contains generic block types).
[OPC Server FF] This column shows the OPC READ (R) and WRITE
(W) access.
To change the read and write access use Edit > Station
access....

Modifications to Existing Tags

If modifications are made to existing tags, these may affect the various objects. In
order to avoid errors, in the event of modifications, the objects concerned are listed.
Thereafter a decision may be reached as to whether the modifications should take
effect.
1. Select desired field by double clicking.
2. Carry out or discard modifications.

Edit Tag List

Sort
1. Data > Sort
2. Select sort criteria

118 3BDD012902R4101
Section 5 System Configuration Edit Tag List

The entries of the Tag List are output on the screen in accordance with the pre-
selected sort criterion. Refer to Figure 47 and Table 15.

Figure 47. Selection of the Sort Criterion

Table 15. Selection of the Sort Criterion

Dialog element Description

Name, alphabetic order Sorting according to alphabetical name.
Block type Sorting according to block types.
Alphabetical sorting according to block types: first the
standard library (S), then the extended library (X).
OK Sorting of data records is activated.
Cancel Cancels the sort action.

End
Tag list > Exit
Return to the Project Editor.

Search
Edit > Search...
Tags can be searched for via their name using the search function. After selection
of this function from the menu or the context menu, a dialog field appears with an

3BDD012902R4101 119
Edit Tag List Section 5 System Configuration

input field. By entering a name or the beginning of a name, the first suitable entry is
automatically found, refer to Figure 48.

Figure 48. Search in the Tag List

Define Filter Criteria

1. Data > Filter...
2. Compile up to 10 filter criteria in one dialog field.
The entries in the list can be output on the screen in accordance with set filter
criteria. A dialog with 10 identical tabs appears for this purpose. Wildcards such as
* (for several characters) and ? (for any character) are permitted. Refer to Figure 49.

120 3BDD012902R4101
Section 5 System Configuration Edit Tag List

Each of the 10 filter criteria may be individually activated and deactivated in the tab
or by means of a corresponding toolbar button.

Figure 49. Define Filter Criteria

Table 16. Define Filter Criteria

Dialog element Description

Activate Activate filter criteria of this tab. After closing this dialog,
all active filter criteria are evaluated and the list of entries
for which all the criteria are met is displayed.
T Define object type as search criterion. Valid entries are
S, T and *.
Type name Define type name as search criterion. The block types
used in the project may be displayed in a list and
selected. The use of wildcards is permitted.
L Define library type as search criterion. Valid entries are
S, X and *.

3BDD012902R4101 121
Edit Tag List Section 5 System Configuration

Table 16. Define Filter Criteria

Dialog element Description

Access by gateway The search criterion is met if read and/or write rights for
station the selected gateway were defined. The gateway names
used in the project may be displayed in a list and
selected. The use of wildcards is permitted.
Show unused tags All tags which are defined but not used in a program are
displayed. Tags for which access rights are assigned via
a gateway but which are not used in the project, are also
unused tags.

The configuration of the filter criteria is saved with the project. Upon calling up the
Tag List, the configured filters are deactivated.
Activated filter criteria can be identified by the correspondingly depressed toolbar
buttons. The configured filter criteria are displayed on the toolbar buttons as
ToolTip. The number of entries in the entire list which meet the search criteria set is
displayed in the status line.

Undo
Edit > Undo.
The last modification is reversed and the old status retained. If reversal is not
possible, the menu item may not be selected (displayed in gray).

Insert new Tag in List

Edit > Insert new tag
If the cursor is in an empty field (e.g. at the end of the list), a new tag is entered
directly into the individual fields of the list line.
If the cursor is on a list entry that is already assigned, a window appears; refer to
Figure 50. This dialog is also displayed when using copy and paste or when
importing tag names that are already in use. In this window is the selected name for

122 3BDD012902R4101
Section 5 System Configuration Edit Tag List

information and as a new entry. This new entry must then be modified to the desired
new name. All other data is imported from the pre-selected tag.

Figure 50. Insert New Tag

Table 17. Insert New Tag

Dialog element Description

Old The name of the selected tag is displayed as
information.
New As default of the name of the selected tag which must
now be modified.
OK New tag is inserted.
Cancel The existing tag is not modified.
Next When inserting a single tag, this button has no function.
When inserting multiple tags by import or copy/paste,
skip to the next already assigned list entry.

If the filter is activated, i.e. the list is not displayed in full, no new tags may be
entered.
If inserting a block, the inserted tags must be given a new name. Using the Next
button, it is possible to skip over several tags in the block and not to include them
again in the list.

Edit Field
1. Select desired field by double clicking, cursor is on last input position.

3BDD012902R4101 123
Edit Tag List Section 5 System Configuration

2. Move cursor on input position within the field.

3. Enter modifications.
The contents of the text in the field selected may be modified. After the modification,
an inquiry is made in another window, if need be, as to whether the modification
should be valid throughout the project or only in certain objects. Refer to
Modifications to Existing Tags on page 118.

Delete Unused Tags

In the Tag List, unused tags are displayed in red.
In the filter for the Tag List the unused tags can be shown and hidden.
Tags for which access rights are assigned via a gateway but which are not used in
the project, are also unused tags.
To delete unused tags, select > Edit > Delete unused tags...

Block Processing
Only one block can be defined each time. A block consists of a sequence of
selected, complete lines in the list and can be selected as follows:
1. Click the cursor on the desired start of block.
2. Keeping the left mouse button pressed down, drag the mouse across the desired
area up to the end.
or
Hold down the SHIFT key and move the cursor with arrow keys.
The block which arises in this way is indicated and is also retained if the left mouse
button or SHIFT key is released.

Cut
1. Select block.
2. Edit > Cut
A defined block is removed from the Tag List and stored in the clipboard.

124 3BDD012902R4101
Section 5 System Configuration Edit Tag List

The command Paste is used to reinsert this stored block at any desired position in
the Tag List.

Copy
1. Select block.
2. Edit > Copy
A defined block is copied and stored in the clipboard.
The command Paste is used to reinsert this block in the desired position in the Tag
List.

Paste
1. Select block.
2. Edit > Paste
A copied or cut block in the clipboard is pasted below the cursor position.
As the tag names have to be modified, the same window appears as under the
menu item Insert new tag.

Delete
1. Select block.
2. Edit > Delete

3BDD012902R4101 125
Edit Tag List Section 5 System Configuration

A defined block is deleted after confirmation; refer to Figure 51 and Table 18.

Figure 51. Delete Tag

Table 18. Delete Tag

Dialog element Description

Cancel Return to the corresponding list.
Delete Selected tag is deleted.
Do not delete Selected tag is not deleted.
Show object Jump to the selected object.

Export
1. Select block.
2. Edit > Export block...
A defined block is stored as a file on a data medium (hard disk, floppy disk). To this
end, a further window appears into which the file path and the file name must be
entered. This file can be imported into other projects using Import file.

Import
Edit > Import block...

126 3BDD012902R4101
Section 5 System Configuration Edit Tag List

A stored file can be read in from a data medium (hard disk, floppy disk). To this end, a
further window appears (refer to Figure 52) into which the file path, the file name and
the file type must be entered. If tag names are found during an import in the project
which already exist with the same name in the project, they are handled like a new tag.
Refer to Insert new Tag in List on page 122. The importing of files (file type .msr)
exported with Fieldbus Builder FF or text files (file type .csv or .txt) is supported.

Figure 52. Import Tags

Fieldbus Builder FF Format

Files which are exported using Export file from the Tag List, may be reimported.
These files have the extension .msr.
External format
With the tag import it is also possible to import files generated using external
applications (e.g. Microsoft Excel) into the Tag List. These files have the extension
.csv or .txt.

3BDD012902R4101 127
Edit Tag List Section 5 System Configuration

The files to be imported must be text files in Unicode format with the following
structure: per line the import file contains the name of the tag, the short text and the
long text. The type of tag is not yet specified here.
These three texts are separated by a list separator. The list separator can be a comma
’,’ or a semicolon ’;’. Different separators may not be used within a line. In the
event that a text itself contains the list separator, the text or the list separator must be
put in inverted commas (" "). The end of the file is identified by a line break.
The import file must be a Unicode file.

When importing, a check is made as to whether the existing restrictions for tag
names have been observed, otherwise the import of this tag is rejected.
The short text may contain 12 characters maximum. If the short text is longer, the
remaining characters are ignored during importing. The long text is 30 characters
long maximum, and on importing, only the maximum number of characters
permitted are read in.
The short and long text may not contain any list separators in their text which are
not in inverted commas. Otherwise, the tag import regards this character as a
separator and evaluates the next character as the first character of the following
field. If there are more than two list separators in a line, all characters after the third
list separator until the end of the line are ignored. On the other hand, if there are
fewer than two separators per line, the importing of this tag is rejected.
If format errors are detected in the import file during the tag import, the import is
cancelled at this point.
The tag and the library type are initialised upon entry of new tags with ’----’ for tag
type and ’-’ for library type. The tag type can be directly assigned to the Tag List
(refer to Modifications to Existing Tags on page 118) or during configuration of the
blocks.

Station Access
1. Select block.

128 3BDD012902R4101
Section 5 System Configuration Cross References

2. Edit > Station access

Figure 53. Configure Station Access

If the inputs, outputs and internal parameters of a tag are to be read or written via an
OPC Server FF, this access must be released; refer to Figure 53.
For further details refer to Enabling of Tags for OPC Access on page 260 and
Configuration with Fieldbus Builder FF on page 253.

Modify Block Type

1. Select block.
2. Edit > Change functionblock type...
A new block type can be assigned to the marked tags. All the block types known in the
system are available for selection: block types of the standard library or the expanded
library.

Cross References
Cross references are references to places at which a tag is declared or used.
All cross references of a tag can be displayed within a list.
1. Select tag.
2. Key F5 or Tools > Cross references...

3BDD012902R4101 129
Project Editor Section 5 System Configuration

A window shows the names of all objects in which the tag is used, refer to
Figure 54. For available actions, refer to Table 19.

Figure 54. Show Cross References

Table 19. Show Cross References

Dialog element Description

Show object The incidence point of this tag in the FF Object Editor
structure is called up.
Show declaration Shows declaration of the tag in the Tag List.

Project Editor
Call up Project Editor
The Project Editor is called up via the menu item >
Project comment > Exit or,
FF Object editor > Exit or,

130 3BDD012902R4101
Section 5 System Configuration General Description of the Project Editor

Documentation > Exit or,

Tag list > Exit.

General Description of the Project Editor

The configuration data of an HSE subnet are managed by the Fieldbus Builder FF in
the form of a project.
The Project Editor permits the following actions:
• Editing of project information
• Create/Modify a project comment
• Switchover between the operating modes Off-Line and On-Line
• Display of version information about Fieldbus Builder FF

Edit Project Information

The project information contains general data about the project which are entered in
the drawing header or footer of a sheet in the project documentation. To edit the
project information, select: > Project > Project information.
The window Configuration: Project Information is opened. The project size in KB,
the date and the time of the last data backup are displayed.
The window contains the data which were set up upon creation of a new project.

3BDD012902R4101 131
General Description of the Project Editor Section 5 System Configuration

For further details refer to Documentation on page 134.

Figure 55. Configuration Project Information

The following data applicable to the whole project can be entered: refer to Table 20.

Table 20. Configuration Project Information

Dialog element Description

Project name max. 12 characters, regardless of the name of the
project file (.pro)
Project manager Name 27 characters max. long
Project no. 6 characters max. long project number
Project orderer 27 characters max. long customer identifier
Project order no. 12 characters max. long order number

132 3BDD012902R4101
Section 5 System Configuration General Description of the Project Editor

Table 20. Configuration Project Information

Dialog element Description

Project password In this version this function has been deactiviated.
Project size The current size of the project file (*.pro) in KBytes is
displayed.
Version The date of the creation of the project is displayed.
Project comment max. 34 characters
Edit drawing header / Assignment of certain system variables (F2) to the fields
footer of the drawing header. For further details refer to
Documentation on page 134.
Edit header titles / The headings of the individual windows in the drawing
footer titles header may be modified here. For further details refer to
Documentation on page 134.
OK All entries are stored in the database. The dialog is
terminated.
Cancel The dialog is terminated without the entries being
included.

Edit Project Comments

To edit the project comments select: Tools > Project comment.
With the comment editor, a free text for a project can be created, modified and
printed as hardcopy. In addition, there is an import and export function for Unicode
TXT files.

Set up Online Connection

When setting up an online connection via the menu item Options > On-line,
communication links to the devices on the HSE subnet and the subsidiary H1 links
are made.
Upon commissioning, the online connection is set up automatically.

3BDD012902R4101 133
Documentation Section 5 System Configuration

Clearing down Online Connection

When clearing down the online connection via the menu item > Options > Off-line,
the communication links to the devices on the HSE subnet and the subsidiary H1
links are cancelled.

Documentation
General Description of the Documentation
All the objects configured in Fieldbus Builder FF can be documented.
A common layout is used for all documents. There is the option of incorporating
corporate logos into the drawing header or footer. Free sorting when printing the
documents, and a complete table of contents of all project parts make the
documentation easier to handle.
Clear identification of the type of document (Doc Type) via the document
identification code enables easy location of documents.
Automatically derived document identification (Doc ID) refers via the object name
to the function world. Data or also output concerning the customer identification
number is possible.
With the help of the cross-reference list, it is easy to find all references.
By displaying in dialog form, the documentation is clear and easy to read.
Printing of the documentation is controlled by a so-called documentation job, i.e. for
printing, an job must be selected. The contents of the job is defined in a
documentation job.

Documentation Management

Call up of Documentation Management

To call up documentation management, select:
Tools > Documentation

134 3BDD012902R4101
Section 5 System Configuration Documentation Management

The table shows the print jobs available. Blank lines in the table represent free print
jobs. Refer to Figure 56 and Table 21.

Figure 56. List of Documentation Jobs

Table 21. Structure of the List of Documentation Jobs

Column description Description

Name Name of the job; 12 characters max.; must start with a
letter; no special characters; no blank characters.
Comment 34 characters max. of free text (including special
characters).
Last revision Date and time of the last modification; entered
automatically by the system.

Modification of Column Width

If the mouse pointer is positioned on a column separation line, the mouse pointer
changes into a horizontal arrow. With the left mouse button pressed down, the
column width can now be modified. This is stored after leaving documentation
management and is therefore available for every subsequent call-up.

3BDD012902R4101 135
Create Drawing Header / Footer Section 5 System Configuration

Create Drawing Header / Footer

General
In order to be able to make the entries in the drawing header/footer, the header
and/or the footer in the dialog was divided into several horizontal areas to improve
clarity.

Pan-project Drawing Header / Footer

A drawing header/footer valid globally for the project is defined at project level. All
settings which are made in the header or footer, are stored in the project.
Project > Project information...

Figure 57. Edit Project Information

136 3BDD012902R4101
Section 5 System Configuration Create Drawing Header / Footer

The text entered in the upper part of the dialog is assigned to the drawing header
and/or footer. For further details refer to Figure 57 and Edit Project Information on
page 131.

Edit Drawing Header

Project > Project information... > Button: Edit drawing header
Refer to Figure 58 and Table 22.

Figure 58. Edit Drawing Header

Table 22. Edit Drawing Header

Dialog element Description

OK Terminate header entries, entries are stored.
Cancel Terminate header entries, entries are rejected.
Reset All entries are included from the defaults of the file
FRAMES.INI.
Merge All variables from the defaults of the file FRAMES.INI are
included, i.e. all fixed text is retained.

3BDD012902R4101 137
Create Drawing Header / Footer Section 5 System Configuration

Table 22. Edit Drawing Header

Dialog element Description

Clear All field contents are deleted.
Export The current entries of the header are written into the file
FRAMES.INI and are thus the new defaults for Reset
and Merge. If export is used after reset, all the entries
are lost!
Select One section from the file FRAMES.INI may be selected
from the list field. Its contents or defaults are then
activated if Reset or Merge are operated.
Preview A preview of the contents as they appear when printed
out is overlaid. Thus, the appearance of inserted
bitmaps can be assessed.
Titles The title defined by the user is overlaid. Hereby a brief
description of the field or its intended contents is
obtained. In the fields in which the user has not entered
any header description, the field description is entered
(e.g. F52).

Edit Header Titles

Project > Project information... > Button: Edit header titles

138 3BDD012902R4101
Section 5 System Configuration Create Drawing Header / Footer

In this dialog, title descriptions may be entered which can be overlaid later in the
dialog of the header lettering. Refer to Figure 59.

Figure 59. Edit Header Titles

Edit Drawing Footer

Project > Project information... > Button: Edit drawing footer

3BDD012902R4101 139
Create Drawing Header / Footer Section 5 System Configuration

Refer to Figure 60 and Table 23.

Figure 60. Edit Drawing Footer

Table 23. Edit drawing Footer

Dialog element Description

OK Terminate footer entries, entries are stored.
Cancel Terminate footer entries, entries are rejected.
Reset All entries are included from the defaults of the file
FRAMES.INI.
Merge All variables are included from the defaults of the file
FRAMES.INI. I.e. all fixed text is retained.
Clear All field contents are deleted.

140 3BDD012902R4101
Section 5 System Configuration Create Drawing Header / Footer

Table 23. Edit drawing Footer

Dialog element Description

Export The current entries of the footer are written into the
FRAMES.INI file and are thus the new defaults for Reset
and Merge. If export is used after reset, all the entries
are lost!
Select One section from the file FRAMES.INI may be selected
from the list field. Their contents or defaults are then
activated if Reset or Merge are operated.
Preview A preview of the contents as they appear when printed
out is overlaid. Thus, the appearance of inserted
bitmaps can be assessed.
Titles The title defined by the user is overlaid. Hereby a brief
description of the field or its intended contents is
obtained. In the fields in which the user has not entered
any footer title description, the field description is
entered (e.g. F24).

Edit Footer Title

Project > Project information... > Button: Edit footer titles

3BDD012902R4101 141
Create Drawing Header / Footer Section 5 System Configuration

In this dialog, title descriptions may be entered which can later be overlaid in the
dialog of the footer description. Refer to Figure 61.

Figure 61. Edit Footer Title

Automatic Allocation of Object Parameters

To modify entries, the cursor must be placed on a field and the desired entry made.
In the fields of the header and footer designation, furthermore, a list of the
framework designation variables (documentation variables) available in Fieldbus

142 3BDD012902R4101
Section 5 System Configuration Basic Editing Steps

Builder FF can be called up using the key F2. In the lower part a corresponding
explanatory text appears upon selection of a variable. Refer to Figure 62.

Figure 62. Select Dialog Documentation Variable

Assignment of Bitmaps in Drawing Header / Footer

Any bitmaps desired may be displayed in the drawing header/footer and on the
cover sheet. Refer to Fonts, National Languages and Bitmaps in the Drawing Footer
/ Header on page 414.
Any bitmaps desired may also be assigned with #Bitmap Name. This
presupposes that this bitmap is in the standard dictionary.

Basic Editing Steps

Create New Documentation Job

1. Position cursor on a blank line.
2. Enter name of the documentation job in the Name field.
3. Optional: enter explanatory text in the Comments field.

3BDD012902R4101 143
Basic Editing Steps Section 5 System Configuration

Date and time are automatically entered in the Last Revision column by the system.

Copy Documentation Job

A new documentation job can also be created by copying an old documentation job
and storing it under a new name. All definitions of the documentation contents are
included and can then be modified.
Carry out the following editing steps to this end:
1. Position cursor on a documentation job (complete line).
Documentation > Insert
or
1. Mark the row of an existing documentation job.
2. Edit > Copy
3. Position the Cursors on an empty line.
4. Edit > Paste
Specify the new name of the documentation job in the following dialog. Refer to
Figure 63.

Figure 63. Dialog Insert Documentation Job

144 3BDD012902R4101
Section 5 System Configuration Compile Documentation Job

Export Contents
Documentation > Export contents...
The table of contents of the selected job is stored in CSV format with the file ending
*.dco. The file name and the dictionary can be selected in a dialog. The project
dictionary is offered as the default and the first 8 characters of the documentation
job name as the file name. This file can then be opened and edited, for example, in
tabular form in Excel.

End
Documentation > Exit
Documentation management is exited.

Compile Documentation Job

Set up Documentation Contents

After a new documentation job has been stored, as described in Create New
Documentation Job on page 143, the desired documentation contents are set up as
follows:
1. Select documentation job.
2. Edit > Job detail...
Refer to Figure 64 and Table 24.
For selective documentation of the menu item Hardware structure >
Parameter (refer to Table 24) a selection window is available under Options >
Hardware scope.... Refer to Selection of the Hardware Scope on page 149.
You should only select the menu item Hardware structure > Parameter if
hardware expedient for the project has been selected previously as otherwise a
printout for the parameters is created every time for every hardware component
entered in the project!

3BDD012902R4101 145
Compile Documentation Job Section 5 System Configuration

Figure 64. Edit Dialog Documentation Job

Table 24. Edit Dialog Documentation Job

Dialog element Description

Cover page If this field is checked, a cover sheet is printed out before
the documentation job. It contains all the data relevant to
the project, such as e.g. name, comments, date, project
number, etc.
Index If this field is checked, a table of contents is printed out at
the end of the documentation job. It contains a list of all
documents created during default sorting. Refer to
Sorting of the Printout on page 147.
Documentation settings If this field is checked, a sheet with the settings selected
for the documentation job is printed out.

146 3BDD012902R4101
Section 5 System Configuration Documentation Scope

Table 24. Edit Dialog Documentation Job

Dialog element Description

Tag list Here the parts of the Tag List which are to be included in
the documentation are selected. Check the desired
fields. All selected modules are included in the
documentation with the selected additional information.
Furthermore, there is the possibility of setting up the
sorting of the list. Sorting can be done according to tag
name or type name.
The scope of the list may be delimited by making a
selection using wildcards.
Tags cross reference The same selection window as in the Tag List is
displayed.
For further details refer to Tag List on page 116.
Hardware structure Specification, which parts of the FF Object Editor
structure should be printed. Select the desired fields.
Plausibility check errors Plausibility check messages can be printed out. The
checkbox warnings and hints specifies whether only
errors or all messages are printed out.

Documentation Scope

Inspect Selected Documentation Scope

Documentation > Preview...
A table of contents of the selected sheets in the selected documentation job is
displayed in a window.

Sorting of the Printout

Options > Sort fields...

3BDD012902R4101 147
Documentation Scope Section 5 System Configuration

Sorting of the printout can be defined. The documentation printout can be sorted
according to up to 9 criteria. The field contents of the drawing footer may be
selected as sort criteria. Refer to Figure 65.
During printout, each sort criterion selected here automatically becomes a
column in the table of contents.
Sorting according to date is not possible.

Figure 65. Select Dialog Columns of the Table of Contents

148 3BDD012902R4101
Section 5 System Configuration Documentation Scope

Selection of the Hardware Scope

Options > Hardware scope...

Figure 66. Dialog Hardware Scope

In this dialog, a selection of the hardware components desired for the

documentation can be made. Selection and deselection of components may be
undertaken by clicking with the mouse or using the Ins and Del key.
This selection is only active as long as you are in documentation management.
After leaving documentation management, the complete configured hardware is
selected as standard! This item is only significant in connection with selection
under: Edit > Job detail... > Hardware structure > Parameter; refer to Set up
Documentation Contents on page 145.

3BDD012902R4101 149
Print out Documentation Section 5 System Configuration

Selection for Print Error Message

Options > Notify print errors
At this point it is set up whether errors which occur in connection with the printout
of the project documentation, such as e.g. print errors, missing objects (e.g. bit
maps) and invalid or undefined field functions in the drawing header/footer are
displayed on the screen or not.

Print out Documentation

Print
Documentation > Print...
Printing to a file or directly to the printer is started. Refer to Figure 67 and Table 25.
The maximum available hard disk space free must be taken into account. For
further details refer to Inspect Selected Documentation Scope on page 147.
To obtain an overview of the print scope, the preview function should be used.
For further details refer to Inspect Selected Documentation Scope on page 147.

Figure 67. Dialog Configuration: Documentation

Table 25. Dialog Configuration: Documentation

Dialog element Description

Yes Printout is on the standard printers entered in Windows.

150 3BDD012902R4101
Section 5 System Configuration Print out Documentation

Table 25. Dialog Configuration: Documentation

Dialog element Description

No It is possible to print to a file. On selecting this option, a
window opens in which the path and the file name of the
target file can be edited. Defaults for the file name: name
of the documentation job with the extension .DPD.
Cancel Printing is cancelled.

Print File
Documentation > Print file...
A previously created documentation file (extension .DPD) is printed. The file to be
printed must be selected in a dialog field.

Printer Setup
Documentation > Printer setup

3BDD012902R4101 151
Print out Documentation Section 5 System Configuration

The dialog of the Windows operating system for printer setup permits the selection
of a printer and the undertaking of various settings. For further details refer to the
documentation of the operating system.

Figure 68. Dialog Print Setup

Comment Editing

Call up Comment Editor

Tools > Comment editor
The contents of the text of the comment field may be modified.

Export Comment
In comment editor select:
Comment > Export
The contents of the text of the comment field is stored as a text file *.txt and thus
serves as the basis for new print job comments. This text file is stored in Unicode
format.

152 3BDD012902R4101
Section 5 System Configuration Print out Documentation

Import Comment Field

In comment editor select:
Comment > Import
The contents of the text of an originally exported comment field (stored as a text file
*.txt) is inserted in the comment field of the selected print job. Existing entries are
overwritten completely. At this point, any text desired can be inserted, provided that
it has been converted to Unicode format first.

3BDD012902R4101 153
Print out Documentation Section 5 System Configuration

154 3BDD012902R4101
 Section 6 Configuring an FF Network

System Structure
FF Network with Interface to an IEC 61131 Controller
The FF network comprises at least one HSE subnet and any number of H1 links,
which are connected via the FF linking devices (LD). The FF network can be
interfaced with an IEC 61131 controller via a FOUNDATION Fieldbus HSE
communication interface module CI860 in the AC 800M which is connected to an
HSE subnet as an HSE host. Refer to Figure 69.
The devices connected to an HSE subnet - the FF linking devices and HSE hosts -
communicate with one another using the HSE protocol. An FF linking device
generally provides several FOUNDATION Fieldbus H1 links. FF linking devices of
device class 42c allow process data that has been published cyclically on the
subsidiary H1 links to be "republished" on the HSE subnet. By using HSE-
republishing, it is possible to configure cyclical communication between field
devices on different H1 links and devices on the HSE subnet.

3BDD012902R4101 155
 Section 6 Configuring an FF Network

FF linking devices operate as gateways between the HSE subnet and the field
devices on the H1 links both for the configuration data from the field devices and for
the process data which is exchanged cyclically.

Engineering Workplaces
- Control Builder M
- Fieldbus Builder FF Operator Workplaces

Aspect Directory Server

Client Server
Network

Connectivity Server FF Connectivity Server redundant

with OPC Server FF AC 800M Connectivity Server FF
with OPC Server FF

Control Network

AC 800M AC 800M red AC 800M red

CI860 CI860 red CI860 red

HSE Subnet
LD 800HSE LD 800HSE LD 800HSE
LD 800HSE redundant redundant redundant

H1 Links
H1 Links

H1 Links

H1 Links

H1 Field Devices

H1 Field Devices H1 Field Devices H1 Field Devices

H1 Field Devices

Figure 69. Sample System Structure with FF Network

Connectivity servers with OPC Server FF installed provide the connection between
the Client Server network on the one side and the HSE subnets on the other side.

156 3BDD012902R4101
Section 6 Configuring an FF Network

Both the configuration information from the Fieldbus Builder FF and all data
accesses of Plant Explorer are transported to the field devices via OPC Server FF.
Although HSE uses the standard Ethernet Physical Layer, ABB currently does
neither recommend nor support to mix HSE with other protocols or to run several
HSE Subnets on the same Ethernet Physical Layer (wire).
HSE causes a lot of broadcast and multicast traffic, requiring significant
bandwidth on the Ethernet. Without explicit tests, it cannot be guaranteed that
HSE can co-exist with other protocols. Such tests are not executed as part of the
product release.
The Fieldbus Builder FF enables the configuration and commissioning of FF linking
devices of device classes 42a, 42b and 42c.
In order to configure this kind of system structure, the FF objects specified are
configured in the FF Object Editor structure. Table 26 contains a list of the available
FF objects.

Table 26. Overview of Objects

Object Description
FF Block Library FF Block Library object:
Library for accommodating the block classes for Function
blocks, Resource blocks and Transducer blocks that have
been imported via FF device import. The block types
contained in the block library are available for use in the
project.
H1 Device Library H1 Device Library object:
Library for accommodating the H1 device classes imported
using FF device import. The H1 device types contained in
the H1 device library are available for use in the project.
HSE Device Library HSE Device Library object:
Library for accommodating the HSE device classes imported
using FF device import. The HSE device types contained in
the HSE device library are available for use in the project.

3BDD012902R4101 157
 Section 6 Configuring an FF Network

Table 26. Overview of Objects

Object Description
FF Block Class FF Block Class object:
The block class represents the type of a block (analog input,
PID controller etc.). The FF Block Class object contains a set
of initial parameters. When an instance of the block is added
to the application, it is assigned these initial parameters by
default.
H1 Device Class H1 Device Class object:
The H1 device class represents the type of an H1 device.
The H1 Device Class object contains the device-type-
specific data from the device description (DD) and the
capabilities files.
HSE Device Class HSE Device Class object:
The HSE device class represents the type of an HSE device.
The HSE Device Class object contains the device-type-
specific data from the device description (DD) and the
capabilities files. FF linking devices belong to this device
class.
FF Network FF Network object:
The FF Network object is the root node of the project.
Besides the HSE Subnet object up to two OPC Server FF
objects can be present below this root object.
HSE Subnet HSE Subnet object:
Fieldbus network for connecting FF devices using the HSE
communication profile. The HSE Subnet object contains the
signal list for the HSE subnet and the subsidiary H1 links.
HSEHostCI860 HSE Host object:
The HSE Host object represents the interface between the
HSE subnet and an IEC 61131 controller. It contains
configuration data for the exchange of data between the
HSE subnet and the IEC 61131 controller.

158 3BDD012902R4101
Section 6 Configuring an FF Network

Table 26. Overview of Objects

Object Description
HSE Device HSE Device Instance object:
Specific HSE device used in the project with device-specific
parameter data. FF linking devices are represented by HSE
Device Instance objects.
H1 Link H1 Link object:
Fieldbus network on an FF linking device for connecting FF
devices which use the H1 communication profile. FF linking
devices generally provide several H1 links.
H1 Schedule H1 Schedule object:
Editor for displaying the automatically-generated, time-based
processing sequence of FF function blocks that have been
configured in an H1 link, which also provides the option of
post-processing.
FF Application FF Application object:
Application that has been modelled using FF function blocks,
and whose cycle time can be specified by the operator.
H1 Device H1 Device Instance object:
Specific H1 field device used in the project with device-
specific parameter data.
FF Block Block Instance object:
A specific block with its own individual parameter data that is
used in an application.
OPC Server FF OPC Server FF object:
The OPC Server FOUNDATION Fieldbus (OPC Server FF)
makes data from FOUNDATION Fieldbus devices available
to any desired OPC clients.

The FF signals of the HSE subnet are defined using the existing HSE Subnet object.
FF linking devices can be inserted into the structure in the form of HSE Device
Instance objects below the HSE Subnet object.

3BDD012902R4101 159
 Section 6 Configuring an FF Network

A number of H1 Link objects, which depends on the capabilities of the FF linking

device used, can be inserted below the HSE Device Instance object. The bus
parameters for an H1 link are set on an H1 Link object.
An H1 Schedule object is inserted automatically below an H1 Link object. The
graphic view of the H1 Schedule object allows the automatically-generated, time-
based execution sequence (schedule) of FF function blocks that have been
configured in this H1 link to be displayed and optionally post-processed.
On the same level, H1 Device Instance objects can be inserted below an H1 Link
object. Each of these objects represents an actual field device that is present in the
H1 link.
FF Application objects can be inserted below an H1 Schedule object, refer to
Figure 70. These objects represent the applications modeled using function blocks.

Figure 70. Object Structure

The FOUNDATION Fieldbus network is interfaced to the IEC 61131 Controller via
a FOUNDATION Fieldbus HSE communication interface module in the AC 800M.
This is done by inserting an HSE Host object (HSEHostCI860) below the HSE

160 3BDD012902R4101
Section 6 Configuring an FF Network FF Network without Interface to an IEC 61131 Controller

Subnet object in the FF Object Editor structure. The data exchange between the
IEC Controller and the FF network is configured using this object.
If the Engineering Workplace on which the Fieldbus Builder FF is running is not
directly connected to the HSE subnet, an OPC server must be configured. The
OPC server makes available the communications connection required for loading
the configuration data. Refer to Configuration with Fieldbus Builder FF on page
253 for the configuration of an OPC server.

FF Network without Interface to an IEC 61131 Controller

The Fieldbus Builder FF also enables the configuration and commissioning of an
FF network, which is not linked to an IEC 61131 controller. In this case the Fieldbus
Builder FF is linked directly with the HSE subnet. Unlike the structure described
earlier, the HSE Host object (HSEHostCI860) required for interfacing to the
IEC 61131 controller no longer needs to be configured.

FF Libraries
Before you start working with FF libraries familiarize yourself with the FF
libraries concept used in the Plant Explorer Workplace. Please refer to Basic
Principles of the Integration in Plant Explorer on page 77.
When working with FF objects a distinction is made between classes and instances.
The class determines the functionality and visual appearance of an object. For
example, FF block types and FF device types are represented as classes. The classes
are stored together in libraries.
To use a class, instances of the class are formed. For example, an FF Application is
configured in the FF Application Editor using FF function block instances. H1
device instances, on the other hand, are used for configuring an H1 link in the FF
Object Editor structure.
Both the class and the instance have a parameter input dialog. Changes carried out
in the parameter input dialog for the class affect all instances for that class that are
already in use as well as all instances of the class that are created later. So that the
changes become effective in instances that are already in use it is necessary to open
the parameter input dialog for each instance and reset the parameters. Changes in

3BDD012902R4101 161
Block Library Section 6 Configuring an FF Network

the parameter input dialog for an instance, on the other hand, affect only that
instance.
OPC access parameters, OPC short names, user dialoges and list of parameter
values can only be changed in the class description and therefore directly become
effective in all instances.
In the FF Object Editor, underneath the tree view, a window pane showing libraries
can be overlaid. To show / hide this sub-window:
1. View > Templates/Libraries.
2. Select tab Libraries.
The block library, the H1 device library and the HSE device library are displayed.
The initial contents of these libraries is a set of pre-integrated device types and
corresponding block types provided by the FOUNDATION Fieldbus Device
Integration Library. Refer to Section 14, FF Device Integration Library. The
contents of these libraries may be extended by importing FF devices. Refer to
Expanding FF Libraries on page 165.
The Fieldbus Builder FF allows you to benefit from the open FOUNDATION
Fieldbus protocol. The FOUNDATION Fieldbus specification includes some
degrees of freedom. In order to guarantee the system function interoperability
for devices not included in the FF Device Integration Library, a device type
specific in-depth integration test is strongly recommended for H1 devices; it is
required for HSE devices (linking devices).

Block Library
The block library contains the block types that can be used in the project in the form
of FF block classes. This library contains the following branches:
• Function blocks: Provide processing functions in the field devices.
• Resource blocks: Describe general features of the device. Every device has
exactly one resource block class.
• Transducer blocks: Decouple the function blocks from local input/output
functions of the sensor and actuator hardware. There is normally one
transducer block class for each input or output function block class.

162 3BDD012902R4101
Section 6 Configuring an FF Network H1 Device Library

The block library is filled with project-specific data when FF devices are imported.
Refer to Figure 71. For further details refer to Expanding FF Libraries on page 165.

Figure 71. Object Structure Block Library

It is not possible to add library elements explicitly in the block library. This is
performed implicitly by importing FF devices.
It is not possible to delete library elements explicitly in the block library. This is
done implicitly by deleting FF devices in the H1 device library.

H1 Device Library
The H1 device library contains, in the form of FF device classes, the H1 device
types that can be used in the project. Refer to Figure 72.
The special H1 device Standard FBs contains the standard function blocks specified
by the Fieldbus Foundation. Refer to User Application on page 41.

3BDD012902R4101 163
HSE Device Library Section 6 Configuring an FF Network

The H1 device library is expanded by importing H1 devices. For further details refer
to Importing H1 Field Devices on page 165.

Figure 72. Object Structure H1 Device Library

When an H1 device class is deleted, the elements associated with this device class in
the device library are automatically deleted. An H1 device class can therefore only
be deleted if the following criteria are met:
• The project does not contain any instances for this H1 device class.
• There are no block instances in the project which refer to the block classes
imported with this device.

It is not possible to add library elements explicitly in the H1 device library. This
is performed implicitly by importing FF devices.
If an element is deleted from the H1 device library, then the elements associated
with that H1 device class are automatically deleted from the block library.

HSE Device Library

The HSE device library contains, in the form of HSE device classes, the HSE device
types that can be used in the project. FF linking devices are stored in this device
library. Refer to Figure 73.

164 3BDD012902R4101
Section 6 Configuring an FF Network Expanding FF Libraries

The HSE device library is expanded by importing HSE devices. For further details
refer to Importing HSE Devices on page 169.

Figure 73. Object Structure HSE Device Library

An HSE device class can only be deleted if there are no existing instances of that
HSE device class in the project.
It is not possible to add library elements explicitly in the HSE device library. This
is done implicitly by importing HSE devices.

Expanding FF Libraries
All FF devices, which are intended to be used in the project, must be known with
their class description. With the import of an FF device the libraries of the Fieldbus
Builder FF are extended by the device and block classes of this device. Thereby the
required information for configuration and parameterization of the device and all
supported blocks is made available in Fieldbus Builder FF.
The Fieldbus Builder FF allows you to benefit from the open FOUNDATION
Fieldbus protocol. The FOUNDATION Fieldbus specification includes some
degrees of freedom. In order to guarantee the system function interoperability
for devices not included in the FF Device Integration Library, a device type
specific in-depth integration test is strongly recommended for H1 devices; it is
required for HSE devices (linking devices).

Importing H1 Field Devices

When H1 devices are imported, a new device type is added to the H1 device library.
Next to this Resource and Transducer blocks are added to the block library, along
with the block types supported by the field device.

3BDD012902R4101 165
Importing H1 Field Devices Section 6 Configuring an FF Network

The FF device files, i.e. Capabilities files (refer to Section 2, Technical Overview
FOUNDATION Fieldbus, Object Dictionary on page 45) and Device Description
files (refer to Section 2, Technical Overview FOUNDATION Fieldbus, Device
Descriptions on page 46) provided by the device manufacturers, form the basis for
the import.
H1 devices are imported within the H1 device library using menu item Insert.
When Insert is selected, the device selection dialog appears.
1. Select H1 Device Library
2. Edit > Insert
3. Select device file with the file name extension .cff.
4. Press the OK button in the Device Info window. Refer to Figure 74.

Figure 74. H1 Device Info

166 3BDD012902R4101
Section 6 Configuring an FF Network Importing H1 Field Devices

When an H1 field device is imported, the content of the device description (DD)
is interpreted. If the device description contains descriptive elements that are not
supported by the current version of Fieldbus Builder FF, this will be indicated in
the DD Import Log window. Users may decide nonetheless to use the elements
listed there, but they must take responsibility for this decision. During the
configuration and commissioning phases special handling procedures may need
to be employed for these elements.
After the device has been imported, all the information needed to configure and
define parameters for the imported device type is available.
There are only limited facilities for updating an existing device type in the H1
device library. The Capabilities file can generally be updated. An update Device
Description is always imported as a new device.
The parameters MANUFACTURER (manufacturer ID), DEVICE_TYPE,
DEVICE_REVISION and DD_REVISION (revision of the device description)
serve to identify a device description. If two device descriptions show no
differences in any of these identification parameters, then they are considered to
be identical. Each device can be imported only once. If a device description has
at least one identification parameter that differs from an existing device
description, when the second device description is imported a new device is
created in the H1 device library.
In accordance with the FF Specification, the path to the device files contains the
manufacturer ID and the device type. The file name of a capabilities file is
composed of three pairs of characters. These pairs identify the revision of the
device, the device description and the capabilities file. The file name extension is
.cff. When the device is imported, files with extensions .sym and .ffo, which are
stored in the same directory, are also copied.
The path of a capabilities file for the pressure transmitter 2000T from ABB is
shown:
000320/0089/010302.cff
It is made up as follows:
000320 Manufacturer ID: ABB Instruments
0089 Device type: 2000T
01 Revision of the device

3BDD012902R4101 167
Importing H1 Field Devices Section 6 Configuring an FF Network

03 Revision of the device description

02 Revision of the capabilities file
Table 27 of manufacturer IDs does not claim to be comprehensive.

Table 27. Manufacturer ID

Manufacturer ID Manufacturer
0x00012C KROHNE Messtechnik
0x000302 Smar International Co.
0x000309 Fuji Electric Co., Ltd.
0x000310 Micro Motion, Inc.
0x000320 ABB
0x000457 Ohmart/Vega
0x001151 Rosemount, Inc.
0x004649 Fieldbus, Inc.
0x0021C3 Bürkert Werke GmbH & Co.
0x005100 Fisher Controls International, Inc.
0x00E099 Samson AG
0x00FF01 Rotork Controls Limited
0x0B87A3 El-O-Matic
0x0DFC96 Yamatake Corporation
0x385884 Foxboro (and Foxboro-Eckardt)
0x445644 Dresser Valve Division
0x452B48 Endress + Hauser
0x464C4F Flowserve
0x48574C Honeywell IAC
0x4E4943 National Instruments

168 3BDD012902R4101
Section 6 Configuring an FF Network Importing HSE Devices

Table 27. Manufacturer ID

Manufacturer ID Manufacturer
0x502B46 Pepperl + Fuchs
0x524149 Rosemount Analytical Inc.
0x545758 TopWorx
0x594543 Yokogawa Electric Corporation

Importing HSE Devices

When HSE devices are imported a new device type is added to the HSE device
library.
The capabilities files for HSE devices, which manufacturers supply along with the
devices, form the basis for the import.
HSE devices are imported by choosing the Insert menu item within the HSE device
library. When Insert is selected, the device selection dialog appears.
1. Select HSE device library.
2. Edit > Insert
3. Select device file with the file name extension .cfh.
4. Press the OK button in the device info window. Refer to Figure 75.

3BDD012902R4101 169
Assigning Bitmaps Section 6 Configuring an FF Network

Figure 75. HSE Device Info

After the device has been imported, all the information needed to configure and
define parameters for the imported device type is available.
The parameters MANUFACTURER (manufacturer ID), DEVICE_TYPE and
DEVICE_REVISION serve to identify a device type. If all three of these
identification parameters are identical for two devices, then those two devices are
viewed as identical. Each device can be imported only once. If one or more of the
identification parameters is different a new device is created in the HSE device
library when the second device type is imported.
The naming of capabilities files for HSE devices is subject to the same rules as for
H1 devices (refer to Importing H1 Field Devices on page 165). The file name
extension is .cfh.

Assigning Bitmaps
Each object can be represented by device-type-specific bitmaps in the detail view.
The graphical representation of a device in detail views and the view in operating
status Normal and Failure from the superordinate object is defined in a dialog
accessible via the context menu of the appropriate object class.

170 3BDD012902R4101
Section 6 Configuring an FF Network Assigning Bitmaps

1. Select FF Device Class object

2. Object > Set Bitmap...
For the dialog refer to Figure 76 and Table 28.

Figure 76. Assign Bitmaps for FF Devices

Table 28. Assign Bitmaps for FF Devices

Dialog element Description

Change A bitmap is assigned or an existing assignment is
changed.
Delete An existing bitmap assignment is deleted.

3BDD012902R4101 171
Inserting FF Objects Section 6 Configuring an FF Network

Table 28. Assign Bitmaps for FF Devices

Dialog element Description

Detail view Device Representation of the field device in the detail view for
Instance object the Device Instance object.
The recommended size for the bitmap to be entered
here is 400 x 300 pixels (width x height), with up to 256
colors. The maximum size of 800 x 600 pixels (256
colors) should not be exceeded. If no bitmap is specified,
for H1 devices a standard graphic will be displayed in the
detail view for the device instance.
Detail view Representation of the field device in the detail view for
superordinate link the superordinate object.
object In each case, a 70 x 40 pixel (width x height) bitmap can
be entered with up to 256 colors. If no bitmap is
specified, a standard display is presented.

When a bitmap is assigned, the bitmap file is stored in directory

<fbbff_install_dir>\bitmaps.
When a device is imported, bitmap files are assigned automatically if the
necessary information is contained in the capabilities file and if the bitmap files
are located in the same directory as the capabilities file.
Bitmap files are not stored and distributed in the project, i.e. they are also not loaded
along with the project onto an Process Portal A PC.

Inserting FF Objects
For the configuration of an FF network FF objects are inserted in the
FF Object Editor structure.

Insert HSE Subnet Object

Below the root object FF Network an HSE Subnet object can be inserted.
1. Select FF Network object

172 3BDD012902R4101
Section 6 Configuring an FF Network Insert HSE Host Object (HSEHostCI860)

2. Edit > Insert

3. Select HSE Subnet object

Insert HSE Host Object (HSEHostCI860)

Below an HSE Subnet object an HSE Host object (HSEHostCI860) can be inserted.
1. Select HSE Subnet object
2. Edit > Insert
3. Select HSE Host object (HSEHostCI860)

Insert Linking Device Module (HSE Device Instance Object)

Below an HSE Subnet object a linking device module (HSE Device Instance object)
can be inserted.
1. Select HSE Subnet object
2. Edit > Insert
3. Select device type
4. Click OK
For inserting an HSE Device Instance object, the types of devices are available
which are present in the HSE device library.
Refer to Expanding FF Libraries on page 165.

Insert H1 Link Object

Below a linking device module (HSE Device Instance object), H1 Link objects can
be inserted. The maximum number of possible H1 Link objects depends on the type
of the used linking device module. The ABB FF Linking Device LD 800HSE
supports four H1 links.
1. Select HSE Device Instance object
2. Edit > Insert
3. Select an H1 Link object

3BDD012902R4101 173
Insert H1 Schedule Object Section 6 Configuring an FF Network

4. Select link number (1…n)

When The H1 Link object is inserted, an H1 Schedule object is automatically
inserted in the FF Object Editor structure below the newly-inserted object.

Insert H1 Schedule Object

It is not possible to explicitly insert an H1 Schedule object to the FF Object Editor
structure, as this is carried out automatically when the higher-level H1 Link object is
inserted.

Insert FF Application Object

Below an H1 Schedule object, FF Application objects can be inserted.
1. Select H1 Schedule object
2. Edit > Insert
3. Select FF Application object

Insert H1 Device Instance Object

Below the H1 Link object an H1 Device Instance object can be inserted.
1. Select an H1 Link object
2. Edit > Insert
3. Select device type
4. Click OK

For inserting an H1 Device Instance object, the types of devices are available
which are present in the H1 device library.
Refer to Expanding FF Libraries on page 165.

Insert OPC Gateway Object

Below the root object FF Network one or two OPC gateway stations can be inserted.
Are two OPC gateways configured, then these are used for a redundant coupling to
an OPC client, e.g. Operate IT.
1. Select FF Network object.

174 3BDD012902R4101
Section 6 Configuring an FF Network View of FF Object Instances

2. Edit > Insert

3. Enter name of OPC Server FF object

View of FF Object Instances

Detail View of the HSE Subnet Object
The detail view of the HSE Subnet objects shows the devices on the HSE subnet in
the form of 70 x 40 pixel bitmaps. Refer to Figure 77. If no bitmap has been
assigned to the HSE device class, then the standard display for an FF device is
shown. The tag name is shown for the HSE subnet. For each HSE device the most
important data such as tag name, module type and configured IP address are
displayed. Additional information can be found in the parameter input dialog for the
object.

3BDD012902R4101 175
Detail View of the HSE Device Instance Object Section 6 Configuring an FF Network

Select an HSE Subnet object from the tree view.

Figure 77. Detail View of the HSE Subnet Object

Detail View of the HSE Device Instance Object

The detail view of the HSE Device Instance object shows the HSE device and the
inserted H1 links. Refer to Figure 78. The most important data for the HSE device –
such as tag name, module type, brief description and configured IP address – are
displayed for the HSE device.
To obtain a realistic representation of the HSE device a bitmap can be assigned to
the HSE device class. If no bitmap has been assigned, then no graphic will be
displayed in the detailed view.

176 3BDD012902R4101
Section 6 Configuring an FF Network Detail View of the HSE Host Object

Select an HSE Device Instance object from the tree view.

Figure 78. Detail View of the HSE Device Instance Object

Double-click on an inserted H1 link, the program will branch to that H1 link. If you
double-click on an H1 link that has not yet been inserted, then the link concerned
will be inserted.

Detail View of the HSE Host Object

The detail view for the HSE Host object shows the FOUNDATION Fieldbus HSE
communication interface of the IEC 61131 controller. Refer to Figure 79. The most
important data such as tag name and configured IP address are displayed.

3BDD012902R4101 177
Detail View of the H1 Link Object Section 6 Configuring an FF Network

Select an HSE Host object (HSEHostCI860) from the tree view.

Figure 79. Detail View of the HSE Host Object

Detail View of the H1 Link Object

The detail view of the H1 Link object shows the devices on the H1 link in the form
of 70 x 40 pixel bitmaps. Refer to Figure 80. If no bitmap has been assigned to the
device class, then a standard display for an FF device is shown. The tag name and
H1 link address are shown for the H1 link. For each device the most important data
such as tag name, vendor, device type, device ID and bus address are displayed.
Additional information can be found in the parameter input dialog for the object.

178 3BDD012902R4101
Section 6 Configuring an FF Network Detail View of the H1 Link Object

Select an H1 Link object from the tree view.

Figure 80. Detail View of the H1 Link Object

3BDD012902R4101 179
Detail View of the H1 Schedule Object Section 6 Configuring an FF Network

Detail View of the H1 Schedule Object

The detail view of the H1 Schedule object shows the Schedule Editor. Refer to
Figure 81 and Structure of the Graphical Display on page 334.

Figure 81. Detail View of the H1 Schedule Object

Select an H1 Schedule object from the tree view.

180 3BDD012902R4101
Section 6 Configuring an FF Network Detail View of the FF Application Object

Detail View of the FF Application Object

The detail view of the FF Application object shows the FF Application Editor. Refer
to Figure 82 and Configuration Interface of the FF Application Editor on page 303.

Figure 82. Detail View of the FF Application Object

Select an FF Application object from the tree view.

3BDD012902R4101 181
Detail View of the H1 Device Instance Object Section 6 Configuring an FF Network

Detail View of the H1 Device Instance Object

The detail view of the H1 Device Instance object displays more detailed information
on the field device. Refer to Figure 83.

Figure 83. Detail View of the H1 Device Instance Object

These include tag name, vendor, device type, device ID and bus address. The
instances of resource blocks, transducer blocks and function blocks provided by this
device instance are shown along with this information. For each instance of a block,
block ID, OD index, block type and tag name are shown. Function block instances,
which are not yet being used in an FF Application, are displayed in gray.
In order to achieve a realistic representation of the device, a bitmap can be assigned
to the device class. If no bitmap has been assigned, then the standard display for an
FF device is shown.

182 3BDD012902R4101
Section 6 Configuring an FF Network Detail View of the H1 Device Instance Object

Select an H1 Device Instance object from the tree view or the detail view of the H1
link.
Create FF Function Block Instance
There are FF devices for which the FF function block instances must first be
created. This is performed in the detail view for the Device Instance object. Refer to
Figure 84 and Table 29.

Figure 84. Create FF Function Block Instance

Table 29. Create FF Function Block Instance

Dialog element Description

Block type The type of FF function block
Created instances Number of instances of the function block type concerned that
have already been created
Available instances Maximum number of instances of the function block type
concerned that can still be created. This parameter is based on
the total resources available in the field device for creating
function blocks. When a function block is created, these
resources are reduced. Therefore as a rule, the maximum
number of additional function blocks of other types that can be
created is also reduced.

3BDD012902R4101 183
Detail View of the H1 Device Instance Object Section 6 Configuring an FF Network

1. Context menu in the detail view of the device instance object > Create
function block...
2. Select function block type from the list > Create
3. Create further function blocks if required
4. Close
Delete FF Function Block Instance
This action is only available for FF devices for which the FF function block
instances must be created in the manner described previously. In the Device
Instance object detail view for such devices an unused function block instance
(displayed in gray) can be deleted.
1. Context menu of an unused function block instance
2. Delete
The function block instance in the field device is deleted. The resources are
released.
Set Parameter Values for FF Function Block Instance
Function block instances that are already in use (displayed in black) can have
parameter values set via the context menu.
1. Context menu of a used function block instance.
2. Parameters
For details of the parameter setting process refer to FF Block Instance Object on
page 234.

184 3BDD012902R4101
 Section 7 Parameter Settings

HSE Device Library Object

The name of the HSE device library is displayed in the parameter input mask. This
parameter cannot be modified. Refer to Figure 85 and Table 30.

Figure 85. Parameters HSE Device Library

3BDD012902R4101 185
H1 Device Library Object Section 7 Parameter Settings

Table 30. Parameters HSE Device Library

Dialog element Description

Reload Standard This button can be used to reload the standard
Dictionary dictionary provided by the Fieldbus Foundation. The
standard dictionary contains text in several languages
for objects that are defined in the FF specification. The
standard dictionary contains, for example, the names for
inputs and outputs of the FF standard function blocks
and the names and help texts for block parameters.

Since the standard dictionary is automatically loaded when a new project is

created, the dictionary only needs to be reloaded if an updated version is to be
used.

H1 Device Library Object

The name of the H1 device library is displayed in this parameter input mask. This
parameter cannot be modified. Refer to Figure 86 and Table 31.

Figure 86. Parameters H1 Device Library

186 3BDD012902R4101
Section 7 Parameter Settings FF Block Library Object

Table 31. Parameters H1 Device Library

Dialog element Description

Reload Standard This button can be used to reload the standard
Dictionary dictionary provided by the Fieldbus Foundation. The
standard dictionary contains text in several languages
for objects that are defined in the FF specification. The
standard dictionary contains, for example, the names for
inputs and outputs of the FF standard function blocks
and the names and help texts for block parameters.

Since the standard dictionary is automatically loaded when a new project is

created, the dictionary only needs to be reloaded if an updated version is to be
used.

FF Block Library Object

The name of the block library is displayed in this parameter input mask. This
parameter cannot be modified. Refer to Figure 87.

Figure 87. Parameters Block Library

3BDD012902R4101 187
FF Block Class Object Section 7 Parameter Settings

FF Block Class Object

The header area of the parameter dialog contains the following data, refer to
Figure 88 and Table 32.

Table 32. Header Area of the Parameter Dialog

Dialog element Description

Type Name of the FF block class (max. 16 characters). This
name is defined during the FF device import, and can be
changed later. It must be unique within the project. This
name is displayed in the block library and as a type
name for a block instance in the FF Application among
other places.
Comment Free comment text (max. 42 characters).

Initial Instance Parameters Tab

A complete set of initial instance parameters is stored on the FF Block Class object.
When a new block instance is created these parameter values will be assigned by
default.
The initial instance parameter values for the FF block class are set using this tab.
The layout and contents of the tab correspond to those of the FF block instance.
Refer to Parameters Tab on page 236.

188 3BDD012902R4101
Section 7 Parameter Settings Initial Instance Parameters Tab

The download column, OPC access and OPC short name represent a special feature
of the parameter dialog as they can only be edited at the function block class. It is
not possible to edit them at the block instance. Refer to Figure 88 and Table 33.

Figure 88. Initial Instance Parameters Tab

3BDD012902R4101 189
Initial Instance Parameters Tab Section 7 Parameter Settings

Table 33. Initial Instance Parameters Tab

Dialog element Description

Download This entry determines whether the parameter is taken
into account when the device configuration data is
loaded.
The parameter is not downloaded to the FF device.
A present parameter value is written to the FF
device, provided that it is a writable parameter. If no
parameter value is present in the value field, this
parameter is not downloaded with the device
configuration data.
In the case of a structural element the selection state of
the data structure is displayed.
All elements of the data structure are selected for
downloading.
Some elements of the data structure are selected
for downloading.
No element of the data structure is selected for
downloading.
OPC Access This entry defines whether the parameters can be
accessed via an OPC Server.
No access to the parameter via an OPC Server.
Access to the parameter via an OPC Server is
possible. For further details refer to Enabling
Parameters of the FF Blocks for OPC Access on
page 261.
OPC Short name If a value is entered here, the parameter is addressed by
the OPC Server not via the component name from the
Name column, but via the name entered here. This
name must be unique within an object. For further
details refer to Enabling Parameters of the FF Blocks for
OPC Access on page 261.
Reset The parameter values in the grid are reset to the block-
type-unspecific default values or to user-defined block-
type-specific values. For further details refer to
Managing Parameter Value Sets on page 194.

190 3BDD012902R4101
Section 7 Parameter Settings Initial Instance Parameters Tab

Reset to Default Values

Block-type-unspecific default values can be assigned to the parameters in the grid.
1. Button Reset
2. Radio button: Default values, block-type-unspecific

When a Save is subsequently performed the parameter values in the grid are
stored as the values of the initial instance parameters for the function block class.

Reset to User-Defined Values

The values from a user-defined block-type-specific parameter set can be assigned to
the parameters in a grid.
1. Button Reset
2. Radio button: User-defined values, block-type-specific
3. Select the required set of parameter values from the list.
4. The Preview changes check box can be set if desired. The parameters in the
grid that will be altered during the reset will be shown in list format. Individual
parameter values can be deselected in the list.

When a Save is subsequently performed the parameter values in the grid are
stored as the values of the initial instance parameters for the function block class.

Save Values as a User-Defined Parameter Value Set

The current parameter value set can be saved as a user-defined block-type-specific
parameter value set through the context menu.
1. Context menu Store parameter value set
2. Radio button: User-defined values, block-type-specific
3. Choose a user-defined parameter value set from the list (the existing parameter
value set is overwritten) or specify a new name for a user-defined parameter
value set (a new parameter value set will be added).

If the tab is left via Cancel, the parameter value sets that have been stored since
opening the tab will be lost.

3BDD012902R4101 191
Initial Instance Parameters Tab Section 7 Parameter Settings

Exporting Parameter Values

Context menu Export marked (if an individual parameter or block of parameters is
marked)
or
1. Export all parameters (if no parameters are marked)
2. Specify file name.

Importing parameter values

1. Context menu Import
2. Select file from list.
3. A list of parameter values which will be changed in the grid when the import is
carried out is shown. Parameters can be individually deselected in this list.

192 3BDD012902R4101
Section 7 Parameter Settings Block Info Tab

Block Info Tab

The table in the parameter dialog lists the device types that support this block type.
Refer to Figure 89 and Table 34.

Figure 89. Block Info Tab

3BDD012902R4101 193
Managing Parameter Value Sets Section 7 Parameter Settings

Table 34. Block Info Tab

Dialog element Description

Device type Name of the H1 device class that supports this FF block
class. This means that an instance of this block may be
assigned to a device of the given type.
Execution time Time taken for execution of the block.
Profile Profile on which the block definition is based. Among
other things the profile determines whether a block is
standard, enhanced or manufacturer-specific. The
profile number for standard function blocks is assigned
by the Fieldbus Foundation.
Revision Revision of the block profile. Among other things, this
determines whether a function block is standard or
enhanced.
Value Sets... The user-defined parameter value sets for the block
class are listed, and the parameter values are shown for
the selected set of values. It is possible to delete
individual parameter value sets.
Restrictions... If the device description contains descriptive elements
that are not supported by the current version of Fieldbus
Builder FF, these will be indicated. Users may decide to
use the block class, but they must take responsibility for
this decision. During the configuration and
commissioning phases special handling procedures may
need to be employed for the elements listed here.

Managing Parameter Value Sets

Fieldbus Builder FF allows more than one parameter value set to be managed per
block type. Value sets that are permanently stored in Fieldbus Builder FF and
default and example value sets from the Capabilities File cannot be modified by the
user. But users have the opportunity to create their own parameter value sets and to
save these as user-defined parameter value sets. User-defined parameter value sets
may be overwritten by the user.

194 3BDD012902R4101
Section 7 Parameter Settings Managing Parameter Value Sets

Block parameters can be edited on both the FF Block Class object and the FF Block
Instance object. The current parameter values for the object can be saved as a user-
defined parameter value set using the Store values parameter value set item from the
context menu.
Fieldbus Builder FF supports the following parameter value sets:
• Default values, block-type-unspecific
One parameter value set; non-modifiable.
This minimal parameter value set provided by the system contains block-type-
unspecific default values for a small number of selected block parameters.
These values have proved to be useful initial values in the commissioning of a
variety of FF projects. This parameter value set is available for selection on the
FF Block Class object and the FF Block Instance object.
The following parameter value sets are block-type-specific. They do not refer to a
device class.
• Initial instance parameter values, block-type-specific
One parameter value set; modifiable by the user.
This is the current parameter value set for the FF block class. When a new
block instance is created these parameter values will be assigned by default.
This set of parameter values can be edited on the Initial instance parameters
tab; refer to Initial Instance Parameters Tab on page 188. It is prefilled with the
default values, block-type-unspecific.
• User-defined values, block-type-specific
0 .. n parameter value sets, modifiable by the user.
These user-managed parameter value sets are available for selection on the FF
Block Class object and the FF Block Instance object. A new set of user-defined
values, block-type-specific can be created on both the FF Block Class object
and the FF Block Instance object using the Store parameter value set item from
the context menu. Refer to Initial Instance Parameters Tab on page 188 and
Parameters Tab on page 236. The user can view and delete these parameter
value sets on the Block Info tab for the FF Block Class object, refer to Block
Info Tab on page 193.
Parameter value sets that are represented in angel brackets, e. g. <AI Default
Values>, are stored at the superordinate block class.

3BDD012902R4101 195
Managing Parameter Value Sets Section 7 Parameter Settings

The following parameter value sets with additional reference to a device class are
available only on FF Block instances that are assigned to devices. Access to a
parameter value set of this category is only possible if the block type and the
assigned device type agree with the values for the current block instance object.
• Vendor defined values, device-type-specific
0 .. n parameter value sets, non-modifiable.
These non-modifiable parameter value sets contain default values and example
values from the Capabilities File.

Defaults and example values from the Capabilities File are assigned to the block
parameters described in the DD using the parameter names. Therefore, defaults
and example values are only available for those block parameters for which these
values are listed in the Capabilities File under the parameter name used in the
DD. The block parameter names used in the DD appear in the tabs Initial Instance
Parameters for the block class and Parameters for the block instance.
• User-defined values, device-type-specific
0 .. n parameter value sets, modifiable by the user.
These user managed parameter value sets can be created in the Parameters tab
of an FF Block Instance object that is assigned to a device using the Store
parameter value set item from the context menu. Refer to Parameters Tab on
page 236. This type of parameter value set is available for selection on the
corresponding FF Block instances of the same device type.

A parameter value set can also contain empty entries (where no value is entered
for a parameter). When the device configuration data is loaded, these parameters
are ignored.
The entry in the Download column of the parameter table determines whether a
parameter value that is entered is used when the device configuration data is
loaded. Refer to Parameters Tab on page 236.

196 3BDD012902R4101
Section 7 Parameter Settings H1 Device Class Object:

To achieve a reproducible configuration state in a field device it is recommended

that Reset factory values be performed before loading the device configuration
data in the field device. When the device configuration data produced by the
application is loaded subsequently, only those block parameters should be loaded
whose values vary from the factory values following a factory reset. Leaving the
Value field blank and/or editing the entry in the Download column of the block
parameters list are suitable ways of controlling the loading of block parameters.
Refer to Parameters Tab on page 236.
Parameter values can be exported and imported on the FF Block Class object and
the FF Block Instance object. A CSV file is generated when exporting. A CSV file
generated in this way can later be used as the source file for importing. Refer to
Initial Instance Parameters Tab on page 188 and Parameters Tab on page 236.

H1 Device Class Object:

The header area of the parameter dialog contains the following data, refer to
Figure 90 and Table 35.

Table 35. Header Area of the Parameter Dialog

Dialog element Description

Type Name of the H1 device class (max. 16 characters). This
name is defined during the FF device import, and can be
changed later. It must be unique within the project. This
name is displayed, among other places, in the H1 device
library.
Comment Free comment text (max. 42 characters)

3BDD012902R4101 197
Device Info Tab Section 7 Parameter Settings

Device Info Tab

Refer to Figure 90 and Table 36.

Figure 90. Device Info Tab

Table 36. Device Info Tab

Dialog element Description

Manufacturer Name of device manufacturer from the Capabilities File.
Model Name of device model from the Capabilities File.
Device Name Name of device from the Capabilities File.
Device Revision Revision of device from the Capabilities File.

198 3BDD012902R4101
Section 7 Parameter Settings Download Adjustment Tab

Download Adjustment Tab

Refer to Figure 91.

Figure 91. Download Adjustment Tab

For some FF devices download of configuration data may fail when applying the
standard download sequence. If download of configuration data repeatedly fails for
a device type, you may try to select one of the download adjustment options on this
tab:
• Download loads startlist before parameters.
• Download must not use “Clear VCR List” command.
• Download repeats the LAS write service until it succeeds.

3BDD012902R4101 199
Capabilities File Tab Section 7 Parameter Settings

Capabilities File Tab

This tab contains data for identifying the Capabilities File. Refer to Figure 92 and
Table 37.

Figure 92. Capabilities File Tab

Table 37. Capabilities File Tab

Dialog element Description

Description Descriptive text for the Capabilities File.
File Version Version of the Capabilities File.
File Date Creation date of the Capabilities File.

200 3BDD012902R4101
Section 7 Parameter Settings Capabilities File Tab

Table 37. Capabilities File Tab

Dialog element Description

View Info... The content of the Capabilities File is displayed in a tree
structure.
Parameter Value The device-type-specific parameter value sets for the
Sets... blocks are listed in a tree structure. These include the
manufacturer-defined value sets from the Capabilities
File (example values, default values) and user-defined
value sets. The parameter values for the selected value
set are displayed. It is possible to delete individual
parameter value sets.

For importing an up-to-date revision of the Capabilities File refer to Update

Capabilities File on page 204.

3BDD012902R4101 201
Device Description Tab Section 7 Parameter Settings

Device Description Tab

This tab contains identification data from the device description. Refer to Figure 93
and Table 38.

Figure 93. Device Description Tab

Table 38. Device Description Tab

Dialog element Description

Manufacturer ID Internationally unique identification number for the
device manufacturer. The manufacturer IDs are
administered by the Fieldbus Foundation.
Device Type ID Identification number for the device type. The device
type ID is assigned by the device manufacturer.
Device Revision Revision of the device.
DD Revision Revision of the device description.
View Contents The essential content of the device description (DD) is
shown in a tree structure.

202 3BDD012902R4101
Section 7 Parameter Settings VCR Info Tab

VCR Info Tab

This tab contains the pre-defined communication relationships (VCR – Virtual
Communication Relationship) in the device. Refer to Figure 94.

Figure 94. VCR Info Tab

3BDD012902R4101 203
Block Info Tab Section 7 Parameter Settings

Block Info Tab

This tab contains a list of the blocks provided by the device with their most
important identification data. Refer to Figure 95.

Figure 95. Block Info Tab

Context Menu

Update Capabilities File

For importing an up-to-date revision of the Capabilities File proceed as follows:
1. Select H1 Device Class object
2. Object > Update Capabilities File...
3. Select Capabilities File

When the Capabilities File is updated, the device instances and associated block
instances become implausible.

204 3BDD012902R4101
Section 7 Parameter Settings HSE Device Class Object

Set Bitmap
For configuring the graphical representation of device instances proceed as follows:
1. Select H1 Device Class object
2. Object > Set Bitmap...
For details on the assignment dialog refer to Assigning Bitmaps on page 170.

HSE Device Class Object

The header area of the parameter dialog contains the following data: Refer to
Figure 96 and Table 39.

Table 39. Header Area of the Parameter Dialog

Dialog element Description

Type Name of the HSE device class (max. 16 characters).
This name is defined during the FF device import, and
can be changed later. It must be unique within the
project. This name is displayed in the HSE device library
among other places.
Comment Free comment text (max. 42 characters).

3BDD012902R4101 205
Device Info Tab Section 7 Parameter Settings

Device Info Tab

Refer to Figure 96 and Table 40.

Figure 96. Device Info Tab

Table 40. Device Info Tab

Dialog element Description

Manufacturer Name of device manufacturer from the Capabilities File.
Model Name of device model from the Capabilities File.
Device Name Name of device from the Capabilities File.
Device Revision Revision of device from the Capabilities File.
Device Type ID Identification number for the device type. The device
type ID is assigned by the device manufacturer.

206 3BDD012902R4101
Section 7 Parameter Settings Capabilities File Tab

Capabilities File Tab

This tab contains data for identifying the Capabilities File. Refer to Figure 97 and
Table 41.

Figure 97. Capabilities File Tab

Table 41. Capabilities File Tab

Dialog element Description

Description Descriptive text for the Capabilities File.
File Version Version of the Capabilities File.
File Date Creation date of the Capabilities File.
View Info... The content of the Capabilities File is displayed in a tree
structure.

For importing an up-to-date revision of the Capabilities File refer to Update

Capabilities File on page 209.

3BDD012902R4101 207
VCR Info Tab Section 7 Parameter Settings

VCR Info Tab

This tab contains the pre-defined communication relationships (VCR – Virtual
Communication Relationship) in the device. Refer to Figure 98.

Figure 98. VCR Info Tab

208 3BDD012902R4101
Section 7 Parameter Settings Revisions Tab

Revisions Tab
This tab contains the revisions of the virtual field devices (VFD – Virtual Field
Device) in the HSE device. Refer to Figure 99.

Figure 99. Revisions Tab

Context Menu

Update Capabilities File

For importing an up-to-date revision of the Capabilities File proceed as follows:
1. Select HSE Device Class object
2. Object > Update Capabilities File...
3. Select Capabilities File

When the Capabilities File is updated, the device instances in the project become
implausible.

3BDD012902R4101 209
FF Network Object Section 7 Parameter Settings

Set Bitmap
For configuring the graphical representation of device instances proceed as follows:
1. Select HSE Device Class object
2. Object > Set Bitmap...
For details on the assignment dialog refer to Assigning Bitmaps on page 170.

FF Network Object
The FF Network object is the root node of the project. Besides the HSE Subnet
object up to two OPC Server FF objects can be present below this root object.

HSE Subnet Object

FF Signals Tab
This tab shows the FF signal list. It contains all the FF signals for the HSE subnet
and the lower-level H1 links, which are communicated cyclically. For each FF
signal the signal name, the data type (analog, discrete or bitstring), source

210 3BDD012902R4101
Section 7 Parameter Settings HSE Subnet Settings Tab

information, usage (HSE + H1 or H1), the group and an optional comment are
displayed. Refer to Figure 100.

Figure 100. FF Signals Tab

For details of the FF signal list and the parameters that can be defined for it, refer to
FF Signal List on page 288.

HSE Subnet Settings Tab

The cycle time used to update the HSE Live List is set on this tab. The IP address
and the UDP port for Publish/Subscribe multicasting can also be modified, and the

3BDD012902R4101 211
HSE Subnet Settings Tab Section 7 Parameter Settings

system can be configured to detect a disconnection. Refer to Figure 101 and

Table 42.

Figure 101. Settings Tab

Table 42. Settings Tab

Dialog element Description

Device Annunciation
HSE Repeat Time Cycle time used for updating the HSE Live List.

212 3BDD012902R4101
Section 7 Parameter Settings HSE Subnet Settings Tab

Table 42. Settings Tab

Dialog element Description

Publish Subscribe The defaults should generally be used for the
Multicast parameters in this group. Adjustments only need to be
made if different HSE networks from the same project or
different projects are to coexist on one physical Ethernet
network.
ABB currently does neither recommend nor
support to run several HSE subnets on the
same physical Ethernet network.
Base IP Address First IP address used for Publish/Subscribe Multicasting
on the HSE subnet. The additional Multicast-IP
addresses used in this HSE subnet are produced by
incrementing this base IP address.
Different HSE subnets on the same physical Ethernet
network must have different Multicast IP addresses.
The value range for the Multicast IP addresses is
224.0.0.36 to 238,255,255,255.
ABB currently does neither recommend nor
support to run several HSE subnets on the
same physical Ethernet network.
UDP Port Number of the UDP port for Publish/Subscribe
Multicasting on the HSE network.
Different HSE subnets on the same physical Ethernet
network must have different UDP port numbers. The
value range is 1095 to 1104.
ABB currently does neither recommend nor
support to run several HSE subnets on the
same physical Ethernet network.

3BDD012902R4101 213
HSE Subnet Settings Tab Section 7 Parameter Settings

Table 42. Settings Tab

Dialog element Description

Max. No. of Signal In the case of automatic assignment of signals to signal
Groups groups, resource conflicts in the HSE devices may be
triggered via this parameter. It limits the number of
signal groups on the HSE subnet introduced during
automatic assignment.
The value of this parameter should be adjusted to the
capabilities of the HSE devices. Refer to Structure of the
FF Signal List on page 289.
If after automatic assignment for one or more HSE
devices, the number of possible Send/Receive sessions
is exceeded, the value of this parameter should be
reduced and automatic assignment should be repeated.
Signal Republishing
Stall Count This parameter is used to configure the detection of a
disconnection for all subscribers on HSE subnet and
subordinate H1 links. This parameter defines the
maximum number of consecutive frozen input values
which are allowed to occur before a disconnection is
detected.
Network Configuration
Subnet Mask The subnet mask defines the limits of the HSE subnet.
HSE communication is only possible within the limits of
the HSE subnet.
Gateway Address The gateway address must be a valid, unique IP
address for the HSE subnet.

214 3BDD012902R4101
Section 7 Parameter Settings HSE Subnet Settings Tab

Table 42. Settings Tab

Dialog element Description

The gateway address should be the HSE
network interface address of the Connectivity
Server that runs the OPC Server FF for this
HSE subnet.
A valid IP address must be entered here even if
there is no physical gateway in the HSE subnet.
In this case an IP address should be entered
which is not being used on this HSE subnet by
any physically existing subscriber.

3BDD012902R4101 215
HSE Host Object, HSEHostCI860 Section 7 Parameter Settings

HSE Host Object, HSEHostCI860

Communication Tab
Allows the IP parameters to be set which the IEC 61131 controller uses as the
subscriber on the HSE subnet. Refer to Figure 102.

Figure 102. Communication Tab

216 3BDD012902R4101
Section 7 Parameter Settings Published/Subscribed Tab

Table 43. Communication Tab

Dialog element Description

IP Address The IP address is used for identifying the HSE host and
forms the basis for all connection-oriented
communication with the HSE host. The address entered
here is loaded to the CI860 module via Control Builder
M.
Both the IP address of the HSE host and the IP
address of the redundancy module must be
valid, unique IP addresses from the HSE
subnet.
IP Address of red. Unit The IP address of the redundancy module is entered
here.
Redundant unit exists This parameter is used to configure the HSE host as a
redundancy pair.
No redundancy.
Redundancy.

Published/Subscribed Tab
The mapping of FF signals to IEC 61131 I/O channels is configured on this tab. It
contains all the signal channel mappings for the HSE network. For each signal
channel mapping the Channel, the Data type (analog or discrete), the direction of the
data transfer (FF IEC 61131 or IEC 61131 FF), the FF signal name to be
mapped, the Cycle Time for Publishing (Publish) and an optional comment are
displayed. Refer to Figure 103.
For the configuration details of data exchange between an IEC 61131 application on
the AC 800M and the FF network refer to Mapping of FF Signals to Channels for

3BDD012902R4101 217
Published/Subscribed Tab Section 7 Parameter Settings

the HSE Host Object on page 296 and to the manual “800xA - Control and I/O
FOUNDATION Fieldbus, Engineering and Configuration” (3BDD012903) .

Figure 103. Published/Subscribed Tab

218 3BDD012902R4101
Section 7 Parameter Settings HSE Device Instance Object

HSE Device Instance Object

Communication Tab
On this tab, parameters are set for the addresses necessary for HSE device
communication and redundancy settings are defined. Refer to Figure 104 and
Table 44.

Figure 104. Communication Tab

3BDD012902R4101 219
HSE Device Instance Object Section 7 Parameter Settings

Table 44. Communication Tab

Dialog element Description

Device type Device type of the HSE device from the device
description.
Base Link Address The link address of the first H1 link of the FF linking
device. The link addresses of the other H1 links of the
FF linking devices are produced by incrementing this
base link address.
The value range is 4096 to 65276.
The base link address should be chosen such
that the link addresses of the H1 links are
unique within the HSE subnet.
IP address The IP address set on the HSE device is entered here. It
is used for identifying the HSE device, and forms the
basis for all the connection-based communication with
this device.
Both the IP address of the HSE device and the
IP address of the redundancy module must be
valid, unique IP addresses from the HSE
subnet.
Calculated HSE frames Here the number of HSE frames per second for the
per sec. linking device is displayed on the basis of the
configured, republished signals. This value should not
exceed a maximum value determined by the linking
device. Refer to the user documentation for details
relating to the linking device.
Redundancy
IP address of red. Unit The IP address set on the redundancy partner is entered
here.
Redundant unit exists This parameter is used to configure the HSE device as a
redundancy pair.
No redundancy.
Redundancy.

220 3BDD012902R4101
Section 7 Parameter Settings H1 Link Object

H1 Link Object
H1 Settings Tab
Communication parameters and system management parameters for the H1 link are
set on this tab. It is not necessary, as a rule, to change the default values. However, it
may be expedient to change individual values in order to optimize communication.
Refer to Figure 105 and Table 45.
A knowledge of the basics of FF network management and FF system
management is a prerequisite for making changes to the default values. Refer to
the FF Specifications Network Management (FF-801) and System Management
(FF-880). The telegram structure is described in the specification IEC 61158-1 to
5, Digital data communications for measurement and control - Fieldbus for use
in industrial systems.

3BDD012902R4101 221
H1 Link Object Section 7 Parameter Settings

Figure 105. H1 Settings Tab

Table 45. H1 Settings Tab

Dialog element Description

Some of the values shown on the tab are multiples of
the bit transmission time tbit, the byte transmission
time tbyte or the slot time tslot.
tbit = 32µs The bit transmission time is the time taken to transfer
one bit. When a transmission rate of 31.25 kilobits
per second is used in the H1 link, this time is 32
microseconds.

222 3BDD012902R4101
Section 7 Parameter Settings H1 Link Object

Table 45. H1 Settings Tab

Dialog element Description

tbyte = 256µs The byte transmission time is the time taken to
transfer one byte. The value is eight times the bit
transmission time.
tSlot The slot time is a configuration parameter of the link
(see below).
Link Settings The communication parameters compiled in this
group are known to every bus subscriber on the H1
link.
SlotTime This parameter of the H1 link must be greater than
the greatest minimum required slot time for any of
the devices being operated in the H1 link. The value
to be set depends on the reaction time of the devices
being used.
The value of this parameter is also used by every
device in the H1 link as the basis for calculating
monitoring times. These are specified as a multiple
of the slot time. Link master devices use the slot time
to determine the length of time they monitor the link
for inactivity before trying to take over the LAS role.
In the case of link master devices with consecutive
addresses, the inactivity monitoring times differ by
exactly one slot time.
The value range is (1 to 4095) * tbyte.
MaxResponseDelay This parameter for the H1 link must be greater than
the greatest response delay time on any of the
devices being operated in the H1 link with acyclical
communication. The maximum response delay time
of a device is the time between the end of receiving a
request message and the beginning of sending the
immediately following response message.
The value range is (1 to 11) * tSlot.

3BDD012902R4101 223
H1 Link Object Section 7 Parameter Settings

Table 45. H1 Settings Tab

Dialog element Description

MinInterPduDelay This parameter specifies the minimum interval
between two messages in the H1 link. It must be at
least as great as the greatest value for any of the
devices being operated in the H1 link.
The value range is (0 to 120) * tbyte.
If the value chosen for this parameter is
greater than the product of
MaxResponseDelay and SlotTime, then no
communication is possible in the H1 link
concerned.
MaxSchedulingOverhead This parameter determines the maximum
permissible delay when the schedule is executed by
LAS. It is used for creating the schedule.
The value range is (0 to 63) * tbyte.
PerDlpduPhlOverhead This parameter specifies the time interval between
two messages caused by the physical layer. It takes
into account the transfer times for preamble, start
flag, end flag, PreambleExtension and
PostTransGapExtension.
The value range is (2 to 63) * tbyte.
This value cannot be edited. If the values of
PreambleExtension or
PostTransGapExtension are altered, it is
adjusted automatically.

224 3BDD012902R4101
Section 7 Parameter Settings H1 Link Object

Table 45. H1 Settings Tab

Dialog element Description

TimeSyncClass This parameter determines the quality of time
synchronization in the H1 link. The time
synchronization class must be selected such that all
devices in the H1 link support at least that time
synchronization class, if not one with a higher
resolution.
This parameter must be set to a suitable
value according to the parameter
TimeDistributionPeriod.
PreambleExtension Each transmission contains a preamble sequence
eight bits in length. This parameter allows the
preamble to be increased by a further 0 to 7 8-bit
sequences.
The value range is (0 to 7) * tbyte.
Increasing this value leads to an increase in
PerDlpduPhlOverhead.

PostTransGapExtension Following every transmission, a gap of four bit

transmission times is observed. This parameter
allows the gap to be increased by a further 0 to 7 4-
bit transmission times.
The value range is (0 to 7) * 4* tbit.
Increasing this value leads to an increase in
PerDlpduPhlOverhead.

MaxInterChanSignalSkew Devices that receive data via several ports from the
same H1 link must take into account a maximum
time shift (signal skew) of five-bit transmission times.
This parameter allows the maximum permissible
time shift for the H1 link to be increased by 0 to 7 4-
bit transmission times.
The value range is (0 to 7) * 4* tbit.

3BDD012902R4101 225
H1 Link Object Section 7 Parameter Settings

Table 45. H1 Settings Tab

Dialog element Description

ThisLink This parameter contains the link address of the H1
link.
The H1 link address must be unique within
the HSE subnet.
The H1 link address is set using the base
link address of the FF linking device in the
parameter dialog for the HSE device (refer
to HSE Device Instance Object on
page 219).
Proposal This button can be used to produce a suggestion for
the link settings, based on the capabilities of the
devices configured on this H1 link.
Link Master Settings The Link Master, which handles the role of the LAS,
uses the communication parameters compiled in this
group for controlling the communication in the H1
link.

226 3BDD012902R4101
Section 7 Parameter Settings H1 Link Object

Table 45. H1 Settings Tab

Dialog element Description

FirstUnpolledNodeId This parameter shows the first bus address from a
sequence of consecutive bus addresses, which is
excluded from the regular polling for detecting newly
joined bus subscribers.
In order to detect newly joined bus subscribers
automatically, all bus addresses that are not
contained in the Live List of the LAS are addressed
at regular intervals (polling). With this and one of the
following two parameters, a cohesive range of
addresses can be defined which is not subject to this
polling.
The value range is 20 to 247.
When this parameter is modified, the value
of the parameter
NumConsecUnpolledNodeId is adjusted
automatically. For further details refer to
NumConsecUnpolledNodeId,
LastUnpolledNodeId.
NumConsecUnpolledNodeId This parameter specifies the number of a range of
consecutive bus addresses which are excluded from
the regular polling for detecting newly-added bus
subscribers.
The value range is 0 to 228.
This parameter can only be modified
indirectly using the parameters
FirstUnpolledNodeId and
LastUnpolledNodeId.
As minimizing the range of polled bus
adresses causes more frequent updates of
the Live List, it is recommended to adjust
the range of unpolled bus addresses to the
actual needs of the link.

3BDD012902R4101 227
H1 Link Object Section 7 Parameter Settings

Table 45. H1 Settings Tab

Dialog element Description

LastUnpolledNodeId This parameter specifies the last bus address from a
number of consecutive bus addresses which are
excluded from the regular polling for detecting newly-
added bus subscribers.
The value range is 20 to 247.
When this parameter is modified, the value
of the parameter
NumConsecUnpolledNodeId is adjusted
automatically. Refer to
FirstUnpolledNodeId, and
NumConsecUnpolledNodeId.
DefMinTokenDelegTime In order to perform a token transfer for handling non
cyclical data traffic, at least the length of time
specified in this parameter must be available. If less
time than that is available before the beginning of the
next cyclic data transmission, then the LAS will not
transfer the token before. This parameter should be
set such that short messages can be sent within the
time specified.
The value range is (32 to 32767) * tbyte.
DefTokenHoldTime This parameter defines the length of time that the
LAS initially allows to each device for non-cyclical
data traffic within a token rotation. This parameter
differs from the parameter DefMinTokenDelegTime
in that the time can be distributed over several token
transfers.
The value range is (276 to 65000) * tbyte.

228 3BDD012902R4101
Section 7 Parameter Settings H1 Link Object

Table 45. H1 Settings Tab

Dialog element Description

TargetTokenRotTime This parameter specifies the target upper time limit
for a complete token rotation.
The value range is 1 to 60,000 milliseconds.
When defining this value, the maximum
number of devices being operated in the H1
link and the values of parameters
DefTokenHoldTime and
LinkMaintTokHoldTime should be taken into
account.
LinkMaintTokHoldTime This parameter is used to specify the time that the
LAS uses within a token rotation for maintenance of
the H1 link. This includes the detection of new bus
subscribers and the broadcasting of LAS status and
of the time.
The value range is (292 to 65000) * tbyte.
TimeDistributionPeriod This parameter is used to specify the maximum time
interval between the cyclical time broadcasting
messages (scheduling time) in the H1 link. The value
set must be appropriate for the time synchronization
class selected (refer to TimeSyncClass parameter).
Table 46 shows the relationships.
The value range is 5 to 55,000 milliseconds.
To avoid increasing the load on the bus
unnecessarily, the maximum time interval
for the selected time synchronization class,
which is shown in the right-hand column in
the table should be set.

3BDD012902R4101 229
H1 Link Object Section 7 Parameter Settings

Table 45. H1 Settings Tab

Dialog element Description

MaximumInactivityToClaimL The value of this parameter must be greater than the
asDelay greatest internal delay time of any of the link master
devices being operated in the H1 link.
This delay time for a link master device is the time
interval between the expiration of the inactivity
monitoring time and the sending of the necessary
message for taking over the LAS role.
The value range is (1 to 4095) * tbit.
System Management This group contains the system management
parameters.
T1 (Step Timer) This parameter is used to define the maximum
acknowledgement delay for the SetAddress service.
The value range is (0 to 232-1) * (1/32) ms.
T2 (Set Address Sequence The allocation of a new address, which starts with
Timer) the receipt of a SetAddress message, must be
completed within the time that has been set using
this parameter.
The value range is (0 to 232-1) * (1/32) ms.
T3 (Set Address Wait Timer) When a new address is assigned to a device, it must
report back under the new address on the bus at
least before the expiration of the time set here.
The value range is (0 to 232-1) * (1/32) ms.
PrimaryApTimePublisher This is the address of the device which manages and
broadcasts the application time.

230 3BDD012902R4101
Section 7 Parameter Settings H1 Schedule Object

Table 45. H1 Settings Tab

Dialog element Description

ApClockSyncInterval This parameter is used to define the maximum time
interval between the cyclical distribution telegrams
for the application time in the H1 link.
The value range is 1 to 255 s.
Low priority traffic cycle time This parameter defines the cycle time for the
communication of low-priority FF signals (usage
type: HSE + H1 (LP)) on this H1 link. The macro
cycle for the H1 link is produced from this cycle time
and the cycle times of the FF Application objects.

Table 46. Relationship TimeSyncClass and TimeDistributiuonPeriod

Maximum value for

TimeSyncClass
TimeDistributionPeriod
1 µs 5 ms
10 µs 50 ms
100 µs 500 ms
1 ms 5s
10 ms 10 s
100 ms 25 s
1s 55 s
1 µs 5 ms

H1 Schedule Object
The parameter dialog for the H1 Schedule object contains no parameter data other
than the general data. Parameters can be defined in the detail view of the H1
Schedule object, the schedule editor. Refer to Data Exchange on page 331.

3BDD012902R4101 231
FF Application Object Section 7 Parameter Settings

FF Application Object
All the FF function blocks used in an FF Application are processed cyclically with
the same cycle time. This time, which is also known as FF Application cycle time, is
specified on the tab. This parameter is preset to a default value. Refer to Figure 106.

Figure 106. Parameters FF Application

For a detailed description of the FF Application refer to Section 11, FF Application

Editor.

232 3BDD012902R4101
Section 7 Parameter Settings H1 Device Instance Object

H1 Device Instance Object

Refer to Figure 107 and Table 47.

Figure 107. Parameters H1 Device Instance

Table 47. Parameters

Dialog element Description

Device identification
Bus Address Address of the device on the H1 link.
The value range is 20 to 247.
Type Name Device type.
Assigned Device ID The device ID is a unique identification number for the
device. The device manufacturer assigns a unique
device ID to each individual device, and this ID never
changes. The device ID is only displayed if the device
assignment has been carried out.

3BDD012902R4101 233
FF Block Instance Object Section 7 Parameter Settings

Table 47. Parameters

Dialog element Description

Preset Device ID If the device ID for this device instance is known during
commissioning, it may be entered here.
A preset device ID is a prerequisite for using
the automatic device assignment during
commissioning; refer to Automatic Device
Assignment with Pre-configured Device ID on
page 358. If the standard way of device
assignment, i. e. device assignmnet via H1 live
list, is used, this value will be overwritten during
assignment.
LM settings
Backup Link Master Defines whether the device attempts to assume the role
of LAS (Link Active Scheduler) when necessary.
The device does not attempt to take over the LAS
role.
The device attempts to take over the LAS role.
This check box is only offered for Link-Master-
compatible devices; otherwise it appears grayed out.

FF Block Instance Object

Handling the Parameter Dialogs
Using the standard function block, Analog Input, as an example, the basic layout of
the parameter dialogs and the elements used in them is explained as follows. Refer
to Figure 108 and Table 48.

Table 48. Handling the Parameter Dialogs

Dialog element Description

General Data Name, short text and long text for the FF block.
Input field background White: Optional parameter
Red: Mandatory parameter

234 3BDD012902R4101
Section 7 Parameter Settings FF Block Instance Object

Table 48. Handling the Parameter Dialogs

Dialog element Description

Text field E.g. for entering the block name and long text. The
optional parameters Short Text and Long Text cannot be
entered before a block name has been assigned.
The block name can also be selected using
function key F2 from the tag list.

Table Used for displaying and, if appropriate, inputting

parameters such as lower and upper range limits. The
facility for entering input and output parameter values is
provided irrespective of whether or not a signal flow line
is connected to the assigned block pin.
Table background color Gray: Display only; i.e. value cannot be edited.
White: Input; i.e. value can be edited.
Green: Structural element. By clicking on the check box
the data structure can be expanded or collapsed.
The data structure is collapsed.
The data structure is expanded.
Yellow: (only in commissioning mode): The current
value read from the device is different from the
configured value.
Red: (in commissioning mode): Communication has
been interrupted. An error code is displayed.
Red: (in configuration mode): One or more other block
parameters are dependent on the value in this field. A
value must be entered in this field if the value of a
dependent block parameter is to be entered elsewhere
in the table.
Blue: At least one attribute of this block parameter is
dependent on one or more other block parameters.

3BDD012902R4101 235
Parameters Tab Section 7 Parameter Settings

Table 48. Handling the Parameter Dialogs

Dialog element Description

Text color in table Black: Normal display.
Red: The value entered falls outside the permissible
value range.
List There are lists in which only the default list entry is
visible. The invisible part of the list can be expanded.
The desired list entry is accepted by clicking in the input
field.

An FF block is assigned by default the initial instance parameters that were

present at the time of instantiation on the FF block class.
To increase transparency, it is recommended that you enter short and long text for
the FF blocks.
Short and long text can only be entered after the block name has been assigned.

Parameters Tab
This tab displays the block parameters in tabular form. These include inputs, outputs
and internal parameters. Refer to Figure 108.

236 3BDD012902R4101
Section 7 Parameter Settings Parameters Tab

With regard to the names and the meaning of the block parameters you should refer
to the FF specifications FF-890, FF-891 and FF-892 and to the documentation
provided by the device manufacturers.

Figure 108. Parameters Tab

3BDD012902R4101 237
Parameters Tab Section 7 Parameter Settings

The table of the tab contains the following columns, refer to Table 49:

Table 49. Parameters Tab

Dialog element Description

Relative OD Index The relative OD index specifies the relative position of
the parameter in the object dictionary. It is required, for
example, to localize errors when an H1 link is loaded.
Name Parameter name.
Value Value of the parameter. In commissioning mode a choice
can be made here to display either the configured value
from the database or the current value read from the
device.
In the case of data type Bit Enumerated, the values of
the individual bits are displayed by means of the state of
a check box:
bit is reset. Value = 0.
bit is set. Value = 1.
Unit Physical unit of the parameter.
Download The values in this column can only be edited at the block
class. This entry determines whether the parameter is
taken into account when the device configuration data is
loaded.
The parameter is not downloaded to the FF device.
A present parameter value is written to the FF
device, provided that it is a writable parameter. If no
parameter value is present in the value field, this
parameter is not downloaded with the device
configuration data.
In the case of a structural element the selection state of
the data structure is displayed.
All elements of the data structure are selected for
downloading.
Some elements of the data structure are selected
for downloading.
No element of the data structure is selected for
downloading.

238 3BDD012902R4101
Section 7 Parameter Settings Parameters Tab

Table 49. Parameters Tab

Dialog element Description

Type The data type describes the format of the value.
Range Permissible value range.
Class The class determines how the parameter is used in the
field device. Each parameter belongs to one and only
one of the classes Input (IN), Output (OUT) or
Contained (CONT). In addition there are the optional
classes Dynamic (DYN), Diagnostic (DIAG), Service
(SERV), Operate (OPER), Alarm (ALM), Tune (TUNE)
and Local (HOST).
Comment Optional entry of free comment text.
OPC Access The values in this column can only be edited at the block
class. This entry defines whether the parameter can be
accessed via an OPC Server.
No access to the parameter via an OPC Server.
Access to the parameter via an OPC Server is
possible. For further details refer to Enabling
Parameters of the FF Blocks for OPC Access on
page 261.
OPC Short Name The values in this column can only be edited at the block
class. If a value is entered here, the parameter of the
OPC Server is addressed by the OPC Server not via the
component name from the Name column, but via the
name entered here. This name must be unique within an
object. For further details refer to Enabling Parameters
of the FF Blocks for OPC Access on page 261.
Reset The parameter values in the grid are reset to the values
of a parameter value set which should be selected. For
further details refer to Managing Parameter Value Sets
on page 194.

3BDD012902R4101 239
Parameters Tab Section 7 Parameter Settings

The means of managing parameter value sets on this tab are described as follows.
For basic information on the management of parameter value sets refer to Managing
Parameter Value Sets on page 194.

Reset to Block-Type-Unspecific Default Values

Block-type-unspecific default values can be assigned to the parameters in the grid.
1. Button Reset
2. Radio button: Default values, block-type-unspecific

Reset to Initial Instance Parameter Values

The initial instance parameter values for the function block class can be assigned to
the parameter values in the grid.
1. Button Reset
2. Radio button: Initial instance parameter values from the block-type-specific
group

Reset to User-Defined Values

The values from a user-defined parameter value set can be assigned to the parameter
values in the grid. The user may choose between block-type-specific and device-
type-specific value sets.
1. Button Reset
2. Radio button: User-defined values from the block-type-specific or the
device-type-specific group
3. Select the required set of parameter values from the list.
4. The Preview changes check box can be set if desired. The parameters in the
grid that will be altered during the reset will be shown in list format.
Parameters can be individually deselected in this list.

User-defined parameter value sets are only available for selection if the user has
set them up in advance for this FF block class or for this FF device class.

240 3BDD012902R4101
Section 7 Parameter Settings Parameters Tab

Device-type-specific parameter value sets are only available on FF block

instances with a device assignment.

Reset to Vendor Defined Values

The values from a manufacturer-defined parameter value set can be assigned to the
parameter values in the grid. The user may choose between the default values and
example values from the Capabilities File.
1. Button Reset
2. Radio button: Vendor defined values from the device-type-specific group
3. Select the required set of parameter values from the list
4. The Show changed values check box can be set if desired. The parameters in
the grid that will be altered during the reset will be shown in list format.
Parameters can be individually deselected in this list.

Manufacturer-defined parameter value sets are only available on FF function

block instances with a device assignment.

Save Values as an Initial Instance Parameter Value Set

The current parameter value set can be saved as an initial instance parameter value
set for the function block class using the context menu.
1. Context menu: Store values as parameter value set
2. Radio button: Initial instance parameter values from the block-type-specific
group.

If the tab is left via Cancel, the parameter value sets that have been stored since
opening the tab will be lost.

Save Values as a User-Defined Parameter Value Set

The current parameter values can be saved as a user-defined block-type-specific
parameter value set using the context menu. Alternatively, on an FF block instance
with a device assignment it is possible to save the parameter values as a user-
defined device-type-specific parameter value set.

3BDD012902R4101 241
Parameters Tab Section 7 Parameter Settings

1. Context menu Save values as parameter value set

2. Radio button: User-defined values from the block-type-specific or the
device-type-specific group
3. Choose a user-defined parameter value set from the list (the existing parameter
value set is overwritten) or specify a new name for a user-defined parameter
value set (a new parameter value set will be added).

If the tab is left via Cancel, the parameter value sets that have been stored
since opening the tab will be lost.

Importing Parameter Values

1. Context menu Import
2. Select file from list.
3. A list of parameter values which will be changed in the grid when the import is
carried out is shown. Parameter values can be deselected in the list.

242 3BDD012902R4101
Section 7 Parameter Settings Function Block Info Tab

Function Block Info Tab

This tab contains identification data and characteristics for the block. Refer to
Figure 109 and Table 50.

Figure 109. Block Info Tab

3BDD012902R4101 243
Network Configuration Section 7 Parameter Settings

Table 50. Block Info Tab

Dialog element Description

Profile Profile on which the block definition is based. Among
other things the profile determines whether a block is
standard, enhanced or manufacturer-specific. The
profile number for standard function blocks is assigned
by the Fieldbus Foundation.
Profile revision Revision of the block profile. Among other things, this
determines whether a function block is standard or
enhanced.
DD Item ID Identification number of the block within the device
description.
Assigned device Device in which the block is executed.
Execution time Time taken for execution of the block.

Network Configuration
The IP settings of the nodes on the HSE subnet are parameters of the corresponding
objects in the FF Object Editor structure and therefore may be directly entered at
these object. For convenience the central Network Configuration dialog allows to
enter or revise the IP settings for the nodes on the HSE subnet as well as the IP
address and ressource ID of the nodes in the Client/Server network that run the OPC
Server FF for this HSE subnet. Refer to Figure 110.

244 3BDD012902R4101
Section 7 Parameter Settings Network Configuration

Open this dialog via Tools > Network....

Figure 110. Central Network Configuration

The network settings of the local PC (“Engin. PC”) cannot be modified in this
dialog. They can be changed calling up the Configure window:
Start > Programs > ABB Industrial IT 800xA > Device Mgmt - FF >
Configure
For a description of the dialogs refer to the “Industrial IT, 800xA - Fieldbus,
FOUNDATION Fieldbus Device Integration, Installation” (3BDD012901)
document.
For a detailed description of the network parameters refer to the section on
parameter settings for the corresponding object:

3BDD012902R4101 245
Network Configuration Section 7 Parameter Settings

• HSE Subnet (Subnet Mask, Default Gateway): HSE Subnet Settings Tab on
page 211.
• HSE Host CI860: Communication Tab on page 216.
• Linking Device LD 800HSE: Communication Tab on page 219.
• OPC Server FF: Network Configuration on page 255.

246 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus

General Description
The OPC Server FOUNDATION Fieldbus (OPC Server FF) makes data from
FOUNDATION Fieldbus devices available to any desired OPC Client. As a result,
visualization packages which have an OPC Client interface, can access the data of
the connected fieldbus devices.
The user interface Custom Interface of OPC specification version 2.04 is
implemented in OPC Server FF.
All interfaces which are marked "required" in the OPC specifications as well as the
browser interface have been implemented. With the browser functions, it is possible
for an external client to read out the list of the items known by the OPC Server.
The following aspects of OPC Server FF are described in this document:
• Functionality with regard to the system structure, communication of the
process data, tool routing, browser interface and redundancy.
• Configuration with the Fieldbus Builder FF.
• Tools for error diagnostics.
.

3BDD012902R4101 247
Overview of the Functionality of OPC Server FF Section 8 OPC Server FOUNDATION Fieldbus

Table 51. Abbreviations used

Term Explanation
OPC OPC stands for ’OLE for Process Control’ and is based on the OLE
core technologies COM and DCOM from Microsoft.
COM The way that platforms interpret an object must be defined in order to
ensure that objects which are implemented on different platforms or
computer architectures are compatible with each other. A so-called
object model is required for this. OLE uses the COM model
(Component Object Model). It defines the standard for the collaboration
of the components. COM enables procedure calls within a process and
to another process.
DCOM The object model for calls which span computers is called DCOM
(Distributed COM). DCOM is integrated in the Windows operating
systems.
FF FOUNDATION Fieldbus
FBB FF Fieldbus Builder FF
Configuration tool for FOUNDATION Fieldbus applications. The FF
hardware structure and functionality of the H1 and HSE devices are
defined and loaded to the devices.
Data from this fieldbus application are made available to other
programs through the configuration of an OPC Server FF.

Overview of the Functionality of OPC Server FF

System Structure
The Fieldbus Builder FF program is used to configure and commission OPC Server
FF. With a Fieldbus Builder FF project the structure of the hardware (H1 and HSE
devices as well as OPC gateway stations) is defined, the functionality of the
application configured and loaded to the devices and stations.
In a Fieldbus Builder FF project only one HSE subnet can be configured. The
connection between the Fieldbus Builder FF in the Client Server network and the
field level (HSE subnet) is done by the OPC Server FF. OPC Server FF has access

248 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Overview of the Functionality of OPC Server FF

to the data in the HSE subnet and can transfer this to the connected OPC Clients.
Pre-defined diagnostic values in the HSE subnet can also be accessed by OPC
Clients via OPC Server FF.
Each OPC-Server requires at least two network cards, one for the connection to the
Client Server network and one for the connection to the HSE subnet.

Engineering Workplaces
- Control Builder M
- Fieldbus Builder FF Operator Workplaces

Aspect Directory Server

Client Server
Network

Connectivity Server FF Connectivity Server redundant

with OPC Server FF AC 800M Connectivity Server FF
with OPC Server FF

Control Network

AC 800M AC 800M red AC 800M red

CI860 CI860 red CI860 red

HSE Subnet
LD 800HSE LD 800HSE LD 800HSE
LD 800HSE redundant redundant redundant

H1 Links
H1 Links

H1 Links

H1 Links

H1 Field Devices

H1 Field Devices H1 Field Devices H1 Field Devices

H1 Field Devices

Figure 111. Sample System Structure with FF Network

3BDD012902R4101 249
Data Transfer Section 8 OPC Server FOUNDATION Fieldbus

In the example at Figure 111 there are two separate HSE subnets each with an OPC
Server FF. It is not possible to establish a data connection to different HSE subnets
with one PC. Each OPC Server FF must therefore be installed on a dedicated PC.
Each of the HSE subnets is configured and commissioned by an individual Fieldbus
Builder FF project. Several Fieldbus Builder FF projects can be combined in an
800xA system. The data of each HSE subnet can be accessed via the respective
OPC Server FF.

Data Transfer
Fieldbus Builder FF and Plant Explorer are connected to the Client Server network,
but not directly to the HSE subnets. The connection to the HSE subnet is established
via an OPC Server FF.
This means that both the configuration information from the Fieldbus Builder FF
and all data accesses of Plant Explorer are transported to the field devices via OPC
Server FF.
A request is sent to the respective OPC Server FF from Plant Explorer, in order to
display fieldbus data in Plant Explorer. The server converts the request into an HSE
message and sends this to the associated linking device. A corresponding H1
message is generated in the linking device and sent to the FF device. The reply from
the device is converted into an HSE message in the linking device and sent back to
the OPC Server. The OPC Server converts the information into an OPC message
and sends this back to Plant Explorer.

Tool Routing
The conversion and transmission of the Client Server network messages into HSE
subnet requests is referred to as tool routing.
The tool routing functionality is available both in Fieldbus Builder FF and in OPC
Server FF. It is automatically installed during the setup of the software.
If there is an OPC Server FF configured in the HSE subnet, the Fielbus Builder FF
accesses the HSE subnet via the configured OPC Server FF. If there is no OPC

250 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Browser Interface

server configured, the Fieldbus Builder FF assumes to be connected to the HSE

subnet directly and the tool routing process of this PC is used.
FF HSE uses the standard Ethernet Physical Layer like many other Ethernet-based
communication protocols. In general different protocols may share the same
physical Ethernet layer. However, ABB does currently not support this for HSE.
Due to its nature, HSE causes a lot of broadcast and multicast traffic, requiring
significant bandwidth on the Ethernet. Without explicit tests, it cannot be
guaranteed that HSE can co-exist with other protocols without interference.
A full coverage of the different possible protocol combinations cannot be achieved
by a product release test. Therefore ABB currently does neither recommend
nor support to mix HSE with other protocols or to run several HSE Subnets
on the same Ethernet Physical Layer (wire).

Browser Interface
The information loaded in OPC Server FF can be accessed by an OPC Client via the
browser interface. The Fieldbus Builder FF objects admitted to the OPC Server FF
are output in a hierarchical structure:
HSE Linking Device1
H1 Link1
H1 Device1
FF Block1
FF Block2...
H1 Device2
FF Block1
FF Block2...
H1 Link2
...
Each of these objects has parameters which can be read as OPC items.

OPC Server Redundancy

In accordance with the OPC specifications of OPC Foundation, redundancy is not
supported by the OPC Server. In order to implement a redundant OPC connection
between the server and client, two OPC stations are configured in the Fieldbus
Builder FF project and loaded with identical data. The OPC Client assumes the
control of these two OPC Servers in accordance with its redundancy concept.

3BDD012902R4101 251
Resources, Maximum Values and Performance Section 8 OPC Server FOUNDATION Fieldbus

Resources, Maximum Values and Performance

Table 52. Performance Specifications

Description Performance specifications

OPC Gateway stations in a 1; for redundant connection 2
Fieldbus Builder FF project:
OPC Gateway stations in an 1; for redundant connection 2
HSE subnet:
OPC Servers per gateway PC: In principle, any number (dependent only on the
capability of the PC), but only one HSE subnet
can be addressed by a PC.
Scope of communication All the available data can be read out of the FF
between OPC Server FF and devices. Free times within the macro cycles are
the field devices: reserved by the configuration tool for
communication.
Update time for the cyclic Default value = 1000 ms.
reading of the OPC Client: The update time specifies the cycle time with
which a value is to be read out of the connected
devices.
Compliance with the cycle time cannot be
guaranteed. The used FF devices and their
configuration determine how fast the values can
be read out of the devices. If the cycle time is
less than that permitted by the field level, the
values are read as quickly as possible.
Data transfer from the OPC The transmission of the value to the OPC Client
Server to the OPC Client is change-driven, i.e. a constant value is not sent
at all, a changed value at maximum at the cycle
time stated with the value request.
Data throughput Is essentially determined by the configuration of
the field level, since the FF communication is a
great deal slower than the communication in the
Client Server network.

252 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Configuration with Fieldbus Builder FF

Configuration with Fieldbus Builder FF

OPC Server FF
Data from a Fieldbus Builder FF project are made available to other systems by
means of OPC Server FF.
The OPC Server FF is configured in a Fieldbus Builder FF project. OPC Server FF
software is installed on the OPC Server PC. In the commissioning mode of Fieldbus
Builder FF the configured project data is loaded into the OPC Server. The data are
available via the OPC interface directly after the loading.
As a result any Windows program with OPC Client functionality can read and write
the values of all the items available in OPC Server FF of the connected field devices
online.

Insertion of an OPC Server

An OPC Server is inserted below the FF Network node.

3BDD012902R4101 253
Insertion of an OPC Server Section 8 OPC Server FOUNDATION Fieldbus

FF network > Context menu: Insert > Gateway

Figure 112. Insert OPC Server FF

The standard name can be overwritten with a name with up to 16 characters. The
position of the OPC Server is defined.
After initial configuration of an OPC Server FF in an HSE subnet it is
recommended to upload the HSE subnet and to reopen Fieldbus Builder FF,
before switching to commissioning mode.

254 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Network Configuration

A maximum of two OPC Servers FF can be configured in one Fieldbus Builder FF

project. Refer to Figure 113.

Figure 113. System View of OPC Server FF

Network Configuration
In the Network Configuration dialog the IP settings of the OPC Servers FF that
interconnect to this HSE subnet have to be supplied. Here IP addresses and resource
IDs in the Client/Server network as well as IP addresses in the HSE subnet have to

3BDD012902R4101 255
Network Configuration Section 8 OPC Server FOUNDATION Fieldbus

be entered. These values must correspond with the values that have been assigned
during installation of the OPC Server FF software on the corresponding nodes.
The IP address and Resource ID that have been assigned during installation of the
OPC Server FF may be viewed or changed calling up the Configure window
locally on that node:
Start > Programs > ABB Industrial IT 800xA > Device Mgmt - FF >
Configure
For a description of the dialogs refer to the “Industrial IT, 800xA - Fieldbus,
FOUNDATION Fieldbus Device Integration, Installation” (3BDD012901)
document.

256 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Network Configuration

Settings in Client/Server Network

The values entered here must correspond with the IP adresses in the Client/Server
network and the resource IDs that have been assigned during installation of the OPC
Server FF software on the corresponding nodes. Refer to Figure 114.

Figure 114. Settings of OPC Server FF in Client/Server Network

• Tools > Network...

3BDD012902R4101 257
Network Configuration Section 8 OPC Server FOUNDATION Fieldbus

• Select GWY1 in upper half of window > Edit

• Enter Resource ID and IP address or node name (in Client/Server network)
of the node that runs the OPC Server FF for this HSE subnet.
• If you intend to use a redundant OPC Server FF for this HSE subnet, select
GWY2 and enter the required data of the node that runs the redundant OPC
Server FF.

258 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Network Configuration

Settings in HSE Network

The values entered here must correspond with the IP adresses in the HSE network
that have been assigned during installation of the OPC Server FF software on the
corresponding nodes. Refer to Figure 115.

Figure 115. IP Address of OPC Server FF in HSE Network

• Tools > Network...

3BDD012902R4101 259
Enabling of Tags for OPC Access Section 8 OPC Server FOUNDATION Fieldbus

• Select GWY1 in lower half of window > Edit

• Enter IP address (in HSE network) of the node that runs the OPC Server FF
for this HSE subnet.
• If you intend to use a redundant OPC Server FF for this HSE subnet, select
GWY2 and enter the required data of the node that runs the redundant OPC
Server FF.

Enabling of Tags for OPC Access

For each tag in the project it must be configured whether the process data can be
read and/or written via the OPC Server FF.
Within the taglist for each entry the access rights via an OPC Server can be
specified. The configured access rights are visualized in the list by single letters:
R Read
W Write
The dialog for the configuration of the access rights is displayed after a double click
in a gateway column or positioning the cursor in a line and selecting the menu Edit
> Station access.... The access rights can be changed for several list entries at once

260 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Enabling Parameters of the FF Blocks for OPC

by marking several entries before the menu call (station access...) by means of the
shift + arrow keys. Refer to Figure 116 and Table 53.

Figure 116. Defining the OPC Access

Table 53. Defining the OPC Access

Dialog element Description

Left-hand column Listing of the configured gateway stations.
Read The data of the previously selected tags can be read via
the gateway,
Write The data of the previously selected tags can be written
via the gateway.

If the project configuration should be uploaded to the AIP, all the tags must be
configured with read and write permissions.
Tags without access rights for OPC Server FF are created in the AIP, online data
for these objects cannot be displayed, however.

Enabling Parameters of the FF Blocks for OPC Access

For each parameter, input and output of an FF block it is configured as to whether
the data are available via the OPC Server. This configuration is effected in the class

3BDD012902R4101 261
Enabling Parameters of the FF Blocks for OPC Access Section 8 OPC Server FOUNDATION

definition of the block. It is thereby guaranteed that all instances of a block class can
be equally processed by the OPC Client.
Two columns for configuration of the OPC Access are available in the dialog forms
of the FF Block classes. Configuration as to whether the parameter is loaded to the
OPC Gateway or not is effected in the OPC Access column using a check box. The
corresponding parameter can be then accessed in the gateway under
<tagname>/<component name>. If a name is entered in the OPC short name
column, this name is used in the gateway instead of the component name. See
Figure 117 and Table 54.

Figure 117. Enabling Block Parameters for OPC Access

262 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Enabling Parameters of the FF Blocks for OPC

Table 54. Enabling Block Parameters for OPC Access

Dialog element Description

OPC Access The parameter can be accessed via an OPC Server.
OPC Short name The parameter is addressed by the OPC Server via the
name entered here, and not via the component name in the
Name column. This name must be unique within an object.

Each parameter for which OPC access is enabled is accessed by the OPC Server via
its item name. The component name is used as a standard item name. The user can
change this name to an OPC Short name. If the standard parameter name does not
correspond to the nomenclature conventions of the client used, an OPC name must
be defined by the user.
Any OPC name used must be unique within a class description.
The names defined in the class description are valid for all instances of this class.
The OPC Access and the OPC Short name are displayed in the parameter dialog for
the block instances, but cannot be changed there.
A user-defined OPC name replaces the complete structure of the standard name.
Example from Figure 117:
• The parameter MODE_BLK.Actual.Cas is read via the OPC name Cascade.
• The parameter MODE_BLK.Target.Cas is read via the OPC name
MODE_BLK.Target.Cas.
A subsequent change of OPC Access or an OPC Short name will set all instances of
this class into state ’unchecked’. The check function must be repeated for the
programs concerned. The changed information is available to the OPC Clients once
the new function code has been loaded into OPC Server FF.
The contents of the parameter input mask can be exported and imported to another
project.

3BDD012902R4101 263
Parameters of the Hardware Objects Section 8 OPC Server FOUNDATION Fieldbus

Parameters of the Hardware Objects

In addition to the configurable parameters, for the hardware object types HSE
Device, H1 Link and H1 Device, pre-defined parameters are available in the OPC
interface for diagnosis from the OPC.
See Appendix C, Diagnostic Data for the listing of the pre-defined parameters and
description of the Live List.

Starting the Communication

An OPC Server is automatically started on request by an OPC Client.
A manual start is possible via the Windows start menu:
1. Start > Programs > ABB Industrial IT 800xA > Device Mgmt - FF > OPC
Server FF > OPC Server FF xx
2. xx = resource ID no. e.g. 86 as assigned during the setup.
Several OPC Servers can be started on one PC at the same time assumed that they
have different resource IDs.

Loading Project Data into OPC Server

Like the process devices, the OPC Server FF also needs to be commissioned.
After the whole project configuration has been checked for plausibility and all
process devices have been loaded, the project data must also be loaded into the OPC
Server. The OPC Server FF is selected in the tree structure and the command

264 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Addressing of the Data

Object > Download is selected from the menu or the context menu. All necessary
configuration data are transferred to OPC Server FF. Refer to Figure 118.

Figure 118. Loading OPC Servers

With the loading process from Fieldbus Builder FF, all tags for which an OPC
access has been configured (refer to Enabling of Tags for OPC Access) are made
known to OPC Server FF. The data of these tags can be read and written by the
external client.

Addressing of the Data

The data are addressed by the same name within the system and via the OPC
interface.
Input and output pins and parameters of tags are addressed via the tag name and the
pin or parameter name:
<Tagname> / <Pin or parameter name>

3BDD012902R4101 265
Data Types of the OPC Items Section 8 OPC Server FOUNDATION Fieldbus

Example, refer to Table 55:

Table 55. Data Addressing

<Tag name> /
Meaning
<Pin or parameter name>
TIC123/PV.Value Reading of the process value of controller
TIC123
TIC123/MODE_BLK.Target Reading of the target operating mode of
controller TIC123
TIC123/Cascade Reading of the current cascade operating mode
of controller TIC123
The OPC name Cascade was configured for the
parameter MODE_BLK.Actual.Cas

The component and parameter names of the FF blocks are specified during the class
definition of the blocks. Refer to Enabling Parameters of the FF Blocks for OPC
Access on page 261.
The OPC interface is case-sensitive. The names used in the OPC Client must
therefore be written identically to the names configured in the Fieldbus Builder
FF project.

Data Types of the OPC Items

The procedures of the OPC interface are based on the definitions for COM and
DCOM. Canonical data types are used for data transfer within these definitions.
These are the data types which are supported as basic data types with the Microsoft
environment.

266 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Data Types of the OPC Items

A data request via OPC can be made with or without a data type. In the case of data
requests without a data type (variant type), the data types of the FF project are
mapped as follows. Refer to Table 56.

Table 56. Data Types of the OPC Items

Data type in the FF project Internal data types Data types in OPC
kFFBoolean BOOL VT_BOOL
kFFBit
kFFBitEnumerated
kFFInteger (Length=1) INT8 VT_I1
kFFInteger (Length=2) INT16 VT_I2
kFFInteger (Length=4) INT32 VT_I4
kFFUnsigned (Length=1) BYTE VT_UI1
kFFIndex (Length=1)
kFFEnumerated (Length=1)
kFFUnsigned (Length=2) UINT16 VT_UI2
kFFIndex (Length=2)
kFFEnumerated (Length=2)
kFFUnsigned (Length=4) UINT32 VT_UI4
kFFIndex (Length=4)
kFFEnumerated (Length=4)
kFFFloat FLOAT32 VT_R4
kFFAsciiKFFPassword STRING256 VT_BSTR
kFFVisibleString
kFFOctetString STRING VT_BSTR
kFFBitString
kFFDateAndTime DMSTIME VT_DATE
kFFTimeValue
kFFTime TIME VT_I4
kFFDuration

3BDD012902R4101 267
Version Check Section 8 OPC Server FOUNDATION Fieldbus

In the case of data requests with a specified data type (requested data type), only
data types in which a conversion is always possible are accepted. The system
behavior in respect of the required data type conversion can be set in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Fieldbus Builder FF\3.1\
Digicom\Communication]
For the setting "OptimisticDataTypeConversion = 1", an attempt is always made
to convert the read value to the requested data type.
With the setting "OptimisticDataTypeConversion = 0" (default setting), a more
restrictive data conversion is set.

Version Check
The operator will be prevented from writing invalid data to the H1 devices if the FF
configuration of the H1 devices is not identical with the version which was loaded
into the OPC Server FF. A version check guarantees that read and write operations
to FF devices reconfigured by Fieldbus Builder FF are prevented if the OPC Server
was not reloaded.
In general, the OPC Server must also be loaded after a change in the
configuration of an FF device with subsequent loading. This will be indicated by
the engineering status after executing Tools > Check whole project; refer to
Representation in the FF Object Editor Structure on page 110
The following information on the H1 devices is loaded into OPC Server FF during
the download process:
• PD tag of the H1 device
• DD items of the instantiated blocks
• Tag names of the instantiated blocks
After the initialization of an H1 device, those objects which contain this information
are first of all read by OPC Server FF and compared with the internally stored
information.
The restrictions for the data access in the case of a version error are specified in the
registry of the OPC Server PC:
• No restriction
• Restriction for write accesses

268 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Tools for Error Diagnosis

• Restriction for read and write accesses

These restrictions can be set by means of two registry keys. Below the path
[HKEY_LOCAL_MACHINE\SOFTWARE\ABB\Fieldbus Builder FF\3.1\
Digicom\Communication]
the two key words exist:
• ReadWithVersionConflict
• WriteWithVersionConflict
Value 0: no access possible in the case of a detected version conflict.
Value 1: the data can be accessed in spite of a detected version conflict.

Tools for Error Diagnosis

Trace Dialog of the OPC Server
The OPC Server trace dialog can be started from the Windows start menu on a PC
on which at least one OPC Server FF has been installed:
Start > Programs > ABB Industrial IT 800xA > Device Mgmt - FF > OPC
Server FF > OPC Server FF Trace

3BDD012902R4101 269
Tools for Error Diagnosis Section 8 OPC Server FOUNDATION Fieldbus

Both the OPC Servers FF which are locally active on the computer and the OPC
Servers FF which can be reached via a network connection can be monitored by
means of this dialog. Refer to Figure 119 and Table 57.

Figure 119. OPC Server Trace Dialog

Table 57. OPC Server Trace Dialog

Dialog element Meaning

OPC Server
Computer name, The connected OPC Server is described by the two
Res-ID entries. The two fields can be edited after actuation of
the Disconnect button. A connection to the entered
OPC Server is established by means of the Connect
button.

270 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus Tools for Error Diagnosis

Table 57. OPC Server Trace Dialog

Dialog element Meaning

Keyword Trace The various functions of the OPC Server can be
hierarchically selected in the left-hand side of the dialog.
Dependent on the selected entries the respective
function calls in the OPC Server are recorded with the
current parameters. It is thereby possible to trace
selectively specified functions or functional groups of the
OPC Server. Refer to Appendix D, OPC Keyword
Tracing.
Tracelevel The degree of itemization of the trace outputs is defined
by the trace level.
Tracefile
Path The directory for the trace file is stated. A file
opc<Res-ID>.trc is created in the stated directory.
Size [KByte] The maximum size of the trace file in kbytes. If the
maximum size of the trace file is reached, the file is
renamed opc<Res-ID>.bak and the file opc<Res-ID>.trc
re-created.
Apply Settings The settings for the directory and the size of the trace file
are adopted.
Show File The current trace file is displayed in the standard
Windows editor. If information from the *.bak file is
required, it must be called separately.
Clear File The current trace file is deleted. The *.bak file is not
affected by this action.
Server dump
Dump Configuration All the configuration data of the OPC Server are written
to the trace file. The entries are marked by the text
Dumping configuration data... and
...Configuration dump finished.

3BDD012902R4101 271
Tools for Error Diagnosis Section 8 OPC Server FOUNDATION Fieldbus

Table 57. OPC Server Trace Dialog

Dialog element Meaning

Dump Connections An entry in the trace file is generated for each active
connection. The entries are marked by the text
Dumping server objects... and
...Server object dump finished.
Dump Groups An entry in the trace file is generated for each installed
group of the OPC Server. The entries are marked by the
text
Dumping group objects... and
...group object dump finished.
Save Settings All settings of the dialog are stored and preset on a
renewed start of the trace dialog or on a cold start of the
OPC Server.

Example of a trace output. Refer to Figure 120.

Figure 120. Trace Output

272 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus System Monitor for OPC

System Monitor for OPC

A system monitor (performance monitor) is part of the scope of supply of Windows
by means of which the performance of the Windows PC can be controlled and
monitored. All general variables, such as free memory capacity, CPU usage, can be
displayed and monitored by means of this software package from Microsoft.
Application-specific variables of the Fieldbus Builder FF software, e.g. statistical
data about read/write errors in the OPC Server, can also be visualized by means of
an extension.
The system monitor is called via the start menu:
Start > Settings > Control Panel > Administrative Tools > Performance

Select Display Mode - Enter the Variables

The display mode is selected by means of the buttons in the toolbar.
Variables for monitoring can be selected after call of the ’+’ button in the
performance monitor:
1. In the Add Counters dialog:
2. Select computer (Remote operation is possible).
3. Select performance object OPCSRV FF(FBB FF).
4. Select the desired variables via Select counters from list.
5. End the dialog with Add and Close.

If OPCSRV FF (FBB FF) is not displayed in the "Performance object" window,

please check that the correct language has been selected in your operating
system. The language setting of Windows and Fieldbus Builder FF must
coincide.
After the data sources have been specified, the current values are displayed in a
diagram. The display parameters can be set in the System Monitor Properties
dialog.

3BDD012902R4101 273
System Monitor for OPC Section 8 OPC Server FOUNDATION Fieldbus

List of the System Variables of OPC Server FF.

Table 58. Meaning of the General Variables

Name Description
% Communication buffers States the percentage of the communication
buffers currently in use. Since the service time is
relatively small, a value of 0 usually results.
Communications buffers The number of currently used communication
buffers. Since the service time is relatively small, a
value of 0 usually results.
% Connections States the percentage of the available connections
which are active at present.
Connections The absolute number of active connections.
% DMS Handles States the percentage of DMS resources which are
in use at present. This value also includes the
dynamic SEG handles.
DMS Handles Amount of DMS resources used. This value
includes all dynamic SEG handles.
% SEG Handles States the percentage of DMS resources for "cyclic
requests" which is in use.
SEG Handles Amount of DMS resources used for "cyclic
requests".
Process ID Process identification of the running process.
Station Number First station address.

Table 59. Meaning of the OPC Variables

Name Description
Item No Number of configured items.
Event No Number of configured OPC Event
Points.

274 3BDD012902R4101
Section 8 OPC Server FOUNDATION Fieldbus System Monitor for OPC

Table 59. Meaning of the OPC Variables

Name Description
Client connections Number of OPC Data Access Client
Connections.
Groups Number of OPC Groups.
Active items Number of active OPC items, an item in
different groups is only counted once.
AddItem failures (bandwidth) Number of OPC items which could not
be created because of limited bandwidth.
AddItem failures (interaction) Number of OPC items which could not
be created on account of incorrect
interaction between the client and
server.
AddItem failures (configuration) Number of OPC items which could not
be created because of configuration
errors.
Pending jobs Number of acyclic jobs running.
Acyclic read errors Number of acyclic read errors counted
on an item basis.
Acyclic write errors Number of write errors counted on an
item basis.
Station No. for Station n. Station address for station n.
% used cyclic bandwidth St. n Percentage of the cyclic bandwidth used
for station n. If this value 100% reaches,
no further values are cyclically
communicated to this station. On
account of fragmentation, this can also
occur for values slightly under 100%.
Changed cyclic items/second The number of changed cyclic items per
second. Items which were sent to
several clients are only counted once.

3BDD012902R4101 275
OPC Client Section 8 OPC Server FOUNDATION Fieldbus

Table 59. Meaning of the OPC Variables

Name Description
Acyclic reads/second The number of items per second
acyclically read from the device.
Acyclic writes/second The number of written items per second.

OPC Client
OPC-relevant Parameters
The parameters of the FF blocks which are available via the OPC interface are
determined during the configuration of the FF block classes. Refer to Enabling
Parameters of the FF Blocks for OPC Access on page 261.

276 3BDD012902R4101
 Section 9 Dialog Editor for FF Blocks

General Description
To make the input of parameters for FF blocks easier it is possible to configure tabs
individually. These are configured using the dialog editor.
Each FF Block Class object and each FF Block Instance object has a default
parameter input dialog. This default parameter input dialog enables the initial
instance parameter values for the FF Block Class object and the FF block instance
parameter values for an FF Block Instance object to be configured in list form.
The dialog editor allows a specific parameter input dialog to be created for the FF
Block Class object. The parameter dialog pages that were set up earlier for the FF
block class appear as additional tabs for the FF Block Class object and the FF Block
Instance object. Using these tabs the user can easily set the initial instance
parameter values for an FF block class and the parameter values for an FF block
instance.

Operation of the Dialog Editor

The dialog editor is opened as follows: Context menu for an FF block class > Dialog
editor
The elements of the parameter input dialog are the parameters of the FF block class.
All the parameters available for the FF block class are displayed in the left section
of the dialog editor. Refer to Figure 121.

3BDD012902R4101 277
Operation of the Dialog Editor Section 9 Dialog Editor for FF Blocks

The dialog editor allows the text for the operator interface and the input format
(operation) to be specified for each parameter. New tabs can also be added. The
parameter input dialog can be structured using group areas.

Figure 121. Dialog Editor

Table 60. Dialog Editor

Dialog element Description

Parameter list List of parameters available for the FF block class
parameter input dialog.
Name Parameter name
Data type Data type of the parameter
Dialog description Area for defining the parameter input dialog for the FF
block class. Each parameter input dialog must start with
a new dialog page (PAGE).

278 3BDD012902R4101
Section 9 Dialog Editor for FF Blocks Operation of the Dialog Editor

Table 60. Dialog Editor

Dialog element Description

Dialog element Structural element or parameter name
PAGE: Start of a new dialog page (tab) in the parameter
input dialog
GROUP: Start of a new group in the parameter input
dialog
Label Text representing the structural element or the
parameter in the parameter input dialog.
Handling Dialog field controlling the functionality of parameter
input. This can only be entered for parameters.
OK The dialog editor is closed and the changes saved.
Cancel The dialog editor is closed and the changes are
cancelled.
Save The changes are saved.
Delete The selected dialog line is deleted.
If a parameter was assigned, this will appear in the
parameter list again following deletion.
new Page Structural element.
A new dialog page (tab) is created.
A dialog page must have a name.

new group Structural element

A new dialog group is created. This encompasses the
dialog fields until the beginning of the next group or up to
the end of the page.
Test Switches the dialog editor to test mode. Test mode
enables the functionality to be tested of the parameter
input dialog that has been created.
Test mode is available only in parameter input
dialogs that have been checked for plausibility.

3BDD012902R4101 279
Operation of the Dialog Editor Section 9 Dialog Editor for FF Blocks

Table 60. Dialog Editor

Dialog element Description

Check The dialog is checked for plausibility.
Export / Import A selected block from the dialog definition can be
exported to a file in internal system format. This dialog
definition can be re-imported in another FF function
block object.
Text export/ Text All the texts from a selected block are exported to a text
import file in Unicode format. This text file can be edited using a
text editor. This enables text to be translated into another
language for example. Individual units of text are
organized line by line in the text file. Each line includes
the following information separated by semicolons (;):
Parameter name; Value; Text.
Value refers to the value of the text in combo boxes,
radio buttons and bit fields. If none of these is applicable
then the value entry remains blank.

Creating a Parameter Input Dialog

1. Create new tab.
2. Transfer all the parameters that are to be configured.
Create another dialog page if required.
3. Assign text items for the operator interface.
4. Modify the dialog (Label, Handling) if necessary.
5. Structure the parameter input dialog with group areas if necessary.
6. Check parameter input dialog for plausibility.
7. Test parameter input dialog.
Parameters for the parameter input dialog must be copied from the parameters list
into the dialog description: Select individual parameter or block > ’-->’
Parameters can be used more than once in the tabs that are defined by means of the
Copy /Paste functions. However, the same parameter cannot be used more than

280 3BDD012902R4101
Section 9 Dialog Editor for FF Blocks Elements of the Dialog Editor

once in the same tab. The interface layout can only be configured at the point where
the parameter is first pasted. All other usage points refer to this configuration data.
Each parameter line in the dialog editor corresponds to one line in the actual dialog.
If the maximum number of lines in the dialog is exceeded, this will result in an error
during the plausibility check.

Elements of the Dialog Editor

Each parameter is assigned a dialog field (operation). The assigned dialog field
determines the appearance of the parameter in the parameter input dialog.
The dialog fields that can be used depend on the data types of the parameters.

Table 61. Overview Dialog Fields

Enumeration
DWORD
Dialog field
WORD

STRxx
BOOL

REAL
BYTE

TIME
DINT
INT

DT
Edit Control X X X X X X X X X
Check Box X
Bit Field X X X
Radio Button Field X X X X X
Combo Box X X X X X
Combo Box Pre-defined X

3BDD012902R4101 281
Elements of the Dialog Editor Section 9 Dialog Editor for FF Blocks

Edit Control

Figure 122. Edit Control

The edit control can be used to set values for parameters with any data type
(exceptions: BOOL, Enumeration).
The edit controls in the dialog itself are fixed in length. When data has been entered
it can be scrolled.

Check Box

Figure 123. Check Box

A check box is used to define the status of a parameter of data type BOOL.

Bit Field

Figure 124. Bit Field

Bit fields are used for defining individual bits in bitstrings. They can be used for
parameters of data types BYTE.
Texts for the user interface must be configured for a bit field. Please refer to
Configuring Texts on page 284 and Figure 129.

282 3BDD012902R4101
Section 9 Dialog Editor for FF Blocks Elements of the Dialog Editor

Radio Button

Figure 125. Radio Button

Radio buttons are used for defining discrete statuses. They can be used for
parameters of data types BYTE, INT and UINT.
Texts for the user interface must be configured for a radio button. Please refer to
Configuring Texts on page 284 and Figure 129.

Combo Box

Figure 126. Combo Box

Combo boxes are used for defining discrete statuses. They can be used for
parameters of data types BYTE, INT and UINT.
Status texts must be configured for a combo box.

Combo Box Pre-defined

Figure 127. Combo Box Pre-defined

The combo box pre-defined is used for defining discrete statuses which are to be
defined using a parameter of data type enumeration.
The status texts for the combo box pre-defined are fixed, and cannot be modified.

3BDD012902R4101 283
Elements of the Dialog Editor Section 9 Dialog Editor for FF Blocks

Figure 128 shows an example of a parameter input dialog for an FF block class:

Figure 128. Example of a Parameter Input Dialog for an FF Block Class

Configuring Texts
For certain dialog fields, user interface text (bit field, radio button) or status texts
(combo box) must be configured. These texts can be selected using the context
menu:

284 3BDD012902R4101
Section 9 Dialog Editor for FF Blocks Elements of the Dialog Editor

Select dialog element > context menu: Label definition,

refer to Figure 129 and Table 62.

Figure 129. Label Definition

Table 62. Label Definition

Dialog element Description

No. Sequential numbering of entries. New entries are added
via the context menu New value.
Value or bit Value of the block parameter for which a text item is
defined.
Number of the bit for which a text item is defined. Bit 0
describes the lowest-value bit in the data type.
Text Text for the bit, the radio button or the element in the
combo box.

3BDD012902R4101 285
Elements of the Dialog Editor Section 9 Dialog Editor for FF Blocks

Table 62. Label Definition

Dialog element Description

Comment Comment for the value. The comment serves only for the
purpose of documentation.
Export All marked lines are written to a file in ASCII format.
Import A stored file can be read in. When a file is imported in
this way, all the existing entries are overwritten.

286 3BDD012902R4101
 Section 10 FF Signals

Inputs and outputs from FF function blocks can be mapped to FF signals. FF signals
enable the signal flow within the FF network. FF signals are transferred cyclically
by means of the Publish/Subscribe communication mechanism. An FF signal has
one and only one source which publishes the signal cyclically, and any number of
sinks which subscribe the signal. For the publish/subscribe communication the FF
specification FF-890 defines the data structures DS-65 (value & status – analog),
DS-66 (value & status – discrete) and DS-67 (value & status – bitstring), each of
which consists of a value and a status.
HSE republishing, as supported by FF linking devices of device classes 42c and
42d, allows the cyclical communication of FF signals between an H1 link and the
higher-level HSE subnet.
A distinction is made between two types of FF signals:
• FF signals of usage type HSE + H1: Communicated both on the H1 link and
on the HSE subnet. These include FF signals whose sources and sinks lie in
various different H1 links and FF signals which are used for exchanging data
with an HSE host.
• Local H1 signals (usage type H1): Used only for configuring signal flow
within an H1 link. They are required for exchanging data between different FF
Application objects. They can be used as an alternative to a signal line in the FF
Application.

3BDD012902R4101 287
FF Signal List Section 10 FF Signals

From the point of view of FF, the HSE communication interface of the
IEC 61131 controller is an HSE host which is participating in the HSE
communication. For access from the IEC 61131 application, FF signals can be
mapped to channels on the HSE host. Channels which the IEC 61131 application
writes to are thereby mapped to FF signals which are published on the HSE
subnet with a cycle time that is configured separately for each FF signal. The
HSE host is the publisher of these signals. In the opposite direction, FF signals
originating in the HSE subnet are mapped to channels which are read by the
IEC 61131 application. The HSE host is the subscriber for these signals. The
mapping of the FF signals to channels on the HSE host is configured on the HSE
Host object.
FF signals with the extension (LP) (LP = Low Priority) are communicated in a
transmission cycle that is configured for the H1 link (refer to H1 Settings Tab on
page 221). They represent a means of reducing the communication load in the FF
network. It is recommended that this signal type should be used for signals for
which a longer transmission cycle time is sufficient.
All the FF signals of the HSE subnet and the subsidiary H1 links which are also
communicated on the HSE subnet are entered by the system in the FF signal list for
the HSE subnet. The name space for FF signals includes the HSE subnet and the
subsidiary H1 links.

FF Signal List
The FF signal list contains all the FF signals for an HSE subnet and its subsidiary
H1 links. For each FF signal the signal name, the data type (analog, discrete or
bitstring), source information, usage (HSE + H1 or H1) and an optional comment
are displayed.

Call FF Signal List

The FF signal list can be edited in the parameter input mask for the HSE Subnet
object in the FF Signals tab.
1. Select HSE Subnet object in the FF Object Editor structure.
2. Edit > Parameters...

288 3BDD012902R4101
Section 10 FF Signals Structure of the FF Signal List

3. Choose FF Signals tab.

New FF signals can be created here, while existing FF signals can be modified or
deleted.

Structure of the FF Signal List

The structure of the FF signal list is as follows. Refer to Figure 130 and Table 63.

Figure 130. Structure of the FF Signal List

3BDD012902R4101 289
Structure of the FF Signal List Section 10 FF Signals

Table 63. Structure of the FF Signal List

Dialog element Description

FF signal Name of FF signal (max. 14 characters). This name is
displayed in the FF signal icon in the FF Application.
Data type Data type of FF signal, e.g. analog, discrete or bitstring.
Source Link Name of the H1 link or HSE subnet in which the FF
signal is generated.
Usage Defines whether the FF signal is communicated only
within an H1 link (local H1 signal), or whether it is also
communicated on the HSE subnet. Usage can be set to
any of the following values:
• H1: FF signal that is communicated only within the
H1 link.
• HSE + H1: FF signal that is communicated both on
the H1 link and on the HSE subnet.
• HSE + H1 (LP): FF signal that is communicated
both on the H1 link and on the HSE subnet. It uses
the transmission cycle for low-priority FF signals
that has been configured for the HSE subnet.

290 3BDD012902R4101
Section 10 FF Signals Structure of the FF Signal List

Table 63. Structure of the FF Signal List

Dialog element Description

Group This parameter setting assigns the FF signal to a signal
group.
A multicast IP address is used for each signal group; i.e.
all signals of a group are addressed via the same
multicast IP address. As a result, the CPU load can be
minimized for the cyclic communication in the HSE
devices.
Automatic assignment is obtained via the Set HSE
Signal Groups button.
The following optimization criteria should become a
usage type for manual assignment of the FF signals to
groups:
• For each HSE device: minimization of the number
of overhead signals per device. Overhead signals
are signals which are rejected, because they are
not intended for the device. The overhead signals
would generate CPU load.
• For each HSE device: minimization of the number
of multicast IP addresses for transmitting and
receiving (transmission and receiving sessions).
The reason for this optimization lies in the limited
number of transmission and receiving sessions
which an HSE device supports. It is dependent on
the type of device.
During automatic assignment, resource conflicts in the
HSE devices can be resolved by means of the
parameter max. No. of Signal Groups. If the number of
possible transmission/receiving sessions is exceeded in
one or more HSE devices after automatic assignment,
the value of this parameter setting should be reduced.
FF signals which are only communicated within an H1
link (Usage type: H1) do not require group assignment.
Comment Comment on the FF signal (max. 40 characters).

3BDD012902R4101 291
Edit List Entries Section 10 FF Signals

Table 63. Structure of the FF Signal List

Dialog element Description

Set HSE Signal The assignment of the FF signals to signal groups is
Groups generated automatically.
If after automatic assignment for one or more HSE
devices, the number of possible Send/Receive sessions
is exceeded, the value of the parameter max. No. of
Signal Groups should be reduced and automatic
assignment should be repeated; refer to HSE Subnet
Settings Tab on page 211.
Find and set Source The column Source Link is filled with correct values. If
Segments there is exactly one link/HSE subnet containing signal
sources for an FF signal, then the name of that link/HSE
subnet is entered. Otherwise the value in the Source
Link table field remains unchanged.

Edit List Entries

A number of functions are provided for editing individual lines in the list. These can
be used to add new entries and modify and delete existing entries.

Add New FF Signal to List

Context menu > Create Component or INS key.
A new line is added to the FF signal list. The following data should be entered here,
(refer to Table 64):

Table 64. Add New FF Signal to List

Dialog element Description

FF signal Enter signal name (max. 14 characters).
Data type Choose data type from the data types list.
Source Link Choose from the selection list the link/HSE subnet which
contains the signal source.

292 3BDD012902R4101
Section 10 FF Signals Block Editing

Table 64. Add New FF Signal to List

Dialog element Description

Usage Choose usage from the selection list. Usage defines
whether the FF signal is communicated only within an
H1 link (local H1 signal), or whether it is also
communicated on the HSE subnet.
Group Only in case of manual assignment off FF signals to
groups is it necessary to enter a signal group here. Refer
to Table 63.
Comment Optional entry of free comment text (max. 40
characters).

Change FF Signal Entry

1. Select desired field with a left mouse click.
2. Depending on the field that is selected, the new value can either be entered
directly or chosen from a selection list.

If an FF signal is renamed, then the points at which that FF signal is used in an FF

Application are displayed with status error (red).

Delete FF Signal
1. Select the desired line in the list with a left mouse click on the line selection
field.
2. Context menu > Delete Component or DEL key.

The points at which the deleted FF signal is used in an FF Application are

displayed with status error (red).

Block Editing
The editing steps described here are performed on a block. A block is a number of
selected, complete lines in the list. The lines in a block do not necessarily all need to
be consecutive. If a block contains nonconsecutive lines it consists out of several
partial blocks.

3BDD012902R4101 293
Block Editing Section 10 FF Signals

Select Block
1. Left click on the desired start of block.
2. Keeping the left mouse button pressed down, drag the mouse across the block
area up to the end of the first partial block.
3. Release left mouse button.
4. If necessary, hold down the CTRL key and select additional partial blocks.

Cut
1. Select block
2. Context menu > Cut
A defined block is removed from the FF signal list and stored in the clipboard. The
command Paste is used to insert this block in an FF signal list.

Copy
1. Select block
2. Context menu > Copy
A defined block is copied and stored in the clipboard. The command Paste is used
to insert this block in an FF signal list.

Paste
1. Select block
2. Context menu > Create Component
A copied or cut block in the clipboard is pasted into an FF signal list below the
cursor position.
If the name of a pasted FF signal already exists in the FF signal list you will be
prompted to change the duplicate signal name if you save the signal list.
Delete
1. Select Block
2. Context menu > Delete component or DEL key

294 3BDD012902R4101
Section 10 FF Signals Create New FF Signal in an FF Application

A defined block is deleted from the FF signal list.

The points at which the deleted FF signal is used in an FF Application are
displayed with status error (red).

Create New FF Signal in an FF Application

The FF Application Editor provides an alternative way of adding new signals to the
FF signal list. This is accessed via the parameter input mask which can be called for
an FF signal symbol.
1. Double-click on an FF signal symbol in the FF Application Editor.
2. Enter the name of a new FF signal in the signal field.
If the name of an FF signal which is not contained in the FF signal list is entered in
the parameter input mask, then the following dialog for creating a new FF signal
will be displayed. Refer to Figure 131. The following data should be entered. Refer
to Table 65.

Figure 131. Create FF Signal.

3BDD012902R4101 295
Mapping of FF Signals to Channels for the HSE Host Object Section 10 FF Signals

Table 65. Create FF Signal

Dialog element Description

Name Enter signal name (max. 14 characters).
Data type Choose data type from the data types list.
Usage Choose usage from the selection list.
Comment Optional entry of free comment text (max. 40
characters).

The FF signal specified in this way is added to the FF signal list for the HSE subnet.

Mapping of FF Signals to Channels for the HSE Host

Object
In order to exchange data between the FF network and a system outside the FF
network (e.g. an application on an IEC 61131 controller) FF signals must be
mapped to channels on the HSE Host object. Signals in the FF signal list with usage
type HSE + H1 or HSE + H1 (LP) can be used for mapping.
The mapping of FF signals to channels on the HSE Host object is described in this
section. For configuration of Control Builder M control applications with
FOUNDATION Fieldbus using the CI860 module, refer to the manual “800xA -
Control and I/O FOUNDATION Fieldbus, Engineering and Configuration”
(3BDD012903).

Call List of Signal-Channel Mapping

The mapping of FF signals to I/O channels is made in the parameter input mask for
the HSE Host object on the Published/Subscribed tab.
1. Select HSE Host object (HSEHostCI860) in the FF Object Editor structure.
2. Edit > Parameter
3. Choose Published/Subscribed tab.

296 3BDD012902R4101
Section 10 FF Signals Structure of the Published/Subscribed Tab

FF signals with usage type HSE + H1 or HSE + H1 (LP) from the FF signal list can
be mapped to I/O channels here.

Structure of the Published/Subscribed Tab

Refer to Figure 132 and Table 66.

Figure 132. Published/Subscribed Tab

3BDD012902R4101 297
Structure of the Published/Subscribed Tab Section 10 FF Signals

Table 66. Published/Subscribed Tab

Dialog element Description

Default publisher cycle The parameter Cycle Time for a new created
time (ms) signal/channel mapping is preset to the value specified
here.
Channel Name of the I/O channel.
Data type Data type of the I/O channel. The data type must match
that of the FF signal. One of the following data types acc.
to FF-890 can be chosen:
Analog (DS-65)
Discrete (DS-66)
Direction Direction of data transfer, refer to Table 67.
FF signal Name of the FF signal that is mapped. If the FF signal
name entered has not yet been defined, then the dialog
for defining an FF signal is opened.
Cycle Time For direction "FF IEC 61131": Monitoring time.
For direction "IEC 61131 FF": Republishing cycle
time.
EU The unit of measure (engineering unit) on the FF side
configured for this signal.
Comment Comment on the signal-channel-mapping (max. 40
characters).
Calculated FF The communication load of the HSE host calculated in
communication load percent on the basis of the configured signal/channel
mappings.

298 3BDD012902R4101
Section 10 FF Signals Configure Signal-Channel-Mapping

Table 67. Direction of Data Transfer

Direction Source Sink

FF IEC61131 FF network outside the FF network
IEC61131 FF outside the FF network FF network

Configure Signal-Channel-Mapping
To configure a new signal-channel-mapping on the Published/Subscribed tab the
usual procedure, where the FF signal already exists in the FF signal list, involves
carrying out the following steps:
1. Context menu > Create Component
2. Choose an I/O channel from the selection list.
3. Select the input field in the FF Signal column.
4. F2
5. Select an FF signal of usage type HSE + H1 or HSE + H1 (LP) in the signal
selection list, and click OK.
6. The default value in the Cycle Time column can be modified if required.
7. An optional Comment can be entered.
8. Click OK.
If the FF signal does not yet exist in the FF signal list, then the following steps
should be carried out:
1. Context menu > Create Component
2. Choose an I/O channel from the selection list.
3. Select the input field in the FF Signal column.
4. Enter name of the new FF signal to be created.
5. Enter data in the FF signal definition mask (refer to Adding an FF Signal to an
FF Application on page 317).

3BDD012902R4101 299
Delete Signal-Channel-Mapping Section 10 FF Signals

6. The default value in the Cycle Time column can be modified if required.
7. An optional Comment can be entered.
8. Click OK.

Delete Signal-Channel-Mapping
In order to delete a signal-channel-mapping, the following steps should be carried
out on the Published/Subscribed tab:
1. Select line
2. Context menu > Delete component
3. Click OK

300 3BDD012902R4101
 Section 11 FF Application Editor

FF Application
To configure the function block application process described in the FF
specification, Fieldbus Builder FF uses the FF Application. This is generated using
the FF Application Editor. An FF Application comprises the Function Block
Application Process for an H1 link, or part thereof.
In accordance with the FF specification, the function block application process is
described with the aid of function blocks. Function blocks create for themselves
repetitive time-critical functions as parameterizable algorithms which convert input
parameters into output parameters taking into account the specified operating mode
and other internal parameters. For this purpose, Fieldbus Builder FF uses FF
function blocks, which are placed in an FF Application. All the FF function blocks
used in an FF Application are processed with the same cycle time. This cycle time is
assigned to the FF Application. Parameters for the block algorithm are set using the
parameter dialog for the FF function block. This dialog can be called from the FF
Application Editor.
Function blocks are linked with one another by linking the output of one function
block with the input of another. The linked function blocks may be located either on
the same device or different devices. In an FF Application, the connections formed
by signal flow lines are represented. Signal connections between different FF
Applications are modeled using local FF signals.
Signals that are communicated on the HSE subnet must be of usage type HSE + H1.
With signals of this usage type it is possible to configure a signal exchange between
different H1 links and a signal exchange with a system outside the FF network (e.g.
an IEC 61131 controller).
In addition to the function blocks and link objects, the FF specification also provides
for the use of resource and transducer blocks for modelling a function block
application process. These device-related blocks do not appear in the FF

3BDD012902R4101 301
Create FF Application Section 11 FF Application Editor

Application Editor. The parameter dialogs for these blocks can be called up using
the corresponding device instance objects in the FF Object Editor structure.
This version of Fieldbus Builder FF does not support the trend, alarm and view
objects provided in the FF specification for modelling a Function Block Application
Process.
The FF Application thus comprises the following graphical elements:
• FF function blocks.
• Signal flow lines.
• FF signals.
The work area is laid out over 10 x 10 pages. The separate pages can be reached
scrolling horizontally and vertically. The entire work area is provided with a grid.
The page breaks are indicated by a dashed line. When the program documentation is
printed out page-by-page, each page exactly reflects a page in the work area.
The signal flow of an FF Application runs from a signal source (read) symbol or an
FF function block output to a signal sink (write) symbol or a function block input.
The signal flow lines are edited either by pressing and holding down the CTRL key
or by activating Line drawing mode.
The processing sequence of the FF function blocks is determined automatically
according to the signal flow, and can subsequently be changed using the schedule
editor. Refer to Data Exchange on page 331.
FF signals can be declared in the FF Application Editor and then pasted into the FF
Application. FF signals that have already been declared can be selected from the FF
signal list of the HSE subnet and pasted into the FF Application. For further details
refer to FF Signal List on page 288.

Create FF Application
A new FF Application is created in the FF Object Editor structure. FF Application
objects can be added there underneath an H1 Schedule object.
1. Select H1 Schedule object.
2. Edit > Insert

302 3BDD012902R4101
Section 11 FF Application Editor Edit FF Application

Each new FF Application has an empty graphics area and a default cycle time of 500
milliseconds. Name, short text and long text contain null strings. The editing status
is incorrect.

Edit FF Application
The FF Application Editor is the detail view of each FF Application object (FF
Application). An FF Application is therefore called up for editing by simply
selecting the corresponding object in the FF Object Editor structure. When an FF
Application is called up, it is displayed with its content (function blocks, signal flow
lines etc.) and can be modified.
Select FF Application object in the FF Object Editor structure.

Configuration Interface of the FF Application Editor

Structure of the Configuration Interface
The configuration interface of the FF Application Editor comprises two windows:
the graphics area and the function block selection area. Refer to Figure 133.

3BDD012902R4101 303
Configuration Interface of the FF Application Editor Section 11 FF Application Editor

The status line at the bottom of the screen displays the current FF Application
status.

Figure 133. FF Application Editor Configuration Interface

FF function blocks and FF signals are placed in the graphics area and linked by
means of signal flow lines. The graphics area is provided with a grid to enable the
elements to be positioned easily and for minimum clearance between elements to be
maintained. Graphic elements can only be positioned on this grid in the graphics
area. The grid display can be switched on or off.
An FF Application can be up to 10 x 10 pages in size. The separate pages are
divided by dashed lines. Care should be taken to avoid positioning any objects on
the dashed lines as they would then be split up over two pages when the
documentation is printed.

304 3BDD012902R4101
Section 11 FF Application Editor Configuration Interface of the FF Application Editor

The function block selection area is used for selecting the FF function blocks that
are to be placed in the FF Application. It comprises two tabs which enable FF
function blocks to be selected from library view or link view.

Lib Tab
If an FF function block is to be added to an FF Application, the required FF function
block type can be chosen from the library view. Refer to Figure 134. The library
view contains all the FF function block types that can be used in the project, and is
structured in the same way as the block library.
If the selection is made from the library view, then the FF function block that is
placed in the FF Application is not yet assigned to a device.

Figure 134. Lib Tab

Link View Tab

The link view offers an alternative means of selection when adding an FF function
block to an FF Application. Refer to Figure 135. The required FF function block
instance from a device configured in the H1 link can be selected here. For this
purpose, the link view shows the devices configured in an H1 link in a tree structure

3BDD012902R4101 305
Changing the Defaults Section 11 FF Application Editor

along with their function blocks. The graphical representation of the function blocks
differentiates between those that have been assigned to an FF Application
(represented as grey blocks) and those that have not been assigned to an FF
Application (represented as yellow blocks).
When selected from the link view, the FF function block that is placed in the FF
Application is automatically assigned to a device.

Figure 135. Link View Tab

Changing the Defaults

Showing / Hiding the Grid

FF Application > Show grid toggles the grid.
A checkmark behind the menu indicates the current setting. When this setting is
changed, the change remains until the "show grid" menu item is deselected.

306 3BDD012902R4101
Section 11 FF Application Editor Description of the FF Application Elements

Change Colors of FF Application

1. FF Application > Color
2. Select object whose color is to be changed (for example the color for the
function block border).
3. Select desired color.
The color settings can be modified for the following objects, refer to Figure 136:

Figure 136. Color Settings

Description of the FF Application Elements

Signal Flow Lines
Horizontal and vertical connecting lines can be linked to FF signal symbols and FF
function block connections. These signal flow lines represent the signal flow in an
FF function block application process. Signal flow lines always link one signal
source (e.g. FF signal source (read) symbol or FF function block output) with one or
more signal sinks (e.g. FF signal sink (write) symbol or FF function block input).

FF Signal Symbols
FF signal symbols can be positioned anywhere in the FF Application, and are
displayed and edited in a rectangular border.

3BDD012902R4101 307
FF Signal Symbols Section 11 FF Application Editor

There are different graphical representations for FF signals used only within the H1
link and for those which are also used outside the H1 link. The symbol for an FF
signal that is used only within the H1 link is distinguished by an additional vertical
line alongside the left symbol border.
The graphical representation also enables an FF signal source to be distinguished
from an FF signal sink. The symbol for an FF signal source (read) has an output pin
on its right side. The symbol for an FF signal sink (write) has an input pin on its left
side.
Furthermore, there are both short and long versions of the graphical representation
of an FF signal. The short version can display 10 characters. If the label is more than
10 characters in length, the overflow is represented by ‘...’. The long version can
accommodate the maximum possible label length.

Table 68. FF Signal Symbols

Symbol Description/function:
FF Signal Source (read). Also used outside the H1 link

FF Signal Sink (write). Also used outside the H1 link.

FF Signal Source (read). Used only within the H1 link

FF Signal Sink (write). Used only within the H1 link

Short version
Max. 10 characters can be displayed,
overflow indicated by ’...’
Long version
Max. possible label length

A red FF signal symbol indicates that the FF signal assigned to this incidence point
does not exist, e.g. because it has been renamed or deleted in the FF signal list.

308 3BDD012902R4101
Section 11 FF Application Editor FF Function Blocks

FF Function Blocks
Figure 137 provides an example of the graphical representation of an FF Function
Block. Elements are explained in Figure 69.

Figure 137. FF Function Block

Table 69. FF Function Block

Block element Description

Block border The block border delineates the selection area of the FF
function block. Its color indicates whether or not the
function block is selected. The colors used for this
purpose can be changed. Refer to Changing the
Defaults on page 306.
Block name The block name is the tag name of the FF function block.
It is displayed in the header area of the graphical
representation of every FF function block. All FF function
block names are found again in the system-wide tag list.

3BDD012902R4101 309
FF Function Blocks Section 11 FF Application Editor

Table 69. FF Function Block

Block element Description

Icon An icon symbolizes the type of the FF function block. An
FF standard function block and all the enhanced function
blocks based on it are represented by the same icon.
Custom function blocks are represented by a standard
FF icon.
Type Name The type name shown below the icon uniquely identifies
the type of the FF function block within a project. The
type name is the name of the related FF block class. It is
defined during the FF device import and appears in the
FF block library among other places.
Input/output pins Input/output pins represent the input and output
parameters of an FF function block. In accordance with
the signal flow, the inputs are always on the left and the
outputs always on the right. The color and line width of
the input/output pins – as with the signal flow lines –
provide information about the data type that is required
or has been set.
Pin designation A code adjacent to each input/output pin in an FF
function block identifies the pin within the block and
reflects its function. Thus, for example, IN designates the
primary input value for a function block. The pin
designations of the input and output parameters of FF
function blocks can be found in the FF specification and
in the manufacturer’s documentation.
Assigned device
In the footer area of the graphical representation of an
FF function block appears the tag name of the device, in
which the function block is processed. Function blocks
that have not yet been assigned to a device display the
string <?>.

310 3BDD012902R4101
Section 11 FF Application Editor Comments

Comments
Comments can be positioned anywhere in the FF Application, and are displayed and
edited in a rectangular border. While placing a comment the size of the box can be
choosen.

Set Parameters for the FF Application Elements

In order to set parameters for an FF Application element, the following steps must
be taken:
1. Select FF Application element for which parameters are to be set.
2. Edit > Parameters.
Alternatively:
Double-click on the FF Application element.

FF Signals
For Parameter settings for FF signal, refer to Figure 138 and Table 70

Figure 138. Parameter Settings FF Signal

3BDD012902R4101 311
FF Function Blocks Section 11 FF Application Editor

Table 70. Parameter Settings FF Signal

Dialog element Description

Signal Name of the FF signal
An FF signal can be selected from the FF signal list by
pressing F2. If, on the other hand, a signal name is
entered which is not yet included in the FF signal list,
then a dialog box is displayed for creating a new FF
signal (refer to Create New FF Signal in an FF
Application on page 295).
Width
Short The short version of FF signal is chosen, in which only
10 characters can be displayed. If the signal name is
more than 10 characters in length, this is indicated by
’...’.
Long The long version of FF signal is chosen, in which signal
names of maximum length can be displayed.

FF Function Blocks

Parameter Types
Parameters are defined as data that is necessary for a block to be processed and
displayed in the system. The following distinctions are made (refer to Table 71):

Table 71. Parameter Types

Parameter Type Description

Mandatory Essential data such as the block name (tag name).
Optional Not necessarily essential data such as short text and
long text.

312 3BDD012902R4101
Section 11 FF Application Editor FF Function Blocks

Table 71. Parameter Types

Parameter Type Description

External Are passed to a function block by connecting a signal
flow line and vice versa.
Internal Are entered within a parameter dialog. These include
details such as block name and limit values.

Calling up the Parameter Dialogs

1. Select the FF function block for which parameters are to be entered.
2. Edit > Parameter
Alternatively:
Double-click on the FF function block for which parameters are to be entered.
Control passes to the first parameter dialog for an FF function block. Any other
selected elements are now automatically deselected. After exiting from the
parameter dialog, the FF function block whose parameters have been changed is re-
displayed accordingly.

Entering Mandatory Parameters

To enable an FF Application to be signed off as correct, the mandatory parameters
of the individual FF function blocks in the FF Application must be specified. All the
mandatory parameters are displayed with a red background in the parameter
dialogs. As a rule these are only the block name (max. 16 characters) of an FF
function block.
All the names entered for FF function blocks throughout the system are compiled in
the tag list. Refer to Tag List on page 116.

Alternative Facility for Entering the Block Name

1. Select text field name > F2.
2. Choose block name from tag list.

3BDD012902R4101 313
Comments Section 11 FF Application Editor

Contents and Interface of the Parameter Dialogs

Refer to FF Block Instance Object on page 234.

Comments
The only parameter of a comment box is the comment text to be displayed in the FF
application. If the text entered in the configuration dialog does not fit into the box,
the complete text is displayed as a tool tip if the coursor is positioned above the box.

Editing an FF Application
Drawing Signal Flow Lines
Signal flow lines can either be drawn explicitly or created automatically by the
system. To draw the lines explicitly, horizontal and vertical line sections are defined.
If the signal paths are to be determined automatically it is necessary only to specify
the start and end points of the signal flow.

Explicit Drawing of Signal Flow Lines

The FF Application Editor has a special drawing mode in which horizontal and
vertical signal flow lines can be drawn.

Activating Drawing Mode:

FF Application > Draw lines
Alternatively:
1. Right mouse button (context menu)
2. Draw lines (The mouse pointer changes to a cross)
A single left-click marks the start of the line. When the mouse is moved, a
horizontal or vertical line is drawn as long as the cursor is within the snap, and as
long as the line does not cut into any function block or FF variable.
Another left-click marks the end of the line and the start of a new line. A left-click
in the direct snap of the start of a line or outside the snap has the effect of ending a
line.

314 3BDD012902R4101
Section 11 FF Application Editor Editing an FF Application

Figure 139 below clarifies the drawing mode for drawing a line. The snap is exactly
two grid units in width.

Direct snap

Snap

Start of line

Possible lines

Figure 139. Drawing Signal Flow Lines

Drawing a Line
With drawing mode activated: define start and end of line with a left mouse-click.
Alternatively:
With drawing mode not activated: define start and end of line with a left mouse-
click while simultaneously holding down the CTRL key.
A signal flow line can also be drawn directly by pressing the CTRL key and the left
mouse button simultaneously. When the left mouse button is released, this defines a
horizontal or vertical line section.
Releasing the CTRL key has the effect of exiting line-drawing mode.

3BDD012902R4101 315
Editing an FF Application Section 11 FF Application Editor

Deactivating Drawing Mode:

Right-click or ESC key

Automatic Drawing of Signal Flow Lines

1. Start of a signal flow line:
Press CTRL key + SHIFT key and left mouse button simultaneously.
2. Move mouse while keeping keys pressed.
3. End of a signal flow line:
Release all keys.
In order to draw signal flow lines automatically the keys CTRL and SHIFT are
pressed simultaneously. When the left mouse button is pressed, the start point of the
signal flow line is defined, and the end point is defined where the left mouse button
is released.
Once the start point has been defined, the cursor is moved with the mouse button
and the CTRL and SHIFT keys all held down. The possible path of the signal flow
line from the start point to the current cursor position is indicated. When the keys
are released the signal flow line is finally defined.
If there is not sufficient free space available in the drawing area, then the signal flow
line will not be drawn.

Displaying the Signal Flow Lines

A signal flow line indicates the transported data type. The editing status of the signal
flow line, such as error present, selected or not connected, is also displayed.
The transported data type and the editing status of the signal flow line can be seen
from the line width and color. The user can select any color (refer to Changing the

316 3BDD012902R4101
Section 11 FF Application Editor Adding an FF Signal to an FF Application

Defaults on page 306). The relationship between data type, editing status, line width
and the default color is shown in Table 72:

Table 72. Displaying the Signal Flow Lines

Data type/
Color Style Example
Editing status
Analog black wide
Discrete gray wide
Bitstring dark blue wide

Error present red narrow

Selected turquoise wide/narrow
Not connected black narrow

Adding an FF Signal to an FF Application

When an FF signal is added to an FF Application, only an incidence point is initially
added in the FF Application for the FF signal. Only when an FF signal is to be used
which is not yet contained in the FF signal list the new FF signal is automatically
added to the FF signal list. Refer to FF Signal List on page 288.
FF Application > Signal (read) or Signal (write)
Once the signal symbol that is to be added has been chosen for an FF signal source
(read) or an FF signal sink (write), the cursor is displayed as an outline of the FF
signal symbol. The FF signal symbol can be inserted in any position (with a left-
click). If it is not possible to place the signal, it continues to be displayed with an
outline and a warning tone is emitted.
If the symbol has been positioned successfully, the outline cursor continues to be
displayed and further FF signal symbols of the currently selected type can be added.
A right-click ends the insert operation.
Next, the parameter input dialog for this incidence point of the FF signal is called up
with a double-click of the left mouse button on the signal symbol. Refer to FF
Signal List on page 288.

3BDD012902R4101 317
Modifying an FF Signal in an FF Application Section 11 FF Application Editor

FF signals that have already been defined can be selected directly from the FF signal
list.
F2 > Select an FF signal that already exists in the project from the list.
If an FF signal is being used for the first time in the project, it is automatically
included in the FF signal list.
Using the same FF signal more than once as a signal source (read) is not
permitted and will result in an error.

Modifying an FF Signal in an FF Application

Strictly speaking, only an incidence point of an FF signal is changed in the FF
Application. If the name is inserted of an FF signal which is not yet contained in the
FF signal list, then this new FF signal is automatically added to the FF signal list.
Refer to FF Signal List on page 288.
1. Double-click on the FF signal to be modified.
2. Change FF signal name.
3. ENTER
or
1. F2
2. In the Select FF signal window, select one of the currently existing FF signals
on the HSE subnet.

The old FF signal is retained in the FF signal list.

If the modified FF signal is used in more than one place, the other incidence
points remain unaffected by the change.

Adding an FF Function Block

To add an FF function block to the FF Application, the required function block is
selected from the function block selection area and dragged to the graphics area of
the FF Application (drag and drop). There are two ways of achieving this, provided
by the Library view and Link view tabs respectively; these two methods differ both
in procedure and result, and they are described below. In one case, the function

318 3BDD012902R4101
Section 11 FF Application Editor Adding an FF Function Block

block that is added is not yet assigned to a device, while in the other case the device
assignment already exists.
Selection from Library View
1. Select the desired FF function block type from the library view.
2. Move the selected element to the desired position in the graphics area by
holding the left mouse button down and dragging it.
3. Insert the FF function block by releasing the left mouse button.
4. Either position the next function block of the same type by clicking the left
mouse button or terminate the operation with a right mouse button.
5. End positioning: ESC or right mouse button at any time.
After a function block type has been selected, a function block instance is
positioned in the graphics area. During this operation the function block is displayed
in diagrammatic form. After the function block has been inserted a border is
displayed again to indicate that another function block of the same type can now be
inserted.
The function block added to the FF Application in this way is not yet assigned to a
device. Assignment to a device must be performed subsequently.
Each FF function block has a parameter dialog which contains as defaults the values
that were entered for the block class. There are no defaults for the mandatory
parameters block name and assigned device.
The representation of the block must not overlap with other graphic elements in
the FF Application. The minimum clearance of three grid points from
input/output pins and two grid points vertically from other function blocks must
be maintained.

Selection from the Link View

1. Select the desired FF function block from the link view.
2. Move the selected element to the desired position in the graphics area by
holding the left mouse button down and dragging it.
3. Insert the FF function block by releasing the left mouse button.

3BDD012902R4101 319
Assigning an FF Function Block to a Device Section 11 FF Application Editor

The function block added to the FF Application in this way is already assigned to a
device.
Each FF block has a parameter dialog which contains as defaults the values that
were entered for the block class. Only the mandatory parameter block name has no
default.
The representation of the block must not overlap with other graphic elements in
the FF Application. The minimum clearance of three grid points from
input/output pins and two grid points vertically from other function blocks must
be maintained.

Assigning an FF Function Block to a Device

An FF function block that has been added to the FF Application from the library
view of function block selection is not initially assigned to a device. This
assignment must be performed subsequently by means of a drag and drop operation.
1. Select an unassigned FF function block from the link view.
2. Move the selected element to an unassigned FF function block of the same type
in the graphics area by holding the left mouse button down and dragging it.
3. Perform the assignment by releasing the left mouse button.
The FF function block in the FF Application is assigned to the corresponding
function block in the device.
If the FF function block from the library view is dropped on an already-assigned FF
function block in the graphics area, the assignment is changed following
confirmation from the user.
An existing device assignment can be cancelled via Cancel assignment on the
context menu of the FF function block.

Inserting Columns and Rows

Insert Columns
The insertion of columns affects the current FF Application. In the area of the upper
and lower border of the graphics area the form of the cursor changes to a black or
red horizontal double arrow. In the case of the black double arrow, when the left

320 3BDD012902R4101
Section 11 FF Application Editor Inserting Columns and Rows

mouse button is pressed a triangle with a vertical line appears, which can be moved
to the right in steps the size of a grid unit. This has the effect of inserting a
corresponding number of columns, with the part of the network to the right of the
vertical line being moved by the same number of grid units to the right.
When the mouse is moved, if the right-hand visible edge is reached the view scrolls.
The partial network can be moved only if it is not in contact with the right edge of
the graphics area and if the vertical line only cuts through horizontal connections.
Figure 140 clarifies the procedure for inserting columns.

Visible section

max. move

FBAD

Figure 140. Insert Columns

A red double arrow at the edge of the graphics area indicates that it is not possible
to insert columns in this position, e.g. because FF function blocks or FF signals
are cut.
Horizontal signal flow lines are elongated accordingly when columns are
inserted.

3BDD012902R4101 321
Block Operations Section 11 FF Application Editor

Insert Rows
The insertion of rows is similar to the insertion of columns. The double arrow and
triangle is positioned on the left or right-hand edge of the graphics area. The
movement is marked with a horizontal line. Vertical signal flow lines are elongated
accordingly when rows are inserted.

Block Operations

Selecting Individual FF Application Elements

Select by left-clicking on the desired FF Application element.
The whole area of the FF Application element forms the select field. The FF
Application element is selected for further editing and is displayed accordingly.
The default state is unselected.
Connection points of signal flow lines are never displayed as selected.

Selecting Several FF Application Elements at the Same Time

Holding the left mouse button down, stretch the frame around the elements to be
selected.
All elements that are completely enclosed within the frame are selected, and they
are displayed accordingly. In the case of signal flow lines, this applies to all sections
that lie entirely within the frame. Following selection, the desired operation can now
be performed as for individual elements. For example: Edit > Cut.

Selecting Additional FF Application Elements

1. Press and hold SHIFT key.
2. Select additional element.
An element is selected in addition to the existing selection and is displayed
accordingly.
It is also possible to select several elements by holding down SHIFT and
stretching the border.

322 3BDD012902R4101
Section 11 FF Application Editor Block Operations

Unselecting all Selected FF Application Elements

Left-click on an unoccupied position in the graphics area or select an unselected
element.
The FF Application elements are unselected and displayed accordingly.
If a different window is opened, any existing selection is automatically cancelled.

Removing Individual FF Application Elements from a Selection

Press and hold SHIFT key and click on the element to be unselected.
An element is removed from the existing selection and displayed accordingly.

Copy
Edit > Copy
Alternatively:
Context menu > Copy
During copying, the selected elements are transferred into an internal buffer. Any
elements that have been transferred to the internal buffer through an earlier copying
operation are overwritten. It is possible to see whether or not there are any elements
present in the internal buffer from the Paste item on the Edit menu or in the context
menu. If this menu item is disabled, this means that the internal clipboard is empty.
When function blocks are copied, their parameters are retained. However, the tag
name for the copy is deleted as it must be unique.

Cutting and Deleting

Edit > Cut or Delete
Alternatively:
Context menu Cut or Delete

3BDD012902R4101 323
Block Operations Section 11 FF Application Editor

If the selected elements have been cut, then they can be placed back in the same FF
Application by means of Paste. Cut has the effect of overwriting any elements that
are already present in the internal buffer.
If the elements are deleted, then they can no longer be pasted afterwards. Deleted
elements can only be restored by exiting the FF Application without saving.
When function blocks are cut, their parameter data and the tag name are transferred
along with them to the internal buffer, so that all the data is available again the next
time they are pasted.

Paste
The following options are available for pasting previously copied or cut elements:
Edit > Paste
Alternatively:
Context menu Paste
Following the paste, a surrounding rectangle with a dashed border appears at the
position at which the block was previously cut or copied.
Pasted function blocks are assigned the status incorrect. Their parameter data is
pasted with them. The tag name is only available if the function block was
previously cut.

Move Block
The following options are available for moving a block:
1. Click on a selected block and hold the left mouse button down. A rectangle is
then displayed surrounding the selected block. The block can now be moved by
moving the mouse. At the destination position the left mouse button is released
again. If the block cannot be inserted at the target position, a warning tone is
emitted to alert the user and the surrounding rectangle remains active.
2. If the cursor is moved into the rectangle that is displayed after a block is pasted,
it changes into a cross with an arrow for each horizontal and vertical direction
of movement. The block can then be moved by holding down the left mouse
button, moving the mouse, then releasing the mouse button at the target

324 3BDD012902R4101
Section 11 FF Application Editor Block Operations

position. If the block cannot be inserted at the target position, a warning tone is
emitted to alert the user and the surrounding rectangle remains active.
While the selected elements are being moved to a new position their outlines remain
visible. The move process has the effect of disconnecting any signal flow lines that
are involved. These must be corrected later. Parameter data and tag names are
retained for function blocks.

Move Block with Existing Links

If the existing links are to be retained when a block is moved, proceed as follows:
1. Click on a selected block and hold the left mouse button down. A rectangle will
appear surrounding the selected block.
The CTRL and SHIFT keys should also be pressed.
2. The block can be moved by holding down the left mouse button as well as the
CTRL and SHIFT keys while moving the mouse. A rectangle representing the
selected block is displayed, and any existing links are represented as a rubber
band. At the destination position the left mouse button is released again.
3. If it is possible to insert the block at the chosen destination position, a new path
is defined for all the signal flow lines which have previously been shown in
rubber band form. If the block cannot be inserted at the target position, a
warning tone is emitted to alert the user and the surrounding rectangle remains
active.

3BDD012902R4101 325
Block Operations Section 11 FF Application Editor

Figure 141 shows a block before, during and after being moved with existing links.

Figure 141. Move Block with Existing Links

Undo Action
Edit > Undo
Alternatively:

326 3BDD012902R4101
Section 11 FF Application Editor FF Signal List and Tag List

Context menu Undo

This function enables the last action performed to be undone. The status of the FF
Application object remains incorrect following the Undo until the next check is
performed.

FF Signal List and Tag List

FF Signal List
Select FF signal in the FF Application Editor > F2
The application switches to the FF signal list. From all the FF signals in the list for
the HSE subnet concerned, one FF signal can be selected and copied to the FF
Application. This operation is described in FF Signal List on page 288.

Tag List
System > Tag list
The tag list is called up. It contains a list of all the tag names that have been assigned
in the system. Refer to Tag List on page 116.
If tag names that have been assigned to FF function blocks in the FF Application
have been deleted in the tag list, then after returning from the tag list the entries
in the corresponding parameter dialogs will be empty and must be entered again.

Cross References
The cross references can be selected directly from the FF Application.
1. Select tag in the FF Application Editor.
2. Cross references or F5.
3. Select desired action.
Any of the following actions can be performed:
4. Show object: Call the incidence point for the tag.
5. Show declaration: Branch to the declaration of the tag in the tag list.

3BDD012902R4101 327
General Processing Functions Section 11 FF Application Editor

General Processing Functions

Save FF Application
FF Object editor > Save
The FF Application is saved without exiting from it. Even incorrect FF Application
objects can be saved and completed at a later time.
If the FF Application currently being edited (i.e. the detail view of the FF
Application object) is exited, the user is prompted to choose whether or not the
changes made since the last save are to be saved.
If changes are not saved on closing, or previously in the project tree, then
changes in the FF Application do not take effect.

Document FF Application
Tools > Document
This action switches from the FF Application Editor to documentation management.
Here, the project documentation is defined and printed on a user-specific basis.
Refer to Documentation on page 134.

Setting FF Application parameters

1. Select FF Application object in the FF Object Editor structure.
2. Edit > Parameters
Alternatively:
Double-click on the FF Application object in the FF Object Editor structure.

328 3BDD012902R4101
Section 11 FF Application Editor End FF Application Editing

The parameter dialog for the FF Application is opened. Refer to Figure 142 and
Table 73.

Figure 142. Parameter Settings FF Application

Table 73. Parameter Settings FF Application

Dialog element Description

Cycle Time All the FF function blocks in an FF Application are
processed cyclically using this cycle time.

End FF Application Editing

The FF Application Editor is the detail view of each FF Application object (FF
Application). The editing of an FF Application is therefore ended by selecting
another object in the FF Object Editor structure. The user is asked to choose
whether or not to save changes made since the last save.
The changes will not take effect in the FF Application if the project is not saved
when it is closed.

Producing Hard Copy

1. Options > Hardcopy
2. Confirm the printer settings in the Windows printing dialog.
The content of the screen is output to the printer.

3BDD012902R4101 329
Check FF Application Elements Section 11 FF Application Editor

Check FF Application Elements

1. Select FF Application element.
2. Tools > Check subtree
All inputs relevant to the function are checked for correct syntax and context. Any
errors and warnings that are discovered are displayed in the form of an error list. If
the check reveals errors, the editing status of the FF Application element is set to
incorrect.
Newly added, copied or moved FF Application elements have the editing status
incorrect.

Delete FF Application
1. FF Object Editor structure
2. Select FF Application that is to be deleted.
3. Edit > Delete
This action deletes the FF Application. The FF signals and tag names in other FF
Applications, in the FF signal list and the tag list are not affected, and can be
assigned again.

Copy and Paste FF Application

1. FF Object Editor structure
2. Select the FF Application that is to be copied.
3. Edit > Copy or CTRL+C
4. Select H1 Schedule object to which the FF Application is to be copied.
5. Edit > Paste or CTRL+V
6. Assign FF Application name.
The FF Application is copied and assigned under a new, unique name to an H1
link. The FF Application is copied in its current configuration, including the
parameters. The names of the FF function blocks are not copied. The copying of an
FF Application does not affect the declaration of FF signals or tags. The copied FF
Application object is labeled as incorrect.

330 3BDD012902R4101
Section 11 FF Application Editor Data Exchange

Data Exchange
Table 74 provides an overview of the possibilities for data exchange within the FF
network and between the FF network and another external system (e.g. IEC 61131
controller).

Table 74. Data Exchange FF Network and System

H1 <-> H1
H1 local
(different H1 <-> IEC 61131
(same H1 link)
H1 links)
• H1 HSE + H1 HSE + H1
Usage type • (HSE + H1) Signal-channel-
mapping required

Data Exchange Between FF Applications on an H1 Link

The FF Application for an H1 link are preferably linked via FF signals of usage type
H1. If the linking FF signals are also to be available on the HSE subnet, then usage
type HSE + H1 should be configured. Refer to Section 10, FF Signals.

Data Exchange Between FF Applications on Different H1 Links

FF Applications for different H1 links within an FF network are linked together via
FF signals of usage type HSE + H1. The usage type HSE + H1 makes an FF signal
available on the HSE subnet. Refer to Section 10, FF Signals.

Data Exchange Between the FF Network and a System Outside the FF

Network
FF signals of usage type HSE +H1 must be used for data exchange with a system
outside the FF network (e.g. with an IEC 61131 controller. This usage type makes
an FF signal available on the HSE subnet. Mapping of the FF signal to a channel of
the HSE Host object is configured using additional signal-channel mapping. Refer
to Section 10, FF Signals.

3BDD012902R4101 331
Data Exchange Section 11 FF Application Editor

332 3BDD012902R4101
 Section 12 Schedule Editor

H1 Schedule
The H1 scheduler produces the chronological sequence of processing (H1 schedule)
for an H1 link. Based on information from the FF Applications and the devices of
the link, the start times for the function blocks and the communication times within
a macro cycle are determined. The H1 schedule forms the basis for the configuration
data that is to be loaded onto the field devices.
With the help of the Schedule Editor, the automatically generated processing
sequence can be shown and modified in a graphical form.

Schedule Editor Interface

In the Schedule Editor the chronological processing sequence for an H1 link within
a macro cycle is represented in a graphical form.

3BDD012902R4101 333
Structure of the Graphical Display Section 12 Schedule Editor

Structure of the Graphical Display

Figure 143. Schedule Editor Interface

The times for function block processing and bus communication are represented by
blocks of corresponding length arranged on the time axis. The display interval is a
macro cycle.
All the communication blocks are grouped together in the right upper section of the
Figure 143. These represent the whole cyclical communication taking place in the
H1 link.
Additional sections containing both algorithm blocks and communication blocks are
grouped below. Each of these sections shows the chronological processing sequence
of an FF Application, also known as a loop.

334 3BDD012902R4101
Section 12 Schedule Editor Change Defaults

Additional information on each of the objects displayed can be shown using the
Properties window. Some of the data displayed can be edited. The window is opened
as follows:
1. Context menu of the object
2. Properties
The Block properties window for an algorithm block contains, for example, the start
time of the associated function block with reference to the start of the macro cycle
and its execution time. Refer to Figure 144.

Figure 144. Block Properties

Change Defaults

Change Colors
1. Context menu for the H1 Schedule > Colors

3BDD012902R4101 335
Edit H1 Schedule Section 12 Schedule Editor

2. Select object type whose color is to be changed (for example the color for the
communication block)
3. Select desired color
Objects of the corresponding type are displayed in the selected color.

Change Scaling of the Time Axis

1. Context menu for the H1 Schedule > Time Scale
2. Select desired time scale
The FF schedule is displayed with modified time axis scaling.
The scaling can be changed incrementally using the + or - keys on the numeric
keypad.

Edit H1 Schedule
The Schedule Editor is the detail view of each H1 Schedule object. An H1 schedule
(chronological processing sequence for an H1 link) is therefore called up for editing
by simply selecting the corresponding object in the FF Object Editor structure. The
H1 schedule that was called is displayed and can be modified.
1. Select H1 Schedule object in the FF Object Editor structure
When the H1 schedule is opened for the first time, the automatically-generated
optimized schedule for the H1 link is displayed.

Reserve Communication Time for Client/Server Communication

Communication time for client/server (C/S) communication can be reserved in the
form of equally spaced time slices which are incorporated in the automatic
generation of the chronological processing sequence. In addition to this an extra
time slice can be reserved at the end of the macro cycle.
To explicitely reserve communication time for client/server communication, adjust
the parameters in the Properties dialog of the H1 Schedule and restart schedule
generation:
1. Context menu for the H1 Schedule > Properties

336 3BDD012902R4101
Section 12 Schedule Editor Reserve Communication Time for Client/Server Communication

2. Enter appropriate values for the parameters Typ. C/S PDU delay, Typ. C/S
PDU duration and Max. C/S PDU duration. Refer to Figure 145 and
Table 75.
3. OK stores the C/S communication parameters and closes the Properties dialog.
4. Context menu for the H1 Schedule > Optimize
Restarting the H1 schedule generation with modified C/S communication
parameters will also rearrange manually moved blocks. Locking a loop is a
means to protect parts of the H1 schedule against modification. Refer to Lock
and Unlock Loop on page 339.

Figure 145. Schedule Properties

3BDD012902R4101 337
Move Block Section 12 Schedule Editor

Table 75. Parameters

Dialog element Description

Typ. C/S PDU delay This parameter indicates the spacing between the time
slices kept free for C/S communication. The default
value is 0 and indicates that there is no schedule
spacing.
Typ. C/S PDU duration This parameter describes the duration of the time slice
kept free for C/S communication.
Max. C/S PDU duration This parameter describes the duration of the time slice
kept free at the end of the macro cycle.

Move Block
A single block or several blocks of a loop can be moved on the time axis using the
mouse or by changing the start time in the Properties window for the block.

Move a Single Block

1. Hold left mouse button down and move a block
Alternatively:
1. Context menu for block Properties
2. Enter new value for Start Time
The selected block is moved on the time axis. It is assigned a different start time
within the macro cycle.

Move Several Blocks

1. Holding the CTRL key and the left mouse button down, move a block.
Alternatively:
1. Context menu for block > Properties
2. Select check box Move following blocks
3. Enter new value for Start Time

338 3BDD012902R4101
Section 12 Schedule Editor Optimize H1 Schedule

The selected block and all the dependent blocks of the loop in the signal flow (these
are generally the blocks lying to the right of the chosen block) are moved on the
time axis. They are assigned different start times within the macro cycle.

Lock and Unlock Loop

A loop can be protected against unintended modification by locking it. Locking is
recommended in particular after manual changes have been carried out (blocks
moved) in a loop.
In a locked loop and the associated FF Application, no actions which change the
signal flow can be performed. Thus, for example, it is not possible to move blocks
or change the cycle time in this loop. Likewise, the deletion or addition of function
blocks and signal lines and the modification of device assignments in the associated
FF Application are also not permitted. Setting parameters for function blocks and
signals, on the other hand, is permitted.
Lock Loop:
1. Context menu for the loop (select the header row of a loop section. It contains
the name and the cycle time of the associated FF Application)
2. Lock
The loop and the associated FF Application are locked.

Unlock Loop:
1. Context menu for the loop (select the header row of a loop section. It contains
the name and the cycle time of the associated FF Application)
2. Unlock
The lock on the loop and the associated FF Application is cancelled.

Optimize H1 Schedule
An H1 schedule is automatically optimized after changes have been made to an FF
Application from the H1 link.
However, the optimization of the H1 schedule can also be started manually:

3BDD012902R4101 339
Save H1 Schedule Section 12 Schedule Editor

1. Context menu for the H1 Schedule

2. Optimize

During optimization of the H1 schedule, locked loops are not changed.

Save H1 Schedule
1. Context menu for the H1 Schedule
2. Save
The H1 schedule is saved.

340 3BDD012902R4101
 Section 13 Commissioning FF Objects

General Description of Commissioning

Commissioning is the operating mode of Fieldbus Builder FF which permits
precommissioning and loading of objects. In addition, the commissioning mode
offers the opportunity of displaying and modifying online data.
In contrast to the configuration mode, however, no structural modifications may be
made to the objects. Precommissioning can be performed and the configuration data
can be loaded into the physical devices in commissioning mode, only if the whole
configured structure has undergone a plausibility check and download information
have been generated before.
Besides precommissioning and the loading of objects, the individual parameters of
the FF blocks can also be edited. Therefore, parameter setting of the FF blocks is
possible without reloading the FF Application objects concerned.
Despite similar interface, configuration and commissioning are two different
processes. Commissioning requires communication links with the devices on the
HSE subnet and the subsidiary H1 links.
It is possible to switch directly between configuration and commissioning modes.
In order to easily distinguish the two operating modes of Fieldbus Builder FF, it
is recommended to configure different tree view background colors for
configuration and commissioning mode. Refer to Change Background Color of
Tree View on page 104.

Start Commissioning
To commission an HSE subnet, communication links with the devices on the HSE
subnet and the subsidiary H1 links must be made. Communication setup takes place
automatically with the selection of the commissioning mode.

3BDD012902R4101 341
Start Commissioning Section 13 Commissioning FF Objects

FF object editor > Commissioning

Procedure for Commissioning

• Prerequisite: the whole project has passed the plausibility check and download
information has been generated. Refer to Check whole Project for Plausibility
on page 108.
• Change to commissioning mode.
• Perform precommissioning for all objects for which this is necessary
(discernible from engineering status, refer to Representation in the FF Object
Editor Structure on page 110).
• Load all objects for which this is necessary (discernible from engineering
status, refer to Representation in the FF Object Editor Structure on page 110).
• Display online parameters and if necessary, modify. Refer to Phase 3: Online
Parameter Settings on page 379.

Change from Commissioning to Configuration

FF Object editor > Configuration
The change to configuration mode is necessary e.g. if:
• Objects are to be inserted into the FF Object Editor structure or modified.
• Modifications to FF Application objects are undertaken, such as the insertion
of FF function blocks or modification of the cycle time.
• Modifications to the configuration of the OPC Server FF are to be undertaken.

Switch from Configuration to Commissioning

FF Object editor > Commissioning
Switching to commissioning mode is e.g. necessary if:
• the editing steps Precommissioning and/or Loading are to be performed for
objects.
• Parameter values of FF blocks in current system are to be modified.

342 3BDD012902R4101
Section 13 Commissioning FF Objects Commissioning Interface

Commissioning Interface
In commissioning, the same display forms apply for the objects in the FF Object
Editor structure as for configuration. Refer to Representation in the FF Object
Editor Structure on page 110. In addition, status information about the objects is
displayed. For details, refer to Display During Commissioning on page 343.

Display and Write Online Values

During commissioning it is often necessary to modify parameters and to monitor
the effects of parameter modification on-line.
Fieldbus Builder FF offers the following support in the commissioning mode:
• In the parameter dialogs of the FF blocks, the actual values (online values) of
the block parameters can be displayed and optionally included in the
configuration. Refer to Phase 3: Online Parameter Settings on page 379.
• In parameter dialogs of the FF blocks, parameter values may be modified and
loaded directly into the device. Refer to Phase 3: Online Parameter Settings on
page 379.
• In an FF Application, current values of the input and output block are displayed
as Tooltip. Refer to FF Application Object on page 347.

Display During Commissioning

In the commissioning mode of Fieldbus Builder FF, additional status information is
displayed:
• In the tree view of the FF Object Editor structure, the names of the objects
which do not appear with the configured values for tag name, device address
and device ID in the Live List are displayed in red.
• In the detail views of the HSE subnet and an H1 link as well as in the detail
views of the HSE and H1 devices, status displays appear. Status Displays for
the Objects on page 350 provides an overview.

3BDD012902R4101 343
HSE Subnet Object Section 13 Commissioning FF Objects

HSE Subnet Object

The detail view for the HSE Subnet object contains status information for the HSE
devices on the HSE subnet. Refer to Figure 146.
In the detail view for the HSE Subnet object there is no status information about
the HSE Hosts CI860. Neither a green checkmark for a correct HSE Host nor a
red caution symbol for an incorrect HSE Host is displayed.

Figure 146. HSE Subnet Object

344 3BDD012902R4101
Section 13 Commissioning FF Objects HSE Device Instance Object

HSE Device Instance Object

In the detail view for the HSE Device Instance object, status information is shown
both for the HSE device and for the H1 links (channels of the HSE device). Refer to
Figure 147.

Figure 147. HSE Device Instance Object

HSE Host Object

The HSE Host object is displayed in the same way in commissioning mode as in
configuration mode. The detail view does not contain any status information.

3BDD012902R4101 345
HSE Host Object Section 13 Commissioning FF Objects

Neither a green checkmark for a correct HSE Host nor a red caution symbol for an
incorrect HSE Host is shown. Refer to Figure 148.

Figure 148. HSE Host Object

346 3BDD012902R4101
Section 13 Commissioning FF Objects H1 Link Object

H1 Link Object
The detail view for the H1 Link object contains status information for the H1 link
(channel of the linking device) and for the field devices on that link. Refer to
Figure 149.

Figure 149. H1 Link Object

FF Application Object
The FF Application is displayed in the same way in commissioning mode as in
configuration mode. However, in commissioning mode the structure of the FF
Application cannot be altered.
The individual FF function blocks can be selected, and parameter values entered for
them. Commissioners also have certain functions at their disposal for testing the FF

3BDD012902R4101 347
FF Application Object Section 13 Commissioning FF Objects

Application. Thus, for example, if the cursor is placed on an FF signal or function

block pin, the current values are displayed. Refer to Figure 150.

Figure 150. FF Application Object

348 3BDD012902R4101
Section 13 Commissioning FF Objects H1 Device Instance Object

H1 Device Instance Object

The detail view for the H1 Device Instance object contains status information for the
field device. The instances of Resource blocks, Transducer blocks and Function
blocks are shown along with their actual operating mode. Refer to Figure 151.

Figure 151. H1 Device Instance Object

3BDD012902R4101 349
Status Displays for the Objects Section 13 Commissioning FF Objects

Status Displays for the Objects

Table 76, Table 77 and Table 78 list the status displays appearing in the
commissioning mode in the detail views of the FF Object Editor and point out
possible causes of error conditions as well as remedial measures.

Table 76. Status display for an HSE device

Status display Cause Remedial measure

Normal status. There is a none
connection to the HSE device;
the device appears in the Live
List.
A connection cannot be made
to an HSE device with the IP
address, the tag name and the
device ID shown.
• The physical HSE device • Connect the physical HSE
is not connected to the device to the HSE subnet.
HSE subnet.
• The Plant Explorer • Set up a connection between
Workplace, on which the Plant Explorer Workplace
Fieldbus Builder FF and the HSE subnet. If the
operates, is not Plant Explorer Workplace is
connected to the HSE not physically connected to
subnet. the HSE subnet, the
configuration of an OPC
Server FF is required for this.
• At least one of the • If necessary, modify the IP
configured parameters IP address in the configuration
address, tag name or and/or in the physical device
device ID does not and perform
accord with the current precommissioning for the
values of the physical HSE device again.
device.

350 3BDD012902R4101
Section 13 Commissioning FF Objects Status Displays for the Objects

Table 76. Status display for an HSE device

Status display Cause Remedial measure

Redundant linking device: none
normal status. There is a
connection with the primary
and secondary device; both
linking devices appear in the
Live List.

3BDD012902R4101 351
Status Displays for the Objects Section 13 Commissioning FF Objects

Table 76. Status display for an HSE device

Status display Cause Remedial measure

Redundant linking device: a
connection to a secondary
device cannot be set up. Only
the primary linking device
appears in the Live List.
• The secondary device is • Replace the defective
in a fault state; it is not physical HSE device. Note the
ready to take over the instructions for replacing a
primary role. defective linking device in a
redundant set of linking
devices. Refer to Case 1:
Replacement of a Redundant
Linking Device on page 384.
• The physical HSE device • Connect the physical HSE
is not connected to the device to the HSE subnet.
HSE subnet. Note the instructions for
commissioning a redundant
linking device in the User
Documentation on the FF
linking device.
• The configured IP • If necessary, modify the IP
address does not accord address in the configuration
with the current IP and/or in the physical device.
address of the physical Note the instructions for
device. commissioning a redundant
linking device in the User
Documentation on the FF
linking device.

352 3BDD012902R4101
Section 13 Commissioning FF Objects Status Displays for the Objects

Table 76. Status display for an HSE device

Status display Cause Remedial measure

Redundant linking device: a
connection cannot be set up
to any of the configured
devices of the redundancy
pair. None of the devices
appears in the Live List.
• Neither of the two • Connect the physical HSE
physical devices of the devices to the HSE subnet.
redundancy pair is Note the instructions for
connected to the HSE commissioning a redundant
subnet. linking device in the User
Documentation on the FF
linking device.
• The Plant Explorer • Set up a connection between
Workplace, on which the Plant Explorer Workplace
Fieldbus Builder FF and the HSE subnet. If the
operates, is not Plant Explorer Workplace is
connected to the HSE not physically connected to
subnet. the HSE subnet, the
configuration of an OPC
Server FF is required for this.
• The configured IP • If necessary, modify the IP-
addresses do not accord addresses in the configuration
with the current values in and/or in the physical devices
the physical devices. and perform
precommissioning for the
HSE device again. Note the
instructions for
commissioning a redundant
linking device in the User
Documentation on the FF
linking device.

3BDD012902R4101 353
Status Displays for the Objects Section 13 Commissioning FF Objects

Table 77. Status display for an H1 Link

Status display Cause Remedial measure

A connection to the H1 port in the HSE
device (FF linking device) cannot be
set up.
• A connection to the HSE device • Refer to Table 76.
(FF linking device) which contains
this H1 port cannot be set up. For
possible causes, refer to
Table 76.
• The H1 channel in the HSE device • Carry out precommissioning for the
(FF linking device) assigned to HSE device which contains this
this H1 link has not been port.
activated.

Table 78. Status display for an H1 device

Status display Cause Remedial measure

A connection cannot be made to an H1
device with the address, the tag name
and the device ID shown.
• A connection to the H1 port in the • Refer to Table 77.
HSE device (FF linking device)
cannot be set up. For possible
causes, refer to Table 77.
• The physical H1 device is not • Connect the physical H1 device to
connected to the H1 link. the H1 link.
• At least one of the configured • Carry out precommissioning for this
parameters address, tag name or H1 device.
device ID does not accord with the
current values of the physical
device.

354 3BDD012902R4101
Section 13 Commissioning FF Objects H1 Device Assignment Dialog

H1 Device Assignment Dialog

During precommissioning, each device which is physically connected to an H1 link
is assigned a configured H1 device. In the process, the configured tag name and the
bus address are written to the device. In addition, the device ID is read out from the
field device and entered in the configuration database. There are different ways to
assign devices for different types of applications.

Table 79. Device Assignment Status

Device is assigned, i. e.
• configured device with a device ID or
• device in the live list on a non-default bus address with a matching
configured device.
Device is not assigned, i. e.
• configured device without device ID or
• device in the live list on a default bus address (248 to 251) with a
matching configured device.
Device is not configured, i. e.
• device in the live list without a matching configured device.

Device Assignment via H1 Live List

Device assignment via the H1 live list should always be used for the assignment of
multiple devices for which no device ID has been entered yet in the configuration
database.
In the case of a device type with several revisions in the same plant, the device
assignment has to be started via the context menu of the device instance. Refer to
Assignment of a Single H1 Device on page 359 for a description of this dialog.
During device assignment, any function block application which may be present
in the physical device will be deleted.

If configured H1 devices are to be assigned to all H1 devices connected to the FF

network, then the following steps need to be carried out for all H1 links of the FF
network:

3BDD012902R4101 355
H1 Device Assignment Dialog Section 13 Commissioning FF Objects

1. Context menu for the H1 Link

2. Object > Live list...
3. Select a device that is currently available in the H1 link (list of active devices in
the left-hand section of the window).
4. Press and hold down the left mouse button and move it to the desired
configured device (list of configured devices in the right-hand section of the
window).
5. Wait until assignment progress window closes, then repeat steps 3 and 4 until
an active device is assigned to each configured device.
6. Press Close button.
Refer to Figure 152 and Table 80.

Figure 152. Device Assignment via H1 Live List

356 3BDD012902R4101
Section 13 Commissioning FF Objects H1 Device Assignment Dialog

Table 80. H1 Live List

Dialog element Description

Address Bus address of the device. When assigning a device, the
configured bus address is written to the active device.
PD Tag Tag name of the device. When assigning a device, the
configured PD Tag is written to the active device.
Device Type The device type serves as supplementary information for
the user when assigning the device. Only devices with
matching device type may be assigned.
Device ID Unique identification number for the device. The device
manufacturer assigns a unique device ID to each
individual device, and this ID never changes. When a
device is assigned, the device ID is read from the device
and added to the database.
A configured device for which no device ID has
been configured and which has not yet had a
bus subscriber assigned to it, appears with no
device ID in the list of configured devices.
Update The display of the live list is updated.
Show Only Unassigned A filter may be activated to reduce the number of
Devices displayed devices.
All active devices and all configured devices are
displayed.
Only unassigned devices are displayed. These are:
• configured devices with no device ID,
• active devices on temporary default addresses (248
.. 251),
• active devices on permanent addresses (20 .. 247)
that have no counterparts in the list of configured
devices.
Close The live list window is closed.

3BDD012902R4101 357
H1 Device Assignment Dialog Section 13 Commissioning FF Objects

Automatic Device Assignment with Pre-configured Device ID

H1 devices for which a device ID has already been entered in the configuration
database (see H1 Device Instance Object on page 233) can be assigned efficiently
via the automatic device assignment. The automatic device assignment can be
called up via the context menu of the HSE subnet, the HSE device (linking device)
or the H1 link. When calling via the HSE subnet, a configured H1 device is assigned
to all H1 devices which have not yet been assigned but which are physically
connected to the FF network and for which a device ID is entered in the
configuration database. When calling via the HSE device or H1 link, only the
corresponding sub tree is processed.
1. Context menu of the object (HSE Subnet, HSE Device or H1 Link)
2. Object > Assign all devices...
3. The upper section of the device assignment progress window shows the H1
devices that will be assigned.
4. Press Assign button.

358 3BDD012902R4101
Section 13 Commissioning FF Objects H1 Device Assignment Dialog

5. Wait until assignment of all devices in the list has been completed, then press
Close button.

Figure 153. Device Assignment Progress Window

Assignment of a Single H1 Device

To assign a single H1 device or an H1 device with several revisions of that device
type in the plant, call up the assignment dialog via the context menu of the H1
device.
In the case of a device type with several revisions in the same plant, it is required
to use this assignment dialog and to check the check-box Show Other Devices.
During device assignment, any function block application which may be present
in the physical device will be deleted.

1. Context menu for a device to which an active device from the live list is to be
assigned.
2. Object > Assign device ...
3. In the case of a device type with several revisions in this plant check Show
Other Devices.

3BDD012902R4101 359
Download Dialog Section 13 Commissioning FF Objects

4. Select a device from the displayed list of active devices.

5. Press Assign button.
6. Wait until device assignment progress window closes, then press Close button.

Figure 154. Device Assignment of Single H1 Device

The list of active devices to choose from only contains devices with a matching
device ID or device type. To display all active devices on that H1 link check the
check box Show Other Devices.

Download Dialog
After completing the precommissioning stage, the user defines the type and scope of
the download in the Download dialog and then starts the download. Various
download options allow the user to perfectly adapt the download to the current
operating status of the system. The tree view shows which objects will be loaded,
right down to the level of the function blocks. See Figure 155 and Table 82.

360 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Open Download Dialog

The Download dialog can be opened in commissioning mode at the HSE Subnet,
HSE Device, H1 Link or H1 Device object via the context menu or via the menu
bar:
1. Select object (HSE Subnet, HSE Device, H1 link, or H1 Device)
2. Object > Download...
As a general rule, the Download dialog should be opened via the context menu of
the HSE subnet. The download then covers the complete HSE subnet.
If the Download dialog is opened from an object other than the HSE subnet then the
download is restricted to a sub tree of the system structure. This type of download,
which is restricted to a sub tree, is also referred to as a partial download.
In general, the Download dialog should be opened via the context menu of the
HSE subnet to ensure that the download covers the entire HSE subnet. This is the
only way for the system to ensure that all of the required configuration data are
loaded.
Only an experienced user should open the Download dialog from any other object
than the HSE subnet. It is possible that not all configuration data will be loaded
during a partial download. This could lead, for example, to a permanent
interruption of the cyclical communications (HSE republishing on the HSE
subnet).
After carrying out a partial download, check whether any further objects need to
be loaded. To do this, open the Download dialog from the HSE subnet.

3BDD012902R4101 361
Download Dialog Section 13 Commissioning FF Objects

Elements of the Download Dialog

The tree representation of the Download dialog shows the object from which the
Download dialog was opened and the lower-level objects down to the block level.
Only the partial tree shown here is part of the download.

Figure 155. Download Dialog

After opening the Download dialog, version information is read out from the
physical devices. An activity indicator and two progress bars underneath the tree
representation indicate the current status of the on-going online version check. The
left vertical bar shows the progress for the individual devices, and the horizontal bar
to the right of it shows the overall progress of the version check for the entire tree.
The tree representation on the left half of the Download dialog shows the current
commissioning status for each object in the form of a symbol. Detailed information
appears in text form after the object name. Table 81 lists the possible
commissioning states and their symbols. The commissioning status of an object
indicates whether and in what form this object is loaded. It depends on the

362 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

configuration changes which have been applied, the version information read out
from the devices and the selected download options.

Table 81. Commissioning Status

• Version check has not yet been carried out for this object.

• The object will not be loaded. The loaded configuration data are
current.
• In case of a collapsed branch below this object, none of the objects in
the collapsed branch will be loaded. The loaded configuration data for
these objects are current.
• Loading is necessary for at least one object in the collapsed branch.
• Specific commissioning statuses for the object and all objects in the
collapsed branch can be displayed by expanding the branch.
• Only changed configuration data are loaded into the object
(incremental download).
• Only changed configuration data are loaded into the object
(incremental download).
• For an H1 link: The link active scheduler (LAS) is stopped during the
download, i.e. the application is interrupted.
• For an H1 device: The resource block is stopped. As a result, all of the
blocks in the device switch to Out of Service mode.
• The object is loaded with all configuration data (full download).

• The object is loaded with all configuration data (full download).

• For an H1 link: The link active scheduler (LAS) is stopped during the
download, i.e. the application is interrupted.
• For an H1 device: The resource block is stopped. As a result, all of the
blocks in the device switch to Out of Service mode.
• Although configuration of the block (i. e. block parameters) has
changed, block parameters are not loaded because the download
option Load changed block parameters is not selected.

3BDD012902R4101 363
Download Dialog Section 13 Commissioning FF Objects

Table 81. Commissioning Status

• The physical device cannot be reached on the bus.

• Precommissioning action is required for the object. Details should be

taken from the text in the download tree.

After a power fail it cannot be guaranteed that linking devices and H1 devices
have maintained the correct version information of the latest configuration.
Therefore, when the Download dialog is opened after a power fail the
automatically executed version check will detect version errors, which will lead
to a full download of these devices.
The top right corner of the window shows a comparison of version information for
the selected object from the configuration database and from the physical device.
The area underneath displays additional information for the selected object. This
includes details regarding configuration changes as well as hints to suggested user
actions.
In the bottom right of the window the user can select global download options.

Setting Download Options

The default setting for the download options - none of the download options
selected - will result in an incremental download without stopping LAS or H1 link
and not changing parameter settings as they are in the devices unless the
configuration changes made have such an impact on the link and function block
application that they can only be loaded with briefly interrupting the application.
Necessary interrupts are indicated as described above.
It is strongly recommended to keep the download options with the default
settings. The non-default options are only intended for users with in-depth FF
knowledge capable of judging the impact of the different options depending on
the respective status the application is in.

364 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Table 82 describes in detail the various download options.

Table 82. Download Dialog

Dialog element Description

Version information Version information from the configuration database and
from the physical device is compared for the object
selected in the download tree.
Download options
Force full download This download option enables the user to define whether
all or just the modified configuration data are loaded
during the download.
Download modified configuration data only
(incremental download).
This is the recommended setting. Only the modified
configuration data are loaded. Corresponding options
are also available to define whether block parameters
should be taken into account and whether the LAS is to
be stopped during the download.
Load all configuration data (full download).
All of the configuration data including the block
parameters are loaded and the LAS is stopped during
the download.

3BDD012902R4101 365
Download Dialog Section 13 Commissioning FF Objects

Table 82. Download Dialog

Dialog element Description

Load changed block With this download option the user can define whether
parameters changed parameters of function blocks, resource blocks
and transducer blocks should also be loaded during the
incremental download.
Do not load block parameters
This is the recommended setting.
Excluding the block parameters from the
download will leave the current block
parameters in the device unchanged. Changes
to block parameters you have made offline in
your configuration will not take effect until you
include the block parameters in the download.
Use the parameter dialog to reconcile the block
parameters in your device and in the
configuration database. Refer to Phase 3:
Online Parameter Settings on page 379.
Load changed block parameters. For consistency,
all of the block parameters are loaded for a device if at
least one of the parameters in that device has changed.
Including the block parameters in the download
will stop the affected devices for the duration of
the download. The devices will restart with the
downloaded parameters. This may lead to
discontinuity in process operation which could
cause severe damage. Ensure that
discontinuities are acceptable under the current
system conditions.
Block parameters are always loaded during a full
download (“Force full download” option selected).

366 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Table 82. Download Dialog

Dialog element Description

Stop LAS during With this download option the user can define whether
download the link active scheduler (LAS) is to be stopped and
therefore the cyclical communications on the H1 link are
to be interrupted during the incremental download.
Do not stop the LAS
This is the recommended setting. Select this option if
you do not want the publisher/subscriber
communications and therefore the application on the H1
link to be interrupted during the download. In this case it
will take slightly longer to transfer the configuration data
to the H1 devices. No client/server communications are
possible during this time, which may take up to several
macro cycles depending on the schedule.
Stop the LAS
This option allows fast loading of configuration data.
However, publisher/subscriber communications
therefore the application on the H1 link are interrupted.
Stopping the LAS will interrupt the execution of
the control application on the affected H1 link.
This may influence other dependent application
parts and lead to severe damage under
operating conditions! Please ensure that
stopping the LAS is acceptable under the
current system conditions.
The LAS is always stopped during a full download
(“Force full download” option selected).
Start Download Starts the download with the selected settings.
Cancel Ends the Download dialog. The selected settings are
discarded and no download is performed.

3BDD012902R4101 367
Download Dialog Section 13 Commissioning FF Objects

Context Menus of Objects in the Tree Representation

Table 83 lists the context menu entries which are available for the objects in the tree
representation of the Download dialog. They are described briefly below.

Table 83. Context menu of Objects in the Download Dialog

Available on...

(linking device)

(FB, RB, TB)

HSE subnet

HSE device

H1 device
H1 link

Block
Context menu entry

Start full download of device... X X

Write H1 Port address assignment... X
Restart version check X X X X
Force full download for device X X
Load changed block parameters X

Table 84. Context menu entries

Context menu entry Description

Start full download of Loads the complete configuration data into the device,
device... including the block parameters. This function is used
when replacing a device. For more details refer to
Replacing FF Devices on page 383.
Write H1 Port address Writes the port addresses of H1 ports. Execute, if
assignment... precommissioning symbol shows up at linking device
and additional information text requires write of H1 Port
address assignment.
Restart version check Restarts the process of reading out the version
information from the physical devices.

368 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Table 84. Context menu entries

Context menu entry Description

Force full download for This object-specific download option enables the user to
device define whether all or just the modified configuration data
are loaded into the device during the download.
It corresponds to the global download option “Force full
download” from Table 82, but is only effective for the
individual object.
Interaction with the global download option of
the Download dialog:
When the global download option is selected
(checked), the corresponding object-specific
download options are set to “checked” and
“read-only”.
When the global download option is deselected
(unchecked), the object-specific download
options are set to “unchecked” and “enabled”.
Load changed block With this object-specific download option the user can
parameters define whether changed parameters of function blocks,
resource blocks and transducer blocks should also be
loaded into the H1 device during the incremental
download.
It corresponds to the global download option with the
same name from Table 82, but is only effective for the
individual object.
Interaction with the global download option of
the Download dialog:
When the global download option is selected
(checked), the object-specific download options
are set to “checked” and “read-only”.
When the global download option is deselected
(unchecked), the object-specific download
options are set to “unchecked” and “enabled”.

3BDD012902R4101 369
Download Dialog Section 13 Commissioning FF Objects

Start download
To start the download with the selected options, press the Start Download button.
In a separate window the progress of the loading operation and any errors that may
occur are displayed, refer to Figure 156 and Table 85. Successful completion of the
download is indicated by the text “Total error count: 0; Download finished”. If the
download finishes with errors, not all configuration data have been loaded. In this
case each line in the right half of the window which has not been completed with an
“OK” indicates an error. In order to determine the cause of the error, the error class
and error subclass are shown in Table 86. Pressing the Close button will close the
progress windows as well as the Download dialog.

Figure 156. Load Parameters

370 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Table 85. Load Parameters

Dialog element Description

Show only errors If this checkbox is checked, only errors are displayed in
the right half of the window. Lines which have been
completed with an “OK” are suppressed.
Total error count The total number of errors that have occurred during
(text display on left) download is displayed. The display is updated during
download.
Successful completion of the download is indicated by a
total error count of “0” while Current action is “Download
finished”.
Current action The current download action is displayed during
(text display on right) download. Completion of download is indicated by
“Download finished”.
Cancel loading The loading of configuration data is cancelled.

List of Download Errors

Table 86 lists the error class and error subclass of errors that may occur during
download.

Table 86. Download Errors

Error Error Additional

Explanation
Class Subclass Description
0x01 VFD state
0 Other
0x02 Application reference
0 Other
0x01 Application unreachable

3BDD012902R4101 371
Download Dialog Section 13 Commissioning FF Objects

Table 86. Download Errors

Error Error Additional

Explanation
Class Subclass Description
0x03 Definition
0 Other
0x01 Object undefined
0x02 Object attributes inconsistent
0x03 Name already exists
0x04 Resource
0 Other
0x01 Memory unavailable
0x05 Service
0 Other
0x01 Object state conflict
0x02 PDU size
0x03 Object constraint conflict
0x04 Parameter inconsistent
0x05 Illegal parameter

372 3BDD012902R4101
Section 13 Commissioning FF Objects Download Dialog

Table 86. Download Errors

Error Error Additional

Explanation
Class Subclass Description
0x06 Access
0 Other
0x01 Object invalidated
0x02 Hardware fault
0x03 Object access denied
0x04 Invalid address
0x05 Object attribute inconsistent
0x06 Object access unsupported
0x07 Object non-existent
0x08 Type conflict
0x09 Named access unsupported
0x0A Access to element unsupported
0x07 Object Dictionary
0 Other
0x01 Name length overflow
0x02 OD overflow
0x03 OD write-protected
0x04 Extension length overflow
0x05 OD description length overflow
0x06 Operational problem

3BDD012902R4101 373
Commissioning of an FF Network Section 13 Commissioning FF Objects

Table 86. Download Errors

Error Error Additional

Explanation
Class Subclass Description
0x08 This error class contains manufacturer-
specific error subclasses. FF specification
FF-890, Function Block Application
Process, Part 1 defines the reason codes
(Additional Description) listed in this table.
0
0x01 Parameter Check
0x02 Exceeds Parameter Limits
0x03 Wrong Mode for Request
0x04 Write is prohibited by write lock switch
0x05 Data value is never writeable
0x06 Instantiate Not Supported/Unsuccessful
0x07 Delete Not Supported/Unsuccessful
0x08 Alarm already acknowledged

Commissioning of an FF Network
Before starting commissioning, the whole project must have undergone a successful
plausibility check and download information must have been generated. Plausibility
checking and generating download information takes place in the configuration
mode of Fieldbus Builder FF (Tools > Check whole project...). The result can be
detected from the engineering status of the objects in the FF Object Editor structure.
Refer to Representation in the FF Object Editor Structure on page 110.

374 3BDD012902R4101
Section 13 Commissioning FF Objects Commissioning of an FF Network

Furthermore, all devices to be commissioned must be physically connected to the

corresponding section of the FF network (HSE subnet, H1 link) so that the physical
conditions for setting up online connections to the FF devices are met.
Normally the PC on which the Fieldbus Builder FF is running is not connected
directly to the HSE subnet (or, more accurately, the IP address of the PC and the
network address of the HSE subnet are not located in the same IP subnet). In this
case an OPC Server FF must be installed. It makes available the communication
channel between the Fieldbus Builder FF and the FF network which is required
for loading the configuration data.
General information regarding the Commissioning operating mode can be found in
General Description of Commissioning on page 341.
The steps described below for commissioning an FF network are performed in
Fieldbus Builder FF commissioning mode.
The commissioning of an FF network is divided into the following three phases:
1. Precommissioning: precommissioning is performed for all objects for which
this is necessary (detectable from the engineering status, refer to
Representation in the FF Object Editor Structure on page 110, Table 12,
Table 13).
2. Loading: all objects for which this is necessary are loaded (detectable from the
engineering status, refer to Representation in the FF Object Editor Structure on
page 110, Table 12, Table 13).
3. Online parameter settings: online values of block parameters are displayed and
if necessary, modified. Refer to Phase 3: Online Parameter Settings on page
379.

It is strongly recommended that the editing steps of one phase be concluded for
all objects of the FF network before the editing steps of the subsequent phase are
started. In concrete terms this means: precommissioning should be concluded for
all devices before a device is loaded.
The list known as the HSE Live List forms a resource for the commissioning
operation. This is a hierarchical representation of all FF devices actually present in
the FF network.

3BDD012902R4101 375
Phase 1: Precommissioning Section 13 Commissioning FF Objects

Phase 1: Precommissioning

Precommissioning of Linking Devices

The first step in the commissioning of an FF network is the initialization of the FF
linking device followed by the assignment of addresses. In this step the FF linking
device is initialized, and the tag name of the FF linking device and the link
addresses of the H1 links are loaded.
It is recommended to execute the function Linking device initialization and
address assignment only for initial precommissioning of a newly inserted
linking device. Please refer to Activate Single H1 Port on page 378 and Write H1
Port Address Assignment on page 378 for precommissioning actions required
after configuration changes.
In the case of a redundant set of linking devices with a large number of H1
devices connected, Linking device initialization and address assignment may
take up to 5 minutes. Do not cancel the action before.
Executing the function Linking device initialization and address assignment on
an operating linking device stops all HSE republishing and cyclical
communication on all H1 links of that linking device as well as client/server
communication to the linking device and the devices on the H1 links. A backup
LAS that may be configured in an H1 device will not keep the cyclical
communication on the corresponding H1 link running in this situation. No
cyclical or client/server communication on the H1 links of the affected linking
device is possible until a full download for the linking device is performed.
Select the linking device in the Download dialog, then select Start full download
of device... in the context menu.
This step must be performed for all FF linking devices on the HSE subnet:
1. Context menu for the FF linking device
2. Object > Linking device initialization and address assignment...
3. Press Start button.

376 3BDD012902R4101
Section 13 Commissioning FF Objects Phase 1: Precommissioning

Precommissioning of H1 Devices
In the second commissioning step, each device that is actually present on the H1
link is assigned to a configured device.
During device assignment, any function block application which may be present
in the physical device will be deleted.

This step must be performed for all H1 links in the FF network:

1. Context menu for the H1 Link
2. Object > Live list...
3. Select a device that is currently available in the H1 link (list of active devices in
the left-hand section of the window).
4. Press and hold down the left mouse button and move it to the desired
configured device (list of configured devices in the right-hand section of the
window).
5. Wait until assignment progress window closes, then repeat steps 3 and 4 until
an active device is assigned to each configured device.
6. Press Close button.
For details refer to Device Assignment via H1 Live List on page 355.
In the case of a device type with several revisions in the same plant, the device
assignment has to be started via the context menu of the device instance. Refer to
Assignment of a Single H1 Device on page 359 for a description of this dialog.
H1 devices for which a device ID has already been entered in the configuration
database (see H1 Device Instance Object on page 233) can be assigned efficiently
via the automatic device assignment. Refer to Automatic Device Assignment
with Pre-configured Device ID on page 358.

3BDD012902R4101 377
Precommissioning Options Section 13 Commissioning FF Objects

Precommissioning Options

Activate Single H1 Port

This option activates a newly configured H1 port. It requires that an initial linking
device initialization and address assignment has been carried out at least once. Refer
to Precommissioning of Linking Devices on page 376.
This option will activate the newly configured H1 port in the linking device
without impact on H1 communication in other links or HSE republishing.
1. Context menu for the H1 link
2. Object > Activate H1 port...
3. Press Start button
4. After successful completion press Close button.
For a complete precommissioning of this newly configured H1 link it is then
necessary to assign the configured H1 devices. Refer to Precommissioning of H1
Devices on page 377.

Write H1 Port Address Assignment

This option deactivates deleted H1 ports and writes the port addresses of newly
configured H1 ports. It requires that an initial linking device initialization and
address assignment has been carried out at least once. Refer to Precommissioning of
Linking Devices on page 376.
Use this option only if you intend to deactivate a deleted H1 port. For activating
newly configured H1 ports directly use the option described in Activate Single
H1 Port on page 378.
1. Context menu for the FF linking device
2. Object > Write H1 port address assignment...
3. Press Continue button
4. After successful completion press Close button.

378 3BDD012902R4101
Section 13 Commissioning FF Objects Phase 2: Loading

For a complete precommissioning of newly configured H1 links it is then necessary

to activate the H1 port and assign the configured H1 devices. Refer to Activate
Single H1 Port on page 378 and Precommissioning of H1 Devices on page 377.

Phase 2: Loading
This phase should not be started until precommissioning for all objects of the FF
network for which this is necessary has been successfully concluded. This is
detectable from the engineering status of the objects in the FF Object Editor
structure; refer to Status Displays for the Objects on page 350.
In this step of commissioning, the FF linking devices, all devices on the H1 links
along with their configuration data, and the OPC server are loaded.
1. Context menu for the HSE subnet.
2. Open download dialog: Object > Download...
3. Wait until version check has completed, then press Start Download button.
4. Successful completion of the download is indicated by the text “Total error
count: 0; Download finished”. Press Close button to close the progress
windows as well as the Download dialog.
For details regarding the Download dialog and various download options, please
refer to Download Dialog on page 360.
5. Context menu for OPC Server FF.
6. Start download: Object > Download...
If loading of the OPC Server FF is required (indicated by a download arrow), it is
strongly recommended to do this not before all other required downloads in
the HSE subnet have been executed.
For details regarding the download of the OPC Server FF, please refer to Loading
Project Data into OPC Server on page 264.

Phase 3: Online Parameter Settings

In commissioning mode, block parameters can be displayed, written and uploaded
in the parameters mask of the FF Function Block instance object (refer to
Figure 157). In the Parameters tab either the configured parameter values or the
current parameter values read from the device are displayed according to

3BDD012902R4101 379
Phase 3: Online Parameter Settings Section 13 Commissioning FF Objects

preference. The layout and contents of the tab correspond to those of the FF block
instance. Refer to Parameters Tab on page 236.

Figure 157. Online Parameter Settings

380 3BDD012902R4101
Section 13 Commissioning FF Objects Phase 3: Online Parameter Settings

Display Block Parameters

The buttons Current values and Config. values are used to change the display
mode (refer to Table 87):

Table 87. Online Parameter Settings

Dialog element Description

Current values The current parameter values, which are read cyclically
from the field device, are displayed.
Config. values The configured parameter values are displayed.

In Current values display mode, a table displayed with a yellow background

indicates that the current value read from the device is different from the configured
value.

Write Block Parameters

In Current values display mode, a parameter value can be edited in the Value
column and then written to the field device by means of the Write button.
Alternatively, the Correct button enables the new value to be written to the field
device and simultaneously copied into the configuration.
Once a parameter value has been modified, the following buttons are available (refer
to Table 88):

Table 88. Write Block Parameters

Dialog element Description

Write The new parameter value is written to the field device.
The configuration data is not changed.
Cancel The change to the parameter value is canceled.
Correct The new parameter value is written to the field device
and copied into the configuration.

3BDD012902R4101 381
Display Subscribers on the HSE Subnet Section 13 Commissioning FF Objects

Copy Block Parameters to the Configuration (Upload)

In Current values display mode the context menu allows the current values to be
copied from the device to the configuration (upload). By selecting an individual
parameter or a block of parameters, it is possible to upload the selected parameter
values selectively. If no parameters are selected then all the current parameter values
for the block are copied to the configuration.
Uploading an individual parameter value or a block of parameter values:
1. Select an individual parameter or block of parameters.
2. Context menu Upload marked
Uploading all parameter values for the function block:
1. No parameters are selected.
2. Context menu Upload all

Display Subscribers on the HSE Subnet

The HSE Live List is a commissioning tool. It provides a hierarchical representation
of all FF devices that are currently present in the HSE subnet and subsidiary H1
links. FF devices from other projects that may be present on the subnet are also
displayed.
1. Context menu for the FF linking device
2. Object > Live list (refer to Figure 158)

382 3BDD012902R4101
Section 13 Commissioning FF Objects Replacing FF Devices

Figure 158. HSE Live List

Replacing FF Devices
Replacing an FF Linking Device
The following cases must be distinguished:
• Case 1: The linking device to be replaced is a device in a redundancy pair; the
other linking device redundant to this device operates as the primary device.
• Case 2: The linking device to be replaced operates as a non-redundant device.
There is no redundant device for this.
Below there is a description of the steps necessary for replacement of this device for
each of these cases.

3BDD012902R4101 383
Replacing FF Devices Section 13 Commissioning FF Objects

Case 1: Replacement of a Redundant Linking Device

When a linking device which is part of a redundancy pair fails, the linking device
which is redundant for this device continues to operate as a primary device - if
necessary, after successful redundancy switchover.
In this case, the secondary linking device may be replaced by a device of the same
type with an identical firmware version and identical IP configuration without
adversely affecting communication, as the device functions are executed from the
primary device. If the firmware of the replacement device is different, a suitable
firmware must be downloaded to the replacement device: i.e. the firmware must be
either upgraded or downgraded to match the firmware of the primary linking device.
As the replacement device receives its configuration data from the current primary
device, it is not necessary to load the configuration data. Details regarding the
replacement of a redundant linking device can be found in the documentation of the
FF linking device.

Case 2: Replacement of a Non-redundant Linking Device

When a non-redundant FF linking device fails, cyclical communication on the
associated H1 links is generally maintained as long as Backup Link Masters have
been configured.
In this type of situation it is also possible to replace the FF linking device without
interrupting cyclical communication on the H1 links as long as the power supply to
the field devices on the H1 links is assured. In addition, the FF linking device must
be replaced with a device of the same type and with exactly the same firmware
version and IP configuration. If necessary, a firmware update should be
performed. For details refer to the documentation relating to the FF linking device.
Once the FF linking device has been replaced, precommissioning has to be carried
out and the configuration of the linking device has to be loaded.
1. Wait until the FF linking device restarts (show HSE live list).
2. Context menu for the HSE device (FF linking device).
3. Object > Linking device initialization and address assignment...
4. Press Start button.
5. Context menu for the HSE device (FF linking device).

384 3BDD012902R4101
Section 13 Commissioning FF Objects Replacing an H1 Device

6. Open Download dialog: Object > Download...

7. Context menu for the HSE device (FF linking device) in tree structure of
Download dialog.
8. Start full download of device...
9. Successful completion of the download is indicated by the text “Total error
count: 0; Download finished”. Press Close button to close the progress
windows as well as the Download dialog.
The configuration data for the FF linking device, including the local configuration
data for the H1 links, is loaded. The FF devices in the H1 links are not loaded during
this process.

Replacing an H1 Device
When an H1 device in an H1 link fails, the device must be reassigned after it has
been replaced. Next, the configuration of the H1 device must be loaded.
1. Context menu for the H1 device
2. Object > Assign device ...
3. Select a device from the displayed list of active devices.
4. Press Assign button.
5. Context menu for the H1 device
6. Open Download dialog: Object > Download...
7. Context menu for the H1 device in tree structure of Download dialog.
8. Start full download of device...
9. Successful completion of the download is indicated by the text “Total error
count: 0; Download finished”. Press Close button to close the progress
windows as well as the Download dialog.

3BDD012902R4101 385
Replacing an H1 Device Section 13 Commissioning FF Objects

386 3BDD012902R4101
 Section 14 FF Device Integration Library

Overview
The FOUNDATION Fieldbus Device Integration Library provides a set of pre-

Figure 159. Object Type Group FF Libraries in the Object Type Structure

integrated FOUNDATION Fieldbus device types. Device types provided with this

3BDD012902R4101 387
Functionality Section 14 FF Device Integration Library

library are available for immediate use in Fieldbus Builder FF as well as in Plant
Explorer.

Functionality

Functionality in Fieldbus Builder FF

The FF Device Integration Library provides the following additional functionality in
Fieldbus Builder FF:1
• Supplied device types are present in the H1 and HSE device libraries and
therefore need not be imported using Device Description and Capabilities files.
• Device-type-specific bitmaps for representing the device in Fieldbus Builder
FF are provided.
• The block library in Fieldbus Builder FF contains the standard function blocks
specified by the Fieldbus Foundation and additional blocks that come with the
supplied device types.
• For frequently used blocks, specific parameter input dialogs are available.
• For frequently used blocks, predefined block-type-specific parameter value sets
are available for selection on the FF Block Class object or FF Block Instance
object. These parameter value sets contain block-type-specific values for
selected block parameters that have proved to be useful initial values in the
commissioning of a variety of FF projects. For details on selecting these
parameter value sets at the block class, refer to Reset to User-Defined Values
on page 191. For selecting them at the block instance, refer to Reset to User-
Defined Values on page 240.

Functionality in Plant Explorer

In Plant Explorer for each device type that is supplied with the FF Device
Integration Library, a preconfigured object type with the following set of aspects is
provided in the FF H1 Device Library, FF Object Type Group catalog or in the FF
HSE Device Library, FF Object Type Group catalog respectively (refer to
Figure 159):

1. Note that using the full scope of the FOUNDATION Fieldbus Device Integration Library requires the Optimize
IT Asset Optimization software to be installed and licensed.

388 3BDD012902R4101
Section 14 FF Device Integration Library Prerequisites and Requirements

• Product Documentation
• Asset Monitors
• Asset Reporters
• Asset Viewers
• CMMS Connectivity
The preconfigured object types enable each device to
• access device-specific product documentation
• connect to Asset Optimization - a set of extensions that allow plant personnel to
collect, compare, and monitor field device data in order to accurately assess
equipment conditions in real time.
Furthermore in Plant Explorer a block library containing the standard function
blocks specified by the Fieldbus Foundation (refer to User Application on page 41)
and additional blocks that come with the supplied device types is provided in the FF
Block Library, FF Object Type Group catalog.
For a set of frequently used blocks, faceplates are provided. A block faceplate is the
graphical user interface for the operator to the specific process function
(analog/discrete input/output monitoring, PID controller, etc.). Faceplates are
accessible as aspects at the block instance. For detailed information on the provided
faceplates, please refer to the manual FOUNDATION Fieldbus Device Integration,
Operation.
For a complete list of currently supported devices, available blocks with specific
parameter input dialogs, and available function block faceplates, please refer to
the Release Notes of this product listed in Related Documentation on page 31.
For the FF Linking Device LD 800HSE an Asset Monitor in combination with a
Diagnostics Faceplate and Web Server aspects for connecting to the built-in web
server are provided.

Prerequisites and Requirements

The following requirements must be met, in order to get the full functionality
described in this section.

3BDD012902R4101 389
Prerequisites and Requirements Section 14 FF Device Integration Library

• The following system extensions that are provided with Field IT

FOUNDATION Fieldbus Device Integration have been added:
– Fieldbus Builder FF
adds functionality for configuration, commissioning, and management of
FOUNDATION Fieldbus networks, devices, and applications.
– FF Device Integration Library - Basics
provides a library of FOUNDATION Fieldbus devices that are integrated
in and interoperable with the Industrial IT 800xA system.
– FF Device Integration Library - Asset Monitoring
adds asset monitoring functionality to the object types belonging to the
FOUNDATION Fieldbus Device Integration Library.
• The following system extensions that are provided with Optimize IT Asset
Optimization have been added:
– Asset Monitor Environment
– Asset Optimizer Server
– Maximo Connectivity
For details on configuration of Asset Optimization functionality please refer to the
corresponding product documentation.

390 3BDD012902R4101
Section 14 FF Device Integration Library Device-Type-Specific Product Documentation

Device-Type-Specific Product Documentation

For each device type included in the FOUNDATION Fieldbus Device Integration
Library a Product Documentation aspect is provided at the device instance objects.
The Product Documentation aspect has the tabs listed in Table 89.

Table 89. Product Documentation Aspect

Tab Description
Documents This tab shows a list of available product documents.
For Industrial IT certified devices at least the following
categories are available:
• Application Manual
• Data Sheet
• Declarations
• Installation Manual
• Maintenance and Service Manual
• Operating Manual
• Product Classification
• Product Identification
View Document This tab shows the contents of the product document
that has been selected in the Documents tab.
Specific Device Type For certain device types several sets of product
documentation are available, depending on the
specific device type. This tab allows to select the
specific device type for this device instance.

When the Product Documentation aspect is selected at a device instance object

for which more than one set of product documents is available, the Specific
Device Type tab will show up until a specific device type has been selected. This
selection is stored, but can be modified at any time.

3BDD012902R4101 391
Connection to Asset Optimization Section 14 FF Device Integration Library

Connection to Asset Optimization

Asset Optimization consists of system extensions that allow plant personnel to
collect, compare, and monitor field device data in order to accurately assess
equipment conditions in real time.
Information can subsequently be used to set future performance and profitability
goals and to assist managers in making these decisions.
The Optimize IT Asset Optimization software consists of the following
components, for which the FOUNDATION Fieldbus Device Integration Library
provides a connection for its preconfigured field device types.

Asset Monitoring
Asset Monitoring provides the infrastructure that monitors, analyzes, and reports
asset status/condition information. It notifies operators and maintenance personnel
when an abnormal condition calls for maintenance. Asset Monitoring interacts with
third-party CMMS applications to optimize the use of plant equipment and
processes.
An Asset Monitor is an application for retrieving data from, and interacting with,
multiple data servers, e.g. OPC Servers. Asset Monitors can detect problems that
may not affect the process variables, but do affect the maintenance status of an asset
or process.
Prerequisite: The system extension Asset Monitor Environment must be added.

Aspects provided by FF Device Integration Library

For each device type included in the FOUNDATION Fieldbus Device Integration
Library a standard (generic) or a device-type-specific Asset Monitor is provided.
The aspects listed in Table 90 are present for the device types.

392 3BDD012902R4101
Section 14 FF Device Integration Library Asset Monitoring

Table 90. Aspects for interfacing with Asset Monitoring

Aspect Function
Asset Reporter The Asset Reporter provides a detailed view of an
asset condition for an object. It displays information
available to it from all Asset Monitors and their
corresponding current subconditions.
Asset Viewer When the Asset Viewer is present at an object, the
asset condition tree can be displayed. When
displayed, the asset condition tree shows the
condition of that object and all its children, visually
indicating the presence of a fault report by displaying
items in bold text. Context menus permit fault report
submission directly from within the Asset Viewer.
FF Generic Device Asset Standard Asset Monitor for FOUNDATION Fieldbus
Monitor devices.
FF <device_type> Asset Device-type-specific Asset Monitor for FOUNDATION
Monitor Fieldbus devices.
Maximo Equipment ID The Maximo Equipment ID provides information for
mapping the Industrial IT object to the Maximo
equipment in the CMMS database for a particular
Maximo Server. Multiple Maximo Equipment IDs can
be associated with the same asset, thus providing
the ability to map to more than one piece of
equipment defined in Maximo.

3BDD012902R4101 393
CMMS Connectivity Section 14 FF Device Integration Library

CMMS Connectivity
CMMS Connectivity establishes the link that removes the barrier to information
exchange between the Maximo Computerized Maintenance Management System
(CMMS) and the process control system environments and brings maintenance
management to the operator environment.
Context menus for process graphics, the alarm and event list, etc. provide access to a
number of views and actions for the specific CMMS item.
This allows plant personnel to collect, compare, and monitor field device data in
order to accurately assess equipment conditions in real time.
Prerequisite: The system extensions Asset Optimizer Server and Maximo
Connectivity must be added.

Aspects provided by FF Device Integration Library

For each device type included in the FOUNDATION Fieldbus Device Integration
Library a CMMS Connectivity connection to the MAXIMO Computerized
Maintenance Management System (CMMS) is provided by the aspects listed in
Table 91.

Table 91. Aspects for interfacing with CMMS

Aspect Function
View Active Work Orders Lists all active work orders in the CMMS for a
particular asset or group of assets.
View Equipment Status Allows data returned from a status assessment of an
asset or group of assets to be viewed.
View Preventive Lists the preventive maintenance schedule for an
Maintenance Schedule asset or group of assets.
View Spare Parts Lists spare parts in the CMMS for a particular asset
or group of assets.
View Work Order History Lists the history of all work orders in the CMMS for a
particular asset or group of assets.

394 3BDD012902R4101
Section 14 FF Device Integration Library Additional Aspects of LD 800HSE

Additional Aspects of LD 800HSE

For the FF Linking Device LD 800HSE the FF Device Integration Library provides
a set of additional aspects. These are:
• Asset Monitor in combination with a Diagnostics Faceplate:
The Asset Monitor observes the overall Linking Device status, the occurrence
of redundancy switch-overs, and changes in the Live Lists of the four H1 links.
The Diagnostics Faceplate complements the Asset Monitor for easy overview
on the current operating state of the Linking Device. It allows inhibiting the
Asset Monitor during configuration changes.
• Web Server aspects:
They allow for connecting to the built-in web server of the LD 800HSE.

Asset Monitor and Diagnostics Faceplate

The Asset Monitor shown in Figure 160 observes the conditions listed in Table 92.

Figure 160. Asset Monitor of LD 800HSE

3BDD012902R4101 395
Asset Monitor and Diagnostics Faceplate Section 14 FF Device Integration Library

Table 92. Conditions Observed by LD 800HSE Asset Monitor

Condition Subcondition Description

Linking Device Normal • In the case of a non-redundant
Status configuration:
Non-redundant Linking Device in Live List
• In the case of a redundant configuration:
Primary and Secondary Linking Devices in
Live List
No Secondary Device (LD1) Primary Device (LD2) in Live List, Secondary
Device (LD1) not in Live List
No Secondary Device (LD2) Primary Device (LD1) in Live List, Secondary
Device (LD2) not in Live List
No Primary Device (LD1) Primary Device (LD1) not in Live List,
Secondary Device (LD2) in Live List
No Primary Device (LD2) Primary Device (LD2) not in Live List,
Secondary Device (LD1) in Live List
Two Primary Devices Two Primary Devices in Live List
Two Secondary Devices Two Secondary Devices in Live List
No Primary Device, no No Primary and no Secondary Device in Live
Secondary Device List
Non-redundant Linking Device Non-redundant Linking Device not in Live List
is not present
Redundancy No
Switch-over
Current Primary Device is LD1 Redundancy switch-over occurred. Current
occurred
<ip_address> Primary Device is LD1.
Current Primary Device is LD2 Redundancy switch-over occurred. Current
<ip_address> Primary Device is LD2.
Failure: No Current Primary Redundancy switch-over failed. No current
Device Primary Device.

396 3BDD012902R4101
Section 14 FF Device Integration Library Asset Monitor and Diagnostics Faceplate

Table 92. Conditions Observed by LD 800HSE Asset Monitor

Condition Subcondition Description

Change in Live No
List of Link 1
occurred Primary Device (LD1) Change in the Live List of the Primary Device
(LD1) occurred.
Primary Device (LD2) Change in the Live List of the Primary Device
(LD2) occurred.
Secondary Device (LD1) Change in the Live List of the Secondary Device
(LD1) occurred.
Secondary Device (LD2) Change in the Live List of the Secondary Device
(LD2) occurred
Primary and Secondary Change in the Live List of the Primary and
Device Secondary Device occurred.
Change in Live Refer to condition “Change in Refer to condition “Change in Live List of Link 1
List of Link 2 Live List of Link 1 occurred”. occurred”.
occurred
Change in Live Refer to condition “Change in Refer to condition “Change in Live List of Link 1
List of Link 3 Live List of Link 1 occurred”. occurred”.
occurred
Change in Live Refer to condition “Change in Refer to condition “Change in Live List of Link 1
List of Link 4 Live List of Link 1 occurred”. occurred”.
occurred

The Asset Monitor is complemented by a Diagnostics Faceplate as shown in

Figure 161. The Diagnostics Faceplate provides an easy overview on the current
operating state of the Linking Device and allows for
• disabling/enabling the Asset Monitor (e. g. to avoid alarms that may be caused
by applying configuration changes to the Linking Device and the H1 links),
• acknowledging redundancy switch-over,
• acknowledging changes in the Live Lists of the H1 links.
For details on the Diagnostics Faceplate refer to Table 93.

3BDD012902R4101 397
Asset Monitor and Diagnostics Faceplate Section 14 FF Device Integration Library

Figure 161. Diagnostics Faceplate of LD 800HSE

Table 93. Contents of Diagnostics Faceplate

Element Description
Indicators Area
Asset Monitor is enabled.
The Asset Monitor conditions listed in Table 92
are observed and will lead to alarms. The
Diagnostics Faceplate shows current status
information.

398 3BDD012902R4101
Section 14 FF Device Integration Library Asset Monitor and Diagnostics Faceplate

Table 93. Contents of Diagnostics Faceplate

Element Description
Asset Monitor is disabled.
The Asset Monitor conditions are not observed
and the Diagnostics Faceplate does not show
current status information. This is indicated by red
diagonal bars across the faceplate.
Faceplate Element Area (left-hand section)
Linking Device Status Refer to the corresponding condition of the Asset
Monitor in Table 92. The currently active
subcondition is displayed here.
Redundancy Switch-over Refer to the corresponding condition of the Asset
occurred Monitor in Table 92. The currently active
subcondition supplemented by the date and time
of occurrence is displayed here.
Reset Press the Reset button to acknowledge the
redundancy switch-over indicated. This will reset
the corresponding condition of the Asset Monitor
to subcondition “No”.
Without pressing the reset button the
Asset Monitor and the faceplate indicate
the most recent redundancy switch-over.

3BDD012902R4101 399
Asset Monitor and Diagnostics Faceplate Section 14 FF Device Integration Library

Table 93. Contents of Diagnostics Faceplate

Element Description
Link 1 - Link 4 Summarizing information for each H1 link.
Possible values are:
• Normal,
i. e. the LAS status is “running” and no
change in the H1 Live List has occurred.
• Look for details in Link tab,
i. e. the LAS status is different from “running”
and/or a change in the H1 Live List has
occurred. Details are displayed in the
corresponding Link tab (right-hand section of
the faceplate).
• H1 link is not configured,
i. E. the H1 link has not been activated.
Faceplate Element Area (right-hand section)
LAS Status The current LAS status for the H1 link is displayed
here. The following states are indicated:
• running
• stopped
• not loaded
• invalid LAS,
i. e. no valid LAS configuration present.
An H1 link that has not been activated will show
“H1 link is not configured”.
Change in H1 Live List Refer to the corresponding condition of the Asset
occurred Monitor in Table 92. The currently active
subcondition supplemented by the date and time
of occurrence is displayed here.
An H1 link that has not been activated will show
“H1 link is not configured”.

400 3BDD012902R4101
Section 14 FF Device Integration Library Asset Monitor and Diagnostics Faceplate

Table 93. Contents of Diagnostics Faceplate

Element Description
Reset Press the Reset button to acknowledge the
indicated change in the H1 Live List. This will
reset the corresponding condition of the Asset
Monitor to subcondition “No”.
Press the Reset button to acknowledge .
Without pressing the reset button the
Asset Monitor and the faceplate indicate
the most recent change in the H1 Live
List.
Buttons Area
Press this button to enable the Asset Monitor.

Press this button to disable the Asset Monitor.

Observation of the Asset Monitor conditions will
be stopped and the Diagnostics Faceplate will no
longer show current status information. This will
be indicated by red diagonal bars across the
faceplate.
You may want to temporarily disable the
Asset Monitor while applying
configuration changes to the Linking
Device and the associated H1 links. In
this way you avoid the generation of
alarms that can be expected in this
situation due to H1 devices dropping
from the Live Lists and returning.

3BDD012902R4101 401
FWeb Server Aspects Section 14 FF Device Integration Library

FWeb Server Aspects

Two Web Server aspects are used for connecting to the built-in web server of the LD
800HSE. Refer to Figure 162.

Figure 162. Web Server Aspect of LD 800HSE

For connecting to the web server of an LD 800HSE instance, the following

preconditions must be fulfilled:
• The IP address of the linking device instance is configured in the Web Server
aspect of the LD800HSE object.
• TCP/IP communication between the LD 800HSE in the HSE subnet and the
node that runs the Plant Explorer (in the following called Workplace node) is
possible.

Configure Web Server Aspect

Enter the IP Address of the LD 800HSE at the Web Server Device 1 aspect:
1. Context menu of Web Server Device 1 aspect > Override
2. Context menu > Config View
3. Enter the IP address of the linking device into the Address field > Apply

402 3BDD012902R4101
Section 14 FF Device Integration Library FWeb Server Aspects

In case of an redundant set of linking devices enter the IP address of the second LD
800HSE at the Web Server Device 2 aspect.

Configure TCP/IP Communication Path

The following configuration steps are necessary to enable TCP/IP communication
between an LD 800HSE in an HSE subnet and a Workplace node in the
Client/Server network:
1. Enable TCP/IP forwarding at the Connectivity Server that runs the OPC
Server FF for the HSE subnet.
Enable TCP/IP forwarding is an RNRP Parameter that shall typically be set to
1 in a Connectivity Server. RNRP parameters are set using the RNRP Setup
Wizard. For details on setting the RNRP parameters refer to the manual
“Industrial IT 800xA System, Automation System Network, Design and
Configuration” (3BSE034463).

2. Add a persistent static network route to the HSE subnet via this Connectivity
Server to the network routing table of the Workplace node.
Use the Windows ROUTE command to add a route to the network routing table:
ROUTE -p ADD <destination> MASK <netmask> <gateway>
<destination> = IP network address of the HSE subnet
<netmask> = subnet mask of the HSE subnet
<gateway> = IP address of the Connectivity Server interface attached to the
Client/Server network.
For details refer to the help provided for the ROUTE command.

3. Set the Default Gateway in the LD 800HSE; enter the IP address of the
Connectivity Server interface attached to the HSE subnet. For details on how to
modify the network settings of the LD 800HSE refer to its product
documentation.
4. Configure the web browser on the Workplace node not to use a proxy server.

3BDD012902R4101 403
FWeb Server Aspects Section 14 FF Device Integration Library

404 3BDD012902R4101
 Appendix A Configuration Rules

Basic configuration rules for FOUNDATION Fieldbus are given in Table 94.

Table 94. FOUNDATION Fieldbus Basic Configuration Rules

HSE Maximum CI860 throughput 500 signals per second

Maximum number of signals 1000 signals overall out of:
• max 1000 for analog input
• max 500 for analog output
• max 500 for discrete input
• max 250 for discrete output
Maximum number of CI860 at CEX Bus 12(1)
Maximum number of linking devices per 15
HSE subnet
H1 Maximum number of devices per H1 link 16 (application dependent)(2)
Maximum number of signals in total 70
between one H1 link and HSE
Maximum number of signals per second 20
per H1 link between H1 and HSE
(1) A pair of redundant modules counts as two modules.
(2) FF recommendation for H1 segment layout is maximum 12 devices with up to 4 valves.

3BDD012902R4101 405
 Appendix A Configuration Rules

Capacity figures for a Connectivity Server that is exclusively running an OPC

Server FF are given in Table 95.

Table 95. Capacity Figures for the Connectivity Server FF

Maximum number of Connectivity Servers FF There is a limit for the total number
of Connectivity Servers in a system.
Refer to 800xA System Guide.
Maximum number of HSE subnets per 1 (1:1 relationship)
Connectivity Server FF
Maximum number of field devices per 960
Connectivity Server FF

For detailed dimensioning limits of the linking device LD 800HSE and the
communication interface CI860 please refer to the documentation of these products:
• FOUNDATION Fieldbus Linking Device LD 800HSE, User Instructions,
3BDD011677
• 800xA - Control and I/O, FOUNDATION Fieldbus HSE, Engineering and
Configuration, 3BDD012903.

406 3BDD012902R4101
 Appendix B Documentation Settings

Document Types
Table 96. Document Types

Term Type Name

Documentation-Description Documents
Title-/cover pages EAA10 COV Title page
Directories EAB11 IND Table of Contents
EAB12 MAC Setting the documentation job
General Technical Information Documents
Gen.techn. doc. EDY12 OBJ Head confi./ list
EDY20 HWM Tree view
EDY22 NET Network
EDY30 SYS Graphic view
EDY33 MOD Module parameters
Technical Requirements and Dimension/Design Documents
Tag lists, block schema EEC10 TAG Tag list
EEC11 CR_T Cross-reference tag list
Function-Description Documents
freely available EFM10 ERR Plausibility check error

3BDD012902R4101 407
Description of the Fields or Contents Appendix B Documentation Settings

Description of the Fields or Contents

All fields used in the documentation must be unequivocal, i.e. each field is given a
serial number F1-F62. This is used e.g. for describing the field titles, if no other
entry has been made. For a definition of the fonts used, see also Fonts, National
Languages and Bitmaps in the Drawing Footer / Header on page 414.
Drawing Footer:

Drawing Header:

408 3BDD012902R4101
Appendix B Documentation Settings Field Names in the Drawing Footer / Header

Field Names in the Drawing Footer / Header

The following table shows the correlation between:
• Field designation (FIELD),
• Default variable (CONTENTS),
• Default title (TITLE),
• Description or contents of the field acc. To DIN (COMMENT).

Table 97. Field Names in the Drawing Footer / Header

FIELD CONTENTS TITLE COMMENT

F0 Sta1 State 1 of printout
F1 Sta2 State 2 of printout
F2 Sta3 State 3 of printout
F3 Sta Fixed text in frame
F4 $ObjDate Revision1 Revision date1
F5 Revision2 Revision date2
F6 Revision3 Revision date3
F7 Revision Fixed text in frame
F8 Date1 Date1 of revision
F9 Date2 Date2 of revision
F10 Date3 Date3 of revision
F11 Name Fixed text in frame
F12 Norm1
F13 Norm2
F14 Norm3
F15 Norm Fixed text in frame

3BDD012902R4101 409
Field Names in the Drawing Footer / Header Appendix B Documentation Settings

Table 97. Field Names in the Drawing Footer / Header

FIELD CONTENTS TITLE COMMENT

F16 Date Fixed text in frame
F17 Resp Fixed text in frame
F18 Check Fixed text in frame
F19 Norm0 Fixed text in frame
F20 $ObjCDat Date0 Compilation date
F21 $PrjMan Resp
F22 $ObjS Check Checked by
F23 Norm0
F24 Customer Fixed text in frame
F25 #Logocust.bmp Customer logo (bitmap) or text
F26 Origin Fixed text in frame
F27 Origin Original of
F28 Cre.f. Fixed text in frame
F29 Cref
F30 %LogoComp Company logo (bitmap)
F31 Cre.b. Fixed text in frame
F32 Creb
F33 Title Fixed text in frame
F34 $DocTypeName1 Title1 Drawing name1
F35 $DocTypeName2 Title2 Drawing name 2
F36 Custom.D.No. Fixed text in frame
F37 $PrjOrdNr Custom.D.No. Customer drawing number
F38 == Fixed text in frame

410 3BDD012902R4101
Appendix B Documentation Settings Field Names in the Drawing Footer / Header

Table 97. Field Names in the Drawing Footer / Header

FIELD CONTENTS TITLE COMMENT

F39 $PrjName Localization Installation site
F40 Proj.No. Fixed text in frame
F41 $PrjNr Proj.No. Project number
F42 & Fixed text in frame
F43 $DocT Key to documentation type
F44 Doc.T. Fixed text in frame
F45 $ObjKz Object designation
F46 = Fixed text in frame
F47 $ObjFunct Function name of object
F48 + Fixed text in frame
F49 $ObjLoc Location of object
F50 P. Fixed text in frame
F51 $PgNr Sheet number
F52 %LogoLeft Logo (bitmap) in upper left of header
F53 %LogoRight Logo (bitmap) in upper right of header
F54 Name: Fixed text in frame
F55 Comment:: Fixed text in frame
F56 $ObjName Name of object (Path in the project tree)
F57 $ObjComm Comment of object
F58 Start: Fixed text in frame
F59 End: Fixed text in frame
F60 $DocStart Start of selected print scope

3BDD012902R4101 411
Variables for Drawing Footer/ Header Inscriptions Appendix B Documentation Settings

Table 97. Field Names in the Drawing Footer / Header

FIELD CONTENTS TITLE COMMENT

F61 $DocEnd End of selected print scope
F62 $Objld Type of editor

Variables for Drawing Footer/ Header Inscriptions

Table 98. Variables for Drawing Footer/ Header Inscriptions

Command Function
$ Avoids overriding through the project name
$DocEnd End of the selection range in the tree (depends on the
documentation job)
$DocStart Start of the selection range in the tree (depends on the
documentation job)
$DocT DIN number of the current documentation type (Hardcoded,
language dependent).
$DocTypeName1 First part of the name of the current documentation type.
(Hardcoded, language dependent).
$DocTypeName12 Name of the current documentation type. (Hardcoded,
language dependent)
$DocTypeName2 Second part of the name of the current documentation type.
(Hardcoded, language dependent).
$ObjCDat Creation date of the current documentation object. (If
available)
$ObjComm Short comment to the current documentation object. (If
available)
$ObjDate Date of the current documentation object. (If available)

412 3BDD012902R4101
Appendix B Documentation Settings Variables for Drawing Footer/ Header Inscriptions

Table 98. Variables for Drawing Footer/ Header Inscriptions

Command Function
$ObjFunct Name of the current documentation object. (If available)
$ObjId Short Id to the current documentation object. (hardcoded,
language dependent, typically 3 capital letters)
$ObjKz Documentation identifier of the current object.
$ObjLoc Localization of the current object.
$ObjName Name of the current documentation object. (For example
name of the tree object)
$ObjS State of the current documentation object. (CORRECT,
INCORRECT)
$PgNr Current page No. of the print job.
$PrintDate Date of the print issue.
$PrjComm Comment of the current project. (Editable in the project
header)
$PrjDate Date of the current project. (As shown in the project header)
$PrjMan Manager of the current project. (Editable in the project header)
$PrjName Name of the current project.
$PrjNr Number of the current project. (Editable in the project header)
$PrjOrd Orderer of the current project. (Editable in the project header)
$PrjOrdNr Order number of the current project. (Editable in the project
header)
%LogoComp Default bitmap for your company.
%LogoCover Default bitmap for your cover page.
%LogoCust Bitmap for custumer project
%LogoLeft Default bitmap for the upper left corner.
%LogoRight Default bitmap for the upper right corner.

3BDD012902R4101 413
Fonts, National Languages and Bitmaps in the Drawing Footer / HeaderAppendix B Documentation

Allocation of displays (only BMP files are permitted) is carried out in the Windows
Registry. See Fonts, National Languages and Bitmaps in the Drawing Footer /
Header on page 414.

Fonts, National Languages and Bitmaps in the Drawing

Footer / Header
The fonts or the bitmaps used are defined in the Windows Registry.

BitmapDefaultDir Directory containing the bitmaps

BitmapDir Temporary directory
Font0=Arial, Italic,Size 20 in example A
Font1=Courier New, Size 22 in example B
Font2=Courier New, Size 22 in example C
Font3=Courier New Bold,Size 40 in example D
Font4= Courier New,Size 30 in example E
Font5=Courier New Bold, Size 60 in example F
Font6=Courier New Bold,Size 100 inscription of cover page
Font7=Courier New Bold,Size 50 Inscription of cover page
Frame_Default_File path and file with the default field entries
Frame_Default_Sect=FRAMEUS languages section in the file Frames.ini
LogoComp=LogoComp.bmp Name of bitmap for company logo
LogoCover=LogoCove.bmp Name of bitmap for cover logo

414 3BDD012902R4101
Appendix B Documentation Settings Using Fonts in the Drawing Footer

LogoLeft=LogoLeft.bmp Name of bitmaps for the upper left corner

LogoRight=LogoRigh.bmp Name of bitmap for the upper right corner

Using Fonts in the Drawing Footer

Using Fonts in the Drawing Header

3BDD012902R4101 415
Presetting the Field Contents and Titles Appendix B Documentation Settings

Presetting the Field Contents and Titles

The preset values for the field contents or titles are located in the file FRAMES.INI.
Hence in the English version the section FRAMESUS is used as default. But
another section can also be selected.
See also Fonts, National Languages and Bitmaps in the Drawing Footer / Header on
page 414.
The file FRAMES.INI can be edited with any ASCII editor, e.g. EDIT of DOS or
the EDITOR of WINDOWS.
The editor used must not append any control characters to the file!
The lines with the code FIELD_CONT_Pxx (xx=0..62) define the required field
contents for the printout. The lines with the code FIELD_TITLE_Pxx (xx=0..62)
specify a title for the fields. The title text can be superimposed at any time while
entering the field contents to be printed, in order to show the user which entry is to
be made in the fields.

416 3BDD012902R4101
 Appendix C Diagnostic Data

Pre-defined Items of the Hardware Objects

HSE Device
An HSE device is not uniquely identified in the Live List by the tag name, but by its
unique IP address, or both IP addresses in the case of a redundant configuration.
For pre-defined parameters for HSE Device objects, refer to Table 99.

Table 99. Pre-defined Parameters of the HSE Device Objects

Item name Description

LiveListState State of the Live List
PrimIPAddr IP address of the currently active primary. Changes for
each redundancy transfer.
IP1 IP address 1
IP2 IP address 2
PDTagIP1 PD tag name IP address 1
PDTagIP2 PD tag name IP address 2
DeviceIdentIP1 Device identifier IP address 1
DeviceIdentIP2 Device identifier IP address 2
DeviceTypeIP1 Device type IP address 1
DeviceTypeIP2 Device type IP address 2

3BDD012902R4101 417
H1 Link Appendix C Diagnostic Data

Table 99. Pre-defined Parameters of the HSE Device Objects

Item name Description

AbortCnt Number of disconnections between OPC Server and
linking device since the start of the OPC Server.
This counter is also incremented on each redundancy
transfer.
LastAbort_ErrClass Error class of the last disconnection
(in accordance with HSE specification)
LastAbort_ErrCode Error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddCode Additional error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddDesc Additional description of the last disconnection
(in accordance with HSE specification)
LastAbort_Time Time of the last disconnection

H1 Link
An H1 link is not uniquely identified by the tag name in the Live List, but by its
unique FDA address, or both FDA addresses in the case of a redundant linking
device configuration.1
The OPC Server only opens a connection to an H1 link if values are read from this
link. At the moment, only the item "LAS_State" can be read from the H1 link. The
value of the item "LiveListState" is generated from connectionless online data of the
linking device. All other pre-defined variables only exist in the OPC Server, a
connection is not required to read these values.
In accordance with HSE specifications, a disconnection can be signaled in two
ways. Correspondingly, either the items
• LastAbort_AbortIdentifier,
• LastAbort_AbortReason and
• LastAbort_AbortDetail

1. Although the H1 link itself is not redundant, with a redundant linking device there are two communications
from an OPC Server point of view. Therefore two addresses exist.

418 3BDD012902R4101
Appendix C Diagnostic Data H1 Link

or the items
• LastAbort_ErrClass,
• LastAbort_ErrCode,
• LastAbort_AddCode and
• LastAbort_AddDesc
are used. The respective other items are set to the value 0.
All counters ...Cnt are initialized at the start of the OPC Server.
DA_.. = Data Access, Init_.. = Initiate.
For pre-defined parameters for HSE Device objects, refer to Table 100.

Table 100. Pre-defined Parameters for H1 Link Objects

Item name Description

DA_ReqCnt Number of requests to the H1 link
DA_Err_ReqCnt Number of requests to the H1 link in which an error
occurred.
DA_RspCnt Number of responses to the H1 link
DA_Err_RspCnt Number of responses to the H1 link in which an error
occurred.
Init_ReqCnt Number of initialization requests (establishment of a
connection) to the H1 link
Init_Err_ReqCnt Number of initialization requests (establishment of a
connection) to the H1 link in which an error occurred
Init_RspCnt Number of initialization responses (establishment of a
connection) to the H1 link
Init_Err_RspCnt Number of initialization responses (establishment of a
connection) to the H1 link in which an error occurred

3BDD012902R4101 419
H1 Link Appendix C Diagnostic Data

Table 100. Pre-defined Parameters for H1 Link Objects

Item name Description

DA_OpenReqEndurance Length of an active data request in seconds. This
value is reset to 0 on receipt of a response.
Maximum wait of 30 seconds for a response. The
connection is closed after 30 seconds and a new
initialization started. (AbortCnt +1, Init_ReqCnt+1,..)
Init_OpenReqEndurance Length of an active initialization request in seconds.
Maximum wait of 30 seconds for a response. The
connection is closed after 30 seconds and a new
initialization started. (AbortCnt +1, Init_ReqCnt+1,..)
LiveListState State of the Live List
VersNumberIP1 Version number for the 1st IP address.
Is incremented for each logon and logoff of H1 devices
in the linking device.
VersNumberIP2 Version number for the 2nd IP address.
Is incremented for each logon and logoff of H1 devices
in the linking device.
LastAbort_Time Time of the last disconnection
LastAbort_AbortIdentifier Break identifier of the last disconnection
(in accordance with HSE specification)
LastAbort_AbortReason Reason for break of the last disconnection
(in accordance with HSE specification)
LastAbort_AbortDetail Details of break of the last disconnection
(in accordance with HSE specification)
AbortCnt Number of disconnections between OPC Server and
H1 link since the start of the OPC Server.
This connection is only established if the LAS status is
read. In the case of redundancy toggle this counter is
only incremented if the LAS status is read at this time.

420 3BDD012902R4101
Appendix C Diagnostic Data H1 Device (H1 Field Device)

Table 100. Pre-defined Parameters for H1 Link Objects

Item name Description

LastAbort_ErrClass Error class of the last disconnection
(in accordance with HSE specification)
LastAbort_ErrCode Error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddCode Additional error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddDesc Additional description of the last disconnection
(in accordance with HSE specification)
LastReadErr_Time Time of the last read access error
LastReadErr_ErrClass Class of the last read access error
(in accordance with HSE specification)
LastReadErr_ErrCode Number of the last read access error
(in accordance with HSE specification)
LastReadErr_AddCode Additional code to the last read access error
(in accordance with HSE specification)
LastReadErr_AddDesc Additional description tor the last read access error
(in accordance with HSE specification)
LAS_State LAS status
0 = stopped
1 = running
2 = not loaded
3 = invalid LAS

H1 Device (H1 Field Device)

An H1 device is not uniquely identified by the tag name in the Live List, but by its
unique bus address, or both bus addresses in the case of a redundant linking device
configuration.1

1. Although the H1 device itself is not redundant, with a redundant linking device there are two communications
from an OPC Server point of view. Therefore two addresses exist.

3BDD012902R4101 421
H1 Device (H1 Field Device) Appendix C Diagnostic Data

The OPC Server only opens a connection to an H1 device if items are read out of the
FF blocks of the device. The value of the item "LiveListState" is generated from
connectionless online data of the linking device.
All other pre-defined variables only exist in the OPC server, a connection is not
required to read these items.
In accordance with HSE specifications, a disconnection can be signaled in two
ways. Correspondingly, either the items
• LastAbort_AbortIdentifier,
• LastAbort_AbortReason and
• LastAbort_AbortDetail
or the items
• LastAbort_ErrClass,
• LastAbort_ErrCode,
• LastAbort_AddCode and
• LastAbort_AddDesc
are used. The respective other items are set to the value 0.
All counters ...Cnt are initialized at the start of the OPC server.
DA_.. = Data Access, Init_.. = Initiate.
For pre-defined parameters for HSE Device objects, refer to Table 101.

Table 101. Pre-defined Parameters of the H1 Device Objects

Item name Description

DA_ReqCnt Number of requests to the H1 device
DA_Err_ReqCnt Number of requests to the H1 device in which an
error occurred
DA_RspCnt Number of responses to the H1 device
DA_Err_RspCnt Number of responses to the H1 device in which an
error occurred
Init_ReqCnt Number of initialization requests to the H1 device

422 3BDD012902R4101
Appendix C Diagnostic Data H1 Device (H1 Field Device)

Table 101. Pre-defined Parameters of the H1 Device Objects

Item name Description

Init_Err_ReqCnt Number of initialization requests to the H1 device
in which an error occurred
Init_RspCnt Number of initialization responses to the H1 device
Init_Err_RspCnt Number of initialization responses to the H1 device
in which an error occurred
DA_OpenReqEndurance Length of an active data request in seconds. This
value is reset to 0 on receipt of a response.
Init_OpenReqEndurance Length of an active initialization request in
seconds.
Maximum wait of 30 seconds for a response. The
connection is closed after 30 seconds and a new
initialization started. (AbortCnt +1,
Init_ReqCnt+1,..)
LiveListState State of the Live List
VersNumberIP1 Version number for the 1st IP address.
Is incremented for each logon and logoff of H1
devices in the linking device.
VersNumberIP2 Version number for the 2nd IP address.
Is incremented for each logon and logoff of H1
devices in the linking device.
LastAbort_Time Time of the last disconnection
LastAbort_AbortIdentifier Break identifier of the last disconnection
(in accordance with HSE specification)
LastAbort_AbortReason Reason for break of the last disconnection
(in accordance with HSE specification)
LastAbort_AbortDetail Details of break of the last disconnection
(in accordance with HSE specification)

3BDD012902R4101 423
H1 Device (H1 Field Device) Appendix C Diagnostic Data

Table 101. Pre-defined Parameters of the H1 Device Objects

Item name Description

AbortCnt Number of disconnections between OPC Server
and H1 link since the start of the OPC Server.
This connection is only established if the LAS
status is read. In the case of a redundancy toggle
this counter is only incremented if the LAS status
is read at this time.
LastAbort_ErrClass Error class of the last disconnection
(in accordance with HSE specification)
LastAbort_ErrCode Error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddCode Additional error code of the last disconnection
(in accordance with HSE specification)
LastAbort_AddDesc Additional description of the last disconnection
(in accordance with HSE specification)
LastReadErr_Time Time of the last read access error
LastReadErr_ErrClass Class of the last read access error
(in accordance with HSE specification)
LastReadErr_ErrCode Number of the last read access error
(in accordance with HSE specification)
LastReadErr_AddCode Additional code for the last read access error
(in accordance with HSE specification)
LastReadErr_AddDesc Additional description for the last read access error
(in accordance with HSE specification)
LastWriteErr_Time Time of the last write access error
LastWriteErr_ErrClass Class of the last write access error
(in accordance with HSE specification)
LastWriteErr_ErrCode Number of the last write access error
(in accordance with HSE specification)

424 3BDD012902R4101
Appendix C Diagnostic Data Description of the Live List Data

Table 101. Pre-defined Parameters of the H1 Device Objects

Item name Description

LastWriteErr_AddCode Additional code for the last write access error
(in accordance with HSE specification)
LastWriteErr_AddDesc Additional description for the last write access error
(in accordance with HSE specification)
PDTagIP1 PD tag name IP address 1

PDTagIP2 PD tag name IP address 2

DeviceIdentIP1 Device identifier IP address 1

DeviceIdentIP2 Device identifier IP address 2

Description of the Live List Data

HSE Device
The Live List status of an HSE device is encoded in a WORD32. The possible errors
are signaled by single bits which are linked by OR.
If the total value is 0, no errors are signaled for the HSE device or for the lower-level
devices.
For the meaning of the individual bits, refer to Table 102.

Table 102. Live List of an HSE Device

Hexadecimal
Description
value
0X00000000 No error in the HSE device and the lower-level devices
0x00000001 HSE device of the 1st IP address: not in Live List
0x00000002 HSE device of the 1st IP address: invalid PDTag
0x00000004 HSE device of the 1st IP address: not redundant

3BDD012902R4101 425
Description of the Live List Data Appendix C Diagnostic Data

Table 102. Live List of an HSE Device

Hexadecimal
Description
value
0x00000008 HSE device of the 1st IP address: error at link 9 - n.
(errors for link 1 to link 8 are directly encoded in the Live List.)
0x00000010 HSE device of the 2nd IP address: not in Live List
0x00000020 HSE device of the 2nd IP address: invalid PDTag
0x00000040 HSE device of the 2nd IP address: not redundant
0x00000080 HSE device of the 2nd IP address: error at link 9 - n.
(errors for link 1 to link 8 are directly encoded in the Live List.)
0x00000100 HSE device of the 1st IP address: error at link 1
0x00000200 HSE device of the 1st IP address: error at link 2
0x00000400 HSE device of the 1st IP address: error at link 3
0x00000800 HSE device of the 1st IP address: error at link 4
0x00001000 HSE device of the 1st IP address: error at link 5
0x00002000 HSE device of the 1st IP address: error at link 6
0x00004000 HSE device of the 1st IP address: error at link 7
0x00008000 HSE device of the 1st IP address: error at link 8
0x00010000 HSE device of the 2nd IP address: error at link 1
0x00020000 HSE device of the 2nd IP address: error at link 2
0x00040000 HSE device of the 2nd IP address: error at link 3
0x00080000 HSE device of the 2nd IP address: error at link 4
0x00100000 HSE device of the 2nd IP address: error at link 5
0x00200000 HSE device of the 2nd IP address: error at link 6
0x00400000 HSE device of the 2nd IP address: error at link 7
0x00800000 HSE device of the 2nd IP address: error at link 8

426 3BDD012902R4101
Appendix C Diagnostic Data H1 Link

Table 102. Live List of an HSE Device

Hexadecimal
Description
value
0x10000000 Two primaries found
0x20000000 No primary found
0x40000000 No connection
(detailed information can be found via the pre-defined
parameters of the HSE Device object)

H1 Link
The Live List status of an H1 link is encoded in a WORD32. The possible errors are
signaled by single bits which are linked by OR.
If the total value is 0, no errors are signaled for the H1 link or for the lower-level
devices.
For the meaning of the individual bits, refer to Table 103.

Table 103. Live List of an H1 Link

Hexadecimal
Description
value
0x00000000 No error in the H1 link or the lower-level devices
0x00000001 H1 link of the 1st IP address: not in Live List
0x00000002 H1 link of the 1st IP address: invalid FDA address
0x00000004 H1 link of the 1st IP address: Live List contains different H1
devices than the configured ones
0x00000010 H1 link of the 1st IP address: invalid tag name of an H1 device
0x00000020 H1 link of the 1st IP address: not all configured H1 devices in
the Live List
0x00000100 H1 link of the 2nd IP address: not in Live List
0x00000200 H1 link of the 2nd IP address: invalid FDA address

3BDD012902R4101 427
H1 Device (H1 Field Device) Appendix C Diagnostic Data

Table 103. Live List of an H1 Link

Hexadecimal
Description
value
0x00000400 H1 link of the 2nd IP address: Live List contains different H1
devices than the configured ones
0x00001000 H1 link of the 2nd IP address: invalid tag name of an H1 device
0x00002000 H1 link of the 2nd IP address: not all configured H1 devices in
the Live List
0x10000000 No connection to the H1 link
0x20000000 Some configured H1 devices not correct (version error)
0x40000000 No connection to the linking device
0x80000000 No connection to an H1 device
(detailed information can be found via the pre-defined
parameters of the hardware objects)

H1 Device (H1 Field Device)

The Live List status of an H1 device is encoded in a WORD32. The possible errors
are signaled by single bits which are linked by OR.
If the total value is 0, no errors are signaled for the H1 device.
For the meaning of the individual bits, refer to Table 104.

Table 104. Live List of an H1 Device

Hexadecimal
Description
value
0x00000010 H1 device of the 1st IP address: invalid tag name
0x00000020 H1 device of the 1st IP address: not in Live List
0x00001000 H1 device of the 2nd IP address: invalid tag name
0x00002000 H1 device of the 2nd IP address: not in Live List

428 3BDD012902R4101
Appendix C Diagnostic Data H1 Device (H1 Field Device)

Table 104. Live List of an H1 Device

Hexadecimal
Description
value
0x20000000 Version error of the H1 device
0x40000000 No connection to the HSE linking device
0x80000000 No connection to the H1 device

3BDD012902R4101 429
H1 Device (H1 Field Device) Appendix C Diagnostic Data

430 3BDD012902R4101
 Appendix D OPC Keyword Tracing

Structure of Trace Entries

Each line of the trace file includes the following information:
• Current date and time of Trace entry
• No. - not user-relevant
• Trace level (depending on the Trace level set, more (Debug) or fewer (No trace)
outputs are created in the Trace file)
• Keyword by means of which the entry was prompted
• Name of the source file - not application-relevant
• No. - not user-relevant
• Function with parameters
Example:
05/12/2003 Date
14:56:15,853 Time
[764] internal number
DEB Trace level = Debug
OPC_DALCyclicNotification Keyword
I:\DIGIMAT\OPC\OPCSRV\SRC\OPCSRV.CPP
File name
1115 internal number
ValueChangedCB(): ShelfID: 2, Magic: 15, Value: 820,
TimeStamp: 05/12/2003 13:56:58,705, ProtocolQuality: 0.0X0
function with parameters, here a
parameter has adopted the value 820.

3BDD012902R4101 431
Logging of the Keyword Setting Appendix D OPC Keyword Tracing

Logging of the Keyword Setting

The selection and de-selection of a keyword is logged using
Keyword <name> switched on or
Keyword <name> switched off.
With <name> = Keyword, as displayed in the tree structure.
Trace functionality need not be explicitly started or stopped. Immediately after the
selection or unselection of a keyword, the selected functions are logged in the Trace
file or logging is stopped.

Logged Functions
By selecting the keywords, the different functions of the OPC Server are logged.
The logged functions are listed below for every keyword.

Keyword: Alarms and Events

Refer to Table 105.

Table 105. Alarms and Events Keywords

Keyword Description
OPC_AE Creation and removal of alarm tags,
Creation of alarm conditions,
Activation of the alarm lists.
OPC_DMSEvent Update of the alarm conditions,
Acknowledgement handling,
Functionality of the resource table.
OPC_TKEvent not used
OPC_TKInternal not used

432 3BDD012902R4101
Appendix D OPC Keyword Tracing Keyword: Common Functionality

Keyword: Common Functionality

Refer to Table 106.

Table 106. Common Functionality Keywords

Keyword Description
OPC_Common General functions such as e.g.
* Initialization of the protocols,
* Loading of the configuration,
* Entries in the event log.
OPC_Configuration Updates to the OPC Server configuration after a download.
OPC_Shelf Items which are read by a Client are on the shelf.
All operations on the shelf, e.g.:
* Add,
* Remove,
* Clean Up,
* Value Changed,
* Set Value.

Keyword: DAL
The Data Acquisition Layer DAL is the protocol layer in the OPC Server above the
various Fieldbus protocols or the controller protocol (DMS). Refer to Table 107.

Table 107. DAL Notification Keywords

Keyword Meaning
OPC_DALCyclicNotification Cyclical information about value updates.
(ValueChanged Callback)
OPC_DALReadNotification Logs asynchronous Read Callback
OPC_DALWriteNotification Logs asynchronous Write Callback

3BDD012902R4101 433
Keyword: DMS Appendix D OPC Keyword Tracing

Table 107. DAL Notification Keywords

Keyword Meaning
OPC_DALCyclicRead Opening and closing of OPC items.
OPC_DALJob All operations which are called up during a job:
* Start/Finish Job,
* Read/Write Job,
* Sync/Async Read/Write.

Keyword: DMS
The DMS protocol is used for communication between the OPC Server and the FF
devices. Refer to Table 108.

Table 108. DMS Keywords

Keyword Meaning
OPC_DMSACyclic Acyclic read and write operations.
OPC_DMSCommon Information about the state of the FF devices.
OPC_DMSCyclicRead Cyclical reading and writing, and the opening and
closing of FF devices and parameters.

Keyword: Fieldbus
Fieldbus protocols (FF, Profibus, HART) are for communication of the OPC Server
with the field devices. Refer to Table 109.

Table 109. Fieldbus Keywords

Keyword Meaning
OPC_FBACyclic Asynchronous reading and writing on the Fieldbus.

434 3BDD012902R4101
Appendix D OPC Keyword Tracing Keyword: Group Functionality

Table 109. Fieldbus Keywords

Keyword Meaning
OPC_FBCommon Conversion of the error numbers from FF, Profibus and
HART communication into OPC error numbers.
OPC_FBCyclicRead Opening and closing of the cyclical Fieldbus
parameters.

Keyword: Group Functionality

Refer to Table 110.

Table 110. Group functionality Keywords

Keyword Meaning
OPC_AsyncNotification Group notifications such as e.g. reading and writing on
Cache, Refresh and Append.
OPC_Group OPC group operations, e.g.:
* add item
* remove item
* refresh
* on read complete
* on write complete
* configuration updates.

Keyword: Item Functionality

Refer to Table 111.

Table 111. Item functionality Keywords

Keyword Meaning
OPC_Item Updates to the configuration of the item,
Activation and deactivation of the item,
Updates to the status of the higher-level object.

3BDD012902R4101 435
Keyword: OPC Data Access Automation 1.0 Interfaces Appendix D OPC Keyword Tracing

Keyword: OPC Data Access Automation 1.0 Interfaces

These keywords are used for clients that only support OPC specification Data
Access version 1.0. Refer to Table 112.

Table 112. OPC Data Access Automation 1.0 Interfaces Keywords

Keyword Meaning
Group Object (Automation 1.0):
IOPCAsyncIODisp Add and delete callbacks,
asynchronous reading and writing,
Refresh OPC groups.
IOPCGroupStateMgtDisp Status information about the OPC groups.
IOPCItemMgtDisp Insertion and deletion of items in a group,
Setting of the data type,
Activation and deactivation of items, as well as the
associated enumeration.
IOPCSyncIODisp Synchronous reading and writing on the OPC groups.
Item Object (Automation 1.0):
IOPCItemDisp Operation on OPC items, e.g.:
* get/put Value,
* get Access Rights,
* get Access Path,
* Get Item ID.
ServerObject (Automation 1.0):
IOPCBrowseServerAdress Browsing operations,
SpaceDisp All OPC items which are reached by browsing.
IOPCServerDisp All operations which are carried out on the server, such
as e.g.:
Opening and closing of groups,
Status of the OPC Server.

436 3BDD012902R4101
Appendix D OPC Keyword Tracing Keyword: OPC Data Access Custom Interfaces

Keyword: OPC Data Access Custom Interfaces

Refer to Table 113.

Table 113. OPC Data Access Custom Interfaces Keywords

Keyword Meaning
Client Interfaces:
IAdviseSink Update of a value by a group. (OPC Spec 1.0
functionality)
IOPCDataCallback Ended read and write operations, value updates.
IOPCShutdown not used
GroupObject:
IDataObject Opening and closing of groups.
IEnumOPCAttributes All operations of the item enumerator.
IOPCAsyncIO Asynchronous reading and writing of groups,
Refresh and Cancel on the group in accordance with
OPC Spec Version 1.0.
IOPCAsyncIO2 Asynchronous reading and writing of groups,
Refresh and Cancel on the group.
IOPCGroupeStateMgt Renaming of groups, status of groups, copying of
groups.
IOPCItemMgt Insertion and deletion of items in a group,
Setting of the data type,
Activation/deactivation of items,
and the associated enumeration.
IOPCSyncIO Synchronous reading and writing to groups.
IConnectionPointContainer Opening and closing of groups.

3BDD012902R4101 437
Keyword: OPC Data Access Custom Interfaces Appendix D OPC Keyword Tracing

Table 113. OPC Data Access Custom Interfaces Keywords

Keyword Meaning
ServerObject:
IOPCBrowseServerAdressS All operations which are used when browsing the
pace configuration of an OPC Server, e.g.:
* ChangeBrowsePosition
* internal assignments of the OPC items
(BrowseOPCItemIds).
IOPCCommon Information about available OPC Servers,
Setting of the client name.
IOPCItemProperties All operations which are performed on the properties
of an OPC item, e.g.:
* QueryAvailableProperties,
* GetItemProperties,
* LookUpItemIDs
IOPCServer All operations which are carried out on the server,
such as e.g.:
* Opening and closing of groups
* Status of the OPC Server.

438 3BDD012902R4101
Appendix D OPC Keyword Tracing Keyword: Server Functionality

Keyword: Server Functionality

Table 114. Server Functionality Keywords

Keyword Meaning
OPC_Browsing Information about the browsing enumerator.
OPC_CheckServer is not used
OPC_ItemProperties Handling the Item Properties:
* GetItemProperties,
* IsItemValid,
* GetConfProperties.
OPC_Server Information about the status of the OPC Server:
* CheckServer,
* GetNumberOfObjects,
* GetLockStateOfGroup,
* OPCServerManagement,
* GetStart/CurrentTime

Examples of Applications
Which Values are Sent to the OPC Client by the OPC Server?
Using selection Common Functionality / OPC_Shelf, value updates are logged as
follows;
COPCItemShelf::ValueChanged() Item: TIC1623gr/SP Index: 1
Magic: 7 Value: 918 TIME stamp: 05/09/2003 10:42:47,310 rc:
0X0
Item = Name of the parameter (OPC item)
Index = internal index
Magic = internal assignment number
Value = value of the parameter
Time = time of the value update (Local time)
In this case the parameter ’TIC1623gr/SP’ has adopted the value 918.

3BDD012902R4101 439
Which OPC Items are Handled in the OPC Groups? Appendix D OPC Keyword Tracing

Using selection DAL / DAL Notification / OPC_DALCyclicNotification, value

updates are logged as follows:
ValueChangedCB(): ShelfID: 1, Magic: 15, Value: 720,
TimeStamp: 05/12/2003 13:56:58,705, ProtocolQuality: 0.0X0
In this case a parameter has adopted the value 720.

Which OPC Items are Handled in the OPC Groups?

The creation and removal of OPC groups is logged by the keyword selection Group
Functionality / OPC_Group:
COPCGroupRoot::COPCGroupRoot() called (actual number=1)
For each parameter which is entered in an OPC group, the following entry is made:
COPCGroupRoot::InternalAddItems(): add item 'F705/SP' of
canonical type VT_R4, requested type VT_R4 to group 'G3'
successful, client handle: 0
Every send message to the client is logged:
COPCGrouppCust::SendCust() for group G3 called

Which Parameters are Requested by the Client?

Using selection Common Functionality / OPC_Shelf, new requests by the client
are logged :
For every parameter to be removed:
COPCItemShelf::Remove(0) called
COPCItemShelf::Remove(): UnadviseVariable: remove Item
F705/SP at index 0
For every parameter to be entered:
COPCItemShelf::Add(F705/SP) called
COPCItemShelf::Add(): AdviseVariable() for item 'F705/SP'
returns 0X0.0 Index: 0
COPCItemShelf::SetValue() Item: F705/SP Index: 0 Value: 0 TIME
stamp: 05/09/2003 10:47:20,150 rc: 0X0

440 3BDD012902R4101
Appendix D OPC Keyword Tracing Which Client Connections have Existed since when to the OPC

Which Client Connections have Existed since when to the OPC Server?
Using selection OPC Data Access Custom Interface / Server Object /
IOPCServer, these three messages are generated every second for each client
connection.:
GetStatus() called
GetStatus() succeeded, return S_OK
GetStatus(ftStartTime=05/09/2003 09:45:57,348,
ftCurrentTime=05/09/2003 10:04:00,053,
ftLastUpdateTime=05/09/2003 10:03:40,178, dwServerState=0X1,
dwGroupCount=1, dwBandWidth=0, wMajorVersion=7,
wMinorVersion=1, wBuildNumber=2494, szVendorInfo=Freelance
2000 DigiOpc - V7.1 BETA Station 123) returns S_OK
StartTime = starting time of this connection, (when was the connection to this client
established).
CurrentTime = current time
LastUpdateTime = time at which the last data traffic took place.
All time values: GMT

3BDD012902R4101 441
Which Client Connections have Existed since when to the OPC Server? Appendix D OPC Keyword

442 3BDD012902R4101
 Index

A Online Parameter settings 379

Alarm object 43 Precommissioning 376
Application Layer 41 Status displays 350
Application time 45 Commissioning mode 343
Aspekt Communication profile 37
Control Connection 95 Configuration Management 44
FF Device Info 93 Connecting line 307
Asset Monitor 392 Connection type 41
Asset Monitoring 392 Context menu 104
Asset Optimization 392 Copy and Paste FF Application 330
Asset Reporter 393 Cross References 327
Asset Viewer 393 Current values 381

B D
Basic Device 40 Data exchange 331
Block Data Link Layer 40
Export FF Object 106 Data link layer 40
Import FF Object 106 DD 46
Block Library 162 DDL 46
Block parameters Detail view 103
Current values 381 Device class object 155, 157
Bridge 40 Device Description Language 46
Device Descriptions 46
C Device Integration Library 387
Capabilities file 45 Dialog Editor 277
Check subtree 108 Bit field 282
Check whole project 108 Check box 282
CI860 161 Combo box 283
Class 161 Combo box pre-defined 283
Client/Server 41 Edit control 282
CMMS Connectivity 394 Elements 281
Commissioning 341, 343 Radio button 283
Loading 379 Dialog field 281

3BDD012902R4101 443
Index

Display state 110 Set Parameter Values 328

DLL 40 Show/Hide grid 306
Document types 407 Signal flow lines 316
Documentation 134 FF Application Object 160, 174
Create drawing header 136 FF Block 159
Print 150 FF Block Class 158
Printer setup 151 FF Block Library 157
Sorting of the printout 148 FF Device Info Aspect 93
Documentation management 134 FF Function Block 312
Documentation order 134 FF Generic Device Asset Monitor 393
Create 143 FF Linking Device 159
Draw signal flow line 314 FF Network 158
FF Object editor
E Detail view 103
Edit project comments 133 FF Signal 311
Edit project information 131 FF Signal List 288, 327
Enabling block parameters for OPC access 276 FF Signal Symbol 307
Enabling of tags for OPC access 260 FF Signals 287
Enabling OPC Server FF Field contents 416
block parameters for OPC access 261 Field names
Enabling parameters of the FF blocks for OPC Drawing footer 409
access 261 Drawing header 409
End 119 Field titles 408
Export Fieldbus Access Sublayer 41
FF Object 106 Fieldbus Builder FF 248
Tag list 126 Fieldbus Message Specification 41
External, Parameter Type 313 FMS 41
FOUNDATION Fieldbus Device Integration
F Library 387
FAS 41 FOUNDATION Fieldbus HSE communication
Fault management 44 interface module 161
FB 42 Function block 42
FBAP 42 Function Block Application Process 42
FF Application 159, 301
Check Elements 330 H
Delete 330 H1 37
Document 328 H1 Device 159
End Editing 329 H1 Device Class 158
Producing Hard Copy 329 H1 Device Instance Object 160, 174
Save 328 H1 Device Library 157, 164

444 3BDD012902R4101
 Index

H1 Link 159 M
H1 Link Object 160, 173 Mandatory, Parameter Type 312
H1 Schedule 159, 333 Maximum values
H1 Schedule Object 160 OPC Server FF 252
Hardware structure 110
Engineering status 111 N
HSE 37 Name 117
HSE communication interface module 37, 161 Network Management 44
HSE Device 159
HSE Device Class 158
O
HSE Device Instance Object 159, 173
Object Dictionary 41, 45
HSE Device Library 157, 165
OD 41
HSE Host Object 161
Online Parameter settings 379
HSE Live List 382
OPC Clients 247
HSE Republishing 155, 287
OPC Server FF 159, 247
HSE Subnet
Addressing the data 265
Configure 82
Browser interface 247
Library Update 84
Commissioning 264
HSE Subnet Object 158 to 159, 172
Configuration in FBB FF 253
HSEHostCI860 158, 216
Custom Interface 247
Data transmission 250
I Diagnostic data 264
Import Enabling of tags for OPC access 260
FF Object 106 Keyword trace 269
Tag list 127 Loading 264
Importing FF Devices 165 Mapping of the data types 266
Importing H1 Field Devices 165 Maximum values 252
Importing HSE Devices 169 Parameters of the hardware objects 264
Instance 161 Performance 252
Internal, Parameter Type 313 Performance Monitor 273
ISO/OSI Reference model 38 Redundancy 251
Start 264
L System monitor 273
LAS 40 System structure 248
Link Active Schedule 40 Trace dialog 269
Link Master 40 Version check 268
Link object 43 OPC Server FOUNDATION Fieldbus 247
Live List 40 OPC specification 247
Loading 379 OPC-relevant parameters 276
OPC Server FF 264 Optional, Parameter Type 312

3BDD012902R4101 445
Index

OSI reference model 38 Step by Step User Instructions 47

System Management 45
P
Parameter Types 312 T
Parameters of the hardware objects in OPC Server Tag List 327
FF 264 Tag list
Performance Column L 118
OPC Server FF 252 Column T 117
Performance management 44 Library type 118
Precommissioning 376 Long text 117
Product Documentation 391 Name 117
Publish/Subscribe 287 Short text 117
Publisher/Subscriber 41 Type name 117
Type of entry 117
R Tag List entries
RB 42 Modify 118
Redundancy Tag name 117
OPC Server FF 251 TB 42
Replace 383 Template 112
Replacing Template manager 112
FF Linking Device 383 Templates/Libraries 107
H1 Device 385 Time synchronisation 40, 45
Report Distribution 41 Tool routing 250
Republishing 155 Transducer Block 42
Resource Block 42 Trend object 43
Resource block 42 Type name 117

S U
Schedule Editor 333 User Application 42
Schedule Object 174
Signal flow lines 307 V
Signal-Channel-Mapping 299 Value file 46
Sort 118 Variables for drawing footer 412
Station access 128 VFD 41, 43
Step by Step View object 43
Commissioning 67 Virtual Field Device 41, 43
FF Application 56
HSE Subnet 49
HSEHostCI860 61, 73
Precommissioning 64

446 3BDD012902R4101
BackCover.fm Page 19 Wednesday, October 20, 2004 10:27 AM
3BDD012902R4101 Printed in Sweden May 2005
Copyright © 2003-2005 by ABB, All rights reserved
® Registered Trademark of ABB
™ Trademark of ABB

http://www.abb.com/control

Automation Technology Products Automation Technology Products Automation Technology Products

Västerås, Sweden Wickliffe, Ohio, USA Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: [email protected] email: [email protected] email: [email protected]