Foundation Fieldbus Integration

Product Specification

EP03-470-400
Release 400
July, 2010

TOC
Product Introduction ................................................................................................................................................ 4
Product Description & Features .............................................................................................................................. 4
FDM (Field Device Manager) .................................................................................................................................. 6
Fieldbus Testing and Validation .............................................................................................................................. 7
Fieldbus Host Interoperability Test. .................................................................................................................... 7
New Host Profile Registration Process ............................................................................................................... 7
Series-A (CIOM-A) FIM2 Architecture Overview..................................................................................................... 8
Series C FIM Architecture Overview ..................................................................................................................... 11
Combination Systems (FIM2, FIM4 and FIM8) ..................................................................................................... 12
H1 Power Conditioner Basics................................................................................................................................ 13
FOUNDATIONTM Fieldbus Performance Limits .................................................................................................... 14
FOUNDATIONTM Fieldbus Configuration Rules .................................................................................................... 20
FIM2 Configuration Rules ................................................................................................................................. 20
Redundant FIM2 Configuration Rules .............................................................................................................. 21
Mixed Redundant & Non-Redundant FIM2 Configuration Rules...................................................................... 21
Series C FIM (FIM4 & FIM8) Configuration Rules ............................................................................................ 22
Models and Specifications..................................................................................................................................... 23
CC-PFB401 (FIM4) Specifications.................................................................................................................... 23
Series C FIM4, IOTA Model Numbers .............................................................................................................. 23
CC-PFB801 (FIM8) Specifications.................................................................................................................... 24
Series C FIM8, IOTA Model Numbers .............................................................................................................. 24
TC-FFIF01, TK-FFIF01 FIM2 Specifications .................................................................................................... 26
TC-FFIF01, TK-FFIF01 FIM2 Specifications .................................................................................................... 27
CIOM-A FIM2, Cable and RTP Models ............................................................................................................ 27
CIOM-A FIM2 Unpowered RTPs ...................................................................................................................... 27
CIOM-A FIM2 RTP Specifications .................................................................................................................... 28
CIOM-A FIM2 Redundant Powered RTPs........................................................................................................ 28
Fieldbus Usage Licenses.................................................................................................................................. 29
Fieldbus Device Interoperability Testing ............................................................................................................... 30
Foundation Fieldbus Integration, Release 400 2
Foundation Fieldbus Integration, Release 400 3

Revision History

Revision Date Description

0.1 November 20, 2007 VCR spec modified for R310
1.0 July, 2010 Complete revamp to enhance existing
information and add new information for
R400

Fieldbus terminology used in this document:

H1: H1 is a term used to describe a Fieldbus network operating at 31.25 kbit/second.

H1 Field Device: An H1 Field Device is a fieldbus device connected directly to an H1 fieldbus. Typical H1 Field
Devices are valves and transmitters.

Interoperability: Interoperability is the capability for a device from one manufacturer to interact with that of
another manufacturer on a Fieldbus network without loss of functionality.

Link: A Link is the logical medium by which H1 Fieldbus devices are interconnected. It is composed of one or
more physical segments interconnected by bus, Repeaters or Couplers. All of the devices on a link share a
common schedule, which is administered by that link's current LAS. It is the data link layer name for a network.

Network: A network as applied in this document is the termination of one or more Fieldbus segments into an
interface card of the host system.

Commentary:
In this document the term “link” and “network” will be used interchangeably.

Segment: A Segment is a section of an H1 fieldbus that is terminated in its characteristic impedance.

Segments can be linked by Repeaters to form a longer H1 fieldbus. Each Segment can include up to 32 H1
devices.
Foundation Fieldbus Integration, Release 400
Product Introduction
FOUNDATION™ Fieldbus (FF) is
an enabling technology for
completely integrating field
devices with digitally-based
process control systems. It
defines how "smart" field
devices communicate and
operate with other devices in a control network.
The Fieldbus Foundation is the leading organization
dedicated to a single international, interoperable fieldbus
standard and responsible for FOUNDATION Fieldbus.
Established in September 1994, the Foundation is a not-for-
profit corporation consisting of over 200 of the world's
leading suppliers and end users of process control and
manufacturing automation products.
The Experion® PKS System provides an effective and
robust Fieldbus interface through the following two I/O
families and form factors:
 Series C form factor (Figure-1, left module)
 Chassis I/O Series-A (CIOM-A) form factor (Figure-1,
right module)
The generic name used to identify both form factors is
Fieldbus Interface Module (FIM). The Experion FIMs are
high-performance components that completely and
transparently integrate FOUNDATION Fieldbus devices into
the Experion PKS system and help provide the benefits you
expect from this powerful technology.
A numerical value is usually added to the FIM designation
Figure 1. The Experion PKS Series C (left) and CIOM-A (right)
Fieldbus Interface Modules (FIMs)
4
to further identify the specific module and indicates the
number of FF H1 networks that are provided by the module.
Two modules are available today, as follows:
 FIM2 (CIOM-A form factor) with 2 H1 networks.
 FIM4 (Series C form factor) with 4 H1 networks.
 FIM8 (Series C form factor) with 8 H1 networks.
Note: FIM8 is a post R400 release item. Until further
notice, an RQUP is required for FIM8.
Product Description & Features
Robust Fieldbus design. The Series C FIM4 and FIM8
represents the latest advances in capacity, cost-
effectiveness and performance from Honeywell. It
integrates transparently with the Experion PKS C300
Controller and ACE node. The Series C FIM features a
high-capacity design that delivers system-wide integration
of data access, control, connections, diagnostics, and
alarms with the Experion PKS system.
The field-proven CIOM-A FIM2, installs in the Experion PKS
C200 Controller rack or in a remote I/O chassis rack to suit
the needs of the process. Like the Series C FIM, this field-
proven double-width chassis-based module features a high-
capacity design that delivers all of the benefits of a world-
class Fieldbus integration.
Fieldbus is completely and transparently integrated into a
single, unified database using a common engineering tool.
Either FIM may be used with or without their respective
Controllers. Experion supports mixed system containing
FIM2, FIM4 and FIM8.
Foundation Fieldbus Integration, Release 400 5

Easy engineering with Control Builder. Control Builder
is the Experion PKS engineering tool for creating and
configuring process control strategies, including those
utilizing Fieldbus. Time-saving Fieldbus-specific features
such as:
 Creation of FF device templates from vendor DDs
and EDDLs (starting in R400)
engineering effort is required, and implementation time is
minimal. Experion PKS provides flexibility to create your
own custom detail displays. Experion PKS also features
device replacement directly from the operator station. A
failed or troublesome device can be securely replaced with
a new or repaired one without need for engineering support.

 Full device configuration from within CB

Uncommisioned
Devices

