FDM R400

Product Summary,
Enhancements &
Specifications

John Yingst
Product Manager
Phoenix, AZ

April, 2009

FDM R400 Enhancements Summary

Topology -- New MultiServer Environment
Capacity Increase

Device Load and

Network Build Time

Bulk Operations
Tag Generation
Explicit Upload (DTMs)
FHM Changes

Device Health and

Network Scan

MUX Monitoring

Save History Behavior

New Max License

Count models

Dynamic Scanning

New Base Model

Compatibility

Installation

FDM R400 Benefits

Manage assets for any size plant!
Cover more devices, more Experion Servers,
and more non-Honeywell networks than ever
before!
Save more time than ever with vastly improved
device load times!
Save time and money with new bulk loading
options!
Save time managing bandwidth limited HART
MUX networks with Device Health and Network
Scan Settings!
Enjoy the only management
tool that handles both EDDL
and DTM for devices!
3

FDM R400 Basics Topology & Capacity

New Multi-Server Environment
- Supports multiple FDM Servers (no limit)
- FDM Client connects to any FDM Server
- Client can switch Servers on-the-fly
Capacity Enhancements
- 16,000 devices max per FDM Server (was 4,000 before)
- 6 Experion Servers per FDM Server (was 4 before)
- 25 MUXs per FDM Server (was 10)
- 25 MUX Monitoring connections per FDM Server (was 4)
- 25 RCIs per FDM Server (was 10)
FDM
Client

FDM
Server
4

FDM
Client

FDM
Server

FDM
Client

FDM
Client

FDM
Server

FDM R400 Basics MUX Monitoring

MUX Monitoring
- For getting device info into Experion
- FDM Gateway decoupled from FDM Server
- Can install in any PC now (formerly in FDM Server only)
Uses ACE component (no license required!)

- More flexibility and capacity

6 Gateways max per FDM Server
2 Gateways per Experion Server
2 Gateways per PC
12,000 devices max per FDM Server
6 total Gateways per FDM Server

ACE

FDM FDM
Gateway Gateway

FDM FDM
Gateway Gateway

FDM FDM
Gateway Gateway

Gateway PC

Gateway PC

Gateway PC
MUXs

DATA

Experion
Server

FDM
Server

HART
DEVICES

FDM R400 Basics New Models

New Base Model
- HC-SV0000 is now HC-SV0001 in R400
- Now includes
1 Client license (new in R400)
1 MUX license (Hardware Multiplexer

network connection) (new in R400)

16 devices (new in R400)
1 HART Modem connection (no change)
All essential device configuration
management functions (no change)

New Maximum License Counts & Models

Pre-R400
Model

R400
Model

Description

Pre-400
Limit

R400
Limit

HC-HMOMAX

HC-HMOMX1

License that provides ability to connect to maximum

number of multiplexers supported.

10

25

HC-MMOMAX

HC-MMOMX1

License that provides ability to have maximum

number of multiplexers monitoring
connections supported.

25

HC-RIOMAX

HC-RIOMX1

License that provides ability to have maximum

number of RCI connections supported.

10

25

FDM R400 Details Topology

FDM Client can connect to any FDM Server
- Removed one to one correspondence between Client
and Server
- User specifies which FDM Server to connect to
- Either from launching Client or from within the Client
25 Clients max per FDM Server

FDM
Client

FDM
Client

FDM
Client

FDM
Client

FDM Client may

connect to 1 FDM
Server at a time

FDM
Server

FDM
Server

Experion
Server*

Experion
Server*

6 Experion Servers max per FDM

Server or Redundant Server Pair

FDM
Server

FDM Client may run in the

same PC as FDM Server or
RCI (see Configuration
Guidelines)

Experion
Server*

RCI

25 total RCIs, including Experion

Servers, max per FDM Server

FDM R400 Details Topology (contd)

Experion Station Client
- Connects to FDM server
on-the-fly when launched

- Maintain config file on

each station
User can connect to the desired FDM
Server by entering the machine name
during login/Server switch

- Contains map of FDM

Server node name vs
Experion Server node
name

Removal of FDM from

Configuration Studio
- Requirement of new
topology
User can switch to a different
FDM Server without closing the
FDM Client.

- No longer associated with

just one Experion server

FDM R400 Details Network Build Time

