Foundation Fieldbus: EMERSON Process Management Educational Services

FOUNDATION fieldbus
Overview
EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

EMERSON Process Management – Educational Services Course 7032 - Rev 8 - 3/15/04 Copyrighted Material / Duplication Prohibited
1-2
Objectives
Upon completion of this module you will be able to
 Define FOUNDATION fieldbus
 Discuss benefits of FOUNDATION fieldbus
 Describe the Fieldbus Foundation
1-3
PlantWeb Using FOUNDATION fieldbus

PlantWeb is a process automation system that uses

the power of field intelligence to improve plant
performance.
 PlantWeb supports discrete and analog
inputs and outputs as well as HART, Serial,
FOUNDATION fieldbus, Profibus DP,
DeviceNet and AS-i communications
 PlantWeb supports Control Anywhere
 PlantWeb is like a LAN for process control
1-4
Definition & Key Points
FOUNDATION fieldbus is
 An all digital, serial, two-way communication system that interconnects
intelligent measurement and control devices
 Essentially a Local Area Network (LAN) for field devices
 The name of the Fieldbus developed by the Fieldbus Foundation
FOUNDATION fieldbus allows PID control in the field and in various field devices;
i.e., control anywhere. And it uses Device Description Technology similar to HART.
1-5
Fieldbus Foundation
Members
End-user Councils Board of Directors
President
Executive Committee Quality Assurance
Marketing Committee Technical Steering Administration

Committee
 North America  Applications  Application Engineering
 Europe  Specifications  Field Trials
 Asia Pacific  Standards  Training
 Interoperability  Contracts
 Profiles  Trade Shows
 DD Technology  Newsletters
 Testers/Test Technology
1-6
Fieldbus Foundation
Unlike proprietary network protocols, FOUNDATION fieldbus is neither owned by any
individual company, or regulated by a single nation or standards body. The technology
is controlled by the Fieldbus Foundation, a not-for-profit organization consisting of
more than 100 of the world’s leading controls and instrumentation suppliers and end
users.
Beginnings
 Established September 1994
 Merger of WorldFIP North American and the Interoperable Systems Project
(ISP)
 Not-for-profit corporation
 Approximately 120 of the world’s leading suppliers and end users
 Goal is a single international, interoperable Fieldbus standard
1-7
FOUNDATION fieldbus
ABB Ltd. Ficon Technology, Inc. Mobile Technology Co. Shimadzu Corporation
Accutech Fieldbus Inc. Monsanto Company Siemens Energy & Automation,
AlliedSignal FINT Moore Products Co. Inc.
Amdel, Ltd. Fisher Controls Int., Inc. National Instruments Sira Test & Certification, Ltd.
Key Issue:
Applied Informtion Sciences Fisher-Rosemount Systems, Inc. NEC Corporation Smar International Co.
ASAHI/America Flowserve Corporation Neles Controls Smar Research
Automation Research Institute Fraunhofer Institute NEMA Softing GmbH
of Ministry of Metallurgical Fuji Electric Co., Ltd. Niigata Masoneilan Co,. Ltd. SRC NIITEPLOPRIBOR
Industry GATX Terminals Corp. Nippon Gear Co., Ltd SRI International
Bailey Japan Co., Ltd. Groupe Schneider Nohken, Inc. Sterling Valley Associates
Baker Hughes INTEQ Hartmann & Braun Ohkura Electric Co., Ltd Stone & Webster Engineering
Every Major
Bently Nevada Corporation Hitachi, Ltd. Omni Flow Computers Corporation
Boeing Honeywell, Inc. OSICOM StoneL Corporation
BP Oil - Alliance Refinery HuaKong Technology Co., Ltd. Oval Corporation The Foxboro Company
Bray International, Inc. ifak PC&E Tokyo Keiso Co., Ltd
Brazilian Petroleum Institute Instrument Control Service, PDVSA - Servicios TopWorx
Chevron Research and Inc. Automatizagion Toshiba
Process Control
Technology Intellution, Inc. Pepperl + Fuchs Valmet Automation, Inc.
Chinese Fieldbus Professional interlinkBT PMV, Palmstiernas Instruments VEGA Grieshaber KG
Commission Jet Propulsion Laboratory POHTO Walsh Automation Inc.
Chiyoda Corporation JGC Corporation Presys Instruments Westinghouse Electric
Chubu Electric Power K-Patents Oy R. Stahl Schltgeraete GmbH Westlock Controls
Company Kaneka Engineering Relcom Inc. Wonderware Corporation
Company is a Member
City of Columbus Wastewater Corporation Research Reacto Institute of WorldFIP Europe
Treatment Knick Elektronics Kyoto University Yamaha Corporation
Control System Integrators Kongsberg Simrad AS Richard Hirschmann of Yamatake Corporation
Association Koso Service Co., Ltd America, Inc. Yamatake Industrial Systems
Dresser Industries KROHNE Rockwell Automation Co., Ltd.
Duke/Fluor Daniel Kurihara Kogyo Co., Ltd. Rosemount Analytical, Inc. YCV Corporation
DuPont Engineering Co. Kvaerner, Houston Rosemount Inc. Yokogawa Electric Corporation
EL-O-MATIC BV Magnetrol International, Inc. Saudi Arabian Oil Company Yokogawa Industrial
Elsag Bailey Process Measurement Technology Ltd. Shanoc, Inc. Automation
Automation Micro Motion, Inc. Shell Oil Co. Zhejiang Supcon, Co., Ltd.
Endress + Hauser GmbH + Co. Mitsubishi Electric Corporation Shenyang Institute of
Escola PolitÈcnica da Automation
Universidade de S"o Paulo
Exxon Research & Engineering
Co.
fbusmembers
1-8
1-9
PlantWeb Architecture Model
Management Execution (OPC)
Plant-wide Network
Integrated, Modular Software

(DeltaV/AMS Inside)
Scalable Platforms
(DeltaV Hardware)
H1 Fieldbus Network
Intelligent Field Devices
Process Control Asset Management

1-10
PlantWeb Architecture Model
 Intelligent Field Devices — Can be remotely configured and calibrated via
software using an appropriate host or configurator. Many field devices include
PID functions to allow true distributed control and to support the Control
Anywhere concept.
 Scalable platforms — The DeltaV host has been designed to manage large
amounts of data. It is equally well suited for small and large applications. The
hardware is easily expanded by adding additional controllers and additional I/O
capacity.
 Integrated, modular software (AMS Inside) — A package that allows users to
commission, configure, calibrate, and troubleshoot devices from a Windows
Explorer type screen.
 Management execution — With OLE and OPC, data from the DeltaV system can
be communicated via the existing business LAN to other compliant Windows
applications such as Excel and Access.
1-11
Fieldbus Benefits
1-12
Fieldbus Benefits
Traditional 4-20
 One variable passed in one direction
 Two signal wires per device to I/O subsystem
Fieldbus
 Multiple variable communicated directly between devices and/or controller
 Fieldbus Device Alarms
 PlantWeb Alerts
 One twisted pair of wires from field devices to H1 interface (control system)
1-13
Fieldbus Benefits
Interoperability
Any device from any manufacturer that conforms to the FOUNDATION fieldbus
standards will work well with other certified devices. However, the standards for
certification are currently set to confirm minimum functionality only.
Minimum functionality means that a device will communicate a value that is expected
from its device type; i.e., a temperature transmitter will produce a Fieldbus signal for
the measured temperature. The Fieldbus Foundation certification does not guarantee
that other device “bells and whistles” such as auto-calibration routines or configuration
wizards will be functional and/or interoperable.
1-14
1-15
DeltaV Tested Devices
1-16
DeltaV Tested Devices
Fieldbus Devices:
 Contains the list of manufactures of tested Fieldbus devices.
 Each listed manufacture contains specific Fieldbus devices.
 Each Fieldbus device for a manufacture contains the device description.
 A device description, identified by the revision level for the specific device type.
Note: The category Unknown Manufacture is provided for the import of Fieldbus
devices that are not in the list of tested manufactures.
1-17
Communication Technology
Simplified Fieldbus Communication Model

Blocks
User - Resource
Application - Transducer
- Function
Fieldbus Message
Specification Communication Management:
- Scheduling
Fieldbus Access Communication
- What data is sent to
Sublayer “Stack”
what other device(s)
Data Link Layer - Communication support and
management functions
Physical Layer Field Devices and Wiring
Fieldbus
1-18
The communication technology that is used in FOUNDATION fieldbus is based on a
standard (OSI) model, but does not include layers that are not pertinent to ciritical
process control data. The Fieldbus model consists of three major layers.
 Physical Layer
 Communication Stack
 User Application
