1 Fieldbus Basics PDF

FOUNDATION Fieldbus
Fieldbus Basics
Nik Suzaimi
Berkat Honeywell Sdn Bhd, MALAYSIA
On behalf of
Fieldbus Foundation TM
End User Seminar

25 Oct 2010
Kuala Lumpur, MALAYSIA
1994 2008 Fieldbus Foundation
Agenda
H1 Basic Review. FOUNDATION Fieldbus Technology.
What is Fieldbus? H1 network review technology. Intrinsic
Safety.
Integrated Architecture.
DD and CFF Files.
H1 Benefits. Typical Fieldbus installation.
More data is available. Fieldbus Components.
Expanded view of Process and H1 Fieldbus Model
Instruments. User Application Resource, Transducer
Reduction in System Hardware. and Function Blocks.
Wiring Saving.
Standard Function Blocks.
Summary.
4-20mA versus Fieldbus. Example of a Control Loop. H1 Link
Master Redundancy.
H1 Link Active Scheduler.
H1 Link Schedule Optimization
High Speed Ethernet
2
H1 Basic Review
3
What is Fieldbus?
1. A fieldbus is an all-digital, serial two-way, multi-drop communication System.
2. H1 link (31.25kbps) interconnects field equipment (Sensors, Actuators & I/O).
3. HSE (High Speed Ethernet, 100mbps) provides integration of high speed
controllers, subsystems (via Linking Device) and data servers and
workstation.
Data Servers
4
Integrated Architecture
1. Management Information Systems (MIS), Enterprise Resource Planning
(ERP), and Human Machine Interface (HMI) access the H1 Fieldbus
information via the Data Servers.
Data Servers
MIS Business Enterprise

ERP and
HMI Plant Application
Packages
Data Servers
HSE/FTE
H1 and HSE
Factory/Plant
Instrumentation and
H1-Fieldbus Network Control devices
5
H1 Benefits
6
More Data for Better Decision Making
1. Fieldbus allows multiple variables from each device to be brought into the
control system for archiving, trend analysis, process optimization, reporting,
predictive maintenance and for asset management.
2. Fieldbus distortion-free characteristics digital communication enables
improved control capability which can improve product yields.
Control System Network HSE
Analog Controller Fieldbus Controller
PV
PV , Mode , Variables , Alarm
I/O Subsystem Diagnostics , Etc
4-20mA H1
Traditional 4-20mA One Variable (One Direction) Fieldbus Multiple Variables (Both Directions)
7
Expanded View of Process & Instrument
1. Self Diagnostics and communication capabilities of microprocessor based
fieldbus devices helps reduce downtime and improve plant safety.
2. Plant operation and Maintenance personnel can be notified and corrective
actions taken quickly and safely.
PV
4-20mA H1
Traditional 4-20mA View stops at I/O Subsystem Fieldbus Extends View to Field Instrument
8
Reduction in System Hardware
1. Standard Function Blocks is used to implement the Control Strategy.
2. Many control system functions such as AI, PID and AO can be performed by
the field device through the use of these Standard Function Blocks.
3. Distribution of control into field devices can reduced the amount of hardware
and cabinet footprint needed.
PID
PV
I/O Subsystem
Diagnostics , Etc
4-20mA AI AO H1
AI AO PID
Traditional Control and I/O requires extra hardware Fieldbus Extends Control and I/O to Field Instrument
9
Sample Implementation
192 segments per cabinet

Assuming using 8-segment redundant H1
card
Certified for installation in Class 1

Division 2 / Zone 2 hazardous
locations
Translates to 3,072 FF devices per

System Cabinet
It could be more when each FF device
may provide up to 16 process values ( ie.
Temperature Multiplexers)
3,072 FF devices per System Cabinet

