I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N

A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S

Chapter V
Specification for Profibus field networks
1.1. Introduction
PROFIBUS is a field protocol developed by Siemens, Bosch and Klockner-
Moeller to meet the demands of both discrete manufacturing and the European
standards EN50170 and EN50254. Profibus enables communications between
devices made by different manufacturers without requiring special interface
adjustments. Profibus can be used in high speed applications and composite data
exchange.
1.2. Description of protocol
It is also suitable for solving a variety of automation tasks both at the level of
field devices and systems of higher hierarchical level. Profibus is distinguished
by the technical specifications of serial field systems which allow for digital
programmable controllers of distributed intelligence to be connected into a
common network. In terms of topology Profibus is a multi-master system which
means that it allows in-line operation of several automated systems with their
distributed peripheries over a common trunk-line.
This communication technology comprises three main types of protocols: DP
FMS and PA (Fig. 5.1).
The PROFIBUS-FMS (Fieldbus Message Specification) has been used since
1990. It was designed for communication at higher hierarchical level and there-
fore is not suitable as communication medium at the level of field devices.
PROFIBUS-DP (Decentralized Periphery) (1992) is developed for data ex-
change between programmable logic controllers (PLC) and devices connected to
heterogeneous objects. It features data exchange rate of 12 Mbit/s. The method
of communication is either master/slave or peer access. At physical level the
transmission medium is a twisted pair. The maximum number of nodes (devices)
which could be included in a Profibus DP network is a hundred plus. Its typical
areas of application are process management and industrial automation.

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S

PROFIBUS-PA (Process Automation) (1997) is designed for data exchange
between systems of field level located in conventional or Ex-zone (zone of
enhanced security). This protocol meets the requirements of the IEC 61158-2
international standard.
It is designed to connect systems for management of controllers, sensors and
actuators.
Profibus PA is similar to FOUNDATION Fieldbus in terms of characteristics,
however, with Profibus PA the exchange rate is about 30 Kbit/s, the trunk-line
being of master/slave or peer access type and the maximum number of nodes is
over 250 per net.


Fig. 5.1.

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S


Fig. 5.2.
1.3. PROFIBUS-DP functioning
The DP suffix designates "decentralized periphery" i. e. distributed
input/output devices connected to the central controller by fast serial connection.
This network is based on universal international standards and corresponds to
Open System Interconnection model wherein each communication layer has its
precisely defined task (Fig. 5.3). Layer one of this model defines the physical
characteristics of communication. Layer 2 is Data Link Layer which defines
access to the transmission medium. Layer 7 is applicational and defines user
functions. ProfiBus network utilizes only layers 1 and 2 of OSI model and user
interface. Layers 3 to 7 are not used.

Application
Profiles,
for example
Ident System

