Fieldbus: relationship with OSI Model

Applied Data Communication

Lecture 21

Fieldbus technologies

Kristjan Sillmann
reaalajassteemide ppetool
TT automaatikainstituut
kristjan.sillmann@ttu.ee 1 2
Src: Fieldbus book a tutorial

Fieldbus: relationship with OSI Model Fieldbus: Protocol Data Unit

Fieldbus is essentially a local area network. Therefore much of layers
3 through 6 are not required. Those elements that are needed, were
compressed into what is called the Fieldbus Access Sublayer.
A data unit exchanged between the same layers is called Protocol
Data Unit (PDU). A PDU may contain an optional Service Data
Unit (SDU), which is a PDU of the next higher layer.
A communication layer exchanges other PDUs without SDU to
perform its functionality.

3 4
Src: THE FOUNDATION fieldbus PRIMER
 Fieldbus: Communication through VCR Fieldbus: Communication through VCR
Messages are exchanged between applications sitting on the PCIs are appended and removed when a message goes through
fieldbus. When a message is transferred, it goes down VCRs to allow layers, to perform their specific functionality
through a channel called Virtual Communication A fieldbus device has many VCRs so that it can communicate
Relationship(VCR), to add Protocol Control Information with various devices or applications at the same time. It is
(PCI) before it goes possible because the VCR guarantees the message goes to
to the wire. the correct partner without risks of losing information.
A VCR is identified by an application with device-local
At the destination, it identifier called index specified in Application Layer.
goes up through the It is also identified from other devices with DL-address
partner VCR to the specified in Data Link Layer.
receiving application.

5 6

Fieldbus: Communication through VCR Fieldbus physical standards: Profibus example

It is expected a network manager configures VCRs correctly Profibus DP Profibus PA
(Decentralized Periphery / High Speed I/O) (Process Automation / Hazardous Area)
according to the models communicating with each other.
This gives the correct information of the index and DL
address as well as other operating information to VCRs
through Network Management.
Once configured, the FAS layer provides the communication
facility according to these models.

7 8
Src: Profibus Expert talk
 Profibus standards comparison: Profibus PA standard( IEC 1158-2 ):
Character Format rules for Safety

9 10

Fieldbus: user layer Fieldbus: devices architecture

The customary ability in the analog world of being able to replace The entire functionality represented by the
a device from one manufacturer with a similar device from three segments; physical layer,
another manufacturer without loss of functionality, and communication stack, and function block
without requiring special engineering, was an expectation of application, must reside in every active
Fieldbus. device on a Fieldbus network.
So specifying a complete, well designed control application, the
so-called user layer, held equal priority with specifying the In addition, in field devices, the tightly
communication scheme. specified function block application must
The user layer, that is not defined by OSI, is defined in Fieldbus as interface with the unique technology of
the Function Block Application. the device. This is achieved through
transducer blocks.

11 12
 Fieldbus Devices: Control Valve
The electrical output of the CPU is passed through a D/A converter
and an electric to pneumatic converter (E/P), which results in a
pressure signal that modulates the actuator.
The actuator position is fed back through a mechanical to electric
transducer (M/E) and an A/D converter , to get actual valve
position back to the processor.
13
Src: How to Develop Your First FOUNDATION Fieldbus Device
Fieldbus Devices: Control Valve
The AO block is defined in detail by the Function Block
Specifications. The block communicates with the TB through a
numbered channel.
The AO block has 30 standard (mandatory) parameters that provide it
with substantial capability:
It provides high and low limits on the input signal, and limits on
the increasing and decreasing rates of change.
There is a fault-state mechanism for determining the control action
to be taken in the event of a failure, and a readback parameter that
can be used by an upstream control block to avoid wind-up during
limit conditions.
The AO block on this valve contains a simulate parameter that
allows alarms and failure procedures to be tested while the devices
are connected and operating, but not during operation of the
process.
15
Fieldbus Devices: Control Valve
The software diagram illustrates four major components. The
positioner servo performs the servo calculation for the actuator.
The servo SW must communicate with the D/A and A/D. The SW
and HW for this function will be unique to the manufacturer and at
this point, has nothing to do with fieldbus.
The transducer block (TB), is the interface between the positioner and
fieldbus. Most manufacturer specific features of the device will be
done in the TB, including calibration and diagnostics. It is likely
that the designer will want the TB to have access to the actual
valve position. Also, any potential device failures that can be
sensed should be communicated to the TB for use in diagnostics
and fault detection.
Although the TB is unique to a specific manufacturers design, the
data communicated to the Analog Output (AO) function block,
must conform to the
Fieldbus specifications.
14
Fieldbus Devices: Transmitter
There is similar architecture for a transmitter. In this case the TB
interfaces with the signal conditioning circuit of the sensing
device, which is manufacturer specific. Then, via a numbered
channel, connects to an Analog Input (AI) function block.
The AI block has 36 standard parameters. It provides a scaling
function, filtering, and process and block alarms.
16
 Fieldbus Data Link Layer:
LAS and Message Priorities
Only one device on a link is allowed to use the medium at a
time. Link Active Scheduler (LAS) has the role to control the
medium access.
The LAS possesses the token and gives it to another device to
allow it to send messages. The token is then returned to the
LAS for further medium access control.
Since application messages have various levels of urgency,
fieldbus DLL supports a mechanism to transmit messages
according to their urgency.
Fieldbus Data Link Layer:
Scheduled communication
The LAS is responsible for scheduled communication, which is
necessary to link Function Blocks. Function Blocks are
distributed applications operating in a synchronized manner.
A Function Block output parameter is a Publisher of data and
other Function Blocks that receive this data are called
Subscribers.
The LAS controls periodic data transfer from a Publisher to
Subscribers using the Network Schedule.

17 18

Fieldbus Data Link Layer: Fieldbus Data Link Layer:

Scheduled communication Scheduled communication
When the time of scheduled communication comes, LAS sends
Compel Data (CD) PDU to the Publisher. Publisher is
expected to transmit Data Transfer (DT) PDU stored in the
buffer immediately.
When Subscribers receive CD to the Publisher, they presume the
next data transfer comes from the Publisher. Received data is
stored in the buffer of Subscribers.
A CD PDU is a token for a Publisher and the LAS interprets the
publishing DT PDU as the returned token.
Freshness information is appended to the data, so that the
Subscribers know whether data has been updated since the
last publish.

19 20
 Fieldbus Data Link Layer: Fieldbus Data Link Layer:
Unscheduled communication Link maintenance
Other communications take place in an asynchronous way. The The third role of LAS is to maintain the link. The LAS gives the
LAS is responsible to give all nodes on a link a chance to send token to all devices detected by the LAS. When a new device is
messages. added to the network, it must be recognized by the LAS and
The LAS gives a token by sending Pass Token (PT) PDU to a node. entered to the token rotation list called Live List.
A PT contains priority and The LAS sends a Probe Node (PN) PDU to node addresses where a
time interval information. device was not found before. A new device waits until it
A device must return the receives PN and returns Probe Response (PR) PDU to the LAS.
token within the time Then the LAS adds this device to the Live List.
interval given in the PT. This probing is repeated in a given interval. When a device is
This is necessary to removed from the link, it does not respond to PT any more. The
finish the unscheduled LAS detects this and deletes the device from the Live List.
communication before The LAS also broadcasts Time Distribution(TD) in a predefined
the next scheduled interval, to sync the network time, which is used for the
communication. scheduled communications on the fieldbus and the scheduled
function block executions in the User Application.
21 22

Fieldbus Data Link Layer: Fieldbus Data Link Layer:

LAS algorihtm LAS algorihtm
The Fieldbus tokens do not grant The LAS also broadcasts a limited set of messages, such as (TD),
unlimited communication which do not authorize the receiver to respond.
rights. The LAS uses the CD, TD, and PN to cause specific actions to
Tokens delegate very specific occur under control of the LAS itself. In sending a PT to a
instructions of either what is to device, it is giving the device an opportunity to communicate
be communicated, or how long messages under control of the device itself. With the PT
communication may take place. comes a value called the maximum hold time.
In either case, the right of a device So, although the LAS delegates control of what the device may
to use the network is defined communicate, it retains control of how long the device can
and limited. use the bus. The LAS thus maintains determinism, and can
The LAS sends tokens with one of assure that the precise schedule required for control data is
three basic instructions which maintained.
are: Compel Data (CD), Probe Upon receiving the PT, a device may use as much or as little of
Node (PN) and Pass Token its maximum hold time as it needs, but not more.
(PT).
23 24
 Fieldbus Data Link Layer:
LAS algorihtm
If the device needs more time, it will return the PT at the end of
the maximum hold time with a request for more time.
Devices use the bus time granted by a PT to report alarms and
other Event Notifications, exchange Read/Write messages
with HMIs, communicate diagnostic information and answer
requests from operators or other devices.
While the PT grants the device control of what to communicate,
the LAS can influence what the device chooses by providing
a priority within the PT. For example, to indicate that alarms
are to be reported before answering an operators request for
the device model number.
25
Fieldbus Data Link Layer:
LAS scheduling example
Assume that we need to build schedules for the control loop
described in Figure. The schedules contain the start time offset
from the beginning of the absolute link schedule start time.
The absolute link schedule start time is known by all devices on
the fieldbus.
27
Src: Fieldbus Technical Overview - Understanding FOUNDATION fieldbus technology
Fieldbus Data Link Layer:
LAS algorihtm
The LAS controls the message transfer by updating the priority.
When the token is given and returned from all devices in a
short time interval, the LAS gives more time to the nodes by
lowering the priority.
When the token does not go to all devices within a target token
rotation time network parameter, the LAS increases the
priority so that the token is given to all devices in a desired time
interval.
Note that the token is given to the node instead of a particular VCR
(Virtual Communication Relationship). Therefore the device is
responsible to allow all VCRs in the device to send messages.
26
Fieldbus Data Link Layer:
LAS scheduling example
28
 Fieldbus Data Link Layer:
LAS scheduling example
A macrocycle is a single iteration of a schedule within a device.
Figure shows the relationships between the absolute link
schedule start time, LAS macrocycle, device macrocycles, and
the start time offsets.
In Figure, System Management in the transmitter will cause the AI
function block to execute at offset 0.
At offset 20, the Link Active Scheduler (LAS) will issue a Compel
Data (CD) to the AI function block buffer in the transmitter and
data in the buffer will be published on the fieldbus.
At offset 30, System Management in the valve will cause the PID
function block to execute followed by execution of the AO
function block at offset 50.
29
Fieldbus Access Sublayer (FAS):
Three communication models (VCR service types)
Since fieldbus does not have layers (4 to 6)
between DLL and FMS, FAS directly maps
FMS requests to DLL services.
FAS uses the scheduled and unscheduled features
of the DLL to provide a service for the (FMS).
FAS provides three communication models
(a.k.a. Virtual Communication Relationship
service types) for applications:
31
Fieldbus Data Link Layer:
LAS scheduling example
The pattern exactly repeats itself assuring the integrity of the
control loop dynamics.
Note that during the function block execution, the LAS is sending
the Pass Token message to all devices so that they can transmit
their unscheduled messages such as alarm notifications or
operator setpoint changes.
For this example, the only time that the fieldbus can not be used for
unscheduled messages is from offset 20 to offset 30 when the
AI function block data is being published on the fieldbus.
30
Fieldbus communication models:
Publisher/subscriber
The model used in transmitting data for control purposes is
called Publisher/Subscriber.
A VCR has a queue (fast-in, fast-out memory) or a buffer
(memory to store data) to save messages. In this model, the
data to be sent is buffered, meaning the most current data
will be transmitted and any older data is overwritten.
Data required for control must be transmitted at precise intervals
and so transmission is scheduled/cyclic.
32
 Fieldbus communication models:
Publisher/subscriber
There is no requirement (or opportunity) for the receiver to
confirm that data is correctly received. If a data point is
missed, the value is immediately stale and the system will
need to rely on the previous value until a future value is
transmitted. The data is broadcast on the network from a
single source to any device needing the data, one-to-many.
Usually there is no explicit addressing of the subscribers.
Buffer with most
recent data value
Fieldbus communication models:
Publisher/subscriber
Publisher-Subscriber model is designed to link Function Blocks.
When a publishing Function Block runs, its output data is
stored in the buffer of the Publisher VCR. Then the LAS
sends CD to the VCR to force it to transfer the data in DT.
Subscriber VCRs receive this PDU and gives the data to the
subscribing Function Blocks.
A typical example is a linkage from output of an Analog Input
(Al) block to process value input of PID control block.
Subscribers are able to know whether data has been updated
since the last publish. This mechanism is important because
Data Link Layer transfers data as scheduled regardless if the
publishing Function Block updates the data in the buffer.

