FDM R430 User Guide

Honeywell Process Solutions

Field Device Manager - R430 User's Guide EP-FDM-11430 R430 May 2012

Release 430 Honeywell

Notices and Trademarks Copyright 2012 Honeywell International Sárl. Release 430 – May, 2012

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customers. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice. Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell International Inc. Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions 1860 W. Rose Garden Lane Phoenix, AZ 85027 USA 1-800 822-7673

ii

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

About This Document This document provides information on using the Field Device Manager (FDM R430) for configuring and modifying the smart field device information, using different network communication interfaces. It also covers the various features of FDM R430, including configuring network communication interfaces, editing device properties, executing device methods, parameter comparison, maintaining history log, importing/exporting tags, history, and offline configuration.

Prerequisite knowledge It is expected that you are familiar with the following: •

Field devices

•

Network Communication interfaces like Modems and Multiplexers

•

HART protocol

•

FF protocol

•

PROFIBUS protocol

•

DTMs

•

Basic features of Microsoft Windows user management

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

iii

Scope

Scope This document provides procedural steps for performing the tasks related to configuring and monitoring HART, FF and PROFIBUS field devices using FDM R430. It also contains information on the following: •

HART 5/6/7 support

•

FF and PROFIBUS support

•

Station Maintenance View

•

Windows Authentication

•

FDT (Field Device Tool ) or Frame Application in FDM

•

Device DTM support

•

Communication DTM support

•

Mux Monitoring Solution: For more information about mux monitoring solution, refer to the Mux_Monitoring_User_Guide.

•

Gateway DTM support

•

Device DTM configuration support for HART and FF devices in Experion Station

•

Device DTM Configuration support for PROFIBUS devices in FDT Network

•

Device Access Control

•

FDM integration with Safety Manager through Universal Safe Modules

Terms and definitions Term

iv

Definition

Comm DTM

Communication DTM

COTS

Commercial-off-the-Shelf

DD

Device Description Files (These files are in binary format. This contains the device description of HART field devices.)

DDL

Device Description Language

DTM

Device Type Manager Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Terms and definitions

Term

R430 May 2012

Definition

EDD

Electronic Device Description Files (These files are in binary format)

EDDL

Electronic Device Description Language

EPKS

Experion Process Knowledge System

FCH

Field Communication Handler

FDC

Field Device Configurator

FDM

Field Device Manager

FF

Foundation Fieldbus

FHM

FDM HART Multiplexer

FIM

Fieldbus Interface Module

HART

Highway Addressable Remote Transducer

HCF

HART Communication Foundation

HMI

Human Machine Interface

IDE

Integrated Development Environment

IOTA

Input/Output Termination Assembly

MC Toolkit

Multi Communication Toolkit

MODEM

Modulator and Demodulator

MUX

Multiplexer

PDA

Personal Digital Assistant

PMIO

Process Manager I/O

RCI

Remote Communication Interface

RUSIO

Remote Universal Safe I/O

RUSLS

Remote Universal Safe Logic Solver

SM

Safety Manager

SDC

Smart Device Configurator

Field Device Manager - R430 User's Guide Honeywell

v

Conventions Used in this Document

Conventions Used in this Document The following conventions are used in this document: Convention

Description

Words in bold

Field names including buttons in the display, or important phrases.

> Arrow

Windows pull down menus and their options are separated by >. For example, click File > New to open the new platform dialog.

Courier font

Parts of the code quoted for explanations or as examples.

UPPERCASE

Acronyms

UPPERCASE within angle brackets

Command keys For example, press .

References The following list identifies all documents that may be sources of reference for material discussed in this publication. Document Title

vi

Doc ID

FDM R430 Software Installation User’s Guide

EP-FDM-02430

Hart I/O Implementation Guide in Experion Documentation

EPDOC-XX51-en-410A

Series C I/O User’s Guide in Experion Documentation

EPDOC-X126-en-410A

Control Building User’s Guide in Experion Documentation

EPDOC-XX19-en-410A

FDM HART Multiplexer User’s Guide

EP-FDM-13430

Mux Monitoring Solution User’s Guide

EP-FDM-14430

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Support and Other Contacts

Support and Other Contacts United States and Canada Contact: Phone:

Fascimile: Mail:

Honeywell Solution Support Center 1-800-822-7673 Calls are answered by dispatcher between 6:00 am and 4:00 pm Mountain Standard Time. Emergency calls outside normal working hours are received by an answering service and returned within one hour. 1-973-455-5000 Honeywell TAC, MS L17 1860 W. Garden Lane Phoenix, AZ, 85027 USA

Europe, Middle East, and Africa (EMEA) Contact: Phone: Fascimile: Mail:

Honeywell TAC-EMEA +32-2-728-2345 +32-2-728-2696 TAC-BE02 Hermes Plaza Hermeslaan, 1H B-1831 Diegem, Belgium

Contact: Phone:

Honeywell Global TAC – Pacific 1300-364-822 (toll free within Australia) +61-8-9362-9559 (outside Australia) +61-8-9362-9564 Honeywell Limited Australia 5 Kitchener Way Burswood 6100, Western Australia [email protected]

Pacific

Fascimile: Mail:

Email:

India Contact: Phone: Fascimile: Mail:

Email:

R430 May 2012

Honeywell Global TAC – India +91-20- 6603-9400 +91-20- 6603-9800 Honeywell Automation India Ltd 56 and 57, Hadapsar Industrial Estate Hadapsar, Pune –411 013, India [email protected]

Field Device Manager - R430 User's Guide Honeywell

vii

Support and Other Contacts

Korea Contact: Phone: Fascimile: Mail:

Email:

Honeywell Global TAC – Korea +82-2-799-6317 +82-2-792-9015 Honeywell Co., Ltd 4F, Sangam IT Tower 1590, DMC Sangam-dong, Mapo-gu Seoul, 121-836, Korea [email protected]

People’s Republic of China Contact: Phone:

Mail:

Email:

Honeywell Global TAC – China +86- 21-2219-6888 800-820-0237 400-820-0386 Honeywell (China) Co., Ltd 33/F, Tower A, City Center, 100 Zunyi Rd. Shanghai 200051, People’s Republic of China [email protected]

Singapore Contact: Phone: Fascimile: Mail:

Email:

Honeywell Global TAC – South East Asia +65-6580-3500 +65-6580-3501 +65-6445-3033 Honeywell Private Limited Honeywell Building 17, Changi Business Park Central 1 Singapore 486073 [email protected]

Taiwan Contact: Phone: Fascimile: Mail:

Email:

viii

Honeywell Global TAC – Taiwan +886-7-536-2567 +886-7-536-2039 Honeywell Taiwan Ltd. 17F-1, No. 260, Jhongshan 2nd Road. Cianjhen District Kaohsiung, Taiwan, ROC [email protected]

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Training Classes

Japan Contact: Phone: Fascimile: Mail:

Email:

Honeywell Global TAC – Japan +81-3-6730-7160 +81-3-6730-7228 Honeywell Japan Inc. New Pier Takeshiba, South Tower Building, 20th Floor, 1-16-1 Kaigan, Minato-ku, Tokyo 105-0022, Japan [email protected]

Elsewhere Call your nearest Honeywell office.

World Wide Web Honeywell Solution Support Online: https://www.honeywellprocess.com

Training Classes Honeywell Automation College: http://www.automationcollege.com

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

ix

Symbol Definitions

Symbol Definitions The following table lists those symbols used in this document to denote certain conditions. Symbol

Definition ATTENTION: Identifies information that requires special consideration.

TIP: Identifies advice or hints for the user, often in terms of performing a task. REFERENCE -EXTERNAL: Identifies an additional source of information outside of the bookset. REFERENCE - INTERNAL: Identifies an additional source of information within the bookset.

CAUTION

Indicates a situation which, if not avoided, may result in equipment or work (data) on the system being damaged or lost, or may result in the inability to properly operate the process. CAUTION: Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used for alerting against unsafe practices. CAUTION symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual. WARNING: Indicates a potentially hazardous situation, which, if not avoided, could result in serious injury or death. WARNING symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual.

x

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Glossary

Glossary This section assembles and defines the terms and acronyms used in the FDM user’s guide. Term

Definition

B Build Network

Helps to build the network initially after starting the FDM Client or helps to update the actual device status. Reconnects the file that contains the latest device information and displays to the users.

C Connected Device

A device that is physically connected to FDM through the network communication interface.

Commissioned Device

A device that is registered with FDM and available for use.

Network Communication Interface

A device that helps to communicate between FDM and the field devices. Example: RS-232 HART Modem, Honeywell HART DE Modem, RS-485 HART Multiplexer, and Honeywell Experion PKS Multiplexer.

D

R430 May 2012

Database

A set of related files that is created and managed by a database management system (DBMS).

Decommissioned Device

A device that is permanently disconnected from the field.

Device

An instrument that measures and controls the process variables.

Device Configuration

A set of parameters specific to the device and that needs to be configured.

Field Device Manager - R430 User's Guide Honeywell

xi

Glossary

Term

Definition

Device Description (DD)

A file that contains the device information such as commands and parameters. Device vendors develop DD file for each device they develop. These DDs are required to qualify the HART device against the configuration tool. The DD files can be identified with the help of its manufacturer ID, device type, and device version number. A set of instructions written in the HART device description language that defines the parameters, commands, and methods that a host application uses to communicate with a HART field device.

Device History

The past performance information of the device that is stored in the database.

E Experion Integrated Safety Network

It refers to Experion network along with Safety Manager with Universal Safe Modules in which Safety network is integrated with Experion to configure HART devices.

H HART Protocol

Highway Addressable Remote Transducer is an industry standard protocol for digitally enhanced 4-20mA communications with field devices.

HART Device

A device that communicates information using the HART protocol.

HART

Highway Addressable Remote Transducer communication protocol.

HART DE Modem

A network communication interface that establishes the physical connection between the system and the devices. The HART-DE Modem helps to configure a single device at a time.

HART Modem

A network communication interface that establishes the physical connection between the system and the devices. The HART Modem helps to configure a single device at a time.

Hardware Multiplexer

xii

Hardware Multiplexer refers to hardware which enables the communication to multiple HART devices though same physical wiring to the system.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Glossary

Term

Definition

F FDM Client

Client is a workstation that runs FDM program and accesses the server for device information.

FDT Comm Console

User interface to configure the Communication and Gateway DTMs, and to build the complete network using only DTMs.

FDM Server

It refers to the workstation that runs FDM program and allows multiple clients to access it for the device information.

FF Protocol

Foundation Fieldbus is an enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all smart field devices are to communicate with other devices in the control network.

FIM

FIM serves as the bridge between the control environment and the fieldbus control functions. It supports both publish/subscribe and the client/server communication methods to communicate with fieldbus function blocks.

I IOTA

It refers to Universal Safe Module which is either RUSIO or RUSLS module in context of this documentation.

L Locate Device

An option to find the devices in the FDM network.

M Method

Methods are defined in the DD file for the device type with version number. You can select the method and execute it for the device that is connected with FDM.

Modem (Modulator – Demodulator)

A device which converts a signal of one type to other and viceversa. In context of FDM, it refers to a HART modem which enables communication to a HART device through RS232/USB interface on PC. A modem is an analog-to-digital and digital-to-analog converter.

R430 May 2012

Multiplexer

Multiplexer is a communication device that multiplexes (combines) several signals for transmission over a single medium. The multiplexers are called as “MUX.”

Multiplexer Network

A network that connects several multiplexers to connect to multiple field devices. Field Device Manager - R430 User's Guide Honeywell

xiii

Glossary

Term

Definition

O Offline Configuration

Editing and saving the device parameter values, when the device is not loaded. The changes in offline configuration can be transferred to the device using offline download.

Offline Template

FDM template representing the parameters of the device. It is used for offline configuration and the device parameters are initialized with default values.

P Parameter

Any value/measurement represented by the field device passed to a program by the user or by another program in order to customize the program for a particular purpose.

Process Variable (PV)

A process parameter such as Temperature, Flow, Level, and so on, that is being measured or controlled.

Protocol

Protocol is a set of rules that govern transmitting and receiving of data. The protocol is intended to provide a reliable, transaction oriented communication path to and from slave devices such as field instruments, for digital data transfer.

R Registered Device

A device that is currently connected to FDM, for which the DDs are stored in the FDM database.

S

xiv

Spare Device

A device that is registered with FDM, but not assigned for operation. These devices appear in the Spare Device folder.

Series C I/O

Series C I/O modules are an expanding family of traditional and special function input/output signal interface devices. These I/O modules share the same form factor as the C300 Controller and reside on the same type of common mounting system as other Series C components.

Safety Builder

Safety Builder is the client used for configuring Safety Manager network (SMs, IOTAs, and Channels).

Safety Network

Safety Network with Universal Safe Modules (RUSIO/RUSLS).

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Glossary

Term Standalone Safety Network

Definition It refers to a network having Safety Manager with Universal Safe Modules without Experion configured as standalone to configure HART devices.

T Tag

Tag is the label that is assigned to each device to represent the device type, area under which the device is connected.

U Universal Safe Modules

Common classification used for RUSIO (Remote Universal Safe I/O) or RUSLS (Remote Universal Safe Logic Solver).

USB Modem

A network communication interface that establishes the physical connection between the system and the devices. The USB Modem helps to configure a single device at a time.

V Vendor

Manufacturer of the field devices.

W Workstation

R430 May 2012

Refers to the PC that runs the FDM tool.

Field Device Manager - R430 User's Guide Honeywell

xv

Glossary

xvi

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Contents 1.

INTRODUCTION TO FDM R430 ...................................................25 1.1

Overview ....................................................................................................... 25

1.2

Supported technologies .............................................................................. 26 Device description files (DDs and EDDs) .................................................................26 FDT-DTM .................................................................................................................27 HART protocol ..........................................................................................................29 Foundation Fieldbus protocol ...................................................................................29 PROFIBUS protocol .................................................................................................30

1.3

FDM functions and features ........................................................................ 31 Advanced Search .....................................................................................................31 Audit Trail .................................................................................................................31 Automatic network updation .....................................................................................31 Bulk Operations ........................................................................................................31 Client-Server Architecture ........................................................................................31 Device Access Control .............................................................................................32 Device History ..........................................................................................................32 Device Configuration ................................................................................................32 Device Documentation .............................................................................................32 Display Filter.............................................................................................................32 Dashboard ................................................................................................................32 FDM integration with Experion PKS .........................................................................33 FDM integration with Experion LS ............................................................................33 FDM integration with OneWireless ...........................................................................33 FDM integration with Safety Manager through Universal Safe Modules ..................33 Health Scan on the device........................................................................................33 Import and Export Operations ..................................................................................34 Mux Monitoring Solution ...........................................................................................34 Offline Configuration .................................................................................................34 QuickView ................................................................................................................34 Role based User Management .................................................................................34 Station Maintenance View ........................................................................................34 Support for device description files ...........................................................................35

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

xvii

Contents

Support for Experion Redundancy........................................................................... 35 Third party application integration............................................................................ 35 Windows® authentication and Single Sign On ........................................................ 35

1.4

FDM software components and utilities .....................................................36 Overview ................................................................................................................. 36 FDM Server ............................................................................................................. 36 FDM Client............................................................................................................... 36 FDT Comm Console ................................................................................................ 37 FDM RCI ................................................................................................................. 37 FDM Mux Monitoring Solution ................................................................................. 38 FDM HART Multiplexer ............................................................................................ 38 FDM Server Management Tool ............................................................................... 39 FDM Maintenance ................................................................................................... 39 Dr. FDM ................................................................................................................... 39 FDM Data Backup - Restore.................................................................................... 39 FDM Migration Tool ................................................................................................. 39

1.5

Getting started with FDM .............................................................................40 Logging on to the FDM Server Management Tool ................................................... 40 Changing password ................................................................................................. 42 Stopping the FDM Server ........................................................................................ 43 Restarting the FDM Server ...................................................................................... 44 Updating FDM license ............................................................................................. 45 Logging on to the FDM Client .................................................................................. 46 Logging on to the FDT Comm Console ................................................................... 50

2.

USER MANAGEMENT ................................................................. 53 2.1

Overview of FDM role-based User Management .......................................53 FDM Classic Server Security ................................................................................... 53 Windows Security .................................................................................................... 53 Support for Windows Groups................................................................................... 53 Roles and Privileges ................................................................................................ 54 Administrator access privileges ............................................................................... 54 Supervisor access privileges ................................................................................... 56 Engineer access privileges ...................................................................................... 57 Operator access privileges ...................................................................................... 58

xviii

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Contents

2.2

Managing users ............................................................................................ 58 Adding a new user in Classic Server Security ..........................................................58 Adding a user in Windows Security ..........................................................................60 Modifying user details ...............................................................................................63 Deleting a user .........................................................................................................64

2.3

Managing groups ......................................................................................... 65 Overview ..................................................................................................................65 Prerequisite to add a group in FDM ..........................................................................65 Adding a Windows group and associating a role ......................................................66 Editing roles and privileges of groups .......................................................................68 Deleting groups ........................................................................................................69

2.4

Managing roles ............................................................................................. 70 Adding a role ............................................................................................................70 Modifying a role ........................................................................................................72 Deleting a role ..........................................................................................................74

3.

NETWORK CONFIGURATION .....................................................75 3.1

Overview ....................................................................................................... 75

3.2

Configuring FDM for an RS-232 HART modem ......................................... 76 Background ..............................................................................................................76 Configuring COM port setting for RS-232 HART Modem .........................................76 Configuring RS-232 HART modem network .............................................................78

3.3

Configuring FDM for a Honeywell HART DE modem ............................... 79

3.4

Configuring FDM for an RS-485 HART multiplexer .................................. 81

3.5

Configuring FDM for Honeywell Experion ................................................. 83

3.6

Configuring FDM for Safety network.......................................................... 89 Prerequisite ..............................................................................................................89 Importing Safety Builder Export file ..........................................................................89 Configuring FDM for Experion integrated Safety network ........................................91 Configuring FDM for Standalone Safety network .....................................................94 Online update of network configuration ....................................................................98

3.7

Configuring Comm DTM network in FDM ................................................ 103

3.8

Editing a network configuration ............................................................... 104

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

xix

Contents

3.9

4.

Deleting a network configuration ..............................................................106

FDM OPERATIONS .................................................................... 107 4.1

Overview of FDM Client interface..............................................................107 FDM Client - Main window ..................................................................................... 107 Server Poll Status Indication.................................................................................. 108 System notifications ............................................................................................... 109

4.2

Online view functions .................................................................................110 Overview of Online View ....................................................................................... 110 Network View......................................................................................................... 110 Device State View ................................................................................................. 114

4.3

Offline View functions ................................................................................117 Overview of Offline View ....................................................................................... 117 Offline configuration ............................................................................................... 117 Display filter functions ............................................................................................ 118 Device library functions ......................................................................................... 118

4.4

FDM device tags..........................................................................................122 Overview of FDM Tags .......................................................................................... 122 Device tag generation for RS-485 Multiplexer and Modem networks .................... 122 Device tag generation for Experion networks ........................................................ 122 Device tag generation for COMM DTM Interface................................................... 123 Device tag generation for Safety networks ............................................................ 124

4.5

Customizing the FDM settings ..................................................................125 Customizing the System settings........................................................................... 125 Customizing the Audit Trail settings ...................................................................... 133 Choosing DD/DTM load settings ........................................................................... 141

4.6

Customizing the FDT health scan settings ..............................................143

4.7

Switching between FDM Servers ..............................................................144

4.8

Building networks .......................................................................................145 Overview ............................................................................................................... 145 Detecting devices on the network .......................................................................... 146 Building FDT networks .......................................................................................... 147 Configuring PROFIBUS masters ........................................................................... 157 Building Safety networks ....................................................................................... 161

xx

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Contents

4.9

Managing DDs ............................................................................................ 166 Adding a DD file .....................................................................................................166 Deleting a DD file ...................................................................................................167 Synchronizing a DD-based template ......................................................................168

4.10 Managing DTMs .......................................................................................... 169 Updating DTM Library ............................................................................................169 Adding DTMs..........................................................................................................172 Removing DTMs .....................................................................................................172

4.11 Device configuration using DD ................................................................. 174 Overview ................................................................................................................174 Loading a device using DD.....................................................................................175 Configuring a device using DD ...............................................................................179 Executing methods .................................................................................................186 Editing Device Properties from a DD Configuration ................................................189 Exporting online configuration using DD ................................................................191 Saving History Records using DD ..........................................................................192 Saving an Online Configuration as an Offline Configuration using DD ...................193 Viewing device notifications....................................................................................195 Scanning Dynamic Parameters ..............................................................................196 Comparing device configuration .............................................................................198

4.12 Device configuration using DTM .............................................................. 202 Overview ................................................................................................................202 Loading a device using DTM ..................................................................................202 Assigning the DTM to device ..................................................................................207 Configuring a device using DTM ............................................................................209 Exporting online configuration using DTM ..............................................................211 Saving History records using DTM .........................................................................211 Saving an Online Configuration as an Offline Configuration using DTM ................212

4.13 ValveLink integration for FF ...................................................................... 213 4.14 Offline configuration .................................................................................. 215 Overview ................................................................................................................215 Creating a DD offline configuration for a specific device type.................................216 Creating a Generic DD offline configuration ...........................................................221 Creating a DTM offline configuration ......................................................................225 Editing an offline configuration ...............................................................................226 R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

xxi

Contents

Downloading a DD/DTM based offline configuration to an online device .............. 230 Using the Bulk Offline Download feature ............................................................... 235

4.15 Working with device history ......................................................................241 Overview ............................................................................................................... 241 Example for viewing Device History ...................................................................... 242 Importing device configuration history from FDC into FDM ................................... 244

4.16 Bulk Operations ..........................................................................................245 Saving Bulk History ............................................................................................... 245 Saving Bulk Offline Templates............................................................................... 251 Advanced Filter...................................................................................................... 251

4.17 Import and Export Operations ...................................................................253 Overview ............................................................................................................... 253 Importing and Exporting Device Tags .................................................................... 253 Importing and Exporting Audit Trail records .......................................................... 259 Importing and Exporting Offline Device Configuration ........................................... 267 Importing and Exporting Device history ................................................................. 274

4.18 Delete records .............................................................................................282 Deleting Device Tags ............................................................................................ 282 Deleting Offline Device Configuration .................................................................... 287 Deleting Device history .......................................................................................... 289

4.19 Using dashboard.........................................................................................294 Overview ............................................................................................................... 294 Review Information ................................................................................................ 294

4.20 Using display filters ....................................................................................301 Overview ............................................................................................................... 301 Creating a Display Filter from the Query View ....................................................... 301 Creating a Display Filter from the Device View...................................................... 305 Applying a Display Filter ........................................................................................ 307

4.21 Using advanced search..............................................................................308 4.22 Device access control ................................................................................310 Overview ............................................................................................................... 310 Explicit locking ....................................................................................................... 310 Implicit Locking ...................................................................................................... 312 Exclusive access ................................................................................................... 317 xxii

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

Contents

Unlocking a device .................................................................................................319 Lock All/Unlock All ..................................................................................................326

4.23 Working with device documentation........................................................ 327 Overview ................................................................................................................327 Attaching device documentation at Device-type level ............................................328 Attaching device documentation at Device instance level ......................................329 Attaching device documentation at System level ...................................................330 Uploading an updated document ............................................................................331 Detaching device documents .................................................................................333

4.24 Working with FDM Applications ............................................................... 335 Overview ................................................................................................................335 Tasks associated with FDM Applications ...............................................................335 Attaching an application at Device-type Level ........................................................336 Attaching an application at System Level ...............................................................337 Launching an attached application .........................................................................338 Detaching an attached application .........................................................................339

4.25 FDM Help ..................................................................................................... 342 4.26 About FDM .................................................................................................. 342 4.27 FDM Operational Restrictions ................................................................... 343

5.

6.

FDM STATION MAINTENANCE VIEW .......................................347 5.1

Overview ..................................................................................................... 347

5.2

Pre-requisites for viewing a device in the Maintenance view................ 347

5.3

Configuring relationship between Experion Server and FDM Server ... 348

5.4

Access Rights for Maintenance View ....................................................... 352

5.5

Starting Maintenance View in Station ...................................................... 353

FDM DATA BACKUP – RESTORE UTILITY ..............................359 6.1

Overview ..................................................................................................... 359

6.2

Logging on to the Backup and Restore utility ........................................ 359

6.3

Taking a backup of the FDM database ..................................................... 361

6.4

Restoring the database.............................................................................. 362

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

xxiii

Contents

7.

FDM DIAGNOSTICS .................................................................. 363 7.1

Overview of Dr. FDM ...................................................................................363

7.2

Capturing Diagnostics ...............................................................................363

7.3

Service Control functions ..........................................................................369

xxiv

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1. Introduction to FDM R430 1.1

Overview FDM application is an asset management system that supports client/server architecture. The application provides an environment that enables you to configure commission and maintain smart field devices. It supports configuration of device parameters and methods execution for Highway Addressable Remote Transducer (HART), Foundation Fieldbus (FF), and PROFIBUS devices. For HART, it supports protocol version 5.x, 6.x and 7.x. It also supports device configuration using Electronic Device Description Language (EDDL) based configuration screens and FDT-DTM. PROFIBUS device and FF device support is provided only using FDT-DTM (Field Device Tool-Device Type Manager). It also helps in diagnosing field devices. FDM supports FF Device DTMs to read, display and write all the commissioned devices connected to Fieldbus Interface Module in Experion. It also supports Fisher ValveLink DTM to perform maintenance operations and to view diagnostic data for FF Fisher Valves. With FDM R430, FDM is enhanced for the following: •

Support for HART 7 protocol

•

FDM integration with Safety Manager through Universal Safe Modules to maintain HART devices connected to safety systems

•

FDT Comm Console to manage networks and devices integrated in FDM through FDT Communication and Gateway DTMs

•

Support for Experion S8 HART I/O modules

•

Provision for Device Access Control where write access to devices can be configured with password protection

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

25

1. Introduction to FDM R430 1.2. Supported technologies

1.2

Supported technologies FDM supports the following technologies to configure, commission, and maintain field devices.

Device description files (DDs and EDDs) HART devices are capable of providing functions and features, far beyond the basic task of providing a process input or accepting a control output to manipulate process conditions. HART device vendors create a Device Description (DD) or (EDD) for every device that describes the functions and features specific to that device. The DD and EDD also contain information essential for the successful configuration and calibration of the device. FDM uses original unmodified device vendor DDs and EDDs, to provide full configuration and setup for all HCF registered HART devices. Ensure that you use the latest DD and EDD for a particular device type and revision. DDs or EDDs are available from the device vendors. Unlike other configuration tools, FDM does not require custom DD and EDD to be developed for the tool itself. It supports all the unmodified DDs and EDDs of the devices, as registered with the HART Communication Foundation (HCF). ATTENTION FDM supports all devices that have their DDs registered with the HCF.

Electronic Device Description Language (EDDL) EDDL (Electronic Device Description Language) is a clear, structured text description that specifically describes field device data to host systems. It is an enhancement over DD language. It constructs the defined presentation of device information by the host applications and document hosts to store the data on behalf of the device. Using EDDL constructs, DD writers can define the user interface rules that the host application need to adhere to while displaying the user interface for that device. It also has constructs like charts, graphs and so on that provides enhanced user experience. FDM supports HART device configuration through EDDL based DDs.

26

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.2 Supported technologies

Methods Execution Methods are predefined sequence of steps that can be executed by a Host. The device vendors develop these methods and supply them as a part of the device DD file/EDD file or device DTM of the devices. Some examples of methods are: •

Commanding the device to complete a calibration operation.

•

Commanding an advanced diagnostic test procedure.

•

Executing tests to gather information on device operation.

FDM supports: •

Method execution through DD/EDD file or device DTM for HART protocol.

•

Method execution through device DTM for FF protocol.

•

Method execution through device DTM for PROFIBUS protocol.

FDT-DTM FDM supports the Field Device Tool (FDT)-Device Type Manager (DTM) technology to configure HART, FF, and PROFIBUS devices. Field Device Tool: A standard interface defined by the FDT group for integration with field devices. It is used by the host applications like FDM to integrate with the devices and provide the configuration and maintenance capabilities. Any host application, which implements the FDT-DTM technology is referred to as FDT Frame. It has the following three primary functions. •

Interfacing with the Device DTM for device configuration.

•

Interfacing with the Gateway and Communication DTMs to communicate with devices.

•

Managing the DTM Catalog.

Device Type Manager: This is analogous to a device driver that is developed by device vendors for a particular device type. DTM enables usage of devices in all the asset management and device configuration software like FDM, with the help of the FDTDTM technology. •

The DTM has the following primary functions.

•

Provides a Graphic User Interface for device configuration.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

27

1. Introduction to FDM R430 1.2. Supported technologies

•

Provides device configuration, calibration, and management features for the particular device.

The following are the three types of DTMs. Device DTM: The Device DTM represents a field device and contains the details of the User Interface, Device Parameters, DTM documentation for configuration and calibration of devices and diagnostic functions for the device. Communication DTM: The Communication DTM is software that represents a communication device. It has the following features. •

It is provided by the communication device vendor.

•

It can be loaded in an FDT frame in a host application.

•

It is responsible for the communication between FDT host application and physical communication device.

•

It implements the standard interfaces, as specified by the FDT – Group.

•

It allows browsing the complete network and configuring to work with a different type of network.

•

It has its own UI, which allows configuring the communication device for proper communication with network.

•

It has its own installations, which take care of registering the DTMs.

Gateway DTM: The Gateway DTM is the software that represents a gateway device. It has the following features. •

It uses the communication DTMs or other communication drivers for communicating with the devices. Any requests from the devices connected to the Gateway are sent to the Gateway DTM, which is then sent to the Communication DTMs.

•

It has its own UI, which allows configuring the Gateway device for proper communication with network.

•

It has its own installations, which take care of registering the DTMs.

For example, HART-on-PROFIBUS Gateway DTM represents the HART-onPROFIBUS Gateway device that is used for connecting the HART devices on the PROFIBUS networks.

28

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.2 Supported technologies

ATTENTION PROFIBUS devices can be configured in FDM only through DTMs. FDM does not support configuration of PROFIBUS devices through DD/EDD.

HART protocol In a typical process control environment, field devices such as pressure, level, and temperature transmitters and valve positioners provide the physical connection to the process. These devices allow the control system to monitor and manipulate process conditions. Smart field devices, such as HART devices, maintain a database of process configuration, identification, and diagnostic information in memory. These devices use the HART digital protocol (governed and maintained by the HART Communication Foundation) to communicate with the control and asset management system. The HART Communication Foundation (HCF) has a membership of over 150 vendors (including Honeywell), offering over 500 different HART devices. HART is an open smart field device protocol available for use by all member companies. For more details about HART and HCF, visit the web site at: http://www.hartcomm.org/. FDM supports HART devices conforming to HART 5.x, 6.x and 7.x (wired) versions of the HART protocol.

Foundation Fieldbus protocol Foundation Fieldbus is an enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all smart field devices are to communicate with other devices in the control network. The technology is based upon the International Standards Organization's Open System Interconnection (OSI) model for layered communications.Foundation Fieldbus is a sophisticated, objectoriented protocol that uses multiple messaging formats and allows a controller to recognize a rich set of configuration and parameter information (device description) from devices that have been plugged into the bus. Foundation Fieldbus even allows a device to transmit parameters relating to the estimated reliability of a particular piece of data. Foundation Fieldbus uses a scheduler to guarantee the delivery of messages, so issues of determinism and repeatability are solidly addressed (determinism means knowing absolute worst-case response times with 100% certainty). Each segment of the network contains one scheduler. For more details about FF, visit the web site at: www.fieldbus.org.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

29

1. Introduction to FDM R430 1.2. Supported technologies

PROFIBUS protocol PROFIBUS is a powerful and versatile two-wire digital fieldbus system. It is mainly used in the field level with interfacing capabilities downward towards the sensor/actuator level and upwards towards the production and enterprise levels. PROFIBUS devices connected in the PROFIBUS network gives diagnostic information about the health of the devices and the measured values, along with the values themselves. This information is helpful for better maintenance and thus reducing downtime. PROFIBUS is used in Process automation, Factory automation, Motion control and so on. FDM supports configuration and collection of diagnostics of PROFIBUS PA and PROFIBUS DP devices using the FDT-DTM technology. FDM hosts device, communication, and gateway DTMs provided by the PROFIBUS device vendors. You can configure and perform maintenance activities on PROFIBUS devices in the field using these DTMs. PROFIBUS International has over 1200 members worldwide which includes many field device vendors. For more details about PROFIBUS and PROFIBUS International, visit the web site at: www.profibus.com Multi Master Configuration PROFIBUS Masters are classified on a high level into the following two types.

30

•

Master which supports cyclic data communication (DPV0) is normally referred to as Class1 Masters. The Class-1 master (DPM1) is the central control unit of a system, for example, a PLC that exchanges data with the field devices within a specified message cycle. All measured values and set point values required to control the system as well as the device status data are transmitted. When compared with conventional techniques, the cyclic communication of the Class-1 master assumes tasks of the analog 4 to 20 mA standardized signals and additionally enables the bidirectional exchange of data.

•

Master which supports acyclic data communication (DPV1) is normally referred to as Class-II Masters. Class-II masters (DPM2) are used for operation and monitoring purposes and during start-up. The associated exchange of data takes place, if required. Therefore, class-II masters require acyclic communication services exclusively.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.3 FDM functions and features

In the Control System, essential parameters are available through the cyclic data (DPV0). If you want additional data regarding the devices, use acyclic data communication. In this case, you can send commands to the devices and request for additional data from Asset Management Tool through Class 2 masters, which support DPV1 Communication. The following are the typical examples.

1.3

•

Softing FG100

•

T&H xEPI

FDM functions and features FDM Server and FDM Client allow communication across the network throughout the plant area. It is possible to remotely accomplish device-monitoring, configuration, and setup from the operator center, maintenance shop, or relay room. Following are the key functions and features of FDM.

Advanced Search FDM allows you to easily locate specific devices in the network tree using this feature.

Audit Trail FDM provides an Audit Trail feature that logs predefined user actions, custom useractions, and some implicit actions. It can be viewed based on various filter criteria. This feature meets CFR-11 standards.

Automatic network updation FDM detects HART and FF device assets automatically and adds it to the FDM database. The Dynamic detection feature discovers new devices connected to the network after the network is built in FDM.

Bulk Operations FDM provides the Bulk Operations feature that enables you to create history records and offline templates for large number of devices at a time.

Client-Server Architecture FDM supports client-server architecture in which different components may be installed on different systems. In addition, it supports a multi client, multi server architecture, where multiple clients can connect to the same server and one client can connect to any server. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

31

1. Introduction to FDM R430 1.3. FDM functions and features

Device Access Control FDM supports the following features that are used for enhancing the security to the devices, with respect to "write access" to them. •

Automatic lock of devices as they are discovered on the network

•

Password protection for access control of devices that are connected to a network

•

Automatic lock of an unlocked device after a specified time period

•

Exclusive access to unlocked devices

•

Manual lock/unlock of all the devices connected to a network/hierarchy

All these features are individually configurable. Hence, you can customize this function to your specific plant needs.

Device History FDM allows you to historize device configuration. You can also view the historized device configuration.

Device Configuration FDM supports configuration of HART devices through DD and PROFIBUS and FF devices through FDT-DTM technologies. FDM provides an option to view the current configuration settings and downloads configurations from FDM to devices in the field. It can compare configurations of different device instances or of the same.

