fdm detailed features 9 08

7/18/2019 FDM Detailed Features 9 08

http://slidepdf.com/reader/full/fdm-detailed-features-9-08 1/31

Field Device Manager Product Summary andFeatures

Sept 2008



2 Last Modified: 16 January 2008, use through March 2008 (subject to change)

Honeywell Proprietary and Confidential

Field Device Manager (FDM)



3Last Modified: 16 January 2008, use through March 2008 (subject to change)


FDM Overview

• Supports HART & Profibus device configuration andmanagement tasks/functions

• Uses a client-server architecture and

communicates across networks

• Handles large database of HART & Profibus devices frommultiple network communication interfaces (Experion, MUX’s,

Gateways, etc.)

• Uses DDs & DTMs to create configuration templates

• Uses live data from connected devices to establish databaserecords and assign templates

• Allows download of configurations from FDM to devices in the

field





FDM Basic Features

• Detects devices automatically and adds to the FDM database• Supports universal, common practice, device specific commands and

Methods (all part of HART specs)

• Support user management features

– Creating users, login authentication, performing read/write security checks, and

setting permission levels

• Audit Trail logs pre-defined user actions, custom user actions, and some

implicit actions, as well as allows filtering

• Supports both on-line (real-time) and off-line configuration (without

connection)

• Allows importing and exporting of device data in several formats

• Supports Experion HART I/O – Series C, 1756 Series A and PMIO

– Configuration, method execution and monitoring in Experion

– Pass-through data for configuration in FDM





FDM More Detailed Features (1/3)

• Copy selected configuration values from one device to another • Import/export offline configuration and tags in CSV format into/from FDM

• History feature to store or view device configuration history

– XML, CSV, HTML, Documint & FDM formats

• Compare configuration of two devices or with past history






• Attach device-specific documents – Device Type level, Device Instance level, and System level

• Filter devices using various criteria

• MUX Monitoring functionality

– Allows Experion PKS to access to device diagnostic information from devices

connected to HART Multiplexer networks• Complete device configuration from Station displays, including DTMs


http://slidepdf.com/reader/full/fdm-detailed-features-9-08 7/317 Last Modified: 16 January 2008, use through March 2008 (subject to change)



• Automatic Experion Redundancy switchover – Transparent to Experion server switchover

• Supports

– HART 5.x and HART 6.x protocol.

– EDDL (Electronic Device Description Language)

– FDT-DTM for HART and Profibus devices

– Windows® authentication and single sign-on

– Integration with Experion Station

– Profibus devices through Communication DTMs

– Network communication interfaces for HART and Profibus through

communication DTMs supplied by other device vendors

– Configuration of HART Devices over Profibus network using the third party

HART over Profibus gateway DTMs.

– HART Valve Diagnostics via third party valve diagnostic applications through

the FDM HART Multiplexer functionality




Ethernet / FTE

HART deviceConfigurationDatabase

RS-485

RS-232

HARTProtocol

FDM(Server)

HARTModem

HARTdevice

MTL, P+F, R.Stahl,Elcon, Arcom

RS-232

Hardware Mux

ExperionServer

CIOM-A (1756) AI/AO

ExperionERDB

ControlNet/FTE

Redundant PMIO AI/AO

HART devices HART devices

FDM(Client)

FDM(RCI)

RS-232

RS-232

RS-485Hardware MUX

HART Modem

12

3

FDM Architecture

Redundant Series C AI/AO

SW

MUX


http://slidepdf.com/reader/full/fdm-detailed-features-9-08 9/319Last Modified: 16 January 2008, use through March 2008 (subject to change)


Experion Server Field Device Manager Server

HART Enabled I/O

All HART analog and digital

data passes through the

HART enabled I/O.

Universal Commands

Common Practice Commands

Device-Specific Commands

Device Methods

C200

PMIO CIOM-A Series C

C300

FDM Experion Integration




Dynamic Variables

Device Variables

Device Status

Device Range Data

Experion Server Field Device Manager Server

On-line HART digital

device data is

available for use with

control and logic

strategies.

Device Identification Info

C200


C300





On-line HART device data is

available for display in

Alarm/Event, detail, and

custom displays.

C200


C300


Field Device Manager Server Experion Server




ID and resolve problems faster and safer Effectively manage device configuration

Perform Device Diagnostics

Optimize life cycle activities

FDM

– HART Device Management

Improve availability

Field Device Manager Server

HART device data(DD-specific) is

available for use by

FDMC200


C300


Experion Server




I/O

C200

HART

Device

ControlSystem

Field DeviceManager

Device ID information (Tag, manufacturer, model, SN, etc.)

Software and hardware revision level

Dynamic variables (PV, SV, TV, FV)

Device variables up to 255 (Slot-0 through Slot-3)

General and device-specific status information

Range related information

Full device setup and configuration information

Full device diagnostics support

Trends, calibration and test analysis data

On-line

C300

On-line data is scanned,

cached, and published to

the system ASAP!





I/O

C200

HART

Device

ControlSystem

Field DeviceManager

C300

Device ID information (Tag, manufacturer, model, SN, etc.)

Software and hardware revision level