10
Wiring Savings
1. The H1 fieldbus allows many devices to be connected to a single wire pair.
2. This results in less wire, fewer intrinsic safety barriers and fewer marshaling
cabinets.
PV
4-20mA I.S H1
I.S I.S I.S I.S I.S
Traditional 4-20mA wiring, One I.S Barrier, One I.S Barrier, One Wire for Many Devices
One wiring for each Device
11
Summary
Control in-the-field Increased accuracy of
Reduced loading on DCS measurements
Controllers
Easier evolution due to
Reduced number of intrinsic standardized function blocks
safety barriers
Only H1 card in the Marshalling
Increased sophistication and
flexibility of instrumentation
Reduced number of Input/Output
Converters
Increased uptime due to less
equipment,
Reduced number of Power
Supplies and Cabinets.
better self diagnostics and remote
diagnostics
Reduced size of equipment
Rooms.
More information available for
Operations.
Remote configuration of devices.
Significant Contribution to Weight Reduction on your Offshore

12 Platforms 1994 2008 Fieldbus Foundation
4-20mA versus Fieldbus
1. A H1 fieldbus retains and optimizes the desired
features of the 4-20mA analog system:
4-20mA
- single Loop integrity.
- a standardized physical interface to the wire. P.S.
- a bus-powered devices on a single wire pair. 4-20mA
- intrinsic safety options.
2. In addition, FOUNDATION Fieldbus enables:

- 25 x faster communication speed compared to
HART Fieldbus
- increased capabilities (due to full digital P.S.
communication).
- reduced wiring and terminations (multiple
device on one wire).
- increased selection of suppliers (due to
interoperability)
- reduced control room loading (control on wire)
13
- connection to HSE backbone.
FOUNDATION fieldbus
Technology
14
H1 Network Review
1. Multi-Drop wire pair with Power and Signal on same cable.
Fieldbus Signal
2. Support Intrinsic Safety.
3. Fault Tolerant, can have multiple Link Masters.
4. Function Blocks built into Field Devices.
5. Control on the Wire single loop integrity
6. Distance up to 1900 meters
HSE (FTE)
7. Add Repeaters to
extend > 1900 meters
H1 Digital Signal H1 Digital Signal
R
8. Max. of 4 repeaters can
be used to a maximum
distance of 9500 meters 1900 meters Distance > 1900 meters
15
Intrinsic Safety
Control room Field

Field device
I.S certified devices
Trunk
Power
supply
Conditioner T T
Wiring block
I.S Interface
Host
Control
System
I.S certified devices
16
DD and CFF Files
1. Field Devices will consists of:
Actual Physical Device. DD & CFF
Configuration
Device Description (DD). System
Common File Format (CFF).
2. DDs and CFFs will be provided by the
Device Supplier or Host Supplier. www.fieldbus.org
3. Standard parameters present in

devices. Option to include specific
manufacturer parameters.
4. Parameters and Capabilities are
defined in device files DD and CFF. H1 Network
5. Device files are key to off-line

configuration.
z Instruments
described with
Device Description
Language
17
DD and CFF Files
1. Device Descriptor (DD) File allow operation of devices from different
suppliers on the same fieldbus with single host system.
2. Common File Format (CFF) is a file which describes the functions and
capabilities of a field device. The CFF file is used in conjunction with the
Device Descriptor file to enable a host system to configure the system
off-line.
3. CFF files are standard ASCII text file.
18
Typical Fieldbus Installation
DOFC
Control System (Host)
An example of the Fieldbus Interface Module
Chicken foot (tree)
topology.
Redundant, isolated T PC
Power
supply
power conditioning 24V DC
defined by FF-831, Bulk power
Power
Fieldbus PST Specs. PC
supply
Typically 10-12 bus-

powered fieldbus devices
per segment. Trunk
Spur FF-831
120 m distance from FF
T
JB to FF Device
Spur short-circuit
Field
protection. Devices
Up to 1900 meters.
Maximum of 9500 meters Segment
via repeaters.
19
Fieldbus Component FOUNDATION Fieldbus System
Power Supply Workstation HMI

Fieldbus Interface Module
HSE (FTE) Cable

Conditioner Fieldbus Controller
Safe Area (Host)
H1 Bus (Trunk) Hazardous Area (Field)