Device Documentation FDM allows you to attach documents at Device Type level, Device Instance level, and at System level for quick reference.

Display Filter FDM allows you to create filters using various filtering criteria. Using this you can customize the view of the network.

Dashboard Using Dashboard feature, you can view all types of information related to the FDM Client, FDT Comm Console, devices, RCIs, gateways, networks and operations at a single place and provides quick and easy access to it.

32

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.3 FDM functions and features

FDM integration with Experion PKS When integrated with Experion PKS, FDM supports configuration, method execution and monitoring of following devices. •

HART devices connected to a Series C I/O module, PMIO module, 1756 HART I/O module, and S8 HART I/O module.

•

FF devices connected to FIM2, FIM4 and FIM8 modules.

FDM integration with Experion LS When integrated with Experion LS, FDM supports configuration and monitoring of HART devices. Refer to Experion LS R311 Product documentation for more information.

FDM integration with OneWireless When FDM is integrated with OneWireless, it supports configuration and monitoring of wireless devices. Refer to OneWireless R210 Network Planning and Installation Guide and OneWireless R210 Software Change Notice for more information.

FDM integration with Safety Manager through Universal Safe Modules FDM supports configuration and maintenance of HART devices connected to Safety Manager through Universal Safe Modules (RUSIO/RUSLS). However, HART channels connected to local I/O network of SMs are supported through multiplexer network configuration in FDM.

Health Scan on the device FDM indicates the device health status without opening the device configuration for HART devices connected to HART hardware multiplexer, Modem and Experion network. It also indicates the device health status for HART and PROFIBUS devices connected to FDT network. The device health is displayed when the device is discovered for the first time during build network. A healthy device is indicated in green and if a device is found unhealthy, it is indicated in red.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

33

1. Introduction to FDM R430 1.3. FDM functions and features

ATTENTION For a device connected to FDT Network, the device health does not update for a time period when that device is loaded with DTM in the FDT Comm Console. To resume the health update for that device, its DTM configuration page must be closed.

Import and Export Operations FDM allows you to import and export device tags, audit trail records, offline configurations, and device history.

Mux Monitoring Solution FDM allows you to access device diagnostic information from HART devices connected to HART Multiplexer network into the Experion system using Mux Monitoring Solution. And also, HART devices connected to Experion integrated Safety network can be mux monitored.

Offline Configuration FDM allows you to configure a set of device parameters without the need for a device to be available physically. This offline configuration can later be used for configuring an online device.

QuickView Using QuickView feature, you can view the information related to device status, device information, network information, device state information, lock state, and attached documents for all connected and disconnected devices. These informations are available at a single place to access easily.

Role based User Management FDM provides robust role-based user management. It allows you to create users with two mechanism called FDM Classic Server Security and Windows Security.

Station Maintenance View FDM allows you to view the complete device configuration from Experion Flex Station displays. It enables an operator to do necessary modifications to the device configuration.

34

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.4 FDM software components and utilities

Support for device description files FDM uses original unmodified device vendor DDs and EDDs, to provide full configuration and setup for all HCF registered HART devices. DDs or EDDs are available from the device vendors.

Support for Experion Redundancy FDM supports automatic Experion Redundancy switchover such that there is no loss of network view. You need not perform an explicit Build Network operation to re-detect the devices.

Third party application integration FDM HART Multiplexer module of FDM can be used by any third party tools such as valve diagnostic applications to communicate with the HART devices connected to the FDM through one of the following networks. •

Experion network

•

Hardware Multiplexer

•

HART Modem

•

HART DE Modem

Windows® authentication and Single Sign On System administrator can associate an existing Windows user to a particular role. Therefore, system administrator need not create a user using FDM user management utility. Single Sign On allows you to skip the login screen, if you are logging in as an authorized Windows user.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

35

1. Introduction to FDM R430 1.4. FDM software components and utilities

1.4

FDM software components and utilities Overview FDM consists of the following software components. •

FDM Server

•

FDM Client

•

FDM RCI

•

FDM Mux Monitoring Solution

•

FDM HART Multiplexer

FDM consists of the following utilities. •

FDM Server Management Tool

•

FDT Comm Console

•

FDM Maintenance

•

Dr. FDM

•

FDM Data Backup - Restore

•

FDM Migration Tool

FDM Server The FDM Server maintains a record of all users and the Device information such as Device type, Device manufacturer’s detail, Device history, and Device Description files for all devices connected to FDM. The FDM Server also stores Device configuration information, Device history, offline configurations, and audit trail information. FDM Server uses the FDM Remote Communication Interface to communicate with the devices in the field. FDM Server supports simultaneous access from multiple FDM Clients.

FDM Client The FDM Client provides the user interface to interact with the FDM Server, which in turn interacts with the database and the field network through the Remote Communication Interface (RCI) to carry out the necessary task. Using FDM Client, you can access all the FDM functions and communicate with the devices remotely.

36

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.4 FDM software components and utilities

FDT Comm Console FDT Comm Console allows you to configure FDT networks, and build the complete network using DTMs. It also shows other networks including FDT networks as configured on a particular FDM server. But, it does not allow you to perform any operations on other networks. You can also configure devices connected to FDT network under local RCI, in FDT Comm Console.

FDM RCI The FDM Remote Communication Interface (RCI) server is capable of handling multiple network communication interfaces to communicate with the field devices. FDM supports network communication interfaces like RS-232 HART Modem, RS-485 HART Multiplexer, Honeywell HART DE Modem, Honeywell Experion PKS, COMM DTM Interface, and Safety network with Universal Safe Modules. The FDM uses these interfaces to communicate with the field devices. •

The RS-232 HART Modem is widely used when it is required to communicate with a single device at a time. FDM also supports the USB HART modem.

•

The RS-485 HART Multiplexer network enables you to communicate with multiple field devices over a single communication line. Maximum six Mux networks per RCI are allowed with single FDM Server and these networks cannot be associated to different FDM Servers.

•

The Honeywell HART DE Modem has the capability to handle both HART protocol and Honeywell DE protocol. However, FDM supports only the HART protocol. FDM supports HART DE Modem connection through USB to RS232 converter from CableMAX.

•

The Honeywell Experion PKS network enables you to communicate with HART and FF devices. HART devices are connected to the Experion HART enabled I/Os. FF devices are connected to the FIM. When you configure Honeywell Experion PKS interface, you can also associate Safety network with Universal Safe Modules to configure HART devices.

•

The COMM DTM Interface enables you to configure HART and PROFIBUS (that supports DTM) Communication/Gateway DTMs to communicate with HART and PROFIBUS devices respectively.

•

The Safety network with Universal Safe Modules can be configured as Standalone Safety Network (without Experion integration) to configure HART devices connected to Universal Safe Modules.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

37

1. Introduction to FDM R430 1.4. FDM software components and utilities

FDM Mux Monitoring Solution The FDM Mux Monitoring Solution component enables Experion to access HART devices connected to the hardware multiplexer network through the FDM. Using the Mux Monitoring solution, Experion receives alarms/events for the HART devices that are connected to the multiplexer network. With FDM R430, the HART devices connected to Experion integrated Safety Network can be monitored for alarms. REFERENCE - INTERNAL For more details, refer to the Mux Monitoring Solution User’s Guide.

FDM HART Multiplexer FDM HART Multiplexer emulates the P+F HART multiplexer. Any third party tool capable of communicating with the P+F HART multiplexers can use this solution to communicate with devices connected to FDM. FDM HART Multiplexer must be installed along with the FDM Client on a system preinstalled with a third party tool such as valve diagnostic application. The third party tool communicates with the FDM HART Multiplexer through the COM ports in a loop back configuration. The third party tool communicates with the devices connected to the FDM Server through FDM HART Multiplexer. FDM HART Multiplexer enables you to configure a device list based on selection of multiple manufacturer and the device types. The device list can be created, modified, and deleted. The created device list can be saved and later used for viewing the devices in the third party tool. The following are the operations that can be performed using the FDM HART Multiplexer feature. •

Configure a device list.

•

Start the FDM HART Multiplexer service.

•

Send devices to the FDM HART Multiplexer service, so that it can be used in the third party application. REFERENCE - INTERNAL For more details, refer to the FDM HART Multiplexer User’s Guide.

38

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

FDM Server Management Tool Enables you to configure/view network communication interfaces, update product license, and control (start and stop) the FDM Server.

FDM Maintenance FDM Maintenance, enables you to modify the present installation by selecting or removing modules, or reinstall the program data if any existing file is corrupted. Using FDM Maintenance, you can also remove FDM.

Dr. FDM FDM enables you to collect diagnostic information related to FDM functioning. In the event of issues faced with the usage of FDM software, this diagnostic tool can be run on the systems where FDM components are installed. The log files can be sent to Honeywell TAC for further analysis.

FDM Data Backup - Restore FDM enables you to take a backup of the FDM database and restore FDM with the backed up database.

FDM Migration Tool FDM enables you to migrate data from the previous releases to current release. REFERENCE - INTERNAL For more details, refer to the FDM Migration User’s Guide.

TIP To access the FDM utilities, choose Start > All Programs > Honeywell FDM.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

39

1. Introduction to FDM R430 1.5. Getting started with FDM

1.5

Getting started with FDM The following table lists the tasks covered in this document that are related to FDM configuration and operation. Task

Performed using…

Reference

Logging on to FDM Server Management Tool

FDM Server Management Tool

Logging on to the FDM Server Management Tool

Updating FDM license

FDM Server Management Tool

Updating FDM license

Configuring Networks

FDM Server Management Tool

Network configuration

Logging on to FDM Client

FDM Client

Logging on to the FDM Client

Adding users

FDM Client

Adding a new user in Classic Server Security

Building Networks

FDM Client

Building networks

Performing online configuration

FDM Client

Device configuration

Logging on to FDT Comm Console

FDT Comm Console

Logging on to the FDT Comm Console

Logging on to the FDM Server Management Tool FDM Server Management Tool is used for updating the license and managing the networks. ATTENTION If you log on to the server computer as any user other than the administrator, and then launch the FDM Server Management Tool, you are prompted to provide administrative privileges.

40

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

To logon to the FDM Server Management Tool, perform the following steps. Step 1

Action Choose Start > All Programs > Honeywell FDM > FDM Server Management Tool. The Server Manager login window appears.

TIP You can also click the FDM Server Management Tool icon on your desktop.

ATTENTION •

If you are logging on for the first time, use the following logon credentials. Login Name: administrator Password: password Domain Name: Classic Server Security These credentials can be used until the individual user logins are created using the User Management.

•

Ensure that you change the administrator password after logging on for the first time.

2

Type the Login Name.

3

Type the Password.

4

Select the Domain Name.

5

Click Login. The FDM Server Management dialog box appears, displaying the Network Configurator option by default.

ATTENTION Only a user with Administrator privileges can make changes to the configuration in the FDM Server Management Tool. All other users have only ‘read only’ access by default, to view the information. 6

R430 May 2012

After performing the necessary task, click Exit to close the FDM Server Management screen. Field Device Manager - R430 User's Guide Honeywell

41

1. Introduction to FDM R430 1.5. Getting started with FDM

ATTENTION If the Single Sign On is enabled, then the login screen does not appear.

Changing password It is recommended to change the default password after first logon to the FDM system. ATTENTION •

Only a user with the Administrator privileges can change the password for other users.

•

Login credentials for the FDM Client and FDM Server Management Tool are the same.

To change your password, perform the following steps. Step 1

Action Log on to FDM Client. The Field Device Manager window appears.

2

Choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

3

Select an appropriate user, based on your roles and privileges.

4

In the User Manager pane, click Edit User. The Edit User pane appears.

5

Type the existing password in Old Password.

6

Type the New Password.

7

To confirm your password, retype your new password in Confirm New Password.

8

Click Save. FDM validates your old password and checks if the new password entered in New Password and Confirm New Password boxes match. If the details are accurate, FDM updates your new password in the database.

42

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

Stopping the FDM Server The server must be stopped to add, edit, or delete network configuration, and to update the licensing information. The Add New, Edit and Delete buttons in the Network Configurator page are enabled, only when the server is not running (stopped). But, the View Details button is always enabled if you start/stop the server. To stop the FDM Server, perform the following steps. Step

R430 May 2012

Action

1

Log on to the FDM Server Management Tool. If the server is running, the button under Server Control in the left pane appears in green, with the label CLICK TO STOP displayed on it. This indicates that the server is running currently.

2

Click the CLICK TO STOP to stop the server.

3

Type the reason for service status change and click OK. The FDM Server Management dialog box appears prompting you to change the status of the service. It also prompts you to inactivate the configured and loaded FDM Gateway(s) in Control Builder.

4

Click Yes to confirm the operation.

Field Device Manager - R430 User's Guide Honeywell

43

1. Introduction to FDM R430 1.5. Getting started with FDM

Restarting the FDM Server To restart the FDM Server, perform the following steps. Step

Action

1

Log on to the FDM Server Management Tool.

2

If the server is running, the button under Server Control in the left pane appears in yellow, with the label CLICK TO START displayed on it.

ATTENTION When the server is running, you can only view details of the network configuration. 3

Click CLICK TO START icon under Server Control to restart the server.

4

Type the reason for service status change and click OK. The FDM Server Management dialog box appears, prompting you to change the status of the service.

44

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

Step 5

Action Click Yes to proceed with the operation. The server is started and the button under Server Control in the left pane displays CLICK TO STOP and appears in Green.

Updating FDM license Most features in FDM are licensed. You can access only those features for which you possess a valid license. For instance, if you do not have a license for Offline Configuration, you cannot access the Offline Configuration feature. The Server Management Tool provides the functionality to manage licensing for FDM. Using the Licensing option, you can view or update licensing for various features of FDM. ATTENTION After installing FDM, you must first update the license to perform other operations in the FDM Server Management Tool and the FDM Client.

To update the licenses, perform the following steps. Step 1

Action Log on to the FDM Server Management Tool.

ATTENTION Ensure that the server is in the stop mode.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

45

1. Introduction to FDM R430 1.5. Getting started with FDM

Step

Action

2

Click the Licensing icon in the left pane of FDM Server Management dialog box. The list of features and their licensing information are displayed in the right pane of FDM Server Management dialog box. The licensing information is listed with the following details. • Option: It indicates the name of the feature pertaining to the software. • Status: It refers to the present status of the license for a feature. It is either

Licensed or Not Licensed. Value(s): It specifies the number of licenses provided for each feature. For some of the features, the values can be either License Enabled or Disabled. 3

Click Select to browse the folder where the license file is present and choose the file.

4

Click Open in the Select a License File dialog box. The License updated confirmation message appears.

5

Click OK to close the confirmation message. The path appears for the license file with the .xml extension and license information is updated and appears under Licensing Information.

6

Click Exit to close the FDM Server Management dialog box.

Logging on to the FDM Client If FDM Client and Server reside on the same computer, perform the following steps to log on to the FDM Client. ATTENTION

46

•

If you are logging on for the first time, ensure that FDM is updated with the proper license file. To update the license, refer to section Updating FDM license.

•

If Single Sign On is enabled, then the logon screen does not appear.

•

If the Single Sign On is disabled, then client displays the logon screen. You must provide his username and password to log on to the FDM Client.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

Step 1

Action Choose Start > All Programs > Honeywell FDM > FDM Client. The Field Device Manager login window appears.

TIP You can also click the FDM Client icon on your desktop. 2

Type the name of the Server or select the server from the drop-down list.

TIP If you are connecting to the server for the first time, enter the server name. If FDM connects to the specified FDM Server successfully, then the server name is cached and is available for selection from the drop-down list during subsequent logins. Note: If both server and client are running on the same computer, you can use LOCALHOST as server name in the Server box. 3

Click Login. The Field Device Manager login window appears.

ATTENTION •

If you are logging on to the client for the first time enter the following credentials. −

Login Name: administrator

−

Password: password

−

Domain Name: Classic Server Security These credentials can be used until the individual user logins are created using the User Management.

•

R430 May 2012

Ensure that you change the administrator password after logging on for the first time.

4

Type the Username.

5

Type the Password.

6

Select the name of the domain from Domain.

Field Device Manager - R430 User's Guide Honeywell

47

1. Introduction to FDM R430 1.5. Getting started with FDM

Step

Action

ATTENTION

7

•

If you are trying to logon as an FDM user, select Classic Server Security from the drop-down list.

•

If you want to use Windows credentials, select the appropriate domain and type the password. For more information, refer to section Windows Security.

Click Login to validate your login credentials. The Field Device Manager window appears.

ATTENTION FDM R430 supports passwords only greater than or equal to 8 characters. Therefore, change your password length to 8 characters or more. For more information, refer to section Changing password. The Network View tree under the Online View group is displayed by default. The name of the server you are currently connected to appears in the title bar. The left pane of the FDM Client contains two groups. • Online View • Offline View

8

After completing the required tasks, choose FDM > Exit to close the FDM Client. Or Click the Close button at the upper-right corner of the window to close the application. A confirmation message appears.

9

48

Click Yes to close the FDM Client.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

If the FDM Client is installed on a different computer (remote), the user logged on must be a member of the FDMAccessGroup in both the systems (FDM Client and FDM Server). ATTENTION 1.

Any Windows user or Windows group user who wants to access the FDM Server from a FDM Client must be added to the FDMAccessGroup in both FDM Server and FDM Client computers.

2.

If the Windows user has logged on to the FDM Client computer as FDMMngr, the user need not be added to the FDMAccessGroup.

3.

The user who is currently logged on to Windows must be a part of an FDM user group. For more information, refer to section Roles and Privileges.

To add a user to the FDMAccessGroup, perform the following steps. Step 1

Action On the client computer, right-click Computer and click Manage. The Server Manager dialog box appears.

2

In the Server Manager tree, expand Configuration > Local Users and Groups > Groups. The list of groups appears in the right pane.

3

Right-click FDMAccessGroup and click Add to Group.

4

Add the logged on user to this group and click OK.

5

Repeat the above steps 1 through 4 in the FDM Server computer. You can logon to the FDM Server from a remote FDM Client.

REFERENCE - INTERNAL In case of any problem during remote access, refer to the FDM R430 Troubleshooting Guide.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

49

1. Introduction to FDM R430 1.5. Getting started with FDM

Logging on to the FDT Comm Console To logon to the FDM Comm Console which is installed along with RCI, perform the following steps. ATTENTION •

If you are logging on for the first time, ensure that FDM is updated with the proper license file. To update the license, refer to section Updating FDM license.

•

If Single Sign On is enabled, then the logon screen does not appear.

•

If the Single Sign On is disabled, then FDT Comm Console displays the logon screen. You must provide his username and password to log on to the FDT Comm Console.

Step 1

Action Choose Start > All Programs > Honeywell FDM > FDT Comm Console. The Field Device Manager login window appears.

TIP You can also click the FDT Comm Console icon on your desktop. 2

Type the name of the Server or select the server from the drop-down list.

TIP If you are connecting to the server for the first time, enter the server name. If FDM connects to the specified FDM Server successfully, then the server name is cached and is available for selection from the drop-down list during subsequent logins. Note: If both server and client are running on the same computer, you can use LOCALHOST as server name in the Server box. 3

Click Login. The Field Device Manager login window appears.

50

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

1 Introduction to FDM R430 1.5 Getting started with FDM

Step

Action

ATTENTION •

If you are logging on to the FDT Comm Console for the first time, enter the following credentials. −

Login Name: administrator

−

Password: password

−

Domain Name: Classic Server Security These credentials can be used until the individual user logins are created using the User Management.

•

Ensure that you change the administrator password after logging on for the first time.

4

Type the Username.

5

Type the Password.

6

Select the name of the domain from Domain.

ATTENTION

7

•

If you are trying to logon as an FDM user, select Classic Server Security from the drop-down list.

•

If you want to use Windows credentials, select the appropriate domain and type the password. For more information, refer to section Windows Security.

Click Login to validate your login credentials. The Field Device Manager – FDT Comm Console window appears.

ATTENTION FDM R430 supports passwords only greater than or equal to 8 characters. Therefore, change your password length to 8 characters or more. For more information, refer to section Changing password.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

51

1. Introduction to FDM R430 1.5. Getting started with FDM

Step

Action The Network View tree under the Online View group is displayed by default. The name of the server you are currently connected to appears in the title bar. The left pane of the FDT Comm Console contains two groups. • Online View • Offline View

8

After completing the required tasks, choose FDM > Exit to close the FDT Comm Console. Or Click the Close button at the upper-right corner of the window to close the application. A confirmation message appears.

9

52

Click Yes to close the FDT Comm Console.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2. User Management 2.1

Overview of FDM role-based User Management FDM provides a robust role-based user management. There are two user verification mechanisms called FDM Classic Server Security and Windows Security. FDM supports adding an existing Windows user group to FDM and assigning specific roles to it.

FDM Classic Server Security FDM user management allows creation of users with in-built authentication mechanism called FDM Classic Server Security. The user credentials such as user information, password, and so on are stored in the FDM Server Database. At the time of login, the user credentials provided by the user are authenticated by the FDM Server. These users cannot use the Single Sign On feature.

Windows Security If the Windows Security option is selected, FDM does not maintain the password information in its database. During login, FDM uses Windows security to authenticate the user. FDM also supports the Windows groups as this simplifies the task of associating a large number of users to a specific role in FDM. The Single Sign On feature is supported for all the users who choose Windows Security. FDM supports Windows security in: •

A Windows work group.

•

A Windows domain.

Support for Windows Groups FDM supports adding an existing Windows user group to FDM and assigning specific roles to it. The FDM Group Manager is used for managing FDM groups. Instead of associating one user to a specific FDM role, an administrator can create a Windows group and associate it with a specific role in FDM. This provides the flexibility to the administrator to associate any number of windows users to that group. After a group is associated with a role, all the users associated with that group inherit the group’s privileges. FDM creates the following default groups during installation. •

R430 May 2012

FDM Administrators – User added to this group has all the privileges of the FDM administrator role.

Field Device Manager - R430 User's Guide Honeywell

53

2. User Management 2.1. Overview of FDM role-based User Management

•

FDM Supervisors – User added to this group has all the privileges of the FDM supervisor role.

•

FDM Engineers – User added to this group has all the privileges of the FDM engineer role.

•

FDM Operators – User added to this group has all the privileges of the FDM operator role.

•

FDM Access Group – This group is created on all the systems where FDM components are installed. FDM Access Group is not associated with any of the FDM roles. This group is associated with certain Windows privileges which are needed to start FDM Client. Any FDM Windows user who wants to start FDM Client must belong to this group.

The user can add new Windows groups in FDM. To manage groups in FDM, refer to section Managing groups.

Roles and Privileges FDM provides robust role-based user management. FDM has a set of privileges that you can possess, and these privileges are grouped to form the roles. A role is a set of privileges with a common name. A user or a group can get the privileges by associating to one of the roles. FDM has the following predefined roles. •

Administrator

•

Engineer

•

Supervisor

•

Operator

In addition to these roles, users can create their own roles based on organization needs. You can also assign additional privileges to the predefined roles. However, you cannot remove the default privileges associated with the predefined roles.

Administrator access privileges Administrators have full access and privileges to all the functions of FDM. They are mainly responsible for managing users, processing user requests, and updating user data.

54

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.1 Overview of FDM role-based User Management

The following table lists the default privileges of the Administrator role. User Role Administrator

Privileges • Access FDM Tag Builder Tool • FDM Settings • Attach/Detach/Upload Documents • Create/Edit/Rename/Delete Display Filter • Create/Edit/Delete Device Filters • Download/BulkDownload Offline Configuration • Create/Edit/Rename/Delete Offline Configuration • Lock/Unlock Device • Save/Delete History • Rename Node • Create/Delete Role • Delete Records • FDT Health Scan Settings • Modify Write Access for Process Active Devices • Bulk Operations • Create/Edit/Delete Device Filters • Create/Modify/Delete User • Execute Method • Import/Export • Delete Device from Disconnected Nodes list. • Upgrade License • FDM Server start/stop • Add/Delete DD/DTM • Change Network • Change Device State • Compare Configuration

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

55

2. User Management 2.1. Overview of FDM role-based User Management

User Role

Privileges • Create/Modify/Delete Group • Write Parameters • Build Network

ATTENTION Privileges for Administrators cannot be modified.

Supervisor access privileges Supervisors are provided with read and write permission to FDM. They are allowed to make changes in the database and to change the operational settings, as required. The following table lists the default privileges of the Supervisor role. User Role Supervisor

Privileges • Attach/Detach/Upload Documents • Create/Edit/Rename/Delete Display Filter • Download/Bulk Download Offline Configuration • Lock/Unlock Device • Execute Method • Delete Device from Disconnected Nodes list. • Change Device State • Compare Configuration • Write Parameters • Build Network

56

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.1 Overview of FDM role-based User Management

Engineer access privileges Engineer access enables the FDM user to change the values of certain parameters and other related settings, when necessary. The following table lists the default privileges of the Engineer role. User Role Engineer

Privileges • Access FDM TagBuilder Tool • Attach/Detach/Upload Documents • Create/Edit/Rename/Delete Display Filter • Download/BulkDownload Offline Configuration • Create/Edit/Rename/Delete Offline Configuration • Lock/Unlock Device • Save/Delete History • Rename Node • Bulk Operations • Execute Method • Delete Device from Disconnected Nodes list • FDM Server start/stop • Change Device State • Compare Configuration • Write Parameters • Build Network

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

57

2. User Management 2.2. Managing users

Operator access privileges Operators are provided with very limited access to change any configuration. They are assigned the privileges to monitor the status of the operations and respond to the alarms. The following table lists the default privileges of the Operator role. User Role

Privileges • Compare Configuration

Operator

• Build Network

2.2

Managing users FDM has a robust user management feature to prevent unauthorized access and ensure security of the system. It is classified into the following categories based on the type of authentication you choose. •

FDM Classic Server Security

•

Windows Security

Current User Info enables you to view the details of the current user who has logged on to FDM. To view current user details, choose View > Current User Info.

Adding a new user in Classic Server Security ATTENTION Only Administrator with Create/Modify/Delete user privilege can add a user.

To create a user with authentication type as FDM Classic Server Security and assign a role, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

58

Click Add New User. The Add User pane appears. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.2 Managing users

Step

Action

3

Type the Login Name.

4

Select Classic Server Security from Domain Name.

5

Type the Password.

6

Retype the password in Confirm Password.

7

Click User Information tab to add user details.

8

Type the First Name, Middle Name and the Last Name of the user in the corresponding fields.

9

Type other details like Mailing address, Email ID, Telephone, and so on.

ATTENTION Only the First Name field is mandatory on this tab. All other fields are optional. 10

Click the Role Information tab.

11

Select a role for the user from the drop-down list. Depending on the role you select, the default associated privileges for the selected role are enabled.

ATTENTION

12

R430 May 2012

•

The check boxes against the privileges associated with a role are selected by default and appear in Gray. To assign additional privileges to the user, select the check box against the privileges of your choice.

•

You cannot remove the default privileges assigned to a role.

•

While adding any new user as a role of Engineer or Administrator, the following message appears.

Click Save to save the user information.

Field Device Manager - R430 User's Guide Honeywell

59

2. User Management 2.2. Managing users

Adding a user in Windows Security A Windows user can be assigned to a FDM role in the following two ways. •

Associate a single Windows user to one of the roles in FDM.

•

Associate a Windows Group to a Role in FDM, and then add any number of Windows users to the Windows group using Windows user management tools.

To associate a single Windows user to one of the roles in FDM, perform any one of the following, as necessary. If you have a Windows Work Group, perform the following steps. Step

Action

1

Create a Windows user on the FDM Server.

2

Add this user to the FDMAccessGroup on the FDM Server.

3

Create the same user on all the systems where FDM Client and FDM RCI are installed. Ensure that the password is same as that of the user in the FDM Server.

4

Add this user to the FDMAccessGroup on all the systems.

If you have a Windows Domain, perform the following steps: Step

Action

1

Create a Windows user in the domain controller system.

2

Add the Windows domain user to the FDMAccessGroup on all the systems where FDM components (FDM Server, FDM Client, and FDM RCI) are installed.

ATTENTION FDMMngr user must be created in the domain controller system with the same password as everywhere used for enabling the users of domain controller to logon to FDM.

60

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.2 Managing users

To associate a single Windows user to one of the roles in FDM, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

Click Add New User. The Add User pane appears.

3

Type the Windows Login Name.

ATTENTION The Windows user password is considered automatically and you cannot edit the same. 4

Select the Domain from the drop-down list.

5

Repeat the steps 7 through 12 of Adding a new user in Classic Server Security.

TIP •

•

R430 May 2012

Click View Details button in the Server Management Tool to view the following details. −

Login Information

−

User Information

−

Role Information

Click Refresh to get the updated information from the system, if multiple users are performing user management tasks simultaneously.

Field Device Manager - R430 User's Guide Honeywell

61

2. User Management 2.2. Managing users

ATTENTION The installation of FDM creates a default Windows user by the name FDMMngr and adds it to FDM Administrators group and FDMAccessGroup on the Server system. FDMMngr is a local Windows user and it is present on all systems wherever FDM component is installed. If the password policy has changed, ensure that the password is changed with respect to new password policy in all FDM systems. Perform the following steps to change the password. •

On the FDM Server Start menu, right-click Computer and click Manage. The Server Manager dialog box appears.

•

In the Server Manager tree, expand Configuration > Local Users and Groups > Users.

•

In the right pane, right-click FDMMngr and then click Set Password.

To assign a Windows user to FDM by adding the user to one of the FDM groups, perform the following steps. Step 1

Action On the FDM Server Start menu, right-click Computer and click Manage. The Server Manager dialog box appears.

2

In the Server Manager tree, expand Configuration > Local Users and Groups > Groups. The list of groups appears in the right pane.

3

Right-click FDM Group and click Add to Group.

4

Add the Windows user to this group and click OK. For example, right-click the FDM Supervisors group and add the Windows user to this group. The user inherits all the privileges of the FDM Supervisors.

62

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.2 Managing users

Modifying user details ATTENTION •

Only users assigned with Create/Modify/Delete user privileges can modify the details of all users.

•

The users not assigned with Create/Modify/Delete user privileges can modify their own details on the Login Information and Role Information tabs.

To modify details of an existing user account, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

Select a user that you want to edit from the list of users..

3

Click Edit User to modify the information of the selected user. The Edit User pane appears.

4

Make the necessary changes to the user information under the Login Information tab.

ATTENTION

R430 May 2012

•

You can modify the password. However, you must not modify the Login Name.

•

You cannot modify the password of a Windows user.

•

Any modification in user information does not effect until you logon to the client again.

5

Click the User Information tab and make necessary changes to the user information, as required.

6

Click the Role Information tab and modify the user’s role and privileges, if required.

Field Device Manager - R430 User's Guide Honeywell

63

2. User Management 2.2. Managing users

Step

Action

ATTENTION You cannot modify the default privileges assigned to a role. FDM disables the check boxes corresponding to the default privileges. 7

Click Save to save the modifications to the user account.

Deleting a user ATTENTION Only Administrator with Create/Modify/Delete user privilege role can delete a user.

To delete an existing user account, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

Click the user record that you want to delete from the list of users displayed,

3

Click Delete User to delete the selected user account. A confirmation message appears.

4

Click Yes to confirm the delete operation.

5

Click Close.

ATTENTION FDM does not allow you to delete the default Administrator user.

64

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.3 Managing groups

2.3

Managing groups Overview Managing groups involves the following tasks. •

Adding a Windows Group and associating a Role

•

Modifying a Group

•

Editing roles and privileges of groups

•

Deleting groups

•

Viewing a group’s details

Prerequisite to add a group in FDM Only a valid Windows group can be added to the FDM. Any group that is associated to FDM must be assigned to the following policies. •

Access this computer from the network

•

Act as part of the operating system

•

Adjust memory quotas for a process

•

Bypass traverse checking

•

Log on as a batch job

•

Log on as a service

•

Log on locally

•

Replace a process level token

•

Take ownership of files or other objects ATTENTION These policies are set for All the default Windows groups created by FDM.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

65

2. User Management 2.3. Managing groups

To assign the policies, perform the following steps. Step 1

Action Choose Start > Administrative Tools > Local Security Policy. The Local Security Policy dialog box appears.

2

In the left pane, expand Local Policies and click User Rights Assignments. The list of policies appears in the right pane.

3

Right-click the policy and click Properties. The respective policy’s properties dialog box appears. Click Add Users or Groups to assign the group.

Adding a Windows group and associating a role ATTENTION Adding a group in FDM is assigning a valid Windows group to FDM, to make it a valid FDM group.

To add a Windows group to FDM, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

TIP You can also click the User Management icon under the FDM toolbar. 2

Click the Group Manager icon in the left pane. The Group Manager pane appears in which the default groups available in FDM are listed.

3

Click Add New to add new user group. The New Group pane appears.

66

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.3 Managing groups

Step 4

Action Type the Group Name and select the Domain name from drop-down list under New Windows Group tab. In case of Windows work group, the group must be created as local group in the FDM Server system and the FDM Server system name must be added as domain name.

ATTENTION •

The group name entered must be that of an existing Windows group. If you enter the name of a non existing group, an error message appears.

•

Local Groups are supported only if they are created on the FDM Server System and are part of FDM access group.

5

Click the Role Information tab.

6

Select the role from the drop-down list. For the role you select, the corresponding privileges are automatically selected.

ATTENTION If you want to give any additional privilege, select the corresponding check box in the Privileges list. 7

Click Save to associate the group.

ATTENTION After associating Windows Group to a particular role, all users belonging to the Windows group can logon to FDM system and they inherit the group’s role. You need not explicitly add the users to the database.

To add a domain group, perform the following steps. Step

R430 May 2012

Action

1

Create a Windows group in the domain controller system.

2

Add the Windows domain group to the FDMAccessGroup on all the systems where FDM components (FDM Server, FDM Client, and FDM RCI) are installed.

Field Device Manager - R430 User's Guide Honeywell

67

2. User Management 2.3. Managing groups

Step

Action

ATTENTION FDMMngr user must be created in the domain controller system with the same password as everywhere to enable groups of domain controller to work with FDM.

TIP Click View Details to view a group, its default privileges, and all the users associated with the particular role.

Editing roles and privileges of groups To edit roles and privileges of a group, perform the following steps. Step 1 2

Action Follow steps 1 and 2 of Adding a Windows group and associating a role. In the Group Manager pane, select the group that you want to modify and click Edit. The Edit Group pane appears.

68

3

Click the Role Information tab.

4

Select a new role, if you want to change the role.

5

Select new privileges, if you want to change the privileges.

6

Click Save to save the changes.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.3 Managing groups

Deleting groups Deleting a group in FDM is unassigning a Windows group from FDM. To delete a group in the FDM, perform the following steps. Step 1

Action Perform steps 1 and 2 of Adding a Windows group and associating a role. The Group Manager pane appears.

2

Select the group that you want to delete.

3

Click Delete. The confirmation message appears.

4

R430 May 2012

Click Yes to delete the group.

Field Device Manager - R430 User's Guide Honeywell

69

2. User Management 2.4. Managing roles

2.4

Managing roles Managing roles involves the following tasks. •

Adding a role

•

Modifying a role

•

Deleting a role

•

Viewing details of a role

Adding a role ATTENTION Only users assigned with the Administrator privileges can add a new role.

To add a new user role, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

Click the Role Manager icon in the left pane. The Role Manager pane appears in which list of available user roles are listed.

3