Dynamic variables (PV, SV, TV, FV)

Device variables up to 255 (Slot-0 through Slot-3)

General and device-specific status information

Range related information

Full device setup and configuration information

Full device diagnostics support

Trends, calibration and test analysis data

Off-line

Off-line data is demanded

and accessed using pass

through functionality





FDM auto-populates from ERDB Easy

Configuration

1) Install HART enabled I/O

2) Connect the HART device (using traditional wiring practices)

3) Complete the I/O Card Function Block

4) Create a HART device template (if required)

5) Create a Channel Block6) Load the Control Module (CM)





To facilitate channel configuration all

required HART data is available

following the IOP load function.

Manufacture

Device type

Revision

HART Device

IOPConfiguration





DD

Vendor DD

Command-48 Descriptor Strings

HART DD

Manager





Channel Configuration

The user assigns the correct

template to each channel.

If no DD is available the “GenericTemplate” can be assigned.

Manufacture

Device type

Revision

HART Device

Bulk build tools for bulk engineering!





FDM Software Components

• FDM Server

• FDM Client

• FDM RCI

• FDM MUX Monitoring Solution component

• FDM MUX Monitoring Update

• FDM HART Multiplexer

ExperionServer

FDMServer

RCI

FDM Client

FDM Client

FDM Client

FDM Client

FDM Client

ExperionStation

Series C HART I/O

HW MUXRCI

HART Devices





Field Device Manager R301 Features

• HART EDDL Support

• HART 6 support

– Versions 5.x and 6.x now supported

• FDM integration with Experion Station

• Windows Authentication• DD Manager support for EDD

– Now support both DDL and EDDL files

• FDT (Field Device Tool ) or Frame Application in FDM

• Device DTM support

• Communication DTM support

• Gateway DTM support

• Device DTM configuration support for HART devices in Experion Station





FDM Support for HART 6 Protocol

• Allows user to configure, run methods and view detailed diagnostics for a

HART 6 device connected to any of the supported interfaces

• Uses config change counter tracking mechanism to detect parameter

value changes and display the changed values

• Allows user to locate a device using Squawk

– HART Command-72

– Used to identify devices that support it

• Supports device locking

– Implicit and explicit

• Supports Delayed Response for communicating with HART 6 devices• Supports 32 character based Long Tag that is used to identify the device





FDM Support for FDT-DTM

• Stands for Field Device Tool (FDT)-Device Type Manager (DTM)

• Field Device Tool

– Standard interface defined by the Field Device Tool group to support the DTMs

supplied by the device vendors

• Device Type Manager

– Device driver developed by device vendor for a particular device type

• Device DTM

– 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

– Software that represents a communication device

• Gateway DTM

– Software that represents a gateway device





FDM R310 Summary

• Profibus Topology View• HART over Profibus Remote IO support

• Profibus PA devices support

• HART Device load time optimization (Series C I/O)

• Compatibility with Experion R211, R301 and R310

• MC Toolkit Integration

FDMServer

FDM Client FDM Client

RCINodeFDM/Instrument

Database(HART/Profibus)

Communication

Device

FDT Comm Configuration

Tool

FDT Comm Config Tool

used to configure the

networks using the

Comm and Gateway

DTMs on the RCI

machine.

DTMs for devices

connected to Gateways

also loaded in the RCI

Node.

Device DTM #1

Device DTM #2

Device DTM #3

Device DTM #1

Device DTM #2

DTMs can be for HART

or Profibus DP or

Profibus PA devices.

Gateway

Device #2

Communication

DTMGateway DTM #1

Gateway DTM #2

D e v i c e s

Device DTM #1 Device DTM #2

FDT/DTM Installed Components





FDM R310 Details

• Profibus Specifics

– Support for MUX monitoring of HART over Profibus.

• Makes use of existing gateway DTM implementations for HART over

Profibus/multiplexers.

– Support for any Profibus Device DTM (Device Type Manager).

• Will be upgraded to support for the FDT spec 1.2.1.

– Support for any Profibus Communication DTM

– Support for any Profibus Gateway DTMs

• Load Time Goals for simple, moderate, and complex devices

# params Expected Max

Simple <100 params 30 sec 125 sec

Moderate <200 params 90 250

Complex >400 180 500





FDM R310 Topology Example

• Top Level is PC Node

• Everything Self-Discovered

• MUX Network

– MUX_NETWRK name of RS485 link

– MUX’s under link

– Then devices under each MUX

• Profibus Network

– SOFTING_PROFI name of Comm DTM

– Gateways under Comm

– Gateways and Devices follow

• Experion Network – PRDMKT name of Experion Server

– C300 and C200 controllers next

– HART-enable I/O next

– Then devices under each I/O





Profibus Comm DTM Example





MC Toolkit Integration

• Synchronize MC Toolkit data withFDM database

– MC Toolkit SDC625 Field

Communicator

– Works with MCT101 and MCT 202

– Available as MC Tool Kit release 3.1

– Synchronize HART device history

snapshot with FDM database

– Help maintain a comprehensivedatabase of all the on line and offline

devices in FDM




www.honeywell.com

fdm detailed features 9 08

Documents