PROFINET Design Guideline 8062 V153 Sept22

PROFINET
Design Guideline
Guideline
for PROFINET
Version 1.53 – Date 21. Sept, 2022

Order No.: 8.062
File name: PROFINET_Design_Guideline_8062_V153_Sept22.docx
Prepared by PI Working Group PG3 “Installation Guides PROFIBUS and PROFINET” in

Committee B.
The attention of adopters is directed to the possibility that compliance with or adoption of PI (PROFIBUS&PROFINET
International) specifications may require use of an invention covered by patent rights. PI shall not be responsible
for identifying patents for which a license may be required by any PI specification, or for conducting legal inquiries
into the legal validity or scope of those patents that are brought to its attention. PI specifications are prospective
and advisory only. Prospective users are responsible for protecting themselves against liability for infringement
of patents.
NOTICE:
The information contained in this document is subject to change without notice. The material in this document details
a PI specification in accordance with the license and notices set forth on this page. This document does not
represent a commitment to implement any portion of this specification in any company's products.
WHILE THE INFORMATION IN THIS PUBLICATION IS BELIEVED TO BE ACCURATE, PI MAKES NO
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL INCLUDING, BUT
NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF
MERCHANTABILITY OR WARRANTY OF FITNESS FOR PARTICULAR PURPOSE OR USE.
In no event shall PI be liable for errors contained herein or for indirect, incidental, special, consequential,
reliance or cover damages, including loss of profits, revenue, data or use, incurred by any user or any third
party. Compliance with this specification does not absolve manufacturers of PROFIBUS or PROFINET
equipment, from the requirements of safety and regulatory agencies (TÜV, BIA, UL, CSA, etc.).
PROFIBUS® and PROFINET® logos are registered trade marks. The use is restricted to
members of PROFIBUS&PROFINET International. More detailed terms for the use can be
found on the web page www.profibus.com/Downloads. Please select button
"Presentations & logos".
In this specification the following key words (in bold text) will be used:
may: indicates flexibility of choice with no implied preference.
should: indicates flexibility of choice with a strongly preferred implementation.
shall: indicates a mandatory requirement. Designers shall implement such mandatory
requirements to ensure interoperability and to claim conformance with this
specification.
Publisher:
PROFIBUS Nutzerorganisation e.V.
Haid-und-Neu-Str. 7
76131 Karlsruhe
Germany
Phone : +49 721 986197 0
Fax: +49 721 986197 11
E-mail: [email protected]
Web site: www.profibus.com
© No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
Page 2 / 242
© Copyright by PNO 2022 – all rights reserved
Revision log
Ver Date Author Changes/history
1.04 18.11.2010 Niemann Final version
1.05 11.06.2013 Niemann Internal version, not published
1.06 --- Niemann Internal versions, not published

to
1.10
1.11 05.08.2014 Niemann PoE and 4-pair cables. Enhancement of performance

considerations. Layout change to DIN A4
1.12 16.11.2014 Niemann Modifications and comments added the English version by
A.V. Internal Version, not published
1.13 20.11.2014 Niemann Consolidation of review comments by WG Chair
1.14 30.12.2014 Niemann Review Comments after Advisory Board review integrated.
1.15- ---- Niemann Internal versions, not published

1.23
1.24 07.09.2018 Niemann Processing von Review comments, chapter network

documentation added. Chapter EMC adapted to new EMC
guideline. Chapter EMC deleted and reference to new
guideline added. Table for cable distances corrected,
missing multipliers added, example added. Internal word
graphics replaced by png graphics to resolve Word stability
problems
1.25 --- Niemann Internal version
1.26 08.09.2018 Niemann Final review by WG Chair and last changes prior to WG
review.
1.32 01.01.2019 Niemann Document was renewed due to crash problems
1.35 07.05.2019 Niemann Processing of comments: Preferred use of cable type B for
to vibration effects, use of 1 Gbit/s Ethernet between switches
1.37
Page 3 / 242
1.38 17.09.2019 Niemann Final editing. Disclaimer about min Cable Distances added
1.39 01.03.2022 Niemann Intermediate Version
1.40 13.06.2022 Niemann Additions for Ethernet APL, Correction, Images updated to
to new style guide, Liability exclusion updated, standards and
1.50 documents updated to recent versions. Error in device
names fixed (Hyphens replaced by dash)
1.51 28.07.2022 Niemann Reviev comments from Review meeting 13.06.2022

processed. Rate limiter added
1.52 31.07.2022 Niemann Final Proof reading
1.53 23.09.2022 Niemann Finalization for release of document
Page 4 / 242
Table of contents
1 INTRODUCTION........................................................................................................................... 15
1.1 PREFACE ................................................................................................................................ 16
1.2 LIABILITY EXCLUSION ............................................................................................................... 17
1.3 PNO DOCUMENTS ................................................................................................................... 18
1.4 REFERENCED STANDARDS ....................................................................................................... 20
1.5 SYMBOLS AND THEIR MEANING ................................................................................................. 23
1.5.1 Symbols for structuring the text..................................................................................... 23
1.5.2 Symbols for components ............................................................................................... 24
1.5.3 Symbols for PROFINET cables ..................................................................................... 27
1.5.4 Symbols for areas ......................................................................................................... 28
1.6 ABOUT THE STRUCTURE OF THIS GUIDELINE .............................................................................. 29
1.7 GOAL OF THE GUIDELINE .......................................................................................................... 31
2 ANALYSIS AND PRELIMINARY CONSIDERATIONS ............................................................... 32
2.1 DETERMINATION OF AUTOMATION COMPONENTS ....................................................................... 33
2.2 DEVICE SELECTION .................................................................................................................. 36
2.2.1 The PROFINET Conformance Classes ........................................................................ 37
2.2.2 Special timing requirements .......................................................................................... 39
2.2.3 Further criteria for device selection ............................................................................... 42
2.3 DEFINITION OF DEVICE TYPES ................................................................................................... 48
2.4 DOCUMENTATION OF RESULTS ................................................................................................. 50
3 NETWORK TOPOLOGY .............................................................................................................. 51
3.1 PROFINET TOPOLOGY ........................................................................................................... 53
3.2 APPLICABLE TRANSMISSION MEDIA ........................................................................................... 57
3.2.1 PROFINET copper cabling (4-core, 8 core) .................................................................. 58
3.2.2 Ethernet APL Cables ..................................................................................................... 61
Page 5 / 242
3.2.3 Separation distances between cables .......................................................................... 62
3.2.4 PROFINET optical fiber cabling .................................................................................... 65
3.2.5 Selection of required connectors................................................................................... 71
3.3 PREFERRED DEVICES FOR PRIMARY INFRASTRUCTURE .............................................................. 73
3.4 DEFINITION OF NETWORK TECHNOLOGY .................................................................................... 75
3.5 TOPOLOGY CHECK AND REFINEMENTS ...................................................................................... 80
3.6 DOCUMENTATION OF TOPOLOGY .............................................................................................. 81
4 SPECIAL DESIGN ASPECTS ...................................................................................................... 83
4.1 USE OF “FAST STARTUP” ......................................................................................................... 84
4.2 UTILIZATION OF EXISTING CABLE INFRASTRUCTURE ................................................................... 85
4.3 CONNECTION TO HIGHER LEVEL NETWORKS (CORPORATE NETWORK) ......................................... 86
4.4 DETERMINATION OF FIRMWARE REVISION LEVELS ...................................................................... 87
4.5 PLANNING OF ACCESS POINTS FOR NETWORK DIAGNOSES ......................................................... 88
4.6 UTILIZATION OF 4-PAIR CABLING ............................................................................................... 89
4.7 DOCUMENTATION OF MODIFIED NETWORK TOPOLOGY ................................................................ 90
5 ETHERNET-APL .......................................................................................................................... 91
5.1 W HAT IS ETHERNET-APL ......................................................................................................... 92
5.2 POSSIBLE TOPOLOGIES FOR AN APL SYSTEM ............................................................................ 94
5.2.1 Alternative 1: APL field switches with Industrial Ethernet connection........................... 94
5.2.2 Alternative 2: Powered APL Trunk ................................................................................ 96
6 PERFORMANCE CONSIDERATIONS ........................................................................................ 98
6.1 PROFINET TRANSMISSION CYCLE ......................................................................................... 100
6.1.1 Prioritization of PROFINET packets and switching technologies ............................... 100
6.1.2 Update time ................................................................................................................. 101
6.1.3 Network load ............................................................................................................... 103
6.1.4 Response time of processing chains .......................................................................... 104
6.2 PLANNING OF THE IO CYCLE................................................................................................... 108
Page 6 / 242
6.2.1 Planning of update times ............................................................................................. 108
6.2.2 Definition of PROFINET communication monitoring ................................................... 110
6.3 CHECKING THE PERFORMANCE OF THE PLANNED NETWORK TOPOLOGY .................................... 113
6.3.1 Checking the line depth for 100 Mbit/s network .......................................................... 113
6.3.2 Checking the line depth for Ethernet-APL networks ................................................... 116
6.3.3 Checking the cyclic real-time network load ................................................................. 117
6.3.4 Checking the non-real-time network load ................................................................... 122
6.4 MIXED LINK SPEEDS AND STAR TOPOLOGY .............................................................................. 125
6.4.1 Problem Description mixed link speeds and star topology ......................................... 126
6.4.2 Example System ......................................................................................................... 127
6.4.3 Prioritized queues in network switches ....................................................................... 128
6.4.4 Congestion loss due to prioritization of messages ...................................................... 129
6.4.5 Congestion loss due to input / output unbalance port count wise ............................... 130
6.4.6 Congestion loss due to input / output unbalance link speed wise .............................. 131
6.4.7 Congestion loss in Ethernet-APL Systems ................................................................. 132
6.4.8 Summary congestion loss ........................................................................................... 134
6.4.9 Permanent or spurious congestion loss ...................................................................... 136
6.4.10 Planning measures to avoid congestion loss .............................................................. 137
6.5 DOCUMENTING YOUR SETTINGS.............................................................................................. 139
7 PLANNING OF ADDITIONAL FUNCTIONS .............................................................................. 140
7.1 INCREASED AVAILABILITY........................................................................................................ 141
7.2 W IRELESS TRANSMISSION TECHNOLOGY ................................................................................. 146
7.3 POWER OVER ETHERNET ....................................................................................................... 149
8 DEFINITION OF DEVICE PARAMETERS ................................................................................. 151
8.1 ASSIGNMENT OF NAMES ......................................................................................................... 153
8.2 PLANNING OF IP ADDRESSES ................................................................................................. 155
8.3 PROFINET PLANT EXAMPLE.................................................................................................. 158
Page 7 / 242
9 SUMMARY .................................................................................................................................. 164
10 ANNEX ........................................................................................................................................ 166
10.1 ADDRESSES .......................................................................................................................... 167
10.2 GLOSSARY ............................................................................................................................ 167
10.3 DETAILS ABOUT PROFINET COPPER CABLES......................................................................... 168
10.4 DETAILS ABOUT PROFINET OPTICAL FIBERS ......................................................................... 180
10.5 SELECTION OF CONNECTORS ................................................................................................. 185
10.6 CABLING EXAMPLES ............................................................................................................... 195
10.7 SELECTION OF SWITCHES....................................................................................................... 202
10.8 FUNCTIONAL EQUIPOTENTIAL BONDING AND SHIELDING BY PROFINET .................................... 206
10.9 PROFINET DOCUMENTATION ............................................................................................... 207
10.9.1 PROFINET information relevant for documentation ................................................... 207
10.9.2 Proposal for a PROFINET forwards documentation ................................................... 210
10.9.3 Example of a PROFINET forwards documentation .................................................... 214
10.9.4 Problems of forwards documentation in the product lifecycle ..................................... 229
10.9.5 Proposal for a PROFINET backwards documentation................................................ 231
10.9.6 Difficulties of backwards documentation ..................................................................... 232
10.9.7 Requirements on future backwards documentations .................................................. 232
10.10 NETWORK LOAD CALCULATION TOOL....................................................................................... 233
11 INDEX ......................................................................................................................................... 238
Page 8 / 242
List of figures
Figure 1-1: Design structure ........................................................................................... 29
Figure 2-1: Floor plan of a plant with pre-placed components ..................................... 34
Figure 2-2: Sample layout plan of a plant with special assignment ............................. 35
Figure 2-3: Classification and content of the individual conformance classes ........... 38
Figure 2-4: Coverage of communication timing requirements ..................................... 41
Figure 2-5: Use of PROFIsafe via PROFINET ................................................................. 45
Figure 2-6: Difference integrated switch and separate switch...................................... 46
Figure 2-7: Sample layout of a plant with device preselection ..................................... 48
Figure 3-1: Star topology ................................................................................................. 54
Figure 3-2: Tree topology ................................................................................................ 55
Figure 3-3: Line topology ................................................................................................ 56
Figure 3-4: Application of optical fiber technology for EMI .......................................... 65
Figure 3-5: Topology example ........................................................................................ 74
Figure 3-6: Example of a factory automation ................................................................. 77
Figure 3-7: Example of a machine automation .............................................................. 78
Figure 3-8: Example plant process automation with remote IO.................................... 79
Figure 3-9: Example Plant Process Automation with Ethernet APL ............................. 80
Figure 3-10: Plant example with preliminary topology .................................................. 82
Figure 4-1: Implementation of “Fast Start-Up“ with PROFINET.................................... 85
Figure 4-2: Plant example with connection to the corporate network.......................... 86
Figure 4-3: Reading data streams via TAP ..................................................................... 89
Figure 5-1: Differences between Fast Ethernet and APL .............................................. 93
Figure 5-2: Field switches with Industrial Ethernet connection ................................... 95
Figure 5-3: Powered APL trunk ....................................................................................... 96
Figure 6-1: Prioritization of real-time communication with PROFINET ...................... 100
Figure 6-2: PROFINET transmission cycle ................................................................... 101
Figure 6-3: Network load, transmission cycle 4 ms, controller transmission clock 1
ms ................................................................................................................................... 102
Figure 6-4: Network load, transmission cycle 4 ms, controller transmission clock 4
ms ................................................................................................................................... 102
Page 9 / 242
Figure 6-5: Example of the network load development during a transmission cycle103
Figure 6-6: Cycles in the processing chain .................................................................. 104
Figure 6-7: Examples of cycles in the processing chain, shortest response time .... 105
Figure 6-8: Examples of cycles in the processing chain, longest response time ..... 106
Figure 6-9: Cyclic PROFINET network load as a function of update time and number
of network nodes (typ. PROFINET packets) ................................................................. 108
Figure 6-10: Communication problems with error threshold 3 ................................... 110
Figure 6-11: Comparison of low (3, left) and high (10, right) threshold ..................... 111
Figure 6-12: Line depth example................................................................................... 113
Figure 6-13: Example of reduced line depth ................................................................ 115
Figure 6-14: Line depth with APL Field-switches connected to 100 Mbit/s network . 116
Figure 6-15: Line depth with APL trunk ........................................................................ 117
Figure 6-16: Example of network load distribution in a single controller application

........................................................................................................................................ 118
Figure 6-17: Example of network load distribution in a multi-controller application 119
Figure 6-18: Example topology with standard Ethernet nodes................................... 122
Figure 6-19: Integration of standard Ethernet nodes .................................................. 124
Figure 6-20: Optimized topology with reduced network load ..................................... 125
Figure 6-21: Mixed Link speeds and star topology in a PROFINET system............... 127
Figure 6-22: Switch principle with queues ................................................................... 128
Figure 6-23: Congestion loss due to input/output unbalance port wise .................... 130
Figure 6-24: Example for input/output unbalance port count wise ............................ 131
Figure 6-25: Example for input/output unbalance link speed wise ............................ 132
Figure 6-26: System Structure of an APL System with trunk and spur topology ...... 133
Figure 6-27: Ethernet-APL system with 100 Mbit/s industrial Ethernet to the field
switches.......................................................................................................................... 134
Figure 7-1: Device exchange in a line topology ........................................................... 141
Figure 7-2: Device exchange in a star or tree structure .............................................. 142
Figure 7-3: Upgrading a line topology to a ring structure ........................................... 143
Figure 7-4: High-availability plant network................................................................... 145
Figure 7-5: Use of wireless transmission technology ................................................. 147
Figure 7-6: Topology limitations with Power over Ethernet ........................................ 149
Figure 8-1: PROFINET device (delivery status)............................................................ 153
Page 10 / 242
Figure 8-2: PROFINET device (address allocation) ..................................................... 155
Figure 8-3: Overall structure of example plant ............................................................ 158
Figure 10-1: PROFINET cable type A ............................................................................ 174
Figure 10-2: PROFINET PE cable .................................................................................. 175
Figure 10-3: PROFINET ground cable........................................................................... 176
Figure 10-4: Trailing cable ............................................................................................. 177
Figure 10-5: Cables for festoons................................................................................... 178
Figure 10-6: Ethernet-APL cable ................................................................................... 179
Figure 10-7: PROFINET optical fiber cable................................................................... 183
Figure 10-8: PROFINET FO trailing cable ..................................................................... 184
Figure 10-9: Typical RJ45 push-pull connector with IP65 rating ................................ 187
Figure 10-10: Typical RJ45 push-pull connector with IP20 rating .............................. 187
Figure 10-11: Typical D-coded M12 connector ............................................................ 188
Figure 10-12: Typical M12 TypeX connector ................................................................ 188
Figure 10-13: Typical SCRJ push-pull connector with IP20 rating ............................. 190
Figure 10-14: Typical SCRJ push-pull connector with IP65 rating ............................. 190
Figure 10-15: Typical LC-Connector with IP20 rating .................................................. 191
Figure 10-16: Typical M12 hybrid connector ................................................................ 191
Figure 10-17: RJ45 distribution module for top hat rail mounting in IP20
environments ................................................................................................................. 193
Figure 10-18: RJ45 connection socket for IP65 / IP67 environments ......................... 193
Figure 10-19: RJ45 Push-Pull bulkhead connector for use with cabinets ................. 194
Figure 10-20: M12 bulkhead connector for use with cabinets .................................... 195
Figure 10-21: Examples of copper-based cabling ....................................................... 195
Figure 10-22: Example of FO cabling ........................................................................... 197
Figure 10-23: Representation of attenuation balance for single-mode optical fiber

links ................................................................................................................................ 199
Figure 10-24: Representation of attenuation balance for POF FO link....................... 200
Figure 10-25: Fields of interest in a plant lifecycle ...................................................... 210
Figure 10-26: Cover page example for PROFINET forwards documentation............. 215
Figure 10-27: Example of forwards documentation for the automation of three plant
sections .......................................................................................................................... 218
Figure 10-28: Example of PROFINET forwards documentation, physical topology

plan ................................................................................................................................. 219
Page 11 / 242
Figure 10-29: Example of PROFINET forwards documentation, logical topology
plan ................................................................................................................................. 219
Figure 10-30: Example of PROFINET forwards documentation, ring topology ......... 220
Figure 10-31: Example of PROFINET forwards documentation, information in cases

of faults ........................................................................................................................... 227
Figure 10-32: Example of PROFINET forwards documentation, diagnostic port

example .......................................................................................................................... 228
Figure 10-33: Example of PROFINET forwards documentation, IT security

assessment .................................................................................................................... 229
Figure 10-34: User interface of the network load calculation tool .............................. 233
Figure 10-35: Network load calculation using average values ................................... 235
Page 12 / 242
List of tables
Table 1-1: Symbols for structuring the text.................................................................... 23
Table 1-2: Symbols for components............................................................................... 24
Table 1-3: Symbols for PROFINET cables ...................................................................... 27
Table 1-4: Symbols for areas .......................................................................................... 28
Table 2-1: Differentiation between application and communication ............................ 39
Table 2-2: Differentiation between application and communication ............................ 40
Table 2-3: Connection technologies for PROFINET devices ........................................ 44
Table 2-4: Benefits of both switch connection options ................................................. 47
Table 3-1: Minimum required separation distances for PROFINET cables according
EN 50174-2:2018............................................................................................................... 62
Table 3-2: Factor P for power cabling............................................................................. 63
Table 3-3: Specific attenuation of fiber types ................................................................ 66
Table 3-4: Attainable transmission links of optical fiber types..................................... 67
Table 3-5: Maximum permissible PROFINET end-to-end link attenuation ................... 68
Table 3-6: Attenuation of splices and connector pairs.................................................. 69
Table 3-7: Use of different fiber types ............................................................................ 70
Table 3-8: Transmission link length and connector pairs (copper) .............................. 72
Table 3-9: Transmission link length and connector pairs (FO)..................................... 73
Table 5-1: Features of different APL network structures .............................................. 94
Table 6-1: Maximum line depths with “Store and Forward” switches........................ 114
Table 6-2: Maximum line depth with “Cut Through” switches.................................... 114
Table 6-3: Generated cyclic real-time network load (typ. PROFINET packet size 60
byte of PROFINET payload data, 100 Mbit/s) ............................................................... 120
Table 6-4: Limit values for the network load of cyclic real-time communication ...... 121
Table 6-5: Categories of congestion loss..................................................................... 135
Table 6-6: Planning steps to avoid / reduce congestion loss ..................................... 137
Table 8-1: Private IPv4 address ranges ........................................................................ 156
Table 8-2: Overview of number of PROFINET network nodes .................................... 159
Table 8-3: Address selection in automation plant 1 .................................................... 162
Table 10-1: Cable parameters PROFINET Type A copper cable ................................. 168
Page 13 / 242
Table 10-2: Cable parameters PROFINET Type B copper cable ................................. 169
Table 10-3: Cable parameters PROFINET Type C copper cable ................................. 169
Table 10-4: Cable parameters PROFINET 8-core Type A copper cable...................... 170
Table 10-5: Cable parameters PROFINET 8-core Type B copper cable...................... 170
Table 10-6: Cable parameters PROFINET 8-core Type C copper cable...................... 171
Table 10-7: Mechanical properties of PROFINET copper cables ................................ 172
Table 10-8: Mechanical properties of single / multimode FO ...................................... 180
Table 10-9: Mechanical properties of POF optical fibers ............................................ 181
Table 10-10: Mechanical properties of PCF optical fibers........................................... 181
Table 10-11: Types of FO cables ................................................................................... 183
Table 10-12: Material list copper-based cabling .......................................................... 196
Table 10-13: Material list FO cabling ............................................................................ 198
Table 10-14: Calculation of end-to-end link attenuation for single-mode fibers........ 200
Table 10-15: Calculation of end-to-end link attenuation for polymer fiber links........ 201
Table 10-16: Further information on the devices in the topology............................... 213
Table 10-17: Example of PROFINET forwards documentation, preliminary

considerations ............................................................................................................... 214
Table 10-18: Information in the title box in accordance with [ISO 7200] .................... 216
Table 10-19: Proposal for title box in accordance with [ISO 7200] ............................. 217
Table 10-20: Table 1 9: Example of title box in accordance with [ISO 7200].............. 217
Table 10-21: Example for PROFINET forwards documentation, information related

to the ring topology ....................................................................................................... 220
Table 10-22: Example for PROFINET forwards documentation, additional device

information ..................................................................................................................... 222
Table 10-23: Example for PROFINET forwards documentation, enhanced device

information ..................................................................................................................... 224
Table 10-24: Example of PROFINET forwards documentation, cable list .................. 226
Page 14 / 242
Introduction
1 Introduction
Page 15 / 242
Introduction
1.1 Preface
The goal of this PROFINET Design Guideline is to support engineers who have to design
PROFINET automation systems, to facilitate the professional design of plants and to serve as
a helpful guide for the step-by-step design of a plant.
The information is presented in a way which tries to be as brief and easy to understand as
possible. It is nevertheless assumed that users have basic knowledge of PROFINET
technology, electrical engineering and network technology.
This guideline is not intended as a PROFINET compendium. If you need more detailed
information about PROFINET, please use the appropriate documents published by
PROFIBUS Nutzerorganisation e.V. or comparable technical literature. This guideline does
not cover the installation and commissioning of PROFINET. Please refer to the PROFINET
Installation Guideline (Order No.: 8.072) and the PROFINET Commissioning Guideline
(Order No.: 8.082) for more details. Information with respect to functional bonding and
shielding for PROFIBUS and PROFINET can be found in the guideline with the same title
Order No.: 8.102.
This Design Guideline does not replace any previous documents. It is intended as an
application-oriented complement to the other guidelines. The previous PNO documents
therefore continue to be valid.
Page 16 / 242
Introduction
1.2 Liability exclusion
PROFIBUS Nutzerorganisation e.V. (PROFIBUS user organization, hereinafter in this

disclaimer referred to as “PNO”) has taken utmost care in the preparation of this document
and compiled all information to the best of its knowledge. This document is nevertheless based
on present knowledge, is of an informative character and is provided on the basis of liability
exclusion. This document may be subject to change, enhancement or correction in the future
without any expressive reference.
This document has no normative character. It may be useful in certain operating environments,
in certain technical constellations or when used in certain countries to deviate from the given
recommendations for action. In this case, the installer and operator of the installation should
weigh up the advantages and disadvantages of the recommendations made in the specific
application and, if deemed appropriate, decide on the implementation of a different solution if
necessary.
The user may not distribute, rent or make available the Information in any other way to any
third party at any time.
Any liability for defects as to quality or title of the information, especially in relation to the
correctness or absence of defects or the absence of claims or third-party rights or in relation
to completeness and/or fitness for purpose are excluded, except for cases involving gross
negligence, willful misconduct or fraudulent concealment of a defect. Any further liability is
excluded unless required by law, e.g. in cases of personal injury or death, willful misconduct,
gross negligence, or in case of breach of fundamental contractual obligations.
Page 17 / 242
Introduction
1.3 PNO documents
[PNO2022] Application Layer protocol for decentralized periphery
Technical Specification for PROFINET IO. Version 2.4 MU3. Order No. 2.722.
[CCA2008] Conformance Class A Cabling Guideline
Order No.: 7.072, Version 1.0, July 2008
[APL2021] Ethernet-APL Engineering Guideline
Order No.: 8.122, Version 1.11, Dec. 2021
[APS2021] Ethernet APL Port Profile Specification
Order No.: 2.662, Version 1.0, June 2021
[EMC2022] Functional Equipotential Bonding and Shielding of PROFIBUS and