Click Add New Role to add details for a new user role. The following page appears.

70

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.4 Managing roles

Step

Action

The All Privileges list contains all the privileges that can be assigned to a user role. 4

Type the role name in Role.

5

Assign privileges to the new role, using the arrow buttons. • To assign all the available privileges to the user role, select the privileges

. All the privileges listed in All you want to add and then click Privileges are moved to Selected Privileges. • To assign some of the privileges, select the required privilege from All

Privileges and click privileges.

. Repeat this step to continue adding other

• To remove all the privileges from Selected Privileges and move them back

to All Privileges, select the privileges you want to remove and then click

.

• To remove some of the privileges from the Selected Privileges, select the

privilege that you want to move back to All Privileges, and then click

R430 May 2012

. Follow this step to remove other privileges.

Field Device Manager - R430 User's Guide Honeywell

71

2. User Management 2.4. Managing roles

Step 6

Action Click Save to save the new role. If you click Save, the new user role is listed in Role Manager.

TIP Click View Details to view a role and its default privileges.

Modifying a role ATTENTION •

Only users assigned with the Administrator privileges can modify an existing role.

•

Modifying a role affects all the users associated to that particular role. Hence, ensure that you change the role of the users that you do not want to be affected by the role modification.

To modify the existing role information, perform the following steps. Step 1

Action From the FDM Client, choose Tools > User Management. The User Manager pane appears, displaying the list of existing users and their roles in the right pane.

2

Click the Role Manager icon in the left pane. The Role Manager pane appears in which the list of roles available in FDM are listed.

3

From the list of roles, select a role that you want to edit and click Edit. The Edit Role pane appears. • The All Privileges list includes the privileges that are not assigned to the

selected role. • The Selected Privileges list includes those privileges that are currently

assigned to the selected role. 4

72

Use the arrow buttons to add or remove the privileges for the selected user role.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

2 User Management 2.4 Managing roles

Step

Action • To assign all the available privileges to the user role, select the privileges

. All the privileges listed in All you want to add and then click Privileges are moved to Selected Privileges. • To assign some of the privileges, select the required privilege from All

Privileges and click privileges.

. Repeat this step to continue adding other

• To remove all the privileges from Selected Privileges and move them back

to All Privileges, select the privileges you want to remove and then .

click

• To remove some of the privileges from the Selected Privileges, select the

privilege that you want to move back to All Privileges, and then click

. Follow this step to remove other privileges.

ATTENTION A user role must have at least one privilege. Hence, you cannot remove all the privileges from Selected Privileges. 5

Click Save to save the information.

ATTENTION

R430 May 2012

•

If you modify a role, all the affected users must have the modified role’s access privileges.

•

Any modification in Role information does not effect until the corresponding user logon to the client again.

Field Device Manager - R430 User's Guide Honeywell

73

2. User Management 2.4. Managing roles

Deleting a role ATTENTION •

Users with the Administrator privileges can delete an existing role.

•

FDM does not allow you to delete a role, if users are associated to the role.

To delete an existing user role, perform the following steps. Step 1

Action Perform steps 1 and 2 of Adding a role. The Role Manager pane appears.

2

From the list of roles, select the role that you want to delete.

3

Click Delete Role to delete the selected role. A confirmation message appears.

74

4

Click Yes to confirm the delete operation. FDM deletes the role, provided you have dissociated all the users associated to the role. If there are users associated to the role, the following dialog box appears. Click Yes to continue.

5

Click Close to close the Role Manager pane.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3. Network configuration 3.1

Overview Based on the field devices and interface used for communication with FDM, you need to identify and configure the appropriate network. FDM supports the following types of network using FDM Server Management Tool. •

RS-232 HART Modem: FDM uses the RS-232 HART Modem to communicate with HART devices using the serial port. You need to configure FDM to send and receive data through the HART communication port.

•

Honeywell HART DE Modem: The Honeywell HART DE Modem provides the network communication interface to HART devices. This modem supports both, HART protocol and Honeywell Proprietary DE (Digital Enhanced) protocol.

•

RS-485 HART Multiplexer: Using the RS- 485 HART Multiplexer, FDM can communicate to multiple HART devices in the field. Multiplexers transmit signals over a single communication line. HART Multiplexers can be used for communicating with multiple HART devices, enabling remote configuration, monitoring, and troubleshooting of those devices. A single HART Multiplexer network can have thirty-two multiplexers and is connected to many devices.

•

Honeywell Experion PKS: Honeywell Experion PKS network in server management tool helps you to configure, monitor and perform device specific operations on HART/FF devices connected to Experion system. Following are the options that exist for configuring a network against Honeywell Experion PKS.

•

R430 May 2012

−

Honeywell Experion as a Non-Redundant configuration

−

Honeywell Experion as a Redundant Server configuration

−

Honeywell Experion integrated Safety network with Universal Safe Modules configuration.

COMM DTM Interface: FDM supports the following using FDT Comm Console. −

HART network

−

PROFIBUS network

−

HART over PROFIBUS network Field Device Manager - R430 User's Guide Honeywell

75

3. Network configuration 3.2. Configuring FDM for an RS-232 HART modem

•

3.2

Safety Network with Universal Safe Modules: This enables you to configure HART channels of Standalone Safety network with Universal Safe Modules when SM is integrated with third party DCS.

Configuring FDM for an RS-232 HART modem Background The RS-232 HART modem is used for configuring a single device at a time. It can also be configured for multiple devices, if the modem functions with the multi-drop feature. FDM also supports the usage of USB HART modems. ATTENTION •

For an RS-232 HART Modem configuration, it is imperative that the Use FIFO buffers (requires 16650 compatible UART) check box is cleared in the Advanced Settings dialog box while configuring the COM Port settings.

•

For more details on configuring the COM port setting for an RS-232 HART Modem, refer to section Configuring RS-232 HART modem network .

Configuring COM port setting for RS-232 HART Modem Before configuring the FDM for an RS-232 HART Modem, you need to ensure that the COM port settings are configured correctly. Perform the following steps to configure the COM port settings. Step 1

Action On the FDM Server Start menu, right-click Computer and click Properties. The System dialog box appears.

2

Click Advanced system settings under Tasks. The System Properties dialog box appears.

3

Click the Hardware tab.

4

Click Device Manager. The Device Manager dialog box appears.

76

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.2 Configuring FDM for an RS-232 HART modem

Step

Action

5

In the Device Manager network tree, choose Ports (COM & LPT) > Communication Port. Right-click Communication Port to select Properties. The Communication Port Properties dialog box appears.

6

Click the Port Settings tab.

7

Click Advanced to view the Advanced Settings for the communication port. The Advanced Settings dialog box appears.

8

By default, the Use FIFO buffers option is checked, clear this option and click OK.

ATTENTION It is imperative to clear the Use FIFO buffers (requires 16550 compatible UART) select check box for the RS-232 HART Modem. However, this setting does not make a difference for RS-485 HART Multiplexer and Honeywell HART DE Modem. You can leave it selected or cleared. 9

R430 May 2012

Restart the computer for the changes to take effect.

Field Device Manager - R430 User's Guide Honeywell

77

3. Network configuration 3.2. Configuring FDM for an RS-232 HART modem

Configuring RS-232 HART modem network After the COM port settings are configured, you can configure the RS-232 HART modem network communication interface for FDM, using the Server Management Tool. To configure FDM for an RS-232 HART Modem, perform the following steps. Step

Action

1

On the FDM Server computer, choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

ATTENTION The Add New, Edit and Delete buttons are enabled, only when the server is stopped. 5

Choose the network type as RS-232 HART Modem from Network Type.

6

Type the interface name (a unique name) in Network Interface Name.

7

Type the name of the server in RCI Server Name. The configured network is connected to the RCI Server.

8

Select the COM port from COM Port drop-down list. FDM R430 supports COM ports 1 to 255.

9

Specify the retry count ranging between 0 and 9 in Retry Count, as required.

ATTENTION For the RS-232 HART Modem, the BAUD rate is 1200 bps, which is predefined. You are not allowed to modify the BAUD rate. 78

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.3 Configuring FDM for a Honeywell HART DE modem

Step 10

Action Click OK to save the configuration.

ATTENTION •

If you click OK without entering details for all the mandatory fields, the

•

3.3

icon appears against the blank fields.

By default, FDM populates RCI Server Name with LOCALHOST. If you leave this unchanged, FDM considers the RCI Server to be the local host and displays an appropriate message to that effect.

Configuring FDM for a Honeywell HART DE modem To configure FDM for a Honeywell HART DE Modem, perform the following steps. Step

Action

1

On the FDM Server, choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

ATTENTION The Add New, Edit and Delete buttons are enabled, only when the server is stopped.

R430 May 2012

5

Choose the network type as Honeywell HART DE Modem from Network Type drop-down list.

6

Type the name of the interface, in Network Interface Name box. Field Device Manager - R430 User's Guide Honeywell

79

3. Network configuration 3.4. Configuring FDM for an RS-485 HART multiplexer

Step 7

Action Type the name of the RCI server in RCI Server Name box. The configured network is connected to the RCI Server.

8

Select the COM port from COM Port drop-down list. FDM R430 supports COM ports 1 to 255.

ATTENTION Honeywell HART DE Modem supports a BAUD rate of 9600 bps, which is predefined. You cannot manually enter/edit this value. 9

Specify the retry count ranging between 0 and 9 in Retry Count box.

10

Enter the poll address of the modem ranging between 0 and 15 in the Start Poll Address box.

11

Enter the poll address (any value between 0 and 15) in the End Poll Address. The entered range reflects the poll addresses that are scanned for detecting the HART devices in the network.

ATTENTION The value entered in End Poll Address must be greater than the value entered in Start Poll Address. 12

Click OK to save the configuration.

ATTENTION •

If you click OK without entering details for all mandatory fields, the

•

80

icon appears against the blank fields.

By default, FDM populates RCI Server Name with LOCALHOST. If you leave this unchanged, FDM considers the RCI Server to be the local host and displays an appropriate message to that effect.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.4 Configuring FDM for an RS-485 HART multiplexer

3.4

Configuring FDM for an RS-485 HART multiplexer To configure FDM for an RS-485 HART Multiplexer, perform the following steps. Step

Action

1

On the FDM Server, choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

ATTENTION The Add New, Edit and Delete buttons are enabled, only when the server is stopped. 5

Choose the network type as RS-485 HART Multiplexer from Network Type drop-down list.

6

Type the interface name (a unique name) in Network Interface Name.

7

Type the name of the server in the RCI Server Name. The configured network is connected to the RCI Server.

8

Select the Enable Mux Monitoring check box if you want the Mux Monitoring feature to be enabled for this particular network configuration.

ATTENTION The Enable Mux Monitoring check box is enabled only if you have updated the Maximum Number of Mux Monitoring Network supported license. If not, FDM disables this check box. 9

R430 May 2012

Select the COM port where the multiplexer is connected, from COM Port. FDM R430 supports COM ports 1 to 255. Field Device Manager - R430 User's Guide Honeywell

81

3. Network configuration 3.5. Configuring FDM for Honeywell Experion

Step 10

Action Select the BAUD Rate.

ATTENTION The BAUD rate for RS-485 HART Multiplexer is 9600 and 19200. 11

Enter the poll address of the multiplexer ranging between 0 and 127 in Start Poll Address.

12

Enter the poll address (any value between 0 and 127) in End Poll Address. The entered range reflects the poll addresses that are scanned for detecting the multiplexers in the network.

ATTENTION

13

•

Ensure that the value you enter in End Poll Address is greater than the value you enter in Start Poll Address.

•

The MTL network does not support poll address 0.

•

To achieve optimum performance, it is recommended that the poll address range closely matches the actual addresses to which multiplexers are configured on the network.

Click OK to save the configuration.

ATTENTION •

If you click OK without entering details for all the mandatory fields, the icon appears against the blank fields. Enter the appropriate data for all the mandatory fields.

•

By default, FDM populates RCI Server Name with LOCALHOST. If you leave this unchanged, FDM considers the RCI Server to be the local host and displays an appropriate message to that effect.

REFERENCE – INTERNAL For additional details on Experion Software Multiplexers, refer to the HART I/O Implementation Guide in Experion documentation.

82

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.5 Configuring FDM for Honeywell Experion

3.5

Configuring FDM for Honeywell Experion To configure FDM for Honeywell Experion as a non redundant configuration, perform the following steps. Step

Action

1

Choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

5

R430 May 2012

In the Network Type drop-down list, click Honeywell Experion PKS.

Field Device Manager - R430 User's Guide Honeywell

83

3. Network configuration 3.5. Configuring FDM for Honeywell Experion

Step

Action

6

Under Redundancy, click Non Redundant.

7

Type the name of the server in RCI Server Name. This is the system in which the Experion server resides.

ATTENTION The COM Port, Start Poll Address, BAUD Rate, End Poll Address and Retry Count fields are not applicable to the Honeywell Experion Network Type configuration. Hence, FDM disables these fields. 8

Click OK to save the configuration.

ATTENTION •

If you click OK without entering details for all the mandatory fields, the

84

icon appears against the blank fields.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.5 Configuring FDM for Honeywell Experion

Step

Action •

By default, FDM populates RCI Server Name with LOCALHOST. If you leave this unchanged, FDM considers the local host as the RCI Server. If the Experion/RCI server is not found on the system, the following message appears.

−

Click Yes, if the network interface name matches with the alias name of the RCI Server. Or

−

Click No, if you want to modify the RCI Server Name/Network Interface Name (Alias Name).

ATTENTION If you add a Honeywell Experion PKS network, you cannot add other network communication interfaces (RS-232 HART Modem, Honeywell HART DE Modem, and RS-485 HART Multiplexer) on the same computer. A message appears to remove all the existing networks when you try to add a Honeywell Experion PKS.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

85

3. Network configuration 3.5. Configuring FDM for Honeywell Experion

To configure FDM for Honeywell Experion, as a redundant configuration, perform the following steps. Step

Action

1

Choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

5

In the Network Type drop-down list, click Honeywell Experion PKS.

6

Under Redundancy, click Redundant. The Primary Server and Secondary Server fields appear, instead of RCI Server Name.

86

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.5 Configuring FDM for Honeywell Experion

Step

7

Action

Type the name for the primary server in Primary Server box. This is the system in which the Primary Experion server resides.

ATTENTION The COM Port, Start Poll Address, BAUD Rate, End Poll Address, and Retry Count fields are not applicable to the Honeywell Experion PKS Network Type configuration (non-redundant and redundant). Hence, FDM disables these fields. 8

Type the name for the secondary server in Secondary Server box. This is the system in which the Secondary Experion server resides.

9

R430 May 2012

Click OK to save the configuration.

Field Device Manager - R430 User's Guide Honeywell

87

3. Network configuration 3.5. Configuring FDM for Honeywell Experion

Step

Action

ATTENTION •

If you click OK without entering details for all mandatory fields, the icon appears against the blank fields. Enter the appropriate details for all mandatory fields.

•

By default, FDM populates Primary Server with LOCALHOST and Secondary Server with NOT SELECTED. Ensure that you enter the Primary Server/Secondary Server names accurately. If the Experion/RCI server is not found on the system, the following message appears.

−

Click Yes, if you have entered the details of the Primary Server/Secondary Server accurately. Or

−

Click No, if you want to modify the Primary/Secondary Server Names or the Network Interface Name (Alias Name).

ATTENTION If the redundant system (Secondary) stops responding, the Primary takes over the FDM operations automatically.

88

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

3.6

Configuring FDM for Safety network Before using FDM with Universal Safe Modules connected HART devices, it is recommended that all SM connected devices and strategies to be commissioned first. After commissioning, the configuration is imported to FDM through a Safety Builder export file. Then, Safety Network is configured using the FDM Server Management tool. This Safety Network configuration can be one of the following types. •

Experion integrated Safety Network configuration – when Experion is present

•

Standalone Safety Network configuration – when Experion is not present

Prerequisite Ensure that Safety Builder configuration data is exported from Safety Builder in XML format. This file is referred as Safety Builder Export File. REFERENCE - EXTERNAL For more information about Safety Manager network configuration in Safety Builder and exporting Safety Builder configuration data from Safety Builder, refer to Safety Builder Users Guide.

Importing Safety Builder Export file ATTENTION

R430 May 2012

•

You can import only one SB Export file per FDM Server. Hence, you must plan the configuration accordingly in Safety Builder.

•

The SB Export file generated from Safety Builder can have a combination of Standalone and Experion integrated Safety networks. Hence, you can import this file and configure both Standalone and Experion integrated Safety networks without reimporting the file again.

•

Ensure to import SB Export file before you start with Safety Network configuration.

Field Device Manager - R430 User's Guide Honeywell

89

3. Network configuration 3.6. Configuring FDM for Safety network

To import the Safety Builder Export file, perform the following steps. Step

Action

1

On the FDM Server computer, choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

3

Click Import Resource. The following page appears.

4

Under Add Resource, click Safety Builder Export File from the drop-down list and then click Browse. The Open dialog box appears.

90

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step

Action

ATTENTION

5

•

You can add SB Export file from any system within the network. It is not necessary that you must add it from the FDM server.

•

Importing resource operation may modify the network(s) configuration. Hence, ensure that there are no networks operations are in progress before you import resource when FDM Server is running.

Select the SB Export file and then click Open. The Reason for Resource Update dialog box appears.

6

Type the reason for resource update and then click OK. The message appears displaying resource is added to the database successfully. And also, added resource is listed under Available Resources.

ATTENTION Safety Builder (SB) is case-sensitive for tag names (SM/IOTA/Channel). For example, consider two tag names, “Test” and “test”. Here, SB considers the both the tag names as different and FDM considers them as same tag names. Hence, tag conflict occurs. When such SB Export file is imported to FDM, the second tag is renamed to “_Conflict” when it appears in FDM Client. Perform the following to avoid tag conflicts. •

Rename the tag names in SB.

•

Re-export the tags in SB using SB Export file.

•

Re-import the updated SB Export file in FDM Server database using Online Update Tool.

Configuring FDM for Experion integrated Safety network To configure FDM for Experion integrated Safety network, perform the following steps.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

91

3. Network configuration 3.6. Configuring FDM for Safety network

Step

Action

1

Choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

5

92

In the Network Type drop-down list, click Honeywell Experion PKS.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step 6

Action Select Safety Manager with Universal Safe Modules Present check box. The Enable Alarm Monitoring for Safety Manager option is enabled.

ATTENTION When the resource file is not imported, SMs are not available to configure the Experion integrated Safety network and Safety Manager with Universal Modules Present checkbox is dimmed. In this case, if you try to add an Experion integrated Safety network, icon appears. However, if you proceed with the Experion integrated Safety network configuration, only Experion network is configured. 7

If you want to monitor alarms for devices, select Enable Alarm Monitoring for Safety Manager.

ATTENTION The Enable Alarm Monitoring for Safety Manager check box is enabled only if there is mux monitoring license available. 8

Type the name of the RCI server in RCI Server Name. This is the system in which the Experion server resides.

ATTENTION The COM Port, Start Poll Address, BAUD Rate, End Poll Address and Retry Count fields are not applicable to the Honeywell Experion network type configuration. Hence, FDM disables these fields. 9

Click OK to save the configuration.

ATTENTION •

If you click OK without entering details for all the mandatory fields, the

R430 May 2012

icon appears against the blank fields.

Field Device Manager - R430 User's Guide Honeywell

93

3. Network configuration 3.6. Configuring FDM for Safety network

Step

Action •

•

By default, FDM populates RCI Server Name with LOCALHOST. If you leave this unchanged, FDM considers the local host as the RCI Server. If the Experion/RCI server is not found on the system, the following message appears.

−

Click Yes, if the network interface name matches with the alias name of the RCI Server. Or

−

Click No, if you want to modify the RCI Server Name/Network Interface Name (Alias Name).

If you add a Honeywell Experion PKS network, you cannot add other network communication interfaces (RS-232 HART Modem, Honeywell HART DE Modem, and RS-485 HART Multiplexer) on the same computer. A message appears to remove all the existing networks when you try to add a Honeywell Experion PKS.

Configuring FDM for Standalone Safety network To configure FDM for Standalone Safety network, perform the following steps. Step

Action

1

Choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

94

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step

Action

ATTENTION Ensure that the server is in the stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

5

In the Network Type drop-down list, click Safety Network with Universal Safe Modules.

ATTENTION You can group the SMs under different Standalone Safety networks in the same or different RCIs. This option helps you to distribute the SMs across Standalone Safety networks.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

95

3. Network configuration 3.6. Configuring FDM for Safety network

Step 6

Action Click Associate Safety Managers. The Safety Network Configuration dialog box appears.

7

To associate Safety Managers from export file, • Select a SM from the Available list. • Click > to move it to the Selected list. Then, selected SM is configured to

the particular network. • To move all SMs to the Selected list, click the >> button. Then, selected

SMs are configured to the particular network. 96

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step

Action The selected SM, IOTA and HART channels are displayed under Selected Safety Manager Hierarchy.

8

In the Safety Network Configuration dialog box, click Save and Close. In FDM Server Management dialog box, the Configuration Status displays as Complete that indicates Standalone Safety network configuration is completed.

9

Type the name of the RCI server in RCI Server Name. The configured network is connected to the RCI Server.

ATTENTION The COM Port, Start Poll Address, BAUD Rate, End Poll Address and Retry Count fields are not applicable to the Safety Network with Universal Safe Modules Network Type configuration. Hence, FDM disables these fields. 10

Click OK to save the configuration. The following message appears if any other network is configured on an Experion Server computer.

11

Click OK to configure the network on non-Experion Server computer.

ATTENTION •

If you click OK without entering details for all the mandatory fields in FDM Server Management dialog box, the appears against the blank fields.

•

R430 May 2012

icon

By default, FDM populates RCI Server Name with LOCALHOST. If you do not change this, FDM considers the local host as the RCI Server.

Field Device Manager - R430 User's Guide Honeywell

97

3. Network configuration 3.6. Configuring FDM for Safety network

Online update of network configuration After SB Export file is imported to FDM and Safety network is configured (as Integrated with Experion or as Standalone), in order to update the network information like adding/removing SM/IOTA/HART Channels to the already configured networks, Online update of network configuration can be used. Most of the changes that can be accommodated through this online update of network configuration are supported without stopping the FDM Server. To update (import) network configuration data to FDM, perform the following steps. Step

Action

1

Log on to the FDM Server Management Tool.

2

In FDM Server Management dialog box, click Import Resource.

3

In the right pane, under Add Resource, click Safety Builder Export File from the drop-down list and then click Browse. The Open dialog box appears.

ATTENTION You must provide the audit trail reason to update (import) the network configuration data to FDM. 4

Select the updated SB export file and then click Open. The Update Safety Network Configuration dialog box appears. The updated SB Export file is compared with the previously imported SB Export file and the differences are displayed under Preview Changes with their corresponding impact.

98

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step

Action

5

If you want to view the impact due to changes made in SB Export file, click the Impact link. The description of the impact is displayed under Impact Description. All the impacted networks are listed in the Impacted Networks list, and the network hierarchy is also displayed with the changes in the form of icons and tooltips for updated SM/IOTA/HART channels. The following icons are displayed in the summary grid view and Impacted Networks list. Icon

Description Network(s) would be updated automatically with edited SM(s), IOTA(s), and HART channel(s). These changes are reflected in FDM Client Network View once reconfiguration is successful. Network is not impacted with the changed SB export file. This is due to either the new Safety Builder Export file has insignificant changes or changes are available in other SMs which are not configured in the existing networks.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

99

3. Network configuration 3.6. Configuring FDM for Safety network

Step

Action You can still click Update button to update the new Safety Builder Export file into FDM Database. Network(s) would be collapsed. Perform Build network operation to view the new network configuration after reconfiguration is successful. Stop FDM Server to associate the newly added SM(s) to either Standalone Safety Network or Experion integrated with Safety Network as shown in the Impact Description. Displays if SM/IOTA/HART Channel is not changed. Displays if SM/IOTA/HART Channel is added. Displays if SM/IOTA/HART Channel is removed. Displays if SM/IOTA/HART Channel is edited.

6

Click Update to reconfigure the network. • If FDM Sever is not in running state, Update network configuration

operation updates the updated SB Export file into FDM database and the impacted network configuration appropriately. When FDM Server and FDM Client are started, after Build Network operation, changes are reflected in the FDM Client Network View. • If FDM Server is in running state, Update network configuration operation

updates the new network configuration in FDM database. And also, the changes are reflected in all FDM Clients. The following changes are visible in FDM Client (without restarting the FDM Server) due to network resource update. −

In case of both Experion integrated Safety network and Standalone Safety network, • If the impact on the network is only rename of SM/IOTA/HART tag,

the network in the Client is automatically updated with the new configuration.

ATTENTION When the device tags which are alarm monitored are renamed, the changes are not reflected in FDM Client automatically. For these changes to get reflected, inactivate the devices in Control Builder and do a build network at any level (Network/SM/IOTA) as appropriate. 100

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.6 Configuring FDM for Safety network

Step

Action

• If the impact on the network is add/removal of SM/IOTA/HART, the

corresponding impacted network is collapsed and build network operation should be performed only on the impacted network to view the updated network changes. −

If new SM controllers are added in the updated SB Export file which has no Experion association, stop the FDM server and click Edit option in the FDM Server Management Tool. It associates the newly added SMs to the existing network or to the new Standalone Safety network.

−

If there are new SMs added under a Honeywell Experion PKS which is already configured in the Server Management Tool, then the network collapses and the new SMs are reflected after the build network on the corresponding Safety Network. If the SMs are added under a new Honeywell Experion PKS, you must import the resource file, stop the FDM server and configure a new Honeywell Experion PKS with Safety Network.

ATTENTION Before you click Update button, ensure to verify the details under Preview Changes for the changes in an SB Export file and corresponding impacts. Since updating the resource might lead to change in network configuration, a warning message appears before updating SB export file. 7

Click Yes. The Update Network Summary dialog box appears. It displays the summary of the network name and reconfiguration status. Click the reconfiguration status link to view the status description.

REFERENCE – INTERNAL If the reconfiguration status displays any error for the updates, refer to FDM R430 Troubleshooting Guide. 8

R430 May 2012

Click OK.

Field Device Manager - R430 User's Guide Honeywell

101

3. Network configuration 3.6. Configuring FDM for Safety network

ATTENTION Sometimes, if you import the updated SB Export file, may not be able to view the direct impact on the network tree. This might be due to some specific changes on SM controller (For example, IP address changes).

Standard Operating Procedure for Online Update Step

102

Action

1

Add FDM Server block and Safety Managers in Safety Builder with recommended Physical and Logical view. For more information on how to add and configure the nodes in Safety Builder, refer to Safety Manager User’s Guide.

2

Assign HART enabled channels to Safety Mangers which you want to maintain using FDM in Safety Builder. Also configure those points in FLD’s of Safety Builder. For more information on how to assign HART channels and creating FLD in Safety Builder, refer to Safety Manager User’s Guide.

3

Compile the application in Safety Builder.

4

Once compilation is successful without any errors, export the xml file from Safety Builder.

5

Download the compiled application to Safety Manger.

6

Import the xml file generated from Safety Builder using “Import resource” option in Server Management Tool. For more information on how to import resource, refer to section Importing Safety Builder Export file in FDM R430 User’s Guide.

7

Configure the networks using Server Management Tool

8

Launch FDM Client and initiate build network on the configured network. Safety Mangers along with IOTAs and devices appears in online network view.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.7 Configuring Comm DTM network in FDM

3.7

Configuring Comm DTM network in FDM To configure the Comm DTM network in FDM, perform the following steps. Step

Action

1

On the FDM Server computer, choose Start > All Programs > Honeywell FDM > FDM Server Management Tool.

2

Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in stop mode. 3

In the left pane, click Network Configurator. The Network Configuration page appears.

4

Click Add New to add a new network. The Add Network page appears.

5

In the Network Type drop-down list, click COMM DTM Interface.

6

Type the unique interface name in Network Interface Name box.

7

Type the name of the server in the RCI Server Name.

8

Click OK to save the configuration.

ATTENTION Communication DTMs can be configured only in the RCI server computer.

TIP Click View Details to view the details of the configuration in the Server Management Tool.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

103

3. Network configuration 3.8. Editing a network configuration

3.8

Editing a network configuration To modify the details of an existing network configuration, perform the following steps. Step 1

Action Log on to FDM Server Management Tool. The FDM Server Management dialog box appears.

ATTENTION Ensure that the server is in the stop mode. 2

Click Network Configurator in the left pane. In the right pane, the list of network configuration appears.

3

Select the network from the list and then click Edit. The Edit Network pane appears.

4

Make the necessary changes to the network configuration in the Edit Network pane.

ATTENTION

5

•

While editing Safety Network with Universal Safe Modules network configuration, you can add/remove SM(s).

•

While editing Honeywell Experion PKS network configuration, you can update Network Interface Name.

Click OK to save the modifications done to the network configuration.

ATTENTION Even when the server is stopped, FDM RCI keeps running to store the network information. Consequently, if you have modified or deleted any of the networks configured on an RCI that is running, you must stop the RCI manually.

104

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

3 Network configuration 3.9 Deleting a network configuration

To stop the RCI manually when you delete all the networks on RCI, perform the following steps. Step

Action

1

Right-click Computer and click Manage.

2

On the client computer, right-click Computer and then click Manage. The Server Manager dialog box appears.

3

In the Server Manager tree, expand Configuration > Services. The list of services appears in the right pane.

4

Select FDM Remote Communication Interface in the right pane.

5

Click Stop the service under FDM Remote Communication Interface. The Service Control dialog box appears and displays status of the service.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

105

3. Network configuration 3.9. Deleting a network configuration

3.9

Deleting a network configuration ATTENTION If you delete the network configuration from the database, the devices are disconnected from the Network View.

To delete a network configuration from the database, perform the following steps. Step 1

Action Log on to the FDM Server Management Tool. The FDM Server Management dialog box appears.

2

Click the Network Configurator icon in the left pane. In the right pane, the list of configured networks appears in the Network Configuration page.

3

Select the network from the list and click Delete to remove the network configuration. A confirmation message appears.

106

4

Click Yes to proceed with the delete operation.

5

Click Exit on the FDM Server Management dialog box to close it.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4. FDM Operations 4.1

Overview of FDM Client interface FDM Client - Main window When you log on to the FDM Client after configuring the network, the main window appears, with tree views groups in the left pane. By default, the Online View group appears.

Click either the Online View or Offline View group to access the tabs under each group.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

107

4. FDM Operations 4.1. Overview of FDM Client interface

REFERENCE - INTERNAL •

For more information about Online View, refer to section Online view functions.

•

For more information about Offline View, refer to section Offline View functions.

Server Poll Status Indication The FDM Server polls all open clients that are connected to it at regular intervals to know its status. The status indicator on the FDM Client status bar shows the status of the polling. The following polling states appear on the FDM Client status bar. •

Online: This state indicates that the server is actively polling the client at regular intervals.

•

Polling Delay: This state indicates that the server has not polled the client within a specified interval. This usually indicates that the server is busy performing some other operation.

•

Polling Stopped: If the server does not poll the client within a time interval greater than a predefined maximum time interval, the status changes to Polling Stopped. This usually indicates that the server is busy, has stopped or terminated or that the server has stopped responding.

•

Polling Resumed: If the Server is temporarily busy, the status can show Polling Delay or Polling Stopped depending on the time interval that FDM Server has not polled the client. The moment Server resumes polling the client, the status changes to Polling Resumed and subsequently back to Online. ATTENTION The Polling Stopped status must not be construed as evidence that the FDM Server has stopped responding. In all possibility, the Server might be busy performing some operation. Refer to the FDM Troubleshooting Guide on how to determine whether the server has terminated or has stopped responding.

108

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.1 Overview of FDM Client interface

TIP Placing the mouse pointer over the status area gives a short description of the current poll status.

System notifications After you perform any operation in FDM Client/FDT Comm Console, the status of the operation appears in the System Notifications pane. It has Information, Error, and Warning tabs. Each tab displays Time Stamp, Entity, and Description for all operations. To view the System Notifications pane, choose View > System Notifications. To hide this pane, use the close icon [ ] in the System Notifications pane.

For each error, warning, and information tab, maximum 1000 rows are supported. If it exceeds 1000 rows, then the initial row is removed and at the end new row is added. You can right-click anywhere in the System Notifications pane and click Clear Row(s) to clear the contents of the window.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

109

4. FDM Operations 4.2. Online view functions

4.2

Online view functions Overview of Online View The Online View is used for configuring and viewing HART, and FF devices that are connected to FDM. The following are the two tabs in Online View in the left pane. •

Network View

•

Device State View

Network View The Network View tab group lists devices by network and RCI Interface name. For HART, FF, PROFIBUS, and Standalone Safety network, the Network View list displays complete hierarchy that includes FDM Server, RCI Interface name, FIM, links, Communication DTMs, Gateway DTMs, IO DTMs, SM controllers, IOTAs, HART channels connected to IOTAs, and all the field devices belonging to the connected server. For Experion integrated Safety network configuration, the Network View list displays complete hierarchy that includes FDM Server, RCI Interface name, and Process and Safety network groups. Under Process network group, the Network View displays the Experion Controllers/IOs/Devices like C300, FIM, links connected to Experion server. Under Safety network group, the Network View displays the SM controllers, IOTAs, and HART channels connected to IOTAs. The following figure displays the Network View for Experion integrated Safety network configuration.

110

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.2 Online view functions

TIP When Redundant Experion network is configured, the RCI interface name appears as Primary Server’s name in the Network View. If Primary Server is stops/fails, the RCI Interface name appears as Secondary Server’s name.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

111

4. FDM Operations 4.2. Online view functions

Using Network View tab, you can configure the device, view device history, compare device configuration for DD devices, rename a device, download offline configuration to a device, and explicitly lock a device. ATTENTION You cannot rename an Experion device until it is in disconnected state. If Experion tag is renamed when it is in disconnected state and if the device is connected back it accepts the Experion tag not the renamed tag.

The device health is displayed when the device is discovered for the first time during build network. A healthy device is indicated in green and if a device is found unhealthy, it is indicated in red. The unhealthy devices are listed under Unhealthy devices in the Network View list. If a node (Device\Mux\Controller\IO\IOLINK\FIM2\FIM4\FIM8\FFLINKS\SM Controller\IOTA) is disconnected from the network, then node is moved to the Disconnected Nodes list in the Network View tree. You can view history, rename the device tag, and delete the device tag from the Disconnected Nodes list. The following icons are displayed in the Network View tree. Icon

Description FDM Server Node Remote Communication Interface Hardware Multiplexer Network Experion Network Honeywell HART/DE Modem HART Modem C200/C200E Controller Module

112

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.2 Online view functions

Icon

Description 1756 HART I/O Module PM HART I/O Module Series C I/O/Series 8 I/O Module

IO Link Module C300 Controller Module COMM DTM Interface FIM2 FIM2, FIM4 Links FIM4, FIM8 FDT Communication DTM FDT Gateway DTM Device DTM SM controller IOTA Safety Network group Process Network group Unhealthy devices Disconnected Nodes R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

113

4. FDM Operations 4.2. Online view functions

You can perform the following tasks from the Network View tree by right-clicking a device and selecting the appropriate option. •

Device configuration

•

Comparing Device Configuration (currently supported only for DD based device configuration)

•

Viewing/Deleting Device History

•

Viewing audit trail

•

Locking and unlocking a device

•

