FF Booklet Technology

FOUNDATION Fieldbus Technology Training 2010
Table of Contents
Slide
1 / 340
FOUNDATION Fieldbus Technology, Market
Testing, Certification and Registration
17
Analog to Fieldbus Digital Communication
35
OSI Model Fieldbus Layers
50
Physical Layer Topologies
61
Physical Layer Components
77
Communication Layer Principles
123
Device Driver
157
Address range
176
User Layer Function Blocks
186
User Layer Function Block Application
210
Physical Layer Properties
246
Physical Layer Installation
260
Physical Layer Calculation
285
Physical Layer Troubleshooting
300
FieldXpert
330
Glossary, NI Tool guideline
338
FOUNDATION Fieldbus Technology, Market

FOUNDATION Fieldbus Basic Training I
PC-PS
Slide 2
History of FOUNDATION Fieldbus technology

The technology is the result of a worldwide effort to develop a single
interoperable international fieldbus
Technical work based upon IEC/ISA SP50 functional requirements
1980
process control suppliers

work on their own proprietary digital communication bus standard
ISP
WFIP
1994
Slide
3 / 340
Merge to found the Fieldbus Foundation

Fieldbus competition in the nineties:
FIP: French standard supported by the
major French suppliers
WFIP: World Factory Instrumentation
Protocol; International development
from FIP
PROFIBUS: German standard
supported by the major German
suppliers
ISP: Interoperable Systems Project
FF: Formed from ISP and WFIP in
1994
Slide
4 / 340

FF was Formed from WFIP and ISP in 1994
Slide
5 / 340
WFIP:
was developed from an earlier French
National Standard known as NFC 46600
ISP:
is based on the German National
Standard DIN STD19245, also known
as Process Field Bus, or Profibus.
Major members:
Honeywell (Arizona)
Bailey Controls (Ohio)
Cegelec (Paris)
Allen Bradley Corporation (Ohio)
Telemcanique (Paris)
Ronan Engineering Co. (California)
Square D
Electricit de France (France)
Elf (France)
Endress+Hauser (Switzerland)
Major members:
Siemens (Germany)
The Rosemount Group (Minnesota)
Fisher Controls, Inc. (Texas)
Foxboro Co. (Massachusetts)
ABB Co. (Sweden)
Yokogawa Electric Corporation
(Tokyo)
Endress+Hauser (Switzerland)
FOUNDATION Fieldbus - PROFIBUS
Europe
Canada
USA
India
Japan
Brazil
Southeast Asia
Argentina
South Africa
Slide
6 / 340
Slide
7 / 340
FOUNDATION Fieldbus vs. Fieldbus Foundation

FOUNDATION Fieldbus Technology
Fieldbus technology is open and available to all parties.
Fieldbus technology is based on the work of the International
Electrotechnical Commission (IEC) and the International Society of
Automation (ISA).
Slide
8 / 340
FOUNDATION Fieldbus vs. Fieldbus Foundation

The Fieldbus Foundation is an independent, non-profit making
organization :
Consisting of over 350 leading process and manufacturing automation
companies worldwide
Major purpose is to provide an open and neutral environment for the
development of a single, international, interoperable fieldbus
Environment for end users, manufacturers, universities and research
organizations working together to develop the technology
Provide development tools, support and training
Enable product interoperability
Slide
9 / 340
Fieldbus Foundation Organization

www.fieldbus.org
Slide
10 / 340
Fieldbus Foundation Organisation

Location: Austin, Texas
Fieldbus Foundation
9005 Mountain Ridge Drive
Bowie Bldg - Suite 190
Austin, TX 78759-5316
info@fieldbus.org
Slide
11 / 340
Phone: +1 512 794 8890

Fax: 512.794.8893
Fieldbus Foundation Members

Member companies
ABB Asea Brown Boveri, Ltd.
AEG Schneider Automation, Inc.
Alfa Laval Automation AB
Allen-Bradley Co., Inc.
Alpret (Pty) Ltd.
Analog Devices, Inc.
Apparatebau Hundsbach GmbH
Bailey Controls Co.
Bailey Japan Co., Ltd.
Beamex Oy, Ab
Belden Wire & Cable
Borst Automation
Bray International
Bronkhorst High Tech
Brooks Instrument
Caltex Services Co.
Chevron Research & Technology
Danfoss A/S
Digi Table thielen GmbH
DKK Corporation
Druck Ltd.
DuPont Engineering Co.
Eckardt AG
EMCO
Endress + Hauser GmbH
Enraf
Exxon Research & Engineering
FINT
Fisher Controls International
Fisher-Rosemount Systems
The Foxboro Company
Fraunhofer Institute (IITB)
Fuji Electric Co., Ltd.
Furon Company, Dekron Division
Glaxo Inc.
GSC Precision Controls
Hartmann & Braun
Hitachi, Ltd. Instrument Division
Honeywell Inc.
i.f.a.c.
Instituto de Investiganciones
Johnson Controls, Inc.
Johnson Yokogawa Corp.
KK Codix
K-Patents Oy
Keystone Controls
Kimray Inc.
Knick Elektronische
Koso Service Co., Ltd.
KROHNE Messtechnik GmbH
Leeds & Northrup
Limitorque Corp.
Magnetrol International
Masoneilan-Dresser
Measurement Technology, Ltd.
Mettler - Toledo Inc.
Micro Motion Inc.
Milltronics
Mitsubishi Electric
Monsanto Company
Motoyama
Nagano Keiki Seisakusho
National Instruments
NEC Corporation
Neles-Jamesbury Oy
NEMA
Niigata Masoneilan Ohkura Elec.
Norsk Hydro a.s.
Ohkura Electric Co., Ltd.

Westlock Controls Corp.
Oval Corp.
WorldFIP Europe
Pacific Avionics Co.
Yamatake-Honeywell Co.
Pepperl + Fuchs
Yokogawa Electric Corp.
POHTO
Yokogawa Electronics Corp.
Politecnico di Torino-Dai
Presys Instrumentos
Procter & Gamble Co.
R. Stahl GmbH & Co.
Ramsey Technology, Inc.
Ronan Engineering
Rosemount Inc.
Rosemount Analytical Inc.
Saab Tank Control
Schneider North America
Servomex Company Inc.
Shell Oil
Shimadzu Corporation
Ship Star Associates
Siebe ECD
Sieger TPA Ltd.
Siemens Industrial Automation
Simrad Albatross AS
SMAR International
Softing GmbH
SOR, Inc.
StoneL Corp.
TMG i-tech GmbH
Tokyo Keiso Co., Ltd.
Toshiba Corporation
Valmet Automation Inc.
VALTEK
VEGA Grieshaber
Vinson Supply
And more
Slide
12 / 340
FOUNDATION Fieldbus Markets

General Figures as of 2009
> 1 million devices
Slide
13 / 340
10000 Systems

Industry Distribution
Slide
14 / 340

Area/Location Distribution
Asia Pacific
Europe
North America
Middle East Asia
Slide
15 / 340

A few examples of customers using FF technology:
Shell, Total, Repsol, BP, Statoil, Saudi Aramco, Viscolube,
Gaz de France, Fanavaran Petrochemical, Qatar Petroleum, Petroleum
Development Oman, Oman Gas Company, Wintershall Noordzee,
South Pars Refinery, Scanraff, Petronas, Petrobras, Reliance, PMex,
BASF, Degussa, DSM, Huntsmann, Sasol, Borden, Arya Sasol Polymer,
Eval, Shinetsu
Genzyme, Biogen, Novartis, Glaxo, Amgen
Linde
Slide
16 / 340
Testing, Certification and Registration

FOUNDATION Fieldbus Basic Training II
PC-PS
Slide 17
Integration Tests the Triangle of Testing
FOUNDATION
Fieldbus Foundation
FF
Triangle
of Testing
Endress+Hauser
Slide
18 / 340
DCS Systems Vendors
Communication Conformance Test
Physical Layer Conformance Test

local, in-house testing
Conformance Test Kit (CTK)
in Frankfurt
Software Stack
Communication
Hardware
+
Complete device
Slide
19 / 340
DD file
Interoperability Test Kit

in Austin, Texas
Test of Communication
Slide
20 / 340
Slide
21 / 340
Official Fieldbus Foundation Testing

Fieldbus Foundation has a qualified certificate
system for fieldbus devices and therefore

guarantees the interoperability.
DD file
Device to be checked including

device description
All Endress+Hauser are officially tested and

registered by the Fieldbus Foundation
Test in
Test Laboratory
(Austin,TX)
No
OK ?
Yes
Slide
22 / 340
Certificate
from
Fieldbus Foundation
Organisation
ITK Revisions and Certified devices

ITK History:
www.fieldbus.org
ITK
2000
Slide
23 / 340
ITK
2003
ITK
2004
ITK 5.2
ITK 5.0
end of 2006 end of 2009
Fieldbus Foundation Device ITK Certificates
Slide
24 / 340
Fieldbus Foundation DD/CF ITK Certificates
Slide
25 / 340
Registration at the Endress+Hauser - Website
Slide
26 / 340
www.products.endress.com/foundation-fieldbus-dd
Registration at the Fieldbus Foundation - Website
Slide
27 / 340
Registration TMT162 Webpage
Slide
28 / 340
Registration TMT162 Webpage
Slide
29 / 340
Integration Tests the Triangle of Testing
FOUNDATION
Fieldbus Foundation
FF
Triangle
of Testing
Endress+Hauser
DCS Systems Vendors
Relationship between Instrument and DCS Vendor is a key !

Slide
30 / 340
Host Interoperability Support Test (HIST):

FOUNDATION Fieldbus Host Test Kit (HTK: HTK 2.1)
Control System
ABB
Symphony
AC800M
AC800F
ABB
Composer
Fieldbus Builder
Control Builder
Endress+Hauser
ControlCare
Endress+Hauser
FieldCare
Emerson
Delta V
Emerson
AMS
FC 375
Honeywell
PlantScape
Experion PKS
Invensys
IA Series
Rockwell
Control Logix
Yokogawa
Centum CS3000
Slide
31 / 340
Asset Management
SMAR
System 302
Honeywell
Control Builder
PKS*
Invensys
IA Series
PactWare
Rockwell
RS Fieldbus
Yokogawa
PRM**
How do I find the right DD?

Fieldbus Foundation
www.fieldbus.org
Emerson
www2.emersonprocess.com/enUS/documentation/deviceinstallkits/Pages
/AboutDeviceInstallKits.aspx
Yokogawa
www.yokogawa.com/fbs/fbs-interoperability-en.htm
Honeywell
hpsweb.honeywell.com/Cultures/enUS/Products/Systems/ExperionPKS/FieldbusInteroperabilitySupport/Devic
esTestedbyHoneywell/Documents.htm
Slide
32 / 340
Slide
33 / 340
Wie finde ich das richtige DD?
Slide
34 / 340
Analog to Fieldbus Digital Communication