PROFINET
Order No.: 8.102, Version 3.1, Sept 2022
[HIG2020] High Availability Guideline for PROFINET
Order No.: 7.242, Version 1.2, February 2020.
[PLM2008] Physical Layer Medium Dependent Sublayer on 650 nm Fiber Optics
Order No.: 2.432, Version 1.0, January 2008
Page 18 / 242
Introduction
[PCI2021] PROFINET Cabling and Interconnection Technology
Order No.: 2.252, Version 5.0, May 2021
[PNC2022] PROFINET Commissioning Guideline
Order No.: 8.082, Version 1.53, Sept 2022
[PNI2022] PROFINET Installation Guideline
Order No.: 8.072, Version 2.12, Sept. 2022
[MRE2018] PROFINET Media Redundancy Guideline for PROFINET
Order No.: 7.212, Version 1.03, April 2018
[PNS2013] PROFINET Security Guideline
Order No.: 7.002, Version 2.0, November 2013
[PSD2018] PROFINET System Description – Technology and Application
Order No.: 4.132, November 2018
Page 19 / 242
Introduction
1.4 Referenced standards
[EN 50174-2]:2018
Information technology - Cabling installation - Part 2: Installation planning and practices inside
buildings
[EN 50174-3]:2013 + A1:2017
Installation technology – Cabling installation - Part 3: Installation planning and practices

outside buildings
[EN 50310]:2016 + A1:2020
Application of equipotential bonding in buildings with information technology equipment
[IEC 11801-3]:2017 + AMD1:2021 CSV
Information technology - Generic cabling for customer premises – Part 3: Industrial Premises
[IEC 60364-4-41]:2005+AND1:2017 CSV
Low voltage electrical installations - Part 4-41: Protection for safety - Protection against electric
shock
[IEC 60364-5-54]:2011 + AMD1:2021 CSV
Low-voltage electrical installations - Part 5-54: Selection and erection of electrical equipment
- Earthing arrangements and protective conductors
Page 20 / 242
Introduction
[IEC 60529]:1989 + AMD1:1999 + AMD2:2013
Degrees of protection provided by enclosures (IP Code)
[IEC 61140]:2016
Protection against electric shock - Common aspects for installation and equipment
[IEC 61300-3-4]:2012
Fiber optic interconnecting devices and passive components - Basic test and measurement
procedures - Part 3-4: Examinations and measurements - Attenuation
[IEC 61156-13]: xxxx (Not yet released)
Multicore and symmetrical pair/quad cables for digital communications – Part 13: Symmetrical
single pair cables with transmission characteristics up to 20 MHz – Horizontal floor wiring -
Sectional specification.
[IEC 61158-2]:2014
Industrial communication networks – Fieldbus specification – Part 2: Physical layer

specification and service definition
[IEC 61918]:2018
Industrial communication networks – Installation of communication networks in industrial

premises.
[IEC 61784-5-3]:2018
Industrial communication networks - Profiles - Part 5-3: Installation of fieldbuses – Installation

profiles for CPF 3
Page 21 / 242
Introduction
[IEE802.1Q]
IEEE 802 LAN/MAN Standards Committee, IEEE 802.1Q-2018: IEEE Standard for Local and
Metropolitan Area Networks—Bridges and Bridged Networks, 2018.
https://standards.ieee.org/standard/802_1Q-2018.html.
[IEEE P802.3cg]: 2019
IEEE Standard for Ethernet Amendment 5: Physical Layer Specifications and Management
Parameters for 10 Mb/s Operation and Associated Power Delivery over a Single Balanced
Pair of Conductors. https://standards.ieee.org/standard/802_3cg-2019.html
[RFC_5681]
Allman, et al.: RFC 5681 - TCP Congestion Control.
https://datatracker.ietf.org/doc/html/rfc5681.
Page 22 / 242
Introduction
1.5 Symbols and their meaning

The figures used in this guideline will help you better understand the text. In addition, symbols
for text structuring will be used. These symbols highlight important text passages or
summarize certain sections.
1.5.1 Symbols for structuring the text
Table 1-1: Symbols for structuring the text
Symbol Name Meaning
Tip Used to mark a recommendation and / or

summary of the current topic.
Important Used for information which, if not observed,

may result in malfunctions during operation.
Instruction Used for direct instructions.
Danger! Used to mark a danger to life and health. The

observance of an instruction marked in this way
is extremely important!
Page 23 / 242
Introduction
1.5.2 Symbols for components
Table 1-2: Symbols for components
Symbol Name Meaning
Operator Command and control station

console
IO Supervisor An engineering station or PC with commissioning

and diagnostic functions for PROFINET
Controller A device (typically a control unit) that initiates the IO

data traffic.
Router Network component for interconnecting data traffic

between different sub-networks.
Switch Device for the interconnection of several PROFINET

devices. Eight respective four ports for copper
media.
Switch Device for the interconnection of several PROFINET

devices. Six ports for Copper-Media plus two ports
for fiber optic media
Power APL power Ethernet switch. Converts Industrial Ethernet to

switch Ethernet-APL. Needs auxiliary power to power the
subordinate APL network. Indicated by thick green
APL
arrow.
Page 24 / 242
Introduction
APL field This Ethernet-APL field switch connects to the APL

switch without Trunk to Ethernet-APL field devices (Spurs) and
auxiliary power provides power for the APL field devices connected
supply to the switch. Receives energy via a powered trunk
APL field This Ethernet-APL field switch with auxiliary power

Power switch with supply connects the Industrial Ethernet or the
auxiliary power unpowered APL trunk with the Ethernet-APL field
supply devices (Spurs) and provides power for the APL
APL
field. The switch is connected to auxiliary power and

does receive power neither via the unpowered APL
trunk nor the industrial Ethernet.
Device A locally assigned field device that is allocated to a

PROFINET controller. This can be e. g. a remote IO,
a drive or a panel display.
APL field APL field device, (e.g. temperature transmitter,

device pressure transmitter, flow transmitter, positioner),
with Ethernet-APL interface. Device is powered and
communicates via Ethernet-APL. Transmitters with
external power supply (four wire transmitters) are
possible, but will not be handled separately
Page 25 / 242
Introduction
WLAN access A device that allows changing over from wired to

point wireless communication.
Device with Local field device with WLAN.

WLAN
Media converter Converter from one physical medium to another,

e. g. from copper to fiber optic media.
TAP Abbreviation of “Test Access Point”.
Device for reading the network traffic without causing

any impact
Video camera Device for image-based monitoring
Control station Standard PC with control functions
Server Server computer, e.g. for backup tasks.
Page 26 / 242
Introduction
1.5.3 Symbols for PROFINET cables
Table 1-3: Symbols for PROFINET cables
Symbol Name Meaning
Standard Ethernet Standard Ethernet connection which does not

involve the PROFINET protocol
PROFINET PROFINET Industrial Ethernet cable with copper

copper cable wires
Sheath color: green
The dotted line indicates a connection with

increased determinism requirements.
FO Fiber-optic cable
Sheath color: green
Note: for easier differentiation between copper

and FO, the FO are highlighted orange in this
guideline although the cable sheath is usually
green.
APL Ethernet-APL Ethernet-APL connection without Ex

cable without Ex qualification. (used for Trunk and Spur)
qualification
Sheath color: not defined.
Page 27 / 242
Introduction
APL Ex e Ethernet-APL with Ethernet-APL connection that can run in areas

increased safety with explosive atmosphere. Increased safety (Ex
(Ex e) e / non incendive). (used for Trunk)
The dotted line indicates an inactive ring

redundancy connection for increased availability
requirements.
Ethernet-APL with Ethernet-APL connection that can run in areas

Ex i or I.S.
intrinsic safety with explosive atmosphere. Intrinsic safety.
(Ex i) (Used for APL-spurs)
Conductive link Electrically conductive link
1.5.4 Symbols for areas
Table 1-4: Symbols for areas
Symbol Name Meaning
Area where the occurrence of electromagnetic inter-

EMI EMI
ference (EMI) must be expected.
Page 28 / 242
Introduction
1.6 About the structure of this guideline

The structure of this guideline corresponds to the design process. This process will be followed
step by step, while each modification in a later process shows a possible implication on the
previous steps. Figure 1-1 shows the structure of the design process.
Figure 1-1: Design structure
The chapters of this design document follow this procedure. While chapter 1 contains an
introduction, the following chapters go from general issues to the details of the design process.
The chapters highlight the following issues:
Chapter 2: This chapter starts with a preview and analysis of the process to be automated.
The properties and the placement of the automation components are described.
Chapter 3: This chapter includes the topology definition of the automation plant based on the
findings gathered in chapter 2.
Chapter 4: The existing basic design is extended by such cases which are typically not part
of PROFINET.
Page 29 / 242
Introduction
Chapter 5: In order to ensure the performance in a PROFINET network, based on the

previous chapters, the PROFINET design aspects relevant for the performance are
considered.
Chapter 6: PROFINET offers a multitude of possible applications for additional functions

which require a special consideration. The chapter provides an overview of these functions.
Chapter 7: This chapter describes a careful planning of name and address assignment
Chapter 8: This provides a short summary of design results.
The annex (chapter 9) of this document also provides additional information about different
components and their properties which are used in a PROFINET network. This includes
information such as cable parameters or application examples for cable design and many
more.
An index is provided in chapter 10 to facilitate the search for topic-related information in the
guideline.
Page 30 / 242
Introduction
1.7 Goal of the guideline

The main goal of this guideline is to help you to select devices and networking components
for a PROFINET system, and to design and layout the system to give reliable performance
and allow easy installation, commissioning and maintenance.
After completion of the design process, the following information should be available or be
generated.
• Plant design
• Topology
• Selection of components
• Selection of transmission medium
• Selection of connectors
• Communication relations
• Estimate of data volumes to be transmitted
In case any of this information should be missing, the design process has to
be restarted at the relevant position.
Page 31 / 242
Analysis and preliminary considerations
2 Analysis and preliminary considerations
Page 32 / 242
Before you can start …
…you need an overview of your project. For example this may include the physical layout, a
plan of the plant or the plant schematics.
This information provides a first idea of the extent of the PROFINET network to be designed.
The goal of the next section is to analyze and to describe the process to be automated.
The properties and the placement of the individual automation components will be defined. In
addition, information will be provided about the points to be considered when selecting the
components.
As a rule, bear in mind that PROFINET design is an iterative process

followed step by step. If required, the process has to be repeated several
times.
2.1 Determination of automation components

In the following step, the designer has to determine the components for plant automation.
First, each component needs to be appropriately placed based on the plant design information
or the building floor plan.
For example:
Controller placement in a separate switch cabinet away from the process or together with other
PROFINET devices close to the process, remote I/O placed close to the process or in a remote
cabinet, display panels for control close to the process or geographically remote for
monitoring, etc.
Page 33 / 242
The required components should then be added to the layout plan of the automation plant.
After this, the components should be grouped to allow for geographical and functional
component assignment.
The geographical assignment is usually created by considering the geographical proximity in

the layout plan. The functional assignment is determined via common control tasks which can
be determined from the mutual data exchange between control and periphery. It also makes
sense to create a functional grouping according to the conformance classes (see next
chapter).
Figure 2-1: Floor plan of a plant with pre-placed components
In Figure 2-1, the initial placement of the automation components has been completed with
the PROFINET devices positioned according to the task in the automation plant.
Page 34 / 242
Figure 2-2: Sample layout plan of a plant with special assignment
Figure 2-2 shows the geographical and functional assignment of components. In this example,
the automation plant is sub-divided into two islands. The chosen arrangement depends upon
local conditions which may occur, in this case, different plant areas.
The relationship between the controllers in automation island B does not only require a
geographical differentiation, but also a functional differentiation - a fact that is indicated by the
additional gray frames in automation island B. Another example might be a common task
within the plant part but where each individual part has to meet different requirements.
There is also an additional geographical separation within the second plant part in automation
island B since the PROFINET devices must be positioned separately from the rest.
It is furthermore necessary to identify any communication relations that are required between
the control systems. These relations are shown as arrows in the example. At a later stage of
design, you have to check whether the required communication relation can be realized for
the selected devices. If this is not the case, you have to foresee additional hardware
components.
Direct communication between the control systems is required within island B, it is also
necessary for these controllers to communicate with the control system within island A.
Page 35 / 242
At this point, the components are not interconnected, but only positioned in
the automation plant and combined to groups with different functionalities.
Mark the areas with increased requirements, e.g. determinism, to ensure

they can be considered separately during the design.
2.2 Device selection

Depending on the required positions of the automation components within the plant, the
PROFINET devices can now be selected. This chapter describes the preselection of
PROFINET network nodes and their properties.
In general, the following criteria should be observed:
• Conformance Class
• Time request
• Consideration of device function
• Feasibility of the required communication relations
• Type of connection of PROFINET device (copper cable or FO with appropriate
connection technology)
• Protection class of device
• other specifications
The preselection of devices according to the following criteria makes sure

that your components are able to fulfill the automation task. You should also
check the manufacturer data of the selected devices for possible restrictions
and requirements.
Page 36 / 242
2.2.1 The PROFINET Conformance Classes
The functionality of the PROFINET components has been categorized into application classes
or so-called Conformance Classes (CC). The target of these categories is to define reasonable
functionalities in order to narrow down the decision criteria for plant operators when using
PROFINET components.
For detailed information on the individual conformance classes, please use

the document “PROFINET Conformance Classes” (Order No.: 7.041)
provided by the PROFIBUS User Organization.
After assigning an application to a CC, the user can select a number of components, which
definitely meet the defined minimum requirements. All CCs already have a certain basic
functionality. This may e.g. include:
• Cyclic data traffic

• Acyclic data traffic
• Identification and maintenance functions
• Prioritization of data traffic
• Basic mechanism for neighborhood screening and device swapping
Another grading has been added to these basic functions. So each conformance class (CC-
A, CC-B, CC-C) defined different functionalities.
In general, these classes cover content such as
• the type of communication (TCP/IP and real-time communication),

• the transmission medium (copper, FO, wireless) used,
• synchronized communication and
• the redundancy behavior.
Figure 2-3 shows the structure of the conformance classes as well as an extract of their
functionality.
Page 37 / 242
Figure 2-3: Classification and content of the individual conformance classes
As you can see from the figure, CC-B includes the functionality of CC-A. The same is true for
the functionality of CC-C which in turn includes the functionality of CC-B and this also CC-A.
You should define the conformance class of each device in the design
phase. To ensure that the required functionality will be available in a certain
PROFINET device.
Mark the plant parts that are subject to special requirements. You should
check whether the conformance class you have defined really covers this
requirement profile, and adjust the selection of PROFINET devices
accordingly.
Page 38 / 242
2.2.2 Special timing requirements
General information on communication
While a real-time channel is used for cyclic transmission of process data, PROFINET offers
an additional channel based on standard Ethernet communication (standard channel) for
acyclic services such as parameterization and diagnosis. Table 2-1 shows the basic
differences between these two communication channels.
Table 2-1: Differentiation between application and communication
Standard channel Real-time channel
Reading of diagnostic data Cyclic data exchange
Acyclic data exchange Synchronous data exchange
Device parameterization Alarms
PROFINET also enables unrestricted open TCP/IP data traffic (non real-time data traffic), with
real-time communication getting higher priority compared to non real-time communication.
In addition to the terms mentioned above, the following terms have been established for
PROFINET transmission technologies:
IRT: Isochronous real-time, for a cyclic data transmission which is the basis of a
synchronous application.
RT: Real-time for a cyclic data transmission.
NRT: Non real-time for an acyclic data transmission (e.g. TCP / IP, UDP / IP).
For more detailed information about the structure of communication and the
properties of data channels, please use appropriate literature.
Page 39 / 242
Definition of the timing requirements
Depending on the target group, PROFINET devices face different requirements in terms of
timing. In general we distinguish between the timing of the application on the automation plant
and the communication on PROFINET.
Table 2-2: Differentiation between application and communication
Communication Application
Real-time (RT) Non-synchronous application
Isochronous real-time Non-synchronous or synchronous application

(IRT)
The communication and the application have to be fit to each other.
A synchronous application can be only be realized via an isochronous communication.
To facilitate the selection of PROFINET devices, the various conformance classes include
appropriate communication request profiles, starting from CC-A with a simple standard
Ethernet transmission, up to CC-C for synchronous transmission.
Page 40 / 242
Figure 2-4: Coverage of communication timing requirements
Since every higher level CC includes the functionality of the lower level CC, any higher level
CC provides enhanced communication functionality (e.g. LLDP, SNMP). To make sure that
the PROFINET devices meet these requirements profiles, the device manufacturer has to
carry out a certification test.
Always use certified PROFINET devices with the appropriate requirement

profile. You can thus make sure that these devices have been configured
for the relevant automation task. You should determine which requirement
profile your PROFINET devices have to meet.
Page 41 / 242
2.2.3 Further criteria for device selection
Further important criteria for the selection of devices will be explained in more detail on the
following pages. This includes points such as:
• End user specifications,

• Environmental requirements,
• Connection to PROFINET device,
• PROFIsafe and
• PROFINET devices with integrated switch.
End user specifications concerning device selection
In many cases, the requirement profile of an automation plant has been predetermined. In
such cases it is common practice for the design or the selection of devices to use so-called
approval lists which are provided by the end user. These lists include the components
approved by the end user. The goal of such an approval list is:
• to reduce the selection process time and effort,

• to use homogeneous components in the entire plant and
• to always have the same requirement profile available.
Device selection specifications provided by the end user must always be observed. It is also
important that the approval lists correspond to the specifications of the conformance classes.
You should check whether the latest version of approval lists is available to
you.
Page 42 / 242
Environmental requirements for the PROFINET device
Environmental aspects must also be considered for the selection of PROFINET devices when
planning an automation plant. With reference to the location of the devices, we basically
differentiate between the installation in a cabinet and the unprotected installation in the plant
environment.
Both environments imply certain requirements for the nodes of the PROFINET network.
• Penetration of foreign objects and liquids (IP protection class).

• Mechanical requirements, e.g. vibration, shock
• Temperature influences
• Electromagnetic influences
In order to optimize your device selection, mark those areas of the plant that
generate special requirements for the PROFINET device to be installed.
For the device selection, consider potential external influences. Adjust your
device selection according to the manufacturer information.
Page 43 / 242
Type of connection at the PROFINET device
PROFINET supports many different types of connection to the network. Copper cabling is
normally used for the connection of PROFINET devices. Optical fiber and wireless
communication can also be used.
Several connection technologies are available when using wired transmission media. These
connection technologies can be categorized according to their transmission medium, as
shown in Table 2-3.
Table 2-3: Connection technologies for PROFINET devices
Copper cable connections Optical fiber connections
M12 M12
RJ45 (IP20) SCRJ (IP20)
Push-Pull-RJ45 (IP65) SCRJ Push-Pull (IP65)
The connection technology is determined by the selected PROFINET

device. In a later design step, additional media converters may be necessary
due to certain topology or environmental requirements.
All connectors and cables are PROFINET components that require a

manufacturer declaration concerning the compliance with PROFINET
standards.
Take a note of the connection technology of the selected device since this
may require adaptation at a later stage.
Page 44 / 242
PROFIsafe via PROFINET
PROFIsafe is a standard for safety-relevant communication. It ensures that people and

machinery will not suffer any damage during the operation of an automation plant. PROFIsafe
equipment can be mixed with non PROFIsafe equipment within your PROFINET network.
Figure 2-5 shows an example of the use of PROFIsafe devices in a PROFINET network.
Figure 2-5: Use of PROFIsafe via PROFINET
The safety-relevant PROFIsafe communication (yellow) is transmitted over the same network
as the standard PROFINET communication. All nodes of the safety-relevant communication
must be certified according to IEC 61010 (the equipment CE label).
For the device selection you should consider safety-relevant aspects to

ensure that damage to people and machinery has to be averted during
operation. PROFIsafe devices must be both PROFINET and PROFIsafe
certified.
You will find more information about PROFIsafe in the IEC 61784-3-3 as
well as under www.PROFIsafe.net.
Page 45 / 242
Use of switches or integrated switches
PROFINET devices are connected to the network via switches. Switches route the PROFINET
data traffic through the network. Many devices offer the functionality of an integrated switch.
Figure 2-6 shows the difference between the connection via an integrated switch or via a
separate switch.
Figure 2-6: Difference integrated switch and separate switch
While a system based on integrated switches does not require any additional component for
routing, a device without integrated switch may require an additional separate switch.
Note that when using integrated switches in a line structure, device failure or replacement can
cause all devices downstream from the failure to also fail. Generally a star or tree structure
using separate switches gives improved availability in the event of device failure and
replacement.
PROFINET devices equipped with an integrated switch can provide different

numbers of ports.
Page 46 / 242
Use the plan to check whether additional switches may be required.
Check whether your plant consists of independent plant parts. Plant parts
should be linked in a star or tree topology.
Table 2-4 lists the benefits of switch connection options.
Table 2-4: Benefits of both switch connection options
Benefits of separate switches Benefits of integrated switches
Replacement of defective network nodes is Cost reduction since no additional switch is

possible without interruption of the remaining required.
communication for star and tree topologies.
Replacement of defective network nodes
without interruption of the remaining
communication is possible for line topology
with ring redundancy.
Separate switches are required if your PROFINET devices are not equipped with integrated
switches or if it is necessary due to the distribution of network nodes within the plant.
The requirements for system availability during device failure and

replacement will often dictate when you should use integrated or separate
switches.
The selection criteria of the PROFINET network nodes with respect to

device properties and environmental requirements must also be determined
for separate switches.
You should define a suitable number of additional separate switches for the
future definition of the network topology.
Page 47 / 242
Conformance class B requirements, where applied, means that switches

have device properties. That is they have a PROFINET device name and
are capable of providing diagnostic data. If separate switches need to
comply with conformance class B, additional information is provided in the
Annex of this document.
2.3 Definition of device types

Devices can now be selected based on the information available concerning the plant as well
as the environmental conditions and the requirements to the automation task.
Figure 2-7: Sample layout of a plant with device preselection
Figure 2-7 shows the example plant with devices preselected. It also shows the assignment
to different conformance classes and their timing requirements. Further analysis shows that
some devices are equipped with integrated switches.
In this example the automation island A is assigned to the requirements of CC-B. Island B is
also subject to these requirements. However, in this case a plant area is subject to more
deterministic timing requirements. The area is there for categorized as conformance class C.
Page 48 / 242
The preselected devices may have to be modified at a later stage in order

to adjust the connection technology and the transmission medium to the
requirements.
You should make a further check that all the positioning and device
requirements have been met.
During the design you should take into account the grounding as well as an
equipotential bonding for the network nodes. In the Annex of this document
you will find information about power supply and grounding of network nodes
in PROFINET systems.
Page 49 / 242
2.4 Documentation of results

After completion of the analysis and preview of the automation task, all information concerning
device selection should be available. This includes device information such as
• Device connection or transmission medium (copper, POF, HCS, optical fiber (mono-
mode, single mode) or wireless),
• Number of integrated switch ports at the PROFINET device and
• The conformance class requirements.
In the automation task, mark the PROFINET devices and the related
applications that are subject to high real-time requirements. These devices
must be considered separately during the design process.
Detailed planning of device characteristics, options and parameters are not

required at this point. These will be covered later.
All relevant information on the selected PROFINET devices and network

components should be collected and documented at this stage. A list of
selected devices and their properties should be generated.
Page 50 / 242
Network topology
3 Network topology
Page 51 / 242
Network topology
This chapter is preceded by the analysis of the automation project. The first step was to
determine which components will be used in the plant.
As part of the progressing more detailed planning, the next step is to create the network
topology for the plant. First, some general topology examples are discussed, followed by a
brief overview of the transmission media that can be used and their most important properties.
This is followed by concrete examples of typical network topologies in automation plants.
Once the topology and the transmission media to be used have been defined, a check is made
to see whether the network devices selected in Chapter 2 permit the connection of the selected
transmission media.
Finally, the topology planning is documented.
The information on transmission media and connectors considered here is

only a brief outline of the most important information.
Please consult the appropriate source (e.g. the manufacturer) for more
detailed information.
Page 52 / 242
Network topology
3.1 PROFINET topology
Additional switches may be required to create the topology.
The following pages of this section will introduce the different basic PROFINET topologies.
Flexibility in network design and layout is a key feature of PROFINET. Since all standard
Ethernet topologies are used, PROFINET supports an almost unlimited number combination
options.
The network topology mainly results from criteria such as:
• The location of the components,

• the distances to be covered,
• the EMC requirements,
• electrical isolation requirements,
• conformance class requirements,
• requirements for increased availability and
• consideration of network loads.
The selection of the correct topology is important for the future design of the
PROFINET automation plant. The topology may have to be adjusted in a
later design step.
To set up the topology, additional switches might be necessary
Page 53 / 242
Network topology
The different basic topologies of PROFINET are presented on the following pages of this
section.
Star topology
The star topology is suitable for areas with limited geographical extension. A star-topology is
automatically created if several communication nodes are connected to a common switch.
Figure 3-1: Star topology
If a single PROFINET node fails or is removed, the other PROFINET nodes will continue to
operate. However, if the central switch fails, the communication to all the connected nodes will
be interrupted.
Page 54 / 242
Network topology
Tree topology
A tree topology is created by combining several star-shaped networks to one network. Plant
parts forming a functional unit are combined to star points. These are inter-networked via
neighboring switches.
Figure 3-2: Tree topology
One switch operates as a signal distributor in the star point. Since the switch routes messages
based on an address, only those messages will get to a neighboring distributor which are
really required at this distributor.
The tree topology is a typical example for an automation plant being grouped
into different manufacturing islands.
Page 55 / 242
Network topology
Line topology
The line is a well-known topology used in automation. It is used for applications in extensive
automation plants such as conveyor belts, but also for small machine applications. PROFINET
devices equipped with an integrated switch facilitate the realization of line topologies.
Figure 3-3: Line topology
The line is a well-known topology used in automation. It is used for applications in extensive
automation plants such as conveyor belts, but also for small machine applications. PROFINET
devices equipped with an integrated switch facilitate the realization of line topologies.
When using line topologies, bear in mind that in case of a line interruption
(e.g. outage of a device), the devices located behind the failed device can
no longer be contacted. This can be prevented by extending the line to a
ring structure using a redundancy protocol.
Page 56 / 242
Network topology
3.2 Applicable transmission media

