Power and productivityfor a better worldTM

System 800xA Device ManagementFOUNDATION FieldbusConfiguration

System Version 5.1

System 800xA Device ManagementFOUNDATION Fieldbus

Configuration

System Version 5.1

NOTICEThis document contains information about one or more ABB products and may include adescription of or a reference to one or more standards that may be generally relevant tothe ABB products. The presence of any such description of a standard or reference to astandard is not a representation that all of the ABB products referenced in this documentsupport all of the features of the described or referenced standard. In order to determinethe specific features supported by a particular ABB product, the reader should consult theproduct specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intel-lectual property in the ABB products described in this document.

The information in this document is subject to change without notice and should not beconstrued as a commitment by ABB. ABB assumes no responsibility for any errors thatmay appear in this document.

In no event shall ABB be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB beliable 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 usedfor any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license. Thisproduct meets the requirements specified in EMC Directive 2004/108/EEC and in LowVoltage Directive 2006/95/EEC.

TRADEMARKSAll rights to copyrights, registered trademarks, and trademarks reside with their respec-tive owners.

Copyright 2003-2010 by ABB. All rights reserved.

Release: June 2010Document number: 3BDD012902-510

3BDD012902-510 5

TABLE OF CONTENTS

About This BookGeneral ............................................................................................................................17

Document Conventions ...................................................................................................17

Use of Warning, Caution, Information, and Tip Icons ....................................................17

Terminology.....................................................................................................................18

Related Documentation ...................................................................................................20

Section 1 - Product OverviewIntroduction .....................................................................................................................21

Fieldbus Builder FOUNDATION Fieldbus .....................................................................21

OPC Server FOUNDATION Fieldbus.............................................................................22

Device Library Wizard ....................................................................................................22

Device Type Objects........................................................................................................23

Product Documentation........................................................................................23

Asset Monitoring..................................................................................................23

Maintenance Management ...................................................................................23

Function Block Faceplates ...................................................................................24

Section 2 - Technical Overview FOUNDATION Fieldbus

Section 3 - Integration in Plant ExplorerBasic Principles of the Integration in Plant Explorer ......................................................27

Object Types in Plant Explorer........................................................................................29

H1 and HSE Device Library ................................................................................30

FF Block Library..................................................................................................30

Table of Contents

6 3BDD012902-510

Reservation of objects ..................................................................................................... 30

FF libraries ........................................................................................................... 30

Reserve objects in Plant Explorer workplace ...................................................... 30

Reserve objects in Fieldbus Builder FF ............................................................... 31

Short time locking................................................................................................ 31

Edit FF Libraries ............................................................................................................. 31

Insert Device Object Types in FF Libraries by ABB Device Library Wizard ..... 32

Edit FF Libraries in Fieldbus Builder FF............................................................. 32

Upload FF Libraries to the Plant Explorer Workplace ........................................ 32

Configure HSE Subnet .................................................................................................... 33

Create HSE Subnet in the Plant Explorer Workplace .......................................... 33

Configure HSE Subnet in Plant Explorer Workplace .......................................... 34

Configure HSE Subnet in Fieldbus Builder FF ................................................... 34

Upload HSE Subnet to the Plant Explorer Workplace......................................... 36

Navigation ....................................................................................................................... 37

Navigating to the FF Libraries ............................................................................. 37

Navigating to the HSE Subnet ............................................................................. 37

Navigating to a Selected FF Instance Object ....................................................... 37

Aspects of Fieldbus Builder FF in the Plant Explorer .................................................... 38

FF Management ................................................................................................... 39

FF Upload ............................................................................................................ 39

FF Device Info ..................................................................................................... 40

OPC Data Source Definition................................................................................ 41

Control Connection.............................................................................................. 43

Aspects of LD 800HSE................................................................................................... 44

Asset Monitor ...................................................................................................... 45

Diagnostics Faceplate .......................................................................................... 47

Web Server Aspects ............................................................................................. 50

Audit Trail ....................................................................................................................... 52

Security Definition .......................................................................................................... 53

Advanced Management of FF Libraries.......................................................................... 53

Table of Contents

3BDD012902-510 7

3BDD012902-510 7

FF Library Merge .................................................................................................53

System Backup and Export .............................................................................................54

Import/Export a single HSE-Subnet ................................................................................54

Export a single HSE-Subnet.................................................................................55

Import a single HSE-Subnet.................................................................................56

Advanced Administration of FF Configuration Data ......................................................56

Overview .............................................................................................................56

Resolve a Conflict ................................................................................................59

Break a Lock ........................................................................................................61

Section 4 - System ConfigurationGeneral Instructions.........................................................................................................63

Fieldbus Builder FF Tools ...............................................................................................64

FF Object Editor ..............................................................................................................64

Call up FF Object Editor ......................................................................................64

General Description of the FF Object Editor .......................................................64

Interface of the FF Object Editor .........................................................................65

Operating Modes..................................................................................................66

General Functions of the FF Object Editor ..........................................................66

Representation in the FF Object Editor Structure ................................................77

Configuration of an FF Network..........................................................................79

Tag List ............................................................................................................................79

General Description of the Tag List .....................................................................79

Edit Tag List .........................................................................................................81

Signal List........................................................................................................................91

General Description of the Signal List.................................................................91

Call up the Signal List..........................................................................................92

Structure of the Signal List ..................................................................................92

Edit Signal List.....................................................................................................94

Cross References................................................................................................100

Documentation ..............................................................................................................103

General Description of the Documentation........................................................103

Table of Contents

8 3BDD012902-510

Documentation Management ............................................................................ 103

