Basic FF

FOUNDATION fieldbus
How It Works and Why It Works!

An Introduction
General Assembly
28 February 2003
© 2003 by the Fieldbus Foundation. All rights reserved. “. . . dedicated to a single
Singapore Polytechnic international fieldbus.”
Agenda
08:00 – 08:30 Refreshments and Introductions

08:30 – 10:00 Presentation
10:00 – 10:30 Break
10:30 – 12:30 Demonstrations
General Assembly
28 February 2003
Topics
• Introduction to the Technology
• How it Works!
– Distributed Controls
– Device Description Technology
– HSE Redundancy
• Testing and Registration
– H1 Devices
– Linking Devices
– Host Systems
General Assembly
28 February 2003
Introduction
General Assembly
28 February 2003
H1 Fieldbus
Fieldbus - a digital, two-way multi-drop communication

link among intelligent measurement and control
devices, and automation and display systems.
Fieldbus
Process Plant
P
L
Automation
and
Display Systems
F
General Assembly
28 February 2003
H1 Fieldbus Benefits
REDUCED WIRING AND INSTALLATION
4-20 mA
IS IS IS IS IS
Fieldbus
Traditional 4-20 mA wiring,

One IS barrier, one pair
one IS barrier, one pair
for many devices
for each device
General Assembly
28 February 2003
EXPANDED VIEW OF PROCESS
4-20 mA
IS IS IS IS IS
Fieldbus
General Assembly
28 February 2003
MORE INFORMATION FOR ENGINEERING AND MAINTENANCE
4-20 mA
IS IS IS IS IS
Fieldbus
One Process Value Mode, Value, Status, Alarms, Trends
General Assembly
28 February 2003
DISTRIBUTION OF FUNCTIONS
AI PID PID
AO
4-20 mA
IS
Fieldbus
PID
AI
AO
Fieldbus can be used in the same way,

In today’s systems, control functions but fieldbus also enables control and I/O
all reside in central controllers. functions to be distributed to field
instruments.
General Assembly
28 February 2003
High Speed Ethernet
HSE uses the same User Layer technology as H1
– Function Blocks
– Device Descriptions
HSE uses the Ethernet/Internet for Communications

– Standard IEEE Physical Layer
– Standard Internet Protocols for the “Stack”
– Commercial Off The Shelf (COTS) Network Equipment
General Assembly
28 February 2003
High Speed Ethernet
HSE Devices
HSE CLIENT 100 Meters on Twisted Pair

2000 Meters on Fiber
COTS
High 100 Mbit/s
Spe
ed E Switch
ther
net
High Spe
ed Ethernet Linking
net Device
r
Ethe
e d Linking H1
Spe P
gh Device
Hi
L
Plant
H1 H1 H1
Ethernet P P P
Field Device L L L
Plant Plant Plant
General Assembly
28 February 2003
High Speed Ethernet Benefits
HSE is Designed for High Performance Control
• Distributed Control on a COTS 100 Megabit per Second Backbone
• Same Function Blocks and Device Description Technology as H1
• Function Block Synchronization on the Backbone
• System Time Synchronization - Master Clock (e.g. GPS) to HSE to H1
• New Flexible Function Blocks for Hybrid/Batch/PLC/Remote I/O Applications
• Supports High Speed Data Generators/Users (e.g. Analyzers, Controllers)
• Uses Standard Internet DHCP - Address Lease Reuse Reduces Startup Time
• Short Messages Can be Packed to Reduce Interrupts on Receiving CPUs
• Provides Redundant Network Interface and Redundant Devices
HSE is Designed for Flexibility