In general, you may think of the role of each of the layers as follows:
Physical Layer
The physical layer includes the wiring of the field devices and the components that
actually interface with the process; e.g., transmitters and valve positioners. The Physical
Layer receives encoded messages from the upper layers and converts the messages to
physical signals on the Fieldbus transmission medium and vice-versa.
1-19
Communication Stack
The comm stack consists of the three layers of communication which, taken all together,
manage communication between two devices or between a device and a host such as
DeltaV.
User Application
Fieldbus Foundation has defined a standard User Application based on Blocks;
representations of different types of application functions.
1-20
1-21
Fieldbus Blocks
Function Block
Transducer (Servo) Block Define Control System Behavior
FIELDVUE
Interface to Sensors • AI, AO, DI, DO, PID, etc.
• Calibrate Information • Approximately 30 Blocks Defined
• Configure Information • Blocks Configured by Host to
Implement a Control Strategy
Resource Block
Device Characteristics
• Name
• Manufacturer
• Serial Number
• Enable Features
Fieldbus
1-22
Fieldbus Blocks
Each Fieldbus device includes three different types of blocks.
Resource Block
The resoucrce block includes read only information that helps to define the device.
Information may include:
 Manufacturer Name
 Model Number
 Materials of Construction
 Device Options
Dependng on the device, there may also be several configurable parameters. Examples
include:
 Mode (Automatic or Out of Service)
 Alarm options
 Security and access limiting features; e.g., write locks, feature disabling, etc.
1-23
Fieldbus Blocks
Function Block
FIELDVUE
Resource Block
• Name
• Manufacturer
• Serial Number
• Enable Features
Fieldbus
1-24
Fieldbus Blocks
Transducer Block
Transducer Blocks are an interface to sensors used to measure temperature, pressure,
flow, etc. The transducer block includes calibration and other data.
For example:
 Device calibration information
 Sensor data
The mode of the transducer block (automatic or out of service) is configurable. In order
to perform calibration routines on most devices, the block must be set to OOS (*out of
Service).
1-25
Fieldbus Blocks
Function Block
FIELDVUE
Resource Block
• Name
• Manufacturer
• Serial Number
• Enable Features
Fieldbus
1-26
Fieldbus Blocks
Function Blocks
The function block(s) in a device depend on the type and style of the device. For
example, a pressure transmitter with only one PV may include only one AI block. On
the other hand, the transmitter could include a second PV, for example, board
temperature, and it could include a PID algortihm.
Note: Shadow Blocks in DeltaV Control Studio are representations of Function Blocks
in Fieldbus devices.
1-27
Role of Function Blocks
Control Modules in DeltaV — When using DeltaV as a host, the inputs and outputs of
function blocks in various field devices and in the controller are graphically linked
together to form a complete control strategy called a control module. The graphical
blocks that are included in DeltaV’s Control Studio package are sometimes referred to
as Shadow Blocks.
1-28
1-29
Device Descriptions (DDs)
The Fieldbus Foundation provides a standard software library called Device Description
Services which can read the DD binary. Any host with Device Description Services can
interoperate with a FOUNDATION device if it has the device's DD.
DD’s
 Define Standard Block Parameters and Supplier Unique Parameters
 Are loaded into a host that supports DD Services (DeltaV)
 Are unique for every different device
 Revision level must match device revision
1-30
Device Descriptions (DD’s) are a key element of the User Layer technology that enables
interoperability. DD’s are used to describe:
 Standard block parameters
 Supplier unique parameters
DDs allow any compliant host to interoperate these parameters. The DD is fundmentally
an extended description of the device parameters used by the host.
The Fieldbus Foundation provides DDs for all standard blocks.
Device suppliers typically prepare an incremental DD which adds additional functionality.
Device suppliers register common DD's with the Fieldbus Foundation. These registered
DDs are available to the users with a subscription process.
1-31
The Web site for DeltaV tested and supported
device DD’s is
Easydeltav.com/keytechnologies/
fieldbus/devicedownloads
 Select the DeltaV revision or
manufactures
 Select from the list of verified devices
 Download the device revision required
1-32
1-33
Communication Scheduling
1-34
Communication Scheduling
Distribution of control to the field device is made possible by synchronizing:
 Function block execution
 Communication of function block parameters on the Fieldbus
Macrocycle - A single iteration of a schedule within a segment. The schedule macro-
cycle is the user-specified execution time for all the Fieldbus function blocks on the
segment. Change the scheduled macrocycle by clicking
DeltaV Explorer  Fieldbus port  Properties  General tab
Valid choices are 250 msec, 500 msec, 1 sec (default), 2 sec and 5 sec. The schedule
macrocycle should always be set greater than, or equal to, the required macrocycle.
The required macrocycle is the actual execution time plus any publisher CD time. This
is calculated by the LAS (H1 card). Check the required macrocycle by clicking
DeltaV Explorer  H1 port  Properties  Advanced tab
If the required macrocycle is calculated for a time greater than the schedule macrocycle,
the required macrocycle takes precedence over the configured macrocycle.
1-35
Device Types
Linkmaster Device
DeltaV H1 Card CD
• Maintains Live List - PN (Device X)
• Manages Macrocycle - CD
(Scheduled Communication)
• Issues Pass Token - PT
(Unscheduled Communication)
Publish Message
Basic Devices
Field Instruments Device X Device Y Device Z
• Respond to PN Data Data Data
• Respond to CD
• Respond to PT Device Y does not Device Z does not
subscribe to Device X subscribe to Device X
1-36
Device Types
Linkmaster
Link Master devices are capable of becoming the Link Active Scheduler (LAS). The
DeltaV H1 card is the master device in the PlantWeb solution. Field devices may also
have Link Master capabilities and would be a backup LAS if the master fails. The Link
Master performs many functions, including the following:
Scheduled Communications
 Macrocyle — The LAS maintains a list of tramsmit times for all data buffers in