Copper cables and optical fibers are available for a wired connection of network nodes. The
cable used must meet the requirements of the planned automation project. For this purpose,
the cable manufacturers offer a range of PROFINET cables that are differentiated by their
applications and special properties.
The following section describes the main considerations when selecting the PROFINET
copper and optical fiber cabling. Compared to copper cabling, the optical fiber cabling has
additional typical parameters such as attenuation and used wavelength which primarily restrict
the length of the transmission link.
In the Annex to this document, in addition to an overview of typical cable properties you will
find a description of the transmission media as well as their application ranges and versions.
When selecting the transmission medium you should bear in mind the
possible influences in the application area (e.g. chemical, electrical or
mechanical).
Some examples are provided in the annex to illustrate the selection of

cabling components. Pre-assembled and field-assembled cables are also
described.
The correct installation of the PROFINET cabling must be considered in the

design. Make sure the allowed distance between power cables and data
cables will not be undercut. For more information, please see the
PROFINET Assemblling Guideline Order No.: 8.072.
Page 57 / 242
Network topology
A PROFINET connection between two devices is named “end-to-end link” if

the two connectors at the end of the cable are considered. A channel is a
connection that excludes the two connectors at the end of the cable. .
At this the channel can consist of different transmission mediums like copper
or fiber optical cables.
3.2.1 PROFINET copper cabling (4-core, 8 core)
A typical PROFINET copper cable is a 4-core, shielded copper cable (star quad). For high
transmission rates (1000 Mbit/s) an 8-core cable is specified. The different types of cables
vary in.
• the structure of the wires (solid core / stranded for fixed / flexible applications)
• and / or the jacket material and construction.
The cores are color-coded. In a 4-core cable, wire pair 1 is yellow and orange, wire pair 2 is
white and blue. The cores in each pair are arranged to be diametrically opposite within the
cable. 8-core PROFINET copper cables consist of 4 wire pairs, with green, blue, orange and
brown wires and the corresponding white wire.
As in standard Ethernet applications, the maximum distance between the end points of
communication is limited to 100 m when using copper cabling. This transmission link has been
defined as PROFINET end-to-end link.
For automation plants you may only use PROFINET cables.
The corresponding manufacturer's declaration is available for PROFINET

cables.
Page 58 / 242
Network topology
Application-neutral cabling (e.g. based on existing building cables) may only

be used in network areas that correspond to conformance class A (e. g. to
interconnect automation islands).
However, it is recommended to use PROFINET cabling for this application

(e.g. in order to cover higher conformance class requirements).
The common installation of power cables and copper cables for

communication is subject to regulations in order to minimize the
electromagnetic influence of power cables on the communication lines.
Optical fibers however are not subject to these electromagnetic influences
(see chapter 3.2.4).
Regulations for the common installation of power cables and PROFINET

copper cables must be observed for the design of cable routing.
Follow the instructions provided in the PROFINET Installation Guideline

Order No.: 8.072.
Cable types
PROFINET copper cables are categorized in different types which are mainly differentiated by
the relevant applications:
Type A cables are designed for fixed installations. This cable type is not subject to any motion
after being installed.
Type B cables are designed for flexible installations. This cable type allows for occasional
motion or vibrations. When vibrations occur, use this type of cable because it is less
susceptible to vibrations.
Page 59 / 242
Network topology
Type C cables are designed for special applications (e.g. for continuous movement of the
cable after being installed). This includes e.g. applications such as trailing chains or festoons.
Special properties of some copper cables, such as flexibility for use in

trailing chains or construction using flame retardant materials, can reduce
the maximum length of a copper cable to less than 100 m.
Observe the manufacturer data for cables and connectors.
In addition to the special properties of PROFINET copper cables, the Annex

of this document provides detailed data concerning the individual cable
types.
Types of PROFINET copper cables
A number of special cable types are available for PROFINET. The most commonly used
PROFINET cable types as well as their applications are listed below:
• PE cables: PE cables are suitable for installation in areas where constant humidity
must be expected.
• Buried cables
• Flame retardant non-corrosive cables (FRNC cables): Suitable for installation in
areas where special fire protection regulations must be observed, e.g. halls with public
access.
• Trailing cable for installation on moving machine parts.
• Festoon cable
• Ship wiring cable (with approval for shipbuilding): For installation on board ships
and offshore units.
You should only use cables that have been specified as PROFINET cables
by the manufacturer. Only such cables will ensure trouble-free operation of
the network.
Observe the information material provided by the cable manufacturer.
Page 60 / 242
Network topology
You will find further information about the installation and grounding of
copper cabling in the PROFINET Installation Guideline Order No.: 8.072.
3.2.2 Ethernet APL Cables
Ethernet APL defines a two-wire cable to connect sensors and actuators to PROFINET. The
connection provides a data rate of10 Mbit/s and delivers energy to the field devices.
Please check the Ethernet-APL Engineering Guideline [APL2021] for

further details on Ethernet APL cabling.
Page 61 / 242
Network topology
3.2.3 Separation distances between cables
When laying PROFINET copper cables, observe the minimum required separation distances
specified in Table 3-1. The values have been taken from the EN 50174-2 standard. The
minimum distance A between power cable (s) and PROFINET cable is calculated by
multiplying the minimum separation distance S to be taken from Table 3-1 by the factor for the
power supply wiring P from Table 3-2. According to section 11.5.2 of the standard the
recommended distance should be the double of the minimum distance.
Table 3-1: Minimum required separation distances for PROFINET cables according EN 50174-2:2018
Conduits used for information technology cables and mains

power cables
Separation without Open metallic Perforated metallic Solid metallic

electromagnetic conduits a conduits b, c conduits d
barriers
10 mm 8 mm 5 mm 0 mm
a
Shielding effect (0 MHz to 100 MHz) equivalent to welded meshed steel basket with
mesh size 50 mm × 100 mm. The same shielding effect can be achieved using steel
cable trays (cable bundles, without cover) with a wall thickness of less than 1.0 mm
and/or an evenly perforated surface of more than 20%.
b
Shielding effect (0 MHz to 100 MHz) equivalent to a steel cable tray (cable bundles,
without cover) with a minimum wall thickness of 1.0 mm and an evenly perforated
surface of not more than 20%. This shielding effect can also be achieved with
shielded power cables which do not provide the features specified in footnote d.
c
The top surface of the installed cables must be at least 10 mm below the top surface
of the barrier.
d
Shielding effect (0 MHz to 100 MHz) equivalent to a steel installation pipe with a wall
thickness of 1.5 mm. The specified separation distance must be taken into account
in addition to the separation distance required by dividers/barriers.
Page 62 / 242
Network topology
Table 3-2: Factor P for power cabling
Type of electrical circuit Number of circuits Factor for the power supply
a, b, c
cabling P
1 to 3 0,2
4 to 6 0,4
7 to 9 0,6
10 to 12 0,8
13 to 15 1,0
20 A, 230 V, single-phase 16 to 30 2
31 to 45 3
46 to 60 4
61 to 75 6
>75 6
a
Three phase cable must be treated as 3 single-phase cables.
b
More than 20 A must be treated as a multiple of 20 A.
c
Power cables for lower AC or DC power must be treated based on their rating, i.e. H. a
100 A/50 V-DC cable is equivalent 5 of the 20-A-cables (P = 0,4).
As a next step we will look at a calculation example for the recommend distances.
Assumptions:
• Open metallic conduit: according Table 3-1 Minimum distance S = 8 mm

• 20 Power circuits with 20 A each according Table 3-2: Factor P = 2
• Recommended distance is twice the minimum distance according sections 11.5.2 of
the standard.
Page 63 / 242
Network topology
This results in:
Recommended_distance = 2  Minimum_Distance
Minimum_Distance = S  P
Recommended_distance = 2  S  P
Recommended_distance = 2 8 mm 2 = 32 mm
Disclaimer:
The information regarding the minimum cable distances refers to installations in which
PROFINET / PROFIBUS cables run parallel to unshielded power lines over longer distances.
The values given here provide an orientation framework. For shorter parallel cable runs, e.g.
inside machines, with shielded power cables or when using hybrid cables, it is permissible to
stay below the minimum distances.
The application-specific reduced distances must be specified by the manufacturer of the

system cables. This procedure is provided for in EN 50174-2.
For more details about minimum separation distances please refer to the
IEC 61784-5-3 or EN 50174-2 standard, respectively.
Connecting PROFINET cable shields
While the cable types and PROFINET copper cable versions that can be used are determined
by the environmental condition, when laying the PROFINET copper cabling, additional care
must be taken to ensure that the cable shields are correctly connected to the potential
equalization system. This does not apply to optical fibers.
The cable shield must be properly connected to the potential equalization system at both
ends of every cable, i.e. at each connected network node. Usually, the connector collar in
the PROFINET device provides a connection to the connector. If no large-area grounding of
the cable shield is visible on the device, you should ground the cable shield near the device.
Page 64 / 242
Network topology
You will find information about the assembly and the grounding construction
as well as about the equipotential bonding in a PROFINET network in Annex
of this document as well as in the PROFINET Installation Guideline
Order No.: 8.072 as well as in the guideline Functional Bonding and
Shielding of PROFIBUS and PROFINET Order No.: 8.102
3.2.4 PROFINET optical fiber cabling
In areas where electromagnetic interference may be present or significant earth potential

differences are expected it is recommended that fiber optic (FO) connection is used. Fiber
optic connection can completely remove problems caused by electromagnetic interference
(EMI) and/or ground equalization currents flowing in copper cable screens.
Figure 3-4: Application of optical fiber technology for EMI
Figure 3-4 shows the application of optical fiber technology for the connection of network
nodes and / or switch cabinets in areas subject to electromagnetic interference. The benefits
of optical fibers over copper cables are:
• Optical fiber cables usually cover longer distances as compared to copper cables.
• FO cables provide total electrical isolation between plant areas.
• FO cables are totally immune to electromagnetic interference (EMI).
A description of the different fiber types that can be used for the design of the PROFINET
network is provided below
Optical fiber types
Page 65 / 242
Network topology
Four different fiber types can be employed when using optical fibers (FO) for PROFINET. The
fiber types must be selected according to requirements given by the planned automation
project.
The following fiber types are available:
• Plastic optical fiber (POF)

• Glass fiber (multi-mode)
• Glass fiber (single-mode)
• Glass fiber with plastic jacket (hard-cladded silica fiber (HCF) or plastic-cladded fiber
(PCF))
The key parameters of optical fibers are listed below.
Specific attenuation of the fiber
The specific attenuation of the fiber depends on the operating wavelength and is indicated in
dB/km. The maximum values for the different fiber types, based on IEC 61784-5-3, are shown
in Table 3-3.
Table 3-3: Specific attenuation of fiber types
Fiber type Maximum attenuation Wavelength
650 nm
POF ≤ 230 dB/km
(LED excitation)
Multi-mode ≤ 1.5 dB/km 1 300 nm
Single-mode ≤ 0.5 dB/km 1 310 nm
HCF / PCF ≤ 10 dB/km 650 nm
Page 66 / 242
Network topology
Maximum FO transmission path
The maximum FO cable length is limited due to the attenuation of the optical signal within the
fiber. The optical wavelength that is used will also have an effect.
Table 3-4: Attainable transmission links of optical fiber types
Sheath Transmission path

Fiber type Core diameter
diameter (typ. values)
POF 980 µm 1 000 µm up to 50 m
HCF / PCF 200 µm 230 µm up to 100 m
Multi-mode 50 or 62.5 µm 125 µm up to 2 000 m
Single-mode 9 to 10 µm 125 µm up to 14 000 m
The maximum transmission link is a criterion for the design of the optical
fiber link. The maximum PROFINET end-to-end link attenuation of optical
fiber links however is decisive.
Maximum permissible PROFINET end-to-end link attenuation
Table 3-5 summarizes the maximum admissible attenuation values, based on the IEC 61784-
5-3 and IEC 61300-3-4 standard for optical transmission links.
Page 67 / 242
Network topology
Table 3-5: Maximum permissible PROFINET end-to-end link attenuation
Maximum PROFINET end-to-

Fiber type Wavelength
end link attenuation
650 nm
POF 12.5 dB
(LED excitation)
62.5/125 µm : 11.3 dB
Multi-mode optical fiber 1 300 nm
50/125 µm : 6.3 dB
Single-mode optical fiber 10.3 dB 1 310 nm
HCF / PCF 4.75 dB 650 nm
When using optical fiber links, make sure that the maximum permissible
PROFINET end-to-end link attenuation are observed as taken from
IEC 61300-3-4.
These limit values already include attenuation reserves.
Page 68 / 242
Network topology
Additional junctions in optical cables
Additional junctions in the link (splices or plug connections) cause an additional attenuation of
the transmitted optical signal. Plastic optical fiber (POF) and hard-cladded silica are often
assembled in the field using simple tools. This practice has been accounted for by means of
a higher attenuation for the junction. Typical values are shown in Table 3-6.
Table 3-6: Attenuation of splices and connector pairs
Fiber type  Optical fiber Plastic optical fiber /
Connection  Hard-cladded silica / PCF
Per thermal
0.3 dB Not possible
splice connection
Per pair of connectors 0.75 dB 1.5 dB
Page 69 / 242
Network topology
Use of different fiver types
The use of different fiber types in one plant often produces costs due to additional materials
or tools being required. Although it is possible to use various types of fiber in the same plant,
this should only be done in exceptional cases.
Table 3-7: Use of different fiber types
The use of different types of fiber can be The use of different types of fiber should
justified: be avoided:
If, within one plant, numerous links can be If most of the links have to be configured as
realized using plastic fiber and only one link, glass fiber and only a few links can be
due to its length, requires the use of glass realized using plastic fiber. This could cause
fiber. In this case the overall costs would be higher costs due to the additional treatment
higher if all links were realized using glass of the plastic fiber required (tools, material).
fiber.
Attenuation of an optical fiber link
The secure operation of an optical fiber transmission system requires that optical signals
reaching the receiver have sufficient signal strength. The PROFINET end-to-end link
attenuation must not exceed the maximum permissible attenuation value.
The following parameters could have an influence:
• Specific attenuation of the fiber

• Additional junctions in optical cables
In order to achieve reliable communication over optical fibers, the following condition should
be checked.
Transmit power - total attenuation ≥ receiver sensitivity
For short transmission links it may be necessary to check the max. permissible receiver
sensitivity. If required, reduce the transmit power of the transmitter.
Page 70 / 242
Network topology
For the design of an optical fiber link, the specified limit values indicate the
maximum transmission link length. You should also use a simple attenuation
calculation to check the link.
You will find examples for the selection of cabling components for optical
fiber links in the Annex of this document. In addition, you will find an example
for the determination of the attenuation balance.
However, bear in mind that this is only a verification which by no means

replaces potential acceptance measurements.
3.2.5 Selection of required connectors
PROFINET cables are equipped with connectors at both ends. The combination of connectors
at the cable and at the socket is considered as a connector pair.
The connectors at both ends of the cable must also be included. Each of
them forms a pair with the socket of the terminal device.
Detachable connections including bulkhead connectors and transition points

are also part of the cable/connector system. The Annex provides a short
description of such items.
Page 71 / 242
Network topology
Connectors of copper cabling
For the design of your PROFINET network you should bear in mind that the number of
detachable links within an end-to-end link is limited.
Table 3-8: Transmission link length and connector pairs (copper)
If the specified cables are used in combination with the specified connectors,
a maximum cable length of 100 m can be achieved when using up to four
connector pairs. You should try to use as few plug connections are possible
since each plug connection represents a potential disturbance source.
In case more than four connector pairs are required for an application, you
have to make sure that the attenuation values for the entire link are
observed. (channel class-D values)
Page 72 / 242
Network topology
Connectors for optical fiber links
The maximum number of detachable connections for a channel based on optical fiber is
limited, similar to a channel based on copper cabling.
Table 3-9: Transmission link length and connector pairs (FO)
The comparably high attenuation of POF fibers, combined with the

simultaneous use of several connectors, has a large impact on the
maximum length of a POF connection. This should be considered in case
you use POF fibers in a network.
3.3 Preferred devices for primary infrastructure

Compared to cyclic real-time communication, data exchange in a PROFINET network mainly
occurs between the controllers and the devices. As a result, PROFINET-certified switches
should be used for the communication link with the major load.
Generally, a link can be established by using a line structure with arbitrary PROFINET devices
and integrated switches. However, depending on the application, it is recommended to define
a primary communication link to which sub networks or line topologies can be connected. This
will also simplify later plant extensions.
Conformance Class B requirements mean that managed switches are mandatory. These
switches also provide various benefits such as improved diagnostic features for plants
Page 73 / 242
Network topology
according to Conformance Class A; this it is recommended to use managed switches in all

cases.
Figure 3-5: Topology example
Figure 3-5 shows an example of a primary communication link (gray box). This link can also
be implemented as a redundant configuration, to increase the availability.
If possible, you should design a primary communication link using

PROFINET-certified, managed switches.
In a PROFINET network, it is possible to use 1 Gbit/s Ethernet between the switches, even
though the PROFINET devices are only designed for 100 Mbit/s. The Ethernet connection is
made between the switches. To use 1 Gbit/s Ethernet, a CAT 6 cable must be used.
Page 74 / 242
Network topology
3.4 Definition of network technology

Based on the information available the topology of the planned automation project can now
be defined.
A systematic approach is recommended as follows:
Step 1: Define the required position of all network nodes in the automation plant.
Determine which network nodes must be installed together in one location.
Based on this positioning, define your topology.
Furthermore, connect the individual components, bearing in mind to check

whether the PROFINET devices are already equipped with switches.
Step 2: This step considers PROFINET devices with special requirements in terms of
deterministic timing or synchronization. Deterministic timing requires specific
considerations in the topology definition.
All PROFINET devices supporting IRT must be connected

to switches supporting IRT. Devices and switches not
supporting IRT can still be connected to the network, but the
topology must be laid out so that these do not degrade IRT
communication.
Bear in mind that any replacement of devices in live operation

will interrupt an existing line structure. In order to ensure the
availability, you should consider using additional switches or
extending the line to a ring structure.
Page 75 / 242
Network topology
Step 3: Next the transmission medium must be selected. Determine which links shall
be designed as optical fiber or as copper connection.
Check whether the network node supports this transmission medium. If

necessary, you should install additional media converters in the transmission
link (see chapter 3.5).
Make sure here that the cabling is compatible with the

environmental conditions.
Also make sure not to exceed the maximum permissible

number of connector pairs within a link.
The Annex provides a description of the connectors currently available for PROFINET. The
following pages provide some example plants and their topology. These examples can only
show a brief overview of possible PROFINET topologies.
Page 76 / 242
Network topology
Example 1: Factory automation
The topology for an automation plant, designed for factory automation, could have following
structure.
Figure 3-6: Example of a factory automation
In this example, the controllers and switches are installed in separate switch cabinets next to
the production line. All controllers are able to communicate with each other without limitation.
Due to the large distance between the plant areas, the links between the switches are
implemented by means of optical fiber.
In plant area A, the devices are located near the manufacturing process and are connected
via a line structure while plant area B, in addition to a synchronous connection of drives,
foresees additional PROFINET devices with cyclic communication such as devices and
panels.
This example clearly shows the combination of different topologies.
Page 77 / 242
Network topology
Example 2: automation of a machine
The following example shows the automation of a machine. Here, the plant is subdivided into
several areas, which assume different functions. The response times of the plant typically are
very short.
Figure 3-7: Example of a machine automation
While the operator panel is installed in the control room and the controllers outside the
machine area are in a switch cabinet, the devices and an panel are located in the machine
area.
The PROFINET devices, which do not require a synchronous connection are positioned first
and connected to the switch. The special requirement in terms of determinism (e.g. position-
controlled axes) also implies the drives to be synchronously connected to a switch supporting
IRT. Non-IRT PROFINET devices can also be routed via the IRT switches jointly with the IRT
traffic.
Page 78 / 242
Network topology
Example 3: Process automation with remote IO
Process automation amongst others covers chemical industry applications. Here, the network
structure is typically used to link:
• chemical reactors,
• power plants or
• chemical plants.
The requirements in terms of response times are typically lower in process automation than
they are in manufacturing or machine automation.
Figure 3-8: Example plant process automation with remote IO
The control room monitors both processes, which are divided into plant part A and B. Both
plant parts have a local switch cabinet, which is equipped with a switch and a controller.
Due to the extensive distances involved in the plant, the network nodes are linked via a star
topology from the control room to the switch cabinets with FO cable and a line structure inside
the plant parts A and B. This reduces the amount of cabling required.. The sensors and
actuators are connected to the remote IOs, e. g. via 4 … 20 mA and HART.
Page 79 / 242
Network topology
Example 4: Process automation with Ethernet-APL
Ethernet-APL is a two wire 10 Mbit/s Ethernet that is intended to connect sensors and
actuators directly to PROFINET. See chapter 5 and the Ethernet-APL Engineering Guideline
[APL2021] for further details.
Figure 3-9: Example Plant Process Automation with Ethernet APL
Figure 3-9 shows an example plant in the process industry equipped with Ethernet-APL
sensors. The plant layout in the upper part is similar to the previous example shown in Figure
3-8, but instead of the remote IO, APL field switches convert the 100 Mbit/s PROFINET to the
10 Mbit/s Ethernet APL signals. The APL field devices are connected to the field switches via
10Mbit/s APL spurs. These spurs convey data as well as energy to the sensors. The use of a
remote IO is not any longer necessary.
For further information refer to chapter 5 and the Ethernet-APL Engineering

Guideline.
3.5 Topology check and refinements

After defining the topology and the transmission media deployed for the individual links you
need to check whether the selected PROFINET devices support the corresponding chosen
media.
Page 80 / 242
Network topology
Where possible, select devices that support the required transmission media. Where this is
not possible, additional media converters or switches with support for different media may be
required.
Bear in mind that the installation of a switch or media converter requires

additional space.
Document the modification to the preview and analysis of the planned

automation project and check whether it is necessary again to adjust the
network topology.
3.6 Documentation of topology

To conclude the definition of the network topology, document all information about the
selection of
• the transmission media and

• the connectors
It makes sense to use a predefined plant overview of the automation project. If necessary this
can be extended by means of PROFINET network nodes and transmission links. Some
engineering tools and design software provide additional functions that can generate
documentation.
The topics covered in the following chapters, i.e. consideration of network

performance and integration of additional network nodes, could lead to an
adjustment of the network topology.
Figure 3-10 on the following page shows the first draft of a network topology for the plant
example from chapter 2.3.
The plant is now networked via several switches. As agreed, all nodes of the network have
been connected to the network in the first step. An additional switch may have extended the
Page 81 / 242
Network topology
network. In the next step, areas with high determinism requirements have been taken into
account. As a result, appropriate PROFINET devices have been integrated into the network.
Figure 3-10: Plant example with preliminary topology
PROFINET automation plants can be extended with a variety of additional functions. This
includes the integration of standard Ethernet devices as well as the connection to higher level
networks. The following chapter covers these special design aspects.
Page 82 / 242
Special design aspects
4 Special design aspects
Page 83 / 242
This section provides information about
• fast start-up (FSU),

• connection to higher level networks,
• utilization of existing cable infrastructure
• determination of firmware revision levels
• planning of access points for network diagnoses
The special design aspects may require an adjustment of decisions already

taken for the design of topology.
4.1 Use of “Fast Startup”

In some applications it is necessary for PROFINET devices to be operational within a very
short time. For example, after a tool change on a robot. In order to minimize the startup time,
PROFINET offers the “Fast Startup“(FSU) protocol function. This function can be activated
when configuring the devices that support fast start-up.
To be able to realize start-up times below 500 ms, it must be possible to deactivate the auto
negotiation and auto crossover function at the relevant switch of the network node. Without
auto crossover activated a crossover cable or a switch with internal cross connection is
required. Figure 4-1 shows the implementation using a crossover cable.
Page 84 / 242
Figure 4-1: Implementation of “Fast Start-Up“ with PROFINET
Please see the manufacturers’ documents for details about FSU

functionality and the connection of the relevant network nodes.
4.2 Utilization of existing cable infrastructure

Existing cable infrastructure can be used for the future use of PROFINET. This is however
possible only in case the cable infrastructure is suited for PROFINET transmission.
This is the case if the cabling consists of a 4-core, symmetric twisted and shielded copper
cable for the transmission of standard Ethernet.
When using PROFINET, the application-neutral cabling frequently used for standard Ethernet
in industrial environments is categorized as a conformance class and application and may
only be used as such.
If you plan to use existing cabling for the PROFINET plant to be designed
you will find relevant information at www.profinet.com in the Conformance
Class A Cabling Guideline (Order No.: 7.072).
Page 85 / 242
When using existing cabling, the design should be based on the existing infrastructure. The
existing cable infrastructure must be extended by the required transmission links. This
corresponds to the preliminary topology definition as per the previous chapter.
When using standard switches in an existing infrastructure, make sure that they are suitable
for VLAN and relay the priority information of the PROFINET data packet without changing it.
4.3 Connection to higher level networks (corporate network)

In many cases it is necessary for the automation plant to be connected to the operation control
level. Any connection of PROFINET to a higher level network, which is usually based on
standard Ethernet, must always be coordinated with the IT department.
In most cases routers are used for the connection to other networks. For security reasons,
these routers should have firewall functionality.
Figure 4-2: Plant example with connection to the corporate network
The connection via a firewall prevents unauthorized external access to your plant.
Special broadcast packets (so-called “Broadcast” or “Multicast”) will not be relayed by the
routers, thus limiting data traffic to a single network area. This therefore minimizes the data
volume to be routed in a network.
Page 86 / 242
The router acts as a barrier in order to separate a network into several areas and routes the
authorized data to the connected sub-networks.
For the connection of higher-level networks to your PROFINET solution,