Figure 4. Chart Visualization gets the right

information to the operator

Experion R400 now supports vendor provided EDDL files

Figure 2. Experion PKS Control Builder provides on-line
 Assignment of FF device function blocks to the
control strategy
which greatly enhance the device HMI by the use of
graphics and trends and by allowing the device vendor to
better define where and how parameters are displayed and
located.

 Commission and un-commission devices

 Device firmware download

 Device replacement wizards

 Device maintenance and troubleshooting

Chart Visualization to get the correct information to the

operator. Chart Visualization is a powerful feature that
presents device blocks (Resource and Transducer) and
function blocks (AI, AO, PID, etc.) with all manufacturer-
defined information directly to the operator. With Chart
Visualization, there is no need for custom forms or displays
for every type of device.

There is also no need to worry about the security of

parameters. Access follows the Station security level and is
Figure 3. Experion PKS can simultaneously
the same as for parameters all other displays. No special download firmware to multiple devices!
Foundation Fieldbus Integration, Release 400
Full Support for Link Active Schedule and Backup Link
Schedule. The Link Active Scheduler (LAS) can be
considered the traffic cop that determines when and how
every FF device (including the FIM) will access the H1
network and what data they will transfer. One device (at any
given time) is the LAS. Others can be assigned as backups
in the event the lead LAS fails (backup FIMs are always
considered the first backup LAS device). Other FF devices
Figure 5. Experion PKS’s graphical Link
Schedule display with Optimization
can also be configured as backup LAS devices.
LAS setup and management is essential to effective FF H1
communications. Experion provides a best in class solution
for the management of the LAS component. Graphical
support of the Link Active Schedule (LAS) is an important
Experion tool for building schemes around Fieldbus.
Experion PKS supports the Back-up Link Active Schedule in
multiple LAS-capable devices, for highest possible
robustness. Link Schedule Optimization maximizes
available communications bandwidth, allowing for more
devices and better performance, resulting in significant cost
savings over competitive systems.
FIM Redundancy
All FIM types support full automatic redundancy. Fieldbus
function blocks continue to execute and communicate
during switchover or failover. With Honeywell’s advanced
diagnostics, the primary and secondary FIM modules are in
constant communication. The absence of a redundant
partner, for example, is detected and announced to the user
in the form of a system notification, not a process alarm.
6
Diagnostics are also provided for a potential failure or
problem with Fieldbus power. In the event of a power
problem on the RTP, IOTA or link, the FIM alerts the
operator with a system alarm.
FDM (Field Device Manager)
Experion Control Builder and Station provides the ability to:
 Fully configure all Foundation registered FF devices
(using DDs or EDDLs)
 Fully configure the control and logic scheme
 Display and monitor all FF device parameters,
conditions, events, and alarms
 Perform preventive maintenance tasks
 Perform responsive maintenance for devices that have
failed
Figure 6. Control Builder provides consistent
configuration of devices and control strategies along
as well as transparent redundancy implementation
FDM R410 includes functions and features focused on
Foundation Fieldbus devices. FDM provides an additional
level of coverage in the asset management arena. FDM
communicates through the FIM to access Fieldbus Devices.
FDM is intended for the maintenance user and provides an
environment optimized for the maintenance individual. FDM
and Experion provide a complete Fieldbus solution. Refer to
the latest FDM specification document for more details.
Foundation Fieldbus Integration, Release 400 7

Fieldbus Testing and Validation

Fieldbus Host Interoperability Test.

For all release prior to R400, the Experion PKS Fieldbus
solution has successfully completed the FOUNDATION
Fieldbus Host Interoperability Support Testing (HIST),
performed at Honeywell’s Fieldbus Interoperability Test Lab
and witnessed by a Fieldbus Foundation representative.
HIST procedures provide a common methodology for
assessing host interoperability with registered devices.

As of January, 2009 the Foundation has implemented a

new and mandatory validation process for Host systems
referred to as the “Host Profile Registration” process.

New Host Profile Registration Process

The Fieldbus Foundation's previous Host Interoperability
Support Test (HIST) provided a host test protocol with no
provision for formal product registration. With HIST, the host
vendor chose the implementation.

As of January, 2009 all HOST systems must pass a formal

test process (administered by the foundation) to be
considered an official registered Host.

Under the new Host Profile Registration Process, the

foundation conducts functional testing with a test device
and specialized test Device Descriptions (DDs) and
Capabilities Files (CFs). The host profile under test must
support a clear set of required features.

Use of the FOUNDATION Product Registration symbol in

conjunction with a foundation-registered host is the
manufacturer's representation that a sample of the product
has successfully completed all requirements specified in the
Host Profile Registration Process.

With Experion R400 and going forward, Experion is a 61a

compliant system and has passed all required Host Profile
registration testing.

Refer to the foundation website at the following link for proof

of compliance. Host systems that have not passed the
formal testing cannot appear on the website.

http://www.fieldbus.org/
Foundation Fieldbus Integration, Release 400 8

Series-A (CIOM-A) FIM2 Architecture Overview

The FIM2 occupies two slot positions (a two wide module) in a standard Series-A chassis. The FIM2 can be implemented in
a non-redundant or optionally redundant configuration. Each FIM2 (non-redundant or redundant) supports two FF H1
networks. For more details Series-A implementation refer to the associated Knowledge Builder documentation (such as the
“Experion Control Hardware Planning Guide”).

The FIM2 can be located locally in the Control Processor Module (C200 or C200e) chassis, or remotely, up to 10 kilometers
away (in a down link I/O chassis). H1 link connections are made using the FIM2 RTP (remote terminal panel). As with all
FIMs, the FIM2 can be used with a control process or can be implemented as a standalone module. When a control
processor is used, the FIM2 can only interface with the C200 or C200e (not the C300).

Figure-7 provides a simplified diagram of a non-redundant FIM2 configuration. The FIM2 is shown here in the control
processor chassis, but it can also be placed into any remote I/O chassis. Not shown in this figure, is the connection between
processor chassis and the remote I/O chassis. This is accomplished using a CNI (ControlNet Interface) module in the control
processor and the remote chassis. All communications are over the I/O ControlNet media.

The FIM2 connects to an RTP (Honeywell or 3rd party, DIN rail mountable) that provides the connection point for each of the
two H1 networks. Up to 16 FF devices can then be connected to each H1 network. Not shown here is the power conditioner
that is required for each network. These are 3rd party components. For the CIOM-A FIM2, qualified third-party DIN-rail
mounted Remote Termination Panels (RTPs) allow link power to be maintained in the unlikely event the FIM is shut down or
disconnected.

Communications back to the EVS (Experion Server) is either over ControlNet or FTE. For ControlNet a CNI is used as the
interface module. For FTE an FTEB module is used.