• Annunciation contains Manufacturer Identification and Model Number
• Network Independence - Supports Dual LAN and Ring Topologies
• Isolated Subnet, Backbone, Device and Subsystem Integration
• Built-in Diagnostics - Annunciation of Changes and Network Statistics
General Assembly
28 February 2003
High Speed Ethernet Benefits
HSE is Designed for the Future
•Takes Full Advantage of Modern Microprocessors and Network
Architecture
• Uses Platform Independent Internet Standards
• HSE is Not a tunneling protocol - Not Constrained by Legacy Packet
Design
• Word Alignment and Flat Data Structures Greatly Reduce CPU Cycles
• Modern - 32 Bit Object Address, 64 Bit Memory Address, 32 Bit Data
Length
• No Tag/Length Codes Needed Because There is No Old Protocol
• IETF Recognized - Reserved Multicast Address - Annunciation &
Redundancy
• IETF Recognized - Reserved Ports for SM, FMS
• Consistent Interface with Web Technology
• Easy to extend to standard monitors
General Assembly
28 February 2003
Function Blocks
HMI Each device contains

• One resource block
H1 Fieldbus • Transducer blocks for each

input and output
• At least one function block
FT
FT PID-110
AI-110 FC
FC AO-110
Process
Function blocks:
• Encapsulate basic automation functions
• Reside in device or in host
• Are connected and provide deterministic control
General Assembly
28 February 2003
Flexible Function Block
Flexible Function Block (FFB)

for
Discrete/Batch/Hybrid Applications
Application-Specific I/O Application-Specific Algorithm
Number and Type Configured by User
Configured by User
General Assembly
28 February 2003
Flexible Function Block (FFB)
FFB is a “Wrapper” for an IEC 61131 Application
AI OUT IN_0 OUT CAS_IN AO
DI OUT_D IN_D
IEC
OUT_D IN_D DO
61131
Application
O O I
U I U N
N
MAI T T
1 MAO
1 1 1 -
- - - 8
8 8 8
Flexible Function Block
General Assembly
28 February 2003
Function Blocks
♦ Single Loop Control ♦ Lead/Lag Compensation ♦ Supervisory Data Acquisition
♦ Feedforward Control ♦ Signal Characterization ♦ Sensor bus interfacing
Example ♦ Cascade Control ♦ Timing and Integration ♦ Coordinated Drives
Applications ♦ Override Control ♦ Advanced Alarming ♦ Batch Control
♦ Ratio Control ♦ Motor Control
♦ Manual Loader ♦ Math
Basic Function Blocks Advanced Function Blocks Flexible Function Blocks

PID Control, Ratio Control Analog Alarm, Arithmetic 8 Channel Analog Input/Output
Manual Loader, PD Control Deadtime, Device Control 8 Channel Discrete Input/Output
Ratio,Control Selector Input Selector, Integrator and
Discrete Input/Output Setpoint Ramp Generator Application Specific (IEC 61131-3)
Analog Input/Output Splitter Lead/Lag, Timer
Bias/Gain Signal Characterizer
FOUNDATION
fieldbus
User Layer
Standard Flexible
Function Function
Blocks Blocks
Basic and Advanced Process Control Batch/Discrete/Hybrid/

Applications Remote I/O/PLC Applications
FOUNDATION
fieldbus
Communication H1/HSE
Network
General Assembly
28 February 2003
Integrated Architecture
OPEN, INTEGRATED
ARCHITECTURE MIS
for
INFORMATION INTEGRATION
APPLICATION
PACKAGES
HSE - Server
Integration
HSE - Subsystem
Integration
H1 - Device P P P P
Integration L L L L
General Assembly
28 February 2003
H1 INTEGRATES DEVICES AT THE FIELD LEVEL OPEN, INTEGRATED

ARCHITECTURE
Function Blocks Running in Field Devices for
Control in the Field - Single Loop Integrity INFORMATION
Fault Tolerant – Multiple Link Masters INTEGRATION
Power & Signal on a Single, Multi-Drop Wire Pair
Distances up to 1900 Meters without Repeaters
Can Add Repeaters - Fiber Optics Option
Supports Intrinsic Safety
H1 - Device P P P P
Integration L L L L
General Assembly
28 February 2003
HSE INTEGRATES SUBSYSTEMS OPEN, INTEGRATED

ARCHITECTURE
High Performance Control Backbone (100 Mbps) for
Standard Ethernet Equipment and Wiring INFORMATION
Standard Function Blocks PLUS INTEGRATION
Flexible Function Blocks for Discrete/Batch/PLC
Redundant HSE Interfaces and Devices
Linking Devices Integrate H1
HSE - Subsystem
Integration
General Assembly
28 February 2003
HSE INTEGRATES DATA SERVERS OPEN, INTEGRATED

