P+F Mux

PROCESS AUTOMATION
MANUAL
TEMPERATURE MULTI
INPUT DEVICE
TM-I
TEMPERATUR MULIT INPUT DEVICE
With regard to the supply of products, the current issue of the following document is appli-
cable: The General Terms of Delivery for Products and Services of the Electrical Industry,
published by the Central Association of the Electrical Industry (Zentralverband Elektrotech-
nik und Elektroindustrie (ZVEI) e.V.) in its most recent version as well as the supplementary
clause: "Expanded reservation of proprietorship"
Temperature Multi Input Device
1 Validity of these instruction manual/manual ......................................... 3
2 Symbols used ........................................................................................... 3
3 Introduction .............................................................................................. 4
4 Instruction Manual ................................................................................... 5

4.1 Intended Use ........................................................................................................... 5
4.2 Marking .................................................................................................................... 6
4.3 Ambient Conditions ................................................................................................ 6
4.4 Mounting and Dismounting ................................................................................... 6
4.4.1 Mounting and Dismounting of F2D0-TI-Ex8.FF.*:* ................................................... 6
4.4.2 Mounting and Dismounting of RD0-TI-Ex8.FF.* ....................................................... 7
4.5 Installation and Commissioning ........................................................................... 7
4.5.1 Installation in Category 2G (Zone 1) ......................................................................... 8
4.5.2 Installation in Category 3G (Zone 2) and safe areas ................................................ 9
4.5.3 Use as Intrinsically Safe Apparatus ........................................................................ 10
4.5.4 Use as Associated Apparatus ................................................................................. 10
4.5.5 Use as non-arcing Apparatus "nA" ......................................................................... 10
4.5.6 Commissioning the TM-I Device ............................................................................. 11
4.5.7 Installation and Commissioning of RD0-TI-Ex8.FF.* .............................................. 12
4.5.8 Installation and Commissioning of F2D0-TI-Ex8.FF.*.* .......................................... 12
4.6 Handling of the Cable Glands .............................................................................. 15
4.6.1 Handling F*D0-TI-Ex8.FF.CG Cable Glands .......................................................... 15
4.6.2 Handling the F*D0-TI-Ex8.FF.CGB and F*D0-TI-Ex8.FF.CGS Cable Gland ......... 16
4.7 Grounding and Shielding of the TM-I Device ..................................................... 17
4.8 Repair and maintenance ...................................................................................... 17
4.9 Fault elimination ................................................................................................... 17
4.10 Disposal ................................................................................................................. 17
5 Installation .............................................................................................. 18
5.1 Electrical Connection ........................................................................................... 18
5.1.1 Sensors .................................................................................................................. 18
5.1.2 Fieldbus and Shield Connection ............................................................................. 18
5.2 DIP Switches ......................................................................................................... 18
6 Configuration .......................................................................................... 19
6.1 Introduction ........................................................................................................... 19
6.2 Block Interaction and Channel Mapping ............................................................ 19
6.3 Identification, Device ID, PD Tag ......................................................................... 20
6.4 Getting Started ...................................................................................................... 20
6.5 Sensor Block Configuration ................................................................................ 21
6.5.1 Measurement Data Flow ......................................................................................... 21
6.5.2 Sensor Type ........................................................................................................... 22
6.5.3 Sensor Wiring and Wire Resistance ....................................................................... 22
6.5.4 Measurement Unit .................................................................................................. 22
6.5.5 Filtering ................................................................................................................... 22
11/2008 132328
6.5.6 Sensor Diagnosis .................................................................................................... 22

6.5.7 Cold Junction Compensation .................................................................................. 23
Subject to reasonable modifications due to technical advances. Copyright Pepperl+Fuchs, Printed in Germany
Pepperl+Fuchs Group • Tel.: Germany +49-621-776-0 • USA +1-330-4253555 • Singapore +65-67-799091 • Internet www.pepperl-fuchs.com 1
6.5.8 User Calibration ...................................................................................................... 23

6.5.9 Non-functional Parameters ..................................................................................... 24
6.5.10 Block Mode ............................................................................................................. 24
6.6 Concentrator Block Configuration ...................................................................... 24
6.6.1 Body Temperature .................................................................................................. 24
6.6.2 EMC Filter ...............................................................................................................25
6.6.3 Block Mode ............................................................................................................. 25
6.7 AI and MAI Block Configuration .......................................................................... 25
7 Operation ................................................................................................ 26
7.1 Primary Value Status ............................................................................................ 26
7.2 Body Temperature Status .................................................................................... 26
7.3 Device Self-diagnosis ........................................................................................... 26
7.4 Alarms .................................................................................................................... 26
8 Error Detection and Problem Remedy ................................................. 28

8.1 LED Indications ..................................................................................................... 28
8.2 Resource Block ..................................................................................................... 29
8.3 Sensor Block ......................................................................................................... 29
8.4 Concentrator Block ............................................................................................... 31
8.5 AI Function Blocks ............................................................................................... 32
8.6 MAI Function Block .............................................................................................. 33
8.7 Diagnostic Summary ............................................................................................ 35
9 Block Descriptions ................................................................................ 36

9.1 Resource Block (RB) ............................................................................................ 36
9.2 Analog Input Function Block (AI) ........................................................................ 38
9.3 Multiple Analog Input Function Block (MAI) ...................................................... 40
9.4 TI_SENS Sensor Blocks (TIS) .............................................................................. 40
9.5 Concentrator Block (TIC) ..................................................................................... 43
10 List of Tables .......................................................................................... 45
11 List of Figures ........................................................................................ 46

11/2008 132328
2 Pepperl+Fuchs Group • Tel.: Germany +49-621-776-0 • USA +1-330-4253555 • Singapore +65-67-799091 • Internet www.pepperl-fuchs.com
1 Validity of these instruction manual/manual
Pepperl+Fuchs offers three different types of Temperature Multi Input Devices:

• F2D0-TI-Ex8.FF.*:* in a IP 67 housing for panel mounting.
• RD0-TI-Ex8.FF.* for mounting on a 35-mm DIN rail in accordance with EN 50 022.
This manual applies to all types.
The manufacturer of the product, Pepperl+Fuchs GmbH in D-68301 Mannheim, has
a certified quality assurance program in accordance with ISO 9001.
ISO9001
A corresponding declaration of conformity may be requested from the

manufacturer.
2 Symbols used
This symbol warns of a danger.

In the event the warning is ignored, the consequences may range from
personal injury to death or from damage to equipment to destruction.
This symbol warns of a possible fault.

Failure to observe the instructions given in this warning may result in
the device and any facilities or systems connected to it developing a
fault or even failing completely.
This symbol draws your attention to important information.

11/2008 132328
3 Introduction
This manual describes the Pepperl+Fuchs FOUNDATION Fieldbus version of the

Temperature Multi Input Device (TM-I Device) for universal temperature measure-
ment, voltage and resistance input.
This manual shall allow the user to install, start, parameterize and operate the Pep-
perl+Fuchs TM-I Device. In addition it provides all necessary information about status/
error messages, device safety and monitoring functions as well as fault diagnosis and
fault elimination.
Capter 6 provides in-depth information about configuration of the Pepperl+Fuchs de-
vice specific transducer blocks since they contain device and manufacturer specific
functionality. The Resource, AI and MAI blocks and their use are documented by the
control system.
The manual assumes the user has technical knowledge and experience in the areas
of FOUNDATION Fieldbus, explosion protection, as well as planning, projecting and
installing FOUNDATION Fieldbus systems. It does not provide an introduction to
FOUNDATION Fieldbus or explosion protection for inexperienced users. Please refer
to other information sources if required.
11/2008 132328
4 Instruction Manual
These instructions apply in conjunction with the respective data sheets and EC-type-
examination certificate. You can access the documents at www.pepperl-fuchs.com.
The operator of the system bears the responsibility in terms of planning,

mounting, commissioning, operation and maintenance, especially in
conjunction with applications in hazardous areas.
4.1 Intended Use
The 8 channel TM-I Device transfers signals from resistance temperature measuring
sensors (RTD’s), thermocouples, resistance and millivolt signals via FOUNDATION
Fieldbus. Each channel could be configured independently.
The TM-I Device can be used for FOUNDATION Fieldbus H1 bus that use the phys-
ical layout in accordance with IEC 61158-2/ISA-S50.02-1992.
The TM-I Device may be installed in category 2G (Zone 1) or category 3G (Zone 2)
of a hazardous area.
For category 2G (Zone 1) applications the type of protection is "Intrinsic Safety". The
associated field devices could operate in a category 1G (Zone 0) or category 1D
(Zone 20) location.
For category 3G (Zone 2) applications the type of protection is EEx nA. The TM-I De-
vice could be connected to non-intrinsically safe H1 segment. Independent of the type
of protection of the H1 bus the inputs remains intrinsically safe.
The EC-Type Examination certificate and the data sheet are considered as an integral
part of this instruction manual. The data sheet contains the electrical data of the EC-
Type Examination certificate.
TM-I Devices that are operated in general electrical systems must not
thereafter be operated in electrical systems that are connected in haz-
ardous areas.
Laws and/or regulations governing the use or intended usage goal must be observed.
TM-I Devices are only approved for proper professional usage in accordance with the
intended purposes. Improper handling will void any claim made under the warranty
and any manufacturer's liability.
Protection of operating personnel and the system is not ensured if the
module is not used in accordance with its intended purpose.
The device can only be operated by trained professionals in accordance with the
11/2008 132328
available instruction manual.
4.2 Marking
TM-I Devices are identified by:

F2D0-TI-Ex8.FF.*:* RD0-TI-Ex8.FF.*
Pepperl + Fuchs Pepperl + Fuchs
68301 Mannheim, Germany 68301 Mannheim, Germay
F2D0-TI-Ex8.FF.*:* RD0-TI-Ex8.FF.*:*
PTB 03 ATEX 2237
¬ II 2 (1G/D) Ex ia IIC T4
¬ II (1) GD [Ex ia] IIC
¬ II 3 G Ex ic IIC T4
¬ II (3) GD [Ex ic] IIC
PTB 03 ATEX 2238 X
¬ II 3 G Ex nA II T4
¬ II 3 G Ex nL II T4
¬ II (3) G [Ex nL] IIC
Table 4.1: Marking of the Temperature Multi Input Device
4.3 Ambient Conditions
For the ambient temperature range, please refer to the respective data sheet.
4.4 Mounting and Dismounting
Mounting, dismounting, installation and commissioning must only be performed by

specialist who are trained specifically for this purpose.
Recognized rules of the technology and setup requirements must be maintained dur-
ing mounting and dismounting. Especially for tasks on electrical systems, special
safety requirements must be observed. Special attention must be paid to the following
points:
1. Has the TM-I Device been installed in accordance with specifications?
2. Is the TM-I Device free of damage?
3. Is IP protection ensured?
4. Are the screws tightened securely?
Plastic cable glands must be protected against mechanical force.
The Device has to be protected against electro static charge.
4.4.1 Mounting and Dismounting of F2D0-TI-Ex8.FF.*:*
F2D0-TI-Ex8.FF.*.*
The housing of TM-I Device F2D0-TI-Ex8.FF.*:* reaches the degree of protection
IP67. It is intended for panel mounting. 2 screws with a diameter of 6 mm should be
used for mounting. The mounting material should be selected according to the nature
of the sub-surface (the wall). When selecting mounting material, care must be taken
that it will ensure a secure fastening.
11/2008 132328
4.4.2 Mounting and Dismounting of RD0-TI-Ex8.FF.*

TM-I Device RD0-TI-Ex8.FF.* is designed for mounting on a 35-mm DIN rail in accor-
dance with EN 50 022 and must be protected against electro static discharge.
The Device must be mounted inside a housing that corresponds to at least degree of
protection
• IP20 in accordance with IEC 60529 for category 2G (Zone 1) application. The hous-
ing must be suitable for this application.
• IP54 in accordance with IEC 60529 for category 3G (Zone 2) application. The hous-
ing must be suitable for this application.
Housings of light alloy must not contain more then 6% of magnesium in

total weight.
Plastic housing must be designed in accordance with IEC 60079-0 or

need to be protected against electro static charge.
4.5 Installation and Commissioning
The Temperature Multiplexer meets the requirements of the Foundation Fieldbus

physical layer profile 111 and 511 as well as the requirements for non IS fieldbus seg-
ments in acc. with IEC 61158-2/ISA-S50.02-1992.
The TM-I Device has to be installed according to its designation in Zones 1 or 2.
11/2008 132328
Host Power Host Power

Host Supply
Host Supply
Safe
area
Cartegory 1 Cartegory 2G Cartegory 3G
Zone 0 Zone 1 Zone 2
Figure 4.1: Possibilities of installation

In Zone 1 the fieldbus must be intrinsically safe in accordance with the FISCO or En-
tity model. Is the TM-I Device mounted in Zone 2 it is not required to have an intrinsi-
cally safe fieldbus. In this case the TM-I Device works as an associated apparatus.
The EC-type-examination certificate or the statement of conformity

must be observed. It is especially important to maintain any „special
conditions“ that may be indicated.
4.5.1 Installation in Category 2G (Zone 1)

If the TM-I Device is installed in Zone 1 environments, the fieldbus has to be powered
intrinsically safe. A suitable fieldbus power supply has to be certified according to the
Entity or the FISCO model (IEC 60079 part 27). For the marking of the TM-I Device
please refer to Table 4.1 on page 6.
When using intrinsically safe analog input circuits in the Dust Ex Area 'D' only appro-
priate certificated field devices must be connected.
When installing intrinsically safe fieldbus segments, EN 60079-14/IEC 60079-14 must
be observed. For the interconnection of intrinsic safe field devices with the TM-I De-
vice the maximum values in the meaning of explosion protection must be observed.
Only the certified analogue inputs are allowed, depending on the type of explosion
protection, to be installed in a category 1 (Zone 0) area.
For the Federal Republic of Germany, the „National Foreword“ of
11/2008 132328
DIN EN 60079-14/VDE 0165 Part 1 must also be observed.
4.5.2 Installation in Category 3G (Zone 2) and safe areas

The TM-I Device could be installed in a category 3G (Zone 2) location.
In Zone 2 environment or safe areas the TM-I Device is normally powered by a non
intrinsically safe fieldbus power supply.
Only devices which are suitable for use in hazardous areas, category 3G (Zone 2) and
for the conditions at the place of installation must be installed in category 3G (Zone 2;
see declaration of conformity or statement of conformity)
The sensors connected to the inputs could be located
• in a category 3G (Zone 2) location
• in a category 1G (Zone 0) or 2G (Zone 1) location or
• in a category 1D (Zone 20) or 2D (Zone 21) location.
A segregation between the bus terminals and the input terminals is
required. To segregate the terminals of the fieldbus to the terminals of
the sensor inputs the segregation plate which is delivered with the TM-I
Device has to be installed on to the housing (see figure 4.2)
Segregation plate (required for Zone 2 installations)
Figure 4.2: Zone 2 installation

When connecting intrinsically safe field devices to the TM-I Device the respective
peak values as defined by explosion protection (proof of intrinsic safety) have to be
observed.
In Zone 2 the connection and disconnection of the internal terminal connectors as well
as the closing of circuits while the power is on is only permissible for reasons of in-
11/2008 132328
stallation, maintenance or repair.
The coincidence of an explosive atmosphere with installation, mainte-

nance or repair in Zone 2 is considered to be unlikely.
If a F2D0-TI-Ex8.FF.*:* with external connectors for the H1 bus mounted at the hous-
ing is in use, these connectors are allowed to be connected or disconnected only if
the H1 bus segment is not powered.
Only intrinsically safe analogue input circuits must be carried in Zone 1 or Zone 2 de-
pending on the ignition protection class.
Sensors mounted in a category 1D (Zone 20) or 2D (Zone 21) location
When using intrinsically safe analogue input circuits in the Dust Ex Area 'D' only ap-
propriate certificated field devices must be connected.
4.5.3 Use as Intrinsically Safe Apparatus
The current supply circuit in category 2G (Zone 1) must be intrinsically safe ia or ib.
The current supply circuit in category 3G (Zone 2) must be intrinsically safe ia, ib or ic.
Only intrinsically safe analogue input current circuits must be carried in Zone 0 or
Zone 1 depending on ignition protection class.
For interconnection of intrinsically safe field devices with the TM-I device take into ac-
count the respective maximum values in the sense of explosion protection (proof of
intrinsically safety).
4.5.4 Use as Associated Apparatus
Only intrinsically safe analogue input current circuits must be carried in Zone 0, Zone
1 or Zone 2 depending on ignition protection class.
4.5.5 Use as non-arcing Apparatus "nA"
Only devices which are suitable for use in hazardous areas, category 3G (Zone 2) and
for the conditions at the place of installation must be installed in category 3G (Zone 2;
see declaration of conformity or statement of conformity)
Only intrinsically safe analogue input current circuits must be carried in Zone 0, Zone
1 or Zone 2 depending on ignition protection class.
11/2008 132328
In Zone 2 the connection and disconnection of the internal terminal connectors as well
as the closing of circuits while the power is on is only permissible for reasons of in-
stallation, maintenance or repair.
The coincidence of an explosive atmosphere with installation, mainte-

nance or repair in Zone 2 is considered to be unlikely.
4.5.6 Commissioning the TM-I Device

When installing intrinsically safe fieldbus segments, EN 60079-14/IEC 60079-14 must
be observed. For the Federal Republic of Germany, the "National
Foreword“ of DIN EN 60079-14/VDE 0165 Part 1 must also be observed.
The DIP-switches for configuration can be activated even during operation.
The following identifying values must be observed when connecting fieldbus trans-
mission lines:
• The insulating length of the wire is 9 mm.
• Wire cross-section 0.2 mm² to 2.5 mm² or AWG 24 to 14.
• If a cable, consisting of fine wire is in use, the ends of the leads must be protected
(e. g. with core cable ends).
• Tightening torque of the screw terminals (if present) 0.4... 0.5 Nm.
• If a Thermocouple is connected to the terminals H and L of the TM-I Device, it is
not allowed to connect something to the terminals + and -.
• A fieldbus transmission line with an insulation voltage between the bus line and
shield of at least 500 V must be used for intrinsically safe fieldbus segments.
• The serial interface (see figure 4.3) is for parameterization only. It fulfills the type of
protection EEx ia IIC/IIB resp. EEx ib IIC/IIB with the following values:
- UO = 7.2 V
- IO = 29.1 mA
- PO = 52,38 mW
- Li = 0
- Ci = 0
- Characteristic curve: linear
- Only for connection of intrinsically safe circuits
- Ui = 5 V
Tasks for parameterization via the serial interface must only be performed by special-
ists who are specially trained and authorized by Pepperl+Fuchs.
11/2008 132328
4.5.7 Installation and Commissioning of RD0-TI-Ex8.FF.*

TM-I Device RD0-TI-Ex8.FF.*:* is mounted on a DIN rail in accordance with
EN 50 022.
LED comm. Separation, used when device

