Phoenix Contact Fieldbus FB-DIAG/FF/LI User manual

User manual
Field diagnostics module for
monitoring Foundation
Fieldbus™ fieldbus segments
UM EN FDM

2014-11-13
PHOENIX CONTACT 3228_en_A
Field diagnostics module for monitoring Foundation Fieldbus™ fieldbus
segments
UM EN FDM
A
Designation Version Order No.
FB-DIAG/FF/LI 2316284
FB-DIAG/FF/NC 2316297
User manual
Designation:
Revision:
This user manual is valid for:

PHOENIX CONTACT
Please observe the following notes
User group of this manual
The use of products described in this manual is oriented exclusively to:
– Qualified electricians or persons instructed by them, who are familiar with applicable
standards and other regulations regarding electrical engineering and, in particular, the
relevant safety concepts.
– Qualified application programmers and software engineers, who are familiar with the
safety concepts of automation technology and applicable standards.
Explanation of symbols used and signal words
How to contact us
Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be
found on the Internet at:
www.phoenixcontact.com
Make sure you always use the latest documentation.
It can be downloaded at:
www.phoenixcontact.net/products
Subsidiaries If there are any problems that cannot be solved using the documentation, please contact
your Phoenix Contact subsidiary.
Subsidiary contact information is available at www.phoenixcontact.com.
Published by PHOENIX CONTACT GmbH & Co. KG
Flachsmarktstraße 8
32825 Blomberg
GERMANY
Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:
[e-mail]
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible in-
jury or death.
There are three different categories of personal injury that are indicated with a
signal word.
DANGER This indicates a hazardous situation which, if not avoided, will re-
sult in death or serious injury.
WARNING This indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION This indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.
This symbol and the accompanying text provide the reader with additional in-
formation or refer to detailed sources of information.

Please observe the following notes
PHOENIX CONTACT
General terms and conditions of use for technical documentation
Phoenix Contact reserves the right to alter, correct, and/or improve the technical documen-
tation and the products described in the technical documentation at its own discretion and
without giving prior notice, insofar as this is reasonable for the user. The same applies to any
technical changes that serve the purpose of technical progress.
The receipt of technical documentation (in particular user documentation) does not consti-
tute any further duty on the part of Phoenix Contact to furnish information on modifications
to products and/or technical documentation. You are responsible to verify the suitability and
intended use of the products in your specific application, in particular with regard to observ-
ing the applicable standards and regulations. All information made available in the technical
data is supplied without any accompanying guarantee, whether expressly mentioned, im-
plied or tacitly assumed.
In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.
This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.
Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.
Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

3228_en_A PHOENIX CONTACT 1
Table of contents
1 Introduction.................................................................................................................................3
1.1 Description ............................................................................................................ 3
1.2 Hardware and software requirements.................................................................... 3
1.3 Hazardous locations.............................................................................................. 3
1.3.1 ATEX and IECEx special conditions for safe use ................................... 3
1.3.2 CSA conditions for certification .............................................................. 4
2 Installation ..................................................................................................................................5
2.1 Mounting ............................................................................................................... 5
2.2 Connection ............................................................................................................ 5
2.3 Typical installation ................................................................................................. 6
2.4 LED indicators ....................................................................................................... 7
3 Operation....................................................................................................................................9
3.1 Monitored parameters ........................................................................................... 9
3.2 Alarms ................................................................................................................... 9
3.2.1 Standard alarms .................................................................................... 9
3.2.2 Namur NE-107 alarms ......................................................................... 10
3.2.3 Field diagnostic alerts .......................................................................... 11
3.3 Host support files................................................................................................. 12
3.3.1 Viewing segment information ............................................................... 12
3.3.2 Viewing device information .................................................................. 13
3.4 Setting alarm limits .............................................................................................. 14
3.5 Detecting and diagnosing an alert ....................................................................... 15
3.6 Resetting diagnostic data alarms......................................................................... 17
3.7 Trend data ........................................................................................................... 18
3.7.1 EDDL trend data .................................................................................. 18
3.7.2 DTM trend data .................................................................................... 19
3.7.3 Exporting a trend report in .csv format ................................................. 19
3.8 Commissioning reports ....................................................................................... 20
3.8.1 DTM commissioning report .................................................................. 20
3.9 Mapping alerts to an AI or DI block ...................................................................... 22
3.10 FB-DIAG⁄FF⁄… device identification..................................................................... 24
A Technical appendix...................................................................................................................25
A 1 FB-DIAG⁄FF⁄… parameters ................................................................................. 25
A 2 Parameter descriptions....................................................................................... 28
A 3 Alerts and recommended actions....................................................................... 34
A 4 Foundation Fieldbus field diagnostic alerts......................................................... 37
A 5 Foundation Fieldbus field diagnostic alerts ........................................................ 39