please see the notes in the PROFINET Security Guideline
(Order No.: 7.002)
Please bear in mind that PROFINET-RT- and IRT communication are not
possible through a router.
Consider that a router without configuration is not able to negotiate the traffic
between the connected devices. This means that no data traffic through the
router can be expected before the router has been configured accordingly.
Configuration of routers should be done only after coordinating with the IT

department of your company.
4.4 Determination of firmware revision levels

Frequently, different firmware revisions are used for PROFINET devices, e.g. if functions have
been extended in the software.
It is nevertheless useful to determine a corporate firmware revision level in the design phase
of the plant and to make sure – prior to commissioning – that all PROFINET devices have the
same firmware revision level. This ensures consistent device behavior and project planning.
Please contact your device vendor for the latest firmware revision level and determine this
level as a standard for each device type used. Different firmware revision levels for the same
device type should be avoided.
Page 87 / 242
Determine a common firmware revision level for each device type.
It may also be useful to determine a common hardware revision level.
Prior to commissioning, update all PROFINET devices with an older firmware

version to the defined firmware revision level.
4.5 Planning of access points for network diagnoses

In the commissioning phase and for maintenance you will need network access points, e.g.
for analyzing network traffic or reading device data. Such access points are also helpful for
trouble-shooting or long-time diagnosis of the network condition.
In order to be able to connect diagnostic devices without interrupting normal plant operation,
network access points should be available.
For diagnostic purposes, reserve easily accessible ports distributed over the
entire plant.
In any case switches with diagnostic ports should be provided at the

communication nodes, e.g. directly at the controller.
Free ports can be used for a first rough analysis of the network traffic, if the corresponding
switch supports port mirroring.
A TAP (Test Access Point) can be used to analyze data streams for an exact data traffic
diagnosis. A TAP is directly implemented in the communication link, as shown in Figure 4-3.
Page 88 / 242
Figure 4-3: Reading data streams via TAP
A PC can be used for evaluating the data stream. Diagnostic devices with integrated TAP are
also available on the market.
In order to be able to install or remove a TAP, you have to open the communication link. It
may be useful to permanently install TAPs at important points in your plant design.
TAPs are additional network components which may affect the network availability. However,
this effect is negligible when using passive, non-reactive TAPs. See also [PNC2022].
Providing TAPs at important points, e.g. directly at the controller, may be

advisable.
It is recommended to exclusively use passive TAPs without any reaction on

the PROFINET communication.
4.6 Utilization of 4-pair cabling

A consistent cable infrastructure for PROFINET and Standard-IT can be implemented using
4-pair cabling. The corresponding connectors are described in chapter 10.5. This allows you
to integrate other networked systems to the PROFINET network with consistent cabling.
Page 89 / 242
Note that when using 4-pair cabling, PROFINET devices can currently only
run at a transmission rate of 100 Mbit/s. M12 connectors may require the
use of appropriate transition connectors from a Gigabit switch to a
PROFINET device.
4.7 Documentation of modified network topology

You should update your documentation with the results that you have gathered while
considering the special aspects. In the Appendix a proposal for a network documentation is
given in section 10.9.
Some engineering tools, company-internal documentation tools or design

software provide additional functions that can generate design
documentation.
Page 90 / 242
Ethernet-APL
5 Ethernet-APL
Page 91 / 242
Ethernet-APL
This section describes the basics of Ethernet-APL, which is a 2-wire-physical layer used to
connect field devices to an Ethernet network. Detailed information about the planning process
of Ethernet-APL can be found in the Ethernet-APL Engineering Guideline [APL2021].
5.1 What is Ethernet-APL

The increasing use of Industrial Ethernet yields benefits with respect to network diagnosis,
training of staff and the use of single converged technology, in case Ethernet technology is
used throughout the plant. The basic requirements for such a network are:
• Communication considering the requirements of the process industry (harsh

environment, specific topology specifications)
• Operation in areas with explosive atmosphere shall be possible
• Handling by maintenance personnel shall be possible
• Robust and simple connection technology
• Cycle time for the transmission is between 10 ms and 2 000 ms, depending on the task
• All field devices shall support the same defined and standardized physical layer.
• The protocols shall be supported by all bus components (e.g. field devices, process
control systems, infrastructure components, ...).
• All protocols used shall be interoperable with each other, i.e. simultaneous operation
shall be possible.
With the Ethernet-APL physical layer, the cooperating standards development organizations
(SDOs) cooperating in the APL project defined a communication solution to meet the demand
of the process industry for a converging network architecture in the automation domain having
the following features:
• Ethernet based communication

• Two-wire connection to the sensor
• Power supply of the devices via two-wire connection
• Re-use of existing cable installations shall be possible (depends on cable type)
• Operation of field devices and switches in the areas with explosive atmosphere is
possible
• Replacement of failing devices during operation in areas with explosive atmosphere is
possible.
Page 92 / 242
Ethernet-APL
Figure 5-1: Differences between Fast Ethernet and APL
Figure 5-1 shows the differences between an Industrial Ethernet (typ. 100 Mbit/s) and
Ethernet-APL. In the top left corner, a controller is shown in combination with an engineering-
and operator station. The two devices are connected e. g. via a 100 Mbit/s Industrial Ethernet.
Both devices need an auxiliary power. The Ethernet cable uses 4 wires, the communication
usually runs in full duplex mode at a length of 100 m maximum, when using copper media.
The center of Figure 5-1 shows an APL power switch. The APL power switch connects on the
one side to the fast Ethernet and receives auxiliary power. The APL power switch converts
the 100 Mbit/s fast Ethernet to the 10 Mbit/s Ethernet-APL. The Ethernet-APL uses two wires
(single pair) and provides full duplex communication. The APL trunk connects the APL power
switch with the APL field switches. The length of an APL trunk segment can be up to 1 000 m.
The APL power switch provides in parallel electrical energy for the devices, connected to the
APL network. In this case the APL field switch and the APL field devices. The APL field devices
are connected via APL spurs to the APL field switches. In addition, Figure 5-1 also shows a
field switch that is directly connected to the 100 Mbit/s Industrial Ethernet.
It can be seen, that Ethernet-APL is just another physical Layer for PROFINET. The user now
has the choice to use 100 Mbit/s Ethernet physical layer, higher data rates or the 10 Mbit/s
Ethernet-APL-Physical Layer.
Page 93 / 242
Ethernet-APL
5.2 Possible topologies for an APL system

Ethernet APL offers three different topologies that are compared in Table 5-1 with respect to
their features.
Table 5-1: Features of different APL network structures
Feature Field switches with Industrial Powered APL trunk

Ethernet
Maximum spur length ≤ 200 m for cable category IV 1 ≤ 200 m for cable category IV³
Maximum trunk Fiber optic: Depends on type of ≤ 1 000 m for cable category IV.
length / Industrial fiber. Typically, ≤ 2 000 m for Depends on power load of the field
Ethernet length multimode fibers. switches and the devices and the
Copper cable: ≤ 100 m cable used.
Voltage drop on the No Yes

trunk cable to be
considered
Data rate on trunk / Typ. 100 Mbit/s 10 Mbit/s
Industrial Ethernet
Network load Yes, but at 100 Mbit/s data rate Yes
(communication load) impact will be negligible
on trunk / Industrial
Ethernet to be
observed
Auxiliary power Yes, to power the field switches No, field switches are powered via
needed in the field trunk
Equipotential bonding In case fiber optic is used to To be observed, especially when long
connect the field switches, trunk connections are used
equipotential bonding is
uncritical
The next sub-chapters will deal with the three topology alternatives in detail.
5.2.1 Alternative 1: APL field switches with Industrial Ethernet connection
This alternative uses standard Industrial Ethernet to connect the APL field switches to the
control network. In this case the control network is routed to the APL field switches via a fiber
optic. Copper cable is possible as well, but length limitation has to be observed. A power
switch is not necessary. The APL field switches need to be powered by an auxiliary power
source.
1 See [APS2021] for Cable specification details

Page 94 / 242
Ethernet-APL
Figure 5-2: Field switches with Industrial Ethernet connection
Figure 5-2 shows the network structure using Industrial Ethernet cable. Copper cables allow
distances up to 100 m. Multimode optical fibers typically allow distances between the APL field
switches of up to 2 000 m.
When creating APL networks with large cable lengths, the functional bonding
and shielding needs to be observed. See APL Engineering Guideline
[APL2021] for further details. In plants with an unclear situation with respect
to functional bonding and shielding, the use of fiber optic Industrial Ethernet
(FO), as described in the next section, is an alternative.
Check the Ethernet-APL Engineering [APL2021] Guideline for further details.
Page 95 / 242
Ethernet-APL
5.2.2 Alternative 2: Powered APL Trunk
This section deals with the powered APL trunk.
Figure 5-3: Powered APL trunk
Figure 5-3 defines the last limitation for the placement of the APL field switches in case a
powered trunk is used. The maximum distance for each segment in the line can be up to
1000 m, but depends on the following parameters:
• Output voltage of the APL power switch.

• Number of the APL field switches connected to the powered APL trunk.
• Number of the APL field devices connected to the field switches and their power
consumption.
• Cross section (wire gauge) of the trunk cable.
• Temperature of the trunk cable, as resistance depends on ambient temperature.
The location of the APL field devices is defined by the technical process
and is input for the APL planning process. APL field switches to be placed
in a way that maximum spur length is 200 m, maximum distance between
the power switch and the last field switch in the line has to be calculated.
These cable lengths depend on the cable type
Page 96 / 242
Ethernet-APL
Check the Ethernet-APL Engineering Guideline [APL2021] for further

details.
Page 97 / 242
Performance considerations
6 Performance considerations
Page 98 / 242
It is necessary to next consider the performance of the network. This chapter will guide you
through the analysis of your design plan in a step by step manner and show which points have
to be considered primarily in terms of the network performance. The following section deals
with:
• the description of the PROFINET cycle,
• the definition of the device parameters relevant for the performance of the network and
• the PROFINET network topology with a special focus on the cyclic and non-cyclic load
which is generated by PROFINET devices and standard Ethernet devices.
The topology of your network may have to be adjusted to ensure reliable and
timely communication.
Isochronous real-time communication (IRT) and the effect of safety and security concepts are
beyond the scope of this chapter.
The following chapter 6.1 provides a short overview of general Ethernet

functions and of the PROFINET functions relevant for performance. If you
are already familiar with these topics, you can skip this chapter and continue
with chapter 6.2.
Page 99 / 242
6.1 PROFINET transmission cycle

This chapter describes the PROFINET functions relevant for the performance. It provides a
good basis for the analysis of the design planning you have made so far.
6.1.1 Prioritization of PROFINET packets and switching technologies
Two types of communication may be used within a PROFINET network: real-time

communication (RT) and non-real-time communication (NRT).
Real-time communication is prioritized. The standard Ethernet prioritization mechanism in the
VLAN Tag, illustrated in the example in Figure 6-1, is used. It can be seen that the RT packet
get higher priority compared to the NRT packets.
Figure 6-1: Prioritization of real-time communication with PROFINET
As a result, NRT communication is only executed in time periods when no RT communication

occurs. Usually, the following switching technologies are applied:
• “Store and Forward” Switches: The packet is received in its entity, checked for errors
and then forwarded or – in case of an invalid packet – dropped.
• “Cut Through“ Switches: Only the packet parts that are essential to the forwarding
process (i.e. the address information) are read and then the packet is directly
forwarded without further delay.
The switching technology used is of major importance to your topology design plan, especially
regarding the line depth (i.e. number of switches between the controller and the device). For
more details about this topic, please see chapter 6.3.1.
Page 100 / 242

6.1.2 Update time
PROFINET devices can be updated at different intervals depending on the process

requirements and the hardware used. The update time may vary for different PROFINET
devices within the same plant. The length of the transmission cycle, in which all PROFINET
devices receive or transmit their data at least once, is determined by the PROFINET device
with the slowest update time, see Figure 6-2.
Figure 6-2: PROFINET transmission cycle
For fast update times the transmission cycle is subdivided into several phases. The phase
time Tp is always an integer multiple of the PROFINET base clock of 31.25 μs, as given by the
formula (6-1). This integer multiple is the SendClockFactor.
Tp = SendClockFactor  31.25 µs (6-1)
Update times, Ta, other than the minimum transmission clock, are achieved by using a
ReductionRatio as given by the formula (6-2).
Ta = ReductionRation  SendClockFactor  31.25 µs (6-2)
In the example in Figure 6-2 the minimum transmission clock resulting in an update time of
1 ms is required by the device D1. A ReductionRatio of 2 would be assigned to the device D2,
and a ReductionRatio of 4 to the device D3, giving a transmission cycle of 4 ms.
The transmission clock, which defines the minimum clock for the transmission of packets, can
be set in the controller. You can additionally set the transmission clock that defines the
Page 101 / 242

minimum clock for the transmission of packets. The chosen controller transmission clock will
generally correspond to the fastest update time assigned to a device.
The following example illustrates the choice of timing for a typical application. Note that the
values in this example have been chosen arbitrarily to illustrate the principle.
Example Controller data is to be transmitted to 4 devices with an update time of 4 ms.
If the controller transmission clock is chosen as 1 ms, a data packet

will be transmitted every millisecond.
Figure 6-3: Network load, transmission cycle 4 ms, controller transmission clock 1 ms
However, if the controller transmission clock is chosen as 4 ms, the

data packets will also be transmitted every 4 milliseconds.
Figure 6-4: Network load, transmission cycle 4 ms, controller transmission clock 4 ms
In the first case, the load is evenly distributed within the transmission cycle,
whereas in the second case the transmitted packets are bunched together
giving an uneven load on the bus.
As shown in the example, it is recommended to keep the controller transmission clock short
even with slower update times of the devices. This is done to achieve a better distribution of
the generated network load. As a result, you should modify the ReductionRatio rather than the
controller transmission clock when changing the update time of the devices.
Page 102 / 242

Usually, these calculations are made by the engineering tool. Only the
update time has to be preset by the user.
Once the update time has been defined, the PROFINET device will automatically transmit its
data at the intervals given by the update time. With PROFINET RT-communication only this
time interval, at which the data packets are to be sent and not the exact time, is defined.
The preset update time has a major impact on the transmitted data volume and, thus, the
network load. This aspect will be detailed in the following chapter.
6.1.3 Network load
The ratio of the used bandwidth and the maximum available bandwidth is called the network
load. The load distribution of the load over the considered time period is can be considered as
random.
The period under consideration is important to the definition of the network load, because
100% of the entire network bandwidth is occupied for specific time periods during a
transmission process, as shown in Figure 6-5, using a transmission cycle as an example.
Packets of different length – 108 bytes (green, gray) and 300 bytes (blue) in the example –
use the full bandwidth while being transmitted.
Figure 6-5: Example of the network load development during a transmission cycle
The distribution of the network load over the time period under consideration cannot be
determined directly, as the values are always averaged. The longer the period under
consideration, the more the averaging effect takes effect, i.e. short network load peaks are
simply “blurred”. In the example shown in Figure 6-5 the network load is 2% related to 4 ms.
Page 103 / 242

With PROFINET the data is usually transmitted in full-duplex mode, i.e. data is simultaneously
transmitted and received. As a result, you can individually consider each communication
direction.
The ratio of the used bandwidth and the maximum available bandwidth is
called the network load.
Depending on the data volume to be transmitted and the preset update time the bandwidth
required for the RT communication varies. The bandwidth available for NRT communication
changes accordingly. Please note that Ethernet APL (see chapter 5) runs at a data rate of
10 Mbit/s. The mix of different link speeds in a network can lead to congestion issues in
switches. Check chapter 6.4 for further information.
6.1.4 Response time of processing chains
Every PROFINET device sequentially executes its program within a specific cycle time. The
inputs are read at the beginning and the outputs are set at the end of each cycle. The relative
timing of these cycles to each other (see Figure 6-6) has an impact on the response time in a
processing chain.
Figure 6-6: Cycles in the processing chain
Figure 6-7 shows an example for processing an event. This event could be, for example, the
entry of a stop command for a motor.
Page 104 / 242

Figure 6-7: Examples of cycles in the processing chain, shortest response time
The execution time is determined by:
• The cycle time of the controller TC.

• The processing time in the controller ΔTC.
• The cycle times of the devices TD1 and TD2.
• The cycle times / update times of the devices TPN1 and TPN2.
• The transmission times of the data through the network ΔTPN1 and ΔTPN2.
In this example it is assumed that the PLC tasks are cyclically executed in the controller, e.g.
with IEC 61131-3-systems. It is assumed that the processing time of the PLC task ΔTC is faster
than the cycle time TC of the task. If the tasks are executed in the controller cyclically (“PLC
mode”), the cycle time of the controller TC corresponds to the processing time in the controller
ΔTC.
In the best case, the data are received “just in time” right before the start of the next cycle and
can be directly processed. No additional delay occurs.
In the worst case the execution must wait for an entire cycle in each processing step until
evaluation and response will be possible again, see Figure 6-8. This consideration is based
on the assumption that with cyclic processing the event has “just been missed” and processing
will not be possible before the next cycle starts.
Page 105 / 242

Figure 6-8: Examples of cycles in the processing chain, longest response time
As the cycles of the components in a system are not synchronized with each other, variations
of the response time must be expected.
In the worst case the response time in the processing chain may be twice the time required in
the best case, as shown in the following example:
Example Assuming
TC = 15 ms
ΔTC = 10 ms
TD1 = TD2 = 3 ms
TPN1 = TPN2 = 2 ms
ΔTPN1 = ΔTPN2 = 100 μs
gives a response time of
min.
TD1+ΔTPN1+ΔTC+ΔTPN2+TD2 = 16,2 ms
max.
2·TD1+TPN1+ΔTPN1+TC+ΔTC+TPN2+ΔTPN2+2·TD2 = 41,2 ms
Page 106 / 242

In the example described above, the impact of the PROFINET update time is rather low, as
shown in the example below:
Example Reducing the response time TPN1 and TPN2 from 2 ms to 1 ms while maintaining
the assumptions specified in the previous example will result in a minimum
response time of 16.2 ms and a maximum response time of 39.2 ms.
In this case, the ratio of the update time and the controller cycle time is 1:15.
In the above example the reduction of the controller cycle time has a considerably higher
impact on the response time:
Example Reducing the controller cycle time TC from 15 ms to 10 ms with a controller

processing time ΔTC of 5 ms while maintaining the other assumptions of the
first example gives a minimum response time of 11.2 ms and a maximum
response time of 31.2 ms.
In this case, the ratio of the update time and the controller cycle time is 1:5.
A change of the ratio of the update time and the controller cycle time will result in a change of
the response time.
Make sure that the response time of your control system is sufficiently fast
for your application, but only as fast as needed.
Page 107 / 242

6.2 Planning of the IO cycle

The following section deals with the definition of the device configuration. In this context, the
PROFINET update times and monitoring functions are discussed.
6.2.1 Planning of update times
Controllers operate cyclically with a specified update time. The update time of all other
PROFINET devices must be defined as a function of the controller cycle time. For multi-
controller applications the devices assigned to the corresponding controller must be
considered.
With fast update times the data will be updated at shorter intervals. As a result, they will be
available for processing more quickly. However, the data volume transmitted in a time period
and, thus, the network load is increased.
Figure 6-9 illustrates how the network load increases as a function of the update time and the
number of network nodes, using the typical PROFINET packet size 108 bytes (60 bytes
payload data) as an example.
Figure 6-9: Cyclic PROFINET network load as a function of update time and number of network nodes (typ.
PROFINET packets)
Page 108 / 242

When the network load is increased by cyclic real-time communication, the bandwidth
available to other communications decreases. The network load topic is discussed in more
detai in chapter 6.3.3.
Ethernet APL (see chapter 5) runs at a data rate of 10 Mbit/s and is intended to connect
sensors and actuators to the PROFINET network. The typical network updated times in the
process industry used for Ethernet APL field devices and are slow, compared to factory
automation. Therefore, the network update rates for Ethernet-APL sensors should be set to
values that fit the need of the process automation application (e. g. 128 ms). Detailed
information about the calculation of the network load of Ethernet-APL segments can be found
in [APL2021].
The faster the update time, the larger the bandwidth occupied by cyclic real-
time communication.
The slower the update time, the slower the response time.
It is therefore recommended to choose the update time per PROFINET

device as fast as required and as slow as possible.
Observe the line depth and update time specifications in chapter 6.3.1.
• Define the update time for all devices.

• Bear in mind that you have to adapt the update times accordingly
when using wireless transmission technologies.
• Check the response time of the entire system resulting from this.
• Document these specifications.
Page 109 / 242

6.2.2 Definition of PROFINET communication monitoring
Data transmission errors may occur in a network. As a result, communication monitoring must
be fault-tolerant to a certain extent. However, it must be possible to detect an error as early
as possible to be able to react accordingly in the event of communication failure, e.g. by setting
outputs to a defined state. The goal is to check and, if required, adapt communication
monitoring.
The communication monitoring function in a PROFINET network checks if valid data are
received. If no valid data are received within a preset time or number of communication cycles,
it is assumed that an error has occurred.
In the following description, the number of communication cycles without valid data after which
an error is assumed is called the threshold.
The designation of the communication monitoring setting depends on the

manufacturer. Examples include:
• “Number of accepted update cycles with missing IO data”

• “Number of update cycles without IO data”
• “Number of faulty telegrams before communication is terminated”
Figure 6-10 illustrates the process of setting the standard threshold to 3.
Figure 6-10: Communication problems with error threshold 3
Page 110 / 242

In the first case (left part of the figure) the communication is disturbed for two cycles, for
example by electromagnetic interference (EMI). As the threshold is not reached, the counter
is reset at the restoration of the communication, and normal communication continues.
If the problem persists for a longer time (right part of the figure) a communication error is
assumed and the communication is terminated.
The threshold value determines the time from which on the absence of data will be considered
as an error.
The higher the threshold, the later a communication error will be recognized. Figure 6-11
shows the situation of a persistent communication error, using the standard threshold of 3 and
a threshold of 10 as an example.
Figure 6-11: Comparison of low (3, left) and high (10, right) threshold
The time until an error is recognized is given by the communication cycle time and the
threshold. This means that with a standard threshold of 3 and an update time of 2 ms an error
would be detected after 6 ms, whereas an update time of 4 ms would result in an error
detection time of 12 ms, etc.
Page 111 / 242

A higher threshold increases the fault tolerance in case of problems, but also
delays the detection of an error.
It is recommended to keep the standard threshold setting of 3. If you should

choose another threshold value, you have to check if the response time in
the event of an error is sufficiently short.
Define the thresholds for the monitoring function and document your
settings.
Page 112 / 242

6.3 Checking the performance of the planned network topology

Having defined the update times and the monitoring functions, the designer should check the
expected performance of the planned topology.
6.3.1 Checking the line depth for 100 Mbit/s network
Each switch that is placed between a device and its controller introduces a delay in the data
transfer. The number if switches between a controller and a device is called the line depth.
The designer must take account of the line depth in the proposed topology. A line topology
will exhibit a significant line depth because of the integrated switches in the devices. A large
line depth will introduce delay which must be considered when planning the topology. Figure
6-12 shows an example with a line depth of 9.
Figure 6-12: Line depth example
Usually, critical communication relations occur between devices and controllers. If more than
one controller is involved, the devices assigned to each controller must be considered.
The larger the line depth, the larger the delay of data transmission. As a result, the data will
have a certain age when it arrives at the destination. Excessive line depth should be avoided
for time-critical applications.
Page 113 / 242

A large line depth may affect the response time.
The maximum line depths listed in Table 6-1 are valid for “Store and Forward” switches.
Check which type of switches (“Store and Forward” or “Cut Through”) are to
be used in your network. Store and Forward switches give more delay than
Cut Through switches. If you do not know the type of switches used, assume
“Store and Forward” switches, to be on the safe side.
When using "Store-and-Forward" switches, the maximum line depths specified in Table 6-1
apply.
Table 6-1: Maximum line depths with “Store and Forward” switches
Update rate 1 ms 2 ms 4 ms 8 ms
Maximum line depth 7 14 28 58
In a worst-case scenario, the processing time for these line depths in a line topology is as
large as the update time.
The maximum line depths listed in Table 6-2 are valid for “Cut Through” switches.
Table 6-2: Maximum line depth with “Cut Through” switches
Update rate 1 ms 2 ms 4 ms 8 ms
Maximum line depth 64 100 100 100
Page 114 / 242

It is recommended to plan a maximum line depth of 45, for the benefit of

higher availability and easier diagnosis.
This also allows future extensions using media redundancy (MRP).
A mixed setup of “Store and Forward” and “Cut Through” switches can be
used. In this case it is recommended to assume the limit values for “Store
and Forward” switches or explicitly calculate the processing time.
If it should not be possible to observe the values specified in Table 6-1 apply. Table 6-1 resp.
Table 6-2. You should re-design the structure of your network. It is, for example, possible to
segment line topologies to achieve several short lines, as shown in Figure 6-13.
Figure 6-13: Example of reduced line depth
The re-structuring options depend on the structure of your individual plant. Possible additional
expenditure for supplementary switches or cabling is compensated by a higher plant
availability and shorter plant response time.
Check the line depth of your plant. If required change the topology. Take
into account the specifications in Table 6-1 resp. Table 6-2.
Page 115 / 242

6.3.2 Checking the line depth for Ethernet-APL networks
Ethernet-APL allows to connect APL field devices directly to a PROFINET network by using
the 10Mbit/s Ethernet Advanced Physical Layer (Ethernet-APL). Possible network structures
can be found in chapter 5. Figure 5-2 shows a topology, that connects the APL field devices
via a field switch directly to the 100 Mbit/s PROFINET network.
Figure 6-14: Line depth with APL Field-switches connected to 100 Mbit/s network
Figure 6-14 shows the calculation of the line depth for network with Ethernet-APL field
switches that are directly connected to the 100 Mbit/s PROFINET. The calculation principle is
the same as described in chapter 6.3.1.
For an APL topology with a powered trunk, as shown in Figure 5-3, the line depth of the trunk
has to be considered in addition to line depth known up to now.
Page 116 / 242