Downloading a DD/DTM based Offline Configuration to an Online Device

•

Renaming FDM Tags

•

Logging User-defined Audit Trail Actions

•

Device Documentation at Device level ATTENTION You must not connect handhelds such as MC Toolkit and so on if a device is connected in FDM with Honeywell HART DE Modem, However, if you connect handheld to a device and change few parameters, then ghost devices appear in FDM Client Network View. The ghost device refers to the device, which is not available in the network, but the device appears in the FDM Client Network View.

Device State View The Device State View tab displays the state of devices that are connected to the network or disconnected from the process. Assigning devices to various device states is a manual task that you can perform from the FDM Device Properties tab in the Device Configuration form or from Device State View tab.

114

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.2 Online view functions

These devices can be spares, connected to the process, disconnected for maintenance, or decommissioned. The following are the different states of devices. •

Calibration Status – This displays the status of devices as Calibrated, Calibration Required or Not set.

•

Device Health – This displays the device status as Good, Needs Service, Not Set, Sent to Repair, or Discarded.

•

Device Usage – This shows the device status as Connected to Process, Decommissioned (device should not be used), Disconnected from Process, Not set, or Spare. REFERENCE – INTERNAL For details on changing the device state (Device Usage, Calibration Status, and Device Health), refer to section Editing Device Properties from a DD Configuration.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

115

4. FDM Operations 4.2. Online view functions

Device State View icons The following icons are displayed in the Device State View tree. Icon

Description Calibration Status Calibration Status (Calibrated, Calibration Required, and Not Set) Device Health Device Health – Different States (Discarded, Good, Needs Service, Not set, Sent to Repair) Device Usage Device Usage – Different States (Connected to Process, Decommissioned, Disconnected from Process, Not set, Spare.)

116

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.3 Offline View functions

4.3

Offline View functions Overview of Offline View The Offline View group is used for all offline activities like managing offline configuration, managing display filters for the Network Tree view and also viewing the Device Library that lists all the DDs and DTMs that are available in FDM.

The Offline View group contains following three tabs. •

Offline Configuration

•

Display Filter

•

Device Library

Offline configuration The Offline Configuration feature enables you to configure a set of device parameters without the need for a device to be available physically. The Offline Configuration tab enables you to create an offline configuration for a device. This offline configuration can be downloaded to an online device (of the same type) later. You can create a device-specific offline configuration that can be used for configuring devices of a particular device type or a generic offline configuration that can be used for configuring all devices. REFERENCE - INTERNAL For details on creating and using offline configuration, refer to section Offline configuration.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

117

4. FDM Operations 4.3. Offline View functions

Display filter functions The display filter feature enables you to filter the nodes/devices displayed in the Online View > Network View tree. Filters can be created based on Network Type, Manufacturer Type, Device Type, Configured Networks, and Device Tags. When a filter is applied, the Network View tree view displays only those nodes/devices included in the filter. REFERENCE - INTERNAL For more details, refer to section Using display filters.

Device library functions The Device Library tab displays DD Library and DTM Library. The DD Library displays the following information about DDs available in FDM. •

Manufacturer Name/ID

•

Device Type

•

Device Revision

•

DD Revision

The hierarchical device information is displayed in a tree structure as follows:

118

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.3 Offline View functions

REFERENCE – INTERNAL You can manage (attach/modify or upload/detach) Device Documentation at the Device Type level using the Device Library tab. For more details on attaching/detaching/modifying or uploading device documentation, refer to section Working with device documentation.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

119

4. FDM Operations 4.3. Offline View functions

The DTM Library displays the following three types of DTMs. •

Communication devices

•

Gateway/Modular devices

•

Field devices

•

The number against the DTMs shows the number of DTMs of that type.

It displays the following device information for each device type. •

Manufacturer Name/ID

The hierarchical device information is displayed in a tree structure as follows:

120

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.3 Offline View functions

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

121

4. FDM Operations 4.4. FDM device tags

4.4

FDM device tags Overview of FDM Tags FDM provides each device a unique name to identify the device, which appears adjacent to the device icon in the Network View tree. When you browse a network (except for EPKS) for the first time, the devices are listed under network view with the HART tags. After you load a device, the tag name of the device appears in the Tag field in the right pane. ATTENTION •

Ensure that length of the device tag is not more than 16 characters and does not contain any special characters or spaces.

•

HART tags appear as FDM tags for devices connected through RS-485 Multiplexer.

•

The tags are derived from Control Builder for devices connected through Experion.

Device tag generation for RS-485 Multiplexer and Modem networks When the devices are connected through RS-485 Multiplexer and modem networks and if you perform build network for the first time, then the device tag for HART 5, HART 6 and HART 7 devices appears as HART Tag and HART Long Tag respectively. If the device does not have a tag, then the device tag appears as InvalidTag in the network view. In addition, if there is more than one such device with blank tags, they are detected as InvalidTags appended by conflict tag and a number. After the network browse is complete for the first time and all the tags are detected with HART tags, even if you change the HART tag field in the device, it is not reflected in the network view and vice versa. When you rename the tags in the network view, the tag name is changed and it is saved in the FDM database. But, the HART tag name is not changed in the device. To change the Tag name in the device you must open the device configuration form and then rename it in the Tag field.

Device tag generation for Experion networks When the devices are connected through Experion network, the alias name appears instead of Network Interface name in the Network View. For an Experion network, a device tag is the same tag as shown in Experion system.

122

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.4 FDM device tags

From an Experion network, if a device is moved to any other network (Example RS-232 HART Modem), the tag of this device in the Network View displays as Experion tag name. You can rename the tags using Rename option. From a Mux network, if a device is moved to Experion network, the tag of this device in the Network View displays as Experion tag name. ATTENTION •

Renaming of HART devices connected to the Experion interface can only be done using the Control Builder. But, when a mux connected device is being monitored from the Experion system, FDM does not allow you to rename that particular device.

•

If the Device Configuration page is open, FDM does not allow you to rename the device.

Device tag generation for COMM DTM Interface When the devices are connected through COMM DTM Interface, the tag name appears in the Network View. FDM generates automatically the tag for COMM DTM Interface. This is applicable for HART and PROFIBUS devices: •

If the detected device is HART and it does not have a DTM or you do not select a DTM, then the device tag depends on the HART tag of the device. This device is added to the network tree since it can be loaded with DD.

•

If the detected device is PROFIBUS and it does not have a DTM or you do not select a DTM, this device is not added to the network tree.

When you rename the tags in the network view through Rename option, the tag name is changed and it is saved in the FDM database. TIP Besides FDM Client, you may also rename devices connected to COMM DTM network from the corresponding FDT Comm Console to which these devices are belong to.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

123

4. FDM Operations 4.4. FDM device tags

Device tag generation for Safety networks FDM Client Network View displays the similar tags that are present in Safety Builder which are exported from Safety Builder and imported to FDM as SB Export File. Tags under Safety network cannot be renamed. When devices connected to Safety network are moved to other network, based on the network type, the tag might be retained in the new network. Example, From Safety network, if a device is moved to Multiplexer network, the device would appear with the same tag. And also, if a device is moved from Safety network to Experion network, the device would appear with the tag from the Experion system. ATTENTION During build network of Safety network, any device tag of Safety network has conflict with the device tag of existing network (For example, Multiplexer network), Safety network tag is appended with tag conflict. Then, the following message displays in the Warning tab in FDM Client System Notifications pane.

To resolve the tag conflict, rename the device connected to Multiplexer network and then rebuild the network at IOTA level corresponding to the device where conflict is observed.

124

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

4.5

Customizing the FDM settings Customizing the System settings The system setting is used for changing the single sign on, device configuration load option, write access for Experion connected devices, device health and network scan for Mux connected devices, device health scan for FDT connected devices, Experion event journal logging option, and device lock. All these settings affect relevant functionality at the FDM Server level. All these options are enabled only for the user who has administrator privileges. To view the system settings, choose FDM > Settings. The Settings dialog box appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

125

4. FDM Operations 4.5. Customizing the FDM settings

126

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

The following table describes the features of System Settings. Feature

Description

Single Sign On

Single Sign On allows you to logon to the FDM without entering the user credentials. Any valid Windows user who is a part of one of the FDM user groups can log on to FDM without entering any credentials. Ensure that if you enable Single Sign On, any user who is not part of any of the FDM user groups does not able to login even if he has a valid ‘Classic server security’ user name and password. • To enable the Single Sign On feature, select the Enable Single

Sign On check box. • To disable the Single Sign On feature, clear the Enable Single

Sign On check box. Note: A user with only administrative privileges can enable Single Sign On using FDM System settings. Device Configuration Load Option

Device Configuration Load Option is used for loading configuration parameters from Database or Device. This applies only to DD/EDD devices and not to the devices loaded using DTMs. • To load the configuration parameters from the database click

Load From Database. This is the default option. When you select this option, all the parameter values from the Database are available. But, if there is any change in the configuration parameters value, FDM automatically ignores the values from the database and loads from the device. • To load the configuration parameters from the device click Load

From Device. All the recent changes in the configuration parameter values are available, irrespective of the values stored in the database.

ATTENTION

R430 May 2012

•

When you are loading the device for the first time, irrespective of the option Load From Database and Load From Device selected, the configuration parameters are loaded from the device.

•

When the configuration parameters are modified by handheld or any other third party application, the following message appears if you try to load a device from the database.

Field Device Manager - R430 User's Guide Honeywell

127

4. FDM Operations 4.5. Customizing the FDM settings

Feature

Write Access For Experion Connected Devices

Description

−

If you click Ignore, then all the parameters are loaded from the database.

−

If you click Suppress for the specified occurrences, then this message does not appear and all the parameters are loaded from the device.

When FDM is connected to the field devices through Experion interface, the devices that are in process are locked by default. To edit any device parameter you must inactivate the device or enable the Write Access For Experion Connected Devices option. • To allow the read/write access for the process active devices

connected to Experion, select the Allow Write Access for Process Active Devices check box. • To prevent the read/write access for the process active devices

connected to Experion, clear the Allow Write Access for Process Active Devices check box. Device Health and Network Scan for Mux Connected Devices

128

Device Health and Network Scan has two settings namely Scan for Device Health and Communication every ___ Seconds and Scan Network for New Devices every ___ Minutes. a)

Scan for Device Health and Communication every ___ Seconds option defines the system behavior with respect to scanning the device health and connection status. This setting is applicable to all devices connected to the HART hardware multiplexer network. −

To enable the Health Scan feature, select the Scan for Device Health and Communication every ___ Seconds check box.

−

To disable the Health Scan feature, clear the Scan for Device Health and Communication every ___ Seconds check box.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Feature

Description If a device is found unhealthy, it is indicated in red in the network view. If a mux network is removed from the network, it is removed automatically from Online network view and appears under Disconnected Nodes. You can also set the time interval (in seconds) for the FDM, to scan the health and connection status of the devices. This indicates that each mux in the network does health scan and dynamic removal for its devices after every 60 seconds. But, the range is from 60 to 600 seconds. Note: Even if Scan for Device Health and Communication every ___ Seconds option is disabled, FDM displays the device health properly in the following cases.

b)

−

When the network is built/rebuilt.

−

When a device is loaded in FDM Client/Experion Station.

−

When a device is accessed from a third party tool through FHM.

−

When the device Detail Display page is opened in the Control Builder.

−

When Dynamic Scan is enabled in device configuration.

Scan Network for New Devices every ___ Minutes option defines the system behavior for discovering any new devices connected to the network after the network is built in FDM. −

To enable the discovery of the new devices connected to the undiscovered loops/channels, select the Scan Network for New Devices every ___ Minutes check box.

−

To disable the discovery of the new devices connected to the undiscovered loops/channels, clear the Scan Network for New Devices every ___ Minutes check box.

If Scan Network for New Devices every ___ Minutes option is enabled and the network build is complete, FDM continuously polls all the disconnected loops/channels of the multiplexers to find if new devices are connected to the network. If a new device is found at these loops/channels, it is displayed in the network view. If this option is disabled, FDM does not poll for new devices, after the network build operation is complete. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

129

4. FDM Operations 4.5. Customizing the FDM settings

Feature

Description You can also set the time interval (in minutes) for the FDM, to poll the new devices connected to the network. This setting indicates that each discovery cycle for new devices happens only after 2 minutes from the last discovery cycle. The Scan Network for New Devices every ___ Minutes has 2 minutes interval by default. But, the range is from 2 to 600 minutes. Note: The Scan Network for New Devices every ___ Minutes option is applicable only for the devices connected to new loops/channels in the multiplexer after the build network operation is complete. If the device is connected to the loop/channel which is already discovered then, Scan Network for New Devices every ___ Minutes option does not scan that device. To view the status for such devices, FDM uses the Scan for Device Health and Communication every ___ Seconds option.

ATTENTION

Device Health Scan for FDT Connected Devices

•

Disabling the Device Health and Network Scan for Mux Connected devices option disables the Mux Monitoring feature (if applicable) and alarms are not reported in Experion Station.

•

It is recommended that the Scan Network for New Devices every ___ Minutes is disabled during post commissioning phase or you provide a large interval to have better device load performance.

Scan for Device Health every ___ Minutes option defines the system behavior with respect to scanning the device health. This setting is applicable to all devices connected to the FDT network. By default this option is disabled. −

To enable the Health Scan feature, select the Scan for Device Health every ___ Minutes check box.

If a device is found unhealthy, it is indicated in red in the network view. You can also set the frequency (time interval in minutes) at which the devices under FDT network must be scanned for health information. This indicates that each FDT network does health scan for its devices continuously for this specified time interval. 130

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Feature

Description The range is from one to 60 minutes. You can also configure device health for the selected devices that are connected to the FDT network. For more information, refer to section Customizing the FDT health scan settings.

ATTENTION Very frequent device health scan on FDT network can causes the Comm/Gateway/IO DTMs state to become non-responsive and hindering the basic FDT operations like network scan, DTM configuration and so on. This behaviour might worsen if large number of devices are connected. Hence it is recommended to choose appropriate health scan interval based on the size of the network. Bigger the network, greater must be the health scan interval for FDT network. Experion Event Journal Logging

Every event such as point status change or an operator action, is stored in an event summary. In Experion Station, to record all the parameter changes into Event summary for all FF devices that are connected to FIM, select the Log parameter changes to Experion Event Journal check box in the FDM Client through the Settings menu. . The log parameter enables log for all FF devices in the Network tree.

ATTENTION . Experion Event journal logging for devices can also be changed from Device Configuration page. Device Lock

Device Lock feature has the following options that are used for enhancing the security to the devices. • Lock all newly discovered devices by default • Automatic lock devices after ____ Minutes • Prompt User for Device Unlock Password • Exclusive Access to Unlocked devices

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

131

4. FDM Operations 4.5. Customizing the FDM settings

Feature

Description

ATTENTION The device lock options are recommended for FDM systems that are fully commissioned. Since, during commissioning, devices need to be modified extensively, it is recommended to turn off the device lock settings during this phase. a)

Select the Lock all newly discovered devices by default check box to lock newly discovered devices on the network automatically. This affects the devices that are discovered using dynamic discovery or if you browse an existing network again. Even after enabling this setting, all the devices that were already discovered in the network retain their existing lock status.

b)

Select the Automatically lock devices after ____ Minutes check box to automatically lock an explicitly unlocked device after a specified time period. This feature does not affect the devices that were explicitly unlocked before this option was enabled. Additionally, when this feature is enabled, if the device configuration page of the device is closed, then device is automatically locked. If this option is enabled, a device might be automatically locked in the middle of device configuration or during method execution. Hence, FDM allows you to extend the automatic lock by displaying reminder message as“Device auto lock imminent. Click here to extend” in the Device configuration page before 5 minutes to timeout. Click this message to extend the autolock timeout interval. Device autolock interval must be in the range of 30 to 120 minutes.

ATTENTION When the device autolock feature is enabled, the devices under network are locked automatically for security in the following scenarios.

132

•

If the unlocked devices are disconnected.

•

If the RCI on which the device is connected, is stopped.

•

If the network on which the device is connected is rebrowsed.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Feature

Description

c)

•

If the device configuration page is closed.

•

If FDM Station Maintenance View is refreshed or closed.

Select the Prompt User for Device Unlock Password check box to protect the devices that are connected to a network using a password. You need to enter a password to unlock a device if this feature is enabled. If the password is already set and if you want to reset the password, then click Reset Password. The device unlock password must have a minimum of eight and maximum of 20 characters.

d)

Select Exclusive Access to Unlocked devices check box to provide exclusive write access for the device in FDM Client where it is unlocked. In all other FDM Clients, the same device is in read-only and it is not allowed to lock/unlock unless the device is closed/locked in first FDM Client. If this option is not enabled, then it is possible to unlock a device in one FDM Client and load it in another FDM Client with write access.

ATTENTION It is recommended to use this setting to implement better security for write access for device.

Customizing the Audit Trail settings The Audit Trail feature enables you to select audit trail time format and to view a log of actions that users perform on FDM. Some actions are implicitly logged. You can add user-defined audit trail actions using Log User Action option. To view Audit Trail settings, choose FDM > Settings > Audit Trail. The following dialog box appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

133

4. FDM Operations 4.5. Customizing the FDM settings

134

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

The following table describes the Audit Trail Settings. Feature

Description

Audit Trail Time Format

Audit Trail Time Format enables you to display the time stamp in one of the following formats for Audit Trail records. • Show UTC time: Choose Show UTC time to display the

time stamp in the Coordinated Universal Time (UTC) for Audit Trail records. • Show Local time: Choose Show Local time to display the

time stamp in the local time for Audit Trail records This is the default option. Audit Trail Action Settings

Audit Trail Action Settings enables to select the action types for which you want to enter a reason for performing the action. Action Type indicates the various system actions that can be audited. Reason Enabled indicates whether the logging of Reason is mandatory for the action type or not. You can select or clear Check/Uncheck All to enable/disable logging reason for all action types.

ATTENTION Only an Administrator can the change Audit Trail settings.

The following action types are audited in FDM. Action Type

R430 May 2012

Description

Param Change

When a parameter is changed, FDM logs a record in the audit trail.

Rename Device

When a device is renamed, FDM logs a record in the audit trail.

Lock/ Unlock Device

When a device is explicitly locked/unlocked, FDM logs a record in the audit trail.

Execute Method

When a method is executed, FDM logs a record in the audit trail.

Field Device Manager - R430 User's Guide Honeywell

135

4. FDM Operations 4.5. Customizing the FDM settings

Action Type

136

Description

Build Network

When a network is built (using the Build Network option), FDM logs a record in the audit trail.

Add/ Delete DD/DTM

When a DD or DTM is added/deleted, FDM logs a record in the audit trail.

User Login

When a user logs in, FDM logs a record in the audit trail.

Add/Delete/Modify User

When a new user is added or an existing user’s details are modified, or when an existing user account is deleted, FDM logs a record in the audit trail

Add/Delete/Modify Role

When a new user role is added or an existing user role’s details are modified, or when an existing user role is deleted, FDM logs a record in the audit trail.

Change License

When a license is updated, FDM logs a record in the audit trail.

Stop Server

When the server is stopped, FDM logs a record in the audit trail.

Delete Device

When a device tag is deleted, FDM logs a record in the audit trail.

Import/Export

When a device tag/ history/audit trail/offline configuration is imported/exported, FDM logs a record in the audit trail.

Add/Delete/Modify Group

When a Group is added/ deleted/modified, FDM logs a record in the audit trail.

Device List Actions

When the device list is configured (created/modified/deleted), FDM logs a record in the audit trail.

Change Audit Trail Settings

When the audit trail settings are changed, FDM logs a record in the audit trail.

User Explicit Action

When any explicit user-defined action is performed, FDM logs a record in the audit trail.

Modify Write Access for Process Active Devices

When the write access is enabled or disabled for process active devices, FDM logs a record in the audit trail.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Action Type

R430 May 2012

Description

Device Status Change

When the device status is changed, FDM logs a record in the audit trail.

Device Lock Change

When the state of the device lock is changed (from locked to unlocked or unlocked to lock), FDM logs a record in the audit trail.

Hart Multiplexer Actions

When FDM Hart Multiplexer is started/stopped, FDM logs a record in the audit trail.

Add/ Delete/ Modify Network

When a network configuration is added /deleted /modified, FDM logs a record in the audit trail.

History Actions

When the user explicitly saves history or whenever the user deletes history, FDM logs a record in the audit trail.

Offline Configuration Actions

When the user creates /opens/modifies/deletes or renames an Offline Configuration, FDM logs a record in the audit trail.

Device Documentation Actions

When the user attaches/uploads/detaches a device document (at the device level, device type level or system level), FDM logs a record in the audit trail.

Display Filter Actions

When the user creates/modifies/opens/deletes or renames a Display Filter, FDM logs a record in the audit trail.

Mux Monitoring Actions

When the user performs an action related to Mux Monitoring, like accessing the FDM Tag Builder tool, FDM logs a record in the audit trail.

Device Application Launch

When a third party application is started, FDM logs a record in the audit trail.

Bulk Operations

When the user performs bulk operation to create history record or offline templates for certain set of devices, and bulk offline download, FDM logs a record in the audit trail.

Delete Records

When the user deletes the records of device tags, offline device configuration, and device history, FDM logs a record in the audit trail.

Field Device Manager - R430 User's Guide Honeywell

137

4. FDM Operations 4.5. Customizing the FDM settings

Action Type

Description

DTM Operations

When there is a DTM related audit trail events (if DTM supports audit trail) or user performs DTM library update, FDM logs a record in audit trail.

ATTENTION For DTM Configuration, Audit Trail dialog box (Enter Reason for current action dialog box) appears only when supported by DTM.

Viewing Audit Trail To view the audit trail, perform the following steps. Step 1

138

Action Choose View > Audit Trail. The following page appears.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Step

Action

TIP You can also access the Audit Trail feature by clicking the below the FDM Toolbar.

icon

2

Action Type lists all the actions that are currently audited in FDM. For instance, Param Change indicates any change that a user makes to a parameter, logged in the Audit Trail. Select the required action types from Action Type. To view the Audit Trail for all parameters, select All.

3

User lists all the users created in FDM. To view the audit trail for a particular user, select the user from User. To view the audit trail for all users, select All.

ATTENTION The actions ‘Device Status Change’ and ‘Device Lock Change’ are not specific to a user. Hence, these actions do not have a user assigned to them. While filtering these actions, select “All” in the User box. 4

Nodes lists all the HART and FF devices that are online and connected to FDM or devices from history (devices whose state is not online currently). Select the required device from Device. To view the Audit Trail for all devices, select All.

5

Select the From and To dates using the calendar.

ATTENTION To change the Audit trail settings, click the Settings button. The Settings dialog box appears. For details, refer to section Customizing the Audit Trail settings.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

139

4. FDM Operations 4.5. Customizing the FDM settings

Step

Action

6

Click View. The following Audit Trail details appear in the lower portion of the Audit Trail screen. • SNo: Displays the serial number of Audit trail records. • Time Stamp: Displays the Date and Time when the user performed the

action. • Action: Displays the action (Example: Stop Server) that the user

performed. • User: Displays the user who performed the action. • Device Tag: Displays the device tag name for a device that appears in the

Network Tree view. This field displays the device tag of the device on which the user performed the action. • Description: Displays the description that FDM automatically logs for each

action implicitly. • Reason: If the Administrator has enabled reason logging for this particular

Action Type, this column displays the Reason that the user has entered while performing the action.

140

7

To export the Audit Trail details, click Export.

8

To print the audit trail records in HTML format, click Print. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.5 Customizing the FDM settings

Step

Action

ATTENTION •

When you want to view a large number of audit trail records, client takes time to collect all the records and the status displays as fetching in the audit trail page.

•

The maximum number of audit trail records that you can view at any time is 15000. If the total audit trail records fetched are more than 15000, the following message appears.

Choosing DD/DTM load settings This setting enables the devices to determine if FDM loads the configuration using a DD or DTM. To set or change DD/DTM setting, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose FDM > Settings. The Settings dialog box appears.

3

Click the DD/DTM tab. All the HART device types which have both DD and DTM are listed in Load Using DD/EDD by default. DTMs must be installed for the devices if you want to load a device with a DTM and FDM DTM library must be updated.

4

To load a device type using DTM, perform the following steps. • Select a device type from the Load Using DD/EDD list. • Click > to move it to the Load Using DTM list. • To move all device types to the Load Using DTM list, click the >> button

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

141

4. FDM Operations 4.5. Customizing the FDM settings

Step 5

Action To load a device type using DD/EDD, perform the following. • Select a device type from the Load Using DTM list. • Click < to move it to the Load Using DD/EDD list. • To move all device types to the Load Using DD/EDD list use the Switch Server. The Field Device Manager login screen appears.

2

Follow the procedure explained in Logging on to the FDM Client to connect to a different server.

ATTENTION When you try to a logon to a different server, the connection to the current server is lost, irrespective of whether the logon succeeds or not.

144

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

4.8

Building networks Overview After configuring the network, you must establish the connection with the network and detect devices connected to the network. This process of detecting devices connected to the configured networks is known as building a network. All devices must be commissioned to appear in FDM Network View. For example, FF devices are detected when you configure Honeywell Experion PKS in FDM Server Management Tool and Fieldbus Interface Module (FIM) in Control Builder to which FF devices are connected. ATTENTION

R430 May 2012

•

Before trying to connect to the devices using FDM, ensure that you establish the physical connection between the device and the required network communication interfaces (RS-232 HART Modem, RS-485 Multiplexer, Honeywell HART DE Modem, Honeywell Experion PKS, Safety Network with Universal Safe Modules, or COMM DTM Interface).

•

During build network, if you try to perform multiple operations, FDM system becomes slow.

•

You cannot perform build network, if devices connected to the same network are in use.

•

If you perform build network from cache, a message appears displaying Build network from cache completed in the status bar. This message appears only when you stop FDM Server, open a new FDM Client (connecting to new instance of FDM Server), and perform build network from the cache.

•

If you perform build network for a device that is active under mux monitoring in Control Builder, a message appears displaying Network build is aborted in the status bar.

Field Device Manager - R430 User's Guide Honeywell

145

4. FDM Operations 4.8. Building networks

Detecting devices on the network To detect a device connected to the network, perform the following steps using FDM Client. Step 1

Action From the Network View under Online view, expand FDM Server network tree. The list of network interfaces appears.

2

Right-click the required network interface and then click Build Network. When Build Network operation is performed, the status of the operation appears in the System Notifications pane. FDM detects the devices connected to the network and displays them in the tree view.

ATTENTION Depending upon the type of communication hardware and interface, discovery of devices varies in FDM. When a new device is detected, it automatically appears in the Network View tree. Similarly, when a device goes offline or is disconnected, it disappears from the Network View tree.

ATTENTION For Safety networks, when the devices are disconnected, changes are reflected automatically in the online network view. But, when the devices are connected back, they are not reflected in the network view automatically till you turn the Fault Reset key on the SM controller. If a device is found unhealthy, it is indicated in red and listed under Unhealthy devices in the Network View tree. 3

146

If a node (Device\Mux\Controller\IO\IOLINK\FIM2\FIM4\FIM8\FFLINKS\SM\IOTA) is disconnected from the network, then node is moved to the Disconnected Nodes list in the Network View tree.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Building FDT networks FDT Comm Console allows you to configure FDT networks, and build the complete network using DTMs only on the RCI Server. After configuring the Communication and Gateway DTMs, and scanning the network, the network is available on the FDT Comm Console. It shows other networks configured on a particular FDM server. In FDT Comm Console, you can view all network related updates, but device related operations are restricted to the local FDT network configured for that particular RCI. The following table lists the features which are supported in FDM Client and FDT Comm Console. Features

R430 May 2012

FDM Client

FDT Comm Console

Advanced Search

Supported

Supported

Add//Edit/Delete User

Supported

Supported

Add/Edit/Delete Role

Supported

Supported

Add/Edit/Delete Group

Supported

Supported

Bulk Offline Download

Supported

Not supported

Bulk Operations

Supported

Not supported

Import and Export

Supported

Not supported

Delete Records

Supported

Supported

Attach/Detach/Upload Document

Supported

Supported

Attach/Detach Application

Supported

Supported

Add/Delete DD File

Supported

Supported

FDT Health Scan Settings

Not supported

Supported

Save and Restore network

Not supported

Supported

Go Online/Offline

Not supported

Supported

Upload/Download parameters

Not supported

Supported

Add/Delete device

Not supported

Supported

Rename device tag

Supported

Supported

Field Device Manager - R430 User's Guide Honeywell

147

4. FDM Operations 4.8. Building networks

To build the FDT networks, perform the following steps. Step 1

Action Configure the COMM DTM Interface in the FDM Server Management Tool. For more details, refer to the section Configuring Comm DTM network in FDM.

2

Log on to the FDT Comm Console.

ATTENTION The RCI machine name on which the FDT Comm Console is launched, appears in Bold font in Network View to clearly highlight the local RCI node. 3

In the Network View list, right-click COMM DTM interface name and then click Add Device. The DTM Selection Dialog appears with the list of all the available DTMs.

4

Select the communication DTM and then click OK. The communication DTM is added to the Server and appears in the left pane.

ATTENTION Ensure that DTM library is updated with the installed DTMs before you creating the network. For more information about updating DTM library, refer to section Updating DTM Library. 5

Right-click the communication DTM and then click Open Configuration. The configuration page appears in the right pane.

6

The configuration page provides all the available functions of the Communication DTM. Use these functions to configure the Communication DTM. For more information, refer to the DTM specific help to ensure proper configuration. The following figure displays the configuration page of PROFIBUS Gateway (Lite) Communication DTM.

148

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Step

Action

You must enter appropriate values in all the fields, for the Communication DTM to function as required. 7

After configuring the Communication DTM, right-click the communication DTM and click Go Online to make it online.

ATTENTION It is not necessary to open configuration page to make DTM online. 8

Right-click the Communication DTM and then click Scan for Devices. The Channel Selection Dialog appears.

9

Select the required channels or All and then click OK. The ScanStatus message appears displaying the progress of the scan. After scanning, the Dtm Assignment dialog box appears. The devices are detected and listed in the Dtm Assignment dialog box.

10

For the selected channel number and address, assign DTMs to the devices. You can view the suggested DTMs for the devices.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

149

4. FDM Operations 4.8. Building networks

Step 11

Action Select the suggested DTM. Or If you want to assign different DTM, then click the Assign DTM button. The DTM Selection Dialog appears. Select the necessary DTM and then click OK.

12

Click OK in the Dtm Assignment dialog box. The detected devices are visible in the FDT Comm Console (Network View > COMM DTM Interface).

13

If a gateway DTM is detected, perform steps 5 through 10 on the gateway DTM. The detected devices are visible in the FDT Comm Console (Network View > COMM DTM Interface).

ATTENTION •

Ensure to close all the configuration pages in FDT Comm Console before closing it.

•

Ensure to make the modules Offline (if they are Online) before closing the opened configurations in FDT Comm Console.

•

Ensure to close all the configuration pages in FDT Comm Console before deleting the device. To delete the device, rightclick the device and then click Delete device. The device is deleted from both FDT Comm Console and FDM Client Network View.

•

Ensure to save the network before you close the FDT Comm Console.If you do not save the network, the entire FDT networks configured in FDT Comm Console is lost.

•

With FDM R430, you can rename the tags in FDT Comm Console Network View. To rename the tags, right-click the device and then click Rename. The tag name is changed and it is saved in the FDM database.

You can configure the device parameters, view history, and download offline configuration for DTM based devices from the FDT Comm Console.

Saving and restoring FDT networks The Save and Restore feature in the FDT Comm Console allows you to save the FDT network that has been configured on a particular RCI computer. This network can be later restored and used. 150

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

To save and restore network, perform the following steps during building FDT network. 1.

Initiate scanning a Comm DTM or Gateway DTM. For more information, refer to section Building FDT networks.

2.

After scan completion, DTM Assignment dialog box appears.

3.

After necessary changes, acknowledge the DTM Assignment dialog box.

4.

Click icon to save the FDT network. The Save Project dialog box appears where you can specify file name and location. The network is saved in a xml file.

5.

After saving the network, close the FDT Comm Console.

6.

Launch the FDT Comm Console and click icon to restore the saved network file (XML) and make the Comm DTMs and Gateway DTMs online.

Resource consumption notifications in FDT Comm Console The current resource usage of FDT Comm Console is indicated in status bar in percentage format as shown below. This is important because FDT Comm Console deals with third party DTMs that might primarily contribute to overall resource consumption of this tool. The following are the three types of computer resource consumption information. ATTENTION FDM records a log in the audit trail for resource consumption and you can view these logs using View > Audit Trail. •

R430 May 2012

Normal Resource Usage information: During Normal Resource Usage, you can continue to work on the FDT Comm Console.

Field Device Manager - R430 User's Guide Honeywell

151

4. FDM Operations 4.8. Building networks

•

152

Resource Warning Message: FDM monitors the resource consumption of FDT Comm Console and warns you appropriately when the resource consumption goes higher than the threshold limit. This allows you to take appropriate actions like saving the network, closing FDT Comm Console and restoring the network.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

•

R430 May 2012

Maximum Resource Limit Warning Message: FDT Comm Console warns you appropriately when the resource consumption exceeds the maximum resource limit. This allows you to take appropriate actions like saving the network, closing FDT Comm Console and restoring the network.

Field Device Manager - R430 User's Guide Honeywell

153

4. FDM Operations 4.8. Building networks

ATTENTION Creating a FDT network consumes the process memory of the FDT Comm Console program. The amount of memory consumed varies from one DTM to another. The resource monitor on the FDT Comm Console status bar allows you to keep track of the resource usage. If the resource usage exceeds the set threshold limits, the user is notified. Hence, it is recommended you to save the network, close and restart FDT Comm Console and then restore the network to reduce the resource consumption. This is to ensure that any further FDT operations are not affected by high resource consumption.

154

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Configuration of Gateway modules which do not support scan operation Some Gateway DTMs do not support scan operation on them. You must manually add devices under DTM. Perform the following steps to configure the modules in FDT Comm Console. Step

Action

1

Perform steps 1 through 10 of the section Building FDT networks to configure DTMs in FDT Comm Console. The configuration varies from one Gateway to another. For more information about the configuration details, refer to the individual gateway manuals.

2

After the Gateway is made Online, select the Gateway module in FDT Comm Console.

3

Right-click the Gateway module and then click Add Device. The DTM Selection Dialog appears.

4

Select the appropriate Gateway module and click OK. The Channel Address Selection dialog box appears.

5

Select the channel number from the drop-down list and type an appropriate number in the Bus address box, which depends on the Gateway and click OK. For more information, refer to the gateway manuals. The appropriate module is listed under the Gateway of the FDT Comm Console hierarchy.

6

Perform steps 5 through 10 of the section Building FDT networks on the gateway DTM. Detected device DTMs along with the Communication and Gateway DTMs are listed in the FDM Client Network View under Comm DTM network. You can configure these devices from FDM Client and also from FDT comm console in the RCI machine where these devices are connected.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

155

4. FDM Operations 4.8. Building networks

The following procedure is an example of configuring Phoenix Contact Inline IO in FDT Comm Console that does not support dynamic scan. Step

Action

1

Scan the Communication DTM to which the Phoenix Contact IO module is connected. The Phoenix Contact IO module must be detected.

2

After the Gateway is made Online, select the Gateway module in FDT Comm Console.

ATTENTION It is not necessary to open the configuration page to make DTM online. 3

Right-click the Gateway DTM and click Add device. The DTM Selection Dialog appears.

