Escolar Documentos
Profissional Documentos
Cultura Documentos
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Copyright Fisher-Rosemount Systems 1998. All Rights Reserved. This document contains excerpts of copyrighted
materials that are the property of the Fieldbus Foundation and are reproduced with its express written permission.
Fisher-Rosemount, Managing the Process Better, PlantWeb, and RS3 are marks of one of the Fisher-Rosemount family
of companies. FOUNDATION is a mark of the Fieldbus Foundation. All other marks are the property of their respective
owners. The contents of this publication are presented for informational purposes only, and while every effort has been
made to ensure their accuracy, they are not to be construed as warranties or guarantees, express or implied, regarding
the products or services described herein or their use or applicability. All sales are governed by our terms and
conditions, which are available on request. We reserve the right to modify or improve the designs or specifications of our
products at any time without notice.
FOUNDATION™ fieldbus—the
technology of tomorrow—
Plant-Wide
available today.
Network
FOUNDATION fieldbus technology is
the basis of the next generation of
process control. This overview Process Automation System
explains fieldbus technology so you and
can take the next step of LANs
integrating fieldbus into your
control strategy with confidence.
PID
I/O & Control
AI Subsystem
I/O & Control AO with
Subsystem
Fieldbus Interface
I.S.
I.S. I.S. I.S. Fieldbus
PID
AO
AI
Figure 2. With fieldbus, I.S. requires only one barrier for multiple devices, and control is managed within the devices.
2
FOUNDATION fieldbus certification. OSI MODEL* FIELDBUS MODEL
That means that you have
increased flexibility in supplier USER USER
APPLICATION APPLICATION
selection with the assurance that
all devices will work together, FIELDBUS MESSAGE
regardless of manufacturer. APPLICATION LAYER 7 SPECIFICATION
FIELDBUS ACCESS
FOUNDATION Fieldbus PRESENTATION LAYER 6
SUBLAYER
Technology COMMUNICATION
SESSION LAYER 5 "STACK"
FOUNDATION fieldbus technology
TRANSPORT LAYER 4
consists of three parts:
NETWORK LAYER 3
■ Physical Layer
■ Communication “Stack” DATA LINK LAYER 2 DATA LINK LAYER
The Open Systems Interconnect *The user application is not defined by the OSI Model.
(OSI) layered communication
model is used to model these
components. (See Figure 3.) Figure 3. The Open Systems Interconnect (OSI) layered communications model.
3
Physical Layer Conversion tasks include adding the middle of a bit time as a logical
and removing preambles, start “0” and a negative transition as a
The Physical Layer is defined by delimiters, and end delimiters. logical “1”. (See Figure 5.)
standards from the International
Fieldbus signals are encoded using Special characters are defined for
Electrotechnical Commission
the Manchester Biphase-L the preamble, start delimiter, and
(IEC) and The International
technique. The signal is called end delimiter. (See Figure 6.)
Society of Measurement and
“synchronous serial” because the
Control (ISA). The preamble is used by the
clock information is embedded in
the serial data stream. Data is receiver to synchronize its internal
The Physical Layer receives
combined with the clock signal to clock with the incoming fieldbus
messages from the communication
create the fieldbus signal. The signal.
stack and converts the messages
into physical signals on the receiver of the fieldbus signal
Special N+ and N- codes are in the
fieldbus transmission medium and interprets a positive transition in
start delimiter and end delimiter.
vice-versa. Note that the N+ and N- signals do
not transition in the middle of a bit
time. The receiver uses the start
1 Bit Time
delimiter to find the beginning of a
fieldbus message. After it finds
CLOCK the start delimiter, the receiver
accepts data until the end
delimiter is received.
The H1 Fieldbus
DATA 1
0 The H1 fieldbus can be used for
control applications such as
temperature, level and flow
0 1 1 0 0
+ control.
MANCHESTER
BIPHASE-L Devices can be powered directly
ENCODING from the fieldbus and operate on
-
wiring that was previously used for
4-20 mA devices.
Figure 5. Fieldbus signals are encoded using the Manchester Biphase-L technique.
The H1 fieldbus can also support
intrinsically safe (I.S.) fieldbuses
with bus powered devices. An I.S.
1
CLOCK barrier is placed between the
0
power supply in the safe area and
+ 1 0 1 0 1 0 1 0 the I.S. device in the hazardous
PREAMBLE 0 area. (See Figure 2.)
-
H1 Fieldbus Signaling
START + 1 N+ N- 1 0 N- N+ 0
The transmitting device delivers
DELIMITER 0 ±10 mA at 31.25 kbit/s into a 50
-
ohm equivalent load terminator to
+ 1 N+ N- N+ N- 1 0 1 create a 1.0 volt peak-to-peak
END
0 voltage modulated on top of the
DELIMITER -
direct current (DC) supply
voltage.
Figure 6. Special characters are defined for the preamble, start delimiter, and end
delimiter.
4
The DC supply voltage can range
from 9 to 32 VDC (See Figure 7.)
However, for I.S. applications, the Fieldbus Device
+
Device Current
allowed power supply voltage Fieldbus Signal
depends on the barrier rating. 15 to 20 mA p-p
0.75 to 1.0 V p-p
H1 Fieldbus Wiring
Voltage
0
Receiving Transmitting Power 9 to 32 Volts
The H1 fieldbus allows stubs or
“spurs” as shown in Figure 8. The 100 Ohm 100 Ohm
length of the fieldbus is Time
Power
determined by the communication Supply
C C
rate, cable type, wire size, bus
Terminator
power option, and I.S. option. Fieldbus Network C is sized to pass 31.25 kbit/s.
NOTE: As an option, one of the terminators may be center-tapped and grounded
The main run cannot exceed a to prevent voltage buildup on the fieldbus.
total length of 1900 m (6,232 ft)
with shielded twisted pair cable.
The cable length is determined by
adding together the length of the
trunk cable and all of the spur Figure 7. Signaling waveforms for the H1 Fieldbus.
lengths. As shown in Figure 8,
terminators are located at each
Control Room
end of the main trunk cable. Equipment
5
Fieldbus Device Fieldbus Signal
Device Current +
Voltage
5.5 to 9.0 V p-p
73 to120 mA p-p
Time
0
Receiving Transmitting
Control Room
Equipment
150 Ohm 150 Ohm NOTE
Terminator
6
Communications Stack
H2 Fieldbus
Data Link Layer
The DLL is a subset of the Figure 12. Bridges are used to interconnect individual fieldbuses to create larger
networks.
emerging IEC/ISA DLL standard.
Schedule LAS = Link Active Scheduler
Device Types CD = Compel Data
a
b CD (a) Fieldbus
Three types of devices are defined LAS
c
in the DLL specification:
Message
8
Fieldbus Access Sublayer (FAS) may send a request message to
another device on the fieldbus.
The FAS uses the scheduled and The requester is called the ■ Publisher/Subscriber VCR Type
unscheduled features of the Data “Client”, and the device that The Publisher/Subscriber VCR
Link Layer to provide a service for received the request is called Type is used for buffered, one-
the Fieldbus Message Specification the “Server.” The Server sends to-many communications.
(FMS). The types of FAS services the response when it receives a
are described by Virtual PT from the LAS. Buffered means that only the
Communication Relationships latest version of the data is
(VCR). The Client/Server VCR Type is maintained within the network.
used for operator initiated New data completely overwrites
The VCR is like the speed dial
requests such as setpoint previous data.
feature on your memory
telephone. There are many digits changes, tuning parameter
access and change, alarm When a device receives the
to dial for an international call—an
acknowledge, and device upload Compel Data (CD), the device
international access code, country
and download. will “Publish” or broadcast its
code, city code, exchange code,
message to all devices on the
and the specific telephone
■ Report Distribution VCR Type fieldbus. Devices that wish to
number.
The Report Distribution VCR receive the published message
This information only needs to be Type is used for queued, are called “Subscribers.”
entered once and then a “speed unscheduled, or user-initiated
dial number” is assigned. After one-to-many communications. The CD may be scheduled in
setup, only the speed dial number the LAS, or it may be sent by
needs to be entered for the dialing When a device with an event or Subscribers on an unscheduled
to occur. a trend report receives a Pass basis. An attribute of the VCR
Token (PT) from the LAS, it indicates which method is used.
In a similar fashion, after sends its message to a “group
configuration, only the VCR address” defined for its VCR. The Publisher/Subscriber VCR
number is needed to communicate Devices that are configured to Type is used by the field devices
with another fieldbus device. listen on that VCR will receive for cyclic, scheduled publishing
the report. of User Application function
Just as there are different types of
block input and outputs such as
telephone calls, such as person to
The Report Distribution VCR process variable (PV) and
person, collect, or conference
Type is typically used by primary output (OUT) on the
calls, there are different types of
fieldbus devices to send alarm
VCRs:
notifications to the operator
■ Client/Server VCR Type consoles.
The Client/Server VCR Type is
used for queued, unscheduled, Table 3. Summary of VCR Types
user initiated, and one to one
communication between Client/Server Report Distribution Publisher/Subscriber
devices on the fieldbus. VCR Type VCR Type VCR Type
Used for Used for Used for
Queued means that messages Operator Messages Event Notification and Publishing Data
are sent and received in the Trend Reports
order submitted for Setpoint changes. Send process alarms Send transmitter PV
transmission, according to their Mode changes. to operator consoles. to PID control block
priority, without overwriting Tuning changes. and operator console.
previous messages. Upload/download. Send trend reports
Alarm management. to data historians.
When a device receives a Pass Access display views.
Token (PT) from the LAS, it Remote diagnostics.
9
fieldbus. Communication
Services
Fieldbus Fieldbus
Fieldbus Message Specification Device Device
(FMS)
USER USER
APPLICATION APPLICATION
Fieldbus Message Specification
(FMS) services allow user
FIELDBUS MESSAGE FIELDBUS MESSAGE
applications to send messages to SPECIFICATION SPECIFICATION
each other across the fieldbus
FIELDBUS ACCESS FIELDBUS ACCESS
using a standard set of message SUBLAYER SUBLAYER
formats.
DATA LINK LAYER DATA LINK LAYER
FMS describes the communication
services, message formats, and PHYSICAL LAYER PHYSICAL LAYER
protocol behavior needed to build
messages for the User Application.
(See Figure 16.) Figure 16. FMS services allow user applications to exchange messages over the
fieldbus.
Data that is communicated over Object Dictionary
the fieldbus is described by an
Index 0
“object description.” Object
Index 1 Object Description 1
descriptions are collected together
Index 2 Object Description 2
in a structure called an “object
Index n Object Description n
dictionary” (OD). (See Figure
17.)
Figure 17. The object dictionary contains a collection of object descriptions.
The object description is identified
Fieldbus Device
by its index in the OD. Index 0,
called the object dictionary Network and System Function
header, provides a description of Management Block
Application Application
the dictionary itself and defines
Network and System User
the first index for the object Management Application
descriptions of the User VFD VFD
Application. The User Application
NMIB Object SMIB Object NMIB Object
object descriptions can start at any Descriptions Descriptions Descriptions
index above 255.
NMIB Object SMIB Object NMIB Object
Index 255 and below define Data Data Data
descriptions. FAS
PHY
A “Virtual Field Device” is used to
remotely view local device data
FIELDBUS
described in the object dictionary.
A typical device will have at least Figure 18. A typical device will have at least two Virtual Field Devices (VFDs).
two VFDs. (See Figure 18.)
provides for the configuration of used for System Management.
Network Management is part of the communication stack. The This VFD provides access to the
the Network and System Virtual Field Device (VFD) used Network Management Information
Management Application. It for Network Management is also Base (NMIB) and to the System
10
Management Information Base ● GetOD
(SMIB). NMIB data includes Read an object dictionary (OD) The following FMS services
Virtual Communication ● InitiatePutOD
allow the User Application to
Start an OD Load
Relationships (VCR), dynamic ● PutOD upload and download a Domain
variables, statistics, and Link Load an OD into a device in a remote device.
Active Schedule (LAS) schedules ● TerminatePutOD ● RequestDomainUpload
(if the device is a Link Master). Stop an OD Load Request Upload
SMIB data includes device tag and ● InitiateUploadSequence
■ Variable Access Services Open Upload
address information, and schedules
The following FMS services ● UploadSegment
for function block execution.
allow the user application to Read data from device
System Management is described access and change variables ● TerminateUploadSequence
further in the User Application associated with an object Stop Upload
Section. description. ● RequestDomainDownload
Read
●
Request Download
Communication Services ● InitiateDownloadSequence
Read a variable
● Write Open Download
FMS communication services Write a variable ● DownloadSegment
provide a standardized way for ● InformationReport Send data to device
user applications such as function Send Data* ● TerminateDownloadSequence
blocks to communicate over the ● DefineVariableList
Stop Download
fieldbus. Specific FMS Define a Variable List
● DeleteVariableList
communication services are ■ Program Invocation Services
Delete a Variable List
defined for each object type. * Can use Publisher/Subscriber or The “Program Invocation” (PI)
Report Distribution VCR Types. allows the execution of a
All of the FMS services can use
program in one device to be
only the Client Server VCR Type ■ Event Services controlled remotely.
except as noted. The following FMS services
allow the user application to A device could download a
Communications Services include
report events and manage event program into a Domain of
the following:
processing. another device using the
■ Context Management Services ● EventNotification
download service and then
Report an event*
The following FMS services are remotely operate the program
● AcknowledgeEventNotification
used to establish and release Acknowledge an event by issuing PI service requests.
Virtual Communication ● AlterEventConditionMonitoring
Relationships (VCR) with, and Disable/Enable event* The state diagram for the PI is
determine the status of, a VFD. * Can use Report Distribution VCR shown as an example of FMS
● Initiate Type.
protocol in Figure 19.
Establish Communications ● CreateProgramInvocation
● Abort ■ Upload/Download Services Create a program object
Release communications It is often necessary to remotely ● DeleteProgramInvocation
● Reject upload or download data and Delete a program object
Reject improper service programs over the fieldbus, ● Start
● Status especially for more complex Start a program
Read a device status devices such as programmable ● Stop
● UnsolicitedStatus logic controllers. Stop a program
Send unsolicited status ● Resume
● Identify Resume program execution
Read vendor, type and version To allow uploads and downloads
using the FMS service, a ● Reset
■ Object Dictionary Services Reset the program
The following FMS services “Domain” is used. A Domain
● Kill
allow the User Application to represents a memory space in a
access and change the object device.
descriptions (OD) in a VFD.
11
Committee (CCITT) in the early
DELETE 1980s, as a part of the CCITT mail
Non-
existent standardization activities.
CREATE Unrunnable
See Figure 20 for a partial example
RESET
Idle
of ASN.1 definition for the FMS
START KILL read service.
The Access-specification is a
USER CHOICE of using either an index
APPLICATION or a name to access a variable.
FMS The sub-index is OPTIONAL. It is
FAS
used only to select an individual
element of an array or record
DLL
variable.
PHY
The numbers in the brackets are
the actual encoding numbers that
Figure 19. Behavior Rules for the Program Invocation Object.
are used to identify the fields in an
encoded message.
Protocol Behavior
Read_Request::=SEQUENCE {
Access-specification CHOICE { Certain types of objects have
index [0] IMPLICIT Index, special behavioral rules that are
variable name [1] IMPLICIT Name,
variable-list-name [2] IMPLICIT Name, described by the FMS
},
sub-index [3] IMPLICIT Subindex OPTIONAL
specification. For example, the
} simplified behavior of a Program
Invocation object is shown in
Figure 19.
USER
APPLICATION A remote device can control the
state of the program in another
FMS
device on the fieldbus. For
FAS example, the remote device would
DLL
use the Create Program Invocation
FMS service to change the
PHY
program state from Non-existent
to Idle.
12
User Application—Blocks
USER USER
The Fieldbus Foundation has APPLICATION APPLICATION
defined a standard User
Application based on “Blocks.” FIELDBUS MESSAGE
SPECIFICATION
Blocks are representations of
FIELDBUS ACCESS
different types of application SUBLAYER
functions. (See Figure 21.)
COMMUNICATION
"STACK"
The types of blocks used in a User
Application are described in
Figure 22.
13
and across the fieldbus network.
● VIEW_1—Operation
Dynamic—information
Data Trend Alarms AI PID, AO required by a plant operator to
Static run the process.
Fieldbus
AI
● VIEW_2—Operation Static—
Diagnostics Information that may need to
Display Sets
Detail Display be read once and then
View_1 View_2 View_3 View_4
Operation Operation All Dynamic Other Static displayed along with the
XYZ Block Dynamic Static dynamic data.
SP X X
PV X X ● VIEW_3—All Dynamic—
SP HI LIMIT X
CAS IN X
Information that is changing
GAIN X and may need to be referenced
in a detailed display.
Figure 24. Example of how common Function Block variables map into the views. ● VIEW_4—Other Static—
Configuration and maintenance
information.
Transducer Blocks each input or output function
block.
Transducer Blocks decouple
Function Blocks from the local The following additional objects
input/output functions required to are defined in the User
read sensors and command output Application:
hardware. They contain
information such as calibration Link Objects define the links
date and sensor type. There is between Function Block inputs
usually one transducer block for and outputs internal to the device
14
Fieldbus Device Definition
Resource Block
The function of a fieldbus device is
determined by the arrangement
Sensor Transducer
and interconnection of blocks (See 1
Function
Block 1 Block 1
Figure 25).
RESOURCE BLOCK
FUNCTION BLOCKS
TRANSDUCER BLOCKS
LINK OBJECTS
ALERT OBJECTS
TREND OBJECTS
VIEW OBJECTS
Figure 26. The Directory provides the starting indexes of all the other entries
used in the Function Block application.
15
Index
0 OD HEADER
User
Function Block Application
Application Virtual
301 DIRECTORY
Field Device
Resource Block 302 RESOURCE BLOCK
Transducer Function
Block 1 350
Block 1 LINK OBJECTS Stack
400 TREND OBJECTS
Links Physical
View Lists Layer
500 FUNCTION BLOCKS
Alerts 600 FUNCTION BLOCKS
16
System Management Table 4. Offset from Absolute Link Schedule Start Time
Figure 28. The start of individual macrocycles is defined as an offset from the
absolute link schedule start time.
17
For this example, the only time become active if the currently to the device that forces the
that the fieldbus can not be used active time publisher should fail. device to move to the new
for unscheduled messages is from network address.
Device Address Assignment
offset 20 to offset 30 when the AI
function block data is being Every fieldbus device must have a ■ The sequence is repeated for
published on the fieldbus. unique network address and all devices that enter the
physical device tag for the fieldbus network at a default address.
Application Clock Distribution
to operate properly.
The FOUNDATION Fieldbus supports Find Tag Service
an application clock distribution To avoid the need for address
switches on the instruments, For the convenience of host
function. The application clock is systems and portable
usually set to the local time of day assignment of network addresses
can be performed automatically by maintenance devices, System
or to Universal Coordinated Time. Management supports a service
System Management.
System Management has a time for finding devices or variables by
publisher that periodically sends The sequence for assigning a a tag search.
an application clock network address to a new device is
as follows: The “find tag query” message is
synchronization message to all broadcast to all fieldbus devices.
fieldbus devices. The data link Upon receipt of the message, each
■ A physical device tag is assigned
scheduling time is sampled and device searches its Virtual Field
to a new device via a
sent with the application clock Devices (VFD) for the requested
configuration device. This can
message so that the receiving tag and returns complete path
be done “off-line” at a bench or
devices can adjust their local information (if the tag is found)
“on-line” through special default
application time. Between including the network address,
network addresses on the
synchronization messages, VFD number, virtual
fieldbus.
application clock time is communication relationship
independently maintained in each (VCR) index, and object
■ Using default network
device based on its own internal dictionary (OD) index. Once the
addresses, System Management
clock. path is known, the host or
asks the device for its physical
Application clock synchronization device tag. System Management maintenance device can access
allows the devices to time stamp uses the physical device tag to the data for the tag.
data throughout the fieldbus look up the new network
network. If there are backup address in a configuration table.
application clock publishers on the System Management then sends
fieldbus, a backup publisher will a special “set address” message
18
Device Descriptions
Virtual Field Device
A critical characteristic required of
fieldbus devices is interoperability. Object Pointer to
Description Device Description of Data
To achieve interoperability, Device of Data
Description (DD) technology is
used in addition to standard
function block parameter and
behavior definitions.
Data
The DD provides an extended DD
description of each object in the
Virtual Field Device (VFD) as
shown in Figure 29.
19
DDs. Suppliers may also add
supplier specific features such as
calibration and diagnostic Standard Device Descriptions from
procedures to their devices. These the Fieldbus Foundation Number of digits
Plus Optional of precision.
features can also be described in Incremental Device Descriptions from Engineering Unit
the incremental DD. Suppliers Label
20
The third level is called The fourth level of the hierarchy is The test report identifies the
Transducer Block Parameters. At called Manufacturer Specific Universal, Function Block,
this level, parameters are defined Parameters. At this level, each Transducer Block, and
for the standard Transducer manufacturer is free to add Manufacturer Specific Parameters
Blocks. In some cases, the additional parameters to the in the device. An identifier called
Transducer Block specification Function Block Parameters and the manufacturer’s Identification is
may add parameters to the Transducer Block Parameters. used to correlate the device type
standard Resource Block. These new parameters will be and revision with its Device
included in the incremental DD Description and DD revision.
The Fieldbus Foundation has discussed earlier.
written the Device Descriptions for Any host using the Device
the first three layers of the Description Services (DDS)
Interoperability
hierarchy. These are the standard interpreter will be able to
Fieldbus Foundation DDs. Each manufacturer will provide interoperate with all parameters
the Fieldbus Foundation with an that have been defined in the
interoperability test report for device by reading the device’s DD.
each device.
21
System Configuration
TRANSMITTER VALVE
FIELDBUS DEVICE FIELDBUS DEVICE
Fieldbus system configuration
consists of two phases:
■ System Design
■ Device Configuration
AI OUT PID OUT
System Design
IN
The system design for fieldbus-
based systems is very similar to
today’s Distributed Control
Systems (DCS) design with the AO
following differences. IN
22
FOUNDATION fieldbus—get
ready, get set, go!
FOUNDATION fieldbus is ready to go. Prove to yourself and to your plant ■ enhanced reporting information
You can begin to experience the management the benefits of based upon increased
benefits of fieldbus immediately. fieldbus: information resident in the field
devices
It’s simple. Are you adding a new ■ reduced investment in I/O and
plant unit? Is there an area of the control equipment with the Ready to begin? Just call your
plant that has just not been cost ability to have multiple devices local Fisher-Rosemount Sales
effective to bring to your DCS? on a singe pair of wires Representative and you’ll start
That’s it. That’s the first fieldbus your journey into tomorrow—
installation for your plant. ■ lower engineering costs with today!
easy-to-configure control
Select your devices. Install a strategies—managed within the
DeltaV scalable control system. devices
You don’t have to have lots of
points, just a few to start. ■ preventative maintenance
capabilities that enable you to
reduce process variability
23