Build Time Enhancements
R400 network build time is significantly enhanced
If FDM server is interrupted, FDM RCI service keeps
running
When FDM Server is available, network information
is published from RCI cache in seconds
During Experion Server switchover, network build is
much faster
Initial network build time for hardware MUX networks
has not changed

FDM R400 Details Device Load

Load Enhancements
Initially, Client reads a minimal set
of parameters to populate the UI
Subsequent parameters read only when
a user visits a particular menu or tab
Non-dynamic parameters are read
once on visiting a menu
Visible dynamic parameters refreshed every 40
seconds if "Enable Dynamic Scan" enabled
Results
- Fast device load time
Upon visiting each
- Quick response for configuration
menu, the progress of
- Low network traffic
the parameter read will
be shown here

10

FDM R400 Details Device Load

Upon visiting each

menu, the progress of
the parameter read will
be shown here

11

FDM R400 Details Dynamic Scanning

Enable Dynamic Scanning
provides optional parameter
refresh
- Every 40 seconds
- Applies to PV, SV, TV, QV, etc.
- Option disabled by default
Useful maintenance tool
- Monitoring device response
- Looking for status changes
- More flexibility in managing
bandwidth

12

FDM R400 Details Save History Behavior

Save History Change
While closing a device, prompt reminds to Save History Record

Previously, parameters read during device load

- History saved when the last instance closed across Clients

- New device load paradigm no longer performs this
In R400, use Save History Record

- Read all the device parameters and save the history

- FDM will read all unread values from the device before saving
history

13

FDM R400 Details DTM Explicit Load

Quick availability for configuration
For DTMs, Client initially reads
minimal set of parameters

- Most DTMs will provide data when

you then visit a page or tab

Explicit Read All Parameters

option

- Used after loading the DTM

- Reads all device parameters
- Consistent with other FDT frames
and systems
- Expected behavior of most DTMs
- Fewer delays while opening
- Useful for DTMs that dont refresh
page/tab
14

Read All Parameters

FDM R400 Details Device Health

Device Health and Network Scan Settings
Health scan utility in FDM R310 now part of Settings in FDM R400
Enabled by default, with values of 10 sec for device health scan
and 2 min for network scan
Applicable ONLY for Hardware MUX networks
Very flexible

Device Health and

Network Scan Setting.
.

15

FDM R400 Details Device Health

Device Health and Communication Option
If enabled, FDM scans health of all network devices
every X seconds
Provides health status of connected devices
Also identifies disconnected or re-connected
devices
Inhibits MUX Monitoring alarms if disabled
New Devices Option
If enabled, FDM scans empty slots for
new devices every Y minutes
Only to discover new devices

16

FDM R400 Details Bulk Operations

Bulk Operations Bulk History & Offline Template Save
Bulk History
- Good for snapshots of devices as commissioned
- Saves history for a large number of devices
Bulk Offline Template Save
- For creating offline configurations of available device types
- Same as Bulk History, but can be edited and used for
downloading to devices later
Common UI for Both Operations
- Invoke from FDM Client Tools Bulk Operations
- User selects required devices from Online Network
- User can save a report of the operation
- User can abort at any point in time

17

FDM R400 Details Bulk Operations (contd)

Bulk Operations UI
Select the desired
bulk operation
Option to filter the
available network tree

Devices selected for

Bulk History / Bulk
Template
Devices currently
available in the FDM
network

Prefix for the records

to be saved.

18

Buttons to select/deselect devices

Time interval within which

each device must be loaded
and history/template saved

FDM R400 Details Bulk Operations (contd)

Bulk operation progress window
Server Notified Errors tab lists
errors (if any) notified by FDM
server during Bulk Operations.

Devices shows the current status of

all the selected devices along with
timestamp

Export the Bulk Operation

report to a CSV file

19

FDM R400 Details Bulk Download

Allows configuring multiple devices simultaneously
Applies to multiple offline configurations
Download to one or more device types
Two options
- Manual selection of device versus offline configuration, or
- CSV file to specify device versus offline configuration
Previous FDM Bulk Offline Download
- Applied to single offline configuration
- Download limited to single device type

20

FDM R400 Details Bulk Download (contd)

Selecting the devices manually through device selection option

21

FDM R400 Details Bulk Download (contd)

Selecting the devices Through .CSV file.

22

FDM R400 Details Tag Generation

For non-Experion devices
- Typically, from MUXs
- Provides automatic way to name tags not in the
system
- Tag Name generated based on device HART Tag
- Created when device first added
- User can change through Rename or Tag Import
- If no valid HART Tag, shows INVALID TAG
- Easy to use!

