Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Contents
Slide
1 / 340
17
35
50
61
77
123
Device Driver
157
Address range
176
186
210
246
260
285
300
FieldXpert
330
338
PC-PS
Slide 2
1980
ISP
WFIP
1994
Slide
3 / 340
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)
Europe
Canada
USA
India
Japan
Brazil
Southeast Asia
Argentina
South Africa
Slide
6 / 340
Slide
7 / 340
Slide
8 / 340
Slide
9 / 340
Slide
10 / 340
Fieldbus Foundation
9005 Mountain Ridge Drive
Bowie Bldg - Suite 190
Austin, TX 78759-5316
info@fieldbus.org
Slide
11 / 340
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.
And more
Slide
12 / 340
Slide
13 / 340
10000 Systems
Slide
14 / 340
Asia Pacific
Europe
North America
Middle East Asia
Slide
15 / 340
Slide
16 / 340
PC-PS
Slide 17
FOUNDATION
Fieldbus Foundation
FF
Triangle
of Testing
Endress+Hauser
Slide
18 / 340
Software Stack
Communication
Hardware
+
Complete device
Slide
19 / 340
DD file
Test of Communication
Slide
20 / 340
Slide
21 / 340
DD file
Test in
Test Laboratory
(Austin,TX)
No
OK ?
Yes
Slide
22 / 340
Certificate
from
Fieldbus Foundation
Organisation
ITK
2000
Slide
23 / 340
ITK
2003
ITK
2004
ITK 5.2
ITK 5.0
end of 2006 end of 2009
Slide
24 / 340
Slide
25 / 340
Slide
26 / 340
www.products.endress.com/foundation-fieldbus-dd
Slide
27 / 340
Slide
28 / 340
Slide
29 / 340
FOUNDATION
Fieldbus Foundation
FF
Triangle
of Testing
Endress+Hauser
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**
Slide
33 / 340
Slide
34 / 340
PC-PS
Slide 35
Slide
36 / 340
1 0 0 1 0 0 1
Slide
37 / 340
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 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
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
CPU
Digital
Slide
40 / 340
CPU
Pressure device
e.g. Cerabar S
PLC/DCS
16 bit
I/O
16 bit
16 bit
cable
16.8 mA
16 bit
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]
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
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
Slide
48 / 340
Fieldbus
a fieldbus standard (hardware, software and communications
protocol) defined by the Fieldbus Foundation
Slide
49 / 340
PC-PS
Slide 50
*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
Physical Layer
Physical Layer
Fieldbus Access
Sublayer (FAS)
H1
Communication
Stack
Physical Layer
Application Layer
OSI Model
Slide
52 / 340
Application Layer
Presentation Layer
Session Layer
Transport Layer
Network Layer
Physical Layer
Physical Layer
Fieldbus Access
Sublayer (FAS)
Sensor
User Layer
Communication
Layer
Physical
Layer
Slide
53 / 340
Fieldbus Device
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
Communication Layer
Sensor
The communication layer (stack)
provides:
Encoding and decoding of the
user layer messages
User Layer
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
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:
Physical Layer
Physical Layer
Wire Medium
Holds envelope
Address & flag
FB: Device address
Truck:
transports envelope,
independent of
message
FB: Electrical signals on wire
Application Layer
Parameter / FB
Read / Write
10.7 / Good
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
PC-PS
Slide 61
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
62 / 340
PC
field controller
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
PC
field controller
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
Basics of Termination
+
100
1 uF
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
H1
Slide
68 / 340
H1 Combined Topology
Combined topology*/ H1
Operator Workstation
Engineer Workstation
Junction
Box
Power Conditioner
+ terminator
H1
Daisy Chain
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
Power
Supply
Power Conditioner
+ terminator
Spur
Cable
Split spur
Junction Box
(with Terminator)
Slide
72 / 340
Fieldbus
Terminator
Field Wiring
and Field Devices
Slide
73 / 340
Bus / Spurs
Terminator
Spur
Cable
Tree
Home Run Cable
Junction Box
(with Terminator)
Spur
Cable
Split spur
Junction Box
(with Terminator)
Examples
Slide
75 / 340
Notes
Slide
76 / 340
PC-PS
Slide 77
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
78 / 340
Local Displays
7 / 8 Plugs
Female
Male
Front View
(shield)
(ground)
Protector functionality
Slide
82 / 340
Connection example
Slide
83 / 340
T connector example
Slide
85 / 340
Slide
86 / 340
Slide
87 / 340
Stone L
Slide
88 / 340
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
Slide
93 / 340
Chemical Protection
Improved Fire Behavior
Slide
94 / 340
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
Standard 24v DC
Power Supply
Power Conditioner
+ terminator
Slide
98 / 340
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
Standard 24v DC
Power Supply
Power Conditioner
+ terminator
Slide
101 / 340
Slide
102 / 340
ABB FIO-100
Linking
H1
Device
Emerson HSE Linking Device
H1
Softing FieldGate FF
Fieldbus Foundation H1-Segment
Slide
103 / 340
earth 1
Slide
105 / 340
earth 2
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
Slide
109 / 340
Slide
111 / 340
Slide
112 / 340
Power Conditioner
+ terminator, 500mA
Foundation Fieldbus H1
Main trunk EEx e
EEx ia outlets
Slide
113 / 340
T
Zone 1
Zone 0
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
LEDs
Cover for
Ex e
Terminals
Ex i
Terminals
Trunk In
Cable Glands
Grounding
Point
Slide
116 / 340
4 Outlets with
Cable Glands
Slide
117 / 340
Slide
118 / 340
Slide
119 / 340
Installation Examples
Slide
121 / 340
Notes
Slide
122 / 340
PC-PS
Slide 123
Communication Layer
Sensor
The communication stack
provides:
Encoding and decoding of the
user layer messages
User Layer
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
Device ID
Unique number
Bus address
Slide
125 / 340
Example:
H1
Slide
126 / 340
Manufactor ID - Endress+Hauser
452B48
1007
Serial number
- 7PY015575
FF device ID example:
452B481007- 7PY015575
H1 Bus segment
Tag =
TIT1701
Slide
128 / 340
NO
Change Tag
Yes
Change Address
Yes
No Valid Address
No Tag
TIT1701
Set Tag
Slide
129 / 340
No Valid Address
0x18
TIT1701
Set Address
Slide
130 / 340
Slide
131 / 340
Slide
132 / 340
Slide
133 / 340
TD = Time distribution
Time Synchronized !
Slide
134 / 340
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
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
Strategy
Engineer
Transmission &
Schedule.
Transmission lists
LAS
Slide
137 / 340
Transmission lists
LAS
CD = Compel Data
CD = Compel Data
DT = Data transfer
(Broadcast)
Transmission lists
Slide
138 / 340
Publisher
Publisher
Transmission lists
Subscriber
Subscriber
Address:
16
25
27
28
XX
Token
PT = Pass
Token
Slide
139 / 340
Field devices
Address:
16
25
27
28
XX
PT = Pass Token
DT = Data Transfer
RT = Return Token
Token
Token
Slide
140 / 340
Field devices
Communication schedule
The LAS follows a strict schedule
Slide
142 / 340
Slide
143 / 340
Control
Publisher
Subscriber
Slide
144 / 340
Alert data
Slide
145 / 340
Slide
146 / 340
Slide
147 / 340
Slide
148 / 340
Slide
149 / 340
Slide
150 / 340
H1 to H1
H1 to HSE
Republishing
Linking
Device
42a
No
Yes
Bridge
42c
Yes
Yes
Functions Included
42a
Configuration of H1 Nodes
42b
Monitoring of H1 Nodes
42c
H1 to H1 Republishing
42d
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
Basic class
device
Slide
152 / 340
Link Master
class device
Backup rule
Link Master
class device
Slide
153 / 340
Link Master
class device
Slide
154 / 340
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
Notes
Slide
156 / 340
Device Drivers
FOUNDATION Fieldbus-Advanced Training I
PC-PS
Slide 157
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
DD - .ffo
DD - .sym
Slide
159 / 340
DD - .cff
Slide
160 / 340
DD
.ffo
.sym
Slide
161 / 340
.cff
Device
Slide
163 / 340
Device
Description
DD Services
Packet Assembly
Read Value
DD Files / mapping
Example block error:
DD
DD
Extensions:
0x2A: Block error
0x21: Out of service
.
Block error !
Configuration tool
Slide
164 / 340
Slide
165 / 340
Slide
166 / 340
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
Slide
169 / 340
Filenames / revision
Slide
170 / 340
Vendor Name
-> Device Name
Slide
171 / 340
ManufacturerID
-> Device Type
Device Revision
Drivers
CFF (CFF)
DD (SYM+FFO)
Slide
172 / 340
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
User Layer
Communication
Stack
Physical
Layer
Slide
177 / 340
FF Training
H1 Bus segment
FF Training
Slide
179 / 340
FF Training
Slide
180 / 340
FF Training
Slide
181 / 340
FF Training
Slide
182 / 340
0x18 (20)
0xF7 (247)
0xF8 (248)
Operational
Operational
Link Master
Basic
Initialize or
Uninitialized
FF Training
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
Slide
184 / 340
Notes
Slide
185 / 340
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
Inputs
Outputs
Algorithm
Example: PID
Standard Block
Parameters
Mode, etc
Slide
188 / 340
Block Specific
Parameters
Bias, etc
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
Function Block
Function Block:
analog input
analog output
analog input
analog output
PID
signal characterizer
Slide
192 / 340
Slide
193 / 340
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
SPG
Input Selector
IS
Arithmetic
AR
Timer
TMR
Analog Alarm
AAL
FF-892
(Part3)
MAI
MAO
MDI
MDO
FF-893
(Part4)
Slide
196 / 340
Slide
197 / 340
ESPG
Enhanced PID
EPID
Advanced PID
APID
ALGORITHM
Function Block:
Flip Flop and Edge Trigger
FFET
Hardware Configurator
HC
MBCF
Slide
199 / 340
Name Symbol:
Transducer
Transducer
Control Strategy
Channel
1
2
3
4
Channel
PI
Manufacturer specific
Slide
200 / 340
AO
1
2
Transducer
Transducer
Control Strategy
Channel
1
2
3
4
Channel
A
+
PI
+
Enhanced Manufacturer
function block
(Pressure, Temperature )
AO
1
2
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
mV
Slide
203 / 340
Measurement
RS Block
Transducer
Transducer
Transducer
Transducer
PID Block
PID Block
Control
AI Block
AI 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.
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
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
Slide
208 / 340
Example:
Notes
Slide
209 / 340
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
PCV
FI302
88
P
LD302
I
Flow
88
SM AR
FV-31
FE-31
Slide
212 / 340
(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
Slide
214 / 340
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
AI
PID
AO
AI
PID
AO
AI
PID
Slide
216 / 340
AO
Classification:
INTERNAL
10/18/2006
Slide
Slide 217
217 / 340
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 Instantiation
PID
Device Memory
AI_2
PID_1
PID_2
PID_3
TIMER_1
.
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:
Slide
221 / 340
DESCRIPTION
BEHAVIOR
OOS
Out Of Service
IMAN
Initialization Manual
Local Override
Manual
Automatic
Cascade
RCAS
Remote Cascade
ROUT
Remote Output
LO
MAN
AUTO
CAS
Slide
222 / 340
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
Slide
223 / 340
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
Slide
224 / 340
Slide
225 / 340
simulation
Value
Status
scaling
XD_Scale
OUT_Scale
fault values
limits
Fail safe
value
HH
H
L
LL
Parameterization - AI Block
130 Parameters !!!
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
Slide
228 / 340
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.
: 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
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.
Value
Discrete value
Status
2 byte
Value
IEEE-754 Floating
5 byte
Slide
233 / 340
Status
BAD -
UNCERTAIN -
Good -
Sub Status
Non Cascade
Cascade
Device Failure
Limit
High Limited
Low Limited
Constant
Not Limited
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.
Slide
237 / 340
Input Selector
Slide
238 / 340
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
ISEL
56.4
Slide
240 / 340
: Auto
: eg. First good
The PID block is key to many control schemes and is used almost universally.
Slide
241 / 340
Slide
242 / 340
Description:
CAS_IN
IN
BKCAL_IN
BKCAL_OUT
TRK_IN_D
TRK_VAL
FF_VAL
BKCAL_OUT
OUT
Slide
243 / 340
GAIN:
RESET:
RATE:
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
PC-PS
Slide 246
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
247 / 340
0100110
Bus cable
MBP
Sensor
uP
Firmware
MAU
*
Physical layer
Slide
248 / 340
0100110
Slide
249 / 340
Manchester Encoding
Fieldbus Signal
Voltage
dc bias
9 to 32 Volts
Time
Fieldbus Network
100 Ohm
1uF
Slide
250 / 340
100 Ohm
1uF
Data
Clock
Encoded
Data
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
Pre
Slide
254 / 340
SD
FCF
SD/DA
Data
CRC
ED
PRE
Preamble
SD
Start Delimiter
FCF
SA /
DA
Destination / Source
addresses
1-3
Data
Frame Data
Up to 8,16,32
CRC
ED
End Delimiter
Slide
255 / 340
Acronym
Definition
Number of Octets
Description
Pre
The preamble
1 octet
SD
Start Delimiter
1 octet
FCF
FOUNDATION
Control Flag
1 octet
SA,DA
Destination /
Source
addresses
1-3 octets
DATA
Frame data
Up to 8,16,32 octets
CRC
Cyclical
Redundancy
Check
4 octets
ED
End Delimiter
1 octet
Preamble
Slide
256 / 340
Start delimiter
End delimiter
Slide
257 / 340
Slide
258 / 340
Fieldbus Signals
32 S
Current
+ 9 mA
- 9 mA
Slide
259 / 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
Stack
Physical
Layer
Slide
261 / 340
Tank
Tank
Slide
263 / 340
Slide
264 / 340
Isolated installation
The bus shield is not connected
to ground
Slide
265 / 340
Slide
266 / 340
Slide
267 / 340
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
Slide
270 / 340
Slide
271 / 340
Slide
272 / 340
Slide
273 / 340
Hazardous area
Fieldbus barrier
Field
device
FF
Power
Repeater
?
Potential equilization
Slide
274 / 340
Potential equilization
Hazardous area
Hazardous area
FF Power Repeater
Ex e
FieldBarrier
Ex i
Field
device
Potential equilization
Hazardous area
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
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
Power conditioner
T
PROFIBUS PA
Slide
279 / 340
Power conditioner
Advantage:
Slide
280 / 340
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
Slide
282 / 340
Slide
283 / 340
Notes
Slide
284 / 340
PC-PS
Slide 285
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
286 / 340
Example:
UBUS = 24 V
I BUS = < 400 mA
Slide
287 / 340
H1
MBP
Max. 1900 m
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
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
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
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
Calculation of Voltage
Worst Case
imax
RL
ix
i1
i2
UL
Uout
Slide
293 / 340
> 9V
RL2
i1
i2
Uout
Slide
294 / 340
ix
> 9V
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
Slide
296 / 340
Slide
297 / 340
Slide
298 / 340
Notes
Slide
299 / 340
PC-PS
Slide 300
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
301 / 340
Bits:
19 mA
I B =10 mA
1 mA
1 Bit 1 Bit
Slide
303 / 340
Slide
304 / 340
50%
Supply
voltage
50%
data line A
Slide
305 / 340
A
Test probe
Channel 1
Example with noise:
Slide
306 / 340
Signal Level
Signal level defined by IEC 61158-2
Transmit level:
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
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).
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
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
Slide
319 / 340
PDU
FDL_PDU
Slide
320 / 340
Bus idle
Cycle communication
A cycle communication
Bus idle
Mobile Diagnostic
DM-AM
FDT/DTM based
PC Tool
Slide
321 / 340
Slide
322 / 340
Slide
323 / 340
F809F
FDT/DTM based
PC Tool
Slide
324 / 340
Segment 1 of 8
H1 Fieldbus
Controller I/O
Slide
325 / 340
Basic failure
alarms
On-line
Diagnostic Module
Segment Voltage
Bus termination
Average device signal level
-ve to shield short
Peak Noise
Average Noise
Shield Short
Ripple
Continuous Diagnostics
of 16 H1 Segments
Noise
Jitter
Las Level
Device Level
Power Supply 1
Power Supply 2
Segment current
Slide
327 / 340
Slide
328 / 340
Your notes
Slide
329 / 340
PCPS PAM HW
Slide 330
WiFi
Access Point
Softing
Linking Device
FG100
3a
3
FF H1/Bluetooth Modem
Visitor or LAS
FF Power
Conditioner
RPC49-205
2a
2
FOUNDATION Fieldbus H1
1
Field Xpert SFX100
+ Device Xpert FF
Software
Slide
331 / 340
TMT85
Cerabar S
TMT162
Smar FI302
3b
Metso
Neles ND9000
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
Slide
333 / 340
Slide
334 / 340
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
Slide
336 / 340
Your notes
Slide
337 / 340
Your notes
Slide
338 / 340