is installed in zone 2 and inputs
Service Interface LED channel error LED power Configuration in zone 1 or zone 0
DIN mounting rail

217 60
CH3
CH5
CH7
CH1
Bus
CH2
CH4
CH6
CH8
100
CH1 ... CH8 Bus

Mounting on
DIN rail
+ H L - + - S
Figure 4.3: Dimensions and pinout of RD0-TI-Ex8.FF.*:*

4.5.8 Installation and Commissioning of F2D0-TI-Ex8.FF.*.*
Tightening torques of the screwed connection of cable glands:
The tightening torques of cap nuts depends on the type cable used and must there-
fore be determined by the user. The cap nuts must be securely tightened. Tightening
the cap nuts too tight can have a negative effect on the protection method. The fol-
lowing figures should be taken as a rough guides:
Type Cap nut Lower part

F2D0-TI-Ex8.FF.*:*.CG 2.5 Nm 3.75 Nm
F2D0-TI-Ex8.FF.*:*.CGB 4.17 Nm 6.25 Nm
F2D0-TI-Ex8.FF.*:*.CGS 4.17 Nm 6.25 Nm
F2D0-TI-Ex8.FF.*:*.CGAB 22 Nm 28 Nm
11/2008 132328
Only permanently laid cables and lines must be inserted into the cable glands. For the
permissible cable diameters, please refer to the respective data sheet. The operator
must provide an appropriate strain-relief clamp (for example with a suitable cable
clamp). The mounting notes in chapter 4.4.1 must be observed.
258
228
84
9.5
240
for fixing
with screws
(57)
CH3
CH5
CH7
CH1
Bus
M6
CH2
CH4
CH6
CH8
114
X
Earthing point
20 8 Inputs, see tables Fieldbus IN
Figure 4.4: Dimensions and pinout of F2D0-TI-Ex8.FF.*:*

Cable glands that are not in use must be closed off with a corresponding plug or re-
placed by an appropriate screw plug. The required degree of protection (e. g. IP66)
must be observed.
The ambient temperature range can be restricted by the stop plug.
For examples of stop plugs and screw plugs, please refer to the respective data
sheets.
11/2008 132328
For metal housings in hazardous areas, a suitable potential equalization in accor-

dance with EN 60 079 is required. A grounding screw is provided on the housing for
this purpose. The connection must be designed to prevent lossening and must be pro-
tected against corrosion. Protection against corrosion can also be achieved by using
tinned cable plates, for example
Before closing the cover, a visual inspection must be performed to ensure that there
are no visible signs of damage on the cover seal. In the event of damage, the seal
must be replaced by an original seal.
The screws on the cover should be tightened with a torque of 2.5 Nm.
11/2008 132328
4.6 Handling of the Cable Glands
4.6.1 Handling F*D0-TI-Ex8.FF.CG Cable Glands

1. Strip the insulation of the cable up to about
120 mm
2. Loosen the cap nuts from the
TM-I Device and push it onto the cable.
Remove the seals from the TM-I Device as
well and push them onto the cable.
The following table will indicate when Seal 1
should be used and when it is not required:
Terminal
Type Seal 1
area [mm]
Step 1
M16 x 1.5 5 - 10 No
M20 x 1.5 5-8 Yes
M20 x 1.5 8 - 13 No
Seal 2 must always be used!
3. Push the seals that are used far enough over Seal 1
the cable so that the covering extends about
5 mm beyond the seal.
Seal 2
4. Insert the cable with the seals into the cable
gland of the TM-I Device. Then tighten the
cap nut.
Step 2
The tightening torques of cap nuts depends
on the cable typeis used and must therefore
be determined by the user.
As a rough guide for the FieldBarrier of type
F*D0-TI-Ex8.FF.CG you may use 2.5 Nm for
the cap nut and 3.75 Nm for the lower part.
Step 3
11/2008 132328
Step 4
4.6.2 Handling the F*D0-TI-Ex8.FF.CGB and F*D0-TI-Ex8.FF.CGS Cable Gland

1. Strip the insulation of the cable up to about
120 mm
2. Loosen the cap nuts from the
TM-I Device and push it onto the cable.
3. Remove the seals from the inside plastic part
as well and push them onto the cable.
Move the inside plastic part far enough over
Step 1
the cable that the covering is completely sur-
rounded by the seal.
The covering must not stand out over the end
of the plastic inner part.
4. Pull the shield over the inside plastic
part and shorten it to the correct length. The
shield should protrude about 3 to 4 mm bey-
ond the O-ring. Step 2
5. Insert the cable with the inside plastic part
into the lower part of the cable gland.
6. Then tighten the cap nut.
The tightening torques of cap nuts depends O-ring
on the cable typeis used and must therefore Inner plastic piece
be determined by the user.
As rough guides for FieldBarrier type Step 3
F*D0-TI-Ex8.FF.CGS you may use 4.17 Nm
for the cap nut and 6.25 Nm for the lower O-ring
part.
3 to 4 mm
Step 4
Step 5
11/2008 132328
Step 6
4.7 Grounding and Shielding of the TM-I Device
If the shield of the fieldbus transmission line is grounded for reasons

related to EMC, the appropriate sections of the FOUN DATION Fieldbus
Application Guide 31.35 bit/s Intrinsically Safe Systems must always be
observed.
The terminal S of the intrinsically safe fieldbus segment is

• in case of using the F2-version connected internally to the housing. The housing
should be connected to the potential equalization.
The housing of the F2-version must be connected to the potential

equalization in case of Category 2G (Zone 1) applications.
• in case of using the R version connected internally to the DIN rail. The DIN rail
should be connected to the cabinet and the cabinet should be connected to the po-
tential equalization.
Depending on this the shield is automatically connected to the potential equalization.
4.8 Repair and maintenance
The transmission behavior of the TM-I Device is stable even over long periods of time.
There is thus no need for regular adjustments or similar tasks. Maintenance is there-
fore not required.
4.9 Fault elimination
TM-I Devices that are operated in connection with hazardous areas must not be mod-
ified. If there is a defect, the TM-I Device must always be replaced.
Defective housing parts (for example cover seals) must be replaced only by original
parts. For detailed information please refer to the respective data sheet.
Tasks for eliminating malfunctions must only be performed by specialists who are
specially trained and authorized for the task.
4.10 Disposal
Disposal of the packaging and TM-I Device must only take place in accordance with
the requirements of the country in which the TM-I Device is installed.
The TM-I Device does not contain any batteries that must be disposed of separately
from the TM-I Device.
11/2008 132328
5 Installation
5.1 Electrical Connection
5.1.1 Sensors
Five types of sensors can be connected to each channel according to the following
scheme:
+ -
H L
RTD, 2-wire mV Millivolt
technology
+ L -
RTD, 3-wire
H L
technology Thermocouple
+ H L -
RTD, 4-wire
technology
Figure 5.1: Sensor connection

5.1.2 Fieldbus and Shield Connection
The TM-I Device provides a connector for the fieldbus cable. The device itself can op-
erate in both polarities. As not all FOUNDATION Fieldbus devices support polarity in-
dependent operation, it is recommended to wire all field devices in a consistent way.
5.2 DIP Switches
The device has eight DIP switches. Only DIP switch 1 and 2 are in use:
DIP Switches
Figure 5.2: DIP Switches

Switch 1: Simulation ON/OFF. With activated simulation, the sensor input
transferred from the transducer block to the function block can be
set by the control system independent from the hardware input of
an input channel. For safety reasons, it is recommended to set the
switch to OFF for normal operation.
Switch 2: Hardware write protection ON/OFF. Parameterization of the de-
vice via the bus is no longer possible when write protection is acti-
vated (setting ON).
11/2008 132328
6 Configuration
6.1 Introduction
The Pepperl+Fuchs Temperature Multi Input Device contains a resource block (like
any FOUNDATION Fieldbus Device), 9 transducer blocks (8 sensor and one concen-
trator block) and 9 standard FOUNDATION Fieldbus function blocks (8 AI and one
MAI block).
The sensor transducer blocks provide connection to the sensor hardware and the
possibility to configure the eight temperature sensors that can be connected to the de-
vice.
The concentrator transducer block provides convenient access to the most impor-
tant configuration options of all sensors as well as Device Description (DD) methods
for easy configuration of the device. This will increase the productivity at configuration
time. Additionally, it provides the device's body temperature and EMC filter settings.
It allows to view the values and diagnostics information of all channels at the same
time.
The Analog Input (AI) blocks are conform to the FOUNDATION Fieldbus specifica-
tion and can be used to build a FOUNDATION Fieldbus application and provides tem-
perature/voltage/resistance value depends on the configuration.
The Multiple Analog Input (MAI) block is conform to the FOUNDATION Fieldbus
specification and provides all eight sensor values in one block. Limits handling and
alarms are not implemented in this block. Also, the block consumes only one execu-
tion time so the FOUNDATION Fieldbus schedule time can be reduced. This block is
convenient if e.g. the device is used for monitoring purposes because it is very easy
to project and do not require configuration. Additionally, there is only one block to con-
figure instead of 8.
6.2 Block Interaction and Channel Mapping
Transducer blocks provide a measurement value to AI and MAI blocks. The connec-
tion between the blocks is configured via the „Channel“ parameter of the AI block
which chooses the sensor block to get the process data from.
Number Selected sensor Usable by

1 Sensor 1 AI
2 Sensor 2 AI
3 Sensor 3 AI
4 Sensor 4 AI
5 Sensor 5 AI
6 Sensor 6 AI
7 Sensor 7 AI
8 Sensor 8 AI
9 Sensor 1 to 8 MAI
11/2008 132328
10 Body temperature AI
Table 6.1: Channel Mapping
In addition to the measurement value, status information is conveyed to the AI and