FB-DIAG/FF/…
2PHOENIX CONTACT 3228_en_A
B Appendixes...............................................................................................................................41
B 1 List of figures ...................................................................................................... 41
B 2 List of tables ....................................................................................................... 43
B 3 Explanation of terms........................................................................................... 45

Introduction
3228_en_A PHOENIX CONTACT 3
1Introduction
1.1 Description
The field diagnostics module (FB-DIAG⁄FF⁄…) is a DIN rail-mounted device that provides
measurements, monitoring, and alarming for the physical layer of an active Foundation
Fieldbus™ fieldbus segment.
Critical process measurements, such as segment voltage, device count, signal level,
communication status and noise levels, can be realized on each segment using an
FB-DIAG⁄FF⁄…. The use of device descriptor (DD), electronic device description language
(EDDL) and device type manager (DTM) files allow seamless integration into any control
system without the need for protocol or media conversion.
The FB-DIAG⁄FF⁄LI is for use in a legacy block type device coupler installation or where an
FB-ET is not incorporated onto a segment.
The FB-DIAG⁄FF⁄NC utilizes a T-BUS connector and is designed for field enclosure
installation in conjunction with an FB-ET module.
This user manual describes the start-up procedures as:
– Installation of the FB-DIAG⁄FF⁄…
– Selecting and configuring the application options
–Startup
1.2 Hardware and software requirements
– Installation of the DD, EDDL (DD5), or DTM file
– Foundation Fieldbus™ network
– Fieldbus host communication or asset management software capable of installing a
DD-type file
1.3 Hazardous locations
1.3.1 ATEX and IECEx special conditions for safe use
If the module is installed in a zone 2 hazardous area, it shall be housed in an enclosure that
is coded Ex nA, Ex e, Ex d or Ex p. If the module is installed in a zone 22 or 21 hazardous
area, it shall be housed in an enclosure that is coded Ex tD or Ex t. For some types of
enclosure, additional certification is required to permit the installation of the module within
the enclosure. Reference should be made to the enclosure certificate. The installer shall
ensure that the maximum ambient temperature of the module, when installed, is not
exceeded. If the module is installed in a non-hazardous area, the enclosure or location shall
provide suitable protection. This may be either by the use of an enclosure approved for use
in zones 2 or 22, or by meeting the following requirements:
– Non-metallic enclosures must be capable of withstanding the thermal endurance
requirements of IEC 60079-0 prior to impact and IP54 testing.

FB-DIAG⁄FF⁄…
4PHOENIX CONTACT 3228_en_A
– Any enclosure must be capable of withstanding an impact of 7J or the module is
otherwise protected from impact.
– The enclosure or location must provide an ingress protection of at least IP54.
– If exposed to sunlight, non-metallic enclosures must be capable of meeting the
requirements of IEC 60079-0 clause 26.10 regarding resistance to light.
When the module is mounted in a zoned area, live connection and disconnection of the
module from the rail is only permitted if the potentially explosive atmosphere is shown to be
absent.
1.3.2 CSA conditions for certification
This device is “open” type equipment that must be used within a suitable end-use system
enclosure. The suitability of the enclosure is subject to investigation by the “local authority
having jurisdiction” at the time of installation.

Installation
3228_en_A PHOENIX CONTACT 5
2 Installation
The FB-DIAG⁄FF⁄NC is supplied with a T-BUS connector. The FB-DIAG⁄FF⁄LI does not utilize
a T-BUS connector but connects via terminal block to a short-circuit protected trunk.
2.1 Mounting
1. Place the module onto the DIN rail from above. The upper holding keyway must be
hooked onto the top edge of the DIN rail.
2. Push the bottom of the module toward the DIN rail until the bottom foot snaps onto the
rail.
Figure 2-1 Installation
2.2 Connection
Figure 2-2 FB-DIAG⁄FF⁄LI block diagram
MAU
F+
F–
S
μC


FB-DIAG⁄FF⁄…
6PHOENIX CONTACT 3228_en_A
Figure 2-3 FB-DIAG⁄FF⁄NC block diagram
2.3 Typical installation
The FB-DIAG⁄FF⁄NC is intended to be installed with the Phoenix Contact modular device
coupler system. Installation of the FB-DIAG⁄FF⁄NC is to the right of an FB-ET trunk module
on a segment.
Figure 2-4 Typical installation of FB-DIAG⁄FF⁄NC
The FB-DIAG⁄FF⁄LI is intended for connection to a short-circuit protected spur, such as a
legacy device coupler.
MAU
F+ F– S
μC
TBUS