Create Drawing Header / Footer ........................................................................ 105

Basic Editing Steps ............................................................................................ 111

Compile Documentation Job ............................................................................. 113

Documentation Scope ........................................................................................ 116

Print out Documentation .................................................................................... 118

Section 5 - Configuring an FF NetworkSystem Structure ........................................................................................................... 121

FF Network with Interface to an IEC 61131 Controller .................................... 121

FF Network without Interface to an IEC 61131 Controller ............................... 127

FF Libraries ................................................................................................................... 127

HSE Device Library........................................................................................... 128

Block Library ..................................................................................................... 128

H1 Device Library ............................................................................................. 129

Expanding FF Libraries................................................................................................. 130

Adding Device Type Objects with Device Library Wizard ............................... 131

Importing FF Devices in Fieldbus Builder FF ................................................... 131

Assigning Bitmaps ............................................................................................. 136

Inserting FF Objects ...................................................................................................... 137

Insert HSE Subnet Object .................................................................................. 138

Insert HSE Host Object (HSEHostCI860)......................................................... 138

Insert Linking Device Module (HSE Device Instance Object).......................... 138

Insert H1 Link Object ........................................................................................ 139

Insert H1 Schedule Object ................................................................................. 139

Insert FF Application Object ............................................................................. 139

Insert H1 Device Instance Object ...................................................................... 140

Insert OPC Gateway Object ............................................................................... 140

View of FF Object Instances ......................................................................................... 141

Detail View of the OPC Server FF Object ......................................................... 141

Detail View of the HSE Subnet Object.............................................................. 141

Detail View of the HSE Device Instance Object ............................................... 142

Detail View of the HSE Host Object ................................................................. 143

Table of Contents

3BDD012902-510 9

3BDD012902-510 9

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

Detail View of the H1 Schedule Object .............................................................146

Detail View of the FF Application Object .........................................................147

Detail View of the H1 Device Instance Object ..................................................148

Section 6 - Parameter SettingsHSE Device Library Object...........................................................................................151

H1 Device Library Object .............................................................................................153

FF Block Library Object ...............................................................................................154

FF Block Class Object...................................................................................................155

Initial Instance Parameters Tab ..........................................................................155

Initial Instance Alarm Parameters Tab ...............................................................159

Block Info Tab....................................................................................................159

Managing Parameter Value Sets.........................................................................162

H1 Device Class Object.................................................................................................164

Device Info Tab ..................................................................................................165

Capabilities File Tab...........................................................................................166

Device Description Tab ......................................................................................168

Download Adjustment Tab.................................................................................169

VCR Info Tab .....................................................................................................171

Block Info Tab....................................................................................................172

Object Menu.......................................................................................................172

HSE Device Class Object ..............................................................................................173

Device Info Tab ..................................................................................................174

Capabilities File Tab...........................................................................................175

VCR Info Tab .....................................................................................................176

Revisions Tab .....................................................................................................177

Context Menu.....................................................................................................177

FF Network Object ........................................................................................................178

HSE Subnet Object........................................................................................................179

HSE Subnet Settings Tab ...................................................................................179

HSE Host Object HSEHostCI860 .................................................................................181

Table of Contents

10 3BDD012902-510

Communication Tab........................................................................................... 181

Referenced Signals Tab...................................................................................... 182

Linking Device Object .................................................................................................. 184

Communication Tab........................................................................................... 184

H1 Link Object.............................................................................................................. 186

H1 Basic Tab...................................................................................................... 187

H1 Schedule Object....................................................................................................... 197

FF Application Object................................................................................................... 197

H1 Device Instance Object............................................................................................ 199

General Tab........................................................................................................ 199

Context Menu..................................................................................................... 200

FF Block Instance Object.............................................................................................. 201

The Block Properties Dialog.............................................................................. 201

Advanced: Properties ......................................................................................... 202

Advanced: Block Info ........................................................................................ 210

Advanced: Download Sequence ........................................................................ 212

Advanced: Alarm Parameters ............................................................................ 213

DD Menus.......................................................................................................... 215

Parameters.......................................................................................................... 217

Details Windows ................................................................................................ 218

UserDialogs ....................................................................................................... 220

Network Configuration.................................................................................................. 221

Section 7 - OPC Server FOUNDATION FieldbusGeneral Description ...................................................................................................... 223

Overview of the Functionality of OPC Server FF......................................................... 224

System Structure ................................................................................................ 224

Data Transfer...................................................................................................... 226

Browser Interface............................................................................................... 227

OPC Server Redundancy ................................................................................... 227

Resources, Maximum Values and Performance ................................................ 228

Configuration with Fieldbus Builder FF ....................................................................... 229

Table of Contents

3BDD012902-510 11

3BDD012902-510 11

OPC Server FF ...................................................................................................229

Insertion of an OPC Server ................................................................................229

Network Configuration ......................................................................................231

Enabling Parameters of the FF Blocks for OPC Access ....................................235

Parameters of the Hardware Objects ..................................................................237

Starting the Communication ..............................................................................238

Loading Project Data into OPC Server ..............................................................238

Addressing of the Data.......................................................................................239

Tools for Error Diagnosis ..............................................................................................240

Trace Dialog of the OPC Server.........................................................................240

Performance Monitor for OPC...........................................................................244

OPC Client.....................................................................................................................247

OPC-relevant Parameters ...................................................................................247

Section 8 - Dialog Editor for FF BlocksGeneral Description.......................................................................................................249

Operation of the Dialog Editor ......................................................................................249

Elements of the Dialog Editor .......................................................................................253