4

Select Phoenix Contact Hart AI module DTM and click OK. A Channel Address Selection dialog box appears.

5

Select the channel number.

6

Type the appropriate module in the Bus Address and click OK. The DTM Dialog appears.

ATTENTION Ensure that bus number should be unique for IO DTMs. 7

Select the slot number as necessary from the Slot drop-down list and click OK in the DTM Dialog.

8

After you made Hart module Online, right-click the HART module and click Scan for Devices. The ChannelSelectionDialog dialog box appears.

9

Select the required channels or All and click OK. After the scan operation on all selected channels completes, DTM Assignment dialog box appears, listing all the devices detected.

10

156

The DTM Assignment dialog box lists the recommended DTM against each device, if a matching DTM is found in the current DTM library.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Step 11

Action You can select the suggested DTM. Or For a selected device at a particular channel/address, you may change the DTM. For this, click the Change DTM button. The DTM Selection Dialog appears. Select the necessary DTM and click OK.

12

Click OK in the Dtm Assignment dialog box. The detected devices are visible in the FDM Client (Network View > COMM DTM Interface).

ATTENTION Ensure that the connected devices in Communication and Gateway DTMs are unloaded from FDM Client before making the Communication and Gateway modules Offline.

Configuring PROFIBUS masters Class-II masters (DPM2) are used for operation and monitoring purposes and during the start-up. The associated exchange of data takes place if required. Therefore, class-II masters require acyclic communication services exclusively. Following are the two scenarios in which a Class-II master is used. •

In first scenario, the Class-I master cannot provide the data into the Asset management system. In this case, the setup needs both Class-I and Class-II masters in order to obtain the data into DCS and also in Asset management system.

•

In second scenario, the Class-I master itself acts as both Class-I and Class-II and provides data into DCS and also Asset management system.

Configuration with both Class-I and Class-II Master Class-I masters which do not have communication DTMs cannot provide the data into Asset management tools like FDM. In this case, in order to obtain data into FDM, you must use both Class-I and Class-II masters.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

157

4. FDM Operations 4.8. Building networks

When you are using both Class-I and Class-II masters, during configuration of Class-II master in FDM, the configuration parameters must be same as that of Class-I master. This scenario can be better explained by taking the example of Woodhead SST-PFBCLX module (PBIM) multi-dropped with Softing’s FG100. Woodhead SST-PFB-CLX module (PBIM) is a Class-I Master which does not have a communication DTM and Softing’s FG100 is a Class-II master which has communication DTM. Multi master configuration of Woodhead SST-PFB-CLX module (PBIM) with Softing’s FG100. In this scenario:

158

•

The Woodhead SST-PFB-CLX module (PBIM), Softing’s FG100, and other DP slaves are connected in Multi drop.

•

Woodhead SST-PFB-CLX module (PBIM) acts as a Class-I master and fetches process data cyclically into a DCS system.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

•

Softing’s FG100 acts as a Class-II master and fetches acyclic data as and when requested by the FDM.

Configuration with only Class-I master Class-I masters which have communication DTMs can be used for providing the process data cyclically into DCS as well as for providing acyclic data into an Asset management system like FDM. Honeywell’s PMD Controller which has communication DTM can be taken as an example for this scenario. Following is a procedure for configuring and scanning PROFIBUS PA devices connected to PMD controller through Pepperl and Fuchs DP/PA link.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

159

4. FDM Operations 4.8. Building networks

To configure PMD in FDM, perform the following steps. Step

Action

1

Configure all the DP slaves connected to PMD controller in multi drop from the PMD builder and download into the PMD controller.

2

Install the PMD Comm DTM provided by the vendor in the RCI machine to perform the PMD configuration in FDM.

3

Add the PMD Comm DTM to FDM DTM library. For more information, refer to section Updating DTM Library.

4

Open the FDT Comm Console in the RCI machine where PMD Comm DTM is installed.

5

Right-click COMM DTM Interface and then click Add device. The PMD Comm DTM is added in the FDT Comm Console hierarchy.

6

Right-click the PMD node and then click Open Configuration. The Configuration page appears.

7

Click the Configuration tab and select the check box for the required devices and click OK.

8

Make the PMD Comm DTM Online and scan for the devices.

9

The communication DTM detects devices present in the network. The Dtm Assignment dialog appears with the list of available DTMs for all the detected devices. Select the Suggested DTM or if you want to change DTM, click the Assign DTM button. The DTM Selection Dialog appears. Select the necessary DTM and then click OK.

10

Click OK in the Dtm Assignment dialog box. As the Pepperl and Fuchs DP/PA link acts as a transparent link, it is not detected when the network is scanned, instead the PA devices are detected directly under the Communication DTM in network hierarchy.

160

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Building Safety networks You can build safety network in the following ways. •

If Standalone Safety Network is configured, then you can perform build network at network level, SM controller level, and IOTA (Universal Safe Modules) level.

•

If Experion integrated Safety Network is configured, then you can perform build network at network level and at group level (Process and Safety network level). And also, you can perform build network at SM controller level, IOTA (Universal Safe Modules) level.

When you export configuration file from Safety Builder, there is an element called controller version in XML file. This controller version should exactly match with version in the actual firmware of the controller. If they do not match, FDM does not perform build network operation and displays the configuration mismatch error message in the Error tab as follows.

To resolve this issue, you need to generate the new SB Export file with proper configuration information and update in FDM. Then, perform the build network.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

161

4. FDM Operations 4.8. Building networks

Building Standalone Safety network To build the Standalone Safety network, perform the following steps. Step 1

Action From the Network View under Online view, expand FDM Server network tree. The list of network interfaces appears.

2

Perform any one of the following to build Standalone Safety network. • Right-click the standalone network interface and then click Build Network.

FDM detects the SM controllers, IOTAs and HART channels connected to the network and displays them in the tree view.

162

−

Right-click the SM controller and then click Build Network. FDM detects the IOTAs and HART channels connected to the network and displays them in the tree view.

−

Right-click the IOTA and then click Build Network. FDM detects the HART channels connected to the network and displays them in the tree view.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

Building Experion integrated Safety network To build the network for Experion integrated Safety network, perform the following steps. Step 1

Action From the Network View under Online view, expand FDM Server network tree. The list of network interfaces displays with both Process and Safety network groups.

2

Perform any one of the following to build Experion integrated Safety network. • Right-click the Experion integrated Safety Network and then click Build

Network. FDM detects all devices connected to SM and Experion and displays them in the tree view.Right-click the Process Network group and then click Build Network. FDM detects all devices connected to the Experion network and displays them in the tree view.Right-click the Safety Network group and then click Build Network. FDM detects all SM controllers, IOTAs, and HART channels connected to the Safety network and displays them in the tree view. • After SM controller is discovered, right-click the SM controller and

then click Build Network. FDM detects the IOTAs and HART channels connected to the network and displays them in the tree view. • After SM controller is discovered, right-click the IOTA and then click

Build Network. FDM detects the HART channels connected to the network and displays them in the tree view.

ATTENTION When Build Network operation is initiated on Safety Network from FDM, you might see few devices than actual devices or devices might not appear. This issue is observed when HART devices and RUSIOs (configured in SB) are disconnected and connected back to Safety Manger. To detect these HART devices and RUSIOs dynamically in FDM, turn the Fault Reset key on Safety Manager and check for defined diagnostic messages on Safety Manager. For more details about diagnostic messages on Safety Manager, refer to Safety Builder User’s Guide.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

163

4. FDM Operations 4.8. Building networks

SM network redundancy handling in FDM The redundant SM has two Control Processors, CP1 and CP2. Control Processor (CP) has different states that are Running, Idle, and Unknown. When both the CPs are in Idle state, only SM is shown in network with "grayed out" icon and you cannot perform build network on it.

164

•

The network communication is available when any one of the CPs or both the CPs are in running state.

•

If one of the CPs state is changing from Running to Idle/Unknown and vice-versa, then Network View is not impacted due to the CP switchover.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.8 Building networks

•

If both the CPs are in Idle state or if one of the CP is in Unknown and other CP is in Idle state, then, only SM is displayed in the network. But, there is no communication with IOTAs and devices from FDM.

•

If both the CPs are in Unknown state, then it does not display SM(s) in Network View.

The following notifications appear in System Notification pane under Warning tab for the above scenarios during CP switchover.

If CP switchover occurs during device configuration, the warning message appears in System Notifications pane under Warning tab as follows:

To avoid communication error and timeout error, close the device configuration page and retry the operation. REFERENCE - INTERNAL For more information about CP switchover behavior, refer to FDM R430 Troubleshooting Guide.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

165

4. FDM Operations 4.9. Managing DDs

4.9

Managing DDs Every manufacturer of devices creates a Device Description (DD) file for each model or type of device that they make. The DD file contains device-specific information that is used for interpreting the responses received from the device. You can add and delete DD file from the client.

Adding a DD file If you do not have a DD for a given device, you can add DD to the DD library by using the Add DD File option. When you add a DD, the server automatically generates the corresponding template for the DD. This template is published to all the open clients. ATTENTION Only users assigned with the privileges associated with the Administrator role can add/delete a template or synchronize data.

To add any new DD file from the client to the server, perform the following steps. Step 1

Action Choose Library > Add DD File from the FDM Client. The Select a DD file dialog box appears.

TIP You can also click the Add DD File icon under the FDM Toolbar. 2

Browse to the folder where the .fms or .fm6 or .fm8 file is located, select the file and click Open. A message appears informing you that the DD is uploaded successfully.

ATTENTION If you add a DD that is already exists in the DD library, then an error message appears displaying “Template generation failed”. 3

166

Click OK to return to the FDM Client.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.9 Managing DDs

Deleting a DD file This feature enables you to delete a particular version of a DD file. When a DD for a particular device type and device revision is deleted, all subsequent loading of devices of that type uses the previous DD revision. If no previous DD revisions are present, it uses the Generic DD. ATTENTION •

It is recommended not to use this option unless suggested by Honeywell TAC.

•

After deleting a DD, FDM Clients that are open must be synchronized.

•

After a DD is deleted from the FDM Database, Offline configurations of that particular DD is deleted.

To delete a DD file, perform the following steps. Step 1

Action Choose Library > Delete DD File from the FDM Client. The Delete DD File dialog box appears.

2

Select the manufacturer of the device DD that needs to be deleted and click Next. The Delete DD File dialog box appears displaying all the device types supported by that manufacturer.

3

Select the device type of a DD that needs to be deleted and click Next. The Delete DD File dialog box appears displaying all the device revisions supported by that device type.

4

Select the Device Revision of a DD that needs to be deleted and click Next. The Delete DD File dialog box appears displaying all the DD revisions supported by that device revision.

5

Select the DD revision for the device revision of a device that needs to be deleted and click Delete. The Delete DD File dialog box appears displaying the details of the selected DD file that needs to be deleted and prompting you to confirm the deletion of the selected DD file.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

167

4. FDM Operations 4.9. Managing DDs

Step 6

Action Click Yes to delete the DD file. After Deleting a DD, a message appears displaying DD Deleted successfully.

Synchronizing a DD-based template FDM provides an option to synchronize the client data with the server data and update it with the latest templates. When you add a DD file to the server, it generates the template for the corresponding DD that is added. To view this template on your client, you need to either log off from the FDM and log on again, or use the Template Caching option to synchronize the data. This functionality can be used for synchronizing DD information between the FDM Server and FDM Client. Closing and opening the FDM Client automatically performs the synchronization. To synchronize and update the client with the server, perform the following steps. Step

Action

1

Assume that the new template is generated in the server for the DD file added.

2

From the FDM Client, choose Library > Template Caching. The Template or Icon Download dialog box appears.

ATTENTION If all templates are already synchronized, the following message appears.

3

Click Start to start the synchronization. The Template or Icon Download dialog box appears displaying the synchronization progress.

4

168

Click Close.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.10 Managing DTMs

4.10 Managing DTMs The DTM Library Manager provides the details of all DTMs present in FDM. The following operations can be performed using the DTM Library Manager. •

Updating the DTM Library

•

Adding DTMs

•

Removing DTMs

Updating DTM Library After you have installed DTMs from FDM Client or FDT Comm Console, you need to perform an update to detect these changes. ATTENTION •

DTM library is system dependant. If you have installed and updated the DTM library in one client, it does not reflect in other clients. This procedure has to be performed on all clients wherever DTM(s) are installed.

•

When FDM Client is installed on RCI, and if you are updating DD/DTM settings in both FDM Client/FDT Comm Console, then this setting is effective in both.

•

Ensure to close FDM Client/FDT Comm Console after updating DTM library on re-launch to proceed.

To update the DTM library, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Library > Manage DTM Library. The DTM Library Manager dialog box appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

169

4. FDM Operations 4.10. Managing DTMs

Step

Action

ATTENTION

3

•

Click

to expand the DTM Updates pane.

•

Click

to expand the DTM library pane.

Click Update. The following DTM library message appears.

170

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.10 Managing DTMs

Step 4

Action Click Yes to discard the changes and continue with updating the library. The following DTM library message appears.

5

Click Yes to update the DTM library. The DTM Updates lists all the newly installed and removed DTMs in the system. For more information about adding newly detected DTMs to the DTM Library, refer Adding DTMs section. Following are the different DTM status and their indications. Status

Description

DTM not updated

Indicates that the DTM has not been updated recently.

New DTM

Indicates that the DTM has been updated recently.

DTM Available

Indicates that the DTM is available and selected to the DTM library.

DTM Unavailable

Indicates that the DTM has been removed.

Modified DTM (Available)

Indicates that the DTM has been modified.

ATTENTION The DTM Updates pane shows the previously scanned list of DTMs that were not selected in DTM library pane. To view the latest list of DTMs, ensure to click Update button.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

171

4. FDM Operations 4.10. Managing DTMs

Adding DTMs To add DTMs to the DTM Library, perform the following steps. Step 1

Action Perform the steps1 through 5 of the Updating DTM Library. The DTM Library Manager dialog box appears.

2

Select the DTMs that you want to add to the DTM Library from DTM Updates.

TIP To select all the DTMs in any of the lists, select the first DTM and then press CTRL+SHIFT+END on the keyboard. To select multiple DTM(s), press CTRL and then select the required DTMs. 3

Click Add >>. The new DTMs are added to the DTM Library.

4

Click Save.

Removing DTMs To Remove DTMs from the DTM Library, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Library > Manage DTM Library. The DTM Library Manager dialog box appears.

3

Select the DTM or DTM(s) that you want to remove from the DTM Library.

4

Click Detailed Setup > Instrument under Device Functions. The following page appears displaying set point, variables, and so on.

180

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Step

Action

ATTENTION •

You can change configuration of the device only if it is unlocked. For more details, refer to section Device .

•

When FDM is connected to the field devices through the Experion interface through the PM HART IO or the Series C I/O module, devices that are in process are locked by default. To edit any device parameter or run a method, you need to inactivate the device.

•

When FDM is connected to field devices through the Experion interface through the 1756 HART IO module, the channel mode needs to be changed to ‘OFF CONTROL’ in order to configure the devices.

If the same device is open in two or more clients, then only the first client has read write access to the device, assuming that the user has required privileges. The second and subsequent client shows this device as locked. 2

The bottom pane displays the parameter names, values, and their corresponding units, methods, and edit display. The parameter values are updated dynamically as per the actual values of the device in the field. If required, modify the values for the configurable parameters. Note: You cannot modify the parameter values that appear in grey or is disabled.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

181

4. FDM Operations 4.11. Device configuration using DD

Step 3

Action Select the parameter to modify the value. The parameter value field turns yellow when you modify the value.

Move the mouse pointer over the parameter name. The tool tip appears displaying the information about the parameter such as Label, Value, Unit, and Help, and so on. The tool tip information available from the DD. For example, place the mouse pointer over a parameter name to read the tool tip. When you are editing parameters, the pre/post edit actions and warnings appear if they are defined in the DD. You must respond to those actions before editing the parameters. These actions and warning varies from one variable to another. For example, the following warning message appears when you edit PV LRV parameter in a device.

182

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

R430 May 2012

Step

Action

4

Click OK to edit the parameter. The post edit action message appears when you click parameter in a device.

Field Device Manager - R430 User's Guide Honeywell

183

4. FDM Operations 4.11. Device configuration using DD

Step 5

Action Click

icon to update the modified parameters values to the field device.

The Parameters To Download dialog box appears.

6

Click Download to download the edited parameter values onto field devices.

ATTENTION

184

•

.

•

For better performance of FDM, it is recommended to close the device configuration page after the configuration activities for a device are completed.

•

For some devices to edit device parameters, device’s write protect (if present in device) should be disabled.

•

For a device connected to an RS-485, DD over Comm DTM networks or an Experion network communication interface, FDM does not allow changing of poll address.

•

Ensure the local time zone format is set to “English (United States)” using Control Panel >Clock, Language, and Region > Change the time zone. Editing the date and time parameters may fail if the local time zone changes. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

TIP To view the device status with respect to network communication, devices, and commands, click FDM Device Status from the Device Configuration page.

The FDM Device Status displays the diagnostic information of the device health. However, the details displayed under the Field Device Status tab vary from one device to another.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

185

4. FDM Operations 4.11. Device configuration using DD

Executing methods Methods are a predefined sequence of actions that can be performed on a HART field device. Methods are specified by the device vendor to perform the actions like loop test, calibration, write protection, and so on. The information regarding methods is available in the DD file of a device. Methods are available in the following two places. •

FDM lists all the methods in the Device Configuration page as MethodList entry point.

•

The method is defined in the DD for a device which can be browse through the menus. ATTENTION

186

•

When a device is in the process of loading, the methods under MethodList does not appear.

•

When executing a method, you cannot perform any other operation on the device.

•

If a method is running and the device autolock feature is enabled, then it may lead to method failure if the device is allowed to lock itself. Hence, it is recommended to extend the timeout interval or disable the device autolock feature before running methods.

•

The following procedure is just an example. The steps in each method type are device-specific and vary from device to device. Follow the instructions mentioned in the method’s wizard to execute a method.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

To execute a method for a device, perform the following steps. Step

Action

1

On the Device Configuration page, click Method List.

2

Click Loop test. The method execution wizard appears. Note: The Help information is displayed in the wizard, if the help is defined for the device in the DD.

TIP •

Place the mouse pointer over the method name. The tool tip appears displaying the label name and other information about the method. The tool tip information displays only when the help is defined in the DD.

•

To view the help information during the method execution process, click

R430 May 2012

in the wizard.

Field Device Manager - R430 User's Guide Honeywell

187

4. FDM Operations 4.11. Device configuration using DD

Step

3

Action

Click OK to continue executing the method. If you click OK, the method execution wizard continues displaying the subsequent step in the method execution process. Or Click Abort to cancel the method execution. Similarly, select any other method and follow instructions on the wizard to execute the method.

188

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Editing Device Properties from a DD Configuration On FDM Device Properties tab, you can view and edit the device properties such as device information, maintenance notes, and so on. To view/edit the device properties, perform the following steps. Step 1

Action On the Device Configuration page, click FDM Device Properties.

It contains details such as Manufacturer Name, Device Type Name, Device Revision, DD Revision, Maintenance Notes, Special Instruction, Device Usage, Calibration Status, Calibration Due Date (MM/ DD/ YYYY), and Device Health.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

189

4. FDM Operations 4.11. Device configuration using DD

Step

Action

2

If necessary, you can modify the values for Maintenance Notes, Special Instruction, Device Usage, Calibration Status, Calibration Due Date, and Device Health by re-entering/re-selecting the values from the list.

3

To change the device usage state, select any of the appropriate values (Not set, Connected to Process, Spare, Disconnected from Process, and Decommissioned) from the Device Usage list box.

4

To change the calibration status, select any of the appropriate values (Not set, Calibrated or Calibration Required) from the Calibration Status list box.

5

Change the calibration due date by re-entering the value in the MM/DD/YYYY format in the Calibration Due Date text box.

ATTENTION Enter a value greater than the current date for Calibration Due Date. An appropriate message appears, if you enter a value in the past. 6

To change the device health, select any of the appropriate values (Not set, Good, Needs Service, Sent to Repair, and Discarded) from the Device Health list box.

7 Click

icon.

The Parameters To Download dialog box appears. 8

Click Download to download the values onto the field devices. Or Click Reset to discard the changes and restore the original values.

ATTENTION If you change the Device Usage, Calibration State or Maintenance Notes, these values are reflected in the State Information of the Entry Points page. 190

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Exporting online configuration using DD An online configuration can be exported to a file in the CSV, Excel or Documint format. Using Export option, you can export the summary of device configuration operation. To export an online configuration, perform the following steps. Step 1

Action On the Device Configuration page, click Export under FDM Tasks. The Export dialog box appears.

2

Click the required format for export. Export File Name & Location box displays the name of the exported file and location. To change the name and/or location, click the

button.

The Save As dialog box appears. 3

Choose the drive/directory/sub-directory on FDM Client, where you want to save the file.

4

Type a file name and click Save. The Export dialog box with the updated file name and location appears.

5

Click OK. The following message appears on the status bar of the Device Configuration page.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

191

4. FDM Operations 4.11. Device configuration using DD

Saving History Records using DD To explicitly save history records, perform the following steps. Step 1

Action On the Device Configuration page, click Save History Record. The Save History Record dialog box appears.

ATTENTION

2

•

You must provide the audit trail reason for saving history records.

•

When Save History Record operation is performed, the parameters which are not already read are read from the device. Therefore, this operation may take some time.

•

When you are performing Save History Record, the Enable Dynamic Scanning option under FDM Tasks must not be selected.

Enter an appropriate file name to save history record and click OK. FDM reads all the parameters from the device and status is as shown in the following message.

When the operation is completed, the following message is displayed on the status bar

192

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Step

Action

ATTENTION •

FDM does not accept duplicate names for history records. Ensure that you specify a unique name for each record.

•

Depending upon the HART command traffic on the network, the reading of parameters from the device may be slow. If FDM cannot read all the required parameters from the device in 10 minutes, the operation is aborted and a message is displayed to the user stating Operation Timed Out. It is recommended to re perform the operation again without closing the device configuration page.

•

Even if you change any dynamic parameter through Handheld Communicator at device level, it is not saved by Save History Record operation.

•

On closing the Device Configuration page, the following message displayed to remind you to save the changes made to the device using save history operation before closing the device record.

Saving an Online Configuration as an Offline Configuration using DD A device’s online configuration can be saved as an offline configuration, thus enabling you to use this configuration to configure other devices of the same Manufacturer, Device Type and Device Revision. To save an online device’s configuration as an offline configuration, perform the following steps.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

193

4. FDM Operations 4.11. Device configuration using DD

Step 1

Action On the Device Configuration page, click Save as Offline Template. The Save Online As Offline dialog box appears.

ATTENTION

2

•

You must provide the audit trail reason for saving online configuration as offline configuration.

•

When Save As Offline Template operation is performed, the parameters which are not already read are read from the device.

•

When you are performing Save as Offline Template, the Enable Dynamic Scanning option under FDM Tasks must not be selected.

Enter the name for the online configuration that you want to save as an offline configuration, in File Name and click OK. FDM reads all the parameters from the device and status is as shown in the following message.

When the operation is completed, the following message is displayed on the status bar.

194

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Step

Action

3

FDM saves the online configuration as an offline configuration and the offline configuration appears in the Offline View > Offline Configuration > Offline Templates tree. Depending upon the HART command traffic on the network, the reading of parameters from the device may be slow. If FDM cannot read all the required parameters from the device in 10 minutes, the operation is aborted and a message is displayed to the user stating Operation Timed Out. It is recommended to perform the operation again without closing the device configuration screen.

Viewing device notifications If any error, information, and warning after you perform few operations in device configuration page, then these device notifications appears in the Notifications pane. It has Information, Error, and Warning tabs. Each tab displays Time Stamp and Description for all operations. To view the device notifications, click Notifications link under FDM Tasks in the from the lower-right of the device configuration page. And also, you can click device configuration page to view the device notifications.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

195

4. FDM Operations 4.11. Device configuration using DD

For each error, warning, and information tab, maximum 1000 rows are supported. If it exceeds 1000 rows, then the initial row is removed and at the end, new row is added. You can click anywhere in the Notifications pane and click Clear Row(s) to clear the contents of the window.

Scanning Dynamic Parameters Values of certain variables are updated by the field device without any stimulus from the communication network or the user. Such variables are called as dynamic parameters. For example, PV, SV, TV, and so on. After reading the parameter values, FDM does not automatically refresh these values. Using Enable Dynamic Scanning option, parameter values can be refreshed periodically from the device. If Enable Dynamic Scanning is enabled, FDM refreshes any dynamic parameter value being viewed on the current menu every 40 seconds. By default, this option is disabled.

196

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

ATTENTION The Enable Dynamic Scanning option is available only for DD/EDD configurations. Enabling this option leads to sending more commands to the device on a periodic basis. Consequently, this increases the HART command traffic on the network. Hence, it is recommended to reset this option when not required, otherwise it affects other device related operations on the same network.

To enable periodic refreshing of dynamic parameters, perform the following steps. Step 1

Action On Device Configuration page, select Enable Dynamic Scanning under FDM Tasks. The following message appears.

2

Click OK to scan all dynamic parameters of the selected device.

ATTENTION Enable Dynamic Scanning setting does not affect the updation of graphical items like charts.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

197

4. FDM Operations 4.11. Device configuration using DD

Comparing device configuration Using the Compare Configuration feature, you can either compare the device data of two different devices belonging to the same Device Type or the device data of the same device history. You can compare configurations of only DD/EDD based devices. To compare the device configuration for two different devices of similar type, perform the following steps. Step

Action

1

Select the device tag from the Online View > Network View list.

2

Right-click the device and click Compare Configuration. The Compare Configuration page appears.

The selected device name is displayed in the Device Tag drop-down list.

198

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.11 Device configuration using DD

Step

Action

ATTENTION

3

•

To describe the functionality, the device 1 is referred as base device.

•

Device autolock in Compare Configuration :If Device autolock feature is enabled for a device loaded in the compare configuration page and the device’s autolock timer is about to expire (5 minutes before the end of the autolock timeout interval), a message appears in the lower right side of the page. The autolock timeout interval can be extended from a range of 10 to 60 minutes. Clicking this message allows you to extend the autolock timer. If you don’t want to extend the timer, ignore the message and the device is locked automatically when the timer expires. The reminder message is displayed only to the users with Write Parameter privilege.

Select history record’s name or Current for the source device in date and Time. Choose the Current option, if you need to compare the present (online) configuration of the device with another device’s configuration or with a previously saved configuration of the same device (history).

ATTENTION Only if the base device configuration is Current, then it can be edited. 4

The Devices drop-down list, lists all the connected devices of the same device type. The connection status for the selected device is displayed in Connection Status. Select the device from the Devices drop-down list against which the base device configuration needs to be compared.

R430 May 2012

5

Select the required date and time in Record Name for the device that you want to compare with. If Current is selected, then the present configuration of the device is loaded.

6

Click Compare to view the selected device configuration. The device information appears.

Field Device Manager - R430 User's Guide Honeywell

199

4. FDM Operations 4.11. Device configuration using DD

Step

Action

The column on the left side (Device 1) displays the configuration for the base device. The column on the right side (Device 2) displays the configuration of the device that is being compared with the base device configuration. If the base device configuration is Current, then the particular parameter value is highlighted (Blue) in both the columns and Refresh Device List to refresh the device tree in the ValveLink software for all devices which are appearing in FDM Client Network view list. For more information about ValveLink operations, refer to the AMS ValveLink Software Guide.

214

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

4.14 Offline configuration Overview The Offline Configuration feature enables you to configure a set of device parameters without the need for a device to be available physically. In other words, it enables you to create a configuration for a device, without the device being available online. The Offline View > Offline Configuration tab enables you to create an offline configuration for a device. The offline configuration can be downloaded to the device by right-clicking a device in the Online View > Network View. A user can create three types of Offline Configurations which are as follows: •

DD offline configurations – This enables you to create a DD offline configuration that is specific to a Device Type. You can use this offline configuration only for devices belonging to the specific Device Type.

•

Generic DD offline configurations – This enables you to create a DD offline configuration that contains a set of standard parameters that are applicable to all Device Types. Hence, you can use a generic DD offline configuration to configure devices of any Device Type.

•

DTM offline configurations – This enables you to create an offline configuration for DTM. You can use this offline configuration only for the devices for which load setting is Load Using DTM. ATTENTION •

Offline Configuration feature is not supported for FF devices.

•

Though you can create a DD offline configuration for a device as described below, it is recommended to use an offline configuration of a device by using Save as Offline template feature. For more information, refer to section Saving an Online Configuration as an Offline Configuration using DD. An offline configuration thus saved is more accurate in terms of reflecting proper configuration of device and the representative values.

When creating an offline configuration for the first time, you have to explicitly select the Manufacturer, Device Type and Device Revision for the configuration, from the respective list boxes in the Create Configuration form. However, if you are creating another offline configuration for the same Manufacturer and/or Device Type and/or Device Revision, you can browse through the Offline Configurations tree, right-click and choose the Create Configuration option, either at the Manufacturer level, the Device R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

215

4. FDM Operations 4.14. Offline configuration

Type level or the Device Revision level. FDM automatically populates the appropriate vendor information in the respective list boxes in the Create Configuration page.

Creating a DD offline configuration for a specific device type To create a DD offline configuration for a specific device type, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Click the Offline View group. The Offline Configuration, Display Filter and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/DTM Offline configurations tree appears in the left pane.

4

Right-click DD Offline Configurations and click Create Configuration. The Offline – Create Configuration page appears in the right pane.

216

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step 5

Action From the Manufacturer list, select the manufacturer of the device. Based on the manufacturer that you select the device types are populated in the Device Type list.

6

Select the appropriate device type from Device Type. FDM populates the corresponding Device Revisions.

7

Select the appropriate Device Revision and DD Revision.

8

Click Create. The device parameters appear in the Configuration View panel.

The Items (Parameters), Value and the Units appear in a tabular format. To display the parameter IDs, select View IDs.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

217

4. FDM Operations 4.14. Offline configuration

Step

Action

9

If necessary, you can edit the parameters. For more information about editing parameters, refer to section Editing an offline configuration. After making the required changes to the parameter values, select the check box (located in the Select column) corresponding to the parameters that you want to download to the device(s). Select All to download all the parameters to the device.

10

Click Save to save the changes. The following dialog box appears.

11

Type an appropriate name for the offline configuration in Name. Click OK to save the configuration with the name you typed. The name of the configuration appears in Configuration Name box.

ATTENTION •

If you want to save the copy of offline configuration as a new offline configuration with the specified file name, click Save As. The new offline configuration name appears in the DD Offline Configurations tree.

•

Ensure that file name does not contain special characters.

In addition, the name of the configuration appears under Manufacturer ID > Device Type > Device Revision in DD Offline Configurations tree.

218

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step

Action

TIP •

If you want to rename a DD Offline Configuration, right-click offline configuration (name) and click Rename.

•

If you want to delete a DD Offline Configuration, right-click offline configuration (name) and click Delete.

•

You cannot rename and delete a DD Based configuration if another user (FDM Client) has opened the configuration form.

For instance: Creating an offline configuration at Manufacturer level: To create an offline configuration, as an existing configuration for the same Manufacturer, but for a different Device Type and Device Revision, perform the following: •

R430 May 2012

In the Offline Configurations tree, right-click Manufacturer and click Create Configuration.

Field Device Manager - R430 User's Guide Honeywell

219

4. FDM Operations 4.14. Offline configuration

Creating an offline configuration at Device Type level: To create an offline configuration for the same Manufacturer and Device Type, but for a different Device Revision, perform the following: •

In the Offline Configurations tree, right-click the Device Type and click Create Configuration

Creating an offline configuration at Device Revision level: To create an offline configuration for the same Manufacturer, Device Type and Device Revision, perform the following: In the Offline Configurations tree, right-click the Device Revision, and click Create Configuration.

220

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Creating a Generic DD offline configuration To create a Generic DD offline configuration for all device types, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Click the Offline View group. The Offline Configuration, Display Filter, and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/DTM Offline configurations tree appear in the left pane.

4

Right-click the Generic DD Offline Configurations and click Create Generic Configuration. The Offline – Create Configuration page appears in the right pane.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

221

4. FDM Operations 4.14. Offline configuration

Step

Action

As the configuration is generic, the fields (Manufacturer, Device Revision, Device Type, and DD Revision) in the Configuration Details panel are disabled and populated with predefined values.

222

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step 5

Action Click Create. The generic device parameters appear in the Configuration View panel.

6

The Items (Parameters), Value, and the Units appears in a tabular format. To display the parameter IDs, select View IDs.

7

If necessary, you can edit the parameters. For more information about editing parameters, refer to section Editing an offline configuration. After making the required changes to the parameter values, select the check box (located in the Select column) corresponding to the parameters that you want to download to the device(s). Select All to download all the parameters to the device.

8

R430 May 2012

Click Save to save the changes.

Field Device Manager - R430 User's Guide Honeywell

223

4. FDM Operations 4.14. Offline configuration

Step

Action The following dialog box appears.

9

Type the name for the offline configuration in Name. Click OK to save the configuration with the name you typed. The name of the configuration appears in Configuration Name box.

ATTENTION •

If you want to save the copy of offline configuration as a new offline configuration with the specified name, click Save As. The new offline configuration name appears in the Generic DD Offline Configurations tree.

•

Ensure that file name must not contain special characters.

In addition, the name of the configuration appears in Generic DD Offline Configuration tree view.

TIP

224

•

If you want to rename a Generic DD Offline Configuration, right-click offline configuration (name) and click Rename.

•

If you want to delete a Generic DD Offline Configuration, rightclick offline configuration (name) and click Delete.

•

You cannot rename and delete a Generic DD Based configuration if another user (FDM Client) has opened the configuration form.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Creating a DTM offline configuration To create a DTM offline Configuration, perform the following steps. ATTENTION The DTM offline configurations can be created only in FDM Client in which the DTMs are installed and the FDM DTM Library is updated with the installed DTMs. Step

Action

1

Log on to the FDM Client.

2

Click the Offline View group. The Offline Configuration, Display Filter, and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/DTM Offline configurations tree appear in the left pane.

4

Right-click DTM Offline Configuration and click Create Configuration. The Create Configuration page appears.

ATTENTION The functionality and appearance of the offline configuration page is vendor specific. 5

Select the device manufacturer from Manufacturer drop-down list and device from Device Type drop-down list, and click View. The DTM Start Page appears in the right pane.

6

Edit the parameter required for offline configuration. Refer to section Configuring a device using DTM for the steps on how to edit device parameters.

7 Click

R430 May 2012

icon to save DTM Offline Configuration.

Field Device Manager - R430 User's Guide Honeywell

225

4. FDM Operations 4.14. Offline configuration

Step

Action The following dialog box appears.

8

Type the name for the offline configuration in Name.

9

Click OK to save the DTM Offline Configuration. The saved configuration appears in the DTM Offline Configurations tree.

TIP •

If you want to rename a DTM Offline Configuration, right-click offline configuration (name) and click Rename.

•

If you want to delete a DTM Offline Configuration, right-click offline configuration (name) and click Delete.

•

You cannot rename or delete a DTM based offline configuration if it is being used in another FDM Client.

•

Offline DTM configuration is available only in the clients in which the respective DTMs are installed. For example, if you create a Honeywell DTM configuration in Client1, it is available only in the clients in which Honeywell DTMs are present in the DTM library.