Figure 6-15: Line depth with APL trunk
Figure 6-15 shows a system with an APL trunk. Up to now, only one APL field switch is allowed
to be connected to a trunk
The limitation to one field switch per trunk is a preliminary value due to
PROFINET as conformance testing is ongoing. This limitation is not related
to Ethernet-APL and assumed to be changed in future.
6.3.3 Checking the cyclic real-time network load
You should have defined update times of the PROFINET devices in a

previous step.
As already mentioned in chapter 6.2.1, every PROFINET device generates a specific cyclic
network load with a given update time. In this chapter, the cyclic real-time network load (RT
network load) is analyzed and evaluated.
Figure 6-16 shows a PROFINET network with one controller and several devices as an
example. For illustration purposes, it is assumed that each device in the example generates a
cyclic real-time network load of 1%. This value is used for illustration, only. In a real plant it is
usually smaller. In the example only the direction from the device to the controller is
investigated, although the data are actually transmitted in both directions.
Page 117 / 242

Figure 6-16: Example of network load distribution in a single controller application
As shown in the example, the data streams in the same direction add up. The highest network
load, i.e. the total of all network loads generated, occurs in the link between the switch and
the controller.
This applies also to applications with multiple controllers. As an example, the given
configuration is extended by another controller and three assigned devices, as shown in Figure
6-17. At the locations highlighted red the network loads of the different controllers add up.
Page 118 / 242

Figure 6-17: Example of network load distribution in a multi-controller application
It is important for your planning to identify the critical locations in your topology, i.e. the
locations of maximum network load. In the given example these are the links to both of the
controllers.
The critical locations are those of maximum network load.
The communication runs simultaneously in transmit and receive direction. In

practice it is sufficient to analyze only the direction with the higher load.
In order to be able to identify the critical locations, you have to know the cyclic real-time
network load generated by each PROFINET device, which depends on the update time and
data volume.
Table 6-3 is an example of the cyclic real-time network load generated by PROFINET devices
at different update times and assuming a network bandwidth of 100 Mbit/s. A typical
PROFINET packet of 108 bytes (60 bytes payload data) is considered. As the data volume
depends on the application, this table is only intended to give you a first idea. It is
recommended to calculate the generated network load for your individual application.
Page 119 / 242

Table 6-3: Generated cyclic real-time network load (typ. PROFINET packet size 60 byte of PROFINET
payload data, 100 Mbit/s)
Update time Generated cyclic real-time network load per PROFINET device
1 ms 0.86 %
2 ms 0.43 %
4 ms 0.22 %
8 ms 0.11 %
The specified values include Preamble, StartFrameDelimiter and InterFrameGap.
Determine the network load of your plant and identify critical locations.
The network load calculation tool is available free of charge for download at:
www.profinet.com
under “Download > Installation Guide > PROFINET Installation Guide”
An overview of the user interface as well as a short user manual is provided

in the Annex.
Programs for network load calculation are also offered by various vendors.
Usually, the engineering tool of your control system also provides this
option.
Refer to Table 6-3 an introduction.
In order to provide sufficient reserve for future extensions and especially for NRT
communication, it is recommended to observe the limit values specified in Table 6-4 when
designing your PROFINET network.
Page 120 / 242

Table 6-4: Limit values for the network load of cyclic real-time communication
Network load Recommendation
<20%: No action required.
20…50%: Check of planned network load recommended.
>50%: Take the appropriate measures to reduce the network load.
There are various options, of which the following should be considered first:
Increasing the update time (see chapter 6.2.1).
• For multi-controller applications: Separating PROFINET devices assigned to the

corresponding controller to different network paths, thus reducing the load of links
with parallel data traffic as shown in Figure 6-17.
• Connecting subnets via additional network adapters in the controller
• Using additional controllers for load distribution: The controllers should be
connected to the network via separate paths to actually reduce the network load in
critical sections.
Change the topology as required and document the changes.
Ethernet-APL networks require the same considerations with respect to network load, as
described in this chapter, but adapted to the 10 Mbit/s data rate of the Ethernet-APL network.
A detailed description of the network load calculation for Ethernet-APL networks can be found
in the Ethernet-APL Engineering Guideline [APL2021].
Page 121 / 242

6.3.4 Checking the non-real-time network load
PROFINET allows standard Ethernet nodes such as video cameras, PCs or HMI stations to
be directly integrated into the plant network.
Consideration must be given to the effect of such devices on the performance of the real-time
communication. The PROFINET data traffic and the standard Ethernet data traffic may
interfere. Standard Ethernet nodes may under certain circumstances exchange large data
volumes.
The following scenarios are possible:
Regular NRT communication: For example, a video stream from a camera to an evaluation
PC. Additional network load is permanently generated.
Temporary NRT communication: Data streams that occur only occasionally, for example
during a data backup on an archive server, or during call up of process graphics at an operator
station.
Figure 6-18 shows an example topology with an archive server (temporary NRT
communication) and a video camera and an operator station representing standard Ethernet
nodes that regularly generate NRT communication (video stream).
Figure 6-18: Example topology with standard Ethernet nodes
It is often very difficult or even impossible to exactly determine the additionally generated
network load. If it can be determined, this information is useful for evaluating the total network
load.
Page 122 / 242
If possible, determine the regular NRT network load.
This load adds up to the cyclic real-time network load described in chapter
6.3.3. If required, identify the critical locations of your topology again and
check if the network load limits specified in chapter 6.3.3 are complied with.
For temporary NRT communication it is often not possible to determine when communication
actually occurs.
Some standard Ethernet nodes also prioritize their data packets. This may
cause priority conflicts with PROFINET packets, which are consequently no
longer getting higher priority against other prioritized packets.
This applies especially to image (camera) and voice (VoIP) data streams.
All network nodes that generate image or voice data streams should there for be checked for
possible message prioritization. Where present the prioritization should be disabled if possible.
If, however, this prioritization cannot be disabled or you cannot reliably determine whether
these devices conduct prioritized data transmission or not, it is recommended to separate
these data streams.
If required separate network nodes that prioritize their messages.
Change the topology if required and document these changes.
Page 123 / 242

Communication relations not only exist between controllers and devices. Devices can also
communicate with each other. This type of communication often occurs between standard
Ethernet nodes.
Figure 6-19 shows a typical example of this type of communication between standard Ethernet
nodes. A large data volume is transmitted from a camera to an operator station.
Figure 6-19: Integration of standard Ethernet nodes
Disadvantageous topologies as shown in the example in Figure 6-19 imply that the data
stream runs throughout the entire plant network, generating additional load on the parts that
convey cyclic real-time communication. In the example the additional communication volume
would cause a network load of 50% in some locations (Figure 6-19, red circle).
To solve this problem the topology should be changed. In the example, the camera and the
PC could be directly connected to the switch. As a result, the large data stream would no
longer represent a considerable load for the other sections of the network, see Figure 6-20.
Page 124 / 242

Figure 6-20: Optimized topology with reduced network load
Usually, switches have a sufficient internal bandwidth, so “crossing” data streams usually do
not affect each other.
Check if it is necessary to separate data streams.
Change the topology, if required and document these changes.
6.4 Mixed link speeds and star topology

This chapter deals with networks that use different data rates (link speeds) in different parts
of the network. In addition to that the impact of topologies with a star structure will be covered.
These two items are discussed here together, as they both may lead to the loss of data in
switches, called congestion loss, if not observed during the planning process.
Page 125 / 242

6.4.1 Problem Description mixed link speeds and star topology
Mixed Link speeds: The previous chapters of this document assumed a data rate of
100 Mbit/s throughout a PROFINET network. Due to technical progress, higher data rates like
10 Gbit/s, 1 Gbit/s are now applicable for PROFINET [PNO2022]. At the same time lower data
rates of 10 Mbit/s will be used to directly connect sensors and actuators to PROFINET, e. g.
by using the Ethernet-APL physical layer [APL2021] or a network connection according to
Single Pair Ethernet [IEEE P802.3cg]. This leads to a situation, where a mix of different data
rates, called mixed link speeds are used in a single network. Mixed link speeds put additional
requirements on a switch, as the amount of data coming into the switch on a high-speed link,
needs to be forwarded to one or more links with a lower speed. If these data streams are not
balanced properly, a data loss might occur in a switch. This data loss is called congestion loss.
Star topology: Field devices build as end stations are connected to a switch. Switches with
higher port counts are typically used in this case. In star topology, congestion loss is possible,
if the buffer size on the uplink port is not sufficiently large. APL field switches, that connect a
larger number of field devices in a star manner to an uplink, are an example for this case. The
Ethernet APL Physical Layer allows to connect Ethernet APL Field devices to PROFINET
[APL2021].
Page 126 / 242

6.4.2 Example System

Figure 6-21 shows a sample system that illustrates the mixed link speed as well as the star
topology issue. Please note that this a simplified example only. Typical systems that use such
high data rates consist of far more components that shown here.
Figure 6-21: Mixed Link speeds and star topology in a PROFINET system
The connection between the Controller and Switch 1 as well as the connection between Switch
1 and Switch 2 operate at a link speed of 1 Gbit/s. The connection between Switch 2 and the
APL power switch runs at 100 Mbit/s, as well as the connection to the Remote IOs. The
Ethernet-APL connection between the APL power switch and the APL field switch, called APL
trunk, as well as the connection between the APL field switch and the APL field devices runs
at 10 Mbit/s.
In this example the controller serves as the central processing point that receives and send all
data from and to the devices. The link speed data rates are increasing from the sensors to the
controller according to the data volume to be transferred. The use of mixed link speeds is a
good measure, to adapt the bandwidth of the links to the needs of the application. At the same
time, mixed link speeds need special attention with respect to congestion loss.
In parallel the example in Figure 6-21 shows on the right side a star topology with an Ethernet-
APL field switch. The field switch is able to connect 16 devices to a single uplink, the Ethernet-
APL trunk.
Page 127 / 242

In parallel to the described real time communication via PROFINET additional communication
relations like OPC-UA or http-connections to web servers in the devices can exist.
6.4.3 Prioritized queues in network switches

This section will explain different scenarios that lead to congestion loss. In order to understand
the issue of congestion loss in general, a closer look at the function principle of a switch has
to be taken.
PROFINET uses prioritized network traffic according to [IEE802.1Q]. This standard defines
eight priorities from 0 (low) to 7 (high). In order to simplify the following example, only two out
of the eight priorities are considered. The examples differentiate between nor real-time traffic
(NRT) with a low priority and real-time traffic (RT) with a high priority.
Figure 6-22: Switch principle with queues
Figure 6-22 shows the simplified structure of a switch. A switch is a device that receives an
Ethernet data packet on an ingress port (RX) and forwards the data package to an egress port
(TX), depending on the address information in the data packet. Every port of a switch (white
squares with TX and RX) connects to a cable, also called link. Every link can receive and
transmit data, usually in full duplex mode. Switches used for PROFINET usually support the
prioritization of traffic according to IEEE 802.1Q. This allows to assign a priority between 0 and
7 to each data packet. The switch provides different queues for the outgoing data of each port,
assigned to the different priorities. As already described, Figure 6-20 will only show two out of the
eight queues for the priorities. Outgoing data is sent according to its priority.
Page 128 / 242

When working with mixed link speeds, it is helpful to limit the amount of data on the incoming
section of the port with the high data rate, in order to ensure propagation of data to the ports with
the lower data rate. For this purpose, ingress rate limiters are used. [PNO2022] describes ingress
rate limiters in switches in Figure 6-22. The rate limiting is based on [IEE802.1Q] chapter 8.6.5.
6.4.4 Congestion loss due to prioritization of messages
Figure 6-22 shows the prioritized buffers in a simplified manner. For each port the output
buffers for high priority data packets (named RT, green box) and the output buffers for low
priority packets (named NRT, grey box) are shown. If a prioritized RT packet (green line)
comes in at port 1, the packet is received, the destination address in the packet is read and
the switch electronics forwards the packet to the respective destination port. In this case port
2. There the RT packet is stored in the output queue for RT packets (green box) and afterwards
the packet gets sent via port 2. If at the same time, a low priority (NRT) packet (black line)
enters the switch at port 0 and if the packet has the same destination port, the switch electronic
will forward the package also to port 2, but will store it in the NRT output queue. The priority
scheme at the output now ensures that the data in the RT queue will be sent first, afterwards,
if the RT queue is empty, the switch will send the NRT packet. Due to hardware constraints
the size of the output queues (i. e. the number of packages that can be stored in a queue) is
limited. If more packages enter the queue as the packages leave the switch through the port,
the queue gets overloaded and, in this case, typically the NRT data packages are dropped,
due to the limited size of the output queue. In case that there is a high amount of outgoing RT
packets, the buffer for the NRT packages might get full, resulting in the drop of NRT packages.
We will refer later to this as Case 1: Priority Congestion loss.
Page 129 / 242

In many cases the NRT communication (e. g. http or https) operates connection oriented. This
means that the TCP/IP protocol detects the loss of data packets and repeats them. Therefore,
priority congestion loss will lead to a degradation of the connection speed but not to a real loss
of the NRT data, if the used protocol supports adaption to the available bandwidth and
retransmission.
6.4.5 Congestion loss due to input / output unbalance port count wise
As the priority impact has been considered in the previous chapter, this chapter will focus on
data packages with the same priority.
Figure 6-23: Congestion loss due to input/output unbalance port wise
Figure 6-23 shows an example, where three incoming data packets on port 0, 1 and 3 shall
be forwarded to port 2. If the size of the output buffer of port 3 allows to store all three packets,
the transmission of the data will be o.k. In case the buffer is smaller, one or more of the data
packets are dropped and congestion loss occurs.
Page 130 / 242

Figure 6-24: Example for input/output unbalance port count wise
An example for such an unbalance is shown in Figure 6-22. In this example, the Ethernet-APL
field switch is shown. In this case, the APL field switch has 16 spur connections to connect
the APL field devices with 10 Mbit/s each and one 10 Mbit/s connects the field switch to the
power switch (see also overview in Figure 6-19). It can be seen, that in an unfavourable
situation (e. g. all devices randomly send data packets at the same time) a congestion loss
could possibly happen. In case the APL field switch operates as a PROFINET device itself,
the number of nodes will even go up from 16 to 17. This issue will be further referenced as
Case 2: Congestion loss input / output unbalance port count wise. Chapter 6.4.9 will dig
into a differentiation between a permanent and a spurious congestion.
6.4.6 Congestion loss due to input / output unbalance link speed wise
The previous two chapters covered congestion loss examples, where all links operated at the
same link speed. The next example will now provide an example with mixed link speeds.
Page 131 / 242

Figure 6-25: Example for input/output unbalance link speed wise
Figure 6-25 shows an example where the controller connects to switch 1 via a link with 1 Gbit/s
(L1). At the same time the Remote IOs 1 to 5 are connected to the same switch with a
100 Mbit/s connection via a line topology (L2). If we assume now, that the controller sends out
the output data to the remote IOs in a burst, a congestion issue could arise at the outgoing
port of switch 1 that connects the Remote IOs via the link L2. This high rate of incoming data
packets at Link L1 might cause an overflow of the output port that forwards the data to L2.
This issue is referenced as Case 3: Congestion loss input / output unbalance link speed-
wise.
The described congestion loss is also relevant in case there is a higher number of broadcast
or multicast packages present in the network. As a switch forwards broad- or multicast
packages to all ports, the ports with the lower speed might experience an overload condition
due to a higher number of broad- or multicast messages.
Chapter 6.4.9 will dig into a differentiation between a permanent and a spurious congestion.
The next section will now summarize the three described cases.
6.4.7 Congestion loss in Ethernet-APL Systems

The next chapter focusses on Ethernet-APL systems and possible congestion loss situations
in such systems. Figure 6-26 shows an APL System with a trunk and spur topology.
Page 132 / 242

Figure 6-26: System Structure of an APL System with trunk and spur topology
In this example, the controller is connected via a 100 Mbit/s PROFINET connection to switch.
An APL power switch converts the 100 Mbit/s physical layer to the 10 Mbit/s Ethernet-APL
physical layer. It can be seen that the congestion loss issues describe in chapter 6.4.6 apply
for the APL Power switch. At the same time, the APL field switches 1 and 2 have to be
considered with respect to the congestion loss issues described in chapter 6.4.5. It can be
seen in Figure 6-24, that the APL field switch 1 needs to handle the incoming data from the
16 spurs as well as the incoming data coming from the APL trunk on the right side.
Figure 6-27 shows an alternative topology, that uses industrial Ethernet with a data rate of
100 Mbit/s to connect the field switches with the controller.
Page 133 / 242

Figure 6-27: Ethernet-APL system with 100 Mbit/s industrial Ethernet to the field switches
In this case, the APL field switches 1 and 2 have to be considered with respect to the
congestion loss issues described in chapter 6.4.5. Compared to the example with the trunk
and spur topology, the congestion loss issue is less relevant, as the connection to the
controller runs at a data rate of 100 Mbit/s compared to 10 Mbit/s shown in Figure 6-24.
Further details about possible Ethernet APL topologies can be found in [APL2021].
6.4.8 Summary congestion loss

This chapter summarizes the congestion problems discussed in the previous chapters. Table
6-5 sums up the categories discussed and the respective root cause.
Page 134 / 242

Table 6-5: Categories of congestion loss
Case Nr. Description Root cause
1: Priority Output queue for low priority RT traffic outgoing on the same
congestion loss packets (NRT) gets overloaded port in parallel to NRT traffic
due to the preferred
(Chapter 6.4.4) transmission of high priority
traffic (RT). Usually uncritical if
aligned with the retransmission
strategy as the NRT traffic is
connection oriented and lost
data packets will be repeated.
2: Congestion loss A switch connects a number of Unsynchronized sending of a high

input / output devices and all devices sent number of devices connected to a
unbalance port wise. their data to a single (outgoing) switch simultaneously sending
port. information to a single outgoing
(Chapter 6.4.5) port
Case 3: Congestion A switch connects a link with Link speed conversion in a switch
loss input / output high data rate (e. g. 1 Gbit/s) to with a burst of data packets or a
unbalance link a link with a lower data rate high number of broadcast and/or
speed wise (e. g. 100 Mbit/s). A burst of multicast packages to be
data packages comes in at the forwarded to a port with a lower
(Chapter 6.4.6) link with the high data rate and data rate.
all packets need to be
forwarded to a single port with
a lower data rate.
Cyclic transmitted real-time traffic does not use retransmission. Thus, frame dropping
due to congestion loss may lead to connection loss.
Other traffic, for example connection establishment or diagnosis and events, supports
retransmission. Thus, frame dropping due to congestion loss leads to retransmission
and, if the congestion loss occurs aligned with the retransmission, to connection loss.
After having discussed the congestion problems in general, the next chapter will
evaluate, if these issues arise during normal operation.
Page 135 / 242

6.4.9 Permanent or spurious congestion loss

When looking back at the described scenarios, it has to be questioned, how likely such
a congestion loss is in practice. In order to find this out, two issues have to be
considered:
1. Network load due to permanent, cyclic traffic.
2. Burst network load due to a larger number of data packets sent out in a very
short time frame.
In order to evaluate the permanent network load, the example in Figure 6-24 shall be
looked at in more detail. The example shows an APL field switch with sixteen 10 Mbit/s
spurs feeding data into a single 10 Mbit/s trunk link. In [APL2021] an equation is given
to calculate the netload that is generated by a single APL field device. The following
assumptions apply in for this calculation:
• Network update rate 64 ms
• Payload for one data frame: 46 Bytes (minimum frame size)
• Data rate 10 Mbit/s
• Number of APL field devices connected to the switch: 16
According to the calculation in [APL2021], this setup leads to an overall netload of 2.2%
on the APL trunk. It is obvious, that the setup will not suffer from any congestion loss
due to permanent cyclic traffic, but the sustained network load should be calculated
and the maximum values, recommended in [APL2021] shall be observed and a reserve
for other cyclic or non-cyclic traffic shall be considered. Please note that the low
network update rate and the small payload size is process industry related. Other
applications might require larger payloads and higher data rates. Nevertheless, the
calculation principle described in [APL2021] allows the calculation of any network
update rate in combination with any data size within the limitations of the Ethernet
protocol.
So, if the sustained network load in the previous example is quite low, why does this
document discuss the issue of congestion loss at all? This is due to the fact that the
devices send out their data cyclically, but the point in time, when they send, is not
synchronized. This could lead to the situation, where all the sixteen APL field devices
in Figure 6-24 send out their data simultaneously. In this (possibly unlikely) event, a
congestion loss is likely to occur. Due to the fact, that PROFINET RT does not provide
Page 136 / 242

a synchronisation of the sending points in time, the problem is present, even though
not extremely likely. Nevertheless, the planning process can help to reduce the impact
of a possible congestion loss. The needed precautions will be described in the next
chapter.
6.4.10 Planning measures to avoid congestion loss

This chapter covers the measures to avoid congestion loss in the network or at least to reduce
the likelihood of a congestion loss. For this purpose, the planning measures, described in
Table 6-6 shall be observed.
Table 6-6: Planning steps to avoid / reduce congestion loss
Measure Description Document Reference
1 Calculate the cyclic network load APL: See [APL2021] chapter

and keep the load below the 4.8.2.
recommended limits. This PROFINET in general: See this
measure keeps sufficient document chapter 6.1.3.
bandwidth also for non-real time
traffic. Keep the update rates as
fast as needed, but as low as
possible.
2 Observe that switches with a high Check the manufacturers
number of ports, like shown in specification and/or contact the
Figure 6-24, might cause a manufacturer of the switch used.
congestion loss due to the
unsynchronized operation of the
field devices. Make sure that the
switch provides a sufficient buffer
size for the data to be transmitted
to the trunk
3 Make sure, that the controller does [PNO2022] describes a limiter for
not send out IO data in bursts, output data (Traffic shaper for
when using mixed speed networks output data) to avoid bursts that
as described in chapter 6.4.6. could cause congestion loss.
Check the manufacturers
specification and/or contact the
manufacturer of the controller
used.
4 Use a rate limiter in a switch in [PNO2022] describes rate limiters

order to limit the amount of traffic in switches on the domain
(esp. bursts) that runs from a boundary in Figure 124. The rate
Page 137 / 242

network with higher speed (e.g. limiting is based on [IEE802.1Q]

100 Mbit/s) to a network with lower chapter 8.6.5.
speed (e.g. 10 Mbit/s). The rate
limiter can be placed for example
in Switch 1 or the APL Power
switch in Figure 6-26.
Besides these planning steps the PROFINET Commissioning Guideline [PNC2022] should be
observed, especially section 5.4.3 (Network load) and 5.4.4 (Broadcasts and multicasts).
Page 138 / 242

6.5 Documenting your settings

Once all the settings described in the above-listed steps have been incorporated, they should
be incorporated into the documentation. The settings to be documented include:
• Changes of the network topology

• Update time settings
• Monitoring function settings
It is important to ensure that all settings and changes are incorporated in

your documentation and are up to date. If required, add missing items.
Page 139 / 242

Planning of additional functions
7 Planning of additional functions
Page 140 / 242

In addition to the functionality described above, PROFINET offers a number of additional

functions which need to be considered when designing the network.
This includes:
• the optimization of the plant availability,

• the use of a wireless connections and
• the Engineering access for commissioning and service.
The following section provides a short summary of these functions.
7.1 Increased availability

In some cases, automation plants require an increased availability. Several approaches exist
for PROFINET systems. Here we will introduce the network structures to increase plant
availability.
In addition, the properties of a redundant structure will be discussed. We differentiate between

bumpless and non-bumpless changeover.
Adjustment of network infrastructure
Figure 7-1 shows a line topology of a plant part for which a device is to be exchanged.
Figure 7-1: Device exchange in a line topology
Page 141 / 242

Removal of a PROFINET device from a line structure causes the communication to

downstream devices to be interrupted.
A device exchange or the outage of a link interrupts the downstream

communication.
The interruption of a link has the same effect. The primary solution to increase the availability
and to reduce interruptions of communication in a line topology is the use of a star or tree
structure.
Figure 7-2 shows two device exchange scenarios in a star or tree structure.
Figure 7-2: Device exchange in a star or tree structure
In scenario 1, the device exchange does not affect communication of the other network nodes
since the process-related PROFINET devices in this topology do not communicate with each
other. This means all PROFINET devices can be exchanged without any impact on
communication.
In scenario 2 the outage or change of the central switch or a link interruption will inevitably
interrupt communication of the remaining nodes in this branch. This can be avoided by using
a ring structure, as shown in Figure 7-3.
Page 142 / 242

Figure 7-3: Upgrading a line topology to a ring structure
Ring structures are built up using switches. These can be separate switches or switches
integrated in PROFINET nodes. To be able to use ring structures in PROFINET plants, all
PROFINET nodes in the ring have to support the "Media Redundancy Protocol" (MRP).
PROFINET nodes are differentiated according to their function as either MRP Manager or
MRP Client. One of the PROFINET nodes within the ring structure assumes the function of
MRP Manager. The MRP Manager monitors the link to all PROFINET nodes connected in the
ring. All other PROFINET nodes in the ring structure assume a function as MRP Client.
The MRP Manager not only monitors the ring structure, but also controls the data traffic. The
redundancy manager in case of error-free operation uses only one path to send data. The
MRP Manager thus forms a line with the other PROFINET nodes in the ring structure: this line
prevents data telegrams from circling within the ring structure without limitation, thus causing
undesired network load.
If now the ring structure is interrupted (case 1 in Figure 7-3), data will also be forwarded via
the redundant path. The MRP Manager has two ring ports and thus forms two lines each with
a subset of PROFINET nodes within the ring structure. The MRP Client only acts as a receiver
of data.
Page 143 / 242

In conformance class C PROFINET networks, the "Media Redundancy with Planned