ARCHITECTURE
Application Packages Provide Information for MIS for
Servers Provide the Platform for Application Package MIS INFORMATION
e.g. HMI, Configuration, Diagnostics, ERP, MES, etc. INTEGRATION
HSE is the Open Common Interface for Server Access
All H1 and HSE Data is Available to the Server
APPLICATION
PACKAGES
HSE - Server
Integration
General Assembly
28 February 2003
H1 + HSE Provides Full Information Integration
• H1 and HSE Have the Same Proven Function Block User Layer
• H1 and HSE Have Plug and Play Interoperability
• H1 Provides Distributed Process Control and Device Integration
• HSE Provides High Performance Control and Subsystem Integration
• End User Selects Communications Performance Desired: H1 or HSE
• HSE Allows Data Servers to Integrate all Plant Information
H1 + HSE Flattens the Plant Hierarchy, Cuts Cost and Increases Performance
• Integration of Sensors, I/O Converter and Controller into a Single Device
• Single Architecture Reduces Networks and Gateways in the Plant
• Open Architecture has Suppliers Competing on Features, Not Network
• High Volume of H1 Devices and COTS Ethernet is Driving Down Cost
• Diagnostics Reduce Shutdowns and Reduce MTTR
General Assembly
28 February 2003
How it Works
Distributed Control on H1
General Assembly
28 February 2003
Function Blocks
A location-independent model for distributed control
HMI
H1 Fieldbus
FT
FT
FC
FC
Process
AI-110 PID-110 AO-110
General Assembly
28 February 2003
H1 DEVICE TYPES
• The “Link Active Scheduler” (LAS) controls
communication on the bus.
– Distributes Time to other devices
– Compels devices to publish data at precise time
• Device Type
– Link Master - Capable of supporting the LAS function.
– Basic - Not capable of supporting the LAS function.
General Assembly
28 February 2003
DEVICE TYPES H1
LAS = Link Active Scheduler
Fieldbus
BASIC
DEVICE
LAS
LINK MASTER
DEVICE
BASIC
DEVICE
BASIC
DEVICE
XLAS
LINK MASTER BASIC

DEVICE DEVICE
General Assembly
28 February 2003
Deterministic Scheduling
• Execution of function blocks and communication is
scheduled
• Execution is deterministic
• Control is really distributed “on the wire”
• KEY feature of FOUNDATION fieldbus - it is a system,
not just a bus
• FF also includes provisions for a back-up schedule
General Assembly
28 February 2003
Scheduling Example
HMI Each device contains

• One resource block
H1 Fieldbus • Transducer blocks for each

input and output
• At least one function block
FT
FT PID-110
AI-110 FC
FC AO-110
Process
Function blocks:
• Encapsulate basic automation functions
• Reside in device or in host
• Are connected and provide deterministic control
General Assembly
28 February 2003
Scheduling Example
AI110
PID110
AO110
Macrocycle
Cyclic Acyclic
Alarms/Events
Maintenance/Diagnostic Information
Program Invocation
Function Block Execution Permissives/Interlocks
Display Information
Cyclic Communication - Publish
Trend Information
Acyclic Communication Configuration
General Assembly
28 February 2003
How it works
Device Description Technology
General Assembly
28 February 2003
Device Descriptions
• Device descriptions describe all the capabilities of a
Foundation Fieldbus device in a standard language
• Device description services uses device
descriptions to provide all the information from a
device to the system’s host devices
Benefits of device descriptions include:
•
Operators use only one HMI, and all process data
looks and feels the same for operators
• Maintenance needs only one configurator, not a
different handheld for each device
• Device descriptions are the key to interoperability
General Assembly
28 February 2003
Device Description
A DD contains the following information about the
parameters of a device:
•Attributes like coding, name, engineering unit, write
protection, how to display etc.
• The arrangement of the parameters in a menu
structure, names of menus and submenus.
• Information about the relation of a parameters to
others.
• Information about help texts and help procedures.
• Information about necessary operating interactions
(e.g. calibration), also called methods.
General Assembly
28 February 2003
Vendor Writes DD for Device
DDL Source File
VARIABLE ProcessVariable
{ LABEL "MEASURED_VALUE";
TYPE FLOAT { DD Token File (.FFO)
DISPLAY_FORMAT "3.1f";
MAX_VALUE 110.0; 009 101
MIN_VALUE 0.0; 002 "MEASURED_VALUE"
}} 001 010
061 "3.1f"
021 066 220 000 000
020 000 000 000 000
Tokenizer Tool DD Symbol File (.SYM)
block __analog_output_block 0x800201F0