all connected devices.
 CD (Compel Data) — When it is time for a particular device to transmit the
contents of its buffer, the LAS sends a CD (Compel Data) message to the device.
 Publish/Subscribe — Upon receipt of a CD, the device publishes (sends) data to
all devices on the Fieldbus. Devices that are configured to receive the data are
called subscribers.
1-37
Device Types
Publish/Subscribe
The H1 card supports a maximum of 20 publisher and 20 subscriber links per port not to
exceed a total 25 links. For example, the card can support 20 publisher and five
subscriber links or five publisher and 20 subscriber links.
A link is defined as a connection between a Fieldbus parameter in one device on the
segment and a Fieldbus parameter in another device on the segment. More specifically,
a subscriber link is an input parameter in a Fieldbus device receiving an output from a
Fieldbus device parameter or DeltaV controller on the segment. A publisher link is an
output from a DeltaV controller or Fieldbus device to the input of a parameter in a
Fieldbus device.
Basic Devices
Basic devices are those that do not have the capability of becoming the LAS.
1-38
Device Types
Uncheduled Communications
 Probe Node (PN) and Live List Maintenance — Between transmissions
of scheduled messages, the LAS regularly issues a PN (probe node) message to
determine if any changes have been made to the list of devices on the “live list”.
If devices have been added or removed, the LAS revises the Live List.
 Pass Token (PT) — Between transmissions of scheduled messages, each device
is given an opportunity to transmit unscheduled messages. The LAS grants
permission to access the Fieldbus for unscheduled communication by issuing a
(PT) pass token to the device. When the device receives the token, it is allowed
to send messages. Unscheduled tranmissions are generally for changes in
configuration data, changes in setpoints, alarm information, and other non
control-critical information.
1-39
Device Audit Trail (DAT)
Changes to the configuration of a Fieldbus device resource or transducer block are
recorded in the Device Audit Trail which displays up to 10,000 events. Select
Fieldbus device (right mouse)  Audit Trail
1-40
Device Audit Trail software enables the DeltaV system to maintain an audit trail of
historical records, called events, for Fieldbus devices. Device Audit Trail software
records changes to a device’s configuration, such as changes made from a resource or
tranducer block’s properties screen or context (right-click) menu. When a user changes
a devices upper or lower sensor trim for example, Device Audit Trail records the
changes. An audit trail is maintained for all standby and commissioned Fieldbus
devices.
Device Audit trail displays up to 10,000 events. If there are more than 10,000 events,
the most recent 10,000 are displayed. The system automatically sorts the audit trail
events by time, from the most to least recent.
Once the software is installed and the PC is licensed, you can view events for a device
by selecting the device, clicking the right mouse button and selecting Device Audit Trail
from the pop up menu.
Note: The Device Audit Trail is an install selection on the DeltaV installation CD.
1-41
Device Audit Trail display includes the following information for each event
 Date and time
 Event type (configuration change in the current version)
 User (who made the change)
 Reason the event was recorded
– User Configuration Change (changing a block to out of service mode)
– Field Change (changing from standby to commissioned state)
– A method performed (setting factory trim on 3244 transmitter)
 Application effecting the change
1-42
Double clicking the event displays a

Configuration Change Detail dialog
box. This dialog box can not be edited.
1-43
1-44

Foundation Fieldbus: EMERSON Process Management Educational Services

Uploaded by

Copyright:

Available Formats

Foundation Fieldbus: EMERSON Process Management Educational Services

Uploaded by

Document Information

Original Title

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

Foundation Fieldbus: EMERSON Process Management Educational Services

Uploaded by

Copyright:

Available Formats

FOUNDATION fieldbus

EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

PlantWeb is a process automation system that uses

End-user Councils Board of Directors

Executive Committee Quality Assurance

Marketing Committee Technical Steering Administration

Integrated, Modular Software

Intelligent Field Devices

Process Control Asset Management

Simplified Fieldbus Communication Model

Physical Layer Field Devices and Wiring

Double clicking the event displays a

You might also like