FTE or
ControlNet
Series-A Chassis
I
n CPM FIM
t 2
r

ESV
RTP

H1 network 2
FF FF FF FF FF
D D D D Device

H1 network 1
FF FF FF FF FF
D D D D Device

Figure 7. Series-A (CIOM-A) FIM2 (Non-Redundant configuration) with two H1 Networks

Foundation Fieldbus Integration, Release 400 9

Refer to Figure-8. This shows a simplified diagram of a FIM2 implemented in a redundant configuration. The primary and
backup FIM2 are located in two different chassis. They are synchronized via the RM (Redundancy Module) and a sync cable
interconnecting the two RM modules. Redundancy can be implemented in two processor chassis or by using two remote I/O
chassis.

Both primary and backup FIM2 use a common RTP (Honeywell or 3rd party, DIN rail mountable) that provides the connection
point for each of the two H1 networks. Up to 16 FF devices can then be connected to each H1 network. Not shown here is
the power conditioner that is required for each network. These are 3rd party components. For the CIOM-A FIM2, qualified
third-party DIN-rail mounted Remote Termination Panels (RTPs) allow link power to be maintained in the unlikely event the
FIM is shut down or disconnected.

Communications back to the EVS (Experion Server) is either over ControlNet or FTE. For ControlNet a CNI is used as the
interface module. For FTE an FTEB module is used.

FTE or
ControlNet
Series-A Chassis
I
n CPM RM FIM
t 2
r
Sync

ESV
RTP
I
n CPM RM FIM H1 network 2
t 2
FF FF FF FF FF
r D D D D Device

H1 network 1
FF FF FF FF FF
D D D D Device

Figure-8 Series-A (CIOM-A) FIM2 (Redundant configuration) with two H1 Networks

Foundation Fieldbus Integration, Release 400 10

FIM2 RTP notes

The CIOM-A Fieldbus Interface Module (FIM2) connects to a DIN-rail mounted Remote Termination Panel (RTP) via a FIM
Cable (available in several lengths). Unpowered RTPs are available as standard Honeywell products, and powered RTPs
are available from P+F and MTL as described later in this document.

An RTP supports two (2) H1 Fieldbus link connections. CIOM-A FIMs can be placed in all rack locations that support Series
A Chassis I/O. Like the Series C FIM, the CIOM-A FIM does not require presence of the C200 controller.

The FIM may be used in either non-redundant or redundant configurations. A non-redundant FIM can be located in a C200
or remote I/O chassis and connects to a single Non-Redundant RTP. Redundant FIM pairs reside in redundant racks
following the same rules as C200 Controller and IO Link Module redundancy (racks must be identical in every way).

The Redundant RTP has two FIM cable connections, and each FIM in the redundant pair connects via a separate FIM cable.

For additional details refer to the following sections in this document:

H1 Power Conditioner Basics

FOUNDATIONTM Fieldbus Performance Limits

FOUNDATIONTM Fieldbus Configuration Rules

Foundation Fieldbus Integration, Release 400 11

Series C FIM Architecture Overview

Refer to Figure-9. All Series C interface modules, I/O modules, and the C300, use the concept of an IOTA (Input Output
Terminal Assembly) that mounts to a standard Series C mounting channel assembly. This provides for a standardized
cabinet, mounting, and power and grounding infrastructure for all Series C modules (see appropriate Knowledge Builder
documents for additional details).

The FIM4 module is provided in the Series-C form factor. As Figure 9 shows it can be mounted to a non-redundant or
redundant IOTA. The non-redundant IOTA is 6 inches long, while the redundant IOTA consumes 12 inches of channel
space. The user can implement the FIM4 as a non-redundant module by using the non-redundant IOTA, or by mounting only
one FIM4 (upper position) to a redundant IOTA. This will allow the user the option to easily add a second FIM4 later if
redundancy should become necessary.

Figure-9 also shows the various connection points. Note that 24 Vdc (to power the modules) is provided by mounting the
IOTA to the channel and carrier assembly. This 24 Vdc supply is isolated from the 24 Vdc that is provided by the separate
power conditioners connected to each of the four H1 networks. Each IOTA provides four H1 connectors (one for each of the
H1 networks). There are also FTE (grn & yel) connectors for each FIM4 module. The FIM4 FTE (IP) index address is also
set using the rotary switches on the IOTA. This represents the last octet of the four octets that make up the complete IP
address. A connector is provided for the power conditioners (from P+F and MTL) that are provided on Series C IOTAs and
mount on the standard Series C channel assemblies. This provides for easier wiring when these conditioners are used, but
the user can also implement conditioners from other 3rd party venders and hard wire the conditioners in using standard FF
H1 practices. Note that all power conditioners and the H1 network are isolated from the Series C power system.

The FIM4 is a standard FTE node. The FTE cables must be connected to a CF9 (Control Firewall). This can be the same
CF9 as the associated C300 or can be a separate CF9 in the case of a remote configuration. FIM4 can be used with a
control process or can be standalone. When used with a control processor it can only be a C300 (no C200 or C200e
allowed).

The FIM8 is new for R400 and can be considered a FIM4 with 4 additional H1 links. FIM8 has a redundant IOTA only. For
non-redundant configurations the FIM8 module is inserted into the upper module position of the redundant IOTA. The odd
and even FTE address is always consumed. The user can easily add a backup FIM8 at any time. Refer to Figure-9 and the
redundant FIM4 IOTA. The FIM8 IOTA is similar, but has 8 H1 connectors and 2 power conditioner connectors. Both IOTAs
are 12 inches long. At this time an RQUP is required for FIM8.

Non-Redundant Redundant
H1 (1) IOTA IOTA
FTE Green FTE Green
H1 (1) Primary
H1 (2) OK 3
H1 (2)
OK 3

FTE Yellow H1 (3) FTE Yellow

H1 (3) H1 (4)
H1 (4) Power Cond FTE Green
OK 3 Backup
FTE address (lowest octet) FTE Yellow

Connector for
MTL & P+F power FTE Address
conditioners. Set odd address for primary FIM4
next even address is assumed for backup.

Figure-9 Series C FIM4 IOTA types (redundant and non-redundant)

Foundation Fieldbus Integration, Release 400 12

For additional details refer to the following sections in this document:

H1 Power Conditioner Basics

FOUNDATIONTM Fieldbus Performance Limits

FOUNDATIONTM Fieldbus Configuration Rules

Combination Systems (FIM2, FIM4 and FIM8)

The Experion system fully supports clusters that are composed of mixtures of FIM2 (C200, C200e) and FIM4/FIM8 (C300)

For details refer to the following sections in this document:

FOUNDATIONTM Fieldbus Performance Limits