member VL_SP_LO_LIM variable-list 0xC0010175
variable ProcessVariable float 0x80020136
General Assembly
28 February 2003
Host Associates DD with Data
“Process Value”
Fieldbus
DD
101011010101010…..
Structured text description
for each field device that
precisely defines the
format of its data
Descriptions Values
Enumerations …
Units …
Relationships …
Calibration …
Help ...
General Assembly
28 February 2003
Host Uses DD to display data
Values are read from
the device over the
fieldbus.
Number of digits of precision
Engineering Unit
Label
DD Files
25.50 %
Host Measured_Value
Application
Device Description
Services Library
General Assembly
28 February 2003
Capability file
• Based on the Common File Format specification
• Provides the details of device for offline
configuration tool.
• Describes the Communication aspects of the device
• Provides examples values
General Assembly
28 February 2003
CFF VS. DD
Device Description Capability File
•Describes Function Block •Profile information
parameters
• Actual number of Function
• Menu and Method Blocks inside device
Procedures for configuring
a device’s Function Block. • Function Block Timing
• Multi-lingual label and help • Provides example

information communication and
function block data
• Parameter relationships
• Details host systems need
to for offline configuration.
General Assembly
28 February 2003
DD/CFF Files available on the Web
The Fieldbus Foundation
will maintain the Device Fieldbus.org
Descriptions and
Capability Files for
registered devices.
Accessible via FTP or
http://www.fieldbus.org
INTERNET
Fieldbus Host System

General Assembly
28 February 2003
How it works
HSE Redundancy
General Assembly
28 February 2003
HSE Fault Tolerance
• Use COTS hardware and software.
• Provide redundant communication paths;
redundant paths must be transparent to
Applications.
• Provide for redundant devices; devices connect to
all network types.
• Test connectivity through all ports; devices make
independent decisions about which port to use.
• Devices share knowledge of network status.
General Assembly
28 February 2003
HSE Fault Tolerant Example
Simple Network (Non- Redundant)
HSE Subnet
Non Fault Tolerant LAN
Interface
A
A A
HD
LD-X LD-Y
LD = Linking
Device
HD = Host
Device
General Assembly
28 February 2003
Dual Interface/Dual LAN
HSE Subnet
LAN A
LAN B
Interfaces
A
A B A B HD
A B
LD-X LD-Y HD
LD = Linking Device
HD = Host Device
General Assembly
28 February 2003
Dual Interface/Single LAN
HSE Subnet
Single Fault Tolerant LAN
Interface
A
A B A B
HD
LD-X LD-Y
LD = Linking
Device
HD = Host
Device
General Assembly
28 February 2003
Redundancy Example
Device Device Device Device

1 2 3 4
A B A B A B A B
X X
LAN A
LAN B
Node 3: Interface A partial failure; can receive, but not transmit

Node 4: Interface B complete failure.
General Assembly
28 February 2003
Redundancy Example
Diagnostic Message Received Reported Status Extracted from
Diagnostic Message
Device # Received on Received on Device 3 Device 3

Interface A Interface B Received on Received on
Interface A Interface B
Received from Received from Received from Received from
Interface A/B* Interface A*/B Interface A/B* Interface A*/B
1 OK/X X/OK X/X X/OK
2 OK/X X/OK X/X X/OK
3 (this device) OK/X X/OK OK/X X/OK
4 OK/X X/X X/X X/X
* Note that the cross statuses will all be “X” for a dual LAN. That is, messages originating from an
interface A are never heard on an interface B and vice versa.
General Assembly
28 February 2003
Testing and Registration
General Assembly
28 February 2003
Interoperability
Interoperability is the capability to substitute a field
device from one manufacturer for that of another
manufacturer without loss of functionality.
Interoperability offers:
• Freedom to choose the right device for an
application
• The ability of the manufacturer to add new and
useful features
• Elimination of proprietary protocols and custom
software drivers and upgrade
General Assembly
28 February 2003
Benefits of Testing and Registration
• Every device must pass interoperability

testing to be registered by the Foundation
• Assures users that devices from different
manufacturers have been subjected to
common set of tests
• Confirms characteristics of devices
• Assures interoperability
Registered devices display the Fieldbus Foundation

registered mark
Fieldbus Foundation publishes a list of registered

devices in the product directory at www.fieldbus.org
General Assembly
28 February 2003
H1 Conformance Testing
• Conformance test of communication stack confirms
compliance with FOUNDATION protocol
specification
• Conformance testing is performed only at
Fraunhofer Institute, an independent testing facility
in Germany
• Test results from stack under test are compared
with those from a system with a known good stack
for verification
General Assembly
28 February 2003
Stack Registration Process
Upper
Tester
™
= FOUNDATION
Tests Run at Registered

H1 Stack Fraunhofer Institute H1 Stack
to be tested in
Karlsruhe, Germany
Report issued to FF
General Assembly
28 February 2003
Stack Registration Status
50 Registered Stacks
•26 Link Masters
• 24 Basic Stacks
Updated: 14-Feb-2003
General Assembly
28 February 2003
HSE Testing Kit (HTK) Test Scope
• Annunciation and Startup
• Address/Tag Assignment
• System/Network Management Behavior
• HSE Messaging
• H1-H1 Bridging
• HSE-H1 Communication
• Capability File
• Redundancy Messaging
General Assembly
28 February 2003
HSE Linking Device Registration
HSE
HSE
Stack
™
Registered = ;
FOUNDATION
H1 Stack
Tests Run at Registered
Fieldbus Foundation
Linking Device
H1
in
Austin, TX
Exhibit A on Web Site
Linking Device Report issued to
;
to be tested Device Manufacturer
General Assembly
28 February 2003
Linking Devices
• Allow communications
between HSE and H1
networks
• Registered Linking Devices
– ABB
Linking
– Emerson Device
HSE
– SMAR
– Softing
H1 Links
General Assembly
28 February 2003
Interoperability Testing Program
• Confirms common characteristics of devices
• Essential for plug & play
• Assures users that devices from different
manufacturers have been subjected to common set
of tests
• Fieldbus Foundation will publish list of registered
devices in a product directory (www.fieldbus.org)
• Devices tested and verified by a Third Party
General Assembly
28 February 2003
Interoperability Testing Requirements
• Registered Communication Stack
– Confirm compliance with communication protocol
specification
• Physical Layer Conformance Test
– Ensure device complies with physical layer specification
Only when both requirements are meet can a