FOUNDATION Fieldbus Basic Training III
PC-PS
Slide 35
Analog Data Transmission
Slide
36 / 340
Digital Data Transmission
1 0 0 1 0 0 1
Slide
37 / 340
Value Transmission Technology

PLC / DCS
16 bit
16 bit
CPU
16 bit
mA
CPU
Analog
16 bit
Slide
38 / 340
CPU
Identification
Digital tag:
software version:
serial number:
etc. .....
1st process value
2nd process value
engineering unit
status
diagnostic
CPU
= PI 012
= 1.1
= 0M60237
= 70.32
= 230.2
= mbar
= good/bad
= temperature high
Expanded System View

Limited system view
Does not include diagnostics and
other information from field devices.
Expanded view
Field devices are part of the system.
Slide
39 / 340
Identification tag:
software version:
serial number:
etc. .....
1st process value
2nd process value
engineering unit
status
diagnostic
= PI 012
= 1.1
= 0M60237
= 70.32
= 23.02
= mbar
= OK
= temperature high
Value Transmission Technology

PLC / DCS
16 bit
16 bit
4 20mA
CPU
16 bit
mA
CPU
Analog
16 bit
16 bit
mA
D
A
CPU
A Smart Signal
D
16 bit
CPU
Analog + digital (hybrid)

16 bit
CPU
Digital
Slide
40 / 340
CPU
4-20 mA - Analog Transmission
Pressure device
e.g. Cerabar S
PLC/DCS
16 bit
I/O
16 bit
16 bit
cable
16.8 mA
16 bit
U [mV] I [mA] P [bar]
Slide
41 / 340
20
1.5
16
1.4
12
1.3
1.2
1.1
0.4
0. 8
1.2
1.6
2.0
2.4
2.8
t [s]
HART - Hybrid Communication
Pressure device
e.g. Cerabar S
PLC/DCS
16 bit
I/O
16 bit
Slide
42 / 340
cable
16.8 mA
16 bit
16 bit
Fieldbus Digital Transmission
Pressure device
e.g. Cerabar S
PLC/DCS
ASIC
I/O
16 bit
Bus cable
ASIC
16 bit
1/0/1/1/0...
or
Slide
43 / 340
System Diagrams
Controller+
Terminal board
Controller
One variable
One way
Multivariable
Bidirectional
4-20mA analog
communication
Slide
44 / 340
Bi-directional communications
possible between control valve,
transmitters and controller
What is a Fieldbus?
The fundamental task of a fieldbus system is to exchange information
digitally
with less wiring (unlike point to point connections )
with more than one participant (several nodes)
safe (communication layers)
fast (real-time)
Slide
45 / 340
Open Technology
Manufacturer
A
Manufacturer
A
STANDARD
DRIVER
A/B
DRIVER
A/C
MANUFACTURER
B
MANUFACTURER
D
MANUFACTURER
C
Slide
46 / 340
DRIVER
A/D
FIELDBUS
INTERFACE
MANUFACTURER
MANUFACTURER
D
B
MANUFACTURER
C
Process Automation Fieldbus features

Process Automation main points:
Open and standardized
Power supplied to the devices (powered network)
Designed for installation in hazardous area
Robust and reliable in industrial environment
Long distance networks (above 500 meters)
Easy for installation and commissioning
High degree of freedom in installation
Exchange and connection of new devices during operation
Fulfilling real-time requirements
Slide
47 / 340
The right Fieldbus for the Process Automation
Established communication systems for process

automation
Slide
48 / 340
fieldbus vs. Fieldbus

fieldbus
any open, digital, multi-drop communications network for
intelligent field devices
Fieldbus
a fieldbus standard (hardware, software and communications
protocol) defined by the Fieldbus Foundation
Slide
49 / 340
OSI Model Fieldbus Layers

FOUNDATION Fieldbus Basic Training IV
PC-PS
Slide 50
Communication Layers ISO/OSI Model

OSI Model
H1 FOUNDATION Fieldbus Model
*Open Systems
Interconnection Reference
Model
User Layer
User Layer
Fieldbus Message
Specification (FMS)
Slide
51 / 340
Application Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Data Link Layer
Data Link Layer
Physical Layer
Physical Layer
Fieldbus Access
Sublayer (FAS)
H1
Communication
Stack
The user layer is not defined by the OSI
Physical Layer
Application Layer
OSI Model
Fieldbus Access Sublayer:

User Layer
Fieldbus Message
Specification (FMS)
Slide
52 / 340
Application Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Data Link Layer
Data Link Layer
Physical Layer
Physical Layer
Fieldbus Access
Sublayer (FAS)
Provides interface between layer 2 and 7

Supports client/server model
Supports publisher/ subscriber model
Supports report distribution model
Fieldbus Message Specification:
Provides encoding and decoding of

user layer messages
Provides logical addressing using
object dictionary
Provides services based object type
It is the responsibility of this layer to provide protocols/services

internally within and between devices on a fieldbus.
What Does FOUNDATION Fieldbus Do ?

Sensor, final control
element or host
Sensor
Moves data from here to there
User Layer
Communication
Layer
Physical
Layer
Slide
53 / 340
Fieldbus Device
You do control, trends,

alarms with data here
Communication Stack ensures

secure communication
You connect wires here
Wire medium
User Layer
Communication
Layer
Physical
Layer
Fieldbus Device
Sensor
Sensor
Process variables (values and status)
Diagnostic data
Calibration data
User Layer
Configuration data
Communication
Layer
Physical
Layer
Slide
54 / 340
User Layer
Sensor
Provides the interface with the
process and for user interaction
with the control system
Uses block structure for interaction:
User Layer
Resource blocks
Transducer blocks
Communication
Layer
Physical
Layer
Slide
55 / 340
Function blocks
Enables trending and alarms

Key differentiating technology in
Foundation Fieldbus
Communication Layer
Sensor
The communication layer (stack)
provides:
Encoding and decoding of the
user layer messages
User Layer
Deterministic control of message

transmission
Efficient and secure message transfer
Communication
Layer
Physical
Layer
Slide
56 / 340
Physical Layer
Sensor
The physical layer converts data
from the stack into a physical
signal on the fieldbus wire
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
57 / 340
The 31.25 kbps H1 physical layer

complies with the approved IEC and
ISA standard for the physical layer
Fieldbus Communications Model

Fieldbus devices and host systems must use a common language
User Layer
Fieldbus Message
Specification (FMS)
Application Layer
Presentation Layer
Slide
58 / 340
Fieldbus Access
Sublayer (FAS)
Session Layer
Transport Layer
Network Layer
Mail message:
Common language
Read & understood
FB: Function Blocks
Paper contains:
TO/FROM
Mail message
FB: Data values
Envelope contains:
Address TO/FROM
Stamp
Mail message inside
Data location is critical
FB: Which message is sent
when by which device
Mailbox:
Data Link Layer
Data Link Layer
Physical Layer
Physical Layer
Wire Medium
TAG TIC 101

Reactor Temperature
PV = 242 degrees C
Holds envelope
Address & flag
FB: Device address
Truck:
transports envelope,
independent of
message
FB: Electrical signals on wire
Fieldbus Communications Model

User
Application Layer
Parameter / FB
Read / Write
10.7 / Good
Data Link Layer

Header
Data
100 0011 0011.
80/33 33 28 41
IEEE
Physical Layer
I
Slide
59 / 340
Bin
1
Data transfer
Tail
Notes
Slide
60 / 340
Physical Layer Topologies

FOUNDATION Fieldbus Basic Training V
PC-PS
Slide 61
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
62 / 340

H1 and HSE Physical Layers
PC
field controller
HSE 100 Mbit/s

linking
device
H1
linking
device
linking
device
31.25 kBit/s
H1
IEC 61158-2
H1 IEC 61158-2
32 devices per
segment
Slide
63 / 340
H1
FISCO
Physical Layer HSE
PC
field controller
HSE 100 Mbit/s
Defined by the IEEE 802.3 specifications.

100 Mbit/s
HSE uses two Ethernet transport protocols to send data over the network.
100BASE-T: two pairs of high-quality twisted-pair wires
100BASE-F: fiber optic cables
In each case, the length of a twisted-pair segment may be
up to 100 meters (328 feet). Possible to expand with repeaters.
Slide
64 / 340
Physical Layer H1
linking
device
H1
linking
device
linking
device
31.25 kBit/s
H1
IEC 61158-2
H1 IEC 61158-2
H1
FISCO
32 devices per
segment
Defined by the IEC 61158-2 specifications.

