HART b0400ff V
HART b0400ff V
HART b0400ff V
User’s Guide
*B0400FF* *V*
B0400FF, Rev V
January 2023
https://www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as is"
basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
This document contains standardized industry terms that some customers might find
insensitive or offensive. These terms do not reflect the official policy or position of
Schneider Electric.
HART Communication Interface Modules User’s Guide
Table of Contents
Preface ...............................................................................................................6
Revision Information.........................................................................................6
Related Documents..........................................................................................6
Schneider Electric Products Mentioned in this Document ....................................7
Global Customer Support .................................................................................8
We Welcome Your Comments...........................................................................8
Chapter 1: Introduction ....................................................................................9
Overview .........................................................................................................9
HART Support in Foxboro DCS Control Software .............................................12
Upgrading 200 Series Analog FBMs to HART FBMs While Retaining Existing
Termination Assemblies..................................................................................13
Chapter 2: Quick-Start Example ..................................................................14
Chapter 3: Functional Characteristics .........................................................16
Functional and Environmental Constraints .......................................................16
Input/Output Cabling ......................................................................................17
Cable Type ..............................................................................................18
Cable Length ...........................................................................................18
Use of Baluns...........................................................................................18
Intrinsic Safety Considerations ........................................................................20
Chapter 4: Equipment Installation ................................................................21
HART FBMs and Termination Assembly Installation..........................................24
Redundant Adapter Installation..................................................................24
HART Device Connections........................................................................24
Connections to FBM215/218 .....................................................................36
Connections to FBM244/245 .....................................................................38
FBM244/245 Termination Assembly Connections .......................................39
HART Communication Interface Modules Entity Parameters .............................42
Chapter 5: Control Block Configuration Information..................................44
ECBs and DCI Blocks Used with HART FBMs ..................................................44
Block Interconnections ...................................................................................44
Configuration Procedures ...............................................................................45
Inter Replacement and Operational Conflict Between the FBM214e and
FBM214b Modules ...................................................................................49
Configuring IOBAD Options.......................................................................57
Point Addresses for HART and Analog I/O Signals ......................................58
Data Type Conversions.............................................................................60
Equipment Control Blocks (ECBs) ...................................................................61
Creating and Editing FBM ECB (ECB200 or ECB202) .................................61
Configuring SYSOPT in FBM ECB (ECB200) for HART FBMs .....................62
Creating and Editing Device ECB (ECB201) ...............................................63
Configuring DCI Blocks...................................................................................64
Example for Reading Pressure Measurement .............................................65
DCI Block Processing .....................................................................................66
Key DCI Block Functions ................................................................................67
B0400FF, Rev V 3
HART Communication Interface Modules User’s Guide
4 B0400FF, Rev V
Important Safety Instructions HART Communication Interface Modules User’s Guide
This safety alert symbol that lets you know about potential personal
injury hazards. Obey all safety messages with this symbol to avoid
possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death
or serious injury.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation that, if not avoided, could result in
death or serious injury.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
CAUTION
CAUTION indicates a hazardous situation that, if not avoided, could result in
minor or moderate injury.
Failure to follow these instructions can result in injury or equipment damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions can result in equipment damage.
Please Note
Electrical equipment should only be installed, operated, serviced, and maintained by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training to
recognize and avoid the hazards involved.
B0400FF, Rev V 5
HART Communication Interface Modules User’s Guide Preface
Preface
This document describes the HART® Communication Interface Modules (FBM214/
214b/214e, FBM215, FBM216/216b, FBM218, FBM244, and FBM245).
It is intended for the use of process control engineers and operators, instrument and
maintenance engineers, and other qualified and authorized personnel involved in
setting up and configuring, and maintaining EcoStruxure™ Foxboro™ DCS equipment
to provide a HART communication interface.
Prior to using this book, be generally familiar with Foxboro™ DCS, and with Standard
and Compact 200 Series Subsystem User's Guide (B0400FA). Detailed information
relating to the various Foxboro DCS software and hardware elements is found in
these reference documents.
Revision Information
This revision of the document includes these changes:
Related Documents
These documents provide additional and related information.
• FBM214, HART® Communication Input Interface Modules (Legacy) PSS 21H-
2Z14 B4
• FBM214b, HART® Communication Input Module PSS 41H-2S214
• Compact FBM214b, HART® Communication Input Interface Module PSS 41H-
2C214
• Compact FBM214e, 16 Channel HART® Communication Input Interface Module
PSS 41H-2C214e
• FBM215 HART® Communication Output Module PSS 41H-2S215
• Compact FBM215 HART® Communication Output Interface Module PSS 41H-
2C215
• FBM216 HART® Communication Redundant Input Interface Modules PSS 21H-
2Z16 B4 (Legacy)
• FBM216b Redundant HART® Communication Input Module PSS 41H-2S216
• Compact FBM216b, HART® Communication Redundant Input Interface Module
PSS 41H-2C216
• FBM218 HART Communication Redundant Output Module (FBM218) PSS 41H-
2S218
• Compact FBM218 HART® Communication Redundant Output Interface Module
PSS 41H-2C218
• FBM244, 0 to 20 mA I/O Module with HART Support PSS 41H-2S244
• FBM245, 0 to 20 mA I/O Module with HART Support (Redundant) PSS 41H-
2S245
• Compact 200 Series I/O Subsystem Overview PSS 41H-2COV
• Standard and Compact 200 Series Subsystem User's Guide (B0400FA)
6 B0400FF, Rev V
Preface HART Communication Interface Modules User’s Guide
B0400FF, Rev V 7
HART Communication Interface Modules User’s Guide Preface
8 B0400FF, Rev V
Chapter 1: Introduction HART Communication Interface Modules User’s Guide
Chapter 1: Introduction
This chapter provides an overview of the HART™ Communication Interface Modules,
and the network configuration in which they are used.
Overview
The HART® Communication Input/Output Interface Modules (FBM214/214b/214e/
215/216/216b/218/244/245) provide analog and digital communications to and from
HART compliant field devices. They also support standard 4-20mA signals from
analog devices. Each of these Foxboro™ Fieldbus Modules (FBMs) contains eight
channels that are group isolated for the FBM214/216 and individually isolated for the
FBM214b/215/216b/218/244/245. The FBM214e module contains 16 input channels,
compliant with NAMUR NE43 signal range.
These HART FBMs are available as either Compact or standard 200 Series FBMs:
• FBM214/214b – Each channel provides bidirectional digital communications with
a field device, and performs analog to digital conversion on the 4 to 20 mA input
control signal on that device.
• FBM214e – Each channel provides bidirectional digital communications with a
field device, and performs analog to digital conversion on the 4 to 20 mA input
control signal from that device. The module also complies with NAMUR NE43
standards.
• FBM215 – Each channel provides bidirectional digital communications with a field
device, and performs digital to analog conversion to generate the 4 to 20 mA
output control signal to that device.
• FBM216/216b – These modules, used in pairs, provide a redundant version of
the FBM214/214b.
• FBM218 – This module, used in pairs, provides a redundant version of the
FBM215.
Compact 200 Series FBMs provide the same functionality as standard 200 Series
FBMs while utilizing a smaller footprint, as shown in the figure. While a standard 200
Series FBM baseplate supports up to eight standard 200 Series FBMs, a Compact
200 Series 16-slot horizontal baseplate supports up to sixteen Compact 200 Series
FBMs in a similar amount of space. Compact 200 Series FBMs have the same
software as their standard 200 Series FBM counterparts and Foxboro DCS Control
Core Services do not distinguish between them. The Compact 200 Series I/O
subsystem is described in Standard and Compact 200 Series Subsystem User's
Guide (B0400FA) and Compact 200 Series I/O Subsystem Overview (PSS 31H-
2COV).
B0400FF, Rev V 9
HART Communication Interface Modules User’s Guide Chapter 1: Introduction
These HART FBMs are available only as standard 200 Series FBMs:
• FBM244 – Each input channel accepts an analog sensor input such as a 4 to 20
mA transmitter or a self-powered 20 mA source. Each output channel drives an
external load and produces a 0 to 20 mA output. It supports any mix of standard 4
to 20 mA devices and HART devices.
• FBM245 – These modules, used in pairs, provide a redundant version of the
FBM244.
HART FBMs communicate with the fieldbus I/O devices on a master/slave basis.
HART is a communications standard which supports digital communication between a
master (one of the HART FBMs) and a broad range of slave devices which include
transmitters and actuators. Each HART FBM can service up to eight slave devices in
a point-to-point network configuration; multidrop network configurations are not
supported. During normal operation, each communication is initiated by the HART
FBM, which serves as the primary master. The slave devices can only acknowledge
received messages, or send messages to the master when requested to do so.
The HART communication protocol is based on the Bell 202 telephone communication
standard and operates according to the frequency shift keying (FSK) principle. This is
in addition to the 4 to 20 mA normal analog input or analog output signal (depending
on the FBM model). The digital signal is made up of two frequencies, 1,200 Hz and
2,200 Hz, representing respectively the bits 1 and 0. The sine waves of these two
frequencies are superimposed on the direct current (analog) signal to provide
simultaneous analog and digital communications. The FSK signal allows
communication at 1200 baud. Burst mode of communication is not used by the HART
FBMs.
The FBMs operate in a point-to-point configuration. In this mode, the traditional 4-20
mA signal is used to communicate one main process variable. The HART
communication digital signal provides access to secondary process variables,
configuration parameters, and other device data that can be used for operations,
commissioning, maintenance, and diagnostic purposes.
The figure shows the relationship between the various equipment elements in the
subsystem. The HART FBMs provide a communication interface between the
Foxboro control station and the HART I/O field devices. Termination assemblies (TAs)
provide for physical connection of the field devices to the FBMs.
10 B0400FF, Rev V
Chapter 1: Introduction HART Communication Interface Modules User’s Guide
NOTE:
• Each HART FBM can service up to eight slave devices in a point-to-point
network configuration.
• FBM214e HART FBM can service up to 16 slave devices in a point-to-point
network configuration.
Physically, the FBMs mount on a baseplate that is DIN rail mounted. For detailed
information on the functional aspects of the FCMs and other DIN rail mounted
equipment, For more information, refer Standard and Compact 200 Series Subsystem
User's Guide (B0400FA).
The redundant adapter, used with the redundant FBM pairs (FBM216/216b, FBM218
and FBM245), provides a “Y” connection between the FBM pairs and the associated
TA. This allows either module in the pair to communicate with the field devices.
The field devices can be configured using any of these:
• Foxboro™ DCS Intelligent Field Device Configurator (IFDC) version 3.2.1 or later,
which is an optional component of Foxboro DCS
NOTE: IFDC currently does not support FBM214e. FBM214e connects and
configures with FCP280 only. It does not interface with FCM.
• A hand held configurator connected to the active (operational) link between the
TA and the devices.
Software residing in the HART FBMs, control station, and Foxboro DCS workstations
provide full support of the HART communication protocol. On the Foxboro DCS side,
the HART FBMs interface with the control station and other hardware and software
elements of Foxboro DCS to provide proven control, alarming, trending, and display
capabilities. The major functional components of this software are:
• Run-time Software – Supports the reading and writing of data to and from the
field device, treating these data as standard field I/O values in Foxboro DCS. This
includes Distributed Control Interface (DCI) control blocks, which are specifically
designed to interface I/O signals from field devices.
• Foxboro DCS Software – Integrates the HART FBMs and connected field devices
into the overall Foxboro DCS equipment configuration. This integration is
consistent with the integration of other Foxboro DCS FBM types, and the field
devices to which they connect.
• Diagnostics – Startup and maintenance diagnostics are provided for the HART
FBMs.
B0400FF, Rev V 11
HART Communication Interface Modules User’s Guide Chapter 1: Introduction
12 B0400FF, Rev V
Chapter 1: Introduction HART Communication Interface Modules User’s Guide
Schneider Electric has evaluated these configurations and found them to comply with
relevant safety and EMC standards.
Be advised that in the subsequent releases of the HART FBM TAs, surge suppression
was added on the input lines to comply with current regulatory controls. This
suppression is not provided by the analog FBM TAs. If using the existing analog FBM
TAs, the inputs of the HART FBMs will be more susceptible to surge events on those
lines. Your Risk Management plan should account for the possibility of such an event.
B0400FF, Rev V 13
HART Communication Interface Modules User’s Guide Chapter 2: Quick-Start Example
Start
Stop
NOTE: or
• FBM214e connects and configures with FCP280 only. Step 3 is not applicable
for FBM214e.
• This overview of procedures assumes that you are familiar with Foxboro DCS
concepts and HART concepts. Appropriate documents and sections herein
are referenced in each step.
14 B0400FF, Rev V
Chapter 2: Quick-Start Example HART Communication Interface Modules User’s Guide
B0400FF, Rev V 15
HART Communication Interface Modules User’s Guide Chapter 3: Functional Characteristics
16 B0400FF, Rev V
Chapter 3: Functional Characteristics HART Communication Interface Modules User’s Guide
NOTE:
• Each HART FBM can service up to eight slave devices in a point-to-point
network configuration.
• FBM214e HART FBM can service up to 16 slave devices in a point-to-point
network configuration.
Factors to be considered when designing a fieldbus network configuration for your
particular application are:
• Input/output cabling – Type, length, and the use of baluns
• Intrinsic safety.
These factors are addressed in these subsections.
NOTE: These subsections apply only to HART FBMs when connected to HART
field devices.
Input/Output Cabling
The basic cabling scheme is shown in figure and the actual connections to the TAs are
addressed in Chapter 4: Equipment Installation, page 21. These paragraphs provide
additional information.
B0400FF, Rev V 17
HART Communication Interface Modules User’s Guide Chapter 3: Functional Characteristics
NOTE:
• Each HART FBM can service up to eight slave devices in a point-to-point
network configuration.
• FBM214e HART FBM can service up to 16 slave devices in a point-to-point
network configuration.
Cable Type
Cable Type A, standard shielded twisted pair (STP) cabling, is used to wire the field
devices to termination assemblies (TAs). Unshielded cable can be used only when it
has been conclusively demonstrated that ambient noise does not affect
communication. For details, see the HART FSK physical layer specification document
HCF_SPEC-54.
Cable Length
The maximum permissible distance from a HART FBM to a compliant field device is a
function of the device type. For details, see the HART FSK physical layer specification
document HCF_SPEC-54.
Use of Baluns
A cable balun module, shown in the figure, is used to maintain digital communication
line balance for Intelligent Field Devices connected in FBM loops that are powered
from a common external power supply. This powering method effectively connects
one line of each loop to a single point. Without the use of a balun, the multiple
common connections at the external power source would cause cross-talk between
the loops.
18 B0400FF, Rev V
Chapter 3: Functional Characteristics HART Communication Interface Modules User’s Guide
The figure shows typical hookup. The Cable Balun module helps provide protection to
the HART signal and removes cross-talk between the channels and disruption to the
HART signal. They are recommended when the HART protocol on the HART FBM’s is
being used and the customer is providing external power to the loop. The use of an
external power supply common to two or more loops requires a Cable Balun Module
to maintain communication signal line balance.
NOTE:
Each balun module supports four channels. Two balun modules are required for
eight channels of the FBM, while four balun modules are required for 16 channels
of the FBM.
There is no signal isolation circuitry in the Cable Balun that would provide any
isolation when used on the 4-20mA signal. However, if high frequency noise is present
on the lines, the baluns can also tend to cancel out this external interference noise.
B0400FF, Rev V 19
HART Communication Interface Modules User’s Guide Chapter 3: Functional Characteristics
FBM
Termination
Assembly
+ Intrinsic +
Safety iP
T _ _
Barrier i+
(when used) i-
20 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Module Fieldbus
Baseplate
To Fieldbus To Next
Communications ® ® ®
Baseplate (If
Modules, Operational Status Operational Status
IR Active 01
Operational Status
IR Active 01
Applicable)
IR Active 01
FCP270, or Master
Tracker
02
03
04
Master
Tracker
02
03
04
02
03
04
FCP280 05
06
07
05
06
07
05
06
07
08 08 08
Termination
Cable
Status
Operational
01
IR Active
02
08 03
8
07
I
N
06
P
U
A
T
m
05
0
-2
04
04
0
03
,
1
0
2
02
M
B
01
F
05
i- i+ iP
i- i+
i- i+ iP
i-
i- i+ iP
i- i+ iP
i- i+ iP
C
06
i- i+ iP
C
C 07 08
i+ iP
iP
C 06
C 07
C 04 05
01
C
C 02 03
B 07
B
B 08
08 Fieldbus
B 06
4
B 02
01
B 03
B 05
B 04
A
FBM21
,
Module
A 08
A 07 unication
8 Comm ut
A 03
A 0
A 05
A 04
6
HART
P0914X
Inp
Q ® (FBM214b)
A 02
01
Termination
Assembly
NOTE: For diagrams and installation instructions for the Compact 200 Series
FBMs, see Standard and Compact 200 Series Subsystem User's Guide
(B0400FA).
As shown in figure “Example Standard HART FBM and Termination Assembly
Baseplate Installation”, the HART FBMs mount on their appropriate baseplate, and
the termination assembly (TA) connects to the baseplate by means of a Type 1
termination cable. The image shows the available FBM mounting slots in the
horizontal and vertical standard baseplates.
B0400FF, Rev V 21
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Horizontal-Mount Baseplate
Slots for Non-Redundant HART FBMs
1 2 3 4 5 6 7 8
1 2
OFF
Baseplate I. D.
No. 1 2
0 ON ON
1 OFF ON
2 ON OFF
3 OFF OFF
A B C D
Vertical-Mount Baseplate
1
A
1
OFF
2
Baseplate I. D.
No.
2
1 2
0 ON ON
1 OFF ON
2 ON OFF
3 OFF OFF
3
B
4 Slots for
Slots for Redundant Pairs Non-Redundant
5 HART FBMs
C
6
7
D
8
NOTE: For the available Compact FBM mounting slots in the Compact 200 Series
16-slot horizontal baseplate, for more information, refer Standard and Compact
200 Series Subsystem User's Guide (B0400FA).
Table 1 - Part Numbers for HART FBMs, Redundant Adapters and TAs
22 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Table 1 - Part Numbers for HART FBMs, Redundant Adapters and TAs (Continued)
For the available termination cables, refer Standard and Compact 200 Series
Subsystem User's Guide (B0400FA).
For general instructions on installing the FBMs and TAs, refer Standard and Compact
200 Series Subsystem User's Guide (B0400FA). The non-redundant FBM214/214b/
214e/215/244 can be located in any slot on the appropriate standard or Compact
baseplate, with the associated TAs connected to the associated cable connectors.
The redundant FBM216/216b/218/245 require a redundant adapter. They must be
located in adjacent positions on the baseplate:
• For the Compact 200 Series 16-slot horizontal baseplate, positions 1 and 2, 3
and 4, 5 and 6, 7 and 8, 9 and 10 (the second 1 and 2), 11 and 12 (the second 3
and 4), 13 and 14 (the second 5 and 6), or 15 and 16 (the second 7 and 8)
• For standard 200 Series FBM baseplates, positions 1 and 2, 3 and 4, 5 and 6, or
7 and 8.
B0400FF, Rev V 23
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
® ®
IR Active 01 IR Active 01
Master 02 Master 02
Tracker 03 Tracker 03
04 04
05 05
06 06
07 07
1 2 08 08
2
FBM216 01 02 03 04
1
Redundant Adapter
Redundant
2
Input (P)
1
08 07 06 05
Input (P)
Adapter
Input (-)
® 01 04
P0917XQ 05 08
NOTE: For the redundant adapters used on the Compact 200 Series 16-slot
horizontal baseplate, refer Standard and Compact 200 Series Subsystem User's
Guide (B0400FA).
24 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Connections to FBM214/214b/214e/216/216b/244
Make the cable connections to the FBM214/214b/216/216b/244 TA as shown in
Figure. For reference purposes, schematic representations of the input signal flows
for the FBM214/214b/216/216b is shown in Figure. Cable Balun Module connections
for 2-wire devices are shown in Figure. Cable Balun Module connections for 4-wire
devices are shown in Figure. Also, a simplified schematic of the FBM214/214b/216/
216b input circuitry is shown in Figure.
iP iP iP iP iP iP iP iP
i+ i+ i+ i+ i+ i+ i+ i+
i- i- i- i- i- i- i- i-
Signal
Connection C
Points:
C = iP B
B = i+
A = i- A
To
HART
Field
Devices
NOTE: Cable connections are shown for Channel 1. Other channels are
connected in a similar manner.
B0400FF, Rev V 25
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
NOTE: Cable connections are shown for channel 1. Other channels are
connected in a similar manner.
26 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
B0400FF, Rev V 27
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Figure 14 - FBM214e Input Signal Flow with Group Isolated External Power
Supply TA
28 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Figure 15 - FBM214e Input Signal Flow with Group Isolated Internal Power
Supply TA
B0400FF, Rev V 29
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
+ iP+ Cx* i+
i+ Bx* 280 i-
- Test
Transmitter iP
Ax*
i+
Test
Termination Assembly i-
Termination
(P0916BX, P0926EA, Cable Type 1
RH924JH/P0924JH)
Field Connections To
FBM216/216b
FBM216 or (redundant
FBM216b module)
Redundant Adapter
To
FBM216/216b
(primary
Internally (FBM) Powered Transmitter with Intrinsic Safety Barrier module)
Test
iP
+ iP+ Cx* i+
Intrinsic
Safety 280 i-
i+ Bx* Test
- Barrier iP
Transmitter Ax* i+
Test
i-
Termination Assembly
(P0916BX, P0926EA,
Termination
RH924JH/P0924JH)
Cable Type 1
Field Connections To
FBM216/216b
FBM216 or (redundant
FBM216b module)
Redundant Adapter
30 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
NOTES:
1. Field circuitry must have entity parameters compatible with those of FBM216 (TA Part No. P0916BX
and P0926EA) or FBM216b (TA Part No. P0924JH) as listed in the table “Entity Parameters for
HART™ Communication Interface Modules” for hazardous location applications.
2. Each input requires separate connections to the power supply.
* x indicates FBM channel number.
B0400FF, Rev V 31
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Figure 19 - Cable Balun Module, Internal and Externally Powered HART Input
Channels, Wiring Diagram
32 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Figure 20 - Cable Balun Module with Intrinsic Safety or Zener Barriers, Internal and Externally Powered HART
Input Channels, Wiring Diagram
B0400FF, Rev V 33
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Figure 21 - Cable Balun Module with Transformer Isolated Barrier, Internal and Externally Powered HART
Input Channels, Wiring Diagram
34 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Figure 22 - Cable Balun Module, Group Isolated Externally Powered HART Input Channels, Wiring Diagram
for FBM214e
Figure 23 - Cable Balun Module with Transformer Isolated Barrier Internal and Externally Powered 4-wire
Devices, Wiring Diagram
B0400FF, Rev V 35
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Transmit Driver
5.5 V +7.5 V Transmit Signal
4.7 mF 51 Ω
SIGPOS
7.5 K Ω
61.9 5.5 V A to D Converter
CHNEG SIGNEG
7.5 K Ω
2.5 V Ref. +5 V dc
Connections to FBM215/218
Make the cable connections to the FBM215/218 TA as shown in the figure. For
reference purposes, schematic representations of the output signal flows for the
FBM215/218 are shown in figure “FBM215 Output Signal Flow” and “FBM218 Output
Signal Flow”, respectively. Also, a simplified schematic of the FBM215/218 output
circuitry is shown in figure “FBM215/218 Field Device Output Interface, Simplified
Schematic”. Entity parameters for the FBM215/218 are listed in HART
Communication Interface Modules Entity Parameters, page 42.
36 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Signal o+ o+ o+ o+ o+ o+ o+ o+
Connection o- o- o- o- o- o- o- o-
Points:
B = o+ B
A = o-
A
To
HART
Field
Device
NOTE: Cable connections are shown for Channel 1. Other channels are
connected in a similar manner.
Actuator
+ Bx* Baseplate
o+
(to FBM215)
- o- Ax*
Termination Assembly
(RH926SP) Termination
Field Connections Cable Type 1
(25 pin to 37 pin)
NOTE: Field circuitry must have entity parameters compatible with those of
FBM215 (TA Part No. P0917XV, and P0926EK) as listed in the table “Entity
Parameters for HART Communication Interface Modules” for hazardous location
applications.
* x indicates FBM channel number.
B0400FF, Rev V 37
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
+ o+ Bx*
o+ FBM218
Ax* o- (primary
- o- module)
Termination Assembly
(RH926SP) Termination
Actuator Field Connections Cable Type 1
(25 pin to 37 pin)
o+ FBM218
(redundant
o-
module)
NOTE: Field circuitry must have entity parameters compatible with those of
FBM215 (TA Part No. P0917XV, and P0926EK) as listed in the table “Entity
Parameters for HART Communication Interface Modules” for hazardous location
applications.
* x indicates FBM channel number.
Isolated
Loop 24 v p-p 200 KHz
OUTPOS Squarewave
Power
Supply
33 V
OUTNEG Current
Driver
D/A TO ASIC
Opto-Isolators
Converter Logic
Transmit Driver
1.96 KΩ
123 Ω 1 mF Transmit Signal
5 KΩ
Receive Filter
Receive Signal
33 V 680 pF
Connections to FBM244/245
Make the cable connections to the FBM244/245 TAs as shown in figure. For reference
purposes, schematic representations of the output signal flows for the FBM244/245
are shown in figure “FBM244 Output Connections” and “FBM245 Output Connections
with Redundant Adapter Connections”, respectively.
38 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
NOTE: The FBM245 has four HART-compatible inputs and four HART-compatible
outputs. The test points provide a measurement check of the FBM derived loop
supply voltage for input channels 1-4. These test points do not reflect the loop
supply voltage when loops are externally powered.
TA P0924QZ has four output bypass jacks for use with the Output Bypass Station,
and is not suitable for use in any hazardous locations - ordinary locations only. For
more information on the Output Bypass Station, see Standard and Compact 200
Series Subsystem User's Guide (B0400FA).
Also, simplified schematics of the FBM244/245 output circuitry is shown in figure.
Entity parameters for the FBM244/245 are listed in HART Communication Interface
Modules Entity Parameters, page 42.
Isolated
Loop 24 v p-p 200 KHz
OUTPOS Squarewave
Power
Supply
33 V
OUTNEG Current
Driver
D/A TO ASIC
Opto-Isolators
Converter Logic
Transmit Driver
1.96 KΩ
123 Ω 1 mF Transmit Signal
5 KΩ
Receive Filter
Receive Signal
33 V 680 pF
Customer Customer
Labeling Labeling
Area Area
B0400FF, Rev V 39
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Cx*
Actuator
+ Bx* Baseplate
o+
(to FBM244)
- o- Ax*
Termination Assembly
(RH924QU/P0924QU) Termination
Field Connections Cable Type 1
(25 pin to 37 pin)
Cx*
Actuator
+ Bx* Baseplate
o+
(to FBM244)
- o- Ax*
Termination Assembly
(RH924QZ/P0924QZ) Termination
Field Connections Cable Type 1
(25 pin to 37 pin)
NOTES:
1. Field circuitry must have entity parameters compatible with those of FBM244 (TA Part No. P0924QU)
as listed in the table “Entity Parameters for HART™ Communication Interface Modules” for hazardous
location applications.
2. TA P0924QZ has 4 output bypass jacks for 0-20 mA supplied by Output Bypass Station.
3. Each input requires separate connections to Power Supply.
* x indicates FBM channel number.
40 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
Termination Assembly
(RH924QU/P0924QU) Termination
Field Connections Cable Type 1
(25 pin to 37 pin)
o+ FBM245
(redundant
o-
module)
Termination Assembly
(RH924QZ/P0924QZ) Termination
Field Connections Cable Type 1
(25 pin to 37 pin)
o+ FBM245
(redundant
o-
module)
NOTES:
1. Field circuitry must have entity parameters compatible with those of FBM245 (TA Part No. P0924QU)
as listed in the table “Entity Parameters for HART™ Communication Interface Modules” for hazardous
location applications.
2. TA P0924QZ has 4 output bypass jacks for 0-20 mA supplied by Output Bypass Station.
3. Redundant Adapter (P0924DU) must be used with the FBM245.
4. Each input requires separate connections to Power Supply.
* x indicates FBM channel number.
B0400FF, Rev V 41
HART Communication Interface Modules User’s Guide Chapter 4: Equipment Installation
Isolated
Loop 24 v p-p 200 KHz
OUTPOS Squarewave
Power
Supply
33 V
OUTNEG Current
Driver
D/A TO ASIC
Opto-Isolators
Converter Logic
Transmit Driver
1.96 K Ω
123 Ω 1 F Transmit Signal
5 KΩ
Receive Filter
Receive Signal
33 V 680 pF
42 B0400FF, Rev V
Chapter 4: Equipment Installation HART Communication Interface Modules User’s Guide
B0400FF, Rev V 43
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
Block Interconnections
In order for process control operations to be performed, you must create and
configure ECBs, DCI blocks, and other Foxboro DCS control blocks for control
scheme implementation. The figure shows the ECB hierarchy.
44 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
Foxboro
Control Station
ECB110
(FCM)
ECB200
(FBM214/214e/
215) or
ECB202*
(FBM216/218) ECB201 ECB201
HART Devices
* Each ECB202 block represents a pair of redundant FBMs: FBM216s, FBM216bs,
FBM218s or FBM245s.
Configuration Procedures
As indicated in figure “ECB Hierarchy”, an ECB200 must be configured for each
FBM214, FBM214b, FBM214e, FBM215, or FBM244 and an ECB202 must be
configured for each FBM216, FBM216b, FBM218 or FBM245 redundant pair. For
each device associated with the FBMs, a child ECB201 must be configured and
connected to the (parent) ECB200 or ECB202. In addition, a DCI block must be
configured for each HART FBM parameter that is connectable. (Table ECBs and DCI
Blocks Used with HART FBMs, page 44 lists the DCI block types used in HART data
transfer operations for the HART FBMs.) The DCI blocks can be configured anywhere
in the Continuous List hierarchy (List 1 or 2), in any compound in a control station.
This image shows the user-configured connections between the various elements of a
typical control scheme using an FBM214/214b with HART input devices. In this figure,
a RIN block is used to process a real input from HART devices.
B0400FF, Rev V 45
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
ECB200
NAME SLOT03
DEV_ID SLOT03
HART
Device
Channel#8 ECB201 RIN Block
NAME PT_108 NAME PT_108
PARENT :SLOT03 IOMID CP6SG5_ECB:PT_108
DVOPTS HART PNT_NO (See Note 2)
DVNAME CH8
(See Note 3)
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the device’s ECB201 for
each HART signal/value that is to be interfaced to Foxboro DCS.
2. Certain DCI block parameters (PNT_NO, in this case) must be configured to contain a point
address which indicates, to the HART device, the I/O operation to be performed. See “Point
Addresses for HART and Analog I/O Signals” for details.
3. DVNAME contains the channel number CH1-CH8 of the associated device.
46 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
ECB200
NAME SLOT03
DEV_ID SLOT03
HART
Device
Channel#16 ECB201 RIN Block
NAME PT_108 NAME PT_108
PARENT :SLOT03 IOMID CP6SG5_ECB:PT_108
DVOPTS NAMUR43 PNT_NO (See Note 2)
DVNAME CH16
(See Note 3)
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the device’s ECB201 for
each HART signal/value that is to be interfaced to Foxboro DCS.
2. Certain DCI block parameters (PNT_NO, in this case) must be configured to contain a point
address which indicates, to the HART device, the I/O operation to be performed. See “Point
Addresses for HART and Analog I/O Signals” for details.
3. DVNAME contains the channel number CH1-CH16 of the associated device.
4. NAMUR43 is the only applicable DVOPTS for FBM214e. It operates the FBM214e always in
HART enabled mode.
B0400FF, Rev V 47
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
ECB202
NAME SLOT0C
DEV_ID SLOT0C
HART
Device
Channel#8 ECB201 ROUT Block
NAME VP_108 NAME VP_108
PARENT :SLOT0C IOMID CP6SG5_ECB:VP_108
DVOPTS HART PNT_NO (See Note 2)
DVNAME CH8
(See Note 3)
NOTES:
1. A DCI block (such as ROUT) must be configured and connected to the device’s ECB201 for
each HART signal/value that is to be interfaced to Foxboro DCS.
2. Certain DCI block parameters (PNT_NO, in this case) must be configured to contain a point
address which indicates, to the HART device, the I/O operation to be performed. See “Point
Addresses for HART and Analog I/O Signals” for details.
3. DVNAME contains the channel number CH1-CH8 of the associated device.
48 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
ECB200
NAME SLOT04
DEV_ID SLOT04
Input
Device
Channel#8 ECB201 RIN Block
NAME FT_108 NAME FT_108
PARENT :SLOT04 IOMID CP6SG5_ECB:FT_108
DVOPTS 4-20 PNT_NO CURRENT
DVNAME CH8
(See Note 2)
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the device’s ECB201 for
each signal that is to be interfaced to Foxboro DCS.
2. DVNAME contains the channel number CH1-CH8 of the associated device.
NOTE:
• A DCI block (such as RIN) must be configured and connected to the device’s
ECB201 for each signal that is to be interfaced to Foxboro DCS.
• DVNAME contains the channel number CH1-CH8 of the associated device.
Configuration for other types of device I/O parameters and corresponding DCI blocks
is similar, with similar interconnections between the ECBs and DCI blocks. Inter
Replacement and Operational Conflict Between the FBM214e and FBM214b
Modules, page 49 lists key parameters, which either specify the linkages between
ECBs and DCI blocks or contain information relating to the transfer of I/O values.
The ECB200, ECB201, ECB202, and DCI block parameters are defined in Integrated
Control Block Descriptions (B0193AX).
NOTICE
POTENTIAL DATA LOSS
Do not insert the FBM214b module in the slot configured for FBM214e or the other
way round. When replacing the FBM214e module, keep the TA cable (Type 4)
connected. See Inter Replacement and Operational Conflict Between the FBM214e
and FBM214b Modules, page 49
Failure to follow these instructions can result in data loss.
B0400FF, Rev V 49
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
The FBM214b module uses the Type 1 TA cable and FBM214e uses the Type 4 TA
cable.
However, if you insert the FBM214b module without a TA cable in the slot configured
for FBM214e, the FBM214b goes online and enables communication with channels 1
to 8. If you replace the FBM214b with an FBM214e module, the FBM214e module
goes online too. However, it can only enable communication with channels 1 to 8.
Channels 9 to 16 are not serviceable, and display an unresolved connection state.
To resume operations for all 1 to 16 channels for the FBM214e module, you need to
undeploy the module, and then re-deploy the FBM configuration using Control
Software, or by rebooting the FCP.
See Control Software Control Database Deployment (B0750AJ) for more information
on the undeployment and deployment procedures.
ECB202
NAME SLOT0C
DEV_ID SLOT0C
HART
Device
Channel#8 ECB201 ROUT Block
NAME VP_108 NAME VP_108
PARENT :SLOT0C IOMID CP6SG5_ECB:VP_108
DVOPTS HART PNT_NO (See Note 2)
DVNAME CH8
(See Note 3)
NOTES:
1. A DCI block (such as ROUT) must be configured and connected to the device’s ECB201 for
each HART signal/value that is to be interfaced to Foxboro DCS.
2. Certain DCI block parameters (PNT_NO, in this case) must be configured to contain a point
address which indicates, to the HART device, the I/O operation to be performed. See “Point
Addresses for HART and Analog I/O Signals” for details.
3. DVNAME contains the channel number CH1-CH8 of the associated device.
50 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
ECB200
NAME SLOT04
DEV_ID SLOT04
Input
Device
Channel#8 ECB201 RIN Block
NAME FT_108 NAME FT_108
PARENT :SLOT04 IOMID CP6SG5_ECB:FT_108
DVOPTS 4-20 PNT_NO CURRENT
DVNAME CH8
(See Note 2)
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the device’s ECB201 for
each signal that is to be interfaced to Foxboro DCS.
2. DVNAME contains the channel number CH1-CH8 of the associated device.
This table lists key parameters, which either specify the linkages between ECBs and
DCI blocks or contain information relating to the transfer of I/O values.
B0400FF, Rev V 51
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
52 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
B0400FF, Rev V 53
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
54 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
B0400FF, Rev V 55
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
NOTE:
• The FBM214e module with DVOPTS NAMUR43 always operates in HART
enabled mode. In this mode, both HART and analog input field devices are
accessed. As the module operates in the HART enabled mode, the Device
Status Display parameter in the System Manager always displays the module
as a "HART Device", for both HART and analog input devices.
• For configurations in which a ZCP270 is connecting to the FBMs via an FCM,
the first four characters of the FBM letterbug (SLOT) are created per user
preference, but they must match the first 4 characters of FCM name. For a
non-redundant FBM, the last two characters (03) reflect the physical position
(slot 3) of the FBM and its associated baseplate (0). For a redundant FBM
pair, the last two characters (0C) reflect the physical position (slot C) of the
module pair and its associated baseplate (0). For more information, see figure
and Standard and Compact 200 Series Subsystem User's Guide (B0400FA).
Horizontal-Mount Baseplate
Slots for Non-Redundant HART FBMs
1 2 3 4 5 6 7 8
1 2
OFF
Baseplate I. D.
No. 1 2
0 ON ON
1 OFF ON
2 ON OFF
3 OFF OFF
A B C D
Vertical-Mount Baseplate
1
A
No.
1
OFF
2
Baseplate I. D.
2
1 2
0 ON ON
1 OFF ON
2 ON OFF
3 OFF OFF
3
B
4 Slots for
Slots for Redundant Pairs Non-Redundant
5 HART FBMs
C
6
7
D
8
56 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
B0400FF, Rev V 57
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
• IOBAD 0.00
Using the special key of 0.00 shuts off alarms generated by any type of detected
device malfunction entirely. This must be used sparingly because it is hiding
potential problems. However, the operator can still tell a malfunction has been
detected by checking the top bit of device status 3 in the System Monitor. Identify
this device state by checking if the MSB is active in the System Manager, as no
system alarms are generated.
NOTE: When running IOM version 2.49D or later, configuring a DVOPTS of
IOBAD 0.00 helps prevent any detected device malfunctions and HART
blocks from transferring a “BAD” status to the 4-20 signal. System Manager,
the smon_log, and the “device status 3” continue to report detected device
malfunctions or update their status accordingly, or both.
NOTICE
POTENTIAL DATA LOSS
Verify the dynamic variables your HART devices or other analog I/O source support.
Only with this knowledge can you identify when a seemingly good value is invalid
because it is associated with an unused variable.
Failure to follow these instructions can result in data loss.
The values returned by HART devices or other analog I/O sources depend on the
dynamic variables they support. For example, in response to a “Read Dynamic
Variables and P.V. Current” command (PVCURR), some devices or other sources
return data only for the variables they support. Other devices or other sources return
data for all four possible dynamic variables supported by the HART protocol, with the
data for unused variables being zero.
The FBM knows that a variable is unused only if the device does not return a value for
it. For such (unused) variables, the data is marked out of service (OOS).
When the device or other source returns a value (such as 0) for unused variables, the
FBM treats this value as good (not OOS) because it has no way of knowing that the
variable is unused. In this case, you are responsible for knowing that data for unused
variables is invalid.
58 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
B0400FF, Rev V 59
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
60 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
NOTE: All other HART data types not specified in this table are converted by the
HART FBM to/from the appropriate Foxboro DCS data type.
NOTICE
POTENTIAL DATA LOSS
When modifying an ECB201configuration with changes that are related to DCI
connections (for example, when changing a device address), DO NOT wait for the
system to report any possible detected error(s) associated with that change. Rather,
monitor the ECB201 block detailed display while modifying the ECB201
configuration (see Chapter 6: Process Operator Displays, page 72. This helps
ensure that all possible errors are detected (and resolved) before starting process
control operations.
Failure to follow these instructions can result in data loss.
NOTE: Be aware that the fastest allowed ECB period for the HART FBMs is 100
milliseconds (PERIOD = 0). However, we recommend that you refer to Sizing
Guidelines and Excel Workbook the appropriate for your Control Processor to
determine the optimal BPC for this ECB in order to help prevent overloading.
B0400FF, Rev V 61
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
To create and edit an ECB using FoxCAE software, see Computer Aided Engineering
for I/A Series Control Station Databases, FoxCAE Version 4.0 (B0193MR).
For the ECB200 and ECB202 parameter definitions, see Integrated Control Block
Descriptions (B0193AX).
62 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
NOTE: Be aware that when making changes to the integration time for an FBM,
points can go Bad for a full integration period which could affect the operation of a
running process.
See Integrated Control Block Descriptions (B0193AX) for more information on
configuring the remainder of the ECB200’s parameters.
Be aware that for the ISCM214 and ISCM215, SYSOPT is used for power supply
monitoring, as described in the table “SYSOPT Bits in ECB200/202 for Power Supply
Monitoring” in the Intrinsically Safe I/O Subsystem User’s Guide (B0700DP).
B0400FF, Rev V 63
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
To create and edit an ECB using FoxCAE software, see FoxCAE V4.0 Computer
Aided Engineering for Control Station Databases (B0193MR).
For the ECB201 parameter definitions, see Integrated Control Block Descriptions
(B0193AX).
NOTE:
• You can use the block name for the PARENT parameter whenever the child
ECB and the parent ECB reside in the same compound. For example, you
might enter ECB200BK15 for the PARENT parameter because the child
ECB201 and the parent ECB (ECB200 or ECB202) reside in the PRIMARY_
ECB compound (F41CP6_ECB).
• If the child ECB and the parent ECB are not in the same compound, you must
enter the full compound:block pathname for the PARENT parameter.
64 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
The DCI blocks are created in the same general manner as the ECBs. For more
information, see Integrated Control Configurator (B0193AV). For parameter
definitions, see Integrated Control Block Descriptions (B0193AX).
As part of the editing operations performed on the newly created DCI blocks, certain
parameters (PNT_NO, R11_PT and others) must contain a point address to specify
the particular HART universal command to be performed regarding the input or output
data handled by the DCI block. see Point Addresses for HART and Analog I/O
Signals, page 58 for detailed information.
In conjunction with creating and editing DCI blocks, you need to configure the various
blocks and compounds required for the desired control scheme. Refer to these
documents to perform these operations:
• Standard and Compact 200 Series Subsystem User's Guide (B0400FA)
• Integrated Control Software Concepts for CP270, FCP280, and FDC280 User’s
Guide (B0700AG)
• Integrated Control Block Descriptions (B0193AX).
To create and edit a DCI block in an existing compound using the Control Software’s
Block Configurator, see Block Configurator User's Guide (B0750AH).
To create and edit a DCI block using the I/A Series Configuration Component (IACC),
see I/A Series® Configuration Component (IACC) User’s Guide (B0700FE).
NOTE: IACC/FoxCAE does not provide support for FBM214e. We recommend
that you use ICC or Control Software Editor v7.2 or later to configure an
FBM214e.
To create and edit a DCI block using FoxCAE software, see Computer Aided
Engineering for I/A Series Control Station Databases, FoxCAE Version 4.0
(B0193MR).
NOTE: The engineering units configured for the block detail display must match
the units configured in the device.
To verify operation of the DCI blocks and the HART device data using the block detail
displays:
• Access the appropriate application:
◦ For the Foxboro Console Software Block Select application, see Control HMI
Application User's Guide (B0750AQ).
◦ For the FoxSelect compound/block overview utility, see Process Operations
and Displays (B0700BN).
• Access the block detail display for each DCI block created, and confirm its data.
B0400FF, Rev V 65
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
For parameter definitions for the RIN block, see Integrated Control Block Descriptions
(B0193AX).
If the RIN block PNT_NO parameter is set to CURRENT, the RIN block output will be
the Primary Variable (Pressure in this example), based only on the 0 to 20 mA dc
current signal coming into the HART FBM from the HART device, and this output will
be the raw counts of the 0 to 20 mA dc signal converted to the equivalent Engineering
Units in the exact same manner as an AIN block does the conversion with a 0-to-20-
mA-only FBM. If the PNT_NO parameter is set to the HART variable PV, the RIN
block reads the Primary variable from the transmitter (Pressure in this example) in a
digital response format which has the value already converted to engineering units by
the transmitter, and, therefore, the RIN block output is just this digitally-read value
without any additional conversions or manipulations applied to it.
66 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
Periodic/Change-Driven Execution
All DCI blocks are executed periodically according to their Period/Phase parameter
configuration. The ROUT block normally sets write requests to the HART FBM only
when the output value changes. If the secondary loop timer (SECTIM) is configured
non-zero, write requests are also set if the timer expires between output changes.
Simulation Mode
Simulation mode is supported in all DCI blocks. When SIMOPT is set, the DCI
connections are not used. In the STRIN block, the string value can be written into the
block by an object manager (OM) write access command. In the RIN, and IIN blocks,
the input is provided by a separate, configurable input parameter. In the ROUT block,
confirmation of the output value change is simulated automatically. The simulation
mode can be used in conjunction with the Auto/Manual mode. The two features can
co-exist in any DCI block.
Input Limiting
The input values of the RIN block are constrained by the engineering range (HSCI1/
LSCI1) configured in the block. If the input value is out-of-range, it is clamped to the
high/low range value, and the corresponding LHI/LLO status bit is set in the value
record.
Confirmed Outputs
The output of the ROUT block is confirmed by a readback of the actual value written to
the HART FBM. When an output is changed in one of these blocks by Foxboro DCS, it
B0400FF, Rev V 67
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
is stored in a request location that is part of the output value record in the block. (In
Foxboro DCS terminology, this type of output is referred to as a “shadow” output and
is reflected in the shadow status bit (Bit 12) in the value record.) The actual output
value of the block is not updated until confirmation of the requested change at the field
device is received during the next processing cycle of the DCI block.
The request value is written to any output-capable HART FBM (such as FBM215/218/
244/245), which writes the value to the HART field device. If the write operation is
successful, the output-capable HART FBM stores the value as the readback value in
its DCI connection record.
On the next ROUT block cycle, the block output value is updated in the Foxboro
control station with the readback value from the HART FBM, thus completing
confirmation of the change.
Output Clamping
The output value of the ROUT block is constrained by the limit values (HOLIM/LOLIM)
configured in the block. The limit values are constrained by the engineering range
(HSCO1/LSCO1) configured in the block. If the output value exceeds its limiting
constraints, it is clamped to the high/low value, and the corresponding LHI and LLO
status bit is set in the value record. This feature can be enabled in Auto mode only or
in both Auto and Manual modes.
Output Initialization
The output value of a ROUT block initializes to the readback value in each of these
cases:
• When the compound containing the block is turned on
• When the block is installed and runs its first cycle
• When control station-to-FBM communication recovers from a detected failure
condition
• When the Initialization Input (INI_PT), if used, is set
The readback value contains the most recent value written to the HART FBM by the
control station.
Whenever a ROUT block is initialized (such as when its compound is turned on), it
sends an initial value to the FBM and this value is sent by the FBM to the slave device.
The initial value used for the ROUT block is the value that you have configured into
the block’s fail-safe value parameter FSOUT.
The ROUT block output initialization is done whether fail-safe is configured for the
block; the default value for the fail-safe value for the ROUT block is zero. If you care
about what value is written to the ROUT block when it is initialized, you must configure
the fail-safe value for the block, even if the fail-safe option is not used.
Cascade Initialization
Upstream logic in a cascade is initialized by a ROUT block in each of these cases:
• When the DCI block initializes
• When the DCI block mode changes from Manual to Auto mode
• When control station-to-FBM communication recovers from a detected failure
condition
• When the readback value transitions from Bad, Out-of-Service or both to Good
status
68 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
Fail-Safe Actions
Fail-safe actions are performed in accordance with specific parameters set in ECB200
or ECB202, and in the ROUT DCI block. In ECB200 or ECB202, these parameters
control fail-safe actions:
• FSENAB – Fail-Safe Enable, when true, activates the FSDLAY timer to detect a
communication failure from the control station, and start fail-safe action in the
FBM. The FSENAB setting is downloaded to the HART FBMs when the FBM is
rebooted. It is used by the HART FBMs to enable/disable the logic to assert fail-
safe action when a loss of control station communication is detected, or when a
control station fail-safe request is received.
• FSDLAY – Fail-Safe Delay is a communication fail timer. When enabled by
FSENAB, it specifies the length of time (in units of 0.01 seconds) that the FBM
can be without communication from the control station before taking fail-safe
action. If the Fail-Safe On Commfail bit is set in the FSOPTN parameter of the
output control block (ROUT), the FBM sets the Initialize Fail-safe bit in the status
of the OUT parameter of the associated AO function block. When this value is
next received by the connected device, the device asserts fail-safe and drives its
output to the fail-safe value. For example, the default value of 1000 in FSDLAY
causes the FBM to wait 10 seconds between read/write messages before going
to the Fail-safe state (provided FSENAB is configured true).
In the ROUT DCI block, these parameters control fail-safe actions:
• FSOPTN – Fail-safe Option is a configurable option that specifies the fail-safe
conditions and action to be taken in the FBM for an output point in a ROUT block:
◦ Assert fail-safe if an input/measurement error is detected.
◦ Set/clear fail-safe when a SETFS input is set/cleared.
◦ Assert fail-safe if a control station-to-FBM communication failure was detected
by the FBM.
Combinations of these conditions for fail-safe can be specified.
• SETFS – Set Fail-safe Request is a settable Boolean parameter that requests
fail-safe action to be set/reset by the FBM and field device for the specific output
value of the ROUT block.
• FSOUT – Fail-safe Real Output (ROUT block) specifies the real fail-safe value
that is to be used by the external device when any condition specified in FSOPTN
exists.
A Failsafe Enable (FSENAB) option can be configured by the user in an ECB200 or
ECB202. This option is downloaded to the HART FBM when it is rebooted or when
configuration of the ECB200 or ECB202 is changed. FSENAB is used by the HART
FBM to enable/disable logic to assert fail-safe action on the HART channels
automatically when a loss of control station communication is detected. It is also used
by the HART FBMs to override all explicit fail-safe request actions from the control
station for each DCI output connection.
If the FSENAB option is set, the Fail-safe Delay (FSDLAY) value configured in the
ECB200 or ECB202 is used to set the fail-safe timer in the HART FBM. The fail-safe
timer counts down and is reset to the FSDLAY value whenever a DCI message is
received. If the fail-safe timer expires, the HART FBM stops communication on the
channels, and sets the Fail-safe Active (FSA) status in the associated DCI output
connection records.
When communication with the control station is restored, the fail-safe timer is
automatically reset to full value by the first DCI message received, and the HART
FBM clears the FSA status in the associated DCI output connection records.
Fail-safe options (FSOPTN) can also be configured in each DCI output block. These
options are downloaded into the HART FBM when the DCI output connection is
B0400FF, Rev V 69
HART Communication Interface Modules User’s Guide Chapter 5: Control Block Configuration Information
established. If any of the fail-safe options are set, the HART FBM writes the
associated fail-safe value into the DCI connection record.
Fail-safe action can also be triggered by either of two events in a DCI output block:
• The Fail-safe Request parameter (SETFS) is toggled or, if the detected error
option (EROPT) is configured.
• The status of the primary input in the block goes bad (or becomes good).
When either of these events occurs, a Write_Data message is sent to HART FBMs
with the Fail-safe Request bit set (or cleared) in the message. If FSENAB is set, and if
the Fail-safe Upon CP Request option is set in the DCI output connection, the HART
FBM sets (or clears) the FSA status in the DCI connection record. If the Fail-safe
Request is set, the HART FBM writes the fail-safe value stored in the DCI connection
record to the HART field device.
For more information, see Integrated Control Block Descriptions (B0193AX).
70 B0400FF, Rev V
Chapter 5: Control Block Configuration Information HART Communication Interface Modules User’s Guide
RIN Block
IOM_ID PIDA Block ROUT Block
(1) PNT_NO IOM_ID
MEAS MEAS PNT_NO (1)
MEALM RSP
RIN Block (2) BCALCO
OUT MEAS OUT
MEAS BCALCI BCALCO
SUP_IN
SUPBCP MEALM
Notes: Block (2)
(1) PNT_NO = Point address of HART de vice
MEAS
(2) MEALM blocks are used to perform BAD alarming.
B0400FF, Rev V 71
HART Communication Interface Modules User’s Guide Chapter 6: Process Operator Displays
72 B0400FF, Rev V
Chapter 6: Process Operator Displays HART Communication Interface Modules User’s Guide
B0400FF, Rev V 73
HART Communication Interface Modules User’s Guide Chapter 6: Process Operator Displays
74 B0400FF, Rev V
Chapter 6: Process Operator Displays HART Communication Interface Modules User’s Guide
B0400FF, Rev V 75
HART Communication Interface Modules User’s Guide Chapter 6: Process Operator Displays
When the status bit changes state from 1 to 0, as observed by the FBM, the additional
status is read once more. After this final reading, the FBM discontinues the additional
status read until the status bit transitions to 1 again.
The 25-byte “additional status” value is accessible with standard DCI input blocks. All
twenty five bytes can be read as a string of hex digits using a STRIN block and
specifying “STATUS” for the PNT_NO parameter. The bytes are presented by this
block least significant to most significant order; for example, 01 02 03 ... 24 25.
Additionally, the individual status bits can be read in groups of 32 bits using the PAKIN
block with PKIOPT set to 3, displayed in most significant to least significant order, as
shown in table
System Alarming
Whenever DDIAG1 Byte 0, Bit 7 (“Device Malfunction”) is 1, the FBM sets the System
Alarm bit for the device. On the transition from 0 to 1 of the System Alarm bit for a
device, a system message is sent to the SMON log and the System key on Foxboro™
DCS FoxView software flashes red. In addition, all I/O blocks connected to a device
with this bit set indicates BAD I/O (Red) and the data will not be used for control.
While the System Alarm bit for a device is set, the device icon in SMDH must be
yellow as a system alarm indicator.
76 B0400FF, Rev V
Chapter 6: Process Operator Displays HART Communication Interface Modules User’s Guide
B0400FF, Rev V 77
HART Communication Interface Modules User’s Guide Chapter 7: Security for FBM214e
Vulnerabilities
The possibility of these vulnerabilities exists for FBM214e. However, each can be
mitigated as described in the table.
Vulnerability Mitigation
If there is a bad baseplate connection due to Inspect all pins and other connectors on an FBM214e before
missing or bent pins on the connector or if it is mounting FBM214e onto the baseplate. Help verify that the
improperly seated in its baseplate slot, the FBM214e is properly seated and verified in its baseplate slot.
vulnerabilities are, FBM214e;
FBMs execute a check to determine if there is a second FBM at
• Might not come online the same address. This causes the FBM214e to shut itself
• Could infer the wrong baseplate location. down and forget what it has already read. The operator sees
This could cause control issues (integrity two FBMs refusing to come online.
and availability) to be detected after a power
In addition, these preventative controls exist to mitigate this
cycle or other event which causes the
vulnerability:
FBM214e to read its baseplate location.
• Input validation at receiving function for message size and
• Could exhibit undefined behavior during
operation. An intermittent electrical content.
connection could cause errors detected in • HDLC transport 2-byte CRC to help verify data integrity.
communication.
• Dual redundant HDLC bus to increase availability.
The HART Device Configurator (Second Master) Under these circumstances, FBM214e ignores all requests
could attempt to query or configure FBM214e, from a HART Device Configurator (Second Master). This
which could affect data integrity or availability if mitigation is preventive control, implemented in the
FBM214e does not ignore these requests. In all communication software.
cases, any interaction between FBM214e and
HART Device Configurator (Second Master) is
unauthorized.
A HART Device Configurator (Second Master) FBM214e allows the hand-held configurator connected to the
could be used to help prevent or disrupt active (operational) link between the TA and the devices for the
communication between FBM214e and a slave HART device configuration.
HART device by holding the transmit line longer
than is legal. It might be possible to use more See Chapter 1: Introduction, page 9 and PSS_41h-2c214e for
than one configurator simultaneously to permitted use of hand-held configurator.
accomplish this same goal.
Follow the instructions for configuration and usage of the HART
Device Configurator as described in the documentation
accompanying the Configurator.
A HART Device Configurator (Second Master) Follow the instructions for configuration and usage of the HART
could be used to disrupt communication Device Configurator as described in the documentation
between FBM214e and a slave HART device by accompanying the Configurator.
78 B0400FF, Rev V
Chapter 7: Security for FBM214e HART Communication Interface Modules User’s Guide
Vulnerability Mitigation
changing the configuration settings of the
device.
FBM214e is designed to communicate to one See Chapter 4: Equipment Installation, page 21 for instructions
HART device per channel, point to point. The on wiring the FBM214e’s baseplate.
HART specification allows multi-drop
configurations. However, this is not supported by
FBM214e. FBM214e might exhibit digital data
integrity issues detected if more than one HART
device is connected to a single channel.
FBM214e might exhibit data integrity or FBM214e is designed to ignore any extended headers for
availability issues detected if it receives a protocol versions above v5.0. This mitigation is a preventive
message in an unsupported format (that is, control, implemented in the communications software.
HART extended headers for protocol versions
above v5.0).
FBM214e is designed to communicate with one See Chapter 4: Equipment Installation, page 21 for instructions
HDLC Master (FCP280). If it receives messages on wiring the FBM214e’s baseplate.
from more than one HDLC Master it might
exhibit data integrity or availability issues
detected. Multiple simultaneous masters can
send conflicting commands or different
configurations because the FBM214e replies to
any device that sends it a message on the HDLC
channel.
The HDLC Master (FCP280) sends HDLC These preventive controls have been implemented in the
messages to FBM214e which contain product software to mitigate this vulnerability:
commands and configuration data. A malformed, • Input validation at receiving function for message size and
out-of-sequence or corrupt message could content.
cause FBM214e data integrity and availability
issues detected. • HDLC transport 2-byte CRC to help verify data integrity
These product features also work in conjunction to mitigate
this vulnerability as compensating controls.
FBM214e might exhibit data integrity and The A/D input function performs input and range validation in
availability issues detected if it receives values software. This mitigation is a preventive control.
from the A/D Converter that are out of range.
The specific effects are unknown, but an out-of-
range value might be misinterpreted by the
software, cause data corruption or cause the
software to branch to an untested routine.
B0400FF, Rev V 79
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Chapter 8: Maintenance
This chapter provides maintenance information for the HART FBMs.
NOTE: In general, maintenance includes periodic inspection and cleaning,
checking the status of LED indicators, and checking for loose cable connections.
DANGER
HAZARD OF ELECTRIC SHOCK, EXPLOSION, OR ARC FLASH
To help prevent an explosion, install and remove cables, wiring, modules and other
replaceable components only when the area is known to be non-hazardous.
Failure to follow these instructions will result in death or serious injury.
Overview
The general Foxboro DCS system management philosophy applies to the HART
FBMs incorporated into Foxboro DCS. Through the System Management Displays,
you can receive status information on the HART FBMs, as well as send change
requests to the FBMs.
System management for the HART FBMs is supported on these system and display
management packages:
• System Manager - discussed in System Manager (B0750AP)
• SMDH - discussed in System Management Displays (B0193JC)
• FoxView software - discussed in Process Operations and Displays (B0700BN)
• Foxboro™ DCS Control HMI - discussed in Control HMI Application User's Guide
(B0750AQ).
Operating Status
The operating status of the HART FBMs is reported by Foxboro DCS using on-screen
and printed messages. Refer to these documents for information on the reporting of
equipment operating status and detected errors:
• System Manager User’s Guide (B0750AP)
• System Management Displays (B0193JC)
• Control Core Services V9.x System Messages Reference Guide (B0700AF)
• Process Operations and Displays (B0700BN).
80 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
The System Manager allows you to access equipment information and status for the
Foxboro DCS, including the HART FBMs, HART slave devices, and their associated
Control Processor. This display reflects the system’s current operating status and
provide a valuable maintenance aid by allowing you to observe the current operating
status of the various system elements and intervene in system operations. For
information on navigating through the System Manager screens, see System
Manager User’s Guide (B0750AP).
For information on viewing the HART FBM and device runtime information in the
Control HMI, see Control HMI Application User's Guide (B0750AQ).
The figure shows an example System Manager display page for a HART device which
contains operational status, hardware and software information.
In Foxboro DCS, the System Management Display Handler (SMDH) obtains current
and historical information about the system, and displays this information in System
Management displays. With regard to HART FBMs and the associated HART slave
devices, the SMDH provides these displays:
• A Fieldbus level display (PIO Network), which shows the control station, FCM(s),
and any other Fieldbus devices
• A module Fieldbus level display (PIO Sub-Network), which shows the selected
FCM and associated FBMs
• A device level display (I/O Display), which shows the associated HART devices
for the selected FBM
• Detailed equipment information (EQUIP INFO) and equipment change (EQUIP
CHG) displays for each HART FBM and the associated HART devices.
B0400FF, Rev V 81
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
The term “Fieldbus” used here refers to the Foxboro DCS 10 Mbps Ethernet trunk
Fieldbus or the 2 Mbps module Fieldbus.
For detailed information on the first three items above (Fieldbus level display, module
Fieldbus level display, and I/O device display), see System Management Displays
(B0193JC).
Field Description
NAME User-supplied ECB name.
RUN MODE Online or Offline (default) appears. Set the RUN MODE using the GO
ONLINE and GO OFFLINE options in the Equipment Change Display. If the
FBM automatically goes offline:
• Verify hardware
• Verify related fields, such as FBM STATUS
• Download (restart) the FBM.
FAIL ACK STATE Acknowledged (default) or Not Acknowledged appears. If the DEVICE STATE
value changes from Not Failed to Failed, the FAIL ACK STATE value changes
to Not Acknowledged to indicate this transition, and remains until you
acknowledge the detected FBM failure.
DB DOWNLOAD STATE Not applicable to HART FBMs.
LAST CABLE ACCESS Both Cables OK, Cable A Not OK, Cable B Not OK, or Both Cables Not OK
appears. This field indicates whether transmissions were successfully sent
the last time either Bus A or B was used. A Not OK status indicates a detected
PIO bus send failure. To resolve this:
• Verify the PIO bus.
• Change to the other cable if the bus is bad.
COMPOUND NAME Compound name containing the FBM ECB200.
BLOCK NAME Block name for the FBM ECB200.
HARDWARE TYPE Configured value for HWTYPE parameter in ECB200.
SOFTWARE TYPE Configured value for SWTYPE parameter in ECB200.
HARDWARE PART Hardware part number related to this FBM.
HARDWARE REV Hardware release level of this FBM hardware type.
SOFTWARE REV Release level of this FBM software.
EEPROM REV Firmware release for this FBM.
SERIAL NUMBER Serial number assigned to this FBM hardware module.
MANUF DATE Date of manufacture for this FBM. For MANUF DATE“180133”, the factory
number is 18, the year is 01, and the week is 33.
LOGICAL ADDR Logical Address is the number of the FBM, 1 through 120. FBMs are typically
numbered as they appear in the display (left to right).
TYPE Predefined FBM type from ECB200.
82 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Field Description
DEVICE STATE Failed or Not Failed (default) appears. This field changes to Failed if a
detected fatal hardware fault (including a possible communication cable
break) causes the FBM to fail.
ALARMING STATE Alarming State indicates whether alarming is Enabled or Inhibited for the
device. When alarming is inhibited, the System Monitor continues to indicate
overall system and network health (a green SYS BAR) while equipment is
Failed or Offline.
WARNING CONDITION Yes appears if the device has a non-fatal error condition detected; otherwise,
No is displayed.
DEVICE ATT Yes is displayed if the FBM has devices attached; otherwise, No appears.
FAIL DEV ATT Yes is displayed if one or more HART devices connected to the FBM have
failed; otherwise, No is displayed.
FAIL DEV ACK Acknowledged (default) or Not Acknowledged appears. If any of the devices
attached to the FBM fail and become unacknowledged, Not Acknowledged
appears.
POWER 1 OK or Failed indicates the state of primary power to FBM.
POWER 2 OK or Failed indicates the state of backup power to FBM.
DIAG STATUS 1 Diagnostic Status 1 is a hexadecimal value related to the FBM status.
Typically this value is 4, indicating a non-fail-safe condition – typical status for
an FBM with a green status LED on.
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic
status field, call Global Product Support (GPS).
DIAG STATUS 2 Diagnostic Status 2 is a hexadecimal value indicating the FBM startup
condition. If the value is 0, there is no history of the last start condition due to
lack of communication. Hexadecimal values and the related conditions are as:
Value Condition
• 1 - Cold start (power up)
• 2 - Power fail recovery
• 4 - Watchdog timer failure detected
• 8 - Warm reset (equipment change download)
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic
status field, call the Global Product Support.
DIAG STATUS 3 Diagnostic Status 3 is a hexadecimal value relating to the previous detected
software or hardware error for the selected FBM.
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic
status field, call the Global Product Support.
DIAG STATUS 4 Diagnostic Status 4 is a hexadecimal value relating to the current detected
software or hardware error for the selected FBM. Normally, this value is 0 (no
error detected). Other values are detected fatal errors; the FBM is not
operational. Typical values and their meaning are as:
Value Condition
• 0 - No error detected
• 15 - Hardware type mismatch (FBM installed in the wrong slot)
• 16 - Software type mismatch (ECB configuration error detected)
B0400FF, Rev V 83
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Field Description
84 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Field Description
PORT2 FAIL STATE Not applicable to HART FBMs.
FBM STATUS These can be displayed to define the FBM status:
• HART FBM — FBM On-Line
• DCI Not Ready — FBM Off-Line
• DCI Ready — Unresolved Connection
• FBM Failed — System Alarm
BUS ID Not applicable to HART FBMs.
PORT1 STATUS Not applicable to HART FBMs.
PORT2 STATUS Not applicable to HART FBMs.
Field Description
NAME User-supplied ECB name.
MAIN SLOT NO Baseplate slot number where the main FBM is installed.
MAIN STATE Main State indicates the main FBM operational state:
• Main Downloading — Main Offline
• Main EE Updating — Master
• Main Failed — Tracker
TYPE Predefined FBM type from ECB202.
FAIL ACK STATE Acknowledged (default) or Not Acknowledged appears. If the DEVICE STATE
value changes from Not Failed to Failed, the FAIL ACK STATE value changes
to Not Acknowledged to indicate this transition, and remains until the detected
FBM failure is acknowledged by the user.
FAIL DEV ACK Yes (default) or No appears. If any of the devices attached to the FBM fail and
become unacknowledged, No appears.
ALARMING STATE Alarming State indicates whether alarming is Enabled or Inhibited for the
device. When alarming is inhibited, the System Monitor continues to indicate
overall system and network health (a green SYS BAR) while equipment is
Failed or Offline.
FAIL DEV ATT Yes appears if one or more HART devices connected to the FBM has failed;
otherwise, No appears.
B0400FF, Rev V 85
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Field Description
PRIM CMD STATE Primary Command Status is a value related to the status of communication
between the primary FBM and the HART FBM. Typically, this value is 0 or 1,
where 1 indicates that a successful retry took place and communication has
been restored to normal. Primary Command Status can have these values:
Value Condition
• 0 - Normal, no error detected
• 1 - Success with retry (this condition is very rare)
• 2 - FCM timed out FBM
• 3 - CP timed out FCM
• > 3 - Link level protocol error detected (this is very rare and transient)
IOM CMD STATUS IOM Command Status is a hexadecimal value associated with the return status
included in the header of every response from the HART FBM to the primary
FBM. Typically, the hexadecimal value is 0, indicating the command was
understood and action was taken.
Value Condition
• 1 - Command not understood.
• 2 - Command understood, but unable to take action.
• 4 - Invalid argument.
MAIN LOGICAL ADDR Logical Address is the number of the main FBM, 1 through 120. FBMs are
typically numbered as they appear in the display (left to right).
FBM DIAG STAT 1 Diagnostic Status 1 is a hexadecimal value related to the FBM status. Typically
this value is 4, indicating a non-fail-safe condition – typical status for an FBM
with a green status LED on.
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic status
field, call the Global Product Support.
FBM DIAG STAT 3 Diagnostic Status 3 is a hexadecimal value relating to the previous detected
software or hardware error for the selected FBM.
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic status
field, call the Global Product Support.
MAIN HDWR PART NO Hardware part number related to the main FBM.
MAIN HARDWARE REV Hardware release level of the main FBM.
MAIN EEPROM REV Firmware release for the main FBM.
MAIN SERIAL NUMBER Serial number assigned to the main FBM.
BKUP SLOT NO Baseplate slot number where the backup FBM is installed.
BACKUP STATE Backup State indicates the main FBM operational state:
Bkup Downloading — Bkup Offline
Bkup EE Updating — Master
Bkup Failed — Tracker
ACT CABLE ACCESS Both Cables OK, Cable A Not OK, Cable B Not OK, or Both Cables Not OK
appears. This field indicates whether transmissions were successfully sent the
last time either Bus A or B was used. A Not OK status indicates a detected PIO
bus send failure. To resolve this:
86 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Field Description
• Verify the PIO bus.
• Change to the other cable if the bus is bad.
WARNING CONDITION Yes appears if the device has a detected non-fatal error condition; otherwise,
No appears.
COMPOUND NAME Compound name containing the FBM ECB202.
BLOCK NAME Block name for the FBM ECB202.
HARDWARE TYPE Configured value for HWTYPE parameter in ECB202.
SOFTWARE TYPE Configured value for SWTYPE parameter in ECB202.
POWER 1 OK or Failed indicates the state of primary power to FBM.
POWER 2 OK or Failed indicates the state of backup power to FBM.
FBM DIAG STAT 2 Diagnostic Status 2 is a hexadecimal value indicating the FBM startup
condition. If the value is 0, there is no history of the last start condition due to
lack of communication. Hexadecimal values and the related conditions are as:
Value Condition
• 1 - Cold start (power up)
• 2 - Power fail recovery
• 4 - Watchdog timer failure detected
• 8 - Warm reset (equipment change download)
If the FBM is operating normally, this field can be ignored. For resolution of the
detected FBM hardware and software errors indicated by this diagnostic status
field, call the Global Product Support.
FBM DIAG STAT 4 Diagnostic Status 4 is a hexadecimal value relating to the current detected
software or hardware error for the selected FBM. Normally, this value is 0 (no
error detected). Other values are detected fatal errors; the FBM is not
operational. Typical values and their meaning are as:
Value Condition
• 0 - No error detected
• 15 - Hardware type mismatch (FBM installed in the wrong slot)
• 16 - Software type mismatch (ECB configuration error)
Corrective actions include:
• Installing the FBM in the correct slot
• Correcting ECB200 and ECB201 configuration errors
• Restarting the FBM using the DOWNLOAD function on the Equipment
Change display
• Reloading the FBM software using the EEPROM UPDATE function.
If the above actions do not correct the detected problem, call the Global Product
Support.
BKUP HDWR PART NO Hardware part number related to the backup FBM.
BKUP HARDWARE REV Hardware release level of the backup FBM.
BKUP EEPROM REV Firmware release for the backup FBM.
BKUP SERIAL NUMBER Serial number assigned to the backup FBM.
B0400FF, Rev V 87
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Field Description
MAIN MANUF DATE Date of manufacture for this FBM. For MAIN MANUF DATE “180151”, the
factory number is 18, the year is 01, and the week is 51.
MAIN SOFTWARE REV Release level of the main FBM software.
MAIN FBM TYPE Type of main FBM supported by ECB202.
MAIN VER NO Version number of the main FBM.
FILE ID Not applicable to HART FBMs.
FBM STATUS These might appear to define the FBM status:
• HART FBM — FBM Online
• DCI Not Ready — FBM Offline
• DCI Ready — Unresolved Connection
• FBM Failed — System Alarm
BKUP MANUF DATE Date of manufacture for this FBM. For BKUP MANUF DATE “180133”, the
factory number is 18, the year is 01, and the week is 33.
BKUP SOFTWARE REV Release level of the backup FBM software.
MAIN STATUS Main Status indicates the operational status of the main FBM:
• Not Operational — HART Comm Fault(a)
• Offline — Slot Conflict
• Master — Power 1 Fault
• Tracker — Power 2 Fault
• HDLC Fault — Fatal Error Flash
• Interlink Fault — Non Spec Fatal
• A/D Converter Fault — Non Spec NonFatal
• D/A Converter Fault
BKUP STATUS Backup Status indicates the operational status of the backup FBM:
• Not Operational — HART Comm Fault(a)
• Offline — Slot Conflict
• Master — Power 1 Fault
• Tracker — Power 2 Fault
• HDLC Fault — Fatal Error Flash
• Interlink Fault — Non Spec Fatal
• A/D Converter Fault — Non Spec NonFatal
• D/A Converter Fault
(a) The HART COMM Fault text field appears if the FBM is unable to communicate with a HART device on any of
the eight/sixteen channels, even if this is due to the lack of an electrical connection to the device.
NOTICE
POTENTIAL DATA LOSS
Do not attempt to use or power down the FBM while the EEPROM is being updated.
Failure to follow these instructions can result in data loss.
88 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Action Description
GO ON-LINE Connects the FBM to the Foxboro
control station, thus enabling
communication.
GO OFF-LINE Disconnects the FBM from the Foxboro
control station, thus disabling
communication.
EEPROM UPDATE Use this action to update the firmware in
an FBM with updated EEPROM Foxboro
software. You should use this action only
with an authorized and distributed
official Foxboro release.
To update firmware in an FBM with
updated EEPROM software, click
EEPROM UPDATE on the Equipment
Change display. The FBM becomes
inoperable. The update takes less than
one minute. When the update is
complete, the FBM is placed online. The
system displays a message in the
message line indicating whether the
update was a success or not.
ENABLE DEVICE ALARMING Allows device alarms to propagate
upward in the Foxboro system.
INHIBIT DEVICE ALARMING Inhibits device alarms from propagating
upward in Foxboro DCS.
B0400FF, Rev V 89
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
2. Click Go Online.
More information is available in System Manager User’s Guide (B0750AP).
-OR-
a. Access the System Management displays. For more information, see
System Management Displays (B0193JC).
b. On the PIO SUB NETWORK display, click the FBM and then click EQUIP
CHG.
c. On the EQUIPMENT CHANGE display, click GO ON-LINE.
The FBM is now online.
Action Description
GO ONLINE Connects the FBM to the Foxboro control station, thus
enabling communication.
GO OFFLINE Disconnects the FBM from the Foxboro control station, thus
disabling communication.
DOWNLOAD Restarts the FBM logic. This action does Not download the
FBM image.
EEPROM UPDATE Use this action to update the firmware in an FBM with
updated EEPROM Foxboro software. You must use this
action only with an authorized and distributed official
Foxboro software release.
After an EEPROM update of one or both FBM216/218
modules, the updated modules are placed in the state
(online or offline) that they were in prior to the EEPROM
update. Other 200 Series FBMs are placed online after an
EEPROM update.
To update firmware in a redundant pair of FBMs with
updated EEPROM software, click EEPROM UPDATE on
the Equipment Change display, and then click, BACKUP, or
both.
Updating FBMs Offline
When you update the main or backup module, that module
becomes inoperable, is updated, and returns to the offline
state. When you update both modules, the main module
becomes inoperable, is updated, and returns to the offline
state. Then, the backup module becomes inoperable, is
updated, and returns to the offline state. The update takes
less than one minute for each module. The system displays
a message in the message line indicating whether the
module update was a success or not.
Updating FBMs Online
When you update the main or backup module, that module
becomes inoperable, is updated, and becomes the Tracker.
90 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Action Description
When you update both modules, the main module becomes
inoperable, is updated and becomes the Tracker with the
backup module as Master. Then, the backup module
becomes inoperable, is updated, and becomes the Tracker
with the main module as Master. The update takes less than
one minute for each module. The system displays a
message in the message line indicating whether the module
update was a success or not.
ENABLE DEVICE Allows device alarms to propagate upward in Foxboro DCS.
ALARMING
INHIBIT DEVICE Inhibits device alarms from propagating upward in Foxboro
ALARMING DCS.
SWITCH ROLES Switches the Master/Tracker roles of the main and backup
modules.
B0400FF, Rev V 91
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Field Description
NAME User-supplied ECB name.
COMMUNICATIONS Indicates the state (Enabled or Disabled) of communication to or from the HART
device.
FAIL ACK STATE Acknowledged (default) or Not Acknowledged appears. If the DEVICE STATE
value changes from Not Failed to Failed, the FAIL ACK STATE value changes to
Not Acknowledged to indicate this transition, and remains until the detected device
failure is acknowledged by the user.
DB DOWNLOAD STATE Downloading appears when the FBM is downloading its application image;
otherwise, Not Downloading appears.
FAIL DEV ATT Yes appears if one or more HART devices connected to the FBM have failed;
otherwise, No appears.
COMPOUND NAME Compound name containing the FBM ECB201.
EE UPDATE STATE Updating appears if the EEPROM in the FBM is being updated; otherwise, Not
Updating appears.
HARDWARE TYPE Configured value for HWTYPE parameter in ECB201.
PRIMARY STATUS Primary Status is a value related to the status of communication between the
primary FBM and the HART FBM. Typically, this value is 0 or 1, where 1 indicates
that a successful retry took place and communication has been restored to normal.
For HART FBM, Primary Status can have these values:
Value Condition
• 0 - Normal, no error detected
• 1 - Success with retry (this condition is very rare)
• 2 - FCM timed out FBM
• 3 - CP timed out FCM
• > 3 - Link level protocol error detected (this is very rare and transient)
FBM CMD STATUS FBM Command Status is a hexadecimal value associated with the return status
included in the header of every response from the HART FBM to the primary FBM.
Typically, the hexadecimal value is 0, indicating the command was understood and
action was taken.
Value Condition
• 0 - Command understood.
• 1 - Command not understood.
• 2 - Command understood, but unable to take action.
• 4 - Invalid argument.
FBM IOM STATUS FBM IOM Status is a hexadecimal value related to current HART FBM status.
Typically this value is 4, indicating the instructions are valid.
Value Condition
• 1 - FBM status has changed – requests CP to poll for extended status.
• 2 - Diagnostic Register is nonzero. This indicates a detected fatal error. The
FBM does not start if this value is set.
• 4 - Non-fail-safe condition. This is the typical status for a HART FBM (green
status LED on). This value is reset only if the output mode of operation is fail-
safe.
• 40 - FBM is offline. In offline mode, the software control is ROM-based. In
online mode, the software is RAM-based.
92 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
Table 14 - HART Device Equipment Status and Information Display Fields (Continued)
Field Description
• 80 - Initialization is taking place – all channel and I/O data is initializing. Also,
indicates that the FBM has a delayed response message ready.
FILE REVISION Not applicable.
DEVICE TYPE Type of field device represented by the ECB201.
VERSION NUMBER Version information returned by the field device in response to the HART command
Read Unique Identifier. Version Number has four parts that are separated by
semicolons (for example, “005; 001; 013; 016”):
• Universal Command Major Revision Number implemented by this device
• Device Revision Level
• Software Revision Level of this device
• Hardware Revision Level of the electronics in this device.
FILE ID Not applicable.
MANUFACTURER Manufacturer Identification Code for the field device. see HART Common Tables
Specifications (HFC_SPEC-183).
TYPE Field device (DEV 214, 215, 216 or 218) represented by the ECB201.
DEVICE STATE Failed or Not Failed (default) appears. This field changes to Failed if a detected
device fatal hardware fault (including a possible communication cable break)
causes the device to fail.
ALARMING STATE Indicates whether alarming is enabled or inhibited for the device. When alarming is
inhibited, the System Monitor continues to indicate overall system and network
health (a green SYS BAR) while equipment is Failed or Offline.
WARNING CONDITION Yes appears if the device has a non-fatal error condition detected; otherwise, No
appears.
FAIL DEV ACK Acknowledged (default) or Not Acknowledged appears. If any of the devices
attached to the FBM fail and become unacknowledged, Not Acknowledged
appears.
BLOCK NAME Block name for the FBM ECB201.
MANUF DATE Field Device date of manufacture.
SOFTWARE TYPE Configured value for SWTYPE parameter in ECB201.
FBM DIAG STATUS 2 Not applicable.
FBM DIAG STATUS 3 Not applicable.
FBM DIAG STATUS 4 Not applicable.
BUS ID Bus ID is not applicable for HART FBMs.
PORT NUMBER Not applicable.
MODEL Not applicable.
DEVICE NAME Name of the field device associated with the ECB201.
DEVICE ADDRESS Reflects the DVADDR parameter in the associated ECB201. This parameter is not
used by HART FBMs.
DEVICE OPTIONS Device Options reflects the DVOPTS parameter in the associated ECB201, which
controls the use of HART protocol or standard 4-20 mA communication.
see the footnote in the table “Key Parameters” for a description of the allowed
values of DVOPTS in ECB201.
B0400FF, Rev V 93
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
Table 14 - HART Device Equipment Status and Information Display Fields (Continued)
Field Description
MASTER ADDRESS Not applicable.
IDENTIFICATION NO Not applicable.
DEVICE STATUS These appear to define the slave device status:
• HART Device — Device Disabled
• DCI NOT Ready — Unresolved Connection
• DCI Ready — System Alarm
• Device Failed
DEV DIAG STATUS These appear to define the slave device diagnostic status:
• Field Device Malfunction — Non-Primary Out-of Limits
• Configuration Changed — Primary Out-of Limits
• Cold Start — A/D Converter Fault
• More Status Available — D/A Converter Fault
• Primary Output Fixed — HART Comm Fault
• Primary Output Saturated
Action Description
ENABLE COMMUNICATIONS(a) Enables HART communication between the
device and FBM.
DISABLE COMMUNICATIONS Disables HART communication between the
(a)
device and FBM.
ENABLE DEVICE ALARMING Enables device alarms to propagate upward to
Foxboro DCS.
INHIBIT DEVICE ALARMING Inhibits device alarms from propagating upward
to Foxboro DCS.
(a) If the device parent FBM214/215 is offline, these key actions are not available. If
the device parent FBM216/218 main and backup modules are offline, these key
actions are not available.
94 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
2. Do one of these:
– In the Information pane, click the Connections tab.
– Click Enable Communications to enable communication to the HART slave
device.
-OR-
– Click the FBM to open its menu and click Enable Communications for
Multiple Devices.
-OR-
– On the Actions menu, open the Equipment Change submenu and click
Enable Communications for Multiple Devices.
For more information, see System Manager User’s guide (B0750AP).
-OR-
a. Access the System Management displays. For more information, see
System Management Displays (B0193JC).
b. On the PIO SUB NETWORK display, click the FBM and then click NEXT
LEVEL to open the I/O DISPLAY.
c. On the I/O DISPLAY, click the device and then click EQUIP CHG.
d. On the EQUIPMENT CHANGE display, click ENABLE COMMUNICATIONS.
e. Repeat Steps 3 and 4 for each additional slave device.
B0400FF, Rev V 95
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
1. Place the negative probe of a voltmeter at test point common 01 [Input (-)], and
test the loop power (voltage) for channel 01, modules 1 and 2 (at Input (P) 01).
Both readings must be 24 V dc ±5%. A reading significantly below the
specification indicates the module is not performing to the best of its ability
(detected defective loop power).
2. Repeat Step 1 for the remaining seven channels (02 through 08), using the
respective common points and loop power test points.
Test Points
2
FBM216 01 02 03 04
1
Redundant Adapter
2
Input (P)
1
08 07 06 05
Input (P)
Input (-)
® 01 04
P0917XQ 05 08
A Test Points
B Test Point Commons
96 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
A Test Points
B Test Point Commons
B0400FF, Rev V 97
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
A All LEDs are shown in the On state for showing color and position.
All LEDs are clear in the Off state.
98 B0400FF, Rev V
Chapter 8: Maintenance HART Communication Interface Modules User’s Guide
A Colored LEDs are in the On state for showing color and position.
LEDs indicate their channel is clear when in the Off state.
A Colored LEDs are in the On state for showing color and position.
LEDs indicate their channel is clear when in the Off state.
B0400FF, Rev V 99
HART Communication Interface Modules User’s Guide Chapter 8: Maintenance
A All LEDs are shown in the On state for showing color and position.
All LEDs are clear in the Off state.
A Colored LEDs are in the On state for showing color and position.
LEDs indicate their channel is clear when in the Off state.
On the front of all HART FBMs, two Operational Status LEDs (red and green) indicate
the operational status of the module. During normal online operation of the FBM with
communication enabled with the connected HART devices, the green LED is on, and
the red LED is off.
LEDs 01 through 08 indicate the operational status of the eight HART communication
channels. Each LED is on when the FBM is expecting and receiving valid messages
from the HART device on the channel. If the ECB201 is configured as “4-20” (4 to 20
mA analog channel), the LED is always off.
For FBM 214e, LEDs 01 through 16 indicate the operational status of the sixteen
HART communication channels. Each LED is on when the FBM is expecting and
receiving valid messages from the HART device on the channel.
On the redundant HART FBMs, the Master and Tracker LEDs indicate the master/
tracker status of the redundant module pair. The Master LED is on when the module is
controlling HART communication. The Tracker LED is on when the module is ready to
control HART communication.
The table lists the state of the FBM LEDs under various operating conditions. This
table assumes that you have properly configured the ECB201s for communication
with HART devices. It also assumes that you have placed the FBMs online and
enabled device communication using the appropriate displays (System Manager or
SMDH).
These system messages might contain an “[M|B]” device type for messages reported
from a Main or Backup Master FBM:
• M indicates the Main Master FBM sent the message.
• B indicates the Backup Master FBM sent the message.
However, a Tracker FBM can record messages that need to be posted, but holds
them until it takes the Master role. Such messages are marked with “[m|b]” instead:
• m indicates the Main Tracker FBM sent the message.
• b indicates the Backup Tracker FBM sent the message.
The internal time of each message (the actual time of the event) is recorded in the
smon_log. This time represents the number of milliseconds since the last reboot of the
particular FBM. The recording of the message in the smon_log can be delayed. For
example, when an FBM is not in the Master role, and it is holding messages until it
takes this role, such a delay occurs.
NOTICE
POTENTIAL DATA LOSS
This field rolls over every 1.8 hours. It is intended to provide relative timing to other
messages posted by the same FBM only.
Failure to follow these instructions can result in data loss.
Some of these messages can be turned off by setting gating bits in the SYSOPT
register. Those gating bits are shown in the table.
Glossary
F
Fieldbus Communication Module (FCM): The Fieldbus Communications Module is
an interface that allows the HART™ Communication Interface Modules (and other DIN
rail mounted FBMs) to communicate with the control station via the Foxboro DCS 10
Mbps Ethernet trunk Fieldbus. It converts the 10 Mbps Ethernet signals used by the
control station to 2 Mbps signals used by the FBM, and vice versa.
Fieldbus Module (FBM): FBMs provide the interface between process sensors/
actuators and the Fieldbus in a standard Foxboro DCS. FBM214/214b/214e/215/216/
216b/218/244/245 are examples of the many types of FBMs offered as part of
Foxboro DCS.
Fieldbus: Typically applies to two specific buses: the 10 Mbps Ethernet trunk fieldbus
and the 2 Mbps Fieldbus Module (Fieldbus Module (FBM)). These optionally
redundant buses, conforming to the EIA standards’ general requirements for RS-485,
carry data communication on a twinaxial cable between control processors and
fieldbus modules.
H
HART: Highway Addressable Remote Transducer, a bi-directional industrial field
communication protocol used to communicate between intelligent field instruments
and host systems over 4-20 mA instrumentation wiring.
I
IFDC: The Foxboro DCS Intelligent Field Device Configurator, a software package
providing remote bidirectional communications with the Foxboro and Eckardt
intelligent field devices.
L
letterbug: Alphanumeric string that the user defines to identify a station in an
I/A Series control system
P
Parameter: Named element in the data structure of a device function block,
Equipment Control Block (ECB), or other control block.
R
redundant adapter: Provides a “Y” connection between the supported redundant
FBM pairs (Fieldbus) and the associated Termination Assembly (TA). This allows
either module in the pair to communicate with the field devices.
T
TA: Terminal Assembly, wiring points, and, in some cases, protection circuitry to
connect Fieldbus Modules (Fieldbus Module (FBM)s) to their field devices.
Index E
ECBs
creating and editing......................................... 61, 63
A hierarchy..............................................................44
list of....................................................................44
Auto/Manual mode, DCI blocks .................................67 Entity parameters.....................................................42
Environmental constraints.........................................16
Equipment Change display
B FBM214/214b/214e/215........................................89
Baseplate ..................................................................9 FBM216/216b/218 ................................................90
Baseplate, FBM mounting slots .................................21 HART device ........................................................94
Block Detail Displays ................................................72 Equipment Information display
ECB 200 ..............................................................72 FBM214/214b/214e/215........................................82
ECB 201 ..............................................................74 FBM216/216b/218 ................................................85
ECB 202 ..............................................................73 HART device ........................................................91
Equipment installation Example.................................21
C
F
Cable balun module .................................................18
Cable Length ...........................................................18 Fail-safe actions
Cable Type A ...........................................................18 DCI blocks ...........................................................69
Cascade initialization FBM214/214b ............................................................9
ROUT block .........................................................68 FBM214e ..................................................................9
Configuration information FBM215 ....................................................................9
DCI blocks ...........................................................44 FBM216/216b ............................................................9
Configuration Procedures .........................................45 FBM216/216b redundant power supply test ...............95
Configuring DCI Blocks.............................................64 FBM218 ....................................................................9
Control schemes FBM244 ....................................................................9
DCI blocks ...........................................................70 FBM245 ....................................................................9
Creating and editing ECB
ECB 200 ..............................................................61
ECB 201 ..............................................................63 G
ECB 202 ..............................................................61 Group displays.........................................................72
D H
Data type conversions Hand held configurator ...............................................9
DCI blocks ...........................................................60 HART communications standard .................................9
DCI blocks HART point addresses
block interconnection example ...............................45 DCI blocks ...........................................................58
Cascade Initialization ............................................68
configuration information .......................................44
configuration procedures .......................................45 I
configuring ...........................................................64
control schemes ...................................................70 Input limiting
data type conversions ...........................................60 RIN......................................................................67
fail-safe actions ....................................................69 Input signal flow
functions ..............................................................67 FBM 216/216b......................................................25
HART point addresses ..........................................58 Install Foxboro DCS .................................................14
input limiting .........................................................67 Installation
output clamping ....................................................68 Equipment............................................................21
output initialization ................................................68 FBMs and TAs ......................................................24
periodic/change-driven execution...........................67 redundant adapters...............................................24
signal conditioning and linear scaling......................67 Intrinsic safety considerations ...................................20
simulation mode ...................................................67
status transformations...........................................70
Device connections to TAs ........................................24 K
Device data verification.............................................14
Diagnostics........................................................ 12, 98 Key parameters .......................................................49
L
LED status indicators
N
Network configurations ...............................................9
U
User-generated displays...........................................72
O
Output clamping
ROUT block .........................................................68
Output confirmation
ROUT block .........................................................67
Output initialization
ROUT block .........................................................68
Output signal flow
FBM 215 ..............................................................36
FBM 218 ..............................................................36
P
Part numbers
FBMs...................................................................21
redundant adapter ................................................21
TAs......................................................................21
periodic/change-driven execution
DCI blocks ...........................................................67
Process operator displays.........................................72
Product application...................................................16
Q
Quick start example..................................................14
R
Redundant Adapter
installation............................................................24
Related documents ....................................................6
Revision information...................................................6
Run-time software ....................................................12
S
Signal conditioning and linear scaling
RIN and ROUT block ............................................67
Simulation mode
DCI blocks ...........................................................67
SMDH .....................................................................80
Station displays........................................................72
Status transformations
DCI blocks ...........................................................70
System Manager displays .........................................80
T
TA....................................................................... 9, 21
TA cable connections
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: