Eaton Crouse-hinds series User manual

MTL F809F-Plus
FOUNDATIONTM fieldbus diagnostics module
INM F809F-Plus Rev 3
Instruction manual
MTL fieldbus networks
DRAFT - 02 March 2017
March 2017

ii
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
DECLARATION OF CONFORMITY
A printed version of the Declaration of Conformity has been provided separately within the
original shipment of goods. However, you can find a copy of the latest version at -
http://www.mtl-inst.com/certificates

iii
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
CONTENTS
DECLARATION OF CONFORMITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iv - v
1 OVERVIEW ........................................................................1
1.1 Components and accessories ..............................................................1
2 INSTALLATION .....................................................................2
2.1 Mounting ...............................................................................2
2.2 Power requirements......................................................................3
2.3 Configuration of fieldbus communication segment ............................................3
2.4 Installation for communication on separate fieldbus segment ...................................4
2.4.1 Interconnection via carrier ...............................................................4
2.4.2 Interconnection via top connector .........................................................5
2.4.3 Fieldbus segment design rules............................................................6
2.4.4 Diagnostics module power supply.........................................................6
2.4.5 Diagnostics module segment termination ..................................................6
2.5 Ground Reference Switches ...............................................................6
3 CONFIGURATION ...................................................................7
3.1 Standard ...............................................................................7
3.2 F809F-Plus Configuration..................................................................7
4 BLOCK CONFIGURATION ............................................................8
4.1 Resource Block .......................................................................8-10
4.1.1 Diagnostic Bits .....................................................................10-11
4.1.2 Block errors...........................................................................11
4.1.3 Modes ...............................................................................11
4.2 Transducer Blocks.......................................................................12
4.2.1 Transducer Block Errors ................................................................12
4.2.2 Transducer Block Modes ................................................................12
4.2.3 Transducer Block Alarm Detection ........................................................13
4.2.4 System Transducer Block (SysTB) .....................................................13-15
4.2.4.1 System alarms ...................................................................16
4.2.4.2 Self test alarms ..................................................................16
4.2.4.3 Methods ........................................................................17
4.2.5 Segment Transducer Block (SegTB)....................................................17-20
4.2.5.1 SEGMENT_ALARMS - Descriptions and Corrective Actions ...........................21-22
4.2.5.2 DEVICE_ALARMS - Descriptions and Corrective Actions ................................22
4.2.5.3 DEVICE_ALERTS - Descriptions .....................................................22
4.3 Discrete Input Block .....................................................................23
4.3.1 Discrete Input Block Errors ..............................................................23
5 OPERATION AND MAINTENANCE ....................................................24
5.1 LED indicators..........................................................................24
5.2 FOUNDATIONTM fieldbus Information .........................................................24
5.2.1 Commissioning (Addressing) ............................................................24
5.3 Hardware Maintenance ..................................................................24
5.3.1 Communication/Power Check............................................................24
5.3.2 Resetting the Configuration (RESTART)....................................................24
5.4 Troubleshooting ........................................................................25
5.4.1 FOUNDATIONTM fieldbus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
5.4.2 Resource Block ........................................................................25
5.4.3 System and Segment Transducer Block Troubleshooting .....................................25
APPENDIX A: Troubleshooting Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-27

iv
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
GENERAL INFORMATION
NOTE
This manual applies to Diagnostic Module F809F-Plus version MT03. The version number is indicated on
the module’s side label.
For F809F versions MT01 and MT02, refer to instruction manuals INM F809F-1 or INM F809F-2C, which are
available to download from the MTL website.
Safety instructions for installation and operating personnel
These operating instructions contain basic safety instructions for installation, operation and maintenance and
servicing. Failure to comply with these instructions can endanger personnel, the plant and the environment.
Before installation/commissioning:
• Read the operating instructions.
• Give adequate training to the installation and operating personnel.
• Ensure that the contents of the operating instructions are fully understood by responsible personnel.
• The national installation and mounting regulations (e.g. EN 60079-14) apply.
When operating the devices:
•
Make the operating instructions available at the installation area (at all times).
• Observe safety instructions.
• Observe national safety and accident prevention regulations.
• Operate the equipment within its published specification.
• Servicing/maintenance work or repairs which are not described in the operating instructions must not be
performed without prior agreement with the manufacturer.
• Any damage may render hazardous-area protection null and void.
• No changes to the devices or components impairing their hazardous-area protection are permitted.
• The device may only be fitted and used if it is in an undamaged, dry and clean state.
If there are any points that remain unclear:
•
Contact your local Eaton Office
• Product and contact details are also available from the company website: http://www.mtl-inst.com
Consignes de sécurité pour le personnel d’installation et le personnel d’exploitation
Ces consignes d’exploitation renferment les consignes de sécurité de base pour l’installation, l’exploitation la mai
tenance et les services Ne pas se conformer à ces consignes peut mettre en danger le personnel, l’usine et
l’environnement.
Avant l’installation et la première mise en service :
• Lire les consignes d’exploitation
• Fournir la formation appropriée aux personnels d’installation, et d’exploitation
• S’assurer que le contenu des consignes d’exploitation est pleinement assimilé par le personnel responsable
• Appliquer les règlements nationaux en vigueur pour l’installation et le montage (par ex. NE 60079-14)

v
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
Au cours de l’exploitation des appareils:
•
Faire en sorte que les consignes d’exploitation soient à disposition sur la zone d’installation
(à tous moments)
• Observe safety instructions.
• Observer les consignes de sécurité.
• Observer les règlements nationaux de sécurité et de prévention des accidents
• Exploiter l’équipement dans les limites de sa spécification publiée
• Les travaux de service/maintenance ou les réparations non décrits dans les consignes ne doivent pas
être exécutés sans l’agrément préalable du fabricant.
• Tout endommagement peut rendre caduque la protection en zone dangereuse
• Aucune modification apportée à l’appareil ou aux composants, portant atteinte à leur protection en zone
dangereuse, ne sera autorisée
• L’appareil ne peut être utilisé que s’il se trouve dans un état non endommagé, sec et propre.
S’il reste quelques points à éclaircir :
•
Contactez votre bureau Eaton local
• Les détails sur les produits et les contacts sont également disponibles à partir du site de la compagnie
http://www.mtl-inst.com
NOTE
The F809F-Plus should only be fitted to a carrier whose low voltage DC power is derived
from a power supply compliant with EN61010 or EN60950 double or reinforced insulation.
The F809F-Plus has an extended operating temperature range. Cabling connected to it
should be rated in accordance with maximum and minimum ambient temperatures expected
FOR US AND CANADA:
THIS EQUIPMENT IS SUITABLE FOR USE IN CLASS1, DIVISION 2, GROUPS A, B, C, D AND CLASS 1, ZONE
2, GROUP IIC OR NON-HAZARDOUS LOCATIONS ONLY.
WARNING/AVERTISSEMENT
EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR
CLASS 1, DIVISION 2.
RISQUE D’EXPLOSION - LA SUBSTITUTION DE COMPOSANTS PEUT RENDRE CE MATERIEL
INACCEPTABLE POUR LES EMPLACEMENTS DE CLASS 1, DIVISION2
WARNING/AVERTISSEMENT
EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS
RISQUE D’EXPLOSION - AVANT DE DECONNECTER L’EQUIPEMENT, COUPER LE COURANT
OU S’ASSURER QUE L’EMPLACEMENT EST DESIGNE NON DANGEREUX.

vi
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
this page is left intentionally blank

1
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
1 OVERVIEW
The F809F-Plus Fieldbus Diagnostic Module is available as an option for use with 918x
Series, F800 Series and some F600 Series fieldbus power supplies. It plugs into a 918x,
F8xx or F6x8 Series power supply carrier, or an F8x8 diagnostic module carrier and
monitors the performance of each of the eight fieldbus segments, providing information
on the network health and capturing retransmissions between the fieldbus devices and
control system.
The parameters measured include the bulk power supply input voltage, temperature,
segment voltages and signal levels of all devices. Average and peak noise are measured
in each of three frequency bands. Additionally the monitor checks for correct bus
termination and for short-circuits between the fieldbus signal wires and cable shields.
Retransmissions are also measured. The measured physical layer parameters are used
to predict the corrective action required. This allows problems to be rectified before poor
network health results in devices being removed from the ‘live list’, which could affect
the operation of the plant. Measurements may alternatively be captured and sent to off-
site experts for interpretation.
The F809F-Plus is a FOUNDATION
TM
fieldbus device, and communicates with the host
control system via a fieldbus segment. This allows the network status and measured
parameters to be displayed in the instrument management software on the host control
system.
1.1 Components and accessories
This manual is designed to assist in the installation, configuration and maintenance of the
F809F-Plus Fieldbus Diagnostic Module version MT03 (see side label), as explained on
the opposite page under General Information.
For product specification see the EPS F809F-Plus data sheet.
Features of this version include:
• Superior immunity to noise on the ‘communicating’ segment – continues to report
diagnostic information in electrically noisy environments.
• Enhanced short-to-shield detection, including wider choice of ground reference
options and immunity to interference from mains-connected Emerson 375 and
475 communicators.
• Extended measurement range for fieldbus power supply voltage – compatible
with full range of MTL power supply types.
• Registered to Fieldbus Foundation ITK 6.0, including field diagnostic bits according
to NAMUR NE107 recommendations.
• Support for fully updated eEDDL and DTM user interfaces.
MTL F809F-Plus Diagnostics module

2
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
2 INSTALLATION
The F809F-Plus is designed for carrier mounting and may be mounted on any 918x,
MTL F8xx or F6x8 series carrier. See the MTL 918x, F8xx or F6x8 series power
supply or F8x8 carrier installation manual for details of how these carriers are
installed.
The F809F-Plus Fieldbus Diagnostic Monitor receives redundant power feeds
and connections to the eight monitored fieldbus segments via the carrier. The
diagnostic information is conveyed to the controlling host via a fieldbus segment
and the user has the choice of segment 1 or 8 (of the segments being monitored),
or a totally separate segment of their choosing. The segment chosen for
communication is configured using a plugin connector located on the front edge of
the module.
2.1 Mounting
Align the F809F-Plus module with the two multi-pin connectors* on the carrier and
hold it in place while tightening the two captive fixing screws.
NOTE
The fixing screws should be tightened to a minimum torque value of 1.2Nm, but
should not exceed a torque value of 1.5Nm.
To remove the F809F-Plus, support the module while unscrewing the two fixing
screws at its base. Lift the module off the carrier connector.
* A third connector is provided on the module for factory testing and firmware
upgrade. This connector, the largest of the three, is not used on the carrier and is
identified on the F809F-Plus side label. See Figure 2.1.
Figure 2.1: Unused connector
Figure 2.2: Configuration “comb”

3
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
2.2 Power requirements
An F809F-Plus module draws approximately 15mA from the communicating fieldbus
segment. This needs to be included when calculating the total design current
requirement for that segment.
2.3 Configuration of fieldbus communication segment
The communications segment that will be used is determined by configuring the
connector on the front face of the module. A 6-pin “comb”, supplied with the module,
is used to define the communication segment by inserting it one of two ways into the
connector (see Figure 2-2), or omitting it altogether.
The F809F-Plus is supplied pre-configured to communicate on segment 8 (eight) of the
monitored fieldbus segments.
The communication segment can be changed “in the field” by a simple change to the
connector on the front face.
1. Remove the protective cap from the top of the fieldbus module by squeezing
the ends. See Figure 2-3.
2. Loosen the six screws in the connector.
3. Remove the “comb” from the connector.
4. (a) For communication on segment 8 (as supplied)
Place the “comb” in the connector, as shown (Figure 2-2), so that the
number “8” is visible on the top (right) surface.
(b) For communication on segment 1
Place the “comb” in the connector so that the number “1” is visible on
top (right) surface.
(c) For communication on a separate segment
No comb is required.
5. If the comb is being used, tighten the six screws to retain it.
6. Replace the protective cap.
Figure 2.3: Removing protective cap

4
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
2.4 Installation for communication on separate fieldbus segment
If a separate fieldbus segment is the chosen option, then it can communicate the
diagnostic data via the top connector on the F809F-Plus or, in some cases, through
dedicated connectors on the carrier. The table below shows which carriers (by batch
code) provide this option.
Carrier type Diagnostic data connection options
via carrier via top connector
F618D-CL All All
F860-CA None All
F880-CR-xx None All
F880-CL-xx None All
F880-CA-xx 0727 or later All
F888-CA-xx All All
F890-CA-xx 0727 or later All
F892-CA-xx 0727 or later All
F898-CA-xx
918x-CA-Px
All
All
All
All
2.4.1 Interconnection via carrier
Figure 2-4 shows how a dedicated diagnostic segment, comprising multiple F6x8, F8xx or 918x
carriers, is interlinked, powered and terminated. Where carriers are installed in vertical columns,
connect the H1+, H1- and S terminals of adjacent carriers as shown.
Figure 2.4: Carrier linking

5
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
2.4.2 Interconnection via top connector
Figure 2-5 shows how a dedicated diagnostic segment comprising multiple F8xx
carriers is interlinked and terminated.
The fieldbus spur is connected to the two middle terminals in the top connector -
see Figures 2-2 and 2-6.





































Figure 2.5: Module connector linking
Figure 2.6: Connector wiring

6
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
2.4.3 Fieldbus segment design rules
A segment may support a number of F809F-Plus modules. The actual number is based
on a number of factors:
• the logical device limit of the host,
• the fieldbus power supply capacity,
• operational constraints such as bandwidth
• the overall impact on the system if that diagnostic segment should be lost.
Shielded, twisted-pair cable, complying with FOUNDATION
TM
fieldbus ‘Type A’ construction
is recommended for the diagnostic segment. Unshielded instrument cable is suitable for
short interconnections between adjacent carriers.
2.4.4 Diagnostics module power supply
The diagnostic segment must be powered by a conditioned fieldbus power supply (see
Figure 2-4 & 2-5) that will provide a voltage in the range 9–32V DC at each F809F-Plus
fieldbus diagnostic module. This power supply may be either simplex or redundant,
depending on the application, and be capable of providing sufficient current for the entire
diagnostic segment.
Each F809F-Plus module draws approximately 15mA, so a segment comprising 10
F809F-Plus modules, for example, will require an output current of at least 150mA.
Suitable multi-segment redundant fieldbus power supplies include MTL 918x-x1 and
F8x0. Type FPS-I may be selected where a single-segment redundant power supply is
preferred. Alternatively, if a non-redundant power supply is acceptable, suitable types
include F101, F102 and FPS-DT.
2.4.5 Diagnostics module segment termination
As with all Fieldbus segments, the one used for the diagnostic data must be terminated
at both ends to maintain the bus impedance within FOUNDATION
TM
fieldbus limits. When
interconnections are via the carrier, a terminator must be connected between the H1+
and H1- terminals of the diagnostic bus connector at the far end of the segment (see
Figure 2-4). Suitable terminators for this are MTL type FBT1-IS or F100.
When F809F-Plus modules are interconnected by means of the top connector, it is
preferable to connect each module to the spur of a Megablock device coupler. This
protects the diagnostic segment against a short-circuit on any spur. A Megablock with
a built-in terminator should be selected. Termination of the bus at the host end may be
provided either by an integrated terminator within the power supply or by means of a
separate terminator.
2.5 Ground Reference Switches
Switches are provided on the side of the F809F-Plus module to select different grounding
options - see Figure 2.7. The switch positions are chosen according to the type of MTL
Fieldbus Power Supply with which the F809F-Plus is being used, as described in the
following table:
Switch A position Switch B position Fieldbus power supply type
0 0 Invalid configuration - do not select
0 1 All F8xx Series except F860
1 0 F618D
1 1 All 918x Series and F860

7
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
A separate case ground terminal is provided (Figure 2-8) to enable the case of the module
to be linked to a ground terminal on the circuit board.
3 CONFIGURATION
3.1 Standard
Each FOUNDATION
TM
fieldbus configuration tool or host system has a different way of
displaying and performing configurations. Some will use Device Descriptions (DDs)
and DD Methods to make configuration and displaying of data consistent across host
platforms.
Refer to the fieldbus control system’s documentation to perform configuration changes
using a FOUNDATION
TM
fieldbus host or configuration tool.
The function of the F809F-Plus is to provide diagnostic data, therefore configuration
changes can be made with the MODE_BLK.ACTUAL in AUTO, MANUAL or Out Of
Service (OOS) mode.
NOTE
Fieldbus devices used in process applications usually have to be set to OOS
mode before making configuration changes.
3.2 F809F-Plus Configuration
The F809F-Plus is available with the standard configuration setting. The configuration
settings and block configuration may be changed in the field with the FOUNDATION
TM
fieldbus host or a configuration tool.
Figure 2.7: Ground reference switches Figure 2.8: Case ground terminal

8
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
4 BLOCK CONFIGURATION
4.1 Resource Block
The resource block defines the physical resources of the device including type of
measurement, memory, etc. The resource block also defines functionality, such as shed
times, that is common across multiple blocks. The block has no linkable inputs or outputs
and it performs memory-level diagnostics.
Table 4.1: Resource block parameters
Number Parameter Description
00 BLOCK
01 ST_REV
The revision level of the static data associated with the function block.
02 TAG_DESC
03 STRATEGY
The strategy field can be used to identify grouping of blocks.
04 ALERT_KEY The identification number of the plant unit.
05 MODE_BLK The ACTUAL, TARGET, PERMITTED, and NORMAL modes of the block. For further
description, see the Mode parameter formal model in FF-890.
06 BLOCK_ERR This parameter reflects the error status associated with the hardware or software
components associated with a block. Multiple errors may be shown. For a list of
enumeration values, see FF-890, Block_Err formal model.
07 RS_STATE State of the function block application state machine. For a list of enumeration values,
see FF-890.
08 TEST_RW Read/write test parameter - used only for conformance testing.
09 DD_RESOURCE String identifying the tag of the resource which contains the Device Description for the
resource.
10 MANUFAC_ID Manufacturer identification number - used by an interface device to locate the DD file for
the resource.
11 DEV_TYPE Manufacturer’s model number associated with the resource - used by interface devices
to locate the DD file for the resource.
12 DEV_REV Manufacturer revision number associated with the resource - used by an interface device
to locate the DD file for the resource.
13 DD_REV Revision of the DD associated with the resource - used by the interface device to locate
the DD file for the resource.
14 GRANT_DENY Options for controlling access of host computer and local control panels to operating,
tuning and alarm parameters of the block.
15 HARD_TYPES The types of hardware available as channel numbers. The supported hardware type is:
SCALAR_INPUT
16 RESTART Allows a manual restart to be initiated. See also Section 5.4.2
17 FEATURES Used to show supported resource block options. The supported features are: SOFT_
WRITE_LOCK_SUPPORT and REPORTS.
18 FEATURE_SEL Used to select resource block options.
19 CYCLE_TYPE Identifies the block execution methods available for this resource. The supported cycle
types are: SCHEDULED, and COMPLETION_OF_BLOCK_EXECUTION.
20 CYCLE_SEL Used to select the block execution method for this resource.
21 MIN_CYCLE_T Time duration of the shortest cycle interval of which the resource is capable.
22 MEMORY_SIZE Available configuration memory in the empty resource. To be checked before attempting
a download.
23 NV_CYCLE_T Minimum time interval specified by the manufacturer for writing copies of NV parameters
to non-volatile memory. Zero means it will never be automatically copied. At the end
of NV_CYCLE_T, only those parameters which have changed need to be updated in
NVRAM.
24 FREE_SPACE Percent of memory available for further configuration. Zero in preconfigured resource.
25 FREE_TIME Percent of the block processing time that is free to process additional blocks.
26 SHED_RCAS Time duration at which to give up on computer writes to function block RCas locations.
Shed from RCas will never happen when SHED_RCAS = 0.
27 SHED_ROUT Time duration at which to give up on computer writes to function block ROut locations.
Shed from ROut will never happen when SHED_ROUT = 0.
28 FAULT_STATE Condition set by loss of communication to an output block, fault promoted to an output
block or physical contact. When faultstate condition is set, then output function blocks
will perform their FSTATE actions.
continued