Installation
3228_en_A PHOENIX CONTACT 7
Figure 2-5 Typical installation of FB-DIAG⁄FF⁄LI
2.4 LED indicators
There are two green and one red LED on the FB-DIAG⁄FF⁄…. The LEDs provide low-level
indication depending on circumstances existing on the segment or by self-diagnostics of the
FB-DIAG⁄FF⁄….
All of the LEDs illuminate for 0.5 s upon initial startup. This shows that all LEDs are
functional. All flash rates are 50 ±2% duty factor at the respective flash rates.
If an error occurs, the LEDs will flash two full duty cycles before returning to the original
state, once the error has been removed.
For example:
–TheFB-DIAG⁄FF⁄… is joined to the network and communicating correctly. The PWR
LED and COMM LED are illuminated solid.
– The shield is shorted to T+ for a moment. The ERR LED flashes to indicate this error.
The ERR LED will flash for two cycles (2.8 Hz * 2) continuously, until the error is cleared.
– If a retransmit is detected, the LED will flash two times for each retransmit. For example,
if there are three retransmits, the LED flashes six times. At the time the error is cleared,
the COMM LED will flash for two additional cycles (1.4 Hz * 2)
Table 2-1 shows the LED reaction based on different states:

FB-DIAG⁄FF⁄…
8PHOENIX CONTACT 3228_en_A
An FB-DIAG⁄FF⁄… failure (non-flashing Err LED trigger event) will persist until the
FB-DIAG⁄FF⁄… is reset or power cycled. If the Err LED does not reset, contact the
manufacturer (see “Resetting diagnostic data alarms” on page 17).
Table 2-1 Diagnostic LEDs
LED label Color/status Function
PWR Solid green Power is present
Off Power is not present
DAT Solid green Communication link established
Flashing green Communication errors
ERR Solid red System error
Flashing red Diagnostic alarms are present
NOTE:
The FB-DIAG⁄FF⁄… is polarity sensitive. For the FB-DIAG⁄FF⁄LI, the plus terminal must be
wired to the positive conductor of the fieldbus cable. The wiring and power should all be
standard Foundation Fieldbus. The two green LEDs will be on if the FB-DIAG⁄FF⁄… is
wired properly and connected to an active fieldbus segment.
NOTE:
If the red LED is flashing after connecting power, either on the T-BUS connector
(FB-DIAG⁄FF⁄NC) or terminal block (FB-DIAG⁄FF⁄LI), be sure to reset the segment re-
transmits prior to initiating a commissioning report.

Operation
3228_en_A PHOENIX CONTACT 9
3Operation
3.1 Monitored parameters
The FB-DIAG⁄FF⁄… captures information for the following parameters. These can be
categorized as segment information or device data.
Segment information
The FB-DIAG⁄FF⁄… monitors:
–Segmentvoltage
– Shield short circuit
–Low-frequencynoise
– High-frequency noise
– Fieldbus frequency noise
– Lowest signal level
–Ambienttemperature
–Retransmits
– Number active devices
–LASaddress
– Device add drop
Device data
–Address
– Device tag (available in DTM automatically, or inserted by an operator in the EDDL)
– Fieldbus signal level
– Add/drop state
–Retransmits
– Trend assignment (available in DTM only)
3.2 Alarms

FB-DIAG⁄FF⁄…
10 PHOENIX CONTACT 3228_en_A
3.2.1 Standard alarms
Diagnostic alarms can be configured to monitor certain parameters.
3.2.2 Namur NE-107 alarms
The FB-DIAG⁄FF⁄… supports diagnostics per specification from the Fieldbus Foundation
consistent with those defined in NE-1071. The diagnostics are broken down into the
following four categories: maintenance, off-specification, check function and failure.
Maintenance
Although the output signal is valid, the wear reserve is nearly exhausted or a function will
soon be restricted due to operational conditions. For example, the build-up of deposits.
Off-specification
Off-specification means that the device is operating outside its specified range or an internal
diagnostic alarm indicates deviations from measured or set values due to internal problems
in the device or process characteristics. For example, bubbles forming in a flow meter or a
valve sticking.
Check function
Output signal is temporarily invalid (frozen) due to ongoing work on the device.
Failure
Output signal is invalid due to a malfunction in the field device or its peripherals.
Table 3-1 Default alarm settings
Parameter Default setting
Low voltage <12.0 V DC
High voltage >32.0 V DC
Retransmits/hour 10
Retransmits/day 100
Minimum fieldbus signal 150 mV
Maximum Foundation Fieldbus noise 35 mV
Maximum low-frequency noise 85 mV
Maximum high-frequency noise 85 mV
1Descriptions from Function Block Fieldbus Specification, Part 2: FF-891 FS 1.10

