HART Comm Module User's Guide (b0400ff - M)
HART Comm Module User's Guide (b0400ff - M)
HART Comm Module User's Guide (b0400ff - M)
HART Communication
Interface Modules
Users Guide
*B0400FF*
B0400FF
Rev M
May 6, 2015
*M*
Schneider Electric, Invensys, Foxboro, Foxboro Evo, FoxCAE, I/A Series, and InTouch are trademarks of
Schneider Electric SE, its subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 20022015 Invensys Systems, Inc.
All rights reserved.
Invensys is now part of Schneider Electric.
Contents
Preface.................................................................................................................................... xi
1. Introduction ...................................................................................................................... 1
Overview ................................................................................................................................... 1
HART Support in Foxboro Evo Control Software and Foxboro Control Software (FCS) ......... 4
2. Quick-Start Example ......................................................................................................... 5
3. Functional Characteristics ................................................................................................. 9
Functional and Environmental Constraints ............................................................................... 9
Input/Output Cabling ............................................................................................................
Cable Type .........................................................................................................................
Cable Length ......................................................................................................................
Use of Baluns .....................................................................................................................
10
10
11
11
17
18
18
19
23
27
28
29
29
32
32
36
36
37
38
46
47
iii
B0400FF Rev M
Contents
50
59
59
61
62
63
64
66
66
69
71
72
73
80
80
80
80
80
80
80
81
81
81
82
83
87
88
88
88
89
89
89
90
Contents
B0400FF Rev M
B0400FF Rev M
vi
Contents
Figures
1-1.
1-2.
2-1.
3-1.
3-2.
3-3.
4-1.
4-2.
4-3.
4-4.
4-5.
4-6.
4-7.
4-8.
4-9.
4-10.
4-11.
4-12.
4-13.
4-14.
4-15.
4-16.
4-17.
4-18.
4-19.
4-20.
4-21.
4-22.
4-23.
4-24.
4-25.
4-26.
4-27.
4-28.
4-29.
4-30.
4-31.
4-32.
Compact 200 Series FBM and Standard 200 Series FBM (Examples) ........................... 2
HART FBMs used in a Typical Network Configuration ............................................... 3
Typical HART/Foxboro Evo Integration Process .......................................................... 5
Cable Balun Module ................................................................................................... 11
Use of a Cable Balun (Externally Powered) ................................................................. 12
Intrinsic Safety Barrier Usage, Module-Powered Device .............................................. 12
Example Standard HART FBM and Termination Assembly Baseplate Installation ..... 13
FBM Mounting Slots in Standard 200 Series Standard Baseplates ............................... 14
Redundant Adapter or Baseplate-Mounted TA Installation (Typical) .......................... 17
FBM214/216 or FBM214b/216b TA Field Device Connections ................................ 18
FBM214/214b Input Signal Flow (1 of 2) .................................................................. 19
FBM216/216b Input Signal Flow (1 of 2) .................................................................. 21
Cable Balun Module, Externally Powered
HART Input Channels, Wiring Diagram .................................................................... 23
Cable Balun Module, Internal and Externally Powered
HART Input Channels, Wiring Diagram .................................................................... 24
Cable Balun Module with Intrinsic Safety or Zener Barriers,
Internal and Externally Powered HART Input Channels, Wiring Diagram ................. 25
Cable Balun Module with Transformer Isolated Barrier,
Internal and Externally Powered HART Input Channels, Wiring Diagram ................. 26
Cable Balun Module with Transformer Isolated Barrier,
Internal and Externally Powered 4-wire Devices, Wiring Diagram .............................. 27
FBM214/214b/216/216b Field Device Input Interface, Simplified Schematic ............ 28
FBM215/218 TA Cable Connections ......................................................................... 29
FBM215 Output Signal Flow ..................................................................................... 30
FBM218 Output Signal Flow ..................................................................................... 30
FBM215/218 Field Device Output Interface, Simplified Schematic ........................... 31
FBM244/245 TA Field Device Connections ............................................................... 32
FBM244 Output Connections .................................................................................... 33
FBM245 Output Connections with Redundant Adapter Connections ....................... 34
FBM244/245 Module, Channel Isolated Output Circuit, Simplified Schematic ......... 35
FBM247 TA Field Device Connections ...................................................................... 38
FBM247 Loop-Powered Current Input Connections .................................................. 39
FBM247 Self-Powered or Externally Powered Current Input Connections ................. 40
FBM247 Analog Voltage Input or Discrete Voltage Monitor Connections ................. 40
FBM247 Loop-Powered Current Output Connections ............................................... 41
FBM247 Self-Powered or Externally Powered Current Output Connections .............. 42
FBM247 Digital Dry Contact Sense Connections ....................................................... 43
FBM247 Solid State Switch Connections ................................................................... 43
FBM247 24 V dc Discrete Output Connections ......................................................... 44
FBM247 Voltage Pulse In - Pulse Count Frequency, etc. Connections ....................... 44
FBM247 Current Pulse In -Pulse Count Frequency, etc. Connections ........................ 45
FBM247 with Cable Balun, Externally Powered HART Input Channels,
Wiring Diagram Example ........................................................................................... 46
vii
B0400FF Rev M
5-1.
5-2.
5-3.
5-4.
5-5.
5-6.
5-7.
5-8.
5-9.
5-10.
5-11.
5-12.
5-13.
7-1.
7-2.
7-3.
7-4.
7-5.
7-6.
7-7.
7-8.
7-9.
7-10.
7-11.
7-12.
7-13.
7-14.
7-15.
viii
Figures
Tables
4-1.
4-2.
5-1.
5-2.
5-3.
5-4.
5-5.
5-6.
5-7.
5-8.
5-9.
5-10.
5-11.
5-12.
5-13.
5-14.
7-1.
7-2.
7-3.
7-4.
7-5.
7-6.
7-7.
7-8.
7-9.
7-10.
7-11.
7-12.
7-13.
7-14.
7-15.
Part Numbers for HART FBMs, Redundant Adapters and TAs .................................. 15
Entity Parameters for HART Communication Interface Modules .......................... 47
ECBs and DCI Blocks Used with HART FBMs ......................................................... 49
Key Parameters ............................................................................................................ 55
DCI Block Parameters Requiring a Point Address ....................................................... 60
Point Address Values for DCI Blocks .......................................................................... 60
Data Type Conversions ............................................................................................... 62
ECB200 SYSOPT Parameter - Analog and Pulse Input Integration Period ................. 66
ECB201 DVOPTS Parameter - Device Options ......................................................... 70
RIN, BIN, ROUT, and BOUT PNT_NO Parameter Settings ................................... 71
RIN PNT_NO Parameter Settings for HART Floating-Point Digital Variables ......... 73
IIN PNT_NO Parameter Settings for HART Integer Digital Variables ...................... 73
HART Device Status Bits ............................................................................................ 73
STRIN PNT_NO Parameter Settings for HART String Input Variables .................... 74
PAKIN PKINGP Parameter Settings for HART Packed Boolean Block
Configuration ............................................................................................................. 75
DCI Parameter Status ................................................................................................. 83
FBM214/215 Equipment Status and Information Display Fields ............................... 96
FBM216/216b/218 Equipment Status and Information Display Fields ...................... 99
FBM247 Equipment Status and Information Display Fields ..................................... 105
FBM214/214b/215/244/247 Equipment Change Actions ........................................ 111
FBM216/216b/218/245 Equipment Change Actions ............................................... 112
HART Device Equipment Status and Information Display Fields ............................ 115
FBM247 Channel (ECB201) Equipment Status and Information Display Fields ..... 118
HART Device and FBM247 Device/Signal Equipment Change Actions .................. 121
FBM247 ECB200 ECB Status Indicators ................................................................. 123
FBM247 ECB200 FBM Status Indicators ................................................................. 123
FBM247 Information in a ECB200 Faceplate ........................................................... 125
FBM247s Device ECB201 ECB Status Indicators ................................................... 126
FBM247s Device ECB201 DVC Status Indicators .................................................. 127
FBM247 Information in a ECB200 Faceplate ........................................................... 128
HART FBM Operational Status LEDs ..................................................................... 134
ix
B0400FF Rev M
Tables
Preface
This document describes the HART Communication Interface Modules (FBM214/214b,
FBM215, FBM216/216b, FBM218, FBM244, and FBM245). This document also describes
how to use the HART-capable FBM247, which supports a range of analog, digital and pulse field
I/O signals, with HART analog I/O signals.
Revision Information
For this revision of the document (B0400FF-M), the following changes were made:
Chapter 5 Control Block Configuration Information
Updated information about IOBAD on page 58.
Added Configuring IOBAD Options on page 59.
Added the IOBAD option to Table 5-7 on page 70.
Reference Documents
The following documents provide additional and related information.
Foxboro Documents
B0400FF Rev M
Preface
xii
Preface
B0400FF Rev M
Intelligent Field Device Configurator IFDC for use with I/A Series Systems (B0700EU)
HT991 Universal Hand terminal for HART Devices [MI EMO0110 A-(en)].
Most of these documents are available on the Foxboro Evo Electronic Documentation media
(K0174MA). The latest revisions of each document are also available through our Invensys
Global Customer Support at https://support.ips.invensys.com.
HART Documents
The following is a partial listing of the documents available at the HART website
(http://www.hartcomm.org):
HART FSK Physical Layer Specification, HCF_SPEC-54
HART Application Guide, HCF LIT 34
End User Info
Complete HART Guide.
Glossary of Terms
The following terminology, used throughout this users guide, relates to the HART FBMs and
their associated equipment.
Baseplate
The baseplate provides mounting for DIN rail mounted FBMs and FCMs
(see Figure 4-1 on page 13). A standard 200 Series baseplates eight
mounting positions can accommodate up to eight FBMs, or a combination of FBMs and FCMs. A Compact 200 Series 16-slot horizontal baseplate can accommodate up to 16 Compact 200 Series FBMs. The
baseplate also provides the necessary connectors for dc power, the Foxboro
Evo module Fieldbus, and termination cables.
Control Station
This is any Foxboro Evo module that effects process control via the Foxboro Evo Ethernet trunk Fieldbus. An example is the Field Control Processor 280 (FCP280). The control station controls process variables using
algorithms contained in functional control blocks configured by on-site
process engineers to implement the desired control strategies.
xiii
B0400FF Rev M
Preface
interface digital field device I/O communications with the Foxboro control station.
ECB
An equipment control block, created for each FBM and external field
device, provides a holding place for the software data associated with
that FBM or external field device.
FBM
FCM
Fieldbus
This term applies in general to two specific buses: the10 Mbps Ethernet
trunk Fieldbus and the 2 Mbps Module Fieldbus. (Figure 1-2 shows how
these buses are used in the Foxboro Evo communication network.)
FoxCAE
HART
IFDC
The Foxboro Evo Intelligent Field Device Configurator is a software package providing remote bidirectional communications with the Foxboro and
Eckardt intelligent field devices.
Letterbug
Parameter
Redundant Adapter
The redundant adapter, used with the redundant FBM pairs (FBM216,
FBM216b or FBM218), provides a Y connection between the FBM
pairs and the associated Termination Assembly (TA). This allows either
module in the pair to communicate with the field devices.
TA
xiv
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/214b215/216/216b/218/244/245) and the HART-capable FBM247 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 FBMs contains eight channels that are
group isolated for the FBM214/216 and individually isolated for the
FBM214b/215/216b/218/244/245 and FBM247.
The following 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 from that device.
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.
B0400FF Rev M
1. Introduction
Figure 1-1. Compact 200 Series FBM and Standard 200 Series FBM (Examples)
The following 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.
FBM247 - This HART-capable FBM supports a wide range of analog, digital or pulse
I/O capabilities, including support for HART I/O signals. Each channel is individually configurable, allowing multiple types of I/O signals to connect to a single
FBM247. Refer to the FBM247 Current/Voltage Analog/Digital/Pulse I/O Configurable Channel Interface Module with HART Support section in DIN Rail
Mounted Subsystem Users Guide (B0400FA) to learn about the full capabilities of this
FBM.
HART FBMs and the HART-capable FBM247 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-topoint 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 FBM247 can support HART field devices in a similar manner as the HART FBMs, in addition to the I/O signals described in DIN Rail Mounted Subsystem Users Guide (B0400FA).
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
2
1. Introduction
B0400FF Rev M
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.
Figure 1-2 shows the relationship between the various equipment elements in the subsystem. The
HART FBMs and the HART-capable FBM247 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.
To FCP280, FCP270, or
ZCP270/FCM100E/Et Pair
2 Mbps
Module Fieldbus
FBM214
or
FBM214b
Termination
Assemblies
TA
...
FBM215
TA
...
FBM216
FBM216
or
or
FBM216b FBM216b
FBM218
FBM218
REDUNDANT ADAPTER
REDUNDANT ADAPTER
TA
TA
...
...
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, refer to DIN Rail
Mounted Subsystem Users 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.
As well, a baseplate-mounted termination assembly (TA) is available for the HART-capable
FBM247 (as well as other non-HART FBMs, as discussed in DIN Rail Mounted Subsystem Users
Guide (B0400FA)). Using a baseplate-mounted TA eliminates the need to have a separate marshalling cabinet for the FBMs I/O, or for the spacing requirements needed to mount a separate,
standard termination assembly. This TA mounts directly onto the field I/O connectors of the 200
Series baseplate, in a similar manner as the redundant adapter. This TA supports two, non-redundant FBMs, provided that these FBMs are installed in adjacent slots as described in Redundant
Adapter and Baseplate-Mounted TA Installation on page 16.
B0400FF Rev M
1. Introduction
2. Quick-Start Example
This chapter provides an example configuration, which provides most of the information you
need to get your Foxboro Evo system and HART subsystem up and running in the shortest
possible time.
A typical sequence for installing and configuring a HART subsystem in a Foxboro Evo system is
outlined in Figure 2-1. Following this diagram is the procedure, whose steps are keyed to the
diagram.
NOTE
The following assumes that the individual HART field devices have been configured
for the required process control operations.
Start
1
Install HART FBMs
(or FBM247) and
Associated Foxboro Evo
Equipment
Connect Field
Devices to TA(s)
4
Create and Edit
an ECB200 for
Each FBM214/214b/215/
244/247
5
Create and Edit
Create
andfor
Edit
an
ECB202
ECB202
(if required)
Each
FBM216/216b/218
Configure Field
Devices
Enable
Communication with
Each Field Device
10
8
Place FBMs On-line
Checkpoint the
Database
12
Stop
NOTE: For the FBM247, all I/O signals may be from various sources, not necessarily field devices.
However, the same basic principles for configuration apply to this FBM.
Figure 2-1. Typical HART/Foxboro Evo Integration Process
B0400FF Rev M
2. Quick-Start Example
NOTE
This following overview of procedures assumes that you are familiar with Foxboro
Evo system concepts and HART concepts. Appropriate documents and sections
herein are referenced in each step.
1. Install the Foxboro Evo system, including the HART FBMs.
a. Plan the major elements of the current Foxboro Evo system, such as the 200 Series
baseplates, HART FBMs, and their power supplies, as described in DIN Rail
Mounted Subsystem Users Guide (B0400FA).
To set up your workstation, refer to the Hardware and Software Specific Instructions
document that was shipped with your workstation.
Plan and install the legacy I/A Series system equipment as described in
System Equipment Installation (B0193AC).
b. Perform the system definition by referring to the Configuration Information
section of DIN Rail Mounted Subsystem Users Guide (B0400FA).
c. Install the current Foxboro Evo Control Core Services software; refer to the appropriate Control Core Services installation document. All these documents are available on the Invensys Global Customer Support website
(https://support.ips.invensys.com).
d. Install the HART FBMs and the associated baseplate, FCM(s), redundant adapters, and TA(s) as described in the DIN Rail Mounted Subsystem Users Guide
(B0400FA) and Chapter 4 Equipment Installation of this user guide.
2. Connect field devices to the TAs.
Connect the field devices directly to the FBM TAs as described in Chapter 4 Equipment Installation.
3. Create and edit ECB110 for FCM or FCM100E/Et that hosts the HART FBMs.
Refer to the appropriate document for your system:
Block Configurator User's Guide (B0750AH)
I/A Series Configuration Component (IACC) User's Guide (B0700FE)
Integrated Control Configurator (B0193AV)
2. Quick-Start Example
B0400FF Rev M
B0400FF Rev M
2. Quick-Start Example
3. Functional Characteristics
This chapter addresses various requirements and constraints relating to the connection of the
HART FBMs and the HART-capable FBM247 to the field devices or HART I/O signals, and
their operation in conjunction with the control station.
When planning for installation and operation of the HART FBMs and the associated field
devices, or the HART-capable FBM247 and its associated HART I/O signals (or field devices),
you must consider the following factors:
FBM functional and environmental constraints
Input/Output Cabling.
Foxboro Evo Control Core Services v9.0 or later supports all HART FBMs.
For legacy systems with I/A Series software:
- FBM214b and FBM216b require I/A Series software, version 8.2-v8.8.
- FBM244 and FBM245 require I/A Series software, version 8.6-v8.8.
- The HART-capable FBM247 requires I/A Series software, version 8.7-v8.8.
- The Compact 200 Series FBMs require I/A Series software v8.8 or Foxboro Evo
Control Core Services v9.0 or later.
Refer to the following documents for functional and environmental specifications relating to the
FBM214/214b/215/244, the redundant FBM216/216b/218/245 and FBM247 modules and the
associated TAs:
PSS 21H-2Z14 B4 FBM214, HART Communication Input Interface Modules
(Legacy)
PSS 21H-2Z14 B5 FBM214b, HART Communication Input Interface Module
PSS 31H-2C214 B4 Compact FBM214b, HART Communication Input Interface
Module
PSS 21H-2Z15 B4 FBM215 HART Communication Output Interface Module
PSS 31H-2C215 B4 Compact FBM215 HART Communication Output Interface
Module
PSS 21H-2Z16 B4 FBM216 HART Communication Redundant Input Interface
Modules (Legacy)
9
B0400FF Rev M
3. Functional Characteristics
The HART-capable FBM247 supports a wide range of analog, digital or pulse I/O
capabilities, including support for HART I/O signals. Refer to the FBM247 Current/Voltage Analog/Digital/Pulse I/O Configurable Channel Interface Module with
HART Support section in DIN Rail Mounted Subsystem Users Guide (B0400FA) to
learn about the full capabilities of FBM247.
HART FBMs and the HART-capable FBM247 are used in the configuration shown in Figure 1-2
on page 3. 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 the following subsections.
NOTE
These subsections apply only to HART FBMs and the HART-capable FBM247
when connected to HART field devices. To learn about cabling for the FBM247
when connected non-HART field devices, refer to the Field Signal Connections
section in DIN Rail Mounted Subsystem Users Guide (B0400FA).
Input/Output Cabling
The basic cabling scheme is shown in Figure 1-2 on page 3 and the actual connections to the TAs
are addressed in Chapter 4 Equipment Installation. The following paragraphs provide additional information.
Cable Type
Cable Type A, standard shielded twisted pair (STP) cabling, is used to wire the field devices to
termination assemblies (TAs). Unshielded cable may be used only when it has been conclu-
10
3. Functional Characteristics
B0400FF Rev M
sively demonstrated that ambient noise does not affect communication. For details, refer to
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, refer to HART FSK physical layer specification document
HCF_SPEC-54.
Use of Baluns
A cable balun module, shown in Figure 3-1, 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.
Figure 3-2 shows typical hookup. The Cable Balun module provides protection to the HART signal and eliminates cross-talk between the channels and/or disruption to the HART signal. They
are recommended when the HART protocol on the HART FBMs 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.
11
B0400FF Rev M
3. Functional Characteristics
FBM
Termination
Assembly
_
T
+
Intrinsic
Safety
Barrier
(when used)
iP
Field
Cable
Side
1
2
3
4
5
6
7
8
System
Side
i+
i-
1
2
3
4
5
6
7
8
Cable
Balun
Module
CBM-4
(P0903SV)
To Other
Channels
External
Power
Supply
To NegativeTerminal
of Ext. Power Supply
Note: Each balun module supports four channels. Two balun modules are required for eight
channels of the FBM.
Figure 3-2. Use of a Cable Balun (Externally Powered)
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.
Intrinsic
Safety
Barrier
(when used)
FBM
Termination
Assembly
+
iP
i+
i-
12
4. Equipment Installation
This chapter provides installation information for the HART FBMs, redundant adapters, and
associated termination assemblies (TAs).
Before installing the HART FBMs, you must install the major elements of the Foxboro Evo Process Automation System as follows [refer to DIN Rail Mounted Subsystem Users Guide
(B0400FA)]:
1. Perform the system definition by referring to Configuration Information in the
DIN Rail Mounted Subsystem Users Guide (B0400FA).
2. Install the current Control Core Services - refer to the appropriate Control Core Services installation document. All these documents are available on the Invensys Global
Customer Support website (https://support.ips.invensys.com).
3. Install the HART FBMs associated baseplate, if it is not already installed, as described
in DIN Rail Mounted Subsystem Users Guide (B0400FA).
A typical standard HART FBM installation including an FBM214, FBM215, and a redundant
pair of FBM216s is shown in Figure 4-1.
Module Fieldbus
Baseplate
To Fieldbus
Communications
Modules,
FCP270, or
FCP280
Operational Status
Operational Status
Operational Status
IR Active
01
IR Active
01
IR Active
01
Master
02
Master
02
Tracker
03
Tracker
03
03
04
04
04
05
05
05
06
06
06
07
07
07
08
08
08
FBM216
Baseplate I. D.
8 Communication,
No.
1
Redundant HART
Input
0
ON
P0917TN
1
OFF
2
ON
ON
ON
OFF OFF
To Next
Baseplate (If
Applicable)
02
FBM216
FBM215
8 Communication,
Redundant HART Input
P0917TN
Channel Isolated
8 Communication,
HART Output
P0917TQ
OFF
Termination
Cable
al Status
Operation
01
01
02
03
04
02
03
08
N
P
U
T
05
0607
04
05
i- i+
i-
iP
i+ iP
i- i+ iP
i- i+ iP
i- i+ iP
i- i+ iP
i- i+ iP
i- i+ iP
-2
IR Active
C
C 8
C 70
C 60
C 05 0
C 4
C 30
C 02 0
01
06
07
08
B
B 08
B 07
B 06
B 05
B 04
B 03
B 02
1
A
A 08
A 07
A 06
A 05
04
A
A 03
A 02
FBM21
n,
unicatio
8 Comm ut
Inp
HART Q
P0914X
Fieldbus
Module
(FBM214)
01
Termination
Assembly
Figure 4-1. Example Standard HART FBM and Termination Assembly Baseplate Installation
13
B0400FF Rev M
4. Equipment Installation
NOTE
For diagrams and installation instructions for the Compact 200 Series FBMs, refer
to DIN Rail Mounted Subsystem Users Guide (B0400FA).
As shown in Figure 4-1, 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. Figure 4-2
shows the available FBM mounting slots in the horizontal and vertical standard baseplates.
Horizontal-Mount Baseplate
Slots for Non-Redundant HART FBMs
2
OFF
Baseplate I. D.
No.
0
1
2
3
1
ON
2
ON
OFF ON
ON OFF
OFF OFF
Vertical-Mount Baseplate
1
A
1
OFF
Baseplate I. D.
No.
0
1
2
3
1
ON
2
ON
OFF ON
ON OFF
OFF OFF
B
4
Slots for Redundant Pairs
5
Slots for
Non-Redundant
HART FBMs
C
6
7
D
8
Figure 4-2. FBM Mounting Slots in Standard 200 Series Standard Baseplates
14
4. Equipment Installation
B0400FF Rev M
NOTE
For the available Compact FBM mounting slots in the Compact 200 Series 16-slot
horizontal baseplate, refer to FBM Installation (Placement) in DIN Rail Mounted
Subsystem Users Guide (B0400FA).
The part numbers for HART FBMs and the associated TAs are listed in Table 4-1.
Table 4-1. Part Numbers for HART FBMs, Redundant Adapters and TAs
Equipment
FBM214
FBM214b (Standard)
FBM214b (Compact)
FBM215 (Standard)
FBM215 (Compact)
FBM216
FBM216b (Standard)
FBM216b (Compact)
FBM218 (Standard)
FBM218 (Compact)
FBM244
FBM245
FBM247
Redundant Adapter for FBM216
Redundant Adapter for FBM216b (Standard)
Redundant Adapter for FBM216b (Compact)
Redundant Adapter for FBM218 (Standard)
Redundant Adapter for FBM218 (Compact)
Redundant Adapter for FBM245
Compression-type TA for FBM214/216
Compression-type TA for FBM214b/216b
Compression-type TA for FBM215/218
Compression-type TA for FBM244/245
Compression-type TA for FBM247
Baseplate-mounted TA2 for FBM247
Ring lug-type TA for FBM214/216
Ring lug-type TA for FBM215/218
1.
2.
Part Number
P0914XQ/P0922VT
P0927AH
RH101AB
P0917TQ/P0922VU
RH101AC
P0917TN/P0922VV
P0927AJ
RH101AD
P0917XK/P0922VW
RH101AE
P0927AK
P0927AL
P0927BN
P0917XQ
P0924DT
RH101AX
P0916QD
RH101AY
P0924DU
P0916BX
P0924JH
P0917XV
P0924QU, P0924QZ1
P0924WW
P0924WG
P0926EA
P0926EK
15
B0400FF Rev M
4. Equipment Installation
For the available termination cables, refer to Polyurethane Termination Cables and Part Numbers, Low Smoke Zero Halogen (LSZH) Termination Cables and Part Number, and Hypalon
TA Cables and Part Numbers in DIN Rail Mounted Subsystem Users Guide (B0400FA).
For general instructions on installing the FBMs and TAs, refer to DIN Rail Mounted Subsystem
Users Guide (B0400FA). The non-redundant FBM214/214b/215/244/247 can be located in any
slot on the baseplate, with the associated TAs connected to the associated cable connectors.
NOTE
FBM247s may use baseplate-mounted TAs, which mount directly onto the field
I/O connectors of the 200 Series baseplate. A baseplate-mounted TA provides field
I/O wiring support for two FBM247s in adjacent positions on the baseplate (positions 1 and 2, 3 and 4, 5 and 6 or 7 and 8).
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.
16
4. Equipment Installation
B0400FF Rev M
The redundant adapter and the baseplate-mounted TA are position dependent, supporting field
I/O wiring for two FBMs in paired baseplate slots (for example, in positions 1 and 2, 3 and 4, 5
and 6, or 7 and 8), since their connectors must engage the corresponding pairs of connectors on
the baseplate, adjacent to their associated FBM pair.
NOTE
On the horizontal baseplate, paired FBMs (and thus the redundant adapter) are
placed in adjacent odd/even paired positions on the baseplate (see Figure 4-2). On
the vertical baseplate, paired FBMs may be placed in any adjacent odd/even paired
positions.
For a redundant pair of HART FBMs, attach their redundant adapter onto the two I/O connectors which correspond to the FBM pairs slot position on the baseplate. Figure 4-3 shows installation of a redundant adapter for the FBM216. The redundant adapters for the FBM216b,
FBM218 and FBM245 are similar in construction.
Operational Status
Operational Status
IR Active
01
IR Active
01
Master
02
Master
02
Tracker
03
Tracker
OFF
03
04
04
05
05
06
06
07
07
08
08
FBM216
FBM216
8 Communication,
Redundant HART Input
P0917TN
8 Communication,
Redundant HART Input
P0917TN
Baseplate I. D.
2
ON
ON
OFF
OFF
01 02 03 04
Input (P)
Input (P)
08 07 06 05
FBM216
Redundant Adapter
1
ON
OFF
ON
OFF
No.
0
1
2
3
Redundant
Adapter
Input (-)
P0917XQ
01
05
04
08
NOTE
For the redundant adapters used on the Compact 200 Series 16-slot horizontal baseplate, refer to Redundant Adapter Installation for Compact 200 Series Baseplates
in DIN Rail Mounted Subsystem Users Guide (B0400FA).
B0400FF Rev M
4. Equipment Installation
shown on the TA labels. Type A, shielded twisted-pair cables (for making the device connections
to the TAs) are available from Foxboro and have the following part numbers:
P0170GG (flame retardant)
P0170GF (non-flame retardant).
Connections to FBM214/214b/216/216b/244
Make the cable connections to the FBM214/214b/216/216b/244 TA as shown in Figure 4-4. For
reference purposes, schematic representations of the input signal flows for the
FBM214/214b/216/216b are shown in Figure 4-5 and Figure 4-6, respectively. Cable Balun
Module connections for 2-wire devices are shown in Figure 4-7 through Figure 4-10. Cable Balun
Module connections for 4-wire devices are shown in Figure 4-11. Also, a simplified schematic of
the FBM214/214b/216/216b input circuitry is shown in Figure 4-12 on page 28. Entity parameters for the FBM214/214b/216/216b are listed in Table 4-2.
8
C
O
M
M
U
N
I
C
A
T
I
O
N
TA Label
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
Points:
C = iP
B = i+
A = iTo
HART
Field
Devices
C
B
A
See Note
Note: Cable connections are shown for Channel 1. Other channels are connected in a similar manner.
Figure 4-4. FBM214/216 or FBM214b/216b TA Field Device Connections
18
4. Equipment Installation
B0400FF Rev M
iP+ Cx*
Baseplate
(to FBM214
or FBM214b)
i+ Bx*
Transmitter
Ax*
Termination Assembly
(P0916BX, P0926EA, P0924JH)
Field Connections
Termination
Cable Type 1
(25 pin to 37 pin)
Transmitter
Intrinsic
Safety
Barrier
iP+ Cx*
Baseplate
(to FBM214
or FBM214b)
i+ Bx*
Ax*
Termination Assembly
(P0916BX, P0926EA, P0924JH)
Field Connections
Termination
Cable Type 1
(25 pin to 37 pin)
19
B0400FF Rev M
4. Equipment Installation
See Note 8
+
Transmitter
Intrinsic Safety +
Barrier
Field
Cable
System
1
1
2 Balun 2
3 Module 3
4
4
5
5
6 CBM-4 6
7
7
8 P0903SV 8
Baseplate
(to
FBM214 or
FBM214b)
i- Ax*
Refer to Note 2
External Power
Supply
Termination
Cable Type 1
20
4. Equipment Installation
B0400FF Rev M
iP
iP+ Cx*
i+
280
i+ Bx*
Transmitter
Test
Ax*
iiP
i+
Test
Termination Assembly
(P0916BX, P0926EA,
P0924JH)
Field Connections
Termination
Cable Type 1
i-
To
FBM216/216b
(redundant
FBM216 or
module)
FBM216b
Redundant Adapter
+
Transmitter
iP+ Cx*
Intrinsic
Safety
Barrier
iP
i+
280
i+ Bx*
Test
Ax*
iiP
i+
Test
Termination Assembly
(P0916BX, P0926EA,
P0924JH)
Field Connections
To
FBM216/216b
(primary
module)
i-
Termination
Cable Type 1
FBM216 or
FBM216b
Redundant Adapter
To
FBM216/216b
(redundant
module)
21
B0400FF Rev M
4. Equipment Installation
Termination Assembly
(P0916BX, P0926EA,
Cx*
P0924JH)
Field Connections
i+ Bx*
i+
280
Test
+
Transmitter
Intrinsic Safety +
Barrier
Field
System
1 Cable 1
2
2
3 Balun 3
4 Module 4
5
5
6
6
7 CBM-4 7
8
8
P0903SV
iP
i- Ax*
iiP
i+
Test
i-
Refer to Note 2
External Power
Supply
To
FBM216/
FBM216b
(redundant
module)
FBM216 or
FBM216b
Redundant Adapter
Termination
Cable Type 1
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.
Figure 4-6. FBM216/216b Input Signal Flow (2 of 2)
22
4. Equipment Installation
B0400FF Rev M
iiP
i+
i-
i+
iP
TA Terminal Block
23
iiP
i+
i-
i+
iP
i-
i+
4. Equipment Installation
(iP+)
TA Terminal Block
iP
B0400FF Rev M
24
iiP
i+
i-
i+
iP
i-
B0400FF Rev M
(iP+)
i+
TA Terminal Block
4. Equipment Installation
Figure 4-9. Cable Balun Module with Intrinsic Safety or Zener Barriers,
Internal and Externally Powered HART Input Channels, Wiring Diagram
25
4. Equipment Installation
iiP
i+
i-
i+
iP
i-
i+
TA Terminal Block
iP
B0400FF Rev M
26
4. Equipment Installation
B0400FF Rev M
TA Terminal Block
27
B0400FF Rev M
4. Equipment Installation
LP_PWR
+24 V dc
Current Limiter
Transmit Enable
26 V
Transmit Driver
5.5 V
51
4.7 F
+7.5 V
CHPOS
Transmit Signal
Receive Filter
5.1 K
+5 V
680 pF
Receive Signal
220
SIGPOS
7.5 K
61.9
A to D Converter
5.5 V
CHNEG
SIGNEG
7.5 K
2.5 V Ref.
+5 V dc
NOTE
28
4. Equipment Installation
B0400FF Rev M
Connections to FBM215/218
Make the cable connections to the FBM215/218 TA as shown in Figure 4-13. For reference purposes, schematic representations of the output signal flows for the FBM215/218 are shown in
Figure 4-14 and Figure 4-15, respectively. Also, a simplified schematic of the FBM215/218 output circuitry is shown in Figure 4-16. Entity parameters for the FBM215/218 are listed in
Table 4-2.
8
C
O
M
M
U
N
I
C
A
T
I
O
N
TA Label
Signal
Connection
Points:
B = o+
A = oTo
HART
Field
Device
o+ o+ o+ o+ o+ o+ o+ o+
o- o- o- o- o- o- o- o-
See Note
Note: Cable connections are shown for Channel 1. Other channels are connected in a similar manner.
Figure 4-13. FBM215/218 TA Cable Connections
29
B0400FF Rev M
4. Equipment Installation
Actuator
+
o+
Baseplate
(to FBM215)
Bx*
o- Ax*
Termination Assembly
(P0917XV, P0926EK)
Field Connections
Termination
Cable Type 1
(25 pin to 37 pin)
NOTES:
1. 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.
Figure 4-14. FBM215 Output Signal Flow
+
-
Actuator
o-
Bx*
o+
o-
Ax*
Termination Assembly
(P0917XV, P0926EK)
Field Connections
FBM218
(primary
module)
Termination
Cable Type 1
(25 pin to 37 pin)
o+
o-
FBM218
(redundant
module)
NOTES:
1. Field circuitry must have entity parameters compatible with those of FBM218 (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.
Figure 4-15. FBM218 Output Signal Flow
30
4. Equipment Installation
B0400FF Rev M
Isolated
Loop
Power
Supply
OUTPOS
33 V
OUTNEG
Current
Driver
D/A
Converter
Opto-Isolators
TO ASIC
Logic
Transmit Driver
123
1 mF
1.96 K
Transmit Signal
5 K
Receive Filter
Receive Signal
33 V
680 pF
31
B0400FF Rev M
4. Equipment Installation
Connections to FBM244/245
Make the cable connections to the FBM244/245 TAs as shown in Figure 4-17. For reference purposes, schematic representations of the output signal flows for the FBM244/245 are shown in
Figure 4-18 and Figure 4-19, respectively.
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, refer to FBM Replacement using the Output Bypass Station in DIN
Rail Mounted Subsystem Users Guide (B0400FA).
Also, simplified schematics of the FBM244/245 output circuitry are shown in Figure 4-20. Entity
parameters for the FBM244/245 are listed in Table 4-2.
P0924QZ
01 02 03 04 05 06 07 08
Customer
Labeling
Area
Signal
Connection
Points C = iP
B = i+
A = i-
01 02 03 04 05 06 07 08
Customer
Labeling
Area
iP iP iP iP sh sh sh sh
i+ i+ i+ i+ o+ o+ o+ o+
i- i- i- i- o- o- o- o-
Signal
Connection
Points C = iP
B = i+
A = i-
32
4. Equipment Installation
B0400FF Rev M
5 Cx*
Actuator
+
o+
o- Ax*
Termination Assembly
(P0924QU)
Field Connections
Baseplate
(to FBM244)
Bx*
Termination
Cable Type 1
(25 pin to 37 pin)
5 Cx*
Actuator
+
o+
o- Ax*
Baseplate
(to FBM244)
Bx*
Termination Assembly
(P0924QZ)
Field Connections
Termination
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.
Figure 4-18. FBM244 Output Connections
33
B0400FF Rev M
4. Equipment Installation
5 Cx*
Actuator
+
o+
o- Ax*
Bx*
o+
o-
Termination Assembly
(P0924QU)
Field Connections
Termination
Cable Type 1
(25 pin to 37 pin)
o+
o-
FBM245
(primary
module)
FBM245
(redundant
module)
Redundant Adapter
(P0924DU) (mounted
on baseplate)
5 Cx*
Actuator
+
o+
o- Ax*
Bx*
Termination Assembly
(P0924QZ)
Field Connections
o+
o-
FBM245
(primary
module)
Termination
Cable Type 1
(25 pin to 37 pin)
o+
o-
FBM245
(redundant
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.
Figure 4-19. FBM245 Output Connections with Redundant Adapter Connections
34
4. Equipment Installation
B0400FF Rev M
Isolated
Loop
Power
Supply
OUTPOS
33 V
OUTNEG
Current
Driver
D/A
Converter
Opto-Isolators
TO ASIC
Logic
Transmit Driver
123
1 mF
1.96 K
Transmit Signal
5 K
Receive Filter
Receive Signal
33 V
680 pF
Figure 4-20. FBM244/245 Module, Channel Isolated Output Circuit, Simplified Schematic
35
B0400FF Rev M
4. Equipment Installation
Connections to FBM247
The FBM247 contains eight individual channels which can be individually configured for a range
of analog, digital and pulse field I/O signals, including the following:
HART Analog Input (AI)/Analog Output (AO) 4-20 mA
0-20 mA AI/AO, non-HART
0-10 V and 0-5V AI, non-HART
4. Equipment Installation
B0400FF Rev M
external loop power, the channel input impedance is approximately 170 Ohms. These configurations allow for the connection of various two-wire sensors such as switches, relay contacts, or
active proximity devices. The input current switching thresholds are chosen to be compatible with
the recommendations of the NAMUR standard. For non-intrinsically safe applications, this
allows the convenience of direct connecting two-wire NAMUR sensors as input devices.
NAMUR fault detection is not implemented for these configurations.
NOTE
For some NAMUR sensors, additional external loop resistance may be required for
proper operation. Follow the details contained within the manufacturer's sensor
device data sheet.
For some NAMUR sensors, additional external loop resistance may be required for
proper operation. Follow the details contained within the manufacturer's sensor
device data sheet.
In addition to NAMUR type sensors, the NAMUR configuration supports an array of other types
of contact inputs. To ensure that the open circuit detection functions properly when using nonNAMUR contact type inputs, the addition of a resistor across the contacts is required to provide
the proper non-alarm current level (i.e. 0.5 to 1.0 mA) for the open contact condition.
NOTE
37
B0400FF Rev M
4. Equipment Installation
Customer
Labeling
Area
Signal
Connection
Points C = +
B=A = SH
P0924WG
Baseplate-Mounted
01 02 03 04 05 06 07 08
+ + + + + + + +
- - - - - - - Sh Sh Sh Sh Sh Sh Sh Sh
Signal
Connection
Points C = +
B=A = SH
01 02 03 04 05 06 07 08
FBM POS 1, 3, 5, 7
+ + + + + + + +
- - - - - - - Sh Sh Sh Sh Sh Sh Sh Sh
01 02 03 04 05 06 07 08
FBM POS 2, 4, 6, 8
+ + + + + + + +
- - - - - - - Sh Sh Sh Sh Sh Sh Sh Sh
38
4. Equipment Installation
Transmitter
+
B0400FF Rev M
25 V dc
Isolated
Loop Power
Supply
Loop Power
43 V
Current In
Current
Driver
I Limit
Set to
35 mA
I Limit
from ASIC
Logic
50 Ohms 1 F
HART
Transmit
Driver
+
A/D
120 Ohms
Control
SDI
SCLK
5 KOhms
680
Pf
ISOLATORS
SH
SDO
HART
Receive
Filter
HART
Transmit
Signal
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
HART
Receive
Signal
39
B0400FF Rev M
4. Equipment Installation
Current In
43 V
Current
Driver
Transmitter
P.S. See Note
- Return
I Limit
Set to
35 mA
SH
I Limit
from ASIC
Logic
50 Ohms 1 F
HART
Transmit
Driver
Control
SDI
SCLK
+
A/D
120 Ohms
-
5 KOhms
680
Pf
ISOLATORS
SDO
HART
Receive
Filter
HART
Transmit
Signal
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
HART
Receive
Signal
Control
0-5 or
0-10
V dc
Input
43 V
10 MOhms
SDI
A/D
SCLK
SDO
ADC Controls
ISOLATORS
x1
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
Offset
SH
40
4. Equipment Installation
Actuator
+
25 V dc
Isolated
Loop Power
Supply
Loop Power
43 V
SH
B0400FF Rev M
Current In
Current
Driver
D/A
I = 0 to
20.4 mA See Note
HART
Transmit
Driver
Control
SDI
SCLK
+
120 Ohms
A/D
-
5 KOhms
680
Pf
ISOLATORS
1550 Ohms** 1 F
I Limit
from ASIC
Logic
SDO
HART
Receive
Filter
HART
Transmit
Signal
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
HART
Receive
Signal
41
B0400FF Rev M
4. Equipment Installation
43 V
+
Current In
Current
Driver
D/A
I = 0 to
20.4 mA See Note 2
Return
+
P.S.
1550 Ohms** 1 F
HART
Transmit
Driver
See
Note 1
SH
Control
SDI
SCLK
+
A/D
120 Ohms
-
5 KOhms
680
Pf
SDO
HART
Receive
Filter
I Limit
from ASIC
Logic
ISOLATORS
Actuator
-
HART
Transmit
Signal
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
HART
Receive
Signal
NOTES:
1. Power supply may be internal to the actuator/positioner.
2. 4-20 mA for HART.
* Shield connection provided if required.
** This resistor must be 1550 Ohms when an actuator is connected.
Figure 4-26. FBM247 Self-Powered or Externally Powered Current Output Connections
42
4. Equipment Installation
B0400FF Rev M
25 V dc
Isolated
Loop Power
Supply
Loop Power
+
+
43 V
Return
External Contact
Current
Driver
I Limit
Set to
10 mA
I Limit
from ASIC
Logic
+
A/D
120 Ohms
* Shield connection provided
if required.
Control
SDI
SCLK
ISOLATORS
SH
SDO
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
+
Load
43 V
+
Current
Driver
Output
ON/OFF
from ASIC
Logic
I Limit
20.4 mA
Return
+
P.S.
See
Note
SH
*
+
A/D
120 Ohms
-
Control
SDI
SCLK
SDO
ISOLATORS
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
43
B0400FF Rev M
4. Equipment Installation
25 V dc
Isolated
Loop Power
Supply
Loop Power
+
+
Load
43 V
Return
Current
Driver
*
Output
ON/OFF
from ASIC
Logic
I Limit
set to
20.4 mA
+
120 Ohms
* Shield connection provided
if required.
A/D
ISOLATORS
SH
Control
SDI
SCLK
SDO
ADC Controls
Serial Data
To ADC
Serial Clock
To ADC
Serial Data
From ADC
Voltage
Pulse
In
SH
43 V
-
V
Threshold
Data Out
ISOLATORS
Data Out
44
4. Equipment Installation
B0400FF Rev M
+
+
43 V
Current
Pulse In
I Limit
10 mA
SH
Source
120 Ohms
* Shield connection provided
if required.
I Threshold
(NAMUR
Units)
Data Out
ISOLATORS
I Set
ON/OFF
from AIS
Logic
Data Out
Figure 4-31. FBM247 Current Pulse In -Pulse Count Frequency, etc. Connections
45
B0400FF Rev M
4. Equipment Installation
* Refer to B0400FA for detailed installation instructions for the P0903SU Cable Balun
i-
i+
SH
i-
i+
SH
TA Terminal Block
Figure 4-32. FBM247 with Cable Balun, Externally Powered HART Input Channels,
Wiring Diagram Example
46
4. Equipment Installation
B0400FF Rev M
Entity Parameters3
FBM
Type
TA Type
(P/N)1
FBM214
P0916BX,
P0926EA
FBM214
*, P0926TD
FBM2164
P0916BX,
P0926EA
FBM2164
*, P0926TD
FBM214b/
FBM216b4
P0924JH
FBM215
P0917XV,
P0926EK
*, P0926SP
P0917XV,
P0926EK
*, P0926SP
P0924QU,
P0924QZ
FBM215
FBM2184
FBM2184
FBM244
FBM2454
P0924QU,
P0924QZ
FBM247
P0924WW,
P0924WG
TA Field
Terminal
Field Circuit
Type2
(S) Um
(R) Ui
(S) Io
(R) Ii
(S) Co
(R) Ci
(S) Lo
(R) Li
i+ to iP
i+ to ii+ to iP
i+ to ii+ to iP
i+ to ii+ to iP
i+ to ii+ to iP
i+ to io+ to o-
Input (S)
Input (R)
Input (S)
Input (R)
Input (S)
Input (R)
Input (S)
Input (R)
Input (S)
Input (R)
Output (S)
25
60
25
60
25
60
25
60
25
60
33
33
34
33
34
64
34
33
34
64
34
21
3nF
0
3nF
0
3nF
0
3nF
0
3nF
0
3nF
0
0
0
0
0
0
0
0
0
0
0
o+ to oo+ to o-
Output (S)
Output (S)
33
33
21
21
3nF
3nF
0
0
o+ to oiP to i+
iP to ii+ to io+ to oiP to i+
iP to ii+ to io+ to oi+ to i-
Output (S)
Input (S)
Input (S)
Input (R)
Output (S)
Input (S)
Input (S)
Input (R)
Output (S)
Input/
Output (S)6
Input/
Output (R)
33
25
25
6
32
25
25
6
32
27
21
35
35
215
21
70
70
215
21
30
3nF
0.4
0.4
0
0.18
0.4
0.4
0
0.18
0.309
0
65
65
0
180
16
16
0
180
88.9
30
30
i+ to i1.
2.
3.
4.
The TA part numbers are listed as follows: compression type, ring lug type. * indicates that there
is no compression-type equivalent for this TA.
(S) = the FBM terminals supply energy; (R) = the FBM terminals receive energy. This defines
whether to use Um or Ui, Io or Ii, Co or Ci, and Lo or Li in the entity parameter columns.
Units are expressed as follows: Um and Ui in dc Volts; Io and Ii in dc mA; Co and Ci in F; Lo
and Li in mH.
Requires redundant adapter mounted on baseplate to support redundancy.
47
B0400FF Rev M
5.
6.
48
4. Equipment Installation
ECB/DCI Block
ECB110
ECB200
ECB202
ECB201
RIN
ROUT
IIN
STRIN
1.
Description
Fieldbus Communications Module (FCM) for DIN rail subsystem
Parent ECB, representing the FBM214, FBM214b, FBM215, FBM244
or FBM247
Parent ECB, representing a pair of redundant FBMs: two FBM216s, two
FBM216bs, two FBM218s or two FBM245s
Child ECB representing a field device, or I/O source for one FBM247
channel
Real Input DCI Block
Real Output DCI block
Integer Input DCI block
String Input DCI block
The FBM247 supports additional blocks not listed in this table (BIN, BOUT and PAKIN).
Refer to Configuring Blocks for FBM247 on page 66 for the full range of blocks supported
by the FBM247 for all the types of I/O signals this FBM supports.
This chapter provides key information regarding control block configuration. For specific information on the ECB/DCI control block parameter settings, refer to Integrated Control Block
Descriptions (B0193AX) and Integrated Control Block Descriptions for FOUNDATION fieldbus
Specific Control Blocks (B0700EC).
49
B0400FF Rev M
Block Interconnections
In order for process control operations to be performed, you must create and configure ECBs,
DCI blocks, and other Foxboro Evo control blocks for control scheme implementation.
Figure 5-1 shows the ECB hierarchy.
Foxboro
Control Station
ECB110
(FCM)
ECB200
(FBM214/215)
or
ECB202*
(FBM216/218)
ECB201
ECB201
HART Devices
* Each ECB202 block represents a pair of redundant FBMs: FBM216s, FBM216bs,
FBM218s or FBM245s.
Figure 5-1. ECB Hierarchy
Configuration Procedures
As indicated in Figure 5-1, an ECB200 must be configured for each FBM214, FBM214b,
FBM215, FBM244, or FBM247 and an ECB202 must be configured for each FBM216,
FBM216b, FBM218 or FBM245 redundant pair. For each device associated with the FBMs (or
for the FBM247, each I/O signal associated with the FBM247), 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 or FBM247 parameter that is connectable. (Table 5-1 above lists the
DCI block types used in HART data transfer operations for the HART FBMs, and for other data
transfer operations supported by the FBM247.) The DCI blocks can be configured anywhere in
the Continuous List hierarchy (List 1 or 2), in any compound in a control station.
NOTE
In the following examples, the source of the I/O signal does not need to be a HART
device for the HART-capable FBM247.
Figure 5-2 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. (This real input could be derived from an alternative
source for the FBM247.)
Figure 5-3 on page 52 shows the user-configured connections between the various elements of a
typical control scheme using an FBM218 with HART output devices. In this figure, a ROUT
50
B0400FF Rev M
block is used to process a real output value directed to HART devices. (This real output could be
derived from an alternative source for the FBM247.)
Figure 5-4 on page 53 shows the user-configured connections between the various elements of a
typical control scheme using an FBM214/214b with 4-20 mA input devices. In this figure, a RIN
block is used to process a real input from 4-20 mA devices. (This real input could be derived from
an alternative source for the FBM247.)
Configuration for other types of device I/O parameters and corresponding DCI blocks is similar,
with similar interconnections between the ECBs and DCI blocks. Table 5-2 on page 55 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).
ECB200
NAME
DEV_ID
HART
Device
Channel#1
HART
Device
Channel#8
SLOT03
SLOT03
ECB201
NAME
PARENT
DVOPTS
DVNAME
PT_101
:SLOT03
HART
CH1
(See Note 3)
ECB201
NAME
PARENT
DVOPTS
DVNAME
PT_108
:SLOT03
HART
CH8
(See Note 3)
RIN Block
NAME
PT_101
IOMID
CP6SG5_ECB:PT_101
PNT_NO (See Note 2)
RIN Block
NAME
PT_108
IOMID
CP6SG5_ECB:PT_108
PNT_NO (See Note 2)
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the devices ECB201 for
each HART signal/value that is to be interfaced to the Foxboro Evo system.
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. Refer to Point
Addresses for HART and Analog I/O Signals on page 59 for details.
3. DVNAME contains the channel number CH1-CH8 of the associated device.
Figure 5-2. Typical Block Interconnections for FBM214/214b with HART Input Devices
51
B0400FF Rev M
ECB202
NAME
DEV_ID
HART
Device
Channel#1
HART
Device
Channel#8
SLOT0C
SLOT0C
ECB201
NAME
PARENT
DVOPTS
DVNAME
VP_101
:SLOT0C
HART
CH1
(See Note 3)
ECB201
NAME
PARENT
DVOPTS
DVNAME
VP_108
:SLOT0C
HART
CH8
(See Note 3)
ROUT Block
NAME
VP_101
IOMID
CP6SG5_ECB:VP_101
PNT_NO (See Note 2)
ROUT Block
NAME
VP_108
IOMID
CP6SG5_ECB:VP_108
PNT_NO (See Note 2)
NOTES:
1. A DCI block (such as ROUT) must be configured and connected to the devices ECB201 for
each HART signal/value that is to be interfaced to the Foxboro Evo system.
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. Refer to Point
Addresses for HART and Analog I/O Signals on page 59 for details.
3. DVNAME contains the channel number CH1-CH8 of the associated device.
Figure 5-3. Typical Block Interconnections for FBM218 with HART Output Devices
52
B0400FF Rev M
ECB200
NAME
DEV_ID
Input
Device
Channel#1
Input
Device
Channel#8
SLOT04
SLOT04
ECB201
NAME
PARENT
DVOPTS
DVNAME
FT_101
:SLOT04
4-20
CH1
(See Note 2)
ECB201
NAME
PARENT
DVOPTS
DVNAME
FT_108
:SLOT04
4-20
CH8
(See Note 2)
RIN Block
NAME
FT_101
IOMID
CP6SG5_ECB:FT_101
PNT_NO CURRENT
RIN Block
NAME
FT_108
IOMID
CP6SG5_ECB:FT_108
PNT_NO CURRENT
NOTES:
1. A DCI block (such as RIN) must be configured and connected to the devices ECB201 for
each signal that is to be interfaced to the Foxboro Evo system.
2. DVNAME contains the channel number CH1-CH8 of the associated device.
Figure 5-4. Typical Block Interconnections for FBM214/214b with 4-20 mA Input Devices
53
B0400FF Rev M
ECB200
NAME
DEV_ID
HART Input Device
Channel #1
FBM247_01
FBM001
ECB201
NAME
PT_0101
DEV_ID
DV0102
PARENT
:FBM247_01
DVOPTS
HART (4)
DVNAME
CH1 I LPWR (3)
NAME
DEV_ID
PARENT
DVOPTS
DVNAME
ECB201
FT_0102
DV0102
:FBM247_01
4-20 (4)
CH2 I EPWR (3)
ECB201
NAME
DI_0103
DEV_ID
DV0103
PARENT
:FBM247_01
DVOPTS
VOLT (4)
DVNAME
CH3 I (3)
ECB201
NAME
VP_0108
DEV_ID
DV0108
PARENT
:FBM247_01
DVOPTS
NOFAIL (4)
DVNAME
CH8 O LPWR (3)
RIN Block
NAME
IOM_ID
PNT_NO
SCI
PRESS_01
PT_0101
CURRENT (2)
3 or 0 (2)
RIN Block
NAME
IOM_ID
PNT_NO
SCI
FLOW_02
FT_0102
CURRENT (2)
1 or 3
BIN Block
NAME
IOM_ID
PNT_NO
DIN_03
DI_0103
DI 20 80 (2)
ROUT Block
NAME
IOM_ID
PNT_NO
SCO
VALVE_08
VP_0108
CURRENT (2)
3
NOTES:
1. A DCI block (such as RIN, BIN or ROUT) must be configured to the devices ECB201 for
each HART, current or voltage signal or value that is to be interfaced to the Foxboro Evo system.
2. DCI block parameters defined in PNT_NO must be configured to contain a point address
which indicates the I/O operation to be performed. Refer to Table 5-8 through Table 5-13 beginning on page 71 for details.
3. DVNAME contains the channel number (CH1-CH8), Input or Output (I or O) and External or
Loop Power (EPWR or LPWR) options. Refer to page 69 for details.
4. DVOPTS may be HART, NOFAIL or NOALARM for HART devices or 4-20 for ordinary current I/O or VOLT for voltage inputs. Refer to Table 5-7 on page 70 for details.
Figure 5-5. Typical Block Interconnections for FBM247 with Various I/O Devices
54
B0400FF Rev M
Table 5-2 lists key parameters, which either specify the linkages between ECBs and DCI blocks or
contain information relating to the transfer of I/O values.
Table 5-2. Key Parameters
ECB or DCI Block
Parameter
Usage
Typical Syntax
ECB110
NAME
A user-configured name used for communications between the control station and DIN rail
baseplate(s).
:SLOT00
55
B0400FF Rev M
Parameter
Usage
Typical Syntax
ECB200/ECB202
NAME
DEV_ID
User-configured letterbug of the FBM. It is copied into the DEV_ID parameter of each DCI I/O
block connected to this ECB200/ECB202.
FSDLAY
1000 ms
DESCRP
1 to 32 chars
PERIOD
PHASE
HWTYPE
214
SWTYPE
214
SYSOPT
SYSCFG
1000ms
56
B0400FF Rev M
Parameter
Usage
Typical Syntax
ECB201
NAME
PT_100
PARENT
DVOPTS1
HART
DVNAME
CH1
DESCRP
1 to 32 chars
PERIOD
PHASE
HWTYPE
214
SWTYPE
214
IOMID
CP6SG5_ECB:PT_1
00
57
B0400FF Rev M
Parameter
Usage
PNT_NO
These parameters (PNT_NO, RI1_PT, RI2_PT, and RI3_PT) must contain a specific point address specifying the required data I/O operation.
(See Table 5-4 on page 60.)
For the FBM247, configure IIN as described in Configuring IIN Block for
HART Integer Digital Variables and Device Status Bits for the FBM247
on page 73, configure RIN and ROUT as described in Configuring I/O
Blocks (RIN, BIN, ROUT and BOUT) for the FBM247 Hardware Channels on page 71, and configure STRIN as described in Configuring
STRIN Block for HART String Input Variables for the FBM247 on
page 74.
[Varies]
(For the FBM247 only) Configure these blocks as described in Configuring I/O Blocks (RIN, BIN, ROUT and BOUT) for the FBM247 Hardware
Channels on page 71 and Configuring PAKIN Block for HART Packed
Boolean Variables for the FBM247 on page 75.
1.
Typical Syntax
At the present time, for the HART FBMs (not FBM247), there are five legitimate values for
DVOPTS in the ECB201.
If the device is a HART device, one of the following four settings should be used, depending on the
desired OOS and system alarm handling. With any of these settings the ECB201 block will collect
HART status and diagnostic information which may be used for asset management purposes. With
all four settings, the 4-20 mA analog current signal is available for fast control by setting the
PNT_NO parameter of the DCI block such as an RIN or ROUT to the point address of
CURRENT. See Table 5-4 for valid DCI block point address settings.
HART Enables HART communication to the device and if the communication is interrupted for
more than a few seconds, all points are marked OOS (Out of Service).
NOFAIL Enables HART communication; however, the current input or output will always be
OK regardless of the HART communication failure.
NOALARM The same as NOFAIL with the exception that system alarms will also be suppressed
for HART communication failures.
OCD (Open Circuit Detection) Enables HART communication similar to NOFAIL but will
mark the current input or output as OOS after 10 seconds of continuous HART communication
failure.
IOBAD - Enables HART communication to the device and reads additional status information of
the device from HART Command 48. For information about configuring the IOBAD option, refer
to Configuring IOBAD Options on page 59.
If the device or I/O signal source is not a HART device, the following setting should be used:
4-20 - Disables all HART communication on that channel. When configuring the DCI block such
as RIN, the only valid point address is the CURRENT parameter. This setting is not recommended
for HART devices as the ECB201 block will not collect the HART device status and diagnostic
information useful in asset management of the device.
If the DVOPTS parameter is left BLANK, the behavior will default to be the same as the HART setting.
For FBM247, configure DVOPTS as described in Configuring Device ECB (ECB201) for
FBM247 on page 69.
58
B0400FF Rev M
NOTE
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 additional information, refer to Figure 4-2 on page 14 and DIN Rail
Mounted Subsystem Users Guide (B0400FA).
MM represents the hexadecimal bit mask to identify the valid IOBAD condition.
Valid range of MM is 1<= MM <= FF.
The IOBAD options have a minimum of one field and a maximum of five fields in the form of
N.MM where N is the byte number and MM is a hex bit mask. If more than one N is greater
than 9, the option can have only four fields due to the 32 character limit in the DVOPTS string.
The bit mask specifies bits that are to be used from command 48 to generate IOBAD in the control blocks, independent of the setting of the Device Malfunction bit. This allows flexibility to
consider other status bits that are unrelated to the Device Malfunction bit, thereby decoupling the
two functions entirely.
Example:
IOBAD 3.FF 4.FD 1.01 25.18
3. FF field monitors all bits in the 3rd byte and generates IOBAD if any one bit of the
3rd byte is active.
4.FD field monitors all bits except the 2nd bit in the 4th byte and generates IOBAD
if any one of that bit is active.
1.01 field monitors only the first bit in the 1st byte and generates IOBAD if that bit is
active.
25.18 field monitors only the 4th and 5th bits in the 25th byte and generates IOBAD
if any one of those bits is active.
You can configure the 3rd byte and then the 1st byte as shown in the example. The HART
check box is selected in FBM247 SYSCFG when the IOBAD options are configured. For
details, refer to Configuring Blocks for FBM247 on page 66.
B0400FF Rev M
I/O source, the specific data I/O operation (command) to be performed (see Table 5-4). The
HART FBMs and the FBM247 support the HART universal commands. For specific commands
supported by HART devices or the analog I/O source, refer to literature from the device
manufacturer.
! CAUTION
Make sure to know what dynamic variables your HART devices or other analog I/O
source support. Only with this knowledge can you know when a seemingly good
value is invalid because it is associated with an unused variable.
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.
Table 5-3. DCI Block Parameters Requiring a Point Address
DCI Block
RIN
ROUT
IIN
STRIN
Connection Parameter(s)
to be Configured
PNT_NO
PNT_NO
PNT_NO
PNT_NO
Point Address*
UID
CURRENT
CURRENT
PV
PVUNITS
PVCURR
PVPCTRNG
SV
60
Description
Unique Identifier
Current (analog input current value)
Current (analog output current value)
Primary Variable
Primary Variable Units
Primary Variable Current
Primary Variable Percent of Range
Secondary Variable
DCI Block
Signal
Condition
Index
Device
Type
STRIN
RIN
ROUT
RIN
STRIN
RIN
RIN
RIN
---SCI = 1-10
SCO = 1-5
SCI = 0
---SCI = 0
SCI = 0
SCI = 0
Input
Input
Output
Input
Input
Input
Input
Input
B0400FF Rev M
Point Address*
SVUNITS
TV
TVUNITS
FV
FVUNITS
MSG
TAG
DESC
DATE
PVSENSER
PVSENSUP
PVSENSLOW
PVSENSPAN
PVSENUNITS
PVALMSEL
PVXFRFUN
PVUPRNG
PVLOWRNG
PVDAMP
PVRNGUNITS
WP
PLDC
FINASSYNUM
Description
Secondary Variable Units
Tertiary Variable
Tertiary Variable Units
Fourth Variable
Fourth Variable Units
Message
Tag
Descriptor
Date
Primary Variable Sensor Serial Number
Primary Variable Sensor Upper Limit
Value
Primary Variable Sensor Lower Limit
Value
Primary Variable Sensor Minimum
Span Value
Primary Variable Sensor Limits and
Minimum Span Units
Primary Variable Alarm Select Code
Primary Variable Transfer Function
Code
Primary Variable Upper Range Value
Primary Variable Lower Range Value
Primary Variable Damping Value
Primary Variable Upper and Lower
Range Values Units
Write Protect Code
Private Label Distributor Code
Final Assembly Number
DCI Block
Signal
Condition
Index
Device
Type
STRIN
RIN
STRIN
RIN
STRIN
STRIN
STRIN
STRIN
STRIN
IIN
RIN
---SCI = 0
---SCI = 0
------------------SCI = 0
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
RIN
SCI = 0
Input
RIN
SCI = 0
Input
STRIN
----
Input
IIN
IIN
-------
Input
Input
RIN
RIN
RIN
STRIN
SCI = 0
SCI = 0
SCI = 0
----
Input
Input
Input
Input
IIN
IIN
IIN
----------
Input
Input
Input
* For standard 4 to 20 mA analog I/O devices (not HART devices), use point address CURRENT.
61
B0400FF Rev M
converted to HART format after the inverse scaling and/or inverse signal conditioning has been
applied.
In ROUT blocks, the readback value is converted to Foxboro Evo format before applying signal
conditioning and/or linear scaling to the data. The output value to be written to the FBM is converted to HART format after the inverse scaling and/or inverse signal conditioning has been
applied.
Table 5-5. Data Type Conversions
DCI Block
Parameters
Foxboro Evo
Data Type
RIN
RIN
single-precision
float
ROUT
OUT
single-precision
float
IIN
IIN
32-bit long
integer
NOTE
All other HART data types not specified in this table are converted by the HART
FBM to/from the appropriate Foxboro Evo data type.
NOTE
Be aware that the fastest allowed ECB period for the HART FBMs and FBM247 is
100 milliseconds (PERIOD = 0). However, it is recommended that you refer to the
Sizing Guidelines and Excel Workbook appropriate for your Control Processor to
determine the optimal BPC for this ECB in order to prevent overloading.
62
B0400FF Rev M
The only supported control configurators for the HART-capable FBM247 are the
Foxboro Control Software editors and the ICC.
To create and edit an ECB using the Foxboro Evo Control Editors Block Configurator, refer to
the section Configuring Blocks in Block Configurator User's Guide (B0750AH).
To create and edit an ECB using the ICC, refer to the section View Blocks/ECBs in this Compound and Insert New Block in Integrated Control Configurator (B0193AV).
To create and edit an ECB using the I/A Series Configuration Component (IACC) (for any
FBMs other than the FBM247), refer to the section Control Blocks in I/A Series Configuration
Component (IACC) Users Guide (B0700FE).
To create and edit an ECB using FoxCAE software (for any FBMs other than the FBM247), refer
to Computer Aided Engineering for I/A Series Control Station Databases, FoxCAE Version 4.0
(B0193MR).
For the ECB200 and ECB202 parameter definitions, refer to Integrated Control Block Descriptions
(B0193AX).
For the FBM247, also refer to Configuring Blocks for FBM247 on page 66.
63
B0400FF Rev M
Figure 5-6. System Manager - Connections Tab - For FCP270 Connected to HART FBMs
The only supported control configurators for the HART-capable FBM247 are the
Foxboro Control Software editors and the ICC.
To create and edit the slave device ECBs (ECB201s) using the Control editors Block Configurator, refer to the section Configuring Blocks in Block Configurator User's Guide (B0750AH).
To create and edit the slave device ECBs (ECB201s) using the ICC, refer to the sections View
Blocks/ECBs in this Compound and Insert New Block in Integrated Control Configurator
(B0193AV).
To create and edit an ECB using the I/A Series Configuration Component (IACC) (for any
FBMs other than the FBM247), refer to the section Control Blocks in I/A Series Configuration
Component (IACC) Users Guide (B0700FE).
64
B0400FF Rev M
To create and edit an ECB using FoxCAE software (for any FBMs other than the FBM247), refer
to Computer Aided Engineering for I/A Series Control Station Databases, FoxCAE Version 4.0
(B0193MR).
For the ECB201 parameter definitions, refer to Integrated Control Block Descriptions (B0193AX).
For the FBM247, also refer to Configuring Blocks for FBM247 on page 66.
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.
Figure 5-7. System Manager - General Tab (FBM Equipment Status Display) - For HART FBM
65
B0400FF Rev M
The only supported control configurators for the FBM247 are the Foxboro Evo
Control Editors and the ICC.
Table 5-6. ECB200 SYSOPT Parameter - Analog and Pulse Input Integration Period
SYSOPT Value
1
66
B0400FF Rev M
Table 5-6. ECB200 SYSOPT Parameter - Analog and Pulse Input Integration Period (Continued)
SYSOPT Value
2
3
4
Any other value
250 milliseconds
500 milliseconds
1 second
500 milliseconds
The SYSCFG parameter data is used as a bit mapped parameter to indicate that a channel is preconfigured as a HART device, as an input or an output, and if loop power is required. This
enables the FBM247 to obtain a live list for the selected channels. SYSCFG is an unsigned long
(32-bit) which should be entered as a hex value. Each of the four bytes has a function in defining
the I/O channel type, with channel 1 as the least significant bit (LSB) and channel 8 as the most
significant bit (MSB), as shown in Figure 5-8 below:
0
B32
B31
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9
B30
B29
B28
B27
B26
B25
B24
B23
B22
B21
B20
B19
B18
B17
B16
B15
B14
B13
B12
B11
B10
B9
B8
B7
B6
B5
B4
B3
B2
B1
NOTE
In Figure 5-8, the output (Byte 2) and loop power (Byte 0) configuration bits are
only valid when HART communications have been enabled.
The purpose of each of the bytes is as follows:
1. Byte 3 (most significant) and byte 1 must be identical as they indicate which channels
are to be preconfigured by the SYSCFG parameter. As a security feature, the entire
configuration will be ignored if these two bytes do not match exactly. When a bit is set
in these two bytes, the corresponding channel is enabled for the HART live list
according to the information in other two bytes. If the bit is clear, the channel remains
in an unpowered state.
2. Byte 2 indicates that the channel is an output device when the bit is set. The channel
is an input device when the bit is clear.
3. Byte 0 (least significant) indicates that the channel uses loop (FBM) power when the
bit is set, or uses an external power source when the bit is clear. Note that most output
devices require loop power to provide the current output, whereas input devices usually do use loop power but some devices either provide their own power or are powered from a separate field power supply.
For example, the value 0x83018303 indicates a loop powered HART output device on channel 1,
a loop powered HART input device on channel 2 and an externally powered HART input device
on channel 8 with channels 3 through 7 not configured.
67
B0400FF Rev M
NOTE
1. The default value for SYSCFG is 1000 (0x000003E8) which does not configure
any of the channels since that value does not meet the security requirements outlined in the first item above. Therefore, if the user takes no explicit action to configure this parameter, the channels will not be configured until the ECB201 and I/O
block configurations are downloaded to the FBM.
2. Channels that have been preconfigured in SYSCFG require that the ECB201 and
I/O block configurations are appropriate for that channel. If the ECB201 or I/O
block configuration is incompatible with the preconfigured value, the configuration
is rejected by the FBM. Preconfigured channels must be analog current input or
output and powered as defined in SYSCFG.
3. Channels that have not been preconfigured remain in a safe powered-off state
until the ECB201 and I/O block configurations have been downloaded and validated by the FBM.
To configure the SYSCFG parameter in the Control Softwares Block Configurator, you will need
to invoke a grid control from the V button, beside the System Configuration (HART
Options) field in the ECBs -> FBM tab for the ECB200, as shown in Figure 5-9.
Figure 5-9. Configuring SYSCFG in the Block Configurator From Grid Control
The grid control shown above allows you to configure channels for up to eight HART devices.
SYSCFG will not be changed if you do not make any changes via this grid control.
In order to configure a channel, the checkbox in the HART column of that channel must be
checked (see Figure 5-9 above). If the checkbox in the HART column for a channel is checked,
the Input/Output and Power columns are enabled. If the checkbox in the HART column for a
channel is unchecked, the Input/Output and Power columns are disabled.
When the SYSCFG parameter has a value of 1000 (or any invalid values), the grid control will not
have any selections to configure.
Refer to the Block Configurator Users Guide (B0750AH) for additional details on using this editor.
68
B0400FF Rev M
During normal system operation, you can view the current configuration of the SYSCFG parameter for an FBM247 via the FBM247s ECB200 faceplate (detail view) in the Foxboro Evo Control HMI. See Figure 7-6 ECB200 Faceplates for FBM247 Devices - Configuration Views on
page 124.
The following ECB200 parameters are not used with FBM247:
PORTEX
WDTMR
FILEID
SFILID.
HWTYPE = 247
SWTYPE = 247
DVNAME = CHn t [LPWR]:
Where
n is 1 to 8
t is I or O representing input or output.
[LPWR] selects the loop power option for current I/O.
If configured as EPWR (or omitted), the external power option is selected for current
I/O signal. This identifies the I/O channel and power option used by the current I/O
device connected to the channel.
To configure the DVNAME parameter in the Control Softwares Block Configurator,
you will need to invoke a grid control from the V button, beside the Device Name
(Channel Configuration) field in the ECBs -> FBM tab for the ECB201 derived
from $DEV_ECB201 template, as shown in Figure 5-10.
Figure 5-10. Configuring DVNAME in the Block Configurator From Grid Control
The grid control allows you to configure Input/Output and Power values for the
DVNAME parameter. You cannot configure the Channel value in the grid control.
To set the Channel value for ECB201 device, drag and drop the device on FBM247
channel in Network View as shown in Figure 5-11.
69
B0400FF Rev M
Refer to the Block Configurator Users Guide (B0750AH) for additional details on
using this editor.
DVOPTS = Device Options; see Table 5-7 below.
DVOPTS sets up the hardware interface for the appropriate signal types to be connected to the I/O channel. The actual signal type is defined by the I/O block type and
connection string.
The mode VOLT sets the I/O channel into voltage input mode with no HART
communication. All the other modes set the channel into the current I/O mode and
specify if HART communication is enabled or not.
Table 5-7. ECB201 DVOPTS Parameter - Device Options
DVOPTS Mode
VOLT
4-20
NOFAIL
NOALARM
POWER OFF
HART
IOBAD
Device Option
Analog voltage input mode; no HART communication
Analog current only mode, input or output; no HART communication
Enables HART communication; however, the current input or output will
always be OK regardless of the HART communication failure
The same as NOFAIL with the exception that system alarms also will be
suppressed for any HART communication failures
Disconnects the I/O channel from the device for troubleshooting or driving
the device with an external source. It is a software equivalent to a quick
disconnect.
Enables HART communication to the device and if the communication is
interrupted for more than about five seconds; all points are marked out-ofservice (OOS)
Enables HART communication to the device and reads additional status
information of the device from HART Command 48. For information about
configuring the IOBAD option, refer to Configuring IOBAD Options on
page 59.
Note that certain combinations of DVOPTS and PNT_NO configurations of the I/O blocks are
invalid. For example, when DVOPTS = VOLT, the RIN blocks parameter PNT_NO can only be
10V, 5V, PULSE, FREQ, ACCEL or JERK to be valid.
70
B0400FF Rev M
The Mode column in Table 5-8 in the next subsection shows if the variable is valid for current (I),
voltage (V) or either (I/V) mode. Output block variables are only available in current mode. Conflicts must be resolved before the I/O block can come on-line.
Also, the DDIAG1 parameter of the ECB201 allows you to read the current HART device status
- a single byte returned with each HART message response to the FBM247. The general details of
this parameter are discussed in ECB201 Extended Status Support on page 91; however, the specific use of this parameter with FBM247 and HART devices is discussed in Configuring IIN
Block for HART Integer Digital Variables and Device Status Bits for the FBM247 on page 73.
During normal system operation, you can view the current configuration of the DDIAG1 parameter for an FBM247 via the FBM247 devices ECB201 faceplate (detail view) in the Foxboro Evo
Control HMI. See Figure 7-7 ECB201 Faceplates for FBM247s Devices on page 126.
Finally, the following ECB201 parameters are not used with FBM247:
PORTNO
FILEID
DVADDR
DVTYPE
SFILID
MANFTR
VERNUM
ERROPT.
Configuring I/O Blocks (RIN, BIN, ROUT and BOUT) for the FBM247
Hardware Channels
The PNT_NO parameter in the RIN, BIN, ROUT and BOUT blocks configures an FBM247
hardware I/O channel along with the signal type. One (and only one) of the blocks listed in
Table 5-8 below may be configured for each FBM247 I/O channel with one exception; if any one
of the pulse channel inputs marked with (*) in the Block column are configured, the other three
inputs may also be configured since they are all obtained from the pulse counter channel data.
HART communication is only available when the PNT_NO is set to CURRENT or
CURRENT+LFD.
Table 5-8. RIN, BIN, ROUT, and BOUT PNT_NO Parameter Settings
PNT_NO
CURRENT
CURRENT+LFD
10V
5V
PULSE
FREQ
Block
RIN
Description
Mode
SCI/SCO
1 to 10
1 to 10
V
V
I/V
I/V
1 to 10
1 to 10
0
8
71
B0400FF Rev M
Table 5-8. RIN, BIN, ROUT, and BOUT PNT_NO Parameter Settings (Continued)
PNT_NO
ACCEL
RIN (*)
JERK
DI 0t 1t
SOE
NAMUR
CURRENT
CURRENT+LFD
CURRENT
CURRENT+LFD
DO
PO nnn
1.
Block
Description
Mode
SCI/SCO
I/V
I/V
I/V
8
n/a
I/V
n/a
n/a
3 or 5
3 or 5
1 to 5
1 to 5
I
I
n/a
n/a
Life Fault Detection is a feature in which the FBM monitors for specific conditions which might
indicate issues with the I/O signal, such as the analog current input is below or above specific levels,
or the analog output current loop is open.
For the block parameter definitions, refer to Integrated Control Block Descriptions (B0193AX).
NOTE
The variables listed in the following two subsections are not available if the ECB201
DVOPTS parameter is in either the VOLT or 4-20 modes.
72
B0400FF Rev M
Table 5-9. RIN PNT_NO Parameter Settings for HART Floating-Point Digital Variables
PNT_NO
PV
PVCURR
PVPCTRNG
SV
TV
FV
PVSENSUP
PVSENSLOW
PVSENSPAN
PVUPRNG
PVLOWRNG
PVDAMP
Description
SCI
0
0
0
0
0
0
0
0
0
0
0
0
Configuring IIN Block for HART Integer Digital Variables and Device
Status Bits for the FBM247
The HART integer digital variables are accessed by using IIN blocks with the PNT_NO connection strings in Table 5-10 below.
Table 5-10. IIN PNT_NO Parameter Settings for HART Integer Digital Variables
PNT_NO
PVSENSER
PVALMSEL
PVXFRFUN
WP
PLDC
FINASSYNUM
DEVSTS
Description
Primary Variable Sensor Serial Number
Primary Variable Alarm Select Code
Primary Variable Transfer Function Code
Write Protect Code
Private Label Distributor Code
Final Assembly Number
HART device status (see below)
The HART device status (DEVSTS) is a single byte returned with each HART message response
to the FBM247. (This value is also obtainable through the DDIAG1 parameter of the ECB201.)
These bits are shown in the System Management Equipment Information display for each HART
device and are universally defined for all HART devices. The I/O block state is also changed based
upon the value of certain bits as shown in Table 5-11:
Table 5-11. HART Device Status Bits
Bit
0 (LSB)
Description
PV Out-of-Limits
73
B0400FF Rev M
Bit
1
2
3
4
5
6
7 (MSB)
Description
Non-PV Out-of-Limits
PV Analog Output Saturated
PV Analog Output Fixed
More Status Available
Cold Start
Configuration Changed
Field Device Malfunction
Normal
Error
Track
Normal
Normal
Normal
BAD
If the HART device reports a Field Device Malfunction in the HART device status (bit 7), this
causes the following alarms to occur regardless of the setting of the DVOPTS parameter in
ECB201:
All I/O blocks connected to that HART device show BAD I/O.
The device shows a Warning Condition or Device Failure in the applicable system
management application.
None of the other bits cause a system alarm.
Bit 4 is set (More Status Available) when the HART device has additional device-specific
statuses to report. When this bit is set, the FBM247 retrieves up to 25 additional status bytes
from the HART device; these bytes contain the additional status information. Refer to the
documentation provided by the original manufacturer of the HART device for a description of
the statuses indicated by these bits. These status bytes can be displayed in a STRIN block and in
multiple PAKIN blocks, as discussed in next two subsections.
Configuring STRIN Block for HART String Input Variables for the FBM247
As discussed above, the device-specific status bytes returned by the HART device can be displayed
via the STRIN block.
HART string input variables, as well as the input signal type, can be configured via a STRIN
block with the PNT_NO connection strings in Table 5-12 below.
Table 5-12. STRIN PNT_NO Parameter Settings for HART String Input Variables
PNT_NO
UID
PVUNITS
SVUNITS
TVUNITS
FVUNITS
MSG
TAG
DESC
DATE
PVSENUNITS
74
Description
Unique Identifier
Primary Variable Units
Secondary Variable Units
Tertiary Variable Units
Fourth Variable Units
Message
Tag
Descriptor
Date
Primary Variable Sensor Limits and Minimum Span Units
B0400FF Rev M
Table 5-12. STRIN PNT_NO Parameter Settings for HART String Input Variables (Continued)
PNT_NO
Description
PVRNGUNITS
STATUS
You can use the STRIN block to view HART device-specific status information as described in
the previous subsection. This status information can be retrieved in conjunction with the PAKIN
block, as discussed below.
Configuring PAKIN Block for HART Packed Boolean Variables for the FBM247
As discussed above, the device-specific status bytes returned by the HART device can be displayed
via multiple PAKIN blocks.
PAKIN blocks are used to retrieve up to four individual HART device status bytes which can be
displayed via a STRIN block configured with the STATUS parameter. This configuration allows
an operator to connect to and monitor the states of specific bits and bytes in the additional status
information provided by the response to HART command 48, discussed above. While 25 bytes
are made available by these block connections, not all devices return that many bytes. Bytes that
are not returned by the device are always set to zero (0), whereas the STATUS parameter setting in
Table 5-12 above only displays the number of bytes that were actually returned from the HART
device.
The STRIN block displays the bytes in ascending order like 01020304 whereas the PAKIN block
displays the bytes in descending order like 04030201. This means that the most significant bit
(MSB) of byte 04 is displayed as bit 1 and the least significant bit (LSB) of byte 01 is displayed as
bit 32. If the STRIN value is 01020304 this would show bits 6, 15, 16, 23 and 32 as ON and all
of the other bits OFF in the PAKIN block.
The PKIOPT parameter in the PAKIN block must be changed from the default value (1) to 3
to display the bits and bytes in the order described above. (Leaving this parameter set to 1 causes
the PAKIN block to swap the order of the bits and bytes which would make bit 1 display the least
significant bit of byte 01 and bit 32 would display the most significant bit of byte 04.)
A Boolean connection can be made to any individual bit by using
COMPOUND:BLOCK.PAKCIN.Bn where n is the bit number from 1 to 32.
For example, the connection can be made to a CIN block to provide a state alarm message when
the state of the corresponding bit changes.
Set the PKINGP parameter as shown in Table 5-13 to extract the appropriate bytes from the
HART devices response to the request for status bytes from the FBM247.
Table 5-13. PAKIN PKINGP Parameter Settings for HART Packed Boolean Block
Configuration
PKINGP
STATUS1
STATUS2
STATUS3
STATUS4
STATUS5
Description
Bytes 4 to 1 (4=MSB) of HART device response
Bytes 8 to 5 (8=MSB) of HART device response
Bytes 12 to 9 (12=MSB) of HART device response
Bytes 16 to 13 (16=MSB) of HART device response
Bytes 20 to 17 (20=MSB) of HART device response
75
B0400FF Rev M
Table 5-13. PAKIN PKINGP Parameter Settings for HART Packed Boolean Block
Configuration (Continued)
PKINGP
STATUS6
STATUS7
76
Description
Bytes 24 to 21 (24=MSB) of HART device response
Byte 25 (LSB) of HART HART device response
B0400FF Rev M
This section applies to all HART FBMs and the HART-capable FBM247.
In a control strategy, the DCI control blocks interface the Foxboro Evo system to the HART slave
devices. The DCI blocks used with HART devices are listed in Table 5-1.
The DCI blocks are created in the same general manner as the ECBs. For detailed information,
refer to Integrated Control Configurator (B0193AV). For parameter definitions, refer to 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. Refer to Point Addresses for HART and Analog I/O Signals on page 59 for detailed
information.
In conjunction with creating and editing DCI blocks, you will need to configure the various
blocks and compounds required for the desired control scheme. Refer to the following documents
to perform these operations:
DIN Rail Mounted Subsystem Users Guide (B0400FA)
Control Processor 270 (CP270) and Field Control Processor 280 (CP280) Integrated
Control Software Concepts (B0700AG)
Integrated Control Block Descriptions (B0193AX).
NOTE
The only supported control configurators for the HART-capable FBM247 are the
Foxboro Control Software editors and the ICC.
To create and edit a DCI block in an existing compound using the Control Softwares Block Configurator, refer to the section Configuring Blocks in Block Configurator User's Guide
(B0750AH).
To create and edit a DCI block in an existing compound using the ICC, refer to the sections
View Blocks/ECBs in this Compound and Insert New Block in Integrated Control Configurator (B0193AV).
To create and edit a DCI block using the I/A Series Configuration Component (IACC) (for any
FBMs other than the FBM247), refer to the section Control Blocks in I/A Series Configuration
Component (IACC) Users Guide (B0700FE).
To create and edit a DCI block using FoxCAE software (for any FBMs other than the FBM247),
refer to 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.
77
B0400FF Rev M
To verify operation of the DCI blocks and the HART device data using the block detail
displays:
1. Access the appropriate application:
For the Foxboro Console Software Block Select application, refer to the Control
HMI Application User's Guide (B0750AQ) for details.
For the FoxSelect compound/block overview utility, refer to Process Operations and
Displays (B0700BN) for details.
2. Access the block detail display for each DCI block created, and confirm its data.
The only supported control configurators for the HART-capable FBM247 are the
Foxboro Control Software editors and the ICC.
To create and configure a RIN block to read pressure measurement using the Control Softwares
Block Configurator, refer to the section Configuring Blocks in Block Configurator User's Guide
(B0750AH).
To create and configure a RIN block to read pressure measurement using the ICC, refer to the
sections View Blocks/ECBs in this Compound and Insert New Block in Integrated Control
Configurator (B0193AV).
To create and edit a RIN block using the I/A Series Configuration Component (IACC) (for any
FBMs other than the FBM247), refer to the section Control Blocks in I/A Series Configuration
Component (IACC) Users Guide (B0700FE).
To create and edit a RIN block using FoxCAE (for any FBMs other than the FBM247), refer to
Computer Aided Engineering for I/A Series Control Station Databases, FoxCAE Version 4.0
(B0193MR).
For parameter definitions for the RIN block, refer to 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.
78
B0400FF Rev M
79
B0400FF Rev M
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 may 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 may be used in conjunction with the
Auto/Manual mode. The two features may 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 the Foxboro Evo system, it is
stored in a request location that is part of the output value record in the block. (In Foxboro Evo
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
80
B0400FF Rev M
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
or FBM247), 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 the following 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 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 blocks fail-safe value parameter FSOUT.
The ROUT block output initialization is done whether or not 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 the following cases:
When the DCI block initializes
When the DCI block mode changes from Manual to Auto mode
81
B0400FF Rev M
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, the following 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 communications 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, the following 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 input/measurement error.
Set/clear fail-safe when SETFS input is set/cleared.
Assert fail-safe if 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/or 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 may 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 communications 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.
82
B0400FF Rev M
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 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 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 Failsafe 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.
Refer to the DCI block descriptions in Integrated Control Block Descriptions (B0193AX) for additional details.
Meaning
FBM to HART device communication failure, HART device disabled, device/point connection is unresolved, compound is off, or
control station to FBM communication failure
Transmitter/sensor failure, valve/actuator failure, I/O diagnostic
failure, device failure, or control station to FBM communication
failure
Set when the PV is out of limits or the analog output is saturated
Set when the PV is past its high limit.
Set when the PV is past its low limit.
Fail-safe has been asserted by the HART FBM.
83
B0400FF Rev M
Parent
ECB200/ECB202
(HART FBM)
Child ECB201
(HART device)
Child ECB201
(HART device)
PARENT
RIN Block
IOM_ID
(1) PNT_NO
MEAS
RIN
PARENT
PIDA Block
MEALM
Block (2)
MEAS
SPT
OUT
BCALCI
MEAS
RIN Block
IOM_ID
(1) PNT_NO
MEAS
RIN
PIDA Block
MEALM
Block (2)
MEAS
MEAS
RSP
BCALCO
OUT
BCALCI
SUP_IN
SUPBCP
Notes:
(1) PNT_NO = Point address of HART device
(2) MEALM blocks are used to perform BAD alarming.
Figure 5-12. Simple Cascade Configuration
84
ROUT Block
IOM_ID
PNT_NO (1)
MEAS OUT
BCALCO
MEALM
Block (2)
MEAS
B0400FF Rev M
Parent
ECB200/ECB202
(HART FBM)
Child ECB201
(HART device)
Child ECB201
(HART device)
PARENT
RIN Block
IOM_ID
(1) PNT_NO
MEAS
RIN
PIDA Block
MEALM
Block (2)
MEAS
RIN Block
IOM_ID
(1) PNT_NO
MEAS
RIN
PARENT
MEAS
SPT
OUT
BCALCI
PIDA Block
MEALM
Block (2)
MEAS
MEAS
RSP
BCALCO
OUT
BCALCI
SUP_IN
SUPBCO
ROUT Block
IOM_ID
PNT_NO (1)
MEAS OUT
BCALCO
MEALM
Block (2)
MEAS
Supervisory Control
Application
(for example,
Connoisseur MPC)
Solaris/Windows NT
Workstation
Notes:
(1)
(2)
85
B0400FF Rev M
86
The only system management package that supports the HART-capable FBM247 is
the System Manager.
87
B0400FF Rev M
SWTYPE
88
B0400FF Rev M
SWTYPE
89
B0400FF Rev M
SWTYPE
90
B0400FF Rev M
The DDIAG1 (Device Diagnostics #1) parameter of ECB201 is a 32-bit packed Boolean output
which reports additional issues using Byte 0, Bit 4 (More status available for HART devices
only).
FBM214/214b/215/216/216b/218/247 monitors the state of this status bit from the device, and
when this bit changes from 0 to 1, the FBM issues the HART Common Practice Command 48 to
the device to read the additional status. The FBM stores the returned data as a 25-byte additional
status value where it can be read by the control processor. While this status bit remains at 1, the
FBM will read this additional status data from the device approximately every ten seconds.
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 read until the status bit transitions to 1 again.
The 25-byte additional status value is accessible with standard DCI input blocks. All twentyfive 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 below
Bytes
4-1
8-5
12 - 9
16 - 13
20 - 17
24 - 21
25
Configure PKINGP
STATUS1
STATUS2
STATUS3
STATUS4
STATUS5
STATUS6
STATUS7
Example
04 03 02 01
08 07 06 05
12 11 10 09
16 15 14 13
20 19 18 17
24 23 22 21
00 00 00 25
Be aware of the following with regards to the 25-byte additional status value:
Not all devices provide additional status. It is assumed that a device that does not support the Common Practice Command 48 will never set the More status available bit
in ECB201.
A device that does provide additional status may not provide a full 25 bytes of additional status. For this reason, before the FBM issues the first Command 48 following
transition of the More status available bit from 0 to 1, the FBM clears (sets to 0) the
entire 25-byte storage area so that any unused bytes will not contain misleading ones
(1s). The STRIN block will only display the number of bytes actually received from
the device.
91
B0400FF Rev M
The PKIOPT parameter of the PAKIN blocks must be set to 3 to avoid swapping of
the bits and bytes. The default setting of this parameter is 1.
The PAKIN block detail display shows the PAKCIN parameter as in the examples
above, but the individual bits are displayed as most significant bit=1 (upper left) and
least significant bit=32 (lower right). This means that the top line displays the bits in
byte 4 and the bottom line displays the bits in byte 1.
Refer to Integrated Control Block Descriptions (B0193AX) for definitions of the additional bits in
the DDIAG1 parameter of ECB201.
Also, for the FBM247, refer to Configuring IIN Block for HART Integer Digital Variables and
Device Status Bits for the FBM247 on page 73 for additional details on reading HART device
status using the IIN, STRIN and PAKIN blocks with the FBM247.
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
warning message is sent to the SMON log and the System key on FoxView software flashes red. In
addition, all I/O blocks connected to a device with this bit set will indicate 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 will be yellow as a
warning indicator.
92
7. Maintenance
This chapter provides maintenance information for the HART FBMs and the HART-capable
FBM247.
NOTE
! WARNING
To prevent explosion, install and remove cables, wiring, modules and other replaceable components only when the area is known to be nonhazardous.
Overview
The general Foxboro Evo system management philosophy applies to the HART FBMs incorporated into the Foxboro Evo system. 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 the following system and display management packages:
System Manager - discussed in System Manager (B0750AP)
NOTE
The only system management package that supports the HART-capable FBM247 is
the System Manager.
Operating Status
The operating status of the HART FBMs and the HART-capable FBM247 is reported by the
Foxboro Evo system using on-screen and printed messages. Refer to the following documents for
information on the reporting of equipment operating status and errors:
B0400FF Rev M
7. Maintenance
Figure 7-1. System Manager - General Tab (Equipment Information Display) for HART Device
94
7. Maintenance
B0400FF Rev M
In the Foxboro Evo system, 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 the following displays:
A Fieldbus1 level display (PIO Network), which shows the control station, FCM(s),
and any other Fieldbus devices
A module Fieldbus1 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.
For detailed information on the first three items above (Fieldbus level display, module Fieldbus
level display, and I/O device display), refer to System Management Displays (B0193JC).
1. The
term Fieldbus used here refers to the Foxboro Evo 10 Mbps Ethernet trunk Fieldbus and/or
the 2 Mbps module Fieldbus.
95
B0400FF Rev M
7. Maintenance
Field
NAME
RUN MODE
DB DOWNLOAD
STATE
LAST CABLE ACCESS
COMPOUND NAME
BLOCK NAME
HARDWARE TYPE
SOFTWARE TYPE
HARDWARE PART
HARDWARE REV
SOFTWARE REV
EEPROM REV
SERIAL NUMBER
MANUF DATE
LOGICAL ADDR
TYPE
DEVICE STATE
96
Description
User-supplied ECB name.
On-line or Off-line (default) is displayed. Set the RUN MODE using the
GO ON-LINE and GO OFF-LINE options in the Equipment Change
Display. If the FBM automatically goes off-line:
Check hardware
Check related fields, such as FBM STATUS
Download (restart) the FBM.
Acknowledged (default) or Not Acknowledged is displayed. 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 FBM failure is acknowledged by the user.
Not applicable to HART FBMs.
Both Cables OK, Cable A Not OK, Cable B Not OK, or Both Cables
Not OK is displayed. This field indicates whether transmissions were
successfully sent the last time either Bus A or B was used. A Not OK
status indicates a PIO bus send failure. To resolve this:
Check the PIO bus.
Switch to the other cable if the bus is bad.
Compound name containing the FBM ECB200.
Block name for the FBM ECB200.
Configured value for HWTYPE parameter in ECB200.
Configured value for SWTYPE parameter in ECB200.
Hardware part number related to this FBM.
Hardware release level of this FBM hardware type.
Release level of this FBM software.
Firmware release for this FBM.
Serial number assigned to this FBM hardware module.
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 Address is the number of the FBM, 1 through 120. FBMs are
typically numbered as they appear in the display (left to right).
Predefined FBM type from ECB200.
Failed or Not Failed (default) is displayed. This field changes to Failed if
a fatal hardware fault (including a possible communications cable
break) causes the FBM to fail.
7. Maintenance
B0400FF Rev M
Table 7-1. FBM214/215 Equipment Status and Information Display Fields (Continued)
Field
ALARMING STATE
WARNING CONDITION
DEVICE ATT
FAIL DEV ATT
FAIL DEV ACK
POWER 1
POWER 2
DIAG STATUS 1
DIAG STATUS 2
Description
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 Off-line.
Yes is displayed if the device has a non-fatal error condition; otherwise,
No is displayed.
Yes is displayed if the FBM has devices attached; otherwise, No is displayed.
Yes is displayed if one or more HART devices connected to the FBM
have failed; otherwise, No is displayed.
Acknowledged (default) or Not Acknowledged is displayed. If any of
the devices attached to the FBM fail and become unacknowledged, Not
Acknowledged is displayed.
OK or Failed indicates the state of primary power to FBM.
OK or Failed indicates the state of backup power to FBM.
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 safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call Global Product Support (GPS).
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 communications. Hexadecimal values and the related
conditions are as follows:
Value Condition
1 - Cold start (power up)
2 - Power fail recovery
4 - Watchdog timer failure
8 - Warm reset (equipment change download)
DIAG STATUS 3
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
Diagnostic Status 3 is a hexadecimal value relating to the previous software or hardware error for the selected FBM.
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
97
B0400FF Rev M
7. Maintenance
Table 7-1. FBM214/215 Equipment Status and Information Display Fields (Continued)
Field
DIAG STATUS 4
Description
Diagnostic Status 4 is a hexadecimal value relating to the current software or hardware error for the selected FBM. Normally, this value is 0
(no error). Other values are fatal errors; the FBM is not operational.
Typical values and their meaning are as follows:
Value Condition
0 - No error
15 - Hardware type mismatch (FBM installed in the wrong slot)
16 - Software type mismatch (ECB configuration error)
98
7. Maintenance
B0400FF Rev M
Table 7-1. FBM214/215 Equipment Status and Information Display Fields (Continued)
Field
IOM STATUS
EXTENSION TYPE
FILE REVISION
FBM TYPE
VERSION NUMBER
FILE ID
PORT1 FAIL STATE
PORT2 FAIL STATE
FBM STATUS
BUS ID
PORT1 STATUS
PORT2 STATUS
Description
IOM Status is a hexadecimal value related to the current 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 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 off-line. In off-line mode, the software control is ROMbased. In on-line mode, the software is RAM-based.
80 - Initialization is taking place all channel and I/O data is initializing. Also, indicates that the FBM has a delayed response message ready.
Not applicable to HART FBMs.
Not applicable to HART FBMs.
Type of FBM supported by ECB200.
Version number of the FBM.
Not applicable to HART FBMs.
Not applicable to HART FBMs.
Not applicable to HART FBMs.
The following may 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
Not applicable to HART FBMs.
Not applicable to HART FBMs.
Not applicable to HART FBMs.
Field
NAME
MAIN SLOT NO
Description
User-supplied ECB name.
Baseplate slot number where the main FBM is installed.
99
B0400FF Rev M
7. Maintenance
Table 7-2. FBM216/216b/218 Equipment Status and Information Display Fields (Continued)
Field
MAIN STATE
TYPE
FAIL ACK STATE
MAIN LOGICAL
ADDR
100
Description
Main State indicates the main FBM operational state:
Main Downloading Main Off-Line
Main EE Updating Master
Main Failed Tracker
Predefined FBM type from ECB202.
Acknowledged (default) or Not Acknowledged is displayed. 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 FBM failure is acknowledged by the user.
Yes (default) or No is displayed. If any of the devices attached to the
FBM fail and become unacknowledged, No is displayed.
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 Off-line.
Yes is displayed if one or more HART devices connected to the FBM
has failed; otherwise, No is displayed.
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 the following values:
Value Condition
0 - Normal, no error
1 - Success with retry (this condition is very rare)
2 - FCM timed out FBM
3 - CP timed out FCM
> 3 - Link level protocol error (this is very rare and transient)
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.
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).
7. Maintenance
B0400FF Rev M
Table 7-2. FBM216/216b/218 Equipment Status and Information Display Fields (Continued)
Field
FBM DIAG STAT 1
WARNING CONDITION
COMPOUND NAME
BLOCK NAME
HARDWARE TYPE
SOFTWARE TYPE
POWER 1
POWER 2
Description
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 safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
Diagnostic Status 3 is a hexadecimal value relating to the previous software or hardware error for the selected FBM.
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
Hardware part number related to the main FBM.
Hardware release level of the main FBM.
Firmware release for the main FBM.
Serial number assigned to the main FBM.
Baseplate slot number where the backup FBM is installed.
Backup State indicates the main FBM operational state:
Bkup Downloading Bkup Off-Line
Bkup EE Updating Master
Bkup Failed Tracker
Both Cables OK, Cable A Not OK, Cable B Not OK, or Both Cables
Not OK is displayed. This field indicates whether transmissions were
successfully sent the last time either Bus A or B was used. A Not OK
status indicates a PIO bus send failure. To resolve this:
Check the PIO bus.
Switch to the other cable if the bus is bad.
Yes is displayed if the device has a non-fatal error condition; otherwise,
No is displayed.
Compound name containing the FBM ECB202.
Block name for the FBM ECB202.
Configured value for HWTYPE parameter in ECB202.
Configured value for SWTYPE parameter in ECB202.
OK or Failed indicates the state of primary power to FBM.
OK or Failed indicates the state of backup power to FBM.
101
B0400FF Rev M
7. Maintenance
Table 7-2. FBM216/216b/218 Equipment Status and Information Display Fields (Continued)
Field
FBM DIAG STAT 2
Description
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 communications. Hexadecimal values and the related
conditions are as follows:
Value Condition
1 - Cold start (power up)
2 - Power fail recovery
4 - Watchdog timer failure
8 - Warm reset (equipment change download)
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
Diagnostic Status 4 is a hexadecimal value relating to the current software or hardware error for the selected FBM. Normally, this value is 0
(no error). Other values are fatal errors; the FBM is not operational.
Typical values and their meaning are as follows:
Value Condition
0 - No error
15 - Hardware type mismatch (FBM installed in the wrong slot)
16 - Software type mismatch (ECB configuration error)
7. Maintenance
B0400FF Rev M
Table 7-2. FBM216/216b/218 Equipment Status and Information Display Fields (Continued)
Field
MAIN FBM TYPE
MAIN VER NO
FILE ID
FILE REVISION
FBM STATUS
BKUP STATUS
1.
Description
Type of main FBM supported by ECB202.
Version number of the main FBM.
Not applicable to HART FBMs.
Not applicable to HART FBMs.
The following may 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
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.
Release level of the backup FBM software.
Main Status indicates the operational status of the main FBM:
Not Operational HART Comm Fault1
Off-line 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
Backup Status indicates the operational status of the backup FBM:
Not Operational HART Comm Fault1
Off-line 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
The HART COMM Fault text field is displayed if the FBM is unable to communicate with a
HART device on any of the eight channels, even if this is due to the lack of an electrical connection
to the device.
103
B0400FF Rev M
7. Maintenance
104
7. Maintenance
B0400FF Rev M
Field
Name
Type
Run Mode
Device State
Devices Attached
Failed Devices Attached
Failed Acknowledged
State
Description
User-supplied ECB name.
Set to FBM247.
On-line or Off-line (default) is displayed. Set the RUN MODE using the
GO ON-LINE and GO OFF-LINE options in the Equipment Change
Display actions (right-click the FBM). If the FBM automatically goes
off-line:
Check hardware
Check related fields, such as FBM STATUS
Download (restart) the FBM.
Failed or Not Failed (default) is displayed. This field changes to Failed if
a fatal hardware fault (including a possible communications cable
break) causes the FBM to fail.
Yes is displayed if the FBM has devices attached; otherwise, No is displayed.
Yes is displayed if one or more HART devices connected to the FBM
have failed; otherwise, No is displayed.
Acknowledged (default) or Not Acknowledged is displayed. 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 FBM failure is acknowledged by the user.
105
B0400FF Rev M
7. Maintenance
Table 7-3. FBM247 Equipment Status and Information Display Fields (Continued)
Field
EEPROM Update State
Description
106
7. Maintenance
B0400FF Rev M
Table 7-3. FBM247 Equipment Status and Information Display Fields (Continued)
Field
Description
Integration Period
HART Enabled
Input Channel
Output Channel
107
B0400FF Rev M
7. Maintenance
Table 7-3. FBM247 Equipment Status and Information Display Fields (Continued)
Field
Loop Powered
Bus ID
Log Count
(Diag Status 3)
108
Description
(Information is per channel) Indicates the status of the SYSCFG bit
map - see Configuring FBM ECB (ECB200) for FBM247 on
page 66.
HART Enabled: Indicates which channel(s) that have been enabled for
HART communication or Not Configured if no channel is configured.
Input Channel: Indicates which of the HART Enabled channels that
are configured as an input channels.
Output Channel: Indicates which of the HART Enabled channels that
are configured as an output channels.
Loop powered: Indicates which of the HART Enabled channels that are
configured to supply loop power.
Module ID of the FCM that connects the FBM247 to a ZCP270.
Not used if the FBM is attached to an FCP270 or FCP280.
Diagnostic Status 3 is a hexadecimal value relating to the previous software or hardware error for the selected FBM.
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
Logical Address is the number of the FBM, 1 through 120. FBMs are
typically numbered as they appear in the display (left to right).
Physical address of the FBM on the baseplate chain.
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 the following values:
Value Condition
0 - Normal, no error
1 - Success with retry (this condition is very rare)
2 - FCM timed out FBM
3 - CP timed out FCM
> 3 - Link level protocol error (this is very rare and transient)
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.
7. Maintenance
B0400FF Rev M
Table 7-3. FBM247 Equipment Status and Information Display Fields (Continued)
Field
IOM Status
Power Status
(Diag Status 1)
Description
IOM Status is a hexadecimal value related to the current FBM status.
Typically this value is 4, indicating the instructions are valid.
Value Condition
Status Change - FBM status has changed requests CP to poll for
extended status.
Error - Diagnostic Register is nonzero. This indicates a fatal error.
The FBM does not start if this value is set.
Not failsafe (default) - 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.
Power fail restart - Power fail restart.
SOE Data Available - SOE Data is available.
Out of Service - FBM is out of service.
Off Line - FBM is off-line. In off-line mode, the software control is
ROM-based. In on-line mode, the software is RAM-based.
Poll request - Poll request is occurring.
Diagnostic Status 1 is a hexadecimal value related to the FBM status.
Value Condition
0x00 - Non-fail-safe condition typical status for an FBM with a
green status LED on
0x01 - Primary power supply (1) is missing.
0x01 - Secondary power supply (2) is missing.
Startup Status
(Diag Status 2)
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call IOM Global Product Support (GPS).
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 communications. Hexadecimal values and the related
conditions are as follows:
Value Condition
Cold Start - Power up
Cold Reset - Power fail recovery
Watchdog Failure - Watchdog timer failure
Warm Start - Warm reset (equipment change download)
Fatal Error Flashed - Fatal error has occurred.
If the FBM is operating normally, this field can be safely ignored. For
resolution of the FBM hardware and software errors indicated by this
diagnostic status field, call the Global Product Support.
109
B0400FF Rev M
7. Maintenance
Table 7-3. FBM247 Equipment Status and Information Display Fields (Continued)
Field
FBM Runtime Status
(Diag Status 4)
Description
Diagnostic Status 4 is a hexadecimal value relating to the current software or hardware error for the selected FBM. Normally, this value is 0
(no error). Other values are fatal errors; the FBM is not operational.
Typical values and their meaning are as follows:
Value Conditions
OK
Config Table Invalid
Fatal Babble
Secure Write Failed
Clock Overrun
AI Overrun
HW Type Mismatch
SW Type Mismatch
RAM Checksum Fail
Illegal Interrupt
Pulse Input Overrun
FPGA Failure
EEPROM UPDATE Fail
Bad RAM Stack Pointer
Bad ROM Stack Pointer
Flashed Error
Main IO Status Error
Max IO Errors Exceeded
EEPROM Checksum Fail
Mfg Data Checksum Fail
Mfg Ext Checksum Fail
EEPROM Update In Progress
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 problem, call the Global Product
Support.
110
7. Maintenance
B0400FF Rev M
Action
GO ON-LINE
GO OFF-LINE
DOWNLOAD
EEPROM
UPDATE
Description
Connects the FBM to the Foxboro control station, thus enabling
communication.
Disconnects the FBM from the Foxboro control station, thus disabling
communication.
Restarts the FBM logic. This action does not download the FBM image.
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.
! CAUTION
Do not attempt to use or power down the FBM while the
EEPROM is being updated.
ENABLE
DEVICE
ALARMING
INHIBIT
DEVICE
ALARMING
Inhibits device alarms from propagating upward in the Foxboro Evo system.
Right-click the FBM to open its context menu. -OR From the Actions menu, open the Equipment Change submenu.
3. Click Go On-line.
More information is available in System Manager (B0750AP).
111
B0400FF Rev M
7. Maintenance
-OR1. Access the System Management displays. For detailed information, refer to System
Management Displays (B0193JC).
2. On the PIO SUB NETWORK display, click the FBM and then click EQUIP CHG.
3. On the EQUIPMENT CHANGE display, click GO ON-LINE.
The FBM is now on-line.
Action
GO ON-LINE
GO OFF-LINE
DOWNLOAD
112
Description
Connects the FBM to the Foxboro control station, thus enabling
communication.
Disconnects the FBM from the Foxboro control station, thus disabling
communication.
Restarts the FBM logic. This action does not download the FBM image.
7. Maintenance
B0400FF Rev M
Action
EEPROM UPDATE
Description
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 software release.
! CAUTION
Do not attempt to use or power down the FBM while the
EEPROM is being updated.
Following an EEPROM update of one or both FBM216/218 modules,
the updated modules are placed in the state (on-line or off-line) that they
were in prior to the EEPROM update. Other 200 Series FBMs are placed
on-line following 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 MAIN, BACKUP, or BOTH.
Updating FBMs Off-Line
When you update the main or backup module, that module becomes
inoperable, is updated, and returns to the off-line state. When you update
both modules, the main module becomes inoperable, is updated, and
returns to the off-line state. Then, the backup module becomes inoperable, is updated, and returns to the off-line 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 failure.
ENABLE DEVICE
ALARMING
INHIBIT DEVICE
ALARMING
SWITCH ROLES
B0400FF Rev M
7. Maintenance
114
7. Maintenance
B0400FF Rev M
Field
Description
NAME
COMMUNICATIONS
DB DOWNLOAD
STATE
FAIL DEV ATT
COMPOUND NAME
EE UPDATE STATE
HARDWARE TYPE
PRIMARY STATUS
Value Condition
0 - Normal, no error
1 - Success with retry (this condition is very rare)
2 - FCM timed out FBM
3 - CP timed out FCM
> 3 - Link level protocol error (this is very rare and transient)
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.
115
B0400FF Rev M
7. Maintenance
Table 7-6. HART Device Equipment Status and Information Display Fields (Continued)
Field
FBM IOM STATUS
FILE REVISION
DEVICE TYPE
VERSION NUMBER
FILE ID
MANUFACTURER
TYPE
DEVICE STATE
ALARMING STATE
WARNING CONDITION
FAIL DEV ACK
BLOCK NAME
116
Description
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 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 off-line. In off-line mode, the software control is ROMbased. In on-line mode, the software is RAM-based.
80 - Initialization is taking place all channel and I/O data is initializing. Also, indicates that the FBM has a delayed response message ready.
Not applicable.
Type of field device represented by the ECB201.
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.
Not applicable.
Manufacturer Identification Code for the field device. Refer to HART
Common Tables Specifications (HFC_SPEC-183).
Field device (DEV 214, 215, 216 or 218) represented by the ECB201.
Failed or Not Failed (default) is displayed. This field changes to Failed if
a device fatal hardware fault (including a possible communications
cable break) causes the device to fail.
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 Off-line.
Yes is displayed if the device has a non-fatal error condition; otherwise,
No is displayed.
Acknowledged (default) or Not Acknowledged is displayed. If any of
the devices attached to the FBM fail and become unacknowledged, Not
Acknowledged is displayed.
Block name for the FBM ECB201.
7. Maintenance
B0400FF Rev M
Table 7-6. HART Device Equipment Status and Information Display Fields (Continued)
Field
Description
MANUF DATE
SOFTWARE TYPE
FBM DIAG STATUS 2
FBM DIAG STATUS 3
FBM DIAG STATUS 4
BUS ID
PORT NUMBER
MODEL
DEVICE NAME
DEVICE ADDRESS
DEVICE OPTIONS
MASTER ADDRESS
IDENTIFICATION
NO
DEVICE STATUS
117
B0400FF Rev M
7. Maintenance
Table 7-7 describes the available Equipment Information fields provided for the FBM247s channels in the order that they appear on the System Manager display pages.
Table 7-7. FBM247 Channel (ECB201) Equipment Status and Information Display Fields
Field
Name
Type
Communications
Device State
Failed Acknowledged
State
118
Description
User-supplied ECB name.
Set to FBM247.
Run mode status of channel/device; either Enabled or Disabled.
Failed or Not Failed (default) is displayed. This field changes to Failed if
a fatal hardware fault (including a possible communications cable
break) causes the associated channel/device to fail.
Acknowledged (default) or Not Acknowledged is displayed. 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 channel/device failure is acknowledged by the
user.
Alarming State indicates whether alarming is Enabled or Inhibited for
the channel.
7. Maintenance
B0400FF Rev M
Table 7-7. FBM247 Channel (ECB201) Equipment Status and Information Display Fields (Continued)
Field
Warning Conditions
Exist
Compound:Block
Device Name
Device Options
Circuit Type
HART Device
Point Type
HART System Alarm
Option
HART OOS Option
Block Config
Hardware Type
Software Type
Manufacturer
Device Type
Version Number
Fieldbus Type
Description
Yes is displayed if the channel has reported a non-fatal error condition;
otherwise, No is displayed.
Compound and block name containing the FBM ECB200.
The device name for the channel - the value of DVNAME; see Configuring Device ECB (ECB201) for FBM247 on page 69.
The device options for the channel - the value of DVOPTS; see Configuring Device ECB (ECB201) for FBM247 on page 69.
Voltage, Current, or Disabled.
This is determined by the DVOPTS parameter; see Configuring
Device ECB (ECB201) for FBM247 on page 69.
Yes is displayed if the channel is supporting a HART device; otherwise,
No is displayed.
This is determined by the DVOPTS parameter; see Configuring
Device ECB (ECB201) for FBM247 on page 69.
Indicates the type of point: AI, AO, DI, DO, Pulse In, Pulse Out,
SOE Input, or NAMUR Input.
Enabled or Disabled.
This is determined by the DVOPTS parameter; see Configuring
Device ECB (ECB201) for FBM247 on page 69.
Enabled or Disabled.
This is determined by the DVOPTS parameter; see Configuring
Device ECB (ECB201) for FBM247 on page 69.
Primary connection string for the block connection to the channel.
Configured value for HWTYPE parameter in ECB201 - FBM247.
Configured value for SWTYPE parameter in ECB201 - FBM247.
Manufacturer Identification Code for the field device. Refer to HART
Common Tables Specifications (HFC_SPEC-183).
Device type identification for this channel.
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.
Indicates type of communication protocol used, such as HART.
119
B0400FF Rev M
7. Maintenance
Table 7-7. FBM247 Channel (ECB201) Equipment Status and Information Display Fields (Continued)
Field
Device Status
Device Diagnostic
Status
120
Description
The following are displayed to define the device/signal status:
DCI Ready/DCI Not Ready
Device Failed
Device Disable
DB Download Failed
DB Download Active
Unresolved Connection
System Alarm
System Message
The following are displayed to define the device/signal diagnostic status:
Primary Out of Limits
Non-Primary Out of Limits
Primary Output Saturated
Primary Output Fixed
More Status Available
Cold Start
Configuration Changed
Field Device Malfunction
A/D Converter Fault
D/A Converter Fault
HART Comm Fault
7. Maintenance
B0400FF Rev M
Action
ENABLE
COMMUNICATIONS1
DISABLE
COMMUNICATIONS1
ENABLE DEVICE
ALARMING
INHIBIT DEVICE
ALARMING
1.
Description
Enables HART communication between the device and FBM.
Disables HART communication between the device and FBM.
Enables device alarms to propagate upward to the Foxboro Evo system.
Inhibits device alarms from propagating upward to the Foxboro Evo
system.
If the device parent FBM214/215 is off-line, these key actions are not available. If the device parent
FBM216/218 main and backup modules are off-line, these key actions are not available.
B0400FF Rev M
7. Maintenance
3. On the I/O DISPLAY, click the device and then click EQUIP CHG.
4. On the EQUIPMENT CHANGE display, click ENABLE COMMUNICATIONS.
5. Repeat Steps 3 and 4 for each additional slave device.
Communications with the slave devices is now enabled.
Diagnostic View
Figure 7-5. ECB200 Faceplates for FBM247 Devices - Main View and Diagnostic View
122
7. Maintenance
B0400FF Rev M
The
button adds buttons to the right side of the faceplate for selecting configuration and diagnostic displays (see Figure 7-6 below).
The trends button (
) is not used as there are no trend displays associated with
equipment control blocks.
The ECB Status display in the ECB200 faceplates main view indicates operational states of the
ECB200 (above the bold line in Table 7-9) and error conditions when they apply (below the bold
line in Table 7-9). The information is sourced from the ECB200 BLKSTA parameter. Refer to
Integrated Control Block Descriptions (B0193AX) for a detailed description of the parameter.
Table 7-9. FBM247 ECB200 ECB Status Indicators
Status
ECB ON or
ECB OFF
DEV READY or
DEV NOT READY
ON SCAN or
OFF SCAN
DEV FAIL
UNDEF
DEV SHUT DWN
COMM FAIL
Description
The ECB200s compound is either ON or OFF.
The FBM is either ready or not ready to exchange data with the
attached devices.
The ECB200 is either in on-scan or off-scan mode.
There was a hardware failure in the FBM.
The ECB has an unresolved configuration problem.
The FBM is not operating.
There is a problem with communications between the FBM and
the CP.
The FBM Status display in the ECB200 faceplates main view is derived from the FBMSTS
parameter. The display indicates operational states of the FBM247 (above the bold line in
Table 7-10) and error conditions (below the line in Table 7-10) when they apply.
Table 7-10. FBM247 ECB200 FBM Status Indicators
Status
DCI READY or
NOT READY
ON LINE or
OFF LINE
FBM OK or
FBM FAIL
DWNLD FAIL
UNRESOLVED
Description
The DCI configuration in the FBM is ready.
The FBM is on-line or off-line.
The FBM is OK (that is, operating and communicating with the
CP), or failed.
A reset of the FBM247 failed because the FBM could not receive its
configuration correctly. Also shown when a DB Download fails for
an FBM configured with ICC.
The control processor reports that there is an unresolved connection to the FBM.
123
B0400FF Rev M
7. Maintenance
Configuration View - FS
2. Click CONFIG to display the ECB parameters in the BLOCK overlay (Figure 7-6,
Configuration View - Block).
124
7. Maintenance
B0400FF Rev M
3. Click FS at the bottom of the view to display failsafe settings (Figure 7-6,
Configuration View - FS).
4. Click SYSCFG to display the mapping for the SYSCFG parameter (described in
Configuring FBM ECB (ECB200) for FBM247 on page 66).
Table 7-11 describes the ECB parameters displayed on the Configuration Views in the ECB200
faceplate.
Table 7-11. FBM247 Information in a ECB200 Faceplate
Parameter
TYPE
PERIOD
PHASE
ERCODE
SYSCFG
SYSOPT
FSENAB
FSDLAY
Description
The ECB type is ECB200 for an FBM247
Scanning frequency set for the ECB
BPC phase in which the ECB is scanned
Error Code is not used by the FBM247
The length of time at which the System Configuration parameter is polled. The
SYSCFG parameter is described in Configuring FBM ECB (ECB200) for
FBM247 on page 66.
System Option parameter specifies whether system alarming and/or messaging
are to be disabled. This is described in Configuring FBM ECB (ECB200) for
FBM247 on page 66.
When Failsafe is enabled (FSENAB=1), the FBM starts a timer when it loses
communications with the control station. If communications are not restored at
the end of the specified time, the FBM takes failsafe action. The time is specified
in units of 10 ms. In Figure 7-6 for example, the parameter is set to 1000 (the
default) for a delay of 10 seconds. These are described in Configuring FBM
ECB (ECB200) for FBM247 on page 66.
The Diagnostic View (not shown) provides a general list of diagnostic messages applicable to the
FBM247s operation.
125
B0400FF Rev M
7. Maintenance
Configuration View
The
button adds buttons to the right side of the faceplate for selecting configuration and diagnostic displays.
The trends button (
) is not used as there are no trend displays associated with
equipment control blocks.
The ECB Status display in the ECB201 faceplates main view indicates operational states of the
ECB201 (above the bold line in Table 7-12) and error conditions when they apply (below the
bold line in Table 7-12). The information is sourced from the ECB200 BLKSTA parameter. Refer
to Integrated Control Block Descriptions (B0193AX) for a detailed description of the parameter.
Table 7-12. FBM247s Device ECB201 ECB Status Indicators
Status
ECB ON or
ECB OFF
126
Description
The ECB201s compound is either ON or OFF.
7. Maintenance
B0400FF Rev M
Status
Description
DEV READY or
DEV NOT READY
ON SCAN or
OFF SCAN
DEV FAIL
UNDEF
DEV SHUT DWN
COMM FAIL
The FBM is either ready or not ready to exchange data with the
attached devices.
The ECB201 is either in on-scan or off-scan mode.
There was a hardware failure in the FBM.
The ECB has an unresolved configuration problem.
The FBM is not operating.
There is a problem with communications between the FBM and
the CP.
The DVC Status display in the ECB201 faceplates main view is derived from the DEVSTS
parameter. The display indicates operational states of the FBM247s device (above the bold line in
Table 7-13) and error conditions (below the line in Table 7-13) when they apply.
Table 7-13. FBM247s Device ECB201 DVC Status Indicators
Status
DCI READY or
NOT READY
DEV ENABLD or
DEV DISBLD
DVC OK or
DVC FAIL
PORT DISABLD
DWNLD FAIL
UNRESLVD
Description
The DCI configuration in the FBM is ready.
Whether the device is on-line or off-line.
The FBMs device is OK (that is, operating and communicating
with the CP), or failed.
Shown if the port is disabled.
A reset of the FBM247 failed because the FBM could not receive its
configuration correctly. Also shown when a DB Download fails for
the host FBM configured with ICC.
Shown when there is an unresolved connection to the device.
127
B0400FF Rev M
7. Maintenance
Table 7-14 describes the ECB parameters displayed on the Configuration View in the ECB201s
faceplate.
Table 7-14. FBM247 Information in a ECB200 Faceplate
Parameter
TYPE
PERIOD
PHASE
ERROPT
ERCODE
PORTNO
DVNAME
MODLID
DVADDR
DVOPTS
DVTYPE
MANFTR
PARENT
Description
Equipment control block type, always ECB201
ECBs execution time base
Configured execution phase for the ECB
Error Alarm Option is not used for DeviceNet devices
Error Code is not used by the FBM247
Port 1 identifies the FBM247s port for this device
Device Name is the name of the field device associated with the ECB201. It is
used by the FBM to validate the identity of the field device when the device connection is made.
Model name (ProdName) and model ID (ProdCode) extracted from the EDS
file
Device address read back from the device itself
Device address as configured in ICC or Foxboro Evo Control Editors
Device type (ProdTypeStr) and type ID (ProdCode) extracted from the EDS file
Device manufacturer (VendName) and ODVA number (VendCode) extracted
from the EDS file
Compound and name of the parent ECB200, that is, the ECB of the FBM247
to which the device is connected
Selecting the DIAG1 button in these ECB201 views (see Figure 7-7 on page 126) displays the
contents of the DDIAG1 parameter of the ECB201, which allows you to read the current HART
device status. The general details of this parameter are discussed in ECB201 Extended Status
Support on page 91; however, the specific use of this parameter with FBM247 and HART
devices is discussed in Configuring IIN Block for HART Integer Digital Variables and Device
Status Bits for the FBM247 on page 73.
This status check pertains to redundant FBM216/216b inputs that are powered
from the FBM. It does not pertain to externally powered inputs.
The purpose of the following test is to validate operation of the per channel power supply for each
module in the FBM216 or FBM216b module pair. The test should be performed periodically.
The more often the test is performed, the higher the reliability.
128
7. Maintenance
B0400FF Rev M
The power supplies of each input channel of a redundant pair are diode ORd on the redundant
adapter associated with the input pair. Test points are provided on the redundant adapter to measure loop power for each channel.
The FBM216 redundant adapter for the standard FBM is shown in Figure 7-8, and the adapter
for the Compact FBM216b is shown in Figure 7-9. Along the bottom of the redundant adapter
are test point commons [Input (-)] for each channel. Along the top and right side are positive test
points [Input (P)] for each channel. Two test points are provided for each channel, one for the left
FBM216 module (1), and one for the right FBM216 module (2)].
To perform the status check, refer to Figure 7-8 and proceed as follows:
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 should be 24 V dc 5%. A reading significantly below specification indicates
a defective module (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
P0917XQ
01
05
2
1
01 02 03 04
Input (P)
Input (P)
08 07 06 05
1
FBM216
Redundant Adapter
Input (-)
04
08
129
B0400FF Rev M
7. Maintenance
Test Points
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.
The purpose of the following test is to validate operation of the per channel power supply for each
module in the FBM245 module pair. The test should be performed periodically. The more often
the test is performed, the higher the reliability.
The power supplies of each input channel of a redundant pair are diode ORd on the redundant
adapter associated with the input pair. Test points are provided on the redundant adapter to measure loop power for each channel.
The FBM245 redundant adapter is shown in Figure 7-10. Along the bottom of the redundant
adapter are test point commons [Input (-)] for each channel. Along the top and right side are positive test points [Input (P)] for each channel. Two test points are provided for each channel, one
for the left FBM245 module (1), and one for the right FBM245 module (2)].
To perform the status check, refer to Figure 7-10 and proceed as follows:
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 should be 24 V dc 5%. A reading significantly below specification indicates
a defective module (defective loop power).
2. Repeat Step 1 for the remaining three channels (02 through 04), using the respective
common points and loop power test points.
130
7. Maintenance
B0400FF Rev M
Test Points
Input (P)
2
FBM245
Redundant Adapter
01 02 03 04
01 02 03 04
Input (-)
P0924DU
Operational Status
01
02
03
04
05
06
07
08
FBM214
8 Communication,
HART Input
P0914XQ
131
B0400FF Rev M
7. Maintenance
Operational Status
01
Master
02
Tracker
03
04
05
06
07
08
FBM216
8 Communication,
Redundant HART Input
P0917TN
132
7. Maintenance
B0400FF Rev M
Operational Status
01
02
03
DI/DO, Pulse
04
05
HART
06
07
08
FBM247
Channel Isolated
8 Configurable Channels
(AI/AO)+HART, DI/DO, Pulse
P0927BN
133
B0400FF Rev M
7. Maintenance
On the front of all HART FBMs and the FBM247, two Operational Status LEDs (red and green)
indicate the operational status of the module. During normal on-line operation of the FBM with
communications enabled with the connected HART devices, the green LED is on, and the red
LED is off.
LEDs 01 through 08 provide different information on the HART FBMs than on the FBM247:
For the HART FBMs, 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 the FBM247, LEDs 01 through 08, indicate the operational status of the eight
communication channels, depending on what the source of each channel has been
configured for. When a channel is configured for HART or analog communications,
its associated LED is on when the FBM is expecting and receiving valid messages on
the channel. If the ECB201 is configured as 4-20 (4 to 20 mA analog channel), the
LED is always off.
When a channel is configured for digital I/O signals, the yellow LED indicates the on
or off state of the digital input or output channel.
On the redundant HART FBMs (not currently supported on the FBM247), 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 communications. The Tracker LED is on when the
module is ready to control HART communications.
Table 7-15 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
(or with the FBM247, the FBMs associated I/O source). It also assumes that you have placed the
FBMs on-line and enabled device communications using the appropriate displays (System Manager or SMDH).
Table 7-15. HART FBM Operational Status LEDs
Operational Status
Red LED
Green LED
01 to 08
Master
Tracker
Status
Normal Operation
Off
On
On for
channels
with normal
HART
communications
On or
Off
On or
Off
Power Off
Off
134
Off
Off
Off
Off
7. Maintenance
B0400FF Rev M
Operational Status
Red LED
Green LED
01 to 08
Master
Tracker
Status
Diagnostic Failure1
On
Flashing
0.5 s on,
0.5 s off
Off
Off
Off
On
Flashing
three 0.5 s
flashes
every 5 s
Flashing
four 0.5 s
flashes
every 5 s
Off
Off
Off
Off
Off
Off
On
Off
Off
Off
On
On
Off-Line
On
On
Off
On or
Off
On or
Off
Flashing
Off
On or
Off
On or
Off
EEPROM Update
Flashing
Flashing
Off
Flashing
Flashing
B0400FF Rev M
7. Maintenance
Operational Status
Red LED
Green LED
01 to 08
Master
Tracker
Status
On
Any one
LED off
On or
Off
On or
Off
On
Occasional
flickering of a
Trackers
LED
On or
Off
On or
Off
On
Trackers
LEDs are
consistently
different
than
Masters
LEDs
On or
Off
On or
Off
Fail Safe
Off
Flashing
On for
channels
with normal
HART
communications
On or
Off
On or
Off
Module Failure
On
1.
136
Off
Off
On or
Off
On or
Off
Module failure.
Failure detected during startup diagnostics. Reboot the module to clear the diagnostic error. If the
problem still exists, remove the module from the baseplate and reinstall it in the same slot (refer to
the WARNING at the beginning of this chapter on page 93). If problem continues, replace the
module. Refer to DIN Rail Mounted Subsystem Users Guide (B0400FA) for details.
7. Maintenance
B0400FF Rev M
137
B0400FF Rev M
138
7. Maintenance
These system messages may 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 will hold 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.
! WARNING
This field rolls over every 1.8 hours. It is intended to provide relative timing to
other messages posted by the same FBM only.
Some of these messages may be turned off by setting gating bits in the SYSOPT register. Those
gating bits are shown in Table A-1 below.
139
B0400FF Rev M
Table A-1. Gating Bits in the SYSOPT Register for HART FBM System Messages
Gated
by Bit
Error
Code
Error Text
Corrective Action
08
21
08
22
08
22
08
22
08
23
08
24
08
25
08
26
08
44
60
08*
61
comms timeout
These indicate that the HART device has communication timeouts with DVOPTS set to OCD. HART
Device fault
08*
62
08*
63
08*
64
08*
65
08*
66
malfunction cleared
08*
67
n/a
Ch1-8
n/a
Ch1-8
n/a
Ch1-8
n/a
Ch1-8
n/a
Ch1-8
DVOPTS Is Invalid
n/a
Ch1-8
n/a
Ch1-8
n/a
Ch1-8
n/a
Ch1-8
DI Thresholds Backwards
n/a
Ch1-8
140
B0400FF Rev M
Table A-1. Gating Bits in the SYSOPT Register for HART FBM System Messages
Gated
by Bit
Error
Code
Error Text
Corrective Action
10
48
10
49
10
53
10
54
10
55
10
56
10
57
Power 1 Fault
10
58
Power 2 Fault
10
59
Slot conflict
ERROR: Either
- The Master FBM and its partner are not agreeing
on the interlink use
- The Master FBMs expectation of the partners
sending state does not match the reported state.
Best to reseat the pair one at a time, starting with
Tracker.
40
10
41
10
42
10
43
10
44
10
45
master: no partner
141
B0400FF Rev M
Table A-1. Gating Bits in the SYSOPT Register for HART FBM System Messages
Gated
by Bit
Error
Code
Error Text
Corrective Action
10
46
10
47
10
50
10
51
10
52
The interlink between the pair of modules is experiencing problems. As the interlink is very short,
this is usually a seating issue.
142
Index
A
Auto/Manual mode, DCI blocks 80
B
Baseplate xiii, 3
Baseplate, FBM mounting slots 14
Baseplate-mounted TA
FBM247 36
Block detail display 7, 87
ECB200 88
ECB201 90
ECB202 89
C
Cable balun module 11
Cable length 11
Cable Type A 10
Cascade initialization
ROUT block 81
Compound detail displays 87
Configuration information
DCI blocks 49
Configuration procedures 50
Configuring DCI blocks 77
Control schemes
DCI blocks 84
Control station xiii
Creating and editing ECB
ECB200 63
ECB201 64
ECB202 63
D
Data type conversions
DCI blocks 61, 62
DCI xiii
DCI blocks 50
Auto/Manual mode of operation 80
block interconnection example 51, 52, 53, 54
cascade initialization 81
configuration information 49
configuration procedures 50
configuring 77
143
B0400FF Rev M
control schemes 84
data type conversions 61, 62
fail-safe actions 82
functions 80
HART point addresses 59, 60
input limiting 80
key parameters 55
list of 49
output clamping 81
output confirmation 80
output initialization 81
periodic/change-driven execution 80
signal conditioning and linear scaling 80
simulation mode 80
status transformations 83
Device connections to TAs 17
Device data verification 7
Diagnostics 4, 135
Distributed Control Interface xiii
E
ECB xiv
ECBs
creating and editing 63, 64
hierarchy 50
list of 49
Entity parameters 47
Environmental constraints 9
Equipment Change display
FBM214/214b/215 111
FBM216/216b/218 112
HART device 121
Equipment Control Block xiv
Equipment Information display
FBM214/214b/215 96
FBM216/216b/218 99
FBM247 104
FBM247 device/signal 118
HART device 115
Equipment installation 13
Example
DCI block interconnections 51, 52, 53, 54
F
Faceplate
FBM247 122
Fail-safe actions
DCI blocks 82
144
Index
Index
B0400FF Rev M
FBM xiv
FBM214/214b 1
FBM215 1
FBM216/216b 1
FBM216/216b redundant power supply test 128, 130
FBM218 1
FBM244 2
FBM245 2
FBM247 2
FCM xiv
Fieldbus xiv
Fieldbus Communications Module xiv
Fieldbus Module xiv
FoxCAE software xiv
G
Glossary xiii
Group displays 87
H
Hand held configurator 4
HART communications standard 2
HART point addresses
DCI blocks 59, 60
I
IFDC xiv
Input limiting
RIN 80
Input signal flow
FBM214/214b 19
FBM216/216b 21
Install the Foxboro Evo system 6
Installation
equipment 13
FBMs and TAs 16
redundant adapter 16, 17
Intrinsic safety considerations 12
Invensys Global Customer Support xiii
K
Key parameters 55
L
LED status indicators
Compact FBM214b/215 132
Compact FBM216b/218 133
145
B0400FF Rev M
146
Index
Index
B0400FF Rev M
DCI blocks 80
SMDH 95
Station displays 87
Status transformations
DCI blocks 83
SYSCFG parameter for FBM247 67, 124
System Management displays 94, 121
System Manager displays 94
T
TA xiv, 3, 13
TA cable connections
FBM214/214b/215 18
FBM215/218 29
FBM244/245 32
FBM247 38
TAs
device connections 17
Termination assemblies xiv, 3, 13
U
User-generated displays 87
147