Section 9 - Alarms and EventsOverview........................................................................................................................259

Configuration of FF Alarms and Events........................................................................260

Device Specific Alarm Configuration ................................................................260

Block Specific Alarm Configuration..................................................................261

FF System Alarms and Events ...........................................................................263

Advanced Configuration Options in Plant Explorer ..........................................265

Section 10 - FF Application EditorFF Application...............................................................................................................267

FF Signals...........................................................................................................268

Create FF Application ........................................................................................270

Edit FF Application............................................................................................270

Table of Contents

12 3BDD012902-510

Configuration Interface of the FF Application Editor................................................... 271

Structure of the Configuration Interface ............................................................ 271

Changing the Defaults........................................................................................ 274

Description of the FF Application Elements................................................................. 275

Signal Flow Lines .............................................................................................. 275

FF Signal Symbols............................................................................................. 275

FF Function Blocks............................................................................................ 277

Comments .......................................................................................................... 279

Set Parameters for the FF Application Elements .......................................................... 279

FF Signals .......................................................................................................... 280

FF Function Blocks............................................................................................ 281

Editing an FF Application ............................................................................................. 283

Drawing Signal Flow Lines ............................................................................... 283

Adding an FF Signal to an FF Application........................................................ 284

Modifying an FF Signal in an FF Application................................................... 285

Adding an FF Function Block ........................................................................... 286

Assigning an FF Function Block to a Device .................................................... 288

Vertical and Horizontal Shift of Objects in the FF Application ........................ 289

Block Operations ............................................................................................... 290

Switch to Tag List .............................................................................................. 294

General Processing Functions ....................................................................................... 294

Save FF Application........................................................................................... 294

Setting FF Application parameters .................................................................... 295

End FF Application Editing ............................................................................... 296

Check FF Application Elements ........................................................................ 296

Delete FF Application........................................................................................ 296

Copy and Paste FF Application ......................................................................... 296

Section 11 - Schedule EditorH1 Schedule .................................................................................................................. 299

Schedule Editor Interface .............................................................................................. 299

Structure of the Graphical Display .................................................................... 300

Edit H1 Schedule........................................................................................................... 300

Table of Contents

3BDD012902-510 13

3BDD012902-510 13

Optimize H1 Schedule .......................................................................................301

Save H1 Schedule...............................................................................................301

Move Block ........................................................................................................301

Properties of the Schedule Editor.......................................................................303

Change Default Settings for Schedule Editor................................................................308

Change Colors ....................................................................................................308

Change Scaling of the Time Axis.......................................................................309

Section 12 - Commissioning FF ObjectsGeneral Description of Commissioning .......................................................................311

Start Commissioning .....................................................................................................312

Commissioning Interface ...................................................................................313

Reconcile Block Parameter Values ....................................................................313

Display and Write Online Values .......................................................................314

Commissioning of an FF Network ................................................................................314

Phase 1: Precommissioning................................................................................316

Precommissioning Options ................................................................................318

Phase 2: Loading ................................................................................................319

Phase 3: Online Parameter Settings ...................................................................320

Display Nodes on the HSE Subnet.....................................................................322

Display During Commissioning ....................................................................................322

HSE Subnet Object ............................................................................................323

HSE Device Instance Object ..............................................................................324

HSE Host Object ................................................................................................326

H1 Link Object...................................................................................................327

FF Application Object........................................................................................327

H1 Device Instance Object.................................................................................329

Status Displays for the Objects ..........................................................................330

H1 Device Assignment Dialog...........................................................................335

Online Dialog .....................................................................................................340

Replacing FF Devices....................................................................................................357

Replacing an FF Linking Device .......................................................................357

Table of Contents

14 3BDD012902-510

Replacing an H1 Device .................................................................................... 359

Section 13 - Device Type ObjectsOverview ....................................................................................................................... 361

Functionality ...................................................................................................... 362

Prerequisites and Requirements......................................................................... 363

Device-Type-Specific Product Documentation............................................................. 365

Connection to Asset Optimization ................................................................................ 366

Asset Monitoring ............................................................................................... 366

CMMS Connectivity .......................................................................................... 368

Device Library Wizard .................................................................................................. 369

Overview .......................................................................................................... 369

Prerequisites....................................................................................................... 369

Managing FF Device Type Objects ................................................................... 370

Step 1: Obtain Device Types.............................................................................. 371

Step 2: Extract Device Type Files...................................................................... 372

Step 3: Read Release Notes ............................................................................... 372

Step 4: Install / Restore Device Types ............................................................... 373

Step 5: Post-Installation ..................................................................................... 374

Appendix A - Configuration Rules

Appendix B - Documentation SettingsDocument Types............................................................................................................ 379

Description of the Fields or Contents............................................................................ 380

Field Names in the Drawing Footer / Header................................................................ 381

Variables for Drawing Footer/ Header Inscriptions ...................................................... 384

Fonts, National Languages and Bitmaps in the Drawing Footer / Header.................... 386

Using Fonts in the Drawing Footer.................................................................... 387

Using Fonts in the Drawing Header................................................................... 388

Presetting the Field Contents and Titles........................................................................ 388

Appendix C - Diagnostic Data

Table of Contents

3BDD012902-510 15

3BDD012902-510 15

Pre-defined Items of the Hardware Objects...................................................................389

HSE Device ........................................................................................................389

H1 Link ...........................................................................................................390

H1 Device (H1 Field Device).............................................................................393

Description of the Live List Data ..................................................................................397

HSE Device ........................................................................................................397

H1 Link ...........................................................................................................399

H1 Device (H1 Field Device).............................................................................400

Appendix D - OPC Keyword TracingStructure of Trace Entries..............................................................................................403

Logging of the Keyword Setting ...................................................................................404

Logged Functions ..........................................................................................................404

Keyword: Alarms and Events.............................................................................404

Keyword: Common Functionality......................................................................405

Keyword: DAL...................................................................................................405

Keyword: DMS ..................................................................................................406

Keyword: Fieldbus .............................................................................................406

Keyword: Group Functionality ..........................................................................407

Keyword: Item Functionality .............................................................................407

Keyword: OPC Data Access Automation 1.0 Interfaces....................................408

Keyword: OPC Data Access Custom Interfaces ................................................409

Keyword: Server Functionality ..........................................................................411

Examples of Applications..............................................................................................411

Which Values are Sent to the OPC Client by the OPC Server? .........................411

Which OPC Items are Handled in the OPC Groups?.........................................412

Which Parameters are Requested by the Client? ...............................................412

Which Client Connections have Existed since when to the OPC Server? .........413

Appendix E - FF Bulk Data ExamplesIntroduction ...................................................................................................................415

Table of Contents

16 3BDD012902-510

Create new FF object structures with Bulk Data Manager ........................................... 416

Prerequisites:...................................................................................................... 416

Start Bulk Data Manager ................................................................................... 416

Set BDM Options............................................................................................... 418

FF HSE Subnet .................................................................................................. 420

FF HSE Host CI 860.......................................................................................... 425

FF Linking Device ............................................................................................. 425

H1 Link .......................................................................................................... 425

H1 Schedule ....................................................................................................... 426

H1 Device .......................................................................................................... 426

Function Block Application Diagram (FBAD).................................................. 429

Rename and configure objects with Bulk Data Manager.............................................. 433

Modification of FF Parameters with Bulk Data Manager............................................. 440

Duplicate Existing Structures with Fieldbus Builder FF .............................................. 444

Index

3BDD012902-510 17

About This Book

GeneralThis manual describes the configuration and commissioning for Device Management FOUNDATION Fieldbus, i.e. Fieldbus Builder FF and OPC Server FF, and the usage of the Device Library Wizard for managing FF Device Type Objects in an 800xA system.

Document ConventionsMicrosoft Windows conventions are normally used for the standard presentation of material when entering text, key sequences, prompts, messages, menu items, screen elements, etc.

Use of Warning, Caution, Information, and Tip IconsThis 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:

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.

Terminology About This Book

18 3BDD012902-510

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.

TerminologyA complete and comprehensive list of terms is included in the IndustrialIT Extended Automation System 800xA, Engineering Concepts instruction (3BDS100972*). The listing included in Engineering Concepts includes terms and definitions as they apply to the 800xA system where the usage is different from commonly accepted industry standard definitions and definitions given in standard dictionaries such as Websters Dictionary of Computer Terms.

The table below contains terms that uniquely apply to this instruction.

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

Term/Acronym Description

Application Process (AP)

Application Process (AP) is a term defined by the 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).

FF Network A FOUNDATION Fieldbus network is comprised of one or more HSE subnets and/or one or more H1 links all interconnected

About This Book Terminology

3BDD012902-510 19

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 Network

Please refer to FF Network.

Function Block Application Diagram (FBAD)

The Function Block Application Diagram includes function blocks and signal linkages between them.

Function Block Application Process (FBAP)

A Function Block Application Process (FBAP) is that part in the software of a device which contains the Function Blocks and executes the Function Block Application. The FBAP is organized as separate VFD.

H1 Link An H1 link interconnects one or more H1 Devices.

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.

Physical Device (PD) The term references the real field device as opposed to a Virtual Field Device (VFD).

Republishing The action taken when subscribing to data on one network segment (UDP or H1) and publishing it on another.

Term/Acronym Description

Related Documentation About This Book

20 3BDD012902-510

Related DocumentationA complete list of all documents applicable to the 800xA IndustrialIT Extended Automation System is provided in Released User Documents, 3BUA000263*. This document lists applicable Release Notes and User Instructions. It is provided in PDF format and is included on the Release Notes/Documentation media provided with your system. Released User Documents are updated with each release and a new file is provided that contains all user documents applicable for that release with their applicable document number. Whenever a reference to a specific instruction is made, the instruction number is included in the reference.

The table below contains documentation that additionally apply to this instruction.

Title Description

FOUNDATION Fieldbus Technical OverviewFD-043Publisher: Fieldbus Foundation, 2003

Definition and explanation of key technical concepts inherent in FOUNDATION Fieldbus technology.(1)

(1) The document can be downloaded from the Fielbus Foundations website: http://www.fieldbus.org/ProductsAndServices/FFProductCatalog/

FOUNDATION Fieldbus System Engineering GuidelinesAG-181Publisher: Fieldbus Foundation, March 2010

Guideline reflecting standard industry practices for the application of FOUNDATION Fieldbus H1 projects.(1)

Industrial Ethernet: A Pocket GuideISBN: 1556177887Publisher: ISA - The Instrumentation, Systems, and Automation Society, May 2002

How to plan, install, and maintain TCP/IP Ethernet networks: the basic reference guide for automation and process control engineers.

Foundation Fieldbus: A Pocket GuideISBN: 1556177755Publisher: ISA - The Instrumentation, Systems, and Automation Society, July 2002

Summary of background information, tips, tricks, and items to note when installing, maintaining, or trouble-shooting.

3BDD012902-510 21

Section 1 Product Overview

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

Device Management FOUNDATION Fieldbus consists of a set of software components for efficient planning, commissioning, and maintaining of field devices within ABBs Industrial IT 800xA system.