Editing an offline configuration After creating an offline configuration, FDM lists the configurations in the DD Offline Configurations/Generic DD Offline Configurations/DTM Offline Configurations tree under the Offline Configuration tab. You can browse through the DD/Generic DD/DTM Offline Configuration tree, open a specific/generic configuration, modify the configuration, and save the changes if required. To modify a DD/Generic DD/DTM Offline configuration, perform the following steps.

226

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step

Action

1

Log on to the FDM Client.

2

Click the Offline View group. The Offline Configuration, Display Filter and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/ DTM Offline configurations tree appears in the left pane.

4

R430 May 2012

Right-click offline configuration and click Open to edit.

Field Device Manager - R430 User's Guide Honeywell

227

4. FDM Operations 4.14. Offline configuration

Step

Action If you select DD offline configuration name, its configuration page appears in the right pane.

Offline configuration allows you to edit all the parameters of the device that affect the configuration of the device. The solution provides an interactive interface that guides you to change the values and configuration of the device as you edit it.

228

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step

Action

ATTENTION •

Some writeable parameters are not directly exposed through the menu structure of a device, and can be edited only through a method. But they often are critical in configuring the device and hence are exposed in offline configuration. Sometimes such parameters may not always succeed in a download. It is advised to ensure the value of such parameters to be same as that in the device.

•

A Device Description file may contain variables whose values have an impact on other variable(s). In FDM, the former is referred to as Dominant variable and the latter as Dependant variable(s). An example is the dependency of sensor range value on the sensor type. Hence, sensor type can be referred to as a Dominant variable.

•

When you edit a dominant editable variable, FDM automatically updates the corresponding values for the dependant variables.

•

Read only parameters which are not editable in the device but have other editable parameters that depend on its value.

When you are editing parameters, the pre/post edit actions and warnings appear if they are defined in the DD. You must respond to those actions. These actions and warning varies from one variable to another. Following icons are used for indicating different states of the parameters during an offline configuration.

indicates Invalid parameters. – These parameters are not valid parameters as per the current configuration. indicates Valid parameters – These parameters are valid as per the current configuration and the writable parameter can be downloaded to the device. indicates Changed parameters – When a valid parameter is edited any other parameter(s) which are dependent on it must have the icon changed to green. This indicates that the value of these parameters needs to be verified and probably downloaded. 5

R430 May 2012

If you make any modification, the Save button is enabled.

Field Device Manager - R430 User's Guide Honeywell

229

4. FDM Operations 4.14. Offline configuration

Step

Action

ATTENTION You cannot modify the offline configuration if another user (FDM Client) has opened the configuration form before. You can modify the parameter values, only after all other users who have opened the configuration before you close the form. 6

Click Save to save the changes and click Close. If you select a DTM offline configuration, respective DTM Start page appears in the right pane.

7

To edit parameters, refer to section Configuring a device using DTM.

ATTENTION •

If you make modifications and close the screen without saving the changes, a confirmation message appears prompting you to save. Click Yes to save.

•

The Reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings.

8 Click

icon to save DTM Offline Configuration.

Downloading a DD/DTM based offline configuration to an online device To download a DD/DTM based offline to an online device, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Click the Online View to view Network View.

3

Right-click the device and click Download Offline Configuration. Depending on the DD/DTM settings, the offline configuration selection form appears in the right-pane.

230

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

To download DD-based offline configuration to an online device, perform the following steps. Step 1

Action Choose DD/DTM settings as Load Using DD/EDD. The following page appears.

Configuration Name (in the Select Configuration panel of the form) lists the offline configurations applicable to the Device Type of the selected device. If the selected device does not have a DD, then the Configuration Name lists the generic offline configurations. 2

R430 May 2012

Select the DD offline/generic DD offline configuration, from Configuration Name drop-down list.

Field Device Manager - R430 User's Guide Honeywell

231

4. FDM Operations 4.14. Offline configuration

Step

Action

3

Click View. The details of the DD/generic DD offline configuration appears.

4

If required, you can modify the parameter values. When you change the value of any parameter, the changed parameters turns yellow and Save button is enabled. To display the parameter IDs, select View IDs.

5

Click Save to save the changes.

6

If you had selected the parameters for downloading, at the time of creating the offline/generic offline configuration, the check boxes appears as selected against those parameters. If you want to download other parameters that you had not selected, while creating the offline/generic offline configuration, select the check box corresponding to those parameters. FDM allows you to download the whole set of parameters or a partial set of parameters. Check the Select All check box to select all parameters for downloading.

232

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step 7

Action Enter Device Timeout (in minutes) under Timeout panel, before you start downloading the offline configuration. If the download offline configuration fails in the specified timeout period, the following error message appears.

TIP Device time out includes the time to load the device and download the parameters to the device. The time to complete the operation depends on the complexity of the device and the HART network. The user needs to carefully choose the time out period taking these into account.

ATTENTION

8

•

Ensure that Device Timeout is in the range of 4 to 30 minutes.

•

When all parameters are selected and downloaded, only the writable parameters are downloaded. The read only and method editable parameters are not downloaded. They are considered only to validate the correct values of the editable parameters.

•

FDM does not allow you to download invalid parameters. These parameters appear in Red color. An appropriate message appears when you try selecting the checkbox corresponding to an invalid parameter.

•

If you select a dependant variable for downloading, the corresponding dominant variables are also automatically selected for downloading. An appropriate message appears to this effect.

Click Download. FDM does a validation of the parameters that are selected for downloading. If the validation fails, FDM does not download the offline configuration and the following download status window displays.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

233

4. FDM Operations 4.14. Offline configuration

Step

Action

The download status window indicates the reason for the failure in validation and the action you need to do. FDM downloads the offline configuration only if the values that are selected for downloading are valid. The actual downloading of parameters to the device proceeds after the validation succeeds. If the write for one or more parameter fails, then the download status box appears detailing the reasons and suggested actions for the failures. Follow the suggested actions to proceed further.

ATTENTION The chances of having a valid offline template are more if the offline template is created from an online configuration using the Save Online as offline feature. This ensures that most parameters have valid values. You can modify this template and download the configuration. The status bar in the right pane displays the status of the download operation. After the download is complete, the status bar displays Download completed.

ATTENTION FDM does not allow downloading some invalid parameters while downloading a HART DD/EDDL based offline configuration. For example, changing of poll address. 234

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

To download DTM based offline configuration to an online device, perform the following steps. Step 1

Action Select the Offline Record and click View. The DTM start page is vendor specific. This is an indicative page.

2

3

If you want, you can edit the parameters before downloading those parameters. To edit parameters, refer to section Configuring a device using DTM. Click

to download the parameters to the device.

Using the Bulk Offline Download feature The Bulk Offline Download feature enables you to use a DD offline configuration to configure multiple devices simultaneously. In other words, you can download multiple DD offline configurations to multiple devices of the different Manufacturer, Device Type, Device Revision, and DD Revision. You can do bulk offline download with following options. •

Bulk offline download with Select devices.

•

Bulk offline download with Import records from file. ATTENTION •

For performing a Bulk Offline Download, you must ensure to create a DD offline configuration.

•

When the device autolock/exclusive access to unlock devices feature is enabled, you are not allowed to perform Bulk Offline Download.

To download multiple DD offline configurations to multiple devices with Select Devices option, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Bulk Offline Download. The Bulk Offline Download page appears in the right pane.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

235

4. FDM Operations 4.14. Offline configuration

Step

3

Action

Under Select Devices pane: • Select the required Manufacturer from Manufacturer. FDM populates the

Device Type list box with the Device Types corresponding to the selected Manufacturer. • Select the device type from Device Type. FDM populates the Device

Revisions list box corresponding to the selected Device Type. • Select the appropriate device revision from the Device Revision list box.

236

4

If the devices matching the selected vendor information are found online, FDM lists the online devices under Device Tag.

5

From Device Tag, select the device(s) to which you want to download the offline configuration.

6

Based on the details (Manufacturer, Device Type, Device Revision, and DD Revision) you have selected, FDM populates the Offline Configuration list box with the matching offline configuration(s). Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step 7

Action From Offline Configuration, select the appropriate offline configuration to download to the selected devices.

ATTENTION If no offline configurations matching your selection are created, then Offline Configuration list box appears empty. 8

Click Add.

A T T E NT ION You can only select the device(s), if an offline configuration corresponding to the selected vendor information (Manufacturer, Device Revision, Device Type, or DD Revision) is available. FDM disables the Add button, if no offline configuration is available. The following page appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

237

4. FDM Operations 4.14. Offline configuration

Step

Action The grid shows the Device Name, Offline Configuration, Status, and Report for the selected devices.

9

Enter Device Timeout (in minutes), before you starts downloading the offline configuration.

ATTENTION The device timeout range is from 4 to 30 minutes. 10

Click Download.

ATTENTION When you click Download button, only if some other operations are in progress, then an error message appears displaying Operation is denied. Acknowledge the error and close the operations listed in the error message on the corresponding Clients to start bulk offline download. The following message appears.

11

Click Yes to continue the Bulk offline Download. The progress report indicates the progress in downloading the offline configurations and provides the following information. • Individual devices selected offline configuration, status and report. The

device status can be Pending, Loading, Downloading, Success, Failed, Timed out or Aborted. • Total number of offline configurations downloaded.

Status

238

Description

Pending

Device is not yet loaded.

Loading

Device is loading.

Downloading

Downloading of offline configuration starts on the device.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.14 Offline configuration

Step

Action Success

Downloading offline configuration is completed.

Failed

Downloading offline configuration is failed.

Timed out

Downloading offline configuration did not happen within the specified timeout.

Aborted

Downloading offline configuration is aborted.

Disconnected

The device is disconnected from the network.

Load Failed

The device failed to load due to some internal error.

Device Tag does not exists

Device tag entered in CSV file is not a valid device tag.

Offline configuration does not exists

Offline configuration entered in CSV file is not a valid offline configuration.

Device is locked

Bulk Offline Download is failed due to devices are locked.

Unknown Error

Bulk offline download is failed for some of the devices due to internal error.

No parameters selected for download

Bulk offline download is failed due to parameters are not selected for download in the offline configuration.

Communication Error

Bulk offline download is failed while writing parameters to device due to command sent to the device was timed out or command response was returned as communication error.

ATTENTION When Downloading of offline configuration on device fails, you can view the report by clicking Download Failed link in Report column.

R430 May 2012

12

After the download is complete, the following message appears.

13

Click Export to export the summary of bulk offline download operation. Field Device Manager - R430 User's Guide Honeywell

239

4. FDM Operations 4.14. Offline configuration

To download multiple DD offline configurations to multiple devices with Import records from file link, perform the following steps. ATTENTION You have to update the .csv file which is present at the default location C:\ProgramData\Honeywell\Fdm\Client\Resources\ Resource Templates with device tags and offline templates that is required for download. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Bulk Offline Download. The Bulk Offline Download page appears.

3

Click Import records from file. The Select File dialog box appears. The selected .CSV file with device tags and offline configuration shows in the Device Name and Offline Configuration columns in the grid. It also displays the status and report of bulk offline download operation.

4

Click Download. The following message appears.

5

Click Yes to continue the Bulk offline Download. In the next page, the progress report indicates the progress in downloading the offline configurations.

6

240

After the download is complete, the following message appears.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.15 Working with device history

Step

7

Action

Click Export to export downloaded DD offline configuration for selected devices in the CSV format.

4.15 Working with device history Overview FDM supports historization and maintains a history of device configuration with timestamps for all the connected devices. You can explicitly save history for a device configuration at any point in time. History record saves all the details pertinent to a device that are displayed in the Device Configuration and Device Status. You can select a device and view the history, export the details of the device in the CSV, HTML, XML, Documint or FDM format. FDM also provides an option to print the history in the HTML format. ATTENTION In FDM, you can view DD/DTM device configuration irrespective of the Load Settings for devices.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

241

4. FDM Operations 4.15. Working with device history

Example for viewing Device History To view the device history, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Build the Network to ensure that the devices are displayed under the Online View > Network View tree.

REFERENCE – INTERNAL For details on building a network, refer to section Building networks. 3

From the Network View list, right-click the required device tag and click View History. The DD/EDD or DTM history form appears in the right-pane irrespective of DD/DTM load settings.

4

• FDM saves each saved versions of the device history with the time stamp

(date and time). • Explicitly saved history versions have user-defined names.

Select a history version from the list and click View. The Device Configuration page appears.

242

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.15 Working with device history

Step 5

Action Following is an example to view the device configuration page, which is opened through history form. Click Online under Device Functions. The following page appears.

The Online window is split horizontally into the upper and lower panes. • The upper pane holds the set of menus based on timestamp selected. • The parameters associated with the selected menu appear in the lower

pane. 6

R430 May 2012

Click the “+” sign to expand items in the list and view the details.

Field Device Manager - R430 User's Guide Honeywell

243

4. FDM Operations 4.15. Working with device history

Step

Action

TIP •

Right-click and click View History to view history of the disconnected devices.

•

If you want to delete the device history, right-click the selected device and click Delete History.

Importing device configuration history from FDC into FDM The history snapshot saved in FDC can be imported into FDM for record and audit purposes. FDM allows you to synchronize the device configuration data through the MC Toolkit handheld. With FDC, you can save the device configuration snapshot as device history. This is saved as .fdm format. Consequently, the same device configuration history can be imported into FDM through the standard history import feature using the Import/Export wizard. Perform the following steps to import the device configuration history from FDC into FDM. Step

Action

1

Connect your MC Toolkit handheld to the computer where FDM Client is installed.

2

Browse to the folder for SD Card > FDC > Resources > History. The FDC history records are named as per the following convention for the primary name: DeviceTag_ManufacturerIDDeviceTypeDeviceRevisionDDRevision_Devic eID.

3

Copy the desired history record files (with .fdm extension) from the above mentioned location to a temporary location on FDM Client computer.

4

Use FDM Import/Export wizard to import the history records into FDM. For more details on how to use FDM Import/Export feature, refer to section Importing and Exporting Device history.

244

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.16 Bulk Operations

Step

Action After you import successfully, • The snapshot of device history is imported into FDM database and appear

as a history record for the corresponding device in FDM. • The Audit Trail entry for such a record identifies if it is imported through the

MC Toolkit handheld. • If the device is not part of any of the FDM configured networks, it appears

under Disconnected Nodes in FDM network view. • All operations allowed on Device History Record in FDM are allowed for the

record imported through the MC Toolkit handheld.

4.16 Bulk Operations The Bulk Operations feature enables you to create the history records and offline templates for several devices at the same time. This feature ensures that you do not have to manually open each device and save history/offline. This feature enables you to get the history snapshot of a set of devices in the maintenance database through a single operation. In addition, it is very helpful to create offline templates of a set of devices through a single operation. ATTENTION •

Bulk operations feature does not support creation of history and offline records using DTMs. It supports only DD/EDDL based history and offline records. Hence it is not applicable to the devices that cannot be loaded only with DTMs like PROFIBUS and FF devices.

•

If the user does not have privilege to perform bulk operations, then this option is disabled on the Tools menu.

Saving Bulk History To save the history records in bulk for the devices, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Bulk Operations. The Bulk Operations dialog box appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

245

4. FDM Operations 4.16. Bulk Operations

Step

3

Action

Click Bulk History. The Advanced Filter enables you to filter the nodes/devices displayed under the Select Devices left tree.

REFERENCE – INTERNAL For more information about Advanced Filter, refer to section Advanced Filter. 4

246

The left tree view shows the available devices and right tree view shows the selected devices. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.16 Bulk Operations

Step

Action Select the network node(s)/ device(s) using the following buttons. Click this button to move all selected nodes/devices in the Network (under Select Devices) to the right pane. Click this button to move a single node/device in the Network (under Select Devices) to the Selected box. Click this button to remove a single node/device from the Selected box to Select Devices. Click this button to remove all the nodes/devices from the Selected box to Select devices.

ATTENTION

5

•

You must select at least one device for creating history of the data for the devices in Select Devices.

•

If the devices are not selected from the list, then a dialog box appears prompting you to select a device before starting Bulk Operation.

•

When performing bulk operation, client must not perform any other device specific or server intensive operation.

•

If display filter is applied to the network tree, the filtered tree appears in the Bulk Operations.

Under Record Prefix: • Type the prefix name for the history record in Prefix record name with

box. You can maintain the unique name for history record with prefix. History record name contains the given prefix string followed by an internally generated number which is unique. The number is unique for each device. • Type the time in Device Timeout (Minutes) box. This is the time in which

FDM must save history of an individual device. If the device does not respond for all read requests during this time interval, the operation is timed out and is reported accordingly. This is a mandatory field and the allowed timeout range is 4 to 30 minutes.

ATTENTION •

R430 May 2012

Ensure that the prefix name does not exceed 14 characters. If the Prefix has any special characters, then the following dialog box is displayed.

Field Device Manager - R430 User's Guide Honeywell

247

4. FDM Operations 4.16. Bulk Operations

Step

Action

•

6

If the Device timeout exceeds or less than the timeout range, then a dialog box appears warning you that the device time out must be between 4 to 30 minutes.

From the Bulk Operations dialog box, click Start. A dialog box appears asking if you want to start the Bulk Operation.

ATTENTION

7

•

When Bulk Operation starts, FDM internally changes the Device Configuration Load Option to Load From Device and disables Write Access option in FDM Settings temporarily. However, these options are restored to original settings after bulk operation completes.

•

When you click Start button, an error message appears displaying Operation is denied due to some other operations on other Clients are in progress. Acknowledge the error and close the operations listed in the error message on the corresponding Clients to start bulk operations.

Click Yes to continue. The selected devices are grouped into batches and operation is performed on one batch at a time. The Bulk Progress dialog box appears. The following are the two tabs in Bulk Progress dialog box. • Devices • Server Notified Errors

248

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.16 Bulk Operations

Step

Action

The Devices tab displays the following information. • Individual device selected in the bulk operation, status of the bulk

operation. And also, the timestamp is recorded when history record is saved or when operation is failed in the Time column. • The progress report indicates the overall progress of the bulk operation. • Total number of devices for which bulk operation is completed.

All the error notifications received from the server are displayed under Server Notified Errors tab.

ATTENTION •

You can abort the bulk operation of the selected nodes/devices by clicking Abort.

Note: When you click Abort:

R430 May 2012

−

For Pending and Loading devices, the bulk operation is aborted.

−

For Saving History devices, the bulk operation is aborted after historization is completed.

Field Device Manager - R430 User's Guide Honeywell

249

4. FDM Operations 4.16. Bulk Operations

Step

Action Following are the different device status and their indications. Device status

Description

Pending

The device is not yet loaded.

Loading

The device is loading.

Saving History

The device is loaded and Save History for the device is in progress.

Note: For Bulk Offline Templates operation, device status displays as Saving Template Success

The device history is successfully saved.

Timed Out

The device is not loaded completely within the specified time out period..

Disconnected. Not Saved.

The device is disconnected from the Network. Although a device is disconnected, this status may not be shown for the device if it had succeeded or timed out before getting disconnected.

Load Failed

FDM Server failed to load the device.

Abort

Bulk operation is aborted.

Corrupt Template

The offline template generated for the device is corrupt.

Unknown Error

Bulk operation is failed for some of the devices due to internal error.

Device is in process active

Bulk operation is failed for devices connected in Experion network due to devices are process active.

8

Click Save Report to save the summary of bulk operation. The Save As dialog box appears.

9

Type the File name and click Save. The history records are saved in CSV format that contains Device name, Status, and Timestamp. The server notified errors also exported in CSV file if errors are received during bulk operation.

250

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.16 Bulk Operations

Saving Bulk Offline Templates To save the offline templates in bulk for the devices, perform the following steps. Step 1 2

Action Log on to the FDM Client. Choose Tools > Bulk Operations. The Bulk Operations dialog box appears.

3

Click Bulk Offline Templates.

REFERENCE – INTERNAL Refer to step 4 through 9 of Saving Bulk History to continue with saving offline templates in bulk.

Advanced Filter Advanced filter feature enables you to filter the nodes/devices displayed in the left tree view. Filters can be created based on the Network Type, Manufacturer Type, Device Type, and Device Tags. When a filter is applied, the Network View tree displays only those nodes/devices included in the filter. Note: By default no Advance Filter is applied, when you select the bulk operation. The Advanced Filter must be applied explicitly. To apply Advanced Filter, perform the following steps. Step

Action

1

Click Advanced Filter in the Bulk Operations dialog box.

2

From the Network drop-down list, select the configured network. Note: To select all the network types, select All.

3

From the Manufacturer drop-down list, select the manufacturer. Note: To include all the manufacturers, select All.

4

From the Device Type drop-down list, select the device type for the selected manufacturer. Note: To include all the device types, select All.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

251

4. FDM Operations 4.17. Import and Export Operations

Step

Action Device Tag is the tag name of the device that is displayed in the Network View tree. You can use the tag name to further filter the Advanced filter criteria. Type the tag name either fully or partially. (You can use wild card characters for searching such as ‘*’ and ‘?’) Example: To include devices with tag name containing STT25H, type *STT*. Example: To display devices starting with ‘S’ and ‘A’, you can enter *S*; *A*. This lists all devices matching the selected query criteria (Network Type, Network Configured, Manufacturer, and Device Type) that begin with S and/or A. For example, to display devices of type STT25H, type STT25H in the tag name.

ATTENTION Use semicolons to separate multiple tag names. 5

To view the devices included in the Advanced filter, click Select. The devices matching the selected filter criteria appear in the left tree view.

6

Click Select. Under Select Devices, the left network tree view is filtered according to the selected filter criteria. Right network tree view remains unaffected.

7

Click Reset to undo filtering. The filter on the tree view is removed. The selected device remains in right network view even after Reset.

252

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

4.17 Import and Export Operations Overview The database maintains information such as device tags, audit trail, offline configuration, and history records for each device and this information can be imported or exported using Import and Export feature. Using the Import and Export wizard the following four operations can be performed. •

Import – Export of Device Tags: It provides a feature to import tags from CSV and XML format. You can export tags in HTML, CSV, and XML format.

•

Import – Export of Audit Trail: It provides a feature to import audit trail records from XML format and export in CSV, HTML or XML format.

•

Import – Export of Offline Device Configuration: It provides a feature to import an offline configuration from CSV and FDM (.fdm) format. You can export in HTML, CSV, and FDM (.fdm) format.

•

Import – Export of Device History: It provides a feature to import history records from FDM (.fdm) format and export in CSV, XML, FDM (.fdm), and HTML.

Importing and Exporting Device Tags To export device tags in CSV, HTML or XML format, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears. 3

Click Export Data.

4

Click Device Tags in the list and then click Next. A dialog box appears prompting you to enter reason for the export action.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

253

4. FDM Operations 4.17. Import and Export Operations

Step

Action

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for exporting the device tag and then click OK. The following page appears.

6

The Query View enables you to filter the device tags based on the combination of Network Type, Configured Network, Protocol, Manufacturer, and Device Types. • To filter the device tags based on the Network type, select any Network

type and Configured network corresponding to that network. • To filter the device tags based on the protocol type, select any protocol

from the Protocol list.

254

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action • When you select a protocol from the list, the manufacturer list appears as

follows: −

If you select the HART protocol then the manufacturer list appears using available HART DD library information. For HART device that do not have a DD, the Unrecognized Manufacturers entry is available for the HART protocol. If the manufacturer is present in the DTM library then the device’s manufacturer appears as a separate manufacturer entry.

−

If you select a non-HART protocol then the manufacturer list appears using list of manufacturers from the DTM library. For non HART devices that do not have an entry in the DTM library, the Unrecognized Manufacturers entry is available in the list.

−

If you select multiple protocols then the corresponding manufacturers are listed under Manufacturers list.

• You can select device types from Device types list. The device types list

appears as follows: −

If you select HART manufacturers, then the device type appears using the HART DD library.

−

If you select non-HART manufacturers, then the device type appears using the DTM library information available.

−

If you select ‘Unrecognized manufacturers’ from the manufacturer list then the options available are the default ‘All’ option and ‘Unrecognized device types’.

• To filter the device tags of selected configured network(s) based on

Protocols, Manufacturers, and device types, select one or more Manufacturer(s) and Device Type(s). • To export all the devices tags, select All for all options in the Query View

and click Next.

ATTENTION If the FDT network discovers few devices that uses protocols which are not qualified in FDM, then you must select Unqualified Protocols in the Protocols list. Based on filter selection, select the device types to be displayed in the list. In the next page, you can export Connected devices, Disconnected Nodes, or All devices from the list. Corresponding device tags populates in the following box. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

255

4. FDM Operations 4.17. Import and Export Operations

Step

Action

7 Select the device tag and click List box.

to move it to the Selected Device Tag

Or Click

to move all the device tags to the Selected Device Tag List box.

TIP The number of device tags selected is listed in the right pane under Selected Device Tag List. 8

Click Next.

9

In the next page, select the file format to export the device tags and click Browse.

ATTENTION By default, the file location is: C:\ProgramData\Honeywell\FDM\Client\Export\Device Tags\ 10

Select the location to save the exported file. FDM populates the file location in the Save Exported File As box.

11

Click Export. In the next page, the progress report displays the progress in exporting the device tags and provides the following information. • Total number of devices succeeded, failed, and aborted. • The Operation state of the device tags exported.

ATTENTION During exporting device tags, status column does not display the status of individual device export. 12

Click Next. In the next page, the Summary Report displays the path of the record and status of the exported device tag.

13 256

Click Finish to close the wizard. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action You can open the exported device tag file from the path, which is displayed in the Summary Report. The following figure displays the device tag information, which is exported in HTML format.

The exported HTML file displays the Tag, NodeType, ManufacturerID, DeviceType, DeviceRev, DevTypeName, ManufacturerName, DeviceID, NodeId, and DeviceTag, ProtocolId, ProtocolName, and Release information. The Tag column corresponds to the tag in the Network View. The Device Tag column corresponds to the tag in the device.

To import device tags, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears.

ATTENTION You cannot import Experion Tags.

R430 May 2012

3

Click Import Data.

4

Click Device Tags in the list and click Next.

Field Device Manager - R430 User's Guide Honeywell

257

4. FDM Operations 4.17. Import and Export Operations

Step

Action A dialog box appears prompting you to enter reason for the import action.

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for importing the device tag and click OK.

6

In the next page, click Browse to select the file that you want to import. The Open dialog box appears.

7

Select the file to import and select the file format from the Files of type list.

8

Click Open. The location of the file appears in the Select Files box.

9

Click Import. In the next page, the progress report indicates the progress of importing the device tags and provides the following information. • The grid displays the selected file path and status of import operation. • Total number of devices succeeded, failed, and aborted. • The Operation state of the device tags imported.

10

Click Next. In the next page, the Summary Report displays the record name and status of the records.

11

258

Click Finish to close the wizard.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

ATTENTION •

In case you want to rename the tags in the exported CSV, ensure that you rename only in the Tag column and not in the Device Tag column.

•

It is recommended not to edit any other column in the exported file.

•

After import operation, tag for the devices which are not connected to a network configured on a particular FDM Server, appears under the Disconnected Nodes list.

Importing and Exporting Audit Trail records Audit trail records can be exported in XML, CSV or HTML format using Import – Export wizard or Audit Trail option from the View menu. To export audit trail records through Audit Trail option, perform the following steps. Step

Action

1

Choose View > Audit Trail. The Audit Trail page appears. For more information about how to view the audit trail records, refer to section Viewing Audit .

2

Click Export in the Audit Trail page after you receive the Audit Trail records. A dialog box appears prompting you to select the format (CSV, XML, HTML) in which you want to export.

Click the required format. 3

R430 May 2012

Export File Name & Location displays the name of the exported file and location where FDM saves the exported file. To change the name and/or location, click the button. Field Device Manager - R430 User's Guide Honeywell

259

4. FDM Operations 4.17. Import and Export Operations

Step

Action

4

In Save in box, choose the drive/ directory / sub-directory on your system, where you want to save the file.

5

Type the File name.

6

Click Save to save the file. The Export dialog box appears with the updated file name and location. Click OK. The file is exported to the selected location and a confirmation message appears as follows.

In addition, you can export the Audit Trail records through Import and Export option. To Export the Audit Trail records through Import and Export option, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears. 3

Click Export Data.

4

Click Audit Trail in the list and then click Next. A dialog box appears prompting you to enter reason for the export action.

260

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for exporting audit trail records and then click OK. The following page appears.

6

The Query View enables you to filter the audit trails based on the combination of Network Type, Configured Network, Protocol, Manufacturer and Device Type. • To filter the audit trail records based on the Network type, select any

Network type and Configured network corresponding to that network. • To filter the audit trail records based on the protocol type, select any

protocol from the Protocol list.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

261

4. FDM Operations 4.17. Import and Export Operations

Step

Action • When you select a protocol from the list, the manufacturer list appears as

follows: −

If you select the HART protocol then the manufacturer list appears using available HART DD library information. For HART device, that do not have a DD, the Unrecognized Manufacturers entry is available for the HART protocol. If the manufacturer is present in the DTM library then the device’s manufacturer appears as a separate manufacturer entry.

−

If you select a non-HART protocol then the manufacturer list appears using list of manufacturers from the DTM library. For non HART devices that do not have an entry in the DTM library, the Unrecognized Manufacturers entry is available in the list.

−

If you select multiple protocols then the corresponding manufacturers are listed under Manufacturers list.

• You can select device types from Device types list. The device types list

appears as follows: −

If you select HART manufacturers, then the device type appears using the HART DD library.

−

If you select non-HART manufacturers, then the device type appears using the DTM library information available.

−

If you select ‘Unrecognized manufacturers’ from the manufacturer list then the option available is the default ‘All’ option and ‘Unrecognized device types’.

• To export all the audit trail records, select All for all options in the Query

View and click Next.

ATTENTION If the FDT network discovers few devices that uses protocols which are not qualified in FDM, then you must select Unqualified Protocols in the Protocols list. The following page appears.

262

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

7

Action

Based on filter criteria, Device list lists all the devices that are online and disconnected. Select the required device from Device list. To export the Audit Trail for all devices, select All. Selection of audit trail data based on the Device list is as follows: • If devices are found, select All in the Device list and then select Export

Non-Device Specific Audit Trails check box. All audit trails of devices listed in the Device list and all non-device specific audit trails are exported. • If device list is empty, then select Export Non-Device Specific Audit

Trails check box. All non-device specific audit trails are exported. The User list all the users created in FDM. To view the audit trail for a particular user, select the user from User field. To view the audit trail for all users, select All.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

263

4. FDM Operations 4.17. Import and Export Operations

Step

Action Action Type drop-down list lists all the actions that are currently audited in FDM. For instance, Param Change indicates any change that you make to a parameter, logged in the Audit Trail. Select the required action types from Action Type. To view the Audit Trail for all parameters, select All.

8

If you select From and To dates using the calendar, the audit trail records of that particular period are exported.

9

Click Next.

ATTENTION If device list is empty and Export Non-Device Specific Audit Trails check box is not selected, and if you click Next, then the following message appears.

Click OK and select the Export Non-Device Specific Audit Trails check box to export all non-device specific audit trails. 10

In the next page, select the file format to export the audit trail records and click Browse.

ATTENTION By default, the file location is: C:\ProgramData\Honeywell\Fdm\Client\Export\Audit Trail\. 11

Click Export. In the next page, the progress report indicates the progress of exporting and provides the following information. • Total number of devices succeeded, failed, and aborted. • The Operation state of the audit trail records exported.

264

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step 12

Action Click Next. In the next page, the Summary report displays the record and status of the exported audit trail records.

ATTENTION During exporting of audit trail records, status column does not display the status of individual device export. 13

Click Finish to close the window.

To import audit trail records, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears. 3

Click Import Data.

4

Click Audit Trail in the list and then click Next. A dialog box appears prompting you to enter reason for the import action.

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for importing the audit trail records and then click OK.

6

In the next page, click Browse and select .xml files to import.

7

Click Open. The location of the file appears in the Select Files field.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

265

4. FDM Operations 4.17. Import and Export Operations

Step 8

Action Click Import. In the next page, the progress report indicates the progress in importing and provides the following information. • The grid displays the selected file path and status of import operation. • Total number of devices succeeded, failed, and aborted. • The Operation state of the audit trail data imported.

9

Click Next. In the next page, the Summary report displays the record and status of all audit trail files, which are selected for import.

10

Click Finish to close the wizard.

ATTENTION

266

•

Import of audit trail records automatically imports the tag of the particular audit trail record.

•

After import operation, tags for the devices which are not connected to a network configured on a particular FDM Server, appears under the Disconnected Nodes list.

•

If the audit trail is Device specific, then the exported Audit trail file contains corresponding Tag information along with audit trail data.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Importing and Exporting Offline Device Configuration FDM enables you to export DD/Generic DD offline configuration in the CSV, HTML, or FDM (.fdm) format. You can export DTM offline configuration only in FDM format. ATTENTION The FDM (.fdm) format is not editable. Therefore, you cannot edit DTM offline configuration after exporting.

To export DD/Generic DD offline configuration, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Click the Offline View. The Offline Configuration, Display Filter and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/ DTM Offline configurations tree appear in the left pane.

4

Browse through the tree DD Offline Configurations> Manufacturer > Device Type > Device Revision > Offline Configuration (name), right-click and then click Export. Or Browse through the tree Generic DD Offline Configurations> Generic Offline Configuration (name), right-click and then click Export. A dialog box appears prompting you to enter reason for the export action.

ATTENTION A reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for exporting offline configuration and then click OK. The following dialog box appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

267

4. FDM Operations 4.17. Import and Export Operations

Step

Action

Click OK.

ATTENTION If you try to export an old offline configuration that is migrated from previous releases, an appropriate message appears stating that you must upgrade the configuration before exporting.

Click Yes. FDM upgrades configuration and a confirmation message appears.

6 Click

to select the location where you want to save the file.

The Save As dialog box appears. 7

268

Select the location where you want to save the file and enter the name of the file in File name field.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step 8

Action Click Save. The Export dialog box appears with the name and location details populated in Export File Name & Location.

9

Click OK to export the file. The following message appears.

10

Click OK. FDM exports the file to the selected location.

In addition, you can export DD/Generic DD/DTM offline configuration through Import and Export option. To export DD/Generic DD/DTM offline configuration through Import and Export option, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears. 3

Click Export Data.

4

Click Offline Device Configuration in the list and then click Next. A dialog box appears prompting you to enter reason for the export action.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

269

4. FDM Operations 4.17. Import and Export Operations

Step

Action

5

Type the reason for exporting offline configuration and then click OK. The following page appears.

6

Select the offline configuration, which you want to export under Offline Library. • Click

to move it to the Selected Offline Templates box.

• Click

to move all the offline configurations.

• Click

to clear the offline configuration from the Selected Offline Templates box.

• Click

to clear all the offline configurations.

TIP The number of offline configuration selected are displayed under Selected Offline Templates : .

270

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

7

Click Next.

8

In the next page, select the file type for exporting and then click Browse.

ATTENTION By default, the file location is: C:\ProgramData\Honeywell\Fdm\Client\Export\Offline Templates\ 9

Select the folder where you want to save the offline configuration file and click OK. The file location appears in the File Location field.

10

If output file exists, perform any one of the following as necessary. Click Overwrite to replace the existing offline template with a new file, but with the same file name. Or Click Auto Rename to automatically rename the existing file and to create a new file. The new file name appears in the format of currentDateTimeStamp. Or Click Skip to skip the exporting the existing offline templates.

11