9
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
29 SET_FSTATE Allows the FAIL_SAFE condition to be manually initiated by selecting Set.
30 CLR_FSTATE Writing a Clear to this parameter will clear the device FAIL_SAFE if the field condition has
cleared.
31 MAX_NOTIFY Maximum number of unconfirmed notify messages possible.
32 LIM_NOTIFY Maximum number of unconfirmed alert notify messages allowed.
33 CONFIRM_TIME The time the resource will wait for confirmation of receipt of a report before trying again.
Retry will not happen when CONFIRM_TIME=0.
34 WRITE_LOCK If set, all writes to static and non-volatile parameters are prohibited, except to clear
WRITE_LOCK. Block inputs will continue to be updated.
35 UPDATE_EVT This alert is generated by any change to the static data.
36 BLOCK_ALM The BLOCK_ALM is used for all configuration, hardware, connection failure or system
problems in the block. The cause of the alert is entered in the subcode field. The first
alert to become active will set the Active status in the Status attribute. As soon as the
Unreported status is cleared by the alert reporting task, another block alert may be
reported without clearing the Active status, if the subcode has changed.
37 ALARM_SUM The current alert status, unacknowledged states, unreported states, and disabled states of
the alarms associated with the function block.
38 ACK_OPTION Selection of whether alarms oscillated with the block will be automatically acknowledged.
39 WRITE_PRI Priority of the alarm generated by clearing the write lock.
40 WRITE_ALM This alert is generated if the write lock parameter is cleared.
41 ITK_VER Major revision number of the interoperability test case used in certifying this device as
interoperable. The format and range are controlled by the Fieldbus FOUNDATIONTM.
42 FD_VER The major version of the Field Diagnostics specification used for the development of this
device.
43 FD_FAIL_ACTIVE This parameter reflects the error conditions that are being detected as active as selected
for the 'Failed' category. It is a bit string, so that multiple conditions may be shown.
44 FD_OFFSPEC_ACTIVE This parameter reflects the error conditions that are being detected as active as selected
for the 'Off Specification' category. It is a bit string, so that multiple conditions may be
shown.
45 FD_MAINT_ACTIVE This parameter reflects the error conditions that are being detected as active as selected
for the 'Maintenance' category. It is a bit string, so that multiple conditions may be shown.
46 FD_CHECK_ACTIVE This parameter reflects the error conditions that are being detected as active as selected
for the 'Check Function' category. It is a bit string, so that multiple conditions may be
shown.
47 FD_FAIL_MAP This parameter enables or disables conditions to be detected as active for the 'Failed'
category
48 FD_OFFSPEC_MAP This parameter enables or disables conditions to be detected as active for the 'Off
Specification' category
49 FD_MAINT_MAP This parameter enables or disables conditions to be detected as active for the
'Maintenance' category
50 FD_CHECK_MAP This parameter enables or disables conditions to be detected as active for the 'Check
Function' category
51 FD_FAIL_MASK This parameter is used to suppress any single or multiple conditions that are active, in the
'Failed' category, from being broadcasted through the Alarm parameter.
52 FD_OFFSPEC_MASK This parameter is used to suppress any single or multiple conditions that are active, in the
'Off Specification' category, from being broadcasted through the Alarm parameter.
53 FD_MAINT_MASK This parameter is used to suppress any single or multiple conditions that are active, in the
'Maintenance' category, from being broadcasted through the Alarm parameter.
54 FD_CHECK_MASK This parameter is used to suppress any single or multiple conditions that are active, in the
'Check Function' category, from being broadcasted through the Alarm parameter.
55 FD_FAIL_ALM This parameter is used to broadcast a change of an unmasked 'Failed' condition.
56 FD_OFFSPEC_ALM This parameter is used to broadcast a change of an unmasked 'Off Specification' condition.
57 FD_MAINT_ALM This parameter is used to broadcast a change of an unmasked 'Maintenance' condition.
58 FD_CHECK_ALM This parameter is used to broadcast a change of an unmasked 'Check Function' condition.
59 FD_FAIL_PRI This parameter allows the user to specify the priority of the 'Failed' Alarm category.
60 FD_OFFSPEC_PRI This parameter allows the user to specify the priority of the 'Off Specification' Alarm
category.
61 FD_MAINT_PRI This parameter allows the user to specify the priority of the 'Maintenance' Alarm category.
62 FD_CHECK_PRI This parameter allows the user to specify the priority of the 'Check Function' Alarm
category.
continued