The main components are:

Fieldbus Builder FOUNDATION Fieldbus

OPC Server FOUNDATION Fieldbus

Device Library Wizard

Device Type Objects

Fieldbus Builder FOUNDATION FieldbusThe 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

OPC Server FOUNDATION Fieldbus Section 1 Product Overview

22 3BDD012902-510

Creating FF Applications running on H1 links

Parameterization of field devices

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 which are available as device type objects 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 FieldbusThe OPC Server FOUNDATION Fieldbus makes data and alarms from FOUNDA-TION Fieldbus 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.

Device Library WizardFor integration of fieldbus devices from ABB and third party vendors into the Industrial IT 800xA environment ABB provides single device type objects. The Device Library Wizard is a tool that is used to install, extend, and restore separately delivered device type objects into an 800xA system. Device type objects are available from 800xA System Device Library DVDs or for download from the ABB SolutionsBank.

Refer to Device Library Wizard on page 369 for detailed information.

Section 1 Product Overview Device Type Objects

3BDD012902-510 23

Device Type ObjectsFOUNDATION Fieldbus device type objects are pre-configured device representations with proven interoperability by online tests with the device. They 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. For frequently used blocks, both specific parameter input dialogs and predefined block-type-specific parameter value sets are provided.

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 DocumentationProduct 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 MonitoringAsset Monitor, Asset Reporter and Asset Viewer acquire and analyze asset status and condition information. They notify operators and maintenance personnel when an abnormal condition calls for maintenance action.

Maintenance ManagementCMMS 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-

Function Block Faceplates Section 1 Product Overview

24 3BDD012902-510

configured CMMS views allowing for the quick and efficient assessment of maintenance needs and status.

Function Block FaceplatesFurthermore 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 after configuration and download, the right faceplate is immediately available for operation of functions distributed in the FF subsystem.

The device type objects 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.

3BDD012902-510 25

Section 2 Technical OverviewFOUNDATION 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. Device Management FOUNDATION Fieldbus supports the ABB Linking Device LD 800HSE.

In an 800xA environment 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.

For detailed information on the FOUNDATION Fieldbus protocol refer to the publications of the Fieldbus Foundation.

Section 2 Technical Overview FOUNDATION Fieldbus

26 3BDD012902-510

3BDD012902-510 27

Section 3 Integration in Plant Explorer

Basic Principles of the Integration in Plant ExplorerThe 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. Refer to Section 2, Configuration / Device Management & Fieldbusses / FOUNDATION Fieldbus Field Devices of the manual Industrial IT, 800xA - System, Configuration (3BDS011222*).

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 can be done either in the Plant Explorer or in the Fieldbus Builder FF. The insertion of new objects can be done in Fieldbus Builder FF as well as in Plant Explorer. Special FF configuration settings as Parameter settings etc., are provided by Fieldbus Builder FF only. When the configuration is done and saved in the Fieldbus Builder FF the configuration data of the HSE Subnet is automatically uploaded to the Plant Explorer Workplace. Then the configured objects appear in the Control Structure.

In order to edit the libraries it is switched from the Object Type Structure to the Fieldbus Builder FF. 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 completion and saving the changes of library contents they have to be uploaded to the Plant Explorer Workplace via the FF Upload Aspect. The changes appear in the Object Type Structure and are automatically available at all HSE subnets.

In one Fieldbus Builder FF instance only one HSE subnet can be configured. Working on the same subnet with different Fieldbus Builder FF instances is possible. Objects that shall be edited have to be reserved by the user and are locked then for all other users. All Fieldbus Builder FF instances and the Plant Explorer Workplace work with the same FF libraries.

Section 3 Integration in Plant Explorer

28 3BDD012902-510

A new opened instance of Fieldbus Builder FF always provides automatically the actual FF libraries. If a library upload has been performed during runtime of a Fieldbus Builder FF instance it gets visible in the status bar by a red LIB writing. An update of the uploaded libraries can be started by double-clicking on the red LIB writing.

The following typical workflow results:

1. Edit FF libraries in Fieldbus Builder FF.

2. After completion save the changes and upload the changed library to the Plant Explorer via the FF Upload Aspect.

3. Create HSE Subnet in the Plant Explorer Workplace.

4. a) Configure HSE Subnet in Fieldbus Builder FF. The actual FF libraries are provided automatically in the Fieldbus Builder FF. If a library update is performed during configuration in Fieldbus Builder FF, an upload can be performed manually if necessary. After saving in Fieldbus Builder FF, the HSE subnet is uploaded automatically to the Plant Explorer workplace.b) Configure HSE subnet in Plant Explorer workplace. The actual FF libraries are provided automatically for configuration.

Figure 1. Mark for Library update

Section 3 Integration in Plant Explorer Object Types in Plant Explorer

3BDD012902-510 29

Object Types in Plant ExplorerAdditional object types which allow the configuration of FF networks are made available to the Plant Explorer Workplace by the Fieldbus Builder FF system extension and device library wizard. Loading the Fieldbus Builder FF system extensions, the FF object groups and the ABB LD 800HSE Object type group are provided. For adding the device object types the ABB Device Library Wizard has to be used.

These object types are combined in the Object Type Structure of the Plant Explorer under the object type group FF libraries. Refer to Figure 2.

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 the basic objects used in Fieldbus Builder FF for the configuration of an HSE subnet.

Figure 2. Object Type Group FF Libraries

H1 and HSE Device Library Section 3 Integration in Plant Explorer

30 3BDD012902-510

