Professional Documents
Culture Documents
Overview
FOUNDATION™ fieldbus
“Freedom to Choose. Power to Integrate.”
Compliments of:
This overview has been prepared to aid understanding of the technical aspects of FOUNDATION
fieldbus.
The booklet begins with a brief summary of fieldbus benefits followed by the goals, principles
and organization of the not-for-profit Fieldbus Foundation.
The main portion of the booklet is devoted to the definition and explanation of key technical
concepts inherent in FOUNDATION fieldbus technology.
I sincerely hope this information proves useful to you. Please contact the Fieldbus Foundation
if you need additional information about this exciting new technology.
David A. Glanzer
Director of Technology Development
Fieldbus Foundation
9005 Mountain Ridge Drive
Bowie Bldg., Suite 200
Austin, TX 78759-5316
USA
DISCLAIMER OF WARRANTIES
This document is provided on an “as is” basis and may be subject to future additions, modifications, or corrections. The Fieldbus
Foundation hereby disclaims all warranties of any kind, express or implied, including any warranty of merchantability or fitness for
a particular purpose, for this document. In no event will the Fieldbus Foundation be responsible for any loss or damage arising
out of or resulting from any defect, error or omission in this document or from anyone’s use of or reliance on this document.
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Table of Contents
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Table of Contents
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Table of Contents
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Introduction
1.1 H1 Benefits
Data Service
Significant benefits are achieved in the control
H1 * HSE system life-cycle through the application of H1
fieldbus technology (Figure 3).
I/O P PLC PLC
Workstations
*Linking Planning
Device Plant/Factory and Operation Maintenance Evolution
Figure 1 Installation
Figure 2 Figure 3 3
Figure
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Introduction
1.1.2 Expanded View of the Process and The consistent, block-oriented design of function
Instruments blocks allows distribution of functions in field
The self-test and communication capabilities of devices from different manufacturers in an
microprocessor-based fieldbus devices help integrated and seamless manner, thus reducing
reduce downtime and improve plant safety. risk of system failure.
Upon detection of abnormal conditions or the need Distribution of control into the field devices can
for preventive maintenance, plant operations and reduce the amount of I/O and control equipment
maintenance personnel can be notified. This allows needed, including card files, cabinets, and power
corrective action to be initiated quickly and safely supplies.
(Figure 5).
H1 4-20 mA
AI PID
AO
Traditional
Fieldbus
Traditional 4-20 mA Fieldbus Control and I/O
One Variable Multiple Variables requires extra equipmnet Control and I/O in
One Direction Both Directions field instruments.
Figure 4 Figure 6
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Introduction
1.1.4 Wiring Savings The status associated with function block parameters
The H1 fieldbus allows many devices to connect to is generated by field instruments based on failed
a single wire pair. This results in less wire, fewer sensors, stuck valves, etc., and is used for loop shut-
intrinsic safety barriers, and fewer marshaling downs, windup protection and bumpless transfer.
cabinets (Figure 7).
1.2.4 Control Backbone
HSE provides peer-to-peer communication capabili-
1.2 HSE Benefits
ty. Devices communicate with each other directly
In addition to the same life cycle benefits as H1, without having to go through a central computer.
HSE provides the control backbone that integrates This makes it possible to realize powerful, advanced
all of the systems in the plant. control strategies involving variables throughout the
plant without the risk of a central computer failure,
1.2.1 High Performance further reducing risk. HSE can also bridge informa-
tion between devices on different H1 networks at
FOUNDATION™ fieldbus enables asset management
different ends of the plant. Thus, control can span
functions such as diagnostics, calibration, identifica-
between process cells and a plant area.
tion and other maintenance management operations
to “mine” massive information from field devices in
HSE replaces enterprise, control and remote-I/O
real-time. Asset management allows users to move
networking levels, thus flattening the enterprise
to proactive maintenance which allocates resources
pyramid.
to where they are really needed. Users employing
fieldbus-based field devices and permanently
The Linking Device (LD) brings data from one or
connected online asset management software
more H1 fieldbus networks directly onto the
need HSE performance.
HSE backbone.
1.2.2 Subsystem Interoperability
1.2.5 Standard Ethernet
Plants are comprised of a number of subsystems.
Standard cable is used for HSE devices; no
With HSE, subsystems for burner management,
special tools or skills are required. Installation
gas chromatographs, paper web scanners, shut-
is simple and fast. HSE uses standard Ethernet
down systems, compressor controls tank farms,
network equipment such as switches.
etc., integrate easily because of the open protocol.
Users can mix and match subsystems for basic
Standard Commercial Off-The-Shelf (COTS)
control, emergency shutdown, paper quality control,
Ethernet components are made in extremely
advanced control and compressor control, etc.,
high volume. Cable, interface cards and other
from different suppliers. Utilizing HSE, information
networking hardware are extremely low cost com-
can be accessed without custom programming.
pared to proprietary networks. Ethernet options
Users can select decimal subsystems to keep cost
for media include twisted pair, fiber optics and
low, while at the same time reducing the configura-
wireless. Networking hardware is available in
tion effort.
both commercial and industrial grades from
many suppliers.
Data integrity, diagnostics and redundancy manage-
ment are part of HSE and work seamlessly between
devices from different manufacturers.
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Organization
2.1.3 President
The President reports to the Board of Directors,
manages the day-to-day activities of the Fieldbus
Foundation, and provides direction for the Executive,
Technical, Marketing, and Member Support functions.
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
the activities of the foundation and provide input to and training, newsletter printing and distribution,
help ensure the specifications meet the needs of the memberships, coordination of trade shows and field
marketplace now and in the future, and to promote tests, product catalogs, Device Description software,
the further adoption of the technology. and device registrations.
USER USER
APPLICATION APPLICATION
FIELDBUS MESSAGE FMS USER Encoded Data
FIELDBUS MESSAGE SPECIFICATION PCI*
SPECIFICATION 4 0 to 251
APPLICATION LAYER 7
FIELDBUS ACCESS FIELDBUS ACCESS
SUBLAYER FAS FMS PDU**
SUBLAYER
PCI*
PRESENTATION LAYER 6 1 4 to 255
COMMUNICATION
SESSION LAYER “STACK” DATA LINK LAYER DLL Frame Check
5 PCI*
FAS PDU** Sequence
TRANSPORT LAYER 4 5 - 15 5 to 256 2
Figure
Figure9 9 Figure 10
Figure 10
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
The User Application is not defined by the OSI model. Devices are configured using Resource Blocks and
The Fieldbus Foundation has specified a User Application Transducer Blocks. The control strategy is built
model, significantly differentiating it from other models. using Function Blocks.
Blocks
USER USER
APPLICATION APPLICATION
Resource
FIELDBUS MESSAGE Block
SPECIFICATION
FIELDBUS ACCESS
SUBLAYER Function
COMMUNICATION Transducer
Block Block
“STACK”
PHYSICAL LAYER
PHYSICAL LAYER PHYSICAL LAYER
Fieldbus
Figure
Figure 3111 Figure 12
Figure 32
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
The following eleven standard function blocks are For example, a simple temperature transmitter may
defined by the g FF-892 Function Block contain an AI function block. A control valve might
Application Process – Part 3. contain a PID function block as well as the expected
AO block. Thus, a complete control loop can be built
Function Block Name Symbol using only a simple transmitter and a control valve
Device Control DC (Figure 14).
Output Splitter OS
Signal Characterizer SC 3.1.3 Transducer Blocks
Lead Lag LL g FF-902 Transducer Block Application Process –
Deadtime DT Part 1
Integrator (Totalizer) IT g FF-903 Transducer Block Application Process –
Setpoint Ramp Generator SPG Part 2
Input Selector IS
Arithmetic AR Like the Resource Block, the Transducer Blocks are
Timer TMR used to configure devices.
Analog Alarm AAL
Transducer Blocks decouple Function Blocks from
The following four standard function blocks are the local input/output functions required to read
defined by the g FF-893 Function Block sensors and command output hardware. They
Application Process – Part 4. contain information such as calibration date and
sensor type.
Function Block Name Symbol
Multiple Analog Input MAI 3.1.3.1 Supporting Objects
Multiple Analog Output MAO The following additional objects are defined in the
Multiple Discrete Input MDI User Application:
Multiple Discrete Output MDO
Link Objects define the links between Function
The Flexible Function Block is defined by the Block inputs and outputs internal to the device and
g FF-894 Function Block Application Process – across the fieldbus network.
Part 5. A flexible Function Block (FFB) is a user
defined block. The FFB allows a manufacturer or Trend Objects allow local trending of function block
user to define block parameters and algorithms to parameters for access by hosts or other devices.
suit an application that interoperates with standard
function blocks and host systems (Figure 13). Alert Objects allow reporting of alarms and events
on the fieldbus.
Function blocks can be built into fieldbus devices as
needed to achieve the desired device functionality. Multi-Variable Container (MVC) Object serves to
“encapsulate” multiple Function Block parameters
in order to optimize communications for Publishing-
Subscriber and Report Distribution transactions. It
AI OUT IN_0 OUT CAS_IN AO has a user-configured list to define the required
parameters, whose data values are referenced in a
variable list.
DI OUT_D IN_D
IEC
OUT_D IN_D DO
61131
View Objects are predefined groupings of block
Application
O O I parameter sets that can be displayed by the
U I U N
MAI T N T
1 MAO human/machine interface. The function block
1
1
- -
1
-
-
8
specification defines four views for each type of
Flexible Function
8 8
Block
8
block. Figure 15 shows an example of how common
Function Block variables map into the views. Only
a partial listing of the block parameters is shown in
Figure 13 the example.
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
HSE Fieldbus
• VIEW_2 - Operation Static -
Information which may need to
be read once and then dis-
Linking
Device H1 Fieldbus played along with the dynamic
data.
Device 1 Device 2 PID 110 • VIEW_3 - All Dynamic -
AI 110 Information which is changing
AO 110
and may need to be referenced
in a detailed display.
Links
Diagnostics View
Detail Display Lists
Display Sets
Alerts
View_1 View_2
Operation Operation View_3 View_4 MVC
XYZ Block Dynamic Static All Dynamic Other Static
SP X X
Sensor Transducer Function
PV X X Block 2
SP HI LIMIT X 2 Block 2
CAS IN X
GAIN X
Figure 34 Trend
Object View
Lists
Figure 15 Figure 16
TREND OBJECTS
Fieldbus
VIEW OBJECTS
Object Descriptions
Figure 17
Figure 36
Figure
Figure 18 37
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
For example, in the basic PID control template the DL Offset = 0 for
AI execution.
Sequence
Repeats
standard “0108” FF PID block is used. When the Device 1
block is later assigned to a device the engineering Macrocycle
AI DL Offset = 20 for AI
tool confirms with the Capability File of the device AI Communication.
LAS
that “0108” standard PID is supported. This means Macrocycle
you can drag and drop the same block into a Unscheduled
Communication
Permitted DL Offset = 30 for
PID execution.
DL Offset = 50 for
AO execution.
PID AO PID AO
Scheduled Al Function Block Extension 0
0 20 40 60 80 100 120 20 40 60 80 100 120
Scheduled Communications of Al 20
Scheduled PID Function Block Execution 30
Macrocycle Macrocycle
Scheduled AO Function Block Execution 50
Figure 19 Figure 20
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
In Figure 20, System Management in the transmitter 3.2.2 Device Address Assignment
will cause the AI function block to execute at offset 0. Every fieldbus device must have a unique network
At offset 20 the Link Active Scheduler (LAS) will address and physical device tag for the fieldbus to
issue a Compel Data (CD) to the AI function block operate properly.
buffer in the transmitter and data in the buffer will
be published on the fieldbus. To avoid the need for address switches on the
instruments, assignment of network addresses can
At offset 30 System Management in the valve will be performed by configuration tools using System
cause the PID function block to execute followed Management services.
by execution of the AO function block at offset 50.
The pattern exactly repeats itself assuring the The sequence for assigning a network address to a
integrity of the control loop dynamics. new device is as follows:
Note that during the function block execution, the • An unconfigured device will join the network at
LAS is sending the Pass Token message to all one of four special default addresses.
devices so that they can transmit their unscheduled
messages such as alarm notifications or operator • A configuration tool will assign a physical device
setpoint changes. tag to the new device using System Management
services.
For this example, the only time that the fieldbus
can not be used for unscheduled messages is from • A configuration tool will choose an unused perma-
offset 20 to offset 30 when the AI function block nent address and assign this to the device using
data is being published on the fieldbus. System Management services.
On the HSE fieldbus the function blocks execute • The sequence is repeated for all devices that enter
as shown but, since there is no LAS, the communi- the network at a default address.
cation is immediate instead of scheduled
• Device store the physical device tag and node
3.2.1 Application Clock Distribution address in non-volatile memory, so the device will
FOUNDATION fieldbus supports an application clock retain these settings after a power failure.
distribution function. The application clock is usually
set equal to the local time of day or to Universal 3.2.3 Find Tag Service
Coordinated Time. For the convenience of host systems and portable
maintenance devices, System Management supports a
System Management has a time publisher which service for finding devices or variables by a tag search.
periodically sends an application clock synchroniza-
tion message to all fieldbus devices. The data link The “find tag query” message is broadcast to all
scheduling time is sampled and sent with the appli- fieldbus devices. Upon receipt of the message, each
cation clock message so that the receiving devices device searches its Virtual Field Devices (VFD) for the
can adjust their local application time. Between requested tag and returns complete path information
synchronization messages, application clock time is (if the tag is found) including the network address,
independently maintained in each device based on VFD number, virtual communication relationship
its own internal clock. (VCR) index, and object dictionary (OD) index.
Once the path is known, the host or maintenance
Application Clock synchronization allows the devices device can access the data for the tag.
to time stamp data throughout the fieldbus network.
If there are backup application clock publishers on
the fieldbus, a backup publisher will become active
if the currently active time publisher should fail.
10
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
3.3 Device Descriptions The DDs are similar to the drivers that your personal
computer (PC) uses to operate different printers and
A device is supplied with three device support files: other devices that are connected to the PC. Any
two Device Description Files and one Capability control system or host can operate with the device
File. A critical characteristic required of fieldbus if it has the device's DD.
devices is interoperability. To achieve interoperabili-
ty, Device Description (DD) technology is used in 3.3.1 Device Description Tokenizer
addition to standard function block parameter and g FD-900 Device Description Language
behavior definitions. DDs are platform and operating Specification
system independent. g FD-100 DDL Tokenizer User’s Manual
Object Pointer to
Description Device Description
of Data of Data
Data
DD
Extended Descriptions
Associated with the Data
Figure 41 21
Figure
11
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
Device Descriptions for registered field devices can 3.3.3 Device Description Hierarchy
be found on the Fieldbus Foundation’s website at The Fieldbus Foundation has defined a hierarchy
http://www.fieldbus.org. of Device Descriptions (DD) to make it easier to
build devices and perform system configuration.
3.3.2 Device Description Services (DDS) The hierarchy is shown in Figure 24.
g FD-110 DDS User’s Guide
The first level in the hierarchy is referred to as
On the host side, library functions called Device Universal Parameters. Universal Parameters consist
Description Services (DDS) are used to read the of common attributes such as Tag, Revision, Mode,
device descriptions (Figure 22). etc. All blocks must include the Universal
Parameters.
Note that DDS reads descriptions, not operational
values. The operational values are read from the The next level in the hierarchy is Function Block
fieldbus device over the fieldbus using FMS Parameters. At this level, parameters are defined for
communication services. the standard Function Blocks. Parameters for the
standard Resource Block are also defined at this
New devices are added to the fieldbus by simply level.
connecting the device to the fieldbus wire and
providing the control system or host with the The third level is called Transducer Block
DD for the new device (Figure 23). Parameters. At this level, parameters are defined for
the standard Transducer Blocks. In some cases, the
DDS technology allows operation of devices from transducer block specification may add parameters
different suppliers on the same fieldbus with only to the standard Resource Block.
one version of the host human interface program.
Standard DDs
plus optional
Incremental DDs Number of digits
of precision.
Engineering Unit
Descriptions are Label
read from the DD.
25.50 %
Figure 22
12
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
Universal
Parameters
DD Defined
Services Function AI PID by
Block RESOURCE AI PID Fieldbus Foundation
Device from Inside Device Parameters Specification
Supplier A Descriptions
Transducer
Block TEMP FLOW
Parameters
Device from
Supplier Z Manufacturer
Defined
Specific
by
Fieldbus Parameters Manufacturer
Figure 23 Figure
Figure24
46
13
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
USER USER
APPLICATION APPLICATION
FIELDBUS MESSAGE
SPECIFICATION
FIELDBUS ACCESS
SUBLAYER
COMMUNICATION
STACK
Figure 25
14
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
Technology
Figure 26
Figure 27
15
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology Technology
3.4.1.4.1 CD Schedule The device will remain in the Live List as long as it
The CD Schedule contains a list of activities responds properly to the PTs sent from the LAS.
that are scheduled to occur on a cyclic basis. At The LAS will remove a device from the Live List if
precisely the scheduled time, the LAS sends a the device does not either use the token or immedi-
Compel Data (CD) message to a specific data ately return it to the LAS after three successive tries.
buffer in a fieldbus device. The device immediately
broadcasts or “publishes” a message to all devices Whenever a device is added or removed from the
on the fieldbus. This is the highest priority activity Live List, the LAS broadcasts changes to the Live
performed by the LAS. The remaining operations List to all devices. This allows each Link Master
are performed between scheduled transfers. device to maintain a current copy of the Live List.
Issue
Device x PN, TD, or PT
Figure 23
16
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
3.4.1.4.3 Data Link Time Synchronization 3.4.3 Fieldbus Access Sublayer (FAS)
The LAS periodically broadcasts a Time Distribution g FF-875 Fieldbus Access Sublayer
(TD) message on the fieldbus so that all devices Specification
have exactly the same data link time. This is impor-
tant because scheduled communications on the The FAS uses the scheduled and unscheduled
fieldbus and scheduled function block executions features of the Data Link Layer to provide a service
in the User Application are based on information for the Fieldbus Message Specification (FMS). The
obtained from these messages. types of FAS services are described by Virtual
Communication Relationships (VCR).
3.4.1.4.4 Token Passing
The LAS sends a Pass Token (PT) message to all The VCR is like the speed dial feature on your
devices in the Live List. The device is allowed to memory telephone. There are many digits to dial
transmit unscheduled messages when it receives for an international call such as international access
the PT. code, country code, city code, exchange code and,
finally, the specific telephone number.
3.4.1.4.5 LAS Redundancy
A fieldbus may have multiple Link Masters. If the This information only needs to be entered once and
current LAS fails, one of the Link Masters will then a “speed dial number” is assigned.
become the LAS and the operation of the
fieldbus will continue. The fieldbus is designed After setup, only the speed dial number needs to be
to “fail operational.” entered for the dialing to occur. Likewise, after
configuration, only the VCR number is needed to
3.4.2 System Management communicate with another fieldbus device.
g FF-800 System Management Specification
Just as there are different types of telephone calls
Function Blocks must execute at precisely defined such as person to person, collect, or conference
intervals and in the proper sequence for correct calls, there are different types of VCRs.
control system operation.
3.4.3.1 Client/Server VCR Type
System management synchronizes execution of the The Client/Server VCR Type is used for queued,
Function Blocks to a common time clock shared by unscheduled, user initiated, one to one, commu-
all devices. nication between devices on the fieldbus.
System management also handles other important Queued means that messages are sent and
system features such as publication of the time of received in the order submitted for transmission,
day to all devices, including automatic switchover according to their priority, without overwriting
to a redundant time publisher and searching for previous messages.
parameter names or “tags” on the fieldbus.
Fieldbus devices do not use jumpers or switches When a device receives a Pass Token (PT) from the
to configure addresses. Instead, device addresses LAS, it may send a request message to another
are set by configuration tools using System device on the fieldbus. The requester is called the
Management services. “Client” and the device that received the request is
called the “Server.” The Server sends the response
All of the configuration information needed by System when it receives a PT from the LAS.
Management such as the Function Block schedule is
described by object descriptions in the Network and The Client/Server VCR Type is used for operator
System Management Virtual Field Device (VFD). This initiated requests such as setpoint changes, tuning
VFD provides access to the System Management parameter access and change, alarm acknowledge,
Information Base (SMIB), and also to the Network and device upload and download.
Management Information Base (NMIB).
17
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
3.4.3.2 Report Distribution VCR Type The Publisher/Subscriber VCR Type is used by the
The Report Distribution VCR Type is used for field devices for cyclic, scheduled, publishing of
queued, unscheduled, user initiated, and one-to- User Application function block input and outputs
many communications. such as Process Variable (PV) and Primary Output
(OUT) on the fieldbus.
When a device with an event or a trend report
receives a PT from the LAS, it sends its message 3.4.3.4 Summary of VCR Types
to a “group address” defined for its VCR. Devices (Figure 30)
that are configured to listen for that VCR will
receive the report. 3.4.4 Fieldbus Message Specification (FMS)
g FF-870 Fieldbus Message Specification
The Report Distribution VCR Type is typically used
by fieldbus devices to send alarm notifications to Fieldbus Message Specification (FMS) services
the operator consoles. allow user applications to send messages to each
other across the fieldbus using a standard set of
3.4.3.3 Publisher/Subscriber VCR Type message formats. FMS describes the communica-
The Publisher/Subscriber VCR Type is used for tion services, message formats, and protocol
buffered, one-to-many communications. behavior needed to build messages for the User
Application (Figure 31).
Buffered means that only the latest version of the
data is maintained within the network. New data Data that is communicated over the fieldbus is
completely overwrites previous data. described by an “object description.” Object
descriptions are collected together in a structure
When a device receives the Compel Data (CD), the called an “Object Dictionary” (OD), (Figure 32).
device will “Publish” or broadcast its message to all
devices on the fieldbus. Devices that wish to receive
the Published message are called “Subscribers.”
Fieldbus Fieldbus
The CD may be scheduled in the LAS, or it may be Device Device
sent by Subscribers on an unscheduled basis. An User Communication User
attribute of the VCR indicates which method is used. Application Services Application
FMS FMS
FAS FAS
DLL DLL
FIELDBUS ACCESS SUBLAYER SERVICES PHY PHY
FIELDBUS
Figure 31
Client/Server Report Distribution Publisher/Subscriber
VCR Type VCR Type VCR Type
Figure 30 Figure 32
18
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
Read_Request::= SEQUENCE {
Access-specification CHOICE {
index [0] IMPLICIT Index,
variable-name [1] IMPLICIT Name,
variable-list-name [2] IMPLICIT Name,
},
sub-index [3] IMPLICIT Subindex OPTIONAL
}
User
Application ASN.1 Definition of a Read_Request
FMS
FAS
DLL
PHY
Figure 29
Figure 34
20
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
The previous example states that the items Access- 3.5 H1 Physical Layer (31.25 kbit/s)
specification and sub-index occur in SEQUENCE in the g ISA S50.02-1992 ISA Physical Layer Standard
message.
g IEC 61158-2:2000 (ed. 2.0), Fieldbus standard
for use in industrial control systems — Part 2:
The Access-specification is a CHOICE of using
Physical Layer specification and service definition
either an index or a name to access a variable.
g FF-816 31.25 kbit/s Physical Layer Profile
The sub-index is OPTIONAL. It is used only to Specification
select an individual element of an array or record
variable. The Physical Layer is defined by approved
standards from the International Electrotechnical
The numbers in the brackets are the actual encod- Commission (IEC) and ISA (the international society
ing numbers that are used to identify the fields in an for measurement and control).
encoded message.
The Physical Layer receives messages from the
3.4.4.4 Protocol Behavior communication stack and converts the messages
into physical signals on the fieldbus transmission
Certain types of objects have special behavioral
medium and vice-versa.
rules that are described by the FMS specification.
For example, the simplified behavior of a Program
Conversion tasks include adding and removing
Invocation object is shown in Figure 35.
preambles, start delimiters, and end delimiters
(Figure 36).
A remote device can control the state of the
program in another device on the fieldbus. For
example, the remote device would use the Create
Program Invocation FMS service to change the
program state from Non-existent to Idle.
The Start FMS service would be used to change
the state from Idle to Running and so on.
Non- DELETE
existent
USER
CREATE Unrunnable
APPLICATION Example of voltage mode signaling
RESET
Idle
START KILL
Running Fieldbus
Messages
STOP RESUME
Stopped COMMUNICATION
“STACK”
1 1
1 1
User
Voltage
Application
Behavior Rules for the Program
Invocation Object. PHYSICAL LAYER
FMS
FAS
DLL
PHY
Figure 35
Figure 30
Fieldbus Media Time
(Wire)
Figure3611
Figure
21
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
Fieldbus signals are encoded using the well-known and end delimiter. Note that the N+ and N- signals
Manchester Biphase-L technique. The signal is do not transition in the middle of a bit time. The
called “synchronous serial” because the clock receiver uses the start delimiter to find the begin-
information is embedded in the serial data stream. ning of a fieldbus message. After it finds the start
delimiter, the receiver accepts data until the end
Data is combined with the clock signal to create the delimiter is received.
fieldbus signal as shown in the figure below. The
receiver of the fieldbus signal interprets a positive 3.5.1 31.25 kbit/s Fieldbus Signaling
transition in the middle of a bit time as a logical “0” The transmitting device delivers ±10 mA at
and a negative transition as a logical “1” (Figure 12). 31.25 kbit/s into a 50 ohm equivalent load to create
a 1.0 volt peak-to-peak voltage modulated on top
Special characters are defined for the preamble, of the direct current (DC) supply voltage.
start delimiter, and end delimiter (Figure 38).
The DC supply voltage can range from 9 to 32 volts.
The preamble is used by the receiver to synchronize However, for Intrinsically Safe (I.S.) applications, the
its internal clock with the incoming fieldbus signal. allowed power supply voltage depends on the
Special N+ and N- codes are in the start delimiter barrier rating (Figure 39).
1 Bit Time
CLOCK 1
0
CLOCK
1 0 1 0 1 0 1 0
+
PREAMBLE 0
DATA 1 -
1 N+ N- 1 0 N- N+ 0
0 +
START
0 1 1 0 0 DELIMITER 0
+ -
MANCHESTER 1 N+ N- N+ N- 1 0 1
BIPHASE-L +
ENCODING END 0
DELIMITER
- -
Figure 13
FigureFigure
37 12 Figure 38
22
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Technology
31.25 kbit/s devices can be powered directly from 3.5.2 31.25 kbit/s Fieldbus Wiring
the fieldbus and can operate on wiring previously g AG-140 31.25 kbit/s Wiring and Installation Guide
used for 4-20 mA devices. AG-163 31.25 kbit/s Intrinsically Safe Systems
Application Guide
The 31.25 kbit/s fieldbus also supports I.S. AG-165 Fieldbus Installation and Planning Guide
fieldbuses with bus powered devices. To accom-
plish this, an I.S. barrier is placed between the The 31.25 kbit/s fieldbus allows stubs or “spurs”
power supply in the safe area and the I.S. device (Figure 40).
in the hazardous area.
The length of the fieldbus is determined by the
To address Intrinsic Safety applications, the communication rate, cable type, wire size, bus
Fieldbus Foundation supports using either the power option, and I.S. option.
traditional Entity model or the newer Fieldbus
Intrinsically Safe Concept (FISCO). The mixing of the Figure 41 gives a summary of examples of options
Entity model with the FISCO approach in the prepa- available in the Physical Layer standard.
ration of a system design is not recommended.
0
Receiving Transmitting
0.75 to 1.0 V p-p Spurs
Voltage
Figure 39 Figure 15
Figure 14 Figure 40
Figure 41
23
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
High Speed Ethernet
24
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
High Speed Ethernet
of the HSE Presence is employing SNMP augment- The following capabilities are provided by network
ed to support Fieldbus Foundation unique Ethernet management:
Stack parameters. • Configuring the H1 Bridge, which performs data
forwarding and republishing between H1 interfaces
The universal set of protocols which may be includ- • Loading the HSE Session List or single entries in
ed in a given implementation of HSE Presence is this list. An HSE Session Endpoint represents a logical
identified in Table A. communication channel between two or more HSE
devices.
3.6.3 Field Device Access (FDA)
• Loading the HSE VCR List or single entries in this
The FDA Agent has the following objectives: list. An HSE VCR is a communication relationship
• Convey System Management (SM) services over used for accessing VFDs across the HSE.
UDP and Fieldbus Message Specification (FMS) • Performance Monitoring through the collection of
services over UDP/TCP. This allows HSE and H1 field statistics for Session Endpoints, HSE VCRs, and the
devices, conventional I/O devices, and non-FF I/O H1 Bridge.
devices to be connected to the HSE through a linking
• Fault Detection Monitoring.
or a gateway device.
• Republish H1 data from linking devices that do not
support H1 bridging. This allows linking devices to be 3.7 Redundancy
constructed from multiple standalone H1 interfaces
instead of using an H1 bridge. g FF-593 High Speed Ethernet Redundancy
• Send and receive LAN redundancy messages to
support redundancy of HSE interfaces in devices. For use in factory and process automation, Ethernet
has to be made industrial strength. FOUNDATION
The FDA Agent allows control systems to operate fieldbus HSE is based on Ethernet and is used at
over the HSE and/or through Linking Devices and it the host-level of the control system. The host-level
enables remote applications to access field devices of network ties the whole system together linking the
any type across UDP/TCP using a common interface. various subsystems to the host. Thus, the visibility of
hundreds and perhaps thousands of loops depends
3.6.4 HSE System Management on the host-level network as does any intra-area
System management is the activity that integrates control loops. A complete failure could result in heavy
devices on an HSE network into a coherent communi- losses. High availability for the host-level network is
cation system. therefore paramount. HSE is the only open, Ethernet-
based protocol to address the need for round-the-
The following functions are supported: clock availability of network and devices. Because
device and port redundancy requires interoperability
• Each device has a unique, permanent identity and
beyond Ethernet and IP, other Ethernet solutions do
a system-specific configured name.
not support it. HSE is the first standard protocol to
• Devices maintain version control information. offer functionality to select which device in a redun-
• Devices respond to requests to locate objects, dant pair and which one of redundant ports that a
including the device itself. transmitting device should address. Exchange of
• Time is distributed to all devices on the network. redundancy management information is part of the
• Function block schedules are used to start function standard protocol.
blocks.
• Devices are added and removed from the network HSE is built on standard Ethernet, originally a technol-
without affecting other devices on the network. ogy for the office environment. However, industrial
grade hardware is available and HSE has a number
3.6.5 HSE Network Management of functions built in to insure fault tolerance. The
modern form of Ethernet uses UTP (Unshielded
HSE Network Management permits HSE host sys-
Twisted Pair) wiring using a hub-based star topology
tems to conduct management operations over the
in which there is only one device per wire segment.
HSE network with their associated devices with an
HSE interface.
25
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
High Speed Ethernet
Therefore, devices can be disconnected and connect- Media redundancy works only on the physical layer
ed without disrupting other devices and any wire fault and is therefore independent of protocol used.
only affects a single device (i.e., the impact of a fault
is reduced somewhat). Some solutions require a central redundancy
management device that may be an Achilles heel,
A shared hub is a multiple port repeater that joins whereas other solutions have the redundancy
several segments into a single network. A switched management built into the hubs. Very often the
hub is a multiple port bridge that joins several net- media redundancy ring is implemented using fiber
works together. Fiber optic media can be employed optics. The ring is not a standard Ethernet topology
to increase tolerance towards electrical noise and and the special splitting hubs and transceivers
ground potential differences further increasing the usually use standard media but employ proprietary
robustness of the system. Industrial grade hubs with mechanisms to manage the switchover. Therefore,
redundant power supplies, wide temperature ranges, all the splitters in the ring have to come from the
rugged enclosures, etc., are available for use in a same manufacturer.
tough plant environment.
Simple media redundancy may be sufficient for
3.7.1 Need for Host-Level Redundancy some applications, but not all. For example, some
The shutdown of a plant is extremely disruptive applications combine media redundancy with
and downtime means heavy losses. At the host- fully duplicated networks and linking devices.
level the network and devices are shared between
many loops, making these parts very critical to the 3.7.3 Complete Network Redundancy
operation of the plant. If the host-level network is The HSE protocol goes further than simple media
not functioning the operators would be unable to redundancy. Special integrity-checking diagnostics
monitor and supervise the plant and, therefore, and redundancy management part of the HSE pro-
many loops would have to be shut down. The tocol in each device enables use of two completely
host-level network is also used for intra-area control independent networks, redundant communication
loops that would have to be shut down. Unlike the ports, and also redundant device pairs. All redun-
field-level where high availability is achieved by dant Ethernet device pairs and the workstations are
distributing functionality thereby isolating faults to connected to both Ethernet buses. When a single
a small sector, at the rather centralized host-level unit has two ports these are named “A” and “B”.
redundancy is instead used to achieve high The switchover is totally bumpless and transparent.
availability. Any Ethernet network can use media The redundancy scheme leaves several device
redundancy to achieve some measure of increased options open (Figure 45), but they are all compatible
availability, but HSE also supports complete device with each other, e.g.:
and networking redundancy.
• Redundant device pair where primary and
3.7.2 Media Redundancy secondary have one port each
Any Ethernet device even with just a single port can • Redundant device pair where primary and
have simple media redundancy using some form of secondary have two ports each
port “splitter”. Splitters are implemented in different • Single device that has two ports
ways but all work in the same basic fashion. A
single port is split in two, connecting devices All parts of the network have redundancy, including
together in a circle providing alternate communica- the hubs (i.e. two independent networks ensuring
tion paths. If communication in one direction is not that communication can continue even if one
possible, communication is routed the other way network fails). This means that the network can
(i.e., the network is “self-healing”). The switchover sustain multiple faults but still continue to function.
time is very short. Recovery time is much faster Thus the networking is extremely reliable, minimiz-
than the traditional spanning tree algorithm, and ing loss of data and unnecessary shutdowns.
thus operations will continue without any loss of
data. A splitter may either be a transceiver handling The philosophy of the HSE redundancy is one of
a single port requiring one at every node, or may be “operational transparency and diagnostic visibility”.
implemented between hubs in a ring topology.
26
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
High Speed Ethernet
This means that the control application sees either identical devices, one primary and one secondary.
the primary or the secondary Ethernet device The HSE protocol specifies how these devices com-
depending on which one is active, whereas the municate with others and how the communication
system diagnostics sees both. Thus, the diagnostics is switched over. However, HSE does not specify
insures that even the inactive devices are fully how the functionality is switched or how device
functional and ready to take over at any moment. configuration and data are synchronized.
A wide diagnostic coverage is an integral part of
the HSE protocol going far beyond mere hardware
duplication. Every HSE device, including the host or
any “redundancy manager”, independently keeps
track of the status of the networks and all the Single Fault Tolerant LAN
devices on it. Because HSE is not only Ethernet
media but also has a standard application layer,
devices from different manufacturers periodically
exchange their view of the network with each other
Port
using diagnostic messages through all ports on
both networks which also serve as sign of life indi-
cation. Every device has a complete picture of the HD
LD-X LD-Y
network to intelligently select which network, device
and port to communicate with. Failure detection LD = Linking
Device
includes late and lost messages and duplication. HD = Host
Device
Through exhaustive network diagnostics every
device knows the health of the primary and Figure 42
secondary, as well as communication port A and B,
of every other device on the network. Diagnostics in
each device detect failure, allowing the device to
respond to and circumvent these faults as well as
notifying the operator. No other standard protocol
has this level of redundancy capability. Because
LAN A
the redundancy management is distributed to each LAN B
27
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
High Speed Ethernet
operator even if one interface fails. FOUNDATION The distinction between the single LAN and dual LAN
fieldbus always insures there is a window to the topologies is that a device with dual interfaces has the
process. This compares favorably to a solution capability to receive its own transmissions on a single
with only a single field-level interface. LAN topology, whereas this is not possible in the dual
LAN topology.
Primary and secondary devices need to have
identical configuration in order to allow for a quick Figure 44 illustrates the single interface devices on a
switchover in case of failure. When a primary single LAN. There is no redundancy as illustrated. While
device fails the secondary takes over the role of such systems do not benefit from using LAN redundan-
the primary. Primary to secondary configuration cy, the devices are configured to send diagnostic mes-
data synchronization is typically done over the sages to allow detection of Duplicate PD Tags. These
Ethernet. The HSE technology allows the primary networks do benefit from the use of LAN Redundancy.
and secondary units in the device pair to be physi-
cally separated i.e. mounted some distance apart. Figure 43 represents a dual local area network. The
To eliminate the chance of common failures such as topology of two local area networks is restricted to be
faulty backplane or faults due to exposure to stress. within the HSE Subnet. It is not required that they be
identical. LAN A is constructed by connecting interface
3.7.5 LAN Topologies A of all devices to the LAN media. Similarly, LAN B is
This specification does not dictate the topology of HSE constructed by connecting interface B of all devices to
networks, but does divide them into three categories it. There is no connectivity between the LANs. The figure
from a device perspective. does include a device with a single interface. Examples
are hand-held calibrators or commercial workstations.
1. Single interface devices on a single LAN. Such devices are able to communicate only with
2. Dual interface devices on dual LANs. devices connected to the LAN to which their interface is
3. Dual interface devices on a single LAN. connected. Therefore, in the presence of one or more
Port
Dual Port
Type Type Type Type Type
Devices N-1 N-2 N-2 N-3 N-3
HD Node Node Node Node Node
LD-X LD-Y
Figure 44
28
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
System Configuration
faults, they may not be able to communicate with all The second difference is the ability to distribute the
other devices on the Dual LAN. control and input/output (I/O) subsystem functions
from the control system to the fieldbus devices. This
Figure 42 illustrates this type of network. The local area may reduce the number of rack mounted controllers
network topology is not restricted. The distinguishing and remote mounted I/O equipment needed for the
characteristic is that the network has some degree of system design (Figure 46).
fault tolerance, but behaves as a single network. The
figure includes a device with a single interface.
Examples are hand-held calibrators or commercial 4.2 Device Configuration
workstations. Such devices are able to communicate
After the system design is completed and the
with all other devices connected to the LAN.
instruments have been selected, the device
configuration is performed by connecting Function
4.0 SYSTEM CONFIGURATION Block inputs and outputs together in each device
as required by the control strategy (Figure 47).
Fieldbus system configuration consists of two phases:
1) System Design and 2) Device Configuration. After all of the function block connections and other
configuration items such as device names, loop
tags, and loop execution rate have been entered,
4.1 System Design the configuration device generates information for
each fieldbus device.
The system design for fieldbus-based systems is
very similar to today’s Distributed Control System
A stand-alone loop can be configured if there is
(DCS) design with the following differences. The
a field device that is a Link Master. This will allow
first difference is in the physical wiring due to the
continued operation of the loop without the config-
change from 4-20 mA analog point-to-point wiring
uration device or a central console (Figure 48).
to a digital bus wiring where many devices can be
connected to one wire.
The system becomes operational after the fieldbus
devices have received their configurations.
Each device on the fieldbus must have a unique
physical device tag and a corresponding network
address.
TRANSMITTER
Control Room Console VALVE
FIELDBUS DEVICE
FIELDBUS DEVICE
PID
OUT
AI OUT IN
31.25 kbit/s Fieldbus #1
IN AO
31.25 kbit/s Fieldbus #2
Figure 47
Figure 46 Figure4748
Figure
29
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Field Test
Condensate
Tank
TT-104 CV-202
Network Setup Network Setup
VCR Setup VCR Setup LT-101
Device Address List TAG Setup FT-201
Initial Values Link Object Setup
LAS Schedule Initial Values CV-103
Active/Standby LAS Function Block Schedules
FT-204 TT-104
To Water
Recirculation FT Treatment
Pump
FT-102
Link Master Device Fieldbus Basic Devices
Figure 50
Figure4948
Figure Figure 49
30
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Field Test
Wiring was configured by connecting the fieldbus Some applications might specify fewer devices
devices to one of two terminal panels in a junction per wire pair than the test system. In that case,
box located by the process equipment. Two wire the savings shown in the above table would be
pairs, one pair for each terminal panel, were used proportionately reduced according to the specific
to connect the fieldbuses to the control room. wiring configuration.
The total condensate level of the system is During the checkout phase, a reduction in effort
controlled by selecting a preferred setpoint on the to confirm the proper connection of the fieldbus
level PID, LIC-101, which is located in the level devices was observed. One person performed the
transmitter. The level PID is used as the primary checkout by using the test tool connected to the
loop cascaded to the flow PID, FIC-103, located in fieldbus. With conventional 4-20 mA wiring, two
the valve on the feedwater system. people would have been required to check out each
wire and confirm operation of each transmitter.
The re-circulation of condensate, from the conden-
sate tank to the flash tank, is controlled by an Each transmitter was interrogated and adjusted
additional PID loop, FIC-202, located in the valve. remotely. Device parameters such as the high and
The control strategy for this cascade loop is totally low range values were changed without having a
implemented in the transmitters and flow valve as technician adjust a potentiometer in the field.
shown in Figure 50.
When a device was disconnected from the fieldbus,
the disconnection did not affect any other devices
5.2 Installation, Startup, and Operation remaining on the bus. When the device was recon-
Benefits Observed nected, the system had no trouble re-establishing
communication with the device. Approximately two
The wire runs, from fieldbus devices to the terminal person-days of labor (25%) were saved due to the
panel, averaged 28 meters of new wire for each remote verification of wiring, remote device identifica-
device, while two 185 meters of existing wire runs tion, and remote device configuration checkout.
were used from each of the terminal panels to the
control room. The processing load on the DCS controller was
reduced because of the PID algorithms which were
If standard 4-20 mA analog devices had been used, executing in the fieldbus devices.
ten new runs of 230 meters (28 meters from the
device to the terminal panel plus 185 meters to the
equipment room plus 17 meters to the DCS) would
have been required. Savings in installation costs are
summarized in the following table.
31
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Features Summary
6.0 FEATURES SUMMARY (Figure 51). The I/O Subsystem Interface shown in
the figure allows other networks such as DeviceNet®
FOUNDATION fieldbus technology is already changing and Profibus®
the way systems perform control and will have an to be mapped into standard FOUNDATION fieldbus
even greater impact on system architecture, interop- function blocks. The I/O Subsystem Interface can
erability and openness than the H1 technology. be connected to the 31.25 kbit/s fieldbus or HSE.
FOUNDATION fieldbus tightly integrates system Since all of the 31.25 kbit/s FOUNDATION fieldbus
components, making field instruments an integral messages are communicated on the HSE using
part of the system just like the controls (i.e., field standard Ethernet protocols (e.g. TCP/IP, SNTP,
instruments and “system” are not two separate SNMP, etc.), commercial off-the-shelf HSE
islands). The operator workstations and interfaces equipment such as Switches and Routers are
are referred to as the “host” of the system. used to create larger networks (Figure 52). Of
Whereas, FOUNDATION H1 fieldbus technology is course all or part of the HSE network can be
used at the field device level making such devices made redundant to achieve the level fault
as transmitters and positioners interoperable, the tolerance needed by the application.
FOUNDATION HSE fieldbus technology is used at a
higher level in the system hierarchy, where host In the control system architecture H1 fieldbus is
devices and subsystems are networked. The capa- used at the field-level to connect transmitters and
bilities of HSE go far beyond that of traditional positioners etc. HSE is used at a higher level between
remote-I/O and control-level networks. linking devices and the host workstations (i.e.,
HSE will not replace H1, but the two complement
A Linking Device is used to interconnect 31.25 each other and serve enterprise needs at different
kbit/s fieldbuses and make them accessible to an levels of the plant hierarchy).
HSE backbone running at 100 Mbit/s or 1Gbit/s
Automation Automation
and and
Display Devices Display Systems
Figure 51 Figure 52
32
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Features Summary
H1 HSE
Speed 31.25 kbit/s 100 Mbit/s
Distance (per segment) 1900 m 100 m
Two-wire Yes No
Multidrop Yes No
Bus power Yes No
Intrinsically safe Yes No
Redundancy No Yes
Deterministic Yes Yes
33
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Features Summary
Standard Function Blocks Running in Field Devices Distributed Control on a COTS 100 Megabit per
Second Backbone
Single-loop Integrity – Control in Field – Increased Same Function Blocks and Device Description
Loop Performance Technology on H1
Reduces Traffic/Load on the Central Control System Function Block Synchronization on the Backbone
More Information for Operators – Including Signal System Time Synchronization – Master Clock
Status (e.g., GPS) to HSE to H1
Increases Measurement Accuracy New Flexible Function Blocks for
– Reduces A/D Conversions Hybrid/Batch/PLC/Remote I/O Applications
– Supports All Digital Sensor Integration
Fault Tolerant – Supports Multiple Link Masters and Supports High Speed Data Generators/Users
Time Masters (e.g., Analyzers, Controllers)
Reduces Wiring, Cabinets, Power Supplies, and Uses Standard Internet DHCP – Address Lease
Equipment Room Size Reuse Reduces Startup Time
Increases Uptime Due to Better Remote Diagnostics Short Messages Can Be Packed to Reduce
and Less Equipment Interrupts on Receiving CPUs
Provides Redundant Network Interface and
Redundant Devices.
34
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Features Summary
FOUNDATION
fieldbus
Communication H1/HSE
Network
35
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
Field Test
References
23
36
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.
References
10.0 TERMINOLOGY
Network: (Fieldbus) All of the media, connectors, and
associated communication elements by which a given
set of communicating devices are interconnected. ISA
S50 (IEC 61158-2:2000 (ed. 2.0), fieldbus standard for
use in industrial control systems — Part 2: Physical
Layer specification and service definition)
37
© 1996 (Rev.1998, 2003) Fieldbus Foundation, Austin, Texas. All rights reserved.