Click Export. In the next page, the progress report indicates the progress in exporting offline configuration and provides the following information. • The grid displays the individual offline template selected and their status. • Total number of devices succeeded, failed, and aborted. • The Operation state of the offline device configuration exported.

12

Click Next. In the next page, the Summary report displays the record and status of the offline configuration export operation.

ATTENTION If you click Skip in the Select File Location page, then exporting of the existing offline templates are skipped and status in the Summary report displays as Export skipped as per user setting. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

271

4. FDM Operations 4.17. Import and Export Operations

Step 13

Action Click Finish to close the wizard. The following figure displays the offline device configuration information which is exported in CSV format.

The CSV file displays the Id, Parameter Label, Parameter Value, WriteAcess, and Selected columns. The Selected column displays 0 and 1. If you want to edit CSV file before importing, change the value in Value column and variable 0 to 1 in the Selected column. The WriteAcess column displays the variables like READ_WRITE, READ_ONLY, WRITE_WITH_WARNING, and so on.

FDM enables you to import DD/Generic DD offline configuration in the CSV or FDM (.fdm) format. To import DD/Generic DD offline configuration, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

272

icon on the FDM tool bar. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action The Import and Export Wizard appears.

3

Click Import Data.

4

Click Offline Device Configuration in the list and then click Next. A dialog box appears prompting you to type the reason for the import action.

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for importing the offline configuration and click OK.

6

In the next page, click Browse. The Open dialog box appears.

7

Select the file or files to import and select the file format for import from the Files of type list and click Open. The location of the file appears in the Select Files box.

8

Click Import. In the next page, the progress report indicates the progress of importing and provides the following information. • The grid displays the selected file path and status of import operation. • Total number of devices succeeded, failed, and aborted. • The Operation state of the offline device configuration imported.

9

Click Next. In the next page, the Summary report displays the record and status of the imported offline configuration.

10

Click Finish to close the window. The imported offline configuration appears in the Offline View.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

273

4. FDM Operations 4.17. Import and Export Operations

Importing and Exporting Device history After viewing a history record, you can export the history in CSV, HTML, or FDM (.fdm) format. You can export a history record in the following two ways. •

Using Device Configuration page

•

Using the Import and Export option

To export a history record using device configuration page, perform the following steps. Step 1

Action Perform the steps 1 through 4 of the section Example for viewing Device History. The following page appears.

2

Under FDM Tasks, click Export. The following dialog box appears.

274

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

Click the required format. 3

The Export File Name & Location displays the name of the exported file and location where FDM saves the exported file. To change the name and/or location, click the

button.

The Save As dialog box appears. 4

Choose the drive/ directory/sub-directory on your computer, where you want to save the file.

5

The default file name appears in the File name box. To save the file with a different name, enter a new name in File name.

6

Click Save to save the file. The Export dialog box with the updated file name and location appears. Click OK in the dialog box. The file is exported to the selected location and the following message appears on the status bar.

7

R430 May 2012

Click Close.

Field Device Manager - R430 User's Guide Honeywell

275

4. FDM Operations 4.17. Import and Export Operations

To export the history records using the Import and Export option, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

A dialog box appears prompting you to type reason for the export action.

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 3

Type the reason for exporting device history and then click OK. The Import and Export Wizard appears.

ATTENTION The history records for DTM devices are exported in FDM (.fdm) format. 4

Click Device History in the list and then click Next. The following page appears.

276

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

5

The Query View enables you to filter the history records based on the combination of Network Type, Configured Network, Protocol, Manufacturer and Device Type. • To filter the history records based on the Network type, select any

Network type, and Configured network corresponding to that network. • To filter the history records based on the protocol type, select any

protocol from the Protocol list. • When you select a protocol from the list, the manufacturer list appears as

follows: −

R430 May 2012

If you select the HART protocol then the manufacturer list appears using available HART DD library information. For HART device that do not have a DD, the Unrecognized Manufacturers entry is available for the HART protocol. If the manufacturer is present in the DTM library then the device’s manufacturer appears as a separate manufacturer entry. Field Device Manager - R430 User's Guide Honeywell

277

4. FDM Operations 4.17. Import and Export Operations

Step

Action −

If you select a non-HART protocol then the manufacturer list appears using list of manufacturers from the DTM library. For non HART devices that do not have an entry in the DTM library, the Unrecognized Manufacturers entry is available in the list.

−

If you select multiple protocols then the corresponding manufacturers are listed under Manufacturers list.

• You can select device types from Device types list. The device types list

appears as follows: −

If you select HART manufacturers, then the device type appears using the HART DD library.

−

If you select non-HART manufacturers, then the device type appears using the DTM library information available.

−

If you select ‘Unrecognized manufacturers’ from the manufacturer list then the option available is the default ‘All’ option and ‘Unrecognized device types’.

• To export all the history records, select All for all options in the Query

View and click Next.

ATTENTION If the FDT network discovers few devices that uses protocols which are not qualified in FDM, then you must select Unqualified Protocols in the Protocols list. 6

Based on filter selection, select the types of devices to be displayed from the list. In the next page, you can export Connected devices, Disconnected Nodes, or All devices form the list. Corresponding device tags are populated in the Available Device Tags List box.

7 Select the device tag and click List box.

to move it to the Selected Device Tag

Or Click 8

278

to move all the device tags.

Click Next.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action

9

In the next page, click All records or Select Time Duration (From and To) and then click Next. • If you click All records, all the history records are exported. • If you click Select Time Duration (From and To), the history records of

that particular period are exported. 10

In the next page, select the file format in which you want to export the history record.

11

Click Browse and select the folder to save the exported file.

ATTENTION By default, the file location is: C:\ProgramData\Honeywell\Fdm\Client\Export\History Records\ 12

If output file exists, perform any one of the following as necessary. Click Overwrite to replace the existing file. Or Click Skip to skip the exporting the existing files.

13

Click Export.

In the next page, the progress report indicates the progress in exporting and provides the following information. • Total number of devices succeeded, failed, and aborted. • The Operation state of the device history data exported.

ATTENTION During exporting device history, the status column does not display the status of individual device history export. 14

Click Next. In the next page, the summary report displays the record and status of history records.

15

R430 May 2012

Click Finish to close the window.

Field Device Manager - R430 User's Guide Honeywell

279

4. FDM Operations 4.17. Import and Export Operations

FDM enables you to import history records in FDM (.fdm) format. To import history records, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Import and Export. Or Click

icon on the FDM tool bar.

The Import and Export Wizard appears. 3

Click Import Data.

4

Click Device History in the list and then click Next. A dialog box appears prompting you to enter reason for the import action.

ATTENTION The reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. For more information, refer to section Customizing the Audit Trail settings. 5

Type the reason for importing history records and then click OK.

6

In the next page, click Browse to select files that you want to import. The Open dialog box appears.

7

Select the .fdm files to import.

8

Click Open. The location of the file appears in the Select Files field.

9

Click Import. In the next page, the progress report indicates the progress of importing and provides the following information. • The grid displays the selected file path and status of import operation. • Total number of devices succeeded, failed, and aborted. • The Operation state of the device history imported.

10 280

Click Next. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.17 Import and Export Operations

Step

Action In the next page, the Summary report displays the overall status of the imported history records.

11

Click Finish to close the window.

ATTENTION

R430 May 2012

•

If the history record already exists in the database, the message History record already exists, is displayed in the summary report.

•

Import of device history automatically imports the tag of the particular device.

•

After import operation, tag for the devices, which are not connected to a network configured on a particular FDM Server, appears under the Disconnected Nodes list.

Field Device Manager - R430 User's Guide Honeywell

281

4. FDM Operations 4.18. Delete records

4.18 Delete records With FDM R430, you can delete the records such as device tags, offline device configuration, and history records for several devices at the same time using Delete Records feature.

Deleting Device Tags You can delete the disconnected device tags in following two ways. •

Using Delete Tag/Delete All option under Disconnected Nodes

•

Using Delete Records feature

To delete the device tags using Delete Tag/Delete All option under Disconnected Nodes, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Under Disconnected Nodes, right-click the device tag and then click Delete Tag. The following message appears.

Or Right-click Disconnected Nodes and then click Delete All. The following message appears.

282

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.18 Delete records

Step 3

Action Click Yes to delete the device tags from FDM along with device history records. Or Click No to delete the device tags from FDM. But, the device history records are retained.

To delete the disconnected device tags using Delete Records feature, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Delete Records. The Delete Records Wizard appears.

3

Click Device Tags in the list and then click Next. The following page appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

283

4. FDM Operations 4.18. Delete records

Step

4

Action

The Query View enables you to filter the device tags based on the combination of Protocol, Manufacturer, and Device Types. • To filter the device tags based on the protocol type, select any protocol

from the Protocol list. • When you select a protocol from the list, the manufacturer list appears as

follows:

284

−

If you select the HART protocol then the manufacturer list appears using available HART DD library information. For HART device that do not have a DD, the Unrecognized Manufacturers entry is available for the HART protocol. If the manufacturer is present in the DTM library then the device’s manufacturer appears as a separate manufacturer entry.

−

If you select a non-HART protocol then the manufacturer list appears using list of manufacturers from the DTM library. For non HART devices that do not have an entry in the DTM library, the Unrecognized Manufacturers entry is available in the list. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.18 Delete records

Step

Action −

If you select multiple protocols then the corresponding manufacturers are listed under Manufacturers list.

• When you select device types from Device Type list, the device types list

appears as follows: −

If you select HART manufacturers, then the device type appears using the HART DD library.

−

If you select non-HART manufacturers, then the device type appears using the DTM library information available.

• To filter the device tags based on Protocols, Manufacturers, and device

types, select one or more Manufacturer(s) and Device Type(s). • To delete all the devices tags, select All for all options in the Query view

and then click Next.

ATTENTION If the FDT network discovers few devices that uses protocols which are not qualified in FDM, then you must select Unqualified Protocols in the Protocols list. 5 Select the device tag and click List box.

to move it to the Selected Device Tags

Or to move all the device tags to the Selected Device Tag List box.

Click

TIP The number of device tags selected is listed in the right pane under Selected Device Tag List. 6

Click Next. If history data is not associated with the device tag, then a message appears to confirm the deletion of the selected device and then perform step 7. Or If any of the tag(s) selected for deletion have history data associated with them, then following page appears.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

285

4. FDM Operations 4.18. Delete records

Step

7

Action

a)

Under Select column, select the check box for which you want to delete the history data along with the device tag.

b)

Click Next. A message appears to confirm the deletion of the selected device tag along with history data and then perform step 7.

Click Delete. In the next page, the progress report displays the progress in deleting the device tags and provides the following information. • The grid displays the selected device tag and status of device tag deletion

operation. • Total number of device tags deletion operation succeeded, failed, and

aborted. • The Operation state of the device tags deleted.

8

Click Save Report. The Save As dialog box appears.

286

9

Enter the file name and then click Save.

10

Click Finish. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.18 Delete records

Deleting Offline Device Configuration You can delete the DD/Generic DD/DTM offline configuration in following two ways. •

Using Delete option under Offline Configuration in Offline View tab.

•

Using Delete Records feature

To delete the Offline Device Configuration using Delete option under Offline Configuration, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Click the Offline View. The Offline Configuration, Display Filter and Device Library tabs appear.

3

Click the Offline Configuration tab. The DD Offline Configurations/Generic DD Offline Configurations/ DTM Offline configurations tree appear in the left pane.

4

Browse through the tree DD Offline Configurations> Manufacturer > Device Type > Device Revision > Offline Configuration (name), right-click and then click Delete. Or Browse through the tree Generic DD Offline Configurations> Generic Offline Configuration (name), right-click and then click Delete. The following message appears.

5

R430 May 2012

Click Yes.

Field Device Manager - R430 User's Guide Honeywell

287

4. FDM Operations 4.18. Delete records

To delete DD/Generic DD/DTM offline configuration through Delete Records feature, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Delete Records. The Delete Records Wizard appears.

3

Click Offline Device Configuration in the list and then click Next. The following page appears.

4

288

Under Offline Library, select the offline configuration which you want to delete. • Click

to move it to the Selected Offline Templates box.

• Click

to move all the offline configurations. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.18 Delete records

Step

Action • Click

to clear the offline configuration from the Selected Offline Templates box.

• Click

to clear all the offline configurations.

TIP The number of offline configuration selected are displayed under Selected Offline Templates : . 5

Click Next. In the next page, a message appears to confirm the deletion of the selected offline device configuration.

6

Click Delete. In the next page, the progress report indicates the progress in deleting offline configuration and provides the following information. • The grid displays the individual offline template selected and status. • Total number of operations succeeded, failed, and aborted. • The Operation state of the offline device configuration deleted.

7

Click Save Report. The Save As dialog box appears.

8

Enter the file name and then click Save.

9

Click Finish.

Deleting Device history You can delete device history records in the following two ways. •

Using Delete History option from the shortcut menu

•

Using the Delete Records feature

To delete a history record using Delete History option, perform the following steps.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

289

4. FDM Operations 4.18. Delete records

Step

Action

1

Log on to the FDM Client.

2

Click the Online View. The Network View and Device State View tabs appear.

3

Click the Network View tab. The devices belonging to the connected server are displayed.

4

Right-click the device and then click Delete History. The History Records dialog box appears.

5

Select the check box to delete the device history record. If you want to delete all history records at a time, select Select All check box.

6

Click OK. The confirmation message appears before you delete the history records.

7

Click Yes. The historized data for the selected device is deleted.

To delete the history records using the Delete Records feature, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Delete Records. The Delete Records Wizard appears.

3

Click Device History in the list and then click Next. The following page appears.

290

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.18 Delete records

Step

Action

4

The Query View enables you to filter the history records based on the combination of Network Type, Configured Network, Protocol, Manufacturer and Device Type. • To filter the history records based on the Network type, select any

Network type, and Configured network corresponding to that network. • To filter the history records based on the protocol type, select any

protocol from the Protocol list. • When you select a protocol from the list, the manufacturer list appears as

follows: −

R430 May 2012

If you select the HART protocol then the manufacturer list appears using available HART DD library information. For HART device that do not have a DD, the Unrecognized Manufacturers entry is available for the HART protocol. If the manufacturer is present in the DTM library then the device’s manufacturer appears as a separate manufacturer entry.

Field Device Manager - R430 User's Guide Honeywell

291

4. FDM Operations 4.18. Delete records

Step

Action −

If you select a non-HART protocol then the manufacturer list appears using list of manufacturers from the DTM library. For non HART devices that do not have an entry in the DTM library, the Unrecognized Manufacturers entry is available in the list.

−

If you select multiple protocols then the corresponding manufacturers are listed under Manufacturers list.

• You can select device types from Device Type list. The device types list

appears as follows: −

If you select HART manufacturers, then the device type appears using the HART DD library.

−

If you select non-HART manufacturers, then the device type appears using the DTM library information available.

−

If you select ‘Unrecognized manufacturers’ from the manufacturer list then the option available is the default ‘All’ option and ‘Unrecognized device types’.

• To delete all the history records, select All for all options in the Query

View and click Next.

ATTENTION •

If the FDT network discovers few devices that uses protocols which are not qualified in FDM, then you must select Unqualified Protocols in the Protocols list.

•

If you delete device tags and retain history records of these devices in the database, then these records are termed as Orphan records. To delete these orphan records, select Show Orphan Records check box.

In the next page, you can select device tags for connected devices, disconnected Nodes, or for all devices form the list. Corresponding device tags are populated in the Available Device Tags List box. 5 Select the device tag and click List box.

to move it to the Selected Device Tag

Or Click 6 292

to move all the device tags.

Click Next. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.19 Using dashboard

Step

Action

7

In the next page, click All records or Select Time Duration (From and To) and then click Next. • If you click All records, all the history records are deleted. • If you click Select Time Duration (From and To), the history records of

that particular period are deleted. 8

In the next page, select the check box to delete history record and then click Next. In the next page, a message appears to confirm the deletion of the device history records.

9

Click Delete. In the next page, the progress report displays the progress in deleting the history records and provides the following information. • The grid displays the selected device history record name and status of

device history record deletion operation. • Total number of device history records deletion operation succeeded,

failed, and aborted. • The operation state of the device history data deleted.

10

Click Save Report. The Save As dialog box appears.

R430 May 2012

11

Enter the file name and then click Save.

12

Click Finish.

Field Device Manager - R430 User's Guide Honeywell

293

4. FDM Operations 4.19. Using dashboard

4.19 Using dashboard Overview The FDM Server maintains various types of information related to the FDM Client, devices, RCIs, gateways, networks and operations. The FDM Client does not display all types of information that FDM Server maintains. Using Dashboard feature, you can view all these types of information at a single place and provides quick and easy access to it. You can view the following information. •

Tags Information

•

Devices Information

•

Clients Information

•

Loaded Devices Information

•

Network Information

•

Gateways Information

•

Operations Information

•

License Usage Information

You can refresh the information displayed in the dashboard by fetching the latest data from the FDM Server and save the dashboard report in HTML format.

Review Information To review the information, perform the following steps. Step

Action

1

Log on to FDM Client.

2

Click View > Dashboard. Or In the Network View list under Online View, right-click the required RCI or Network node and click Dashboard. Once the data is fetched from the FDM Server, the details appear on the Dashboard page depending on the location from where it is launched.

294

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.19 Using dashboard

Step

Action The following Dashboard page appears when launched through the View menu.

ATTENTION •

If dashboard is launched through the View menu, then the Summary tab is displayed.

•

If Dashboard is launched through the context menu of RCI or network node, then the Summary tab and the Network Information tab are displayed.

After data is fetched from the server, the message appears Dashboard Loaded Successfully on the status bar of the Dashboard page. The Summary page displays the following details. • Tags: It shows the total number of online and disconnected tags. • Devices: It shows the total number of healthy, unhealthy and disconnected

devices. • Clients Running: It shows the total number of clients running at various

locations. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

295

4. FDM Operations 4.19. Using dashboard

Step

Action • RCIs Configured: It shows the total number of RCI servers configured. • Devices Loaded: It shows the total number of devices loaded across all

the clients. • Gateways Configured: It shows the total number of gateways configured. • Current Ongoing Tasks: It shows the total number of tasks going-on

across all the clients. • License Usage: It shows the total number of licenses available for a

particular entity and the number of licenses that are currently in use. 3

Under Tags, you can view the total number of online and disconnected tags.

4

Under Devices, you can view the total number of healthy, unhealthy and disconnected devices.

5

Under Clients, click the link for Clients Running. The Clients Information page appears. It displays the following information for each client. • The machine name on which the client is running. • The user who has launched the client. • Client Type and Client ID.

6

Under Network, click the link for RCI’s Configured. The Network Information page appears.

296

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.19 Using dashboard

Step

Action

The Network Information page displays the machine name on which RCI is configured, total number of online tags, disconnected tags, healthy devices, unhealthy devices, mux monitored devices, and currently loaded devices. Click to view the details of the network interface configured on the RCI as shown in the below figure.

Click to view the details of the configured network as shown in the below figure.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

297

4. FDM Operations 4.19. Using dashboard

Step

Action

ATTENTION If any information related to configured network is not applicable, then value displays as -NA-. 7

Under Loaded Devices, click the link for Device Loaded. The Loaded Devices Information page appears.

The Loaded Devices Information page displays the device name, manufacturer name, device type, device revision, DD revision, loaded With DD or DTM (Offline/Online), RCI name, network name, and name of the machine which has locked the device. Click to view the following information. • Machine name on which the device is loaded. • User who has launched the client. • Client type

298

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.19 Using dashboard

Step

Action

ATTENTION If you want to refresh the dashboard data, click which is present in the upper-right corner of the Dashboard page. The following message appears.

Click OK to refresh the data. 8

Under Gateways, click the link for Gateways Configured. The Gateways Information page appears. The Gateways Information page displays the Experion Server name, gateway host name, gateway name, total number of monitored devices, active devices, and inactive devices.

9

Under Tasks, click the link for Current Ongoing Tasks. The Operations Information page appears.

The Operations Information page displays the details of each operation that is currently running in any of the clients. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

299

4. FDM Operations 4.19. Using dashboard

Step

Action Click

to view the following information.

• Machine name on which the operation is going on. • User who has launched the client. • Client type and Client ID.

10

Under Licenses, click the link for License Usage. The License Information page appears. It displays the following information. • The licensed entity name. • The number of licenses for the corresponding entity. • The number of licenses currently in use for the corresponding entity.

11

To save the dashboard report, click corner of the Dashboard page.

that is present in the upper-right

ATTENTION The Save Report icon appears shaded if a dashboard Refresh operation is in progress.

300

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.20 Using display filters

4.20 Using display filters Overview The display filter feature enables you to filter the nodes/devices displayed in the Online View > Network View tree. Filters can be created based on Network Type, Manufacturer Type, Device Type, Configured Networks, Protocol, and Device Tags. When a filter is applied, the Network View tree displays only those nodes/devices included in the filter. You can create a display filter in the following two ways. •

Query View - Enables you to create a display filter when you select appropriate values for Network Type, Network Configured, Protocol, Manufacturer, Device Type and Tag Name.

•

Device View - Enables you to create a display filter by selecting the required nodes/ devices from the list of Available Devices, and moving them to Selected Devices. ATTENTION To create a display filter from Query View, the selected devices need not be connected and online, they may be disconnected devices as well. However, to create a display filter from Device View, only online devices can be included.

Creating a Display Filter from the Query View Creating a display filter from the Query View involves selecting one or more values for the following fields. •

Network Type

•

Network Configured

•

Protocol

•

Manufacturer

•

Device Type

•

Tag Name

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

301

4. FDM Operations 4.20. Using display filters

To create a display filter from the Query View, perform the following steps. Step 1

Action Click the Offline View group. The Offline Configuration, Display Filter and Device Library tabs appear.

2

Click the DisplayFilter tab.

3

Right-click the Display Filter and then click New. The following page appears.

4

Select the network type from Network Type list. To select all the network types, select All. When you select the network type, the networks configured for the selected network type appears in Network Configured drop-down list.

302

5

Select the desired network configuration from Network Configured dropdown list.

6

Select the desired protocol from Protocol list. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.20 Using display filters

Step 7

Action Select the manufacturer from Manufacturer drop-down list. To include all the manufacturers, select All.

8

Select the device type from Device Type drop-down list. To include all the device types, select All.

9

Tag Name is the name of the device that is displayed in the Network View tree in the left pane of FDM. You can use the tag name to further filter your display filter criteria. Type the tag name either fully or partially. To type partially, use ‘*’. Example: To include devices with tag name containing STT25H, type *STT*. Example: To display devices starting with ‘S’ and ‘A’, you can type *S*; *A*. This lists all devices matching the selected query criteria (Network Type, Network Configured, Protocol, Manufacturer, and Device Type) that begin with S and/or A. For instance, to display devices of type STT25H, type STT25H in the tag name.

ATTENTION

10

•

Use semicolons to separate multiple tag names.

•

Use Device View filter to filter devices that do not have DD(s).

To view the devices included in the display filter, click View. The devices corresponding to the selected filter criteria appear.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

303

4. FDM Operations 4.20. Using display filters

Step 11

Action Click Save to save the display filter. To close the window without saving the changes, click Close.

ATTENTION You can Save a display filter, without viewing (performing step 10) the details of the display filter. 12

If you click Save, a dialog box appears prompting you to type the reason for saving display filter. Type the reason for creating the new filter and click OK.

ATTENTION The Reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. 13

The Filter Name dialog box appears. Type the name for the display filter in Name and click OK. FDM saves the display filter with the specified name and displays the filter in the Display Filter tree in the left pane.

TIP •

To open the display filter browse through the Display Filter tree, right-click the display filter you want to open and click Open.

•

To modify you can re-select the Display Filter criteria in the Query View or re-select the nodes/devices in the Device View.

•

To rename the display filter browse through the Display Filter tree, right-click the display filter you want to rename and click Rename.

•

To delete the display filter browse through the Display Filter tree, and right-click the display filter you want to delete and click Delete.

ATTENTION FDM does not allow you to rename and delete a display filter, if the display filter has been applied to the Network View tree in the Online View group or if the display filter is open in any FDM Client.

304

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.20 Using display filters

Creating a Display Filter from the Device View Creating a display filter from the Device View involves selecting one or more nodes/devices that you want to be displayed in the Network View list. To create a display filter using the Device View, perform the following steps. Step 1

Action Click the Offline View group. The Offline Configuration, Display Filter, and Device Library tabs appear.

2 3

Click the Display Filter tab. Right-click the Display Filter and click New. The Display Filter page appears.

4

R430 May 2012

Click the Device View tab.

Field Device Manager - R430 User's Guide Honeywell

305

4. FDM Operations 4.20. Using display filters

Step 5

Action The online devices connected to FDM in Available Devices appear. Select the desired network node(s)/ device(s) using the following buttons. To select all nodes/devices in the network (under Available Devices) and move them to Selected Devices, click this button. To select a single node/device (under Available Devices) and move it to Selected Devices, click this button. To remove a single node from Selected Devices, click this button. To remove all the nodes from Selected Devices, click this button.

ATTENTION You must select at least one device for creating a display filter from the Device View. 6

Click Save. The Reason dialog box appears. Type the reason for creating the new filter. The Filter Name dialog box appears.

ATTENTION The Reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings. 7

Type the name for the display filter and click OK. FDM saves the display filter with the specified name and displays it in the Display Filter tree.

306

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.20 Using display filters

Applying a Display Filter After creating a display filter from the Offline View, you can go to the Online View and apply the filter. To apply a filter, perform the following steps. Step

Action

1

In the FDM Client, choose the display filter from the Display Filter drop-down list.

2

Click Apply. FDM applies the display filter and displays only those nodes/devices included in the selected Display Filter.

ATTENTION If none of the network nodes/devices that are included in the display filter is online and connected to FDM, then the Network View appears blank and does not display any device. 3

R430 May 2012

To remove an applied filter, choose the No Filter option from Display Filter and click Apply.

Field Device Manager - R430 User's Guide Honeywell

307

4. FDM Operations 4.21. Using advanced search

4.21 Using advanced search FDM provides an advanced search feature to find the required devices listed under the FDM Server. Choose Tools > Advanced Search to use this feature. To search for a device, you can use any of the following independently, or as a combination. •

Protocol indicates the type of devices which can be HART, FF or PROFIBUS.

•

Manufacturer ID indicates the unique ID for each HART Device manufacturer.

•

Device Type indicates the type of device — for instance, the device can be a pressure transmitter, temperature transmitter or flow transmitter. Device Tag indicates the tag as configured for the device. It can be alphanumeric string of length 8 characters.

•

FDM Tag is the tag displayed for a device in the Network View tree.

Example: If you want to search for an STT25H temperature transmitter manufactured by Honeywell, perform the following: 1.

Select HART protocol from the Protocol list.

2.

Select the Honeywell_23 from the Manufacturer ID list

3.

‘Select the device type for the STT25H from Device Type list.

4.

Click Search. FDM lists all the STT25H devices configured in the network. TIP To broaden your search results, restrict your search criteria to a few fields.

Based on the search result, the device names are listed. When you double-click the device, it is displayed in the Network View tree, if the device is online. To search the required devices listed under the FDM Server, perform the following steps.

308

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.21 Using advanced search

Step 1

Action Choose Tools > Advanced Search. The Advanced Search page appears.

TIP You can also click the Advanced Search icon under the FDM tool bar. 2

To search by protocol, select an appropriate value in Protocol. AND/OR To search by manufacturer ID, select an appropriate value in Manufacturer ID. AND/OR To search by device type, select an appropriate value in Device Type. AND/OR To search by device tag, type an appropriate value in Device Tag. AND/OR To search by FDM tag, type an appropriate value in FDM Tag.

3

Click Search. If a device matching the search criteria you have entered is found, it displays the search results in the Search Result pane.

4

Double-click the required device. FDM locates the device in the Network View tree, provided the device is online.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

309

4. FDM Operations 4.22. Device access control

4.22 Device access control Overview Device lock is a feature used for locking devices from being accessed by multiple users. When a device loaded with DD is locked, the device is in read-only mode. This means that the user can view the device configuration but cannot modify it. When a device loaded with DTM is locked, you cannot open the device configuration page.

Explicit locking FDM allows you to lock or unlock a device manually, when required. When device is explicitly locked, users cannot modify the device configuration, not even the user who locked it. To lock the device, perform the following steps. Step

Action

1

Select the device tag from the Online View > Network View tree.

2

Right-click the device and then click Lock. The lock icon appears for the device in the Network View as follows:

310

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

Step

R430 May 2012

Action

Field Device Manager - R430 User's Guide Honeywell

311

4. FDM Operations 4.22. Device access control

Step

Action

3 Subsequently, when you select Device Configuration, the lock on the upper-right corner of the window.

appears

The lock status can also be viewed by selecting QuickView from the context menu of the device. If you want to lock all devices simultaneously, right-click the network and then click Lock All. If the Prompt User for Device Unlock Password feature is enabled, then you are prompted to enter the password.

Implicit Locking Implicit locking occurs in the following three ways. ATTENTION

•

312

•

Implicit locking is not available for FF devices.

•

Implicit lock cannot be removed by performing an explicit unlock on the device and the system continues to display the Implicit lock icon on the upper-right corner of the window.

FDM tool provides implicit access locking of device when more than one user accesses the same device concurrently. When the first user accesses the device, the device is locked for all subsequent users, and are provided read-only access. In addition, there is a lock icon displayed the upper-right corner of the device configuration page to indicate that another user has already opened the selected device.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

The following is the example scenario for Implicit Locking when multiple users access the same device. Step

R430 May 2012

Action

1

User A accesses the device, EJA_F10 to perform a necessary task.

2

When the User B tries to access the same device, EJA_F10, the lock icon appears for the device in Network View as follows:

Field Device Manager - R430 User's Guide Honeywell

313

4. FDM Operations 4.22. Device access control

Step

314

Action

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

Step

Action Subsequently, when you select Device Configuration, the lock appears on the upper-right corner of the window.

icon

And also, to see the lock status, right-click the device and then click QuickView from the shortcut menu. When locked, you can only view the device data, but cannot edit them. 3

When User A closes the device, a notification message appears to User B of the device in Notifications pane under Information tab. This indicates that the User B can edit the device data.

ATTENTION If there are more than two users trying to access the device, the access to the device is granted in the order in which the users load the device. For instance, if three users A, B and C try to load the device one after another, the device is locked for B and C when A loads the device. When A unloads the device, the access is granted to B and when B unloads the device, the access is granted to C. •

Process Lock When devices are connected through Experion, devices that are in process are implicitly locked. ATTENTION •

When FDM is connected to the field devices through the Experion interface through the PM HART IO or the Series C I/O module, devices that are in process are locked by default. To edit any device parameter or run a method, you need to inactivate the device.

•

When FDM is connected to field devices through the Experion interface through the 1756 HART IO module, the channel mode needs to be changed to ‘OFF CONTROL’.

•

Process locked devices can also be unlocked by enabling the setting “Allow Write Access for Process Active Devices”.

Safety Lock is a lock initiated by Safety System to prohibit any configuration of Safety Devices from FDM. Safety Lock/Unlock happens at Safety Builder and the device lock state is modified accordingly in FDM Network View for that device. And also, to see the lock status, right-click the device and then click QuickView from the shortcut menu.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

315

4. FDM Operations 4.22. Device access control

Subsequently, when you open Device Configuration page, the lock the upper-right corner of the window.

316

Field Device Manager - R430 User's Guide Honeywell

icon appears on

R430 May 2012

4 FDM Operations 4.22 Device access control

ATTENTION Devices connected to SM controllers have a safety lock by default. You can load those devices in read-only mode only with the DD. You cannot open the device configuration pages with DTM for safety locked devices. •

FHM Lock: when a device is in use byFDM HART Multiplexer, the device is locked and not available for use elsewhere in FDM. This is termed as an FHM lock in FDM. Ensure to consider the following while using FHM. −

When the device is explicitly locked, it cannot be used with FHM.

−

When a device is used by one instance of FHM it cannot be used by FHM on another client.

−

When a device has an exclusive lock on it, only the FHM on the client that has received exclusive access can use it.

Exclusive access FDM provides the exclusive read/write access to the device which is unlocked in one FDM Client. However, in multi-client scenarios, the same device remains exclusive locked in other clients. The following is the example scenario for Exclusive Locking when two clients are connected to single FDM Server. Step

Action

1

Open two Clients which are connected to single FDM Server.

2

In Client-1, choose FDM > Settings. The Settings dialog box appears.

3

Under Device Lock, select Exclusive Access to Unlocked devices check box.

4

Click Apply and the click OK.

5

In Client-1, right-click the device and then click Unlock from the shortcut menu. If the Prompt User for Device Unlock Password feature is enabled, then you are prompted to enter the password to Unlock the device.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

317

4. FDM Operations 4.22. Device access control

Step

Action

6

A similar device in Client-2 is in Exclusive lock state and lock icon appears for the same device in Network View as follows:

And also, to see the lock status, right-click the device and then click QuickView from the shortcut menu. Subsequently, when you open Device Configuration page, the lock icon appears on the upper-right corner of the window. For the device which is in Exclusive lock state, you do not have Lock/Unlock option in the shortcut menu. You need to lock the device explicitly in Client-1 (where the device is unlocked exclusively) and then Lock/Unlock option appears in the shortcut menu for the device in Client-2.

318

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

For more information about how to lock and unlock HART channels connected to Universal Safe Modules, refer to Safety Builder User’s Guide.

Unlocking a device You can unlock an explicitly locked device, process active device and FHM locked device. Unlocking an explicitly locked device To unlock the device, right-click the device under Network View and click Unlock. A message appears confirming that write-protection is removed on the device in Notifications pane. This process immediately unlocks a device and provides write access to the user even if the device configuration is open. And also, you can unlock an explicitly locked device by clicking Lock icon from the device configuration page. Unlocking a process active device You can unlock process active device by following three ways. •

By enabling Pass Through setting: This is applicable when FDM is connected to the field devices through the Experion interface through the 1756 HART I/O, PM HART I/O module or the Series C I/O module. In such cases, when you access the devices that are in process, the device appears as locked. To edit any device parameter or run a method, you need to inactivate the device or enable the pass through setting in FDM.

•

Unlocking device connected through 1756 HART IO: To modify the device configuration when connected through 1756 HART IO, you need to first change the state of the device to off-process. This can be done through the Control Builder, in the following two ways. −

Changing the state of the device block to OFFCONTROL.

−

Changing the state of the IO Module to INACTIVE. ATTENTION

R430 May 2012

•

If you change the state of the device block to OFFCONTROL, only the specific device becomes inactive.

•

If you inactivate the IO Module, all the devices connected to the IO module go off-process.

Field Device Manager - R430 User's Guide Honeywell

319

4. FDM Operations 4.22. Device access control

To change the state of a device connected through 1756 HART IO to off-process, by changing the state of the device block to OFFCONTROL, perform the following steps. Step

Action

1

From the Experion Control Builder, select the required device.

2

Right-click the device and click Configure Module Parameters.

3

On the Main tab, select the value for Normal/Off-Control as OFFCONTROL.

The following message appears.

320

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

Step 4

Action Click Yes to change the mode. This action brings the device out of process and you can edit the configuration using FDM. A message appears confirming that write-protection is removed on the device.

ATTENTION After you finish editing the configuration using the FDM Client, repeat Steps 1 through 3 to restore the device state back to NORMAL.

To change the state of a device connected through 1756 HART IO to INACTIVE through the IO Module in the Experion Control Builder, perform the following steps. Step