Up to 32 participants per segment (up to 10 for EEx-ia IIC applications)
Remote power supply and communication in 2-wire technology
Designed to be installed in explosive area (Zone II/I; Class I Div1/Div2)
Fixed transmission rate of 31.25 kBit/s
Cable (twisted pairs line length up to 1900m (EEx-ia up to 1000 m)
Slide
65 / 340
Basics of Termination
Fieldbus devices are connected in parallel on the bus,

which carries digital data from/to all the devices on
the bus.
+
100
Terminator to impedance match circuit and prevent

reflections/ringing
1 uF
100 Ohm resistor

1 F capacitor
Terminator must be placed at the beginning and at the
end of a segment
Slide
66 / 340
Do NOT make your own!
H1 possible Topologies
Operator Workstation
Engineer Workstation
Junction
Box
Power Conditioner
+ terminator
H1
Tree
Point-to-Point
Bus with Spurs
Slide
67 / 340
= terminator
Daisy Chain
Daisy Chain Topology

If a field device must be replaced (e. g. depending on a fault or maintenance)
the transmission cable must be interrupted
All field devices to the right of the defective field device will fail additional
All field devices to the left of the defective field device will perhaps continue
the communication
H1
Slide
68 / 340
To avoid this, Junction Boxes are required !
H1 Combined Topology
Combined topology*/ H1
Operator Workstation
Engineer Workstation
Junction
Box
Power Conditioner
+ terminator
H1
Bus with Spurs

Slide
69 / 340
Daisy Chain
* (Possible with fieldbus, but not likely)
Tree
Bus/Spurs Topology
Bus / Spurs
Home Run Cable
Power
Supply
Slide
70 / 340
Power Conditioner
+ terminator
Spur
Cable
Terminator
Tree Topology
Tree
Power
Supply
Power Conditioner
+ terminator
Junction Box
(with Terminator)
Slide
71 / 340
Bus/Split Spurs Topology

Bus / Split Spurs
Home Run Cable
Power
Supply
Power Conditioner
+ terminator
Spur
Cable
Split spur
Junction Box
(with Terminator)
Slide
72 / 340
Junction Box Wiring Example
Inside Junction Box

To
Controller
or main trunk line
Twisted Pair
(Shielded)
Fieldbus
Terminator
Field Wiring
and Field Devices
Slide
73 / 340
Typical H1 Segment Topologies Summary

Home Run Cable
Bus / Spurs
Terminator
Spur
Cable
Tree
Home Run Cable
Junction Box
(with Terminator)
Spur
Cable
Bus / Split Spurs

Slide
74 / 340
Split spur
Junction Box
(with Terminator)
Examples
Slide
75 / 340
Notes
Slide
76 / 340
Physical Layer Components

FOUNDATION Fieldbus Basic Training VI
PC-PS
Slide 77
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
78 / 340

Fieldbus Components for H1 segment

Bus Terminator
Repeater
Power Supply
Power Conditioner
Fieldbarrier / Multibarrier
Junction boxes
Overvoltage protection
Wires
H1 Card
Slide
79 / 340
Local Displays
7 / 8 Plugs
Female
Male
Front View
Pin 1 : blue / blue

( - voltage)
Pin 2 : brown / orange ( + voltage)
Pin 3 : bare
Pin 4 : green/yellow*
(shield)
(ground)
*never wire the ground pin!

Slide
80 / 340
Possible Qualities of Junction Boxes

IP protection
Indication LED
Active / passive
Connector type (PG, 7/8, M12 or terminals)
EX version
Mounting (Din rail,)
Terminator with on/off switch
Removable spur wiring connections
Slide
81 / 340
Protector functionality
Bus Topology with spurs

For the Bus/Spurs, Split Bus/Spurs and Tree topology
Junction Boxes are required
Active Junction Boxes can be used
Segment Protectors have a current limitation (e. g. 45 mA)
at the spur outlet and prevent the complete segment from failing
An active Junction Box causes an additional voltage drop
(depends on the vendor) and has a current consumption
(depends on the vendor)
Slide
82 / 340
Connection example
Slide
83 / 340
Junction Box - MTL

Fieldbus Megablocks
Connects spurs to trunk cable
2/4/8/10 and 12 devices supported
per hub
Short-circuit protected with visual
fault indication.
Optional, terminator with on/off switch
Removable Spur wiring connections
Global hazardous area approvals
Encapsulated for environmental protection
Can also be provided mounted in
suitable enclosure for ambient environment
Slide
84 / 340
Junction Box - TURCK

FOUNDATION fieldbus IP67 junction box, 6-channel
Junction box for wall mounting with stainless steel 7/8" flange connections
Integrated terminating resistor (switch-in)
Cable shielding: capacitive or direct connection to housing potential
selectable via switch
Powder-coated die-cast aluminum housing
Pressure compensation element for protection against condensation water
Connection of the housing potential via an M5 x 1 bolt
T connector example
Slide
85 / 340
Junction Box Pepperl+Fuchs

Passive fieldbus junction box
Versions with 4, 6 or 8 channels
Fieldbus terminator with on/off switch
Variants with different plug connections
Different versions of shielding are possible
Slide
86 / 340
Junction Box Pepperl+Fuchs

Fieldbus distributor with individually short-circuit
current limited outlets
12 outlets for the connection of spurs to one
field device each
Installation in Zone 1/Class I, Div. 2
Connection of Ex d certified devices
located in Zone 1/Class I, Div. 1
Built-in surge protection for trunk and spurs
Fieldbus terminator with on/off switch
Integrated Fieldbus status and fault indication
via LEDs
Slide
87 / 340
Junction Box Moore Hawke

Moore Hawke
Stone L
Slide
88 / 340
Alternate Junction Box (example)

FBCon fieldbus integrators
7/8 plug-and-socket connection
Tension clamp connection technology
EMC cable glands
External earth connection
Uninterrupted Bus operation
Easy to use
Low installation costs
EX version TATEX is pending
Pressure compensation element
Slide
89 / 340
External bus termination
External terminator
Terminator
A terminator is used at the beginning at the end of a segment to
avoid reflection.
Terminator impedance value is equivalent to an impedance
100 Ohm and 1uF.
Slide
90 / 340
Cable Types
The physical layer specification IEC 61158-2 defines
4 types of cables:
Cable type A: shielded twisted pair
Cable type B: one or more shielded twisted pair
Cable type C: one or more non-shielded twisted pair
Cable type D: multiple conductor cable not twisted with overall shield
Type A
Type B
Type C
Type D
Slide
91 / 340
Cable Types
Cable type A is the preferred cable type
Only with cable type A you can reach the max. cable length of
1900 m for Non-IS application
1000 m for IS application (in acc. with FISCO model)
Slide
92 / 340
Cable Type Main Characteristics
Slide
93 / 340
Cable design option

Mechanical Protection
armor of corrugated steel tape
Chemical Protection
Improved Fire Behavior
armor of galvanised round steel wires
with multilayer sheath

armor of galvanised steel wire braid
Slide
94 / 340
Example of Kerpen cable
Slide
95 / 340
Power Conditioner
An ordinary constant voltage power supply cannot be used directly to
power a Fieldbus.
A power conditioner (PC) needs to be used to provide an isolation between
the network and the power source so that the communication signal
on the network get equalized and compensated by by the power source.
Images below represent the basic required circuit though all manufacturers
incorporate additional features.
H1 Fieldbus
Slide
96 / 340
Power
Supply
FF Host
Conditioner
Example
of power conditioner
Power Supply / Power Conditioner

Fieldbus Power Supply:
A galvanically isolated power source followed by a power conditioner
necessary to power a fieldbus segment combined in one device.
Fieldbus Power conditioner type 1:

Circuit necessary to power a fieldbus segment from a galvanically isolated
constant voltage power supply intended for use with non-specific
general purpose power supplies.
Fieldbus Power conditioner type 2:

Circuit necessary to power a fieldbus segment from a galvanically isolated
constant voltage power supply intended for use only with specific general
purpose power supplies.
Slide
97 / 340
FPC Fieldbus Power Conditioner

230VAC
Turck, Power Conditioner 2 channel

Part Nr: 6603801
Standard 24v DC
Power Supply
Power Conditioner
+ terminator
Slide
98 / 340
Relcom, FCS-BPC series

Power Conditioner
Combined products
230VAC
Power Supply +
Power Conditioner+
terminator
Or
Example:
Relcom Dual Fieldbus Power Supplies provide isolated power
conditioning for two (2) Fieldbus H1 Network segments
and facilitates the connection of redundant input power supplies.
Slide
99 / 340
Fieldbus Power Hub

230VAC
Pepperl+Fuchs, Fieldbus Power Hub

MB-FB-System
Standard 24v DC
Power Supply
Power Conditioner
+ terminator
Power supply system for

FOUNDATION Fieldbus H1
For applications with all Host systems
Collective error message and diagnostic
bus for several modules
Slide
100 / 340
Various isolation and redundancy concepts
Power supply / conditioner for FISCO, FNICO

Power supply and Conditioner in one unit
MTL FISCO power supply IIC-9121-IS (5 x 20 mA)
MTL FISCO power supply IIB-9122-IS (12 x 20 mA)
MTL FNICO power supply IIC-9111-NI (12 x 15 mA)
MTL FNICO power supply IIB-9112-NI (20 x 15 mA)
Slide
101 / 340
H1 - I/O Interface Cards

A H1 I/O-card provides a direct link to a Foundation Fieldbus network.
There are different types of interfaces:
PCMCIA/H1 cards
PCI/H1 cards
USB/H1 modules
Ethernet/H1 modules
Slide
102 / 340
Linking Devices for Foundation Fieldbus
ABB FIO-100
E+H SFC162 Controller

HSE
Linking
H1
Device
Emerson HSE Linking Device
H1
Softing FieldGate FF
Fieldbus Foundation H1-Segment
Slide
103 / 340
Why Overvoltage Protection?

Due to the increased use of sophisticated microcontrolled electronics, there is a growing demand
for overvoltage protection
Overvoltage protection can prevent the destruction
of electronic components and the resulting failures
of entire plants.
Destruction of electronic components is caused by:
High load switching
Lightning induced voltage impulses
The cost for overvoltage protection is in most cases

only a fraction of the financial loss caused by
outages and damage.
Slide
104 / 340
Close or direct influence / galvanic influence quantity
earth 1
Slide
105 / 340
earth 2
Indirect influence / inductive and capacity influence quantity
L
C
Line loop
earth 1
Slide
106 / 340
earth 2
Protection example
Slide
107 / 340
Functional construction
Rough protection
e.g. discharge
line
t
Decoupling comp.
e.g. resistance
inductance
capacitance
filter
Fine protection
e.g. Suppressor
diode
Low and matched impedance between the individual protection stages in

the unit guarantee high compatibility with the system to be protected !
Slide
108 / 340
Selection of Overvoltage Protection
Also for FF applications
Slide
109 / 340
E+H HAW 569

Over voltage protection for 4-20mA,
Profibus-PA, PFM
Easy installation between sensor
housing and cable gland
Intrinsically safe version as an option
Corrosion resistant and water proof field
housing
Screw connector M20 x 1,5
Support of 3 shielding concepts
Slide
110 / 340
E+H HAW 569
Slide
111 / 340
Lightning and Surge Protection -You Choose

Surge Protection is often taken for granted and not
specified!
Surge Protection reports additional Operating Expenses
(OPEX) benefits through:
Higher System Integrity

Increased Reliability
Reduced Downtime
Reduced Spares Inventory
Slide
112 / 340
Topology with Multibarrier/ Fieldbarrier
Power Conditioner
+ terminator, 500mA
Foundation Fieldbus H1
Main trunk EEx e
EEx ia outlets
Slide
113 / 340
T
Zone 1
Zone 0
Field Barrier / Multibarrier

Use of standard power supply (non-Ex): cost savings
Intrinsically safe outlets: conform to the FISCO model
High-performance in the field using the Ex e supply concept
Short-circuit protected, intrinsically safe outlets
Integrated fieldbus terminator
40 mA outlet current per channel (P+F)
Max. spur length: 120 meters (P+F) each
Outputs galvanically isolated from the supply loop (P+F)
Barriers replace field wiring junction boxes
Short-circuits in one outlet do not affect bus communication
or remaining outlets
Slide
114 / 340
Pepperl+Fuchs Field Barrier (Example)
Fieldlink (FD02-FB-EX4.CG)
ignition protection class:
Ex me [ia]IIC T4
voltage Uo:
15,75 V
current Io:
248 mA
power Po:
975 mW
I operation current:
up to 220 mA,
40mA/outlet
short circuit: :
yes
(Ioc up to 256 mA)
galvanic isolation:
yes
grounding:
hard, capacitive
Slide
115 / 340
Pepperl+Fuchs Field Barrier (Example)

On/Off Fieldbus
Termination Resistor
LEDs
Cover for
Ex e
Terminals
Ex i
Terminals
Trunk In
Cable Glands
Grounding
Point
Slide
116 / 340
4 Outlets with
Cable Glands
Trunk Out with

Cable Glands
Pepperl+Fuchs Field Barrier
Slide
117 / 340
Pepperl+Fuchs Field Barrier
Slide
118 / 340
TURCK Multibarrier (Example)

Field devices in EX areas
4 intrinsically safe short-circuit-proof 40 mA outlets

Galvanic isolation: Outlet-Outlet; Trunk line-Outlets
Integrated Termination (on/off switch)
Zone 1 - Admittance
Slide
119 / 340
Stahl Fieldbus Barrier (Example)

Approval for Class I, Div 2 installation with IS
spurs in progress
Standard Glass Reinforced Polyester and
Stainless Steel options
9311-FB DIN-rail mount module
Intelligent power management

Low start-up current
Multiple spur short-circuits have no impact
Comprehensive cable shield grounding options
Custom enclosure example
Configurable to achieve best performance in

noisy environments
Wide ambient temperature
Comprehensive LED fault indication
Slide
120 / 340
Standard GRP enclosure
Installation Examples
Slide
121 / 340
Notes
Slide
122 / 340
Communication Layer Principles

FOUNDATION Fieldbus Basic Training VII
PC-PS
Slide 123
Communication Layer
Sensor
The communication stack
provides:
user layer messages
User Layer

transmission
Communication
Layer
Physical
Layer
Slide
124 / 340
Device Identification
How does the system know what kind of device is connected on the bus?
Tag name (PDTag)
User level
Who are you ?

+
Device ID
Unique number
Bus address
Slide
125 / 340
Example:
Low level (up to the system)
Deltabar S / 452B481009- 7PY018575 / 25
Device Identification Device ID
H1
Every FF device has a specific device
( vendor number // device number // serial number )
Slide
126 / 340
Manufactor ID - Endress+Hauser
452B48
Device Type - Cerabar
1007
Serial number
- 7PY015575
FF device ID example:
452B481007- 7PY015575
Device Identification Node Address

The address range of a bus participant is spitted in to
three major parts:
Assigned -> final destination, ready for operation
Temporary / Default -> Not commissioned / not operational
Visitor -> handheld
Visitor: 0x
Assigned address: 0x10
H1 Bus segment
Temporary / Default address: 0xF8

Slide
127 / 340
Device Identification Device Tag

Configured or Pre-Configured
Device Tag
Tag =
TIT1701
Slide
128 / 340
Device Configure Set Tag and Address

Change Device ID
NO
Not possible to change
Change Tag
Yes
Set Tag by user
Change Address
Yes
Set Address by user or system
No Valid Address
No Tag
TIT1701
Set Tag
Slide
129 / 340
No Valid Address
0x18
TIT1701
Set Address
Device Configure Set Tag

Set the PDTag consists of giving a unique 32 characters name
to the device
Slide
130 / 340
Device Configure Set Address

Set Address consists of giving a final valid address to the device
to become operational
Slide
131 / 340
Link Active Scheduler (LAS)

Network Administrator
Manage all the bus
communication
Knows all devices
Broadcast timing of all devices
Slide
132 / 340
Chief of the bus!

Task for Network Administrator
Keeping the Live List. This list, in which all the fieldbus
users are recorded, is checked by the LAS regularly.
Recognition and reporting of newly connected devices
Reporting the removal of devices no longer communicating with the
fieldbus.
Requesting process data from the field devices in accordance with

a fixed and deterministic schedule
Allocation of send rights (tokens) to devices between the
unscheduled data transfer
Slide
133 / 340
LAS - TD Time distribution
TD = Time distribution
Time Synchronized !
Slide
134 / 340
LAS - Live List Maintenance

Live List
Device:
Deltabar S
Micropilot M
Valve
X
ID:
452B48 1009 -7PY018575
452B481011- 7PY018568
000E050320- ND800FF94
X
Address:
25
27
28
X
LAS
PR = Probe response
PN = Probe node
Identif PN = Probe node
No response
Y
Slide
135 / 340
25
27
Field devices
28
LAS - Live List Maintenance / Pass Token

Live List
Device:
Deltabar S
Micropilot M
Valve
X
ID:
452B48 1009 -7PY018575
452B481011- 7PY018568
000E050320- ND800FF94
X
Address:
25
27
28
X
LAS
PT = Pass Token
No response
Y
Slide
136 / 340
25
27
Field devices
28
LAS - Scheduled Data Transmission
Strategy
Engineer
Transmission &
Schedule.
Transmission lists
LAS
Slide
137 / 340
LAS - Scheduled Data Transmission

CD is a token for the publisher
DT interprets as returned token
Transmission lists
LAS
CD = Compel Data
CD = Compel Data
DT = Data transfer
(Broadcast)
Transmission lists
Slide
138 / 340
Publisher
Publisher
Transmission lists
Subscriber
Subscriber
LAS - Unscheduled Data Transmission / PT Pass Token

Live list
Device:
Config Tool
Ceraber
Micropilot
Valve
XXX
Address:
16
25
27
28
XX
Token
PT = Pass
Token
Eg.Device configuration Tool

Token
RT = Return Token
DR = Data Request
(eg. index: 202,208..)
Slide
139 / 340
Field devices
LAS - Unscheduled Data Transmission / PT Pass Token

Live list
Device:
Config Tool
Ceraber
Micropilot
Valve
XXX
Address:
16
25
27
28
XX
PT = Pass Token
DT = Data Transfer
RT = Return Token
Token
Token
Slide
140 / 340
Eg.Device configuration Tool
Field devices
LAS Main Operation

Task for Network Administrator
TD (Time Distribution): for time synchronization of
every device on the network
CD (Compel Data): schedule for scheduled, cyclic and
highest priority communication
PT (Pass Token): for unscheduled, acyclic, no priority communication
Live List Maintenance
PN (Probe Node): to address device not in the live-list
PR (Probe Response): for the devices that received and
answer a Probe Node
Slide
141 / 340
PT (Pass Token): removed if not answering PT (3 times consecutive)
Communication schedule
The LAS follows a strict schedule
Slide
142 / 340
Scheduled Communication Publisher/Subscriber

Scheduled communication (deterministic)
Publisher/Subscriber
Slide
143 / 340
Control
Publisher
Subscriber
Non-Scheduled Communication Client/Server

Non-Scheduled communication
Client/Server:
Read, write configuration data
Slide
144 / 340
Non-Scheduled Communication Report Distribution

Non-Scheduled communication
Report Distribution:
Alert data
Slide
145 / 340
Device Operational Functional Class

There are 3 Operational Functional Classes
of FOUNDATION Fieldbus devices:
Basic
Link Master
Bridge
The class gives a direct indication on the capability of the device

from an operational function on the bus
Slide
146 / 340

Basic Class
Basic devices are simply transmitters or final control element performing
all of the basic functions.
They are not capable of supporting the function of the Link Active
Scheduler (LAS)
Slide
147 / 340
not capable of supporting the function of LAS

Link Master Class
Link Master Class devices are similar in function to the basic class device
but are capable of supporting the functions of the Link Active Scheduler
(LAS)
Slide
148 / 340
capable of supporting the function of LAS
Identify three Fieldbus Device Types

Bridge Class
The bridge class supports all of the functions af the basic devices and the
link master class devices. It further supports the ability to connect
multiple FOUNDATION fieldbus segments.
Linking devices are bridge class devices. ( in the same groupe)
Slide
149 / 340
capable of supporting the function of LAS
Bridge Class Devices

Used to interconnect 31.25 kbps H1 and High Speed Ethernet (HSE)
backbone running at 10 or 100Mbps
The following table outlines the differences between Linking Devices
and Bridges:
Slide
150 / 340
Bridge Class Profile

Function
Class
H1 to H1
H1 to HSE
Republishing
Linking
Device
42a
No
Yes
Bridge
42c
Yes
Yes
Bridge Class Device

The following table outlines the major functions added
with each profile class:
Bridge Class Profile Number
Functions Included
42a
Configuration of H1 Nodes
42b
Monitoring of H1 Nodes
42c
H1 to H1 Republishing
42d
Flexible Function Block
Example:
The 42c class device can do all the functions of classes 42a and 42b
in addition to the functions of a 42c device but cannot do any
functions of a 42d device
Slide
151 / 340

Backup LAS
If only one device supports the LAS functionality, this device will keep
the task as LAS
Basic class
device
Slide
152 / 340
Link Master
class device

Backup LAS only one device becomes the LAS
If in a segment several Link Master class devices are available, only one
device becomes the LAS.
Backup rule
Link Master
class device
Slide
153 / 340
Link Master
class device

LAS Redundancy - Transfer LAS
Slide
154 / 340
If there are multiple Backup Link Master devices on a segment, then

the device with the next lowest network address will be assigned
the primary LAS function
Backup LM location
Rules for the selection of the device to act as the backup Link Master:
Field device with the lowest commissioned FOUNDATION Fieldbus
device address.
Field Device with limited maintenance potential
If maintenance required, not available as backup
Field Device that is common to the plant

Ease of replacement in the event of service
Field Device with multiple CPUs or low utilization of clock resources

Simple application of AI block
Slide
155 / 340
Notes
Slide
156 / 340
Device Drivers
FOUNDATION Fieldbus-Advanced Training I
PC-PS
Slide 157
Drivers - DD and CFF files
Device from
Supplier A
Device Description
Device from Supplier A
Fieldbus
DD Service
Inside
Device from
Supplier B
Capability File
Device from Supplier A
Slide
158 / 340
Drivers - DD and CFF files
DD - .ffo
DD - .sym
Slide
159 / 340
DD - .cff
DD and CFF files

Three driver files :
Device Description file (DD)
.sym file
.ffo file or.ff5 file
Capability file (CFF)

.cff file
Single zip file that can be downloaded from FF website
Slide
160 / 340
DD and CFF files
DD
For offline & online configuration
For offline configuration

Capability file
.ffo
.sym
Slide
161 / 340
.cff
Device Description File - Content

Extended Descriptions
Label of the parameter
Engineering units
DDL Source File

Variable Process Variable
{ Label Measured_Value:
Type Float
{Display_Format 3.1;
Max Value 110.0..
Number of decimal digits

Help text
Parameter relationships
Calibration and diagnostic menus
Methods
Slide
162 / 340
DD Token File (.FFO)

9 101
2 Measured_Value
1 010
61 3.1
.
Device Description File - Content
Device
Floating Point Value
Slide
163 / 340
Device
Description
DD Services
Packet Assembly
Read Value
DD Files / mapping
Example block error:
DD
DD
Status byte = 0x2A
Extensions:
0x2A: Block error
0x21: Out of service
.
Block error !
Configuration tool
Slide
164 / 340
Device Description File - Methods

Methods can be used as Wizard for the setup/configuration of the
devices
Not all devices support this functionality
Slide
165 / 340
Device Description File - Download
Slide
166 / 340
Capability File - Content
VCRs
Device Name
& Class
Power
Requirements
Function Block
Execution Time
1280/32=40ms
Slide
167 / 340
Manufacture ID
How does the system know which DD belongs to which device?
Identify the device manufacturer by his ID
Manufacturer ID is a unique code given to the manufacturer by the
Fieldbus Foundation.
It is a hexadecimal expression.
Example: It is a FF Device, Manufacturer = 452B48 =
Slide
168 / 340
Device type
Device type identifies the device from others of the same

manufacturer by the two-byte data expressed in a four-character
hexadecimal form.
Example: It is a FF Device, Manufacturer = 452B48 =Endress+Hauser;
Device type = 1051 = Promass 83
Slide
169 / 340
Filenames / revision
The file names belongs to the revision.

FFO file:
SYM file:
CFF file:
Slide
170 / 340
Device revision / DD revision

Device revision / DD revision
Device revision / DD revision / CFF revision
Device Library example
Vendor Name
-> Device Name
Slide
171 / 340
ManufacturerID
-> Device Type
Device Library example
Device Revision
Drivers
CFF (CFF)
DD (SYM+FFO)
Slide
172 / 340
Integration vs. Driver Technology
Frame
Integration
technology
Driver
Driver
technology
DTM
Slide
173 / 340
DTM Drivers
Slide
174 / 340
Notes
Slide
175 / 340
Address range
FOUNDATION Fieldbus Advanced Training II
Slide 176
FF Training
Communication Stack
Sensor
The communication stack

provides:
user layer messages
transmission
User Layer
Communication
Stack
Physical
Layer
Slide
177 / 340
FF Training
Device Identification Node Address / Recap

The address range of a bus participant is spitted in to
three major parts:
Assigned -> final destination, ready for operation
Temporary / Default -> Not commissioned / not operational
Visitor -> handheld
Visitor: 0x
H1 Bus segment
Temporary / Default address: 0xF8

Slide
178 / 340
FF Training
Device Identification Node Address Range

0-15 are reserved
16247 are available for permanent devices.
Some host systems may further subdivide this range.
This range is typically shortened for efficiency
248251 are available for devices with no permanent address such as
new devices or decommissioned devices
252255 are available for temporary devices, such as handhelds
Slide
179 / 340
FF Training
Device Identification Node Address detailed
Slide
180 / 340
FF Training

Dead address range where the nodes are not polled
Slide
181 / 340
FF Training
Slide
182 / 340
0x18 (20)
0xF7 (247)
0xF8 (248)
Operational
Operational
Link Master
Basic
Initialize or
Uninitialized
FF Training

Address conflict:
Case1:
D1 at 0x18 and D2 at 0xF8 from the shelf -> OK no collision.
Case 2:
D1 at 0x18 and D2 at 0x18 from the shelf -> Collision !!
The DLL layer makes sure that device D2 does not affect
the communication on the segment and that D2
automatically goes into address range F8
Slide
183 / 340
FF Training
Device Configure Set Address

Set Address consists of giving a final valid address to the device
to become operational
Slide
184 / 340
Notes
Slide
185 / 340
User Layer Function Blocks

FOUNDATION Fieldbus Advanced Training III
PC-PS
Slide 186
User Layer
Sensor
Provides the interface with the
process and for user interaction
with the control system
Uses block structure for interaction:
User Layer
Transducer
Block
Resource blocks
Function
Block
Transducer blocks
Communication
Layer
Physical
Layer
Slide
187 / 340
Resource
Block
Function blocks
Enables trending and alarms

Key differentiating technology in
Foundation Fieldbus
Function Block Model
Inputs
Outputs
Algorithm
Example: PID
Standard Block
Parameters
Mode, etc
Slide
188 / 340
Block Specific
Parameters
Bias, etc
Function Block Class
Resource Block
Transducer Block
Function Block
Slide
189 / 340
maintenance
field technician
programmer
Resource Block
Resource Block:
device type
manufacturer
software version
hardware version
diagnosis
...
Slide
190 / 340
This block contains data that is specific to the hardware and associated
with the resource. The mode of the Resource Block controls the mode
of all other blocks in the device.
Transducer Block
Transducer Block:
level
flow
pressure
analytical
temperature
valve positioner
Transducer blocks insulate function blocks from the specifications of I/O

devices, such as sensors, actuators, and switches. Transducer blocks
control access to I/O devices through a device independent interface
defined for use by function blocks.
Slide
191 / 340
Function Block
Function Block:
analog input
analog output
analog input
analog output
PID
signal characterizer
The Function Blocks are part of the Foundation Fieldbus specification

and the key to the possibility of using control loops in the field.
Slide
192 / 340
It is the responsibility of the device manufacturer to decide on the kind

of function block he wants to implement.
Function Block classification

Function Blocks are placed into three classes:
Standard Block as specified by the Fieldbus Fundation

Enhanced Block with additional parameters and algorithm
Open Block or a Vendor-specific Block designed by individual
vendors
Slide
193 / 340
Standard Function Block Types
Slide
194 / 340
Analog Input
AI
Analog Output
AO
Bias/Gain
BG
Control Selector
CS
Discrete Input
DI
Discrete Output
DO
Manual Loader
ML
Proportional/Derivative
PD
Proportional/Integral/Derivative
PID
Ratio
RA
FF-891
(Part2)
Slide
195 / 340
Device Control
DC
Output Splitter
OS
Signal Characterizer
SC
Lead Lag
LL
Deadtime
DT
Integrator (Totalizer)
IT
Setpoint Ramp Generator
SPG
Input Selector
IS
Arithmetic
AR
Timer
TMR
Analog Alarm
AAL
FF-892
(Part3)

Multiple Analog Input
MAI
Multiple Analog Output
MAO
Multiple Discrete Input
MDI
Multiple Discrete Output
MDO
FF-893
(Part4)
Slide
196 / 340
Enh. Flexible Function Block (Part5 FF-894)

A flexible Function Block (FFB) is a user defined block
The FFB allows a manufacturer or user to define block parameters and
algorithms to suit an application that interoperates with standard
function blocks and host systems
Slide
197 / 340
Enhanced Function Block Types

Supplier can take a standard function block and add on some specific
parts, algorithm, functions etc..
Enhanced Setpoint Generator
ESPG
Enhanced PID
EPID
Advanced PID
APID
Standard function block
ALGORITHM
Additional implemented function

Slide
198 / 340
Enhanced Function Block
Manufacturer Specific Function Block Types

Examples:
Function Block:
Flip Flop and Edge Trigger
FFET
Hardware Configurator
HC
Modbus Configuration Block
MBCF
Slide
199 / 340
Name Symbol:
Transducer / Function Block Types
Transducer
Transducer
Control Strategy
Channel
1
2
3
4
Channel
PI
Standard function block
Manufacturer specific
Slide
200 / 340
AO
1
2
Transducer / Function Block Types
Transducer
Transducer
Control Strategy
Channel
1
2
3
4
Channel
A
+
PI
+
Enhanced Manufacturer
function block
Profile specific transducer

Slide
201 / 340
(Pressure, Temperature )
AO
1
2
Linking Function Blocks

AI
AI
DI
AI
ML
PID
Input
PD
AO
AO
AI
AO
Manual Control
PID
AO
Feedback Control
AO
Track, Feed forward
Capability in Control
AI
AI
AI
PID
PID
AI
RA
AI
AI
PID
PID
SS
PID
PID
AO
AO
AO
Override Control
Slide
202 / 340
AI
DI
DO
Output
AI
Ratio Control
Cascade Control
BG
BG
AO
AO
Split Range Control
Various measurement and control applications can be built by linking

these Function Blocks. Figure shows typical examples using Part-2
blocks.
Path of signal in a fieldbus device

H1 FOUNDATION Fieldbus
OUT
mV
Slide
203 / 340
Measurement
RS Block
Transducer
Transducer
Transducer
Transducer
PID Block
PID Block
Control
AI Block
AI Block
AI Block
Parameters example; Function Block Analog Input AI

OUT
Schematic AI - Function Block
AI Block
Transducer
mV
Sensor raw value
Slide
204 / 340
The AI block takes the input data from the transducer block and
makes it available to other function blocks.
Function Block Analog Output AO

The Analog Output function block includes the same parameters
as the parameters for the Analog Input
In addition to these parameters, the Analog Output function block
has parameters for the setpoint
IN
AO Block
Transducer
mV
Slide
205 / 340
Actor
Write Lock
When write protection is activated, parameters cannot be modified
The current write protection status is displayed in the WRITE_LOCK
parameter (Resource Block)
Slide
206 / 340
Example: E+H / TMT 162
Simulation
Simulation active = DIP switch for simulation mode active.
The SIMULATE parameter allows you to replace the input value with
a simulation value and activate simulation. By specifying the status and
the simulation value, the reaction of the complete Analog Input
function block can be tested.
Slide
207 / 340
Simulating the input of the Analog Input function block

The input value (measured value and status) can be specified by
means of the SIMULATE parameter group
Since the simulation value runs through the entire function block, all
the parameter settings of the block can be checked
Slide
208 / 340
Example:
Notes
Slide
209 / 340
User Layer Function Block Application

FOUNDATION Fieldbus Advanced Training IV
PC-PS
Slide 210
Shift of Control
ControlSystem
Network
Controller
PID
Controller
I/O
subsystem
4-20mA
PID
AO
AI
AI
AO
Slide
211 / 340
Traditional
Fieldbus
Function Block and Control Strategy
PCV
FI302
88
P
LD302
I
Flow
88
SM AR
FV-31
FE-31
Slide
212 / 340
Control In the Field

Control Strategy
function blocks
Data exchange controlled by

Direct data exchange between
field devices is possible
H1
LAS
(LAS)
Every E+H FF device
can become LAS
TM
TM
TM
Slide
213 / 340
TM
I n t e l l i g e n t
TM
F i e l d
D e v i c e s
TM
Function Block and Control Strategy
Slide
214 / 340
Macrocycle & Link Schedule -Simple PID
AI
PID
AO
Scheduled Communication
Unscheduled Communication
Function Block Scheduling
AI
Slide
215 / 340
PI
AO
Alarms/Events
Maintenance/Diagnostic Information
Program Invocation
Permissive/Interlocks
Display Information
Trend Information
Configuration
Macrocycle & Link Schedule Mode Loops
AI
PID
AO
AI
PID
AO
AI
PID
Slide
216 / 340
AO
Function Block Application

Mode Handling, basic configuration and Status
Classification:
INTERNAL
10/18/2006
Slide
Slide 217
217 / 340
Function Block Instantiation
Device Firmware
AI
CHAR
ISS
Insta
ntiat
e3P
ID
ARTH
SPLT
TIMER
.
Slide
218 / 340
Instantiate 2
A
IMER
Instantiate 1 T
AI_1
Function Block Library
PID
Device Memory
AI_2
PID_1
PID_2
PID_3
TIMER_1
.

Customize the Device Functionality.
Configuration Flexibility.
Field Control.
Field Control Distribution Flexibility.
Better Device Performance
Only used block are running.
Better Control Performance.
It is possible to minimize external links.
Slide
219 / 340
Methods
Methods are an optional addition to Device Descriptions.
Methods are used to define automate procedures, such as calibration, for
operation of field devices.
Slide
220 / 340
Example NI tool:
Function Block Modes

All blocks have their mode, expressed by the MODE_BLK parameter.
It is a record of four components:
Target
Actual
Permitted
Normal
.
Slide
221 / 340

Overview:
MODE
DESCRIPTION
BEHAVIOR
OOS
Out Of Service
Algorithm not being executed
IMAN
Initialization Manual
Cascade Loop open
Local Override
Algorithm Overridden and output set by

external condition
Manual
Manual Operation - output set by operator
Automatic
Automatic Operation - Setpoint set by operator

Cascade input disregarded
Cascade
Cascade Operation - Cascade input used as

Setpoint
RCAS
Remote Cascade
Remote Setpoint coming from a non FF source
ROUT
Remote Output
Remote Output coming from a non FF source
LO
MAN
AUTO
CAS
Slide
222 / 340

Out of service (OOS)
Algorithm not being executed
The output is maintained at last value or, in case of output class function blocks,
the output is maintained at Fault State Value
Manual (MAN)
Output set by operator
The output is not being calculated, although it may be limited. It is directly set
by the operator through an interface device
Initialization Manual (IMAN)

Cascade Loop open
Local Override (LO)
Slide
223 / 340
Algorithm Overridden and output set by external condition

The output is being set to track the value of the track input parameter

Automatic (AUTO)
The setpoint is set by the operator, cascade input is disregarded
A local setpoint value is used by the algorithm to determine the primary
output value
Cascade (CAS)
Cascade input used as set point
A setpoint supplied by another function block through the cascade input
parameter is used by the algorithm to determine the primary output value
Remote Cascade (RCAS)

Remote Output (ROUT)
Slide
224 / 340
Slide
225 / 340
simulation
Value
Status
scaling
XD_Scale
OUT_Scale
fault values
limits
Fail safe
value
HH
H
L
LL
Process value transferred over the field bus
Value from Transducer
Function Block Model - AI Block
Parameterization - AI Block
130 Parameters !!!
What should I do?
All parameters come with default values.

You must change only some of them to have the
block up and running
Basic operational configuration:

MODE_BLOCK
L_TYPE
XD_SCALE
OUT_SCALE
CHANNEL
Slide
226 / 340
:Auto
:Indirect
:0 - 50 C
:0 100%
:1, 2 or 3
Scaling - AI Block
Parameter L_TYPE controls scaling and square root
Value of a contained parameter PV (Process Value) of AI is
determined by L_TYPE
When its value is direct, Channel value becomes OUT value.
When its value is indirect, Channel value is scaled with
XD_SCALE and OUT_SCALE.
AI
XD_SCALE =
0 - 30 bar
OUT_SCALE = 0 to 100 %
L_TYPE =
Slide
227 / 340
Indirect
Scaling example - AI Block
Slide
228 / 340
Channel Selection AI / AO Block
1
2
Transducer
3
block
Mass Flow
Density
AI Block
Temperature
Channel = 3
Slide
229 / 340
Parameterisation - AO Block
BKCAL_OUT
The value and status required by an upper blocks BKCAL_IN so
that the upper block may prevent reset windup and provide bumpless
transfer to closed loop control.
CAS_IN
This parameter is the remote setpoint value, which must come from
another Fieldbus block, or a DCS block through a defined link.

MODE_BLK.Target
CHANNEL
PV_SCALE
XD_SCALE
SHED_OPTS
Slide
230 / 340
: Cas
: 1,2 or 3
: eg. 100%
: eg. 4-20mA
: Normal Shed, Normal Return
Limits
The limits will be indicated by the transfered status byte
When PV value is smaller than LO_LIM or LO_LO_LIM, a LO or
LO_LO, alarm is generated, respectively
when PV value is larger than HI_LIM or HI_HI_LIM, a HI or HI_HI
alarm is generated.
Slide
231 / 340
Following order is expected:

LO_LO_LIM a LO_LIM a HI_LIM a
Fail Safe Actions

Fault State Actions are embedded on Fieldbus Technology, using all the
Status information.
Temp. Transmitter
AI
BAD
PID
AO
MAN
Fail Safe
Positioner
Slide
232 / 340
With the Fault State Actions configured and taken care on the
Final Element itself.
Process Value and Status
Value
Discrete value
Status
2 byte
Value
IEEE-754 Floating
5 byte
Slide
233 / 340
Status
Function Block Status
BAD -
The value is not useful.
UNCERTAIN -
The quality of the value is less

than normal, but the value
still be useful.
Good -
The value is useful
All Process Data has a Value and a Status

Slide
234 / 340
Function Block Status

All function block input/output contain status transmitted with each
data value. They are mainly used for:
Linking
Calculation
Propagation
Cascade Initialization
Trouble shooting
Quality
Good
Uncertain
Bad
Slide
235 / 340
Sub Status
Non Cascade
Cascade
Device Failure
Limit
High Limited
Low Limited
Constant
Not Limited
Status Included with each Data value transmitted

Some examples:
Good(NonCascade)/Non-Specific/Not Limited
Good(NonCascade)/Active Critical Alarm
Good(Cascade)/Initialization Request
Good(Cascade)/Fail Safe Active
Bad/Sensor Failure
Bad/Out of Service
Quality
Slide
236 / 340
Sub Status
Limit
Simulation
This functionality is very useful in starting up the plant
If you set SIMULATE.EnDisAble to Enabled
AI block uses Simulate Value and Simulated Status as Channel value
instead of Transducer Value and Transducer Status.
Example: Level = 10 meter / good
Slide
237 / 340
This function is active only when Simulation Switch (hardware) is ON!
Input Selector
Slide
238 / 340
The input selector is useful to select incoming value under specific

conditions and forward it to a process
Example Redundant sensors

The Input Selector Block
can take care of it!
AI
AI
OUT
OUT
IN_1
SEL_TYPE:
First Good
Maximum
Middle
Minimum
Average
Operator
IN_2
ISEL
?
OUT
IN
PID
BKCAL_IN
OUT
CAS_IN
AO
Slide
239 / 340
BKCAL_OUT
Input Selector
56.4
72.9

MODE_BLK
SELECT_TYPE
ISEL
56.4
Slide
240 / 340
: Auto
: eg. First good
PID Standard PID Control
The PID block is key to many control schemes and is used almost universally.
Slide
241 / 340
PID parameter description

Parameter:
Slide
242 / 340
Description:
CAS_IN
= input of remote setpoint value from another function block
IN
= input of a process variable from another function block
BKCAL_IN
= the analog input value and status from another blocks
BKCAL_OUT
= output that is used for backward output tracking for

bumpless transfer and to pass limit status
TRK_IN_D
= Discrete Input for activate the external tracking function
TRK_VAL
= input for the external value for tracking from another

function block
FF_VAL
= input of influence quantity from another function block
BKCAL_OUT
= the value and status required by the BKCAL_IN input

parameter of another function block to prevent reset winup
and to provide bumpless transfer to closed loop control
OUT
= the output value and status (control value) of the PID
PID - Let`s tune it !

GAIN, RESET and RATE are the tuning constants for the P, I and D terms.
GAIN is a dimensionless number. RESET and RATE are time constants
expressed in seconds.
Slide
243 / 340
GAIN:
Dimensionless value used by the block algorithm in

calculation the block output.
RESET:
The integral time constant, in seconds per repeat.
RATE:
Defines the derivative time constant, in seconds.

Gain - Proportional Gain
Reset - Integral Action
Rate - Derivative Action
PID Standard PID Control

MODE_BLK
BYPASS
PV_SCALE
OUT_SCALE
SP
GAIN
RESET
RATE
CONTROL_OPTS
SHED_OPTS
Slide
244 / 340
: Auto or Cas
: Off or On
: Ex. 0 to 2 m
: Ex. 0 to 100 %
: Setpoint
: Proportional constant
: Integral constant
: Derivative constant
: Direct Acting
: Normal Shed, normal Return
Notes
Slide
245 / 340
Physical Layer Properties

FOUNDATION Fieldbus Advanced Training V
PC-PS
Slide 246
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
247 / 340

0100110
Bus cable
Physical Layer - H1 MAU
MBP
Sensor
uP
Firmware
MAU
*
Physical layer
Slide
248 / 340
* MAU: Medium Attachment Unit
Physical Layer H1 MAU
0100110
Slide
249 / 340
Manchester Encoding
Fieldbus Signal
Voltage
0.75 to 1.2V p-p
dc bias
9 to 32 Volts
Time
Fieldbus Network
100 Ohm
1uF
Slide
250 / 340
100 Ohm
1uF
Data Frame - Data Encoding

Bit level encoding
puts a time reference on a signal to determine bit boundaries
Manchester bit encoding method
Data
Clock
Encoded
Data
Manchester bit encoding method
Slide
251 / 340
Data Frame
If an oscilloscope were used to observe the signals on the Fieldbus, the
display would show frames with gaps of silence between them, as
shown below:
Slide
252 / 340
Data Frame
The Data portion of a frame can be up to 266 bytes long.
Slide
253 / 340
Data Frame - Packet Construction
Pre
Slide
254 / 340
SD
FCF
SD/DA
Data
CRC
ED
PRE
Preamble
Used to synchronize the bit cell boundaries.
SD
Start Delimiter
Indicates the start of the packet.
FCF
FOUNDATION Control Flag
This lag indicates the packet type and whether

there will be addresses time stamps and also what
type of data is in the packet.
SA /
DA
Destination / Source
addresses
1-3
Depending on the type of packet it will indicate

the source or destination of the packet.
Data
Frame Data
Up to 8,16,32
Minimum of 64,128 or 256 bits.
CRC
Cyclical Redundancy Check
Data integrity error checking
ED
End Delimiter
Indicates the end of packet
Data Frame - Packet Construction
Slide
255 / 340
Acronym
Definition
Number of Octets
Description
Pre
The preamble
1 octet
Used to synchronize the bit cell

boundaries
SD
Start Delimiter
1 octet
Indicates the start of the packet
FCF
FOUNDATION
Control Flag
1 octet
This lag indicates the packet

type and whether there will be
addresses time stamps and also
what type of data is in the
packet
SA,DA
Destination /
Source
addresses
1-3 octets
Depending on the type of

packet it will indicate the
source or destination of the
packet
DATA
Frame data
Up to 8,16,32 octets
Minimum of 64,128 or 256 bits
CRC
Cyclical
Redundancy
Check
4 octets
Data integrity error checking
ED
End Delimiter
1 octet
Indicates the end of packet
Data Frame - Preamble

When a device initiates transmission, it sends out a preamble.
This is a prescribed sequence of 8 bits (one octet) with alternating
ones and zeros
This preamble sequence allows devices to synchronize the bit cell
boundaries
Preamble
Slide
256 / 340
Data Frame - Start-End Delimiter

Fieldbus uses two no-data symbols. N+ that is a high level during the
whole bit cell and N- that is a low during the whole bit cell
Both symbols are used to make an 8 bit start and end delimiter to
show where real data transmission starts and stops
Start delimiter
End delimiter
Slide
257 / 340
Data Frame - Bit cell

Digital data is sent on the Fieldbus at a rate of 31.25 kbits/second
thus, each bit cell is 32us.
A zero is a positive signal transition in the middle of a bit cell;
a one is a negative transition in the middle of a bit cell.
A sequence of Manchester encoded ones and zeros would look like
this
Slide
258 / 340
Fieldbus Signals
32 S
Current
+ 9 mA
- 9 mA
Slide
259 / 340
Physical Layer Installation

Grounding shielding, termination
PC-PS
Slide 260
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Stack
Physical
Layer
Slide
261 / 340

Grounding and Shielding

Central grounding
Tank
Potential matching line
Tank
In neutral star earth bonding it is assumed that the device is electrically

connected to the tank via the process connection.
The Tanks are grounded at a central grounding point.
Slide
262 / 340
Potential matching line

Example:
Rothaus Brewery, Germany
Slide
263 / 340
Grounding and Shielding

There are three main different methods to put the shield of the
wire to the ground.
Those International practice and options for grounding and
shielding of fieldbus systems are based on IEC 61158-2:
Single point grounding
Capacitive grounding
Multiple point grounding
Slide
264 / 340
Isolated installation
The bus shield is not connected
to ground
The devices and other

components could be connected
to ground
Slide
265 / 340
Isolated installation with one ground

The bus shield is only grounded in
one point
The devices and other components

could be connected to ground
Slide
266 / 340
Installation with central grounding

The whole plant is grounded only
at one point

components could be
connected to ground
Slide
267 / 340
Installation with central and capacitive grounding

The different parts of a plant
have different ground potentials.
The bus shield is capacitively
grounded

components could be
connected to ground
Slide
268 / 340
Capacitive grounding
If capacitive grounding on one end is used, there is no need for the
potential equalization conductor for non-Ex applications.
However, the EMC protection is not as good as when the shield is
applied on both sides.
If there is a transition from the hazardous area to the safe area with
capacitive grounding
the capacitor must meet the following requirements:
It must have a solid dielectric, for example ceramic
C < 10 nF
Test voltage > 1500 V
Slide
269 / 340
Installation with multiple grounding

The different parts of a
plant are multiple grounded.
A potential equalisation
line is used.

components could be
connected to ground
Slide
270 / 340
Single Point Shield Grounding
Slide
271 / 340
Multiple Point Shield Grounding
Slide
272 / 340
Multiple Point Shield Grounding with capacitive coupling
Slide
273 / 340
Possibility with Field Barrier (Pepperl+Fuchs)

Safe area
Hazardous area
Fieldbus barrier
Field
device
FF
Power
Repeater
?
Potential equilization
Slide
274 / 340
Hazardous area
With Ex-applications a secure equipotential has to be created

between hazardous and safe area.
Drawback: The cost savings achieved by the fieldbus cabling get
lost.
Possibility with Field Barrier (Pepperl+Fuchs)

Safe area
Hazardous area
FF Power Repeater
Ex e
FieldBarrier
Ex i
Field
device
Hazardous area
Due to the galvanic isolation of the Field Barrier no equipotential

has to be created between the safe and the hazardous area.
The benefits of the fieldbus cabling can be fully realized.
Slide
275 / 340
Terminations on H1 segment
Bus / Split Spurs
Home Run Cable
Power
Supply
Power Conditioner
+ terminator
Spur
Cable
Split spur
Junction Box
(with Terminator)
Slide
276 / 340
Termination in star topology

Foundation Fieldbus H1
Power conditioner
300 m
Junction box
10 m
Slide
277 / 340
30 m
20 m
Termination
Junction box
Power conditioner
10 m
5m
T
50 m
H1
The rule for locating terminators is one that may be bent!

The right hand terminator shown is located at the junction box.
(Ideally it should be placed at the field device on the longest spur)
If one spur is significantly longer, then the terminator is located
at the end of this spur.
Slide
278 / 340
Expanding the segment
Power conditioner
T
PROFIBUS PA
Slide
279 / 340
This segment has just been expanded.

Should the terminator be moved from its original location to the last device
on the segment?
Termination FOUNDATION Fieldbus H1

How to terminate the network
1. The H1 termination could be implemented on Power conditioner
Termination
+
100
1 uF
-
Power conditioner
Advantage:
Slide
280 / 340
No additional costs, since the termination is installed

already in to the power conditioner

How to terminate the network
2.
Termination in the field with special plug, end termination box etc.
Termination in the
T box
+
100
1 uF
-
T-Distributor
Advantage:
Slide
281 / 340
Field device
Because of termination in the T box, a field device can be

removed without influencing the termination.

Signals with correct/incorrect termination
1. Correct termination at both ends.
Slide
282 / 340

Signals with correct/incorrect termination
2. Incorrect termination - just at one end of the bus
Slide
283 / 340
Notes
Slide
284 / 340
Physical Layer Calculation

FOUNDATION Fieldbus Advanced Training
PC-PS
Slide 285
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
286 / 340

FOUNDATION Fieldbus H1 topology

FF interface
Example:
UBUS = 24 V
I BUS = < 400 mA
Slide
287 / 340
H1
MBP
Max. 1900 m
Cable Length Restriction
Trunk line
20 m
50 m
120 m
680 m
Verteiler
Box
60 m
40 m
Spur
Total segment length is limited to 1900 meters (safe segment).
The total segment length is calculated as follows:
total segment length = trunk + all spurs
Trunk = 680 m
Spur = 120 m + 50 m + 20 m + 40 m + 60 m
Slide
288 / 340
Total segment length = 970 m
Cable Length Restriction

FF interface
Trunk line
H1
Spur
Slide
289 / 340
Total
25-32
19-24
15-18
13-14
1-12
1 per spur
1m
30 m
60 m
90 m
120 m
2 per spur
1m
1m
30 m
60 m
90 m
3 per spur
1m
1m
1m
30 m
60 m
4 per spur
1m
1m
1m
1m
30 m
Cable Length and Spurs

Functionality between No. of devices and spur length
No. of devices
1 device
per spur
2 devices
per spur
3 devices
per spur
4 devices
per spur
1 12
120 m
90 m
60 m
30 m
13 14
90 m
60 m
30 m
15 18
60 m
30 m
19 24
30 m
e
r
1m t
o
N
25 32
1m
1m
m
1m
m
o
c
Based on cable type , non-IS area

Slide
290 / 340
d
e
d
1m
n
e
1m
1m
1m
1m
1m
Calculation of Current
Worst Case
m
I SEG = I FDE+
n=1
IBn
I SEG < I S
I SEG
I B1...n
I FDE
IS
m
n
Slide
291 / 340
: total current in a segment (mA)

: basic current of devices
: additional current in case of fault
: current supply of the segment coupler
: number of all devices
: count index
Calculation of Voltage
Worst Case
UBn = US - ISEG x (R x Lges)

U Bn > 9.0 V
U Bn
US
IS
R
L ges
I seg
Slide
292 / 340
: voltage of last device [V]

: voltage of segment coupler
: current of segment coupler
: loop resistance of the wire
: total length
: total current in a segment
Worst Case Calculation

The distribution of stations on the FF-H1 segment can have a negative effects on
the maximum possible line length in certain circumstances.
imax
RL
ix
i1
i2
UL
Uout
Slide
293 / 340
> 9V
RL = Line resistance of the line segment x

ix = Current consumption of the FF-device x
Voltage Calculation and Line Length

Since in practice the stations are not all connected compactly at the end
of the transmission line, the resulting structure is as follows:
In
I2
I1
RL1
RL2
i1
i2
Uout
Slide
294 / 340
RLx = Line resistance of the line segment x

ix = Current consumption of the FF-device x
ix
> 9V
Cable Length Issue Influence factors

If less current is required, the max. cable length increases
If more voltage is available, the max. cable length increases
But for zone 1 or zone 2 applications a voltage limitation is required
Max. cable length will be reduced
The loop resistor of 44 Ohm/km for type A cable is valid for 20C
ambient temperature
Higher temperatures decreases the max. cable length
E.g. loop resistor of type A cable at 50C = 49.15Ohm/km
In practice very often the minimum input voltage of a field device is

defined to 10 V or 11 V
Slide
295 / 340
This decreases max. cable length
Cable Length Issue - Conclusion

A detailed calculation of voltage drop/cable length is required
Perhaps you should integrate a security factor of approx. 10% for the
min. input voltage for the field devices
Minimum input voltage of the field device e 10V
Slide
296 / 340
Segment Design Tool Example Pepperl+Fuchs
Slide
297 / 340
Segment Design Tool Example TURCK
Slide
298 / 340
Notes
Slide
299 / 340
Physical Layer Troubleshooting

FOUNDATION Fieldbus Advanced Training
PC-PS
Slide 300
Physical Layer
Sensor
and vice versa.
User Layer
Communication
Layer
Physical
Layer
Slide
301 / 340

Segment Voltage and Current

IEC 61158-2 specifies the supply voltage to 9V32VDC
Ex Application the supply voltage typically 13.5 VDC
The measured supply voltage depends on the point of measurement
Different results in the control room and in the field
The max. supply current is limited by the fieldbus power supply

(Segment Coupler, Power Conditioner)
Current could be measured
with a specific diagnostic tool (Pepperl+Fuchs)
or using a multimeter in series by opening the fieldbus cable (this implies
a shut down)
Slide
302 / 340
Manchester Bus Powered (MBP)

If a slave communicates, the current signal moves in the area
starting from +9 mA and-9 mA of the sum of all basic current.
Current signal
Bits:
19 mA
I B =10 mA
1 mA
1 Bit 1 Bit
Slide
303 / 340
Example shown above, one slave a 10mA basic current.
Manchester Bus Powered (MBP)
Between 650 mV and 1000 mV
The oscilloscope shows the voltage in relationship to the current signal.
Slide
304 / 340
50%
Supply
voltage
50%
Measuring in the practice

Measuring between data line A and B
data line B
data line A
The measuring channel at the

oscilloscope must be set on AC
Slide
305 / 340
You can measure the signal with the oscilloscope

directly between data line A (-) and B(+).
Measuring in the practice

Measuring between data line and shield
S
B
A
Test probe
Channel 1
Example with noise:
Slide
306 / 340
With this type of measuring, it is possibly to measure the individual

data line opposite the shield. The signal strength should be now the half the
measured Signal between A and B.
Signal Level
Signal level defined by IEC 61158-2
Transmit level:
0.75Vpp to 1Vpp @ 50 Ohm
Signal level will be measured by diagnostic module or oscilloscope

Value depends on measurement point !
In case when transmission signal is between

1Vpp and 2Vpp one or more terminators are missing
Recommended values for transmit level are as follows:
Slide
307 / 340
Transmit level
peak-to-peak
Transmit level
peak
Wire condition
> 1V
> 0.5V
Missing terminator
0.7V 1V
0.35V 0.5V
good
0.3V 0.7V
0.15V 0.35V
e.g. 3 terminators
< 0.3V
< 0.15V
3 or more terminators
Termination
Records of correct terminated segments
Depending on the segment length and the place of measurement, the
peak-to-peak signal can show different level.
Begin of segment
Slide
308 / 340
End of segment
Termination
Missing Termination
This record shows a situation of a segment with only one termination.

(Example; Termination only at the beginning)
Slide
309 / 340
Termination
In this segment are altogether 3 termination in use.
In most cases the peak-to-peak level will be less than the typical 6501000 mV. It can come to a signal pawning at the same time (Jitter).
A sawtooth signal forms.
Slide
310 / 340
Noise
Noise is an undesired disturbance within the signal frequency band
Noise may appear with different characteristics. A high noise level may
cause communication problems and a lack of operational reliability
A: Noise level
B: Signal level
Slide
311 / 340
Noise
Noise can be caused by many elements including:
bad wiring practice
bad shielding/grounding practice
a non-regulated supply can pass supply voltage glitches
onto the bus
a DC power supply injecting noise into the bus
a regulated FOUNDATION Fieldbus supply injecting
switching noise into the bus
Slide
312 / 340
Jitter
Jitter is the deviation from the ideal timing of an event.
In this case it is deviation from the ideal zero crossing point of the
transmitted signal curve during the nominal bit duration, measured with
respect to the previous zero crossing (reference event).
A: Reference event; first zero crossing point

B: Actual zero crossing point
Slide
313 / 340
C: Bit cell jitter, deviation from the

ideal timing
D: Ideal zero crossing point
Jitter
Jitter is composed of many factors, e. g.:
cross talk
electromagnetic interferences (EMI)
simultaneous switching outputs
device dependency
bad wiring practice
Slide
314 / 340
Jitter
A high jitter level may cause communication problems and a lack of
operational reliability.
The transmitted bit cell jitter shall not exceed 10 % of one bit time. E.
g. at 31.25 kbits/s one bit time is 32 s long.
So the maximum bit cell jitter shall not exceed 3.2 s.
Indeed, your system may be able to run with a higher jitter level but
with a reduced level of immunity against EMC influences.
Slide
315 / 340
Balance of the Communication Signal

The communication signal must be:
symmetrical to the supply voltage (measured between the leads)
balanced to ground
a DC unbalance is the result of a capacitive or resistive connection
between the Fieldbus signal wires and the ground (cable shield)
50%
Supply
voltage
50%
Slide
316 / 340
Balance
Why is a Balanced Signal so Important?
A DC unbalance is the result of a capacitive or resistive connection
between the Fieldbus signal wires and the ground (cable shield).
An undetected DC unbalance may cause communication problems as
well as a lack of EMC stability. In the worst case an undetected DC
unbalance may harm the communication.
A single pole-to-shield fault is not absolutely critical, but if a second
pole to-shield-fault happens at the same time, corruption of the
communication signal and high crosstalk levels can occur between the
two affected segments.
Slide
317 / 340
Balance
Possible causes for non-balance of the signal:
Miswiring/incorrect installation: In a installation scenario several
devices have been incorrectly installed. One device on each of two
independent segments has been wired with the negative data line tied to
the shield and the shield is tied to earth ground.
Device influence: To increase EMC stability some facilities modify their
Fieldbus devices with asymmetric capacitive connections between shield
and their + or - fieldbus line. If such Fieldbus devices are connected to
the plant they influence the balance of the specific field device or the
entire segment.
Wire damage: a wire damaged by external influences is also able to
create unbalance if there is short-circuit between a Fieldbus line and the
cable shield.
Slide
318 / 340
Initial Cable Checkout with multi-meter

Requirements
cables and junction boxes are installed
no power supplies and field devices are connected to the segment
possible Measurements/Checkouts using an external multimeter or a
Checkbox, you can measure:
Connection between signal lines and cable shield

missing Terminator
exceeded cable capacity
cable shields not connected to ground
Slide
319 / 340
Fieldbus Diagnostic Products - NI

With a bus monitor, it is possible to check the quality of the
communication
Frames
Frame errors
PDU
FDL_PDU
Slide
320 / 340
Bus idle
Cycle communication
A cycle communication
Bus idle
Fieldbus Diagnostic Products Pepperl+Fuchs
Mobile Diagnostic
DM-AM
Power Hub Diagnostic Module

HD2-DM-A (Advanced Diagnostic)
FDT/DTM based
PC Tool
Slide
321 / 340
Fieldbus Diagnostic Products
Slide
322 / 340
Fieldbus Diagnostic Products
Slide
323 / 340
Fieldbus Diagnostic Products - MTL
F809F
FDT/DTM based
PC Tool
Slide
324 / 340

Host control system
Instrument Management Software

(including fieldbus diagnostics)
Fieldbus power supply

system
Segment 1 of 8
H1 Fieldbus
Controller I/O
Slide
325 / 340
Basic failure
alarms
On-line
Diagnostic Module
Field junction box

Voltage
Segment Voltage
Bus termination
Average device signal level
-ve to shield short
Peak Noise
Average Noise
Shield Short
+ve to shield short

Total retransmissions
Retransmissions rate (segment)
Retransmissions rate (worst device)
Add - Drop detection

of devices
on the segment
Device count
Generating reports
Slide
326 / 340
Lowest device signal level

Average FF-band noise level
Peak FF-band noise level
Average LF-band noise level
Peak LF-band noise level
Average HF-band noise level

Add-drop error rate
Peak HF-band noise level
Fieldbus Diagnostic Products - TURCK

HSE Diagnostic Bus
FF-Function blocks
FF-Alarms
DTM
DD
Temperature
Local Advance Diagnostics
Ripple
Continuous Diagnostics
of 16 H1 Segments
Noise
Jitter
Las Level
Device Level
Power Supply 1
Power Supply 2
Segment current
Slide
327 / 340
Fieldbus Diagnostic Products - TURCK

H1-Segment-, System- and HSE Diagnostics
Measurement of elec. and com. values
Live List
Trending excel compatible
On/Offline Parameterization excel compatible
Slide
328 / 340
Your notes
Slide
329 / 340
Field Xpert Device Xpert
PCPS PAM HW
Slide 330
The Screwdriver for

FOUNDATION Fieldbus device
configuration
Field Xpert - Device Xpert FF
Easy parameterization of FOUNDATION Fieldbus

field devices with Field Xpert
Ethernet/FF HSE
ControlCare
Field Controller
Linking Device
SFC162
WiFi
Access Point
Softing
Linking Device
FG100
3a
3
FF H1/Bluetooth Modem
Visitor or LAS
FF Power
Conditioner
RPC49-205
2a
2
FF Junction Box, 4-port

JRBS-40SC-4R/Ex
Field Xpert PDA (1)

Connection via Bluetooth (2)
and Bluetooth modem (2a) to
Connection via Wifi (3) and
Access Point over Linking
Device (3a, 3b) to
Quick and Fast commissioning
of FF devices
Visitor and LAS Mode
1
Field Xpert SFX100
+ Device Xpert FF
Software
Slide
331 / 340
TMT85
Cerabar S
TMT162
Smar FI302
3b
Metso
Neles ND9000
Field Xpert - Device Xpert FF - typ. usage phases/focus
planning
procurement
commissioning
optimization
maintenance
Pre-Configuration
Online
Commissioning
D
X
FF
Diagnosis
Loop-Test/Simulation
Calibration
Optimization
Documentation, Verification and Backup
Focus: Resource Block, Transducer Block
Host
Slide
332 / 340
Focus: more Function Block oriented, scheduling, wiring
Device Xpert FF Device Configuration
Slide
333 / 340
Device Xpert FF Methods and Diagnosis
Slide
334 / 340
Device Xpert FF Block information and DD Library
Slide
335 / 340
Manufacturer ID
Device
Device Type
Serial-No.
H1 Adress
Device Revision
0x452B48
TMT85
0x10CE
A20074042B7
25 (0x19)
1
DD Revision
Device Class
Basic
Device Xpert FF Device Report
Slide
336 / 340
Your notes
Slide
337 / 340
Your notes
Slide
338 / 340

FF Booklet Technology

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

FF Booklet Technology

Încărcat de

Drepturi de autor:

Formate disponibile

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus Technology, Market

Testing, Certification and Registration

Analog to Fieldbus Digital Communication

OSI Model Fieldbus Layers

Physical Layer Topologies

Physical Layer Components

Communication Layer Principles

User Layer Function Blocks

User Layer Function Block Application

Physical Layer Properties

Physical Layer Installation

Physical Layer Calculation

Physical Layer Troubleshooting

Glossary, NI Tool guideline

FOUNDATION Fieldbus Technology, Market

FOUNDATION Fieldbus Technology Training 2010

History of FOUNDATION Fieldbus technology

process control suppliers

Merge to found the Fieldbus Foundation

FOUNDATION Fieldbus Technology Training 2010

History of FOUNDATION Fieldbus technology

FOUNDATION Fieldbus Technology Training 2010

History of FOUNDATION Fieldbus technology

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus - PROFIBUS

FOUNDATION Fieldbus Technology Training 2010

History of FOUNDATION Fieldbus technology

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus vs. Fieldbus Foundation

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus vs. Fieldbus Foundation

FOUNDATION Fieldbus Technology Training 2010

Fieldbus Foundation Organization

FOUNDATION Fieldbus Technology Training 2010

Fieldbus Foundation Organisation

Phone: +1 512 794 8890

FOUNDATION Fieldbus Technology Training 2010

Fieldbus Foundation Members

Ohkura Electric Co., Ltd.

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus Markets

> 1 million devices

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus Markets

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus Markets

FOUNDATION Fieldbus Technology Training 2010

FOUNDATION Fieldbus Markets

Testing, Certification and Registration

FOUNDATION Fieldbus Technology Training 2010

Integration Tests the Triangle of Testing

DCS Systems Vendors

FOUNDATION Fieldbus Technology Training 2010

Communication Conformance Test

Physical Layer Conformance Test

Interoperability Test Kit

FOUNDATION Fieldbus Technology Training 2010

Physical Layer Conformance Test

FOUNDATION Fieldbus Technology Training 2010

Physical Layer Conformance Test

FOUNDATION Fieldbus Technology Training 2010

Official Fieldbus Foundation Testing

system for fieldbus devices and therefore