23

FDM R400 Details FHM Changes

FDM HART Multiplexer (FHM)

User-Created COM Ports for R400 FHM

- User installs hardware COM port extenders OR
Virtual COM ports
- FHM service connects to one of these ports
- Third party application connects to the other
- Physical COM ports connect through a loop back
connection

FHM Device Lock Mechanism

- Device in use through FHM considered locked in FDM client
- Opens in read-only mode in any Client
- Not available to other FHM Clients
- Provides protection against unintentional change

24

FDM R400 Specs Connections & Clients

Description
Network connections per FDM Server

Value
25

(HART Modem, RS 485 HART hardware MUX network, or Experion Server or Redundant Server pair)

Experion network interfaces per FDM Server

(Consumes 1 RCI. RCI configured for Experion interface cannot be used for any other type of connection.)

Number of FDM RCIs configurable per FDM Server

25

(Total of RCI PCs including Experion Servers)

Number of RCIs per PC

For Non-Experion networks, number of network connections per FDM RCI

(where 1 network connection is defined as 1 HART Modem or 1 RS 485 HART hardware MUX network)

Concurrent FDM Clients or Station maintenance views per FDM Server

25

(Total connections = Maximum concurrent FDM clients + Maximum concurrent Experion stations with
maintenance view open. Station maintenance display consumes one client license.)

FDM Client-to-Server Relationship

1-to-1

(One Server connected at a time. User can select server during login or change after log-in.)

Maximum number of FDM Client instances per node

Number of device configuration screens simultaneously opened in FDM

50

(Subject to Server memory limitations)

25

FDM R400 Specs MUX Monitoring

Description
MUX Monitoring Solution -- FDM Gateway
FDM Gateways connected per FDM Server

Value
6

Devices monitored per FDM Gateway

4,000

Devices that one FDM Server can monitor via the MUX Monitoring

12,000

(devices can be connected to one or more HART Hardware multiplexer networks)

FDM Gateways that can be connected per Experion cluster

HART hardware MUX networks configured for MUX Monitoring

25

(using Server management tool )

FDM Gateways per Gateway PC (ACE) node

(FDM Gateway is a component of MUX Monitoring Solution. Each Gateway PC requires
installation of Experion ACE component and can run either 1 or 2 FDM Gateways. No ACE
license purchase is required. Note that the ACE component in the Gateway PC node
cannot be used as an Experion ACE node.)

26

FDM R400 Specs Server Points

Description
Number of network nodes one FDM Server can recognize

Value
18,000

(Device, I/O, controller, Hardware MUX, COMM DTM, or Gateway DTM)

Number of devices one FDM Server can communicate with

16,000

Number of devices connected to an Experion cluster that one FDM

Server can support

10,000

(subject to Experion Server point license limitations)

Number of history records per FDM server

160,000

(subject to availability of disk space )

Number of devices selected for Bulk History operation at a time

150

(Bulk History operations can take a very long time.)

Number of devices selected for Bulk offline creation at a time (using

Bulk save online as offline feature)
Number of Offline templates created per FDM server
Number of devices to which Offline configuration can be downloaded
at a time using Bulk offline download feature

27

150
16,000
150

FDM R400 Specs FDM HART MUX

Description

Value

Number of FDM HART Multiplexers per FDM Client PC

Number of FDM HART Multiplexers simultaneously connected to one

FDM Server

Maximum number of devices connected per FDM HART Multiplexer

2,048

Number of third party packages that can be integrated per FDM HART
multiplexer

Maximum number of users configured

50

Maximum number of windows groups that can be configured

20

Maximum number of audit trail records for the entire FDM database

3,200,000

(subject to availability of disk space )

Maximum number of audit trail records for a single device

For HART modem, number of devices that can be connected

28

2,000
1

FDM R400 Specs MUXs

Description
Recommended number of device configuration screens simultaneously opened
in FDM for one Hardware MUX network

Recommended number of device configuration screens simultaneously opened

in FDM for one Experion Series A I/O

Recommended number of device configuration screens simultaneously opened

in FDM for one Experion Series C IO or PM I/O

Recommended number of device configuration screens simultaneously opened

in FDM per HART modem

Description

Value

For RS-485 MUX networks, maximum number of HART devices per network

992