R430 May 2012

Action

1

From the Experion Control Builder, select the required IO Module.

2

Right-click the IO module and click Configure Module Parameters.

Field Device Manager - R430 User's Guide Honeywell

321

4. FDM Operations 4.22. Device access control

Step

Action

3

Click the Module Configuration tab.

4

In the Execution State drop-down list, click INACTIVATE.

The following message appears.

5

Click Yes to change the state of the device block. This action brings the device off process and you can edit the configuration using FDM. A message appears confirming that write-protection is removed on the device.

322

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

Step

Action

ATTENTION After you, finish editing your configuration using the FDM Client, repeat step 3 to set the value of the field Execution State back to ACTIVE. •

Unlocking devices connected through PM HART I/O or Series C: To modify the device configuration when connected through PM HART IO/Series C I/O, you need to first change the state of the device to off-process. This can be done through the Control Builder, in the following two ways. −

By changing the state of the device block to INACTIVE.

−

By changing the state of the IO Module to INACTIVE. ATTENTION •

If you inactivate the Device Block, only the specific device becomes inactive.

•

If you change the state of the IO Module to INACTIVE, all the devices connected to the IO module goes off-process.

To change the state of a device connected through PM HART IO/Series C I/O to offprocess by changing the state of the Device Block to INACTIVE, perform the following steps. Step

R430 May 2012

Action

1

From the Experion Control Builder, select the required device.

2

Right-click the device and choose Inactivate > Selected Item(s).

Field Device Manager - R430 User's Guide Honeywell

323

4. FDM Operations 4.22. Device access control

Step

Action

The Change State dialog box appears. 3

Click Yes to make the device block inactive. This action brings the device out of process and you can edit the configuration using FDM. A message appears confirming that write-protection has been removed on the device.

4

After you finish editing the configuration using FDM, in Control Builder, select the device, right-click and choose Activate > Selected Item(s). The Change State dialog box displays the message Set Selected object(s) Active? Click Yes to activate the device block.

324

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.22 Device access control

To change the state of a device connected through PM HART I/O/Series C I/O, to offprocess by changing the state of the IO Module to INACTIVE, perform the following steps. Step

Action

1

From the Experion Control Builder, select the required IO Module.

2

Right-click the IO module and choose Inactivate > Selected Item(s).

The Change State dialog box appears. 3

Click Yes to change the IO Module to inactive state. This action brings the device out of process and you can edit the configuration using FDM. A message appears confirming that write-protection is removed on the device.

4

After you finish editing the configuration using FDM, in Control Builder, select the device, right-click and choose Activate > Selected Item(s). The Change State dialog box displays the message Set Selected object(s) Active? Click Yes to activate the IO Module.

Unlocking an exclusively locked device You can unlock the device in the following scenarios. •

When you lock the device explicitly in client using Lock option in shortcut menu.

•

When Automatically lock devices ____ Minutes check box is selected in the Settings dialog box.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

325

4. FDM Operations 4.22. Device access control

•

When you close the client which is unlocked.

•

When devices are disconnected or RCI is down.

Unlocking FHM locked device To unlock FHM, click Stop button in the FDM HART Multiplexer form.

Lock All/Unlock All Using this feature, you can lock or unlock all devices that are connected to a network. •

If you want to lock/unlock all devices simultaneously, right-click the network and then click Lock All/ Unlock All. If the Prompt User for Device Unlock Password feature is enabled, then you are prompted to enter the password. ATTENTION •

The Lock All/Unlock All feature is a convenience option provided, so that you need not perform individually lock/unlock of devices in the network. There is no explicit lock/unlock state applied to the network when this feature is used. Due to this, it is possible to unlock any device under a network on which you have performed a lock all or lock a device under a network on which you have performed an unlock all.

•

The autolock feature is applicable to the devices under a network that are unlocked using the Unlock all feature.

•

When device is in Exclusive lock state, if you perform Lock All operation, then it overwrites the Exclusive lock state. Unlock All operation (overrides the Exclusive Lock, if there is any) unlock the devices under that Network and provides Read-Write access to all the Clients.

326

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.23 Working with device documentation

4.23 Working with device documentation Overview FDM enables Administrators, Engineers, and Supervisors to attach device documents for a device instance, device type or at the system level (applicable to all devices across FDM) in any chosen document format. These documents can have information related to the specific device instance, device type or system level information. ATTENTION Attaching documents at Device type level is applicable only to the DD library. You cannot attach documents to the DTM library.

Device documentation can be maintained at following three levels. •

Device Instance Level - Device documentation for a specific device instance can be attached/detached/opened/modified/uploaded from the Online View > Network View tab. The document is associated only with device instance.

•

Device Type level - Device documentation for a Device Type can be attached/detached/opened/modified/uploaded from the Offline View > Device Library tab. The document is associated with all the devices of that type.

•

System level – Device documentation can be attached/detached/opened/modified from the Tools > Systems Documents menu. The document is associated with the FDM application. Task

To achieve, perform the following

Attaching document

Uploading document

Detaching document

R430 May 2012

a)

Choose Offline View > Device Library > DD Library.

b)

Right-click Device Revision No and choose Device Documentation > Attach Document.

a)

Choose Offline View > Device Library > DD Library.

b)

Right-click Device Revision No and choose Device Documentation > Upload Document.

a)

Choose Offline View > Device Library > DD Library.

b)

Right-click Device Revision No and choose Device Documentation > Detach Document.

Field Device Manager - R430 User's Guide Honeywell

327

4. FDM Operations 4.23. Working with device documentation

Attaching device documentation at Device-type level To attach device documentation at the Device-type level perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Under Offline View, click the Device Library tab.

3

Browse through the DD Library tree and expand the network tree corresponding to the Device Type.

4

Select a Device Revision No.

5

Right-click and choose Device Documentation > Attach Document.

ATTENTION The Reason dialog box appears, only if the Administrator has enabled reason logging for this action type in the Audit Trail settings. 6

Type the reason and click OK. The Open dialog box appears.

7

Browse through your computer and locate the folder where you have saved the document.

8

Select the document and click Open. FDM attaches the document to the specific device type and a confirmation message appears.

9

To crosscheck if the document is attached, browse through the Device Library. Expand Manufacturer > Device Type > Device Revision No. Right-click the device revision no to which you have attached the document and click Device Documentation. The name of the attached document appears as a submenu under Device Documentation.

ATTENTION Device Documentation attached at the Device Type level can also be opened, modified, and uploaded at the Device Instance level.

328

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.23 Working with device documentation

ATTENTION •

Two documents of the same type (.xls or .csv) attached to the devicetype level cannot be opened at the same time. Close the first document and then open the second document of the same type.

•

Any modification that you make after opening an attached document is only saved in the local version of the device document on the FDM Client. It is not updated onto the FDM Server, until you upload the document with the changes.

•

Ensure that the document you want to detach is closed. FDM does not allow you to detach an open document.

Attaching device documentation at Device instance level To attach device documentation at the Device instance level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

From the Online View, click the Network View tab.

3

Browse through the network.

4

Right-click a device and choose Device Documentation > Attach Document.

5

The Open dialog box appears.

6

Browse through your computer and locate the folder where you have saved the document.

7

Select the document and click Open. FDM attaches the document to the specific device and a confirmation message appears.

8

To crosscheck whether the document has been attached, browse through the Network View, select the device, right-click and click Device Documentation. The name of the attached document appears as a submenu under Device Documentation.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

329

4. FDM Operations 4.23. Working with device documentation

Step

Action

ATTENTION •

The two documents of the same type (.xls or .csv) attached to the device instance level cannot be opened at the same time. Close the first document and then open the second document of the same type.

•

Any modification that you make after opening an attached document is only saved in the local version of the device document on the FDM Client. It is not updated on the FDM Server, until you upload the document with the changes.

•

Documents attached at the device instance level can also be opened, modified, and uploaded from the device type level.

Attaching device documentation at System level To attach device documentation at the Device level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > System Documents > Attach Document. The Open dialog box appears.

3

Select the document that you want to attach and click Open. FDM attaches the document at the system level and a confirmation message appears.

4

Click OK.

ATTENTION

330

•

The two documents of the same type (.xls or .csv) attached to the system level cannot be opened at the same time. Close the first document and then open the second document of the same type.

•

If another document of the same type as the attached document is open in your system, FDM does not allow you to open the attached document. An appropriate message appears.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.23 Working with device documentation

Step

Action

−

Close the document of the same type as the attached document and then retry opening the attached document.

•

Ensure that you upload the document(s) that you modify. If you do not upload, the changes to the document(s) are lost when you close the FDM Client.

•

Documents attached at the System Level, can only be detached from the System Level and not from the device level.

Uploading an updated document If you open a device document attached at the Device Type level and modify it, you must ensure that it is uploaded onto the FDM Server, so that the changes are updated in FDM and the modified document(s) are available to all users. You can upload a modified document at the device type, device instance, and system level. For example, to upload a modified document at Device Type level onto the FDM Server, perform the following steps. Step

R430 May 2012

Action

1

Log on to the FDM Client.

2

Under Offline View, click the Device Library tab.

3

Browse through the Device Library tree.

4

Expand the Manufacturer > Device Type > Device Revision No. Right-click the device revision no to which you have attached the document and choose Device Documentation> Upload Document.

Field Device Manager - R430 User's Guide Honeywell

331

4. FDM Operations 4.23. Working with device documentation

Step

Action

ATTENTION

5

•

The Upload Document option is enabled only if you have attached at least one document to a device type.

•

The Upload Document option lists only those (attached) documents that are opened and modified from the FDM Client using the Device Documentation > ‘Document Name’ menu option. Hence, ensure that you open and modify the attached document from FDM Client only.

•

A document attached at the device type level can also be uploaded by launching from a device instance.

The following dialog box appears.

This dialog box lists all the documents are opened and modified, from the FDM Client, but not uploaded onto the FDM Server. 6

Select the check box corresponding to the document(s) you want to upload. Click OK. FDM uploads the revised document to the FDM Server.

ATTENTION Some type of documents such as Microsoft Paint documents (.bmp) cannot be tracked by FDM. So if you attach a BMP file, launch it from FDM, modify it and save it, this document is not detected as being modified by FDM and hence, it is not available for upload. (An error message appears, stating that there is no document to upload). To upload such documents, detach the document and attach it again after modification. 332

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.23 Working with device documentation

Detaching device documents You can detach documents attached to a device, device type or system level. For example, to detach documentation attached to a device, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

From the Online View, click the Network View tab.

3

Browse through the network.

4

Right-click a device and choose Device Documentation > Detach Document. The following dialog box appears.

ATTENTION

6

•

If a document is attached at the Device Type level, it can only be detached from the Device Type (from Offline View > Device Library tab). It cannot be detached from a Device (Online View > Network View tab) belonging to that Device Type.

•

However, you can open, modify, and upload documents attached at a Device Level, from a device (Online View > Network View tree).

Select the check box corresponding to the document(s) you want to detach. Click OK.

ATTENTION Ensure that the document you want to detach is closed. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

333

4. FDM Operations 4.23. Working with device documentation

Step

Action

7

A confirmation message appears. To proceed with the operation, click Yes in the message dialog box.

8

If you click Yes, the following dialog box appears.

9

Type the reason in the dialog box and click OK. FDM detaches the device.

ATTENTION The Reason dialog box appears only if the Administrator has enabled reason logging, for this action type, in the Audit Trail settings.

334

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.24 Working with FDM Applications

4.24 Working with FDM Applications Overview FDM enables Administrators, Engineers, and Supervisors to attach applications for a device type or at the system level (applicable to all devices across FDM). These applications can be any third party applications that you can use to perform additional tasks on the devices or can be any other tool, which is relevant to device management. Application can be maintained at the following two levels. •

Device-Type level - Application for a Device-Type can be attached/launched/detached from the Offline View > Device Library tab.

•

System level – Application can be attached/launched/detached from the Tools > Other Applications menu. ATTENTION •

Attaching applications at Device type level is applicable only to the DD library. You cannot attach applications to the DTM library.

•

Attached applications are client specific. This means that if you attach an application in one client, it is valid only on that computer. You cannot launch or detach that application from another client.

Tasks associated with FDM Applications FDM enables you to attach/launch/detach application at the Device-Type level. You can perform this using the Device Library tab of the Offline View. Any application attached to a device type can be started from a device instance of that type. Task

To achieve, perform the following

Attaching application

R430 May 2012

a)

Choose Offline View > Device Library > DD Library.

b)

Right-click Device Revision No and choose Applications > Attach Application.

Launching application

From the applications listed under Applications, click the application that you want to launch.

Detaching application

a)

Choose Offline View > Device Library > DD Library.

b)

Right-click Device Revision No and choose Applications > Detach Application.

Field Device Manager - R430 User's Guide Honeywell

335

4. FDM Operations 4.24. Working with FDM Applications

Attaching an application at Device-type Level To attach an application at the device-type level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Under Offline View, click the Device Library tab.

3

Browse through the DD Library tree and expand the network tree corresponding to the Device Type.

4

Select a Device Revision No.

5

Right-click and choose Applications > Attach Application. The Select Application dialog box appears.

6 to browse for an application.

Click

The Open dialog box appears. 7

Browse through your computer and locate the folder where you have saved the document.

8

Select the application and click Open. The Select Application dialog box appears displaying the application name along with its path in the Display Name.

336

9

Enter a suitable display name to the application in the Display Name.

10

If any arguments are to be passed to the attached application, enter them in the Application Arguments.

11

Click OK. Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.24 Working with FDM Applications

Step

Action FDM attaches the application to the specific device type and a confirmation message appears.

12

Click OK.

13

To crosscheck whether the application has been attached, browse through the Device Library, expand the Manufacturer > Device Type > Device Revision No to which you have attached the application. Right-click and click Applications. The name(s) of application(s) appears as a submenu under Applications:

Attaching an application at System Level To attach an application at the system level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Other Applications > Attach Application. The Select Application dialog box appears.

3 Click

to browse for the application.

The Open dialog box appears. 4

Browse to the location where you have saved the application on your computer.

5

Select the application that you want to attach and click Open. In the Select Application dialog box, the application name appears along with its path in the Display Name.

R430 May 2012

6

Type a suitable display name to the application in Display Name.

7

Type the arguments in Application Arguments and click OK.

Field Device Manager - R430 User's Guide Honeywell

337

4. FDM Operations 4.24. Working with FDM Applications

Step

Action FDM attaches the application at the system level and a confirmation message appears.

8

Click OK.

9

To crosscheck whether the application has been attached, choose Tools > Other Applications. The name(s) of the attached application(s) appears as a submenu under Other Applications.

ATTENTION If the application is already launched on your computer, FDM does not allow you to launch the attached application. An appropriate error message appears. Close the application and then retry launching the attached application.

Launching an attached application You can launch the attached application from device type and also from system level. For example, to launch an application attached at the system level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Choose Tools > Other Applications > FDM launches the selected application.

338

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.24 Working with FDM Applications

Step

Action

ATTENTION If the application is already launched in your system, FDM does not allow you to launch the attached application. An appropriate error message appears. Close the application and then retry launching the attached application.

Detaching an attached application You can detach an application at device type and system level. For example, to detach an application attached at the Device-Type level, perform the following steps. Step

Action

1

Log on to the FDM Client.

2

Under Offline View, click the Device Library tab.

3

Browse through the Device Library tree.

4

Expand the Manufacturer > Device Type > Device Revision No to which you have attached the application.

5

Right-click and choose Applications > Detach Application. The Select dialog box appears.

6

R430 May 2012

Select the check box corresponding to the application(s) you want to detach.

Field Device Manager - R430 User's Guide Honeywell

339

4. FDM Operations 4.24. Working with FDM Applications

Step

7

Action

Click OK. An appropriate confirmation message appears.

8

Click Yes to detach the application. Or Click No to cancel the operation.

ATTENTION Ensure that the application you want to detach is closed. FDM does not allow you to detach an application that is running. An appropriate message appears. If you click Yes, FDM detaches the application from the specific device type and the following message box appears.

340

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.24 Working with FDM Applications

Step

9

Action

Click OK.

ATTENTION Applications attached at the Device-Type Level cannot be detached at the Device level.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

341

4. FDM Operations 4.25. FDM Help

4.25 FDM Help FDM provides an online help and it is accessible from the Help menu of the FDM Client. Use the F1 shortcut key to access context-sensitive (feature-based) Help.

4.26 About FDM FDM displays an About Honeywell Field Device Manager window from the Help menu of the FDM Client. You can view the Copyright information, the product license information, installed modules, and their release versions.

342

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.27 FDM Operational Restrictions

4.27 FDM Operational Restrictions In a multiple client scenario, it is important to ensure integrity of the operations. Therefore, FDM restricts concurrent execution of certain operations to ensure success of a given operation. When you try to execute an operation and if this operation is rejected by FDM Server, as certain operation(s) are currently in progress on other clients, following error message is displayed.

The error message gives the list of clients performing other operations, due to which, the current operation is denied. •

Click Details button to view the list of operations in each of the clients that are restricting the current operation.

•

Click OK button to acknowledge the message.

If the attempted operation is restricted due to operations being performed by the same client, then the following error is displayed.

You may have to wait for these operations to complete or stop them to perform the necessary operation. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

343

4. FDM Operations 4.27. FDM Operational Restrictions

The following table lists various operations and the operations that are restricted when they are in progress. Current Operation

344

Restricted operation

Open Device Configuration

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Bulk History

Open Device Configuration, Explicit Build Network, Bulk History, Bulk Template, Bulk Offline Download, Import Export, Open Offline Configuration, Save Offline Configuration, Delete Offline Configuration, Rename Offline Configuration, Rename Tag, View Audit Trail, Add DD file, Delete DD file, Delete History, FDM Settings (Device Configuration Load Option and Write Access option), Tag Builder, and Delete Records

Bulk Template

Open Device Configuration, Explicit Build Network, Bulk History, Bulk Template, Bulk Offline Download, Import Export, Open Offline Configuration, Save Offline Configuration, Delete Offline Configuration, Rename Offline Configuration, Rename Tag, View Audit Trail, Add DD file, Delete DD file, Delete History, FDM Settings (Device Configuration Load Option and Write Access option), Tag Builder, and Delete Records

Bulk Offline Download

Open Device Configuration, Explicit Build Network, Bulk History, Bulk Template, Bulk Offline Download, Import Export, Open Offline Configuration, Save Offline Configuration, Delete Offline Configuration, Rename Offline Configuration, Rename Tag, View Audit Trail, Add DD file, Delete DD file, Delete History, FDM Settings (Device Configuration Load Option and Write Access option), Explicit Lock Node, Tag Builder, and Delete Records

Import Export

Open Device Configuration, Explicit Build Network, Bulk History, Bulk Template, Bulk Offline Download, Import Export, Open Offline Configuration, Save Offline Configuration, Delete Offline Configuration, Rename Offline Configuration, Rename Tag, View Audit Trail, Add DD file, Delete DD file, Delete History, FDM Settings (Device Configuration Load Option and Write Access option), Tag Builder, and Delete Records

Open Offline Configuration

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

4 FDM Operations 4.27 FDM Operational Restrictions

Current Operation

Restricted operation

Save Offline Configuration

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Delete Offline Configuration

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Rename Offline Configuration

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Rename Device Tag

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Add DD File

Bulk History, Bulk Template, Bulk Offline Download, Import Export, Add DD File, Delete DD File, and Tag Builder

Delete DD File

Bulk History, Bulk Template, Bulk Offline Download, Import Export, Add DD file, and Delete DD File

View Device History

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

FDM Settings (Device Configuration Load Option and Write Access option)

Bulk History, Bulk Template, Bulk Offline Download, and Import Export

Tag Builder

Bulk History, Bulk Template, Bulk Offline Download, Import Export, and Add DD file

Delete Records

Bulk History, Bulk Template, Bulk Offline Download, Import Export, and Delete Records

Online Update Operation

Build network for any network at any level (Network level, Safety group, Process group, SM, IOTA and so on.), Bulk Operations, Device Load Note: It is recommended not to perform any network related operations in Client when online update is being performed.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

345

4. FDM Operations 4.27. FDM Operational Restrictions

346

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

5. FDM Station Maintenance view 5.1

Overview FDM Device Configuration pages are integrated into Experion Flex Station. This enables the use of the Experion Flex Station for maintenance. The FDM window is embedded with the HART/FF device detail display pages and can be used for viewing detailed information of the devices. It helps to make online changes (if privileges are available) and perform diagnostics as supported by the HART/FF devices. This view shows the EDDL/DTM based device window, which is similar to the device configuration window displayed in the FDM Client. The FDM embedded detail display page, within the Experion Flex Station is to be used only for Flex Station maintenance. Do not use it on Experion Flex Station used for plant operations. These detailed displays are not supported on Experion Console Stations. In the Maintenance View of Station, you can view the HART/FF devices connected to one of the following interfaces.

5.2

•

1756 HART I/O

•

PMIO

•

Series C I/O

•

Series 8 I/O

•

Hardware Multiplexer (P+F, MTL, STAHL)

•

FIM2, FIM4 and FIM8

•

Universal Safe Modules

Pre-requisites for viewing a device in the Maintenance view To view a device in the Maintenance View of Station, ensure the following: •

The network interface to which the HART/FF device is connected is configured in the FDM Server using FDM Server Management Tool.

•

Network is browsed and the devices are detected by FDM.

•

The FDM Client and the FDM specific display files are installed on the Flex Station system.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

347

5. FDM Station Maintenance view 5.3. Configuring relationship between Experion Server and FDM Server

•

5.3

A relationship between the FDM Server and Experion server is established using the configuration file.

Configuring relationship between Experion Server and FDM Server To enable Maintenance view to open a specified device, you must know the name of the FDM Server on which the Experion server is configured. To view a device connected to a particular Experion server, it must be configured in the Server management tool of an FDM Server. FDM Server and Experion server relationship must be configured in a file so that Maintenance view can be automatically connected to the device when it is opened in Experion Station. To configure the relationship perform the following steps. Step

Action

1

Choose Start > Run.

2

In the Open box, type notepad and then click the OK button.

3

Browse to the location C:\ProgramData\Honeywell\Experion PKS\Client\Station and open the file FdmExperionCache.xml. The default file contents are as follows. < fdmExperionServerCache > DUMMYEPKSSERVER DUMMYFDMSERVER

348

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

5 FDM Station Maintenance view 5.3 Configuring relationship between Experion Server and FDM Server

Step 4

Action To configure relationship between FDM Server fdmsvr1 to Experion server expsvrA, modify the contents in the default file as follows:

EXPSVRA FDMSVR1 Replace DUMMYEPKSSERVER by the name of the actual Experion server, expsvrA and DUMMYFDMSERVER by the name of the FDM Server, fdmsvr1.

ATTENTION •

Ensure that you enter the names in capital letters. For example, expsvrA and fdmsvr1 have to be entered as EXPSVRA and FDMSVR1 respectively.

•

The text between and constitutes one FDM Server – Experion server relationship.

•

Redundant Experion servers should have two entries in the configuration file, one for the primary and one for the secondary. The fdmServer name remains the same for both entries though. For example: < fdmExperionServerCache > EPKSSERVERA FDMSERVER EPKSSERVERB

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

349

5. FDM Station Maintenance view 5.3. Configuring relationship between Experion Server and FDM Server

Step

Action FDMSERVER

5

To configure another relationship, perform the following: a)

Copy the text starting from till , and paste it after

.

350

b)

Type the Experion server name between and .

c)

Type the FDM Server between and .

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

5 FDM Station Maintenance view 5.3 Configuring relationship between Experion Server and FDM Server

Step 6

Action If you want to add another relationship for redundant server, for example, between FDM Server fdmsvr2 and Experion Server expsvrB, the contents must look similar to the following one, after performing the previous step.

EXPSVRA FDMSVR1 EXPSVRB FDMSVR2 7

To configure a relationship between two redundant Experion clusters (EXPServer01a/b and EXPServer02a/b) with their own FDM servers (FDMServer01 and FDMServer02).

EXPServer01a FDMServer01 EXPServer01b FDMServer01

EXPServer02a FDMServer02 R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

351

5. FDM Station Maintenance view 5.4. Access Rights for Maintenance View

Step

Action

EXPServer02b FDMServer02 8

5.4

Repeat step 4 to add as many relationships as required.

Access Rights for Maintenance View The Experion Station user who wants to perform actions on this view has the privilege of the same access level in FDM. For example if you log on with your access level of Supervisor in Experion, then you have the privilege of the FDM Supervisor. ATTENTION To view the Maintenance View on a detailed display page, the user authentication is done by Experion and the authorization is done by FDM. FDM assigns the privileges depending upon the authorization.

When you log on in Experion Station, you are mapped to the FDM access privileges as follows: Experion User Level Manager

Supervisor

Engineer

352

FDM User Level Administrator

Supervisor

Engineer

Privileges (when accessed from FDM Client)

Privileges (when accessed from Experion Station)

Administrator access privileges

Execute Method

Supervisor access privileges

Execute Method

Engineer access privileges

Execute Method

Field Device Manager - R430 User's Guide Honeywell

Read and Write Parameters

Read and Write Parameters

Read and Write R430 May 2012

5 FDM Station Maintenance view 5.5 Starting Maintenance View in Station

Experion User Level

FDM User Level

Privileges (when accessed from FDM Client)

Privileges (when accessed from Experion Station) Parameters

5.5

Operator

Operator

Operator access privileges

Read Only view of device configuration

Ack only

Operator

Operator access privileges

Read Only view of device configuration

View only

Operator

Operator access privileges

Read Only view of device configuration

Starting Maintenance View in Station To start the Maintenance View of a HART/FF device, the detail display page for that device must be accessed. On the Experion Station, you can access the detail display of HART/FF devices from the following pages. •

Search Page

•

System Status page

•

Events page

•

Alerts page ATTENTION Ensure that if you are opening DTMs in the Maintenance view the required executable is added to the DEP exception list. For more information about DEP exception list, refer to section Executables required in DEP Exception list in FDM Software Installation User’s Guide.

For example, to get the FDM device detail display from the system status page, perform the following steps. Step 1

R430 May 2012

Action On the Experion Station computer, choose Start > All Programs > Honeywell Experion PKS > Client > Station and log on to the station.

Field Device Manager - R430 User's Guide Honeywell

353

5. FDM Station Maintenance view 5.5. Starting Maintenance View in Station

Step

Action

2 (System Menu) on the toolbar. The following page appears with Click the System tab.

Type the HART/FF device name you want to search, in the command zone and press F12. If you type the name partially in the command zone, lists of matching device names appear. 3

354

Select the component or node from the Location pane.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

5 FDM Station Maintenance view 5.5 Starting Maintenance View in Station

Step 4

Action Double-click or right-click the required device and click Detail Display. The Detail Display of the HART/FF device appears. Or If you type full name of the device in the command zone, the detail display of that device appears.

REFERENCE - INTERNAL For more information about detail displays from other pages on the Experion Station, refer to the Experion Operator’s Guide. 5

To view the FDM device configuration details from Experion Station, click Maintenance View tab on the Device Configuration Detail Display. This page is identical to the Device Configuration page in FDM Client.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

355

5. FDM Station Maintenance view 5.5. Starting Maintenance View in Station

Step

Action In the following example, you can view DTM Start Page for FF devices.

356

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

5 FDM Station Maintenance view 5.5 Starting Maintenance View in Station

Step

Action In the following example, you can view Entry Points for HART devices.

You can read/write the device parameters, execute Methods, and view the HART device status and properties.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

357

5. FDM Station Maintenance view 5.5. Starting Maintenance View in Station

358

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

6. FDM Data Backup – Restore utility 6.1

Overview The FDM database stores all information related to the network and device configurations. It also stores information related to the users and all actions performed by the users using FDM. The Backup and Restore Utility enables you to take a backup of the FDM database and use the backed up database at a later point in time for restoring FDM.

6.2

Logging on to the Backup and Restore utility To log on to the FDM Backup and Restore utility, perform the following steps. Step 1

Action Choose Start > All Programs > Honeywell FDM > FDM Data Backup Restore. The login screen appears for the backup and restore utility.

R430 May 2012

2

Type the Login Name.

3

Type the Password.

4

Click Login. The FDM Data Backup/Restore dialog box appears.

Field Device Manager - R430 User's Guide Honeywell

359

6. FDM Data Backup – Restore utility 6.2. Logging on to the Backup and Restore utility

Step

Action

ATTENTION Only a user with privileges assigned to an Administrator role can log on to this utility. Other users with Engineer, Supervisor, and Operator privileges cannot use this utility.

360

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

6 FDM Data Backup – Restore utility 6.3 Taking a backup of the FDM database

6.3

Taking a backup of the FDM database To take a backup of the FDM database, perform the following steps. Step 1

Action Log on to the FDM Backup and Restore Utility. The FDM Data Backup/Restore dialog box appears.

ATTENTION

2

•

Only a user with privileges assigned to an Administrator role can log on to this utility. Other users with Engineer, Supervisor, and Operator privileges cannot use this utility.

•

Ensure that you stop the server before performing a backup operation. For more details, refer to section Stopping the FDM Server.

•

Ensure that the SQL Server management studio and FDM related applications are closed.

To take a backup of the FDM database, click Backup.

3 Click the files.

button to select the path where you want to store the backup

The Browse for Folder dialog box appears. 4

Select the folder where you want to store the backup files. To create a new folder, click New Folder.

5

Type a name for the new folder and click OK. The selected folder’s path appears in the dialog box.

6

Click Backup. A progress bar appears, which indicates the status of the backup operation. This operation stores the FDM database files in the selected folder. After the operation is complete, Backup operation completed message appears in the dialog box.

7

R430 May 2012

Click Close.

Field Device Manager - R430 User's Guide Honeywell

361

6. FDM Data Backup – Restore utility 6.4. Restoring the database

6.4

Restoring the database To restore the FDM database, perform the following operations. Step 1

Action Log on to the FDM Backup and Restore Utility. The FDM Data Backup/Restore dialog box appears.

ATTENTION

2

•

Only a user with privileges assigned to an Administrator role can log on to this utility. Other users with Engineer, Supervisor, and Operator privileges cannot use this utility.

•

Ensure that you stop the server before performing a restore operation. For more details, refer to section Stopping the FDM Server.

•

Ensure that the SQL Server management studio and FDM related applications are closed.

To restore the FDM database from a backup, click Restore.

3 Click the stored.

button to select the folder where the backed up database is

The Browse for Folder dialog box appears. 4

Select the folder where you have saved the FDM database backup files.

6

Click OK. The selected folder’s path appears in the dialog box.

ATTENTION It is recommended to take a backup of your current database before performing a restore operation from a previous backup, as restoring from a previous backup overwrites the current database information. 7

Click Restore. A progress bar appears which indicates the status of the restore operation. After the operation is complete, Restore operation completed appears in the dialog box.

8

362

Click Close.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

7. FDM diagnostics 7.1

Overview of Dr. FDM Dr. FDM is a diagnosis tool used for collecting diagnostic information related to the FDM system. In the event of issues faced with the usage of FDM software, this diagnostic tool can be run on the systems where FDM components are installed. The tool collects diagnostic information in the form of various log files. These files can be sent to Honeywell TAC for further analysis.

7.2

Capturing Diagnostics To capture the FDM diagnostic information, perform the following steps. Step 1

Action Choose Start > All Programs > Honeywell FDM > Dr. FDM. The Dr. FDM dialog box appears.

2

Click Start Diagnostics to proceed.

ATTENTION Click Quit, if you want to stop Dr. FDM during the diagnosis. A confirmation message appears. Click Yes to close Dr. FDM. R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

363

7. FDM diagnostics 7.2. Capturing Diagnostics

Step

Action The Choose Diagnostics page appears. By default, the Get Advanced Diagnostics option is selected.

3

Click Continue to proceed with collecting diagnostic information by reproducing the problem.

ATTENTION

4

364

•

Honeywell recommends choosing the Get Advanced Diagnostics option always.

•

To quit Dr. FDM after collecting the initial diagnostic information, select the Quit with Current Diagnostics option and then click Continue.

If you click Get Advanced Diagnostics, the following dialog box appears.

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

7 FDM diagnostics 7.2 Capturing Diagnostics

Step

Action Choose the relevant option depending on the type of problem from Select Problem Type list. • Choose Device Specific Problems, if there is a problem related to device

loading. • Choose Browse Related Problems, if the problem is related to the number

of nodes or hierarchy of nodes. • Choose Mux Monitoring Related Problem, if the problem is related to the

Mux Monitoring solution. • Choose Others for any other scenario. • Choose Create Dumps, to take dumps any time specifically during the time

if you encounter any problem. 5

Click Continue. The following message appears.

All the services listed in the dialog box have to be stopped in order to proceed further.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

365

7. FDM diagnostics 7.2. Capturing Diagnostics

Step

Action

ATTENTION •

The Experion HART Multiplexer service is present only on the Experion system.

•

Ensure that the services listed in the message are stopped. If any of the services is not stopped, the message appears until the service is stopped. For example, if the FDM Server service is not stopped, the system continues displaying the following message.

Stop the service and click OK. •

Ensure that the FDM Remote Communication Interface service is stopped. If the FDM RCI service is not stopped, the system continues displaying the following message.

Stop the service and click OK.

366

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

7 FDM diagnostics 7.2 Capturing Diagnostics

Step 6

Action Click Continue. The following message appears.

This screen remains in the background while you reproduce the problem. 7

Reproduce the problem scenario and then click Continue to proceed to the next step. The following confirmation message appears.

8

R430 May 2012

Click Yes, if you have finished reproducing the problem and the following dialog box appears.

Field Device Manager - R430 User's Guide Honeywell

367

7. FDM diagnostics 7.2. Capturing Diagnostics

Step

Action

This step ensures that all changed values during the usage of Dr. FDM are reset to default values. For more details, refer instructions as in step 5. 9

Stop the services listed in the message dialog box and click Continue. The following message appears.

All the required diagnostic information is stored under the path depends on where the FDM is installed. In this example, it is in C:\ProgramData\Honeywell\FDM\DrFDM.

ATTENTION For further analysis of the problem, move all the files from the path C:\ProgramData\Honeywell\FDM\DrFDM to Honeywell TAC.

368

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

7 FDM diagnostics 7.3 Service Control functions

7.3

Service Control functions Service control tool helps in stopping the device related services. To stop or refresh the device related services, perform the following steps. Step 1

Action Choose Start > All Programs > Honeywell FDM > Dr. FDM. The Dr. FDM dialog box appears.

2

Click Service Control to proceed. The Service Control Panel appears.

ATTENTION When the Dr FDM is launched without clicking Run as administrator, then Service Control does not work.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

369

7. FDM diagnostics 7.3. Service Control functions

Step 3

Action Click Refresh to view the current status of the Device Related Services. If you click Refresh when the Device Related Services is running, then the following dialog box appears.

The status appears as Running. If you click Refresh when the Device Related Service is not running, then the following dialog box appears.

The status appears as Not Running.

370

Field Device Manager - R430 User's Guide Honeywell

R430 May 2012

7 FDM diagnostics 7.3 Service Control functions

Step 4

Action Click Stop to stop the Device Related Services. The following dialog box appears.

The status appears as Stopped.

ATTENTION Ensure to save running device configuration operations in all the FDM clients before you stop the Device Related Services.

R430 May 2012

Field Device Manager - R430 User's Guide Honeywell

371

Honeywell Process Solutions 1860 W. Rose Garden Lane Phoenix, AZ 85027 USA