FOUNDATIONTM Fieldbus Configuration Rules

Foundation Fieldbus Integration, Release 400 13

H1 Power Conditioner Basics

Refer to Figure-10. This diagram shows a simplified depiction of a typical H1 network. All FF devices are connected to the
network in parallel. The power condition is also connected to the network in a parallel arrangement and supplies 24 Vdc to
power each connected device. The power conditioner can be implemented in a non-redundant or redundant configuration.

A typical device will use between 10 and 20 mA. The number of devices and the power consumed by each will determine the
size of the power conditioner (in amps) required. For the example below, assume each device requires 20 mA to operate
properly. The power conditioner would need to be capable of supplying 80 mA (4 x 20 mA).

A terminator must be placed at each end of the network to support proper communications.

Digital communications: Each device (when communicating on the H1 link) will toggle the 24 Vdc to generate the digital
portion of the H1 communications. An H1 power conditioner must have added circuitry to tolerate this digital component and
still provide the 24 Vdc required by each device. A standard of the shelve power supply could not provide this capability (this
is what makes the power conditioner unique). The FIM2, and FIM4 and FIM8 are considered a device with regard to this
example. Although they do not use any power from the conditioner for their operation, they will use about 10 mA when
signaling on the H1 link.

Power Conditioner Validation: Honeywell does not validate any 3rd party power conditioners at this time. Any power
conditioner that complies with the Foundation test specification FF-831 (Fieldbus Power Supply Test Specification) should
operate properly with the Honeywell FIM modules.

Power conditioners may provide other features that make them suitable for applications such as intrinsic safety. Refer to the
3rd party website for more details and features.

H1 network
+

Power
FF FF FF FF
T Conditioner device device device device T
Primary
Backup

Figure-10 H1 Power Conditioner Basics

MTL and P+F Conditioners: These venders have adapted there power conditioners to mount to standard Series C IOTAs
and provide RTPs in the case of the FIM2. More information is provided later in the document.
Foundation Fieldbus Integration, Release 400 14

FOUNDATIONTM Fieldbus Performance Limits

R400 introduces support for a new Series C FIM that supports 8 H1 Links called FIM8.

ATTENTION!
The FIM8 Hardware will be released “after” the R400.1 release. R400.1 has
been qualified to support the FIM8 when the module is ready to be manufactured
and released to the field at a later TBD date.
All specifications for the FIM8 in this version of the Spec are subject to
change until the FIM8 is fully validated & released to the field.

All FIM performance & capacity specification are described in the following sections.

Acronyms*
In order to distinguish the different FIM Module types and their specific and joint specifications, the following acronyms will
be used in this section of the Spec.

FIM – If this acronym is used without a number, then the specification applies to all FIM module types.

FIM2 – The Series A chassis-based FIM used with the C200 Controller and supported on ControlNet or FTE (via FTEB).
This FIM supports 2 H1 Links and can be deployed in a redundant or non-redundant Series A Chassis.

FIM4 – A Series C FIM used with the C300 Controller and only supported on FTE. This FIM supports 4 H1 Links and can be
deployed in a redundant or non-redundant manner using the appropriate IOTA type.

FIM8 – A Series C FIM used with the C300 Controller and only supported on FTE. This FIM supports 8 H1 Links and can be
deployed in a redundant or non-redundant manner using the appropriate IOTA type.

Figure- 11 provides an overview of the FIM2, FIM4 and FIM8 communication architecture. Key concepts important to
understand are the following.
 The Link Active Schedule (LAS) of each H1 network defines the scheduled publication of data and provides time for
unscheduled data access

 All data supplied by the FIM resides in the FIM cache

 The CDA subsystem uses both publish/subscribe and request/response mechanisms to deliver data to the requesting
clients

o The FIM’s PUBMETHOD parameters can be configured to specify the CDA Publish Data Rate per H1
Link between the FIM and its associated C200 or C300 controller.

 Updating the cache with new/fresh values from the H1 networks and CDA delivery of data from the cache to the
interested clients should be thought of as independent activities

 The freshness of data in the cache depends on the number of parameters in the cache, device performance, and the
unscheduled bandwidth available on the H1 networks.

FIM related specifications are presented in the tables following Figure 11.
Foundation Fieldbus Integration, Release 400 15

FIM

Figure- 11 FIM2/FIM4/FIM8 Communication Architecture

Foundation Fieldbus Integration, Release 400 16

FF System Specifications

Capacity Description FIM2 FIM4 FIM8

1
Maximum Number of FIMs per Controller 21 non-redundant or 15 8
12 redundant Redundant or non- Redundant or non-
 C200 and C200E only supports FIM2 redundant in any redundant in any
combination combination
 C300 only supports FIM4 & FIM8
(60 H1 Links) (64 H1 Links)

Maximum Number of FIMs per Server L1 ControlNet 125 125

100 physical FIM2s Redundant or non- Redundant or non-
redundant in any redundant in any
(50 redundant pairs)
combination of FIM2s, combination of FIM2s,
Note: Combinations of FIM2, FIM4, & FIM8 on the L1 FTE FIM4s and/or FIM8s FIM4s and/or FIM8s
same Server is supported on FTE-based systems at 125
the 125 FIM limit. See Section Redundant or non-
FOUNDATIONTM Fieldbus redundant in any
combination of FIM2s,
Configuration Rules for any constraints on FIM4s and/or FIM8s
mixed FIM systems.

Maximum Number of Fieldbus Devices per L1 ControlNet 8,000 12,000

1600 (w/red-FIM2s) (using FIM4 only) (using FIM8 only)
Server
3200 (w/non-red FIM2s)
L1 FTE
4000 (using FIM2 only)

Note 1 – Any redundant and non-redundant combination cannot exceed 21 “Active/Primary” FIMs
Note 2 – With 21 FIM2s assigned under the same C200 or C200E Controller, the Cluster will only support 10 ESC or EST
Nodes. If more than 10 ESCs or ESTs is required, the maximum number of non-redundant FIM2s allowed is 20 or
less.

FF FIM Specifications

Capacity Description FIM2 FIM4 FIM8

Number of H1 Networks per FIM 2 4 8

Maximum Number of FF Blocks per Fieldbus Device 30 30 30

Maximum Number of FF Blocks per FIM 500 1600 3200

ATTENTION

Note: Blocks are counted whether or not the FF

Device’s Blocks are being used/loaded or not in the
FIM strategy. Resources to support every Device’s
Block set must be reserved when the FF Device is
configured on one of the FIM’s H1 Networks.
For example, a device with 1 resource block, 5
transducer blocks and 5 function blocks will
consume 11 blocks from the total block count. It
does not matter if the function blocks are in use or
not.
Foundation Fieldbus Integration, Release 400 17