For MUX monitoring with P+F or MTL MUX network, maximum recommended
number of HART devices per MUX master

32

Baud rates of P+F, MTL or STAHL hardware multiplexer networks that FDM can
connect to

29

Value

9600 and
19.2K

FDM R400 Specs DTMs

Description
Concurrent FDT Communication Tools per FDM Server

Value
25

(One RCI can have one FDT Communication tool configured.)

Concurrent FDT Communication Tools per RCI

(If an RCI is configured for FDT Communication Tool, it cannot be used for any other type
of network connection like Hardware MUX, HART modem or Experion.)

Communication DTMs per Communication Tool

Gateway DTMs per Communication DTM

Refer to vendor
specs

Devices per Gateway DTM

Refer to vendor
specs

Concurrent Network scans per Communication Tool

(Scanning devices from Gateway DTM and Communication DTM)

Number of device configuration screens opened in FDM at any time

per Communication DTM

30

FDM Supported Peripherals/Accessories

Hardware Type

Make

Model

Version

Moxa

Transio A52

ICP-CON

i-7520A

CMS

CS485-AD

MTL

4841 & 4842

Hardware Version-10
Software Version-3

Pepperl + Fuchs

KFD2-HMM-16

Hardware Version-10
Software Version-11

R. Stahl

IS1

Elcon

2700G

Hardware Version-10
Software Version-8

COM Port Extender Cards

Digi International

AccelePort 8r 920
(Dell Part# : A0012190)

RS232 HART Modem

MacTek

Viator

Honeywell Smart DE modem

Honeywell

MC Toolkit Modem

Ethernet to Profibus Gateway

Softing

FG-100

Hardware Version-2
DTM Version- 2.03 (110)

Trebing and Himstedt

xEPI

Hardware Version-2
DTM Version-3.0.0.0

RS 232 to RS 485 converter

Hardware Multiplexer

31

FDM Installation Enhancements

FDM R310

FDM R400

Installation components through FDM Media:

Remote Communication Interface (RCI)

Installation components through FDM Media:

RCI

Client
Server
MUX Monitoring Solution
FDM Hart Multiplexer

Additional Patches:
Software Multiplexer patch,

32

Client
Server
MUX Monitoring Solution
FDM Hart Multiplexer
Station Maintenance View

Additional Patches:

MUX Monitoring Update,

Station display Files

No patches.

FDM Client installation requires FDM Server

machine name during installation

FDM Client installation DOES NOT require FDM

Server machine name during installation

MUX Monitoring installation selects FDM server,

client, RCI and installs automatically

MUX Monitoring installation on ACE will not

install any other components unless specifically
required by user

Software MUX component must be installed for

Experion server, after installation of FDM R310

Selection of RCI component during installation

automatically installs software MUX component
in Experion server

Compatible with Experion R211, R301.1 and

R310.2

Compatible with Experion R310.3

Illustration Server RCI Limit

6 network connections max
per RCI
25 network
connections max
per FDM Server

RCI

MUX
MUX
MUX

MUX
MUX

FDM
Server

MUX

RCI

MODEM
MUX

Experion
Server
Experion
Server

33

6 Experion Servers max per

FDM Server

Total of 10 connections in
this example

Illustration MUX Monitoring Limit

6 total Gateways per FDM Server

FDM
Gateway

FDM
Gateway

Gateway PC*

FDM
Gateway

FDM
Gateway

Gateway PC*

FDM
Server

34

FDM
Gateway

FDM
Gateway

Gateway PC*

*Gateway PC requires installation of

Experion ACE component. Cannot be
used as an Experion ACE node. No ACE
license is required.

Illustration -- FDT/DTM Installed Components

Device DTM #1
Device DTM #1
Device DTM #2

FDM Client

FDM Client

Device DTM #2
Device DTM #3

DTMs can be for HART

or Profibus DP or
Profibus PA devices.

FDT Comm Configuration Tool

FDM/Instrument
Database
(HART/Profibus)

FDM
Server

RCI
Node

Communication DTM
Gateway DTM #1

FDT Comm Config Tool

used to configure the
networks using the Comm
and Gateway DTMs on
the RCI machine.

Gateway DTM #2

Gateway
Device #2

FDT/DTM Installed Component

Illustration (Clients and RCIs)
Devices

35

Devices

Gateway
Device #1

www.honeywell.com

FDM Customer Web Site Link

FDM Employee Only Page
(requires log in)
36