Duplication of frames" (MRPD) can also be used. In order to use MRPD, all PROFINET nodes
in the ring have to support both MRP and MRPD.
MRPD, even in error-free operation, routes only certain PROFINET Realtime Telegrams from
the MRPD Manager via the redundant path. The MRPD Client in error-free operation thus
receives two telegrams containing identical information. In this case the data from the telegram
which has the MRPD Client has received first will be used. The second telegram will be
discarded without being used. Now if the ring is interrupted, the PROFINET nodes will continue
to receive data without interruption via the redundant path. In case 2 shown in Figure 7-3, the
outage of the switch, in spite of the ring structure, will cause an outage of the control system
which is connected to this switch. To further increase the plant availability, a high availability
plant network can be designed. The case of a high availability plant network will be described
on the following pages.
A ring structure minimizes downtimes caused by simple network outages,

e.g. in case PROFINET node within the ring structure is exchanged.
When planning a redundant ring structure, all PROFINET nodes in the ring
have to support the Media Redundancy Protocol (MRP). A PROFINET node
has to support the function of Redundancy Manager and has to be defined
as Redundancy Manager.
If one network component does not have this functionality, redundantly

connected links can cause communication problems or even network
outages. The PROFINET nodes can be configured using a web-based
interface or a vendor-dependent software.
In order to remove the risks of common cause failure of both transmission

paths, the return path to close the ring should be installed on a separate
cable tray. Cabling documentation should be adjusted accordingly.
Page 144 / 242

Figure 7-4 shows the structure of a network based on a high-availability plant network.
Figure 7-4: High-availability plant network
The redundant network construction is shown clearly. Each network node has two ports for
connection to the network. Each of these ports is connected via a separate bus system. One
of the systems each is in an active status.
A high-availability plant network requires considerable planning and involves

high costs!
These systems are therefore only used in special cases, such as e.g. in
process technology, which involve extremely high requirements in terms of
plant availability and application.
Here, a device exchange does not affect the communication of the other
network nodes, not causing any impact.
Switching times
Redundant systems always require some time to detect an interruption and to consequently
switch-over to the redundant path. Two types of redundant switch over can be used:
• Bumpless Changeover – This provides redundant switchover such that no data is lost
during an interruption or a device exchange
Page 145 / 242

• Non-Bumpless Changeover – In contrast, is where some data is lost during the

switching time.
In ring structures, PROFINET uses the Media Redundancy Protocol and the
Media Redundancy for Planned Duplication Protocol (MRP and MRPD). In
addition, PROFINET networks support the standard Ethernet redundancy
protocols.
You can find information about the scope of performance and the properties
of the different protocols in the PROFINET Media Redundancy Guideline for
PROFINET [MRE2018] and the High Availability Guideline for PROFINET
[HIG2020].
In particular, make sure that the switching time of the employed redundancy
protocol matches the application of the plant. Pay special attention to the
reconfiguration times.
7.2 Wireless transmission technology

PROFINET allows for the use of wireless transmission systems. In contrast to the use of cable-
based links, wireless technology uses the free space as transmission medium. In automation
technology, this commonly used medium is usually designed as an infrastructure network with
a central access point. Spontaneous networks without any central access point are rarely
used.
The usage of wireless technology requires the consideration of certain factors that do not
occur in connection with wired transmission technology. This includes terms such as:
• Attenuation in the free field upon visual contact (free-field attenuation),

• Reflection of radio waves from obstacles,
• Interference of mutually impairing signal sources with identical frequency
• Interference from other signal sources or
Page 146 / 242

• Scattering, diffraction and absorption of signals at surfaces and barriers,
All of which have an impact on the signal strength and quality of the wireless system. Figure
7-5 shows the different influences on wireless transmission technology.
Figure 7-5: Use of wireless transmission technology
To ensure full coverage of the supply area, an appropriate transmission field planning and site
survey must have been performed. The transmission field planning is used to determine the
impact on the propagation and the behavior of radio waves. It considers points such as special
conditions, i.e. factors such as also room dimensions, wall thicknesses, wall materials and
metal objects etc.
These factors can e.g. be determined by means of on-site measurements or by means of

checking the building and plant plans. Similarly it is possible to use simulation tools to model
the transmission field allowing prediction and better planning of the signal propagation from
building plans.
After completion of the installation, you should also measure the signal quality in the plant. For
further information see PROFINET Commissioning Guideline Order No.: 8.081.
Note that a wireless access point will require a free switch port.
Page 147 / 242

The fact that wireless systems support different data rates has an impact on the number of
wireless PROFINET network nodes or their update rate. You should therefore select a suitable
update time for the wireless network nodes.
Find out the gross or net data rate supported by your wireless access point
and use the network load calculation tool to design the wireless transmission
system.
The usually lower transmission rate of wireless networks, when compared

to a wired infrastructure, reduces the update rate in a wireless PROFINET
network.
This also reduces the maximum number of clients per access point.
The use of wireless transmission makes sense if a wired system cannot be

used or can only be used with difficulties, or if the use of wireless
transmission technology provides the required mobility and flexibility.
Good candidates for wireless transmission include autonomous guided

vehicles and extensive conveying systems. Wireless can however also be
used for short range sensor networks.
Wireless networks must be protected against unauthorized access from

outside. You have to take appropriate precautions for safeguarding your
wireless network.
This chapter can only give a first introduction to the topic. When using wireless transmission
technology, a more comprehensive design phase is required (e.g. regarding the geographical
coverage, frequency planning, etc.). This work is beyond the scope of this design guideline.
Page 148 / 242

7.3 Power over Ethernet

Power over Ethernet allows low consumption devices to be powered directly over the
PROFINET cable. No separate power supply is therefore required. This may save installation
costs. Typical devices which can be powered over Ethernet are:
• Access points (wireless)

• IP cameras
• HMIs and control stations
• Barcode readers
The PoE functionality must be supported by both the supplying device (e.g. a switch or
separate injector) and the powered device.
Using PoE is recommended if the installation of a power cable in parallel to the PROFINET
cable shall be avoided.
Please note that the utilization of Power over Ethernet implies limitations regarding the network
topology. A direct link must be provided between the supplying device and the powered device
(see Figure 7-6).
Figure 7-6: Topology limitations with Power over Ethernet
Page 149 / 242

Ethernet APL (see chapter 5) also provides power via the network cable. It
should be noted that the power delivery of APL is different to the power delivery
of Power over Ethernet (PoE). The two power concepts must not be mixed in a
system. It is not possible to connect device powered via PoE to an APL-Network
and it is not possible to connect an APL field device to e network with PoE.
Page 150 / 242

Definition of device parameters
8 Definition of device parameters
Page 151 / 242

After completing the planning for network nodes and network infrastructure, appropriate
parameters have to be assigned to the individual network nodes. These include the
• Device name and the

• IP address.
This chapter describes a systematic approach to the assignment of names and IP addresses.
All PROFINET devices need to have a unique device name and unique IP address. For other
network components such as switches this depends on their conformance class.
All PROFINET network nodes of conformance class B must have a device

name and an IP address. Switches of conformance class B can there for
also be considered as PROFINET devices with device names and IP
addresses.
Both address parameters can usually be assigned during the planning of

PROFINET devices, provided that they are supported by the network node.
Document the required address parameters of the devices unless this has
already been done during the device selection.
In order to clarify the topic, an example of ordered name and IP address assignment is shown
after the explanations. This is based on the already familiar system example from the previous
chapters.
Page 152 / 242

8.1 Assignment of names

Before a PROFINET device can communicate with a PROFINET controller, a device name
must be assigned to both communication partners.
Figure 8-1: PROFINET device (delivery status)
For PROFINET, this procedure has been selected since self-explanatory names are easier to
handle than IP addresses. In their original delivery status PROFINET devices do not have a
device name, but only a MAC address. This is stored in the PROFINET device, it is globally
unique and can usually not be modified. Many PROFINET devices have the MAC address
printed on the housing or on the rating plate.
PROFINET devices can be accessed by a PROFINET controller only after its device name
has been assigned. The device name must be stored by the device. If supported by the
PROFINET device, it can alternatively be directly written to a storage medium (for example an
SD card). The storage medium can then be inserted into the PROFINET device so that the
device name is read by the PROFINET device.
Page 153 / 242

The assignment of self-explanatory names will provide you with a better

overview of the plant to be commissioned and it facilitates the diagnosis.
You should therefore use such names for the individual communication
partners which will allow for conclusions as to the relevant plant part.
This device name shall consist of with 1 to 240 characters according to following the definition:
• One or more labels, separated by [.]

• Label length is 1 to 63 octets
• Total length is 1 to 240 octets
• Labels consist of [a-z, 0-9 or -]
• Labels do not start with [-]
• Labels do not end with [-]
Additionally:
• The first label shall not have the form “port-xyz” or “port-xyz-abcde” with a, b, c, d, e,
x, y, z = 0...9, to avoid wrong similarity with the field AliasNameValue.
• Station-names do not have the form a.b.c.d with a, b, c, d = 0...999
When selecting device names, please bear in mind the following considerations:
The device name should include an indication of the type of device. It thus makes sense for
the designation of a remote device to include the designation “remote-io” in the device name.
A drive should perhaps include the word “drive” etc.
It is well worth carefully considering using a device naming convention that gives useful
information to the maintenance engineer as to the location and function of the unit.
Page 154 / 242

8.2 Planning of IP addresses

Automatic address configuration
Figure 8-2: PROFINET device (address allocation)
The IP address is entered in the configuration of the PROFINET project. This is usually done
automatically. The address thus allocated will be transferred to the PROFINET device when
starting PROFINET controller. There is usually a fixed assignment of IP addresses to device
names. In addition, this can also be stored permanently. Addressing of a PROFINET device
therefore in total includes:
MAC address, which is predefined in the PROFINET device and can usually not be modified.
Device name, which can be flexibly selected, but which should be selected according to the
relevant plant part to facilitate the overview.
IP address, for which, just as for the name, a firm plan should be defined for the assignment
of addresses. You will thus facilitate the reference to the device types.
Information on address configuration
Page 155 / 242

The notation of the IPv4 address used in PROFINET networks consists of four decimal
numbers, each in the range between 0 and 255 and separated by a point, as e.g.
192.168.2.10.
In addition to the device name and the unchangeable MAC address, the IP address is required
to clearly identify a network node. In addition to the IP addresses used in public networks such
as the Internet, reserved address ranges have been allocated for private or non-public areas.
Table 8-1 shows the various private address ranges. The bold-faced figure indicates the
network, while the area behind it is uniquely assigned and thus clearly identifies the network
node.
Table 8-1: Private IPv4 address ranges
Number of
No. of Network
Class Address range nodes per
networks mask
network
10.0.0.0 to
1 Class A 255.0.0.0 16.8 million
10.255.255.255
172.16.0.0 to
16 Class B 255.255.0.0 65534
172.31.255.255
192.168.0.0 to
256 Class C 255.255.255.0 254
192.168.255.255
A network mask (sometimes called subnet mask) is assigned in parallel to the IP address. IP
address and net mask form a firm pair. The net mask notation corresponds to the IP address.
We recommend the use of private IP addresses. The use of public IP

addresses is under the responsibility of the plant operator.
Page 156 / 242

For the assignment, the following points should basically be observed:
• From the previous considerations, given the number of nodes in a network, select an
address range of appropriate size.
• Define an address table. Divide the PROFINET network nodes into classes. Define
a separate address range for each class.
• Any duplicate use of IP addresses is not permitted. Any use of identical IP
addresses will inevitably cause communication problems for the affected network
nodes.
In most cases, addressing using the private class C address range is

sufficient. For special cases where a larger address range with more than
254 addresses (Class C) is required, you can switch to a private class B or
class A network.
Remember that in large companies, IP addresses are usually assigned by

the department responsible for corporate networks.
Document the assignment of IP addresses and device names.
Page 157 / 242

8.3 PROFINET plant example

The assignment of IP addresses for a PROFINET automation plant will now be described as
an example, using the example plant previously used in this document.
Figure 8-3: Overall structure of example plant
Plant overview
The topology and the number of PROFINET devices for the plant have been defined during
the design. The result of this design has been assumed as follows:
Automation island A
• Number of PROFINET devices: 4

• Tree topology with connected line topology
• 2 switches, 1 controller
• supervisor, operating station, camera
Automation island B
• Number of PROFINET devices: 4

• Tree topology with connected line topology
• 2 switches (IRT function in one switch), 2 controllers
• IO supervisor, operating station
Higher level connection / control station
Page 158 / 242

• Star or tree topology

• Optical fiber connection
• 1 switch and 1 router
The summary of requirements results in the following number of IP addresses for the example
plant.
Table 8-2: Overview of number of PROFINET network nodes
Process automation plant
Automation island A
Number Number Controller /

2 4 1/1 Other 2
switches devices IO Supervisor
Automation island B
Number Number Controller /

2 4 2/1 Other 1
switches devices IO Supervisor
Higher level connection / control station
Number 1 (+ 1 Number Controller /

0 0/0 Other 0
switches Router) devices IO Supervisor
Address selection
When commissioning a large plant, you should create an address table where the most
important information about the PROFINET nodes can be entered. This will allow you at a
later stage to easily retrieve faulty PROFINET nodes or PROFINET nodes to be replaced.
Individual plant parts can be addressed using these addresses. It is a good idea to allocate
addresses in blocks for each plant area. An alternative scheme is to allocate address ranges
for different device types, such as switches, drives, remote IO etc. Some addresses should
be reserved in each block for future expansion.
A possible scheme for address allocation for our example plant might be as follows.
Page 159 / 242

Selection of IP Addresses
1. Different address ranges are assigned to the individual device types in the plant: (see
example)
Example Controller/Router: 192.168.2.1 to 192.168.2.19
Switches: 192.168.2.20 to 192.168.2.49
PN devices: 192.168.2.50 to 192.168.2.199
I/O: 192.168.2.50 to 192.168.2.99
Drives: 192.168.2.100 to
192.168.2.149
Panels: 192.168.2.150 to
192.168.2.199
Additional functions/ 192.168.2.200 to 192.168.2.254
Reserve:
The net mask here corresponds to the standard class C address range
(sub net mask “255.255.255.0”).
In case the selected address range is too small, a

similar structure can also be applied to the other
private IPv4 address ranges (class A / class B).
2. Each automation plant receives an address range
Page 160 / 242

Example Higher-level connection: 192.168.1.xxx
Automation plant 1: 192.168.2.xxx
Automation plant 2: 192.168.3.xxx etc.
Only a class C network is normally used for

automation plants. For the communication between
the individual automation plants with different address
ranges a router may be used for connection (IP-based
communication, only).
Selection of device names:
According to the structure as per chapter 8.1, the name for a PROFINET device e.g. looks
like:
1. The device name includes the designation of the type.
e.g.: Idevice "io" Switch "swi"
drive "drv" IO panel “hmi"
2. In addition to the device type, a consecutive numbering and / or a position identifier

should be included in the device name to describe the position of the device in the
plant.
e.g.: The second device of automation plant 1 in automation island 2 is named
"io.1.2.2"
In the selected example, "swi.1.0.1" includes the figure "0", indicating that this switch is
assigned to automation plant 1, but it is not assigned to a certain island in this plant. This
switch interconnects the islands and connects them to the higher-level router.
Page 161 / 242
Address selection
Using this notation, the following address assignment can be used for the plant example
Table 8-3: Address selection in automation plant 1
Name according to
Type Device name IP address:
planning
Router ROUT_V1 -/- 192.168.2.1
-/- -/- -/- -/-
PN controller CPU-123-AB cpu.1.1.1 192.168.2.2
PN controller CPU-345-CD cpu.1.2.1 192.168.2.3
PN controller CPU-678-EF cpu.1.2.2 192.168.2.4
Switch Switch-AB1 swi.1.0.1 192.168.2.20
Switch Switch-CD2 swi.1.1.1 192.168.2.21
Switch Switch-EF3 swi.1.1.2 192.168.2.22
Switch Switch-GH3 swi.1.2.3 192.168.2.23
Switch Switch-IJ4 swi.1.2.4 192.168.2.24
PN device I/O device V3 io.1.1.1 192.168.2.50
PN device I/O device-98 io.1.2.2 192.168.2.53
PN device DRIVE _IRT drv.1.1.1 192.168.2.100
PN device DRIVE _V2 drv.1.1.2 192.168.2.101
PN device DRIVE _V4 drv.1.2.1 192.168.2.102
PN device IO_PANEL_1 hmi.1.2.1 192.168.2.150
Page 162 / 242

Video camera CAM_V1 -/- 192.168.2.200
Control station STAT_1 -/- 192.168.2.201
Control station STAT_2 -/- 192.168.2.202
PN IO Supervisor IO_SUP_1 -/- 192.168.2.203
PN IO Supervisor IO_SUP_2 -/- 192.168.2.204
A table provides better overview of the plant, reducing the required work and saving time.
In this example, the switches receive a device name and an IP address.

These are required for switches as of conformance class B and have
therefore been selected in this example.
Page 163 / 242

Summary
9 Summary
Page 164 / 242

Summary
After completion of the PROFINET design, all information about your entire PROFINET
automation plant should be available to you. This includes information such as:
Communication relations with the data volumes to be transmitted and the geographical as
well as functional assignment of all PROFINET devices.
Component selection, such as PROFINET devices, switches, transmission media and

connectors, corresponding to the Conformance Class according to the PROFINET component
approach.
This also includes the requirements to communication and application.
Network topology of the automation plant under consideration of the data volumes to be
transmitted and communication relations of the plant parts. Extensions such as standard
Ethernet devices and potential network loads have been integrated in the topology structure.
A performance consideration reflecting common network loads of standard Ethernet

devices and PROFINET devices as well as their update times has been added to the topology
consideration.
Device parameters, such as IP address and device names.
In this context you should check whether all design information of your
PROFINET automation plant is available to you.
Page 165 / 242

Annex
10 Annex
Page 166 / 242

Annex
10.1 Addresses
PROFINET Competence Center
The PROFINET Competence Centers can be contacted in case of any problems with
PROFINET. The PROFINET Competence Centers have specialists who are able to help in
case of problems. The PROFINET Competence Centers also provide training.
You can find the current contact data of the PROFINET Competence
Centers online at
www.profinet.com
in the Support area.
10.2 Glossary
You will find important definitions about PROFINET in the PI Glossary on

page
www.profinet.com
under the search term "Glossary".
Page 167 / 242

Annex
10.3 Details about PROFINET copper cables

This section of the Annex provides detailed information about PROFINET copper cables.
Properties of PROFINET copper cables
Parameters of cable types
Table 10-1: Cable parameters PROFINET Type A copper cable
Parameter Specified limits
Impedance 100 Ω ± 15 Ω
Loop resistance <115 Ω/km
Transmission rate 100 Mbit/s
Max. cable length 100 m
Number of wires 4
Wire diameter 0.64 mm
Wire CSA 0.32 mm2 (AWG 22/1)
Sheath color green
Color of insulation white, blue, yellow, orange
Page 168 / 242

Annex
Table 10-2: Cable parameters PROFINET Type B copper cable
Number of wires 4
Wire CSA 0.36 mm2 (AWG 22/7)
Sheath color green
Table 10-3: Cable parameters PROFINET Type C copper cable
Number of wires 4
Wire CSA AWG 22/7 or 22/19
Sheath color green
Page 169 / 242

Annex
Table 10-4: Cable parameters PROFINET 8-core Type A copper cable
Loop resistance <85 Ω/km (AWG 23/1)
Number of wires 8
Wire diameter ≥0.546 mm (AWG 23/1)
Sheath color green
Color of insulation white / orange, white / green,

white / blue, white / brown
Table 10-5: Cable parameters PROFINET 8-core Type B copper cable
Loop resistance <85 Ω/km (AWG 23/7)
Number of wires 8
Wire CSA ≥0.254 mm2 (AWG 23/7)
Sheath color green

Page 170 / 242

Annex
Table 10-6: Cable parameters PROFINET 8-core Type C copper cable
Loop resistance <95 Ω/km (AWG 24)
Number of wires 8
Wire diameter Application-specific
Wire CSA Application-specific
Sheath color Application-specific

Page 171 / 242

Annex
Mechanical properties
In addition to the physical data (e.g. diameter and conductor material), the cable
manufacturers specify additional mechanical properties of the cable which provide information
about the application ranges and installation options of the cables. Typical manufacturer
specifications are:
• Bending radius
• Bending frequency
• Tensile strength
While the bending radius and the bending frequency mainly depend on the wire design
(fixed / flexible), additional elements such as aramid fibers are added to the cable to achieve
a higher tensile strength.
The limit values listed in Table 10-7 have been taken from the IEC 61784-5-3 standard.
Table 10-7: Mechanical properties of PROFINET copper cables
Specified
Parameter
limits
Minimum bending radius, single bent 20…65 mm
Bending radius, multi-bent 50…100 mm
Tensile force <150 N
Permanent tensile load < 50 N
Maximum shear force --
Temperature range during installation -20…+60 °C
The limit specifications depend on the cable type. For more detailed
information, please see the manufacturer specifications.
Page 172 / 242

Annex
Chemical properties
PROFINET copper cables are available with different sheath materials to protect them against
environmental influences.
Cable manufacturers specify the properties or the existence of a certain material (e.g.
halogen / silicone) in the cable datasheets. Typical manufacturer specifications are:
• UV resistance
• Freedom from silicone
• Resistance against mineral oils and greases
• Permissible temperature ranges
Special attention must be paid to the flammability of the cables. The relevant data are usually
provided separately by the cable manufacturers, with reference to the following properties:
• Freedom from halogen

• Flame retardance
• Smoke density
The smoke density is closely related to the freedom from halogen and is not
specified by all manufacturers. Therefore, also pay special attention to
additional specifications like FRNC (Flame-Retardant-Non-Corrosive). The
acronym FRNC indicates that a cable is halogen-free and flame-retardant.
Only halogen-free and flame-retardant cables may be used in areas where,

in case of fire, human life is endangered by toxic gas and smoke gas.
Page 173 / 242

Annex
Types of copper cables
PROFINET cable
This section describes PROFINET cables with 2 wire pairs. The specifications for 4-pair cables
are similar.
The most usual material for the PROFINET cable sheath is PVC (PolyVinylChloride). PVC is
generally UV resistant & chemically non-reactive. It is resistant to water, salt solutions, alcohol
and light caustic/acid/oil. However, PVC is not suitable for hydrocarbons or organic solvents
and has a restricted temperature range (-30 °C to +70 °C).
Type A PROFINET cables usually meet most requirements of automation projects and
therefore they are the most frequently used type of cable. As a round cable they have four
wires and are radially symmetric. The wires are stranded to form a so-called star quad.
Figure 10-1: PROFINET cable type A
The PROFINET cable type A has been designed for static installation, e.g.
in cable trays.
Page 174 / 242

Annex
PROFINET PE cable
A PE (PolyEthylene) sheath has better electrical properties than PVC. Excellent moisture
resistance makes PE cables suitable for direct burial and damp environments. PE cables with
black sheath are in addition UV resistant. The only difference to type A copper cables is the
different sheath color and the sheath material.
Figure 10-2: PROFINET PE cable
PE cables are suitable for installation in areas where constant humidity must
be expected. Due to the PE sheath, the cable, without any flame-resistant
additive, is flammable.
Page 175 / 242

Annex
PROFINET ground cable
PROFINET ground cables have robust, black outer sheaths made of PE. In many cases, this
is applied to the PROFINET cable as an additional sheath. After removing the outer sheath,
the uncovered PROFINET cable can be used and assembled as usual.
Figure 10-3: PROFINET ground cable
Suitable for outdoor installation or installation in the ground.
Cables with additional protection against rodents are also available. This
protection is ensured by means of additional, metal or fiber-based mesh.
Observe the manufacturer information about this.
Page 176 / 242

Annex
Trailing cable
The wires of this cable type consist of thin-wired braid, enabling the cable to be used at flexible
machine parts. The quad star four-wire structure increases the crush and tread resistance.
The sheath of this cable type is usually halogen-free and resistant against mineral oil and
grease.
Figure 10-4: Trailing cable
Specially designed cables should be used in cases where the cable will be
subject to frequent flexing or bending, such as with mobile machine parts for
example. Special cables are also available for trailing chains.
Page 177 / 242

Annex
Festoon cable
The wires of this type of cable (similar to trailing cables) consist of thin-wire braid, enabling
the cable to be used for festoon applications. The quad star four-wire structure increases the
crush and tread resistance. The sheath of this cable version is usually halogen-free and
resistant against mineral oil and grease.
Figure 10-5: Cables for festoons
Specially designed festoon cables should be used in cases where the cable
will be subject to permanent movement, such as with mobile machine parts,
hoists and cranes. Special cables are also available for torsional movement.
Page 178 / 242

Annex
Flame retardant non-corrosive cables (FRNC cable)
FRNC (Flame Retardant Non-Corrosive) cable is made with a sheath of halogen-free material
for use where flammability is to be avoided. The sheath color of FRNC cable is normally green.
You should use halogen-free cable for applications in areas where in case
of fire there are more demanding requirements to the fire behavior of the
cable. Possible places of application e.g. are residential buildings or
hospitals.
Ethernet APL Cables
The supported Ethernet-APL cable is a balanced, shielded twisted-pair cable with a

characteristic impedance in the range of 100 Ω ± 20 % in a frequency range of 100 kHz to
20 MHz as typically used for PROFIBUS PA and FOUNDATION Fieldbus H1. Wire diameters
can be in the range of 26AWG (0.14 mm²) to 14AWG (2.5 mm²) either with solid or stranded
wires. Cable parameters for Ethernet-APL cables can be found in the Ethernet-APL
Engineering-Guideline [APL2021] as well as in the Ethernet APL Port Profile Specification
[APS2021]. Figure 10-6 shows the structure of the Ethernet-APL cable.
Figure 10-6: Ethernet-APL cable
Page 179 / 242

Annex
10.4 Details about PROFINET optical fibers

This section of the Annex provides detailed information about PROFINET optical fibers.
Properties of PROFINET optical fibers
Mechanical properties
The mechanical properties of cables give information about possible types of application and
installation. In order to get an overview, the following tables show detailed values for typical
mechanical properties of optical fibers. The tables differentiate between the fiber types used.
The limit values listed in Table 10-8 and Table 10-9 have been taken from the IEC 61784-5-3
standard.
Table 10-8: Mechanical properties of single / multimode FO
Minimum bending radius, single bent minimum 50…200 mm
Bending radius, multi-bent minimum 30…200 mm
Tensile force maximum 500…800 N
Permanent tensile load maximum 500…800 N
Shear forces maximum 300...500 N/cm
Page 180 / 242