FF FIM Specifications

Capacity Description FIM2 FIM4 FIM8

Maximum Number of Unique FF Block Types per 100 200 200

FIM
Note: Unique FF Block Types are defined as the number of
unique blocks across all devices connected to a FIM. Each
time a new unique device is connected to the link, one
unique block type may be reserved for each unique block in
that device.
For example, suppose device X, containing an AI and a PID
block, is connected to a FIM. This would reserve two
unique block types. Adding several more of this device to
the FIM would not require additional unique block types.
Suppose a different device Y, containing an AO, is
connected to the FIM. This would reserve one unique block
type.

Maximum Number of Parameters in FIM cache 800 1600 3200

Note: The maximum number of parameters in the FIM
cache defines the maximum number of parameters that may
be accessed for control, monitoring, and configuration at
any given time.

Maximum Peer Connections per FIM 5 5 5

1
FIM Publication Method options Immediate Immediate Immediate
Note: The FIM Publication Method (PUBMETHOD) is 250 msec 250 msec 250 msec
configurable on a per segment/H1 network basis on the FF
500 msec 500 msec 500 msec
Link function block and controls how frequently data is
published between the FIM2/FIM4/FIM8 and C200/C300 1000 msec 1000 msec 1000 msec
controller.

Overall Data Access performance - CDA 1000 PPS 1600 PPS 2000 PPS

FIM Cache Parameter Refresh Rate 1 second minimum 1 second minimum 1 second minimum
Note: FIM Cache will refresh parameter values at a
maximum rate of once per second. If all parameters cannot
be refreshed within one second due to bandwidth
limitations, the FIM will allocate additional time as needed.
Actual performance will depend on number of parameters
within FIM Cache, device performance, and unscheduled
bandwidth available on H1 Network

Note 1 – This option provides a trade-off between controller performance and control end-end response time. Slower
publication will reduce the network traffic and the performance load on the controller, but increase the overall end-
end response time of a loop (assume AI and AO devices are on H1 and PID is in C300). Conversely, faster
publication will increase the network traffic and increase the performance load on the controller, but decrease the
overall end-end response time of a loop.
Foundation Fieldbus Integration, Release 400 18

FF H1 Network Specifications

Capacity Description FIM2 FIM4 FIM8

Maximum Number of Fieldbus Devices per H1 Network 16 16 16

Note: The maximum number of supportable devices per

network is highly dependent on application, bandwidth, devices,
available current, bus length and topology. An understanding of
Fieldbus is crucial to system sizing.

Agents per H1 Network 50 per H1 Network 100 per H1 100 per H1

Note: An agent is used to transport data between CEE blocks
Network Network
and FF blocks. Agent specifications are measured on a per H1
Network basis. Agents are displayed in the link schedule when
viewed with Control Builder.

A connection between a CEE block and an FF block reserves

one agent.

Maximum Number of VCRs (Virtual Communication 64 per H1 Network, 128 per H1 128 per H1
128 per FIM2 Network, Network,
Relationships) per H1 Network
See Note 1 512 per FIM4 1024 per FIM8
Note: A VCR is a connection endpoint on the H1 Network. VCR
See Note 1 See Note 1
specifications are measured on a per H1 Network basis.
Each connected device reserves two VCRs. A published
connection between a CEE block and an FF block reserves one
VCR. A published connection with back initialization between a
CEE block and an FF block reserves two VCRs. Connections
between FF blocks on a single device or between multiple
devices do not reserve VCR resources on the FIM. It is
recommended that at least one VCR be left free to facilitate
device replacement and any control strategy reloading.

Maximum Scheduled Single-Variable Publications per 16 per H1 Network 16 per H1 Network 16 per H1 Network
Second per H1 Network
Note: Scheduled Single-Variable Publications per Second may
include publications from devices to other devices, from devices
to the FIM, and from the FIM to other devices.

Unscheduled Parameter Reads per Second per H1 16 per Fieldbus 16 per Fieldbus 16 per Fieldbus
Device, Device, Device,
Network
40 per H1 Network 40 per H1 Network 40 per H1 Network
Note: Unscheduled parameter read performance is provided as
a guideline. Actual performance will depend on device
performance and unscheduled bandwidth available on H1
Network.

Unscheduled Parameter Writes per Second per H1 5 burst, 1 sustained 5 burst, 1 5 burst, 1
per Fieldbus Device, sustained per sustained per
Network
20 burst, 5 sustained Fieldbus Device, Fieldbus Device,
Note: Unscheduled parameter write performance is provided as
per H1 Network 20 burst, 5 20 burst, 5
a guideline. Actual performance will depend on device and
sustained per H1 sustained per H1
unscheduled bandwidth available on H1 Network.
Network Network

Available Macrocycle Periods 250, 500 ms.; 1, 2, 4, 250, 500 ms.; 1, 2, 250, 500 ms.; 1, 2,
8, 16, & 32 sec. 4, 8, 16, & 32 sec. 4, 8, 16, & 32 sec.

Note 1 – Device reload or device replacement functionality requires at least one free VCR on a Fieldbus link/segment. If a
segment is configured with the maximum number of VCRs allowed (64 for the FIM2 or 128 for the FIM4), a device replacement
will not be able to done without freeing a VCR on the segment first. Freeing a VCR is typically done by deleting a CM or device
from the monitoring tree. Therefore, it is recommended that at least one VCR is kept free so that device reloads or replacement
will not require a VCR to be freed first. Control Builder will display a warning message when a segment is low on free VCRs.
Foundation Fieldbus Integration, Release 400 19

FF Link Active Schedule (LAS) Specifications

Capacity Description FIM2 FIM4 FIM8

Number of LAS Domains per FIM 2 2 2

Maximum LAS Schedule Size 800 bytes/LAS 2000 bytes/LAS 2000 bytes/LAS

Number of Sub-schedules per LAS 4 4 4

Note: For example, a 2 second macrocycle could have sub-
schedule periods of 1 second, 500 msec, and 250 msec.

Number of sequences per sub-schedule 64 64 64

FF Advanced Alarming Specifications (New for R400)

Capacity Description FIM2 FIM4 FIM8

Custom conditions per device template 32 32 32

Device parameters used in any/all conditions, per device template 10 10 10

1
Individual parameter references, per device template 36 36 36

Note 1 - For a device template, among the (max) 32 conditions, there can only be 36 total references to device parameters.
For example, you can’t have each of the 32 conditions reference the same 2 parameters, since that would create 64
references. See following formula:

Where N = 31, and ConditionParameters = the number of parameters referenced in condition i.

Foundation Fieldbus Integration, Release 400 20

FOUNDATIONTM Fieldbus Configuration Rules

FIM2 Configuration Rules