Terminator
Terminator
Junction Box
H1 Bus Wire (Spurs)
Transmitters Analyzer
20 Actuator Valve 1994 2008 Fieldbus Foundation
H1 Fieldbus Model
FOUNDATION fieldbus H1 technology consists of:
The Physical Layer.
The Communication Stack.
The User Application Layer.
The Open Systems Interconnect
(OSI) layered communication model
is used to model these components.
Physical Layer is OSI layer 1.
Data Link Layer is OSI layer 2.
FMS is OSI layer 7.
Communication stack is comprised
of layer 2 and layer 7.
Fieldbus does not use OSI layer
3, 4, 5 and 6.
FAS maps the FMS into DLL.
21
User Application - Blocks
1. The Fieldbus Foundation has defined a standard User Application Layer
based on Blocks.
2. Blocks are representations of different types of application functions.
3. The types of blocks used in a User Application are described as:
Resource Block,
Transducer Block,
Function Blocks.
4. Devices are configured using
Resource Block and Transducer Block.
5. The Control Strategy is built using
Function Blocks.
22
Resource Block
1. The Resource Block describes characteristics of the fieldbus device such as
device name, manufacturer and serial number, etc.
2. There is only one Resource Block in a device.
FIM H1 link interfaces
Device
Transducer block
Resource block
Device
Control Builder Project tab

23
Transducer Block
1. Transducer Blocks are used to configure devices.
2. Transducer Blocks are required to Read sensors value and command output
value.
FIM H1 link interfaces
Device
Transducer block
Resource block
Device
Control Builder Project tab

24
Function Blocks
1. The Control System Strategy is built using Function Blocks. Input and output
parameters of Function Blocks can be linked over the fieldbus.
2. The execution of each Function Blocks is precisely scheduled and there can
be many function blocks in a single user application.
AI Block PID Block
AO Block
25
Standard Function Blocks
Examples
Function Blocks Function Blocks Function Blocks

Analog Input Device Control
Multiple Analog Input
Analog Output Output Splitter
Multiple Analog Output
Bias/Gain Signal Characterizer
Multiple Discrete Input
Lead Lag
Control Selector
Deadtime Multiple Discrete Output
Discrete Input
Integrator (Totalizer)
Discrete Output
Setpoint Ramp
Manual Loader Generator
Proportional/Derivative Input Selector
Proportional/Integral Arithmetic
/Derivative Timer
Ratio Analog Alarm
26
Example of a Control Loop
1. Control Strategy can be built using Function Blocks built into field devices.
2. A simple temperature transmitter may contain an AI function block. A Control
Valve might contain a PID function block as well as the expected AO Block.
3. Thus, a complete control loop can be built using a simple transmitter and a
control valve. Control in the Field does need a Controller.
AI Block PID Block
HSE (FTE)
Fieldbus Controller
AO Block
H1 Fieldbus
PID
AI
AO
Example of a complete control loop Example of a complete control module strategy

using Function Blocks located in fieldbus Devices. Control on the Wire.
Offload your DCS Controller loading by control on-the-wire

27
Foundation Fieldbus Control Integration
DCS
DCS Controller
Control
PID
AI BKCAL_OUT AO
on-the-
wire ?
28
The one we know : Control on the DCS
All CONTROL Function

Blocks executed in the
DCS
DCS
PID Control
DCS provide primary PID
Control
Fieldbus Device is
AI BKCAL_OUT AO
purely supplying Input
(AI) and output (AO)
Connection
29
FF Way : Control on the Wire
All Function Blocks DCS
executed in the device..