Annex
Table 10-9: Mechanical properties of POF optical fibers
Specified
Parameter
limits
Minimum bending radius, single bent minimum 30…100 N
Bending radius, multi-bent minimum 50…150 N
Permanent tensile load maximum not allowed
Shear forces maximum 35…100 N/cm
Temperature range during installation 0…+50 °C
The limit values listed in Table 10-10 have been taken from the IEC 61784-5-3 standard.
Table 10-10: Mechanical properties of PCF optical fibers
Specified
Parameter
limits
Minimum bending radius, single bent minimum 75…200 mm
Bending radius, multi-bent minimum 75…200 mm
Permanent tensile load maximum < 100 N
Shear forces maximum 75…300 N/cm
The limit specifications depend on the cable type. For more detailed
information, see the manufacturer specifications.
Page 181 / 242

Annex
The cable properties in the tables above meet the requirements of common industrial
applications. Special applications such as trailing cables, festoons or torsional movements
require adjusted cable designs with extended properties.
Chemical properties
FO cables, just as the previously described copper cables, have different sheath materials,
giving them certain properties.
• Typical manufacturer specifications are:

• UV resistance
• Freedom from silicone
• Resistance against mineral oils and greases
• Permitted temperatures
For FO cables as well, special attention must be paid to the fire behavior of the cable.
Manufacturer data for this include:
• Freedom from halogen

• Flame retardance
• Smoke density
Only halogen-free and flame-retardant cables may be used in areas where,

in case of fire, human life is endangered by toxic gas and smoke gas.
Page 182 / 242

Annex
Types of FO cables
The cable types most commonly used for PROFINET, with their applications, are listed in
Table 1-1. The cable types described can use all fiber types mentioned in section 3.2.4.
Additional protection including rodent-protection or special cables for ground installation, are
also available.
Table 10-11: Types of FO cables
Cable version Applications
For simple point-to-point links between two

PROFINET FO cable
PROFINET devices
PROFINET FO trailing
For installation at moving machine parts.
cable
PROFINET FO cable
Figure 10-6 shows the general structure of a PROFINET FO cable. It consists of two parallel
wires. The wires are suitable for direct assembly of connectors. The orange wire is printed
with directional arrows to facilitate the assignment of wires to the transmit and receive
connections.
Figure 10-7: PROFINET optical fiber cable
Page 183 / 242

Annex
PROFINET FO trailing cable
The FO trailing cable (Figure 10-8) has additional non-woven wrapping as well as strain relief
elements and an additional support element. The sheath of this cable type is usually halogen-
free and resistant against mineral oil and grease.
You should use specially designed cables in case the cable will be subject
to frequent movement, such as e.g. the use at mobile machine parts.
PROFINET FO trailing cables are available with all common fiber types.
Cables for use in trailing chains can normally not be used as festoons.
Figure 10-8: PROFINET FO trailing cable
Page 184 / 242

Annex
10.5 Selection of connectors

This chapter will describe these requirements in more detail so that your previous planning
can be completed with suitable connection technology as required for your application.
This chapter covers the following subjects:
• Explanation of differences between pre-assembled cables and cables for field-

assembly
• Introduction of available connection systems
• Selection of required connectors
Differences between pre-assembled cables and cables for field-assembly
Pre-assembled cables
Pre-assembled cables are delivered with connectors fitted on both ends of the cable. Such
pre-assembled cables can only be used if you know the exact distance between the individual
network components (observe cable routing).
Advantages of pre-assembled cables:
• Reduction of installation time since no cable assembly is required.

• Potential assembly mistakes are avoided.
• The installation personnel does not need any training for the assembly of PROFINET
cables.
• No special assembly tools required.
• Suitable in particular for wiring cabinets.
Disadvantages of pre-assembled cables:
• The assembled connectors could be obstructive or could be damaged when installing

the cables.
• Cable lengths must be specified when ordering the cables.
• If pre-assembled cables are too long, the excessive cable length must be
accommodated correctly.
Page 185 / 242

Annex
Cables for field-assembly
Cables for field assembly are delivered by the manufacturer as bulk material without any
connectors and have to be assembled on site by the installation personnel.
Advantages of cables for field-assembly:
• Cable lengths do not have to be specified when ordering the cables.

• Cables are easier to install without connectors attached.
Disadvantages of cables for field-assembly:
• Assembly on site requires additional time.

• Special tools are required.
• The installer needs to be trained for the assembly of PROFINET cables.
• Potential source of errors (acceptance measurement is recommended).
Please contact your cable manufacturer or the manufacturer of the

connection system required for your installation to find out which assembly
tools are required.
For more detailed information about the assembly of connectors and cables,
please see the PROFINET Installation Guideline Order No.: 8.072.
Connection systems for copper cables
This chapter describes the connection systems for copper cables with different protection
types, using various figures.
The connectors shown in the figures below (Figure 10-9 and Figure 10-10)
are generic drawings based on models typically available on the market. The
real design depends on each manufacturer.
Page 186 / 242

Annex
Connectors
RJ45 connectors
RJ45 connectors are suitable for use with terminal devices and network components. A major
criterion for the potential use of connectors is their manageability on site. Inside cabinets, RJ45
connectors are used in the IP20 version. Outside cabinets, the rugged environmental
conditions must be accounted for. In such cases, an RJ45 push-pull connector in IP65 or IP67
version can be used. Another advantage of RJ45 connectors is that they are often used for
connection of engineering tools or laptops etc allowing these to be easily and quickly
connected for service purposes.
Figure 10-9 and Figure 10-10 show two versions of RJ45 connectors with different protection
classes.
Figure 10-9: Typical RJ45 push-pull connector with IP65 rating
Figure 10-10: Typical RJ45 push-pull connector with IP20 rating
Page 187 / 242

Annex
M12 D-coded connector
For applications in rugged industrial environments with IP67 protection class, the PNO has
specified the M12 connector which allows for the safe connection of sensors / actors. The M12
D-coded connector has been standardized in IEC 61076-2-101.
Plug Socket
Figure 10-11: Typical D-coded M12 connector
M12 TypeX connector
The M12 TypeX connector is suited for applications in rugged industrial environments with
high transmission rates. The M12 Type X has been standardized in IEC 61076-2-109.
Figure 10-12: Typical M12 TypeX connector
Page 188 / 242

Annex
Connection systems for optical fiber
The optical interfaces of PROFINET devices have to meet the specifications for multi-mode
fibers (IEC 9314-3) and for single-mode fibers (IEC 9314-4). Non-permanent and permanent
connections of PROFINET FO connectors are differentiated. These connectors should only
be assembled by trained personnel using appropriate special tools.
For more detailed information about the assembly of FO connectors and

cables, please see the PROFINET Installation Guideline Order No.: 8.072.
Please contact your cable manufacturer or the manufacturer of the ordered

connection system required for your installation to find out which assembly
tools are required.
Permanent FO connections are always implemented by means of so-called splicing. Splicing

is mainly used in order to extend FO cables or to repair broken fiber.
Connectors
The connectors shown in the figures below (Figure 10-12 and Figure 10-13)
are generic drawings based on models typically available on the market. The
real design depends on each manufacturer.
Page 189 / 242

Annex
SCRJ connectors
The SCRJ is used for PROFINET data transmission via FO. The basic version of this
connector has been developed for use in switch cabinets (IP20 protection class). The SCRJ
push-pull version (Figure 10-14) is used for rugged environments or IP65 / IP67 requirements.
Figure 10-13: Typical SCRJ push-pull connector with IP20 rating
Figure 10-14: Typical SCRJ push-pull connector with IP65 rating
Page 190 / 242

Annex
Figure 10-15: Typical LC-Connector with IP20 rating
M12 hybrid connector
The M12 hybrid connector (Figure 10-16) provides two optical connections for data
transmission plus two optional electrical connections. For PROFINET applications, the
electrical connections are normally not used. The connector is available for use with multi-
mode, single-mode, POF and PCF fibers.
Two single FO fibers
Figure 10-16: Typical M12 hybrid connector
Connector types BFOC and SC
Page 191 / 242

Annex
The use of connector types BFOC / 2,5 (IEC 60874-10) and of the SC plug
system (IEC 60874-14) is not recommended for new automation plants.
Transition points
Transition points are potential connection points for PROFINET cables for further distribution.
Connectors with protection class IP65 / IP67 are available for use in rugged environments,
while modules with protection class IP20 are available for use in switch or distribution cabinets.
The various distributors and sockets are also differentiated by:
• the number and type of ports (copper or FO),

• maximum number of plug cycles (insertions),
• the connection technology (special tools may be required) and
• the protection class.
Please see the manufacturer data for more detailed information concerning
the technical properties of the required transition points.
Figure 10-17 and Figure 10-18 show two examples of RJ45 distributors with different
protection classes which are based on the models available on the market.
Page 192 / 242

Annex
RJ45 sockets
Figure 10-17: RJ45 distribution module for top hat rail mounting in IP20 environments
Distribution modules are available for IP20 environments for all commonly used FO and
copper connectors with appropriate sockets.
Top hat rail mounted distribution modules should be used for the transition
of the fixed cabling to the internal cabling of the cabinet with patch or adapter
cables.
RJ45 socket
Figure 10-18: RJ45 connection socket for IP65 / IP67 environments
Page 193 / 242

Annex
Connection sockets for all commonly used FO and copper connectors with appropriate ports
and sockets are available from many different manufacturers.
Connection sockets should be used for the transition from fixed to flexible
cabling in the field. Connections in trailing chains can thus be replaced
easily.
Bulkhead Connectors
Bulkhead connectors can be used for securely passing external PROFINET copper cables or
optical fibers into a cabinet. Such connectors provide transition from an IP65 / IP67 external
environment to an IP20 internal environment.
Please see the manufacturer data for more detailed information concerning
the technical properties of the required bulkhead connectors.
Figure 10-19 shows an RJ45 Push-Pull wall duct and Figure 10-20 shows an M12 wall duct.
These wall ducts are generic drawings based on models currently available on the market.
External RJ45 socket in

IP65 environment
Internal RJ45 socket

in IP20 environment
(cabinet)
Figure 10-19: RJ45 Push-Pull bulkhead connector for use with cabinets
Page 194 / 242

Annex
Internal RJ45 socket

in IP20 environment
(cabinet)
External M12 socket in
IP65 environment
Figure 10-20: M12 bulkhead connector for use with cabinets
10.6 Cabling examples

Two examples for the component selection for FO and copper cabling are shown below. A
sample calculation of the attenuation balance is also provided.
Example copper cables
The copper-based, star-topology cabling shown in Figure 10-21 illustrates how the required
components could be selected.
Figure 10-21: Examples of copper-based cabling
Page 195 / 242

Annex
Table 10-12 shows the material list for the copper-based cabling described on the previous
page.
Table 10-12: Material list copper-based cabling
Number Name
Pre-assembled PROFINET cable with RJ45 connectors

1
within an IP20 environment.
Pre-assembled PROFINET cable with RJ45 connectors in

2
IP65 / IP67 environment.
PROFINET cable for field assembly,

3
for static installation with RJ45 connectors in IP65 / IP67
environment and RJ45 connectors in an IP20 environment.
Pre-assembled PROFINET cable with M12 connectors for

4
use in an IP65 / IP67 environment.
Bulkhead connector
5
from RJ45 IP65 / IP67 to RJ45 IP20
Pre-assembled PROFINET cable, for fixed installation with

6
RJ45 connectors in an IP20 environment.
PROFINET cable for assembly in the field, suited for trailing

7
chain, with RJ45 connectors in an IP65 / IP67 environment.
Bulkhead connector
8
from M12 IP65 / IP67 to RJ45 IP20
9 RJ45 connection socket for an IP65 / IP67 environment.
Page 196 / 242

Annex
The FO-based, star-topology cabling shown in Figure 10-22 is supposed to illustrate how the
required components could be selected.
Figure 10-22: Example of FO cabling
Passive couplings such as bulkhead connectors or connection socket will

increase the signal attenuation and thus reduce the available cable length.
For example, each passive coupling used in POF cables will reduce the
maximum cable length by 6.5 m. Thus two passive couplings will reduce the
maximum POF cable length from 50 m to 50 m - 2 ⋅ 6.5 m = 37 m.
Page 197 / 242

Annex
Table 10-13 shows the material list for the FO-based cabling described on the previous page.
Table 10-13: Material list FO cabling
Number Name
Pre-assembled FO cable, with SCRJ connectors in IP65 /

1
IP67 and IP20 environments at each end.
Pre-assembled POF cable, with SCRJ connectors in IP65 /

2
IP67 and IP20 environments at each end.
SCRJ bulkhead connector from IP65 / IP67 to IP20

3
environment.
Pre-assembled adapter cable with SCRJ connectors in an

4
IP20 environment.
Couplings and connectors are available from many different manufacturers,

in multiple versions for different environments and applications. Consult
manufacturers’ information to select suitable connection technology for your
application.
Document your selection of connection technology.
Page 198 / 242

Annex
Calculation examples
Two examples will now be examined illustrating the calculation of attenuation and power
budget.
Figure 10-23 shows a simple example based on a single-mode optical fiber cable.
Figure 10-23: Representation of attenuation balance for single-mode optical fiber links
Note that it is important to account for the total number of connections used
and not the number of connectors.
Table 10-14 shows the individual passive components, the attenuation caused by them and
the total attenuation for the example in Figure 10-23. The attenuation of the fiber is based on
0.5 dB/km and the connections introduce 0.75 dB each. According to Table 3-4, the maximum
permissible PROFINET end-to-end-link attenuation is 10.3 dB.
Page 199 / 242

Annex
Attenuation balance:
Table 10-14: Calculation of end-to-end link attenuation for single-mode fibers
Fiber 1 Connections Fiber 2

Total attenuation
500 m (Con. 1+2/3+4) 2 000 m
0.25 dB 3 ∙0.75 dB 1 dB = 3.5 dB
maximum permissible attenuation is 10.3 dB
Figure 10-24 shows the attenuation calculation based on a polymer fiber link (POF).
Figure 10-24: Representation of attenuation balance for POF FO link
Table 10-15 shows the individual passive components, the attenuation caused by them and
the total attenuation for the example in Figure 10-24. Acc. to Table 3-4, the maximum
permissible PROFINET end-to-end-link attenuation is 11.5 dB.
Page 200 / 242

Annex
Attenuation balance:
Table 10-15: Calculation of end-to-end link attenuation for polymer fiber links
Fiber 1 Connections Fiber 2 Fiber 3

Total attenuation
10 m (Conn 1+2/3+4/5+6) 35 m 5m
2.3 dB 4 ∙1.5 dB 8.05 dB 1.15 dB = 17.5 dB
maximum permissible attenuation is 11.5 dB
As can be seen, the PROFINET end-to-end link attenuation in this example exceeds the
maximum permissible value. To achieve a value of ≤ 11.5 dB, either the transmission link or
the number of passive couplings would have to be reduced.
The calculation and, if applicable, the graphical representation of the

attenuation balance shows whether the planned FO link meets the
transmission requirements.
Page 201 / 242

Annex
10.7 Selection of switches

Switches suited for PROFINET are designed for Fast Ethernet (100Mbit/s, IEEE 802.3u) and
full duplex transmission. In full duplex operation a switch simultaneously transmits and
receives data at the port. There are no collisions.
Switches are available in IP20 versions for top hat rail installation and in IP65/67 versions for
field installation. The following section describes some functions of switches which are
considered in the selection. The switches are first categorized in two types:
• Unmanaged switches
• Managed switches (with additional PROFINET functionality)
The advantage of PROFINET is the prioritization of the PROFINET data

traffic. This feature however is only ensured if switches with „Quality of
Service“ (QoS) support are being used (IEEE 802.1q / p).
Unmanaged switches
Unmanaged switches route the entire data traffic based on the address / port allocation table.
Users are not able to intervene manually. This is a low-cost version of a switch.
Unmanaged switches do not offer a web interface and have no diagnostic

functions.
This type of switch is used in conformance class A networks.
Page 202 / 242

Annex
Managed switches
Managed switches offer several advantages over unmanaged switches. These include user
option selection based on a web interface and diagnostics capability. The functionality of the
management software is different among various switch types, including features ranging from
redundancy control up to statistical analysis of network data traffic.
Managed switches support diagnosis functions. The offered switch

functionality is controlled and read out either via a web-based interface or
via a suitable engineering tool.
To make sure a switch can be identified as PROFINET device, the switch

has to support the PROFINET services. The identification of a switch as
PROFINET device is foreseen as of conformance class B networks.
Managed switches should be used in conformance class B and C networks
Switches can also be selected as “cut through” or “store and forward”.
Cut through switches
Cut through switches give less delay than store and forward switches. This is because the
frame is forwarded directly once the destination address is determined. The switch will buffer
only as many bytes of the data packet as are required for analysis of the address / port
allocation table. Then all incoming bytes of the data packet are sent directly to the relevant
port without any buffering. The routing delay thus does not depend on the frame size.
Page 203 / 242

Annex
Store and Forward Switches
Store and Forward switches read and buffer the complete data packet on the incoming port.
The switch checks the whole frame for errors and, if error free, sends it to the relevant port.
This can cause longer delay times than for switches using the cut through technology. The
delay depends on the telegram size of the data packet to be transmitted.
Auto-sensing / Auto-negotiation
Auto-sensing describes the ability of a device to automatically identify the transmission rate of
a signal.
Auto-negotiation additionally allows the involved devices to jointly negotiate and agree upon
the transmission rate before the first data transmission is started.
If Fast Start-up is used at one port, auto-negotiation should be disabled in

order to further optimize the start-up time.
Auto Cross-Over
Auto Cross-Over provides automatic crossing of transmit and receive lines at a port interfaces.
If this function is deactivated, a cross-over cable or a switch with port wiring for crossing of
connections is sometimes required.
If Fast Start-up is used at one port, auto cross-over should be disabled in

order to further optimize the start-up time.
Page 204 / 242

Annex
Redundancy support
The redundancy support allows for bumpless or non-bumpless changeover of failed links to a
redundant link.
The implementation of redundancy with PROFINET is only achieved by

means of managed switches which support an appropriate Media
Redundancy Protocol (MRP) and which are configured via an engineering
tool or a web-based service.
Port mirroring
Port mirroring is a helpful function for diagnosis in a network. It provides a copy of all the
inbound and outbound data from one port (the mirrored port) of a switch to another port (the
mirror port) in order to analyze the data frames. Most switches with port mirroring allow the
selection and configuration of the mirrored and mirror port from a web page in the switch.
Note that port mirroring is generally only available on managed switches.

Also note that many managed switches do not support port mirroring.
Always ensure that the selected switch supports port mirroring if required.
You will find further information about the diagnostics options in the
PROFINET Commissioning Guideline Order No.: 8.081.
Power over Ethernet
Power over Ethernet (PoE) allows devices with this facility to be powered from the Ethernet
cable. A switch with a PoE injector is required.
Page 205 / 242

Annex
Switches with PoE functionality are available in various variants with

different maximum power specifications. Select the appropriate type
according to the number of components to be supplied.
Gigabit Ethernet
If the implementation of PROFINET networks with a transmission rate of 1 000 Mbit is

intended, this must also be supported by the switches. Select the corresponding models with
the required number of ports supporting Gbit transmission.
Support of the relevant conformance class
As mentioned before, a switch also has to meet the respective requirements to the
conformance class.
The manufacturer must indicate the conformance class for which the switch
is suitable. You should only use switches that have been certified by PI.
10.8 Functional equipotential bonding and shielding by PROFINET

Information about the functional equipotential bonding and shielding can be found in the
guideline Functional Bonding and Shielding for PROFIBUS and PROFINET, Order No.: 8.102.
Page 206 / 242

Annex
10.9 PROFINET Documentation

This chapter makes a proposal for the documentation of PROFINET networks. The notes are
to be regarded as recommendations. Depending on the conditions in the system or in the
company, it is possible to deviate from the specifications.
10.9.1 PROFINET information relevant for documentation
Prior to starting the documentation, the following aspects should be clarified:

• Responsibilities
- For the creation of the network documentation
- For the management of the network documentation
- Are there any persons responsible for the plant? Are there any responsibilities
for individual plant sections?
• How and where will the documentation be distributed?
The cover page should contain all relevant information needed for identifying the document:
• ID of the documentation
- Document type (here: Network documentation)
- ID number / name
- Date of issue
- Revision index or version
- Revision date
- Document status (is it a draft or final version?)
- Specific data (customer name, plant name)
• Information on the creator
- Company name
- Company address
- Responsible author
The network documentation should range from a network overview for the entire plant over
detailed views of the networks of plant section up to device-specific information. A topology
overview is a visual representation and, hence, provides a good introduction.
• For example, an R&I diagram, plant structure or the architecture of the premises.
• Enter the assets into the drawing
- Automation devices
- Network infrastructure
 Cabling including patch fields
 The cabling order must be represented correctly.
 Ring topologies must be marked.
Page 207 / 242

Annex
- The persons responsible of the plant must be noted.

• The identifiers/names of the devices must be included.
- Device type (e.g. PLC, switch, repeater, etc.)
- Make a clear allocation to the locality.
 Specify the building (part).
 Specify the room.
 Make a note of the spot height to allow for easy device localization (e.g.
in a high-bay storage).
 Note the cabinet.
• The connection terminals (ports) of the devices must be designated.
• Segmentation plan
• Information on the cable
- Cable length between two nodes
- Used cable type (included in cable list?)
- Note the medium (copper, FO).
 Where are converters from copper media to optical media used?
For reasons of simplicity, further information should be documented in a separate Annex about
topology.
• Information on the products

- Manufacturer
- Serial numbers of the devices
- Model name / type designation
- Spare parts
 Serial number
 Type number
 Version number
 Supplier (or alternative supplier)
 Reference picture
- Store data sheets.
- Describe the device functionality.
- Certificates
- Document the used software or firmware revision levels.
• Document the reference measurements of the network.
- Measure and document the network load in normal operation.
- Mark any points where EMC disturbances have to be expected.
- Validation report of the physical layer (what are the physical variables during
commissioning?)
- Validation report of the communication layer (what does data modulation look
like?)
Page 208 / 242

Annex
- Validation report of the hazardous area (which devices are used in the
hazardous area?) Are these devices certified?
- Are there any delays? How long is the delay?
• Information for cases of faults
- List for fault localization
- Description of integrated diagnostic systems
- Drawings and diagrams
- Contact information for further help (hotline/support)
- Who is responsible of the plant (parts)?
Further information needs to be documented for PROFINET networks.
• Document the device name in the topology plan.

• Note the IP address on the device in the topology plan.
• Note the subnet mask on the device in the topology plan.
• List the MAC addresses of the devices.
• Are the GSD saved? Which GSD are used?
• Which protocols are used? Which services are supported?
• Ring topology and corresponding switch-over times
The following special documentation items must be listed for an IT security audit:
• When firewalls are used

- Is the firewall password-protected?
- Mark the (physical and logical) installation site.
- Document the set of rules for the firewalls.
• Virus scanner
- Does it exist?
- How often is it updated?
- How often is the segment scanned?
• Which ports/services are active?
• Does the current firmware revision levels feature any security gaps?
• Do VLANs exist?
• Passwords
- Do they exist?
- Was the default password, if any, changed?
- Are access rights to the passwords defined?
• Are access rights to sensitive rooms defined? (R&D)
• Documentation of employee training
• Is an emergency manual available?
Which rules of conduct are to be followed in the event of a cyber attack?
Page 209 / 242

Annex
10.9.2 Proposal for a PROFINET forwards documentation
This section is intended to further explain the information in section 10.9.1. The individual
steps of forwards documentation are discussed and the difficulties are described.
A network documentation often addresses more than one target group (persons in charge of
the installation, revision, operation, troubleshooting or audit). In a simplified approach,
however, it is possible to identify two fields of interest (see Figure 10-25).
Figure 10-25: Fields of interest in a plant lifecycle
As the installation and revision departments normally use electrical wiring diagrams, the plant
operators are the main target group of the network documentation.
The next step defines the format in which the network documentation is to be created. It must
be clarified whether printed plans are to be published or digital documentation is to be used
instead. Mind the fact that sensitive data must be access-protected. Digital plans must be
saved in a file format which ensures (read and write) access and data readability and integrity.
Also pay attention to the retention obligation. The documentation must be available for the
retention period.
The persons responsible for the document creation and management during the operation
phase must be defined. For large companies or plants the persons responsible for the
corresponding plant or plant sections must be contacted.
Every forwards documentation begins with a cover page. The cover page should provide the
information relevant for identification (plant, creator, responsibility). The document revision
information (index, date) provides the revision level and allows you to clearly determine
Page 210 / 242

Annex
whether the document is up to date. It is also useful to indicate the status on the cover page.
Moreover, it must be possible to clearly identify the creator for possible questions.
A table of contents must be included after the cover page. The more details the table of
contents contains, the better, as you can directly access the information needed.
Begin with the topology plan. It is helpful to use the architecture or an R&I diagram as a
template. All necessary network nodes must be integrated and numbered consecutively.
Assign unique device names. The name should indicate the type or function of a node and
also its location (building or building part, room). The spot height can also be provided. Add
the IP address and subnet mask of each device to the topology. The plan must allow for easy
identification of the responsibility for the segments or building parts.
Document all cables and connectors in the correct order. The port of each node must be noted
in the plan to allow for unique identification of the device connectors. Special attention must
be paid to patch field. Ring topologies must be marked expressly. It is useful to assign a unique
name to each connection (does a cable list exist?) and to note down the length of the laid
cables. If different media (copper or FO cables, wireless) are to be used, these must be drawn
differently.
Any further information and details should be moved to the Annex in order to keep the actual
overview short and clear. It is recommended to list all further information in the Annex in a
table and group the individual items by categories (product, cable).
Page 211 / 242