DP-Stack
(DP-V0..V2

RS 485
PROFIBUS-DP
(Manufacturing)

Application
Profiles,
for example
PA Device

DP-Stack
(DP-V1)

RS 485
PROFIBUS-PA
(Process)

Application
Profiles,
for example
PROFIdrive

DP-Stack
(DP-V2)

RS 485
Motor Control with
Profibus (Drives)

Application
Profiles,
for example
PROFIsafe

DP-Stack
(DP-V0..V2)

RS 485
MBP-IS
PROFIsafe
(Universal)

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S


Fig. 5.3.
The ProfiBus system utilizes Profius master device which carries out
polling of slave devices (Fig. 5.4) which are distributed along the RS 485 trunk
line (Fig. 5.5).
The slave devices (sensor, actuator, drive mechanism or other measuring
device) form the so called "passive station" in the net since it has no authorized
access to the net and could only confirm the received messages or send a reply
message to a request from the master device. It should be noted that all slave
devices are of equal priority and communication is effected by the master
device.
Master device (Profius master) is the active station in the net. Profibus
specification determines two types of master devices. Master type 1 maintains
normal communication and data exchange with its associated slave devices (Fig.
5.6). Master type 2 is a special device which is used mainly to upload consumer
applications in slave devices for diagnostic purposes. Some master devices are
capable of maintaining both types of functionality. Usually in Profibus network
specification master-to-master communication is not allowed except for the
purpose of authorizing access for another master by means of sending a special
token.

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S


Fig. 5.4.

Fig. 5.5. Physical layer of PROFIBUS (RS 485)
Token ring setup is feasible only between physically linked devices (within
the frame of a network). Master-to-master communication between two nets
with mono-master system (Fig. 5.7) can be effected through a DP_DP gateway.
The master device can address an individual slave device; carry out multicast by
addressing a group of slave devices or perform broadcast addressing message to
all slave devices. The slave device replies to all directly addressed messages but
does not reply to multicast and broadcast messages. Group messages (Broadcast

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S

and Multicast) in the Profibus network are used as messages for global control
with address 127 and the group number of the target group of slave devices.

Fig. 5.6
M Ma as st te er r / / S Sl la av ve e C Co om mm mu un ni ic ca at ti io on ns s
Class 1 master
Class 1 master
Class 2 master
DP Physical
Network
Class 1 Master full data exchange only with its own slaves
Class 2 Master supervisory communications to all slaves


I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S


Fig. 5.7.
Length of I/O data, which is transmitted from the slave device to the master,
is predetermined in the database of the slave device, GSD file. GSD files of all
devices linked within the net are compiled in the type 2 master as parameter
record that contains data about configuration, parameters address distribution list
plus the network parameters of all connected stations. The parameter record is
uploaded in the master device during the phase of hardware configuring.
Profibus DP
Monitoring Device
DP-Master (class 2)
F-Host/F-PLC
DP-Master (class 1)
F-I/O
DP-Slave

Standard-Host/PLC
DP-Master (class 1)
F-Device
DP-Slave
F-Field Device
PA-Slave
DP/PA
Repeater segment A
segment B
F-Gateway
Other safe
bus systems
Standard-I/O
DP-Slave
failsafe and standard users are sharing the same bus
Master-Slave-mapping
Standard-I/O
DP-Slave

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S


Frame Format
SD LE LE
r
S DA SA FC DSAP SSAP DU FCS ED
68 X X X 8 8 X 62/3 60/3 X X 16
SD: Start Delimiter
LE: Net Data Length +DA, SA , FC, DSAP, SSAP
LE
r
Repeated Length
DA: Destination Address
SA: Source Address
FC: Function Code (FC=13 Signals Diagnostic Data)
DSAP: Destination Service Access Point
SSAP: Source Service Access Point
FCS: Frame Checking Sequence
ED: End Delimiter
Fig. 5.8.
At the time of start-up the master device communicates with each of its asso-
ciated slave devices and initiates a cyclic volume of data. In this point each of
the slave devices has a unique assigned address from 0 to 125. Devices with
dynamic addressing (i.e. address 126 at supply switch-on) wait for the command
Set Slave Address from the class 2 master before being parameterized.
PROFIBUS -DP Principle of User Data Transfer
Request Frame
Trail er Output-Data
Parter
Response Frame
Frames
SRD-Request, variable length of user data
D
P-
Sl
av

i
m
m
e
d
i
a
t
e

r
e
s
p
o
n
s
e

SRD-Response, variable length of user data

D
P
-
S
l
a
v
e

D
P
-
M
a
s
t
e
r

D
P
-
M
a
s
t
e
r

D
P
-
S
l
a
v
e

SYN SD2 LE SD2 DA SA FC DU FCS ED LEr
SD2 LE Er DA SA FC DU FCS ED SD2
Parter
Input-Data
Trail er
DU = Data Uni t
FCS = Frame Check Sequence
ED = End Delimi ter
LEr = Repeated Length
DA = Desti nati on Address
SA = Source Address
FC = Functi on Code
SYN = Synchronisati on Time
SD2 = Start Delimiter 2
LE = Length

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S

The communication protocol and frame are shown in Fig. 5.8 and 5.9.

Fig. 5.9.
1.4. BUS Timing
Polling carried out by the respective master device is used by the net.
Reaction time (the time which the slave device takes to respond to the master) is
constant (Fig. 5.10) even in case of using master type 2 for diagnosing the slave
device during its communication with master type 1.Time spacing between
network cycles is used for diagnostic purposes.
Bit-Time (T
bit
Sync-Time (T
) is the time needed to transmit one bit of information in
accordance with the Baud rate.
SYN
) synchronization time is the minimum time during which
station must remain in idle state before becoming accessible for the next request
For Profibus DP this time is 33
bit
Slave Reaction Time (T
.
SDR
) this is the time in which the slave device
must give a reply to the master inquiry. The minimum value (minT
SDR
) is
established through the parameterization command during slave device
initialization. The maximum value (maxT
SDR
) depends on the exchange rate and
D
P

-

M
A
S
T
E
R

Request
Response
Sequence for Data Block Read
Function
Number
Slot
Number
Index
Function
Number
Slot
Number
Index
Length
Data
D
P

-

S
L
A
V
E

Polling until data is available
Length
DP-Extensions

I IN ND DU US ST TR RI IA AL L N NE ET TW WO OR RK KS S A AN ND D I IN NT TE ER RF FA AC CE ES S I IN N
A AU UT TO OM MA AT TI IO ON N S SY YS ST TE EM MS S

is determined in the GSD file of the device for the respective exchange rates.
For Profibus DP this time is:
bit SRD
T 11 T min = to the maximum value of 256T
bit

.
Fig. 5.10.

min TSDR = 11 Tbit
max TSDR= 60 .. 800 Tbit
TSDR
Tsyn= 33 TBit
T
S/R
= Parter + Net data
Tid= 33 TBit
T
A/R
= Parter + Net data (TSYN)
Timing of one Message Cycle T
MC
= ((T
S/R
+ T
SDR
+ T
A/B
) * T
TD
) + T
ID
Theoretical Calculation of a Message-/ Bus Cycle on the
PROFIBUS - DP (without interferences and repetitions)