H1 and HSE Device LibraryThe 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 129 and Expanding FF Libraries on page 130.

FF Block LibraryThe structure of the FF block library in the Object Type Structure of the Plant Explorer corresponds to the structure of this library in Fieldbus Builder FF. For further details refer to Block Library on page 128.

Reservation of objectsIf objects shall be edited, the user has to lock them by reserving the object. After reserving an object, the user can edit this object. Other users can get only Read access to a reserved object. After finishing work at an object, the object has to be released by the user.

The different possibilities to reserve objects are described in this section.

FF librariesThe FF libraries are locked by opening the object in Fieldbus Builder FF. They dont have to be reserved or released. If they are opened for editing by one user all other users can get Read access only.

Reserve objects in Plant Explorer workplaceIn Plant Explorer workplace an object can be reserved by

Control Structure > Context menu of the object > Reserve...

To release an object in Plant Explorer workplace select

Control Structure > Context menu of the object > Release...

If a Fieldbus Builder FF is opened with objects which are already reserved in Plant Explorer these objects are reserved in Fieldbus Builder as well.

If a user tries to reserve an object, that is already reserved, an information window is shown that the object is reserved and who has reserved it.

Section 3 Integration in Plant Explorer Reserve objects in Fieldbus Builder FF

3BDD012902-510 31

Reserve objects in Fieldbus Builder FFIn Fieldbus Builder FF an object can be reserved by

Context menu of the object > Reserve node

There is the additional possibility to reserve a whole subtree by

Context menu of the root object of the subtree > Reserve nodes recursively

Then the whole subtree is reserved by the user.

All reservations in Fieldbus Builder FF are released when the Fieldbus Builder FF is closed. Objects can be released in the Fieldbus Builder FF by

Context menu of the object > Release node

There is the additional possibility to release a whole subtree by

Context menu of the root object of the subtree > Release nodes recursively

Short time lockingThere are some global objects that cannot be reserved by a user. These objects are locked by the system during saving the objects and then released again. The global objects are:

TAG list

Signal list

Edit FF LibrariesThe following requirements must have been met to be able to carry out the 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.

Reserve recursively/Reserve of an object in a node where several instances of FBB FF are running may popup a dialog showing information which entities are already reserved or focus may switch to FBB FF instance where it is originally reserved.

Insert Device Object Types in FF Libraries by ABB Device Library Wizard Section 3 Integration in

32 3BDD012902-510

Insert Device Object Types in FF Libraries by ABB Device Library WizardTo insert device object types in FFLibraries out of the ABB device library the ABB Device Library Wizard is used. Refer to Device Library Wizard on page 369. After inserting device object types a library upload is requested via FFUpload Aspect of FFLibraries object type group in Object Type Structure.

Edit FF Libraries in Fieldbus Builder FFSwitch to Fieldbus Builder FF to edit the FF libraries, execute 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 Management. Refer to FF Management on page 39.

3. Click Open Project.

4. A Fieldbus Builder FF instance is opened for editing the libraries only.

5. Carry out the required processing steps in the FF libraries in Fieldbus Builder FF. Refer to FF Libraries on page 127.

6. Select menu item: Tools > Check whole project.

7. Save in Fieldbus Builder.

8. Upload library via FFUpload Aspect of FFLibraries object type group in Object Type Structure.

9. Exit Fieldbus Builder FF.

Upload FF Libraries to the Plant Explorer WorkplaceAfter using the device library wizard an upload has to carry out manually to provide the library changes to the Object Type Structure and so also to the HSE subnets. This gives the opportunity to decide at which time a library upload has to be performed.

1. Object Type Structure > FFLibraries, Object Type Group

2. Aspect: FFUpload > Tab: Upload

3. Click Upload.

Section 3 Integration in Plant Explorer Configure HSE Subnet

3BDD012902-510 33

After a successful upload, the green traffic light symbol indicates that the FF library information is up-to-date.

Configure HSE SubnetThe 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 configuration of the HSE subnet can take place either in the Plant Explorer workplace or in the Fieldbus Builder FF.

In the Plant Explorer workplace it is possible to insert, edit or delete objects. For configuration work beyond this, the Fieldbus Builder FF has to be used.

In the Fieldbus Builder FF all activities to configure an HSE subnet can be achieved.

Create HSE Subnet in the Plant Explorer Workplace1. Control Structure > Context menu of the Root object > New Object...

2. Select: Object Types > FFLibraries > HSE Subnet. Refer to Figure 3.

Configure HSE Subnet in Plant Explorer Workplace Section 3 Integration in Plant Explorer

34 3BDD012902-510

3. Enter the name of the HSE Subnet object.

4. Click Create.

Configure HSE Subnet in Plant Explorer WorkplaceTo configure an HSE subnet refer to Section 5, Configuring an FF Network, carry out the required configuration, check for logical errors and save.