CR 1.0 The Series A FIM (aka FIM2) is a doublewide module, utilizing two chassis positions and may be located in any
pair of chassis slots in any size Series A chassis.
CR 1.1 FIM2s may co-reside with a controller, within the power constraints of a chassis.
CR 1.2 FIM2s may reside in a FIM-only chassis. This chassis may reside on a Supervisory ControlNet or FTE Network
or on an I/O ControlNet. The number of FIM2s per chassis must fit within the power constraints of a chassis.
CR 1.3 Each C200 (and C200e) Controller can support FIM2s (redundant or non-redundant up to the maximums allowed
per controller & per server) connected either to the Supervisory Network (ControlNet or FTE) or to an I/O
ControlNet “under” the Controller, but not to both concurrently. In other words, all of the FIM2s connected to a
single controller must reside either on the Supervisory Network or on the I/O Network, but not split between the
two locations. Different C200s in the same Cluster may use either of these configurations simultaneously, e.g.
one C200 uses FIM2s on the Supervisory Network, and another uses FIM2s on its I/O Network.
CR 1.4 FIMs are not supported on any Experion Cluster (in any location) using Ethernet Supervisory network, e.g. using
TC-CEN011 (obsolete) or TC-CEN021 Ethernet Modules in the C200s.
CR 1.5 The use of FIMs by a controller will reduce the allowed I/O used by that controller based upon the IO Unit loading
limits specified in other sections of this document.
CR 1.6 All FIM2 capacity and performance limits found in previous section must be observed.
CR 1.7 The recommended maximum number of single-variable publications per second on an H1 link is 16. The
maximum percentage of publications permitted in the schedule is 50%, guaranteeing time for alerts and client-
server communications. (Each Pub requires a Compel Data (CD) to kick it off + the Analog pub time. The two
consume about 28ms. So 28ms x 16 = 448ms. When housekeeping functions like token passing and time
distributions are included, the total is ~ 50% of bandwidth)
CR 1.8 The macrocycle is the longest cyclic period on the link. It may have a maximum of 4 sub-schedules. For
example, a 2000ms macrocycle could have sub-schedule periods of 1000ms, 500ms, and 250ms. (Sub-
schedule periods must be exactly divisible into the macrocycle period.)
CR 1.9 A given FIM can connect to a maximum number of 5 C200 controllers (using peer-to-peer connections). (In the
future, it is planned that FIMs will be able to connect to other FIMs as peers to support controller-less bridging.)
CR 1.10 Non-redundant FIM2s may not be co-resident in a chassis with I/O modules. All FIM2s should reside on separate
ControlNet segments and the path from the C200 to the FIM2 should not share any CNI modules that are being
used in the path from the C200 to Series A IOMs.
CR 1.11 FF H1 Wiring rules: The ISA SP50.02 standard and the Fieldbus Foundation specify rules for maximum wire
and spur lengths based on cable type. Although the rules have some complexity, there are simplified guidelines
that apply in most instances.
CR 1.12 The FIM2 is not intended for use with the 5 ms CEE execution because CEE execution generally exceeds FF
sampling and transport rates.
CR 1.13 The FIM is not intended for use with any CEE that executes more frequently than the FF device sampling and
transport rate and CDA transport rate.
CR 1.14 A FIM can communicate to a single or to multiple controllers using CDA services. Notes: Rule CR 1.15 will
constrain FIM communications to multiple controllers only when the FIM chassis is resident in the Supervisory
ControlNet or FTE.
CR 1.15 FIM2 Peer-Peer connections are limited to a single “hop” (network segment) from one network node to another
node on a ControlNet or FTE network. For example, a C200 or ACE can’t talk to a FIM2 on a remote ControlNet
I/O segment belonging to another C200, because it would have to go across the Supervisory Network (1st hop)
and then across the I/O Network (2nd hop).
CR 1.16 Series D CNI modules must be used in conjunction with the FIM2 on any ControlNet segment.
CR 1.17 FIMs may be used in systems that also contain Experion Console Station-TPS (ES-T) nodes, but the number of
Console Stations in such a mixed system cannot exceed 11.
Foundation Fieldbus Integration, Release 400 21

Redundant FIM2 Configuration Rules

CR 1.18 Redundant Chassis Pairs must be configured identically - same size chassis, same Redundancy compliant
module types located in the same slots in each chassis, and one Redundancy Module per chassis connected
with an RM Fiber cable. This rule applies to Controller Redundant chassis with FIMs, as well as Redundant FIM-
only chassis.
CR 1.19 Quantity of FIMs per chassis is subject to available slots and power. CNI(s) and RMs must be considered. A
remote I/O chassis, for example, will support a CNI, RM and up to 6 FIMs. A C200 Controller chassis will support
a CNI, C200, and RM and up to 4 FIMs and up to two more CNIs or up to 3 FIMs and an additional IOLIM within
power constraints.
CR 1.20 FIM-only redundant chassis CNI modules will follow the same ControlNet MACID address assignment rules as
those applied to Controller RCP chassis.
CR 1.21 A Redundant FIM-only chassis can support only one CNI module that is connected to either the Supervisory
ControlNet or to a Remote I/O ControlNet segment under a C200 Controller chassis.
CR 1.22 FTEB-based FIM-only or Redundant FIM-only chassis may only be connected to the L1 FTE Control network,
and must follow the same FTE Device Index assignment rules as FTEB-based C200 chassis.
CR 1.23 Redundant FIM2s must use the new redundant compliant Fieldbus RTP – part # TC-FSU01

Mixed Redundant & Non-Redundant FIM2 Configuration Rules

CR 1.24 Cannot mix Redundant & non-Red FIM2s in the same chassis.
CR 1.25 The number of FIM2s per downlink CNI must be calculated using 3 IO Units for each non-redundant FIM and 4
IO Units for each Redundant-FIM with a maximum of 24 IO Units maximum allocated for each downlink CNI.
CR 1.26 The following table describes the allowable combinations of Redundant and non-redundant FIM2s per C200.
Total
Redundant Non-Red Active Total IO Units to be Downlink CNIs
Physical
FIMs FIMs (Primaries) divided into 24/CNI required
FIMs
0 21 21 21 63 3
1 20 21 22 64 3
2 19 21 23 65 3
3 18 21 24 66 3
4 16 20 24 64 3
5 14 19 24 62 3
6 12 18 24 60 3
7 10 17 24 58 3
8 8 16 24 56 3
9 6 15 24 54 3
10 4 14 24 52 3
11 2 13 24 47 2
12 0 12 24 48 2

CR 1.27 The FIM2 is not supported with the C300 Controller.