Operation
3228_en_A PHOENIX CONTACT 11
3.2.3 Field diagnostic alerts
All diagnostic alerts can be assigned to any of the four categories, masked or not mapped
at all. The configuration is designed to be very flexible. The FB-DIAG⁄FF⁄… is configured at
the factory with the following mapping.
Check boxes in the EDDL and DTM are available to select the parameter mapping of
diagnostic alerts.
Figure 3-1 “Maintenance” dialog box
For a Foundation Fieldbus host that does not support the alert mechanism, they can poll
“_Active” parameters to show field diagnostic conditions.
For more detail, please refer to Fieldbus Foundation Specification FF-891 available from
www.fieldbus.org.
Table 3-2 Default diagnostic alerts
Alert Parameter map
Maintenance Off
specification
Check function Failed
High voltage x
Low voltage x
Signal strength x
Low-frequency noise x
High-frequency noise x
Fieldbus frequency noise x
Sensor board fault x
Loss of communication between sensor
board and fieldbus communication board
x
Temperature x
Shield short circuit x
Retransmits per hour rate x
Retransmits per day rate x

FB-DIAG⁄FF⁄…
12 PHOENIX CONTACT 3228_en_A
3.3 Host support files
The FB-DIAG⁄FF⁄… can be configured and diagnostic information viewed with a Device
Type Manager (DTM), the IEC standard Electronic Device Description Language (EDDL) or
a legacy Device Description (DD). New host releases may have the FB-DIAG⁄FF⁄… support
files installed, but it is likely that they will need to be imported. Follow the host procedures
for importing new device files.
DTM files
Support files can be downloaded from Phoenixcontact.com by searching the order number
and clicking the “Downloads” tab.
EDDL or DD
Support files can be downloaded from www.Fieldbus.org/End user resources/registered
products. From the “Manufacture” drop-down menu, select Phoenix Contact. From the
“Category” drop-down menu, select Diagnostic.
Alternatively, go to Phoenixcontact.com, search for the order number, and click the
“Downloads” tab.
3.3.1 Viewing segment information
Segment information can be viewed utilizing whichever file type is desired.
Figure 3-2 Typical “Process Variable Summary” page showing an EDDL file

Operation
3228_en_A PHOENIX CONTACT 13
Figure 3-3 Typical “Process Variable Summary” page showing a DTM file
3.3.2 Viewing device information
Device information can be viewed utilizing whichever file type is desired.
With EDDL and older host user interfaces, only two devices can be displayed
simultaneously. The individual device can be selected by entering the address of the
device. A parameter with a list of the active devices is provided.
Figure 3-4 Sample “Individual Device Info” page for an EDDL file
The DTM operator interface provides a complete list of all the devices on the segment along
with their PD Tag.
Figure 3-5 Typical view of DTM devices

FB-DIAG⁄FF⁄…
14 PHOENIX CONTACT 3228_en_A
3.4 Setting alarm limits
Some parameters are pre-configured with default alarms (see Table 3-1).
Alarm limits can be viewed and edited utilizing whichever file type is desired.
Figure 3-6 Typical “Alarm Limits” page for EDDL file
Figure 3-7 Typical “Alarm Limits” page for DTM file
Factory defaults can be restored using the “Restart” parameter in the resource block. The
factory default does not mask any field diagnostic alerts and all priorities are set to 2.

Operation
3228_en_A PHOENIX CONTACT 15
3.5 Detecting and diagnosing an alert
If the FB-DIAG⁄FF⁄… detects an alert condition, the alarm will go out on the bus and the red
LED on the FB-DIAG⁄FF⁄… will flash. The operator may then go to the FDM user interface.
The “Diagnostic Variable Summary” page will indicate there is a problem.
Figure 3-8 Typical EDDL “Diagnostic Variable Summary” page
Figure 3-9 Typical DTM “Diagnostic Variable Summary” page
The “Diagnostic Variable Summary” page contains information about which alert is activate,
and information supporting the conditions for the alert, possible causes for the alert and
recommended actions to correct the alert.
EDDL and DTM alerts will sometimes include recommended actions.

FB-DIAG⁄FF⁄…
16 PHOENIX CONTACT 3228_en_A
Figure 3-10 Typical EDDL alert message with recommended actions
Figure 3-11 Typical DTM alert message with recommended actions