Configure HSE Subnet in Fieldbus Builder FFSwitch to Fieldbus Builder FF for configuration of the HSE Subnet (refer to Section 5, 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 Management. Refer to FF Management on page 39.

2. Click Open Project.

Figure 3. Create a New HSE Subnet Object

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

3BDD012902-510 35

3. Configure the HSE Subnet in Fieldbus Builder FF. Refer to Section 5, Configuring an FF Network.

4. Select menu item: Tools > Check whole project.

5. Save the configuration in Fieldbus Builder FF. An upload to the Plant Explorer workstation is started automatically by saving.

6. Exit Fieldbus Builder FF.

In the Control Structure, the objects of the HSE subnet configured in Fieldbus Builder FF appear below the HSE Subnet object. Refer to Figure 4. 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.

Upload HSE Subnet to the Plant Explorer Workplace Section 3 Integration in Plant Explorer

36 3BDD012902-510

Upload HSE Subnet to the Plant Explorer WorkplaceIn case that an automatic upload fails, it is possible to start a new upload out of the plant explorer:

1. Control Structure > HSE Subnet object > Aspect: FFUpload

2. Click Upload.

After a successful upload, the green traffic light symbol indicates that the HSE Subnet configuration is up-to-date.

Figure 4. HSE Subnet in the Control Structure

A user who will upload FOUNDATION Fieldbus related data like HSE Subnets, shall be member of the Application Engineers and Operators group.

Section 3 Integration in Plant Explorer Navigation

3BDD012902-510 37

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

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

1. Object Type Structure > FFLibraries, Object Type Group

2. Aspect: FF Management. Refer to FF Management on page 39.

3. Click Open Project.

Return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

Navigating to the HSE SubnetProceeding 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.

2. Aspect: FF Management. Refer to FF Management on page 39.

3. Click Open Project.

Return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

Navigating to a Selected FF Instance ObjectNavigate 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.

2. Aspect: FF Management. Refer to FF Management on page 39.

3. Click Open Project.

Return to the Plant Explorer Workplace by exiting Fieldbus Builder FF.

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

38 3BDD012902-510

Aspects of Fieldbus Builder FF in the Plant ExplorerTable 1 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 which these aspects are present. These aspects are presented in the following sections.

Table 1. Aspects of Fieldbus Builder FF

Aspects of Fieldbus Builder FF

FF M

an

age

men

t

FF Up

load

FF D

evic

e In

fo

OPC

D

ata

Sou

rce

D

efin

ition

Cont

rol C

onne

ctio

n

HSE Subnet X X X

HSE Device (ABB LD800HSE) X X X XH1 Link X X X

H1 Schedule X

FF Application X

FF Block X X

H1 Device X X X

HSE Host CI860 X X

Section 3 Integration in Plant Explorer FF Management

3BDD012902-510 39

FF Management

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. A red traffic light symbol indicates that the object has not been synchronized. The tab shows the synchronization status for the object as well as for the libraries. Furthermore the locking status is displayed here. Refer to Figure 5.

FF UploadHSE Subnet, HSE Device (ABB LD 800HSE), H1 Link and HSE Host CI860 have got the FFUpload aspect. This aspect allows to start an upload for the particular object out of the Plant Explorer workplace. Normally the upload happens fully automatically when saving the Fieldbus Builder FF.

The FF libraries object type group also has an FFUpload aspect. Here the data applies in a general sense. Refer to Upload FF Libraries to the Plant Explorer Workplace on page 32 for the use of the FFUpload aspect for FF libraries.

Figure 5. FF Management Aspect

FF Device Info Section 3 Integration in Plant Explorer

40 3BDD012902-510

The upload tab shows the synchronization status of the object comprising configuration data and libraries. Refer to Figure 6.

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.

The Log field shows the actions logged during the upload.

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

Figure 6. FFUpload Aspect

If an object upload fails, Log field shows the actions logged during the upload.

Section 3 Integration in Plant Explorer OPC Data Source Definition

3BDD012902-510 41

OPC Data Source DefinitionDuring 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-, Service Group > HSE ServiceProvider-, 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

OPC Data Source Definition Section 3 Integration in Plant Explorer

42 3BDD012902-510

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-

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

, Service Group > HSE Service Provider-, 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 affinity 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 Industrial IT, 800xA - System, Post Installation(3BUA000156*).

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.

Section 3 Integration in Plant Explorer Control Connection

3BDD012902-510 43

Control Connection

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

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

Other aspects, e.g. the Faceplate aspect, can access data of the FF devices via these Control Connection aspects.

Figure 7. Property View Tab

Aspects of LD 800HSE Section 3 Integration in Plant Explorer

44 3BDD012902-510

Aspects of LD 800HSEAmong standard aspects the following set of aspects is available for the FF Linking Device LD 800HSE:

FF ABB LD 800HSE Asset Monitor:The Asset Monitor observes the overall Linking Device status.

Diagnostics Faceplate:The Diagnostics Faceplate provides an easy overview on the current operating state of the Linking Device.

Web Server aspects:They allow for connecting to the built-in web server of the LD 800HSE.

Prerequisite for running the asset monitor: Among the system extensions provided with Device Management FOUNDATION Fieldbus the following system extensions that are provided with Optimize IT Asset Optimization have been added:

Asset Monitor Environment

Asset Optimizer Server

Section 3 Integration in Plant Explorer Asset Monitor

3BDD012902-510 45

Asset MonitorThe Asset Monitor shown in Figure 8 observes the conditions listed in Table 2.

Based on these conditions Asset Optimization Alarms are generated.

Figure 8. Asset Monitor of LD 800HSE

Asset Monitor Section 3 Integration in Plant Explorer

46 3BDD012902-510

Table 2. Conditions Observed by LD 800HSE Asset Monitor

Condition Subcondition Description

Linking DeviceStatus

Normal In the case of a non-redundant 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 Secondary Device

No Primary and no Secondary Device in Live List

Non-redundant Linking Device is not present

Non-redundant Linking Device not in Live List

Section 3 Integration in Plant Explorer Diagnostics Faceplate

3BDD012902-510 47

Diagnostics FaceplateThe Diagnostics Faceplate as shown in Figure 9 provides an easy overview on the current operating state of the linking device.

In the faceplate

LD1 denotes the first configured physical device,

LD2 denotes the second configured physical device (only displayed, if a redundant set of devices has been configured).

Link 1 Status Normal In the case of a non-redundant configuration:Non-redundant Linking Device in Live List.

In the case of a redundant configuration:Primary and Secondary Linking Devices in Live List.

Empty Live List The Live List is empty in a non-redundant Linking Device or in Primary and Secondary Linking Device of a redundant configuration.

Empty Live List (LD1) The Live List of LD1 is empty.Empty Live List (LD2) The Live List of LD2 is empty.Missing Devices Configured H1 devices missing in Live List.

Other Devices Other than the configured H1 devices detected in Live List.

Link 2 Status Refer to condition Link 1 Status.

Refer to condition Link 1 Status.

Link 3 Status Refer to condition Link 1 Status.

Refer to condition Link 1 Status.

Link 4 Status Refer to condition Link 1 Status.

Refer to condition Link 1 Status.

Table 2. Conditions Observed by LD 800HSE Asset Monitor (Continued)

Condition Subcondition Description

Diagnostics Faceplate Section 3 Integration in Plant Explorer

48 3BDD012902-510

IP address and operating state are displayed for each physical device. Refer to Table 3 for possible operating states of a physical device. The operating state is based on the live list state of the device available in the OPC Server FF. Refer to Appendix C, Diagnostic Data.

Figure 9. Diagnostics Faceplate of LD 800HSE

Section 3 Integration in Plant Explorer Diagnostics Faceplate

3BDD012902-510 49

Depending on the impact the operating state of a physical device has on the redundant set of devices, the background color of the operating state will vary. Table 4 explains the meaning of the various background colors.

Table 3. Operating States of a Physical Linking Device

Operating State Description

Primary device in live list device is primary device or non-redundant device

Secondary device in live list device is secondary device

No Primary device not in live list device is primary device

No Secondary device not in live list device is secondary device

Device not present device not in live list

Device not configured no valid configuration data loaded into device

Table 4. Background Color of Operating State

Background Color Description

green Normal

yellow In the case of configured device redundancy:Device redundancy not available; no loss of functionality.

red Failure; possible loss of functionality.

Web Server Aspects Section 3 Integration in Plant Explorer

50 3BDD012902-510

Web Server AspectsTwo Web Server aspects are used for connecting to the built-in web server of the LD 800HSE. Refer to Figure 10.

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

Figure 10. Web Server Aspect of LD 800HSE

Section 3 Integration in Plant Explorer Web Server Aspects

3BDD012902-510 51

3. Enter the IP address of the linking device into the Address field > Apply

In case of a 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 PathThe 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.

2. Add a persistent static network route to the HSE subnet via this Connectivity Server to the network routing table of the Workplace node.

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.

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 (3BSE034463*).

Use the Windows ROUTE command to add a route to the network routing table:

ROUTE -p ADD MASK

= IP network address of the HSE subnet = subnet mask of the HSE subnet = IP address of the Connectivity Server interface attached to the Client/Server network.

For details refer to the help provided for the ROUTE command.

Audit Trail Section 3 Integration in Plant Explorer

52 3BDD012902-510

Audit TrailFieldbus 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

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.

Download errors (e.g. parameter check error) are not stored in any log file. Therefore handle the download errors directly by redoing the last action, maybe by a different scope.

Section 3 Integration in Plant Explorer Security Definition

3BDD012902-510 53

Security DefinitionVarious 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 5.

Advanced Management of FF LibrariesFF 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 device type objects with the Device Library Wizard.

This section describes the underlying mechanisms for an FF library merge, considering as example the import of an HSE Subnet from another system.

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.

For example after usage of the Device Library Wizard a library upload is required. Then the existing object types are replaced by the new object types. If there already have been aspects added to object types they would be lost after next library upload. The following steps have to be executed to preserve these additional aspects:

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

Operating mode of FBB FF Requisite privilege in Plant Explorer

Configuration Configure

Commissioning Download

System Backup and Export Section 3 Integration in Plant Explorer

54 3BDD012902-510

Step 1: Run Upload FF Library. Duplicate object types are moved to a folder within the FFLibraries named "FF Duplicates still in use".

Step 2: Move additional aspects from the moved FF object type X in the duplicate folder onto the FF object type X in the FF device type folder to preserve these aspects.

Repeat Step 2 for all object types that have additional aspects.

During the next FF Library upload, the FF object types identified as unused FF object types are removed from the duplicate folder.

System Backup and ExportUsing the systems Backup or Export function

it is recommended to close all Fieldbus Builder FF instances in the system when running a backup or performing an import/export, and

log-in directly on the machine where the backup/export will be created (HSE Subnet configuration data will not be accessible if a backup/export is done via Remote Desktop session), and

FFLibraries object in the Object Type structure has to be uploaded before starting the export, to ensure that changes of the FF library are considered during export.

Beside the full backup a Export/Import of a single HSE-Subnet and a Export/Import of a block of objects or an object with all subordinate objects can be exported. Export/Import of a single FF device instance is opposite to PROFIBUS handling not supported.

Import/Export a single HSE-SubnetThis section describes how to perform a manual backup for a single FOUNDATION Fieldbus HSE-Subnet. Use this procedure if full backup is not performed in the project.

Section 3 Integration in Plant Explorer Export a single HSE-Subnet

3BDD012902-510 55

Export a single HSE-Subnet1. Log-in directly, do not use a Remote Desktop session

2. Close all Fieldbus Builder FF instances in the system

3. Make sure that HSE-Subnet Traffic Light (FFUpload Aspect) is green

4. Open the Import/Export Tool

5. Sele