CR 1.28 Any FIM2 configuration above that results in 21 Active Primary FIM2s will constrain the cluster to only 10 ESCs or
ESTs allowed.
Foundation Fieldbus Integration, Release 400 22

Series C FIM (FIM4 & FIM8) Configuration Rules

CR 1.29 The Series C FIM (FIM4 or FIM8) is a standalone module that will be present directly on the L1 FTE network via
the CF9 Module.
CR 1.31 The C200 Controller does not support the FIM4 or FIM8.
CR 1.32 Each C300 Controller can support Series C FIMs (redundant or non-redundant up to the maximums allowed per
controller & per server) connected to the L1 FTE Network.
CR 1.33 The use of FIMs by a controller will reduce the allowed I/O used by that controller based upon the IO Unit loading
limits specified in other sections of this document.
CR 1.34 All FIM4 and FIM8 capacity limits found in the previous section must be observed.
CR 1.35 The recommended maximum number of single-variable publications per second on an H1 link is 16. The
maximum percentage of publications permitted in the schedule is 50%, guaranteeing time for alerts and client-
server communications. (Each Pub requires a Compel Data (CD) to kick it off + the Analog pub time. The two
consume about 28ms. So 28ms x 16 = 448ms. When housekeeping functions like token passing and time
distributions are included, the total is ~ 50% of bandwidth)
CR 1.36 The macrocycle is the longest cyclic period on the link. It may have a maximum of 4 sub-schedules. For
example, a 2000ms macrocycle could have sub-schedule periods of 1000ms, 500ms, and 250ms. (Sub-
schedule periods must be exactly divisible into the macrocycle period.)
CR 1.37 A given FIM4 or FIM8 can connect to a maximum number of 5 combined C300 controllers or ACEs (using peer-
to-peer connections).
CR 1.38 FF H1 Wiring rules: The ISA SP50.02 standard and the Fieldbus Foundation specify rules for maximum wire
and spur lengths based on cable type. Although the rules have some complexity, there are simplified guidelines
that apply in most instances.
CR 1.39 The FIM is not intended for use with any CEE that executes more frequently than the FF device sampling and
transport rate and CDA transport rate.
CR 1.40 A FIM can communicate to a single or to multiple controllers using CDA services.
CR 1.41 FIMs may be used in Experion on TPS clusters that also contain ESVT & EST nodes. EST limits are constrained
if FIM2s with FTEB are used:
Use of FTEBs w/C200, C200E, or FIM2 constrains the limit to 11 ESCs or ESTs and in a special case, if more than
20 non-redundant FIM2s are configured with 1 C200 or C200E, then only 10 ESCs or ESTs are allowed.
CR 1.42 Redundant Series C FIM4 Pairs require a redundant IOTA. A non-redundant IOTA cannot be used for FIM4
redundancy.
CR 1.43 The FIM8 only supports a redundant IOTA and when FIM8 is Non-redundant, the secondary position in the IOTA
is left empty. That is, there is no non-redundant version of the FIM8 IOTA.
Foundation Fieldbus Integration, Release 400 23

Models and Specifications

Information in this section is intended to provide a set of specifications for the Experion PKS Foundation Fieldbus solution.

CC-PFB401 (FIM4) Specifications

Series C FOUNDATION™ Fieldbus Interface Module with 4 H1 Links (FIM4)

Parameter Specification
Module Type Series C module, conformally coated
Physical Interface H1 FOUNDATION Fieldbus
Number of H1 Networks per FIM 4
(Each network defined as a FOUNDATION Fieldbus 31.25 kbps H1 network)
Indicators on Module  24V Power, Module & FTE Status LEDs
 Front display panel with module and link state
information
Indicators on IOTA 4 H1 Link Status LEDs (1 per Link)
Configurations Non-redundant or Redundant (side-by-side)
Electro-static Discharge IEC 1000-4-2: 1995
Power Dissipation 5.3 watts
Module Current 0.212 amps @ 25 Vdc
Link Connection IOTA directly

Series C FIM4, IOTA Model Numbers

Model Number Model Description IOTA Length

CC-TFB401 FIM4 IOTA, Non-redundant, 4 Links, coated 6 inches

CC-TFB411 FIM4 IOTA Redundant, 4 Links, coated 12 inches

Foundation Fieldbus Integration, Release 400 24

CC-PFB801 (FIM8) Specifications

Series C FOUNDATION™ Fieldbus Interface Module with 4 H1 Links (FIM4)

Parameter Specification
Module Type Series C module, conformally coated
Physical Interface H1 FOUNDATION Fieldbus
Number of H1 Networks per FIM 8
(Each network defined as a FOUNDATION Fieldbus 31.25 kbps H1 network)
Indicators on Module  24V Power, Module & FTE Status LEDs
 Front display panel with module and link state
information
Indicators on IOTA 8 H1 Link Status LEDs (1 per Link)
Configurations Non-redundant or Redundant
Electro-static Discharge IEC 1000-4-2: 1995
Power Dissipation TBD
Module Current TBD
Link Connection IOTA directly

Series C FIM8, IOTA Model Numbers

Model Number Model Description IOTA Length

CC-TFB811 FIM4 IOTA Redundant, 8 Links, coated 12 inches

Note: this IOTA is also used for Non-redundant configurations.
Single IOTA is inserted into the upper module position.
Foundation Fieldbus Integration, Release 400 25

Redundant Powered IOTAs. The F660A Redundant Fieldbus Power IOTA, from MTL/Relcom, provides redundant power
for four H1 fieldbus links to a single Series C FIM IOTA, using two plug-in power modules per link. Each link includes a
switchable fieldbus segment terminator. Galvanic isolation is provided between the fieldbus segment and the input power
supplies. Output voltage and current are maintained even if one power module is available on a segment. A separate
module provides a FIM alarm in the event of a problem with any conditioning module or input. The F660A connects directly
to the Series C FIM IOTA via a multi-conductor cable.

For more information and specifications, contact MTL Incorporated, Houston, TX, at 713-341-7580.

Figure 12. Relcom F660A Redundant Fieldbus Power IOTA

Foundation Fieldbus Integration, Release 400 26

The F860 Redundant Fieldbus Power IOTA from MTL/Relcom provides redundant, isolated conditioned power for eight (8)
H1 fieldbus links, servicing two (2) redundant or non-redundant Series C FIM IOTAs. It requires the same footprint as the
F660A, and so offers greatly improved space usage. Connection to the IOTAs uses the same multi-conductor cable as the
F660A. An on-board, link connected diagnostic module provides detailed H1 performance information about all 8 links. The
F660 can be powered either from the Series C cabinet power supply or from an external power source.

Figure 13. Relcom F860 Redundant Fieldbus Power IOTA

(diagnostic module not shown)

The Pepperl+Fuchs Fieldbus Power Hub IOTA provides redundant, isolated power for four H1 fieldbus links to a single
Series C FIM IOTA, using two plug-in power modules per link. An on-board, diagnostic module provides detailed H1
performance information about all 4 links. Both basic and advanced versions of the diagnostic module are available.

For details and pricing, contact Pepperl+Fuchs Inc., 1600 Enterprise Parkway, Twinsburg, OH 44087-2245, at 330 486-
0171.

Figure 14. Pepperl+Fuchs Fieldbus Power Hub IOTA with Diagnostic Module
Foundation Fieldbus Integration, Release 400 27

TC-FFIF01, TK-FFIF01 FIM2 Specifications

Chassis I/O - CIOM-A FOUNDATION™ Fieldbus Interface Module (FIM2)
Parameter Specification
Module Type Double slot-width chassis module (coated or
uncoated)
Physical Interface H1 FOUNDATION Fieldbus
1
Number of H1 Networks per FIM 2
(Each network defined as a FOUNDATION Fieldbus 31.25 kbps H1 network)
Configurations Non-redundant or redundant
Electro-static Discharge IEC 1000-4-2: 1995
Power Dissipation 7.34 watt max.
Backplane Current See Reference Section
Module Connection to RTP TC-FFCxxx, Fieldbus RTP Cable
(see next two pages)

Model numbers for CIOM-A FIM2, Remote Termination Panels and cables are shown in the table below.

CIOM-A FIM2, Cable and RTP Models

Model Number Model Description
Fieldbus Interface Remote Termination Panels (RTPs)1
TC-FFRU01 Fieldbus RTP, Non-redundant, Unpowered
TC-FFSU01 Fieldbus RTP, Redundant, Unpowered
Fieldbus Interface RTP Cables
TC-FFC010 Fieldbus RTP Cable, 1.0 m
TC-FFC025 Fieldbus RTP Cable, 2.5 m
TC-FFC050 Fieldbus RTP Cable, 5.0 m
TC-FFC100 Fieldbus RTP Cable, 10 m
1
Coated versions (TK- vs TC-) or RTPs are also available.

CIOM-A FIM2 Unpowered RTPs

Figure 15. TC-FFRU01 -- Unpowered Fieldbus RTP Figure 16. TC-FFSU01 – Fieldbus RTP, Redundant,
(DIN-rails included but not shown) Unpowered (with DIN-rail mounts)
Foundation Fieldbus Integration, Release 400 28

CIOM-A FIM2 RTP Specifications

Parameter Specification
Remote Termination Panel (RTP) TC-FFRU01 TC-FFSU01
Description Unpowered, Non-Redundant Unpowered, Redundant
RTP Maximum Power Requirements None None
Fieldbus Current Available per Link Limited by user-supplied power Limited by user-supplied power
Terminators per Link None None
H1 Terminal Connection Type Compression Compression
RTP Dimensions (all models) 4.9" W x 6.1" L 4.9" W x 7.5" L
H1 Distance to Field Devices  Per Clause 22 of IEC 1158-22 specification
 Intrinsically safe distance limited by cable impedance (refer to
MTL Application Brief AB003 for more details)
Each RTP has two connectors to allow quick connection to each of the H1 links. Mating connector is Honeywell P/N 51190691-
102, Wiedmuller part number 150186.

Redundant Powered RTPs. For even greater robustness, Redundant Powered RTPs for use with FIM redundancy are
available from MTL and Pepperl+Fuchs. The MTL-Relcom F650A Redundant Fieldbus Power System provides
redundant Honeywell FIM connections as well as fully redundant, isolated power conditioners for each of two fieldbus
networks. For more information and specifications, contact MTL Incorporated, Houston, TX, 713-341-7580.

The Pepperl+Fuchs RTP for Honeywell Redundant FIM provides redundant FIM connections combined with non-
redundant power conditioners using high-reliability, passive components for each of two fieldbus networks. Up to 1 A of
conditioned power is available from each link. For details and pricing, contact Pepperl+Fuchs Inc., 1600 Enterprise
Parkway, Twinsburg, OH 44087-2245, (330) 486-0171.

CIOM-A FIM2 Redundant Powered RTPs

Figure 17. MTL-Relcom F650A Redundant Figure 18. Pepperl+Fuchs RTP FieldConnex MB-FB-PC2-
Fieldbus Power System HON Power Conditioner System
(DIN-rails included but not shown) (DIN-rails included but not shown)
Foundation Fieldbus Integration, Release 400 29

Fieldbus Usage Licenses

TC-FFLXxx, are required based on the total number of FIMs per Server actually in use. This applies equally to CIOM-A and
Series C FIMs. License model numbers are purchased in combinations that support the total number of FIMs required.
Licenses must be purchased starting with the first FIM used.

Fieldbus Usage License Models (applicable to all FIM types)

Fieldbus Usage Licenses

TC-FFLX01 Fieldbus Usage License, 1 FIM

TC-FFLX05 Fieldbus Usage License, 5 FIMs

TC-FFLX10 Fieldbus Usage License, 10 FIMs

TC-FFLX50 Fieldbus Usage License, 50 FIMs

 Foundation Fieldbus Integration, Release 400 30

Fieldbus Device Interoperability Testing

Device Testing. Experion uses the Control Builder tool to create a library of Fieldbus devices and
their function blocks. Experion also uses Control Builder’s off-line capabilities to implement
strategies involving fieldbus devices and to support live device commissioning. For the system and
the FIM to work properly, devices must be registered with the Fieldbus Foundation.

Honeywell maintains a Fieldbus Interoperability Test Laboratory for testing FOUNDATION Fieldbus
devices with Experion. Although most devices integrate easily, in some cases device
manufacturers’ interpretations of the Fieldbus specifications may vary. When device
interoperability problems arise, Honeywell and the device manufacturer work together to create a successful integration.

Device Descriptor files for devices tested are made available on our public website at the following link:

http://www.honeywell.com/ps
From the home page select Products, then Control & Safety Systems, then Experion PKS, then Fieldbus
Interoperability Support link. It is not necessary to test devices to insure they will work correctly with the system, but we
are happy to test any device at no charge if requested to do so and testing is highly encouraged.

Use the links and instructions on this webpage to schedule a device for testing. There is no charge for devices that meet the
above criteria.

For More Information

To learn more about how Honeywell’s Fieldbus
Solution can protect your system investment, visit our
website www.honeywell.com/ps or contact your
Honeywell account manager.

Automation & Control Solutions

Process Solutions
Honeywell
1860 W. Rose Garden Lane
Phoenix, AZ 86027
Tel: 800-822-7673

www.honeywell.com/ps
EP03-470-400
July 2010
Printed in USA
© 2010 Honeywell International Inc.