Primary PID Control Control
executed by the FF
Device itself
DCS simply the MMI to
change control loop
PID
Mode, Setpoint, etc
PID Execution sitting on BKCAL_OUT AO
AI
the device itself
DCS Controller is not
required at all, for some
vendor implementation
30
H1 Link Master Redundancy
1. Two types of devices are defined in the Data Link Layer (DLL).
Link Master and Basic Device.
2. Link Master Device are capable of becoming
Link Active Scheduler (LAS). Basic Device
do not have this capability.
PRIM LAS
BASIC Device
BKUP LAS
31
H1 Link Active Scheduler
1. LAS provides scheduled communication(*) control on the H1 network.
2. LAS provides unscheduled communication(**) control on the H1 network.
3. LAS maintain a live list (devices that response to the pass token) it uses to
recognize devices on each H1 Link.
4. Provides Data Link Time Synchronization so that all devices have exactly the
same data link time.
5. Insures LAS Backup or LAS Redundancy. If one LAS fails, one of the Link
Master will become the LAS and operation continues.
(*) Sends a compel data (CD) message to a device which allows the device to publish specific data when it
receives the CD message.
(**) Issues a pass token to a device which allows the device to send message until it has finished or the token hold
time expires.
32
H1 Link Active Scheduler
1. PID Loop scheduled and unscheduled communication.
Function blocks:
AI 110
PID 110
AO 110
loop 110 period of execution
Scheduled Unscheduled
Closed loop control Alarms/Events
Maintenance/Diagnostic Information
Function Block Execution Program Invocation
Permissives/Interlocks
Scheduled Communication Display Information
Trend Information
Unscheduled Communication Configuration
33
Link Schedule Optimization
1. Makes effective use of Fieldbus bandwidth.
2. Important for Control on the Wire.
3. Allow for better time management on the Link.
4. Link Schedule Optimization provides a quantum improvement in the
efficiency of Fieldbus Link bandwidth use.
34
Link Schedule Optimization (before)
Unoptimized Schedule
5 control loops 1065 msec
(note too big for 1 sec macrocycle)
35
Link Schedule Optimization (after)
Optimized Schedule
5 control loops -- <365 msec
(now fits with room to spare!)
36
HIGH SPEED ETHERNET
(HSE)
37
FF Integrated Architecture
HSE Subsystem Integration
High Performance Control Backbone
Standard Ethernet Equipment and Wiring
Standard Function Blocks PLUS
Flexible Function Blocks for Discrete/Batch/PLC
Redundant HSE Interfaces and Devices MIS
Linking Devices (LD) Integrate H1
HSE Provides the Open Interface for Data Servers
APPLICATION
PACKAGES
Data Servers
HSE High Speed Control and

Integration Backbone LD LD
P P P P
L L L L
38
High Speed Ethernet Devices
HSE Client Gateway
100 Mbit/s
Switch I/O Network
Linking
HSE Device
Field Device
H1 H1 H1
P P P
L L L
Plant Plant Plant
39
HSE - LAN Redundancy
HSE Client
Gateway
I/O Network
HSE
Field Device Linking
Device
H1 H1 H1
P P P
L L L
Plant Plant Plant
40
HSE - Device Redundancy
HSE Client
Gateway
I/O Network
Linking
HSE Device
Field Device
H1 H1 H1
P P P
L L L
Plant Plant Plant
41
Thank you
www.fieldbus.org
42

1 Fieldbus Basics PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

1 Fieldbus Basics PDF

Hochgeladen von

Copyright:

Verfügbare Formate

FOUNDATION Fieldbus

End User Seminar

MIS Business Enterprise

Control System Network HSE

Analog Controller Fieldbus Controller

Control System Network HSE

Analog Controller Fieldbus Controller

Control System Network HSE

Analog Controller Fieldbus Controller

192 segments per cabinet

Certified for installation in Class 1

Translates to 3,072 FF devices per

3,072 FF devices per System Cabinet

Control System Network HSE

Analog Controller Fieldbus Controller

I.S I.S I.S I.S I.S

Significant Contribution to Weight Reduction on your Offshore

2. In addition, FOUNDATION Fieldbus enables:

Control room Field

I.S certified devices

I.S certified devices

3. Standard parameters present in

5. Device files are key to off-line

Typically 10-12 bus-

Power Supply Workstation HMI

HSE (FTE) Cable

H1 Bus (Trunk) Hazardous Area (Field)

H1 Bus Wire (Spurs)

FIM H1 link interfaces

Control Builder Project tab

FIM H1 link interfaces

Control Builder Project tab

AI Block PID Block

Function Blocks Function Blocks Function Blocks

AI Block PID Block

Example of a complete control loop Example of a complete control module strategy

Offload your DCS Controller loading by control on-the-wire

All CONTROL Function

All Function Blocks DCS

executed in the device..

loop 110 period of execution

HSE High Speed Control and

HSE Client Gateway

Plant Plant Plant

Plant Plant Plant

Plant Plant Plant

Das könnte Ihnen auch gefallen