Profibus DP PDF 1
Profibus DP PDF 1
Profibus DP PDF 1
Organization Technologies
27 Regional
PI Associations
PI Competence
Centers
62 Fieldbus Ethernet
10 33
Proxy
PI PI Technology
Test Labs Training Centers
WGs
1
PI North America
3
What’s a fieldbus?
4
A Fieldbus is a digital, serial, two-way, multi-drop communication link among controllers and its remote I/O, sensors,
actuators and inter-networking components.
In comparison to standard Local Area Networks (LAN), fieldbuses are specialized for the rugged industrial environment,
determinism, bus powering, etc.
2
Before Fieldbuses
5
Process Controller
Direct Wired System
(PLC, DCS, or PAC) PLC = Programmable Logic Controller
DCS = Distributed Control System
PAC = Programmable Automation Controller
Fieldbuses
6
3
Fieldbuses
7
Architecture
8
4
Why use a fieldbus?
9
In 1987 the German Federal Ministry for Research and Technology requested a collaboration project called “Field Bus”
13 Companies and 5 Universities developed an open field bus under the name PROFIBUS for PROcess FIeld BUS based
on the ISO/OSI reference model
5
PROFIBUS and PROFINET Timeline
11
PROFIBUS DP for discrete IO (1993) PROFINET for PROFIsafe & PROFIdrive (2005)
DP = Decentralized Peripheral PROFIBUS PA Profile 3.02 (2009)
DP-V0 PROFIenergy (2010)
PROFIBUS PA for process instruments (1996) PROFINET for Process Automation (2011)
PA = Process Automation
DP-V1 and PA
PROFIBUS for PROFIsafe & PROFIdrive (2001)
DP-V2
PROFINET for CBA and IO (2001)
CBA = Component Based Automation
Factory automation
Vehicle manufacturing
Bottling plants
Warehousing systems
Process automation
Chemical industry
Petrochemical industry
Paper and textiles
Power stations
Drive technology
Machine tools
Packaging machines
Paper production
Hybrid applications
6
PROFIBUS DP and PA
13
PROFIBUS is mainly used for high speed input/output devices and to link intelligent devices such as drives.
It can use different physical layers such as RS-485 (most common), wireless or fiber optics.
PROFIBUS PA refers to the following additional features:
Bus powered by using the Manchester encoded Bus Powered (MBP) physical layer according to IEC 61158-2
Intrinsically safe design
Configuration over the bus
Device profile
DP = Decentralized Periphery
PA= Process Automation
PROFIBUS DP
14
4 Transport layer
3 Network layer
1 Physical layer
7
PROFIBUS PA
15
Network Design
8
PROFIBUS DP Project Steps
17
Eng
Active Station(s) Station
PLC/
PLC/
DCSCS
PROFIBUS
9
Controller - Device Concept
19
Multiple Controllers
Can Share the Bus
One Controller May
Read Data From
Another Controller’s Active Stations
Devices PLC/
PLC/
PLC/ DCS
BUT
DCS
DCS
Only One Controller
Can Write to the
Outputs of a Specific
Device (Must Know
Who Is Controlling PROFIBUS
Outputs)
Outputs
Inputs
Cyclic Channel – I/O Data Exchange
PROFIBUS Features
20
Acyclic Channel –
Parameter Access
10
PROFIBUS Features
21
PROFIBUS Features
22
11
PROFIBUS Project Steps
23
Design considerations
Do I have any very long distances to cover?
How many devices will I have?
What communication medium/media will I use?
Are there any high-EMI areas?
Does my architecture require the use of “stub” lines?
What is the required I/O update cycle time?
How many networks do I need?
Many of these constraints/requirements are inter-related
12
Segment and Network Lengths
25
9.6 1,200m/3,934ft
19.2 1,200m/3,934ft
45.45 1,200m/3,934ft
93.75 1,200m/3,934ft
187.5 1,000m/3,278ft
500 400m/1,311ft
1,500 200m/656ft
3,000 100m/328ft
6,000 100m/328ft
12,000 100m/328ft
13
Number of Devices on a Segment
27
What if the total network must be longer than the segment length allowed at the baud rate used?
What if the total number of devices is greater than 32?
The network is “segmented” by connecting the previous segment having the diminished or distorted signal to a Repeater to refresh
the signal.
Refreshes the voltage level
Reshapes the waveform
R
Diminished/Distorted RS485 Signal e
p
e
a
t
e
r
14
Segment and Network Lengths
29
The network is “segmented” when the maximum segment length for the baud rate is reached or when 32 devices are
attached…either situation requires segmentation no matter which is reached first.
Specific Length=
32 Devices=Segment Segment
Example segmentations
R
e
12,000kbits/s p
Controller e
a
100 meters t
e
r
No devices
R
e
12,000kbits/s p
Controller e
a
50 meters t
e
r
31 devices in first 50 meters
Next device at 60 meters
15
Segment and Network Lengths
31
Example segmentations
R
e
12,000kbits/s p
Controller e
a
100 meters t
e
r
31 devices in first 50 meters
Next device at 130 meters
There is a limit to the number of repeaters that can be used in a communication path between a PLC and a device.
The reason is to avoid the possibility of timing problems.
There is a slight time lag through each repeater on outgoing messages from a PLC and incoming messages from the device.
A PLC will wait only a specific amount of time for a response from the device.
A vendor’s repeater manual will typically list a “maximum cascading depth” that can be tolerated without the possibility of timing problems.
For example, Siemens repeaters have a limit of 9 and Procentec repeaters have virtually no limit
Some other repeaters have a limit of 3
Slower electronics
Don’t amplify the voltage…just reshape signal
16
Cascading Repeaters
33
2,000
2,000 1,200 1,200 1,200 1,200
1,000 1,000 1,000
400 200 1,000
100 100
0 100
9.6 19.2 45.45 93.75 187.5 500 1,500 3,000 6,000 12,000
Although a single communication path has a cascading depth limit, there can be more repeaters used in the entire
network.
Controller
Device
17
Network Segmentation
35
Up to 32
Devices Per
Segment
Address #122 Address #125
No Address = Repeater
= OLM
What communication medium/media will I use? Wide range of available media and technologies.
Copper is the most commonly-used with a wide variety of connector technologies
Almost all devices have a copper connection
RS485 signaling technology used
Wide variety of connectors available
Fiber optics
Long distances with high-quality fiber
Variety of topologies and redundancy
Immune to ground plane differences
Suitable for use in high EMI areas
Few devices have a direct FO connection
Infrared communicators
Good for lateral motion
Limited to about 15m/50ft distances
Maximum baud rate = 1,500kbits/s
18
PROFIBUS Communication Media
37
What communication medium/media will I use? Wide range of available media and technologies.
Laser communicators.
Good for linear, in-line motion
Can communicate to about 400m/1,311ft
Typically used to eliminate trailing cable
Radio transceivers.
Some models communicate up to several miles
Radio-radio communication generally at baud rates of 9.6 or 19.2kbits/s
Two general types available:
Transparent – each device is front-ended by a transceiver
Non-transparent – transceiver acts as a master to devices behind it and must be configured
What communication medium/media will I use? Wide range of available media and technologies.
Other communication technologies:
Slip rings.
For rotating machinery even at up to 12Mbits/s
Hanging conveyor power rails.
Limited to 1.5Mbits/s
For moving assemblies from workstation to workstation
19
PROFIBUS Physical Layers
39
20
Use of Stub Lines
41
For baud rates above 500kbits/s, it’s safer to use a repeater to facilitate a branch away from the main trunk line.
There will never be a problem to extend the segment or increase the baud rate because it is not a spur/stub line
Repeater product availability from Siemens, Procentec, Phoenix Contact, Kunbus, Helmholz, Indusol, Hirschmann, etc.
Eurofast or Minifast
Stub lines from a trunk line to removable buckets in an MCC, for example Connector – Cable to valve
Both architectural examples seem to have some justification, although most MCC wiring uses daisy-chaining
Architectures are possible using stub lines; however, the baud rate restrictions from the PROFIBUS standard must be
observed.
The standard states the restrictions in terms of the total amount of capacitance allowed due to the total of stub lines on a segment
for a given baud rate
Using the Type A cable capacitance of 30pF/m, it’s easy to convert these allowed capacitances to distances,
as shown in the next table
21
Use of Stub Lines
43
Table of total length of allowed stub lines at the different baud rates.
Remember that this is the total for ALL stub lines…not the limit for each individual stub!!
600
550
500
500 500
450
400 Total of Allowed Stubs [m]
350
300 300
250
200
Meters 150
100
100
50 33 20 6.6 0 0
0 0
0
5
00
6
.2
50
7.
.4
.7
50
00
00
9.
19
,0
[kbaud]
45
93
18
1,
3,
6,
12
Stub lines result in “lumped” capacitance at the point of the stub line
Normal Device
Capacitance Lumped Capacitance = L*30pF + N*35pF
L L = cable length in m
N = no. of devices
35pF
22
Fiber Optic Media
45
Least expensive,
Plastic lowest performance,
Low performance, large diameter plastic core easiest to use.
Longer Distances
Line, ring, redundant ring and star configurations are possible
23
Use of Fiber Optic
47
PROFIBUS FO -
Glass, PCF or Plastic
Redundant
OLM Paths
24
Use of Fiber Optic
49
25
Address Assignment
51
What do I need to consider to determine the I/O cycle (update) times required?
The PLC/DCS control cycle time
Should have several I/O updates for each control cycle
Required I/O response times
Input to output
26
I/O Cycle Time
53
What do I need to consider to meet the I/O cycle (update) times required by my control cycle time?
The effect of communication baud rate on cycle time is pretty much self-explanatory
The effect of more/less devices to scan each cycle is also pretty much self-explanatory
The effect of more/less data to be transferred each cycle is also pretty much self-explanatory
The effect of the total number of networks may not be self-explanatory
Some DP/PA couplers are “dumb” and require slowing the baud rate on the DP network to 45.45kbits/s or 93.75kbits/s – more details
later
27
I/O Cycle Time
55
What are the primary things we can do to meet the requirement of 10ms?
Increase the baud rate
Split the devices out onto more than one network
Increasing the baud rate to 12Mbits/s in our configuration tool gave an estimated I/O cycle time of 4.1ms
28
I/O Cycle Time
57
Splitting the 50 devices across two networks of 25 devices at 1.5Mbits/s with our configuration tool gave an estimated
I/O cycle time of 6.5ms
The two separate networks are being scanned in parallel, cutting the I/O cycle time approximately in half
PLC/
DCS
Most PLCs/DCSs accommodate
multiple PROFIBUS controller cards
25 Devices
25 Devices
29
Device Selection: Devices
59
30
Configuration Software Selection
61
Parameter selection
This
This
Or
This?
This
31
Device Selection
63
32
PROFIBUS DP- Decentralized Periphery
Network Configuration
33
System Configuration
67
•Select Master
•Assign Address
•Select Devices
•Assign Address
•Configure I/O
•Set Parameters
PLC/
PLC/
DCS
DCS
Electronic Device Data Sheets (GSD, GSE, GSF, GSG, GSI, GSP, GSS Files)
PROFIBUS
GSD Files
68
34
GSD Files
69
GSD Files
70
35
Startup Sequence
71
Device parameterization
Select parameters with configuration tool
Power ON/
Reset
Parameterization
I/O Configuration
jsdfehrgihw[orijth] ewj]y pokj eky jsdfehrgihw[orijth] ewj]y pokj eky
gadfgsadfhsf ghjjsff ghsf gh gadfgsadfhsf ghjjsff ghsf gh
fdhsdldajhtvi ertivetv ert fdhsdldajhtvi ertivetv ert
34524 34524
575687356nj 8467k nggnhngjt 575687356nj 8467k nggnhngjt
rby5yik57859mnnbvt 456hn, rby5yik57859mnnbvt 456hn,
g76nkbvijyuftis dt0iewryt9ei uoriy g76nkbvijyuftis dt0iewryt9ei uoriy
rywkrowrgowrtohworthorthwrth rywkrowrgowrtohworthorthwrth
rthwrthrwthtryjtyjyuky rthwrthrwthtryjtyjyuky
tyjy7u79jtyu568566ut tyjy7u79jtyu568566ut
rtjhyuiuikujkhyjiyuiy uii rtjhyuiuikujkhyjiyuiy uii
thjyukiuio7ujty ujytuoiuk y thjyukiuio7ujty ujytuoiuk y
tyjyukuikyukuiluili ui oliuiluii l tyjyukuikyukuiluili ui oliuiluii l
6buhyijtiu8o67m8m 747567n8 6buhyijtiu8o67m8m 747567n8
567n75567nm78m78, om87o, 567n75567nm78m78, om87o,
56nu78m,,9o,0p.90. p;0;.;’-;/ 56nu78m,,9o,0p.90. p;0;.;’-;/
Data Exchange
36
Startup Sequence: Parameterization
73
Device parameterization
Download parameters to device
Parameterization
Controller Device
Features Implemented in Device
I/O Configuration Described in GSD File
Processed by Configuration Tool
Selected at Configuration
Data Exchange
Examples:
Enable Channel Diagnostic
Operation Range for Analog Channels
(e.g. ±10V or 0..10V)
Fail-to-Known State Behavior (e.g. Hold Last
Value)
= Parameterization Data = Confirmation (Data Received)
Power ON/
Reset
Parameterization
I/O Configuration
Data Exchange
37
Startup Sequence: I/O Configuration
75
Parameterization
Controller Device
Possible I/O Selections Described in GSD File
I/O Configuration Processed by Configuration Tool
Selected at Configuration
Examples
Data Exchange
8DI (1 Byte), 8DO (1 Byte)
2AI (2 Words), 2AO (2 Words)
RS232 Interface, Counter Module
Power ON/
Reset
Parameterization
I/O Configuration
38
Use of Startup Sequence
77
PROFIBUS PROFIBUS
System
Device
Fails
39
Use of Startup Sequence
79
PROFIBUS PROFIBUS
System New
Device
PROFIBUS PROFIBUS
System New
New
Device
Device
40
PROFIBUS Project Steps
81
Fail-to-Known-State
82
41
Fail-to-Known-State
83
Fail-to-Known-State
84
42
PROFIBUS Project Steps
85
System Configuration
86
•Select Controller
•Assign Address
•Select Devices
•Assign Address
•Configure I/O
•Set Parameters
PLC/
PLC/
DCS
DCS
Electronic Device Data Sheets (GSD, GSE, GSF, GSG, GSI, GSP, GSS Files)
PROFIBUS
43
Demo Rack
87
SIEMENS TURCK
PLC S7-315 I/O System
BL Compact
PHOENIX CONTACT
I/O ILB 24
SIEMENS
DP/PA Link
and Coupler
WAGO SIEMENS
I/O-System 750 SITRANS
Temperature
Transmitter
WAGO
I/O-System 767
Configuration Overview
88
44
Address Assignment
89
Compact Device
45
Example I/O Configuration
91
Modular Device
Parameter Assignment
92
46
Fail-to-Known-State
93
Bus Timing
94
Estimated
Bus I/O Cycle Time
47
PROFIBUS DP- Decentralized Periphery
Installation
48
RS485 Signal
97
B
A
Idle Line
Typically 4V – 7V
RS –Recommended Standard
STP – Shielded Twisted-Pair
RS485 Signal
98
More noise immune than single-wire technologies which transmit and receive on one wire
RS485 uses two wires
Transmits and receives on both wires
Any noise typically couples onto both wires of the STP in the same way
B Differential Signal
A (B-A)
RS –Recommended Standard
STP – Shielded Twisted-Pair
49
PROFIBUS Project Steps
99
The following table gives the maximum RS485 copper segment lengths at the PROFIBUS baud rates.
9.6 1,200m/3,934ft
19.2 1,200m/3,934ft
45.45 1,200m/3,934ft
93.75 1,200m/3,934ft
187.5 1,000m/3,278ft
500 400m/1,311ft
1,500 200m/656ft
3,000 100m/328ft
6,000 100m/328ft
12,000 100m/328ft
50
Number of Devices on a Segment
101
The EIA/TIA 485 specification says that one RS485 transmitter can drive 31 RS485 receivers
Therefore, a maximum of 32 RS485 devices are permissible on a single copper segment
What constitutes a device?
Any component attached to the segment that has RS485 circuitry counts as one of the 32 devices.
PLCs
I/O devices
HMIs
Repeaters
PROFIBUS DP/PA gateways
Fiber optic repeaters (OLMs)
Bus diagnostic tools
Basically anything with a copper connection
Exception is active termination box
The network is segmented when the maximum segment length for the baud rate is reached or when 32 devices are
attached…either situation requires segmentation no matter which is reached first.
Maximum Length=
New Segment
32 Devices=New Segment
51
Total Repeaters In A Network
103
Although a single communication path has a cascading depth limit, there can be more repeaters used in the entire
network.
Controller
Device
Use of Repeaters
104
Segment 1
Segments
Connected Via
Isolation Repeaters
Segment 2 Segment 2
52
Use of Repeaters
105
Branching structures built with repeaters instead of splices into the trunk line
Extension of Segment 1
Segment 1 Segment 1
Isolation Segments
Connected Via
Repeaters
Segment 2 Segment 2
53
Segment Grounding
107
Segment
Grounding
Segment Grounding
108
54
Interference From External Sources
109
Electrostatic injection
Capacitive coupling caused by nearby high voltage power lines
High Voltage
Interference source,
e.g., power cable Capacitive coupling between cables
Pickup
Electromagnetic injection
Inductive coupling caused by varying currents in nearby power lines
High Current
Interference source,
e.g., power cable
Inductive coupling between cables
Pickup
Reduction of Coupling
110
Interference
Interference source.
e.g., power cable
Pickup passes to ground via shield
Rs Rs Rs Pickup
Rs = Shield resistance
For PROFIBUS cable, Rs = 9.5/km
55
Segment Grounding
111
Segment Grounding
112
56
Segment Grounding
113
Continuity
Continuity
Segment Grounding
114
•0.10nF
•1500V
57
Segment Grounding
115
Segment Grounding
116
Grounding
Clamp
Cable Shield
58
PROFIBUS Project Steps
117
Use Appropriate
RS485 Cable
Rated for
PROFIBUS
59
PROFIBUS Cable
119
PROFIBUS Cable
120
60
Connectors for PROFIBUS DP
121
61
PROFIBUS Project Steps
123
Segment Termination
124
Segment
Terminations
62
Segment Termination
125
Segment Termination
126
63
Segment Termination
127
Termination
If device is not powered, the terminating and biasing resistor network is not fully active
Reflections may be generated due to impedance mismatch
A-Line (8)
Biasing Resistor 390 Ohm
DP-GND (5)
(X) Pin in Sub D Connector
Reflections in General
128
64
Segment Termination
129
Segment Termination
130
65
Segment Termination
131
PLC/
DCS
Segment Termination
132
66
PROFIBUS Project Steps
133
67
PROFIBUS Project Steps
135
Proximity to Power
Cables
68
Installation: Best Practice
137
>= 20 cm
>= 50 cm
>= 50 cm
>= 50 cm
Cable
Category IV
69
Installation: Best Practice
139
Connectors/wiring
Interconnection Standard specifies: A to Green / B to Red
Leave 1 Meter between uncertified or uncertain devices or at baud rates > 187.5kbits/s
Avoids “lumped” capacitance
(n = no. of devices)
Device capacitances look like a single
“lumped” capacitance.
Connectors/wiring
No Sharp Bends – minimum bend radius typically 10 x cable diameter
Can crimp copper
Do not mix different cable types
Ensure that each segment has a piggy-back Sub-D connector at least at one end for connection of diagnostic tools
Better to have one at each end
When using insulation displacement (ID) connectors, make sure the scissor blades of the connector make good contact with the
copper wire
If possible, use connectors and cables from the same vendor
If possible, start with a new cable end when re-using an ID connector
Don’t use same cable end more than twice
Check continuity when re-using an ID connector
70
Installation: Best Practice
141
Terminations
Ensure terminations are at segment ends and that the terminations will have constant power
Make sure that there are exactly two terminations per segment…no more and no less!
Bus segmentation
Make sure that all segments meet the length restrictions for the baud rate
Make sure that no segment has more than 32 devices
Check stub line usage
Ensure that the baud rate restrictions due to stub line usage are followed
Check that device addresses are correctly set on the device as shown in your drawings
Device power
If at all possible, fuse each device so it can be powered up/down separately
Ensure that the device has adequate power in all conditions, e.g., high current outputs all turned ON simultaneously
Power a device down prior to connecting or disconnecting the connector, especially at high baud rates
71
PROFIBUS Project Steps
143
72
PROFIBUS Project Steps
145
Run-Time Analysis
146
73
Run-Time Analysis
147
74
Diagnostic Information
149
Diagnostic Information
150
Controller Device
75
Diagnostic Information
151
Controller Device
Diagnostic Information
152
Controller Device
76
Diagnostic Information
153
Controller Device
Diagnostic Information
154
Channel-Related (Standard)
This Device has a Diagnostic
This Module has a Diagnostic
This Input/Output Channel
has a Diagnostic
The Diagnostic is
Wire Break
Device-Related (Vendor Specific) Short Circuit
Identifier-Related (Standard)
Missing Load Power Undervoltage
Module in this Slot has a
Actuator Stuck Overvoltage
Diagnostic
... ...
77
Diagnostic Information
155
Diagnostic Information
156
78
PROFIBUS Project Steps
157
Diagnostic Information
158
79