FOUNDATION™ Fieldbus

Fieldbus Basics

Ramprasad Avhad
What is Field Bus ?
 Types of Field Bus
Foundation Field bus
Profibus
Profinet
ControlNet
DeviceNet
Industrial Ethernet
MODBUS

3
 Foundation Fieldbus
Definition: It is an all-digital, serial, two-way,
Multidrop wiring, Multivariable Instruments, Control
in the field Type communication protocol.

4
 Types of Foundation Fieldbus
 H1 link
Speed 31.25kbps
interconnects field equipment
Sensors, Actuators & I/O
 HSE (High Speed Ethernet)
Speed 100-1000mbps
provides integration of high speed
controllers, subsystems (via Linking Device)
and data servers and workstation.

5
 Foundation Fieldbus Model
FOUNDATION fieldbus 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. 6
 FAS maps the FMS into DLL.
 User Application - Blocks
 The Fieldbus Foundation has defined a standard User Application
Layer based on “Blocks”.
 Blocks are representations of different types of application functions.
 The types of blocks used in a User Application are described as:
 Resource Block,
 Transducer Block,
 Function Blocks.
 Devices are configured using
Resource Block and Transducer Block.
 The Control Strategy is built
using Function Blocks.

7
 Resource Block
 The Resource Block describes characteristics of the fieldbus device such as
device name, manufacturer and serial number, etc.
 There is only one Resource Block in a device.

FIM H1 link interfaces

Device
Transducer block

Resource block
Device

Control Builder Project tab

8
 Transducer Block
 Transducer Blocks are used to configure devices.
 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

9
 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
10
 Example of a Control Loop
 Control Strategy can be built using Function Blocks built into field devices.

 A simple temperature transmitter may contain an AI function block. AControl

Valve might contain a PID function block as well as the expected AO Block.

 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.
 Communication through VCR
Fieldbus Messages are exchanges through Virtual Communication
Relationship (VCR)

Sender Receiver

index index

VCR
FMS FMS

FAS FAS

VCR
DLL DLL

DL-address DL-address
PHL PHL
H1 Benefits

14
 Reduction in System Hardware
 Standard Function Blocks is used to implement the Control Strategy.
 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.
 Distribution of control into field devices can reduced the amount of
hardware and cabinet footprint needed.

Control System Network HSE

PID

Analog Controller Fieldbus Controller

PV
PV , Mode , Variables , Alarm
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

15
 Wiring Savings
 The H1 fieldbus allows many devices to be connected to a single wire pair.
 This results in less wire, fewer intrinsic safety barriers and fewer
marshaling cabinets.

Control System Network HSE

Analog Controller Fieldbus Controller

PV
PV , Mode , Variables , Alarm
I/O Subsystem Diagnostics , Etc
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 ManyDevices
One wiring for eachDevice

16
 Summary
 Control in-the-field
Reduced loading on DCS Controllers
 Reduced number of intrinsic safety barriers
Only H1 card in the Marshalling
 Reduced number of Input/Output Converters
 Reduced number of Power Supplies and Cabinets.
 Reduced size of equipment Rooms.
 Support Interoperability.
 Increased accuracy of measurements
 Support Interchangeability
 Increased sophistication and flexibility of instrumentation
 Increased uptime due to less equipment
 better self diagnostics and remote diagnostics
 More information available for Operations

17
 Fieldbus Component
Power Supply Workstation HMI
Fieldbus Interface Module

HSE (FTE) Cable

Fieldbus Controller
Safe Area (Host)

H1 Bus (Trunk) Hazardous Area (Field)

Terminator
Terminator
Junction Box

H1 Bus Wire (Spurs)

Transmitters Analyzer
Actuator Valve 18
 HIGH SPEED ETHERNET
(HSE)
HSE is a control network technology specifically designed for process
automation to connect higher-level devices such as controllers and remote-I/O,
high-density data generators etc., and for horizontal integration of subsystem
 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

20
 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

21
 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

22