MAI block which can be used to determine the measurement value's quality. For more
information, see chapter 7.1
AI
MAI block
block
1-8
8 * Sensor Body Sensor

values temperature
block
Concentrator 1-8
block
Figure 6.1: Block interaction
6.3 Identification, Device ID, PD Tag
Each FOUNDATION Fieldbus device has a unique device ID. The Pepperl+Fuchs
TM-I Device device ID is structured as follows:
Manufacturer Type Serial number

----------------------------------------------------------------
502B46 0003 12345678901234
The device ID "502B460003-12345678901234" contains the manufacturer identifica-

tion "502B46" for Pepperl+Fuchs and the type "0003" for Temperature Multiplexer.
The first two fields are the same for all Temperature Multi Input Device *-TI-Ex8.*.*.
The serial number is unique for each device, thus a differentiation can be made via
the serial number if several Temperature Multiplexers are connected to one FF-H1
segment. The serial number is also provided on the type label
• on the upper right side (RD0...)
• on the inner left side of the housing.
The PD tag contains as default a cleartext identification for the device and the last
nine characters of the serial number, e.g. „P+F TM-I Device 123456789".
6.4 Getting Started
Step 1 Integration of DD and capability file on the configuration tool

of the host system
11/2008 132328
To parameterize the Temperature Multiplexer in the online mode the as-
sociated device description (DD) must be imported in the engineering

tool used. For offline parameterization a capability file is available. Un-
less the manufacturer of the control system has made integration, you
will find the necessary files on the Internet at the P+F website.
Please consult the control system's manual for instructions on how to im-
port the files.
Step 2 Physical connection to the fieldbus, address assignment
Connect the fieldbus to the appropriate terminals of the device. If a pow-
er supply is connected, the device boots up and the LEDs show a kind
of „progress bar“. In the following the green power LED is on, the sensor
error LEDs are off. The COM LED is flashing until communication with a
link master is established.
Upon delivery, the device is configured to address 248. Most control sys-
tems automatically change the address after startup, so no user action
is required. Please refer to the control system's manual.
Step 3 Commissioning
First, the transducer blocks need to be configured. This can be ac-
complished in two ways:
• Executing the DD methods of the sensor or concentrator block. The
user is guided through the setup process
• By hand via the parameters described in the following sections.
Second, the AI/MAI blocks are configured according to the application's
needs.
Third, a schedule for the complete application is built and downloaded to
all involved devices. For a more detailed TM-I Device configuration de-
scription, please refer to the following sections.
6.5 Sensor Block Configuration
The concentrator and sensor block contains DD methods for convenient

and fast sensor configuration.
6.5.1 Measurement Data Flow

Figure 6.2 „Measurement data flow“ shows the internal data flow in the sensor block
and illustrates the block parameters' influence on measurement. These parameters
11/2008 132328
are explained in detail in the following sections.

TI_SENS Transducer Block
RTD_2_WIRE_OFFSET
CAL_POINT_HI RTD 2 Wire

CAL_POINT_LO Offset
CAL_MODE SENSOR_RANGE SENSOR_TYPE PRIMARY_VALUE_FTIME
Compensation
User Input Range First Order PRIMARY_

Linearisation
Calibration Check Lag VALUE
Sensor
Cold Junction
Compensation
CJC_SELECT
CONSTANT_CJC
Figure 6.2: Measurement dataflow

6.5.2 Sensor Type
The type of the sensor attached to the corresponding connector can be configured via
the „Sensor Type“ parameter. The device supports Thermocouples, RTD’s and bare
voltage or resistance measurement. For a list of supported sensors, please refer to
the data sheet of the device.
6.5.3 Sensor Wiring and Wire Resistance
For resistive sensors, a wiring method can be chosen by the „Sensor Connection“ pa-
rameter.
A maximum value of 50 Ω is allowed for the resistance of a sensor wire.
If 2-wire connection is chosen, it is possible to supply a constant wire resistance value
that is subtracted from the measured resistance via the „RTD 2 Wiring Resistance“
parameter. For all other sensor connection methods, the parameter is ignored. Al-
lowed value range is 0 to 100 Ω.
For voltage based sensors, the „Sensor Connection“ parameter is ignored (and thus
will not produce a configuration error if it is set to another value than 2-wire).
6.5.4 Measurement Unit
It is possible to select between several units for „Primary Value.Value“ via the „Sensor
Range.Units Index“ parameter. If an invalid unit is chosen for the sensor (e.g. „mV“
for a resistance based sensor), the „Configuration error“ bit is set in the
„BLOCK_ERR“ parameter.
6.5.5 Filtering
The „Primary Value.Value“ can be filtered by a first order lag. The filter time is select-
able between 0 s and 255 s via the „Primary Value Filtertime“ parameter. A value of
0 s disables filtering.
6.5.6 Sensor Diagnosis
It is possible to enable sensor monitoring for each sensor via the "Sensor Diagnostics"
parameter. If the sensor diagnosis indicates an sensor error, this will be reported in
the "BLOCK_ERR", "Sensor status" and "Transducer error" parameter. The "Primary
Value.Status" will be set to BAD.
11/2008 132328
The default adjustment is sensor diagnosis enabled. Pepperl+Fuchs recommends to

use the sensor diagnosis for normal operation.
6.5.7 Cold Junction Compensation

Thermocouple temperature sensors require cold-junction compensation for accurate
measurement. The Pepperl+Fuchs TM-I Device supports two methods of CJC com-
pensation:
• Internal: The cold junction temperature measured by a built-in temperature sen-
sors is used for compensation. This is the recommended method.
• Constant: The user can define a constant cold junction temperature that is used
for compensation.
The two methods can be selected via the "CJC select" parameter. If it is set to "Con-
stant", the TM-I Device uses the value in "CJC Constant" for compensation, the unit
is the same as for the "Primary Value.Value" parameter, which is specified by the
"Sensor Range.Units Index" parameter. If the unit is changed, the "CJC Constant" val-
ue is automatically converted to the new unit.
6.5.8 User Calibration

It is possible to perform a user calibration of the device. User calibrated measurement
can be enabled by writing "Calibration on" to the "Calibration Mode" parameter.
A user calibration is done by executing the following steps:
1. Select sensor type, wiring and sensor diagnosis. It may be necessary to turn off
sensor diagnosis if the device is connected to a calibration source that interferes
with the sensor monitoring.
2. Write "Execute user calibration" to "Calibration Mode" parameter.
3. The unit used for calibration can be read from "Calibration Units" parameter.
4. Wait until "Calibration state" reads "Wait first calibration point".
5. Connect first resistor / apply first calibration voltage. Please note that the limits that
can be read from "Calibration highest/lowest Point Limit" have to be taken into ac-
count.
6. Write the first calibration value to "Calibration Highest/Lowest Point" depending on
the applied physical value.
7. Wait until "Calibration state" reads "Wait HI/LO Calibration Point" depending on
whether high or low point was calibrated first.
8. Connect second resistor / apply second calibration voltage. Please note that the
limits that can be read from "Calibration highest/lowest Point Limit" and "Calibration
Minimum Span" have to be taken into account.
9. Write the second calibration value to "Calibration Highest/Lowest Point" depending
on the point that was calibrated first. Note that it is not possible to write two times
to the same parameter during the same calibration procedure to prevent errors.
10."Calibration state" now reads "OK".
11.Enable user calibrated measurement by writing "Calibration On" to "User calibra-
tion" parameter.
If "Calibration state" reads "Failure" during calibration, the following errors may have
11/2008 132328
happened:
• Sensor diagnosis is enabled and a sensor error was detected

• A higher value was written to "Calibration Lowest Point" than to "Calibration Highest
Point".
• Calibration span was too small (see parameter "Calibration Minimum Span" during
calibration)
• Values higher / lower than specified in "Calibration highest/lowest Point Limit" were
applied
Pepperl+Fuchs recommends not to use the user calibration feature, the

device is delivered with a suitable factory calibration.
6.5.9 Non-functional Parameters