10
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
63 FD_SIMULATE When simulation is enabled the Field Diagnostics conditions are taken from 'Diagnostic
Simulate Value' otherwise the conditions are taken from 'Diagnostic Value'.
64 FD_RECOMMEN_ACT This parameter is a device enumerated summarization of the most severe condition or
conditions detected. The DD should describe by enumerated action, what should be done
to alleviate the condition or conditions.
65 IDENTIFICATION_
MEASUREMENT
(PRODUCT_ID, SERIAL_
NUMBER, HW_REVISION,
SOFTWARE_VERSION,
FIRMWARE_CRC)
Measurement product ID, serial number, hardware revision and software version.
View as hexadecimal number.
66 IDENTIFICATION_
FIELDBUS
(SERIAL_NUMBER, HW_
REVISION, SOFTWARE_
VERSION, FIRMWARE_
CRC)
Fieldbus serial number, hardware revision and software version.
View as hexadecimal number.
4.1.1 Diagnostic Bits
Diagnostic bits permit the aggregation of all device status and diagnostics so that a Host
system can integrate this information into its infrastructure.
Four alarm categories as defined by the NAMUR NE-107 specification, Failed, Off-
Specification, Maintenance and Check function share 11 conditions.
The mapping of these conditions is as follows:
Diagnostic
Bit
Condition Description
0CHECK (Fieldbus
Foundation defined
condition)
Set if any transducer block has a normal mode other than OOS and the Actual is not Auto
1“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 1
transducer block.
Set if any Segment / Device alarm bits are set within segment 1
2“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 2
transducer block.
Set if any Segment / Device alarm bits are set within segment 2
3“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 3
transducer block.
Set if any Segment / Device alarm bits are set within segment 3
4“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 4
transducer block.
Set if any Segment / Device alarm bits are set within segment 4
5“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 5
transducer block.
Set if any Segment / Device alarm bits are set within segment 5
6“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 6
transducer block.
Set if any Segment / Device alarm bits are set within segment 6
7“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 7
transducer block.
Set if any Segment / Device alarm bits are set within segment 7
continued

11
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
8“Device Needs
Maintenance Soon”
bit of the BLOCK_ERR
parameter within segment 8
transducer block.
Set if any Segment / Device alarm bits are set within segment 8
9“Device Needs
Maintenance Soon” bit of
the BLOCK_ERR parameter
for the system transducer
block.
Set if any System Alarm and Self-test fault alarms are set
10 Logical OR of the “Device
Needs Maintenance Soon”
bits of all 9 transducer
blocks
Set if any System, Segment, Device or Self-test alarms are set
4.1.2 Block errors
Table 4-2 lists all conditions in the BLOCK_ERR parameter, with conditions in bold
supported by the F809F-Plus.
Table 4.2: BLOCK_ERR conditions
Number Name and Description
0 Other
1Block Configuration Error
2Link Configuration Error
3Simulate Active
4Local Override
5Device Fault State Set
6Device Needs Maintenance Soon
7Input failure/process variable has bad status
8Output Failure
9Memory Failure
10 Lost Static Data: Static data that is stored in non-volatile
memory has been lost.
11 Lost NV Data
12 Readback Check Failed
13 Device Needs Maintenance Now
14 Power Up: The device was just powered-up.
15 OOS: The actual mode is out of service.
4.1.3 Modes
The resource block supports two modes of operation as defined by the MODE_BLK
parameter:
Automatic (Auto)
The block is processing its normal background memory checks. In this mode, changes
can be made to all configurable parameters.
Out of Service (OOS)
The block is not processing its tasks. The BLOCK_ERR parameter shows Out of Service.
In this mode, changes can be made to any configurable parameters. The target mode of
a block may be restricted to one or more of the supported modes.

12
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
4.2 Transducer Blocks
There are two types of transducer blocks that allow the user to view and manage the
channel information. These blocks are:
• System Transducer Block (SysTB) – see “System Transducer Block (SysTB)”
in Section 4.2.4.
• Segment Transducer Block (SegTB), one for each of the eight segments – see
“Segment Transducer Block (SegTB)” in Section 4.2.5.
These Transducer blocks contain specific diagnostic data.
4.2.1 Transducer Block Errors
The following conditions are reported in the BLOCK_ERR parameters. Conditions in
bold are supported in the transducer blocks.
Table 4.3: Block/Transducer error
BLOCK_ERR
Number Name and Description
0 Other
1Block configuration error
2Link configuration error
3Simulate active
4Local override
5Device fault state set
6Device needs maintenance soon
7Input failure
8Output failure
9Memory failure
10 Lost static data
11 Lost NV data
12 Readback check failed
13 Device needs maintenance now
14 Power up: The device was just powered up
15 Out of service: The actual mode is out of service
4.2.2 Transducer Block Modes
The transducer block supports three modes of operation:
Automatic (Auto)
The block outputs reflect the diagnostic measurement board inputs. In this mode,
changes can be made to all configurable parameters.
Out of Service (OOS)
The block is not processed. Channel outputs are not updated and the status is set to Bad:
Out of Service for each channel. The BLOCK_ERR parameter shows Out of Service.
In this mode, changes can be made to any configurable parameters. The target mode of a
block may be restricted to one or more of the supported modes.
Manual Mode
All Transducer blocks move into this mode if the Resource Block is in OOS mode.
The block outputs reflect the diagnostic measurement board inputs. In this mode
changes can be made to all configurable parameters.