Annex
Table 10-16 shows further information. Record the used protocols and services of the
individual devices. All data sheets and certificates must also be stored. It is recommended to
record in the documentation not only the information shown in Table 10-16, but also the type
number, (alternative) suppliers and a picture of the node.
Add a network load calculation and measurement results of the network load in the individual
segments to the documentation. Also record the data communication delays in the
commissioning phase. Areas where EMC disturbances are likely to occur must also be
marked. It is helpful to add a validation report for the physical layer and the communication
layer. The reports should indicate whether and to which extent the physical (current, voltage)
and communication-related (edge rise and fall times) PROFINET requirements were initially
met by the plant.
Mark all integrated diagnostic systems and note the data of contact persons who may provide
support (e.g. line manager, consultant engineer, hotline and support).
Page 212 / 242

Annex
Table 10-16: Further information on the devices in the topology
No. Device name Manufacturer Model/type MAC address HW Firmware Serial number
revision revision level
level
1 Sw.HA1.1 Manufacturer 1 Switch 12 12-34-56-78-9A-BC 1.3 1.3.1 ABC-12345
2 PLC.HA1.1 Manufacturer 2 PLC 5 13-24-56-11-90-01 2.0 2.2 1920-1812-8212-0
Page 213 / 242

Annex
Additional information must be provided for an IT security audit. All places where firewalls are
used must be marked in the topology to allow for the assessment of the IT security. Document
the set of rules for each firewall. Also document whether default passwords were changed. In
order to prevent any loss of knowledge or data in the event of illness, accident, death or job
change of an employee, it is recommended to create and maintain a password list. Mind the
access restriction and protection. Additionally, you should document all employee trainings
related to IT security and have an emergency manual with rules of conduct to be followed in
the event of a cyber attack. When using a virus scanner, document the update intervals and
the frequency of virus scans. Also document all existing VLANs.
10.9.3 Example of a PROFINET forwards documentation
Table 10-17 shows the preliminary considerations.
Table 10-17: Example of PROFINET forwards documentation, preliminary considerations
Target group Operator, special knowledge yes, special language yes
Target country/language Germany/German
Type of publication Printed documents, centrally managed plans, access only by

counter-signature
Number of copies 3 (1 design dpt, 1 operator, 1 external backup copy)
Retention period 12 years, ensured by storage of printed plans in different

locations
Creation Company A, Mr. Sample
Management Company B, Ms. Example
Responsibilities
Ms. Meyer (administration
Plant Mr. Smith (hall 1)
Ms. Schulz (hall 2)
Page 214 / 242

Annex
Figure 10-25 shows a cover page example.
Figure 10-26: Cover page example for PROFINET forwards documentation
The information provided on the cover page should be repeated on all other pages. A title
block on each page is a suitable means of achieving this. The title block must be placed in the
bottom right corner of each page and contains all relevant information on the document. Table
10-18 lists the 15 most important items. Table 10-19 shows the structure of the title box in and
Table 10-20; it also contains an example of the title box which will be represented on the
following pages by a gray box for the purpose of simplification.
Page 215 / 242

Annex
Table 10-18: Information in the title box in accordance with [ISO 7200]
Number Data field
1 Legal owner of the document
2 Title
3 Supplementary title
4 Reference number
5 Change index
6 Date of issue of the initial version of the document
7 Language
8 Number of pages/sheets
9 Document type
10 Document status
11 Responsible department
12 Technical reference (contact person with required knowledge)
13 Name of the person who created the document
14 Name of the person who approved the document
15 Classification/key words
Page 216 / 242

Annex
Table 10-19: Proposal for title box in accordance with [ISO 7200]
Responsible dept. Technical reference Created by Approved by

(11) (12) (13) (14) (15)
Document type Document status

(9) (10)
Title, Supplementary title
(1) (3) (4)
Rev. Date of Issue Lang. Sheet

(5) (6) (7) (8)
Table 10-20: Table 1 9: Example of title box in accordance with [ISO 7200]
Responsible dept. Technical reference Created by Approved by

Design 2 Ms. N. Meyer Mr. S. Sample Mr. K. Smith
Document type Document status

Network Documentation Released
Title, Supplementary title
Company Inc. PROFINET 2508
Plant sections in hall 1
Rev. Date of Issue Lang. Sheet
A 25.08.2016 En 1/5
Page 217 / 242

Annex
Figure 10-27 shows the plant to be automated. It consists of three plant sections in hall 1
(responsible: Mr. Smith) of a company. A cabinet is already planned to be installed in the hall;
therefore, it is represented by a dotted line.
Figure 10-27: Example of forwards documentation for the automation of three plant sections
Figure 10-28 shows the configured automation devices and the required network
infrastructure. In addition to a PLC and three remote IOs, there is a switch for connecting the
network nodes and an HMI (Human Machine Interface) for visualizing the process. Figure
10-28 shows the logical topology plan.
Page 218 / 242

Annex
Figure 10-28: Example of PROFINET forwards documentation, physical topology plan
Figure 10-29: Example of PROFINET forwards documentation, logical topology plan
Page 219 / 242

Annex
Figure 10-30 shows the topology plan of a ring topology. The switch (Sw+HA1+S01_1) is used
to organize the ring. For this purpose, it’s marked with a number (1) in a “ring”. The ring is
drawn exactly between the two ports that spread it out.
Figure 10-30: Example of PROFINET forwards documentation, ring topology
Table 10-21 enhances the topology plan (see Figure 10-30) with further information. The
device in the first position manages the ring and, hence, has a different color.
Table 10-21: Example for PROFINET forwards documentation, information related to the ring topology
No Device name Port Next device Port Next device Manag

. er
No Device name No Device name
. .
1 Sw.HA1.S01. 2 2 IO.HA1.PS2.1 3 4 IO.HA1.PS1.1 x

1
2 IO.HA1.PS2.1 1 1 Sw.HA1.S01.1 2 3 IO.HA1.PS3.1
3 IO.HA1.PS3.1 1 2 IO.HA1.PS2.1 2 4 IO.HA1.PS1.1
4 IO.HA1.PS1.1 1 3 IO.HA1.PS3.1 2 1 Sw.HA1.S01.1
Page 220 / 242

Annex
Table 10-22 contains further information on the automation devices and additional network
nodes. Table 10-23 provides additional information for the replenishment.
Table 10-24 summarizes the most important information on cables as an addition to the
topology plan.
Page 221 / 242

Annex
Table 10-22: Example for PROFINET forwards documentation, additional device information
PW GSD
changed saved?
Firmware
Port: (version
No. Device name IP address Subnet mask Protocols MAC address revision
Service and
Yes No level
storage
place)
10.5
PNIO + Server
1 PLC.HA.-S01.1 192.168.1.10 255.255.255.0 80: HTTP x 13-24-56-11-90-01 2.2
TCP/IP on 2016-
08-31
8.4
PNIO + Server
2 HMI.HA1.S01.1 192.168.1.20 255.255.255.0 80: HTTP x 13-24-56-12-55-21 2.1
TCP/IP on
02.09.2016
1.1
Server
3 Sw.HA1.S01.1 192.168.1.50 255.255.255.0 PNIO 12-34-56-78-9A-BC 1.3.1
on
02.09.2016
Page 222 / 242

Annex
1.3
00-0E-8C-24-C5- Server
4 IO.HA1.PS1.1 192.168.1.71 255.255.255.0 PNIO 2.5
51 on
02.09.2016
1.3
5 IO.HA1.PS2.1 192.168.1.72 255.255.255.0 PNIO 2.5
4E on
02.09.2016
1.3
6 IO.HA1.PS3.1 192.168.1.73 255.255.255.0 PNIO 2.5
12 on
02.09.2016
Page 223 / 242

Annex
Table 10-23: Example for PROFINET forwards documentation, enhanced device information
No. Device name Port Cable Device Manufacturer Model HW/, FW revision level Serial number (Alternative)
supplier
Order No
1 PLC.HA1.S01.1 1 -W101 Sw.HA1.S01.1 Manufacturer 1 PLC 5 2.0 / 2.1.1 1920-1812-8212-0 Vendor X
2 -W102 HMI.HA1.S01.1 7815182
2 HMI.HA1.S01.1 1 -W102 PLC.HA1.S01.1 Manufacturer 1 HMI 17 2.5 / 2.6 1231-3017-0111-5 Vendor X
- - - 4825561
3 Sw.HA1.S01.1 1 -W101 PLC.HA1.S01.1 Manufacturer 2 Switch 12 1.3 / 1.3.2 ABC-12345 Vendor X
2 -W103 IO.HA1.PS2.1 1541527
3 - -
4 - -
4 IO.HA1.PS1.1 1 -W105 IO.HA1.PS3.1 Manufacturer 3 IO S2 2.0 / 2.2 14-93-15 Vendor X
2 - - 4510965
Page 224 / 242

Annex
5 IO.HA1.PS2.1 1 -W103 Sw.HA1.S01.1 Manufacturer 3 IO S2 2.0 / 2.2 14-93-15 Vendor X
2 -W104 IO.HA1.PS3.1 4510965
6 IO.HA1.PS3.1 1 -W104 IO.HA1.PS2.1 Manufacturer 3 IO S2 2.0 / 2.2 14-93-15 Vendor X
2 -W105 IO.HA1.PS1.1 4510965
Page 225 / 242

Annex
Table 10-24: Example of PROFINET forwards documentation, cable list
Name Connector 1 Connector 2 Actual length Medium Type /
Device Port Connection Device Port Connection in meters (m) Nature
-W101 PLC.HA1.S01.1 1 RJ45 Sw.HA1.S01.1 1 RJ45 10.50 Cu A
-W102 PLC.HA1.S01.1 2 RJ45 HMI.HA1.S01.1 1 RJ45 5.00 Cu A
-W103 Sw.HA1.S01.1 2 RJ45 IO.HA1.PS2.1 1 M12 85.00 Cu A
-W104 IO.HA1.PS2.1 2 M12 IO.HA1.PS3.1 1 M12 32.00 Cu A
-W105 IO.HA1.PS3.1 2 M12 IO.HA1.PS1.1 1 M12 25.00 Cu A
Page 226 / 242

Annex
Describe normal plant operation in a clear manner (see Figure 10-31). For further checklists
for visual inspection, cable acceptance checks and the two-part acceptance protocol refer to
the Annex of the PROFINET Commissioning Guideline [PNI2014].
Figure 10-31 shows how the diagnostic port can be marked.
Figure 10-31: Example of PROFINET forwards documentation, information in cases of faults
Page 227 / 242

Annex
Figure 10-32: Example of PROFINET forwards documentation, diagnostic port example
The use of firewalls should be shown clearly in the topology. Further information related to the
access and the default settings must be recorded in a separate list. Figure 10-33 shows an IT
security assessment.
Page 228 / 242

Annex
Figure 10-33: Example of PROFINET forwards documentation, IT security assessment
Keep all data sheets and the manuals of the used devices. Add a functional description of the
plant to your documentation.
10.9.4 Problems of forwards documentation in the product lifecycle
Deviations frequently occur in the installation or commissioning phase already. They should
be eliminated in a revision. However, the large number of manual user interactions by different
employees results in a high risk of faults. Once the system has been delivered to the plant
operator, the designers are no longer responsible, and the knowledge recorded in a good
network documentation is no longer available. In cases of faults, the employees of the plant
operator normally attempt to eliminate the faults themselves. Minor changes of the plant are
often not recorded as they have to be made under some time pressure.
A forwards documentation often contains many items throughout the entire lifecycle of the
plant. These reduce the quality of the network documentation. The network documentation
becomes unclear, difficult to understand or faulty. Often the network documentation is not up-
to-date, the access is denied or the documents are missing.
Page 229 / 242

Annex
Due to these detriments it is not recommended to use the forwards documentation in the
operational phase of the lifecycle. Writing an up-to-date network documentation on site is more
suitable for troubleshooting. A standardized backwards documentation helps reduce the time
required for documentation.
Page 230 / 242

Annex
10.9.5 Proposal for a PROFINET backwards documentation
The requirements on the backwards documentation must be reduced to a minimum as the

documentation is generated automatically. The backwards documentation should also begin
with an overview and then provide details. The cover page contains all relevant information
needed for identification:
• ID of the documentation
- Document type (here: Network documentation)
- ID number / name
- Date of Issue
- Revision index or version
- Revision date
- Document status (is it a draft or final version?)
- Specific data (customer name, plant name)
• Information on the creator
- Company name
- Company address
- Responsible author
The topology must be clearly designed and contain all additional information (device name, IP
address, subnet mask, port assignment, cable length). Further information (cable type, cable
medium) can be provided in tables. From the ports assignment you can derive free access
ports of the plant. Additionally, the firewalls should be shown. Information about an existing
password-protection can be written in the topology on the firewall or can be color-coded (green
= password-protected, red = no password-protection)
Reading out the used network nodes is supposed to provide information on possible spare
parts. This information includes:
• Manufacturer
• Model name/type designation
• MAC address
• Used protocols
- Used ports and services
• Serial number
• Version number
• Reference picture
• Used software or firmware revision levels
• Contact information of the hotline or technical support
• Password security: Are standardized passwords used?
Page 231 / 242

Annex
Any information that cannot be determined through backwards documentation must be

provided by the employees.
Tools for analyzing PROFINET networks are already available. Various vendors offer tools for
backwards documentation. Nearly all criteria can be met.
However, the information determined by commercial tools does not comply with the
requirements of an IT security audit.
10.9.6 Difficulties of backwards documentation
A topology can only be read and visualized by the tools if all nodes are capable of handling
the LLDP (Link Layer Discovery Protocol). This is an obstacle to using backwards
documentation, as low-cost alternatives that do not support LLDP are often used in networks.
Moreover, passive network nodes require different measurement mechanisms and often result
in incomplete network documentations, since passive network nodes cannot be recognized
correctly.
10.9.7 Requirements on future backwards documentations
A backwards documentation should begin with a topology plan. Additional information must
be visualized on the devices. This information includes the device, name, IP address, subnet
mask, port assignment, device function (if not clearly indicated by the device name) and a
reference picture of the device. Further information should be listed in tables. You can find an
overview of all information in section 10.9.1.
The general network documentation can be used as the basis for information on IT security.
All services must be disclosed for this. As a result, the device vendors should reveal the
standard ports/services of their devices.
In order to allow for a successful backwards documentation, the plant manufacturers and
operators must select the appropriate components. Additionally, the product manufacturers
must provide more data for their products. The conversions process is ongoing.
Page 232 / 242

Annex
10.10 Network load calculation tool

Figure 10-33 shows the user interface of the network load calculation tool in Microsoft Excel.
The purpose of the network load calculation tool is to facilitate the network load calculation for
users.
Figure 10-34: User interface of the network load calculation tool
The upper area, highlighted in white in Figure 10-34, has been defined as entry area. Here,
users can define possible device configurations by entering values. The output area,
highlighted in dark gray, displays the calculation results.
The “percentage network load“, with reference to the available bandwidth of a link, must be
calculated by the user (see separate example provided later on). Make sure to consider the
network load separately for the input and the output direction.
Page 233 / 242

Annex
The network load calculation tool uses simple Excel formulae which are
hidden when using the tool. You can however edit these formulae after
inactivating the Excel worksheet protection and making the hidden areas of
these formulae visible.
A detailed description of the network load calculation is included in the

additional Excel worksheets “Description” and “Program flowchart” of the
network load calculation tool. The user manual shown on the following
pages can also be found in the calculation tool in the worksheet “User
manual”.
All entries are checked for consistency. In addition, error messages are
displayed in case of incorrect entries. Entries are possible only in the entry
fields. The other fields are blocked for entries.
Page 234 / 242

Annex
User manual
Figure 10-35 shows the different sections for entry of the calculation basics and the output
fields grouped according to the device groups.
Figure 10-35: Network load calculation using average values
The upper red frame is used to select the minimum transmission clock via a dropdown menu.
A manual entry is possible, but the entered value will be checked for usefulness when applied
in a PROFINET transmission system. The minimum transmission clock is usually pre-
determined by a fast PROFINET device. This information primarily helps to determine the
clock factors of a PROFINET transmission system.
On the left side of the entry mask, device data are entered with separate number of modules
for input and output, such as for remote IOs. On the right side of the entry mask, device data
are entered with identical number of modules for input and output (e.g. drives).
Page 235 / 242

Annex
For each side, entry values for three device groups can be specified, with entries made
underneath each device group. The entry is checked for consistency. Integers are permitted
only. Some entry fields also provide dropdown selection options.
PROFINET uses the full duplex technology. Data are therefore entered separately for each
transmit direction. The individual entry and display areas are used for:
Entry of the number of PROFINET devices per group and

1
selection whether this group has an isochronous connection
(IRT: Isochronous Realtime).
Entry of the number of modules per PROFINET device. This is

2
done separately for each transmit direction, except for device
groups 4 to 6.
Entry of user data (net data) of the PROFINET device in byte,

3
separately for each transmit direction.
Entry of transmit clock in ms, separately for each transmit

4
direction. The transmit clock may be different for both
directions.
Display of required clock factors for configuration of

5
transmission. Clock factors are usually determined via the
engineering tool so that his data is only provided here for
information purposes.
In addition to the network load generated by a device group,

6
the network load of individual PROFINET devices is also
shown here. The value of the device group results from the
multiplication of a single device with the number of PROFINET
devices in the group.
The network load of all PROFINET device groups added up is provided as a result (orange
frame). The result is provided separately for both transmit directions. The determined network
load can now be used in order to determine the percentage network load on a PROFINET
network.
The following example shows how the percentage network load is evaluated:
Page 236 / 242

Annex
Example: The network load calculation tool, after entering the device configuration and the
update times, has determined a total network load of:
3.086 Mbit/s in output direction and
7.538 Mbit/s in input direction.
If in the network a:
100 Mbit/s transmission link is used, this results in a percentage network load of :
3,086 % in output direction and
7,538 % in input direction.
As explained in previous chapters, the total network load only occurs at communication nodes
where several data streams meet. The network load generated by PROFINET should not
exceed the 50% limit at these nodes. Based on the individual device groups in the entry mask,
the group creating a high network load can be analyzed.
Some of the device groups have been left empty in this example. As shown
in this example, they can be individually configured per transmission
direction.
The network load depends on several influencing factors. The network load
calculation tool provides an estimate of these influencing factors.
Based on the individual device groups and their device types in the entry
mask, the group creating a high network load can be analyzed. It is then
possible to modify if necessary.
Page 237 / 242

Index
11 Index
Page 238 / 242

Index
Address selection 159 Controller 24
Addressing scheme 160 Controller transmission clock 101
APL cable 179 Crossover cable 84
APL field device 25 Cut-Through Switch 203
APL field switch 25 Device exchange 141
APL field switch with auxiliary power supply 25 Device names 161
APL field switches with I. E. connection 94 Device parameters 152
APL network structures 94 Device selection 36
APL power switch 24 Documentation PROFINET 207
Application-neutral cabling 85 Electro Magnetic Interference (EMI) 28
Approval list 42 Environmental requirements 43
Attenuation 70 Ethernet APL Cables 61
Auto Cross-Over 204 Ethernet-APL Basics 92
Backwards documentation 231 Ethernet-APL cable 27
Bumpless changeover 146 Ethernet-APL, increased safety, Ex e 28
Cable Distances 62 Example plant
Cable parameters Ethernet-APL cables 179 Machine automation 78
Cable routing 58 Manufacturing automation 77
Communication monitoring 110 Process automation with remote IO 79
Communications relations 35 Example Plant Process Automation with Ethernet

APL 80
Conformance classes 37
FastStartup 84
Connection technology 44
Firmware 87
Connectors 71, 185
Forwards documentation 210
Copper 187
Functional assignment 34
FOC 189
Geographical assignment 34
Control station 26
Gigabit Ethernet 206
Page 239 / 242

Index
High-availability plant network 145 PROFINET optical fiber cabling 65
Increased availability 141 PROFINET optical fibers 180
IP address 153, 155 PROFIsafe 45
IRT 39 Response time 104
Line depth APL trunk 117 Ring structure 143
Line depth for 100 Mbit/s networks 113 Router 24
Line depth with APL Field-switches 116 RT 39
MAC address 153 SendClockFactor 101
Managed Switch 203 Store-and-Forward Switch 204
Media converter 26 Structure of guideline 29
minimum distance 62 Switch 24, 46, 202
Network diagnosis 88 Switching time 146
Network load 103, 117 Symbol meaning 23
Network topology 51 Time requirements 40
Non-bumpless changeover 146 Toplologies
NRT 39 Line 56
Operator console 24 Topologies
PoE 205 Star 54
Port Mirroring 205 Tree 55
Possible toplogies APL 94 Topology 53
Power over Ethernet 149, 205 Transmission medium 57
Powered APL trunk 94 Copper 58
Powered APL Trunk 96 Fiber optical cables 65
PROFINET copper cable 27, 58, 168 Update time 101, 108
PROFINET Device 25 WLAN access point 26
PROFINET FO cable 27
Page 240 / 242

This page is intentionally left blank.
Page 241 / 242

© Copyright by:
PROFIBUS Nutzerorganisation e. V. (PNO)

PROFIBUS & PROFINET International (PI)
Haid-und-Neu-Str. 7 ● 76131 Karlsruhe ● Germany
Phone +49 721 986197 0 ● Fax +49 721 986197 11
E-mail [email protected]
www.profibus.com ● www.profinet.com
KHN
Page 242 / 242


PROFINET Design Guideline 8062 V153 Sept22

Uploaded by

Copyright:

Available Formats

PROFINET Design Guideline 8062 V153 Sept22

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PROFINET Design Guideline 8062 V153 Sept22

Uploaded by

Copyright:

Available Formats

PROFINET

Version 1.53 – Date 21. Sept, 2022

Prepared by PI Working Group PG3 “Installation Guides PROFIBUS and PROFINET” in

1.04 18.11.2010 Niemann Final version

1.05 11.06.2013 Niemann Internal version, not published

1.06 --- Niemann Internal versions, not published

1.11 05.08.2014 Niemann PoE and 4-pair cables. Enhancement of performance

1.13 20.11.2014 Niemann Consolidation of review comments by WG Chair

1.15- ---- Niemann Internal versions, not published

1.24 07.09.2018 Niemann Processing von Review comments, chapter network

1.25 --- Niemann Internal version

1.32 01.01.2019 Niemann Document was renewed due to crash problems

1.39 01.03.2022 Niemann Intermediate Version

1.51 28.07.2022 Niemann Reviev comments from Review meeting 13.06.2022

1.52 31.07.2022 Niemann Final Proof reading

1.53 23.09.2022 Niemann Finalization for release of document

1.1 PREFACE ................................................................................................................................ 16

1.2 LIABILITY EXCLUSION ............................................................................................................... 17

1.3 PNO DOCUMENTS ................................................................................................................... 18

1.4 REFERENCED STANDARDS ....................................................................................................... 20

1.5 SYMBOLS AND THEIR MEANING ................................................................................................. 23

1.5.1 Symbols for structuring the text..................................................................................... 23

1.5.2 Symbols for components ............................................................................................... 24

1.5.3 Symbols for PROFINET cables ..................................................................................... 27

1.5.4 Symbols for areas ......................................................................................................... 28

1.6 ABOUT THE STRUCTURE OF THIS GUIDELINE .............................................................................. 29

1.7 GOAL OF THE GUIDELINE .......................................................................................................... 31

2 ANALYSIS AND PRELIMINARY CONSIDERATIONS ............................................................... 32

2.1 DETERMINATION OF AUTOMATION COMPONENTS ....................................................................... 33

2.2 DEVICE SELECTION .................................................................................................................. 36

2.2.1 The PROFINET Conformance Classes ........................................................................ 37

2.2.2 Special timing requirements .......................................................................................... 39

2.2.3 Further criteria for device selection ............................................................................... 42

2.3 DEFINITION OF DEVICE TYPES ................................................................................................... 48

2.4 DOCUMENTATION OF RESULTS ................................................................................................. 50

3 NETWORK TOPOLOGY .............................................................................................................. 51

3.1 PROFINET TOPOLOGY ........................................................................................................... 53

3.2 APPLICABLE TRANSMISSION MEDIA ........................................................................................... 57

3.2.1 PROFINET copper cabling (4-core, 8 core) .................................................................. 58

3.2.2 Ethernet APL Cables ..................................................................................................... 61

3.2.4 PROFINET optical fiber cabling .................................................................................... 65

3.2.5 Selection of required connectors................................................................................... 71

3.3 PREFERRED DEVICES FOR PRIMARY INFRASTRUCTURE .............................................................. 73

3.4 DEFINITION OF NETWORK TECHNOLOGY .................................................................................... 75

3.5 TOPOLOGY CHECK AND REFINEMENTS ...................................................................................... 80

3.6 DOCUMENTATION OF TOPOLOGY .............................................................................................. 81

4 SPECIAL DESIGN ASPECTS ...................................................................................................... 83

4.1 USE OF “FAST STARTUP” ......................................................................................................... 84

4.2 UTILIZATION OF EXISTING CABLE INFRASTRUCTURE ................................................................... 85

4.3 CONNECTION TO HIGHER LEVEL NETWORKS (CORPORATE NETWORK) ......................................... 86

4.4 DETERMINATION OF FIRMWARE REVISION LEVELS ...................................................................... 87

4.5 PLANNING OF ACCESS POINTS FOR NETWORK DIAGNOSES ......................................................... 88

4.6 UTILIZATION OF 4-PAIR CABLING ............................................................................................... 89

4.7 DOCUMENTATION OF MODIFIED NETWORK TOPOLOGY ................................................................ 90

5.1 W HAT IS ETHERNET-APL ......................................................................................................... 92

5.2 POSSIBLE TOPOLOGIES FOR AN APL SYSTEM ............................................................................ 94

5.2.1 Alternative 1: APL field switches with Industrial Ethernet connection........................... 94

5.2.2 Alternative 2: Powered APL Trunk ................................................................................ 96

6 PERFORMANCE CONSIDERATIONS ........................................................................................ 98

6.1 PROFINET TRANSMISSION CYCLE ......................................................................................... 100