The device offers several non-functional parameters (parameters that do not affect
the device's operation in any kind) to store additional information. These parameters
are:
• "Primary Value Type"
• "Sensor Serial No."
• "Sensor Calibration Method"
• "Sensor Calibration Location"
• "Sensor Calibration Date"
• "Sensor Calibration Who"
• "Calibration Location"
• "Calibration Date"
• "Calibration Who"
6.5.10 Block Mode
Sensor block support two modes: OOS (out-of-service) and AUTO. In OOS mode,
measurement is disabled and the sensor can be configured and/or calibrated. In
AUTO mode, measurement is enabled, all functional parameters except "Sensor Di-
agnostics" are write protected.
6.6 Concentrator Block Configuration
The concentrator block provides a summary view for the most important sensor con-
figuration parameters of each sensor block. These parameters are simply mapped to
their corresponding counterparts in the sensor blocks. The write protection of the pa-
rameters depends on the sensor block's target block mode.
6.6.1 Body Temperature
The device's body temperature can be read from the "Body Temperature" parameter.
It is possible to configure the temperature unit via the "Body Temperature Unit" pa-
rameter.
11/2008 132328
Please note that it is possible to map body temperature to an AI block (see chapter
6.2).
6.6.2 EMC Filter

Measurement values are filtered internally with a 50 Hz or 60 Hz filter to suppress
EMC disturbance by that frequency. The filter can be configured via the "ASIC Rejec-
tion" parameter.
Pepperl+Fuchs recommends to configure the filter in accordance to the

countries' power supply system frequency.
6.6.3 Block Mode

The block mode supports two modes of operation: OOS (out-of-service) and AUTO.
In OOS mode, the body temperature status is always BAD and the body temperature
unit can be configured.
In AUTO mode, body temperature status is GOOD.
Note that the concentrator block mode does not affect write protection
of the sensor parameters since they solely depend on the sensor
block's target block mode.
6.7 AI and MAI Block Configuration
The AI and MAI blocks are standard FOUNDATION Fieldbus block types. Please re-
fer to the FOUNDATION Fieldbus standard for configuration information. The channel
map can be found in chapter 6.2.
11/2008 132328
7 Operation
7.1 Primary Value Status
The primary value of the sensor blocks can have the following status:
• Good (NC)-Non specific
• Good (NC)-Active Block Alarm
• Good (NC)-Unacknowledged Block Alarm
• Bad-Sensor Failure: The sensor value exceeds the values defined by Primary Val-
ue. A sensor range or sensor error (wiring error, lead breakage) is detected for the
sensor inputs. The substatus "Hi-limited" or "Low-limited" define in which direction
the sensor's range has been exceeded. The substatus "Not limited" indicates a
sensor error.
• Bad-Device Error: The internal diagnosis of the device detected a hardware fault.
• Bad-OOS: The actual mode of the block is OOS
7.2 Body Temperature Status
The body temperature status in the Concentrator block is BAD if the block is in OOS
mode. In AUTO mode, the value is always GOOD as long as there is no self-diagnosis
error detected.
7.3 Device Self-diagnosis
The Pepperl+Fuchs TM-I Device continuously monitors its internal hardware and
body temperature. If an error occurs, the status of all Primary Values switches over to
BAD and the "Device needs maintenance now" bit in the "BLOCK_ERR" error param-
eter of the resource block is set which will generate an alarm.
7.4 Alarms
If an error occurs, the corresponding transducer block issues a block alarm

("BLOCK_ALM"). It is a summary alarm for all alarms of this block and is asserted as
long as the fault is still valid. To get information about the reason for the block alarm,
read the following parameters and refer to chapter 8 for remedy:
• "BLOCK_ERR"
• "Transducer error"
If the control system supports alarms, the "Alarm occur" and "Alarm clear" conditions
are conveyed through the bus to the system.
Since this mechanism is not supported by all control systems, the Pepperl+Fuchs
TM-I Device supports another method for error detection: All errors are shown in the
"BLOCK_ERR" parameter of the transducer block. Usually, this parameter is cyclical-
ly read by the control system. For a list of errors reported by "BLOCK_ERR", please
refer to chapter 8.
11/2008 132328
If the control system does not support alarms, the option "Reports" in
the "FEATURES_SEL" parameter of the resource block should be
deactivated.
11/2008 132328
8 Error Detection and Problem Remedy
8.1 LED Indications
The Temperature Multiplexer provides 8 sensor input specific red LEDs to indicate the
status of the related sensor input channels. The status of the bus power is provided
by a green LED, the communication status by a red LED. The LEDs are located on
the upper side of the device.
LED COM ERR
Sensor specific LEDs LED PWR
Figure 8.1: TM-I Device LEDs

Led States Cause Remedy
PWR (green) OFF No power supply • Check power supply
• Check fieldbus cable
wiring
ON permanently Power available -
COM (red) OFF Communication active -
ON permanently Hardware error Send device to Pep-
perl+Fuchs for repair
ON flashing No communication • Check LAS
Communication errors • Check wiring
Sensor (red) OFF No sensor errors -
(Channel detected
1…8) ON flashing Sensor error (Over- / Check sensor wiring.
underrange, wiring For more detailed infor-
error, leadbreakage) mation refer to diagno-
stic messages in the
corresponding sensor
11/2008 132328
transducer block
Table 8.1: LED indications
8.2 Resource Block
Problem Remedy
Parameter Message Cause Procedure
BLOCK_ERR Lost Static Data The parameterization Repeat parameteri-
data stored in the zation. If this error
device were faulty and occurs repeatedly,
replaced by default send the device to
settings Pepperl+Fuchs for
repair
Device needs Hardware error Send device to
Maintenance Pepperl+Fuchs for
now repair
Simulate active Simulation allowed by Check whether
setting the switch 1 simulation shall be
allowed
OOS The target mode of Set block to "Auto"
the block is OOS mode
RS_STATE Online No error -
Stand-by The target mode of Set block into
the block is OOS "Auto" mode
Table 8.2: Resource Block Errors
8.3 Sensor Block
Problem Remedy
BLOCK_ERR Block Confi- • "Sensor Type" is set to Correct parameteriza-
guration Error "Undefined" tion
• "Sensor Range.Unit" is
set to a value not sup-
ported by sensor (e.g.
"mV" for a resistance
based sensor)
• User calibration is
turned on at "Calibration
Mode", but "Calibration
State" shows no valid
user calibration exists
Input failure Several see Table 8.4: Com-
mon Sensor Block
Problems below
11/2008 132328
OOS The target mode of the Set block to "Auto"

block is OOS mode
Problem Remedy
Transducer Configuration See above at See above at
Error Error "BLOCK_ERR" "BLOCK_ERR"
(XD_ERROR) I/O failure The sensor value exceeds see Table 8.4: Com-
the HI or LO sensor limits mon Sensor Block
Problems below
Lead Brea- Sensor wiring fault see Table 8.4: Com-
kage / Sen- mon Sensor Block
sor Problems below
connection
error
Sensor Status Sensor con- See "Transducer Error See "Transducer
nection error Error"
Overrange Sensor high measurement see Table 8.4: Com-
limit exceeded mon Sensor Block
Problems below
Underrange Sensor low measurement see Table 8.4: Com-
limit exceeded mon Sensor Block
Problems below
Table 8.3: Sensor Block Errors
11/2008 132328
Problem Remedy
Cause Procedure
Block does not leave A configuration error is Clear configuration error
OOS mode reported cause. See above
Resource block is in OOS Set Resource block to
mode AUTO mode
Sensor failure Sensor error (Overrange, • Check wiring
underrange, leadbreakage) • Use sensor with a greater
input range
Wrong sensor type selected Configure correct sensor
type
RTD3 / RTD4 wires mixed Check cabling, see chapter
up 5.1.1
Wrong measurement Thermocouple polarity Check thermocouple pola-
values reversed rity
Unable to write to Write protection is enabled Set write protection DIP
parameters switch to OFF. see chapter
5.2
Block is in AUTO mode Set "MODE_BLK.Target" to
"OOS"
Table 8.4: Common Sensor Block Problems
8.4 Concentrator Block
Problem Remedy
BLOCK_ERR Body tempera- Devices' body • Choose another mount-
ture out of range temperature is too ing location
high / too low • Adjust mounting loca-
tions' ambient tempera-
ture
OOS The target mode Set block to "Auto" mode
of the block is
OOS
Transducer Body tempera- See See "BLOCK_ERR"
error ture out of range "BLOCK_ERR
(XD_ERROR
)
Table 8.5: Concentrator Block Errors

11/2008 132328
Problem Remedy
Cause Procedure
Block does not Resource block is in OOS Set Resource block to AUTO
leave OOS mode mode mode
Unable to write to Write protection is enabled Set write protection DIP
parameters switch to OFF (see chapter
5.2)
Corresponding sensor block Set sensor block to OOS
is in AUTO mode mode
"OOS"
Table 8.6: Common Concentrator Problems
8.5 AI Function Blocks
Problem Remedy
The channel parameter Set valid value (see
contains an invalid chapter 6.2).
value.
Block Configu- The function block does Include block into appli-
ration Error not have a schedule cation and download
downloaded schedule to device
"L_TYPE" parameter is Set "L_TYPE" to cor-
set to an incorrect value rect value
BLOCK_ERR
Transducer block Check transducer block
Input failure reports BAD "Primary diagnostics (see Table
Value.Status" 8.3)
Simulation for block is Check simulation acti-
Simulate active
activated vation
Actual block mode is Choose suitable target
Out-of-service OOS mode·Check block con-
figuration
Table 8.7: AI Function Block Errors
11/2008 132328
Problem Remedy
Cause Procedure
Function block does not A "BLOCK_ERR" is repor- Clear block error cause
leave OOS mode ted
The function block does Include block into applica-
not have a schedule down- tion and download sche-
loaded dule to device
Resource block is in OOS Set Resource block to
mode AUTO mode
OUT does not show Simulation activated Disable simulation

transducer block value
Simulation does not acti- Simulation DIP switch set Set simulation DIP switch
vate to OFF to ON (see chapter 5.2).
Unable to write to para- Write protection is enabled Set write protection DIP
meters switch to OFF (see chapter
5.2).
"OOS"
Table 8.8: Common AI Block Problems
8.6 MAI Function Block
Problem Remedy
BLOCK_ERR Block Configu- The channel parame- Set valid value (see
rationError ter contains an invalid chapter 6.2)
value.
The function block Include block into appli-
does not have a sched- cation and download to
ule downloaded device
Table 8.9: MAI Function Block Errors
11/2008 132328
Problem Remedy
Cause Procedure
A "BLOCK_ERR" is repor- Clear block error cause. See above
ted
Function block Resource block is in OOS Set Resource block to AUTO mode
does not leave mode
OOS mode The function block does Include block into application and
not have a schedule download schedule to device
downloaded
Write protection is Set write protection DIP switch to
Unable to write to
enabled OFF (see chapter 5.2).
parameters
Block is in AUTO mode Set "MODE_BLK.Target" to "OOS"
Table 8.10: Common MAI Problems
11/2008 132328
8.7 Diagnostic Summary
The following chapter shows a summary of the diagnostic features the TM-I Device
will provide and the way they are reported.
Diagnostic Alarm Description Alarm indication
Communication H1 segment communication is not LED
Failure established
The device configuration data RB Alarm, RB
EEPROM Failure
base is corrupted BLOCK_ERR
Program Storage The devices firmware is corrupted LED
Failure
The memory inside the device is LED
Memory Failure
defective
Body Temperature The body temperature of the RB Alarm, Concentrator
too high/low device exceeds it's specification BLOCK_ERR
Resource Block is in The actual mode of the RB is OOS RB Alarm, RB
Out of Service Mode BLOCK_ERR
The actual mode of the block is Block Alarm,
Block is in Out of OOS. BLOCK_ERR
Service Mode This is the same for all function
and transducer blocks
One or more parameters of the Block Alarm,
Block Configuration block contain invalid or conflicting BLOCK_ERR
Error values. This is the same for all
function and transducer blocks.
Sensor error (wiring, A cable of the sensor is broken, Block Alarm,
lead break) incorrect sensor wiring. BLOCK_ERR of all TBs
Sensor Over / Measured sensor value exceeds Block Alarm,
Under Range its high or low range limit. BLOCK_ERR of all TBs
The Simulation is enabled for a Block Alarm,
Simulation active
function block. BLOCK_ERR of all FBs
The device detected an internal Block Alarm,
Device HW Failure
HW failure at the measurement BLOCK_ERR of RB,
(ADC, CJC mea-
unit. status of affected val-
surement etc.)
ues, LED
Table 8.11: Device diagnostic summary
11/2008 132328
9 Block Descriptions
9.1 Resource Block (RB)
Rel.
Parameter Description
Index
01 ST_REV The revision level of the static data associated with the resource block.
The revision value will be incremented each time a static parameter value
in the block is changed.
02 TAG_DESC The user description of the intended application of the block.
03 STRATEGY The strategy field can be used to identify grouping of blocks. This data is
not checked or processed by the block.
04 ALERT_KEY The identification number of the plant unit. This information may be used
in the host for sorting alarms, etc.
05 MODE_BLK The actual, target, permitted, and normal modes of the block:·
• Target: The mode to "go to"
• Actual: The mode the "block is currently in"
• Permitted: Allowed modes that target may take on
• Normal: Most common mode for actual
06 BLOCK_ERR This parameter reflects the error status associated with the hardware or
software components associated with a block. It is a bit string so that mul-
tiple errors may be shown.
Supported values:·
• Simulate Active: Hardware switch is set to simulation possible
• Lost Static Data: The database used for storing the NV parameters
within the device is corrupt
• Device Needs Maintenance Now: The hardware of the device failed in
some way (e.g. body temperature too high)
• Out Of Service: The RB is in Mode OOS
07 RS_STATE State of the resource block application state machine.
08 TEST_RW Read/Write test parameter. Used only for conformance testing.
09 DD_RESOURCE String identifying the tag of the resource that contains the device descrip-
tion for this resource.
10 MANUFAC_ID Manufacturer identification number - used by an interface device to locate
the DD file for the resource.
Pepperl+Fuchs ID is 0x502B46.
11 DEV_TYPE Manufacturer's model number associated with the resource - used by
interface devices to locate the DD file for the resource. The P+F TI Mux is
device type 3.
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 an interface
device to locate the DD file for the resource.
14 GRANT_DENY Options for controlling access of host computers and local control panels
to operating, tuning, and alarm parameters of the block.
15 HARD_TYPES The types of hardware available as channel numbers. Only scalar types
are supported.
16 RESART Allows a manual restart to be initiated. Several degrees of restart are pos-
sible:
1. Run - nominal state when not restarting
2. Restart resource - not used
3. Restart with defaults - set parameters to default values
4. Restart processor - does a warm restart of CPU
17 FEATURES Used to show supported resource block options.
11/2008 132328
Rel.
Index
18 FEATURES_SEL Used to select resource block options.
Supported values:
• Unicode: Tells host to use Unicode for string values
• Reports: Enables alarms, must be set for alarming to work
• Hardware Lock: Hardware write locking enabled but not active.
WRITE_LOCK follows the status of the security switch
19 CYCLE_TYPE Identifies the block execution methods available for this resource.
Supported values:
• Schedule
• Completion of Block execution
20 CYCLE_SEL Used to select the block execution method for this resource.
Supported values:
• Scheduled: Blocks are only executed based on the schedule in
FB_START_LIST.
• Block Execution: A block may be executed by linking to another blocks
completion.
21 MIN_CYCLE_T Time duration of the shortest cycle interval of which the resource is capa-
ble.The Pepperl+Fuchs TM-I Device supports 100 ms.
22 MEMORY_SIZE Available configuration memory in the empty resource.
23 NV_CYCLE_T Interval between writing copies of NV parameters to non-volatile memory.
Zero means none.
24 FREE_SPACE Percent of memory available for further configuration. Not supported by
Pepperl+Fuchs TM-I Device.
25 FREE_TIME Percent of the block processing time that is free to process additional
blocks. Not supported by
Pepperl+Fuchs TM-I Device.
26 SHED_RCAS Time duration at which to give up on computer writes to function block
RCas locations.
27 SHED_ROUT Time duration at which to give up on computer writes to function block
ROut locations.
28 FAULT_STATE ondition set by loss of communication to an output block, failure promoted
to an output block or a physical contact. When a fault state condition is
set, the output function blocks will perform their FSTATE actions. The P+F
TI Mux does not support output blocks.
29 SET_FSTATE Allows the fault state condition to be manually initialed by selecting Set.
The P+F TI Mux does not support this function.
30 CLR_FSTATE Writing a Clear to this parameter will clear the device fault state if any field
condition has cleared. The P+F TI Mux does not support this function.
31 MAX_NOTIFY Maximum number of unconfirmed alert notifications messages possible.
This number cannot be changed. The P+F TI Mux supports a maximum of
42.
32 LIM_NOTUIFY Maximum number of unconfirmed alert notification messages allowed.
P+F TI Mux supports a maximum of 42.
33 CONTIRM_TIME The minimum time between retries of alert reports. Retries shall not hap-
pen when parameter is set to 0.
34 WRITE_LOCK If set, no writes from anywhere are allowed, 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 BLOCL_ALM The block alarm 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 ALARM_STATE subcode.
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 associated with the function block will be
11/2008 132328
automatically acknowledged.
39 WRITE_PRI Priority of the alarm generated by clearing the write lock.
Rel.
Index
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 to register
the device with the Fieldbus FOUNDATION.
42 SERIAL_NUM Unit specific serial number to identify production and release information.
Set by manufacturer.
43 SW_REV The software revision of the firmware within the device.
Table 9.1: Resource Block parameter list
9.2 Analog Input Function Block (AI)
Rel.
Parameter Units Description
Index
01 ST_REV The revision level of the static data associated with
the function block. The revision value will be incre-
mented each time a static parameter value in the
block is changed.
02 TAG_DESC The user description of the intended application of
the block.
03 STRATEGY The strategy field can be used to identify a group-
ing of blocks. This data is not checked or pro-
cessed by the block.
04 ALERT_KEY The identification number of the plant unit. This
information may be used in the host for sorting
alarms, etc.
05 MODE_BLK The actual, target, permitted, and normal modes of
the block.
• Permitted: Allowed modes that target may take
on
• Normal: Most common mode for target
06 BLOCK_ERR This parameter reflects the error status associated
with the hardware or software components associ-
ated with a block. It is a bit string, so that multiple
errors may be shown.
07 PV EU of XD_SCALE The primary analog process variable used in block
execution.
08 OUT EU of The primary analog block output value and status.
OUT_SCALE or
XD_SCALE if in
direct L_TYPE
09 SIMULATE A data structure that contains the current trans-
ducer output value and status, the simulated trans-
ducer value and status, and the enable/disable bit.
10 XD_SCALE A data structure that contains the high and low
scale values, engineering units code, and number
of digits to the right of the decimal point associated
with the channel input value.
11 OUT_SCALE A data structure that contains the high and low
scale values, engineering units code, and number
of digits to the right of the decimal point displaying
the OUT parameter.
12 GRANT_DENY Options for controlling access of host computers
and local control panels to operating, tuning, and
alarm parameters of the block. Not used by device.
11/2008 132328
13 IO_OPTS Allows the selection of input/output options used to

alter the input block processing (PV).
Rel.
Index
14 STATUS_OPTS Allows selecting options for status handling and
processing.
The following options are supported in the AI block:
• Propagate fault forward
• Uncertain if limited
• Bad if limited
• Uncertain if manual mode
15 CHANNEL The CHANNEL value is the number of the physical
input (transducer output) that is used as input for
the function block.
Supported values:
• 1-8: physical input from Channel 1 to Channel 8
• 10: physical input from Concentrator block which
is the internal device temperature
16 L_TYPE Determines whether the field value is used directly
(Direct), is converted linearly (Indirect), or is con-
verted with the square root (Indirect Square Root).
17 LOW_CUT % If percentage value of transducer input fails below
this value, then PV is set to 0
18 PV_FTIME Seconds Time constant of the first-order filter for the PV. It is
the time required for a 63% change in the PV or
OUT value. Used for filtering the response time.
19 FIELD_VAL % The value (in percent of the PV range) and status
from the transducer block or from the simulated
input before signal characterization.
20 UPDATE_EVT This alert is generated by any change to the static
data.
21 BLOCK_ALM The block alarm is used for all configuration, hard-
ware, connection failure or system problems in the
block. The cause of the alert is entered in the sub-
code field. The first alert to become active will set
the Active status in the Status parameter. 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.
22 ALARM_SUM The current alert status, unacknowledged states,
and disabled states of the alarm associated with
the function block.
23 ACK_OPTION Used to set auto acknowledgment of alarms.
24 ALARM_HYS % Span, expressed in percent of the PV span, in
which a PV must return before an alarm condition
is cleared.
25 HI_HI_PRI The priority of the HI-HI alarm.
26 HI_HI_LIM EU of PV_SCALE The setting for the alarm limit used to detect the HI-
HI alarm condition.
27 HI_PRI The priority of the HI alarm.
28 HI_LIM EU of PV_SCALE The setting for the alarm limit used to detect the HI
alarm condition.
29 LO_PRI The priority of the LO alarm.
30 LO_LIM EU of PV_SCALE The setting for the alarm limit used to detect the LO
alarm condition.
31 LO_LO_PRI The priority of the LO-LO alarm.
32 LO_LO_LIM LO_LO_PRI The setting for the alarm limit used to detect the
LO-LO alarm condition.
11/2008 132328
33 HI_HI_ALM The HI-HI alarm data, which includes a value of the

alarm, a timestamp of occurrence and the state of
the alarm.
Rel.
Index
34 HI_ALM The HI alarm data, which includes a value of the
the alarm.
35 LO_ALM The LO alarm data, which includes a value of the
the alarm.
36 LO_LO_ALM The LO-LO alarm data, which includes a value of
the alarm, a timestamp of occurrence and the state
of the alarm.
Table 9.2: Analog Input Function Block (AI) Parameter List
9.3 Multiple Analog Input Function Block (MAI)
Rel.
Index
1 ST_REV The revision level of the static data associated with the input selector
block. The revision value will be incremented each time a static param-
eter value in the block is changed.
2 TAG_DESC The user description of the intended application of the block.
3 STRATEGY The strategy field can be used to identify grouping of blocks. This data
is not checked or processed by the block.
4 ALERT_KEY The identification number of the plant unit. This information may be
used in the host for sorting alarms, etc.
5 MODE_BLK The actual, target, permitted, and normal modes of the block.
6 BLOCK_ER This parameter reflects the error status associated with the hardware
R or software components associated with a block. It is a bit string, so
that multiple errors may be shown.
7 CHANNEL Allows for custom channel setting.
Valid values:
• 0: Uninitialized
• 9: Physical channels 1 to 8 will be set to the corresponding sensors
8 -15 OUT_(1-8) EU of The block output value and status.
OUT_SCALE
16 UPDATE_E This alert is generated by any change to the static data.
VT
17 BLOCK_AL he block alarm is used for all configuration, hardware connection fea-
M ture, 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 parameter. As soon as the Unreported status is
cleared by the alert reporting task, another block may be reported with-
out clearing the Active status, if the subcode has changed.
Table 9.3: MAI Parameter List
9.4 TI_SENS Sensor Blocks (TIS)
The properties column lists parameter properties:

• S: Static (a write access to this parameter increments ST_REV)
• W: Parameter is writeable
11/2008 132328
• OOS: Parameter is writeable in OOS mode only

• SP: Special (see description column)
• NF: non-functional parameter (does not change block behaviour).

Since all parameters can be read, this is not explicitly stated.
Rel.
Parameter Properties Description
Index
01 ST_REV The revision level of the static data associated with the
input selector block. The revision value will be incremented
each time a static parameter value in the block is changed.
02 TAG_DESC S, W, NF The user description of the intended application of the
block.
03 STRATEGY S, W, NF The strategy field can be used to identify grouping of
blocks. This data is not checked or processed by the block.
04 ALERT_KEY S, W, NF The identification number of the plant unit. This information
may be used in the host for sorting alarms, etc.
05 MODE_BLK S, W The actual, target, permitted, and normal modes of the
block.
06 BLOCK_ERR This parameter reflects the error status associated with the
hardware or software components associated with a block.
It is a bit string, so that multiple errors may be shown.
Supported values:
• Block Configuration Error: Target block mode is different
than OOS and one of the following conditions is true:
- Sensor type is set to undefined
- "Sensor Range.Unit" is set to a value not supported
by sensor (e.g. "mV" for a resistance based sensor)
- User calibration is turned on at "Calibration Mode",
but Calibration State shows no valid user calibration
exists
• Input Failure: "Primary Value.Status" is BAD, but not
BAD/OOS
• Out-of-Service: Actual mode of the block is OOS
07 UPDATE_EVT This alert is generated by any change to the static data
08 BLOCK_ALM The block alarm is used for all configuration, hardware
connection feature, 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 Sta-
tus parameter.
09 Transducer Error Stores the actual transducer block error with the highest
(XD_ERROR) priority.
Supported values:
• Configuration Error: A block configuration error exists.
See "BLOCK_ERR" for details
• I/O Failure: The sensor value exceeds the HI or LO sen-
sor Limits
• Sensor Connection Error: Sensor cabling error detected
10 Prinary Value Type S, W, NF Defines the type of the Primary Value.
The following values are valid:
• Process temperature
• Non-process temperature
• mV
• Ohm
11 Primary Value The value and status of the sensor input (see chapter 7.1).
12 Primary Value Filter- S, OOS Time constant in seconds of a first order lag filter applied to
time "Primary value". Valid values are 0 to 255 s. A value of 0
disables filtering.
11/2008 132328
Rel.
Index
13 Sensor Type S, OOS Type of the attached sensor. For a list of supported sen-
sors, see datasheet.If "Sensor Type" is written some other
parameters will be set automatically for convenience:
• If voltage mode or a TC is selected,
"SENSOR_CONNECTION" is set to 2-wire
• If voltage mode is selected, Primary Value unit is set to
mV
• If resistance input is selected the Primary Value unit is
set to Ohm
• If a TC or RTD sensor is selected and the Primary Value
Unit is mV or Ohm it is set to °C
14 Sensor Range S, OOS Defines the absolute maximum ends of the sensor range,
the units of those limits and the number of digits to the right
of the decimal point to be used to display these values.
Supported units: mV, Ohm, °C, °F, K, °R
15 Sensor Connection S, OOS Number of wires used to connect the sensor. This parame-
ter is only honored if a resistance-based sensor is config-
ured.
Supported values:
• Two wires
• Three wires
• Four wires
16 Sensor Diagnostics S, W Enables sensor diagnosis.
17 Sensor Status Shows failures of the attached sensor, it is a bit string so
multiple errors can be shown.
Supported values:
• Sensor connection error
• Over range: The measured value is too high for current
sensor
• Under range: The measured value is too low for current
sensor
18 Sensor Serial No. S, W, NF The serial number of the attached sensor.
19 Sensor Calibration S, W, NF Last calibration method used for the attached sensor:
Method • Factory trim standard calibration
• User trim standard calibration
• Factory trim special calibration
• User trim special calibration
• Other
20 Sensor Calibration S, W, NF Shows location of the last calibration for the attached sen-
Location sor.
21 Sensor Calibration S, W, NF Shows date of the last calibration for the attached sensor.
Data
22 Sensor Calibration Who S, W, NF Shows name of person responsible for the last calibration
for the attached sensor.
23 RTD 2 Wire Resistance S, OOS Specifies an offset subtracted from the measured resis-
tance if a two-wire RTD or Ohm sensor is attached. The
value is specified as a positive floating point number.
24 CJC Select S, OOS Selects the method used to do a CJC:
• Internal: use the internally measured value
• Constant: use the value of parameter "Constant CJC"
25 CJC Constant S, OOS Value used for CJ compensation if "CJC select" is set to
Constant. Uses the Unit of "Sensor Range.Units Index".
The value is converted automatically if "Sensor
Range.Units Index" is changed.
26 Calibration Highest S, SP Upper value for calibration of the input. Writeable only dur-
Point ing calibration.
27 Calibration Lowest S, SP Lower value for calibration of the input. Writeable only dur-
Point ing calibration.
11/2008 132328
28 Calibration Highest Highest value allowed to calibrate the input.

Point Limit
Rel.
Index
29 Calibration Lowest Lowest value allowed to calibrate the input.
Point Limit
30 Calibration Minimum Minimum allowed difference between "Calibration Highest
Span Point" and "Calibration Lowest Point".
31 Calibration Units Unit used to calibrate the input. It is set automatically if a
calibration starts. Valid values: mV and Ohm
32 Calibration Mode S, OOS Stipulates the validity of user calibration and turns the cali-
bration mode on for the input
• User calibration off
• User calibration on: A calibration error ("Calibration
State" reads "Failure") will be reported as a block config-
uration error so the block will not switch to AUTO mode.
• Execute user calibration
33 Calibration State Shows the state of the user calibration for the input.
Supported values:
• Not initialized: No user calibration was carry out yet. It's
not possible to turn on the user calibration
• Executing: A user calibration is being started
• OK: A valid user calibration was executed
• Failure: A failure happened during the last user calibra-
tion. The values are invalid. It's not possible to turn on
the user-calibrated measurement. The block will report
a configuration error if "Calibration Mode" is set to "User
calibration on".
• Wait first: Device is waiting for write on "Calibration
Highest Point" or "Calibration Lowest Point" as first cali-
bration point
• Wait second HI: Device is waiting for write on " Calibra-
tion Highest Point " as second calibration point
• Wait second LO: Device is waiting for write on " Calibra-
tion Lowest Point " as second calibration point
• Sampling HI: Device is measuring HI calibration value.
• Sampling LO: Device is measuring LO calibration value
34 Calibration Location S, W, NF Shows location of the last calibration for the input.
35 Calibration Date S, W, NF Shows date of the last calibration for the input.
36 Calibration Who S, W, NF Shows name of person responsible for the last calibration
for the input.
Table 9.4: TI_SENS Block Parameter List
9.5 Concentrator Block (TIC)
The properties column lists parameter properties:

• S: Static (a write access to this parameter increments ST_REV);
• W: Parameter is writeable;
• OOS: Parameter is writeable in OOS mode only;
• SP: Special (see description column);
• NF: non-functional parameter (does not change block behaviour).
Since all parameters can be read, this is not explicitly stated.
Rel.
Index
01 ST_REV The revision level of the static data associated with the
input selector block. The revision value will be incremented
each time a static parameter value in the block is changed.
11/2008 132328
02 TAG_DESC S, W, NF The user description of the intended application of the

block.
Rel.
Index
03 STRATEGY S, W, NF The strategy field can be used to identify grouping of
blocks. This data is not checked or processed by the block.
04 ALERT_KEY S, W, NF The identification number of the plant unit. This information
may be used in the host for sorting alarms, etc.
05 MODE_BLK S, W The actual, target, permitted, and normal modes of the
block.
06 BLOCK_ERR This parameter reflects the error status associated with the
hardware or software components associated with a block.
It is a bit string, so that multiple errors may be shown.
Supported values:
• 15: Out-of-Service = Actual Mode of the Block is OOS
• 129: Body temperature too high or too low
07 UPDATE_EVT This alert is generated by any change to the static data.
08 BLOCK_ALM The block alarm is used for all configuration, hardware
connection feature, 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 Sta-
tus parameter. As soon as the Unreported status is cleared
by the alert reporting task, another block may be reported
without clearing the Active status, if the subcode has
changed.
09 Transducer Error Stores the actual transducer block error wit the highest pri-
(XD_ERROR) ority.Supported values:
• 129: Body temperature too high or too low
10 Block Mode Channel 1 S, W Mode block of sensor input 1.
11 Primary Value The value and status of sensor input 1.
12 Primary Value Filter- S, SP The damping value for sensor input 1. Parameter is write-
time Channel 1 able if corresponding sensor block is in OOS mode.
13 Sensor Unit Channel 1 S, SP The unit used for sensor input 1. Parameter is writeable if
corresponding sensor block is in OOS mode.
14 Sensor Type Channel 1 S, SP The type of sensor input 1. Parameter is writeable if corre-
sponding sensor block is in OOS mode.
15 Sensor Connection S, SP The connection type of sensor input 1. Parameter is write-
Channel 1 able if corresponding sensor block is in OOS mode.
16 Sensor Diagnostics S, W Allows to enable/disable the sensor diagnosis for sensor 1.
Channel 1
18 - 73 The sensor specific values above are repeated for the sensor inputs 2 - 8
• 18 - 24 channel 2
• 25 - 31 channel 3
• 32 - 38 channel 3
• 39 - 45 channel 4
• 46 - 52 channel 5
• 53 - 59 channel 6
• 60 - 66 channel 7
• 67 - 73 channel 8
74 Body Temperature Value and status of the body temperature.
75 Body Temperature Unit S, OOS The unit used to display body temperature.
Valid units: °C, °F, °R, K
76 ASIC Rejection S, W Used to set the electrical noise filter depending on the
power line frequency of the installation. Valid values are
50Hz and 60Hz.
77 Status Summary Overview of the sensor status of all sensors. The parame-
11/2008 132328
ter is a bit string, so multiple errors can be displayed.Sup-

ported values: "Bad sensor 1" to "Bad sensor 8"
Table 9.5: Concentrator Block Parameter List
10 List of Tables
Table 4.1: Marking of the Temperature Multi Input Device ................................ 6

Table 6.1: Channel Mapping............................................................................ 19
Table 8.1: LED indications ............................................................................... 28
Table 8.2: Resource Block Errors .................................................................... 29
Table 8.3: Sensor Block Errors ........................................................................ 30
Table 8.4: Common Sensor Block Problems ................................................... 31
Table 8.5: Concentrator Block Errors............................................................... 31
Table 8.6: Common Concentrator Problems ................................................... 32
Table 8.7: AI Function Block Errors ................................................................. 32
Table 8.8: Common AI Block Problems ........................................................... 33
Table 8.9: MAI Function Block Errors .............................................................. 33
Table 8.10: Common MAI Problems.................................................................. 34
Table 8.11: Device diagnostic summary ............................................................ 35
Table 9.1: Resource Block parameter list ........................................................ 38
Table 9.2: Analog Input Function Block (AI) Parameter List ............................ 40
Table 9.3: MAI Parameter List ......................................................................... 40
Table 9.4: TI_SENS Block Parameter List....................................................... 43
Table 9.5: Concentrator Block Parameter List ................................................. 44
11/2008 132328
11 List of Figures
Figure 4.1: Possibilities of installation................................................................. 8

Figure 4.2: Zone 2 installation ............................................................................ 9
Figure 4.3: Dimensions and pinout of RD0-TI-Ex8.FF.*:*................................. 12
Figure 4.4: Dimensions and pinout of F2D0-TI-Ex8.FF.*:* ............................... 13
Figure 5.1: Sensor connection.......................................................................... 18
Figure 5.2: DIP Switches .................................................................................. 18
Figure 6.1: Block interaction ............................................................................. 20
Figure 6.2: Measurement dataflow ................................................................... 22
Figure 8.1: TM-I Device LEDs .......................................................................... 28
11/2008 132328
PROCESS AUTOMATION –
PROTECTING YOUR PROCESS
Worldwide Headquarters
Pepperl+Fuchs GmbH
68307 Mannheim · Germany
Tel. +49 621 776-0
E-mail: info@de.pepperl-fuchs.com
For the Pepperl+Fuchs representative

closest to you check www.pepperl-fuchs.com/pfcontact
www.pepperl-fuchs.com
132328 / TDOCT0193DENG
Subject to modifications
11/2008
Copyright PEPPERL+FUCHS • Printed in Germany

P+F Mux

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

P+F Mux

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P+F Mux

Uploaded by

Copyright:

Available Formats

PROCESS AUTOMATION

1 Validity of these instruction manual/manual ......................................... 3

2 Symbols used ........................................................................................... 3

4 Instruction Manual ................................................................................... 5

6.5.6 Sensor Diagnosis .................................................................................................... 22

6.5.8 User Calibration ...................................................................................................... 23

8 Error Detection and Problem Remedy ................................................. 28

9 Block Descriptions ................................................................................ 36

10 List of Tables .......................................................................................... 45

11 List of Figures ........................................................................................ 46

1 Validity of these instruction manual/manual

Pepperl+Fuchs offers three different types of Temperature Multi Input Devices:

A corresponding declaration of conformity may be requested from the

This symbol warns of a danger.

This symbol warns of a possible fault.

This symbol draws your attention to important information.

This manual describes the Pepperl+Fuchs FOUNDATION Fieldbus version of the

The operator of the system bears the responsibility in terms of planning,

4.1 Intended Use

available instruction manual.

TM-I Devices are identified by:

4.3 Ambient Conditions

4.4 Mounting and Dismounting

Mounting, dismounting, installation and commissioning must only be performed by

4.4.2 Mounting and Dismounting of RD0-TI-Ex8.FF.*

Housings of light alloy must not contain more then 6% of magnesium in

Plastic housing must be designed in accordance with IEC 60079-0 or

4.5 Installation and Commissioning

The Temperature Multiplexer meets the requirements of the Foundation Fieldbus

Host Power Host Power

Figure 4.1: Possibilities of installation

The EC-type-examination certificate or the statement of conformity

4.5.1 Installation in Category 2G (Zone 1)

DIN EN 60079-14/VDE 0165 Part 1 must also be observed.

4.5.2 Installation in Category 3G (Zone 2) and safe areas

Segregation plate (required for Zone 2 installations)

Figure 4.2: Zone 2 installation

stallation, maintenance or repair.

The coincidence of an explosive atmosphere with installation, mainte-

The coincidence of an explosive atmosphere with installation, mainte-

4.5.6 Commissioning the TM-I Device

4.5.7 Installation and Commissioning of RD0-TI-Ex8.FF.*

LED comm. Separation, used when device

DIN mounting rail

CH1 ... CH8 Bus

Figure 4.3: Dimensions and pinout of RD0-TI-Ex8.FF.*:*

Type Cap nut Lower part

20 8 Inputs, see tables Fieldbus IN

Figure 4.4: Dimensions and pinout of F2D0-TI-Ex8.FF.*:*

The ambient temperature range can be restricted by the stop plug.

For metal housings in hazardous areas, a suitable potential equalization in accor-

4.6 Handling of the Cable Glands

4.6.1 Handling F*D0-TI-Ex8.FF.CG Cable Glands

4.6.2 Handling the F*D0-TI-Ex8.FF.CGB and F*D0-TI-Ex8.FF.CGS Cable Gland

4.7 Grounding and Shielding of the TM-I Device

If the shield of the fieldbus transmission line is grounded for reasons

The terminal S of the intrinsically safe fieldbus segment is

Figure 4.3: Dimensions and pinout of RD0-TI-Ex8.FF.:

Figure 4.4: Dimensions and pinout of F2D0-TI-Ex8.FF.:

4.6.2 Handling the FD0-TI-Ex8.FF.CGB and FD0-TI-Ex8.FF.CGS Cable Gland