13
INM F809F-Plus Rev 3
DRAFT - 02 March 2017 DRAFT - 02 March 2017
4.2.3 Transducer Block Alarm Detection
If any alarm (except the new and removed device alerts) is set within the Transducer
Block then the Needs Maintenance Soon Bit is set in the BLOCK_ERR parameter.
The regular monitoring by the control system of the BLOCK_ERR parameter can
be used to inform the right person of the alarm condition. Typically this will be the
instrument technician responsible for fieldbus network maintenance.
Additionally if any alarm is set in the Transducer Block then:
• The associated Segment Alarm DI Block PV_D will be set to 1.
• The associated Active diagnostic bit will be set to 1 (assuming that the
appropriate map bit is set).
By configuring the DI block in the fieldbus cyclic messaging the right person can be
informed of the alarm condition.
4.2.4 System Transducer Block (SysTB)
There is one SysTB in the F809F-Plus, which allows the user to view system and
self-test alarms together with the system power feed voltages and temperature.
The SysTB allows configuration of the time, the date and the segments monitored.
Additionally, for each device on each of the 8 monitored fielbus segments, the
re-transmission counter can be reset and device history data can be deleted from
within this block.

14
INM F809F-Plus Rev 3
DRAFT - 02 March 2017
Table 4.4: Measurement Transducer Block Parameters
Rel-
index Parameter Name Description Help Text
Default
alarm limit
0BLOCK_HEADER In the BLOCK_HEADER record of a
transducer block only the element
BLOCK_TAG is writable.
1ST_REV The revision level of the static data
associated with the function block.
2TAG_DESC The user description of the intended
application of the block.
3STRATEGY The strategy field can be used to identify
grouping of blocks.
4ALERT_KEY The identification number of the plant
unit.
5MODE_BLK The ACTUAL, TARGET, PERMITTED, and
NORMAL modes of the block. For further
description, see the Mode parameter
formal model in FF-890.
6BLOCK_ERR This parameter reflects the error status
associated with the hardware or software
components associated with a block.
Multiple errors may be shown. For a list
of enumeration values, see FF-890,
Block_Err formal model.
7UPDATE_EVT Update Event
8BLOCK_ALM Block Alarm
9TRANSDUCER_
DIRECTORY
Transducer Directory
10 TRANSDUCER_TYPE Transducer Type
11 XD_ERROR XD Error
12 COLLECTION_
DIRECTORY
Collection Directory
13 PRIMARY_VALUE_D
14 POWER_FEED_A_
VOLTAGE
Power Feed A Voltage
15 POWER_FEED_B_
VOLTAGE
Power Feed B Voltage
16 MODULE_
TEMPERATURE
Module Temperature
17 SYSTEM_ALARMS System Alarms Module temperature high and high-
high alerts; Power feed B voltage
low-low, low, high and high-high
alerts; Power feed A voltage low-
low, low, high and high-high alerts;
18
LATCHING_ALARM_
ACKNOWLEDGE
Acknowledges all active alarms in
this transducer block.
19
ALARM_
ACKNOWLEDGE_
REQUIRED
New alarms require acknowledge-
ment.
20
SELF_TEST_FAULT_
ALARMS
Self Test Fault Alarms
21 SELF_TEST_LOG_1
22 SELF_TEST_LOG_2
23 POWER_FEED_A_
VOLTAGE_LIMITS
Power Feed A Voltage Limits The default values are limits for MTL
fieldbus power supply input voltages.
The user may reset to output limits of
bulk power supply taking into account
voltage drop in wiring at minimum and
maximum load.
Low Low =
19.2V
Low = 19.2V
High = 30V
High High = 30V
24 POWER_FEED_B_
VOLTAGE_LIMITS
Power Feed B Voltage Limits The default values are limits for MTL
fieldbus power supply input voltages.
The user may reset to output limits of
bulk power supply taking into account
voltage drop in wiring at minimum and
maximum load.
Low Low =
19.2V
Low = 19.2V
High = 30V
High High = 30V
continued