manufacturer submit for Interoperability Testing.
General Assembly
28 February 2003
Device Registration Process
Registered Function
Stack Blocks
= ;
™
FOUNDATION
Tests Run at
Registered
Fieldbus Foundation
in
Device
Austin, TX
Device to be tested Listed on FF web site
;
Report issued to
Device Manufacturer
General Assembly
28 February 2003
Device Registration Status
128 Unique Registered Devices
221 Total Registrations (multiple device versions)
General Assembly
28 February 2003
HIST Program Details
• HIST participation is voluntary
• Host System Vendors develop Test Cases based on
FF-controlled HIST Procedures
• FF Staff perform or witness running of tests on host
• Host completing HIST is issued a Letter of
Confirmation (LOC)
• Host functionality supported and posted on FF web
site
General Assembly
28 February 2003
HIST Host Feature Checklist
• Device Tag Assignment • FF Alert Configuration
• Device Address • FF Alert Handling
Assignment
• FF Trend Configuration
• Configuration of Link
• FF Trending Handling
Master Devices
• Block Tag Configuration • Device Description
Services
• Block Instantiation
• DD Method Execution
• Standard Blocks
• DD Menu Handling
• Enhanced Blocks
• DD Edit Displays Handling
• Custom Blocks
• Capability Files
• Function Block Linkage
Configuration
General Assembly
28 February 2003
Host Interoperability Support Test
• The following hosts have met the requirements and
have joined the HIST Program
– ABB - Industrial IT
– Emerson Process Management - DeltaV
– Foxboro - FoxCAE
– Honeywell - PlantScape
– Honeywell - Experion-PKS
– Rockwell - Process Logix
– Smar - System 302
– Yamatake - Industrial-DEO
– Yokogawa - CENTUM
– Yokogawa - STARDOM
General Assembly
28 February 2003
HIST - User Benefits
• Confirms functionality supported by Host Vendors
• Essential for plug & play
• Assures users that registered devices from different
manufacturers have been subjected to many hosts
• Fieldbus Foundation will publish list of Host
functionality supported, and registered devices
used on FF Web site (WWW.FIELDBUS.ORG)
General Assembly
28 February 2003
Additional References
General Assembly
28 February 2003
www.fieldbus.org
Download Technical Guides

•FD-043 Technical Overview
• AG-165 Installation and
Planning Guide
• AG-140 Wiring and
Installation Guide
• AG-163 Intrinsically Safe
Systems Guide
General Assembly
28 February 2003
Title: "Process fieldbuses -
Engineering, Operation and
Maintenance"
Author: Jonas Berge
Publisher: The
Instrumentation, Systems
and Automation Society
(ISA)
ISBN 1-55617-760-7
Price: US$ 95 (US$ 76 for ISA
members)
General Assembly
28 February 2003
Questions
General Assembly
28 February 2003

Basic FF

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Basic FF

Uploaded by

Copyright:

Available Formats

FOUNDATION fieldbus

How It Works and Why It Works!

08:00 – 08:30 Refreshments and Introductions

Fieldbus - a digital, two-way multi-drop communication

Traditional 4-20 mA wiring,

One Process Value Mode, Value, Status, Alarms, Trends

Fieldbus can be used in the same way,

HSE uses the Ethernet/Internet for Communications

HSE CLIENT 100 Meters on Twisted Pair

Plant Plant Plant

HSE is Designed for Flexibility

HMI Each device contains

H1 Fieldbus • Transducer blocks for each

Flexible Function Block (FFB)

FFB is a “Wrapper” for an IEC 61131 Application

AI OUT IN_0 OUT CAS_IN AO

Flexible Function Block

Basic Function Blocks Advanced Function Blocks Flexible Function Blocks

Basic and Advanced Process Control Batch/Discrete/Hybrid/

H1 INTEGRATES DEVICES AT THE FIELD LEVEL OPEN, INTEGRATED

HSE INTEGRATES SUBSYSTEMS OPEN, INTEGRATED

HSE INTEGRATES DATA SERVERS OPEN, INTEGRATED

AI-110 PID-110 AO-110

LAS = Link Active Scheduler

LINK MASTER BASIC

HMI Each device contains

H1 Fieldbus • Transducer blocks for each

Tokenizer Tool DD Symbol File (.SYM)

block __analog_output_block 0x800201F0

• Multi-lingual label and help • Provides example

Fieldbus Host System

Non Fault Tolerant LAN

Single Fault Tolerant LAN

Device Device Device Device

Node 3: Interface A partial failure; can receive, but not transmit

Device # Received on Received on Device 3 Device 3

1 OK/X X/OK X/X X/OK

2 OK/X X/OK X/X X/OK

3 (this device) OK/X X/OK OK/X X/OK

4 OK/X X/X X/X X/X

• Every device must pass interoperability

Registered devices display the Fieldbus Foundation

Fieldbus Foundation publishes a list of registered

Tests Run at Registered

Only when both requirements are meet can a

Download Technical Guides

You might also like