33 34

Fieldbus communication models: Fieldbus communication models:

Publisher/subscriber Publisher/subscriber
Most industrial producer/consumer (or publisher/subscriber)
protocols operating over Ethernet, such as EtherNet/IP and
Foundation Fieldbus HSE, are IP multicast-based.
The first advantage of IP multicasting is network efficiency; by
not repeating the data transmission to the multiple
destinations, a significant reduction in network load can
occur.
The second advantage is that the sending host need not be
concerned with knowing every IP address of every
destination host listening for the broadcast information.
The third, and perhaps most important for industrial control
purposes, is that a single multicast message offers far better
capabilities for time synchronization between multiple
35
control devices than multiple unicast messages. 36
 Fieldbus communication models:
Source/Sink
The second communication category is called a Source/Sink
(a.k.a. Report Distribution Model). It is designed to
broadcast the event messages.
A VCR has a queue (fast-in, fast-out memory) or a buffer
(memory to store data) to save messages. In this model, the
data to be sent is queued rather than buffered. This means
that if a series of values or messages are created, none are
discarded. They will each be sent in turn as time is available.
It is important for such messages to be transmitted with urgency.
Fieldbus communication models:
Source/Sink
It is also important that the message is correctly received. This is
assured by requiring that the appropriate recipient confirm
receipt by sending a return confirmation message. Otherwise,
the original transmission will be periodically re-transmitted.
Reports are initiated by the sender and are transmitted as a one-
to-many message similarly to Publisher/Subscriber.
Queue of
UnAcknowledged
Event Notifications

This is best accomplished by sending them at the earliest

opportunity after the occurrence of the underlying event,
rather than on a scheduled/cyclic basis.

37 38

Fieldbus communication models: Fieldbus communication models:

Source/Sink Source/Sink
When a device with an event or a trend report receives a Pass
Token (PT) from the LAS, it sends its message to a group
address defined for its VCR. Sink VCRs that are configured to
listen on that VCR (same group address) will receive the
message from a Source.
Fieldbus devices use this model for two specific purposes. One is to
report alarms or events detected in the Source, and the other is
to transmit trend of Source Function Block. Alarms are
acknowledged through a Client-Server VCR.
It is desirable for an alarm logger to receive alarms from devices
with one VCR. A Sink can receive messages from many
Sources if the Sources are configured to send messages to the
same global address.

39 40
 Fieldbus communication models:
Client/Server
The third classification of communications is illustrated by an
operator at a host device changing the value of a parameter in
a field device, such as a set point or tuning parameter.
This model is called Client/Server. The values or messages are
queued, so each will be transmitted in its turn. They are
transmitted in the unscheduled time during a macrocycle.
Re-transmission by the sending device will be repeated until a
confirmation message is received from the recipient.
This exchange is between one
specific device and another,
thus it is a one-to-one
two-way Communication
relationship.
41
Fieldbus communication models:
Client/Server
The Client-Server model is universal and used in many
communication technologies. An application called Client
requests another application called "Server" to do a specific
action through FMS. When the Server finishes the requested
action, its result is transferred to the Client.
A typical example is a human-machine interface (Client) to read
data of a Function Block (Server). The Client sends a Read
request to the Server and then Server sends back the data to the
Client. A Client may want to issue many requests at a time.
Client-Server VCR has a queue to store those requests and
sends requests one by one when the node has a token.
A flow-control mechanism is available to manage error recovery
and Servers processing power.
42

Fieldbus communication models: Fieldbus communication models: Summary

Client/Server

43 44
 OPC - OLE for Process Control
Client/ Based on the COM (Component Object Model) architecture,
Server OPC was created as a vendor-independent standard, aimed at
(peer-to-peer) the definition of data exchange between Windows-based
applications, as well applications and vendor-specific
hardware in the realm of automation. It is maintained by an
independent association - the OPC Foundation.
Source
VS OPC defines logical objects and methods tailored to the special
needs of the process industry based on COM technology.
Source/Sink Several OPC-Clients are able to access one OPC-Server in
(report parallel. In the area of fieldbus communication, OPC is the
distribution) most often installed interface between a fieldbus controller
and PC based applications.
OPC uses the mechanisms provided by COM to implement
Sink
synchronous services (comparable to client/server) and
45
asynchronous services (comparable to publisher/subscriber). 46