Propriedade Intelectual

PROPRIEDADE INTELECTUAL
A Siemens declara que todos os desenhos, patentes, marcas registradas, know-how, segredos de
comercialização e quaisquer outros dados e informações utilizados, direta ou indiretamente, para a
execução do objeto deste treinamento, são de sua exclusiva propriedade ou, conforme o caso, de suas
empresas controladoras, controladas ou afiliadas ou, ainda, da propriedade de terceiros, possuindo ela
todas as devidas autorizações e permissões legais para os utilizar. A gravação é expressamente proibida.
O treinamento realizado pela Siemens, bem como as apostilas e dados disponibilizados, não transferem e
nem conferem ao CLIENTE quaisquer direitos que a Siemens seja ou venha a ser titular, reconhecidos ou
não, no âmbito do direito da propriedade industrial ou dos direitos autorais, incluindo, mas não se
limitando, ao direito de distribuição do material disponibilizado, tendo por objeto o treinamento, bem
como os documentos e as informações técnicas prestadas pela mesma em virtude da execução deste
contrato. Em caso de descumprimento desta cláusula ou da legislação aplicável, o CLIENTE estará sujeito
às sanções civis decorrentes da violação dos direitos autorais, previstas nos artigos 101 e seguintes da Lei
9.610/98, sem prejuízo da possibilidade de enquadramento da conduta no crime de violação ao direito
autoral previsto no artigo 184 do Código Penal e das indenizações cabíveis.
Restrito
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
Pe reir
eg o IK-TIAPN
Dy
SITRAIN
Digital Industry Academy
Industrial Communications
PROFINET with Industrial Ethernet in TIA Portal
siemens.com/sitrain
1 Communication with SIMATIC
2 Basics of Industrial Ethernet
3 Basics of PROFINET
4 Network Components
SITRAIN
Training for Industry 5 PROFINET Configuration
M O
6 U
Topology Editor
R
o
Industrial ou tinh
C 7 Diagnostics
Communication
r e ira
Pe
PROFINET with Industrial
o
eg
Dy Portal
8 Web Services for PROFINET
Ethernet in TIA
9 Ring Redundancy MRP
Course IK-TIAPN
10 Shared Device
11 I-Device
PROFINET IRT & Isochronous

12
Mode & Oversampling
U MO
13
o R
Gateways
h
Co utin Communication Possibilities in
Name:
e i r a 14
P er TIA Portal
Course from:
eg
to: o
D y 15 S7 Communication
Instructor:
Location: 16 Open User Communication – OUC
This document was produced for training purposes. 17 OPC UA

SIEMENS assumes no responsibility for its contents.
The reproduction, transmission or use of this document or its
contents is not permitted without express written authority. Appendix:
Offenders will be liable to damages.
18 Diagnostics and Commissioning
Copyright © Siemens AG 2018. All rights, including rights Tools
created by patent grant or registration of a utility model or
design, are reserved.
19 Training and Support
SITRAIN course offer on the internet:www.siemens.com/sitrain
Version: V15.01.00 (for TIA Portal V15.1)

20
Industrial Communication, PROFINET with Industrial Ethernet in the TIA Portal
Contents 1
1. Communication in the SIMATIC World ................................................................. 1-2
1.1. Communication in a Factory ................................................................................................. 1-3
M O
1.2. U
Subnets in SIMATIC ............................................................................................................. 1-4
R
o
tinh
1.3. Industrial Ethernet ................................................................................................................. 1-6
1.4. ou
Industrial Wireless Communication....................................................................................... 1-7
C
1.4.1.
e i ra
IWLAN – Industrial Wireless LAN ......................................................................................... 1-8
Per
1.4.2. IWLAN and WirelessHART ................................................................................................... 1-9
1.4.3.
o
Teleservice (Remote Diagnostics and Remote Maintenance) with SIMATIC
eg
Teleservice .......................................................................................................................... 1-10
1.5. Dy
PROFINET IO ..................................................................................................................... 1-11
1.6. IT Standards & Security ...................................................................................................... 1-12
1.7. Actuator - Sensor Interface ................................................................................................. 1-13
1.8. IO-Link ................................................................................................................................. 1-14
1.9. Gateways ............................................................................................................................ 1-15
1.10. Additional Information ......................................................................................................... 1-16
1.10.1. PROFIBUS .......................................................................................................................... 1-17
1.10.2. EIB, European Installation Bus (KNX) in Building Automation ........................................... 1-18
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Communication in the SIMATIC World

Training Document, V15.01.00 1-1
Communication in the SIMATIC World

1. Objectives
At the end of the chapter the participant will ...
... get an idea of communication in automation
... be familiar with the different communication media
...
M O
get an introduction to communication in the factory
R U
... o
know what the four large subnets in SIMATIC are
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Communication in the SIMATIC World Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

1-2 Training Document, V15.01.00
Communication
1.1. in a Factory
Communication in a Factory
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Management Level / Operations Level
Higher-level tasks that concern the overall operation are handled at the management level
(management functions). These tasks include the storage of process values as well as
processing functions for optimization and analysis and their output in report form. The data
required for this is collected and processed for the whole site. Other sites can also be accessed
from the management level. The number of devices can exceed 1000.
Control Level / Cell Level

All automation and optimization tasks are handled autonomously at the cell level. Programmable
O
controllers, PCs and devices for operator control and monitoring are connected to one another at
M
the cell level.
o RU
Field Level
u t inh
Co
a
The field level is the link between the systems and the programmable controllers. The field
P ereir
devices measure, signal and forward the commands of the cell level to the systems. Small
amounts of data are transmitted in most cases. Hierarchical communication is typical, that is,
e g o
several field devices communicate with one master.
Actuator-Sensor Level
Dy
At this level, a master communicates with the actuators and sensors connected to its subnet. Fast
response times for a few data bits are characteristic for this level.

Subnets
1.2. in SIMATIC
Subnets in SIMATIC
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Industrial Ethernet (IEEE 802.3)
Industrial Ethernet, the international standard for area networking is currently the number one
network in the LAN environment with a share of over 90%. Industrial Ethernet enables powerful
communication networks to be set up over wide areas. On the basis of global wireless standards,
e.g. IEEE 802.11a/b/g/n, GSM, GPRS or UMTS (3G), reliable wireless networks can be set up in
the industrial environment.
PROFINET (IEC 61158/61784)

PROFINET, the international standard uses Industrial Ethernet and enables real-time
O
communication down to the field level. With the full utilization of existing IT standards, PROFINET
M
o RU
enables high-performance motion control applications, efficient cross-manufacturer engineering
and high machine and plant availability on Industrial Ethernet. Due to its flexibility, PROFINET
t inh
offers new options for system design, such as the use of any topology and fail-safe networks,
u
even via wireless connections.
Co
a
PROFIBUS (IEC 61158/61784)
P ereir
e g o
PROFIBUS, the international standard for the field level is the global market leader among
Dy
fieldbus systems. It is the only fieldbus to allow communication both in manufacturing applications
and in process-oriented applications.
AS-Interface (IEC62026/EN 50295)

AS-Interface is the international standard which, as an economical alternative to the cable
harness, links sensors and actuators by means of a two-wire cable.

IO-Link
IO-Link is the standard for intelligently connecting sensors, RFID systems and actuators from the
field level to the control level.
Gateways
Gateways are realized using controllers or links. Configuration and diagnostics can be performed
from any point in the system.
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

Industrial
1.3. Ethernet
Industrial Ethernet
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Industrial Ethernet
Industrial Ethernet is based on the IEEE 802.3 and IEEE 802.11 standards and enables
connection of your automation system to your office networks.
Industrial Ethernet provides information technology (IT) services with which you can access
production data from the office environment and work with the data.
Due to the uniform standard and the standardization of Industrial Ethernet, a smooth transition to
the office environment is possible. This coupling occurs with the help of network components
such as switches, routers or similar.
Compared to the “normal” Ethernet, Industrial Ethernet is subjected to higher requirements.
M O
Industrial Ethernet components therefore also usually have a higher protection class or similar
functionalities, for example.
o RU
u t inh
Co
a
P ereir
e g o
Dy

Industrial
1.4. Wireless
Industrial Communication
Wireless Communication
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Industrial Wireless Communication
Within the scope of industrial communication, wireless communication opens up new prospects –
from partial modernization of a plant to optimization of complex logistics or production processes.
With Industrial Wireless Telecontrol, Industrial Wireless LAN and WirelessHART as a basis,
Siemens offers solutions for reliable automation with Industrial Wireless Communication.
Wireless solutions are increasingly becoming a matter of course in machines and plants. For
stringent data communication requirements, Industrial Wireless LAN (IWLAN) relies on
innovations such as deterministic radio and the PROFINET Industrial Ethernet standard. Through
the use of PROFIsafe via IWLAN, PROFINET opens up completely new prospects – from
O
efficient engineering and real-time solutions to safety-related tasks. Furthermore, an IWLAN
M
RU
infrastructure can also be used for additional applications such as video monitoring.
o
u t inh
Co
a
P ereir
e g o
Dy

IWLAN
1.4.1. – Industrial
IWLAN Wireless
– Industrial LAN
Wireless LAN
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Industrial Wireless LAN
Wireless solutions are increasingly becoming a matter of course in machines and plants. For
stringent data communication requirements, Industrial Wireless LAN (IWLAN) relies on
innovations such as deterministic radio and the PROFINET Industrial Ethernet standard. Through
the use of PROFIsafe via IWLAN, PROFINET opens up completely new prospects – from
efficient engineering and real-time solutions to safety-related tasks. Furthermore, an IWLAN
infrastructure can also be used for additional applications such as video monitoring.
In summary, extensions of the IEEE 802.11 standard are made available with Industrial Wireless
LAN which address the requirements of industrial customers, in particular, with regard to
O
deterministic and redundancy (iFeatures). This gives customers a single radio network for
M
RU
process-critical data (e.g. I/O communication, safety-related communication) and for non-critical
communication (e.g. service and diagnostics).
o
u t inh
Co
a
P ereir
e g o
Dy

IWLAN
1.4.2. and WirelessHART
IWLAN and WirelessHART
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
WirelessHART
WirelessHART is an open industry standard, developed for the particular requirements of wireless
communication at the field level in the process industry. It meets all specific requirements for
reliability, security, cost-effectiveness and user-friendly operation. WirelessHART opens up new
communication options that were previously impracticable or impossible due to the operating
environment or for economic reasons.
SCALANCE W
SCALANCE W provides IWLAN access points, client modules and an IWLAN controller for setup
O
of the wireless infrastructure and connection of terminals in the industrial environment. The
M
RU
products provide the unique combination of reliability, robustness and security. SCALANCE W
o
IWLAN components and the resulting possible PROFINET communication provides a wireless
solution for applications down to the field level.
u t inh
o
The reliability of the radio channel is extended in a dust-free and water-tight design (IP65) of the
C
a
robust enclosure meeting the stringent requirements for mechanical stability for which SIMATIC is
P ereir
known. Modern security mechanisms for user identification (authentication) and data encryption
provide protection against unauthorized access and can be integrated in existing security policies
without any problems. e g o
Dy
The RCoax cables provide a wear-free and reliable radio link, especially for conveyor systems,
robots and rail-guided vehicles of any type.

Teleservice
1.4.3. (Remote
Teleservice Diagnostics
(Remote Diagnostics and Remote Maintenance) with SIMATIC
and Remote Maintenance)
Teleservice with SIMATIC Teleservice
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Teleservice
Remote diagnostics and remote maintenance of production plants have become indispensable in
modern automation technology. They are more efficient and more cost-effective than on-site visits
by a service employee. This allows malfunctions to be detected and corrected much faster.
Downtimes of machines are reduced and their availability is increased.
Machines and plants are increasingly operated in places that are far away from the place of
manufacture. Plant manufacturers must nevertheless be able to guarantee services in case of
malfunctions. During the warranty period, in particular, this can result in high costs. Teleservice
helps to reduce this risk significantly. The possible applications for Teleservice are manifold.
M O
Plants can be diagnosed, values set and data transmitted from anywhere in the world via
telephone lines.
o RU
t inh
Teleservice also enables the sending of text messages per SMS or e-mail by SIMATIC
u
o
controllers, thereby contributing significantly to savings in travel and personnel cost due to fewer
C
a
reir
service visits. In the case of remote Teleservice connections, a distinction is made between
e
remote maintenance and remote connection.
P
e g o
Dy
Remote Maintenance
Remote maintenance permits access to a CPU with STEP 7 or an HMI device via WinCC. For
remote maintenance, a technician dials into a remote system by telephone. STEP 7 can be used
to read status information or to correct the user program remotely.
Remote Connection
Remote connection refers to a connection for data transmission. Remote connections are used to
transmit data over the telephone network. Teleservice supports the program-controlled
establishment of a connection between the PG or PC and automation system. Process data
exchange between several automation systems can also be coordinated.

PROFINET
1.5. IO
PROFINET IO
IO-Controller PN/PN-Coupler IO-Controller
PROFINET IO 1 PROFINET IO 2
M O
RU
o
tinh
I-Device I-Device I-Device IO-Device
IO-Controller
C ou PROFINET IO 3
e i ra
o Per
eg
Dy
IO-Device IO-Device I-Device
SITRAIN
PROFINET IO
PROFINET enables the integration of distributed field devices (IO-Devices such as
signal modules) directly in Industrial Ethernet. With the tried-and-tested configuration with STEP
7, these field devices are assigned to a central controller (the so-called IO-Controller). Existing
modules or devices can continue to be used with PROFINET-capable interfaces or links, which
safeguards the existing investments of PROFIBUS and AS-Interface users. A configuration with
standard and fail-safe modules in one station is also possible. An IO-Supervisor is used for HMI
and diagnostics purposes by means of hierarchical diagnostic screens (Overview and Detailed
diagnostic). User data is transferred via real-time communication. Configuration and diagnostic
data is transferred using TCP/IP or IT standards. The easy tried-and-tested engineering approach
MO
for PROFIBUS has been adopted for PROFINET. From the viewpoint of programming with STEP
RU
7, it does not matter if an I/O device is being accessed via PROFIBUS or PROFINET.
o
u t inh
C o
a
P e reir
e g o
Dy

IT Standards
1.6. & Security
IT Standards & Security
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
IT Standards & Security
With Industrial Ethernet as its basis, PROFINET not only offers scalable real-time communication,
but also standard TCP/IP communication according to IEEE 802.3 – with no compromises. This is
the basis for integrated horizontal and vertical networking, whether wired or wireless. Accordingly,
pioneering functions and established IT standards for network management, network diagnostics,
web services, security and the connection of higher-level Gigabit networks are supported by
PROFINET without any restrictions.
Network Management
O
Vis-à-vis fieldbuses, Ethernet in conjunction with TCP/IP and UDP/IP offers additional options for
M
o RU
network management. The aspects of network infrastructure, IP management, network
diagnostics and time synchronization are components of the integrated network management. It
t inh
simplifies the administration and management of Ethernet – through the use of standard protocols
u
from the IT world.
C o
a
Industrial Security
P ereir
e g o
As Ethernet networks have found their way down to the field level, this has enabled an integrated
Dy
networking of all automation levels – as well as the direct connection to office networks and the
Internet. However, this also means that production networks are exposed to the same risks as
office networks – incorrect internal accesses and external attacks. Even a brief failure or minor
malfunction can bring production to a standstill and cause massive damage. The automation
technology therefore needs a security concept that reliably protects the production networks and
automation components and is perfectly tailored to the particular requirements. Protection
concepts are:
• Access protection to automation cells (cell protection concept)
• Protection against espionage and manipulation
• Secure remote accesses via unsecure networks
These security objectives can be achieved through the use of PROFINET security components
such as SCALANCE S.

Actuator
1.7. - Sensor
Actuator Interface,
- Sensor ASI-Bus
Interface
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Actuator - Sensor Interface
AS-Interface is an open, international standard based on EN 50295 and IEC 62026-2 for process
and field communication. Worldwide, leading manufacturers of actuators and sensors support
AS-Interface. The AS-Interface is a single master system. For automation systems from Siemens,
there are communication processors (CPs) and gateways (Links) which act as master to control
the process and field communication, as well as sensors and actuators which are addressed as
AS-Interface slaves.
MO
o RU
u t inh
C o
a
P ereir
e g o
Dy

IO-Link
1.8. IO-Link
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
IO-LINK
IO-Link is the smart concept for the standardized linking of switching devices and sensors to the
control level by means of an economical point-to-point connection.
The new IO-Link communication standard below the fieldbus level enables central error
diagnostics and localization down to the actuator/sensor level and facilitates both commissioning
and maintenance by allowing parameter data to be modified dynamically, direct from the
application.
The increasing intelligence of field devices and their integration in the overall automation enables
data access down to the lowest field level. The result: higher system availability and reduced
engineering effort.
M O
o RU
As an open interface, IO-Link can be integrated into all common fieldbus and automation
systems. Consistent interoperability ensures maximum protection of investment. This also applies
t inh
in the context of existing machine concepts for continued use of sensors that have no IO-Link
u
interface.
C o
a
P ereir
e g o
Dy

Gateways
1.9. Gateways
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Gateways
Gateways from one bus system to another are realized using links, controllers (PLCs) or PCs. In
the case of PLCs or PCs, integrated interfaces and communication processors (CPs) can be
used for this. Links forward the data autonomously from one network to the other.
Links
Some of the most common links are listed below:
• IE/PB Link and IE/PB Link PN IO for the transition from Industrial Ethernet to
PROFIBUS (also for fail-safe communication)
MO
•
RU
IE/AS-i LINK PN IO for the transition from Industrial Ethernet to AS-Interface
o
•
inh
IWLAN/PB Link PN IO for the transition from IWLAN to PROFIBUS
u t
• C o
PN/PN Coupler for the coupling of two PROFINET networks
i r a
•
ere PA for coupling DP/DP and DP/PA networks
PB DP/PB DP and PB DP/PB
P
•
egtoo AS-Interface
DP/AS-i LINK Advanced
y
and DP/AS-Interface Link 20E for the transition
D
from PROFIBUS
• DP/EIB Link for the transition from PROFIBUS to KNX/EIB

Additional
1.10. Information
Additional Information
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Basics of Industrial Ethernet Page 50 Siemens AG © 2016
Note
The following pages contain either additional information or are for reference to complete a topic.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

PROFIBUS
1.10.1. PROFIBUS
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Entry ID: 59193579
SITRAIN © Siemens AG 2018 IK-TIAPN

Page 16 Communication with SIMATIC
PROFIBUS
PROFIBUS is a bus system for process and field communication in cell networks with a small
number of nodes, with field devices and for data communication compliant with IEC 61 158 /
EN 50170. It is open for the connection of components of other manufacturers that conform to the
standards:
• PROFIBUS DP: for fast, cyclic data exchange with field devices
• PROFIBUS PA: for applications in process automation and in the intrinsically-safe area
• Data communication: PROFIBUS FDL and for data communication between
O
programmable controllers of different manufacturers
M
PROFIBUS Medium
o RU
t inh
The simple and cost-effective two-wire RS 485 transmission technology is exceptionally suitable
u
o
for networks with a linear/tree structure and high data transmission rates. The total size of the
C
a
reir
network is smaller than with an optical network, but can also reach distances up to 1 km (at 12
e
Mbit/s) or up to 10 km (at 187.5 Kbit/s) through segmentation and signal regeneration with up to 9
P
e g o
repeaters. Instead of standard repeaters, it is also possible to use diagnostic repeaters, which not
Dy
only handle the signal regeneration but also the online monitoring of the connected bus segment.
A segment can have up to 32 nodes (master/slaves) and the entire network up to 126 nodes. The
start and end of each segment must be fitted with an active cable termination that is either
already integrated in the device (e.g. repeater) or is available as an active RS 485 terminating
element.
Note
On the Service & Support pages it is possible to download the “SIMATIC PROFIBUS PROFIBUS
with STEP 7 V13” manual. This can be found in the Publication number: 59193579.

EIB, European Installation Bus (KNX) in
Building
1.10.2. Automation
EIB, European Installation Bus (KNX) in Building Automation
Powerline 230 V
Powerline
Bus coupler
DP/EIB Link
Powerline
Coupler
KNX
M O
EIB-binary- R U EIB-buttons
n h o
input-modules
u ti
C o
eira
P e r
eg o
Dy
Wind sensor Drive
Page 17 Communication with SIMATIC
EIB / KNX
The EIB (European Installation Bus) is now commonly used especially in Europe for building
management systems. It is supported by many representatives of the electrical and building
services automation sector who have come together under the auspices of the European
Installation Bus Association (EIBA). A defined standard interface allows products from different
vendors to be used in a common installation.
One of the objectives of the EIB technology is to control all operational functions and processes in
a building by means of a common bus cable. A twisted pair bus cable is looped through the
building for the control. In addition to transmitting the control message frames, this bus cable also
transmits the 24 V supply for the bus nodes. EIB is a distributed, event-driven serial bus system
M O
based on CSMA/CA. It is used to acquire, control, monitor and signal all operational functions in a
building or large facility.
o RU
u t inh
C o
a
P ereir
e g o
Dy

Contents 2
2. Basics of Industrial Ethernet ................................................................................. 2-3
2.1. In the Beginning there was Ether .......................................................................................... 2-4
M O
2.2. U
The Historical Development of Industrial Ethernet ............................................................... 2-6
R
o
tinh
2.3. Horizontal Levels of Industrial Automation ........................................................................... 2-8
2.4. ou
Why Ethernet in the Industrial Environment ......................................................................... 2-9
C
2.5.
e ira Environment........................................................ 2-10
Advantages of Ethernet in the Industrial
r
2.6.
o Pe → Office Ethernet ......................................................... 2-11
Comparison Industrial Ethernet
eg
2.7.
Dy Components ......................................................................................... 2-12
Industrial Ethernet
2.8. ISO / OSI 7 – Layer Model .................................................................................................. 2-13
2.8.1. Layer 1: Physical Layer ....................................................................................................... 2-15
2.8.2. Layer 2: Data Link Layer ..................................................................................................... 2-16
2.9. Ethernet in the OSI Model ................................................................................................... 2-18
2.9.1. Ethernet Specification of the Physical Layer ...................................................................... 2-19
2.9.2. The Ethernet Telegram in the Data Link Layer ................................................................... 2-20
2.10. MAC Address ...................................................................................................................... 2-22
2.11. IP Address V4 / Internet Protocol Address Version 4 ......................................................... 2-23
2.12. Subnet Mask ....................................................................................................................... 2-24
2.13. Network Address ................................................................................................................. 2-25
2.13.1. Additional Network Address ................................................................................................ 2-26
2.14. O
Addresses of a Network ...................................................................................................... 2-27
M
2.15.
RU
Subnetting / Supernetting ................................................................................................... 2-28
o
2.16. inh
Calculation of IP Ranges - Classic...................................................................................... 2-29
u t
2.17. C o
Calculation of IP Ranges - Alternative ................................................................................ 2-30
a
2.18. reir
Alternative Calculation of Device Addresses ...................................................................... 2-31
P e
2.19.
g o
PING / Packet Internet Groper ............................................................................................ 2-32
e
2.20.
2.20.1.
Dy
Task Description: IP Addresses and Subnet Masks .......................................................... 2-33
Exercise 1: Calculating with IP Addresses ......................................................................... 2-34
2.20.2. Exercise 2: Subnetting ........................................................................................................ 2-35
2.21. Access Procedure for Industrial Ethernet: CSMA/CD......................................................... 2-36
2.22. Duplex Mode ....................................................................................................................... 2-37
2.23. Types of Telegrams in Ethernet .......................................................................................... 2-38
2.24. Ethernet HUB ...................................................................................................................... 2-39
2.25. Shared LAN  → Switched LAN ........................................................................................ 2-40
2.26. Ethernet SWITCH ............................................................................................................... 2-41
2.27. Ethernet SWITCH Basics .................................................................................................... 2-42
2.27.1. Ethernet SWITCH Basics 1 ................................................................................................. 2-42
IK-TIAPN – Basics of Industrial Ethernet

2.28. Switching Methods .............................................................................................................. 2-45
2.28.1. Store and Forward .............................................................................................................. 2-45
2.28.2. Cut Through ........................................................................................................................ 2-46
2.28.3. Fragment Free .................................................................................................................... 2-47
2.29. Switching Telegram Forwarding ......................................................................................... 2-48
2.29.1. Prioritization through the PCP ............................................................................................. 2-48
2.29.2. Processing Telegrams through Queues ............................................................................. 2-49
2.30. Task Description: Setting the Field PG IP Address and Resetting Devices to Factory Settings2-50
2.30.1. Exercise 3: Selecting the Field PG Ethernet Card ............................................................. 2-51
2.30.2. Exercise 4: Opening the Adapter Settings .......................................................................... 2-52
2.30.3. Exercise 5: Assigning the Field PG a Static IP Address ..................................................... 2-53
2.30.4. M O
Exercise 6: Networking the Devices ................................................................................... 2-54
2.30.5. R U
Exercise 7: Resetting the Devices to Factory Settings ....................................................... 2-55
h o
2.31.
o u tin
Additional Information .........................................................................................................
2.31.1. ISO / OSI 7 – Layer Model ..................................................................................................
2-57
2-58
a C
r e ir
2.31.1.1. Layer 1: Physical Layer ....................................................................................................... 2-60
P e
2.31.1.2. Layer 2: Data Link Layer ..................................................................................................... 2-61
e
2.31.1.4. Layer 4: Transport g o
2.31.1.3. Layer 3: Network Layer .......................................................................................................
Layer .....................................................................................................
2-63
2-64
Dy Layer ....................................................................................................... 2-65
2.31.1.5. Layer 5: Session
2.31.1.6. Layer 6: Presentation Layer ................................................................................................ 2-66
2.31.1.7. Layer 7: Application Layer .................................................................................................. 2-67
2.31.2. TRACERT / Trace Route .................................................................................................... 2-68
2.31.3. IP Address V6 ..................................................................................................................... 2-69
2.31.4. Special IP Area Ranges / IP Addresses ............................................................................. 2-70
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Basics of Industrial Ethernet

2. Objectives
... be familiar with the history of Ethernet
... understand the difference between Ethernet and Industrial Ethernet
...
M O
basically understand Industrial Ethernet
R U
... o
understand the structure of IP addresses and subnet masks
… ou tinh
be able to calculate with IP addresses and subnet masks
ra C
… e i
understand the difference between Shared LAN and Switched LAN
Per
and be able to explain it
y eg…o know the function of a Switch and how it works

D
SITRAIN
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

2.1. In the war

Am Anfang der Ether
Beginning there was Ether
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Grundlagen Industrial Ethernet Seite 3 Siemens AG © 2016
Ethernet
Digital communication is an integral part of today’s world. The basis on which this digital
communication is even possible is, however, often forgotten: The Ethernet.
The “birth” of Ethernet is depicted in the picture. The most important facts with regard to Ethernet
are the following:
• The first mention of Ethernet was in 1973 in a memo from Robert Metcalfe.
• It was developed between 1973 and 1974. It was modeled on the former ALOHAnet.
• In 1975, Xerox PARC filed the patent for the Ethernet. As the developers involved, the
O
M
RU
patent lists: Robert Metcalfe, Chuck Thacker, Butter Lampson and David Boggs.
o
• Starting in 1980, the Ethernet was further developed as Ethernet-Version 1 by the IEEE in
Working Group 802.
u t inh
C o
i r a
• The standardization of this bus system occurs in 1983 through IEEE 802.3.
• In 1985, SIEMENS launched
P erethe SINEC H1 bus system on the market - the Ethernet for
ego and the predecessor of today’s SIMATIC NET Industrial Ethernet.
the industrial application
y
Drecognition was achieved in 1989 as the ISO/IEC/IEEE 8802-3
• International
Standard for Ethernet was published.

Transmission Techniques
Starting in 1981, IEEE pursued three different techniques:
• CSMA/CD (802.3)
Carrier Sense Multiple Access / Collision Detection
• Token Bus (802.4)
• Token Ring (802.5)
While the Token Bus procedure was supported by General Motors and the Token Ring procedure
by IBM, the ECMA (European Computer Manufactures Association) supported the CSMA/CD
procedure.
In March 1982 their members agreed to support the procedure which was followed by the
published in 1985. M O
recognition of the CSMA/CD 802.3 Standard in December 1982. This Standard was then
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

The Historical
2.2. Development
The Historical of Industrial
Development Ethernet
of Industrial Ethernet
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
SIEMENS Industrial Ethernet
After extensive investigations and the supplementing of the standard by an integrated shielding
and grounding concept, the suitability of Ethernet for industrial use was demonstrated.
In this industrial design, the bus system has captured the industry since 1985 as SINEC H1, the
predecessor of today’s SIMATIC NET Industrial Ethernet. The sceptics of the time, who deemed
a non-deterministic access procedure such as the CSMA/CD used for Ethernet as inappropriate
for industrial use, have been proven wrong by thousands of plants.
Since then, Industrial Ethernet has been consistently further developed. To increase the system
availability, the first redundant networks came into being at the end of the eighties through the
development of a dual Ethernet bus system.
M O
o RU
With the advent of fiber optic cables, the shift of Ethernet as a bus system to a star-shaped
network began at the end of the eighties. Terminals were no longer connected by a commonly
t inh
used bus, rather, point-to-point via an active network component, the star coupler or hub. Greater
u
o
distances between devices became possible. Potential equilization or lightning protection
C
a
reir
measures became redundant. This was the birth of the SINEC H1FO communication system.
Particularly in the terminal connection area, “Twisted Pair” established itself in the mid 1990s as
Pe
e g o
the new transmission medium with which a higher connection density at lower connection costs
Dy
was achieved.
At the same time, the passive cabling technology for the transmission of data and voice were
standardized in the European standard EN 50173 “Generic cabling systems, 1995” and in the
international equivalent ISO/IEC 11801. Company networks were divided into primary area
(network between buildings), secondary area (building backbone) and tertiary area (network on
the floor). The tree-like network topology used primarily in the office area today emerged.
The first SIMATIC NET Industrial Ethernet Switches were introduced to the market at the end of
the 1990s. The OSM (Optical Switch Module) and ESM (Electrical Switch Module) were
specifically designed for use in the plant and terminal network of a process control system. They
were the first representatives of a new product group, the Control Level Switches.
Many properties of the Industrial Ethernet OLMs which were replaced almost completely by the
new switches in today’s plants, can be found once again in the Control Level Switches:
Optimized for use in compact control cabinets, DIN rail mounting, 0°C - 60°C ambient
temperature, 24V DC supply.
Added to this was a considerably simplified network planning with an extensive structure (up to
50 switches can be cascaded), the increase of the transmission speed to 100 Mbit/s, a higher
number of ports per network component, a long distance variant for single distance lengths up to
26km with single-mode fiber optic cables as well as the remote diagnostics via the
SNMPStandard.
The systematic further development of FieldLevel Switches by SIMATIC NET brought the new
device generation with the product lines SCALANCE X-100 (unmanaged switches) and
SCALANCE X-200 (managed switches) onto the market in mid 2004. With a multitude of
electrical and optical connections as well as devices with high IP65 degree of protection and for
isochrones real-time, a suitable device variant is available here for every application.
PROFINET, the open standard for automation, goes one step further: real-time and IT
communication can be operated together on the same network. PROFINET is based on Industrial
O
Ethernet and enables the device interfacing from the field level up into the process management
M
U
level. In addition to the direct connection of distributed field devices, the intelligent terminals, to
R
o
Industrial Ethernet, isochronous Motion Control applications can also be realized.
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

2.3. Horizontal Levels

Horizontal of Industrial
Levels Automation
of Industrial Automation
Process Management
Level
Control Level
Field Level
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 5 Basics of Industrial Ethernet
Process Management Level / Data Management Level
The process management level, also called the data management level, is used to manage, to
archive and to visualize data as well as data sets from the control and field levels.
Control Level
The control level is responsible for the control and regulating of the plant and the process. Here,
the data from the field level comes together and is analyzed intrinsic to the plant section.
Field Level / Production Level

O
The task of the field level is to measure, position and switch the individual plant sections. Here,
M
the sensor and actuator data is read-in and processed.
o RU
Vertical Integration
u t inh
C o
Through the use of Industrial Ethernet, standard mechanisms of communication and information
a
P e reir
technology such as OPC/XML along with standard protocols such as UDP/TCP/IP and HTTP can
be used in automation. This makes a transparent access directly to the data of the automation
g o
systems in the control level and production level by the process management level of the
e
company possible.
Dy
The vertical integration of the individual horizontal levels is thereby extremely simplified!
Note
In a comprehensive integration, the company level is also integrated via the management level. It
can then communicate with the management level via the office Ethernet and exchange data.

Why Ethernet
2.4. in the in
Why Ethernet Industrial Environment
the Industrial Environment
◼ Ethernet is the leader in office networks
◼ PROFINET is the innovation of PROFIBUS

on the basis of Ethernet
◼ The Ethernet technology provides very high

innovative strength, such as, switching
technology, wireless communication, Gigabit,
M O
Security,..
R U
h o
u tinoffers a variety of transmission media
◼ Ethernet
o
ei ra C(copper, fiber-optic, wireless communication)
o Per as well as flexible network structures (star, ring
D yeg and line topologies)
◼ A large number of suppliers / manufacturers,

also for the industrial market
SITRAIN
IK-TIAPN / Basics of Industrial Ethernet
Page 6 Siemens AG © 2016
Communication in the Industrial Environment
The demands on communication in the industrial environment are very different from those of
conventional office communication. This applies to almost all aspects of communication, such as,
active and passive network components, connected terminals, network concepts / network
topologies, availability, data volumes, ambient conditions, only to mention a few.
Likewise, there are network protocols specially optimized for industrial communication, even
though back then TCP/IP, a classic protocol in office communication, had entered into the
production and process control.
Industrial Ethernet – Designed for Industry

M O
The basic idea of Industrial Ethernet is to use the existing R U
standard (Ethernet network standard
IEE 802.3) and to supplement it by the necessary and
n h o
useful details for industrial communication.
u t i
C o
This results in products for the specific circumstances in the production and process control
environment.
eir a
P e r
Note
g o
D ye Ethernet is not a standard! That is why when different manufacturers
Unlike Ethernet, Industrial
talk about Industrial Ethernet they may have different understandings of the specifications.

Advantages of Ethernet in the Industrial

Environment
2.5. Advantages of Ethernet in the Industrial Environment
Uniform network structure

◼ Fewer interfaces
◼ Plant-wide processing
◼ Easy to use
The advantages of Internet technology

can be used in production.
◼ Web services
M O
◼ Remote access / maintenance R U
o
◼ Software updates
ou tinh
ra C
e i
Per
Further development of current systems
◼ Increasing performance
eg o
◼ Larger data volumes
Dy
◼ System integration down to the field level
SITRAIN
IK-TIAPN / Basics of Industrial Ethernet
Advantages of Industrial Ethernet over otherPage 7
Fieldbuses Siemens AG © 2016
• Plant data and IT data can be transmitted almost simultaneously via one common
medium.
• A large address area with an almost unlimited number of devices (subscribers) is
available.
• Through a cascading of switches, large network expansions and a mixture of different
network structures can easily be realized.
• Larger amounts of data can be transmitted quickly and efficiently because of the
transmission rate of 100 Mbit/s. M O
• Future-proof due to Gigabit Ethernet. o RU
• u t inh
Equal bus access for all network participants is possible.
C o
• a
reir
Different transmission media (cable, wireless, fiber optic,…) can be combined.
• Pe
Simple integration of Internet technologies and protocols.
o
• y eg of Industrial Ethernet profits from developments in the “office Ethernet”
The development
D

Comparison
2.6. Industrial
Comparison Ethernet
Industrial → Office
Ethernet → Office
Ethernet
Ethernet
Industrial Ethernet Office Ethernet

Installation ▪System-dependent cabling and cable ▪Fixed base installations in the building
bushing ▪Variable device connection to standard
▪Field assembly connectors up to IP67 work areas
▪Redundant cabling, frequently ring ▪Predominantly star-shaped cabling
structures
Data ▪Small data packets ▪Large data packets

▪Very high network availability O
▪Medium network availability
M
▪Mainly cyclic transmission
RU
▪Mainly acyclic
o
transmission
▪Real-time performance necessary
t i h
▪No real-time
n performance necessary
Environment ▪Expanded temperature range
C ou▪Normal temperature range
e ira or ▪Little
▪Dust, moisture and vibration possible
▪Danger due to mechanicalrdamage
dust, moisture and vibration
chemical load o Pe ▪Very little mechanical or chemical load

▪Low EMC load
▪High EMC loadeg
Dy
SITRAIN
Industrial Ethernet
The same Ethernet Standard is used both in industry and in the office. The requirements
concerning the network products used, however, differ considerably!
In everyday industrial use, networks must work reliably under extreme conditions, such as,
electromagnetic interference, high operating temperatures and mechanical stresses.
Network Products
In order to meet the high demands of industry, there are special Industrial Ethernet network
products. Many suppliers offer both passive as well as active network components which meet
the particular requirements of an industrial environment.
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

2.7. Industrial Ethernet

Industrial Components
Ethernet Components
Easy diagnostics (LEDs)

Easy exchange
Easy exchange
Rugged design
M O
R U
Set – / Reset – button o
tinh
Increased degree of
protection
C ou
e i ra
o Per
Redundant power supply
eg Signal contact
Dy
Industrial Ethernet Components
In the industrial environment, both the active as well as the passive components must withstand
much harsher ambient conditions than in the office world. This becomes perceptible in many
ways!
Industrial Ethernet components, active as well as passive, have a higher protection class, a more
rugged design, and, have integrated diagnostic LEDs, just to mention a few examples.
Note
The use of office Ethernet network products in the industrial environment is not recommended!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

2.8. ISOISO
/ OSI 7 – 7Layer
/ OSI – Layer
Model
Model
Layers
7 Application 7. Application Layer
Anwendungs-
application-
6 Presentation 6. Presentation Layer
orientiert
oriented
5 Session 5. Session Layer
4 Transport 4. Transport Layer

M O
RU
o
Network
tinh
3 3. Network Layer
C o u Transport-
transport-oriented
orientiert
a Link Layer
reir
2 Data Link 2. Data
Pe
1 Physical
e g o 1. Physical Layer
Dy
Open Systems Interconnection (OSI) – Model
The OSI – 7 Layer Model is a reference model for manufacturer-independent communication
systems, that is, a design basis for communication protocols and computer networks.
OSI stands for Open Systems Interconnection and was designed and standardized by ISO as the
basis for communication standards. The OSI layer model or OSI reference model is based on the
DoD layer model on which the Internet is based. In comparison to the DoD layer model, the OSI
layer model is more finely subdivided.
DoD layer model (Department of Defense):
MO
o RU
u t inh
Co
a
Pe reir
e g o
Dy
The OSI model serves as a tool for describing the principle function of a network. It is divided into
seven sub-areas which are also referred to a layers. Each layer, with the exception of the
uppermost layers, makes its function available to the layers above it. The most important layers
for Ethernet are Layer 1 and Layer 2.

For each layer, functions and protocols are defined which must fulfill specific tasks for the
communication between two systems. For communication between two systems, the
communication or the data flow passes through all 7 layers of the OSI layer model twice - once at
the Sender and once at the Recipient. Depending on how many ‘stops’ the communication route
has, the communication also passes through the layer model several times.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

LayerLayer
2.8.1. 1: Physical Layer
1: Physical Layer
1. Physical Layer:
Layers
Measures and procedures for transmitting bit sequences
▪ Devices and network components are assigned to the
7 Application Physical Layer
▪ Defines the optical, electrical and mechanical connection
6 Presentation to the transmission medium
▪ Manages the coding of the individual bits or the bit
5 Session
sequences
4 Transport M O
R U
o
3 Network
ou tinh
ra C
2 Data Link
e i
1 Physicalego
Per
Dy
SITRAIN
Physical Layer
In the physical layer, the electrical, optical and mechanical connection to the transmission
medium used is defined. It is responsible for the proper transmission of individual bits through the
physical channel. This is essentially a matter of the coding of signals, the defining of the
transmission medium and the transmission devices.
Each medium has its own section.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.8.2. 2: Data LinkLink
2: Data Layer
Layer
2. Data Link Layer:

Layers Logical connections to data packets and elementary error
detection mechanisms
7 Application ▪ Consists of two sublayers, the Logical Link Control layer
as well as the Media Access Control layer
6 Presentation ▪ Divides the bit data flow into blocks or frames and adds a
checksum
5 Session ▪ Ensures a reliable and error-free transmission on the
4 Transport
transmission medium
M O
R U
o
3 Network
ou tinh
ra C
2 Data Link
e i
1 Physicalego
Per Logical Link Control
Dy Media Access Control
SITRAIN
Data Link Layer
In the data link layer, the transmission and the grouping of the individual bits in the transferable
unit as well as the access procedure to the network is defined. It provides a reliable connection
between terminal and transmission medium and ensures an error-free transmission.
For this, the bit data flow is divided into (data) blocks, also called frames, and checksums are
added. With this checksum, flawed blocks can be detected by the recipient and subsequently be
rejected or even be corrected.
According to IEEE, the Data Link Layer is divided into two sublayers - the Logical Link Control
and the Media Access Control. Due to the Media Access Control, the data link layer is sometimes
also called the MAC Layer.
M O
Media Access Control
o RU
u t inh
The Media Access Control layer is the lower of the two layers in the data link layer. It controls the
C o
access to the transmission medium. It defines which protocol is to be used. There are two
a
Controlled access: Pe reir
different types of access, a controlled access and a competing access.
e g o
• Token Ring
Dy
• Token Bus
• CSMA/CR
Competing access:
• ALOHA
• CSMA/CD
• CSMA/CA

Logical Link Control

The Logical Link Control layer is the upper of the two layers in the data link layer. It adds several
identifiers to the data packet which are structured as follows:
• DSAP (Destination Service Access Point) of 8 bytes
• SSAP (Source Service Access Point) of 8 bytes
• Control of 8 or 16 bytes
Note
A renewed request of rejected blocks is not regulated or provided in the data link layer!
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

2.9. Ethernet in the

Ethernet OSI OSI
in the Model
Model
Layers
7 Application
6 Presentation
5 Session
4 Transport M O
R U
o
Network
tinh
3
C o u
2b
r e ira
Logical Link Control Ethernet based on
2a o Pe Control
Media Access
Layer 1 + Layer 2a
D yeg
1 Physical

Ethernet in the OSI – Layer Model
Referring to the OSI model, the Ethernet Standard describes Layer 1 as well as Layer 2. To be
more exact, the Ethernet Standard describes Layer 1 and Layer 2a since the Data Link layer is
divided into two sublayers of which only the Media Access Control layer belongs to the Ethernet
Standard.
The Ethernet Standard therefore summarizes both mechanisms and media of the Physical Layer
as well as the access to these in the Media Access Control in the Data Link Layer.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

2.9.1.Ethernet Specification
Ethernet Specificationof
ofthe
the Physical Layer
Physical Layer
Transmission rate
Transmission medium
100Base-TX
Transmission procedure
Typische Teilbereich Übertragungsrate Medium

Standards M O
R U
▪10Base5 ▪10 Mbit/s o
▪Coaxial cable
▪10Base-T ▪10 Mbit/s
o▪Twisted tinh
u Pair cable (TP)
▪100Base-TX ▪100 Mbit/sra
C ▪Twisted Pair cable (TP)
r e i
▪100Base-SX
o PeMbit/s
▪100 ▪Fiber optics (short wave)
D yeg ▪1000 Mbit/s

▪1000Base-T ▪Twisted Pair cable (TP)
▪1000Base-LX ▪1000 Mbit/s ▪Fiber optics (long wave)

Definition of the Medium
In the Physical Layer level, the different transmission media and the resulting data (en)coding are
described in Ethernet. Each medium has its own section in the Standard.
Notation of the Sections of the IEEE 802.3 for the Physical Layer
The notation of the sections can be divided into three parts:
• The transmission rate
• The transmission procedure
• The medium used
M O
100BASE-TX, for example, means that you are working with U
R aPair
transmission rate of 100 Mbit/s
(100) with the baseband transmission (BASE) and a h
n o
Twisted Medium (TX).
u t i
o but the transmission rate is always
These notations are not always 100% consistent
C
recognizable.
eir a
P e r
e g o
Dy

2.9.2.TheThe
Ethernet Telegram
Ethernet Telegramin
inthe
the Data LinkLayer
Data Link Layer
Layer 2 describes the access to Layer 1 as well as the telegram structure
Not part of the Ethernet Telegram according to IEEE802.3 (64 bytes to 1518 bytes)
Ethernet telegram with VLAN Tag maximum 1522 bytes
Preamble SFD Destination Source VLAN Type Data FCS
Address Address Tag
7 Bytes 1 Byte 6 Bytes 6 Bytes 4 Bytes O

2 Bytes
M
46 Bytes – 1500 4 Bytes
R U Bytes
o
ou tinh
VLAN Tag is optional
ra C
e i
Per
TPID TCI
o
yeg
2 Bytes 2 Bytes
D 8100 PCP CFI VID
PROFINET uses PCP

Definition of the Access Procedure
The functional description of the Physical Layer is not enough to be able to targetedly transmit
data. Only with the definitions on the MAC level of the Data Link Layer does it become possible to
transmit data and the targeted sending of data within a network. The Ethernet Standard describes
the access procedure with collision detection and how to proceed after a collision occurs on the
MAC-Layer level.
Definition of the Frame Format and the Addressing

Beyond that, the Frame Format, that is the telegram structure of an Ethernet telegram, and the
addressing scheme are described. This is necessary to guarantee uniform data processing.
M O
The Ethernet Telegram
o RU
u t inh
The Ethernet telegram is standardized according to IEEE802.3 and is therefore subject to a fixed
structure:
C o
a
• Preamble:
e reir
The preamble consists of a 7 byte long alternating bit sequence: “101010…1010”, also
P
g o
called a 10s-series. This is followed by the 1 byte long SFD - the Start Frame Delimiter,
e
Dy
with the bit sequence: “10101011”.
In the past, these 8 bytes were used for the bit synchronization of the different network
devices. With today’s network components and the contemporary network topologies,
this synchronization process is actually no longer necessary and is now only found in the
specification for compatibility reasons.
• Destination Address / Destination – MAC – Address:
The MAC address of the network station which is to receive the data is stored in the 6
bytes of the Destination Address.
• Source Address / Source – MAC – Address:
The MAC address of the network station, which has sent the data to the destination
address is found in the 6 bytes of the Source Address.

• VLAN Tag:
In the Tagged-MAC-Frame according to IEEE 802.1Q there follows an additional 4 bytes
as VLAN-Tag. The first 2 bytes contain the “Tag Protocol Identifier”, short TPID. This
normally contains the constant 0x8100 (=802.1qTagType) which identifies a Tagged-
MAC-Frame as such. The following 2 bytes contain the “Tag Control Information”, also
called TCI. It contains the “Priority Code Point”, PCP, the bit for “Canonical Format
Indicator”, CFI, as well as the “VLAN Identifier”, VID. The VLAN-Tag is also used in
PROFINET with the help of the PCP to prioritize the RT packets.
• Type / Type Field (EtherType):
The Type Field describes which type of packets are transported with this telegram. This
can be, for example, the Internet Protocol (IP). The identifier would then be 0x8000
(IPv4).
O
In earlier versions, the length of the packet was found here instead of the Type.
M
• Data / User data:
RU
o
tinh
The user data of the telegram is found here. It can have a maximum length of 1500
bytes. If the user data is less than 46 bytes, a so-called PAD Field (also called “Padding
C ou
Bytes”) is inserted in order to achieve the minimum size of an Ethernet Frame of 64
bytes.
e i ra
o Per
The minimum size of 64 bytes for an Ethernet Frame is important in order to be able to
reliably detect the collision of Ethernet packets!
eg
• Dy
Frame Check Sequence (FCS) / Test mark:
The Frame Check Sequence (FCS) is a 4 byte long sequence which is calculated from
the previous contents of the packet. It uses the Destination Address, the Source Address,
the Type and the Data to calculate its 4 bytes. It is used by the recipient to verify the
validity of the telegram. If the telegram is changed through errors on the line, it can be
detected with the FCS.
Note
There are circumstances in which the Ethernet Frame can be larger than the maximum byte size
of 1518 bytes. With the use of VLANs, for example, this is the case. A check must be made here
to see whether all network components can even process such an oversized Ethernet Frame
since it will otherwise be rejected!
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

2.10.MAC Address
MAC Address
MAC address of a
SCALANCE XC208
M O
RU
o
ou tinh
ra C
e i Each manufacturer has
o Per an ID
eg
Dy
00-1B-1B FE-B4-BC
Each device has a
unique address
Manufacturer ID Device address

MAC Address
The MAC address is the address of the physical interface of an Ethernet device. It is six bytes
long, is as a rule presented in hexadecimal format and must be unique in the network. Originally,
the address had to be unique worldwide and permanently burnt onto the device. Nowadays,
many devices have adjustable addresses.
The address is divided into an Organizationally Unique Identifier (OUI) which stands for the
manufacturer of the device and a device address given by the manufacturer. Due to their many
products, most manufacturers now have several OUIs.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

IP Address V4 /
2.11.Internet
IP Address V4Address
Protocol Version
/ Internet 4 Address Version 4
Protocol
192.168.0.2
Standard format
192 168 0 2
Decimal format
1100_0000 1010_1000 0000_0000 0000_0010
Binary format
M O
R U
o
ou tinh
127.0.0.1
ra C
ei
Per Localhost address
ego
Dy
An IP address is represented as 4 blocks à 8 bits, separated by a dot

IP Address V4
The IP address in Version 4 is 32 bits wide and uniquely identifies an IP device, also called IP
node, in a network. This address is not, like the MAC address in Ethernet, permanently assigned
to a device but can be freely configured.
To make things easier, when we talk about an IP address after this, it is always assumed that this
is of the type Version 4. If it should be of the type Version 6, it will say so explicitly!
The IP address is represented in four blocks with 8 bits each which are separated by a dot. Even
if this address is calculated in binary format, it is noted in decimal notation for reasons of
readability.
Each block can assume a value of 0 to 255.
M O
RU
Localhost
t i n ho
u
There is a special IP address, the so-called “Localhost” address. Your own computer can always
be addressed with this address regardlessCofowhich IP address the network card currently has.
r e iasrafollows: 127.0.0.1
Pe
The localhost address is composed
o
y eg
D

2.12.Subnet Mask
Subnet Mask
Decimal format
255 255 255 0
Binary format
1111_1111 1111_1111 1111_1111 0000_0000
/24 Alternative
representation
255 255 255 4

M O
RU
o
tinh
1111_1111 1111_1111 1111_1111 0000_0100
C ou Invalid subnet mask
e ira
o Per Network classes
yeg
/8 /16 /24 /32 (outdated)
D
A subnet mask in binary format always consists of an uninterrupted sequence of ones!

Subnet Mask
The subnet mask is, like the IP address, a 32 bit wide number. Together with the IP address, it
defines the size of a network. By means of the subnet mask, an end device can check whether a
communication partner is located in the same network or in another network.
The subnet mask read in binary format consists of an uninterrupted sequence of ones. The
subnet mask is noted either like an IP address in four blocks of 8 bits each or as a number of
leading ones.
The latter representation is always added to an IP address with a “/”. The IP address
192.168.0.100 with subnet mask 255.255.255.0 can therefore also be written as
192.168.0.100/24.
M O
Note o RU
u t inh
The familiar concept of network classes is outdated and was revised. It was replaced in 1993 with
the Classless Inter-Domain Routing (CIDR). Co
a
Pe reir
In the picture, the network classes in alternative representation are only displayed since these are
required for the simplified calculation of IP ranges.
A subnet mask which e
only
o
g consists of ones, that is 32 ones, is not allowed.
D y

2.13.Network Address
Network Address
192 168 0 100 ANDing the

addresses
&
255 255 255 0
=
Network address
192 168 0 0 decimal
IP address and subnet mask in binary notation M O

RU
0110_0100inh
o
1100_0000 1010_1000 0000_0000
ou t ANDing the
ra C & addresses
r e i
1111_1111 1111_1111
Pe 0000_0000
1111_1111
o
eg
Dy =
Network address
1100_0000 1010_1000 0000_0000 0000_0000 binary

ANDing Addresses
In order to place an IP device correctly in a network, an associated subnet mask must always be
configured in addition to an IP address. The IP address and the required subnet mask together
form the network address.
In order to determine the network address of an IP address and so also to check whether two IP
addresses are located in the same network, the IP address is “ANDed” binary and bit-by-bit with
the subnet mask.
This means that each bit of the IP address is linked with the relevant bit of the subnet mask with a
logical “AND”. 1 & 1 becomes 1, 0 & 1 as well as 1 & 0 to 0.
Network Address
U MO
o
The result of the operation described above is the address Rof the network in which the IP address
is located, in other words, the network address. in
t h
With the help of this network address, theC oucan
user find out whether two IP addresses (two
r a
eihave the same network exchange
devices) are located in the same network and can therefore data without a router. This
P e
is the case when both IP addresses r address. If the network addresses
g
are not the same, data can
e o only be exchanged between the devices with the help of a router.
Dy

Additional
2.13.1. Network
Additional NetworkAddress
Address
192 168 3 100 ANDing the

addresses
&
255 255 252 0
=
Same network
192 168 0 0 address as before
M O
RU
o
192 168 9 100
ou tinh ANDing the
ra C & addresses
e i
255 255
o Per
252 0
eg
Dy =
Different network
192 168 8 0 address

Network Mask
The subnet mask can also be seen as the network mask. This means that the subnet mask also
determines the maximum number of devices which can be located in a network.
In a network with the subnet mask 255.255.255.0, there can be 254 valid devices. In a network
with the subnet mask 255.255.254.0, there can be 510 valid devices.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

2.14.Addresses of aof
Addresses Network
a Network
IP address Subnet mask
192 168 0 100 255 255 255 0
192 168 0 0 Network address
256 – 2 valid device

192 168 0 1-254 addresses
192 168 0 255 Broadcast address
M O
IP address
RU Subnet mask
h
n255 o
192 168 9 100
u ti 255 252 0
C o
192 168 8
eir
0a Network address
P e r
8o
192 168
e g
y 11
1 4 x 256 – 2 = 1022
192 168 D 254 valid device addresses
192 168 11 255 Broadcast address

Network
Each network has special network addresses. These are the network address as well as the
broadcast address. These two special addresses cannot be used as device addresses in this
network!
Network Mask
The network mask defines the size and thus the maximum number of devices of a network. The
maximum number of devices is always two less than the maximum number of addresses in a
network. Each network always has at least two valid device addresses!
Network Address
U MO
o R Through this address, it can be
The network address is always the first address in a network.
h
tin network. As a result, the network address
checked whether two devices are located in the same
cannot be used as a device address!
C o u
i r a
Broadcast Address
P ere
y e is oalways
The broadcast address g the highest address in a network, but just like the network
D
address, it cannot be
the broadcast address.
used as a device address! All devices of a network can be addressed via

2.15.Subnetting / Supernetting
Subnetting / Supernetting
IP address Subnet mask
172 100 5 200 255 255 255 192
0 Network address
172 100 5 1-62 64 – 2 valid device addresses
63 Broadcast address
64 Network address
172 100 5 65-126
M O
64 – 2 valid device addresses
127
RU Broadcast address
o
128 ou tinh Network address
172 100 5
ra C
129-190 64 – 2 valid device addresses
e i
Per
eg o
172 100
Dy 5
192
193-254
Network address
64 – 2 valid device addresses

Subnetting
Subnetting is when you divide a network into two or more smaller ones. The smaller a network is
the more stable it runs. Depending on how many devices take part in a network, the subnet mask
must be adjusted.
An expansion of the subnet mask by a One (1) means a halving of the network. Two subnets are
formed. Each additional One halves the networks in turn.
Supernetting
If you remove a One from the subnet mask, this is supernetting. The networks are then twice as
large as before.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

2.16.Calculation of IPofRanges
Calculation - Classic
IP Ranges - Classic
192 168 9 100 IP address
255 255 252 0 Subnet mask
256 Max. number of network addresses
- 252 Subnet mask
= 4
M O
Bandwidth of the IP ranges
R U
o
tinh
Cou
192 168 0 0 First IP range
192 168 3
eira
255 4x256–2 = 1022 devices
P e r
192 168
eg o
4 0 Second IP range
192 168
Dy 7 255 4x256–2 = 1022 devices

IP Ranges
Since there is only a limited space for IP addresses in the IP address space and thus also for
devices in a network, the existing address space must be optimally utilized. This is done with the
help of subnetting and IP ranges.
Before you insert devices in a network you should decide what is the maximum number of
devices which should be possible in the same subnet and which IP range must be reserved for
the devices.
Classic Calculation
O
So that the calculation of how many devices are possible in an IP range can be done quickly,
M
easily and efficiently, the method above can be used.
o RU
u t inh
The octet of the subnet mask which is not completely filled with 1s is looked at. Thinking
decimally, this is the octet which is smaller than 255. This octet is taken and its numerical value is
Co
subtracted from the maximum number of network addresses 256. The result of this calculation is
a
P ereir
the bandwidth of the individual IP ranges which can be found in a network mask with this subnet
mask. The counting of the IP ranges always starts with the first network address which is found at
g o
Address 0. If, for example, a bandwidth of 4 resulted from the calculation, the IP ranges would
e
Dy
start at the addresses 0,4,8,12,16,20,24, etc.
The number of devices is then calculated by multiplying the maximum number of devices in a
network times the bandwidth and then subtracting two devices which are occupied by the network
address and the broadcast address. Thus, in the example above, 4x256 -2 results in a maximum
of 1022 devices per IP range.

2.17.Calculation of IPofRanges
Calculation - Alternative
IP Ranges - Alternative
192 168 116 100 /20 IP address
/8 /16 /24 /32 Network classes
24 Maximum number of Ones
- 20 Subnet mask
= 4 Number of Zeros in the octet
M O
= 16 U
2^4 = 16 Bandwidth of the IP ranges
R
o
ou tinh
192 168 0 0
ra C First IP range
192 168 15
e r ei255 16x256–2 = 4094 devices
P
y eg16o
192 168
D 0 Second IP range
192 168 31 255 16x256–2 = 4094 devices

Alternative Calculation of the Bandwidth
If the subnet mask is not stated in the classic representation as four octets (e.g. 255.255.255.0)
but in the alternative presentation (e.g. /20), an easy calculation of the devices in a mask can also
be done here.
You take the subnet mask and subtract it from the next higher “network class”. In the example
above this is 24 minus 20. The result, in this case 4, is then the exponent. To find the number of
bandwidths in the respective range, you calculate 2 to the power of 4. That is, 24 results in a
bandwidth of 16 for the individual IP ranges.
The calculation of the maximum number of devices is identical to the classic calculation but it can
also be more easily realized using the following method.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

2.18.Alternative Calculation
Alternative of Device
Calculation Addresses
of Device Addresses
192 168 116 100 /20 IP address
/32 max. number of Ones
32 Maximum number of Ones
- 20 Subnet mask
= 12 Number of Zeros in the mask
M O
= 4094
R U
2^12 = 4096 – 2 = 4094 devices
o
ou tinh
ra C
e i
o Per
eg
Dy
Alternative Calculation of the Device Addresses
A further possibility to find out how many device addresses / devices are now possible in an IP
range is just as easy and efficient using the alternative representation of the subnet mask.
You take the subnet mask and subtract it from the maximum number of Ones which would be
theoretically possible in a subnet mask. In the example above this is 32 minus 20. The result, in
this case 12, is then the exponent. To find the number of device addresses in every IP range, you
calculate 2 to the power of 12. That is, 212 results in a maximum number of 4096 device
addresses for the individual IP ranges. From this, two addresses, the network address and the
broadcast address, still have to be deducted. This results in a maximum device number of 4094.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

PING PING
2.19. / Packet Internet
/ Packet GroperGroper
Internet
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Ping / Packet Internet Groper
Simply called “Ping”, this tool is probably the most widely used and most familiar tool for testing
whether a network connection to another network device exists.
A Ping can be executed via the search field in the Windows Start menu as well as in the
command line. It is recommended, however, that you use the command line for a Ping since the
popup window automatically closes after the Ping command is executed via the search field in the
Windows Start menu. The command line can be opened by entering “cmd” in the Windows Start
menu.
Another way to open the command line is to start the execution window using the shortcut
“Windows-key + R” and then entering the command “cmd”.
M O
U
R one after the other by default. In
On a Windows operating system, a Ping is executed four times
h
order to execute a continuous ping, the Ping commandocan have a “-t” added to it. This
tinbe aborted in the command line by using the
continuous Ping as well as all other commandsucan
o
key combination “CTRL + C”!
r a C
i
Function P ere
go the network device sends an ICMP-Packet (Internet Control
After entering the Pingecommand,
y
Message Protocol) Dof the type ICMP Echo Request to the destination address. As soon as this
station has received the Packet, it sends an ICMP-Packet of the type ICMP Echo Reply back.
The throughput time of a packet can be determined when the sender halves the time that has
elapsed until the answer is received from the destination address
Note
By entering “ping” or “ping /?” in the command line, you can get an overview of all possible
combinations that are possible with the Ping command.

2.20.Task Description:
Task Description:
IP Addresses & Subnet
IP Addresses Masks Masks
and Subnet
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
In the following exercises, you are to calculate network addresses, broadcast addresses, device
addresses and subnet masks. You are also to check whether various device addresses are valid
addresses or not.
Do not use any other tools such as a calculator, cell phone ☺, or similar for this.
MO
o RU
u t inh
Co
a
Pe reir
e g o
Dy

Exercise
2.20.1. 1: 1:
Exercise Calculating
Calculatingwith
with IP
IP Addresses
Addresses
Task 1: Network addresses Task 2: Broadcast addresses
IP address 1: 192.168.113.16 IP address 3: 192.168.8.255

Subnet mask: 255.255.248.0 Subnet mask: 255.255.240.0
IP address 2: 172.16.100.34/30 IP address 4: 10.0.50.1

Subnet mask: 255.255.255.252
M O
Task 3: Device addresses
o RU4: Number of devices
Task
u ti nh
C o
IP address 1:
eir
192.168.1.0 a Network 1: 192.168.0.0/29
Subnet mask:
e r
255.255.254.0
P
o
eg192.168.100.3/30
IP address 2: D y Network 2: 10.0.0.0/22

Task
Each partial task has a different purpose. You are to calculate either the network addresses, the
broadcast addresses, whether the device addresses are valid addresses, or, the number of
maximum possible devices.
Task 1
Calculate the network address of the respective IP address.
Network address for IP address 1: _______________________________________
Network address for IP address 2: _______________________________________
M O
Task 2
o RU
u t inh
Calculate the broadcast address of the network in which the respective IP address is located.
C o
Broadcast address for IP address 3: _______________________________________
a
P e reir
Broadcast address for IP address 4: _______________________________________
Task 3 e g o
Dy
Are the following IP addresses valid device addresses?
IP address 5: _______________________________________
IP address 6: _______________________________________
Task 4
Calculate how many device addresses fit in the respective networks.
Number of device addresses in Network 1: _______________________________________
Number of device addresses in Network 2: _______________________________________

Exercise
2.20.2. 2: 2:
Exercise Subnetting
Subnetting
Task 5: Subnetting
You are to connect an automation network to an IT structure. For this, the Administrator of the IT
network has reserved an IP address area for the automation:
192.168.100.0/23
You are to divide the automation network into suitable subnets based on its communication
relationships. Select the subnet masks and the network addresses in such a way that the subnets
which you form are as small as possible but always have two IP addresses / device addresses as a
buffer for expansions.
M O
12 devices 30 devices
R U
230 devices 40 devices
n h o
u ti
C o
eir a
P e r
eg o
Dy
Task
You are to become familiar with subnet masks and solve the task asked below.
Task 5
Select the subnet masks in such a way that the subnets are, on the one hand, as small as
possible, and on the other hand, all devices plus two buffer addresses fit in the subnets.
Network mask & subnet mask for Subnet 1: _______________________________________
O
M
RU
o
Note
u t inh
C o
a
Calculate the subnet mask plus the network address as the solution!
Example: 192.168.200.64/28.
P e reir
e g o
Dy

Access Procedure
2.21.for Access
Industrial Ethernet: for
Procedure CSMA/CD
Industrial Ethernet: CSMA/CD
Station A Station C Station A Station C
Station B Station D Station B Station D
No telegram traffic on the network

O
Station A listens to the network and sends
M
Station A Station C Station A
R U Station C
n h o
u ti
C o
eira
P e r
eg o
Station B
Dy Station D Station B Station D
Station D listens to the network and sends Collision on the network

Collision Afflicted Shared Medium
Historically, Ethernet is a protocol that works with a shared medium. This means that only one
device at a time can send data on a line. If several devices simultaneously send information on
the line, there is an overlapping and the information is lost. This is called a collision. An area in
which collisions could occur is called collision domain. In traditional Ethernet, the entire network is
a collision domain.
Access Procedure: CSMA/CD (Carrier Sense Multiple Access / Collision Detection)

CSMA/CD is an access procedure that was developed to detect collisions on the line and, in this
case, to resend the data. It can be subdivided into the following:
M O
• Carrier Sense (CS):
o RU
Before data is sent, a check is made as to whether another device is already sending
data.
u t inh
• Multiple Access (MA): C o
a
Pe reir
In spite of a previous check, it can happen that two or more devices simultaneously
transfer data. A collision can occur.
•
o
eg (CD):
y
Collision Detection
D the devices check whether a collision has occurred on the line. If a
During sending,
collision is detected, the data is resent after a random waiting time which is determined
according to the back-off algorithm.
Note
A collision is not a faulty behavior in the traditional Ethernet, but a consciously tolerated feature of
the medium. The more devices exchange data in a network or the larger the collision domains,
the more likely a collision is. This also means that with an increasing number of collisions, the
data throughput rate sinks.
In modern networks, collisions are no longer possible because of full duplex data transmission
and the switches used. Today, CSMA/CD is therefore no longer used or required. .

2.22.Duplex Mode
Duplex Mode
Half duplex mode

Simultaneous communication only
possible in one direction
M O
R U Full duplex mode
n h o
Simultaneous communication in both
u ti directions possible
C o
eira
P e r
eg o
Dy
Half Duplex Mode
In communications engineering, half duplex mode is when communication is only possible
alternately in one direction. Traditional Ethernet always worked in half duplex mode, since only
one channel was available via the coaxial cable through which simultaneous data traffic was only
possible in one direction. CSMA/CD ensured that collisions did not occur here.
Full Duplex Mode

The restriction that it is only possible to simultaneously send in one direction does not exist for
modern Ethernet techniques. If twisted pair cables or fiber optic cables are used, you can usually
work in full duplex mode. Here, it is possible to simultaneously send in both directions. Collisions
M O
do not occur and CSMA/CD is not used here. Since information is sent in both directions, the data
RU
throughput also increases. With full duplex, Fast Ethernet achieves 200 Mbit/s and Gigabit
o
Ethernet 2Gbit/s.
u t inh
C o
a
P e reir
e g o
Dy

2.23.Types of Telegrams
Types in Ethernet
of Telegrams in Ethernet
Unicast
M O
U Multicast
h oR
o u tin
a C
e r eir
o P
eg Broadcast
Dy
Distinction between the Recipients
In general, Ethernet distinguishes between three types of telegram on the basis of the number of
recipients - Unicasts, Multicasts and Broadcasts.
Unicast
A unicast is a telegram that has exactly one recipient. The MAC address of this recipient is
specified as the destination MAC address in the Ethernet telegram. Bidirectional communication
usually occurs via Unicasts.
Multicast
M O
o RU
A multicast has several recipients. A telegram to several recipients is recognizable by the first bit
of the MAC address (least significant bit). If this bit is “1”, the telegram is a multicast or broadcast.
t inh
Intelligent network components are required for the correct forwarding of a multicast. If these are
u
o
not able to filter multicasts, a multicast is handled like a broadcast.
C
a
Broadcast
P ereir
g o
A broadcast is a telegram to all Ethernet devices (subscribers). A broadcast always has the
e
Dy
address “FF-FF-FF-FF-FF-FF” as the destination MAC address.
Note
In addition to the three already mentioned types of telegram, there is also the “Anycast” telegram
type. However, in the world of automation it is rarely used.
Anycast
An anycast is really a unicast which is sent to all devices that have this anycast address.
However, only the device which is accessible via the shortest route for the packet is addressed.
This, in turn, is determined by the so-called routing protocol.

2.24.Ethernet HubHUB
Ethernet
All connected devices share

the bandwidth
Symbol: HUB
Only one device (at a

time) can communicate
HUB
M O Whatever arrives at a port,
R U is output to all others

o
ou tinh
ra C
e i
o Per
eg
Dy
Ethernet HUB
In Ethernet, a star distributor which has several connections is referred to as a hub. As a rule,
HUBs have the following basic functions:
• Reproduction of the physical interfaces
• Improvement of the network quality compared to a pure coaxial segment through the
restoration of signal amplitudes, the signal timing or the isolation of a faulty segment
Expansion of the Collision Domain

U MO
When a HUB is used, the network segment remains a shared
o R medium and collisions continue to
t in
occur. The more HUBs are used, the larger the collision h domain becomes and the lower the net
throughput becomes.
C o u
eir a
Principle of Telegram Forwarding
e r
P a HUB has no intelligence. This means that all telegrams are
always forwarded toyall g o
With regard to telegram forwarding,
einterfaces; regardless of which telegram type it is. A unicast is forwarded
to all devices justD
like a broadcast. If the S7-1500 sends a telegram which is addressed to the S7-
300, the HUB nevertheless forwards it to all devices.

2.25.Shared  →Switched
LANLAN
Shared → Switched
LAN LAN
Shared LAN Switched LAN

all devices in a collision domain all devices in their own collision domain
M O
R U
o
ou tinh
ra C
e i
Per Separation of the collision domains
ego
Dy
Data traffic
Shared LAN
In a Shared LAN, all connected devices share the bandwidth of the network. The network is
therefore collision-afflicted and telegrams can be lost. A frame which is sent by a device goes
through all segments. Therefore, there can only always be one telegram in a Shared LAN.
The use of HUBs, repeaters and OLMs require compliance with configuration rules and in each
case reduce the maximum extension of the network.
Switched LAN
In a Switched LAN, every connected device finds itself in its own collision domain. As a result, it
M O
can handle the entire bandwidth of the network. It is virtually impossible for collisions to occur in a
Switched LAN! A frame which is sent by a device only goes through the segments which lie on
RU
the path to its receiver. Therefore, there can be several telegrams in a Switched LAN
o
simultaneously.
u t inh
Co
a
P e reir
e g o
Dy

2.26.Ethernet Switch
Ethernet SWITCH
All connected devices have

the same bandwidth
Symbol:
SWITCH
All devices can
communicate simultaneously
Switch
M O Whatever arrives at a port,
R U is specifically forwarded
o
outinh
ra C
e i
o Per
eg
Dy
Ethernet SWITCH
In network technology, an Ethernet Switch refers to a device which physically and logically
connects the network nodes with one another. Switches are now the standard components for
connecting Ethernet devices to one another.
Reduction of the Collision Domain

A switch decouples its physical interfaces, also called ports, from one another. In half duplex
mode, each port has its own collision domain(s). Modern switches and devices usually can
handle full duplex mode which leads to a collision-free network.
Principle of Telegram Forwarding

U MO
o
Switches have certain intelligence and only forward telegramsR to the desired addressees insofar
as they are known. The rest of the network devices
tiForh
nare not aware of the data exchange. There is
no physical connection between each end device.
C o u a unicast, the Source MAC Address and
the Destination MAC Address is used to a
eionr the Data Link Layer of the OSI model. Multicasts and
decide to which ports which telegram is forwarded. A
e r
switch is thus a device which works
broadcasts are forwarded to P
data intended for it. eg
o several or all devices. Ideally, every final device receives only the
Dy

2.27. Ethernet SWITCH Basics

Ethernet
2.27.1. SWITCH
Ethernet SWITCHBasics
Basics11
Forwarding Database (FDB)

MAC A MAC B
MAC Address Port Switch
▪MAC Address of A ▪P1
▪MAC Address of B ▪P2
▪MAC Address of C ▪P3
M Oof D
RU
P1 P2 ▪MAC Address ▪P4
o
ou tinh
ra C
P3 P4
e i
o Per
eg
Dy
MAC C MAC D

Forwarding Database
Based on the Destination MAC Address of an Ethernet telegram, a switch decides to which of its
ports it specifically forwards which unicast telegrams. For this, it internally creates a database in
which is stored which MAC address is accessible at which port. This database is called Filtering
Database or also Forwarding Database (FDB).
Forwarding Database for Cascading
M O
In the example, only one device each and with that only one MAC address was connected to
each port of the switch. Thus, only one MAC address is assigned to each port. If, however, further
RU
network components such as switches or even HUBs are connected to a port, then more than
o
one MAC address can be accessible on one port.
u t inh
o
The address of the connected switch is not listed since switches usually operate transparently in
C
a
the network. Only Managed Switches actively generate telegrams and so are entered in the FDBs
P
is assigned several MAC addresses! ereir
of the other switches. Here, they behave like final devices. It can therefore very well be that a port
e g o
Unicast Learning Dy
The database is filled with the Source MAC Addresses of the telegrams received. With each
forwarding of packets, these entries are compared with the Destination MAC Address of the
current telegram and only forwarded to the appropriate ports. This ensures that unicast telegrams
are only forwarded to the appropriate ports.

Ethernet
2.27.2. SWITCH
Basics22
Receipt of a telegram Device C sends a telegram to device B

from C
Is the address of C MAC-Adresse
in the FDB?
▪MAC Address of C ▪P3
Yes No
Enter address C and
Reset the Aging Timer
port 3 in the FDB
M O
U
R Time approx.
Is the address of B
h o Aging
in the FDB?
ou tin 30 sec – 40 sec
Yes No
ra C
e i
Per
Forward the packet to the Forward packet to all
port entered in the list
eg o ports
Wait for the next

Dy Not at the receiving port!
telegram
Checking the Source MAC Address
When the first telegram of device C reaches the switch, a check is made as to whether the
Source MAC Address of this packet is already listed in the FDB of the switch. In other words, a
check is made to see whether the switch already “knows” the device. If this is the case, the Aging
Timer for the relevant entry is reset.
If the MAC address (like here) is not listed, a new entry is created. This contains the MAC
address of device C and the port P1.
Checking the Destination MAC Address
O
Next, a check is made as to whether the address of the recipient (in other words, the Destination
M
RU
MAC Address of the Ethernet telegram) is listed in the FDB. Since this is not the case, the
telegram is forwarded to all ports (except that of the receiver). This ensures that the telegram
o
reaches the appropriate end device.
u t inh
C o
Deleting FDB Entries
i r a
There are two ways of deleting e re from the FDB. On the one hand, the associated MAC
P addresses
addresses are deleted foro
e g a Link Down of a port; on the other hand, old entries are sorted out
Dy
based on an Aging Time.
Link Down
A Link Down refers to the pulling of a cable or the interruption of an existing connection through a
cable break or similar.
An active link is immediately established when a cable is inserted between two Ethernet devices
(subscribers) (Lighting up of the usually green LED on the network port).

Ethernet
2.27.3. SWITCH
Basics33
Receipt of a telegram Device B sends a telegram to device C

from B
Is the address of B MAC-Adresse
in the FDB?
▪MAC Adresse
Address von
of C C ▪P3
Yes No
▪MAC Address of B ▪P2
Enter address B and
Reset the Aging Timer
port 2 in the FDB
M O
U
R Time approx.
Is the address of C
h o Aging
in the FDB?
ou tin 30 sec – 40 sec
Yes No
ra C
e i
Per
Forward the packet to the Forward packet to all
port entered in the list
eg o ports
Wait for the next

Dy A SWITCH only learns its port
allocation through incoming telegrams!
telegram
Checking the Source MAC Address
When the first telegram of device B reaches the switch, a check is made as to whether the
Source MAC Address of this packet is already listed in the FDB of the switch. In other words, a
check is made to see whether the switch already “knows” the device. If this is the case, the Aging
Timer for the relevant entry is reset.
If the MAC address (like here) is not listed, a new entry is created. This contains the MAC
address of device B and the port P2.
The only way for a SWITCH to learn which network devices are connected to which of its ports is
therefore via incoming Ethernet telegrams!
M O
RU
Aging Time
o
inh
Every time a MAC address is entered in the database, a timer is started. If it expires, the entry is
u t
considered obsolete and is deleted. This so-called Aging Time is often 30 sec to 40 sec in the
o
C
industrial environment and can be configured for Managed Switches. The Aging Time is stored in
a
reir
the Forwarding Database for every entry. For each packet that reaches the switch, the timer for
e
the relevant Source MAC Address is reset. This procedure ensures that the FDB is always kept
P
as current as possible.
e g o
Dy
If entries didn’t have an expiry date, changes in the network would, under certain circumstances,
not be detected. For cascading networks, it is entirely possible that the failure of a network
participant or the replugging of the device in another port does not necessarily cause the link
down of every port involved, in whose FDB this device is entered.

2.28. Switching Methods

Switching
2.28.1. Methods
Store and Forward- Store and Forward
Switch
Source port
Frame Store Switch Address table
Frame is detected at the source port Fabric
Destination port
Switch
Source port
Entire frame is read in

Store
Frame
M O
Switch
Fabric
Address table
R U
Destination port
o
tinh
Cou
Switch
Source port
FCS is checked and the destination port is
determined based on the destination
r e ira Store Switch
Frame
Fabric
Address table
address P e
o
yeg
Destination port
D Source port
Switch
Store Switch Address table

Frame sent to the destination address or Fabric
rejected Frame
Destination port

Store and Forward
With this switching method, each Ethernet telegram is completely read in before it is forwarded. If
the telegram length is in the valid range of the Ethernet Standard, the checksum is calculated and
compared to the FCS stored in the telegram. If the values are divergent, the data is rejected and
not forwarded. If they match, the switch passes through the various phases of the packet
forwarding. With this method, no invalid, too short or too long Ethernet frames are forwarded in
the network. This is the most commonly used switching procedure.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Switching
2.28.2. Methods – Cut Through
Cut Through
Switch
Source port
Destination port
Switch
Source port
Destination address is read in Fabric
Destination port
M O
Source port R U Switch
oStore
Frame is sent to destination address
u t inh Switch
Fabric
Address table
Frame
C o
r e ira
Destination port
e Switch
eg oP Source port
Dy
FCS is, however, still checked! If Fabric
something doesn’t fit, sending is aborted!
Destination port

Cut Through
With Cut Through, the telegram is already forwarded as soon as the Destination MAC Address
has been read in. However, the FCS is also calculated and compared. The problem is, however,
that the forwarding cannot be reversed. As a result, the sending is simply aborted for an invalid
FCS. This behavior ensures that, under certain circumstances, invalid, too short or even too long
packets are forwarded which have to be filtered by downstream network components or by the
end node. You achieve, however, very short latencies. Cut Through is used for very time-critical
applications such as PROFINET IRT.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Switching
2.28.3. Methods
Fragment Free – Fragment Free
Switch
Source port
Destination port
Switch
Source port
Minimum length of 64 bytes is checked Fabric
Destination port
M O
Source port R U Switch
oStore
The destination port is determined based
u t inh
Frame Switch
Fabric
Address table
on the destination address
C o
r e ira
Destination port
e Switch
egoP Source port
Dy
Frame is sent to destination address Fabric
Frame
Destination port

Fragment Free Switching
This method is a special form of Cut Through. Once again, the entire telegram is not read in.
However, at least 64 bytes are always read in before forwarding begins. In this way, you can
realize very time-critical applications and ensure that at least telegrams which are too short are
not forwarded. Fragment Free is a very special procedure and is not used very often.
Note
Fragments which are under 64 bytes are usually the debris of a collision that no longer make up a
useful frame!
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

2.29. Switching Telegram Forwarding

Switch
2.29.1. – Prioritization
Prioritization through of
theTelegrams
PCP (PCP)
Theoretical simultaneous arrival of two telegrams with different priorities
Telegrams with higher PCP are forwarded

with priority
M O
R U
o
tinh
PCP
C ou
Telegram 1 6
e i ra
Per
Telegram 2 0
Telegram with
higher PCP
eg o
Dy

Prioritization with the Help of the Priority Code Point (PCP)
In the PCP (Priority Code Point) of the VLAN tag, a number is stored with which the type of traffic
can be classified. It is used to give priority to certain telegrams over others.
This is relevant when a switch is working to capacity and it cannot forward the telegrams quickly
enough. Data must be buffered or, in the worst case, rejected. If a telegram then has a higher
priority than the other telegrams, it is forwarded before the others. In this way, it can be ensured
that this telegram is not rejected!
Prioritization Levels
U MO
R as follows:
The different priority levels are specified in the IEEE 802.1Q-2005
o
tin h
o u
Classification C
PCP Priority
r e i ra
1 0 (lowest)
Pe
Background
o
0 1
y eg Best Effort
2 2 D Excellent Effort
3 3 Critical Applications
4 4 Video
5 5 Voice
6 6 Internetwork Control
7 7 (highest) Network Control
PROFINET uses the PCP Priority 6!

Switch
2.29.2. – Mechanismus
Processing Telegrams der Priorisierung
through Queues (Queuing)
PCP
0
1
Queue
2 The PCP value decides in which queue
1 (low priority) which telegram is put
3 2
M O
4 3 R U
5
t
4 (high priority)i n ho
6 C ou
r e ira
7
P e
o
D yeg
PROFINET uses the PCP Priority 6
Depending on the switch, 2-8 queues are
possible

Queues in the Switch
The prioritization is realized through so-called queues in the Switching ASIC of the switch. The
prioritization of telegrams is only relevant when a switch becomes overloaded or several
telegrams arrive simultaneously. Depending on the performance class, switches have differing
numbers of queues (two to eight).
Siemens switches have two ways of processing these queues:
• Strict Priority Queuing
• Weighted Round Robin Priority Queuing
Strict Priority Queuing

M O
RU
The queues are emptied in a fixed order. In the example above, first Queue four, then Queue
o
u t inh
number three, etc. As long as telegrams are buffered in Queue four, no telegram from the other
Queues is forwarded. If there are telegrams in Queue three, no telegrams from Number two or
Number one are forwarded. C o
e i r a
Weighted Round Robin Priority Queuinger
P
e go to the lowest priority are passed through. If there are telegrams in a
All queues from the highest
y
D
queue, they are forwarded. A maximum of X telegrams at a time are sent from a queue, whereby
X depends on the priority. This procedure ensures that no telegrams remain in low priority queues
if a high priority device (for example, in case of a failure) generates too much load.
PCP to Queue Mapping

The decision which telegram is buffered in which queue is decided by the PCP value of the VLAN
tag. An internal table is stored in each switch. This table defines which PCP value is assigned to
which queue. Ex works, the mapping is configured according to IEEE 802.1Q. For modern
switches, this mapping can, however, also often be adjusted to your own requirements.
In the picture, the mapping is presented according to IEEE 802.1Q-2003.

Task Setting
Description: the Field
Setting PG IPPG
the Field Address
IP Address and Resetting
andDevices
Resetting Devices to Factory
to Factory Settings Settings
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
You are to give the Field PG a fixed IP address for all subsequent exercises. This must be
defined in the network card settings. For this, you are to select one of the two network cards and
give it a static IP address. Then, you are to reset all devices to factory settings. To do this, you
must first connect each of the devices to one another.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

2.30.1. Exercise 3:
Exercise 3: Selecting
Selecting the
the Field PG Field PG
Ethernet Network Card
Card
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task
You are to select the virtual interface from the VM-ware which is bridged to the
of the Field PG.
What to Do
1. Configure the interface as shown in the picture.
Note
M O
The identification of the network card of the M5 Field PG is easier “to remember” with the
RU
following. If you stand in front of the device, that is, can look on the display, the left interface is the
o
u i nh
and the right interface is the
t
Co.
a
This is easier to remember if you regard (memorize) the interface with “L” in the name as the left
Pe reir
interface and the interface with “LM” as the left-middle, that is the right interface.
e g o
Dy

Exercise
2.30.2. 4: 4:
Exercise Opening
Openingthe
theAdapter Settings
Adapter Settings
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
In the Control Panel, you are to open the adapter settings.
What to Do
1. Open the Start menu.
2. Switch to the Control Panel.
3. Open the Network and Sharing Center.
4. Go into the menu item “Change adapter settings”.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 5:
Assigning
2.30.3. Exercisethe Field PG the
5: Assigning a Static
Field IP
PGAddress
a Static IP Address
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Task
For the network card you selected in Exercise 3, you are now to assign a static IP address.
What to Do
1. With a double-click, open the Status of the network card (LAN-Connection Status) you
selected.
2. Switch to the Properties of the network card.
3. Highlight the element “Internet Protocol Version 4 (TCP/IPv4)”.
4. Open the Properties of this element.
M O
5. Using the Ping function of your computer, check whether U
R the IP address 192.168.222.250 is
already assigned. If yes, ask the Instructor to comeh o
to you before you continue!
o
6. Use the IP address 192.168.222.250 for this u tin
interface. Use the Subnet mask 255.255.255.0.
r a C
i
ere
7. Confirm your changes.
P
y ego
D

Exercise
2.30.4. 6: Networking
Exercise thethe
6: Networking Devices
Devices
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task
You are to network the devices with one another. You are to proceed as shown in the picture.
What to Do
1. Network the S7-1510SP-1PN CPU with Port P1 of the SCALANCE XC208.
2. Then, network the network card selected by you with Port P2 of the SCALANCE XC208.
3. Finally, connect Port P2 of your S7-1500 case with Port P3 of the SCALANCE XC208.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

Exercise 7:
Resetting
2.30.5. Exercisethe Devices to
7: Resetting theFactory
DevicesSettings
to Factory Settings
HMI Runtime must be

exited
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to reset all devices, which you networked with one another in the previous exercise, to
their factory settings. For this, you are to use the TIA Portal.
What to Do
1. Start the TIA Portal.
2. Expand the menu item “Online access”.
3. Expand your selected interface. If the wiring is correct, the interface should be identified with
the following symbol:
M O
4. Update the accessible devices.
o RU
u t inh
5. One after the other reset all accessible devices to their factory settings. Should there be a
o
choice whether the IP address is to be retained or deleted, delete it. So that the factory
C
a
settings can be re-established for the HMI device via the Online access, the Runtime must be
exited for this!
Pe reir
e g o
6. Finally, update the accessible devices. There should no longer be an IP address for any
device!
Dy
Note
To fulfill this task, you do not have to create a project yet, nor do you have to open an existing
project!
Furthermore, your computer must be in the same subnet as the devices which you want to reset
to their factory settings.

For a PLC with Memory Card, the card must first be formatted before you reset to factory
settings! Otherwise, a reset to factory settings is not possible!
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Additional
2.31. Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Note
MO
o RU
u t inh
C o
a
Pe reir
e g o
Dy

ISOISO
2.31.1. / OSI 7 7– –Layer
/ OSI LayerModel
Model
Layers
7 Application 7. Application Layer

Anwendungs-
application-
6 Presentation 6. Presentation Layer orientiert
oriented
5 Session 5. Session Layer
4 Transport 4. Transport Layer M O

RU
o
tinh
3 Network 3. Network Layer Transport-
transport-
2 Data Link a Cou orientiert
oriented
e r eir
2. Data Link Layer
1 Physical o P
eg 1. Physical Layer
Dy
Open Systems Interconnection (OSI) – Model
The OSI – 7 Layer Model is a reference model for manufacturer-independent communication
systems, that is, a design basis for communication protocols and computer networks.
OSI stands for Open Systems Interconnection and was designed and standardized by ISO as the
basis for communication standards. The OSI layer model or OSI reference model is based on the
DoD layer model on which the Internet is based. In comparison to the DoD layer model, the OSI
layer model is more finely subdivided.
DoD layer model (Department of Defense):
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
The OSI model serves as a tool for describing the principle function of a network. It is divided into
seven sub-areas which are also referred to a layers. Each layer, with the exception of the
uppermost layers, makes its function available to the layers above it. The most important layers
for Ethernet are Layer 1 and Layer 2.

For each layer, functions and protocols are defined which must fulfill specific tasks for the
communication between two systems. For communication between two systems, the
communication or the data flow passes through all 7 layers of the OSI layer model twice - once at
the Sender and once at the Recipient. Depending on how many ‘stops’ the communication route
has, the communication also passes through the layer model several times.
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
MO
o RU
u t inh
Co
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.1. 1: Physical
1: PhysicalLayer
Layer
1. Physical Layer:
Layers
Measures and procedures for transmitting bit sequences
▪ Devices and network components are assigned to the
7 Application Physical Layer
▪ Defines the optical, electrical and mechanical connection
6 Presentation to the transmission medium
▪ Manages the coding of the individual bits or the bit
5 Session
sequences
4 Transport M O
R U
o
Network
tinh
3
C ou
2 Data Link
e ira
1 Physicalego
Per
Dy
SITRAIN
Physical Layer
In the physical layer, the electrical, optical and mechanical connection to the transmission
medium used is defined. It is responsible for the proper transmission of individual bits through the
physical channel. This is essentially a matter of the coding of signals, the defining of the
transmission medium and the transmission devices.
Each medium has its own section.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.2. 2: Data Link
2: Data LinkLayer
Layer
2. Data Link Layer:

Layers Logical connections to data packets and elementary error
detection mechanisms
7 Application ▪ Consists of two sublayers, the Logical Link Control layer
as well as the Media Access Control layer
6 Presentation ▪ Divides the bit data flow into blocks or frames and adds a
checksum
5 Session ▪ Ensures a reliable and error-free transmission on the
transmission medium
4 Transport M O
R U
o
Network
tinh
3
C ou
2 Data Link
e ira
1 Physicalego
Per Logical Link Control
Dy Media Access Control
SITRAIN
Data Link Layer
In the data link layer, the transmission and the grouping of the individual bits in the transferable
unit as well as the access procedure to the network is defined. It provides a reliable connection
between terminal and transmission medium and ensures an error-free transmission.
For this, the bit data flow is divided into (data) blocks, also called frames, and checksums are
added. With this checksum, flawed blocks can be detected by the recipient and subsequently be
rejected or even be corrected.
According to IEEE, the Data Link Layer is divided into two sublayers - the Logical Link Control
and the Media Access Control. Due to the Media Access Control, the data link layer is sometimes
also called the MAC Layer.
M O
Media Access Control
o RU
t inh
The Media Access Control layer is the lower of the two layers in the data link layer. It controls the
u
C o
access to the transmission medium. It defines which protocol is to be used. There are two
a
reir
different types of access, a controlled access and a competing access.
Controlled access: Pe
e g o
• Token Ring
D y
• Token Bus
• CSMA/CR
Competing access:
• ALOHA
• CSMA/CD
• CSMA/CA

Logical Link Control

The Logical Link Control layer is the upper of the two layers in the data link layer. It adds several
identifiers to the data packet which are structured as follows:
• DSAP (Destination Service Access Point) of 8 bytes
• SSAP (Source Service Access Point) of 8 bytes
• Control of 8 or 16 bytes
Note
A renewed request of rejected blocks is not regulated or provided in the data link layer!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

LayerLayer
2.31.1.3. 3: Network
3: NetworkLayer
Layer
3. Network Layer:
Layers Routing and data flow control
▪ It is responsible for the transmission of data packets
7 Application between the sender and the recipient
▪ The Internet Protocol, for example, belongs to the Network
6 Presentation Layer
5 Session
4 Transport M O
R U
o
Network
tinh
3
C ou
2 Data Link
e ira
1 Physicalego
Per
Dy
SITRAIN
Network Layer
The task of the Network Layer is the transmission of data packets between the sender and the
recipient. This includes the routing of the packets, the logical addressing of terminals and the flow
control.
Included in the Network Layer is, for example, the Internet Protocol or also the NSAP addresses.
Note
If communication between the sender and the recipient cannot take place directly, but only via
intermediate ‘stops’, the forwarding of packets occurs in the Network Layer.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.4. 4: Transport
4: Transport Layer
Layer
4. Transport Layer:
Layers
Logical end-to-end connections
▪ It is the link between the transport-oriented layers and the
7 Application application-oriented layers
▪ Ensures data transmission beyond network boundaries
6 Presentation
5 Session
4 Transport M O
R U
o
Network
tinh
3
C ou
2 Data Link
e ira
1 Physicalego
Per
Dy
SITRAIN
Transport Layer
The Transport Layer ensures data transmission beyond network boundaries, which is managed in
the LAN by the Data Link Layer. It is intended to have a logical connection to a remote
communication partner which is checked by acknowledgement telegrams. Connection-less
services are also supported.
Note
The Transport Layer offers Layers 5 to 7 a uniform access to the data. As a result, they do not
have to take the properties of the communication network into consideration.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.5. 5: Session
5: SessionLayer
Layer
Layers
7 Application
6 Presentation
5 Session
4 Transport M O
RU
o
Network
tinh
3
C ou
2 Data Link
r ei ra
5. Session Layer:
Process-to-process connections
e
P Provides the process communication between two
1 Physicalego ▪
Dy ▪
systems
Provides services for a synchronized and organized data
exchange (Check Points)
SITRAIN
Session Layer
The task of the Session Layer is the organization of the communication between the recipient and
the sender. It provides services for an organized and synchronized data exchange. If, for
example, during communication a connection is lost, the session can be continued at so-called
check points and doesn’t have to start at the beginning.
The RPC Protocol (Remote Procedure Call) is included in this layer.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.6. 6: Presentation Layer
6: Presentation Layer
Layers
7 Application
6 Presentation
5 Session
4 Transport M O
RU
o
Network
tinh
3
C ou
2 Data Link ra
iPresentation
re6.Output Layer:
1 Physicalego
Pe of data in standard formats
▪ Converts the data into different codecs and formats
Dy ▪ Makes data exchange between different systems possible
through independent standard formats
SITRAIN
Presentation Layer
The Presentation Layer makes data exchange between different systems possible. This is
achieved by converting system-dependent presentations of data into an independent form.
Furthermore, data compression as well as data encryption belongs to the Presentation Layer.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

LayerLayer
2.31.1.7. 7: Application Layer
7: Application Layer
Layers
7 Application
6 Presentation
5 Session
4 Transport M O
RU
o
Network
tinh
3
C ou
2 Data Link
r ei ra
e
P 7. Application Layer:
1 Physicalego
Dy
Services, applications and network management
▪ Establishes the connection to the lower layers
▪ Manages the data input and the data output
SITRAIN
Application Layer
The Application Layer establishes the connection to the lower layers and provides functions for
the applications. The data input and the data output also takes place in this layer.
It includes the user-specific services of the various communication applications!
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

TRACERT
2.31.2. / Trace
TRACERT Route
/ Trace Route
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
TRACERT / Trace Route
In addition to the Ping command to determine whether a connection exists to a network
component, the TRACERT command can be executed to receive further information.
With the “tracert” command, the path of data packets in an IP network can be tracked and made
visible.
Note
Just as with the Ping command, you can get a listing of all possible combinations with the
“tracert” command by entering “tracert” or “tracert /?”.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

IPv6
2.31.3. IP Address V6
192.168.0.2 2001:0db8:85a3:08d3:1319:8a2e:0370:7344
IPv4 IPv6
Decimal format Hexadecimal format
2001:0db8:85a3:08d3 1319:8a2e:0370:7344
Network Prefix (64 bits)

M O
Interface Identifier (64 bits)
R U
o
tinh
2001:0db8:0000:0000:0000:8a2e:0070:7344 IPv6 address
C ou
2001:db8:0:0:0:8a2e:70:7344
ira Leading zeros can be omitted
P ere
o
yeg
2001:0db8::8a2e:0070:7344 Several zeros can be omitted
D
An IPv6 address is represented in 8 blocks à 4 hex, separated by a colon

IP Address V6
An IPv6 address consists of 128 bits and thus allows an address amount of 2128 or also written as
340,282,366,900,000,000,000,000,000,000,000,000,000 IPv6 addresses. In comparison, IPv4
allows 4.3 billion addresses. That is, 6x1023 addresses per m 2 of the earth’s surface including
areas of water can be assigned!
An IPv6 address is subdivided into 8 times 16 bits. These 16 bits are represented as a
hexadecimal number per each 4 bits. The presentation of an IPv6 address is therefore
hexadecimal. The 8 blocks of 4 hexadecimal numbers each are separated by a colon “:”. In order
to ensure a simplified notation, leading zeros in a block can be omitted and a string of zeros can
be replaced by two colons “::”. However, the last simplification can only be used once in an IPv6
address!
U MO
R Prefix and the last 64 bits as
The first 64 bits of an IPv6 address are referred to as the Network
o
the Interface Identifier.
t in h
C o u
The notation of the hexadecimal characters should also be noted for an IPv6 address. By
i r
definition, these must be written in lower a case and must not be written in upper case!
P ere
Note
y e go
D Stream Protocol which has identified its own packets with an IPv5 identifier.
There is an Internet
However, this was never publically used and was only used for experiments. In order to avoid
confusion and possible complications, it was however therefore determined to call the new
address type IPv6 and not IPv5.

Special
2.31.4. IP IP
Special Area Ranges
Area Ranges/ /IP
IP Addresses
Addresses
Address area Meaning

0.0.0.0/8 Hosts on the local network. Only as source address.
10.0.0.0/8 Private addresses. Not in use on the public Internet
127.0.0.0/8 Loopback addresses. Typically only 127.0.0.1 is used.
169.254.0.0/16 “Link-Local-Address”, can only be used on a Link.
172.16.0.0/12 Private addresses. Not in use in the public network.
192.168.0.0/16 M O
Private addresses. Not in use in the public network.
R U
224.0.0.0/4 o
IPv4 Multicast addresses, only as destination address.
240.0.0.0/4
ou tinh
Reserved addresses with the exception of 255.255.255.255.
C
255.255.255.255/32
r e i a Can only be used in the local network.
Broadcastraddress.
e
eg oP
Dy
Special IP Area Ranges / IP Addresses
It was established and incorporated in the devices that special IP addresses and also IP area
ranges are used for specified tasks. These tasks are incorporated in the hardware of the devices
and can only be used for these, that is, should only be used for these.
The picture shows a brief overview.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Contents 3
3. Basics of PROFINET .............................................................................................. 3-2
3.1. PROFINET ............................................................................................................................ 3-3
M O
3.2. U
PROFINET vs. PROFIBUS ................................................................................................... 3-4
R
o
tinh
3.3. PROFINET Communication Model ....................................................................................... 3-5
3.4. ou
Real-time Communication in PROFINET ............................................................................. 3-6
C
3.5.
e ira .................................................................................... 3-7
Network Components in PROFINET
r
3.6.
o Pe
I/O Communication via PROFINET IO ................................................................................. 3-8
e g
3.7.
Dy Addressing ........................................................................................... 3-10
PROFINET Device
3.8. PRONETA ........................................................................................................................... 3-11
3.8.1. Task Description: PRONETA – IP Addresses & Device Names of the Network Components
& Line Test .......................................................................................................................... 3-12
3.8.1.1. Exercise 1: Assigning IP Addresses to the Devices using the PRONETA Tool ................. 3-13
3.8.1.2. Exercise 2: Initializing the Network Components with the PROFINET Device Name using
PRONETA ........................................................................................................................... 3-14
3.9.1. PI - PROFIBUS and PROFINET International .................................................................... 3-16
3.9.2. Primary Setup Tool – PST .................................................................................................. 3-17
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Basics of PROFINET

Basics of PROFINET
3. Objectives
... know what is meant by the term “PROFINET”
... understand the basic functioning of PROFINET
…
M O
be familiar with the Primary Setup Tool
R U
… o
be familiar with the PRONETA tool
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Basics of PROFINET Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

3.1. PROFINET
PROFINET
PROFINET is Ethernet For comparison: PROFIBUS

▪ Ethernet is the established standard in the IT world for the ▪ One line to which all
fast exchange of data (IEEE 802.3) nodes (devices) are
▪ PROFINET is always full duplex → simultaneous connected
communication in two directions ▪ Performance directly
100 MBit/s
dependent on the number
100 MBit/s
of nodes (devices)
Controller
100 MBit/s full duplex
Master
▪ PROFINET is always
“switched Ethernet”
U MO
o R
t in h
▪ Distribution of network load C o u Slaves
can be influenced using

eira
topology
P e r
▪ PROFINET uses the
eg o
Dy
Devices
standardized structure of
Ethernet telegrams
PROFINET completely uses all possibilities offered by Ethernet
Page 3 Basics of PROFINET
PROFINET
PROFINET combines the advantages of two worlds. It provides the properties of PROFIBUS
needed for industrial use and combines them with the properties of Ethernet. This results in a
flexible, efficient and high-performance system: PROFINET. The following pages explain how
PROFINET works and why.
Advantages of Ethernet in Automation

• With the future demands placed on performance and data quantities, the fieldbus is
reaching its limit
• O
Ethernet offers a powerful and future-proof communication platform through continued
M
technical development
o RU
•
inh
Vertical integration offers previously unused productivity potential through the connection
u t
of the office and automation worlds
C o
a
reir
• In the office world, Ethernet is the unequivocal standard regarding installation technology
and protocols Token Bus (802.4)
P e
e g o
Features of PROFINET
D y
• Internationally standardized: IEC 61158, IEC 61784
• Integrated communication via fieldbus and Ethernet
• Integration of existing fieldbus systems (PROFIBUS, ASI)
• Use of the TCP/IP protocol
• Communication in real-time
• Isochronous drive control for Motion Control applications via IRT

3.2. PROFIBUS vs. vs.

PROFINET PROFINET
PROFIBUS
Property PROFIBUS PROFINET

Bit transfer EIA-485 100 Base-TX, 100 Base-FX
Cable 2-wire 4-wire
Unlimited / network; up to 100 m / copper
Max. length 1200m / segment
cable
9.6 kBit/s – 12 Mbit/s
Transmission rate 100 Mbit/s Full duplex
Half duplex
Topology Line, Tree, Ring M O
Line, Star, Ring, Tree, Wireless
Data transmission Common medium R U
Switched network
h o
User data/Frame 246 bytes
o tinbytes
1440
u
C Unlimited / network;
Devices
r e ira
Up to 32 / segment
up to 256 IO-Devices per IO-Controller
Addresses o Pe1…125
DP address: Device name (unlimited number)
eg
Dy
PROFINET vs. PROFIBUS
The picture shows the most important characteristics and differences between the two bus
systems.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

3.3. PROFINET Communication

PROFINET Model
Communication Model
Prioritization of the RT frames by means of VLAN tagging according to IEEE 802.1q
1 Open TCP/IP channel

IT applications
PROFINET applications • Device
• HTTP
• SNMP parameterization
• DHCP … 1 • Reading diagnostic
Standard data Realtime data data
O
• Negotiating the
Realtime
TCP/UDP
U M
communication channel
o R for user data
IP
2 ou RT tinh 2 Real-time channel
ra C • High performance
i
ere
Ethernet
P
transmission
o • Cyclic data
D yeg • Event-controlled
messages

IT Standards
The WEB integration of PROFINET was primarily designed with commissioning and diagnostics
in mind. Standard protocols (e.g. http) are used to access a PROFINET device from the Internet
or Intranet. The data is transmitted in standard formats, such as, HTML or XML and can be
presented with standard browsers, such as, Firefox or Internet Explorer.
Due to the world-wide accessibility, it is possible for the application producer to easily support the
user in commissioning, device diagnostics etc. The access to the data takes place via web
servers which are integrated in the modules.
Real-time Channel (RT channel)

M O
o RU
In order to be able to satisfy the real-time requirements of automation, an optimized
real-time communication channel, the real-time channel (RT channel), was specified in
PROFINET. It builds on Ethernet (Layer 2).
u t inh
o
The data packets are addressed on the basis of the MAC addresses of the devices involved
C
a
reir
instead of on an IP address. This type of solution minimizes the processing times in the
communication stack considerably and leads to an increase in performance with regards to the
P e
length. e g o
update rate of automation data. Removing several protocol layers reduces the (telegram) frame
Dy

3.4. Real-time Communication

Real-time in PROFINET
Communication in PROFINET
M O
R U
o
tinh
Cou
Real-time data and standard
data on one cable
eira
P e r Separate channels for IO-
eg o data and TCP/IP data
Dy Prioritization of IO-data
according to IEEE 802.1q

Optimized Data Transmission through Prioritization
In addition to the minimized communication stack in the programmable controllers, transmission
of data over the network is also optimized in PROFINET. Measurements have shown that in
switched networks, for an extremely high network load, transmission times of up to 20 ms can
occur between two stations on Ethernet. A network load of this size cannot be ruled out when
using standard network components, for example, when simultaneously uploading quality data
from the devices. In order to be able to achieve the best result here too, the packets are
prioritized in PROFINET according to IEEE 802.1q (VLAN).
The network components control the data flow between the devices on the basis of these
priorities. Priority 6 (Network Control) is used as the standard priority for real-time data. This
O
causes a priority handling over other applications, such as, Internet telephony with Priority 5.
M
RU
The prioritization of PROFINET telegrams with the help of the VLAN tag only causes the
o
PROFINET telegrams to be preferentially sent. Due to the PCP, however, the sending of a lower
priority telegram is not interrupted!
u t inh
o
If, for example, video data with the same priority as the PROFINET data occurs, a difference can
C
i r a
be detected in the RT transmission: → longer jitter times.
e of IRT switches.
P ermeans
Solution: use IRT functionality by
Network components e
y gocontrollers available on the market can be used for real-time
and
communication. OfDcourse, only on the premise that the switches used can evaluate the priority of
the PROFINET telegram.
IRT Channel
Isochronous Real - Time (IRT) as a further development with the following properties:
• Isochronous data transmission
• Cycle times <1ms with jitter accuracy <1µs
• Typical area of application is Motion Control

3.5. Network Components

Network in PROFINET
Components in PROFINET
PROFINET IO-System
IO-Supervisor
S7-1500 IO-Controller
PG/PC
PROFINET / Industrial Ethernet

M O
RU
S7-300 t
ET200i n ho
MP
a Cou
e r eir TP
o P
eg
Dy
I-Device
IO-Device HMI

Devices for PROFINET IO
The general names of the most important devices in PROFINET are presented in the picture. The
following contains a brief explanation of the terms:
• IO-Controller:
Device through which the connected IO-Devices are addressed. This means that the IO-
Controller exchanges the input and output signals with the connected field devices. It
corresponds to Class-1-Master in PROFIBUS.
• IO-Device:
A distributed-arranged field device which is assigned to an IO-Controller, for example,
O
distributed IO, valve block, frequency inverter, switches with integrated PROFINET IO
M
RU
functionality. In PROFIBUS, an IO-Device corresponds to the Slave.
o
• IO-Supervisor:
u t inh
PG/PC/HMI device for commissioning and / or for diagnosis. In PROFIBUS, it
corresponds to a Class-2-Master. C o
a
• I-Device:
P ereir
e g o
Intelligent IO-Device. A PLC is not configured as an IO-Controller, but as an I-Device and
Dy
provides a higher-level controller with I/O data in a transfer area.
• HMI:
Device for operator control and monitoring.

3.6. I/O I/O

Communication via PROFINET
Communication IO IO
via PROFINET
IO-Controller PN/PN-Coupler IO-Controller
IO-Controller – IO-Controller communication via PN/PN coupler
IO-Controller –
I-Device
communication PROFINET IO 1 PROFINET IO 2
M O
IO-Controller – R U
I-Device I-Device I-Device
h o IO-Device
tinPROFINET IO 3
IO-Device IO-Controller
communication
C ou
e i ra
o Per
eg
Dy
IO-Device IO-Device I-Device

PROFINET Communication
PROFINET communication takes place via Industrial Ethernet. The following types of
transmission are supported:
• Acyclic transmission of engineering and diagnostic data and alarms
• Cyclic transmission of user data
PROFINET IO communication occurs in real-time.
I/O Communication
O
The reading or writing of inputs/outputs of distributed IO through PROFINET IO occurs via so-
M
RU
called I/O communication. The picture shows the various network components between which
communication can take place in PROFINET:
t i n ho
ou via PN/PN coupler
• IO-Controller - IO-Controller communication
C
r e ira
• IO-Controller - IO-Device communication
Pecommunication
• IO-Controller - I-Device
o
y eg
D
IO-Controller – IO-Controller Communication via PN/PN Coupler
A fixed number of data is cyclically transmitted between the user programs in CPUs of IO-
Controllers. A PN/PN coupler is required as additional hardware.
The IO-Controllers mutually access configured address areas, so-called Transfer areas, which
can be located within or outside of the process image of the CPUs. If parts of the process image
are used as Transfer areas, these must not be used for real I/O modules.
The data transmission occurs with Load and Transfer operations via the process image (tables)
or via direct access.
IO-Controller – IO-Device Communication

The IO-Controller cyclically sends data to the IO-Devices of its PROFINET IO-System and
receives data from them.

IO-Controller – I-Device Communication

A fixed number of data is cyclically transmitted between the user programs in CPUs of IO-
Controllers and I-Devices.
The IO-Controller does not access I/O modules of the I-Device but configured address areas, so-
called Transfer areas, which can be located within or outside of the process image of the CPU of
the I-Device. If parts of the process image are used as Transfer areas, these must not be used for
real I/O modules.
The data transmission occurs with Load and Transfer operations via the process image (tables)
or via direct access.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

3.7. PROFINET Device

PROFINET Addressing
Device Addressing
IO-Controller
MAC address
IO-Device
IP address
M O
R U
o
ou tinh
ra C
e i MAC address
o Per
eg Device name
Dy IP address

PROFINET IO-System
So that the IO-Devices are accessible for the IO-Controller, they must be supplied with unique
address parameters. Each IO-Device has three address parameters for the complete address:
• MAC Address:
Each PROFINET device already has a burnt-in, world-wide unique MAC address when it
is delivered. As a rule, this cannot be changed. It is required for the real-time
communication.
• Device Name:
Before an IO-Device can be addressed by an IO-Controller, it must have a device name.
O
For PROFINET, this approach was selected because names are easier to manage than
M
complex IP addresses.
o RU
• IP Address:
u t inh
In addition to the device name and the MAC address, an IO-Device also requires an IP
C o
address so that, for example, acyclic Read/Write services can be executed.
a
P e reir
e g o
Dy

3.8. PRONETA
PRONETA
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Entry ID: 67460624

PRONETA
SIEMENS PRONETA is a free PC-based software tool which simplifies the commissioning of
PROFINET systems by being able to take over the following tasks:
• Topology Overview (Network Analysis):
PRONETA automatically scans the PROFINET and all connected components and then
displays a topologic overview. This overview can be exported in the form of a device list.
It is possible to “initialize” the components and do other simple configuration tasks as well
as comparing the real configuration with a reference plant.
• IO Test:
O
PRONETA allows for an IO-Test for quickly testing the wiring of a plant and the module
M
o RU
expansion of components. By reading or writing the inputs and outputs, PRONETA
ensures that the distributed I/Os are correctly wired with their sensors and
t inh
actuators.PRONETA can create test profile templates and store test protocols in order to
u
document the test results.
C o
a
P e reir
All of these tasks can be carried out even before a CPU is integrated in the network.
Moreover, since neither other engineering tools nor hardware are required, PRONETA makes
g o
the fast and easy testing of the plant configuration possible at an early point in time.
e
Dy
PRONETA is an official product of Industrial Communication under PROFINET and so can
also be found on the SIEMENS pages:
http://w3.siemens.com/mcms/automation/de/industrielle-
kommunikation/profinet/produktportfolio/proneta/Seiten/proneta.aspx
Note
You will find further information, documentation as well as the download for the PRONETA Tool
on the Service & Support pages under the Entry ID number: 67460624.

Task Description:
3.8.1. PRONETA
Task Description: PRONETA– IP
– Addresses &
Device
IP Names of the
Addresses Network
& Device Components
Names of the Network Components & Line Test
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task Description
Before you can read out the networking configuration, make the renewed assignment of the IP
addresses and the device names as well as do the line test with the help of the PRONETA tool,
all devices must once again be reset to factory settings. Afterwards, do the steps above for the
devices.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Übung 4: Vergabe der Teilnehmer
IP-Adressen
3.8.1.1. Exercise 1:über das IP
Assigning Tool PRONETA
Addresses to the Devices using the PRONETA Tool
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
IK-TIAPN / Grundlagen PROFINET
Task Seite 19 Siemens AG © 2016
With the help of the PRONETA tool, you are once again to assign an IP address to all network
devices. Again, the devices are to be given the following IP addresses:
• S7-1513-1PN: 192.168.222.1
• ET200SP: 192.168.222.2
• TP700 Comfort: 192.168.222.3
• SCALANCE X208: 192.168.222.4
• S7-1510SP-1PN : 192.168.222.5
M O
R U
All devices are to be assigned the subnet mask 255.255.255.0.
h o
What to Do
o u tin
r a C
1. Start the PRONETA tool.
i
P ereview
2. Switch to the “Network analysis”
3. In any order you ylike,
o all network components the IP addresses as well as the subnet
egassign
mask definedD in the task.
Note
Even the PRONETA tool allows you to identify a device through a flash test:

Exercise 5: Initializing the Network Components

3.8.1.2. Exercise 2: Initializing the Network Components with the PROFINET Device Name using
with the PROFINET Device Name using PRONETA
PRONETA
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task
With the help of the PRONETA tool, you are to assign a PROFINET device name to all network
devices. You are free to use with the following information or choose your own:
• S7-1513-1PN: s7-1513-plc
• ET200SP: et200-io-device
• TP700 Comfort: tp700-comfort-panel
• SCALANCE XC208: scalance-xc208-switch
M O
• S7-1510SP-1PN : s7-1510sp-plc
o RU
What to Do
u t inh
C o
1. Initialize all network devices with the help of the PRONETA tool.
a
P e reir
e g o
Dy

Additional
3.9. Information
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

PI - PROFIBUS
3.9.1. andand
PI - PROFIBUS PROFINET International
PROFINET International
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
PROFIBUS & PROFINET International
27 Regional PI Associations (RPAs) are members in this international umbrella organization. One
of them is the PROFIBUS Nutzerorganisation e.V. (PNO). The goal of the PNO as well as the
other Regional PI Associations is to promote the technology’s advancement as well as the
international propagation of the open and standardized technologies PROFIBUS and PROFINET.
On the PI Homepage, you can get information and can download free-of-charge a variety of
documents such as directives, profiles, presentations, brochures, software etc.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

3.9.2.Primary Setup
Primary Tool––PST
Tool
Setup PST
Browse
Download
Mac address
IP address
M O
R U
o
ou tinh
ra C
e i
o Per Device name
Dyeg
Entry ID: 19440762

PST – Primary Setup Tool
The Primary Setup Tool, short PST, is a software provided by Siemens free of charge. With the
help of the PST, network components, Ethernet CPs, controllers, IO-Devices can be carried out
for SIMATIC NET. As well, address assignments such as the assignment of IP addresses or the
initialization with a PROFINET device name can be carried out for network transitions.
The PST does not require any other software packages or licenses for this functionality. The only
requirement is that these SIMATIC NET devices have a preset ETHERNET (MAC) address and
are accessible online in the network.
If the SIMATIC NET module should have an integrated Web Based Management, this can be
O
called directly in the PST via the button: “Start the browser for configuring INC modules ”.
M
Note RU
o
You will find further information on the various u t i n h
versions of the Primary Setup Tool on the Service
& Support pages under the Entry ID number: C o19440762. Furthermore, you can also download the
various versions of the Primary Setupei r a
Tool from this Entry ID number.
P e r
e g o
Dy

Contents 4
4. Network Components ............................................................................................ 4-2
4.1. System Configurations over the Course of Time .................................................................. 4-3
M O
4.2. U
Basic Structures of the Network Topology ............................................................................ 4-4
R
o
tinh
4.3. Conceptual Design Information ............................................................................................. 4-6
4.4. ou
Network Components ........................................................................................................... 4-7
C
4.5. Cable Categories for Twisted-Pair
r e iraCables............................................................................ 4-8
4.6.
o Pe
FastConnect ........................................................................................................................ 4-10
g
yeCabling with FastConnect ...................................................................... 4-11
4.7.
4.7.1.
D
Task Description:
Exercise 1: Stripping with the Help of the Stripping Tool .................................................... 4-12
4.7.2. Exercise 2: Assembling the IE Cable .................................................................................. 4-13
4.8. Optical Cabling and Connecting Methods .......................................................................... 4-14
4.9. Active Industrial Ethernet Components .............................................................................. 4-15
4.10. Industrial Wireless LAN Components ................................................................................. 4-16
4.11. Communication Processors (CPs) for IE ............................................................................ 4-18
4.12. TIA Selection Tool ............................................................................................................... 4-19
4.13. Task Description: Reading-out the Firmware of the Devices & Configuration of the System in
the TIA Selection Tool ......................................................................................................... 4-20
4.13.1. Exercise 3: Reading-out the Firmware of the Devices (TIA Portal) .................................... 4-21
4.13.2. Exercise 4: Configuration of the System in the TIA Selection Tool .................................... 4-22
4.14. O
Additional Information ......................................................................................................... 4-23
M
RU
4.14.1. Versions of IE FC RJ45 Plugs ............................................................................................ 4-24
4.14.2.
o
Industrial Ethernet FC Modular Outlet RJ45 ....................................................................... 4-25
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Network Components

Network Components
4. Objectives
... have a basic overview of the plant configurations
... know the various network topologies
... be familiar with network components

M O
R U
... o
know and understand the difference between active and passive
network components
ou tinh
...
ra C
understand the FastConnect concept
e i
...
o Per
know the TIA Selection Tool and be able to use it to configure his
eg network configuration
Dy
SITRAIN
IK-TIAPN / Network Components Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

4.1. System Configurations

System overover
Configurations the Course of Time
the Course of Time
Central Not Central Distributed
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 3 Network Components
System Configurations
The demands on industrial systems in automation have kept evolving and increasing over the
years. As a result, technology and the technical possibilities have also been further developing.
In the beginning, without fieldbuses, system components were wired centrally to the controllers
and managed. With the establishment of fieldbus systems, came the first shift into industrial
automation. This saved cabling effort, installation time and cost. However, this also had a more
complex wiring of the system as a consequence. PROFIBUS, in particular, asserted itself here.
Since the Internet and thus also Ethernet components have become more and more common
and accepted in everyday life, the next step into industry was only a question of time. This was
then taken with Industrial Ethernet and PROFINET. Everyday Ethernet components were made
O
compatible for industrial use and so found their way into automation.
M
RU
Distributed networks with switches and routers, the connection to the office world as well as
o
Industrial Security or even IWLAN are today a part of everyday life and are an integral part of
automation.
u t inh
C o
a
P e reir
e g o
Dy

4.2. Basic Structures

Basic of the
Structures of Network Topology
the Network Topology
Line Star Tree
M O
R U
Ring
o
ou tinh
ra C
e i
o Per
eg
Dy
Network Topologies
Network topologies are oriented toward the requirements of the devices to be networked. The
most common topologies include Line, Star and Ring structures. In reality, most systems consist
of mixed structures. These can be implemented with both electrical cables and with optical cables
(fiber optic cables).
Line
The line is the simplest network structure. It is characterized by the "backbone" of the network to
which the individual devices are connected either directly or via individual branches whereby
each branch only contains one device.
U MO
The advantage of the line topology is the easy construction o Rwhich only requires limited hardware
h
tin networking of rigidly coupled machines
investment. It is suitable, for example, for the large-scale
like in a production line. o u
Cthe resources are not fully utilized and that there is a
Disadvantages of the line topology area
i r that
lack of redundancy: a break in the
P ere line at one location cannot be bridged.
o with line structure is the physical arrangement of the network
egtheir
A further limitation for networks
devices. Dependingy on position, the backbone must potentially be laid the long way around
which in turn canD lead to problematic telegram runtimes. Line structures are typically designed
with devices with two integrated network interfaces.
Ring
If the two ends of a line are connected by means of an additional connection, a ring structure is
created. The switches interconnected into a ring do not have to be exclusively connected with
fiber optic or electrical cables. A mixed electro-optical ring is also allowed.

A ring topology without a special redundancy mechanism is not possible! This would lead to the
complete failure of the network. The special redundancy mechanism ensures that the ring
structure normally remains a logical line and consequently no telegrams go around in circles.
When a ring section fails, the mechanism makes it possible for an alternate route to be quickly
available in the ring: instead of via the direct, now interrupted route, the message goes via the
long, intact network section and reaches its recipient "indirectly". The network does not
disintegrate into two segments.
Star
The star topology differs from the line in that a switch acts as the "center" of a network from which
the cables branch to the individual end devices. The connection between the individual devices
thus no longer occurs directly but indirectly via the switch.
M O
U
The immediate effect of this topology is that the messages no longer have to take “detours” via
R
o
other devices but are purposefully sent from the switch to the recipient. This means that the
ou tinh
network performance increases significantly since all devices of the star can communicate
simultaneously. In addition to the network performance, the reliability also increases. Should a
ra C
cable to a device fail, all other network components remain unaffected by it.
e i
o Per
Tree eg
Dy
If several star topologies are connected with one another, this is called a tree topology. Typically,
these star structures are then aligned hierarchically.
Larger networks have this structure, especially when several topologies are combined with one
another. In most cases, a higher-level network element, either a coupler element or another
topology, forms the root. From there, a trunk with many branches is formed.
Intermeshed Topology
Intermeshed networks are when network components are linked multiple times. The network is
fully intermeshed when each component is connected with every other component. This topology
is usually used in an office but it is also used in industry for special cases such as energy
transportation. However, this topology cannot be implemented without a special protocol.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

4.3. Conceptual Design

Conceptual Information
Design Information
Structure networks logically!
M O
R U
Communication
o
bottleneck
ou tinh
ra C
e i
o Per
eg
Dy
Conceptual Design Information
When planning and wiring network components certain framework conditions have to be taken
into account. These are not ‘must’ obligations but are useful information on how to increase the
performance and the availability of the devices:
• Devices that have a high communication load should not be put at the end of line
structures.
• If line structures are planned, the increased failure risk must be taken into account and
must be considered in the plans.
•
O
Due to their high data traffic, CPUs should always be connected to central switches.
M
•
RU
Use firewalls when integrating networks into higher-level networks or when connecting to
the Internet. Topic: Security
t i n ho
• Avoid bottlenecks when designing the u
C o network
• ira a manner as possible
Configure networks in as structured
r e
o Pe
y eg
D

4.4. Network Components

Network Components
Passive Components Active Components
ID: 84922825
M O
RU
o
outinh
ra C
e i
o Per
eg
Dy
Forward a signal without actively
Influence the signal
influencing it

Network Components
Industrial Ethernet networks can contain two types of network components. These network
components are divided into active and passive components.
Passive Components
Network components which do not have an active influence on the signal are classified as
passive components. Normally, all connection technology components such as plugs,
connectors, cables, etc. fall into this category.
A listing of all passive components can be found in the Industry Online Support pages under the
Entry ID: 84922825.
M O
Active Components
o RU
t inh
Network components which actively influence the signal in the network are classified in the
u
o
category of active components. This can be a signal processing or even the rejection of a
C
a
reir
telegram. Examples of active components are switches, access points, repeaters, media
converters or even Link modules.
P e
e g o
Dy

4.5. Cable Categories

Cable for Twisted-Pair
Categories Cables
for Twisted-Pair Cables
Category Transmission speed The Category (CAT) specifies for which

CAT1 --- transmission speed and which maximum length
a cable designed
CAT2 ---
CAT3 10MBit/s
CAT4 16MBit/s
CAT5 100MBit/s
CAT5e 1GBit/s
CAT6 1GBit/s
CAT6a 10GBit/s
M O
CAT6e 10GBit/s R U
o
CAT7
CAT8
10GBit/s
40GBit/s ou tinh
ra C
e i
Still in the
o Per
eg
development stage
Dy
Categories for Twisted-Pair Cables
According to EIA/TIA-568, ISO/IEC-11801, EN50173 and EN 50288-x-x, TP cables are divided
into different categories or levels. They specify the electrical minimum requirements for the cable
and essentially specify the maximum permissible transmission frequency. Currently the
Categories 1 to 7 are defined. The permissible transmission frequency increases with the cable
category. A Twisted-Pair cable of a certain category complies with the requirements of the
respective category and with those categories below that.
Category 1 (CAT1)
Category 1 cables are designed for voice transmission in telephony and for data transmission at a
M O
low transmission frequency of less than 1MHz. Nowadays, such cable is no longer used.
RU
Category 2 (CAT2)
t i n ho
o u
CAT2 cables are designed for transmission frequencies
C of up to 4MHz. Such cable types were
frequently used for house cabling suchaas for ISDN.
e r eir
Category 3 (CAT3)
o P
g
ye for a transmission frequency of up to 10MHz and so permits a
D
A CAT3 cable is designed
transmission speed of up to 10Mbit/s and a maximum cable length of 100m. Nowadays, such
cable types really no longer find a use in the LAN area.
Category 4 (CAT4)
Cables of the CAT4 cable type are designed for transmission frequencies of up to 20MHz and
transmission speeds of up to 16Mbit/s. These were frequently used in Token Ring networks.
Category 5 (CAT5)
Transmission frequencies up to 100MHz are specified in Category 5. Here, transmission speeds
of up to 100Mbit/s are possible.

Category 5e (CAT5e)
As far as the quality of the cable is concerned, there is no difference between Category 5 and
Category 5e. So that a cable fulfills the conditions for Category 5e, more rigorous acceptance
measurements are however necessary. These measurements are defined through the
ANSO/TIA/EIA-TSB-67 standard. If these criteria are fulfilled, a CAT5e cable is also authorized
for the operation of 1000BASE-T, that is, 1GBit/s.
Category 6 (CAT6)
Cables of the CAT6 cable type are designed for transmission frequencies of up to 250MHz and
transmission speeds of 1GBit/s. Category 6 is extended by the two sub-categories 6a and 6e.
Category 6a (CAT6a)
M O
The “a” for Category 6a cable types stands for “augmented”, that is, improved. Such cables are
R U
specified for transmission frequencies of up to 625MHz and thus permit transmission speeds of
o
tinh
up to 10GBit/s and cable lengths of up to 100m.
Category 6e (CAT6e) C ou
e i ra
o Per
Cables of the CAT6e cable type permit frequencies of a maximum of 500MHz and a maximum
length of 55m for a transmission speed of 10GBit/s.
eg
Category 7 (CAT7) Dy
For Category 7 cables, transmission frequencies of up to 600MHz are permitted and a
transmission speed of up to 10GBit/s. Since, however, the requirements for shielding are very
high in Category 7, this not only has an impact on the cable itself but also on the connector
technology and the assembly of these. Category 7 connectors must fulfill either the IEC 60603-7-
7 standard or the IEC 61076-3-104 standard.
Category 8 (CAT8)
In Category 8, a transmission rate of 40GBit/s and a maximum frequency of 2000MHz is planned.
However, this specification is currently still in the planning stages.
Note
The specific cabling of industrial plants is defined in the IEC 61918 standard and the structured
cabling of industrial buildings is defined in the ISO/IEC 24702 standard.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

4.6. FastConnect
FastConnect
Stripping tool for IE

FC cables
M O
RU Special IE FC cable
n h o
u t i
C o
eir a
P e
IE FC RJ45 plug r
eg o
Dy
FastConnect
FastConnect is a cabling system consisting of cables, plugs and tools for PROFIBUS and
Industrial Ethernet/PROFINET networks, available for copper and glass fiber optic cables for on-
site assembly.
FastConnect can be assembled quickly and easily on-site. As a result, the RJ45 cabling
technology, as an existing standard, is also available as an industry-suitable design.
IE FC RJ45 Plugs
The IE FC RJ45 plugs are compact and rugged connectors. They have a rugged, industry-
suitable metallic enclosure which protects the data communication against interference. The
plugs conform to the EN 50173 (RJ45) and ISO/ IEC 11801 standards. M O
RU
IE FC TP Cable
t i n ho
The FastConnect (FC) Twisted Pair (TP) cables
C o u are shielded, radial symmetrically designed
cables with 100 Ohms surge impedance.
e a shield and braided shield make the FC cables
irfoil
r
Pe in an electromagnetic industrial environment. The design also
The combination of twisting the wires,
o
particularly suitable for installation
egTool,
guarantees great stability of the electrical and mechanical data in the installed state.
D y
With the IE FC Stripping it is possible to remove the correct length of outer sheath and
shield of the FC TP cables in one go.
Stripping Tool
With the Industrial Ethernet FastConnect (IE FC) Stripping Tool, the correct length of outer sheath
and shield can be removed from Industrial Ethernet FastConnect cables. The IE FC cable
prepared this way is connected to the plug or the outlet via cutting/clamping contacts. For the IE
FC Stripping Tool there are two knife cassettes with different knife clearances. The IE FC
Stripping Tool is delivered with a yellow knife cassette.
Note
The IE FC Stripping Tool may be used only for stripping SIMATIC NET Industrial Ethernet
FastConnect cables. If the tool is used in any other manner, it can lead to accidents or the
destruction of tool and cable.
Task Description:
Cabling
4.7. with
Task FastConnect
Description: Cabling with FastConnect
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN
Task / Network Components
Description Page 10 Siemens AG © 2016
You are to do a theoretical check of the Ethernet cabling of the training devices. In this context,
you are to remove the insulation from an Ethernet cable and then assemble an RJ45 plug.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 1:
4.7.1.Stripping with
Exercise the Helpwith
1: Stripping of the
the Stripping
Help of theTool
Stripping Tool
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to remove the insulation from a Siemens Industrial Ethernet FastConnect cable.
What to Do
1. Prepare the cable in such a way that you have a clean cut edge.
2. Use the Stripping Tool to measure the required length for removing the insulation.
3. Carry out the cable stripping as shown in the picture.
4. Untwist the stripped cable.
M O
RU
Note
o
inh
So that the insulation is cleanly removed from the cable, the knife cassette of the Stripping Tool
u t
must be adjusted. Use the Allen key provided for this.
o
a C
P e reir
e g o
Dy

4.7.2.Exercise 2: 2:
Exercise Assembling
Assemblingthe
the IE
IE Cable
Cable
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Task
You are to assemble a FastConnect RJ45 plug using the cable you stripped in Exercise 1.
What to Do
1. Prepare the RJ45 plug assembly by imitating the color coding of the plug on the cable.
2. Open the IE FC RJ45 plug. If necessary, use a suitable screwdriver.
3. Carry out the assembly steps as shown in the picture.
4. Close the IE FC RJ45 plug and test its functioning.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

4.8. Optical Cabling

Optical and and
Cabling Connecting Methods
Connecting Methods
Fiber optic cable transmission technology according to IEC 8802-3
Cables
▪ Plastic fiber optic cable (POF*/PCF*)
▪ Glass fiber optic cable according to IEC 60793, 60794
IP 20 plug-in connector
▪ SC RJ push/ pull plug for POF, PCF, Glass M O
fiber optic cable RU
o
▪ SC push pull/ST plug for glass fiber optic cable
ou tinh
ra C
r e i
IP 65/67 plug-in connector P e
e g o
▪ Connector face compatible with IP20 version
D y
▪ Push/ pull plug with integrated SC RJ plug
* POF = Polymer Optic Fiber
* PCF = Polymer Cladded Fiber
Fiber Optic Cable
For fiber optic cables, data transmission occurs through the modulation of electromagnetic waves
in the range of visible and invisible light.
High quality plastic and glass fiber optic is used.
For Industrial Ethernet, there are different fiber optic cable types which offer tailored solutions for
the various operating and ambient conditions for the connection of network components to one
another.
The following fiber optic cables are offered for Industrial Ethernet:
• Glass fiber optic cable
MO
• PCF fiber optic cable
RU
• POF fiber optic cable
t i n ho
C ou For short distances, plastic optical fiber such
Glass fiber optic cables are used for long distances.
r e ira
as Polymer Optic Fiber (POF) or plastic-coated glass fiber optic such as Polymer Cladded Fiber
(PCF) are recommended.
o Peoptic cables vis-à-vis electrical cables are:
Some advantages of using
y eg fiber
• GalvanicD isolation of devices and segments
• No potential equalization necessary
• No shield currents
• No influencing of the transmission paths through external electromagnetic interferences
• No interfering transmissions along the transmission route
• …

ActiveActive
4.9. Industrial Ethernet
Industrial Components
Ethernet Components
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN
Active / Network Components
Industrial Ethernet Components Page 14 Siemens AG © 2016
Active Industrial Ethernet components are network components which have an active influence
on the signal or the telegram. This includes stand-alone devices such as switches, media
converters, link modules or even communication modules (CM) and communication processors
(CP).
Siemens Tools such as the TIA Selection Tool or the SIMATIC NET Selection Tool provide
support for the selection of suitable components for the specific application.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

Industrial
4.10. Wireless
Industrial LAN Components
Wireless LAN Components
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN /WLAN
Industrial Network Components
Components Page 15 Siemens AG © 2016
The SCALANCE W products can be subjected to fluctuations in the extended temperature range
without coming into contact with dust and water. Rugged enclosures and mechanical protection
against jolts and vibration enable the use in a harsh industrial environment. Even the accessories
such as antennas, power supplies and cabling are part of this concept and are manufactured to
industry standards. Energy and data are transmitted with Power-over-Ethernet via a cable and so
save investment and maintenance costs. The removable media C-PLUG (Configuration Plug)
stores project engineering and configuration data which enables a quick device exchange and
without specially trained personnel. This minimizes downtimes and saves training costs.
O
To protect against unauthorized access, the products provide modern standard mechanisms for
M
existing safety concepts without a problem. o RU
user identification (Authentication) and data encryption and can simultaneously be integrated in
u t inh
With the international IEEE 802.11n standard, wireless communication via IWLAN is even more
C o
robust. The greatest advantage results from the use of multipath scattering (Multiple Input,
a
P e reir
Multiple Output (MIMO)). This allows the devices to use several antennas in parallel. In this way,
a higher data rate is achieved and at the same time the susceptibility to interference in
g o
environments with many reflexions is reduced.
e
Access Points Dy
The access points are the central base stations for infrastructure networks. They coordinate and
control the wireless communication within a wireless (radio) cell. If two or more access points are
located in one wireless network, that is, the same wireless network name (SSID), the client
module can switch between the wireless cells which are formed by the individual access points
(roaming). The wireless connection is thereby maintained. This method is used when the required
wireless coverage is greater than the range of an access point. All access points can also be
configured in such a way that their functionality is limited to that of a client.

Client Modules
The client modules of the SCALANCE W product line are used as a gateway from wireless to
wired network segments (bridge function). Usually they communicate with an access point
(infrastructure network).
iFeatures
With the help of a Key Plug, additional functionalities can be activated for special SCALANCE
switches. For the 780s and 740s series, these additional functionalities include the so-called
iFeatures such as iREF, iPCF, etc.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

4.11.Communication Processors
Communication (CPs)(CPs)
Processors for IEfor IE
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Communication Processors (CPs) / Communication Modules (CMs)
Communication processors and communication modules expand the controller by a further
interface. The maximum number of CPs and CMs which can be connected to a controller
depends on their performance class.
A CM or CP allows further networks to be connected to the controller. These, however, do not
have to be connected to the networks of the internal interface of the PLC, but rather a stand-
alone operation of these networks can take place.
CPs and CMs furthermore relieve the internal PLC processor of communication tasks and add
further possible connections. Unlike CMs, CPs additionally expand the functionalities of the
controller (Security, ISO, FTP,…).
MO
Both components are connected to the controller via the internal backplane bus.
U
o
The exact properties of the respective CMs and CPs can R obtained from their device manuals
be
in h
which can be found on the Service and Support tpages.
C o u
i r a
P ere
y ego
D

4.12.TIATIA
Selection ToolTool
Selection
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
TIA Selection Tool
Both the active as well as the passive components must withstand harsher ambient conditions in
the industrial environment than in the office world. This is noticeable in many ways!
With the TIA Selection Tool you can select, configure and order devices for Totally Integrated
Automation. It is the successor to the SIMATIC Selection Tool and combines already familiar
configurators for automation in one tool. You can start it directly in the Siemens Industry Mall or
download it as a file.
The TIA Selection Tool provides you with wizards for selecting the desired devices and networks.
As well, there are configurators for selecting modules and accessories as well as for checking the
O
correct functioning. The TIA Selection Tool generates a complete order list from your product
M
shopping cart. o RU
selection or product configuration. You can export this directly into the Industry Mall or the CA 01
u t inh
With the TIA Selection Tool, you can select and configure the SIMATIC S7, SIMATIC ET 200,
C o
SIMATIC HMI Panels, SIMATIC IPC, SIMATIC HMI Software and Industrial Communication
a
Pe reir
components. Beyond that, you can create PROFIBUS and PROFINET networks, configure their
topology as well as select associated cables and connectors.
o
g TIA Selection Tool can be found via the following link:
Further information onethe
D y
http://w3.siemens.com/mcms/topics/de/simatic/tia-selection-tool/Seiten/tab.aspx
The TIA Selection Tool can be started directly online via the following link:
https://www.siemens.com/tia-selection-tool/start
SIMATIC NET Selection Tool

The SIMATIC NET Selection Tool is a slimmed down version of the TIA Selection Tool which only
deals with industrial communication and only has Industrial Ethernet components for selection.
More information on the SIMATIC NET Selection Tool can be found on the Service and Support
pages under the following Entry ID: 39134641
The SIMATIC NET Selection Tool can also be started directly online via the following link:
http://www.siemens.de/snst

Task Description:Reading-out the Firmware
Reading-out of the Devices
the Firmware of&the Devices &
Configuration of the System
Configuration of theinSystem
the TIA Selection Tool Selection Tool
in the TIA
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
Since all network components have an IP address which is located in the same subnet as our
Field-PG, the firmware of all devices can be read out. This is required afterwards in order to
configure the system in the TIA Selection Tool.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 3: Reading-out the
Firmware
4.13.1. of3:the
Exercise Devices (TIA
Reading-out Portal) of the Devices (TIA Portal)
the Firmware
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
With the help of the TIA Portal, you are to read-out the firmware of all accessible devices. This is
best done via the ‘Online access’ and from there via the accessible devices.
What to Do
1. Display all connected devices via the function “Update accessible devices” in the ‘Online
access’ tab.
2. The firmware of the network components can be obtained via Online & diagnostics and there
in the menu item “General” which is located under Diagnostics (see picture).
MO
3. Determine the firmware of the S7-1513-1PN:__________________________
U
o R
4. Determine the firmware of the ET200SP:_____________________________
tin h
C o u
5. Determine the firmware of the SCALANCEX208:_______________________
r a
6. Determine the firmware of the S7-1510SP-1PN:________________________
i
P ere
egoneed a project!
Note
D y
For this task, you still don’t
The firmware of a module can only be read out if the module has an IP address and this IP
address has the same network address as the device through which the firmware is to be read
out with the help of the TIA Portal.
Example:
S7-1513-1PN: IP address: 192.168.222.1 // Subnet mask: 255.255.255.0
Network address: 192.168.222.0
Field PG: IP address: 192.168.222.250 // Subnet mask: 255.255.255.0
Reading out the firmware via the TIA Portal would be possible in this case!

Exercise 4: Configuration of the System
in the
4.13.2. TIA Selection
Exercise Tool of the System in the TIA Selection Tool
4: Configuration
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to create the hardware configuration of your system in the TIA Selection Tool. You are
then to network the devices in the Network view and assign the ET200SP to the correct IO-
Controller.
What to Do
1. Open the TIA Selection Tool.
2. Create the setpoint configuration of the system so that it matches your actual configuration.
3. Supplement your programming device.
M O
RU
4. Network the devices according to your wiring.
o
inh
5. Assign the ET200SP IO-Device to the correct IO-Controller.
6. Save the TIA Selection Tool project. o u t
a C
7. Export your configuration.
P e reir
e g o
Dy

WennAdditional
4.14. Sie noch mehr wissen wollen
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Netzkomponenten Seite 21 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Versions
4.14.1. of of
Versions IEIE
FCFCRJ45
RJ45Plugs
Plugs
IE FC RJ45 Plug 4x2 IE FC RJ45 Plug 4x2
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
IE FC RJ45 Plug 180° IE FC RJ45 Plug 145° IE FC RJ45 Plug 90°

IE FC RJ45 Plugs
plugs conform to the EN 50173 (RJ45) and ISO/ IEC 11801 standards. They are available in two
pin versions. Once as the IE FC RJ45 plug in 2x2 version for Fast Ethernet cables with 4 wires
and then the IE FC RJ45 plug in 4x2 version for Gigabit Ethernet cables with 8 wires.
IE FC RJ45 Plug 2x2

The IE FC RJ45 plug 2x2 is, for its part, available in three versions. These differ in the cable
outlet of the plug:
• M O
RU
With 180° (straight) cable outlet:
o
Due to the design, the IE FC RJ45 Plug 180 can be used both on devices with single
u t inh
sockets as well as on devices with multiple sockets (blocks). The plug is suitable for
o
connecting IE FC TP cables to SIMATIC NET modules and SCALANCE devices.
C
a
•
reir
With 90° (angled) cable outlet:
Pe
The plug is suitable for connecting IE FC TP cables to ET200 or PN/PN couplers.
• With 145° (angled)
o
eg cable outlet:
The plugDis y
suitable for connecting IE FC TP cables to SIMOTION and SINAMICS
modules.
IE FC RJ45 Plug 4x2

The IE FC RJ45 plug 4x2 is only available in one version:
• With 180° (straight) cable outlet:
Through the plug, point-to-point connections (10 / 100 / 1000 Mbit/s) for Industrial
Ethernet can be implemented between two terminals/ network components of up to 90 m
without patch technology.

IE FC
4.14.2. Modular
Industrial OutletFC
Ethernet RJ45
Modular Outlet RJ45
IE FC Modular Outlet RJ45
Outlet open and

wired
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Insert 2x Fast Ethernet Insert 1x Gigabit Ethernet Outlet Power Insert

Industrial Ethernet FastConnect Modular Outlet RJ45
The Industrial Ethernet FC Modular Outlet RJ45 serves the transition from the rugged Industrial
Ethernet FC TP cables used in the industrial environment to pre-assembled TP Cord cables by
means of an RJ45 socket. In combination with FC TP cables and pre-assembled TP Cords, the
Industrial Ethernet FC Modular Outlet RJ45 ensures time-saving installations. A color coding
prevents errors during wire insertion. The Industrial Ethernet FC Modular Outlet RJ45
corresponds to Category 5 of the ISO/IEC 11801 and EN 50173 international cabling standards.
Modular Outlet Basic Module

The Industrial Ethernet FC RJ45 Modular Outlet basic module is available with three
interchangeable inserts: M O
• Insert 2 FE: o RU
t inh
Basic module with interchangeable insert for two Fast Ethernet connections for
u
o
connecting two 10/100 Mbit/s terminals/network components.
C
a
• Insert 1 GE:
P e reir
Basic module with interchangeable insert for one Gigabit Ethernet connection for
g o
connecting one 10/100/1000 Mbit/s terminal/network component.
e
• Dy
Outlet Power Insert:
Basic module with interchangeable insert for one power supply and one 10/100 Mbit/s
terminal/network component.

Contents 5
5. PROFINET Configuration ....................................................................................... 5-2
5.1. Manual Commissioning of a PN IO-System ......................................................................... 5-3
M O
5.2. U
Manual Commissioning Sequence ....................................................................................... 5-5
R
o
tinh
5.3. Name Assignment using the TIA Portal with Project ............................................................ 5-6
5.3.1.
5.3.2. C ou
Definition of the PROFINET Device Name in the Project ..................................................... 5-6
Assigning the PROFINET Device Name via the Project ...................................................... 5-7
5.3.3.
ei ra
Writing the PROFINET Device Name onto the MMC ........................................................... 5-8
r
e
Name Assignment usingPthe TIA Portal without Project ....................................................... 5-9
ego
5.4.
5.5. y
Download the PROFINET-IO
D Configuration to the IO-Controller ....................................... 5-11
5.6. Device Exchange without Programming Device ................................................................. 5-12
5.7. Task Description: Commissioning the S7-1500 Case ........................................................ 5-13
5.7.1. Exercise 1: Creating a Project ............................................................................................ 5-14
5.7.2. Exercise 2: Configuring and Parameterizing the S7-1500 .................................................. 5-15
5.7.3. Exercise 3: Creating a TP700 Comfort ............................................................................... 5-16
5.7.4. Exercise 4: Configuring and Parameterizing the ET200SP ................................................ 5-17
5.7.5. Exercise 5: Networking & Grouping the Devices ................................................................ 5-18
5.7.6. Exercise 6: Inserting a Tag Table from the Library ............................................................. 5-19
5.8.1. Device Number of an IO-Device ......................................................................................... 5-22
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – PROFINET Configuration

PROFINET Configuration
5. Objectives
... be able to configure PROFINET-IO networks in the TIA Portal
... be able to assign parameters to an IO-Device
...
M O
understand the storing of PROFINET device names
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET Configuration Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

5.1. Manual Commissioning

Manual of a PN
Commissioning of aIO-System
PN IO-System
Assign
Namen zuweisen über
name via
C-Plugoder
TIA Portal,C-Plug
TIA-Portal, MMC
or MMC
M O
R U
o
ou tinh
ra C
e i
o Per
Load configuration
eg
onto IO-Controller
Dy
Page 3 PROFINET Configuration
Manual Name Assignment for a PROFINET IO-System
So that the individual devices are accessible during system startup of the IO-Controller, they are
given device names. This is done during the manual commissioning of the PN IO-System by the
IO-Supervisor.
If the commissioning is done manually, it must however be kept in mind that the device names
which are downloaded into the IO-Controller via the hardware configuration must match those
which the IO-Supervisor assigns to the individual IO-Devices. That is, the device names which
were assigned offline for the individual IO-Devices must match the online device names. This is
comparable with the setting of the PROFIBUS address. If errors are made here, the IO-Device
cannot be reached by the IO-Controller.
M O
RU
The PROFINET name of a device must comply with the PROFINET name convention!
o
u t inh
PROFINET Name Convention C o
i r a
P ereconverted
The following lists the rules for the name. The hardware configuration checks whether
go of the module, then the name of the module must satisfy these
the name conventions are complied with and, if necessary, corrects them. If the converted name
is not to differ from theename
rules: D y
• The name is limited to a total of 128 characters (letters "a" to "z", numbers "0" to "9",
hyphen or dot)
• The name consists of one or more labels, which are to be separated by a dot ".".
• A label within the device name, that is, a character string between two dots, may be a
maximum of 63 characters.
• No special characters such as vowel mutations, brackets, underscore, forward slash,
blank etc. The hyphen is the only special character allowed.
• No capital letters may be used in the device name.
• The device name must not begin with the characters "-" or "." and it must not end with
these characters.

• The device name must not begin with numbers.

• The device name must not begin with the character string "port-xyz-" (x, y, z = 0...9).
• The device name must not have the format n.n.n.n (n = 0...999)
Device names are assigned to the PROFINET IO devices in the commissioning phase.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

5.2. Manual Commissioning

Manual Sequence
Commissioning Sequence
Delivered condition / Factory settings

Device only has a MAC address
IO-Supervisor writes the device name in the IO-

DEVICE or on the MMC of the IO-Device
M O
R U
o
IO-Supervisor downloads the PROFINET-IO
tinh
configuration into the IO-Controller
ou
ra C
e r ei
o P IO-Controller recognizes the
y egIO-Device via the name and writes the IP address
D in this IO-Device during system startup

Manual Commissioning Sequence of a PROFINET IO-System
The manual commissioning of a PROFINET IO-System can be divided into the following steps:
• Delivered condition / Factory settings:
The device is commissioned for the first time or it is reset to its factory settings. The
device has no IP address and no device name. It can only be addressed via its MAC
address.
• Device name assignment:
If the commissioning is done manually, the IO-Device can be assigned a device name in
two ways. The device name can always be written in the IO-Device by the IO-Supervisor.
O
For this, various software packages can be used (TIA Portal, PST-Tool, etc…). If the IO-
M
RU
Device supports an MMC, the device name can also be written directly onto the card
t i n ho
using the PG or using a PC with a connected USB prommer.
•
After all devices have been assignedC oaudevice into
Downloading the PROFINET-IO configuration the IO-Controller:
name either directly via the relevant tools
or using the MMC card, the
r e ra configuration is downloaded into the IO-Controller.
iPN-IO
• o Pe
IP addresses assignment:
y
After the PN-IO egconfiguration is downloaded into the IO-Controller, the controller
searchesD for the PROFINET device names in the network during startup. As soon as one
of these names has been found, the IO-Controller assigns the IP address stored in the
configuration for this name. The IO-Controller and not the IO-Supervisor assigns the IP
address to the IO-Device.
Note
If the IO-Supervisor writes the device name directly in the IO-Device and there is an MMC or a C-
Plug in the device at the time, the device name is stored on this medium and so permits a device
exchange without programming device.

5.3. Name
Name Assignment using the TIA Portal with Project
Assignment using the TIA Portal with Project:
5.3.1.Definition of of
Definition the PROFINET
the PROFINET Device Namein the Project
Device Name
Possible in Network view

and Topology view
M O
R U
o
ou tinh
ra C
e i
o Per
yeg
PROFINET device name is standard-compliant PROFINET device name is not standard-compliant

Name Assignment using the TIA Portal with Project
The TIA Portal makes it possible to assign names to IO-Devices with or without a project.
Definition of the PROFINET Device Name in the Project

The user can define the PROFINET device name with the help of a project either in the Device
view or in the Topology view in the Properties of the IO-Device.
The PROFINET device name of a PROFINET device is either automatically generated or
assigned manually by the user. If the option: “Generate PROFINET device name automatically” is
O
M
activated, the PROFINET device name is derived from the general name of the device. If this is
RU
not the case, a name can be assigned here which differs from the general name.
o
t inh
Activating or deactivating this function has no influence on the control and the compliance with
u
C o
the PROFINET name convention, however. This is always executed by the TIA Portal and the
a
reir
name assigned by the user is automatically corrected by the system in case of an error.
e
Whether the name complies with the convention or not can be checked in the field: “Converted
P
e g o
name”. If the converted name complies with the PROFINET device name, the PROFINET device
Dy
name is defined according to the PROFINET name convention. This is a benefit for the user
because he can immediately carry out the control of the name convention while defining the
device name!
Note
The PROFINET device name must not have any capital letters. These are automatically
converted into lowercase letters by the TIA Portal. Attention should be paid to this when assigning
the device name.

Name Assignment using the TIA Portal with Project:
5.3.2.Assigning the
Assigning Device
the Name
PROFINET Device Name via the Project
Possible in Network view

and Topology view
Name cannot be changed
M O
R U
o
ou tinh
ra C Found IO-Device of the
i
ere
same type
o P
Dyeg Writes the name directly in
the IO-Device

Assigning the PROFINET Device Name via the Project
The assignment of the name defined in the hardware configuration of the IO-Controller for the
respective IO-Device can either be done in the Device view or in the Topology view. A right-click
on the IO-Device calls the dialog “Assign device name”.
In the dialog that now opens, the name stored in the hardware configuration can be assigned to
the selected IO-Device. This PROFINET device name can no longer be changed in this step! The
advantage of this method is that the PROFINET device name which the IO-Controller searches
for during its startup always matches the device name which is loaded on the IO-Device!
Note
O
A right-click on the PROFINET IO-System also calls the dialog “Assign device name”. The
M
RU
difference here to the execution on the IO-Device is that now the PROFINET device name which
o
inh
is to be assigned can be selected via a selection window. That is, all available PROFINET-IO
o u t
Device names are displayed for selection which now can be assigned successively.
C
For the assignment of several IO-Devices, this is in particular a considerable reduction in
a
reir
workload!
P e
If an MMC or a C-Plug is o
egdevice
inserted in the IO-Device while the PROFINET device name is being
D y
written to the device, the name is written onto the MMC / C-Plug and is lost on the device
when the MMC / C-Plug is pulled!

Name Assignment using the TIA Portal with Project:
5.3.3.Writing thethe
Writing Device NameDevice
PROFINET onto Name
the MMC
onto the MMC
MMC must be Possible in Network

inserted in the PG/PC view and Topology view
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Writing the PROFINET Device Name onto the MMC
If a Micro Memory Card is inserted in the PG or the USB prommer, the PROFINET device name
can also be written directly onto the MMC and then inserted into the IO-Device. The IO-Device
then adopts the PROFINET device name during its startup.
This function can be executed both in the Device view and the Topology view by right-clicking on
the IO-Device.
Note
The function “Write IO-Device name to Micro Memory Card” is only displayed if the IO-Device
supports this function!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Name Assignment using the TIA Portal without Project:

Nameand
5.4. Defining Assignment the Device
Assigningusing the TIA Name
Portal without Project
Manually assign device name
M O
R U
h o
Select t
u indesired IO-Device
the
o
ra C
via the interface
ei
o Per
eg
Dy
Name Assignment using the TIA Portal without Project
With the help of the TIA Portal, every IO-Device can be assigned a PROFINET device name. For
this, no additional software and also no project is required.
The user can search for all accessible devices using the ‘Online access’. Then, the IO-Device to
be initialized is selected and the function: “Online & diagnostics” is called. Here, in the “Functions”
tab and the “Assign name” menu item, the IO-Device can be assigned a PROFINET device
name. However, it must be noted here that the user must enter the name himself. If this name
later does not match the name that is loaded into the IO-Controller, the IO-Controller will not be
able to find this IO-Device.
M O
Note o RU
u t inh
The IO-Device does not require an IP address to execute the “Assign name” function! However, it
C o
must be noted that to identify the IO-Device with the help of the TIA Portal, the following
a
requirements must be fulfilled:
• P e reir
e g o
The IO-Device must be assigned an IP address.
•
Dy
The IP address of the IO-Device must be located in the same subnet as the PG or the
PC on which the TIA Portal is installed.

If these requirements are fulfilled, the IO-Device is presented in the “General” tab as follows:
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
If these are not fulfilled, this presentation is as shown:
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy
With the help of the TIA Portal, a temporary IP address can be assigned to every IO-Device!

Downloading the PROFINET-IO

5.5. Configuration
Download theto the IO-ControllerConfiguration to the IO-Controller
PROFINET-IO
PROFINET-IO configuration is
downloaded via the HW-Config
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Maximum configuration time for
each IO-Device

Downloading the PROFINET-IO Configuration
After all IO-Devices have been assigned a PROFINET device name, the PROFINET-IO
configuration must finally still be downloaded to the IO-Controller. This is executed by
downloading the hardware configuration into the IO-Controller. In the HW-Config, all device
names of the IO-Devices are stored which are assigned to this IO-Controller. Then during its
startup phase, the IO-Controller searches for the PROFINET device names. It assigns the
PROFINET-IO configuration which is stored in the hardware configuration to the corresponding
IO-Device names.
Configuration Time for an IO-Device
M O
In the hardware configuration of the IO-Controller, you can define in the menu item: “Startup” the
RU
maximum time the IO-Controller is to try to configure (parameterize) the IO-Device. The default
o
(parameterize) each IO-Device. u t inh
setting for this option is 60 seconds. The IO-Controller will try for 60 seconds to configure
Co
a
Note
P ereir
If, after downloading the hardware configuration using the TIA Portal, the option: “Start all” is
e g o
selected, the IO-Device cannot be configured by the IO-Controller. The TIA Portal cannot be
Dy
addressed for the set configuration time!

5.6. Device Exchange

Device without
Exchange Programming
without Device
Programming Device
Removable media MMC Removable media C-Plug
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Device Exchange without Programming Unit
As previously mentioned, there are PROFINET-IO Devices which support an MMC or a C-Plug.
These make the function: “Device replacement without programming device” possible in the
PROFINET-IO System.
Since, for an IO-Device with an MMC or a C-Plug, the PROFINET device name is not written in
the internal memory of this IO-Device, the MMC or the C-Plug can simply be removed from the
defective device and inserted in the exchange IO-Device when a device fails. The new IO-Device
is automatically initialized with the PROFINET device name of the defective device and the
PROFINET-IO System continues running without an error.
Premise for this of course is that the new IO-Device has the same configuration as the defective
IO-Device. M O
RU
Note
t i n ho
ouC-Plug, must be purchased separately!
The removable media, that is, the MMC or the
C
r e ira
o Pe
y eg
D

Task Description:
Creating
5.7. Taska Project + Commissioning
Description: the 1500
Commissioning Case Case
the S7-1500
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task Description
You are to commission the 1500 case. You are to create the hardware configuration of the
different devices and parameterize the individual modules. Then you are to network them and
load the individual devices with the information from the project.
MO
o RU
u t inh
C o
a
Pe reir
e g o
Dy

Exercise
5.7.1. 1: Creating
Exercise a Project
1: Creating a Project
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task
You are to create a new TIA Portal project in which you will solve most of the following tasks. You
can decide what name you wish to give your project and also where you want to store it!
What to Do
1. Open the TIA Portal.
2. In either the Project view or in the Portal view, create a new project. The name assignment is
you choice. You can define the storage location anywhere on D-drive.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 2:
5.7.2.Configuring
Exercise 2:and Parameterizing
Configuring the S7-1500
and Parameterizing the S7-1500
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Task
You are to configure and parameterize the S7-1500. The digital input and output modules are to
be given the addresses from 0-3 and the analog input module is to be given the range from 44-
59.
The S7-1500 gets the IP address 192.168.222.13 with the subnet mask 255.255.255.0. The
device name is: “1513-io-controller”.
What to Do
1. Add an unspecified S7-1500 to your project.
2. Detect the configuration of the connected S7-1500.
M O
RU
3. Adjust the I/O addresses of the modules according to the picture and the task.
o
t inh
4. Assign the IP address 192.168.222.13 with the subnet mask 255.255.255.0.
u
C
5. The CPU gets the name: 1513-io-controller.o
a
6. Save your project.
P e reir
e g o
Dy

Exercise Creating
CreatingaaTP700
TP700 Comfort
Comfort
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to create a new Comfort Panel TP700 Comfort. This Panel does not have to have any
content but must simply exist in the project. The Panel gets the IP address 192.168.222.70 with
the subnet mask 255.255.255.0. The device name for the Panel is “touch-me”.
What to Do
1. Insert a new TP700 Comfort in your project.
2. Set the interface of the Panel to the IP address 192.168.222.70 with the subnet mask
255.255.255.0.
3. Name the Panel “touch-me”. M O
4. Save your project. o RU
5. Download the Panel with your changes. u t inh
C o
a
P e reir
e g o
Dy

Exercise 4:
5.7.4.Configuring
Exercise 4:and Parameterizing
Configuring the ET200SP
and Parameterizing the ET200SP
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Task
In your project, you are to generate an ET200SP and configure as well as parameterize it. The
digital inputs and outputs are to be in the address range of 4-5, the analog I/Os get the range 6-
13. The ET200SP is assigned the IP address 192.168.222.200 with the subnet mask
255.255.255.0. The PROFINET device name for the IO-Device is “et200sp-io-device”. After the
configuration and parameterization, assign this name to the Online-Device. The initial generation
of the ET 200SP occurs via the Hardware detection. Subsequently, the configuration and
parameterization still has to be completed.
What to Do
M O
1. Generate a new ET 200SP. For this, use the menu command: "Hardware detection / IO
RU
devices" in the "Online" menu in the menu bar of TIA Portal.
o
u t inh
2. If necessary, carry out changes in the parameterization of the ET 200SP that still have to be
made according to the task.
C o
a
reir
3. Assign the IP address 192.168.222.200 with the subnet mask 255.255.255.0 for the IO-
Device.
P e
o
eg Configuration rename the ET 200SP "et200sp-io-device".
4. Offline in the Hardware
y
D of the “AI 4xU/I 2-wire ST” module and adjust the potential group to
5. Go into the Properties
“Enable new potential group (light BaseUnit)”.
7. Assign the Online-Device the device name just configured.
Note
The modules can only be parameterized after the devices have been networked. Therefore, work
through the following exercise and then return to this exercise!

Exercise Networking
Networking&&grouping the Devices
Grouping the Devices
Subnet mask: 255.255.255.0

Name: touch-me
IP: 192.168.222.70
M OName: 1513-io-controller
R U IP: 192.168.222.13
o
tinh Name: et200sp-io-device
a Cou IP: 192.168.222.200
e r eir
o P
eg
Dy
Task
You are to network all devices in the Network view and check the settings such as IP address
and device name. With the networking, a PROFINET IO-System between the ET200SP and the
S7-1500 is to result.
Finally, you are still to group the devices in the TIA Portal Project tree. For this, you are to create
a group with the name: "1513Case".
What to Do
1. Switch to the “Network view” in your project.
2. Network the individual devices one below the other.
M O
RU
3. Check the IO-System between S7-1500 and ET200SP. The ET200SP must be assigned to
the S7-1500 as an IO-Device.
t i n ho
ouET200SP according to the task from the previous
4. Then parameterize the I/O addresses of the
C
exercise.
r e i ra
Pe individual modules as well as their device names.
5. Check the IP addresses of the
o
g option: “Generate PROFINET device name automatically” is activated
6. Also check whetherethe
y
D interface:
for each PROFINET
7. In your Project tree, create a new group with the name "1513Case". Then, assign the S7-
1500, the ET 200SP as well as the TP700 to this group.

Exercise 6:
5.7.6.Inserting a Tag
Exercise Table from
6: Inserting a Tagthe Library
Table from the Library
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to insert the prefabricated tag table from the “IK-TIAPN” library into your project. The
library can either be opened immediately or it must first still be retrieved. In this case, retrieve the
library in the same folder as the archive file is located.
You will find the library under the following path on your computer:
C:\Archives\TIA_Portal\IK-TIAPN
What to Do
1. Open or retrieve (unzip) the library.
U MO
2. Open the Chapter5 (folder) of the IK-TIAPN library and,R
“1513CaseVariables” into your project under “PLCn h o using drag & drop, drag the
tags”.
o u ti
r a C
4. Load the controller. re i
P e
y egohave
5. All modules should now
check your configuration
the status OK, that is, show a green light. If this is not the case,
of the modules.
D
Note
Since you are working with a fail-safe CPU here, you must set the “Full access incl. fail-safe
(no protection)”.

M O
R U
o
ou tinh
ra C
e i
Per
Note
y ego
D
If the offline configured access node of the PLC is not located in the subnet of the physical
device, TIA Portal will automatically query whether you are assigning an IP address in the
address range 192.168.x.241 to 192.168.x.250 of the network card.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

WennAdditional
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET Projektierung Seite 18 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

Device
5.8.1. Number
Device of an
Number of IO-Device
an IO-Device
Is wird
required
bei einigen
for some
Anweisungen
instructions
benötigt
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Device Number of an IO-Device
The device number of an IO-Device is automatically assigned by the TIA Portal when an IO-
Device is created. The device number must be unique in the PROFINET I/O-System, but it can
still be manually adjusted later on. The device number of the IO-Controller is always ‘0’ and
cannot be manually changed.
Various instructions require the device number and not the device name or the geographic
address of a module in order to be able to address it.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Contents 6
6. Topology Editor ...................................................................................................... 6-2
6.1. Automatic Commissioning of a PN IO-System ..................................................................... 6-3
M O
6.2. U
Automatic Commissioning Sequence ................................................................................... 6-4
R
o
tinh
6.3. The LLDP (Link Layer Discovery Protocol) ........................................................................... 6-5
6.4. ou
Basics of LLDP...................................................................................................................... 6-6
C
6.5.
e
Topology Detection with the Help
r iraof the LLDP ..................................................................... 6-7
Structure of a PROFINET e
6.5.1.
o P IO System ................................................................................... 6-7
6.5.2.
6.5.3. y
Name Information eisgDistributed via LLDP
Downloading the Configuration to the IO-Controller ............................................................. 6-8
............................................................................ 6-9
6.5.4. D
IO-Controller assigns further Device Names ...................................................................... 6-10
6.6. Adjusting the Topology View to the Network View ............................................................. 6-11
6.7. Creating the Setpoint Topology .......................................................................................... 6-12
6.8. Downloading the Setpoint Topology into the IO-Controller ................................................ 6-14
6.9. Task Description: Creating the Setpoint Topology ............................................................. 6-15
6.9.1. Exercise 1: Creating the Setpoint Topology of the 1500 Case ........................................... 6-16
6.10. Detecting the Actual Topology of a PN IO-System ............................................................. 6-17
6.11. Offline/Online Comparison of the Topology ........................................................................ 6-18
6.12. Device Replacement without Exchangeable Medium......................................................... 6-20
6.13. Overwriting the PROFINET Device Name .......................................................................... 6-21
6.14. Task Description: Detecting the Remaining Topology of the System and Testing the
M O
RU
Automatic Commissioning .................................................................................................. 6-22
6.14.1.
o
Exercise 2: Configuration & Parameterization of the Missing Devices (Scalance + ET 200SP
u t inh
PLC) .................................................................................................................................... 6-23
6.14.2. o
Exercise 3: Detecting the Actual Topology ......................................................................... 6-25
C
6.14.3. a
Exercise 4: Activating a Device Replacement without Exchangeable Medium .................. 6-26
6.14.4. reir
Exercise 5: Permit Overwriting the Device Names ............................................................. 6-28
P e
6.15.
g o
Additional Information ......................................................................................................... 6-29
e
6.15.1.
Dy
Device Replacement without Topological Configuration .................................................... 6-30
IK-TIAPN – Topology Editor

Topology Editor
6. Objectives
... understand the automatic commissioning of a PROFINET I/O-

System based on a Setpoint (Preset) Topology and be able to apply
it
...
M O
be familiar with the device exchange without removable media
R U
... o
be familiar with the function “Overwriting the PROFINET device
name”
ou tinh
...
ra C
be able to carry out a comparison of the online to the offline
e r ei
topology
...o
Punderstand for what the LLDP is required
y e g
D
SITRAIN
IK-TIAPN / Topology Editor Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

6.1. Automatic Commissioning

Automatic of a PN
Commissioning of aIO-System
PN IO-System
ID: 36752540
Create the topology of

the PN IO-System
M O
R U
IO-Controller assigns
names to IO-Devices
o
ou tinh
ra C
e i
o Per
Download topology
eg
to the IO-Controller
Dy
Page 3 Topology Editor
Automatic Commissioning of a PROFINET IO-System
The function “Automatic commissioning of a PROFINET IO-System” is based on the LLDP (Link
Layer Discovery Protocol).
This function is beneficial especially for the commissioning of multiple machines of the same type with
the same configuration and setpoint (preset) topology: The expenditure of time and the possible
causes of errors during commissioning are minimized.
With this function, the IP address and device name assignment of the PROFINET IO-Devices occurs
automatically through the respective PROFINET IO-Controller, without a removable media (e.g. Micro
Memory Card) with stored device name or a programming device (PG) being necessary.
O
So that the automatic commissioning of a PROFINET IO System can be executed by the IO-
M
Controller, the following requirements must be fulfilled:
o RU
•
u
replacement without exchangeable medium/PG”. t inh
The IO-Controller and the IO-Devices must support the PROFINET functionality “…device
C o
• a
reir
The devices must be reset to the delivered condition (factory settings) (normally!).
• P e
The topology of the PROFINET IO System with the IO-Devices concerned must be
configured.
e g o
• Dy
The configured setpoint topology must match the actual topology.
Note
The topology of the PROFINET IO System is configured offline. With this setpoint topology, the
PROFINET IO-Controller is made familiar with the ‘neighborhood’ relationships of all PROFINET IO-
Devices found in the PROFINET IO- System.
On the Service & Support pages, you will find further information on the function “Device exchange
without exchangeable medium” under the Entry ID number: 36752540 and you will be able to check
which devices support this functionality.

6.2. Automatic Commissioning

Automatic Sequence
Commissioning Sequence
IO-Supervisor creates the topology in the software / the

TIA Portal
IO-Supervisor downloads the PN-IO configuration

including the topology to the IO-Controller
M O
R U
o
During startup, the IO-Controller writes the
ou tinh
PROFINET device names in the IO-Devices on the basis of
the loaded topology
ra C
e i
o Per
yeg
Through the name, the IO-Controller detects the
IO-Device and, during system startup, writes the IP
D address in this IO-Device

Automatic Commissioning Sequence
The automatic commissioning of a PROFINET IO system can be divided into individual steps:
• Creation of the setpoint topology:
The setpoint topology must be created by the IO-Supervisor. So that the automatic
commissioning of the PROFINET IO system can occur later on without errors, it must
match the actual topology.
• Loading the IO-Controller:
After the setpoint topology is created, it must be downloaded into the IO-Controller. With
the help of the setpoint topology, the controller can carry out a comparison to the actual
topology and execute the automatic commissioning.
M O
• IO-Controller writes the PROFINET device namesR U
in the IO-Devices:
h o
device names in the IO-Devices with the u in of the setpoint topology.
During startup, after the configuration is loaded,
thelp the IO-Controller then writes the defined
o
C to the IO-Devices:
•
i r a
IO-Controller assigns the IP addresses
e the assignment of the IP addresses for the individual IO-
erstep.
After the names are assigned,
P
ego
Devices is done as a last
D y

The LLDP
6.3. (Link Layer
The LLDP Discovery
(Link Layer Protocol)
Discovery Protocol)
Layers Link Layer Discovery Protocol:

▪ Manufacturer-independent Layer 2 protocol
7 Application ▪ Enables neighboring devices to exchange information with
one another
6 Presentation ▪ LLDP is a “one-way protocol”! Sending and receiving
takes place independent of one another
5 Session
4 Transport M O
R U
o
3 Network
ou tinh
ra C
2 Data Link e i
Per
1 Physicalego
Dy
SITRAIN
Link Layer Discovery Protocol
The LLDP (Link Layer Discovery Protocol) is a manufacturer-independent Layer 2 protocol. This
protocol is defined according to the IEEE-802.1AB standard and enables neighboring devices to
exchange information with one another.
In a PROFINET IO system, all devices are connected with each other via their Ethernet ports and
through them enter into a ‘neighborhood’ relationship. That is, through these ports, each device
cyclically sends LLDP packets with its own information to its neighbors and receives their
information.
Note
M O
U
R ofto information
The LLDP is a “one-way protocol”. The sending and the receiving takes place
o
independent of one another. A device which sends itshinformation
u tinfrom its neighboring components.
does not expect an answer or a receipt confirmation
o
the neighboring components
r a C
i
P ere
y ego
D

6.4. Basics of LLDP

Basics of LLDP
TIA-Portal
O
Assigns name
M
Assigns name
RU
o
I am “s7-1500”
ou tinh
P1
ra C P1 P5
i
ere
I am “x208” P2 P6
eg oP P3 P7
Dy
PartnerID.PortID
s7-1500
Port1 PartnerMAC.PartnerPort
x208.P1 P4 P8
x208
PartnerID.PortID
Port1 s7-1500.P1
PartnerMAC.PartnerPort
Basics of the Link Layer Discovery Protocol
LLDP packets are sent to the target address 01:80:2C:00:00:0E with the Ethernet type ID
0x88CC. Packets which are sent to this address only reach the port of the direct neighboring
device and are not forwarded. The information received in this way is stored by the neighboring
component in the neighbor table (LLDP MIB (Management Information Base)).
Each connection point in the topology is identified by an alias. The alias consists of the device
identifier (MAC address or device name) and the port identifier (port number). Through the MAC
address, the alias is unique in the network. In this way, the Network Management Station (e.g.
TIA Portal) can detect the topology uniquely.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

6.5. Topology
Topology Detection with the Help of the LLDP
Detection with the Help of the LLDP:
6.5.1.Structure of of
Structure a PROFINET
a PROFINETIO
IO System
System
LLDP-MIB
IO-Controller Neighbor table
Device Name
P1 P1 P5 P1 Port PartnerMAC.PartnerPort
P2 P6 P2
P3 P7 ---
Port1 PartnerMAC.P5
P4 P8
Port2 PartnerMAC.P1
M O
---
R U
o
tinh
P1 Port1 PartnerMAC.P1 P1
Port3 PartnerMAC.P1
Cou
Port5 PartnerMAC.P1 ---
Port1 PartnerMAC.P2
Port8 PartnerMAC.P1
eir a P1
P e r
---
eg o
Dy
Port1 PartnerMAC.P3
---
Port1 PartnerMAC.P8

Topology Detection with the Help of the LLDP
The LLDP makes it possible for the network components to be able to fill their LLDP-MIB, that is,
their neighbor tables with information. Through the sent LLDP telegrams, all devices connected in
the PROFINET get the information about which device is located at which of its ports.
Structure of a PROFINET IO System

The devices are physically linked to one another. Since the IO-Devices do not yet have a name,
M O
each IO-Device sends its neighbor its own MAC address and the port number for each
‘neighborhood’ relationship. This information is stored in the neighbor table of each IO-Device.
RU
Note
t i n ho
The part “PartnerMAC” presented in the picture
C ouwould be replaced by the actual MAC address of
r e ira
the respective partner in a real system!
The LLDP-MIBs presented inP e picture are updated in the devices approximately every 2
the
o
eg a topology error message may occur somewhat time-delayed when a
minutes. For that reason,
cable is switched.Dy

Topology Detection with the Help of the LLDP:
6.5.2.Downloading the
Downloading theConfiguration to the
Configuration to theIO-Controller
IO-Controller
IO-Controller Switch gets port IO-Controller

is loaded information assigns name
P1 P1 P5 P1 P1 P5 P1 P1 P5
P2 P6 P2 P6 P2 P6
P3 P7 P3 P7 P3 P7
P4 P8 P4 P8 P4 P8
--- --- x208

Port1 PartnerMAC.P1 Port1 s7-1500.P1
M O Port1 s7-1500.P1
Port3 PartnerMAC.P1 Port3 PartnerMAC.P1
R U Port3 PartnerMAC.P1
Port5 PartnerMAC.P1 Port5
o
PartnerMAC.P1 Port5 PartnerMAC.P1
Port8 PartnerMAC.P1
ou
Port8
tinh
PartnerMAC.P1 Port8 PartnerMAC.P1
C
r e ira
PROFINET IO-Controller topology information
et200sp-cpu
o Pe et200sp-switch et200sp-sp x208
Port1 x208.P3
eg Port1 x208.P5 Port1 et200sp-switch.P2 Port1 S7-1500.P1
et200s Dy Port2 et200sp-sp.P1 Port3
Port5
et200sp-cpu.P1
et200sp-switch.P1
Port1 x208.P8
Port8 et200s.P1

Downloading the Configuration into the IO-Controller
The first step of automatic commissioning is the downloading of the configuration and thus also
the setpoint topology into the IO-Controller. After this process is completed, the IO-Controller has
been given a PROFINET device name.
This name is now shared with all connected components (in the picture, only the SCALANCE
Switch x208) by LLDP. For their part, these components enter the new information in their
neighbor tables.
Based on the setpoint topology, the IO-Controller can now determine with this new information
which devices are connected to the CPU / the IO-Controller with which port. The IO-Controller
then assigns these devices the names stored in the configuration. In the picture, the IO-Controller
O
detects that the device which is connected to the CPU with its Port 1 is to be given the name
M
RU
x208 according to the setpoint topology. For that reason, this device is assigned this name by the
o
inh
IO-Controller.
o u t
a C
P e reir
e g o
Dy

NameName
6.5.3. Information is Distributed
Information via
is Distributed viaLLDP
LLDP
P1 P5 P1
P2 P6 P2
---
P3 P7
Port1 x208.P5
P4 P8 Port2 PartnerMAC.P1
x208
P1 Port1 s7-1500.P1
Port3 PartnerMAC.P1
Port5 PartnerMAC.P1
M O
Port8 PartnerMAC.P1 P1
RU
o
---
ou tinh
Port1 x208.P3
ra C
e i
o Per Port1
---
x208.P8
eg
Dy
SITRAIN
Name Information is Distributed via LLDP
The SCALANCE switch has now been given new information, namely its PROFINET device
name. The switch forwards this new information to its neighboring devices via the LLDP (in the
picture, the et200sp-cpu, the et200sp-switch and the et200s). For their part, the neighboring
devices then enter the new information in their neighbor tables.
MO
o RU
u t inh
C o
a
P ereir
e g o
Dy

6.5.4.IO-Controller assigns
IO-Controller assignsfurther
further Device Names
Device Names
IO-Controller
Et200sp-sp is then
P1 P1 P5 P1 initialized
P2 P6 P2
P3 P7 et200sp-switch
Port1 x208.P5
P4 P8
Port2 PartnerMAC.P1
x208
P1 Port1
Port3
s7-1500.P1
et200sp-cpu.P1
P1
M O
Port5 et200sp-switch.P1
R U ---
Port8 et200s.P1 P1
n h o Port1 et200sp-switch.P2
u t i
C o
et200sp-cpu
eir a
Port1 x208.P3
P e r
o et200s
D yeg Port1 x208.P8
The procedure of exchanging LLDP information and assigning PROFINET device names is repeated
until all devices from the setpoint topology have been given a device name!

IO-Controller Assigns the Remaining Device Names
With this information and the topology information which is stored in the Controller, the Controller
identifies the IO-Devices and assigns them their names. As soon as the Devices have been given
a name, they share it with their partners.
In this way, the entire PROFINET IO-System is commissioned.
Summary
The topology of the PROFINET IO-System is configured offline. With this setpoint topology, the
‘neighborhood’ relationships of all PROFINET IO-Devices located in the PROFINET IO-System
are made known to the PROFINET IO-Controller.
M O
RU
From the relationships specified through the setpoint topology and the relationships detected via
o
inh
the LLDP real PROFINET-Devices, the IO-Controller can identify the IO-Devices without a name
and assign them the configured name and the IP address.
o u t
a C
P e reir
e g o
Dy

6.6. Adjusting
Adjusting Topology
the the ViewView
Topology to thetoNetwork View View
the Network
Apply positions from the

Network view
M O
RU
o
tinh Network view serves as
Cou
template for
synchronization
eir a
P e r
eg o
Dy

Adjusting the Topology View to the Network View
The function "Apply positions from the Network view" allows you to also adopt the positions of the
devices adjusted in the Network view in the Topology view without further effort. That is, a
synchronization of the Topology view is made. Here, the Network view serves as a template for
the Topology view.
An alignment of the Network view on the basis of the Topology view is not possible!
Note
O
Since - on the basis of the Network view - the Topology view can only derive the configuration of
M
RU
the devices and not the wiring of the devices, only the position is adopted!
o
u t inh
Co
a
P e reir
e g o
Dy

6.7. Creating the the

Creating Setpoint Topology
Setpoint Topology
Networking through
drag & drop
Autofocus for the

port selection
O
Networking through
M
U
tabular selection
R
o
outinh
ra C
e i
Per
Topology – graphic
presentation
eg o
Dy
Topology – tabular
presentation

Creating the Setpoint Topology
When an IO-Device is assigned to the IO-Controller in the Network view it is still not established
how the ports are interconnected with one another. This assignment occurs in the Topology view
or also in the Topology editor.
An interconnection in the Network view does not generate an interconnection in the Topology
view and vice-versa. Creating a device in one of the two views, however, also generates the
device in the other view.
The networking of the ports in the Topology view can either be generated graphically through
drag & drop or through a table. For the tabular Topology overview and the tabular networking, the
overview must be dragged into the editing window using the arrow keys or drag & drop.
M O
o RU
u t inh
Creating a topology is not absolutely necessary! The realtime functionality of a PROFINET
Co
network can be used on its own. When IRT and the automatic commissioning of a PROFINET IO-
a
P e reir
Systems is used, the creation and downloading of a setpoint (preset) topology into the IO-
Controller is, however, absolutely necessary!
g o
In addition to the use of IRT and the automatic commissioning, the creation of a topology also
e
Dy
offers the following advantages:
• By using an Offline/Online comparison, it is possible to carry out a setpoint-actual
comparison for the devices which support this functionality.
• The function “Support device replacement without exchangeable medium” is available.

Note
The interconnection of ports can also be done in the Inspector window instead of graphically or
symbolically in the work area:
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

Downloading the Setpoint Topology into the

6.8. IO-Controller
Downloading the Setpoint Topology into the IO-Controller
PROFINET-IO topology is downloaded

via the HW-Config
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Downloading the Setpoint Topology into the IO-Controller
The setpoint topology created in the Topology view is downloaded into the IO-Controller together
with the hardware configuration. After the download, the IO-Controller then compares the loaded
setpoint topology with the real actual topology. IO-Devices without a name are now, if they fulfill
the requirements, initialized by the IO-Controller – they are assigned the name defined in the
setpoint topology for the Device.
Differences between the setpoint and the actual topology are identified by the IO-Controller and
are signaled to the user via an error evaluation.
Note
M O
Differences between the setpoint topology and the actual topology are also displayed by the IO-
RU
Controller via the diagnostic buffer. An incorrectly inserted patch cable or a wire break could also
o
be identified and signaled in this way!
u t inh
C o
a
P e reir
e g o
Dy

Task Description:
Creating
6.9. Taskthe Setpoint Topology
Description: Creatingofthe
theSetpoint
1500 Case
Topology
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task Description
You are to configure a setpoint (preset) topology for the S7-1500 case which corresponds to the
real topology.
Note
To make it easier to create the setpoint topology, you can also use the PRONETA tool.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise
6.9.1. 1: Creating
Exercise thethe
1: Creating Setpoint
SetpointTopology
Topology of the 1500 Case
Devices must be networked

according to their real connection
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Task
In your project, you are to create a setpoint topology which corresponds to the actual topology of
the system. Then you are to load the controller. No errors should occur for any module. If they do,
eliminate them!
What to Do
1. In your project, switch to the “Topology view”.
2. Network the individual devices with one another just as it corresponds to the real structure.
M O
R
4. Load the controller. No errors should occur for any module.U
h o
5. Eliminate any possible errors.
o u tin
6. Once again load and save your project.
r a C
i
Note P ere
e o editor, you can very easily control which offline wiring does not
gTopology
y
In the online view in the
Dof the system or which has errors during running operation:
fit to the real wiring

6.10.Detecting the the

Detecting Actual Topology
Actual of a PN
Topology of aIO-System
PN IO-System
Topology editor
Topology query by the

TIA Portal to all devices
LLDP MIBs are read-out

M O
RU
o
ou tinh
P1
ra C P1 P5
i
ere P2 P6
eg oP P3 P7
Dy
Port PartnerID.PortID
s7-1500
x208.P1 P4 P8
Port x208
PartnerID.PortID
s7-1500.P1
Detecting the Actual Topology of a PROFINET IO-System
TIA Portal makes it possible to detect the actual topology of a PROFINET IO-System. For this,
TIA Portal sends a topology query into the IO-System and receives in return all LLDP MIBs.
By reading out these neighbor tables, TIA Portal can deduce the required information for building
the interconnections between the individual devices as well as the port allocations and with that
also the topology.
Correlation IP Addresses and LLDP MIB

So that the LLDP MIBs can be read out of the devices, they must have a valid IP address!
TIA Portal can temporarily assign an IP address to devices that do not have an IP address before
M O
the topology is read out. This option can be found in the TIA Portal ‘Settings’ and there under the
item: “Hardware configuration”:
o RU
u t inh
C o
a
P ereir
e g o
Dy
If this option is activated, the popup window questioning whether the TIA Portal is to assign
temporary IP addresses to the IO-Devices appears before every Offline/Online comparison of the
topology.

6.11.Offline/Online Comparison
Offline/Online of the
Comparison ofTopology
the Topology
Synchronize Assignment to the

Offline Device
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
offline networking offline/online comparison online networking

Offline/Online Comparison of the Topology
With the Offline/Online comparison, the configured topology is compared to the actually existing
topology. Online detected devices are automatically assigned to the offline configured devices, as
far as this is possible.
An online detected device is automatically assigned to an offline existing device when the
following properties of the two devices match:
• PROFINET device name
• Order number
• Number of ports
M O
manually to the offline devices if they exist in the project. o RU
All devices detected online which are not automatically assigned can then also be assigned
u t inh
Applying the Online Topology Offline
C o
a
P e reir
After the devices detected online are assigned to the offline configured devices, their port
interconnections are compared and can then also be applied in the offline project as required.
g o
For this the ports, which are to be applied in the offline project, are selected and in the “Action”
e
Dy
column, the selection is changed from “No action” to “Apply” for these:
The loading of the online interconnection in the offline topology, for those where the selection was
set to “Apply”, is then completed via the button “Synchronize”.
For the standard offline/online comparison, a search method is applied which uses the DCP
protocol.

Advanced Offline/Online Comparison

For the standard offline/online comparison, a search method is applied which uses the DCP
protocol.
For the Advanced offline/online comparison, ICMP is additionally used in order to also detect
devices that do not support DCP. PG/PC stations, for example, belong to such devices.
Note M O
R U
o
It can take several seconds until the Offline/Online comparison has been completely carried out
ou tinh
and visualized. During this time, no operator inputs are possible.
The progress of the Offline/Online comparison can, however, be seen in the status bar:
ra C
e i
o Per
eg
Dy
A right-click in the Topology overview opens the selection window in which the selection “Apply
all” can be made. All online port interconnections which can be applied are then set from “No
action” to “Apply”.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

6.12.Device Replacement
Device without
Replacement Exchangeable
without Medium
Exchangeable Medium
IO-Device must support Device does not support a

the function removable media
Requirement:
delivered condition
M O
R U
o
ou tinh
ra C
e i
Per
Must be activated in the
IO-Controller
eg o
Dy
Device Replacement without Exchangeable Medium
IO-Devices, which do not have a slot for a removable media (e.g. ET 200SP, ET 200MP) or which
support the PROFINET functionality ‘device exchange without exchangeable medium/PG’, can be
replaced without a removable media - containing a stored device name - having to be inserted or
without the device name having to be assigned with the PG. The replacement IO-Device no
longer receives the device name from the removable media or from the PG but from the IO-
Controller.
To assign the device name, the IO-Controller uses the configured topology and the
‘neighborhood’ relationships detected from the IO-Devices.
In the Online Support pages, under the Entry ID: 36752540, you will find a listing of all IO-
M O
Controllers and all IO-Devices which support the automatic commissioning without topology, that
is, the ‘device exchange without exchangeable medium’.
o RU
t inh
https://support.industry.siemens.com/cs/de/de/view/36752540
u
C o
So that the name assignment by the IO-Controller can function smoothly, however, the IO-Device
a
P e reir
must first be brought back to its delivered condition, that is, its factory settings since the IO-
Controller can normally not overwrite the PROFINET device name of the IO-Device.
e g o
Note
Dy
So that the device replacement without exchangeable medium is carried out without a problem,
the connection of the new IO-Device must take place exactly the same as for the replaced IO-
Device. That is, the port interconnection must match since the setpoint topology otherwise no
longer matches the actual topology and the IO-Controller cannot assign a name to the IO-Device.

6.13.Overwriting the PROFINET

Overwriting Device
the PROFINET NameName
Device
Delivered condition
not required
IO-Device exchange
M O
R U
o
outinh
ra C
ei
Per IO-Controller overwrites
ego the name
Dy

Permitting Overwriting of the PROFINET Device Name
The function: “Permit overwriting of device names of all assigned IO-Devices” makes it possible
to exchange PROFINET IO-Devices without first resetting them to their delivered condition / their
factory settings. Before the IO-Controller overwrites the PROFINET device name, a check is
made as to whether the type of the new IO-Device matches the type of the configured IO-Device.
If this is the case, the configured name is then written in the IO-Device.
This functionality is possible with an S7-1500 CPU as of Firmware Version V1.5 and with an
ET200SP CPU as of Firmware Version V1.6. The effort in replacing an IO-Device is reduced with
this function.
Note
M O
U
R IO-Devices" is activated,
If the option "Permit overwriting of device names of all assigned
h o
tin
incorrectly connected devices can be given an incorrect PROFINET device name from the
configuration.
o u
Cmalfunctions can cause danger to life, serious risk of
i
Depending on the connected peripherals, r a
injury or material damage!
P ere
y egoexchange,
In every case of a device check whether the correct replacement device is connected
D
and that the port interconnection
possibility of risk!
meets the configured setpoint topology in order to avoid any

6.14.Aufgabenstellung: Restliche
Task Description: Topologie
Detecting der Anlage
the Remaining Topology of the
ermitteln und die automatische IBN testen
System and Testing the Automatic Commissioning
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
The topological networking of the remaining system components is not to be entered manually
but is to be detected using TIA Portal. First the missing Devices must naturally be generated,
configured, parameterized as well as networked in the project!
Then, the PROFINET functions for automatic commissioning of a system, such as, the
functionalities “…device replacement without exchangeable medium” or also “…overwriting of
(PROFINET) device names…” are to be activated and tested in the controller.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise
6.14.1. 2: 2:
Exercise Configuration
Configuration& Parameterization of the
Missing Devices (Scalance
& Parameterization + ET 200SP
of the Missing PLC)
Devices (Scalance + ET 200SP PLC)
Add (detect)
ET 200SP CPU
I/O addresses: 0/0
192.168.222.10
U MO 255.255.255.0
1510-io-controller
o R
ti n h
C o u Add Scalance XC208
a
Pe reir
e g o 192.168.222.208
255.255.255.0
Dy scalancexc208
1513 is IO-Controller for

the Switch

Task
You are to complete your project by inserting the missing devices in TIA Portal which are already
physically networked (CPU 1510SP-1PN + SCALANCE XC208).
The digital inputs and outputs of the 1510SP-1PN controller get the address 0. The controller is
assigned the IP address 192.168.222.10 with the subnet mask 255.255.255.0. The PROFINET
device name is “1510-io-controller”.
For the SCALANCE XC208, the PROFINET device name “scalancexc208” is set in the hardware
configuration offline. It is assigned the IP address 192.168.222.208 with the subnet mask
255.255.255.0. The S7-1513 takes on the role of its IO-Controller.
M O
RU
Subsequently, you are to integrate the two new Devices into the existing PROFINET IO-System.
o
What to Do u t inh
C o
a
reir
1. As a new device, add a SIMATIC ET200CPU. Pay attention to the correct MLFB Number and
the correct Firmware Version. You can also use the functionality “Detect the configuration of
Pe
the connected device” by using an unspecified CPU:
e g o
Dy
2. Configure and parameterize the PLC according to the task.

3. Insert a new device of the type SCALANCE XC-200 managed. Here as well, pay attention to
the correct MLFB Number and the correct Firmware Version.
4. Parameterize the SCALANCE XC208 according to the task.
5. Network the devices in the Network view in TIA PORTAL.
6. Set up the PROFINET IO-System in such a way that the S7-1513 functions as the IO-
Controller for the Switch and not the S7-1510SP.
7. Create a new group with the name "1510Case" and assign the S7-1510SP as well as the
SCALANCE XC208 to it.
9. Download both controllers.
M O
10. The error LED of the S7-1513 should begin to flash. This state is normal and will be fixed in
the following exercises! R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Exercise
6.14.2. 3: 3:
Exercise Detecting
Detectingthe
theActual Topology
Actual Topology
Carry out Offline/Online

comparison
Apply all and Synchronize
M O
RU
o
Show / hide
ou tinh
Topology overview
ra C
e i
o Per
eg
Dy
Task
You are to detect the actual topology of your components. For this, use the integrated
Offline/Online comparison of the Topology editor in TIA Portal.
What to Do
1. Open the Topology view in your project.
2. Show (Expand) the Topology overview.
3. Start an Offline/Online comparison. It can take a few seconds until it shows the desired data.
The current progress is presented in the lower right corner in TIA Portal.
MO
RU
4. Apply the actual topology in your project and then synchronize the setpoint and the actual
topology. Pay attention to the note!
o
u t inh
C o
i r a
6. Download the S7-1513. The error LED continues to flash. This is a desired state!
7. Download the S7-1510SP. Ifethe
P re error LED also flashes for this one, it is also OK!
Note y ego
D
It may be that you have to assign the correct Offline-Devices to the Online-Devices before
applying the actual topology in your project. If necessary, do this using this drop-down window:

Exercise
6.14.3. 4: 4: Activating a Device Replacement without Exchangeable
Exercise
Device Replacement without Exchangeable Medium
Medium
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task
You are to check whether the functionality “Support device replacement without exchangeable
medium” is activated in the S7-1513 as well as in the S7-1510SP. If this is not the case, activate
them. Then you are to test this functionality by resetting the ET 200SP to its factory settings. It
should now automatically be re-initialized by the S7-1513 without you having to do anything! If the
functionality is deactivated, this should not be the case! Test both cases!
What to Do
1. Check whether the functionality is activated in both controllers. If this is not the case, activate
this option and download both controllers!
U MO
2. With the help of the Online access, reset the ET 200SP o Rto its factory settings.
h
n green.
tiflash
3. The ET200SP and all its modules should now
o u
4. After a short time, the IO-ControllerawillC
r e i r automatically initialize the IO-Device, the ET 200SP,
Pe
and also assign it the IP address. The ET 200SP and its modules should now once again light
up green.
o
eg in the S7-1513 and download the controller.
y
5. Deactivate the functionality
D
6. Once again, reset the ET 200SP to its factory settings.
7. The ET 200SP and its modules should now once again flash green. The flashing will not,
however, stop since the IO-Controller cannot automatically initialize the ET 200SP.
8. Ping the IP address of the ET 200SP. This should not be accessible.
9. Activate the functionality in the S7-1513 and download it.
10. The ET 200SP should now once again light up green.
11. Ping the ET 200SP. It should once again be accessible.

Note
The flashing of the S7-1513 error LED is still a normal state!
The functionality “Support device replacement without exchangeable medium” is activated on the
S7-1500 by default!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise
6.14.4. 5: 5:
Exercise Permit
PermitOverwriting
Overwriting the DeviceNames
the Device Names
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
Finally, you are to activate the functionality “Permit overwriting of device names of all assigned IO
devices” on the S7-1513. With this function, the controller can overwrite the SCALANCE XC208
which has an incorrect PROFINET device name and so causes the error on the S7-1513. Then,
you are to change the device names of the IO-Devices for further tests. You are to do this using
the function “Assign name” in the ‘Online access’. When the functionality is activated, the
controller should simply overwrite the names once again.
What to Do
1. Activate the functionality on the S7-1513 and download it.
M O
RU
2. All modules should now light up green and the S7-1513 error LED should no longer flash.
o
inh
3. As a test, overwrite the names of the ET200SP and the SCALANCE XC208. After a few
u t
cycles, the controller should overwrite them with the names specified in the hardware
o
configuration.
a C
4. Save your project!
P e reir
e g o
Dy

WennAdditional
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Topologie-Editor Seite 24 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Device Replacement without Topological
Configuration
6.15.1. Device Replacement without Topological Configuration
ET 200SP supports device

replacement without
topological configuration
M O
R U
PROFINET-Gerätenamen
o
PROFINET device name is
tinh
wird auf dem Bus Adapter
stored on the bus adapter
abgelegt
C ou
e i ra
o Per
eg
Dy
Device Replacement without Topological Configuration
The functionality: “Device replacement without topological configuration” permits a device
exchange without a removable media and without configured setpoint topology in the IO-
Controller.
This function is supported by the following IO-Devices:
• ET 200SP IM 155-6 PN HF with the article number 6ES7155-6AU00-0CN0 as of
Firmware V2.0
• ET 200SP IM 155-6 PN ST with the article number 6ES7155-6AA00-0BN0 and 6ES7155-
6AU00-0BN0 as of Firmware V3.1
M O
For these IO-Devices, the device name is also additionally stored on the bus adapter, if it is of the
RU
type BA 2xRJ45 or 2xFC. Due to the fact that the name can be stored both on the interface
o
inh
module and on the bus adapter, the following scenarios can result when the interface module is
replaced:
o u t
a C
reir
Pe module empty
Interface Interface module with device
eg o name
Bus adapter Dy No device name exists. Device name from interface
empty module is used and copied onto
the bus adapter
Bus adapter Device name from bus adapter is used Device name from bus adapter is
with device and copied onto the interface module. used and copied onto the
name interface module, if the module
contains another device name.

Contents 7
7. Diagnostics ............................................................................................................. 7-2
7.1. Diagnostic Possibilities ......................................................................................................... 7-3
M O
7.2. U
Diagnostics via LEDs ............................................................................................................ 7-4
R
7.2.1. o
LEDs of the PLC S7-1513 – 1PN.......................................................................................... 7-4
7.2.2.
7.2.3. ou tinh
LEDs of the SCALANCE XC208 ........................................................................................... 7-5
LEDs of the ET 200SP .......................................................................................................... 7-6
7.2.4.
ra C
LEDs of the PLC S7-1510SP – 1PN ..................................................................................... 7-7
e i
7.3.
Per
System Diagnostics .............................................................................................................. 7-8
o
7.4. eg
Diagnostics with the Help of Display Units ........................................................................... 7-9
7.5. Dy
Task Description: Commissioning and Diagnosis of the TP700 ......................................... 7-10
7.5.1. Exercise 1: Inserting the TP700 from the Library & Connecting it with the S7-1513......... 7-11
7.5.2. Exercise 2: Creating the Diagnostics View on the TP700 Comfort .................................... 7-12
7.6. Detecting the Hardware Identifier of an I/O Module............................................................ 7-13
7.7. Detecting the Hardware Identifier of an IO-Device ............................................................. 7-14
7.7.1. Data Type GEOADDR ........................................................................................................ 7-15
7.8. Activating / Deactivating an IO-Device ............................................................................... 7-16
7.9. Reading-out the Device Name of the IO-Device................................................................. 7-18
7.10. Task Description: Reading-out the ET 200SP Device Name and Activating / Deactivating the
IO-Device ............................................................................................................................ 7-19
7.10.1. Exercise 3: Reading-out the ET 200SP Hardware Identifier and Outputting it on the HMI 7-20
7.10.2. Exercise 4: Activating / Deactivating the ET 200SP ........................................................... 7-22
7.10.3. Exercise 5: Reading-out the ET 200SP Device Name and Outputting it on the HMI ......... 7-23
M O
7.11.
RU
Reading-out the Module LED Status .................................................................................. 7-24
7.12.
i n ho
Reading-out the Device and Module States ....................................................................... 7-25
t
7.13. C ouState of the ET 200SP................................... 7-27
Task Description: Reading-out the Module
7.13.1. ira State of the ET 200SP.............................................. 7-28
Exercise 6: Reading-out the Module
r e
o Pe
y eg
D
IK-TIAPN – Diagnostics
Diagnostics
7. Objectives
... have a basic overview of the various diagnostic possibilities in the

TIA Portal
... be familiar with the meaning of the LEDs of the different

components
M O
R U
... o
be familiar with the system diagnostics
...
ou tinh
be able to operate the diagnostics with the help of display units
ra C
... e i
be able to program different instructions for diagnostics
o Per
eg
Dy
SITRAIN
IK-TIAPN / Diagnostics Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
7.1. Diagnostic Possibilities

Diagnostic Possibilities
Possibilities Use Conditions

LEDs Directly visible diagnostics On-site on the hardware possible
More detailed diagnostic
PG / TIA Portal Engineering software necessary
information
Predefined diagnostic
System diagnostics Is set in the hardware configuration
information
Display devices
Same presentation of the
(CPU-Display / Web
diagnostic information O
Connection to the CPU is required
M
server / HMI)
R U
Reaction to events directly h o
User program
ou
possible in the program tin Additional programming effort
ra C
e i
o Per
eg
Dy
ID: 98210758

Page 3 Diagnostics
Diagnostic Possibilities
The automation world of SIMATIC offers you a wide range of diagnostic possibilities. For the
simplest diagnostic possibility – the visual inspection of LEDs on the SIMATIC devices, for
example – you do not have to carry out any other activities or programming. For a system
diagnostics or the visualization of the diagnostics on the display devices, you hardly have to do
anything either.
Further and more in-depth diagnostic possibilities are usually defined in the user program and, for
their part, then require advanced programming knowledge.
On the Service & Support pages, you will find an article on diagnostics with an S7-1500 under the
Entry ID number: 98210758.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
7.2. Diagnostics
Diagnostics via LEDs
via LEDs
7.2.1.LEDs of of
LEDs thethe
PLC
PLC1513 – 1PN
S7-1513 – 1PN
Run/Error/Maint-LEDs ID: 59186494
LINK RX/TX-LEDs
Options LINK-LED Meaning M O

RU
LED off
o
A LINK connection does not exist.
LED lights up green ou tinh

There is an Ethernet connection to a
C
communications partner.
ra
e i The "LED flash test" is being performed.
LED flashes green
o Per
eg
Dy
Data is being exchanged with a communications
LED flickers yellow
partner via the PROFINET interface.
Transmission frequency in the PROFINET is so fast
LED lights up yellow
that the flickering appears as a continuous light.

Page 4 Diagnostics
LINK-LEDs of the PLC (X1P1, X1P2)
In order to determine why communication between two partners in the network does not work,
you should first of all always rule out a physical problem! That is, you must check whether a
physical connection, normally via an Ethernet cable, even exists between the devices.
In this case, the LINK-LEDs of the controller lend themselves for this. These signal whether a
LINK, that is a physical connection, is established between the port assigned to the LED and the
communications partner or not. If this LED if off, no LINK connection exists at the moment. This
can be caused either through a wire break in the cable, a general cable break or simply a plug
that is not wired 100 percent.
M O
RU
Communication between Devices
t i n ho
When the devices connected to the PROFINET
C otouorflicker
Ethernet interface exchange data amongst
i r a
themselves, the associated LINK-LED begins yellow. The faster the flickering, the faster
ere
the transmission frequency is between the partners.
P
Note
y ego
D to take on a continuous light, the transmission frequency is so high (fast)
If the LINK-LED appears
that the LED only displays a yellow color.
This behavior can frequently be observed with a coupling between a PROFINET IO-Controller
and a PROFINET IO-Device.
7.2.2.LEDs of of
LEDs thethe
SCALANCE
SCALANCEXC208
XC208
Options Fault-LED Meaning

LED flashes red An internal error was detected.
-Link Down event at one of the monitored
ports
-Loss of one of the two redundant power
supplies
-C-Plug error
LED lights up red -Switch startup (20 seconds)
O
-Device is in PROFINET operation:
M
RU
→no connection to the controller
o
ou tinh→diagnostic interrupt pending
-Redundancy manager connected through
ra C -Loop Detection
e i
o Per
Port-LEDs
DyegFault/RM/Standby/Anzeige-
modus/Power-LEDs
ID: 109476763

Page 5 Diagnostics
Display Mode LEDs of the SCALANCE XC208 (DM1, DM2)
The LEDs (DM1, DM2) indicate which display mode is set. There are 4 display modes (A, B, C
and D). Display mode A is the standard mode. Depending on display mode set, the Power LEDs
(L1, L2) and the Port LEDs show different information.
Power LEDs of the SCALANCE XC208 (L1, L2)

The Power LEDs (L1, L2) of the SCALANCE XC208 indicate in which voltage range the power
supply at the L1 as well as at the L2 connections finds itself or whether the power supply is
generally monitored.
Port LEDs of the SCALANCE XC208 (P1, P2, P3, P4, P5, P6, P7, P8)
U MO
The Port LEDs of the SCALANCE XC208 show the same R
n h o behavior as the LINK LEDs of the S7-
1513-1PN.
o u ti
Fault LED of the SCALANCE XC208 (F)
r a C
i
reXC208 indicates whether the SCALANCE XC208 is currently in
The Fault LED of the SCALANCE
P e
o is notred).lit up) or whether an error detected by the device is currently
eorgflashes
an error-free operation (LED
y
pending (LED is lit up
D detected by the SCALANCE XC208 are listed in the picture. Depending on
The possible errors
the model of the SCALANCE family, different errors and also various numbers of errors are
detected by the respective device.
Redundancy Manager LED of the SCALANCE XC208 (RM)

The RM LED of the SCALANCE XC208 indicates whether the SCALANCE XC208 is
parameterized as a redundancy manager or not. Furthermore, with an active redundancy
manager role, it signals whether the ring is interrupted or not.
Standby LED of the SCALANCE XC208 (SB)

The Standby LEDs (SB) of the SCALANCE XC208 is used to display the standby function of the
SCALANCE XC208. Furthermore, it indicates the status (active/passive).
7.2.3.LEDs of of
LEDs thethe
ETET
200SP
200SP
ID: 59768173
Run/Error/Maint-LEDs
LINK LX-LEDs
Power LED
M O
RU
o
Options LINK-LED
o utinh
Meaning
C
LED off
r e ira A LINK connection does not exist.
LED o Peup green

lights
There is an Ethernet connection to a
eg communications partner.
DyLED flashes green The "LED flash test" is being performed.

Page 6 Diagnostics
LINK LEDs of the Bus Adapter (LK1, LK2)
The various light patterns of the LINK LEDs of the bus adapter are shown in the picture. Unlike
the LINK LEDs of the PLC S7-1513 - 1PN and the SCALANCE XC208, these do not flash yellow
when data is exchanged between the connected devices.They only indicate, through a green
continuous light, that a communication between the connection partners exists.
Power LED of the ET 200SP (PWR)

The Power LED of the Interface Module IM155-6PN ST of the ET200 SP indicates, through a
green continuous light, that there is sufficient supply voltage. If the Power LED does not light up,
there is no or too little voltage connected to the ET200 SP.
M O
Run, Error, Maint LEDs of the ET 200SP (RN, ER, MT)
o RU
u t inh
A listing of the various light and flashing patterns of the Run, Error and Maint LEDs can be found
o
in the manual of the SIMATIC ET200 SP Interface Module IM 155-6 PN ST. This can be found on
C
a
the Service and Support page under the Entry-ID: 59768173.
P e reir
e g o
Dy
7.2.4.LEDs of of
LEDs thethe
PLC
PLC1510SP – 1PN
S7-1510SP – 1PN
Run/Error/Maint-LEDs ID: 90157130
LINK LK-LED CPU
LINK LX-LEDs BA
Power LED
M O
RU
o
Options LINK-LED Meaning
ou
LED off
tinh A LINK connection does not
ra C exist.
e i
Per
There is an Ethernet
o LED lights up green connection to a
Dyeg
Optional BA module communications partner.
The "LED flash test" is being
LED flashes green
performed.
Page 7 Diagnostics
LINK LED of the PLC 1510SP – 1PN (LK3)
The various light patterns of the LINK LEDs of the PLC S7-1510SP – 1PN are shown in the
picture. Unlike the LINK LEDs of the PLC S7-1513 - 1PN and the SCALANCE XC208, these do
not flash yellow when data is exchanged between the connected devices. It only indicates,
through a green continuous light, that a communication between the connection partners exists.
The PLC S7-1510SP - 1PN has an integrated PROFINET interface with one port. Additional ports
can, however, be added via an optional bus adapter (BA) (similar to an ET 200SP).
Power, Run, Error, Maint LEDs of the ET 200SP (PWR, R/S, ER, MT)
A listing of the various light and flashing patterns of the Power, Run, Error and Maint LEDs can be
M O
found in the manual of the SIMATIC ET 200SP CPU S7-1510SP - 1PN. This can be found on the
Service and Support page under the Entry -ID: 90157130.
o RU
u t inh
C o
a
P e reir
e g o
Dy
7.3. System Diagnostics

System Diagnostics
RSE no longer necessary
M O
U
RAlways active
o
ou tinh
ra C
e r ei Possible settings
o P
eg
Dy
Page 8 Diagnostics
System Diagnostics
The system diagnostics of an S7-1500 is always activated by default and cannot be deactivated
by you. No further handling is necessary in order to use these diagnostic possibilities.
What you can set is whether the different Alarm Categories generate alarms and whether these
are to require an acknowledgement or not.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
7.4. Diagnostics withwith

Diagnostics the Help of Display
the Help UnitsUnits
of Display
Exchange
diagnostic data
Diagnostic buffer
PLC on HMI
Sends diagnostic
data
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
HW diagnostics on
the HMI

Page 9 Diagnostics
Diagnostics with the Help of Display Units
Since a programming device is not always available in a plant in order to look at the diagnostic
buffer of the PLC to see what kind of error is currently pending and since the controller has
normally ‘disappeared’ inside the control cabinet so that the display of the S7-1500 is not
accessible without a problem, the possibility of diagnostics on display units lends itself for this.
For system diagnostics on Siemens HMI devices, there is a prefabricated Control which is simply
dragged into the HMI screen using drag & drop and which then provides the user with the
relevant diagnostic information there.
System Diagnostics View Control

M O
CPU on the HMI device. o RU
The system diagnostics view makes it possible to present the diagnostic buffer of the connected
t inh
A further function is the overview of the PROFINET IO-System and the graphic presentation of
u
o
failed devices. This diagnosis is even available module-by-module!
C
a
P e reir
e g o
Dy
Task Description:
Commissioning
7.5. and Diagnosis
Task Description: of the TP700
Commissioning and Diagnosis of the TP700
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN
Task / Diagnostics
Description Page 10 Siemens AG © 2016
You are to commission the TP700 Comfort which is located in your S7-1500 case. For this, you
are to use the template which is located in the “IK-TIAPN” library. Then, you are to establish an
HMI connection between the TP700 Comfort and the CPU S7-1513 - 1PN and create the system
diagnostics view on the Panel. Finally, you are to test whether the diagnostics view also supplies
the desired data.
Your old TP700 Comfort must be deleted from the library before you commission the Panel!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Exercise Inserting the TP700
from the Library
Inserting & Connecting
the TP700 it with&the
from the Library S7-1513it with the S7-1513
Connecting
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy

Page 11 Diagnostics
Task
You are to open the “IK-TIAPN” library and then insert the prefabricated touchpanel TP700
Comfort located in the folder “Chapter7” from the library into your project. Then, you are to
establish an HMI connection between the touchpanel and the CPU 1513 - 1PN.
The library is located on your computer in the following path:
C:\Archives\TIA_Portal\IK-TIAPN
What to Do
1. Delete the TP700 Comfort from your project.
M O
2. Open the “IK-TIAPN” library.
o RU
u t inh
3. Using drag & drop, drag the TP700 Comfort “touch-me” from the folder “Chapter7” and the
subfolder “HMI” into your project.
Co
a
P e reir
4. Establish an HMI connection between the TP700 Comfort and the CPU S7-1513 - 1PN.
e g o
5. Rewire (re-network) the lost topology between the S7-1513 and the Panel as well as between
Dy
the Panel and the SCALANCE XC208.
6. Also drag the new TP700 Comfort back into the folder "1513Case".
8. Download the S7-1513.
Exercise 2: Creating the Diagnostics View on the
7.5.2.TP700 Comfort
Exercise 2: Creating the Diagnostics View on the TP700 Comfort
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 12 Diagnostics
Task
You are to create the diagnostics view on the TP700 Comfort and test it.
What to Do
1. Open the already existing “Diagnosis” screen in the touchpanel.
2. Using drag & drop, drag the Control “System diagnostics view” into the screen.
3. Adjust the size and the properties of the Control as required.
4. Compile the touchpanel.
5. Download your configuration into the touchpanel. M O
6. Test your diagnostics view.
o RU
7. Correct, if necessary, your project.
u t inh
C o
8. Save your changes. a
P e reir
e g o
Dy
7.6. Detecting the the

Detecting Hardware Identifier
Hardware of anof
Identifier I/Oan
Module
I/O Module
Hardware identifier
Data type: HW_ANY
Address of module
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 13 Diagnostics
IO2MOD
The instruction “IO2MOD” allows you to read out the hardware identifier of a module from an I/O
address of the module. The instruction is located in the Extended Instructions and there in the
folder “Addressing”.
At the input “ADDR”, variables of the type I, Q, PI or PQ can be specified. If the programming
language SCL is used, the type PQ is not permitted. The hardware identifier is returned through
the data type “HW_IO” or “HW_ANY”.
The function “IO2MOD” has an internal error evaluation using the output “RET_VAL”.
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy
7.7. Detecting the the

Detecting Hardware Identifier
Hardware of anof
Identifier IO-Device
an IO-Device
Hardware identifier
Data type: GEOADDR
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 14 Diagnostics
GEO2LOG
In the Extended Instructions in the folder “Addressing”, you will find the instruction “GEO2LOG”.
This instruction allows you to detect the hardware identifier of an IO-Device during runtime of the
controller. The hardware identifier is detected through the slot information of the IO-Device. This
information is passed to the instruction via the data type “GEOADDR”.
The hardware identifier is returned with the help of the data type “HW_ANY”.
Note
The instruction “GEO2LOG” also has a system-internal error evaluation which is evaluated via the
parameter “RET_VAL”. The meaning of the error code which is output can be found in the block
help in TIA Portal. M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
7.7.1.Data Type
Data GEOADDR
Type GEOADDR
1: IO-System 2: IO-Device/DP-Slave
3: Rack 4: Module 5: Submodule
0:Central module 1: PROFINET IO

2: PROFIBUS DP 3: AS-I
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 15 Diagnostics
GEOADDR
The data type “GEOADDR” is a structure which consists of the following components:
• HWTYPE:
The component “HWTYPE” determines which further components of the structure
“GEOADDR” are evaluated.
• AREA:
Specification of the bus system to be evaluated.
• IOSYSTEM:
Identifier for the IO-System. The identifier for PROFINET is always 100!
M O
• STATION:
o RU
Specification of the station number, if “AREA” > 0. If “AREA” = 0 then the rack is specified
here.
u t inh
• SLOT: C o
a
Slot number
P e reir
• SUBSLOT: o
e g
Dy
Number of the submodule
7.8. Activating / Deactivating

Activating an IO-Device
/ Deactivating an IO-Device
not edge-triggered
activate/deactiviate Hardware
+ status IO-Device identifier
Deactivation M O Read-out status

Activation
U
hoR
o u tin
a C
e r eir
o P
eg
Dy
Page 16 Diagnostics
D_ACT_DP
The function “D_ACT_DP” can be used to specifically activate or deactivate DP-Slaves as well as
PROFINET IO-Devices. As a further functionality, the instruction also offers the possibility of
reading out the current status of the DP-Slave / PROFINET IO-Device, that is, whether the device
is currently activated or deactivated.
Especially for maintenance work or similar work on distributed I/Os, it makes sense to deactivate
the device before beginning the job so that no unnecessary error messages or error reactions can
occur on the CPU and be executed.
The function “D_ACT_DP” can be found in the Extended Instructions in the folder “Distributed
I/O”.
M O
The instruction “D_ACT_DP” is an asynchronous working instruction, that is, the execution can
RU
extend over several CPU cycles / calls. An internal error evaluation and the status display on the
o
inh
current task can be taken from the parameters “RET_VAL” and “BUSY”.
o u t
Note
a C
P ereir
If you take the hardware identifiers from the previous pages as an example, the block can only
e g o
deactivate and activate the IO-Device ET 200SP with the hardware identifier 264.
Dy
If the hardware identifier 266 is used, the function “D_ACT_DP” outputs the following error:
M O
RU the Help:
The plain text for the error number: 8093 can then be taken from
o
8093:
u t inh
C o
For the address specified in LADDR, there is no DP-Slave/PROFINET IO-Device which can be
ira
activated or deactivated.
r e
o Pe
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
7.9. Reading-out the Device

Reading-out Name
the Device of theofIO-Device
Name the IO-Device
Hardware-Kennung
Hardware identifier
PROFINET IO System
Device number
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy PROFINET
device name

Page 17 Diagnostics
Get_Name
If the hardware identifier of the PROFINET IO-System and the device number of the PROFINET
IO-Device is known, the PROFINET device name of the IO-Device can be read-out at runtime
with the help of the instruction “Get_Name”.
The device name which is output corresponds to the name of the header module.
The “Get_Name” instruction is an acyclic instruction. It can take longer than one CPU cycle for
the function to read out the name of the PROFINET device. Through the parameters “DONE” and
“BUSY”, you can see the current status of the reading-out of the name. The parameter “ERROR”
is used by the instruction as an error output.
Note
U MO
o R at the parameter “DATA”, the
If the PROFINET device name is longer than the area specified
h
tin of characters and the remaining are
parameter is filled with the maximum possible number
discarded. o u
Ccan also be taken from the output parameter “LEN” of
The length of the PROFINET device name
i r a
the instruction “Get_Name”.
P ere
y ego
D
Task Reading-out
Description: the ET200SP
Reading-out DeviceDevice Name
the ET 200SP
Name
andand Activating
Activating / Deactivating
/ Deactivating theIO-Device
the IO-Device
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy

Page 18 Diagnostics
Task Description
Having integrated the HMI device for diagnosis in your project in the previous exercise, this is
now to be used to read out the device name of the ET 200SP at runtime and to be able to
activate as well as deactivate the IO-Device at any time. The programming of this new
functionality takes place in the “FB_Diagnosis” function block which is to be created. This function
block is called in OB1 with the instance data block “iDB_FB_Diagnosis”.
The HMI screen for communication with the controller already exists in the library. The screen
elements are linked with the tags/variables of the data block “PROFINET_Diagnosis”.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Exercise
7.10.1. Exercise3: 3:
Reading-out the ET200SP Hardware
Identifier and Outputting
Reading-out it on
the ET 200SP the HMI
Hardware Identifier and Outputting it on the HMI
Read out the

HW identifier
Input
GEOADDR
M O
Output HW
RU identifier
o
Drag & Drop
ou tinh
ra C
e i
o Per
eg
HMI screen for
output
Dy

Page 19 Diagnostics
Task
You are to integrate the data block “PROFINET_Diagnosis” into your project and use the
variables contained in this block for parameterizing the PLC instructions.
You are to read out the hardware identifier of the ET 200SP and this is subsequently to be output
on the HMI screen “PROFINET-IO”. The reading-out of the hardware identifier is to take place in
the function block “FB_Diagnosis”. This function block is called in the organization block “Main”
and must be created by you.
What to Do
M O
1. Using drag & drop, drag the data block called “PROFINET_Diagnosis” from the IK-TIAPN
RU
library in the folder Chapter7 in the subfolder “SPS” into your project.
o
u t inh
2. Create a new function block called “FB_Diagnosis” and call it in your OB1. Name the instance
data block “iDB_FB_Diagnosis”.
Co
a
identifier.
Pe reir
3. In your FB, create the instructions necessary for reading out and outputting the hardware
o
eg into the controller.
4. Download the changes
y
5. Drag the HMID
screen “PROFINET-IO” into the folder “Screens” and the tag table
“PROFINET_Diagnosis” into the folder “HMI tags” which are located in the Device “touch-me”.
6. Link the "PROFINET-IO" screen with the "Start" screen just as it is in the "Diagnosis" screen.
7. Load the changes onto your HMI device and test your program.
8. If necessary, make changes so that your program matches the task.
Note
Please note that the data types “HW_ANY” and “HW_IO” cannot be used on the TP700 Comfort!
If necessary, take another look at the structure of the data type “GEOADDR” in the Online Help of
TIA Portal.
As required, use temporary as well as static variables in the function block!
It may be that the connection between the touchpanel and the controller does not correspond to
the configured connection in the tag table “PROFINET_Diagnosis”. In this case, adjust the
connection and re-synchronize the HMI tags!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Exercise
7.10.2. 4: 4:
Exercise Activating
Activating/ /Deactivating theET
Deactivating the ET200SP
200SP
Switch on/off
IO-Device
M O
R U
o
ou tinh
ra C
e i
o Per
Control
eg D_ACT_DP
Dy
Page 20 Diagnostics
Task
After the hardware identifier is read-out, it is now to be used to activate and deactivate your IO-
Device during runtime. Furthermore, the status of the IO-Device can then also be read out.
This functionality, as well, is output on the TP700 Comfort and controlled by it.
What to Do
1. Program the functionality called for in the task in your FB “FB_Diagnosis”.
2. Download and test your programming.
M O
Note
o RU
u t inh
The “REQ” parameter of the function “D_ACT_DP” is not edge-controlled.
C o
a
P e reir
e g o
Dy
Exercise
7.10.3. 5: 5:
Exercise Reading-out
Reading-outthe
the ET200SP
ET 200SP Device Name and Outputting it on
Device Name
the HMI and Outputting it on the HMI
Read out the IO-

Device name
M O
R U
o
ou tinh
ra C
ei
o Per
eg Control
Dy Get_Name

Page 21 Diagnostics
Task
Finally, the PROFINET device name of the ET 200SP is to be read out and presented on the HMI
device.
This functionality is also to be implemented in the FB “FB_Diagnosis”.
What to Do
1. Open the function block “FB_Diagnosis” and program the functionality.
M
3. If necessary, make changes so that your program matches the task. O
4. Save your project. o RU
u t inh
Note
Co
a
P e reir
The call of the instruction “Get_Name” is to be made using a multiple instance.
e g o
Dy
7.11.Reading-out the Module

Reading-out LED LED
the Module Status
Status
Hardware identifier
M O
RU
o
tinh
LED-Nummer
1 STOP/RUN
C ou
2 ERROR
e ira
3
Per
MAINT (Maintenance)
o
4
eg
Redundant
5 Dy
Link (green)
6 RX/TX (yellow)

Page 22 Diagnostics
LED
In a plant, most controllers are installed in the control cabinet. This means that the simplest way
of quickly doing a system diagnostics, namely looking at the LEDs on the controller or the
component, is not possible.
The instruction “LED”, however, makes it possible to read out the LEDs of a module and so
visualize the LED Status on a display unit or similar. This way, the LED Status of the module can
be analyzed and evaluated through the program.
The instruction “LED” requires the hardware identifier of the module for this and the specific
identification number of the LED on the module. If this does not exist, it is displayed through the
output parameter “RET_VAL”. Through this parameter, the status of the LED, such as, flashing
with 1 Hz or flashing with 2Hz, can also be displayed. M O
o RU
u t inh
Co
a
P ereir
e g o
Dy
7.12.Reading-out the Device

Reading-out and Module
the Device States
and Module States
Array [0..1023] of BOOL

M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Array [0..127] of BOOL

Page 23 Diagnostics
DeviceStates
If the state or the status information of all modules within a PROFINET IO-System or within a DP-
Master system has to be queried, the instruction “DeviceStates” can be used. This allows you to
read out different statuses of the connected Devices through the parameter “Mode”. These
statuses are stored in the InOut parameter “STATE”. If the status information of a PROFINET IO-
System is to be read-out, an Array of 1024 bits is used at the parameter “STATE”; for a DP-
Master system, an Array of 128 bits is used. For this Array, the Bit 0, that is, the first bit, always
serves as the group display for both systems. If for at least one Device the bit of the status
display is set to 1, the group display bit also has the Status 1.
For a PROFINET IO-System, the individual bits of the Array correspond to the device numbers of
O
the individual IO-Devices. For a DP-Master system, the bits then correspond to the PROFIBUS
M
RU
addresses of the individual DP-Slaves.
o
ModuleStates
u t inh
C o
If, instead of the state of a PROFINET IO-System or a DP-Master system, the state of the
a
P e reir
individual modules of an IO-Device or a DP-Slave has to be read-out, the function “ModuleStates”
can then be used. With the help of this instruction, different status information of the individual
e g o
modules can be queried through the input parameter “MODE”. Just as for the instruction
Dy
“DeviceStates”, the statuses of the individual modules are then stored in the InOut parameter
“STATE”. The parameter “STATE” is an Array with 128 bits. Here as well, the first bit serves as
the group display. If a bit in the Array is set to 1 through the instruction “ModuleStates”, the group
display is also automatically set to 1.
MODE
The value passed via the parameter “MODE” to the instructions “DeviceStates” and
“ModuleStates” causes the same configuration for both instructions. The only difference is that
the setting for the instruction “DeviceStates” refers to the individual Devices/Slaves and for the
instruction “ModuleStates” it refers to the individual modules. The following status information can
be queried via the configuration of the parameter “MODE”:
1. IO-Devices/DP-Slaves – Modules are configured
2. IO-Devices/DP-Slaves – Modules have failed
3. IO-Devices/DP-Slaves – Modules deactivated
4. IO-Devices/DP-Slaves – Modules present
M O
U
5. IO-Devices/DP-Slaves – Modules for which a problem has occurred:
R
o
•
•
tinh
Maintenance necessary or recommended
ou
Not accessible
ra C
• Not available
e r ei
• Error haso
P
e g occurred
• Dy
…
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
Task Description: Reading-out the Module State of the
Reading-out
ET 200SPthe Module State of the ET200SP
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy

Page 24 Diagnostics
Task Description
As a final diagnostic function, the state of the modules of the ET 200SP are to be read-out. This
functionality is also implemented in the FB “FB_Diagnosis” with the help of the instruction
“ModuleStates”.
The evaluation of the status information of the individual modules is to take place through the
data block “PROFINET_Diagnosis”.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Exercise 6:
Reading-out
7.13.1. Exercise 6:the Module State
Reading-out of theState
the Module ET200SP
of the ET 200SP
Read-out module
state
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 25 Diagnostics
Task
You are to supplement your function block “FB_Diagnosis” by adding the function “ModuleStates”
and you are to evaluate the state of the modules of the ET 200SP in it. Decide for yourself which
mode you must use so that the status information displays which modules of the ET 200SP have
failed and which are currently running without errors.
The evaluation of the status information is carried out directly in the data block
“PROFINET_Diagnosis” via the TIA Portal functionality “Monitor block” .
What to Do
1. Open the function block “FB_Diagnosis” and program the functionality.
M O
o RU
u t inh
C o
a
Note
P e reir
o
eg as well as static variables in the function block!
As required, use temporary
D y
Contents 8
8. Web Services PROFINET ....................................................................................... 8-2
8.1. Diagnostics Anywhere, Anytime ........................................................................................... 8-3
M O
8.2. U
Activating the Web Server on the CPU ................................................................................. 8-4
R
o
tinh
8.3. Access with HTTPS .............................................................................................................. 8-5
8.4. ou
Introduction Page & Web Server (Access Level: Minimum) ................................................. 8-6
C
8.5.
e
Web Server (Access Level: Administrative)
r ira .......................................................................... 8-7
P e
8.6.
e g o
Diagnostics ............................................................................................................................ 8-8
8.7.
Dy ................................................................................................................. 8-10
Diagnostic Buffer
8.8. Module Information ............................................................................................................. 8-11
8.8.1. Firmware Update via Module Information ........................................................................... 8-12
8.9. Alarms ................................................................................................................................. 8-13
8.10. Communication Part1 ......................................................................................................... 8-14
8.11. Communication Part2 ......................................................................................................... 8-15
8.12. Set Topology ....................................................................................................................... 8-16
8.13. Actual Topology .................................................................................................................. 8-17
8.14. Topology and Module Information ...................................................................................... 8-18
8.15. Reading the Tag Status ...................................................................................................... 8-19
8.16. Writing the Tag Status ........................................................................................................ 8-20
8.17. MO
Reading the Watch Tables .................................................................................................. 8-21
U
8.18. o R
Writing the Watch Tables .................................................................................................... 8-22
ti n h
8.19.
C o u
Online Backup of the PLC ................................................................................................... 8-23
8.20.
r a
Customer Pages .................................................................................................................
e i 8-24
8.21.
Pe r
Filebrowser .......................................................................................................................... 8-26
8.22. eg o
DataLogs ............................................................................................................................. 8-28
D y
8.23. Task Description: Activating the Web Server of the S7-1513 and Uploading a Filebrowser
File ...................................................................................................................................... 8-30
8.23.1. Exercise 1: Activating the Web Server on the S7-1513 ...................................................... 8-31
8.23.2. Exercise 2: Uploading a File onto the Filebrowser ............................................................. 8-32
8.23.3. Exercise 3: Checking the File on the Memory Card ........................................................... 8-33
8.24. Web Server CPU S7-1510SP - 1PN ................................................................................... 8-34
8.25. Web Based Management (WBM) SCALANCE XC208....................................................... 8-35
8.26. Cable Test ........................................................................................................................... 8-36
8.27. Task Description: Activating the Web Server of the S7-1510SP + Cable Test via the
SCALANCE XC208 Web Server ......................................................................................... 8-37
8.27.1. Exercise 4: Activating the Web Server of the S7-1510SP .................................................. 8-38
8.27.2. Exercise 5: Executing the Cable Tester Function in the Web Server of the SCALANCE
XC208 ................................................................................................................................. 8-39
IK-TIAPN – Web Services
Web Server
8. Objectives
... be familiar with the possibilities of web diagnostics and be able

to apply them
... understand the web server of the S7-1500

M O
... U
be able to parameterize the web server of the S7-1500
R
o
...
tinh
be familiar with the Web Based Management of a SCALANCE
Switch
ou
ra C
... e i
be able to carry out a cable test via a SCALANCE Switch
o Per
eg
Dy
SITRAIN
IK-TIAPN / Web Services PROFINET Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

8.1. Diagnostics Anywhere,

Diagnostics Anytime
Anywhere, Anytime
ID: 59193560
Worldwide
diagnostics
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 3 Web Services PROFINET
Diagnostics via the Web Server
Available from everywhere and accessible at all times - this is what customers always expect
from the diagnostics of systems. When the system is connected to the Internet via a router and
taking into account the relevant security guidelines, you are one step closer to meeting these
expectations. We are talking about the integrated web server on the S7-1500 and the S7-1200 as
well as on most other SIMATIC products of the newest generation here.
Via the web server, it is possible to operate diagnostics with only the help of a web browser. No
further software or other aids are required. The different possibilities are explained in more exact
detail in the following sections.
Note
U MO
o Rfor the function manual about the
On the Service & Support pages, you will find the download
tin h
web server of the S7-1500 under the Entry-ID: 59193560.
C o u
i r a
P ere
y ego
D

8.2. Activating the the

Activating WebWeb
Server on the
Server onCPU
the CPU
Properties
Controller
Eigenschaften
Properties
Schnittstelle
Interface
M O
Activate
R U
web server
o
ou tinh
ra C
e i
Automatic
o Per
update
eg
Dy User Zugriff auf
Activate web
management Webserver
server access
aktivieren
Activating the Web Server
In the CPU’s delivered condition, the web server is deactivated for security reasons. This can be
activated with a few mouse clicks:
• Select (highlight) the CPU either in the Device view or in the Network view
• In the CPU Properties, select the section Web server
• Activate the web server and set the desired update interval
• Edit the User management
• Compile the configuration and reload, O
M
Note
o RU
u t inh
In order to be able to access the web server, the access via the interface through which you want
C o
to reach the PLC web server must however, still be activated!
a
Pe reir
The User management must be adjusted. By default, there is no administrator and every user of
the web server only has minimum authorization!
When activating they
web
o
egserver, the following pop-up window appears in which TIA Portal
separately pointsD
out the need to take appropriate safety measures against manipulation from
outside:

8.3. Access withwith

Access HTTPS
HTTPS
Intro page
web server
M O
R U
o
ou tinh
ra C
Access only with
ei
HTTPS
o Per
eg
Dy
HTTPS – Secure Connection
HTTPS stands for “Hyper Text Transfer Protocol Secure” and is used to transfer data tap-proof in
the World Wide Web. This function can also be used for the SIMATIC web server. If the access to
the web server is only to be possible using a secure connection, the relevant checkmark must be
set for the option “Permit access only with HTTPS”.
For an error-free HTTPS access to the SIMATIC, the following points must be ensured:
• The current time-of-day must be set in the CPU.
• The IP address of the CPU must be stipulated.
• A valid certificate must be installed in the web browser.
M O
RU
Certificate
t i n ho
ou via the Introduction page and then installed
The certificate for the web server can be downloaded
C
e a recommended)” is selected in the window that opens.
in the web browser used. It is also possible
ir(not
if the option: “Continue to this website
to access the SIMATIC without an installed certificate
r
Pe controllers with FW < 2.0.
This is only possible for S7-1500
You will find further y
o
eg on this topic and on self-signed certificates in the Entry-ID
information
103528224. D
Note
Even if the checkmark is not set for the option “Permit access only with HTTPS”, you can always
access the SIMATIC using HTTPS!

Introduction Page & Web Server (Access Level:

8.4. Minimum)
Introduction Page & Web Server (Access Level: Minimum)
User log in
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy minimale
Minimum
Berechtigungen
authorization

Introduction Page Web Server
Through the IP address of the configured CPU, you can establish a connection to its web server
after it was activated in the hardware configuration. The connection can be established either
through a standard connection with the prefix “http://” or through a secure connection with the
prefix “https://”.
By default, the introduction page appears the first time the web server is accessed. Here there
are links to the Industry Mall, to an Overview of the SIMATIC controllers, to the Service & Support
pages and the possibility of downloading the certifcate for the HTTPS connection.
If the option “Skip Intro” is activated, the introduction page is no longer displayed the next time the
web server is accessed. It is then routed directly to the Start page of the web server.
M O
Start Page Web Server
o RU
u t inh
With minimum authorization, only the Start page on the web server of the CPU can be looked at.
Without any authorization level, you (the user) only see(s) in which operating mode (e.g. RUN or
Co
STOP) the PLC is and which status it currently has.
a
Note
Pe reir
o
called by clickingD
yeg “Skip Intro”, you wish to go back to the introduction page, it can be
If, after activating the option
on the link “Intro”.

8.5. Web Server

Web (Access
Server Level:
(Access Administrative)
Level: Administrative)
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy maximale
Maximum
Berechtigungen
authorization

Authorizations Web Server
The assignment of individual access authorizations for the web server user must be made in the
Hardware configuration of the controller.
By default, no user is set up and all accesses to the web server only have minimum authorization.
In case not all authorizations are selected, the user is given limited authorization:
In the following sections, as an example, the individual pages of the web server are displayed
with administrative authorization.
Start Page Web Server

M O
o RU
If the authorizations “flash LEDs” and “change operating mode” are assigned for the logged in
user, he can let the LEDs of the Devices flash as well as set the operating mode to STOP or RUN
on the Start page of the web server.
u t inh
C o
a
P e reir
e g o
Dy

8.6. Diagnose
Diagnostics
Identifikation
Programmschutz
Speicher
Laufzeitinfo
Fehlersicher
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Seite 9 Webdienste PROFINET
Diagnostics
The "Diagnostics" web page of the web server is divided into five subcategories – "Identification",
"Program protection", "Memory", "Runtime information" as well as "Fail-safe".
Identification
The "Identification" tab contains various general CPU characteristics such as the order number or
the Firmware version which is currently loaded on the CPU.
The information which is found in "Identification" can be entered in the general properties of the
controller.
Program Protection
U MO
o R contains a know-how protection or
Here, you will find information about whether the PLC program
a copy protection. As soon as at least one block tisin
h
present in the PLC that has a know-how
protection, it is indicated here. The "Binding"o u
C number of thefieldCPUindicates
information whether a copy protection
i a
is activated through the binding to therserial or the Memory Card for at least
one block of the PLC program. ere
P
Memory y ego
D
Here you will find current values on the memory utilization of the controller. This information is
useful if larger expansions to the program are pending and you are unsure of how much memory
space is currently still available on the CPU and on the memory card.

Runtime Information
You will find current information on program load, communication load and cycle time in the
"Runtime information" tab. From this data you can determine whether runtime problems could
possibly exist for the execution of the user program.
Fail-safe
The safety program of an F-CPU consists of one or two F-runtime groups. The F-runtime group’s
signature, cycle times (F-monitoring time) and runtimes of these F-runtime groups can be found
in the "Fail-safe" tab.
Note
O
The "Diagnostics" page is activated (enabled) through the authorization "query diagnostics":
M
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

8.7. Diagnostic Buffer

Diagnostic Buffer
Selection of the entries

to be displayed
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Diagnostic Buffer
You can look at the diagnostic buffer of the PLC on the web server via the “Diagnostic buffer”
page. For every diagnostic buffer entry, there is a section with the detailed information on the
currently selected entry underneath the list.
A maximum of 50 entries is always displayed which can be selected via a drop-down menu:
M O
o RU
u t inh
C o
i r a
P e re buffer entries can be taken from the technical data of the
The maximum number of diagnostic
respective device.
y ego
Note D
The “Diagnostic Buffer” page is activated (enabled) through the authorization “query diagnostics”:

8.8. Module Information

Module Information
M O
RU
o
ou tinh
ra C
ei
o Per
eg Opens further
Dy details

Module Information
The state of the hardware components can be read-out in the web server via the “Module
information” tab. The state of the CPU as well as the connected PROFINET IO-System and its
components are displayed here. Through the “PROFINET IO-System” section, the diagnostics
can be queried right down to the module level.
Note
The “Module information” page is activated (enabled) through the authorization “query
diagnostics”:
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

8.8.1.Firmware Update
Firmware Updatevia
viaModule
Module Information
Information
M O
RU
Necessary
o
tinh
authorizations
ou
ra C
e i
o Per
eg
Dy
Firmware Update
If the user has the authorization to perform Firmware updates via the web server (see picture),
this can be carried out via the Module information page.
Via the Details view, in the “Firmware” tab, the Firmware downloaded from the Service & Support
pages can be selected and then loaded into the module.
Note
The authorization "perform a firmware update" automatically also activates (enables) the
authorization "change operating mode" as well as the authorization "query diagnostics":
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

8.9. Alarms
Alarms
M O
R U
o
ou tinh
ra C Alarm buffer
Pe rei PLC
e g o
Dy
Alarms
Via the “Alarms” page of the web server, all alarms can be displayed which are currently pending
in the alarm buffer of the controller. These are displayed in the correct order of their occurrence
with date and time. Alarms in the alarm window cannot be acknowledged via the web browser.
In order to get the complete picture of error analysis, it is always recommended to look at the
“Diagnostic buffer” page in addition to the “Alarms” page.
Note
The “Alarms” page is activated (enabled) through the authorization “query diagnostics”:
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

8.10.Communication Part1
Communication Part1
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Communication
On the “Communication” page of the web server, there are four subsections:
• Parameter
• Statistics
• Resources
• Connections
Parameter
M O
RU
Summarized information on the PROFINET and Ethernet interfaces of the associated CPU of the
web server is found in the “Parameter” tab.
o
u t inh
Statistics
C o
a
reir
In order to be able to look at the statistics of the data transmission via the interfaces, you can
e
switch into the “Statistics” tab. Here, there is an overview of the sent and received data packages
P
g o
of the CPU interfaces and the total amount of sent and received packages.
e
Dy

8.11.Communication Part2
Communication Part2
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Resources
An overview of all connection resources in use, all connection resources not in use and the
maximum possible connection resources is found in the “Resources” tab.
Connections
In the "State" section, there is an overview of the communication connections being established
and the already established or set up connections.
For each of these connections, the table contains information on the connection State, the Local
ID, the Slot of the Gateway, the Remote address (IP address), the associated Remote address
type, the Type of connection and the connection Type.
M O
Note o RU
u t inh
The “Communication” page is activated (enabled) through the authorization “query diagnostics”:
Co
a
P e reir
e g o
Dy

8.12.SetSet
Topology
Topology
M O
Sprung zum U Status of all
oR
Jump to Module
Baugruppen- Devices of the
tin h
information
zustand IO-System
C o u
eira
P e r
eg o
Dy
Topology
On the “Topology” web page, you are given information about the topological structure of the
system. Differentiation is made between the Set(point) Topology and the Actual Topology. The
Set Topology is only displayed if a topology was actually configured in the controller in TIA Portal.
The Actual Topology, on the other hand, is always detected and presented in the web server. The
“Topology” web page consists of the following tabs:
• Graphic view
• Table view
• Status overview
M O
o RU
You can only switch between the Set and Actual Topology in the Graphic view. The Actual
Topology is always presented in the Table view tab! Only the devices of the PROFINET-IO
t inh
System of the CPU are displayed in the “Status overview” tab.
u
C o
a
reir
Graphic View
P e
In the “Graphic view” tab, the topology of the system is graphically prepared and presented. You
e g o
can switch here between the presentation format Set Topology and Actual Topology and so carry
Dy
out a comparison between the project and the system.
Status Overview
In the “Status overview” tab, all devices of the PROFINET IO-System connected to the CPU are
presented. Here, a quick overview of the state of the IO-System can be made without distractions
resulting because of topological connection relationships.
Note
If a Set Topology is not configured in the CPU, all PROFINET-IO devices are simply presented in
the “Graphic view” tab when the Set Topology is selected.

8.13.Actual Topology
Actual Topology
M O
RU
o
Zustand
ou tinh
State of Devices
Devices
ra C
e i
o Per
eg
Dy
Actual Topology
The Actual Topology of the system can be displayed in two different formats – graphic and table.
Table View
In the Table view of the Actual Topology, not only the real connections between the devices are
displayed but also the statuses of the individual devices. Differentiation is made between the four
following statuses which can be presented:
• Configured and accessible PROFINET device
MO
• Not configured and accessible PROFINET device
o RU
• u
Configured but not accessible PROFINET device t inh
Co
• a
reir
Device for which no ‘neighborhood’ relationships
can be detected or the ‘neighborhood’ relationships are not
P e
e g o
complete or can only be read-out with errors.
Note Dy
The “Topology” page is activated (enabled) through the authorization “query diagnostics”:

8.14.Topology andand
Topology Module Information
Module Information
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Switch to the Module Information
With a mouse-click on the State symbol of the represented device, you can switch to the
associated Module information. That is, the web server page “Module information” is
automatically opened with the correct Device and the error source can be analyzed!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

8.15.Reading the the

Reading TagTag
Status
Status
Value at time of
update
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Tag tables of the
Dy
controller

Tag Status
In the web server, the status of the tags defined in the controller can be monitored via the “Tag
status” page. Only a symbolic addressing is permitted. Absolute addresses cannot be monitored
via the “Tag status”. Tags from all tag tables defined in the project can be monitored.
When you exit the “Tag status” page, any tags which have been entered are not stored. That is,
the next time the page is opened, the page will be empty. If you want to keep the configuration of
the tags to be monitored, you either have to create a bookmark in the browser for the configured
tag status or you have to save the address line from the browser. That way you can re-access the
same tag configuration.
Note
U MO
o
The “Tag status” page is activated (enabled) through the R
authorization “read tag status”:
ti n h
C o u
i r a
P ere
y ego
D

8.16.Writing the the

Writing TagTag
Status
Status
M O
RU
o
ou tinh
erlaubt
Permitsdas
youWert
to
ra C
change
ändern i
values
e im in
Per
Variablenstatus
the tag status
o
eg
Dy
Write Tag Status
On the “Tag status” page in the web server of the CPU, the authorization “write tag status”
permits you not only to read out the value of tags but also to change the value of these tags via
the web server.
However, you can still only use tags which have been declared symbolically in the controller.
Note
It is possible to only activate the authorization “write tag status”. However, this doesn’t make
sense since the “Tag status” menu item only appears in the web server when the authorization
“read tag status” has been assigned!
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

8.17.Reading the the

Reading Watch Tables
Watch Tables
Without a
symbol, no value
can be
presented
M O
R U
o
ou tinh
ra C
e i
Per
y go
eSteuerung
Eigenschaften
Properties
D Controller
Watch Tables
On the “Watch tables” page of the web server, you can also use the watch tables created in the
project for the controller for the web server. For this, the tables which are also to be displayed in
the web server must be added in the hardware configuration of the controller under the “Web
server” menu item and there under Watch tables.
Currently, only a read-only access to these tables is possible. That is, these cannot be expanded
via the web server.
In addition, the tags in the table can only be read and not controlled (written) via the Watch tables
in the web server, unlike the Watch tables in the project.
M O
If there are absolute addresses without symbol in the symbol table which is displayed in the web
RU
server, then no current values are displayed for these in the Watch tables in the web server. This
o
monitored. u t inh
contrasts with Watch tables in the project where absolute addresses without symbol can also be
Co
a
Note
Pe reir
e g o
The number of Watch tables which can be monitored in the web server depends on the size of
the SIMATIC Memory Card used. When the existing memory space is exceeded by configured
Dy
alarms and tags, Watch tables in the web browser are only partially displayed.
The “Watch tables” page is activated (enabled) through the authorization “read tags”:

8.18.Writing the the

Writing Watch Tables
Watch Tables
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy Permits
erlaubtvalues
das Wert
to be
changed
ändern
in Watch
in
Beobachtungstabellen
tables
Write Tags
If the user is assigned the authorization “write tags”, it is now also possible for him, on the “Watch
tables” page, to change the value of the tags in this table.
Note
So that it is possible to change the values of tags in a Watch table, this must be set in the web
server settings of the controller:
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy
It is possible to only activate the authorization “write tags”. However, this doesn’t make sense
since the “Watch tables” menu item only appears in the web server when the authorization “read
tags” has been assigned!

8.19.Online-Sicherung
Online Backupder PLCPLC
of the
Online-Sicherung nur
in Stopp der CPU
M O
möglich
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Online Backup
The web server of the controller enables the user to create or to restore (load) a backup of the
controller without having to start and operate TIA Portal. Requirement for this, of course, is the
appropriate authorization that must be assigned to the user.
Any number of backups of the controller can be created and as a result different configurations
can be kept for one CPU.
Note
An online backup of the controller is only possible in the "STOP" mode. For that reason, in
O
addition to the right to create or restore an online backup, the user must also be assigned the
M
right to change the operating mode.
o RU
u t inh
C o
a
P e reir
e g o
Dy

8.20.Customer Pages
Customer Pages
ID: 68011496
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Customer Pages
In the "Customer pages" area of the web server, HTML pages, which you yourself create, can be
displayed.
On these pages, tags of the controller can be read and written. The pages are generated and
edited with an HTML editor. Then TIA Portal generates data blocks (Web-Control-DB and
Fragment-DBs) from these pages which are loaded into the controller. Using the instruction
“WWW”, the web server of the controller is then synchronized and initialized with the user
program. The first call of the instruction “WWW” generates the link to the customer pages on the
web server of the CPU (see picture). A click on the link then starts the customer pages in a new
browser window.
M O
o RU
u t inh
Note
C o
a
e reir
The “Customer pages” page is activated (enabled) through the authorizations “open user-defined
web pages” as well as “write in user-defined web pages”. With the authorization “write in user-
P
g o
defined web pages”, the authorization “open user-defined web pages” is also automatically
e
assigned:
Dy

An entry which deals with customer pages on the S7-1500 in more detail can be found on the
Service & Support pages under the Entry-ID: 68011496.
Important
Writing accesses in customer pages can influence the process parameters and with that the
operation of the CPU.
For that reason, it is strongly recommended that a password is always assigned in the User
management for users with write-access in customer pages to protect against manipulations from
outside!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

8.21.Filebrowser
Filebrowser
Uploaded
manuals
M O
R U
o
ou tinh
ra C
e
Activate
r i
e
oP
Filebrowser
eg
Dy Upload/
Delete/Change
permitted
Filebrowser
The “Filebrowser” page is activated (enabled) through the authorization “read files”. Via the web
browser, you can now look at which additional files are on the SIMATIC Memory Card in the CPU
and open them. This is very helpful, for example, for commissioning or for service calls, since
additional information material such as manuals, system descriptions and similar can be stored
here.
With the authorization “write/delete files”, additional authorizations are activated (enabled). These
include:
• The uploading of files to the SIMATIC Memory Card of the controller
• The deleting of files on the SIMATIC Memory Card
U MO
• The renaming of files on the SIMATIC Memoryo R
h Card
tiinnthe web server of the controller! Of course, it
is always possible to write, to delete or to C
o u
All these authorizations refer to the “Filebrowser”
i r a rename files by inserting the SIMATIC Memory Card of
ere
the CPU into a card reader, regardless of the user authorizations in the web server!
P
y ego
D

Note
The authorization “write/delete files” does not yet activate the menu item “Filebrowser” in the web
server:
M O
R U
o
ou tinh
ra C
e i
Per
ego
The File server is only activated with the authorization “read files”.
y
The program filesDwhich are generated when the project is downloaded onto the controller are not
displayed in the File browser for security reasons.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

8.22.DataLogs
DataLogs
ID: 59193101
M O
R U
o
Empty Logfile
ou tinh
ra C
e i
Activate DataLogs
o Per
page
eg
Dy Upload -
Delete - Change

DataLogs
The “DataLogs” page on the web server makes it possible to look at the “DataLogs” generated via
the program and to store it on your local computer. Since a local temporary copy is generated on
the computer when the Log file is opened via the web server, you can still save information in this
Log file from the controller side. The format in which the Log files are generated is the CSV
format (comma separated values).
Via the web server, the Log files present on the controller can also be emptied, if the
authorization “write/delete files” was assigned. However, the Log files are not completely deleted
from the SIMATIC Memory Card through this action. Only the contents, that is, the entries of the
Log file are deleted. This action is however not possible if the selected Log file is still open in the
controller! M O
RU
DataLogs in the Filebrowser
t i n ho
If there are Log files on the SIMATIC Memory
C o uCard, they are also displayed on the “Filebrowser”
page in a separate folder.
r e ira
o Pe
y eg
D

Note
The “DataLogs” page uses the same authorizations as the “Filebrowser” page:
M O
R U
o
ou tinh
ra C
e i
Per
On the Service & Support pages, you will find a document which covers the structure and use of
eg o
the CPU memory of the S7-1500 under the Entry-ID: 59193101. This PDF also contains a
chapter which deals with the topic of data logging and also includes a small programming
example. Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Task Activating
Description: the Web
Activating Server
the Web of theof the
Server
S7-1513 andand
S7-1513 Uploading a Filebrowser
Uploading File File
a Filebrowser
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
You are to activate the web server of the S7-1513. You are then to create a new User and assign
him the necessary rights so that he can use the Filebrowser. You can assign any user name and
password you like. Finally, you are to load a file, such as, your archived project onto the memory
card of the controller via the Filebrowser of the web server.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 1:
Activating
8.23.1. Exercisethe Web Server
1: Activating the on
Webthe S7-1513
Server on the S7-1513
Activate
web server
M O
R U
o
ou tinh
ra C Create new user
i
P ere
o
Dyeg

Task
You are to activate the web server on the S7-1513 controller. Then, you are to set up a new User.
Make sure that he has the necessary authorizations so that he can load files onto the File server
of the web browser and, with that, onto the SD card of the controller.
What to Do
1. Activate the web server on the controller.
2. Activate the option: “Permit access only with HTTPS”.
3. Create a new User and assign the required authorizations as stated in the task.
M O
RU
o
inh
5. Download your changes into the controller.
o u t
Note
a C
activated. Pe reir
Don’t forget to check whether the access to the web server via the desired interface is also
e g o
Dy

Exercise
8.23.2. 2: 2:
Exercise Uploading
UploadingaaFile
File onto theFilebrowser
onto the Filebrowser
Uploaded file
M O
R U
o
ou tinh
ra C
e r ei Upload file to
SD card
o P
eg
Dy
Task
Via the web server, with the help of the Filebrowser, you are to upload any file from your
computer onto the SD card of the controller.
Recommendation: Archive your project and then upload it into the controller.
What to Do
1. Open your Internet Explorer (a browser of your choice).
2. Open the web server of the controller.
3. Log in to the web server using the previously created User.
M O
RU
4. Open the Filebrowser.
o
inh
5. Upload any file, via the Filebrowser, onto the SD card of the controller.
o u t
a C
P ereir
e g o
Dy

Exercise
8.23.3. 3: 3:
Exercise Checking
Checkingthe
theFile
File on the Memory
on the MemoryCard
Card
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
File was uploaded
onto the card

Task
You are to check whether the upload of your file really worked. You are to remove the SD card
from the controller and insert it in the SD card reader on your Field-PG (left side). Then, with the
Windows Explorer, you are to check whether your uploaded file is on the SD card. After that, you
are to re-insert the card in the controller and start the controller.
What to Do
1. Remove the SD card from the controller.
2. Insert the SD card in the card reader of your Field-PG (left side).
MO
3. With the help of the Windows Explorer, check whether your file is on the SD card.
U
4. If it is not on the SD card, repeat the previous exercise!R
t i n htheo Field-PG and re-insert it in the controller.
ou
5. If the file is on the SD card, remove the card from
C
6. Start the PLC.
r e ira
o Pe
y eg
D

8.24.Web Server
Web CPUCPU
Server 1510SP-1PN
S7-1510SP - 1PN
Administrative
authorizations
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Web Server CPU 1510SP - 1PN
From its handling, the web server of the CPU S7-1510SP - 1PN is not different from the web
server of the CPU S7-1513 - 1PN or from that of another CPU. The basic settings, such as,
activating the web server, setting up the User authorizations, setting the accessibility of the web
server, etc. are exactly identical!
The web servers of the various controllers can differ regarding which authorizations can be
activated (enabled) for the different Users.
Below is a comparison between the possible authorizations for an S7-1513 - 1PN V1.7 (left) and
the S7-1513 - 1PN V1.8 (right):
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Unlike an S7-1513 - 1PN V1.7, an S7-1513 - 1PN V1.8 also permits the writing of tags and the
writing of tag statuses.

8.25.Web Based
Web Management
Based (WBM)
Management SCALANCE
(WBM) XC208XC208
SCALANCE
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Web Based Management (WBM) SCALANCE XC208
IE Switches have an integrated HTTP-Server for the Web Based Management. If an IE switch is
addressed via a web browser, it returns HTML pages to the client computer depending on the
user inputs.
The user enters his configuration data into the HTML pages sent by the IE switch. An IE switch
evaluates this information and dynamically generates answer pages. The particular advantage of
this functional principle is that no special software except a web browser is required on the client
side.
Requirements for a WEB

M O
following requirements must be fulfilled: oRU
So that the Web Based Management of an Industrial Ethernet switch can be used, at least the
t i n h
• An IE switch must have and IP address
Management. C ouso that you can use the Web Based
e a
irWeb
• In order to be able to userthe
the IE switch and otheP
e Based Management, an Ethernet connection between
client computer must exist.
• y eg that you use a current browser.
D
It is recommended
• All pages of the Web Based Management require JavaScript. For that reason, make sure
that JavaScript is activated in the browser settings.
• Since the Web Based Management is HTTP or HTTPS-based, you must enable the
access to Port 80 or 443 when a firewall is installed.
Note
The browser must not be setup in such a way that it is to reload the page from the server every
time the page is accessed. The currentness of the dynamic page contents is ensured through
other mechanisms.

8.26.Cable TestTest
Cable
Port selection
M O
RU
Cable must not
o
tinh
be connected
C ou
e ira
Per
Cable error-free
and connected
eg o
Dy

Cable Test
Via the SCALANCE XC208, you can carry out an error diagnosis of the cables on the individual
electrical Ethernet ports. This option is called "Cable Tester" and is found in the Web Based
Management in the menu "System" and there under the entry "Port Diagnostics". This makes it
possible to localize short-circuits and cable interruptions.
This function is not possible for IRT devices.
In order to be able to carry out the error diagnosis, the Ethernet cable must be plugged into the
SCALANCE XC208. However, there must not be any physical connection (link) to another
network component. That is, the other cable end must not be connected!
MO
Then the port, to which the cable is connected, is selected via the Web Based Management and
the test is performed.
o RU
u t inh
C o
a
P e reir
e g o
Dy

Task WebActivating
Description: Server of the
theS7-1510SP + of the S7-1510SP
Web Server
Cable Test via
+ Cable TestSCALANCE XC208 Web
via the SCALANCE ServerWeb Server
XC208
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy

Task Description
You are to activate the web server of the S7-1510SP CPU and become familiar with its user
interface. Then you are to switch into the WBM of the SCALANCE XC208 and there carry out a
cable test for all cables connected to the SCALANCE XC208!
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Exercise 4:
Activating
8.27.1. Exercisethe Web Server
4: Activating the of
Webthe S7-1510SP
Server of the S7-1510SP
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to activate the web server of the S7-1510SP controller and compare its user interface
and options with the web server of the S7-1513 SPS.
What to Do
1. Switch to the Devices view of the S7-1510SP.
2. Activate the web server of the controller and also make sure that it is accessible via the
connected PROFINET interface.
3. Create a new User with an “administrative” access level.
M O
RU
4. Download the changes into the controller.
t i n ho
5. Start the Internet Explorer and call the web server of the controller via its IP address.
6. Log in to the web server using the newly o
C u User.
created
a such as “Diagnostic Buffer”, “Module information” as
7. Test the functionalities of the webirserver
e
r
Pe these to the web server of the S7-1513 which you already
well as “Topology” and compare
know.
eg o
D y

Exercise
8.27.2. 4: 5: Executing the Cable Tester Function in the Web Server of the
Exercise
Activating
SCALANCEthe XC208
Web Server of the S7-1510SP
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy

Task
Via your web browser, you are to call the function ‘Cable Tester’ in the Web Based Management
of the SCALANCE XC208. Then you are to test all cables connected to the SCALANCE XC208
for their length and their functioning.
What to Do
1. Open the Web Based Management of the SCALANCE XC208 in your web browser.
2. Log in to the Web Based Management as Administrator.
MO
3. Switch to the Cable Tester function in the WBM of the SCALANCE XC208.
U
o
4. Carry out a wire test/cable test for all cables connected Rto the switch.
h
tinother options of the Web Based Management
5. After that, you can still become familiar withuthe
of the switch. C o
i r a
Note P ere
y egomost Siemens IE switches have the default administrator access:
In their delivered condition,
admin / admin. ThatD is, both the User name and the User password for administrative
authorizations on the switch is "admin". It is imperative that this is adjusted to your own needs
when the switch is commissioned in a system! This is the only way to prevent an unauthorized
access to the switch and with that the system!
Newer switches of the SCALANCE family automatically
prompt the user to assign a new password after the first
Administrator login!

Contents 9
9. Ring Redundancy MRP .......................................................................................... 9-2
9.1. Ring Topology ....................................................................................................................... 9-3
M O
9.2.
R U
MRP – Media Redundancy Protocol ..................................................................................... 9-4
o
tinh
9.3. Operation of an MRP Ring .................................................................................................... 9-5
9.4. ou
Controlling the Ring with the MRP Manager ......................................................................... 9-6
C
9.5.
e ira
Detecting a Defective Ring Line............................................................................................
r 9-7
Restoring the Defective P
e
9.6.
e g o Ring Line ........................................................................................ 9-8
9.7.
Dy the S7-1513 ............................................................................................... 9-9
MRP Options on
9.8. Domain Settings .................................................................................................................. 9-10
9.9. Watchdog Time ................................................................................................................... 9-11
9.10. Task Description: Introducing a Loop and then Activating MRP ....................................... 9-12
9.10.1. Exercise 1: Introducing a Loop ........................................................................................... 9-13
9.10.2. Exercise 2: Activating MRP with the S7-1513 as MRP Manager ....................................... 9-14
9.10.3. Exercise 3: Running Light for Visualizing the Re-configuration Times ............................... 9-15
9.10.4. Exercise 4: Adjusting the Watchdog Time .......................................................................... 9-16
9.11.1. MRP Manager (Auto) .......................................................................................................... 9-18
9.11.2. MRP on the SCALANCE XC208 ......................................................................................... 9-19
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Ring Redundancy MRP

Ring Redundancy MRP

9. Objectives
... understand what a ‘Loop’ is and why it must be avoided without

MRP
... be able to configure and parameterize MRP

M O
... U
be familiar with and understand the functional principle of MRP
R
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Ring Redundancy MRP Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
IK-TIAPN - Ring Redundancy MRP

9.1. Ring Topology

Ring Topology
ID: 33696406
Circling
telegrams
A LOOP is
introduced
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 3 Ring Redundancy MRP
Ring Topology without Redundancy Protocol
If devices are connected to one another in the Ethernet, it is important to avoid introducing a ring,
also called a loop, between the devices. If this should accidently happen circling telegrams
suddenly result within the network. This is especially the case when a device sends a broadcast
in the loop which is then forwarded by every additional device. Since the ring / loop is not
terminated, the broadcast now circles in the ring. With several circling telegrams, the load is then
so high that the network collapses and no more communication is possible via the network! This
can happen within seconds of a ring being introduced but it can also take several minutes. A
collapse of communication is, however, unavoidable with a ring without a redundancy protocol!
Furthermore, even when the loop is dissolved, it may be necessary to disconnect network
O
devices from the network before they can then be registered again on the network.
M
Redundancy Protocols / Ring Protocols o RU
u t inh
To prevent the circling of data telegrams, redundancy protocols are used in the ring. These have
Co
different ways of working; however, they all have the same effect: the loop is dissolved and only if
a
P ereir
required, that is, with the failure of a cable, is the loop closed once more.
e g
of the PROFINET specification.
o
In automation, the protocol MRP (Media Redundancy Protocol) is often used. This protocol is part
Dy
Note
On the Service & Support pages, you will find an entry under the EntryID: 33696406 which takes
a closer look at the topic of ring redundancy with the Media Redundancy Protocol (MRP).

9.2. MRP – Media

MRP – Media
Redundancy Protocol
Redundancy Protocol
Devices in an MRP Ring can take on the role of either Manager or Client
As a rule, PLCs
can take on both All devices of an MRP ring must support
roles MRP and MRP must be activated
As a rule, Response times of <= 200ms for a device

distributed I/Os number <= 50 devices
can only be a client
M O
o RU
Each Ring must include at least one
nh
As a rule, Managed MRP Manager
Switches can take
u t i
on both roles
C o
eira Connection of the devices must only take
P e r place via the ring ports
e g ocan
As a rule, Panels
Dy only be a client
Standard: EC 61158 Type 10 "PROFINET"

The Ring Redundancy Procedure MRP
The Media Redundancy Protocol (MRP) is a standardized redundancy protocol for automation
and is specified in the standard IEC 61158 Type 10 “PROFINET”. Similar to STP or RSTP
((Rapid) Spanning Tree Protocol), the protocol is established on Layer 2 of the OSI-layer model.
The goal of ring redundancy procedures is to increase the availability of the system. This is
achieved by introducing an alternative route for the telegram traffic. So that circling telegrams
cannot be introduced via this alternative route, the route which the telegrams can take must be
managed. In a ring, this task is handled by the “Manager”. In an MRP ring, it is also called MRP
Manager. All other devices in a ring are referred to as “Clients”. The ports at which the individual
devices of the ring are connected to one another are referred to as “ring ports”.
M O
Note
o RU
u t inh
Whether a device can take on the role of “Manager”, “Client” or “both” in a ring can be found in
o
the device specifications. As soon as a device can take on the role of MRP Manager, it is also
C
a
reir
usually possible to define this device as an MRP Client.
P e
e g o
Dy

9.3. Operation of an
Operation ofMRP RingRing
an MRP
Controller is defined
as Manager
MRP Manager
separates the ring
at a port
ET200SP is defined
as Client
M O
Redundant line
R U
(really exists!)
o
ou tinh Scalance is defined
ra C as Client
TP700 is defined as
e i
Client
o Per
eg
Dy
Requirements MRP Ring
Requirements for smooth operation with the Media Redundancy Protocol MRP are:
• The ring in which MRP is used must only consist of devices which support this function.
• "MRP" must be activated for all devices in the ring.
• All devices must be connected to one another via their ring ports.
• There must be at least one redundancy manager (Role "Manager (Auto)").
• If there is one device in the ring that has the role “Manager”, no further devices with the role
“Manager” or “Manager (Auto)” may be in this ring!
M O
• RU
The ring may consist of a maximum of 50 devices. Otherwise, re-configuration time of greater
than or equal to 200ms can result.
t i n ho
• All partner ports within the ring must have
C u same settings.
othe
Re-configuration Time r e ira
o Petime which the manager in an MRP Ring requires to detect a
cable failure and to y eg the alternative route for the telegrams active. This time can be up to a
The re-configuration time
switch
is the
maximum of 200ms.D
Conditions
• RT operation is possible when MRP is used.
• The IRT operation is not possible in conjunction with MRP.
• The TCP/IP communication is possible in conjunction with MRP, since lost data packets are
repeatedly sent, if necessary.
• Prioritized startup and the use of MRP is not possible.

9.4. Controlling the the

Controlling RingRing
withwith
the MRP Manager
the MRP Manager
Testtelegramm
Test telegram is
wird an beiden
sent to both ports
Ports versendet
MRP Manager
sends
sendet
test
Testtelegramm
telegram
During operation, test telegrams

M O
U
are sent in parallel to both ports
R
o
and must be received at both
ou tinh
ra C
e i
o Per
eg
Dy
The Way the MRP Manager Works
The task of the manager is to monitor the ring topology.
During normal operation of the ring, that is, without ring interruption due to an error, the
redundancy manager separates its two ring ports from one another so that the ring topology
becomes a line from the point of view of communication. As soon as the ring is open because of
the failure of a device or a cable break and the data communication is no longer ensured, the
redundancy manager re-configures the data routes within 200ms. For this, it connects its two ring
ports through and creates a new linear network structure through this replacement route.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

9.5. Detecting a Defective

Detecting RingRing
a Defective Line Line
MRP Manager detects

that no more test
telegrams are received
Redundant line is
M O Cable break between 2
devices
switched active
RU
o
ou tinh Test telegram traffic is
ra C terminated
ei
o Per
eg
Dy
Detecting a Defective Ring Line
Test telegrams are used to detect a defective ring line.
The redundancy manager monitors the ring for interruptions. For this, it sends test telegrams from
both ring port 1 and ring port 2. The test telegrams pass through the ring in both directions until
they arrive at the respective other ring port of the redundancy manager (see picture). If the ring is
interrupted, either due to the failure of the connection between two devices or even due to the
failure of an entire device, the sent test telegrams of the one ring port no longer reach the other
ring port. Through this procedure, the MRP Manager can detect an interruption of the ring and
then connect through its ring ports.
O
So that the devices in the ring do not try to send their telegrams to other devices via the defective
M
o RU
line but also take the “new” route, MRP Manager sends ARP delete telegrams to each device.
These delete the Forwarding Database (FDB) of the switches so that the new accessibility of the
t inh
existing devices is learned. Subsequently, the devices send the telegrams via the replacement
u
line.
Co
a
Note
P e reir
g o
Unlike PROFIBUS, the electrical failure of a device in PROFINET also causes the failure of the
e
Dy
communication path via this device. Due to the failure of the device, the switch of the device also
fails. Incoming telegrams can then no longer be forwarded!

9.6. Restoring the the

Restoring Defective RingRing
Defective Line Line
MRP Manager detects

that test telegrams are
once again arriving
Redundant line is
Defective line was
MO
switched to Standby
exchanged
once again
RU
n h o
u ti Test telegram traffic
C o can circulate once
eira more
P e r
eg o
Dy
Restoring the Defective Ring Line
As soon as the interruption is eliminated, the original transmission routes are re-established, the
two ring ports in the redundancy manager are separated from one another and the redundancy
clients are informed of the change. The redundancy clients then go back to using the original
routes to the other devices. Just as for the line failure, this is also implemented by sending delete
telegrams from the MRP Manager.
The Manager once again sends ARP delete telegrams and so deletes the FDB of the MRP
clients. Subsequently, they once again learn the “old” telegram route to all devices.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

9.7. MRP Options

MRP on the
Options on S7-1513
the S7-1513
Properties
Interface
M O
RU
o
tinh MRP Domains
a Cou MRP Role
e reir
oP
Ring ports CPU
eg
Dy Diagnostics interrupt
Further Domain
settings
MRP Options
The settings for MRP are made in the PROFINET interface of the device. There, the entry “Media
redundancy” is located, where the MRP functionality of the controller can be parameterized. If the
selected device does not support the ring redundancy procedure MRP, this entry does not exist in
the Advanced options.
The following items are found under the entry “Media redundancy”:
• The MRP Domains to which the Device is currently assigned. This can be changed in the
Network view.
•
depending on the possible roles for the device. M O
The Media redundancy role of the device. The drop-down menu for this entry differs
The device can be both “Manager” and “Client”:

o RU
u t inh
C o
a
P e reir
The device can only take on the role of a “Client”:
e g o
Dy
• The ring ports, via which the device is connected with the MRP Ring, are displayed here. If
the Device has more than two PROFINET ports, the ports presented here must be
connected with the ring!
• If the option “Diagnostic interrupts” is to be activated, the Device signals further diagnostic
interrupts, such as, wiring or port errors, a neighbor of the ring port does not support MRP,
ring interruptions and ring restoration, …. Redundancy managers signal more diagnostic
interrupts than clients.
• You can switch to the settings of the MRP Domains in the Network view via the button
“Domain settings”.

9.8. Domain Settings

Domain Settings
MRP
MRP-Domäne
Domains
Devices in the
MO
ring
RU
n h o MRP role of the
u ti devices
C o
eir a
P e r
Setting for Default
Domains
eg o
Dy
MRP Domains
In the Network view, the settings for the MRP domains present in the PROFINET IO-System can
be made.
Here, you get an overview as well as change possibilities for the following settings:
• How many MRP Domains are present in the selected IO-Network and which domains the
Default Domains represent are displayed.
• For each Domain, further information, such as, the number of interfaces within the ring, the
number of managers, etc. is presented:
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
• The IO-Network, to which the MRP Domain is assigned, is displayed.

• Devices which are members of the selected Domains. Here, the associated Domain of the
individual Devices as well as their role in the MRP Domain can additionally be adjusted and
changed.

9.9. Watchdog Time

Watchdog Time
M O
Ansprechüber-
RU Watchdog time
wachungszeit
o
ou tinh
ra C
ei
o Per
eg
Dy
Watchdog time
In the menu item “Watchdog” in the PROFINET interface of an IO-Device, you will find the item
“Accepted update cycles without IO data”. Since the changeover times, in the MRP operation,
between the defective line and the replacement line can be up to 200ms in the Worst Case, this
number must be adjusted if you wish to have a smooth changeover.
With the default setting of 3 accepted update cycles without IO data, the IO-Device always goes
into fault for an MRP changeover and the outputs are briefly de-energized. With an increased
number of update cycles, the IO-Device does not “notice” the breakdown of the line and the
outputs continue to have power. Of course, during the changeover time, the IO-Controller cannot
control the IO-Device.
M O
Note
o RU
u t inh
If the watchdog time is changed, you always have to check whether a critical IO-Device state can
occur in the selected time frame! If this is the case, a shorter time must be selected!
Co
a
P e reir
e g o
Dy

Task Description:
9.10. Task Description:
Introducing a Loop
Introducing a and
Loopthen
andActivating MRP MRP
then Activating
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Ring Redundancy MRP Page 14 Siemens AG © 2016
Task Description
In order to become more familiar with the MRP and rings in networks, you are first of all to
introduce a ring to your system and then modify the introduced ring into an MRP ring in order to
achieve the required ring redundancy.
Finally, you are to program a running light on the ET 200SP so that the re-configuration times of
the MRP ring can be visualized.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise
9.10.1. 1: 1:
Exercise Introducing
IntroducingaaLoop
Loop
M O
RU
o
ou tinh
ra C
e i
o Per
Es A
entsteht
loop isein
Loop!
introduced!
eg
Dy New
neue line
Leitung

Task
With the help of the SCALANCE XC208, you are to introduce a ring which includes the following
devices:
• S7-1513
• ET 200SP
• TouchPanel
• SCALANCE XC208 Switch
What to Do
MO
1. Take two suitably long PROFINET cables.
o RU
t inh
2. Connect the Port “P1” of your S7-1500 training case to the Port “P5” of the SCALANCE
u
switch.
C o
a
switch. Pe reir
3. Then connect the Port “P2” of your S7-1500 training case to the Port “P3” of the SCALANCE
o
eg goes into fault.
y
4. Monitor how the system
D
Note
The system must go into fault in any case. If this is not the case, check all PROFINET
connections of the above-mentioned devices. These must all be connected to one another!

Exercise 2:
Activating
9.10.2. ExerciseMRP with theMRP
2: Activating S7-1513 as S7-1513
with the MRP Manager
as MRP Manager
HMI muss separat

HMI must separately be
auf Client umgestellt
M O
changed over to Client
werden
RU
o
ou tinh
ra C
e i
o Per
eg
Dy PLC is MRP
Manager

Task
In your project, you are to activate the MRP functionality for all devices that are part of the ring.
For this, the S7-1500 is to take on the role of “Manager”. All other devices of the ring are given
the role of “Client”.
What to Do
1. Switch to the Topology view.
2. Update the offline topology of your project. For this, use either the Offline/Online comparison
function or enter the connections manually.
3. Switch to the Network view in your project.
U MO
o
4. Define the roles of the devices either individually via theRvarious PROFINET interfaces of the
devices or collectively via the MRP Domain settings
t h
in the IO-Network.
of
5. Download the modified configuration toCall
u
onecessary devices.
6. Test the MRP functionality. reir
a
o Pe
Note
y eg
D again access the controller, you must dissolve the loop!
Before you can once
The role of the TP700 Comfort cannot be set via the MRP Domain in the Network view. For this,
you must switch to the PROFINET interface Properties of the Panel.

Exercise 3: Running Light for Visualizing the
Re-configuration
9.10.3. Times
Exercise 3: Running Light for Visualizing the Re-configuration Times
Insert in the
project
M O
R U
o
tinh Running light
a Cou from the library
e r eir
o P
eg
Dy
Task
You are to use the “RunningLight_ET 200SP” block from the IK-TIAPN library in order to generate
a running light on the ET 200SP. This running light improves the visual presentation of the re-
configuration times of the MRP ring.
What to Do
1. Open the “IK-TIAPN” library, if it is closed.
2. Using drag & drop, copy the “Running Light” tag table into your project.
3. Then drag the “RunningLight_ET200SP” block from the “Chapter9” folder into your project.
M O
RU
4. Compile and download your project. Then save it.
o
inh
5. Once again test the MRP functionality with the help of the running light. The running light is
o u t
switched on and switched off via the input “S_Runninglight_On” (%I 0.7).
C
The re-configuration times which the Manager requires should now be easier to recognize.
a
Note
Pe reir
o
g following path: “C:\Archives\TIA_Portal\IK-TIAPN”. There, it is either
The library is stored inethe
archived (zipped)D y must
and first still be retrieved (unzippped) or it is already retrieved and only
has to be opened.

Exercise
9.10.4. 4: 4:
Exercise Adjusting
Adjustingthe
theWatchdog Time
Watchdog Time
M O
R U
o
ou tinh
ra C
ei
Adjust the update
P e r cycles
eg o
Dy
Task
You are to change the “Watchdog time” option of the PROFINET interface of all required IO-
Devices in such a way that a smooth changeover is ensured. That is, when a ring line is pulled
and inserted, the breakdown of the running light is no longer to be recognized.
What to Do
1. Switch to the Network view of your project.
2. Change the “Accepted update cycles without IO data” of all required IO-Devices in such a way
that these correspond to the task.
O
UM
3. Compile and download your project. Then save it.
R
ho
4. Test whether your changes ensure a smooth changeover.
t i n
C ou
r e ira
o Pe
y eg
D

9.11. Sie noch mehr

WennAdditional wissen wollen
Information
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
IK-TIAPN / Ringredundanz MRP Seite 19 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

MRP
9.11.1. Manager
MRP (Auto)
Manager (Auto)
MRP Manager role is

negotiated at runtime
M O
R U
o
ou tinh
ra C
e i
Per MRP
BothManager
devices are
Rolle
setwird
to
ego zur Laufzeit

Manager ausgehandelt
(Auto)
Dy
MRP Manager (Auto)
If it is not necessary to have a fixed redundancy manager in the MRP Ring, the function “Manager
(Auto)” can be used. If this role is assigned to several devices of the MRP Ring, then at runtime,
there is a negotiation amongst these devices as to which device takes on the role of redundancy
manager and which one(s) takes on the role of “Client”.
The advantage of this method is that when the negotiated redundancy manager fails during
running operation, one of the other MRP Ring devices that had been given the role of “Client”
during the negotiation can step into the position of the failed redundancy manager and can take
on the role of “Manager (Auto)”. When the failed redundancy manager is restored, the role of
“Manager (Auto)” is then once again negotiated between the devices concerned.
M O
If only one device is assigned the role of “Manager (Auto)” in the MRP Ring, it naturally takes on
the role of redundancy manager.
o RU
u t inh
Note
C o
a
reir
If a device of the MRP Ring is assigned the role of “Manager”, then no other device may be given
e
the role “Manager (Auto)” or “Manager”!
P
e g o
Dy

MRP
9.11.2. onon
MRP thethe
SCALANCE
SCALANCEXC208
XC208
M O
RU
o
tinh
Client or Manager role
possible
C ou
ei ra
Per
Ring ports can be set
ego
Dy Redundanz
Redundancy
einstellbar
alternatively
alternativ
(z.B.
can
beWBM
set (e.g.
oder
WBMSNMP)
or SNMP)

MRP on the SCALANCE XC208
The SCALANCE XC208 Switch offers the same functionality as an S7-1513. Furthermore, it also
offers a support for other ring redundancy procedures, such as, HRP.
Alternative Redundancy M O
o RU
inh
Unlike the S7-1513, the SCALANCE XC208 can also be parameterized via alternative
o u t
mechanisms such as the Web Based Management, WBM, or via the Simple Network
C
Management Protocol, SNMP. This is also true for the Media Redundancy. This is either
a
reir
parameterized via the PROFINET IO Settings via the S7 controller or via the WBM. If a
e
parameterization via the WBM is desired, the option must be activated in the Settings of the
P
e g o
SCALANCE XC208. Then all options are ‘greyed out’ and the parameterizations can be done via
Dy
the Web Based Management.

Contents 10
10. Shared Device....................................................................................................... 10-2
10.1. Traditional System Expansion ............................................................................................ 10-3
M O
10.2. U
Alternative System Expansion ............................................................................................ 10-4
R
o
tinh
10.3. Module-by-Module Shared Device...................................................................................... 10-5
10.3.1. u
Parameterizing the Module-by-Module Shared Device ...................................................... 10-6
C o
Submodule-by-Submodule SharedaDevice ......................................................................... 10-8
eir
10.4.
10.4.1.
e r
Configuring the Submodule-by-Submodule
P
Shared Device ............................................. 10-10
10.5.
10.5.1. y egoShared
MSI – Module-internal
MSI – Module-internal
Input MSO – Module-internal Shared Output ................. 10-11
Shared Input ................................................................................. 10-12
10.5.2. D
MSO – Module-internal Shared Output ............................................................................ 10-13
10.6. Task Description: ET 200SP as Shared Device ............................................................... 10-14
10.6.1. Exercise 1: Copying the S7-1510SP into a New Project .................................................. 10-15
10.6.2. Exercise 2: Copying the ET 200SP into a New Project .................................................... 10-16
10.6.3. Exercise 3: Parameterizing the ET 200SP as Module-by-Module Shared Device ........... 10-17
10.6.4. Exercise 4: Controlling the Conveyor Model via the S7-1510SP ..................................... 10-18
10.7. Additional Information ....................................................................................................... 10-19
10.7.1. Shared Device in the Same Project .................................................................................. 10-20
10.7.2. Requirements for Using Shared Device in the Same Project ........................................... 10-21
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Shared Device

10. Shared Device

Objectives
... know the difference between a traditional system expansion and an

alternative system expansion
... know the term Shared Device, understand it and be able

to explain it
M O
R U
... o
be familiar with the different possibilities to configure and
tinh
parameterize a Shared Device
ou
...
ra C
be able to commission a Shared Device
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Shared Device Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

10.1.Traditional System
Traditional Expansion
System Expansion
Control of the System is

robot expanded
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 3 Shared Device
Traditional System Expansion
In larger or widely distributed systems, numerous IO-Controllers as well as IO-Devices are
frequently used. Often it happens that in time the system or even system parts must be
expanded. For this, further IO-Devices are then used which are connected to new IO-Controllers.
Even for expansions which are located very close together, such as, the installation of new
sensors or actuators for a new IO-Controller, a new IO-Device must be installed in spite of an
existing IO-Device.
The reason for this is that an IO-Device in the traditional sense can always only be assigned to
one IO-Controller. Therefore, the new sensor and actuator data must be coupled to a new IO-
Device which, for its part, is assigned to a new IO-Controller.
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy

10.2.Alternative System
Alternative Expansion
System Expansion
ET 200SP is
Shared Device
M O
ET 200SP HF up to
4 Controllers RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Alternative System Expansion with Shared Device
For a system expansion which is located very close together, investment costs and time can be
saved with the help of the functionality “Shared Device”.
The “Shared Device” function makes it possible to distribute the modules as well as the
submodules of an IO-Device between several IO-Controllers. The IO-Device is indirectly assigned
to several IO-Controllers. Due to this functional principle, no new IO-Device must be installed for
the system expansion but rather an expansion of the existing IO-Devices with further I/O modules
is sufficient. The new data of the system is then assigned to a new IO-Controller.
Note
M O
The “Shared Device” function also permits the mixing of F- as well as ‘normal’ modules in one
RU
and the same IO-Device. This IO-Device can then be accessed not only from an F-controller but
o
also from a ‘normal’ controller.
u t inh
C o
a
P e reir
e g o
Dy

10.3.Module-by-Module Shared
Module-by-Module Device
Shared Device
The same Copy & Paste

IO-Device
M O
R U
o
ou tinh
a C
Up to 4 controllers
e reiInr this case, sharing
oP
share the I/Os of the ET is done module-by-
200SP module
eg
Dy
The IO-Device must support the Shared Device function! Two projects are required!

Module-by-Module Shared Device
The simplest and most widespread form of a Shared Device is the module-by-module Shared
Device. To subdivide an IO-Device module-by-module means that the various IO-Controllers to
which the IO-Device is to be assigned, in each case, have access to one complete module of this
Device. It doesn’t matter what type of module this is as long as this module supports the “Shared
Device” function.
Conditions
So that the “Shared Device” function can be used, some additional points must be taken into
account:
M O
•
RU
The software with which the controller is programmed must support this function (Step7 as of
V12 SP1).
t i n ho
•
ou as of V1.1 as IO-Controller).
The controller must support this function (S7-1500
C
•
ira (see device manual).
The IO-Device must support this function
r e
• P
The IO-Controller(s) which eis/are to use the Shared IO-Device must be created in different
TIA Portal projects. g
e o
• Dy must be configured exactly the same in each of these projects. The
The Shared Device
exception to this is the configuration of the I/O modules.
• The send clock (transmission frequency) of all IO-Controllers which have access to the
Shared Device must be the same.
Note
All advanced functionalities such as “Submodule-by-submodule Shared Device” or module-
internal Shared Input as well as module-internal Shared Output are based on the principle of the
“Shared Device”. That is, these functionalities always require that the IO-Controllers are located
in different projects and that the IO-Device is identically configured as well as parameterized in
the projects (exception: I/O-Module assignment).

Parameterizing the
Module-by-Module
10.3.1. Parameterizing theShared Device
Module-by-Module Shared Device
Controller in
another project
Selection
M
IO-Controller O
R U
o
ou tinh
Property Interface
module
ra C
e i
Per Name of local
ego IO-Controller
Dy IO-Controller of
another project

Parameterization
So that the “Shared Device” function can be used, it is most important that the IO-Devices, which
are used, support this functionality! If the IO-Device does, the entry “Shared Device” can be found
under “Advanced options” under the PROFINET interface of the Device (see picture). Depending
on the Interface module, up to 4 IO-Controllers are supported here.
After you have parameterized how many IO-Controllers are to have access to the modules of the
IO-Device, this must also be defined for the individual modules themselves. In the Device
overview of the module, there is a column with the title “Access” (see picture). If the access to this
module is not to be done by the local IO-Controller, but by one of the others, the correct setting
must be chosen here. After all modules which are to be accessed by the local IO-Controller have
O
been given the name of the local IO-Controller, the hardware configuration can be loaded into the
M
local IO-Controller.
o RU
u t inh
Then, the projects with the other IO-Controllers are opened. The additional IO-Controllers that
o
want to access the IO-Device as Shared Device must be located in a separate project! After that,
C
a
the IO-Device is transferred from the original project into the other projects using Copy & Paste.
P e reir
Finally, the assignment of the I/O modules to the local IO-Controllers takes place.
Note
e g o
Dy
An I/O-Module may only be assigned to one IO-Controller!
You have to perform this consistency check yourself. TIA Portal cannot check whether an I/O-
Module has been assigned to several IO-Controllers!

Alternative Parameterization Methods

The assignment of different IO-Controllers to the individual modules of the IO-Device can also be
done in the Network view in TIA Portal. For this, the IO-Device must be highlighted and after that,
the menu item “Shared Device” can be found in the "General" Properties under the entry “Module
parameters”. The assignment can then be set here!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

10.4.Submodule-by-Submodule Shared
Submodule-by-Submodule Device
Shared Device

IO-Device
M O
RU
o
Up to 4 controllers ou
Sharing is done
tinh
share the I/Os of the
ra C
submodule-by-
e i
Per
ET 200MP submodule
eg o
Dy
The IO-Device and the modules must support submodule-by-submodule Shared Device!
Two projects are required!

Submodule-by-Submodule Shared Device
The functionality of the submodule-by-submodule Shared Device is the further development of
the module-by-module Shared Device. Here, you can not only set whether you would like to
assign individual modules to different IO-Controllers, but you can also decide submodule-by-
submodule which parts of the module are to be assigned to which IO-Controller!
Into how many parts a module can be subdivided depends on the number of I/Os of the module:
• One digital module with 16 inputs / outputs can be subdivided into 2 submodules.
M O
o RU
u t inh
C o
• a
reir
One digital module with 32 inputs / outputs can be subdivided into 4 submodules.
P e
e g o
Dy
• One analog module with 8 inputs / outputs can be subdivided into 8 submodules.

M O
R U
o
• ou tinh
One analog module with 4 inputs and 2 outputs can be subdivided into 4 submodules with 1
ra C
analog input each and into 2 submodules with 1 analog output each.
e i
o Per
eg
Dy
That is, digital modules can only be subdivided into submodules with 8 inputs/outputs while
analog modules can only be subdivided into submodules with 1 input/output. A larger, that is,
other division of the submodules is currently not possible!
Note
A module which supports the functionality “module-by-module Shared Device” does not
necessarily have to support the functionality “submodule-by-submodule Shared Device”.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Configuring the
Submodule-by-Submodule
10.4.1. Shared Device Shared Device
Configuring the Submodule-by-Submodule
Splitting the I/O

addresses
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Configuration
After defining the number of IO-Controllers assigned to the Shared Device, the submodules can
be distributed.
In the "Properties" of the I/O-Modules, under "Module parameters", you will find the section for
configuring the inputs or the outputs, in which the possibility then exists to carry out the
“Configuration of submodules”. Depending on the type, a different subdivision into the individual
submodules occurs.
Assignment of the I/O Addresses

The addresses of the individual submodules are assigned according to the same principle which
MO
is also used for the I/O-Modules. The address area is filled starting from the smallest address
RU
upwards without leaving any possible gaps. As can be seen in the picture, this can mean that a
o
inh
DI 32 module which had the address area from 14..17 before the module distribution, all of a
o u t
sudden occupies the addresses 4,14,15 as well as 16 after the subdivision to submodules.
a C
reir
Note
P e
Currently, a module can either be subdivided into the predefined distribution or it is not
e g o
subdivided. It is, for example, not possible to subdivide a digital input module with 32 inputs into 2
Dy
submodules à 16 inputs. It can either be subdivided into 4 submodules à 8 inputs or not be
subdivided at all!

– Module-internal
10.5.MSIMSI – Module-internal
Shared InputInput
Shared
MSO
MSO– Module-internal
– Module-internal
Shared Output
Shared Output
In MSO,
only 1 Controller can
write outputs

IO-Device
M O
R U
o
ou tinh
ra C
Up to 4 Controllers
e r ei
Up to 4 Controllers
can read back
can read inputs
o P outputs
eg
Dy
The IO-Device and the modules must support MSI or MSO!
Two projects are required!

MSI - MSO
If it is not sufficient that the inputs/outputs of a module are distributed amongst various IO-
Controllers, but all I/Os of a module are required on all Controllers, the functionality “module-
internal Shared Input” as well as “module-internal Shared Output” can be used.
This function permits several IO-Controllers to access the same inputs or outputs.
With this technique, up to 4 IO-Controllers can read-access the data of an input module or an
output module.
Note
M O
RU
The functionality “MSI” as well as “MSO” cannot be used in conjunction with the function
o
inh
“submodule-by-submodule Shared Device”. If one of these two functions is used in the module,
u t
the respective other function is automatically deactivated and cannot be used!
o
a C
P e reir
e g o
Dy

10.5.1. – Module-internal
MSIMSI – Module-internalShared
Shared Input
Input
I-Addresses are added
M O
R U
o
ou tinh
ra C
e i Value status
o Per expands I/Os
eg
Dy
MSI – Module-internal Shared Input
The functionality “module-internal Shared Input” (MSI) enables an input module to provide its
input data to up to four IO-Controllers. Each Controller can read-access the same channels.
Configuration
When the module supports the “MSI” function, a section “Copy of module for Shared Device
(MSI)” can be found in the ‘Module parameters’ in the ‘Properties’ of the module. Here you can
define for how many IO-Controllers the input is to be duplicated. Then, which copy is to be
accessed locally and which copies are available for the other IO-Controllers in other projects is
also defined via the column “Access”.
M O
Note
o RU
u t inh
If the “MSI” function is activated in the module, the functionality “Value status (Quality
o
Information)” is also automatically activated. This supplies a Quality Byte along with every byte
C
which specifies the state of this byte.
i r a
e space which is required for this module, is however,
Due to this automatic setting, the
P raddress
e4Byte
g o
also doubled! (example picture:
e
→ 8Byte)
Dy

MSO
10.5.2. – Module-internal
MSO – Module-internalShared
Shared Output
Output
I-Addresses are added
M O
RU
o
ou tinh
ra C
e i
o Per Value status
Dyeg expands I/Os

MSO – Module-internal Shared Output
The function “module-internal Shared Output” (MSO) enables an output module to provide its
output data to up to four IO-Controllers. With this function you must make sure, however, that still
only 1 IO-Controller has the write permission, that is, the write-access rights for this output
module. All other IO-Controllers are only granted a read-only access to this data.
Configuration
Just as for the function “MSI”, the module must support the functionality “MSO”. If this is the case,
then a section “Copy of module for shared device (MSO)” can be found in the ‘Module
parameters’ in the ‘Properties’ of the module. Here you can define for how many IO-Controllers
M O
the output is to be duplicated. However as mentioned, only a copy of the module output state as
RU
input address occurs here! For the IO-Controller which has the write-access to the output data,
o
inh
the system additionally stores a copy of the output data in the input data. Finally, which copy is to
also defined via the column “Access”. o u t

be accessed locally and which copies are available for the other IO-Controllers in other projects is
a C
Note
P e reir
If the “MSO” function is o
egactivated inactivated.
the module, the functionality “Value status (Quality
D
Information)” is alsoyautomatically This supplies a Quality Byte along with every byte
which specifies the state of this byte.
Due to this automatic setting, the address space which is required for this module, is however,
also doubled! (example picture: 4Byte → 8Byte)

Task Description: Integrating the S7-1510 and

10.6.Defining the ET 200SPET
Task Description: as 200SP
Shared as
Device
Shared Device
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task Description
The ET 200SP is now to be used as a Shared Device between the S7-1513 and the S7-1510SP.
The digital output card of the ET 200SP is to be assigned to the S7-1510SP and the remaining
modules, including the header module, are to be assigned as IO-Controllers to the S7-1513.
For this functionality, you must generate a new TIA Portal project in which one after the other the
S7-1510SP and then the ET 200SP are copied. Then, in both projects, you are to parameterize
the ET 200SP as Shared Device and assign the input and output cards to the correct IO-
Controller.
Finally, the control of the conveyor model via the S7-1510SP is to be made with a simple jog
operation.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise 1:
Copying
10.6.1. the1:S7-1510SP
Exercise Copying theinto a New Project
S7-1510SP into a New Project
M O
R U
o
Copy & Paste
Create new project
ou tinh
ra C
ei
o Per
eg
Dy
Task
You are to create a new TIA Portal project “IK-TIAPN_en_Shared_Device” and copy the
S7-1510SP into this project.
What to Do
1. Open a new TIA Portal Instance.
2. Create a new project. Name it IK-TIAPN_en_Shared_Device.
3. Using drag & drop, copy the S7-1510SP into it.
4. Save your new project.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Exercise 2 :
Copying
10.6.2. the2:ET
Exercise 200SPthe
Copying into
ETa200SP
New Project
into a New Project
M O
RU
o
ou tinh
ra C
Copy & Paste
e i
o Per
eg
Dy
Task
You are to copy the ET 200SP into your new project.
What to Do
1. Copy the ET 200SP into your new project.
2. Create a folder called "Shared" in the project "IK-TIAPN_en_Shared_Device". After that, drag
the S7-1510 and the copied ET 200SP into this folder.
3. Save it.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Exercise
10.6.3. 3: 3:
Exercise Parameterizing
Parameterizing the
the ET 200SPas Module-by-Module Shared
ET 200SP
as Module-by-Module
Device Shared Device
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy

Task
You are to parameterize the ET 200SP in both projects in such a way that it takes on the function
of a module-by-module Shared Device. The "DQ 16x24VDC/0.5A ST_1" module is to be
assigned to the S7-1510SP.
What to Do
1. Open the Device view of the ET 200SP in your original project.
2. Parameterize the ET 200SP as Shared Device (the parameterization in the picture
O
corresponds to the ET 200SP parameterization which is connected to the S7-1513).
M
R U
3. Open the Device view of the ET 200SP in the “IK-TIAPN_en_Shared_Device” project.
h o
4. Complete the parameterization of the ET 200SP
o u tinas Shared Device.
5. Compile your projects and save them. C
r e iracontrollers and check whether all devices function without
Pe
6. Download your projects into the two
error.
eg o
Note D y
Don’t forget your MRP parameterization in the new “IK-TIAPN_en_Shared_Device” project!

Exercise 4:
Controlling
10.6.4. the
Exercise 4: Conveyorthe
Controlling Model via the
Conveyor S7-1510SP
Model via the S7-1510SP
Jog left
Programming Jog left/right S_ConveyorLeft_Man
in the OB Main
M O
RU
Jog right
o
S_ConveyorRight_Man
ou tinh
ra C
neue Variablentabellen per
e i
Drag & Drop anlegen
o Per
eg
Dy
Task
You are to program the control of the conveyor model with the help of the S7-1510SP. A simple
jog operation is to be possible. The input “S_ConveyorLeft_Man” (%I 0.0) is to control the output
“K_Left” (%Q4.6) and the input “S_ConveyorRight_Man” (%I 0.1) the output “K_Right” (%Q4.5).
The jog operation is to be programmed in the OB “Main” of the S7-1510SP. The tag tables for the
tags of the conveyor model and the S7-1510 case can be copied from the library. The new input
tags “S_ConveyorLeft_Man” and “S_ConveyorRight_Man” are located in the tag table
“1510CaseVariables”.
What to Do
O
UM
1. Copy the tag tables from the library.
R
2. In OB1, program the required functionality as per the task.
t i n ho
ou
3. Compile and download your project.
C
4. Test whether the program fulfills theatask.
5. Save your project. e r eir
o P
e g
Dy

10.7. Sie noch mehr

WennAdditional wissen wollen
Information
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
IK-TIAPN / Ringredundanz MRP Seite 19 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Shared
10.7.1. Device
Shared ininthe
Device theSame
Same Project
Project
M O
RU
o
tinh
Copy & Paste
C ou
e i ra
o Per
eg
Dy The same IO-Device

Using a Shared Device in the Same Project
For easier management of the Shared Device functionality, it is also possible to use this function
in a project in TIA Portal.
This can make the maintenance and service of the IO-Device easier. It should, however, be
transparent, that the two IO-Devices are one and the same IO-Device, that is, that the IO-Device
uses the functionality Shared Device!
Note
O
Here as well, it is required that the Shared Device Copy must match the original IO-Device
M
RU
exactly!
o
inh
Furthermore, the Shared Device and the Shared Device Copy cannot be operated in the same
u t
subnet. TIA Portal would detect a double IP address here and would output an error message!
o
a C
P e reir
e g o
Dy

Requirements for Using Shared Device in the Same
Project
10.7.2. Requirements for Using Shared Device in the Same Project
Two identical Device names

not possible
M O
RU Must have the same IP
n h o address → different
u ti networks
C o
eira Deactivate option before
P e r copying
ego
Dy The name of the copied IO-
Device
is adopted

Requirements
The functionality “Generate PROFINET device name automatically” is a convenience function in
TIA Portal. This derives the PROFINET device name automatically from the Device-Name. In that
way, the assignment of an online IO-Device to an offline IO-Device in a project is considerably
simplified.
So that you can now use the functionality ‘Shared Device’ in the same project, the option
“Generate PROFINET device name automatically” must be deactivated for the Shared Device.
Only by deactivating this function is it possible for the copy of the IO-Device, which is to be used
as a Shared Device, to be assigned the same device name offline.
Names! M O
In TIA-Portal, you can have two identical PROFINET device names but not two identical Device-
o RU
u t inh
Note C o
a
P
served as the template, exactly. ereir
The manually set name of the copied IO-Device must match the name of the IO-Device, which
e g o
Changes to the name of the original IO-Device later on must be added manually!
Dy

Contents 11
11. I-Device – Intelligent IO-Device ........................................................................... 11-2
11.1. Data Exchange between Two IO-Controllers ..................................................................... 11-3
M O
11.2. U
I-Device ............................................................................................................................... 11-4
R
11.2.1. o
I-Device without Subordinate PROFINET IO-System......................................................... 11-5
11.2.2.
11.2.3. ou tinh
I-Device with Subordinate PROFINET IO-System.............................................................. 11-6
I-Device as Shared Device ................................................................................................. 11-7
C
11.3.
e ira
Communication via Transfer Areas.....................................................................................
r 11-8
e
P ................................................................................................ 11-9
11.4.
o
Parameterizing the I-Device
e g
11.5. Parameterizingythe
D Transfer Area ..................................................................................... 11-10
11.6. Cross-Project I-Device ...................................................................................................... 11-11
11.6.1. Importing the I-Device in a New Project ........................................................................... 11-12
11.7. Task Description: S7-1510SP as I-Device ........................................................................ 11-13
11.7.1. Exercise 1: Parameterizing the S7-1510SP as I-Device .................................................. 11-14
11.7.2. Exercise 2: Integrating the I-Device in the S7-1513 Project ............................................. 11-15
11.7.3. Exercise 3: Controlling the Conveyor Model with the Help of the S7-1513 as well as
the S7-1510SP .................................................................................................................. 11-16
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – I-Device
11. I-Device – Intelligent IO-Device

Objectives
... understand the IO-Controller communication with PROFINET
... be familiar with the possible applications of an I-Device
...
M O
be able to configure and parameterize an IO-Controller as I-Device
R U
... o
be able to commission an I-Device
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / I-Device Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
11.1.Data Exchange
Data between
Exchange Two Two
between IO-Controllers
IO-Controllers
Data exchange
How can data

exchange be
accomplished?
M O
RU
o
ou tinh
C
I/O data of ET is
ra
e i
to be transferred to
o Per HMI
eg
Dy
Page 3 I-Device
Data Exchange between Two IO-Controllers
If data is to be exchanged between two controllers, the first possible solution that comes to mind
is the CPU-CPU communication using the communication instructions in TIA Portal. These
include, for example, the popular S7 Communication and the Open User Communication (in
short: OUC). It is also possible to use the MODBUS on TCP Communication for the CPU-CPU
communication. Familiar instructions of these communication methods are:
• GET / PUT
• BSEND / BRCV
• TSEND / TRCV
M O
o RU
However, in addition to these more familiar communication methods, data exchange between two
controllers can also be accomplished by using a data exchange functionality offered in
t
PROFINET: the option "I-Device" (Intelligent IO-Device).
u inh
C o
a
reir
Note
P e
Not every controller / IO-Controller supports the functionality I-Device!
e g o
Dy
11.2.I-Device
I-Device
ID: 109478798
Data exchange via transfer area
I-Device
Automatische
IO-Controller is IO-Device for
Aktualisierung
another IO-Controller
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 4 I-Device
Device (Intelligent IO-Device)
In a controller, the functionality "I-Device" makes it possible to exchange data between different
IO-Controllers. That way, the controller can, for example, be used as an intelligent pre-processing
unit for partial tasks. In this case, the controller / the IO-Controller with activated I-Device
functionality is connected to a "higher-level" IO-Controller as an IO-Device.
Data exchange using the I-Device functionality has the following advantages:
• Easy interfacing of IO-Controllers
• Real-time communication between IO-Controllers (Real-Time as well as Isochronous Real-
Time)
M O
RU
• Less processing load on the IO-Controller due to distribution of processing power amongst I-
Devices
t i n ho
• Lower communication load due to processing
C ou of process data on-site
r e ira in separate STEP-7 projects
• Clarity, since partial tasks are processed
o Pe
Ways to Integrate an I-Device
The integration ofD
eg
anyI-Device in the PROFINET IO-System can be done in the following ways:
• I-Device without subordinate PROFINET IO-System
• I-Device with subordinate PROFINET IO-System
• I-Device as Shared Device
Note
On the Service & Support pages, under the Entry-ID: 109478798 you will find further information
on the topic of I-Device and data-set communication.
I-Device
11.2.1. without
I-Device Subordinate
without Subordinate IO-System
PROFINET IO-System
I-Device without its own

PROFINET IO-System
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 5 I-Device
I-Device without Subordinate PROFINET IO-System
The I-Device does not have its own distributed I/O. The configuration and parameterization of the
I-Device in the role of an IO-Device is done in the same way as for a distributed I/O system, for
example, an ET 200SP.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
I-Device
11.2.2. with
I-Device Subordinate
with SubordinatePROFINET IO-System
PROFINET IO-System
I-Device mit
witheigenem
its own
PROFINET IO-System
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 6 I-Device
I-Device with Subordinate PROFINET IO-System
At a PROFINET interface, an I-Device can, depending on the configuration, also be an IO-
Controller in addition to its role as IO-Device. The I-Device then has its own subordinate
PROFINET IO-System. Consequently, through its PROFINET interface, the I-Device is the IO-
Device for a higher-level IO-System and at the same time IO-Controller for its own subordinate
PROFINET IO-System. The subordinate IO-System can, in turn, contain further I-Devices which
for their part also integrate further subordinate IO-Systems (see picture). As a result,
hierarchically structured IO-Systems are possible.
In addition to its role as IO-Controller, an I-Device can, via a PROFIBUS interface, also be a DP-
Master for a subordinate PROFIBUS-System.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
I-Device
11.2.3. as Shared
I-Device Device
as Shared Device
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPNas
I-Device / I-Device
Shared Device Page 7 Siemens AG © 2016
An I-Device can also be used as a Shared Device by several IO-Controllers, when it supports this
functionality. Even in the role of Shared Device, the I-Device can have a subordinate PROFINET
IO-System. This is, however, not absolutely necessary.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
11.3.Communication via Transfer

Communication Areas
via Transfer Areas
Data exchange between

higher-level
IO-Controller and
the I-Device
Data exchange between
higher-level
IO-Controller and normal
IO-Device
M O
U Transfer relationship
h oR between the user
tin
program and the transfer
C o u area
eira
P e r
eg o Data exchange between
Dy the I-Device and a

subordinate
IO-Device

Page 8 I-Device
Transfer Areas
For communication between the I-Device and the IO-Controller, data exchange happens via so-
called "Transfer areas".
The transfer area is always defined in the I/O addresses of the IO-Controller. For a
communication via I-Devices, the process image (table) of the CPU is used.
From the point of view of a higher-level IO-Controller, the communication to an I-Device is the
same as to a distributed I/O with the usual read and write operations of inputs and outputs. From
the point of view of an I-Device, the data transfer to a higher-level IO-Controller is similar to the
data transfer to the local or associated distributed I/O via inputs and outputs.
O
By using the process image (table) in the programming, an engineering tool can directly access
M
example. o RU
all Devices in the network without having to implement additional routing mechanisms, for
u t inh
C o
a
P ereir
e g o
Dy
11.4.Parameterizing the I-Device

Parameterizing the I-Device
M O
R U
o
tinh
Cou
Activate
I-Device
eira
P e r Select
ego
IO-Controller in
Dy
the project

Page 9 I-Device
I-Device
When the device which is to be connected to the IO-Controller as I-Device is located in the same
project as the IO-Controller, the I-Device functionality of the device is parameterized in the Device
view of the I-Device.
The menu item "Operating mode" is located in the Properties of the PROFINET interface of the
I-Device. Here, the controller can be parameterized as the IO-Device for a higher-level IO-
Controller. The IO-Controller is directly selected via a drop-down menu. The networking of the
I-Device to the IO-Controller and the newly created PROFINET IO-System is then also displayed
in the Network view.
O
The other options "Prioritized startup" as well as "Optional IO-Device" are identical to those of a
M
standard IO-Device.
o RU
u t inh
The option "Parameter assignment of PN interface by higher-level IO controller" can only be used
when no subordinate PROFINET IO-System is assigned to the I-Device!
Co
a
Note
P e reir
functionality! e g o
So that the IO-Controller can be parameterized as an I-Device, it must of course also support this
Dy
11.5.Parameterizing the Transfer

Parameterizing Area Area
the Transfer
M O
Details view of
R U
theTransfer area
o
outinh
ra C
ei
Creating and
P e r parameterizing the
areas
eg o
Dy max. size1440 Byte
max. consistency size 1024 Byte
max. number of transfer areas 64

Page 10 I-Device
Transfer Area
Transfer areas are the I/O areas via which the I-Device communicates with the higher-level
IO-Controller.
Each transfer area contains an information unit which is consistently exchanged between the
IO-Controller and the I-Device. These areas are defined when the I-Device function is configured
and are, among other things, included in the subsequently generated GSD file when the I-Device
is to be used across projects.
The following properties must be taken into consideration when defining transfer areas:
• 1440 bytes maximum size of the transfer memory for inputs and outputs per AR (Application
Relation) (gross values, net minus user data supplement).
M O
• 1024 bytes maximum user data consistency length (maximum U
R size of a transfer area).
h o
• Maximum 64 transfer areas (can be distributed
o u tinto the maximum number of supported ARs).
After the transfer areas have been created
r a Cin the I-Device communication tab, you can switch into
i
re suchon as,
the Details view of this area by left-clicking the new tab (name of the transfer area) which has
P
just been created. Here, furthereoptions, assigning the area to a process image, are
possible.
eg o
D y
Note
The address range of the configured transfer areas has an impact on the useable bandwidth of
the I-Device:
Bandwidth of transfer areas + bandwidth of the subordinate IO-System = total bandwidth used on
the I-Device
A too large address space of the transfer areas causes a larger bandwidth need and can lead to
greater updating times as a result.
11.6.Cross-Project I-Device
Cross-Project I-Device
M O
R U
o
Export of GSD /
ou tinh
GSDML file
ra C
ei
o Per
eg
Dy
Page 11 I-Device
Cross-Project I-Device
If the I-Device is to be used in another project or in another engineering system, basically nothing
has to be changed in the previous parameterization. The only thing that has to be done is that the
created configuration and parameterization of the I-Device has to be exported as a GSD /
GSDML file. This is followed by the import into the new project or into the other engineering
system.
Before exporting, you can still specify the designation of the file, the description of the contents as
well as the path manually. The designation is derived from the PROFINET device name of the
I-Device and the description from the hardware properties of the I-Device.
Note
U MO
The import and the use of this GSD /GSDML file is the o R as for a "normal" GSD / GSDML file.
same
tin h
C o u
i r a
P ere
y ego
D
Importing
11.6.1. the
Importing I-Device
the I-Devicein
inaaNew
New Project
Project
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 12 I-Device
Import / Installation I-Device
An I-Device GSD /GSDML file is imported in the same way as a "normal" GSD /GSDML file. You
can start the "Manage general station description files (GSD)" function via the "Options" in the TIA
Portal menu bar. Through this, you can install further GSD as well as GSDML files. The devices
installed in this way are stored in the "Hardware catalog" in the "Other field devices" folder.
Note
The installation of GSD and GSDML files can only be executed when at most one instance of the
TIA Portal is open. If this is not the case, the following error message appears when the "Manage
general station description files (GSD)" function is executed:
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Task S7-1510SP
Description: as I-Device
S7-1510SP as I-Device
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 13 I-Device
Task Description
The S7-1510SP is now to take on the role of an I-Device. The function of the ET 200SP as
Shared Device remains unaffected by this. The parameterization of the S7-1510SP as I-Device is
to occur in the IK-TIAPN_en_Shared_Device project and not in your original project! Then, the
GSDML file of the S7-1510SP is exported and imported into the project of the S7-1513 and
integrated there. Along with that, the old S7-1510SP in the project with the S7-1513 is deleted.
Finally, an expanded control of the conveyor model via both controllers is still to be implemented
with the help of the I-Device functionality.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Exercise 1:
Parameterizing
11.7.1. the S7-1510SP
Exercise 1: Parameterizing the as I-Deviceas I-Device
S7-1510SP
Activate I-Device
function
Parameterize M O
transfer areas
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 14 I-Device
Task
You are to switch to the IK-TIAPN_en_Shared_Device project. You are to parameterize the S7-
1510SP in such a way that it can now also be used as an IO-Device for a higher-level IO-
Controller. The I-Device is to have a receive transfer area as well as a send transfer area of 3
bytes each. Finally, the I-Device is to be exported for further use.
What to Do
1. Open the IK-TIAPN_en_Shared_Device project.
2. Switch either into the Network view or the Device view of the S7-1510SP.
3. Activate the I-Device ‘Operating mode’ of the S7-1510SP.
U MO
o R
4. Parameterize the Transfer area as shown in the picture.
5. Export the GSDML file of the S7-1510SP. tin
h
C ou
r e i ra
7. Download the new hardwareeconfiguration into the S7-1510SP.
o P
Note ye g
D
The intended IO-Controller (the S7-1513) for the S7-1510SP is not located in the same project.
For that reason, an IO-Controller cannot yet be assigned to the S7-1510SP in this exercise.
Exercise 2:
Integrating
11.7.2. Exercise the I-Device in
2: Integrating thethe S7-1513
I-Device Project
in the S7-1513 Project
Assign I-Device to
the S7-1513
Delete old
S7-1510SP
M O
R U
o
ou tinh
ra C Import
rei
GSDML file
P e
e g o
Dy
Page 15 I-Device
Task
You are to assign the I-Device to its IO-Controller. To do so, you must delete the S7-1510SP in
the original project. Then you are to import the GSDML file of the I-Device and insert it in the
Network view. Finally, you are to integrate the I-Device in the PROFINET IO-System of the IO-
Controller as well as assign the I-Device to the S7-1513.
What to Do
1. Open your original project.
2. Delete the S7-1510SP.
MO
3. Import / Install the GSDML file of the I-Device from the previous exercise.
U
4. Integrate the I-Device just like a standard IO-ControllerR
n h o in the configuration.
5. Assign the I/O addresses shown in the picturetifor the transfer area of the I-Device.
C ou
r e i ra
e configuration
7. Download the hardware configuration.
Pexisting All devices should now once again have an error-free
eg o
state. If necessary, correct and parameterization errors!
D y
Exercise
11.7.3. 3: 3:
Exercise Controlling
Controllingthe
the Conveyor Modelwith
Conveyor Model with the
the Help of the S7-1513 as
Help of the S7-1513 as
well as the S7-1510SP well as the S7-1510SP
%Q2.1 %Q2.2 Manual mode

+%Q2.3
%Q2.0
Top Lights
Automatic
M O
RU
o
Control ou tinh
conveyor
ra C
e i
Per
model
eg o
Dy

Page 16 I-Device
Task
With the help of the I-Device communication and the two controllers, you are now to program a
control of the conveyor. The conveyor is to fulfill the following functionalities:
• The system is switched on and switched off via the NC contact “S_On” (%I 0.0).
• When the system is switched on, you can switch the system between the “Auto”
(%I 0.1=0) and “Manual” (%I 0.1=1) operating modes using the switch “S_Man” (%I 0.1).
• In “Manual” mode, the system can be traversed either via the inputs “S_JogLeft” (%I 0.2) or
“S_JogRight” (%I 0.3) on the S7-1513 or via the inputs “S_ConveyorLeft_Man”
(%I 0.0) or “S_ConveyorRight_Man” (%I 0.1) on the S7-1510SP. M O
o RU
• In “Auto” mode, a transport sequence of the system can be started, however, not
t inh
simultaneously at both, via the respective pushbutton “S_Bay1” or “S_Bay2” as soon as a
u
o
metal piece is placed at “B_Bay1” or at “B_Bay2”. The transport sequence stops automatically
C
a
reir
as soon as the metal piece has passed the light barrier.
P e
• The Top Light “TopLeftRed” (%Q2.0) lights up when the system is switched on and is in “Auto”
e g o
mode. However, no metal piece can be at Bay1 or Bay2. If there is a metal piece at the two
Dy
initiators, the Top Light “TopLeftRed” also lights up.
• The Top Light “TopLeftGreen” (%Q2.1) lights up when the system is switched on, is in “Auto”
mode and the input “B_Bay1” or “B_Bay2” detects a metal piece. This signals that the system
is ready for an automatic transport sequence.
• The Top Light right lights up yellow, “TopRightGreen” (%Q2.3) and “TopRightRed” (%Q2.2)
are simultaneously controlled when the system is switched on and is in “Manual” mode.
• If the system is switched off, no Top Light lights up.
In the S7-1513, only the communication to the I-Device as well as the processing of the input and
output signals are programmed. The communication to the I-Device takes place in a function
“Com_I-Device”.
The communication to the IO-Controller as well as the entire control of the conveyor model is
programmed in the S7-1510SP. For this an FB “Conveyor” is created. Along with that, the old
control of the conveyor model in OB1 is deleted!
What to Do
1. Open your original project.
2. Copy the tag table “ConveyorModel_Inputs” from the library into your project.
3. Create a new function “Com_I-Device” and call it in OB1.
4. In this block, program the communication to the I-Device via the Transfer areas as well as the
management of the input and output signals.
5. Open the “IK-TIAPN_en_Shared_Device” project.
6. Copy the tag table “ConveyorModel_Inputs_from_1510SP” into this project.
7. Create a new function block “Conveyor” and call it in OB1. Along with that, delete your old
control of the conveyor model from OB1.
M O
U
8. In this (new) function block, program the control of the conveyor model according to the task. It
R
o
also takes over the management of the transfer areas between I-Device and IO-Controller.
9. Save your project. tinh
ou
C
r e ira controllers and check whether these fulfill the task.
10. Download your modifications into both
Note o Pe
D ytheegtransferring of bytes facilitates the programming of the communication
In certain situations,
between the IO-Controller and I-Device.
The blocks programmed by you do not have to comply with the IEC standard 61131-3. Global
variables in the blocks can be accessed.
Create (on your own) additional global variables and tag tables. Use temporary and static
variables as required.
The light barrier is queried via an edge evaluation.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
Contents 12
12. PROFINET IRT – Isochronous Mode – Oversampling ....................................... 12-2
12.1. Sample System: Packaging System ................................................................................... 12-3
M O
12.2. U
Real-time & Deterministics .................................................................................................. 12-4
R
o
tinh
12.3. PROFINET I/O RT .............................................................................................................. 12-5
12.4. ou
Response Time / Signal Runtime ....................................................................................... 12-6
C
12.5.
e ira Real-Time (Worst Case Scenario)...................... 12-7
Realizing the Customer Requirements:
r
e
P...................................................................................................
12.6.
o
Structure of a Send Clock
g 12-8
PROFINET IRTy–eIsochronous Real-Time.......................................................................... 12-9
12.7.
D
12.8. Comparing RT with IRT System Properties ...................................................................... 12-10
12.9. IRT & Topology ................................................................................................................. 12-11
12.10. Activating IRT on the IO-Controller ................................................................................... 12-12
12.11. Activating IRT on the IO-Devices ...................................................................................... 12-13
12.12. IRT Sync Domain .............................................................................................................. 12-14
12.13. Realizing the Customer Requirements: Isochronous Real-Time (Worst Case Scenario) 12-16
12.14. Isochronous Mode ............................................................................................................ 12-17
12.15. Deterministic Communication Model ................................................................................ 12-18
12.16. Isochronous Mode in TIA Portal ........................................................................................ 12-19
12.17. Isochronous Mode in the Cycle ......................................................................................... 12-20
M O
12.18.
RU
Activating the Isochronous Mode in the Module ............................................................... 12-22
12.19.
t i n ho
Realizing the Customer Requirements: Isochronous Mode (Worst Case Scenario) ....... 12-23
12.20. ou
Oversampling ....................................................................................................................
C 12-24
12.21.
eir a
Oversampling in the Cycle ................................................................................................ 12-25
e r
P on the Module ..................................................................... 12-26
12.22.
o
Activating the Oversampling
g
e Requirements: Oversampling (Worst Case Scenario) .............. 12-27
12.23.
Dy
Realizing the Customer
12.24. Task Description: IRT, Isochronous Mode and Oversampling ......................................... 12-28
12.25.1. Time-Based IOs ................................................................................................................ 12-30
12.25.2. Realizing the Customer Requirements: Time-Based IOs (Worst Case Scenario) .......... 12-31
12.25.3. Terminal-to-Terminal Response Time .............................................................................. 12-32
12.25.3.1. Terminal-to-Terminal Response Time using an S7-1518 as an Example ................... 12-33
IK-TIAPN – PROFINET IRT – Isochronous Mode – Oversampling

12. PROFINET IRT – Isochronous Mode – Oversampling

Objectives
... be familiar with the difference between real-time and deterministics
... be able to explain the term IRT and how it can be applied
...
M O
understand the advantages of isochronous mode
R U
... o
understand how oversampling works and be familiar with the
theoretical application
ou tinh
...
ra C
be familiar with the term and the advantages of Time-Based IOs
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET IRT - Isochronous Mode - Oversampling Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

12.1.Sample System:
Sample Packaging
System: System
Packaging System
Initial situation: Requirements:

Conveyor speed: 5m/s • Count packages
Package length: 20cm - 50cm • Measure packages (±2mm)
• Control the printing robot
• Optimize conveyor speed
M O
RU
o
tinh
2m
C ou
e i ra
o Per
eg
Dy
Page 3 PROFINET IRT
Sample System: Package System
The functions presented in this chapter which are possible with PROFINET and the suitable
components, are explained in more detail using a customer’s system as an example.
The customer’s system is to count packages, measure them with an accuracy of ± 2mm for a
package length of 20cm to 50cm and then to label the packages with a printing robot.
After all these requirements have been achieved, then the final task is to optimize the conveyor
speed. For reasons of productivity, the current conveyor speed of the system is 5m/s and is not to
be slowed down!
To achieve these requirements, different functionalities of PROFINET which build on one another
O
will be explained and discussed in detail during the course of this chapter.
M
Note o RU
u t inh
Not every controller as well as every module supports the functionalities presented in this
chapter! Co
a
P ereir
e g o
Dy

12.2.Real-time & Deterministics

Real-time & Deterministics
Deterministics = a system reacts

in a predictable
(deterministic) manner
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy Real-time = events are
processed within a defined time

Page 4 PROFINET IRT
PROFINET I/O
PROFINET I/O is a scalable real-time communication system based on the Layer2 protocol for
Fast Ethernet. Two data transmission methods with different performance levels are available for
real-time support: RT (for time-critical process data) and IRT (for high-precision as well as
isochronous processes).
PROFINET RT – Real-Time
A PROFINET I/O System with real-time communication meets the following extremely important
requirements:
O
• The transmission of time-critical data takes place in guaranteed time intervals. PROFINET
M
RU
provides an optimized communication channel for real-time communication for this.
o
possible. u t inh
• An exact determination (prediction) of the time at which the data transfer takes place is
C o
a
reir
• This ensures that problem-free communication can also take place in the same network via
e
other standard protocols, such as TCP/IP.
P
e g o
PROFINET with RT is therefore particularly suitable for the following applications:
Dy
• Time-critical applications in factory automation
• Implementation of extensive automation applications in the process industry
According to IEEE802.1Q, the PROFINET IO-telegrams have priority over standard telegrams.
This ensures the determinism required in automation. With this method, the data is transmitted by
means of prioritized Ethernet telegrams. With RT, update times of ≥ 250 μs can be realized.
Standardization
The communication methods PROFINET RT and PROFINET IRT are standardized in the
international standard IEC 61158!

12.3.PROFINET I/O RT
PROFINET I/O RT
State: many uncoordinated cycles!

• T1: Sampling of the input signal
• T2: Backplane bus ET 200
T4 • T3: PROFINET I/O
PLC • T4: CPU cycle duration (OB1)
• T5: Backplane bus ET 200
• T6: Conversion of the output signal
T3 T3
■ PROFINET M O
RU
o
T2 ET 200 T5 ETou200 tinh
ra C
e i
o Per T6
T1 eg
Dy
Page 5 PROFINET IRT
PROFINET I/O RT
PROFINET IO with real-time communication (RT) is the ideal solution for the integration of I/O
systems. It is based on standard Ethernet in the devices and on standard industrial switches as
infrastructure components. A specific hardware support is not required.
With the PROFINET RT communication method, the many uncoordinated cycles a telegram must
pass through can pose a problem if a fast response time is required. As shown in the example
above, in order for an input in the ET 200MP to control an output in the ET 200SP, the cycles T1
to T6 have to be passed through. The T3 cycle in the PROFINET I/O communication even has to
be passed through twice.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

12.4.Response Time
Response / Signal
Time Runtime
/ Signal Runtime
Response time:
• Best case: Sum of all individual
cycles
T4 • Worst case: 2 x Sum of all individual
cycles
PLC
Time accuracy of the output signal
• 2 x Sum of the cycles from the CPU
to the output (T3 – T6)
T3 T3
■ PROFINET M O
Consistency of the I/O signals
• U
Standard: Slot-by-slot
R
o
T2 ET 200 T5 ETou200 tinh
ra C
e i
o Per T6
T1 eg
Dy
Page 6 PROFINET IRT
Response Time /Signal Runtime
The already addressed uncoordinated cycles not only have an effect on the real-time but also the
deterministics in a PROFINET RT System.
The response time in the system above is - in the best case - the sum of all individual cycles; in
the worst case, however, 2 x the sum of all cycles. This is the case when an event occurs just
after the start of the next cycle which results in an additional delay time of one cycle.
The time accuracy of an output signal from the PLC to the ET 200SP, for example, is also
affected by this uncoordinated state. In the worst case, it also takes 2x the sum of the cycles T3
to T6.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

12.5.Realizing the the

Realizing Customer Requirements:
Customer Requirements:
Real-Time (Worst Case Scenario)
Real-Time (Worst Case Scenario)only for Script
Package length = 0.2m – 0.5m

Conveyor speed = 5m/s = 5mm/ms
I/O update time = 1ms, OB35 cycle = 1ms
Signal conversion time IN/OUT each ~ 100µs
Max. error = ±2mm
Count packages :
Minimum time of package under the light barrier: 40ms
Control printing robot:

M O
U
Response time: 2 x (signal conversion timeIN + I/O update timeIN + OB35 cycle +
R
o
I/O update timeOUT + signal conversion timeOUT) = 6.4ms
Time span of package from sensor to actuator: 400ms ou tinh

ra C
e i
Measurement of package:
Per
ego
Jitter during acquisition = 2 x (signal conversion time + I/O update time + OB35 cycle) = 4.2ms
2 edges (package start D

y
& package end) → max. error = 8.4ms
Error when measuring package (with current conveyor speed): → 42mm

Page 8 PROFINET IRT
Realizing the Customer Requirements: Real-Time (Worst Case Scenario)
If you take the given customer requirements (from the sample system) and make the calculations
as to whether these requirements can be realized with the PROFINET RT solution, you will come
to the following result:
• The printing robot can be controlled without a problem! The PROFINET RT-System requires -
from the input of the signal (that a package was detected), the processing and transport, up to
the control of the printing robot – 6.4ms in the worst case. The time span - which would be
available at a conveyor speed of 5m/s and a distance of 2m between sensor and printing robot
- would be 400ms.
M O
RU
• The measurement of a package with a maximum tolerance of ± 2mm cannot be realized with a
o
u t inh
PROFINET RT-System unfortunately. In the worst case, the error for a package measurement
is an unimpressive 42mm and is way outside of the tolerance limits!
Co
a
P ereir
e g o
Dy

12.6.Structure of aof
Structure Send Clock
a Send Clock
PROFINET Communication cycle

communication Controller
Send clock 250µs

M O
PN IO
RT/IRT
R U
NRT
n h o 40% PN
Synchronized IRT
0%
u t i
100µs
fix
250µs
0-100µs
communication
C o
Send clock 500µs – 1ms
ira
PN IO
e r e RT/IRT NRT
max 50% PN
oP
0-500µs
0% 50% 100%
eg
Dy Send clock > 1ms
PN IO
RT/IRT NRT
~ 50% - 12,5% PN
1,125 – 0-500µs
0% 500µs
fix 4ms

Page 9 PROFINET IRT
Structure of a Send Clock
A send clock consists of a maximum of 3 parts. The part for the synchronized communication -
the PROFINET IRT data, the part for the real-time communication - the PROFINET RT data, as
well as the part for the standard communication, for example, the TCP/IP data. The first two parts
combine to produce the so-called PROFINET communication which has a reserved bandwidth in
every send clock. Consequently, this communication always occurs independently without any
external influence from other types of communication!
PROFINET IRT – Isochronous Real-Time

IRT is a synchronized transmission method for the cyclic exchange of IRT data between
M O
PROFINET devices. A reserved bandwidth within the send clock is available for the IRT data. The
RU
reserved bandwidth guarantees that the IRT data can always be transmitted in reserved, timely
o
additional real-time communication). u t inh
synchronized intervals - uninfluenced by other high network loads (e.g. TCP/IP communication or
C o
a
P e reir
e g o
Dy

12.7.PROFINET – Isochronous
IRT IRT
PROFINET – Isochronous
Real-Time
Real-Time
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 10 PROFINET IRT
PROFINET IRT – Isochronous Real-Time
PROFINET with IRT is synchronized communication in reserved time intervals. IRT makes it
possible to be able to control time-critical applications, such as, Motion Control or fast IO-
communication via PROFINET. In addition to that, PROFINET IRT also offers other advantages:
• Extremely precise deterministics allow for maximum control accuracy and with that, for
example, exact positioning of axes.
• Easy and flexible integration of PROFINET devices for real-time applications into existing
company networks.
• Shortest response times and highest deterministics through bandwidth reservation and with
MO
that also suitable for applications with the highest performance requirements, for example,
RU
pressure/position control for presses or register mark detection for packaging machines.
o
t inh
• Secure standard communication parallel to real-time communication via the same
u
transmission medium.
Co
a
Pe
outside of the IRT Sync-Domain.
reir
• PROFINET standard components for the PROFINET I/O-System can continue to be used
g o
eaddressed
applications: D y
Due to the advantages above, PROFINET IRT is particularly suited for the following
• High deterministics for large quantity structures with regards to I/O user data communication
(production data)
• High performance even with many devices with regards to I/O user data communication
(production data)
• Parallel transmission of production data and TCP/IP data via one line.
The reservation of the transmission bandwidth ensures the forwarding of production data, no
matter how high the network load is.

12.8.Comparing RT with
Comparing IRT System
RT with Properties
IRT System Properties
RT IRT
Type of ▪Prioritization of the RT telegrams ▪Path-based switching on the basis of a planning
transmission through Ethernet prioritization (VLAN- of the communication path
Tag) ▪No transmission of TCP/IP frames in the time
domain with IRT communication
Determinism ▪Variation of the transmission time ▪exact, planned transmission
due to the joint use of the ▪Send and Receive points are guaranteed for any
transmission bandwidth with the topologies
other protocols (e.g. TCP/IP)
▪Does not depend on network load
M O
Special Ethernet- ▪Not required ▪Necessary
R U
o
tinh
Controller
required
C ou
e i ra
Per
Isochronous ̶ ▪Yes (only on the integrated PNIO interface of the
controller)
application
eg o
Starting time of
the isochronous
̶
Dy ▪Points in time for the receipt of data are exactly
planned
application ▪Application can be started synchronized to the
cycle
RT and IRT in Comparison
At a glance, you can see the most important characteristics and differences of the two systems in
the table above!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

12.9.IRTIRT
& Topology
& Topology
◼ Path-based switching
through configured
topology
◼ The communication path,

the number of switches
(Delay) is known
M O
R U◼ Expanded diagnostics for
o
tinh communication faults
a Cou
e r eir ◼ Automatic initialization/re-
o P initialization of Device
Dyeg No MRP possible for IRT!
The configuration of the topology is absolutely necessary when IRT is used!

IRT & Topology
If the functionality PROFINET Isochronous Real-Time is to be used, then it is absolutely
necessary that a topology is created for all devices which are to take part in this PROFINET IRT
I/O-System. Without the topology it is not possible to operate IRT!
Note
It is no longer possible to operate the system in MRP when PROFINET IRT is used!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Activating
12.10. IRT IRT
Activating on the
on IO-Controller
the IO-Controller
M O
R U
o
tinh
Cou
PLC takes on the Sync-
Master role
eira
P e r
eg o
Dy
Activating IRT on the IO-Controller
The first step for using PROFINET IRT is the distribution of the different synchronization roles in a
synchronization domain to the intended devices in this domain.
A Sync-Master must be defined which takes on the synchronization of the packages to the Sync-
Slaves. The role of this Master is usually taken on by the IO-Controller. The role of the Sync-
Slaves is assigned to the IO-Devices.
Devices which are not to be integrated in this PROFINET IRT I/O-System are assigned the
synchronization role “Unsynchronized”.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

Activating
12.11. IRT IRT
Activating on the
on IO-Devices
the IO-Devices
M O
RU
o
ou tinh
ra C
e i
o Per With IRT activation,
automatically
eg Sync-Slave role
Dy
Activating IRT on the IO-Devices
For all IO-Devices taking part in the IRT, the RT class must be switched from “RT” to “IRT” in the
Hardware configuration of their PROFINET interface. With this switchover, the role assignment of
the “Sync-Slave” in the field “Synchronization role” automatically occurs.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

IRT Sync
12.12. Domain
IRT Sync Domain
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IRTIK-TIAPN / PROFINET IRT - Isochronous Mode - Oversampling Page 15
Sync Domain Siemens AG © 2016
All devices which exchange data with one another via PROFINET IRT must be members of the
same Sync-Domain. In the Network view in TIA Portal, this can be checked and even the settings
for the individual devices can be changed as required. A click on the “Details” tab, underneath the
selected Sync Domain, results in the presentation of the individual reserved / required bandwidths
for the communication types in this synchronization Domain.
Guidelines PROFINET IRT

Here is a summary of the most important rules /guidelines which have to be adhered to when
using PROFINET IRT:
M O
• When IRT is used, there must be a topology. RU
n ho
Update time, bandwidth and other parameters are thereby calculated exactly.
t i
• If several Sync-Domains are to be used, o
C u have to configure a Sync-Boundary for the port
you
which is connected to a PROFINET
r e iradevice of the respective other Sync-Domain.
o Pe
y eg
D
• There can only be one Sync-Master in a Sync-Domain.

• A PROFINET IO-System may only belong to one Sync-Domain.

• All PROFINET devices which are to be configured in a Sync-Domain and synchronized with
IRT must support IRT communication.
• Preferably, the PROFINET IO-Controller and the synchronization role “Sync-Master” should be
handled by the same PROFINET device.
• If only some of the PROFINET devices of a PROFINET IO-System are synchronized, all other
PROFINET devices which do not take part in the IRT communication must be assigned the RT
class "RT" and the Synchronization role "Unsynchronized" in the Sync-Domain.
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
MO
o RU
u t inh
Co
a
P e reir
e g o
Dy

Realizing
12.13. the the
Isochronous Real-Time (Worst Case
Isochronous Real-Time (Worst Scenario)
CaseScript
Scenario)
I/O update time = 1ms, OB35 cycle = 1ms
Max. error = ±2mm
Count packages:

M O
U
Response time: 2 x signal conversion timeIN + I/O update timeIN + 2 x OB35 cycle +
R
o
I/O update timeOUT + 2 x signal conversion timeOUT = 4.4ms
Time span of package from sensor to actuator: 400ms ou tinh

ra C
e i
Per
ego
Jitter during acquisition = 2 x signal conversion time + I/O update time + 2 x OB35 cycle = 3.2ms
2 edges → max. error =D

y
6.4ms

Realizing the Customer Requirements: Isochronous Real-Time (Worst Case Scenario)
After the PROFINET RT solution, if you take the given customer requirements (from the sample
system) and now make the calculations with a PROFINET IRT solution, you will come to the
following result:
• The printing robot can still be controlled without a problem! Compared to the PROFINET RT
solution, the PROFINET IRT solution even provides a speed advantage of 2ms and a
response time of 4.4ms. This corresponds to an increase in the response speed of
approximately 31%!
O
• However, even with a PROFINET IRT-System the measurement of a package with a
M
RU
maximum tolerance of ± 2mm cannot be realized. In the worst case, the error for a package
o
u t inh
measurement is here 32mm and is thereby still outside of the tolerance limits. An increased
accuracy of 10mm (32mm as opposed to 42mm) was achieved, which corresponds to an
Co
increase of approximately 24%, but this is still not sufficient for the requirements of the sample
a
system!
P ereir
e g o
Dy

Isochronous
12.14. Mode
Isochronous Mode
T1-T6 are synchronized

T4
PLC
Optimized data flow
T3 T3
■ PROFINET
M O
R U
o
tinh
Predictable point in time
ou T5
for outputting
T2 ET 200 ET 200
ra C
e i
o Per T6
eg T1
Simultaneous reading of
Dy Simultaneous outputting
all inputs of all outputs

Isochronous Mode
A good example for isochronous mode (cycle synchronization) is a public transit system.
If public transit could move as fast as possible, and would reduce stopping times e.g. at the bus
stops to an absolute minimum, then quite often the (would-be) passengers would miss the bus.
However, in a public transit system the total travel time is actually determined by the individual
cycles of the buses, subways, trains, etc. Therefore, coordinated and well-synchronized transit
cycles are crucial!
The same principle is applied in distributed automation. Fast cycles are of course important, but
only with coordination and synchronization of the individual cycles can an optimized data
throughput be achieved!
M O
The fast and reliable response time of isochronous mode is based on the fact that all data are
RU
supplied “just-in-time”. The equally spaced PROFINET IO-cycle “beats the drum” to achieve this.
o
Advantages of Isochronous mode u t inh
Co
a
reir
Using isochronous mode in a PROFINET IO-System has the following advantages:
• optimized closed-loop control P e
• determinism e g o
Dy
• consistent (simultaneous) reading of input data
• consistent (simultaneous) reading of output data
Note
In order to use isochronous mode, a PROFINET IRT system is required!

Deterministic
12.15. Communication
Deterministic Model Model
Communication
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET
Deterministic IRT - Isochronous Mode
Communication Model- Oversampling Page 19 Siemens AG © 2016
The deterministic communication model works in the following sequence:

• cycle-synchronous reading of the input data
• transportation of the input data to the IO-Controller (CPU) via the PROFINET-subnet
• further processing in the isochronous mode (cycle-synchronous) application of the CPU
• transportation of the output data to the outputting IO-Device via the PROFINET-subnet
• cycle-synchronous outputting of the output data
M O
RU
In order for all input data to be available for transportation via the PROFINET IO-subnet at the
start of the next PROFINET IO-cycle, the read cycle for the I/O gets a “head start” (with the lead
o
u t inh
time TI). TI is the "flash" for the inputs. At that moment, all synchronized inputs are read.
o
TI is required for compensation of analog-to-digital conversion, backplane bus times, or similar.
C
a
The lead time TI can be configured by STEP7 or by you. It is recommended to have STEP7
automatically assign the lead time TI.
P e reir
g o
The PROFINET IO-subnet transports the input data to the IO-Controller. The application can be
e
Dy
started synchronized with the cycle, that is, the Synchronous Cycle OB is called after a
configurable delay time. The user program in the Synchronous Cycle OB determines the process
response and supplies the output data punctually for the start of the next data cycle. The length of
the data cycle is always configured by you.
TO is the compensation from the backplane bus and the digital-to-analog conversion within the
IO-Device. TO is the "flash" for the outputs. At that moment, the synchronized outputs are output.
The time TO can be configured by STEP7 or by you. It is recommended to have STEP7
automatically assign the lead time TO.

Isochronous
12.16. Mode Mode
Isochronous in the in
TIA Portal
TIA Portal
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET
Isochronous ModeIRT
in- TIA
Isochronous
PortalMode - Oversampling Page 20 Siemens AG © 2016
An overview of the properties of isochronous mode can be found in the Properties of the
PROFINET I/O-System in TIA Portal in the Network view after selecting the PROFINET I/O-
System (see picture). Here, the Application details, the TI / TO values as well as the isochronous
mode of participating IO-Devices and their specific TI / TO times are displayed.
By default, the ‘Automatic (detection of) TI / TO values’ is activated. This can also be adjusted
manually, but it is not generally recommended!
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy

Isochronous
12.17. Mode
Isochronous in the
Mode in Cycle
the Cycle
Send clock Send clock Send clock Send clock
CPU (OB sync) OB6x I P O I P O OB6x
IRT IRT IRT IRT

PROFINET IRT IRT IRT IRT
Value capturing
IO-Device Ti To Ti To
M O Ti To
RU
o
tinh
0 1 1
Digital Input
C ou
e ira
Per
Process
eg o
Problem:
Dy
Problem:verpasste
missed
Signalwechsel
signal change

Isochronous Mode in the Cycle
A sample sequence of an input (Process) over several cycles is presented in the picture. The
isochronous mode permits the synchronous reading of all inputs at a specified point in time but it
doesn’t solve the problem of a fast edge change or a signal change between the reading times.
The function “Isochronous mode” requires modules which support this function as well as the IO-
Controller having an organization block for isochronous processing of the program parts:
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
In this OB, the process images must then be synchronized with the instructions “SYNC_PI” and
“SYNC_PO”.
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
MO
o RU
u t inh
Co
a
P e reir
e g o
Dy

Activating
12.18. the the
Activating Isochronous ModeMode
Isochronous in theinModule
the Module
Interface module + Module must

support Isochronous mode
M O
Module supports isochronous
mode but the Interface module
doesn’t
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Activating the Isochronous Mode in the Module
Both the module and the Interface module of the IO-Device must support the function
Isochronous Mode, otherwise the option is, indeed, visible in the module but it is greyed out and
cannot be activated.
Activating the Isochronous Mode requires a Process image partition and the Synchronous Cycle
OB which must be assigned to this module. When the function is activated, the OB is either
already created or it can be created in the course of the activation.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Realizing
12.19. the the
Isochronous Mode (Worst Case
Isochronous Mode (Worst CaseScenario) Script
Scenario)

I/O update time = 1ms, OB35 cycle = 1ms, OB61 cycle = 1ms
Max. error = ±2mm
Count packages:

M O
U
Response time: signal conversion timeIN + 2 x OB61 cycle + signal conversion timeOUT = 2.2ms
R
o
Time span of package from sensor to actuator: 400ms
ou tinh
ra C
e i
Per
Jitter during acquisition = OB61 cycle = 1.0ms
o
eg
2 edges → max. error = 2.0ms
Dy

Realizing the Customer Requirements: Isochronous Mode (Worst Case Scenario)
After the PROFINET RT solution and the PROFINET IRT solution, if you take the given customer
requirements (from the sample system) and now make the calculations with the activated
Isochronous Mode function, you will come to the following result:
• Here as well, the printing robot can once again be controlled without a problem! Compared to
the PROFINET IRT solution, the Isochronous Mode even provides a further speed advantage
of 2.2ms and a response time of 2.2ms. This corresponds to an increase in the response
speed of 50% compared to PROFINET IRT and of approximately 65% compared to
PROFINET RT!
M O
• The measurement of a package with a maximum tolerance U
Rthe error
of ± 2mm, however, still cannot be
h o
is here 10mm and is thereby still outside ofu t
the intolerance limits! Anforincreased
realized with the Isochronous Mode. In the worst case, a package measurement
accuracy of
22mm (10mm as opposed to 32mm) was C oachieved, which corresponds to an increase of
i r a
erofe the sample system!
approximately 69% compared to the PROFINET IRT solution. However, this is still not
P
sufficient for the requirements
y ego
D

Oversampling
12.20. Oversampling
Increase of the accuracy
Increase of the process

data
Requires Isochronous
M O mode
R U
o
tinh
Requires High-Speed (HS)
modules
C ou
e i ra
o Per
eg
Dy
Oversampling
Oversampling means that the send clock that is set is divided into time-equidistant sub-cycles.
The number of how many sub-cycles the send clock is divided into depends on whether a binary
or an analog signal is read. Each sub-cycle then reads a measured value. These read-in
measured values of a data cycle are copied into the Interface module (IM) in the subsequent
send clock and are then available for the processing CPU one cycle later.
The read-in values or output values are transferred to the user data of the module. This means
that the address space of the module increases by the factor of the sub-cycle per channel as a
result. Example: if the Oversampling is 16-fold, then an analog module with 2 bytes user data per
channel now has 2 x 16 bytes = 32 bytes user data instead of 2 bytes user data for the channel.
M O
o RU
Since the sub-cycles must lie, in principle, within a send clock, oversampling requires (unlike the
3-cycle model of isochronous mode) an additional cycle for copying the read-in and output data
t inh
into the Interface module. This results in a 5-cycle model.
u
C o
Note
i r a
P ere requires an isochronous configuration and modules which
The use of the oversampling function
y e o
support this functionalityg(High-Speed modules).
D

Oversampling
12.21. in the
Oversampling in Cycle
the Cycle
Send clock Send clock Send clock Send clock
CPU (OBsync ) OB6x I P O I P O OB6x
IRT IRT IRT IRT

PROFINET IRT IRT IRT IRT
Value capturing
IO-Device Ti To Ti To T To
M O i
Value capturing
R U
Oversampling
n h o
u t i
C o
Process
eir a
P e r
eg o
Signal
Problem:
longer Dy
change
verpasste
is no
Signalwechsel
missed

Oversampling in the Cycle
The isochronous mode with activated oversampling over several cycles is now presented in the
picture. Compared to only isochronous mode, few to no signal changes are now lost depending
on the number of sub-cycles.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Activating
12.22. the the
Activating Oversampling on the
Oversampling onModule
the Module
M O
R UHigh-Speed module
o
tinh
Cou
Sampling rate setting
eira
P e r
eg o
Dy
Activating the Oversampling on the Module
If the function ‘Isochronous mode’ is activated on the module and it supports oversampling, an
entry “XX configuration” can be found under Module parameters in the Properties of the module.
In this entry, the Sampling rate can be defined. The Sampling interval is automatically determined
and displayed.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

12.23. Realizing the Customer Requirements:

Only for the Script (Worst Case Scenario)
Oversampling

Max. error = ±2mm

Response time: signal conversion timeIN + 2 x OB61 cycle + signal conversion timeOUT = 2.2ms
Measurement of package (32-fold oversampling):

M O
RU
o
tinh
Jitter during acquisition = = 31.25µs
2 edges → max. error = 62.5µs C ou

e ira
o Per
eg
Error when measuring package (with current conveyor speed): → 0.31mm
Dy
→ Increasing the conveyor speed to 32m/s is possible!

Realizing the Customer Requirements: Oversampling (Worst Case Scenario)
If you take the given customer requirements (from the sample system) and now finally make the
calculations with the suitable modules and the activated function Oversampling, you will come to
the following result:
• Compared to the solution with the activated isochronous mode, the control of the printing robot
has not changed. With 2.2ms, the printing robot can be controlled without a problem!
• With the functionality Oversampling, the measurement of a package with a maximum
an accuracy of 0.31mm. MO
tolerance of ± 2mm, is now also achieved! With a conveyor speed of 5 m/s you even achieve
RU
The system can be even further optimized in order to increase the conveyor speed to up to
o
32 m/s and still meet the requirement of ± 2mm!
u t inh
C o
a
P e reir
e g o
Dy

Task Description:
IRT,Task
12.24. Isochronous ModeIRT,
Description: andIsochronous
Oversampling
Mode and Oversampling
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
You are to copy your project and save it under the name “IK-TIAPN-IRT”. Then, you are to try to integrate the
functions which you learned in this chapter (such as, IRT, isochronous mode and oversampling) into your
project, parameterize them and understand them.

Task Description
You are to save your initial project under the name “IK-TIAPN-IRT”. Then, you are to try, as far as
possible, to configure and parameterize the topics discussed in this chapter.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

WennAdditional
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / PROFINET IRT – Taktsynchronität – Oversampling Seite 28 Siemens AG © 2016
Note
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy

Time-Based
12.25.1. IOs
Time-Based IOs
4) Required point in time for ID: 82527590

the response is calculated in
the controller
3) Transmission of event and

time stamp via PROFINET
5) Transmission of event and
time stamp via PROFINET
M O
R U
o
tinh
Cou
2)Timer module adds time 6)6)
Timer
Timer
Baugruppe
module adopts
übernimmt
the
stamp to the event den
predetermined
vorgegebenenresponse
Zeitstempel
time
eir a derstamp
Reaktion
andund
switches
schaltet
theden
P e r Aktoractuator
exakt zum
at exactly
vorgegebenen
the
eg o predetermined
Zeitpunkt time
1)Sensor generates event Dy

Time-Based IO
Many activities in a system require a timely, as precise as possible, reproducibility. The
reproducibility can be optimized within limits through shorter CPU cycle times. The use of high-
accuracy inputs/outputs with Time-based IO leads to an even better reproducibility than is
possible by optimizing the CPU cycle time. A further advantage of Time-based IO is in the
independence from the minimum time base of the application cycle.
Defined Response Times

By adding a predetermined time to the time stamp of an edge at the digital input, an output signal
can be output which reacts with a precise delay time that is independent of the application cycle.
M O
Length Measurement
o RU
u t inh
With the difference between two input time stamps and an associated transport speed, the length
of a passing product can be determined.
C o
a
Note
P ereir
g o
You can look at a video on Time-Based IOs on the Siemens pages using the following link:
e
Dy
http://w3.siemens.com/mcms/topics/de/simatic/simatic-technology/videos/Seiten/video-time-
based-io.aspx
You can find further information on “Time-Based IOs” on the Service & Support pages under the
Entry number: 82527590. The technical manual on “Time-Based IOs” can be downloaded here.

Realizing
12.25.2. thethe
Realizing Customer
CustomerRequirements:
Requirements:
Time-Based
Time-Based IOs (Worst Case Scenario)
IOs (Worst Case Scenario)

Max. error = ±2mm
Jitter during acquisition = 1µs
M O
2 edges -> max. error = 2µs
R U
h o
Error when measuring package (with current conveyor speed):
ou tin → 0.01mm
ra C
e r ei
→ Increasing the conveyor speed P
e g o to 1000 m/s is theoretically possible!
Dy

Realizing the Customer Requirements: Time-Based IOs (Worst Case Scenario)
If you take the given customer requirements (from the sample system) and measure the
packages with the help of Time-Based IOs, you will come to the following result:
• The measurement of a package with a maximum tolerance of ± 2mm, is now possible even
more accurately with Time-Based IOs! With a conveyor speed of 5 m/s you achieve an
accuracy of 0.01mm!
The system can be even further optimized in order to theoretically increase the conveyor
speed to up to 1000 m/s and still meet the requirement of ± 2mm!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Terminal-to-Terminal
12.25.3. Terminal-to-TerminalResponse Time
Response Time
ON-Input signal
DI
t faster slower
ON-Output signal
M O
DO
R U
o
ou tinh
ra C Jitter
i
ere t
oP Terminal-to-Terminal
Dyeg Response time
Response time

Terminal-to-Terminal Response Time
The picture illustrates that even the transport of data via the backplane bus of the controller
requires a certain response time. This time is called “terminal-to-terminal response time” among
experts. The response time for the control of an output (as a response to an input) cannot be
faster than the terminal-to-terminal response time.
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

Response
12.25.3.1. Time using
Terminal-to-Terminal an S7-1518
Response asananS7-1518
Time using Example
as an Example
Internal cycles
➢ T1: Sampling of the input signal
T3 T2 ➢ T2: Backplane bus

➢ T3: CPU cycle duration (OB3x)
➢ T4: Conversion of the output signal
T1 T4 M O
R U
o
260µs Terminal-to-terminal
ou tinh
response time!
ra C
e i
Per
(OB35 @ 100µs) for a S7-1518
with central I/Os
eg o
Dy
Terminal-to-Terminal Response Time using an S7-1518 as an Example
The picture illustrates the terminal-to-terminal response time using an S7-1518 as an example.
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

Contents 13
13. Gateways............................................................................................................... 13-2
13.1. Integrating Other Bus Systems ........................................................................................... 13-3
M O
13.2. U
IE/AS-INTERFACE LINK PN IO ......................................................................................... 13-4
R
o
tinh
13.3. DP/AS-INTERFACE LINK ADVANCED ............................................................................. 13-5
13.4. ou
IE/PB-LINK PN IO ............................................................................................................... 13-6
C
13.5.
e ira
S7-1516-3 PN/DP ...............................................................................................................
r 13-7
P e
13.6.
o
PN/PN COUPLER ...............................................................................................................
g 13-8
13.7.
D
PN/PN COUPLER ye as Gateway between Two PROFINET IO-Systems in
Different Subnets ................................................................................................................ 13-9
13.8. PN/PN COUPLER as Shared Device ............................................................................... 13-10
13.9. The Way the PN/PN COUPLER Works ............................................................................ 13-11
13.10. Configuring a PN/PN COUPLER ...................................................................................... 13-12
13.11. Configuring the I/O Areas ................................................................................................. 13-13
13.12. Setting Options PN/PN COUPLER ................................................................................... 13-14
13.13. Task Description: I/O Communication via the PN/PN COUPLER ................................... 13-16
13.13.1. Exercise 1: Configuring the Networking & the PN/PN Coupler ........................................ 13-17
13.13.2. Exercise 2: Parameterizing the PN/PN Coupler ............................................................... 13-18
13.13.3. Exercise 3: Generating a Running Light with the Correct Time Cycle on the
S7-1510SP ........................................................................................................................ 13-19
13.13.4. Exercise 4: Connecting the Transferred Running Light to the Simulator LEDs ................ 13-20
MO
13.13.5. Exercise 5: Parameterizing the Analog Modules .............................................................. 13-21
U
13.14.
o R
Additional Information ....................................................................................................... 13-22
13.14.1. Exercise 6: Scaling Potentiometer1 and Transferring n h
ti Value to the LEDs............................ 13-24
It ................................................... 13-23
13.14.2. Exercise 7: Connecting Transferred Potentiometer
C o u
i r a
P ere
y ego
D
IK-TIAPN – Gateways
13. Gateways
Objectives
... be familiar with the various devices which make a gateway possible
for the user
... understand how an IO-Controller / IO-Controller communication

M O
functions and what has to be taken into consideration
RU
… o
be familiar with the function of a PN/PN-COUPLER and be able to
explain it
ou tinh
…
ra C
be able to commission a PN/PN coupler
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Gateways Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Integrating
13.1. Other Other
Integrating Bus Systems
Bus Systems
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Gateways Page 3 Siemens AG © 2016
Fieldbus Integration
With PROFINET you can integrate existing fieldbus systems (for example, PROFIBUS, AS-
Interface, MODBUS,…) via a proxy-capable PROFINET device. The devices of these fieldbus
systems are mapped on proxy PROFINET devices. With that, you can design any mixed systems
you like consisting of fieldbus and Ethernet-based partial systems. This makes an integrated data
exchange possible.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
13.2.IE/AS-INTERFACE LINKLINK
IE/AS-INTERFACE PN IO
PN IO
IO-Controller
IE/AS-INTERFACE
LINK PN IO
PROFINET IO
M O
RU
o
tinh
Gateway
a Cou AS-Interface
P e reir
e g o
Entry-ID: 24057268
Dy
Entry-ID: 22712154 Digitale E/A Module

Page 4 Gateways
IE/AS-INTERFACE LINK PN IO
PROFINET is increasingly finding its way into automation. This has the advantage of uniform
network structures from the operations level down to the field level. On the sensor/actuator level,
on the other hand, the AS-i technology continues to be used in larger plants because of the
cost-effective wiring of field devices.
The IE/AS-i LINK PN IO from SIMATIC NET offers the possibility, as central gateway, of
connecting up to two AS-i subsystems as AS-i Master and PROFINET Device to one PROFINET
network.
The IE/AS-INTERFACE LINK PN IO is available in two versions:
• 6GK1411-2AB10 - IE/AS-INTERFACE LINK PN IO, 1 M.:
M O
connected! o RU
IE/AS-INTERFACE LINK PN IO as single master. Only one AS-Interface segment can be
t i n h
• 6GK1411-2AB20 - IE/AS-INTERFACE LINK
IE/AS-INTERFACE LINK PN IO as double C uPN IO,Up2 M.:
omaster. to two AS-Interface segments can be
i r a
ere
connected!
P
Note
y ego
On the Service &D
Support pages, you will find the manual for the IE/AS-INTERFACE LINK PN IO
under the Entry-ID: 22712154. Under the Entry-ID 24057268, you will find an application example
with further information on the topic of “Integration of an AS-i System in PROFINET with the IE-
AS-i LINK PN IO”. Even though this example is based on S7-300, it should still illustrate the basic
interfacing of an AS-Interface with the help of the IE/AS-INTERFACE LINK PN IO.
13.3.DP/AS-INTERFACE LINKLINK
DP/AS-INTERFACE ADVANCED
ADVANCED
This configuration is only possible as of STEP7 V13 SP1!

Older Versions must work with the GSD-file of DP/AS-INTERFACE LINK !
IO-Controller
DP/AS-INTERFACE
LINK ADVANCED
PROFIBUS DP
connection––kein
Ethernet Anschluss
Ethernet no
M O
PROFINET
RU
o
tinh
Gateway
a Cou AS-Interface
P e reir
e g o
Entry-ID: 88778900
Dy
Entry-ID: 22710305 Digitale E/A Module

Page 5 Gateways
DP/AS-INTERFACE LINK ADVANCED
If an AS-Interface system is to be connected to PROFIBUS instead of PROFINET, then the
DP/AS-INTERFACE LINK ADVANCED (as central gateway) can connect up to two AS-i sub
systems as AS-i Master and PROFIBUS SLAVE into a PROFIBUS DP system.
The DP/AS-INTERFACE LINK ADVANCED is available in two versions:
• 6GK1415-2BA10 - DP/AS-INTERFACE LINK ADVANCED, 1 M.:
DP/AS-INTERFACE LINK ADVANCED IO as single master. Only one AS-Interface segment
can be connected!
• 6GK1415-2BA20 - DP/AS-INTERFACE LINK ADVANCED, 2 M.:
M O
DP/AS-INTERFACE LINK ADVANCED as double master. Up to two AS-Interface segments
can be connected!
o RU
Note u t inh
C o
a
reir
On the Service & Support pages, you will find the manual for the DP/AS-INTERFACE LINK
e
ADVANCED IO under the Entry-ID: 22710305. Under the Entry-ID 88778900, you will find an
P
e g o
FAQ on the topic “How do you configure gateways on a SIMATIC S7-1500 controller?”
Dy
13.4.IE/PB-LINK PN IO
IE/PB-LINK PN IO
Slave IO-Controller
IE/PB-LINK PN IO
PROFIBUS PROFINET IO
M
Gateway O
R U
o
Slave
ou tinh
ra C
e i
o Per
eg
Dy
Entry-ID: 19299692

Page 6 Gateways
IE/PN-LINK PN IO
If a gateway has to be established between the PROFIBUS and the PROFINET, the IE/PN-LINK
PN IO can be used for this. Depending on the application, the IE/PN-LINK PN IO can either be
configured as gateway and as PROFINET IO-Device or only as gateway.
Note
On the Service & Support pages, you will find the operating instructions “Network Gateway IE/PB
Link PN IO for Industrial Ethernet / Manual Part BL1” under the Entry-ID: 19299692.
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy
13.5.S7-1516-3 PN/DP
S7-1516-3 PN/DP
Slave
IO-Controller + Master
PROFIBUS PROFINET IO
M
Gateway O
R U
o
Slave
tinh
Cou
IO-Device
eira
P e r
eg o
Dy
Page 7 Gateways
S7-1516-3 PN/DP
An S7-1500 can also be used as a gateway. If both a PROFIBUS and a PROFINET interface are
present, the S7-1500 can simultaneously take on the role of a Master and that of an IO-Controller
in the two bus systems. The exchange of data with other IO-Controllers or PROFIBUS Masters
must, however, take place via known communication methods.
Note
All S7 controllers of the 1500 series which have the abbreviation PN/DP as an appendix can
establish a gateway between PROFINET and PROFIBUS. The same can be applied to S7
controllers of other families!
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy
13.6.PN/PN Coupler
PN/PN COUPLER
IO-Controller 1 IO-Controller 2
PN/PN COUPLER
PROFINET IO 1 PROFINET IO 2
Data set x
M O Data set x
RU
Receipt
o
tinh
Acyclic
azyklische Kommunikation acknowledgement
communication
C ou
Data set y Data set y
e i ra
Per
Receipt
acknowledgement
Cyclic
eg o
Dy
communication
I/O data I/O data
Entry-ID: 44319532

Page 8 Gateways
Communication PROFINET
PROFINET does not permit any direct data exchange between two IO-Controllers.
Communication always only takes place between the IO-Controller and its IO-Devices. If a
communication is to be implemented between two IO-Controllers or two PROFINET IO-Systems
are to be coupled with one another, other supplementary devices such as a PN/PN coupler are
used.
PN/PN COUPLER
The PN/PN COUPLER is used to connect two PROFINET IO-Systems to one another and to
exchange data. User data can be used via input or output address areas or data sets.
M O
When I/O data is transmitted, you must make sure that the maximum size of the transferable
RU
input and output data is 1024 bytes. The input data and the output data can be split any way you
o
u t inh
like so that 824 bytes input data and 200 bytes output data could be configured, for example.
Note C o
i r a
P e e willunder
On the Service & Support pages,ryou
“SIMATIC Bus Links PN/PN COUPLER”
find more detailed documentation on the topic of
e g o the Entry-ID: 44319532.
Dy is used, the two PROFINET networks are completely separated!

When a PN/PN COUPLER
13.7. PN/PN COUPLER as Gateway between Two PROFINET IO-

PN/PN COUPLER
Systems as Gateway
in Different Subnets
IP: 192.168.222.13 IP: 172.163.145.122

Subnet: 255.255.255.0 Subnet: 255.255.255.0
IO-Controller 1 IO-Controller 2
PN/PN COUPLER
M O
R U
o
PROFINET IO 1
ou tinh
PROFINET IO 2
ra C
e i
IP: 192.168.222.222
o Per IP: 172.163.145.111
yeg
Subnet: 255.255.255.0 Subnet: 255.255.255.0
D
A PN/PN COUPLER can connect two PROFINET IO-Systems even though they are in different
subnets. Therefore, a cross-network CPU-CPU communication is possible!

Page 9 Gateways
PN/PN COUPLER as Gateway
The two PROFINET interfaces of a PN/PN coupler must not be assigned the same IP address,
however, the two interfaces can have the same network address, that is, be in the same subnet.
Unlike an I-Device communication, it is however also possible with a PN/PN coupler that the two
PROFINET interfaces are in different subnets and therefore have different network masks. In this
case, the coupler acts as gateway and makes a cross-network communication between two IO-
Controllers possible!
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy
13.8.PN/PN COUPLER
PN/PN as Shared
COUPLER Device
as Shared Device
Settings for Number of IO-

Controllers
Select Access of
IO-Controller
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 10 Gateways
PN/PN COUPLER as Shared Device
The PN/PN coupler can also be operated as a Shared Device. It is possible to permit up to 2 IO-
Controllers per PROFINET interface access to the PN/PN coupler. In total, up to 4 IO-Controllers
can exchange data with one another via the coupler as gateway between two PROFINET I/O-
Systems! However, there can only be 2 IO-Controllers per PROFINET.
The two IO-Controllers which are to be permitted access to one of the PROFINET interfaces must
not be in the same project since the functionality Shared Device cannot be parameterized in one
project. For this, a second project with the second IO-Controller must be created and the PN/PN
coupler is copied into this. That is, the same PN/PN COUPLER must be in both projects!
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
13.9.TheThe
WayWay
the the
PN/PN COUPLER
PN/PN Works
COUPLER Works
M O
R U
o
tinh
Maximum size of 1024
Cou
bytes per side
eira
P e r
o Any split between IN
Dyeg and OUT

Page 11 Gateways
The Way the PN/PN COUPLER Works
The PN/PN COUPLER has two PROFINET interfaces which are each connected to one subnet.
In the configuration, two IO-Devices are made from this one PN/PN COUPLER, that is, one IO-
Device each for each station with its subnet. The respective other part of the PN/PN COUPLER is
known as the coupling-partner. When the configuration is completed, the two parts are brought
together internally in the coupler, so to speak. Both PROFINET interfaces must, however, be
assigned a separate IP address as well as a separate PROFINET device name!
The two interfaces of the coupler must not be assigned the same IP address!
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy
Configuring
13.10. a PN/PN
Configuring COUPLER
a PN/PN COUPLER
PN/PN COUPLER
PROFINET X1
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
PN/PN COUPLER
PROFINET X2

Page 12 Gateways
Configuring a PN/PN COUPLER
In the ‘Hardware catalog’ in the TIA Portal, the PN/PN Coupler is located under ‘Other field
devices’. Since it only has PROFINET interfaces, it is arranged under the PROFINET IO tab.
There, it is located under the name “Gateway”, since it can also manage the transition between
two PROFINET I/O-Systems, as already discussed.
The PN/PN COUPLER is available in several Firmware versions. However, as a particular
feature, under each Firmware version there are two entries with the same MLFB number. This is
due to the fact that the PN/PN Coupler has two PROFINET IO interfaces to which the IO-
Controllers can be connected. These two PROFINET interfaces can be located in the same
project as well as in the same subnet.
O
On the device, these are, just as in the Hardware catalog, identified with X1 and X2 so that there
M
RU
can be no mix up.
o
u t inh
C o
a
P e reir
e g o
Dy
Configuring
13.11. the I/O
Configuring theAreas
I/O Areas
M O
U Swapped configuration of
h oR the I/O areas
o u tin
a C
e r eir
o P
eg
Dy
Page 13 Gateways
Configuring the I/O Areas
The input and output addresses of the two PROFINET interfaces must be configured swapped.
That is, when an input area is configured on the first slot of the PROFINET interface X1, an
output area of the same size must be configured on the first slot of the PROFINET interface X2. If
this is not taken into account, it will not be possible to exchange I/O data between the two
PROFINET I/O-Systems.
An automatic configuration of the second PROFINET interface to match the first interface is
unfortunately not possible. This must be configured manually.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
Setting
13.12. Options
Setting PN/PN
Options COUPLER
PN/PN COUPLER
M O
R U
o
ou tinh Control whether one or both
ra C voltages are missing
e i
o Per Bit0 least significant
yeg
I-Byte displays validity
D Valid data is sent

(STOP PLC?)

Page 14 Gateways
Setting Options PN/PN COUPLER
The PN/PN COUPLER allows you to parameterize various settings for the purpose of diagnostic
possibilities. These only have to be activated and not programmed. When the setting is activated,
the one side of the coupler then automatically generates an error message.
Voltage Control PS 1
By activating the option “Voltage control PS1” a failure of the power supply at connector PS1 can
be diagnosed. This setting should only be activated if the power supply PS1 is actually connected
to the PN/PN Coupler!
Voltage Control PS 2
U MO
The option “Voltage control PS2” activates the diagnosis o on Rthe power supply PS2. If this no
longer be energized, the PN/PN Coupler triggers i h
tannalarm.to the
Just as for “Voltage control PS1”, this
C u
option should only be activated if it is actuallyoconnected PN/PN COUPLER!
eir a
Note
P e r
When both voltage controlg ooptions are activated and connected, only one of the two power
ea time. If one of the two power supplies fails, the other power supply
supplies is operativeyat
D
automatically becomes operative. If both supplies fail, the PN/PN coupler is no longer under
power and can no longer transmit an error message.
Data Validity Display DIA

With the help of the “Data validity display DIA”, you can determine whether the input and output
data transmitted via the PN/PN Coupler are still valid. A check is made as to whether the IO-
Controller(s) connected on the opposite side of the Coupler is/are still sending valid data.
The validity of the data is determined with the help of the least significant input byte on the
receiving side. Bit 0 must be queried. When the option is activated, this bit has the following
meaning:
• Bit 0 = 0:
The data received is invalid since, for example, a PROFINET interface of the PN/PN
COUPLER is faulty or the IO-Controller in the “other” subnet has failed.
• Bit 0 = 1:
The data received is valid. All user data supplements have the status “Good”.
Diagnostic Data Validity

By activating the setting option “Diagnostic data validity” the validity of the transmitted data can
be controlled without having to use the Bit 0 in the least significant byte of the receiving side. This
option triggers an error message on this side of the PN/PN Coupler when invalid data is received.
This happens, for example, when the IO-Controller, which is connected to the opposite
PROFINET interface, is in the STOP state.
Note
The above setting options can be activated or deactivated for both PROFINET interfaces of the
PN/PN COUPLER independent of one another!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Task
13.13. Description:
Task Description:
I/O I/O
Communication via the
Communication viaPN/PN COUPLER
the PN/PN COUPLER
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Page 15 Gateways
Task Description
Finally, you are now to complete the Hardware Configuration of the system and integrate the
PN/PN COUPLER. The PN/PN Coupler enables an I/O data exchange between the S7-1513 and
the S7-1510SP.
On the S7-1510SP, you will generate a running light, along the lines of the S7-1513 running light,
and send it to the S7-1513 via the PN/PN Coupler. There it will subsequently be presented on the
output byte of the LEDs on the simulator board.
From the S7-1513, Potentiometer1 is sent to the S7-1510SP which there controls the LEDs on
the simulator.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Exercise 1:
Configuring
13.13.1. Exercise 1:the Networking
Configuring the & the PN/PN
Networking Coupler
& the PN/PN Coupler
M O
R U
o
outinh
ra C
ei
o Per
eg
Dy
Page 16 Gateways
Task
You are to complete the networking of the system and connect the two PROFINET interfaces of
the PN/PN Coupler to the SCALANCE XC208. Port P8 of the SCALANCE XC208 is to be
connected to Port P1 of the PROFINET interface X1 and Port P5 of the SCALANCE to Port P1 of
the PROFINET interface X2 of the PN/PN Coupler. Then you are to assign the PN/PN Coupler to
the two controllers in the respective projects. The PROFINET interface X1 is assigned to the S7-
1513 as IO-Device and the PROFINET interface X2 is assigned to the S7-1510SP. The interfaces
will be parameterized in the next exercise.
What to Do
M O
1. Network Port P8 of the SCALANCE XC208 to Port P1 of the interface X1 of the PN/PN
Coupler.
o RU
u t inh
2. Network Port P5 of the SCALANCE XC208 to Port P1 of the interface X2 of the PN/PN
Coupler.
Co
a
reir
3. Using drag & drop, drag the PROFINET interface X2 of the PN/PN Coupler into the project
e
IK-TIAPN_en_Shared_Device and assign it to the S7-1510SP.
P
o
g the PROFINET interface X1 of the PN/PN Coupler into your initial
4. Using drag & drop,edrag
y
D to the S7-1513.
project and assign it
5. Save your projects.
Exercise
13.13.2. 2: 2:
Parameterizing the
the PN/PN Coupler
PN/PN Coupler
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 17 Gateways
Task
You are to parameterize the PN/PN Coupler in such a way that it exchanges 8 bytes between the
two controllers using the Transfer area. These 8 bytes are divided into two 4s blocks respectively.
That is, 4 bytes are sent from the S7-1513 to the S7-1510SP and 4 bytes are also received by the
S7-1513 from the S7-1510SP.
In the S7-1513 project, the Start address of the PROFINET interface X1 of the Coupler is “1111”.
In the S7-1510SP project, on the other hand, the Start address of the PROFINET interface X2 of
the Coupler is “2222”.
What to Do
M O
1. Parameterize the PROFINET interfaces X1 and X2 of the PN/PN-COUPLER as shown in the
picture and as described in the task.
RU
2. Save your projects.
t i n ho
3. Download your modifications into bothC ou After that, all devices should light up green.
controllers.
r e ira corrections!
If necessary, make the required error
o Pe
y eg
D
Exercise
13.13.3. 3: 3:
Exercise Generating
GeneratingaaRunning Lightwith the Correct Time Cycle on the
Running Light
with the Correct Time Cycle on the S7-1510SP
S7-1510SP
M O
RU
o
ou tinh
ra C
ei
Drag&Drop
P e r
o
Adjust the time cycle
DyegAdjust the output byte
No switch on and
switch off
Page 18 Gateways
Task
From the S7-1513, you are to copy the OB for the running light control on the ET 200SP into the
S7-1510SP and then you are to name it “RunningLight1513”. Furthermore, the time cycle for
calling this block must be adjusted to a sensible size. It should no longer be possible to switch the
running light on and off and instead of the output byte “QB4”, the output byte “QB2222” is now to
be controlled. Give the QB2222 the symbolic name “PN-PN_RunningLight”.
What to Do
1. Copy the “RunningLightET200SP” block from the S7-1513 into the S7-1510SP.
M O
2. Change the name to “RunningLight1513”.
RU
t i n ho
3. Make the necessary changes to the block according to the task.
C ou
4. Save your project and download your modifications into the S7-1510SP.
eir a
Note
e r
Pvalue for the time cycle of the OB. This can then be fine-tuned in
g o
First of all, estimate a suitable
the next exercise. ye
D
Exercise
13.13.4. 4: 4:
Exercise Connecting
Connectingthe
the Transferred
Transferred Running Light to the Simulator
Running
LEDs Light to the Simulator LEDs
New Program Cycle

Organization block
M O
R U
o
ou tinh
ra C
e i
Control
o Per
Simulator LEDs
eg
Dy

Page 19 Gateways
Task
The running light transferred via the PN/PN Coupler is now to be connected to the LEDs of the
simulator board in the S7-1513. For this, you are to create a new Program Cycle organization
block with the name “PN-PN”. In it, you are to program the control of the LEDs of the simulator
board. Name the input byte of the PN/PN Coupler “PN-PN_RunningLight” and the output byte of
the LEDs “Sim_LEDs”. The simulator LEDs “Sim_LEDs” are assigned to the output byte %QB0.
What to Do
1. Create a new Program Cycle OB with the name “PN-PN”.
M O
2. Program the block according to the task.
RU
t i n ho
3. Save your changes and download these into the S7-1513.
4. Check the control of the Simulator LEDs o
C u adjust the time cycle of the OB30 in the
and
S7-1510SP, if necessary.
r e ira
o Pe
y eg
D
Exercise
13.13.5. 5: 5:
Parameterizing the
the Analog Modules
Analog Modules
M O
RU
o
ou tinh
ra C
ei
o Per
Unused channels
eg
Dy
Page 20 Gateways
Task
So that the analog value from Potentiometer1 can be transferred via the PN/PN Coupler, the
analog inputs and analog outputs must first be parameterized. The exact parameterization is to
be taken from the picture. All unused outputs are to be deactivated for performance reasons.
What to Do
1. Parameterize the analog modules according to the task / picture.
3. Test your changes using a Watch table. The analog values are already created in the tag table
"1513CaseVariables".
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
WennAdditional
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Netzübergänge Seite 20 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Exercise 6:
Scaling
13.14.1. Potentiometer1
Exercise and Transferring
6: Scaling Potentiometer1 It
and Transferring It
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 22 Gateways
Task
You are to create a scaling for Potentiometer1 so that the LEDs of the simulator board of the S7-
1510SP case act like a level indicator. That is, for a potentiometer value of 0V no LEDs light up,
for a potentiometer value of 10V, on the other hand, all LEDs light up. When the analog value
increases from 0V to 10V, more and more LEDs light up.
What to Do
1. Open the Program Cycle OB “PN-PN” on the S7-1513.
M O
RU
Note
t i n ho
You require three blocks for the conversion of
C outhe analog value. Use the combination of NORM_X
and SCALE_X and then make use of the
can be scaled to the output data r e i
type. r a advantages of the CALCULATE Box. Finally, the value
P e
For testing the conversionoit is recommended that you do the next exercise first so that a control
of the LEDs and withy eg a visualization of the programming can be done.
that
D
Exercise 7: Connecting Transferred
Potentiometer
13.14.2. Value to the
Exercise 7: Connecting LEDs Potentiometer Value to the LEDs
Transferred
New Program Cycle

organization block
M O
R U
o
ou tinh
ra C
e i
o Per
eg
ControlDy
Case LEDs

Page 23 Gateways
Task
The scaled Potentiometer value transferred via the PN/PN Coupler is now finally to be displayed
on the LEDs of the S7-1510SP case. You are to program this function in the Program Cycle OB
“PN-PN” which you still have to create. Name the input byte of the PN/PN Coupler
“PN-PN_AnalogueValue” and the output byte of the LEDs “SimLEDs1510SP”.
What to Do
1. Create a new Program Cycle OB with the name “PN-PN” on the S7-1510SP.
3. Save your changes and download these into the S7-1510SP.
U MO
4. If necessary, adjust the conversion of the analog valueR
that the LEDs fulfill the required functionality of n h o indicator.
of the Potentiometer in the S7-1513 so
o u ti a level
r a C
i
P ere
y ego
D
Contents 14
14. Communication Possibilities in TIA Portal ........................................................ 14-2
14.1. Basic Terms ........................................................................................................................ 14-3
M O
14.2. U
Transmission Media for SIMATIC Communication ............................................................. 14-5
R
o
tinh
14.3. Standard Connections via an S7-1500 ............................................................................... 14-6
14.4. ou
Types of Connections ......................................................................................................... 14-7
C
14.5.
e ira
Connection Resources ........................................................................................................
r 14-8
P e
14.6.
e g o
Connections ........................................................................................................................ 14-9
Properties of a y
14.7.
14.7.1.
D Connection ............................................................................................... 14-10
Fully Specified Connection ............................................................................................... 14-11
14.7.2. Unspecified Connection .................................................................................................... 14-12
14.7.3. Connection ID ................................................................................................................... 14-13
14.7.4. Special Connection Properties: Active Connection Establishment for Two-way Connections14-14
14.7.5. Special Connection Properties: One-way Connection ...................................................... 14-15
14.7.6. Address Details of the Different Connections ................................................................... 14-16
14.7.6.1. TSAP for S7 Connections (only S7-1500/S7-1200).......................................................... 14-17
14.7.6.2. TSAP for S7 Connections (at least 1 Classic CPU).......................................................... 14-18
14.7.6.3. TSAP for Unspecified S7 Connections ............................................................................. 14-19
14.7.6.4. TSAP for ISO-on-TCP Connections.................................................................................. 14-20
14.7.6.5. Port for UDP and TCP Connections ................................................................................. 14-21
14.8. Configured Connections ................................................................................................... 14-22
14.9. Programmed Connection .................................................................................................. 14-23
14.10. O
Communication via Ethernet with regard to the OSI Model .............................................. 14-24
M
14.11.
RU
Communication in TIA Portal ............................................................................................ 14-25
14.12.
i n ho
Graphic Creation of a Connection..................................................................................... 14-26
t
14.13. C ou
Textual Creation of a Connection ..................................................................................... 14-27
i r a
14.14.
ere......................................................................................... 14-28
Task Description: Connections
P
y ego
D
IK-TIAPN - Communication Possibilities in TIA Portal

14. Communication Possibilities in TIA Portal

Objectives
… be familiar with the basic terms of communication
... get an overview of different communication possibilities between

stations in the TIA Portal
M O
... U
be familiar with connection types and be able to explain what
R
connection resources are o
... ou tinh
be able to explain the properties of a connection
ra C
e i
Per
... be familiar with the different TSAPs for the various connections
eg o
... be able to create a connection both graphically and textually
Dy
SITRAIN
IK-TIAPN / Communication Possibilities in the TIA Portal Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P ereir
e g o
Dy

14.1.Basic Terms
Basic Terms
Entire network
verschiedene
Different subnets
Subnetze
Station
M O
R U
o CP for network
ou tinh separation / security
ra C
e i
o Per
eg
Dy
Communications-capable
kommunikationsfähige
Baugruppe
module

Page 3 Communication Possibilities in the TIA Portal
Basic Terms
This chapter deals with the basic terms and principles of communication which are relevant for
the exchange of information between automation devices amongst themselves and to Operator
Panels and PCs.
Communication
The term ‘communication’ refers to the transmission of data between two communication partners
which can very well have different performance characteristics. Communication also means the
control of the communication partner as well as the querying of the operating status of the
communication partner.
M O
The communication can be done via different communication paths, such as, via the integrated
RU
communications interface of the CPU, via a separate communications processor (CP), a
o
u t inh
communications module (CM) or via the integrated backplane bus.
Communication Partner C o
e i r a
P erdata.
A communication partner is a communications-capable module which is able to communicate. To
ego Communication partners can be CPUs or FMs, for example.

communicate means exchanging The communication partner can be located in the same
device or in another device.
D y
Station
A station is a device which can be connected to one or more subnets as a unit that belongs
together (for example, an automation system, a programming device, an Operator Panel/System,
a PC, a third-party device).
Subnet
A subnet is the entity of all physical components which are necessary to build a data transmission
line as well as the associated common methods for data exchange.
The devices on a subnet are connected to one another without gateways. The physical ‘whole’ of
a subnet (MPI, PROFIBUS, Industrial Ethernet) is also referred to as a transmission medium.
Each subnet has a unique SubnetID.

Network
A network consists of one or more subnets (of the same or different kind) which are connected to
one another. It includes all stations which can communicate with one another.
Communication Functions
Communication functions are those functions provided by a software interface that use
communication services. Communication functions can transmit data between communication
partners with different performance data, they can control the communication partner (for
example, put it in the STOP state) or they can query its current operating status.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

14.2.Transmission Media
Transmission for SIMATIC
Media Communication
for SIMATIC Communication
ETHERNET PROFINET IO PROFIBUS DP

Acyclic Cyclic Cyclic
communication communication communication
Non time-critical Time-critical Time-critical
applications applications applications
Not deterministic Deterministic M O
Deterministic
U
RMaster – Slave &
Controller – IO-Controller – o
Controller
ou
IO-Device tinh Slave – Slave
communication
ra C
communication communication
e i
o Per
eg
Dy
Transmission Media
To ensure communication between a sender and a recipient, they must be connected via a
transmission medium. In the SIMATIC world, there are three very well-known transmission media
for communication:
• ETHERNET
• PROFINET IO
• PROFIBUS DP
The most important characteristics of these three main communication media are shown in the
picture.
M O
RU
Note
t i n ho
Of course, there are other transmission media u
C o for a SIMATIC communication, such as, the AS-
PROFINET / Industrial Ethernet, eir
a
Interface Bus. However, in the following we will focus on communication with the help of
Pe r
eg o
D y

14.3.Standard Connections
Standard via an
Connections viaS7-1500
an S7-1500
PN PN S7- Open User Modbus Web MRP

S7-1500 IO- Controller I-Device Comm. Comm. TCP Server
PROFINET
X1
PROFINET
M O
X2
R U
o
ou tinh
C
ra not support
reiPROFINET
Second PROFINET Does all
interface
P e functions
e g o
Dy

Page 6 Communication Possibilities in TIA Portal
Standard Connections via the Integrated Interface of an S7-1500
An S7-1500 makes a large number of communication connections possible without the additional
acquisition of external communications modules (CMs) or communications processors (CPs). The
most common types of connection are presented in the picture as well as the interface of an
S7-1500 via which these can be operated.
As of the series >= S7-1515, the S7-1500 not only has a PROFINET interface onboard but also
has a second integrated PROFINET interface. This one, however, doesn’t support all PROFINET
functions. IRT as well as MRP, respectively, MRPD cannot be used.
Furthermore, this second interface can be used to separate the networks between the office
connection and the automation. Even S7 communication or an Open User Communication (OUC)
O
is possible. An S7-1518 has two PROFINET interfaces as well as one ETHERNET interface.
M
RU
Note
t i n ho
The first PROFINET interface must be locatedu
C o intoa have
interface. It is not possible for the two interfaces
different subnet than the second PROFINET
the same network address! In the case
of an S7-1518, all three interfaces e i r
must abe located in different subnets, that is, have three
different network addresses! Per
y ego
D

14.4.Types of Connections
Types of Connections
PG HMI TCP ISO-on-TCP UDP ISO Modbus S7

TCP
Automatic
connection
Programmed
connection
M O
Configured RU
o
connection
ou tinh
ra C
e i
Per
Permanently requires
resources
eg o
Can release the
Dy
resources again

Types of Connections
A connection between two communication partners can be established in three different ways:
• Automatic connection
• Programmed connection
• Configured connection
Automatic Connection
An automatic connection is established and then disconnected once again without any help from
O
the user. These types of connection include a PG connection as well as an HMI connection.
M
RU
Programmed Connection
t i n ho
ou are not configured in the Network view / the
In STEP7, programmed (not configured) connections
Connection table. These connections are C
ira function is called. Upon completion of the data
only specified through the destination address and
r e
implicitly established when the communication
e if need be. These connections also require connection
o P
transmission they are disconnected,
resources on the CPUs.gHowever, these are only occupied (used) as long as the programmed
e
DyAfter the connection is disconnected, the resource is released once more.
connection is active.
Configured Connection
This type of connection is configured in TIA Portal in the Network view. After that, the connection
can be found in the "Connections" tab in the Network view. For each connection, a local ID is
assigned for the respective connection end point. This local ID is required for the
parameterization of the communication functions. The local ID references a data area which,
among other things, contains its own address information and that of the communication partner.
Each configured connection permanently occupies (uses) a specific connection resource of the
controller.

14.5.Connection Resources
Connection Resources
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Connection Resources
Each communication connection between two devices requires connection resources on the
participating stations for the two end points of the connection. That is, sufficient free resources
must be available in the respective communication partners who want to exchange information
with one another. If all connection resources of a communication partner are occupied (used), no
new connection can be established.
Overview of Connection Resources

Each communication connection between two devices requires connection resources on the
participating stations for the two end points of the connection. That is, sufficient free resources
M O
must be available in the respective communication partners who want to exchange information
RU
with one another. If all connection resources of a communication partner are occupied (used), no
o
new connection can be established.
u t inh
Note C o
i r a
The maximum number of possible
P eorreconnections differs depending on the controller,
go data of the respective device or, in part, in the general properties

communications processor (CP) communications module (CM). More information on this can
always be found in theetechnical
y
D Portal.
of the device in TIA
As soon as an online connection to a station is established, an overview of all offline existing and
online used connections can be opened via the Diagnostics tab in the Inspector window. This is
found in the section "Connection information".

14.6.Connections
Connections
Display in the Network

view
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Highlighted connection
is emphasized

Connections
A connection is a logical assignment of two communication partners for executing communication
services. The connection is directly linked with a communication service. Each connection has
two end points (one on each CPU or CP/CM) which contain the necessary information for
addressing the communication partners as well as further attributes for establishing the
connection. The communication functions in the user program only reference the local end point
of the connection.
For each end point of a connection, one connection resource is used.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

14.7.Properties of aof
Properties Connection
a Connection
Online status of the

connections
Rough overview of the

Properties
M O
R U
Further Properties of a
o
tinh
connection
C ou
e i ra
o Per
eg
Dy
Properties of a Connection
A connection has various properties which must be set by you so that the connection functions
correctly. Depending on the communication service which is linked with the connection, these
properties can differ. The picture gives you an overview of the different properties of a connection
which are dealt with in the following:
• Participating controllers to the connection. Is it a fully specified or an unspecified connection?
• IDs of the participating stations.
• Does the station actively establish the connection or does it wait for the partner station to
establish the connection?
M O
• Is it a one-way or two-way connection?
o RU
u t inh
• Which address details does the connection have? TSAP, Port, …?
• Is it a configured or a programmed connection? C o
a
P e reir
e g o
Dy

Fully
14.7.1. Specified
Fully Connection
Specified Connection
Way there and way

back
M O Fully specified
RU connection
o
ou tinh
ra C
e i
o Per
eg
Dy
Fully Specified Connection
When a connection is configured as a fully specified connection then it means that the connection
partner is located in the same project and that the two stations are also networked. One of the
features of a fully specified connection is that the addresses and the network parameters of both
the local as well as the remote communication partner are defined. The communication
connection is operational after the connection parameters have been loaded into the device.
A fully specified connection in the project always creates two connections with the same name in
the Network view – one communication connection for the connection from the Local station to
the Partner station as well as one communication connection for the path from the Partner station
to the Local station. This means that a communication connection can always only be used in one
O
direction. A two-way exchange of data always requires two communication connections.
M
o RU
u t inh
Co
a
P e reir
e g o
Dy

Unspecified
14.7.2. Connection
Unspecified Connection
Unspecified
connection
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Unspecified Connection
Connections to a not yet known device (for example, a diagnostic device) are configured as an
"unspecified" connection. This means that the communication partner is not located in the project
and/or is not networked.
For the configuration and parameterization of the connection, only settings for the local partner
can be made. The settings for the remote partner must then be made in the project in which the
station is located. For that reason, after the connection parameters have been loaded into the
station, an unspecified connection is only operational to a certain extent.
An unspecified connection creates only one connection in a project. Unlike a fully specified
station to the partner station is configured. M O

connection, the way there and the way back are not configured; only the way from the local
o RU
u t inh
C o
a
P e reir
e g o
Dy

Connection
14.7.3. IDID
Connection
M O Local ID + Partner ID for
RU fully specified connection
o
tinh
Cou
Only Local ID for
unspecified connection
eir a
P e r
eg o
Dy
Connection ID
An ID must be assigned to a connection so that the controller can make the assignment of the
communication blocks in the program of the controller to the configured and programmed
connections on the controller. A connection ID may only be used once.
Each communication block has an input parameter “ID” at which the local ID is parameterized in
hexadecimal notation.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Special
14.7.4. Connection
Special ConnectionProperties:
Properties: Active Connection
Active Connection Establishment for Two-
Establishment for
way Connections Two-way Connections
Two-way
M O connection
R U
o
outinh
ra C
Only one station may
ei
actively establish the
o Per
eg
connection
Dy

Active Connection Establishment
To ensure a controlled connection establishment, it is necessary to determine which
communication partner establishes the connection and which one does not. Connections must,
therefore, be active in one end point and passive at the other end point. Which end point
manages the active connection establishment is, however, irrelevant for the linking between two
controllers. If, however, a link between a PC and a controller is made, this point must be
evaluated. As a rule, the active connection establishment is made from the PC-side.
If the option "Active connection establishment" is activated for both end points, or, if it is not
activated for either, the connection cannot be established.
M O
Two-way Connection
o RU
u t inh
A fully specified connection is always a two-way connection. Both communication stations know
their remote partner and the connection is parameterized on both sides. For this reason, the
Co
option "One-way" cannot be activated for a fully specified connection.
a
P ereir
e g o
Dy

Special Connection Properties:
One-way
14.7.5. SpecialConnection
Connection Properties: One-way Connection
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
One-way Connection
In TIA Portal, an unspecified connection is always provided with the option "One-way". This is the
case since it is not known whether a connection configuration is being made in the
communication partner, has been made or is even necessary. In the case of a PUT/GET S7
communication, no two-way connection is required. A one-way connection is sufficient.
However, this fact does not suggest that it is not possible to configure a two-way connection with
an unspecified connection. It is possible, with a fully specified connection as well as with an
unspecified connection, to configure a two-way connection for, for example, a BSEND/BRCV S7
communication. With an unspecified connection, only the control possibilities in TIA Portal are not
available. Here, you have to take greater care and it is easier to make errors in the connection
configuration and parameterization.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Address
14.7.6. Details
Address ofofthe
Details theDifferent Connections
Different Connections
S7 Connection
M O
R U
o
ISOonTCP ou tinh
ra C
e i
o Per
eg
Dy
TCP / UDP

Address Details of the Different Connections
Depending on the communication service which is linked to the connection, the address details of
a connection to be parameterized differ. The following address details are available for a
connection configuration:
• Transport Service Access Point (TSAP) for S7 connections
• Transport Service Access Point (TSAP) for ISO-on-TCP connections
• Transport Service Access Point (TSAP) for ISO connections
• Port & IP for UDP connections
• Port & IP for TCP connections M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

TSAP
14.7.6.1. for
TSAP forS7 Connections
S7 Connections (only(only S7-1500/S7-1200)
S7-1500/S7-1200)
O
Application Controlled
M
R U Communication
o
outinh
ra C
e i
o Per
eg
Dy Transport Service Access
Point

Transport Service Access Point (TSAP) for S7 Connections
Basically, a TSAP is the end-to-end connection for a communication between the Transport Layer
and the Session Layer.
For a SIMATIC controller, this is used to establish a connection. The TSAP ensures that the
connection-specific resources of a module are permanently assigned to this connection. The
assignment naturally assumes that the connection resource can be addressed. The TSAP is the
address of the resource, so to speak.
There are, however, restrictions and rules with regards to the usability of connection resources.
Not every connection resource can be used for every connection type, for example.
TSAP for S7-1500/S7-1200

M O
U
Rthe help of the SIMATIC-ACC
For an S7-1500 or an S7-1200, the TSAP is generated with
(SIMATIC Application Controlled Communication). ho
o u tin
SIMATIC-ACC
r a C
i
The SIMATIC-ACC is structured
P erasefollows:
ego
Rule: “SIMATIC-ACC”<nnn><mm>
y
nnn = local ID
mm = free value
D
In the example in the picture, the free value “01” was selected and the local ID “101”. As a result,
the SIMATIC-ACC has the following value:
SIMATIC-ACC10101

TSAP
14.7.6.2. for
TSAP forS7 Connections
S7 Connections (at 1least
(at least 1 Classic
Classic CPU) CPU)
M O
R U
o
ou tinh Specification of the
ra C Connection resource
e i
o Per
eg
Dy
TSAP for an S7 Connection with at least One Classic S7 Controller
The TSAP of an S7-300 or an S7-400 is generated according to different guidelines than those
for an S7-1500 or an S7-1200. If, for example, an S7-1500 is to communicate with an S7-300, the
S7-1500 uses, in this case, the same TSAP as the S7-300.
TSAP for S7-300/S7-400

The TSAP for an S7-300 or an S7-400 is generated according to the following rules:
Rule: <xx>.<yz>
xx = Number of the connection resource
MO
y = Rack number
z = Slot number
R U
o
In the example in the picture, the S7-300 is located in the
n h slot with the number “2” and in the rack
S7-300 has the following value: o u ti

with the number “0”. The selected connection resource is “10”. As a result, the TSAP for the
r a C
i
ere
10.02
P
y ego
D

TSAP
14.7.6.3. for
TSAP forUnspecified S7 Connections
Unspecified S7 Connections
Selectable, whether “new”

or “classic” version
M O
“new” TSAP RU
o
ou tinh
ra C
e i
o Per
eg
Dy
“classic” TSAP

TSAP for Unspecified S7 Connections
Since the connection partner is not known for unspecified S7 connections, the TSAP must be
selected by you. As a result, in this case, the option “SIMATIC-ACC” can also be selected and
deselected.
Note
It is also possible to connect two S7-1500s with one another and let them exchange data using
the “classic” TSAP. However, this option can only be used for an unspecified connection.
The type of communication, whether SIMATIC-ACC or “classic” TSAP must, however, be
identical on both end points for a two-way connection!
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

TSAP
14.7.6.4. for
TSAP forISO-on-TCP Connections
ISO-on-TCP Connections
TSAP from ASCII

designation
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
TSAP for ISO-on-TCP Connections
ISO-on-TCP connections have a TSAP length of 1 to 16 bytes. During input, the current length is
automatically displayed (visible display: 16 ASCII characters). Local and remote TSAPs can be
entered as a hexadecimal value or as an ASCII string. When input is in ASCII, the entered
characters are also displayed as hexadecimal. When the input is hexadecimal, printable
characters are presented as an ASCII value (visible are 8 hexadecimal characters). If non-
printable characters are entered, the ASCII display is greyed out (ASCII input is no longer
possible) and the non-printable characters are represented as dots.
For the configuration of the local and remote TSAPs, there is a default value "TCP-1" for the first
connection between the two partners (can be changed). For a new connection between the same
O
partners, the default value "TCP-2" is suggested. For a new connection to a new partner, TCP-1
M
is once again used.
o RU
u t inh
C o
a
P e reir
e g o
Dy

Port
14.7.6.5. forforUDP
Port andTCP
UDP and TCP Connections
Connections
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Port for UDP and TCP Connections
For a UDP connection and a TCP connection, the exchange does not occur via the connection
resource TSAP but via IP addresses and ports.
Just like when using the TSAP, you must obey certain rules and guidelines when using port
addresses. For example, for the assignment of port addresses it has to be checked whether they
are already used by other applications or if they are freely available. The following table should be
referenced with regards to the usage of ports for a UDP or TCP connection:
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Note
The term "Connection" is also used here for UDP because, for the configuration – as for example
also for TCP – the communication partners are assigned to one another and thus are logically
"connected". In actual fact, no explicit connection establishment between the communication
partners occurs for UDP.

14.8.Configured Connections
Configured Connections
Connection status
Controller (online)
Connection data is
configured
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Configured Connections
When a station is started, configured connections are automatically established or at least an
attempt is made. As a result, these types of connections permanently occupy (use) a connection
resource. There are two ways of creating a configured connection in the Network view in TIA
Portal. There is the "unspecified connection" and the "fully specified connection" for a configured
connection.
Online Status of the Connection

In the Network view in the "Connections" tab, not only are the connections configured, but it is
also possible to check whether the configured connections have been succesesfully established
M O
and connected. Furthermore, it is also possible to check here whether there are connections
which are only available Online and have not been configured.
o RU
u t inh
For this, you must ‘go online’ to the controller in the "Connections" tab. Then, status information
for all connections of this controller appear in the Diagnostics column for the configured
C o
connections in the project. The following statuses can be assumed by a connection:
a
: connection is established
P e reir
e g o
Dy
: connection is faulty.
: connection only exists online. Connection is established.

14.9.Programmed Connection
Connection data is
programmed
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Programmed Connections
Unlike a configured connection, a programmed connection does not continuously occupy a
communication resource and is not automatically established by the controller. For a programmed
connection, a connection is established via the user program and all data necessary for a
successful communication setup is found there.
This connection data is usually stored in a separate data block in the system blocks of the project.
The parameterization of the communication is then only made via the block or via the
parameterization wizard of the instruction, in this case. The block, itself, then gives you feedback
as to whether the connection to the partner station could be established successfully or whether
this was not possible.
M O
You can also check in the Network view in Online mode whether or not the programmed
connection could be established successfully.
o RU
u t inh
Co
a
P e reir
e g o
Dy

Communication
via Communication
14.10. Ethernet with regard to the OSIwith
via Ethernet Model
regard to the OSI Model
UDP TCP IoT S7 S7 ISO
S7 communication CPU
IoT: ISO-on-TCP
S7 communication CP
Open User Communication

(OUC)
S7 S7
Layer 7 Application Layer
M O
Layer 6 Presentation Layer
R U
o
Layer 5 Session Layer
u 1006
oRFC tinh
Layer 4 Transport Layer C
ra TCP ISO
Industrial
rei
UDP Ethernet
Layer 3 Network Layer

o Pe IP
g
e IEEE 802.2 Logical Link Control (LLC)
Layer 2 Data Link Layer Dy IEEE 802.1 Media Access Control (MAC)
Ethernet
Layer 1 Physical Layer IEEE 802.3 Ethernet

Communication via Ethernet with regard to the ISO/OSI Model
As already discussed in this course, the Industrial Ethernet includes all 7 layers of the ISO/OSI
reference model. In the picture, all 7 layers are presented and all related protocols and
communication types which are supported by the SIMATIC controllers, the communication
processors or the communication modules. Depending on the protocol and / or communication
type, a different layer is accessed. For that reason, depending on the application, different
conditions must also be taken into consideration and settings made. In the following chapters, we
will take a closer look at the S7 communication and the Open User Communication.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Communication
14.11. in the
Communication in TIA
TIAPortal
Portal
S7 communication
OUC
M O
R U
o
ou tinh
ra C MODBUS TCP
e i
o Per
eg
Dy
Communication via CPs
or CMs

Communication in TIA Portal
TIA Portal makes it possible for you to quickly and easily get an overview of all possible
communication methods in the currently configured controller. For this, a block only has to be
created or opened, and, the "Communication" area in the Instructions has to be expanded.
You then have a quick overview of all instructions which are possible with this controller. Further
information on the individual instructions can then be quickly and easily found in the Online Help
of TIA Portal. More in-depth information, application examples and FAQs, on the other hand, can
be found in the Service & Support pages of the Online Support on the Internet.
Note
M O
o RU
Some instructions may not be compatible with the internal PROFINET/IE interface of the
controller and, for that reason, require a separate communications processor (CP) or a separate
communications module (CM).
u t inh
Co
a
P e reir
e g o
Dy

Graphic
14.12. Creation
Graphic of a of
Creation Connection
a Connection
Select the connection
M O
Connect using
U
Drag & Drop
R
o
ou tinh
ra C
e i
o Per
eg
Dy Compatible stations are
highlighted

Graphic Creation of a Connection
Probably the simplest and most intuitive way of creating a connection in TIA Portal is the graphic
creation of a connection.
In the broadest sense, this method matches the networking of individual PROFINET/IE
components. The only difference here is that not all components in the network can be connected
to one another!
First of all, you have to switch from "Network" to "Connections" in the ‘Network view’ in TIA Portal.
Then you have to select the desired connection method. All devices which now could be
connected via this connection are given a pale-blue background by TIA Portal. The familiar drag
& drop method is used to connect two of these devices. The PROFINET interface of the start
O
station is simply dragged onto the PROFINET interface of the destination station using drag &
M
RU
drop. TIA Portal then creates a fully specified configured connection between these two devices.
o
Note
u t inh
C o
If an unspecified configured connection is to be created, the PROFINET/IE interface must simply
a
P e reir
be dragged onto itself using drag & drop. TIA Portal then creates an unspecified connection for
this station with this station as the start point.
e g o
Dy

Textual
14.13. Creation
Textual of a of
Creation Connection
a Connection
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Textual Creation of a Connection
If you do not wish to create a connection graphically but rather create it textually, this can also be
done in TIA PORTAL. For this you right-click on the desired Start Station in the ‘Network view’
and then select the "Add new connection" item.
In the pop-up window which now opens, you can either create a fully specified connection to all
possible devices within the project or you can create an unspecified connection to a device
outside of the project.
Note
Just like the graphic creation, the textual creation of a connection always also generates a
M O
configured connection between two stations. If this is not desired, the connection must be
generated via the user program!
o RU
u t inh
Co
a
P e reir
e g o
Dy

Task
14.14. Description:
Task Connections
Description: Connections
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task Description
You are to generate a copy of your original project by saving it under a different name. For this,
select the ending “xxx_connection”. Then, you are to copy the S7-1510SP in it so that you can
create both fully specified connections as well as unspecified connections.
In this new project, you are now to try to create a few unspecified and a few fully specified
connections. Then you are to become familiar with the different properties of the various
connection types so that you can successfully master the tasks in the following chapters.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Contents 15
15. S7 Communication ............................................................................................... 15-2
15.1. S7 Communication .............................................................................................................. 15-3
M O
15.2. U
S7 Communication Possibilities .......................................................................................... 15-4
R
o
tinh
15.3. User Data Size of the S7 Communication Possibilities ...................................................... 15-5
15.4. ou
Read GET Data from a Remote CPU ................................................................................. 15-6
C
15.5.
e
Write PUT Data to a Remote CPU
r ira...................................................................................... 15-7
15.6.
o PeGET / PUT ................................................................................ 15-8
Access Protection against
g & PUT Communication .................................................................. 15-9
yeGET
15.7.
15.7.1.
D
Task Description:
Exercise 1: S7 Communication on the S7-1510SP .......................................................... 15-10
15.7.2. Exercise 2: S7 Communication on the S7-1513 ............................................................... 15-11
15.7.3. Exercise 3: PUT Communication in the S7-1510SP......................................................... 15-12
15.7.4. Exercise 4: GET Communication in the S7-1513 ............................................................. 15-13
15.7.5. BSEND – Send Data in Segments.................................................................................... 15-14
15.7.6. BRCV – Receive Data in Segments ................................................................................. 15-15
15.7.7. USEND – Send Data Uncoordinated ................................................................................ 15-16
15.7.8. URCV – Receive Data Uncoordinated .............................................................................. 15-17
15.7.9. Task Description: BSEND & BRCV Communication ........................................................ 15-18
15.7.9.1. Exercise 5: Setting Up Two-way S7 Communication ....................................................... 15-19
15.7.9.2. Exercise 6: BSEND Communication on the S7-1510SP .................................................. 15-20
15.7.9.3. Exercise 7: BRCV Communication on the S7-1513 ......................................................... 15-21
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – S7 Communication
15. S7 Communication
Objectives
... understand how the S7 communication relates to the ISO/OSI

model
... be familiar with the various instructions which can be used for an
S7 communication
M O
R U
... o
be able to configure a GET/PUT data exchange
... ou tinh
be able to program a BSEND/BRCV data exchange
ra C
e i
Per
... know how to protect the controller against a GET/PUT access
eg o
Dy
SITRAIN
IK-TIAPN / S7 Communication Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
15.1.S7 S7
Communication only Script
Communication
S7 S7
S7 Communication CPU
S7 Communication CP
S7 S7
M O
R U
o
u 1006
oRFC tinh
ra TCP ISO
i
ere
UDP
o P IP
Layer 2 Data Link Layer Dyeg IEEE 802.2 Logical Link Control (LLC)
IEEE 802.1 Media Access Control (MAC)

Page 4 S7 Communication
S7 Communication
For S7 controllers, the S7 communication provides functions for communication between two
controllers. The S7 communication has the great advantage that it is already integrated in every
SIMATIC S7 controller. Incidentally, this also applies for every SIMATIC M7 as well as C7 device!
With regard to the ISO/OSI reference model, the S7 communication is in Layer 7, the Application
Layer. It is independent of the subnet and can be used in all transmission media (MPI,
PROFIBUS, Industrial Ethernet,…).
Advantages of S7 Communication
• Network-independent user interface. Identical handling for PN/IE, PB and MPI
M O
RU
• Communication via integrated interface of CPU or via external interface such as CP or CM
t i n ho
• Communication via configured connections (S7 connection)
• Amount of data per communication task: o <=u64 KBytes
C
• r
The user program in the Sender e ira information when the data arrives in the user data
receives
o Pe
area of the Recipient (acknowledgement from the remote application).
e g
Dy
15.2.S7 S7
Communication Possibilities
One-way Possibilities for an

communication S7-1200
Two-way
communication
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
S7 Communication Possibilities
The S7 communication offers both one-way connections and two-way connections. However, it
must be noted that the selection of the communication possibilities may differ depending on the
controller. The S7 communication can be divided into three different types of communication:
• GET / PUT (one-way connection)
• USEND / URCV (two-way connection)
• BSEND / BRCV (two-way connection)
Note
M O
RU
All three communication possibilities can only be realized as a configured connection. However
o
inh
here it is irrelevant whether this is an unspecified or a fully specified connection.
o u t
a C
P e reir
e g o
Dy
User Data Size of the

15.3.S7 User
Communication
Data Size ofPossibilities
the S7 Communication Possibilities
Communication of an S7-
1500 with:
Instruction: Partner: S7-300 Partner: S7-400 Partner: S7-1200 Partner: S7-1500

GET / PUT ▪160 Bytes ▪400 Bytes ▪160 Bytes ▪880 Bytes
M O
USEND / URCV ▪160 Bytes ▪440 Bytes -
U ▪920 Bytes
hoR
BSEND / BRCV ▪32768/65534
o u tin
▪65534 Bytes - ▪65534 bytes for
Bytes
a C standard access
e r eir ▪65535 bytes for
o P optimized access
eg
Dy
Guaranteed transferable
user data size

User Data Size of the S7 Communication Possibilities
The amount of data which can be transmitted via an S7 communication differs depending on the
selected communication possibility and the communication partner. The table above gives you an
overview of the user data size which is guaranteed to be transmitted depending on the selected
communication type and communication partner.
The table always describes the second communication partner. In this case, the first
communication partner is always an S7-1500.
Note
O
If this guaranteed user data size above is not sufficient, you can find an exact user data size in
M
RU
the Online Help of the TIA Portal or the Programming and Operating Manual for STEP7.
o
u t inh
C o
a
P e reir
e g o
Dy
15.4.Read GETGET
Read DataData
fromfrom
a Remote CPU CPU
a Remote
Requires an Parameterization and

instance data block Diagnostics
Executing the reading
M O ID of connection to the
Pointer to the area to be
R U remote CPU
o
tinh
read
C ou
Pointer to the area in
e i ra
Per
which the data is to be
stored
eg o Feedbacks of the block
Show the Areas 2-4 Dy

GET
The instruction ‘GET’ permits you to read data from another controller. So that the instruction can
access the data of the other controller, there must be an S7 connection between the two stations.
These two stations are also called Client and Server. In this case, the Client is the controller that
would like to read the data from the other controller, the Server.
The connection between the two controllers doesn’t have to be a two-way connection. It can also
be a one-way connection. In the other CPU, the Server, there therefore doesn’t have to be a
communication block in the user program. The communication block ‘GET’ can operate on its
own.
The communication block ‘GET‘ reads the area, which is parameterized at the parameters
M O
“ADDR_1” to “ADDR_4”, from the remote CPU and writes this in the area “RD_1” to “RD_4” in the
executing controller, the Client controller. The parameters “ADDR_2” to “ADDR_4” as well as
RU
“RD_2” to “RD_4” can be optionally assigned. If, however, “ADDR_2” is assigned, then “RD_2”
o
must also be assigned and vice-versa.
u t inh
C o
Requirements
i r a
e can be successfully used, some requirements must be
P er‘GET’
So that the communication block
fulfilled:
y e go
D of the Partner CPU, the function "Permit access with PUT/GET
• In the Properties
communication from remote partner" was activated under "Protection & Security".
• If the instruction GET is to access data blocks or instance data blocks, they must be created
without the attribute “Optimized block access”.

• You must make sure that the areas defined via the parameters “ADDR_i” and “RD_i” match in
number, length and data type.
• The area (“ADDR_i”) to be read from the remote CPU must not be larger than the area for
storing data in the Client controller (“RD_i”).
15.5.Write PUTPUT
Write DataData
to a to
Remote CPU CPU
a Remote

Executing the writing
M O ID of connection to the
Pointer to the area to be
R U remote CPU
o
tinh
written
C ou
Pointer to the area from
ei ra
which the data is read
o Per
eg Feedbacks of the block
Show the Areas 2-4 Dy

PUT
The instruction ‘PUT’ is the counterpart to the communication block GET.
The communication block ‘GET’ permits you to read data from a remote CPU and the
communication block ‘PUT’ to write data. Here as well, a connection between the Server and the
Client must be configured first. A programmed connection is not possible for both instructions.
Both communication blocks also require an instance data block for their functionality. This can be
configured as either a single or a multiple instance.
Just as for the instruction GET, a one-way connection is sufficient for the instruction PUT. No
programming has to be done in the user program of the remote controller - the Server - so that
the instruction PUT is operational.
M O
The communication block PUT takes the area “SD_1” to “SD_4” from the executing controller, the
RU
Client controller, and writes this in the area in the remote CPU which was defined at the
o
inh
parameters “ADDR_1” to “ADDR_4”. The parameters “ADDR_2” to “ADDR_4” as well as “SD_2”
o u t
to “SD_4” can be optionally assigned. If, however, “ADDR_2” is assigned, then “SD_2” must also
be assigned and vice-versa.
a C
Requirements
Pe reir
o
eg block PUT can be successfully used, some requirements must be
So that the communication
fulfilled: D y
• In the Properties of the Partner CPU, the function "Permit access with PUT/GET
communication from remote partner" was activated under "Protection & Security".
• If the instruction PUT is to access data blocks or instance data blocks, they must be created
without the attribute “Optimized block access”.

• You must make sure that the areas defined via the parameters “ADDR_i” and “SD_i” match in
number, length and data type.
• The area (“ADDR_i”) to be written in the remote CPU must always be as large as the send
area from the Client controller (“SD_i”).
15.6.Access Protection
Access against
Protection GET/PUT
against GET / PUT
M O
R U
o
ou tinh
ra C
e i
o Per Must be activated
eg
Dy

Access Protection on the Controller against GET & PUT Accesses
So that the controller is protected against unauthorized and undesirable accesses with a
GET/PUT communication, an S7-1200 and an S7-1500 offers an access protection against these
connection mechanisms. This can be found in the Device view in the Properties of the controller
under the "Protection & Security" tab. There, you will find the submenu item "Connection
mechanisms". Here, the option "Permit access with GET/PUT communication from the remote
partner" can be activated or deactivated. If an access to the CPU data by remote stations is
wished, this protection must be explicitly deactivated!
Note
M O
This access protection is activated by default. That is, the access to an S7-1200 or an S7-1500
RU
with GET / PUT is not possible. If an access with the instructions GET or PUT is wished, this
option must be manually activated!
t i n ho
beudeactivated on the passive side if an access with
The access protection must logically always o
C
r e ira
GET & PUT is wished on this controller.
o Pe
y eg
D
Task GETGET
Description: & PUT Communication
& PUT Communication
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Task Description
The scaled analog value of the potentiometer which was transmitted onto the S7-1510SP via the
PN/PN Coupler is to be displayed on Display1 and Display2 using an S7 communication with the
help of the communication blocks GET & PUT. Display1 is written from the S7-1510SP with the
help of the instruction PUT and Display2 from the S7-1513 with the instruction GET. That is, the
communication block PUT writes the scaled analog value from the S7-1510SP into the S7-1513
and thus in Display1 while the block GET fetches the scaled analog value from the S7-1510SP
into the S7-1513 and so fills Display2. The instruction PUT is started on the S7-1510SP via the
input “PUT_Com” (%I 0.7) and the instruction GET is started on the S7-1513 with the help of the
input “GET_Com” (%I 0.6).
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Exercise
15.7.1. 1: 1:
Exercise S7S7
Communication
Communication on theS7-1510SP
on the S7-1510SP
Creation of a new S7 Assignment of an ID for

connection the connection
M O
RU
o
On the S7-1510SP
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to create an S7 Communication on the S7-1510SP. This S7 communication is to make a
data transmission between the S7-1510SP and the S7-1513 possible. You are to select the
correct connection properties for this.
What to Do
1. Switch into the project “IK-TIAPN_en_Shared_Device”.
2. Open the Network view in the TIA Portal.
3. Create an S7 connection between the S7-1510SP and the S7-1513.
MO
RU
4. Save your project and download the changes.
o
Note
u t inh
Co
By going Online in the Network view, you can check whether the connection between the stations
a
Pe
parameters of the connection. reir
was successfully established. If this is not the case, then changes still have to be made to the
o
eg a two-way connection. A one-way connection is sufficient!
You do not have to create
D y
Exercise
15.7.2. 2: 2:
Exercise S7S7
Communication
Communication on theS7-1513
on the S7-1513
Creation of a new S7 Assignment of an ID for

connection the connection
M O
RU
o
ou tinh
On the S7-1513
ra C
e i
o Per
eg
Dy
Task
You are to create an S7 Communication on the S7-1513. This S7 communication is to make a
data transmission between the S7-1513 and the S7-1510SP possible. You are to select the
correct connection properties for this.
What to Do
1. Switch into your initial project.
2. Open the Network view in the TIA Portal.
3. Create an S7 connection between the S7-1513 and the S7-1510SP.
MO
RU
o
Note
u t inh
C o
a
Pe
parameters of the connection. reir
o
eg a two-way connection. A one-way connection is sufficient!
You do not have to create
D y
Exercise
15.7.3. 3: 3:
Exercise PUT Communication
PUT in the
Communication in theS7-1510SP
S7-1510SP
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Newly generated block for
Dy Send Poti1 value to
S7 communication Display1

Task
After you have established the one communication between the two controllers, you are now to
program the writing of Display1 with the help of the communication block PUT. The instruction
reads the scaled analog value of Potentiometer1 transmitted into the S7-1510SP via the PN/PN
Coupler and writes this into the S7-1513 in the output byte %QB8 which controls Display1. The
PUT communication is started via the input “PUT_Com” (%I 0.7) and occurs in the “S7-Com”
function block which is now to be created by you. This FB is called in OB1 “Main”. The
communication block PUT is to be called with the help of a multiple instance.
What to Do
1. Switch into the project “IK-TIAPN_en_Shared_Device”.
M O
2. Create a new function block “S7-Com”.
o RU
u t inh
3. In this, with the help of the PUT instruction, program the required functionality according to the
task. C o
a
P e reir
4. Save your project and download the changes into the controller.
g o
5. Test whether your programming fulfills the task. If necessary, make corrections.
e
Note Dy
Independently, create all necessary temporary as well as static variables within the function
block.
If necessary, add the evaluation of the output parameters “DONE”, “ERROR” and “STATUS” of
the instruction PUT. Get the functionality of these parameters from the Online Help of TIA Portal.
Don’t forget to make the necessary change to the Hardware configuration of the controller!
Exercise
15.7.4. 4: 4:
Exercise GET Communication
GET in the
Communication in theS7-1513
S7-1513
M O
R U
o
Newly generated block for
ou tinh
S7 communication
ra C
e i
o Per
eg
Dy Read Poti1 value on
Display2

Task
Now that Display1 can be written via the S7-1510SP, Display2 is also to display the scaled
analog value. However, the analog value is now not to be written from the S7-1510SP but
fetched. That means that you are to program a GET communication in the S7-1513 which reads
the scaled analog value from the S7-1510SP and stores it in the output byte %QB10 for Display2.
The reading of the analog value is started via the input “GET_Com” (%I 0.6). The programming of
the instruction is done in the new function block “S7-Com” which you are to create and which is to
be called in OB1 “Main”. The call of the GET instruction occurs as a multiple instance.
What to Do
1. Switch into your initial project.
M O
2. Create a new function block “S7-Com”.
o RU
u t inh
3. In this, with the help of the GET instruction, program the required functionality according to the
task. Co
a
Pe reir
g o
5. Test whether your programming fulfills the task. If necessary, make corrections.
e
Note Dy
block.
If necessary, add the evaluation of the output parameter “DONE”, “ERROR” and “STATUS” of the
instruction GET. Get the functionality of these parameters from the Online Help of TIA Portal.
Don’t forget to make the necessary change to the Hardware configuration of the controller!
BSEND
15.7.5. – Send
BSEND Data
– Send DataininSegments
Segments
Requires an
instance data block
Activate the sending
operation
Abort the sending process
ID of connection
CPU → remote CPU
M O
RU Common ID of connection
n h o pairs
u ti
C o
eira
Pointer to the Send area
P e r
eg o
Length of the data block to
be sent
Dy Feedbacks of the block

BSEND
The instruction “BSEND” sends data to a remote partner instruction of the type “BRCV”. This
means, unlike a PUT or GET instruction, the communication block “BSEND” is not self-sufficient,
that is, is not operational without the partner instruction “BRCV”. So that the Send job can be
received by the remote CPU, the instruction “BRCV” must be ready to receive in this station. The
instructions BSEND and BRCV require a two-way S7 connection and not a one-way connection.
The amount of user data which can be transmitted with a BSEND/BRCV connection is far larger
than with all other S7 connections. In each case, the maximum amount of data is 65534 bytes for
a non-optimized access and 65535 bytes for an optimized access.
M O
The block “BSEND” furthermore offers a receipt acknowledgement with the output “DONE”. If this
output has the value “1”, the data was safely received by the partner and accepted in the user
program.
o RU
u t inh
For all other Send blocks, the parameter “DONE” only has the function of a Send
o
acknowledgement, not however, a receipt acknowledgement!
C
a
Note
P ereir
e g o
For an unspecified connection, the “One-way” option of an S7 connection is always greyed out
and activated:
Dy
However, it is still possible with the appropriate configuration to operate a BSEND-/BRCV

communication via two unspecified S7 connections.
BRCV
15.7.6. – Receive
BRCV – ReceiveData
DataininSegments
Segments
Requires an
instance data block
Switch on
Ready to receive
ID of connection
CPU → remote CPU
M O Common ID of connection
pairs
R U
o
ou tinh
Pointer to the
ra C
e i
Per
Receive area
ego
Length of the received data

BRCV
The instruction “BRCV” receives data from a remote partner instruction of the type “BSEND”. As
soon as there is a ‘1’ at parameter “EN_R”, it is ready to receive. In order to communicate, the
“BRCV” communication block always requires its counterpart “BSEND”. It cannot operate on its
own.
The amount of user data which can be received by the BRCV instruction depends on the BSEND
block. If it is not possible to receive all user data synchronously, this is signaled by the instruction
BRCV via the STATUS parameter.
After each received data segment, the BRCV communication block sends an acknowledgement
repeatedly until all segments are received. M O

to the partner instruction BSEND. For an asynchronous receipt, the BRCV block must be called
RU
ID
t i n ho
The parameter “ID” is assigned the identifier
C u the S7 connection to the remote CPU has.
owhich
r e iraproperties. This parameter can be different for both
This can be taken from the connection
communication pairs!
o Pe
R_ID y eg
D
The parameter “R_ID” is assigned the same identifier on the receive side as on the send side.
This identifier makes it possible to assign the two block pairs to the S7 connection. This
parameter must be exactly identical for both the BSEND and BRCV communication block! If this
is not the case, no communication is possible!
USEND
15.7.7. – Send
USEND Data
– Send DataUncoordinated
Uncoordinated
Requires an
instance data block
Activate the sending
operation
ID of connection
CPU → remote CPU
Common ID of connection
U MO pairs
o R
ti n h
C o u
Pointer to the Send area
eira
P e r
eg o

USEND
The instruction “USEND” requires the partner instruction “URCV” in a remote CPU. Unlike the
partner instructions BSEND/BRCV, a communication with USEND/URCV occurs without
coordination between the two partner instructions. This means that the data transmission occurs
without an acknowledgement by the partner instruction. The USEND block initiates its sending
operation and also confirms a successful completion of the sending operation. The USEND
instruction, however, does not delivery a confirmation to the user as to whether the sent user data
was also successfully received.
Note
M O
Just like a BSEND process, the data of a USEND sending operation is only received by the
RU
partner controller if the “URCV” communication block is ready to receive.
o
u t inh
C o
a
P ereir
e g o
Dy
URCV
15.7.8. – Receive
URCV – ReceiveData
DataUncoordinated
Uncoordinated
Requires an
instance data block
Switch on
Ready to receive
ID of connection
CPU → remote CPU
M O Common ID of connection
R U pairs
o
ou tinh
ra C
Pointer to the
ei
Receive area
o Per
eg

URCV
The instruction “URCV” forms the counterpart to the communication instruction “USEND” and
receives data from a remote controller in an asynchronous and uncoordinated manner.
The block is ready to receive as soon as there is a ‘1’ at parameter “EN_R”. This means that from
that moment on, data from a Send job of the “USEND” instruction can be received. The “URCV”
instruction delivers a confirmation of a successful receipt of user data but it doesn’t send an
acknowledgement to the partner instruction “USEND”.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
Task
15.7.9. Description:
Task Description:BSEND
BSEND&
& BRCV Communication
BRCV Communication
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Task Description
Now that you have successfully implemented an S7 communication with PUT/GET in the
previous exercise, a new S7 communication/S7 connection is to be configured and
parameterized. The data exchange via this S7 connection will then be done with the block pairs
BSEND and BRCV. You are to create a new data block called “PingPong” both on the S7-
1510SP and on the S7-1513. The S7-1510SP will send the data from its DB “DB_PingPong” to
the S7-1513, which stores the received user data in its data block “DB_PingPong”. On the S7-
1510SP, the sending of data is triggered via the input “BSEND_Com” (%I 0.6) and the data is
received on the S7-1513 via the input “BRCV_Com” (%I 0.5).
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
Exercise
15.7.9.1. Exercise5:
5: Setting
Setting UpUp Two-way
Two-way S7 Communication
S7 Communication
M O
R U
o
ou tinh
ra C
Settings must be
ei
synchronized!
o Per
eg
Dy
Task
You are to create a two-way S7 communication between the S7-1513 and the S7-1510SP.
Through this S7 connection, a communication between the block pairs BSEND and BRCV should
then be possible.
The S7 connection on the S7-1510SP is assigned the ID 110; on the S7-1513 side it is assigned
the ID 113. Name the S7 connection from the S7-1513 to the S7-1510SP
“S7_Connection_BRCV-BSEND” and from the S7-1510SP to the S7-1513
“S7_Connection_BSEND-BRCV”.
What to Do
1. Open the project “IK-TIAPN_en_Shared_Device”. M O
RU
2. Switch into the Network view in TIA Portal.
t i n ho
ou and the S7-1513.
3. Create an S7 connection between the S7-1510SP
C
r e ira to the task.
4. Parameterize the connection according
Pehere as well, open the Network view.

5. Open your initial project and,
o
eg between the S7-1513 and the S7-1510SP so that a two-way S7
6. Create a new S7yconnection
D these devices is the result.
connection between
7. Now parameterize the connection as required in the task.
8. Check the “Special connection properties” as well as the “Address details” for both S7
connections.
9. Save your projects and download the changes.
10. In both projects, switch to the Online view and check whether the connection between the two
stations can be successfully established.
Note
Make sure that the “Special connection properties” and the “Address details” are correctly
parameterized on both S7 connections! If this is not the case, a connection between the block
pairs BSEND and BRCV cannot be achieved later on.
Exercise 6:
BSEND
15.7.9.2. Communication
Exercise on theonS7-1510SP
6: BSEND Communication the S7-1510SP
M O
R U
o
ou tinh
ra C
e i
o Per
yeg
The count is to be increased
with every send operation
D (+1)

Task
Now that the two-way S7 communication between the two stations exists, a data exchange is to
be carried out with the help of the instruction pairs BSEND and BRCV. First, you are to program
the sending of the data. You are to create the “BSEND” block in the already existing function
block “S7-Com” in the S7-1510SP. The instance DB is also to be implemented here as a multiple
instance. The Send job is commissioned via the input “BSEND_Com” (%I 0.6).
The user data which is to be sent is created in a new data block called “DB_PingPong” which you
are to generate. This user data is a LINT variable with the symbolic name “Value_BSEND-
BRCV”. The data block is to be an optimized data block.
Before every Send job by the “BSEND” communication block, the variable “Value_BSEND-
BRCV” is to be increased by ‘1’. This is triggered by an edge of the input “BSEND_Com”.
M O
What to Do
o RU
1. Open the project “IK-TIAPN_en_Shared_Device”.
u t inh
Co
2. Create a new data block “DB_PingPong” and in it the variable “Value_BSEND-BRCV” of the
a
required data type from the task.
Pe reir
3. Switch to the “S7-Com” block and program the counting of the variable “Value_BSEND-BRCV”
e g o
Dy
according to the task.
4. Now program the “BSEND” block in the FB “S7-Com” according to the task.
Note
block.
instruction BSEND. Get the functionality of these parameters from the Online Help of TIA Portal.
Exercise
15.7.9.3. Exercise7:
7: BRCV Communication
BRCV Communication on the
on the S7-1513 S7-1513
M O
R U
o
ou tinh
ra C
ei
o Per Storage of the received count
yeg
(value)
D
Task
Now, you are to program the counterpart of the BSEND instruction – the BRCV instruction on the
S7-1513. You are also to program this in the already existing function block “S7-Com” and
implement it using a multiple instance. The ‘ready to receive’ of the BRCV communication block is
activated via the input “BRCV_Com” (%I 0.5).
The received user data is to be stored in the variable “Value_ BRCV-BSEND” of the data type
“LINT”. This is generated in a new data block called “DB_PingPong” which you are to create. The
data block is of the type “Global-DB” and has an optimized data structure.
What to Do
1. Open your initial project.
M O
2. Create a new data block “DB_PingPong” and in it the variable U
R “Value_ BRCV-BSEND” of the
h o
tin
required data type from the task.
3. Switch to the “S7-Com” block and program o uthe receipt of the user data of the S7-1510SP with
Cto the task.
r
the help of the “BRCV” block according
i a
P ere the changes.
4. Save your project and download
5. Test whether your e
y go
programming fulfills the task. If necessary, make corrections.
D
Note
block.
instruction BRCV. Get the functionality of these parameters from the Online Help of TIA Portal.
Don’t forget that a successful Send operation always requires the ‘ready to receive’ of the “BRCV”
block. If everything works, you will see the count increase by ‘1’ in the variable
“Value_ BRCV-BSEND” after every Send operation when you monitor the DB “DB_PingPong”.
Contents 16
16. Open User Communication ................................................................................. 16-2
16.1. Open User Communication ................................................................................................. 16-3
M O
16.2. U
OUC Communication Possibilities ...................................................................................... 16-4
R
o
tinh
16.3. User Data Size of the OUC Communication Possibilities ................................................... 16-5
16.4. ou
TCP/IP (Transmission Control Protocol / IP) ...................................................................... 16-6
C
16.5.
e ira
ISO on TCP .........................................................................................................................
r 16-7
UDP – User Datagram Protocol
e
P .......................................................................................... 16-8
16.6.
e g o
16.7.
Dy .............................................................................................................. 16-9
OUC with T-Blocks
16.8. TSEND_C – Send Data via Ethernet (TCP) ..................................................................... 16-10
16.9. TRCV_C – Receive Data via Ethernet (TCP) ................................................................... 16-11
16.10. Programmed Connections with OUC ................................................................................ 16-12
16.11. Task Description: ISO-on-TCP Communication with TSEND_C/TRCV_C ..................... 16-13
16.11.1. Exercise 1: Configured ISO-on-TCP Communication on the S7-1510SP ........................ 16-14
16.11.2. Exercise 2: Configured ISO-on-TCP Communication on the S7-1513 ............................. 16-15
16.11.3. Exercise 3: TSEND_C – Configured Connection Sending Data from the S7-1510SP ..... 16-16
16.11.4. Exercise 4: TRCV_C – Configured Connection Receiving Data in the S7-1513 .............. 16-18
16.11.5. Exercise 5: TSEND_C – Programmed Connection Sending Data from the S7-1513 ...... 16-20
16.11.6. Exercise 6: TRCV_C – Programmed Connection Receiving Data in the S7-1510SP ..... 16-22
16.13. TUSEND – Send Data via Ethernet (UDP) ....................................................................... 16-24
M O
TURCV – Receive Data via Ethernet (UDP) ..................................................................... 16-25
RU
16.14.
o
inh
16.15. Task Description: UDP Communication with TUSEND/TURCV ...................................... 16-26
16.15.1.
u t
Exercise 1: Setting Up a UDP Connection ....................................................................... 16-27
o
16.15.2.
a C
Exercise 2: TUSEND Instruction – S7-1513 ..................................................................... 16-28
reir
16.15.3. Exercise 3: TURCV Instruction – S7-1510SP ................................................................... 16-29
P e
e g o
Dy
IK-TIAPN – Open User Communication

16. Open User Communication

Objectives
... understand how the Open User Communication relates to the

ISO/OSI model
... know the difference between a configured connection and a

programmed connection
M O
RU
... o
be able to create a programmed connection
... ou tinh
be able to handle the T-communication blocks
ra C
e i
Per
... be able to create OUC connections
eg o
Dy
SITRAIN
IK-TIAPN / Open User Communication Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

16.1.Open User
Open Communication
User only Script
Communication
UDP TCP IoT ISO
IoT: ISO-on-TCP
Open User Communication

(OUC)

M O
RU
o
u 1006
oRFC tinh
ra TCP ISO
i
ere
UDP
o P IP
Layer 2 Data Link Layer Dyeg IEEE 802.2 Logical Link Control (LLC)
IEEE 802.1 Media Access Control (MAC)

Page 4 Open User Communication
Open User Communication (OUC)
Open User Communication (OUC) is a name for a program-controlled communication procedure
for communication via the integrated PN/IE interface of the SIMATIC controllers. Different
connection types are available (see picture) for this communication procedure.
The Open User Communication is characterized by a high flexibility with regards to the data
structures to be transmitted and thus makes the open exchange of data with any communication
devices possible, insofar as they support the connection types made available here. Since the
communication is exclusively controlled via instructions in the user program, an event-driven
establishment and disconnection of connections is possible. Furthermore, connections can be
modified by the user program at runtime.
O
For CPUs with an integrated PN/IE interface, the connection types TCP, UDP and ISO-on-TCP
M
RU
are available for the Open User Communication. The communication partners can be two
o
SIMATIC PLCs or also a SIMATIC PLC and a suitable third-party device. Via CPs or CMs, the
u t inh
communication via the ISO connection type is also possible.
C o
Advantages of the Open User Communication
i r a
•
P erewith third-party controllers is possible)
Open standard (communication
•
o
Communication viaeagconfigured or programmed connection is possible (TCP, IoT, UDP). ISO
only permits aD
y
configured connection
• Amount of data per communication task: <= 64 KBytes
• Acknowledgement from remote transport system (not for the protocol UDP)
• No acknowledgement from the remote application

16.2.OUC Communication
OUC Possibilities
Possibilities for an
S7-1200
Combined blocks
Single blocks M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
OUC Communication Possibilities
The number of communication possibilities provided by the Open User Communication is the
same for S7-1500 and S7-1200. Differentiation is made here between two types of instructions:
• Combined blocks (instructions)
• Single blocks (instructions)
Combined Blocks (Instructions)

The combined blocks (instructions) get their name from the fact that they contain several single
M O
instructions. The instruction "TSEND_C", for example, internally uses the single communication
instructions "TCON", "TSEND", "T_DIAG", "T_RESET" and "T_DISCON". The "TSEND_C" block
RU
sets up a communication connection and establishes it. After this connection is setup and
o
established, it is automatically maintained by the CPU.
u t inh
C o
Single Blocks (Instructions)
i r a
Single blocks (instructions) are e
P re
designated as such since they fulfill a function. The instruction
"TSEND" sends, for example,
e g o the instruction "TCON",
only data via one connection. This connection must first, however,
Dy
have been established with otherwise no data can be s.

16.3.User Data
User SizeSize
Data of the
of Open UserCommunication
the OUC CommunicationPossibilities
Communication of an S7-
1500 with:
Connection Partner: S7-300 Partner: S7-400 Partner: S7-1200 Partner: S7-1500

type:
TCP ▪1460 Bytes / 32 KByte ▪32 KBytes ▪8 KBytes ▪64 KBytes
U MO
▪32 KBytes ▪32 KBytes o RKBytes
▪8 ▪64 KBytes
nh
ISO on TCP
o u ti
UDP ▪1472 Bytes
r C Bytes
a▪1472 - ▪1472 Bytes
r e i
P e
e g o
Guaranteed transferable
Dy
user data size

User Data Size of the OUC Communication Possibilities
The amount of data which can be transmitted via an OUC communication differs depending on
the selected connection type and the communication partner. The table above gives you an
overview of the user data size which is guaranteed to be transmitted depending on the
connection type and communication partner.
The table always describes the second communication partner. In this case, the first
communication partner is always an S7-1500.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy

16.4.TCP/IP (Transmission
TCP/IP Control
(Transmission Protocol
Control / IP) / IP)
Protocol
100 Bytes
200 Bytes 220 Bytes
50 Bytes 130 Bytes
U MO
o R
ti n h
C o u TCP/IP TCP/IP
a
e reir Ethernet
eg oP
Dy Input block  Output block

TCP/IP (Transmission Control Protocol / Internet Protocol)
A TCP connection in TIA Portal corresponds to a TCP/IP connection. Since TCP provides a data
flow communication without gathering the data in the messages into blocks, the user does not
receive an explicit acknowledgement per job. That means, only the length of the data flow is
transmitted to the recipient so that it can control the receipt. However, no information about the
beginning or the end of a message is transmitted. From the received segments of the data flow,
the recipient cannot recognize where a message ends in the data flow and where the next
message begins.
Note
M O
For the reasons given above that, with a TCP connection, the recipient cannot determine which
RU
data belongs together and which does not when there is a transmission, the following is
recommended:
t i n ho
The number of bytes to be received should be
C o uassigned the same value as the number of bytes
r e ira can be made.
to be sent. This ensures that the correlation
o Pe
y eg
D

16.5.ISOISO
on TCP
on TCP
100 Bytes 50 Bytes

200 Bytes 200 Bytes
50 Bytes 100 Bytes
M O
RU
o RFC 1006 RFC 1006
ou tinh TCP/IP TCP/IP
ra C
ei
o Per Ethernet
eg
Dy Input block = Output block

ISO on TCP
ISO-on-TCP offers services for the transmission of data of variable length via configured
connections. The ISO-on-TCP service complies with the Standard TCP/IP (Transmission Control
Protocol/Internet Protocol) with the expansion RFC 1006 (Request for Comments) according to
Layer 4 of the ISO Reference Model.
ISO-on-TCP is a message-oriented protocol which, on the recipient side, recognizes the end of
the message and indicates to the user the data belonging to the message. This is regardless of
the specified receipt length of the message. With the data transmission via an ISO-on-TCP
connection, information on length and on the end of a message are also supplied.
Note
M O
RU
When both communication partners support not only TCP but also ISO-on-TCP, the
o
u t inh
communication should take place via ISO-on-TCP as a rule!
Co
a
P e reir
e g o
Dy

16.6.UDP
UDP – User
- User Datagram Protocol
Datagram Protocol
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
UDP is multicast and broadcast capable!

User Datagram Protocol (UDP)
In addition to the connection-oriented TCP, there is also the connectionless and unacknowledged
UDP. The User Datagram Protocol (UDP) is positioned on the 4th Layer, the Transport Layer, of
the OSI Layer Model. It has the same task as TCP, only it doesn’t have any methods which
ensure that a data packet has arrived at the recipient. As well, the numbering of the data packets
is not available. UDP is incapable of putting the data flow in the correct order. The UDP packets
are forwarded directly to the application. A secure data transmission, that is the
acknowledgement that the sent data was actually received by the destination, is the responsibility
of the application.
The only thing UDP and TCP have in common is the port structure. They only differ in the fact
M O
that the UDP port structure doesn’t control a connection; instead it receives the arriving data
packets and forwards them directly to the applications.
o RU
u t inh
Note C o
a
P e reir
For a UDP connection, no connection is established in the network like for the protocols TCP
e g o
native and ISO-on-TCP. Here, there is only a connection from the program to the local interface
of the controller which sends the data.
Dy

16.7.OUC withwith
OUC T-Blocks
T-Blocks
TCP
ISO-on-TCP
M O
R U
o
ou tinh
ra C
e i
o Per
yeg
UDP
D
OUC with T-Blocks
For Open User Communication, the communication between the stations is done via so-called
T-blocks. These get their name from the fact that all of these blocks begin with a "T". The same
blocks can be used for a TCP or an ISO-on-TCP connection. Only a UDP connection requires
separate blocks since no real connection is established between the devices for this type of
connection.
The T-blocks are divided into two types of blocks – as already learned – the combined blocks
(instructions) and the single blocks (instructions). To differentiate, the combined instructions
"TSEND_C", "TRCV_C" and "TMAIL_C" can also be called compact blocks (instructions).
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

16.8.TSEND_C – Send
TSEND_C – Send
DataData
via Ethernet (TCP)(TCP)
via Ethernet

Executing the Send job
Disconnect connection or
establish + maintain
M O
Storage location of the
RU Length of the data to be
connection data
n h o sent
u ti
C o
eira
P e r
Pointer to the
Send area
eg o
Dy
Show further parameters Feedbacks of the block

TSEND_C
The instruction "TSEND_C" is a combined block (instruction) or a compact block. The instruction
"TSEND_C" internally uses the single instructions "TCON", "TSEND", "T_DIAG", "T_RESET" and
"TDISCON". It sets up a communication connection and establishes it. After the connection is
setup and established, it is automatically maintained by the CPU.
The instruction is executed asynchronously and has the following functions:
• Setup and establish a communication connection
• Send data via the existing communication connection
• Disconnect or reset the communication connection
M O
Note
o RU
t inh
If the controller should go into the STOP state, an existing connection is aborted and the setup
u
C o
connection is removed. The instruction "TSEND_C" must be executed once again in order to
a
reir
setup and establish the connection once more.
P e
e g o
Dy

16.9.TRCV_C – Receive
TRCV_C – Receive
DataData
via Ethernet (TCP)(TCP)
via Ethernet

Enable receipt of data
Disconnect connection or
establish + maintain
Activation of the TCP ad-
hoc-mode
M O
U Length of the data to be
h oR received
tin
Storage location of the
connection data
C o u
eira
P e r
Pointer to the Receive area
ego
Dy
Show further parameters Feedbacks of the block

TRCV_C
The instruction "TRCV_C" is the counterpart of the communication block "TSEND_C".
Just like the instruction "TSEND_C", the instruction "TRCV_C" is a compact block (instruction)
and internally uses the following single communication instructions: "TCON", "TRCV", "T_DIAG",
"T_RESET" and "TDISCON".
The "TRCV_C" block makes it possible to receive data, is executed asynchronously and offers in
order the following functions:
• Setup and establish a communication connection
• Receive data via the existing communication connection
M O
• Disconnect or reset the communication connection
o RU
Ad-hoc Mode
u t inh
C o
a
The ad-hoc mode is only available for the protocol variant TCP. The ad-hoc mode is used to
P ereir
receive data that has dynamic lengths with the instruction "TRCV_C".
e g o
The ad-hoc mode is activated by assigning the parameter ADHOC the value "1". When the ad-
Dy
hoc mode is used, all data types can be used for data blocks with standard access. For data
blocks with optimized access, only ARRAY of BYTE or data types with a length of 8 bits can be
used (for example, CHAR, USINT, SINT, etc.) as data types. The actually received data length is
output at parameter RCVD_LEN.
Note
If the controller should go into the STOP state, an existing connection is aborted and the setup
connection is removed. The instruction "TRCV_C" must be executed once again in order to setup
and establish the connection once more.

Programmed
16.10. Connections
Programmed with with
Connections OUC OUC
Programmed M O
connection
RU
o
ou tinh
ra C
e i
o Per
eg
Dy Connection-Data of a
configured instruction

Programmed Connections with OUC
With Open User Communication, not only configured but also programmed connections can be
used. A programmed connection is not established via the controller but via the communication
block. The connection is not created in the Network view in the project but in the user program in
the Properties of the communication block. Blocks which can establish a programmed connection
are, for example, TSEND_C or TRCV_C.
A programmed connection stores the parameters which are required by the connection in a data
block. The advantage of a programmed connection is that the connection resources are not
occupied (used) permanently, but only when they are really required. If required, they can then be
released (enabled) for another connection.
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy

Task
16.11. Description:
Task ISO-on-TCP Communication with
Description:
TSEND_C/TRCV_C
ISO-on-TCP Communication with TSEND_C/TRCV_C
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy

Task Description
Using an OUC communication, a data transmission between the S7-1510SP and the S7-1513
controllers is to take place with the help of the communication blocks TSEND_C and TRCV_C. A
LINT value which is changed before every transmission by the respective controller (addition with
1 or with 2) is to be transmitted. In the first step, the communication between the two controllers
occurs via a configured connection and in the second step a programmed connection is set up
with the help of the T-blocks.
The instruction TSEND_C is controlled on the S7-1510SP via the input “ISOonTCP_Send”
M O
(%I 0.5) and the instruction TRCV_C is controlled on the S7-1510SP with the input
“ISOonTCP_RCV” (%I 0.4). On the S7-1513, the input “OUC_RCV” (%I 0.4) controls the
RU
instruction TRCV_C and the input “OUC_SEND” (%I0.7) control the instruction TSEND_C.
o
u t inh
Co
a
P e reir
e g o
Dy

Exercise 1: Configured
ISO-on-TCP
16.11.1. Exercise 1:Communication on the Communication
Configured ISO-on-TCP S7-1510SP on the S7-1510SP
Create a new ISO-on-TCP

connection
M O
RU
o
On the S7-1510SP
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are to create a configured OUC communication on the S7-1510SP. This OUC
communication is to make a data transmission between the S7-1510SP and the S7-1513
possible. You are to select an ISO-on-TCP connection as the connection type and then you are to
adjust the connection properties. The S7-1510SP is to handle the active establishment of the
connection.
What to Do
1. Switch to the “IK-TIAPN_en_Shared_Device” project.
2. Open the Network view in TIA Portal.
M O
RU
3. Create an ISO-on-TCP connection between the S7-1510SP and the S7-1513.
o
u t inh
4. Name the connection “ISOonTCP_TSENDC-TRCVC” and adjust the properties of the
connection.
Co
a
reir
P e
e g o
Dy

Exercise 2: Configured
ISO-on-TCP
16.11.2. Exercise 2:Communication on the Communication
Configured ISO-on-TCP S7-1513 on the S7-1513
Create a new ISO-on-TCP

connection
M O
RU
o
On the S7-1513
ou tinh
ra C
e i
o Per
eg
Dy
Task
You are now to create the other half of the two-way OUC communication on the S7-1513. Name
the ISO-on-TCP connection on the S7-1513 “ISOonTCP_TRCV-TSENDC”. Select the correct
connection properties.
What to Do
1. Switch to your initial project.
3. Create an ISOonTCP connection between the S7-1513 and the S7-1510SP.
M O
4. Name the connection “ISOonTCP_TRCV-TSENDC” and adjust the properties of the
connection.
o RU
u t inh
Co
a
Note
P e reir
e g o
Dy
parameters of the connection.

Exercise
16.11.3. 3: 3:
Exercise TSEND_C––Configured
TSEND_C Connection
Sending Data
Sending from
Data fromthe
theS7-1510SP
S7-1510SP
Add +2 to the value before

sending
M O
R U
o
ou tinh
ra C
e i
o Per Sending the data with
TSEND_C
eg
New (to be generated) Dy
blocks for the OUC

Task Description
Now that you have established a communication between the two controllers, you are to program
the sending of data from the S7-1510SP to the S7-1513. In the first step, you are to create a
Shared DB with the name “DB_OUC_SharedDB” for this and in it create the variable
“Value_TSENDC-TRCVC” of the data type “LINT”. Then, you are to create a function block with
the name “FB_OUC” and call it in the OB ‘Main’. Finally, you are to program the instruction
TSEND_C and the addition of 2 to the send value before each send operation (Value_TSENDC-
TRCVC := Value_TSENDC-TRCVC + 2;). Logically, the addition must be programmed with an
edge evaluation. You are to use, as often as possible, the programming method "multi-instance”.
O
The TSEND_C block is controlled via the input “ISOonTCP_Send” (%I 0.5), which, if it doesn’t
M
RU
exist, must still be created by you.
o
What to Do
u t inh
C o
a
P e reir
2. Create the new function block “FB_OUC”.
g o
3. Create a new global data block “DB_OUC_SharedDB” and in it the variable “Value_TSENDC-
e
Dy
TRCVC” of the data type “LINT”.
4. Call the FB “FB_OUC” in OB “Main”.
5. In this function block program the required functionality according to the task with the help of
the TSEND_C instruction.
6. Use the configured connection and not a programmed connection.
Note
block.
Don’t forget the programming of the addition before the processing of the block TSEND_C.

If necessary, add the evaluation of the output parameters “DONE”, “ERROR”, “BUSY” and
“STATUS” of the instruction TSEND_C. Get the functionality of these parameters from the Online
Help of TIA Portal.
With the configured connection, please pay attention to the parameter: “CONT” (this is a hidden
parameter that only becomes visible when the “TSEND_C” block is expanded).
Statuses:
0: Disconnect communication connection.
1: Establish and maintain communication connection.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

Exercise
16.11.4. 4: 4:
Exercise TRCV_C––Configured
TRCV_C Connection
Receiving Data
Receiving Dataininthe
theS7-1513
S7-1513
Receiving the data with

TRCV_C
M O
R U
o
New (to be generated) ou tinh
blocks for the OUC
ra C Error evaluation
rei
Error evaluation if required
if required
P e
e g o
Dy

Task Description
So that the data, which is sent from the S7-1510SP, can also be received on the S7-1513, the
block TRCV_C must be created and commissioned in it.
For this, you are also to create a global data block with the name “DB_OUC_SharedDB” and in it
the variable “Value_ TRCVC-TSENDC” of the data type “LINT”. Then, you are to generate a
function block “FB_OUC” and call it in the OB “Main”. After that, the instruction TRCV_C is
programmed in this FB so that the data from the S7-1510SP can also be received. The ‘ready to
receive’ of the TRCV_C block is established via the input “OUC_RCV” (%I 0.4). If this doesn’t
already exist in your project, you are to create it.
M O
What to Do
o RU
u t inh
C
2. Create the new function block “FB_OUC”. o
i r a
ere“DB_OUC_SharedDB” and in it the variable “Value_ TRCVC-
3. Create a new global data block
TSENDC” of the data typeP“LINT”.
y egoin OB “Main”.
4. Call the FB “FB_OUC”
D
5. In this function block program the required functionality according to the task with the help of
the TRCV_C instruction.
6. Use the configured connection and not a programmed connection.
8. Test whether the data sent from the S7-1510SP is received on the S7-1513. For each send
job, you should receive a higher value (+2).
9. If this is not the case, make the necessary changes on both controllers.

Note
block.
If necessary, add the evaluation of the output parameters “DONE”, “BUSY”, “ERROR”,
“RCVD_LEN” and “STATUS” of the instruction TRCV_C. Get the functionality of these
parameters from the Online Help of TIA Portal.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

Exercise
16.11.5. 5: 5:
Exercise TSEND_C––Programmed
TSEND_C Connection
Sending Data
Sending from
Data fromthe
theS7-1513
S7-1513
Add +1 to the value before

sending
M O
R U
o Programmed connection
ou tinh via DB!
ra C
e i
Same block
FB_OUC + DB o Per
eg
Dy
Error evaluation if required

Task
Now that data can be transmitted from the S7-1510SP to the S7-1513, the S7-1513 should also
be able to send data to the S7-1510SP. For this, you are to set up a programmed connection on
the S7-1513 via the TSEND_C block. For this communication, the variable “Value_TRCVC-
TSENDC” from the data block “DB_OUC_SharedDB” is also transmitted. So that you can check
the success of this send job, the variable “Value_TRCVC-TSENDC” is increased by ‘1’ before
every send (Value_TRCVC-TSENDC := Value_TRCVC-TSENDC + 1;). The send job on the
S7-1513 is triggered via the input “OUC_SEND” (%I 0.7). If it doesn’t exist, you are to create it.
What to Do
M O
o RU
2. Open the block “FB_OUC”.
u t inh
C o
3. In it, program the required functionality according to the task with the help of the TSEND_C
a
Pe reir
instruction. Don’t forget the addition of the value before the sending. A programmed
connection and not a configured connection is to be used!
o
eg download the changes into the controller.
4. Save your project and
D y
Note
block.
If necessary, add the evaluation of the output parameters “DONE”, “ERROR”, “BUSY” and
“STATUS” of the instruction TSEND_C. Get the functionality of these parameters from the Online
Help of TIA Portal.
The input %I 0.7 is now assigned twice with a symbolic name. For the exercise, this is irrelevant,
but for a real system it should be avoided!
With the programmed connection, please pay attention to the parameter: “CONT” (this is a hidden
parameter that only becomes visible when the “TSEND_C” block is expanded).

Statuses:
0: Disconnect communication connection.
1: Establish and maintain communication connection.
The communication connection is terminated when the CONT parameter is set to "0" even if an
ongoing (running) data transmission has not yet been completed. This, however, does not apply if
you are using a configured connection for "TSEND_C".
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
Co
a
Pe reir
e g o
Dy

Exercise
16.11.6. 6: 6:
Exercise TRCV_C––Programmed
TRCV_C Connection
Receiving Data
Receiving Dataininthe
theS7-1510SP
S7-1510SP
Programmed connection
via DB!
M O
R U
o
ou tinh
Same block
ra C
e i
Per
FB_OUC + DB
o Error evaluation if required
Dyeg

Task
Finally, the data sent from the S7-1513 must also be received by the S7-1510SP. For this, you
are to program a programmed connection in the function block “FB_OUC” with the help of the
instruction TRCV_C. Receiving on the S7-1510SP is enabled via the input “ISOonTCP_RCV”
(%I 0.4). If it doesn’t exist, you are to create it.
What to Do
1. Switch to your “IK-TIAPN_en_Shared_Device” project.
2. Open the block “FB_OUC”.
M O
3. In it, program the required functionality according to theR U
task with the help of the TRCV_C
n h o
instruction. A programmed connection and not a configured connection is to be used!
u t i
C
4. Save your project and download the changes o into the controller.
a
eir a programmed connection was successfully established
5. In the Network view, check whether
on both controllers. P e r
g o
e sent from the S7-1513 is received on the S7-1510SP. For each send
6. Test whether theydata
job, you shouldDreceive a higher value (+1).
7. If this is not the case, make the necessary changes on both controllers.
Note
block.
If necessary, add the evaluation of the output parameters “DONE”, “BUSY”, “ERROR”,
“RCVD_LEN” and “STATUS” of the instruction TRCV_C. Get the functionality of these
parameters from the Online Help of TIA Portal.

WennAdditional
Information
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Netzübergänge Seite 20 Siemens AG © 2016
Note
M O
o RU
u t inh
C o
a
Pe reir
e g o
Dy

TUSEND
16.13. – Send
TUSEND – Send
DataData
via Ethernet (UDP)(UDP)
via Ethernet

Executing the Send job
ID of connection
CPU → remote CPU
Length of the data to be M O

sent
R U
o
ou tinh
Send area
ra C
e i
o Per
Address information of
eg
the remote partner
(TADDR_Param) Dy Feedbacks of the block

TUSEND
The communication instruction "TUSEND" sends data to a remote station, which can then receive
this via the instruction "TURCV". The instruction requires a previously configured UDP connection
in the Network view from which the ID to the block is parameterized. All further address data of
the destination station are passed to the block via the parameter "ADDR". The data type which is
expected at the parameter "ADDR" is the system data type "TADDR_Param".
TADDR_Param
When a UDP connection is used, the address information of the remote partner is stored in the
system data type TADDR_Param. For the instruction "TUSEND", this is the address information
of the recipient.
U MO
The system data type "TADDR_Param" is not recognized o Rby the Intelli-Sense of TIA Portal and
n
must be entered manually. The easiest way to doithis
t his via Copy & Paste from the Online Help of
TIA Portal!
C o u
i r a
Note
P ere
y egovia UDPandaccording
With the data transmission
partner without acknowledgement
to RFC 768, the data is transmitted to a remote
thus unsecured. This means that data can be lost without
D at the block.
this being indicated
For consecutive send operations to various partners, only the parameter ADDR has to be
adjusted for the calls of "TUSEND". The renewed call of the instructions "TCON" and "TDISCON",
on the other hand, is not available. So that the respective remote partner can receive the data,
the addressed UDP port must be set up there.

TURCV
16.14. – Receive
TURCV – Receive
DataData
via Ethernet (UDP)(UDP)
via Ethernet

Enable receipt of data
ID of connection
CPU → remote CPU
M O
Length of the data to be
received R U
o
ou tinh
Receive area
ra C
ei
o Per
Address information of
eg
the remote partner
(TADDR_Param) Dy Feedbacks of the block

TURCV
The communication instruction "TURCV" is the counterpart of the instruction "TUSEND" and
receives data which were sent from it. Here, as well, a previously created UDP connection is
required so that the ID can be parameterized to the block. The remaining data of the remote
station are also passed to the instruction via the input parameter "ADDR".
The data type which is expected at the parameter "ADDR" is the system data type
"TADDR_Param".
TADDR_Param
When a UDP connection is used, the address information of the remote partner is stored in the
M O
system data type TADDR_Param. For the instruction "TURCV", this is the address information of
the sender.
o RU
t inh
The system data type "TADDR_Param" is not recognized by the Intelli-Sense of TIA Portal and
u
o
must be entered manually. The easiest way to do this is via Copy & Paste from the Online Help of
C
a
reir
TIA Portal!
P e
e g o
Note
Dy
With the data transmission via UDP according to RFC 768, the data is transmitted without
acknowledgement and thus unsecured to a remote partner. This means that data can be lost
without this being indicated at the block.

Task
16.15. Description:
Task Description:
UDP Communication
UDP Communicationwithwith
TUSEND/TURCV
TUSEND/TURCV
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Task Description
You are to create a UPD connection between the S7-1510SP and the S7-1513. With the help of
the instruction “TUSEND”, the S7-1513 then sends a LINT value to the S7-1510SP which
receives this via the instruction “TURCV”.
Before every send job, the send value is increased by 69 via an edge evaluation of the send input
“OUC_SEND” (%I 0.7). The receiving of send data is enabled on the S7-1510SP via the input
“UDP_TURCV” (%I 0.3).
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Exercise
16.15.1. 1: 1:
Exercise Setting
SettingUp
UpaaUDP
UDP Connection
Connection
M O
R U
o
outinh
ra C
ei
o Per
eg
Create UDP
connection on both
Dy
controllers

Task
You are to create a UDP connection between the S7-1513 and the S7-1510SP. On the
S7-1510SP, you are to assign the ID “310” and on the S7-1513 the ID “313” for the connection.
On the S7-1510SP, you are to use the port “4444” and on the S7-1513 the port “2222”.
On the S7-1513, you are to give the connection the name “UDP_TUSEND-TRDV” and on the
S7-1510SP give it the name “UDP_TURCV-TUSEND”.
What to Do
U MO
3. Create a UDP connection between the S7-1510SP andR
n h o the S7-1513.
i described in the task.
4. Assign the properties as shown in the picturetand
u
C o
i r a
6. Here as well, open the Network
P ereview.
ego between the S7-1513 and the S7-1510SP.
7. Create a UDP connection
y
D as shown in the picture and described in the task.
8. Assign the properties
9. Save your projects and download the changes.

Exercise
16.15.2. 2: 2:
Exercise TUSEND
TUSENDInstruction – S7-1513
Instruction – S7-1513
Addition +69
send value
M O Send via UDP
R U
o
ou tinh
ra C New send value for UDP
P e rei
e g o
Dy
Address S7-1510SP

Task
You are to create a new variable “Value_TUSEND-TURCV” of the data type “LINT” in the data
block “DB_OUC_SharedDB”. Then you are to open the block “FB_OUC” and in it program the
data transmission of the value via the UPD connection with the help of the instruction “TUSEND”.
Before every send job, the variable “Value_TUSEND-TURCV” is to be increased by 69
(Value_TUSEND-TURCV := Value_TUSEND-TURCV + 69;). The send job is triggered via the
input “OUC_SEND” (%I 0.7).
What to Do
M O
2. Open the data block “DB_OUC_SharedDB” and add the required variable.
o RU
3. Open the function block “FB_OUC” and program the data transmission with the help of the
“TUSEND” block as required in the task.
u t inh
Co
a
Note Pe reir
o
eallgnecessary temporary as well as static variables within the function
block. D y
Independently, create
Use multiple instances.

If required, take the layout and the structure of the data type “TADDR_Param” from the Online
Help of TIA Portal.
Use the default value when entering the data of the destination station (S7-1510SP).

Exercise
16.15.3. 3: 3:
Exercise TURCV Instruction –
TURCVInstruction S7-1510SP
– S7-1510SP
Receive via UDP
M O
R U
o
ou tinh
ra C
ei
Per
Address S7-1513
ego
Dy
Task
You are to create a new variable “Value_ TURCV-TUSEND” of the data type “LINT” in the data
block “DB_OUC_SharedDB”. Then you are to open the block “FB_OUC” and in it program the
receipt of the sent data with the help of the instruction “TURCV”. The enable for receiving the
data is controlled via the input “UDP_TURCV”.
What to Do
2. Open the data block “DB_OUC_SharedDB” and add the required variable.
O
3. Open the function block “FB_OUC” and program the receipt of data with the help of the
M
“TURCV” block as required in the task.
RU
t i n ho
5. Test whether your programming fulfillsC
the
u If necessary, make corrections.
otask.
r e ira
Note
o Pe
allgnecessary temporary as well as static variables within the function
Independently, createe
block. D y
Use multiple instances.
If required, take the layout and the structure of the data type “TADDR_Param” from the Online
Help of TIA Portal.
Use the default value when entering the data of the destination station (S7-1510SP).

Contents 17
17. OPC UA ................................................................................................................. 17-2
17.1. OPC UA – The Open Standard Interface ........................................................................... 17-3
M O
17.2.
R U
OPC UA – One for All ......................................................................................................... 17-4
o
tinh
17.3. System Solution with OPC UA & PROFINET ..................................................................... 17-5
17.4. ou
OPC UA Security Architecture ............................................................................................ 17-6
C
17.5. OPC UA Communication Methods
r e ira..................................................................................... 17-7
17.6.
o Pe
OPC UA Server ................................................................................................................... 17-9
e g
DyLicensing ................................................................................................ 17-11
17.6.1. Activating the OPC UA Server .......................................................................................... 17-10
17.6.2. OPC UA Server
17.6.3. OPC UA Server Options ................................................................................................... 17-12
17.6.4. OPC UA Server Export ..................................................................................................... 17-14
17.6.5. OPC UA Server Export Configuration ............................................................................... 17-15
17.7. Information Security .......................................................................................................... 17-16
17.8. OPC UA Security .............................................................................................................. 17-17
17.8.1. OPC UA Trusted Clients ................................................................................................... 17-18
17.8.2. OPC UA User Authentication ............................................................................................ 17-19
17.9. OPC UA Access Overview ................................................................................................ 17-20
17.10. OPC UA Certificate Handling ............................................................................................ 17-21
17.11. Certificate Management of the Controller ......................................................................... 17-22
17.12. Generating OPC UA Server Device Certificates ............................................................... 17-23
M O
17.13. Global Security Settings .................................................................................................... 17-24
RU
17.13.1. Activation ........................................................................................................................... 17-24
o
inh
17.13.2. Administrator Login ........................................................................................................... 17-25
u t
17.13.3. Contents ............................................................................................................................ 17-26
o
C
17.13.4. Certificate Manager ........................................................................................................... 17-27
a
reir
17.13.4.1. Certificate Authority CA ................................................................................................ 17-27
e
17.13.4.2. Device Certificates ....................................................................................................... 17-28
P
e g o
17.13.4.3. Trusted Certificates and Root Certification Authorities ................................................ 17-29
Dy
17.14. Task Description: OPC UA Communication between Server and Client......................... 17-30
17.14.1. Exercise 1: Activating the OPC UA Server ....................................................................... 17-31
17.14.2. Exercise 2: Creating a DB for the OPC UA Communication ............................................ 17-32
17.14.3. Exercise 3: UaExpert: Adding an S7-1500 ....................................................................... 17-33
17.14.4. Exercise 4: Connect, Browse, Read & Write + Subscription ............................................ 17-34
17.14.5. Exercise 5: Exporting the UAExpert Client Certificate ...................................................... 17-36
17.14.6. Exercise 6: Activating the Global Security Settings .......................................................... 17-37
17.14.7. Exercise 7: Importing the UAExpert OPC UA Client Certificate ....................................... 17-38
17.14.8. Exercise 8: Creating OPC UA Server Device Certificates ................................................ 17-39
17.14.9. Exercise 9: Setting the Security Policies of the Controller ................................................ 17-40
17.14.10. Exercise 10: Adding UaExpert as a Trusted Client........................................................... 17-41
17.14.11. Exercise 11: TIA Portal OPC UA Certificate Export & Import ........................................... 17-42
17.14.12. Exercise 12: UA Expert: Establishing a Connection to the S7-1500 ................................ 17-44
17.14.13. Exercise 13: Connect, Browse, Read & Write + Subscription .......................................... 17-45
IK-TIAPN – OPC UA
OPC UA
17. Objectives
… understand the basics of an OPC UA communication
... be familiar with the various OPC UA communication methods
... understand the OPC UA Security Architecture
... be able to activate and parameterize the OPC UA Server of the S7-1500
... O
develop a basic understanding for certificates
M
R U
...
o
get an introduction to the global security settings in TIA Portal
ou tinh
ra C
e i
o Per
eg
Dy

Page 2 OPC UA
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.1.OPC
OPC – The
UA UA – The
Open Standard
Open Interface
Standard Interface
Openness due to standardized

interface
Connecting any OPC UA

Clients to every S7-1500
Symbolic access to
optimized + classic data
Cloud
Security Integrated
Scalability of
MO
security measures
R U
n h o
u ti
C o S7-1500, ODK 1500S, 1500T,
a
reir
ET200SP CPU, PLCSIM Adv.
Pe
e g o
Dy

Page 3 OPC UA
OPC UA
The OPC Foundation (Open Platform Communications) is an interest group of renowned
manufacturers for the definition of standard interfaces. In order to standardize the information flow
from the process level up to the management level, the OPC Foundation has defined a wide
range of software interfaces in recent years. Reflecting the different requirements within an
industrial application, the following OPC specifications evolved in the past:
• Data Access (DA) – access to process data
• Alarm & Events (A&E) – describes an interface for event-based information including
acknowledgement
• M O
Historical Data Access (HDA) – describes functions for archived data
• o RU
inh
Data eXchange (DX) – defines a server-to-server cross communication.
o u t
a C
e reir
Based on the experiences of these ‘classic’ OPC interfaces, the OPC Foundation has defined a
new platform with the name OPC UA (Unified Architecture). Goal of this standard is the generic
P
g o
description and the uniform access to all information that must be exchanged between systems
e
Dy
and/or applications. This includes the functionalities of all OPC interfaces so far.
Furthermore, the interface can be natively integrated in the particular system. The integration is
irrespective (of) on which operating system the system is operated and with which programming
language the system was created.
You will find further information on the OPC Foundation Homepage: www.opcfoundation.org.
IK-TIAPN – OPC UA
17.2.OPC – One
UA UA
OPC – One
for All
for All
Cloud
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Perfect interoperability at all automation levels due to Openness and Standards

Page 4 OPC UA
OPC UA – The Challenges
In the course of digitalization, automation technology faces the challenge of creating
interoperability between the various levels of automation. The following challenges are
particularly focused on:
• Industry 4.0 / IoT in the Industrial Environment

Within the framework of digitalization, the networking and communication of different
systems play a key role.
• Interoperability between Production and IT Level

M O
The (company) management level is provided with data from the production and process
RU
level in order to ensure the product quality and to optimize production, for example.
o
• Networking of different Devices and Systems
u t inh
C o
In order to network systems of a wide variety of platforms (PC, PLC, HMI, Tablets,…)
a
reir
with one another, an independent and open standard is necessary. However, in order to
e
be able to clearly interpret the data of a wide variety of systems and manufacturers, a
P
e g o
semantic description of the data is integrated.
• IT Security Dy
Within the framework of networking across plant components, the topic of data security
becomes increasingly important. This includes not only the access protection but also
secure transmission methods in particular via the internet.
IK-TIAPN – OPC UA
17.3.System Solution
System Solution OPCOPC
withwith PROFINET
UA &UA & PROFINET
OPC UA PROFINET
Platform-independent Cloud Deterministic
Direct device connection Real-Time-capable
through all levels Management
OPC UA Interface
level Real-time C2C –
PROFINET
Authentication communication
Encryption Operator level
M O Standardized profiles
Semantic services R U
t
Control leveli n ho
C ou
a
P ereirField level
Advantages in the Data &
e g o Advantages in the Control &
Management level
Dy Machine level

Page 5 OPC UA
OPC UA – The Solution
The previously mentioned challenges require an open communication standard for I4.0
communication concepts. As a supplement to PROFINET, OPC UA offers a convenient interface
to third-party providers and for connecting to higher-level systems such as SCADA, MES or to a
Cloud. The following added values are generated by OPC UA:
• Simple, standardized and secure connectivity at all levels
• Platform and manufacturer independent
• With the combination of OPC UA & PROFINET, fulfill all requirements of industry within
the framework of digitalization
M O
•
RU
Limitless communication at all levels without having to use gateways or additional
hardware
t i n ho
• ou
Utilizing only one network from the automation
C level right up to the IT level
• Unrestricted parallel operationa
eir with PROFINET and TCP/IP
•
e r
P existing PN network through OPC UA devices
e g o
Easy expansion of the
•
Dy
Maximum scalability
Note
OPC UA is, however, no replacement for the existing fieldbus protocols. No devices are directly
connected (for example, drives, valves, I/O modules,…) via OPC UA.
IK-TIAPN – OPC UA
17.4.OPC
OPC Security
UA UA Architecture
Security Architecture
OPC UA Client OPC UA Client
Application Layer Application Layer

7 Session
• User authorization • User authorization
6 • User authentication • User authentication
Session Layer
M O• Trusted
Session Layer
5
• Trusted
• Integrity
Secure Channel
R U
o • Integrity
• App authentication
ou tinh • App authentication
ra C
2
e i
1 3
Per Transport Layer
4
ego
Dy

Page 6 OPC UA
OPC UA Security Architecture
OPC UA has a security architecture which consists of the following three layers:
• Session
The user authentication is carried out through the Session. This occurs, for example,
through a user name and a password or through certificates.
• Secure Channel
The mutual authentication of the applications and a message-based securing of the
communication occur through a Secure Channel. Each message is signed and
encrypted in order to ensure the integrity and the confidentiality of the messages. The
O
basis of these mechanisms is certificates (X509) that uniquely identify the applications
M
through a Public Key Infrastructure (PKI) system.
o RU
• Transport Layer
u t inh
o
On the Socket level/Transport Layer level, a connection-oriented safeguarding and
C
a
socket connection through Secure Socket Layer (SSL) or through Virtual Private Network
P e reir
(VPN) can be utilized in addition to or alternatively to the Secure Channel.
e g o
Dy
IK-TIAPN – OPC UA
17.5.OPC
OPC Communication
UA UA Methods
Communication Methods
OPC UA Server OPC UA Client
Browsing
Read/Write
Registered
Read/Write
M O
RU
Subscription
o
ou tinh
ra C
e i
o Per
eg
Dy

Page 7 OPC UA
OPC UA Communication Methods
Currently, the following services are available for the S7-1500 in order to access the data of an
OPC UA server:
• Read
• Write
• Registered Read/Write
• Subscriptions
Browsing
U MO
OPC UA servers provide information in the form of nodes.R
n h o A for
or a method, for example. Nodes have numerous iattributes,
node can be an object, a tag/variable
example, "NodeID",
u
"BrowseName", "Description". A tag/variableoalsot contains the attribute "Value" that contains the
value for PLC tags/variables. a C
e r eir
Address Space
o P
g
ye to one another via references, for example, via the reference
The nodes are connected
D
"HasComponent" that reflects a hierarchical relationship between a node and its subordinate
nodes.
Through their references, the nodes build a network that can take on the form of a tree, but also
other forms. A network of nodes is also referred to as address space. Starting from the root, all
nodes in the address space of the S7-1500 CPU’s OPC UA server are accessible.
Read / Write Access

If the name space index, identifier and data type of PLC tags is known, then individual PLC tags
and DB variables as well as entire Array data blocks and structures can be directly read with this
information.
With the information that you get when navigating through the address space of the server (index,
identifier and data type), values can also be transferred into the S7-1500 with an OPC UA client.
IK-TIAPN – OPC UA
Registered Read / Write Access

As standard method, the character string is used as an identifier, for example,
"DB_OPC_UA"."BrowsingRead". But if you use an internal address instead of a character string
as identifier, accesses are considerably faster. For that reason, the functions "RegisteredRead"
and "RegisteredWrite" should be used for regular accesses to certain tags/variables.
Here, the client first of all registers the PLC tag with the server. The server returns an identifier
that the client uses for the actual accesses. This identifier applies exclusively for the current
session and must be re-obtained in case of termination/loss of the session.
Subscription
The service "Subscription" denotes a function where only variables are transmitted for which an
OPC UA client has logged on to the OPC UA server. The OPC UA server only sends a message
O
to the OPC UA client for these registered variables (subscriptions) when a value has changed.
M
U
Through the monitoring of these variables, a constant querying by the OPC UA client is not
R
required and the network load is thereby reduced. o
ou tinh
In order to use this function, you must create a subscription. For this, the "Publishing Interval" is
set at the OPC UA client. The "Publishing Interval" is the time interval in which new values are
ra C
sent to the client. In the S7-1500 CPU’s OPC UA server, you can specify the smallest update
e i
Per
interval permitted by the server with the help of the parameter "Minimum publishing interval". A
o
subscription of an OPC UA client cannot undercut this interval.
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.6.OPC UA UA
OPC Server
Server
OPC UA Server
M O OPC UA Client
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Flexible Increased performance Individual enable per
access possibilities for Structures + Arrays tag/variable

Page 8 OPC UA
OPC UA Server
The S7-1500 CPUs as of Firmware 2.0 are equipped with an OPC UA server. With "S7-1500
CPUs", the CPU variants S7-1500F, S7-1500T, S7-1500C as well as S7-1500pro CPUs, ET
200SP CPUs as well as the SIMATIC S7-1500 SW Controller are also meant.
Access to the CPU’s OPC UA server is possible via all integrated PROFINET interfaces of the
CPU 1500. The exception to this is the SIMATIC S7-1500 SW Controllers. For them, access to
the OPC UA server is only possible via interfaces that are used for the Software-PLC. For
Firmware 2.0, access is not possible via CP or CM.
For access through clients, the server stores the PLC tags and other information that is made
available in the form of nodes. The nodes are connected to one another and form a network. The
M O
OPC UA Client can browse through this network and can connect itself with one of the previously
explained services on a node.
o RU
Performance u t inh
C o
a
reir
When a wide range of tags/variables are to be read or written from an S7-1500, the performance
e
can be considerably increased by structuring the tags/variables in the S7-1500. For this, Arrays
P
e g o
and Structures are used in order to declare variables to be read / written.
Dy
Viewed individually, Arrays have the best performance. They are about factor 2 to 3 faster than
Structures and these are about factor 10 to 100 faster than individual accesses (for a number of
about 1000 variables).
Note
For recurring accesses, "Registered Read / Write" leads to an increased performance vis-à-vis
normal Read / Write accesses.
IK-TIAPN – OPC UA
Activating
17.6.1. the
Activating OPC
the OPCUA
UAServer
Server
After activating, adjust OPC UA Security

settings!
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 9 OPC UA
Activating the OPC UA Server
The OPC UA server of an S7-1500 controller is activated in the Properties of the PLC. In the
menu item "OPC UA" you will find the checkbox "Activate OPC UA server". As soon as the OPC
UA server has been activated, you must subsequently still confirm that a Runtime license has
been purchased for this option. This is done in the controller’s "Runtime licenses" menu item. The
dialog menu automatically stipulates which license is required for the configured controller.
Note
When the OPC UA server on the controller is used, the following security note appears:
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
This is to inform you that a parameterization of the OPC UA server with regard to security
measures must still be carried out!
IK-TIAPN – OPC UA
OPC
17.6.2. UAUA
OPC Server Licensing
Server Licensing
≙ OPC UA S7-1500 License
M O
small medium R U large
o
S7-1511 / S7-1513
ou tinh
S7-1515 / S7-1516 S7-1517 / S7-1518
S7-1510 / S7-1512
ra C
e i
Per
y ego
D concept with ‘own’ MLFBs depending on the PLC performance class
Simple licensing

Page 10 OPC UA
Licensing
A so-called Runtime license is required for using the OPC UA server on an S7-1500 controller.
This license model was introduced with TIA Portal Version V14 and Firmware V2.0 of the
S7-1500.
There are three different Runtime licenses. Depending on the controller model, you must
purchase either a license of the type "small" (1510, 1511, 1512, 1513), "medium" (1515, 1516) or
"large" (1517, 1518). Currently, this license is only a "paper license". There is no transmission or
similar to the controller. A data points limitation, which can be made available via OPC UA, does
not exist.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
OPC
17.6.3. UAUA
OPC Server Options
Server Options
M O
R U
o
tinh
Cou
OPC UA Server Port number
eira
P e r Limits for the OPC UA Server
o
yeg
Client communication
D
Page 11 OPC UA
OPC UA Server Setting Options
In the (setting) Options of the OPC UA server on an S7-1500, you can configure the following
parameters:
• Port
• Minimum publishing interval
• Minimum sampling interval
Port
O
The port number further specifies the accessibility of the OPC UA server. This must be specified
M
OPC UA client. o RU
along with the IP address of the server / controller when a connection attempt is made via an
t inh
By default, OPC UA uses the TCP-Port 4840. Another port can, however, also be selected.
u
o
Entries of 1024 to 49151 are possible. It is however important that no conflicts with other
C
a
reir
applications result. OPC UA clients must use the chosen port when establishing a connection
e
(only the standard port 4840 can be omitted).
P
e g o
Dy
Minimum Publishing Interval
With "Minimum publishing interval", the timely intervals are set in which the server sends a
notification with the new value to the client when there is a value change.
Minimum Sampling Interval

With "Minimum sampling interval", the timely intervals are set in which the OPC UA server
acquires the value of a CPU tag/variable and compares it to the value so far in order to determine
a value change.
IK-TIAPN – OPC UA
Note
These values have an influence on the communication load and CPU load and should therefore
be taken into consideration!
The smallest possible values depend on the CPU type.
If a smaller sampling interval is selected than the publishing interval and an OPC UA client
requires such a high (number of) publishing intervals for certain PLC tags, then two or more
values can accrue per publishing interval.
In this case, the OPC UA server writes the value changes in the queue and sends all value
changes to the client after the publishing interval has expired. If more value changes accrue in
the publishing interval than fit in the queue, the OPC UA server then overwrites the oldest values.
The most current values are sent to the client.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
OPC
17.6.4. UAUA
OPC Server Export
Server ExportConfiguration
Configuration of
Clients without CPU
XML Export
Standardized OPC
UA XML file
Export via TIA Portal

Download
MO
Openness API
RU
n h o
u ti
C o
eira
P e r
eg o
Dy
Page 12 OPC UA
Export OPC UA Server Configuration
The configuration of an OPC UA client is normally done via the connection to an OPC UA server
and the subsequent browsing of nodes / variables. Should, however, the OPC UA server not be
available, there is the following possibility.
The configuration of the controller’s OPC UA server can also be saved on any computer or
medium via an XML export. This XML file complies with the XML schemata of the OPC
Foundation. With the help of this file, an "offline" configuration of an OPC UA client can be
undertaken without having to connect online to an OPC UA server.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
IK-TIAPN – OPC UA
OPC
17.6.5. UAUA
OPC Server Export
Server ExportConfiguration
Configuration
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 13 OPC UA
S7-1500 XML Export OPC UA Server Configuration
The export of the OPC UA server configuration occurs in the Properties of the S7-1500. Under
the menu item "OPC UA" you will find the sub-item "Export". Here, an export operation of the
OPC server configuration can be carried out via the button "Export OPC UA XML file".
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.7.Information Security
Information Security
“The only communication technology in the factory,

with implicit security features and the potential for the
challenges posed by Industry 4.0, that
M OI am aware of
U
today, is OPC UA” oR
u t inh
C o
— Holger Junker, Head of Unit ‘Cyber-Security in critical IT-Systems, Application
i r a
ere
Architectures’, BSI (Federal Office for Information Security)
P
y ego
D

Page 14 OPC UA
Information Security
OPC UA complies with the global security requirements of the Federal Government (of
Germany). That is, OPC UA is the only communication medium that currently meets the demands
for security and safety laid down by the Federal Government.
Especially in the course of the starting and ever increasing digitalization, OPC UA will therefore
gain in importance and in future will increasingly be put to use in automation.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.8.OPC UA UA
OPC Security
Security
OPC UA Server certificate
M O Available Security Policies
R U
o
tinh
Sign(ing) = protection against
ou
data manipulation
ra C
e i
Per
Encrypt(ion) = protection
against data espionage
ego
Dy

Page 15 OPC UA
OPC UA Security
After the controller’s server certificate has been stored, further security setting options must still
be made. You have to specify via which policy the OPC UA server can communicate with the
OPC UA client. To ensure a secure communication, the highest security policy is therefore
chosen.
Sign
During signing, the sender first of all produces a hash value from the plain text (plain message).
Then, the sender encrypts the hash value and finally transfers the plain text along with the
encrypted hash value to the recipient. To verify the signature, the recipient requires the sender’s
M O
public key (is included in the sender’s X509-certificate). With the sender’s public key, the recipient
RU
decodes the hash value received. Then, the recipient himself produces the hash value from the
o
recipient compares the two hash values: u t inh
plain text received (the hash method is included in the sender’s certificate). Subsequently, the
C o
a
reir
• If the two hash values match, the plain message has not been tampered with (and the
e
recipient received the message unchanged): The transferred file was not manipulated.
P
• o
g thatdowas
identical D yeone
If the two hash values
to the
not match, then the recipient did not receive the plain message
sent: The transferred file was manipulated or damaged
during transmission.
The integrity of a message can be proven via a signature.
Encrypt
Files can be encrypted. This prevents unauthorized (persons) from obtaining knowledge of the
contents. X509-certificates are not encrypted and are public and anyone can inspect them.
During encryption, the sender encrypts the plain message with the recipient’s public key. For this,
the sender requires the recipient’s X509-certificate because it contains the recipient’s public key.
The recipient decodes the message with his private key. Only the recipient can decode the
message. He alone has the private key. For that reason, the private key must never be passed
on.
IK-TIAPN – OPC UA
OPC
17.8.1. UAUA
OPC Trusted
TrustedClients
Clients
Trusted Clients does not mean

that server data can be
accessed!
M O Clients that may establish a

R U
o secure channel
ou tinh
ra C Every client may establish a
secure channel to the server
e i
o Per
eg
Dy
Page 16 OPC UA
Trusted Clients
There can only be a secure connection between the OPC UA server and an OPC UA client if the
server classifies the client’s certificate as trustworthy. The user must decide whether he trusts the
client’s certificate.
If the option "Automatically accept client certificates during runtime" is deactivated, only OPC UA
clients that have been defined as a trusted source can establish a communication with the OPC
UA server. This however does not mean that the data of the OPC UA server may automatically
be accessed!
Caution
Setting after commissioning: M O
RU
To prevent security risks, deactivate the option "Automatically accept client certificates during
o
inh
runtime" after commissioning!
o u t
a C
P e reir
e g o
Dy
IK-TIAPN – OPC UA
OPC
17.8.2. UAUA
OPC User Authentication
User Authentication
Binary user authentication

Every authenticated user may
access the same data
Permit Anonymous / Guest

Login
M O
RU User authentication with
n h o user name + password
u ti
C o
eira List of all valid user names as
P e r well as their passwords
ego
Dy
Page 17 OPC UA
OPC UA User Authentication
When the S7-1500’s OPC UA server is parameterized, you can set how a user of the OPC UA
client must legitimize himself if he wants to access the server. There are the following options:
• Guest authentication
• User name and password authentication
Guest Authentication
The user does not have to prove his authorization (anonymous access). The OPC UA server
does not verify the authorization of the client-user.
M O
User Name and Password Authentication
o RU
t inh
The user must prove his authorization (no anonymous access). The OPC UA server verifies
u
o
whether the client-user is authorized to access the server. The user name with the correct
C
a
reir
password is the proof. If this option is to be used, the guest authentication must be deactivated!
e
Currently, a maximum of 21 users can be added!
P
e g o
Dy
Note
The controller‘s OPC UA server currently only supports a binary user management. That means
that every user can access the same data in the controller.
IK-TIAPN – OPC UA
17.9.OPC
OPC Access
UA UA Overview
Access Overview
Target Unrestricted Access Restriction to Certain Restriction to Certain Users

Devices
Secure Channel ▪ Auto Accept Certificates ▪ Auto Accept Certificates ▪ Auto Accept Certificates
active deactivated active
▪ Device certificates added
User Authentication ▪ Guest access active ▪ Guest access active ▪ Guest access deactivated
▪ User / Password active
Impact Every OPC UA client can Only clients whose Every client can establish a
MOcorrect User / Password can

connect to the server and connection but only with the
certificates are in the Trust
access all available data List can establish a
R U
n h o
connection and then access you access all available data
u t i
all available data.
C o
eir a
P e r
eg o
Dy

Page 18 OPC UA
OPC UA Access Overview
The table above gives a fast overview of the impacts of the various security settings in
combination with the user management.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
IK-TIAPN – OPC UA
OPC
17.10. OPC Certificate
UA UA Handling
Certificate Handling
X.509 X.509
offline certificate exchange
M O
R U
o
ou tinh
-
ra C128bit 256bit
Proven technology
r i2-stage concept
eApplication Use Case-specific
Procedures such as TLS P e and User Several Security Policies
(Transport Layer Security)
ego authentication can be operated in parallel
Dy Performance
Unencrypted communication for
maximum performance
Page 19 OPC UA
Certificate Handling
The exchange of the required certificates always takes place before a connection is established.
The required certificates are exported offline and subsequently imported in the necessary
software packages.
X.509 Certificates
An X.509-certificate contains, among other things, the following information:
• Version number of the certificate
• Serial number of the certificate O
M
•
RU
Information about the algorithm that the certificate authority used to sign the certificate.
o
• inh
Name of the certificate (certification) authority
u t
• C o
Beginning and end of the validity of the certificate
i r a
• Name of the program, the
P ereperson or organization for which the certificate was signed by
eofgothe program, the person or organization.
the certificate authority.
•
D y
The public key
In this way an X.509-certificate links an identity (name of a program, a person or an organization)
with the public key of the program, the person or organization.
So that it can be verified whether a certificate was manipulated, certificates are signed. Here,
there are two ways to proceed:
• You contact a certificate (certification) authority (CA) and have your certificate signed. In
this case, the certificate authority verifies the identity and signs the certificate with the
private key of the certificate authority.
• You produce a certificate yourself and sign it.
IK-TIAPN – OPC UA
Certificate
17.11. Management
Certificate Management ofController
of the the Controller
Recommendation: Activate
Global security settings!
Controller certificates
M O
R U
o
ou tinh
ra C
ei
Certificates of
P e r communication partners
eg o
Dy

Page 20 OPC UA
Certificate Manager
When you have activated the OPC UA server and have confirmed the security notes, STEP 7
automatically generates the certificate for the server and stores it in the local certificates directory
of the CPU. You can look at and manage this directory with the local CPU Certificate manager
(export or delete certificates).
In addition to the OPC UA server, there is also a device certificate for the Web server of the
controller. This is required for an https access.
M O
o RU
u t inh
C o
a
P ereir
e g o
Dy
IK-TIAPN – OPC UA
Generating
17.12. Generating UA Server
OPCOPC Device
UA Server Certificates
Device Certificates
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Page 21 OPC UA
Generating OPC UA Server Device Certificates
If the global security settings are used, the controller device certificate is derived from one of the
two CA-Certificates of the TIA Portal project. For the OPC UA server, the first CA certificate is
always used. The second CA certificate is used for the Web server of the controller.
The certificate of the server is transferred from the server to the client while a connection is
established; the client verifies the certificate.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.13. Global Security Settings

Global Security Settings
Activation
17.13.1. Activation
M O
RU
o
outinh
ra C
e i
o Per
eg
Dy
Enables Global
Security Settings

Page 22 OPC UA
The activation (enabling) of global security settings in TIA Portal enables a central management
of the most important security functionalities in the current project.
Data and settings are stored encrypted in the TIA Portal project. This ensures that no unwanted
unauthorized accesses (hacking) to sensitive data occur.
Activation
O
When you activate the global security settings, you get the following warning:
M
RU
All certificate settings transacted to this point will inevitably be lost with the activation! Please
keep this in mind with a subsequent activation!
o
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Administrator
17.13.2. Login
Administrator Login
Creating a Security Administrator

Account
M O
RU
o
ou tinh
ra C
e i
o Per
y egFirst activation of the global
D security settings

Page 23 OPC UA
First-time Activation of the Global Security Settings
The first time the global security settings are used, the "Settings" (user login) must be carried out.
This serves the security and cannot be circumvented.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Contents
17.13.3. Contents
Project-wide global security

settings
Project protection / Password

guidelines
User management
Certificate management M O
R U
o
tinh
Record system events
C ou security events
Record
e i ra
o Per Record data packets
eg
Dy
Page 24 OPC UA
The global security settings in the TIA Portal project have the following contents, that is, they
serve the management of the following properties:
• Users and roles
• Certificate manager
• Log files
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
17.13.4. Certificate
Global SecurityManager
Settings: Certificate Manager
Certificate
17.13.4.1. CertificateAuthority
Authority CACA
CA certificates in TIA Portal

(with private key)
M O
Two CA certificates areU
o Rproject
created
inh
with every TIA Portal
u t
Co
r e ira
P e
First CA certificate =
OPC UA o
Second CA certificate =
egWeb server
CA certificates are
self-signed certificates
VPN groups are also CA
authorities
Dy

Page 25 OPC UA
Certificate Manager
In the global security "Certificate manager", you get an overview of all certificates used in the
project, for example, CA certificates with information about the certificate holder, issuer, validity,
use and presence of a private key. With the appropriate authorization, you can also manage
certificates for the project there.
The Certificate manager in the (global) Security settings is divided into three different subgroups.
These are: Certificate authority (CA), Device certificates as well as Trusted certificates and root
certification authorities.
M O
The Certificate manager is used to manage all certificates associated with the project. It gives a
quick overview and simplifies the global certificate handling.
o RU
Certificate Authority CA u t inh
C o
a
reir
The Certificate authority within the Certificate manager is used to manage the Certified
Authorities as well as the VPN groups. In a TIA Portal project, VPN groups also belong to the
Certified Authorities. P e
e g o
Dy
The CA certificate is a certificate issued by a "Certificate Authority" from which the device
certificates are derived. Certificate authorities can be:
• STEP 7:
if the certificate holder and issuer are the same, then it is a self-signed certificate, that is,
it is issued by STEP 7.
• Higher-level Certificate authority:
These project-external external certificates are imported and stored in the certificate
manager of STEP 7.
Certificates that are produced by one of the two certificate authorities always have a private key
so that the device certificates can be derived from them.
IK-TIAPN – OPC UA
Global Security Settings: Certificate Manager
Device
17.13.4.2. Certificates
Device Certificates
M O Security devices
R U example, SCALANCE S623)
(for
o
tinh CPU TLS
Cou
(Secure OUC)
r e iraCPU OPC UA Server

Pe
y egoCPU Web server
D
Page 26 OPC UA
Device Certificates
Device certificates are either certificates that were generated by their own controller or certificates
that were produced by the communication partner. After the global security settings are activated,
the device certificates of all devices found in the project are managed globally in the project.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Global
Industrial Security
Communication, Settings:
PROFINET with Certificate Manager
Industrial Ethernet in the TIA Portal
Trusted Certificates and Root Certification
Authorities
17.13.4.3. Trusted Certificates and Root Certification Authorities
M O
CA from communication partner
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 27 OPC UA
Trusted Certificates and Root Certification Authorities
CAs or certificates from communication partners, for example, other TIA Portal projects, or, as in
the example above, the OPC UA Client "UaExpert", can be imported here. These are then used
by the OPC UA servers for identity verification.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Aufgabenstellung:
17.14. Task Description:
OPC UA UA
OPC Kommunikation zwischen
Communication Server
between und and
Server Client
Client
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy

Seite 32 OPC UA
Task Description
You are to establish an OPC UA communication between the S7-1513’s OPC UA server and the
OPC UA client UAEXPERT on your computer.
For this, you have to activate and parameterize the S7-1500’s OPC UA server as well as
exchange the certificates of the two communication partners. The export and the import of the
certificates in TIA Portal are done in the Global Security Settings which are activated for this task.
Furthermore, you are to create a data block in the S7-1513 for the OPC UA connection and fill it
with tags/variables. As soon as the connection between the client and the server exists, these
variables will be browsed and accessed via the OPC UA client UAEXPERT. In these exercises,
M O
the Read/Write Access as well as the Subscription will be used as access methods.
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung
17.14.1. 1: OPC
Exercise UA-Server
1: Activating theaktivieren
OPC UA Server
Nach der Aktivierung OPC UA Security-

Einstellungen anpassen!
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 29 OPC UA
Task
You are to activate the OPC UA server and select the appropriate Runtime license. This is
necessary in order to establish a connection from the OPC Client.
What to Do
2. Open the Device view.
3. Activate the OPC UA server.
4. Activate the Runtime license.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 2:
DB Exercise
17.14.2. für die OPC UA Kommunikation
2: Creating anlegen
a DB for the OPC UA Communication
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 30 OPC UA
Task
You are to create a new global data block with the name "OPC_UA". It will be used for the OPC
UA communication. For this, three global variables with different OPC UA properties are created
in this data block. The first variable in this DB is to be Accessible and Writable from an OPC UA
client. The second variable is only to be Accessible and the third variable is to be neither
Accessible nor Writable.
What to Do
1. Generate the global data block "OPC_UA".
O
2. In this data block, create the global variable with the name "BrowsingWrite" as Integer. It is to
M
RU
be "Accessible" and "Writable from HMI/OPC UA".
o
inh
3. Then, create the global variable "BrowsingRead". For it, only activate the property "Accessible
from HMI/OPC UA".
o u t
a C
4. Finally, create the variable "NotVisible". It is to be neither "Accessible" nor "Writable from
HMI/OPC UA".
P e reir
g o
5. Now, download the modifications into the controller.
e
Dy
IK-TIAPN – OPC UA
Übung 3:
UaExpert:
17.14.3. ExerciseS7-1500 hinzufügen
3: UaExpert: Adding an S7-1500
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 31 OPC UA
Task
Now that all settings have been made, you are to establish the connection of the OPC UA client
UaExpert to the S7-1513’s OPC UA server in this exercise. For this, you have to add the PLC’s
OPC UA server to the UaExpert as a new server and then establish a connection.
What to Do
1. Open the UaExpert software.
2. Add the S7-1513’s OPC UA server as a new server in the area "Custom Discovery". This
dialog opens by clicking on the "+" symbol in the taskbar of UaExpert. You can find the
can’t remember them. M O

address data of the controller’s OPC UA server in the OPC UA tab in the PLC Settings if you
o RU
inh
3. Then, navigate to your server and use it without encryption.
o u t
a C
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 4:
Connect,
17.14.4. Browse,
Exercise Read
4: Connect, & Write
Browse, + Subscription
Read & Write + Subscription
M O
R U
o
ou tinh
ra C
Drag&Drop
e i
Per
Subscription
eg o
Dy Browsing
Read & Write

Page 32 OPC UA
Task
You are now to connect the OPC UA UaExpert client to the S7-1513’s OPC UA server. After a
successful connection attempt, you can browse in the address space of the controller. Look for
the global data block "OPC_UA". There, try to read-access as well as write-access the variables
of the data block. Finally, create a Subscription for each variable and monitor the difference
between a Subscription and a Browsing of a variable.
What to Do
1. Establish a connection to the added S7 controller’s OPC UA server.
O
2. Browse through the address space of the controller until you have found the global data block
M
RU
"OPC_UA".
t i n ho
3. Now read-access and write-access respectively, if possible, the found variables.
u project.
4. Monitor the executed changes in your TIAoPortal
C
r e ira for the found variables.
5. In the UaExpert, create a Subscription
6. Open the "OPC_UA" dataP e in your TIA Portal project and compare the behavior of a
block
o
eg to a Read or Write access.
Subscription in contrast
7. Save your TIAD
y
Portal project.
IK-TIAPN – OPC UA
Note
When you connect to the OPC server, the following message appears. This occurs because you
are currently accessing the OPC server without setting up the certificate encryption. Trust the
server certificate from the point of view of the OPC client and accept it for this session.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Exercise
17.14.5. 5: 5:
Exercise Exporting
Exportingthe
theUaExpert ClientCertificate
UAExpert Client Certificate
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 33 OPC UA
Task
You are to export the trusted certificate of the "UaExpert" software for the later import into TIA
Portal. To do so, you must start the software and then export the certificate in the Settings.
The desktop of your computer is to serve as the storage location.
What to Do
1. Start the "UaExpert" software.
2. Open the "Manage Certificates…" dialog window under the menu item "Settings".
3. Check the Client Certificate. The Client Certificate must have the Domain Name "Sitrain" (Host
M O
Domain name) and the IP address 192.168.222.xxx (Internal IP of the VM-ware) in order to
get to the controller.
o RU
u t inh
C o
a
P e reir
e g o
Dy
4. Copy the software certificate onto the desktop of your computer.
IK-TIAPN – OPC UA
Übung
17.14.6. 6: Globale
Exercise Security-Einstellungen
6: Activating aktivieren
the Global Security Settings
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 34 OPC UA
Task
In order to make it easier to manage the certificates, the Certificate manager in the global
Security settings is used. To get to the next steps, you must first activate the Certificate manager
and protect the project, that is, create an Administrator Account. You can activate the Global
Security settings in the "Protection & Security" settings of the controller.
What to Do
1. In the Properties of the controller under "Protection & Security", activate the Global Security
settings.
O
2. Then go into the Security settings, switch to the Settings and protect your project. Here, you
M
RU
automatically set up an Administrator Account.
o
inh
3. Remember your password!
o u t
a C
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Exercise
17.14.7. 7: 7:
Exercise Importing
Importingthe
theUaExpert Client
UAExpert OPC UACertificate
Client Certificate
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 35 OPC UA
Task
In order to register the "UaExpert" OPC UA Client client as a trusted source with the controller,
you must first import the trusted certificate into the global security settings. In the "Certificate
manager" menu item there is a tab called "Trusted certificates and root certification authorities".
Here, the import operation of the UaExpert certificate can be carried out.
What to Do
1. Open the Certificate manager in the Security settings.
2. Switch to the "Trusted certificates and root certification authorities" tab.
MO
3. Import the previously exported certificate of the OPC UA client UaExpert.
U
o R
4. You should then find an entry "UaExpert@YourComputerName" in the opened tab.
ti n h
C o u
i r a
P ere
y ego
D
IK-TIAPN – OPC UA
OPC
17.14.8. UA Server
Exercise Gerätezertifikate
8: Creating erzeugen
OPC UA Server Device Certificates
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Page 36 OPC UA
Task
You are to create a server certificate for the S7-1513. By activating the global Security settings,
the server certificate of the controller is derived from one of the CA authorities of the TIA Portal
project. For the creation of the server certificate of the controller, you are to use the settings
shown in the picture.
What to Do
1. In the Settings of the controller, open the "General" tab.
2. Navigate to the sub-item "Secure Channel" of the OPC UA "Options".
3. Add a new server certificate for the controller.
U MO
o R from which CA authority you
4. Generate the certificate as shown in the picture. Pay attention
t in
derive the certificate and which signature you use h
for the certificate.
5. Subsequently, you should find the newly C u
ogenerated server certificate of the S7-1513 in the
a
eir manager in the Global security settings.
Device certificates of the Certificate
P e r
e g o
Dy
IK-TIAPN – OPC UA
Übung
17.14.9. 9: Security
Exercise Policys
9: Setting der Steuerung
the Security Policies ofeinstellen
the Controller
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 37 OPC UA
Task
For a secure, signed as well as encrypted OPC UA communication between the OPC UA server
and the OPC UA client, the Security policies available on the server must be defined. Only a
communication via the Policy "Basic256Sha256 - Sign & Encrypt" is to be permitted.
What to Do
1. In the "Secure Channel" settings of the OPC UA server of the controller, only permit the Policy
"Basic256Sha256 - Sign & Encrypt".
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 10:
UaExpert
17.14.10. als vertrauenswürdiger
Exercise 10: Adding UaExpertClient hinzufügen
as a Trusted Client
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 38 OPC UA
Task
The OPC UA client "UaExpert" still has to be registered with the controller as a trusted client.
Since you previously imported the client’s certificate, it is now available in the Security settings of
the controller for selection. The option "Automatically accept client certificates during runtime" is
to be deactivated for security reasons.
What to Do
1. Switch to the Security settings of the S7-1513’s OPC UA server.
2. Add the previously imported OPC UA client certificate of UaExpert.
M O
3. Deactivate the option "Automatically accept client certificates during runtime".
4. Now, download the modifications into the controller.
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 11:
TIA Portal
17.14.11. OPC11:
Exercise UATIA
Zertifikat Export
Portal OPC & Import Export & Import
UA Certificate
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 39 OPC UA
Task
After the OPC UA client has been registered with the controller, the CA authority of the TIA Portal
project / the controller must subsequently still be registered with the OPC UA client as a trusted
authority. For this, the first certificate authority is exported respectively as "Certificate - DER
coded" and as "Certificate - Certificate revocation list, DER coded" and then copied into the
appropriate folder in the Installation directory of UaExpert.
What to Do
1. Navigate to the Certificate manager in the global Security settings.
2. Open the Certificate authority (CA) tab.
M O
RU
3. Export the first certificate authority as data type "Certificate - DER coded". Create a new folder
called "Cert" on your desktop as the storage location.
t i n ho
DER coded". This export, as well, isatoC
oudata type "Certificate - Certificate revocation list,
4. Then export the first certificate authority as
go into the new folder.
5. Now export the PLC’s device e r eir as data type "Certificate - DER coded". Storage
certificate
o P
g
location is the folder "Cert"
yefile of the certificate authority into the following directory on your computer:
6. Now copy theD *.der
C:\Users\[Username]\AppData\Roaming\unifiedautomation\uaexpert\PKI\issuers\certs\
7. Copy the *.crl file into the following directory on your computer:
C:\Users\[Username]\AppData\Roaming\unifiedautomation\uaexpert\PKI\issuers\crl\
8. Now copy the *.der file of the device certificate into the following directory on your computer:
C:\Users\[Username]\AppData\Roaming\unifiedautomation\uaexpert\PKI\trusted\certs\
IK-TIAPN – OPC UA
Note
It is also possible to open the directories directly from the UaExpert:
1. Start or use the already opened "UaExpert" software.
2. Open the dialog window "Manage Certificates" under the menu item "Settings"
3. Select the particular certificate and open the directory (see picture)
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 12:
UaExpert:
17.14.12. S7-1500
Exercise hinzufügen
12: UA Expert: Establishing a Connection to the S7-1500
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Page 40 OPC UA
Task
Now that all settings have been made and certificates have been exchanged, you are to establish
the connection of the OPC UA client UaExpert to the S7-1513’s OPC UA server in this exercise.
For this, you have to add the PLC’s OPC UA server to the UaExpert as a new server and then
establish a connection via the Policy "Basic256Sha256 - Sign & Encrypt".
What to Do
1. Open the UaExpert software.
2. Add the S7-1513’s OPC UA server as a new server in the area "Custom Discovery". This
M O
dialog opens by clicking on the "+" symbol in the taskbar of UaExpert. You can find the
address data of the controller’s OPC UA server in the OPC UA tab in the PLC Settings if you
can’t remember them.
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – OPC UA
Übung 13:
Connect,
17.14.13. Browse,
Exercise Read & Write
13: Connect, + Subscription
Browse, Read & Write + Subscription
M O
RU
o
ou tinh
ra C
Drag&Drop
ei
Per
Subscription
ego
Dy Browsing
Read & Write

Page 41 OPC UA
Task
You are now to connect the OPC UA UaExpert client to the S7-1513’s OPC UA server. After a
successful connection attempt, you can browse in the address space of the controller. Look for
the global data block "OPC_UA". There, try to read-access as well as write-access the variables
of the data block. Finally, create a Subscription for each variable and monitor the difference
between a Subscription and a Browsing of a variable.
What to Do
1. Establish a connection to the added S7 controller’s OPC UA server.
O
2. Once again, browse through the address space of the controller until you have found the
M
RU
global data block "OPC_UA".
t i n ho
3. Now read-access and write-access respectively, if possible, the found variables.
u project.
4. Monitor the executed changes in your TIAoPortal
C
r e ira for the found variables.
5. In the UaExpert, create a Subscription
6. Open the "OPC_UA" dataP e in your TIA Portal project and compare the behavior of a
block
o
eg to a Read or Write access.
Subscription in contrast
7. Save your TIAD
y
Portal project.
IK-TIAPN – OPC UA
Contents 18
18. Diagnostics and Commissioning Tools ............................................................. 18-2
18.1. Primary Setup Tool – PST .................................................................................................. 18-3
M O
18.2. U
PRONETA ........................................................................................................................... 18-4
R
o
tinh
18.3. FastConnect ........................................................................................................................ 18-5
18.4. ou
TIA Selection Tool ............................................................................................................... 18-6
C
18.5.
e ira
Web Server .........................................................................................................................
r 18-7
P e
e g o
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Diagnostics and Commissioning Tools

18. Diagnostics and Commissioning Tools

Objectives
... once again get an overview of all diagnostics and commissioning

tools which were addressed in this course
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
IK-TIAPN / Diagnostics and Commissioning Tools Page 2 Siemens AG © 2016
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

18.1.Primary Setup
Primary – PST
ToolTool
Setup – PST
Browse
Download Mac address
IP address
M O
R U
o
ou tinh
ra C
e r ei Device name
o P
eg
Dy
Entry ID: 19440762

Page 3 Diagnostics and Commissioning Tools
PST – Primary Setup Tool
The Primary Setup Tool, short PST, is a software provided by Siemens free of charge. With the
help of the PST, network components, Ethernet CPs, controllers, IO-Devices can be carried out
for SIMATIC NET. As well, address assignments such as the assignment of IP addresses or the
initialization with a PROFINET device name can be carried out for network transitions.
The PST does not require any other software packages or licenses for this functionality. The only
requirement is that these SIMATIC NET devices have a preset ETHERNET (MAC) address and
are accessible online in the network.
If the SIMATIC NET module should have an integrated Web Based Management, this can be
O
called directly in the PST via the button: “Start the browser for configuring INC modules ”.
M
RU
Note
t i n ho
You will find further information on the various u
versions of the Primary Setup Tool on the Service
& Support pages under the Entry ID number: C o19440762. Furthermore, you can also download the
i r a
ere
various versions of the Primary Setup Tool from this Entry ID number.
P
y ego
D

18.2.PRONETA
PRONETA
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
Beitrags-ID: 67460624

PRONETA
SIEMENS PRONETA is a free PC-based software tool which simplifies the commissioning of
PROFINET systems by being able to take over the following tasks:
• Topology Overview (Network Analysis):
PRONETA automatically scans the PROFINET and all connected components and then
displays a topologic overview. This overview can be exported in the form of a device list. It is
possible to “initialize” the components and do other simple configuration tasks as well as
comparing the real configuration with a reference plant.
• IO Test:
O
PRONETA allows for an IO-Test for quickly testing the wiring of a plant and the module
M
o RU
expansion of components. By reading or writing the inputs and outputs, PRONETA ensures
that the distributed I/Os are correctly wired with their sensors and actuators.PRONETA can
t inh
create test profile templates and store test protocols in order to document the test results.
u
C o
All of these tasks can be carried out even before a CPU is integrated in the network. Moreover,
a
Pe reir
since neither other engineering tools nor hardware are required, PRONETA makes the fast and
easy testing of the plant configuration possible at an early point in time.
o
egproduct of Industrial Communication under PROFINET and so can also
D y
PRONETA is an official
be found on the SIEMENS pages:
http://w3.siemens.com/mcms/automation/de/industrielle-
kommunikation/profinet/produktportfolio/proneta/Seiten/proneta.aspx
Note
You will find further information, documentation as well as the download for the PRONETA Tool
on the Service & Support pages under the Entry ID number: 67460624.

18.3.FastConnect
FastConnect
Stripping tool for IE

FC cables
M O
U Special IE FC
hoR cable
o u tin
a C
e r eir
P
IE FC RJ45 plug
o
eg
Dy
FastConnect
FastConnect is a cabling system consisting of cables, plugs and tools for PROFIBUS and
Industrial Ethernet/PROFINET networks, available for copper and glass fiber optic cables for on-
site assembly.
FastConnect can be assembled quickly and easily on-site. As a result, the RJ45 cabling
technology, as an existing standard, is also available as an industry-suitable design.
IE FC RJ45 Plugs
plugs conform to the EN 50173 (RJ45) and ISO/ IEC 11801 standards. MO
RU
IE FC TP Cable
t i n ho
The FastConnect (FC) Twisted Pair (TP) cables
C o u are shielded, radial symmetrically designed
cables with 100 Ohms surge impedance.
e a shield and braided shield make the FC cables
irfoil
r
Pe in an electromagnetic industrial environment. The design also
The combination of twisting the wires,
o
particularly suitable for installation
egTool,
guarantees great stability of the electrical and mechanical data in the installed state.
D y
With the IE FC Stripping it is possible to remove the correct length of outer sheath and
shield of the FC TP cables in one go.
Stripping Tool
With the Industrial Ethernet FastConnect (IE FC) Stripping Tool, the correct length of outer sheath
and shield can be removed from Industrial Ethernet FastConnect cables. The IE FC cable
prepared this way is connected to the plug or the outlet via cutting/clamping contacts. For the IE
FC Stripping Tool there are two knife cassettes with different knife clearances. The IE FC
Stripping Tool is delivered with a yellow knife cassette.
Note
The IE FC Stripping Tool may be used only for stripping SIMATIC NET Industrial Ethernet
FastConnect cables. If the tool is used in any other manner, it can lead to accidents or the
destruction of tool and cable.
18.4.TIATIA
Selection ToolTool
Selection
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
TIA Selection Tool
Both the active as well as the passive components must withstand harsher ambient conditions in
the industrial environment than in the office world. This is noticeable in many ways!
With the TIA Selection Tool you can select, configure and order devices for Totally Integrated
Automation. It is the successor to the SIMATIC Selection Tool and combines already familiar
configurators for automation in one tool. You can start it directly in the Siemens Industry Mall or
download it as a file.
The TIA Selection Tool provides you with wizards for selecting the desired devices and networks.
As well, there are configurators for selecting modules and accessories as well as for checking the
O
correct functioning. The TIA Selection Tool generates a complete order list from your product
M
shopping cart. o RU
selection or product configuration. You can export this directly into the Industry Mall or the CA 01
u t inh
With the TIA Selection Tool, you can select and configure the SIMATIC S7, SIMATIC ET 200,
C o
SIMATIC HMI Panels, SIMATIC IPC, SIMATIC HMI Software and Industrial Communication
a
Pe reir
components. Beyond that, you can create PROFIBUS and PROFINET networks, configure their
topology as well as select associated cables and connectors.
o
g TIA Selection Tool can be found via the following link:
Further information onethe
D y
http://w3.siemens.com/mcms/topics/de/simatic/tia-selection-tool/Seiten/tab.aspx
The TIA Selection Tool can be started directly online via the following link:
https://www.siemens.com/tia-selection-tool/start
SIMATIC NET Selection Tool

The SIMATIC NET Selection Tool is a slimmed down version of the TIA Selection Tool which only
deals with industrial communication and only has Industrial Ethernet components for selection.
More information on the SIMATIC NET Selection Tool can be found on the Service and Support
pages under the following Entry ID: 39134641
The SIMATIC NET Selection Tool can also be started directly online via the following link:
http://www.siemens.de/snst

18.5.Webserver
Web Server
ID: 59193560
Worldwide
diagnostics
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
Diagnostics via the Web Server
Available from everywhere and accessible at all times - this is what customers always expect
from the diagnostics of systems. When the system is connected to the Internet via a router and
taking into account the relevant security guidelines, you are one step closer to meeting these
expectations. We are talking about the integrated web server on the S7-1500 and the S7-1200 as
well as on most other SIMATIC products of the newest generation here.
Via the web server, it is possible to operate diagnostics with only the help of a web browser. No
further software or other aids are required. The different possibilities are explained in more exact
detail in the following sections.
Note
U MO
o Rfor the function manual about the
On the Service & Support pages, you will find the download
tin h
web server of the S7-1500 under the Entry-ID: 59193560.
C o u
i r a
P ere
y ego
D

Contents 19
M O
R U
19. Training and Support ........................................................................................... 19-2
h o
19.1. Any Questions on our Training Courses Offered??
o u tin ............................................................ 19-3
19.2.
r aC
www.siemens.com/sitrain ...................................................................................................
e i 19-4
19.3.
P
Learning path: SIMATIC S7erProgramming based on TIA Portal ........................................ 19-6
19.4. The Industry Online o – the most important innovations.......................................... 19-7
egSupport
y
Dof Navigation ................................................................................................. 19-8
19.5. The Principle
19.6. Complete product information ............................................................................................. 19-9
19.7. mySupport – Overview ...................................................................................................... 19-10
19.8. Support Request ............................................................................................................... 19-11
19.9. Support Request ............................................................................................................... 19-12
19.10. Forum - the communication platform for Siemens Industry products ............................... 19-13
19.10.1. Conferences and Forum management ............................................................................. 19-13
19.10.2. Interactions in the Forum .................................................................................................. 19-15
19.11. Task and Checkpoint ........................................................................................................ 19-17
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy
IK-TIAPN – Training and Support

19.Training
Training
andand Support
Support
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
TIA-PRO1 / Training and Support Page 2 Siemens AG © 2015
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy
IK-TIAPN - Training and Support

Any Questions
19.1. on our
Any Questions onTraining Courses
our Training Offered?
Courses Offered??
We‘ll help you!

... on the Internet:
www.siemens.com/sitrain
or with e-mail:
info@sitrain.com
M O
RU
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
General Information
We‘ll be glad to help you regarding any questions on our training courses offered.
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

19.2. www.siemens.com/sitrain
M O
R U
o
1
ou tinh
ra C
e i
o Per
eg
Dy
2
SITRAIN
TIA-PRO1 The complete
/ Training range
and Support of courses offered
Pagecan
4 be accessed via the following links:
Siemens AG © 2015
www.siemens.de/sitrain or
Course Search
The course search permits the user to find the required courses by applying different search
1 filters such as keyword, target group, etc. The filters can also be combined.
Course Catalog
M O
Mall structure. o RU
The course catalog permits you to find the required course via learning paths or via the Siemens
u t inh
Co
a
P e reir
e g o
Dy

Top Links
Various courses, e.g. SIMATIC S7-1500 solution line, etc., can be reached directly via the top
2 links.
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

Learning
19.3. Path path: SIMATIC S7 Programming based on TIA Portal
Learning
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

The new Industry Online Support – the most

important
19.4. Online Support – the most important innovations
innovations
The Industry
3
2
4
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
The most important functions are always in the same place on all the pages:
The menu bar links to the main areas of the site. You can subscribe and register at any time to
1 benefit from the features the personalized mySupport option offers.
Links to our service offerings are in the center. On the start page, you will find up-to-date
2 information and links, which quickly brings you to your destination in other areas of Online
Support.
M O
Links from the menu bar are repeated at the top of the page: Product Support, Services, Forum
3 and mySupport.
RU
t i n ho
4 C ou cockpit. There, for example, you can see
On every page, you will find your personal mySupport
when the status of your support inquiryachanges.
e r eir
o P
e g
Dy

The New
19.5. The Principle
Principleof
ofNavigation
Navigation
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
TIA-PRO1 Here,
/ Trainingyou will find
and Support information about Page
all the
7 current and discontinued products,Siemens
such as:
AG © 2015
• Frequently Asked Questions (FAQ)

• Manuals and Operating Instructions
• Downloads
• Product Notes (product announcements, discontinuation, etc.)
• Certificates
• Characteristics
• M O
RU
Application Examples
t i n ho
C ou though
You will not only be able to access these articles the product tree, but also through a
i r a
central filter bar. The integration of various search filters will give you access to relevant
information after only a few clicks.
P
has the effect that several filter
re can be combined clearlymoved
The
esteps product tree has been to an equivalent filter. This
and comprehensibly.
y ego
Based on the previewD numbers you can see the expected set of results before using a filter. This
makes finding relevant information considerably easier and more efficient.
For example, you can customize your search by combining the product tree, a search keyword
and a document type in your search.
There will be no hidden search parameters, all the settings and results will be clearly displayed.

Complete
19.6. product
Complete information
product information
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
TIA-PRO1 A powerful
/ Training function
of the Industry Online
and Support Page 8 Support is the direct access to complete product
Siemens AG © 2015
information. You can use it if you are looking for a quick and easy access to all the technical
information about a Siemens Industry product. For example, for comparing products, if you are
expanding your system or replacing individual components, this is how to do it:
In the Product Support area, there is the central navigation bar.
To select a product, simply select the filter “Product.” Enter an order number or a product name
here. You will be supported by a dynamic display of suitable products (list of suggestions).
One more click and the details of the selected product will be displayed – always up to date:
• O
Product life cycle, consisting of milestones with dates (e.g. delivery release, discontinuation of
M
RU
the product, …). You will find out whether the selected product is a current product or whether
the product is already in the discontinuation phase.
o
• u t inh
Successor products for discontinued products and new developments will be suggested. If
Co
there is a successor product, you will get a direct link to the product information of this
a
•
product.
Pe reir
Technical data – clear, compact and complete. You get all the available technical data
e g o
concerning the selected product here – dimensions, operating voltage or the number of
Dy
inputs/outputs,etc.

mySupport
19.7. mySupport – Overview
– Overview
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
mySupport
The mySupport area will always remain your personal workplace; with this feature you can make
the best of your Industry Online Support experience.
The most important thing, if you're already working with mySupport, you can take all your
previous personal data and information you’ve filed away with you to the Industry Online Support.
In this area, you can compile the information that is important for your daily work – we provide
you with the suitable tools. Create your own folder structures and file information such as
bookmarks. There are numerous options, whether you want to file items by project or by
products.
M O
RU
Moreover, you can now add notes, comments and tags (keywords). The system automatically
o
inh
creates a “Tag Cloud” based on your entries so you can access information quickly and easily by
u t
means of your own terms. The operation is consistent throughout mySupport so that you will
o
C
easily find your way around. “Drag &drop” is also possible.
a
P e reir
As soon as you are logged on, the mySupport cockpit is always at your side. It will immediately
show you when the status of a support request changes, or when you receive new personal
e g o
messages. You also have direct access to your personal keywords in the tag cloud, to the entries
Dy
last visited, and you can see which user is online.
Here, just a few highlights:
• The previous MyDocumentationManager is now completely integrated into mySupport under
the name of “mySupport-Documentation.” The function category “Documention” contains all
the functions of the MyDocumentationManager and provides a few innovations, too.
• The Service & Support Newsletter has been completely revamped. An individual messaging
system will more than replace it.

Support
19.8. Request
Support Request
M O
R U
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
Support Request
To create a Support Request, different options are available to you in Online Support:
• You will find the "Support Request" option in the menu on all Online Support pages.
• Alternatively, you can create a new request in mySupport in the "Requests" category.
• Or directly click on the following link:
http://www.siemens.com/automation/support-request
Tips for creating a request:
M O
•
RU
Select your product and use case as accurately as possible; try to avoid selecting "Other". By
t i n ho
doing so, you ensure optimum support by our experts and appropriate suggested solutions.
•
ou step already offers frequent problems and
Did other users have a similar problem? This
C
solutions. Take a look – it will be worth
ira detail as possible. Pictures or explanatory attachments
your while!
• Describe your problem witheas r emuch
o P your problem from all sides and develop solutions. You can
allow our experts to consider
upload multiple y e g
•
D attachments up to 10 MB per file.
Before each sending, verify your personal contact information and the data you have entered.
The final step additionally offers the option to print the summary.
As a logged in user, you can track the status of your requests online. To do so, navigate to "My
requests" in the "Requests" category in mySupport.

Support
19.9. Request
Support Request
M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
SITRAIN
M O
o RU
u t inh
C o
a
P e reir
e g o
Dy

19.10. Forum - the communication platform for Siemens Industry

products
Industry Online Support Internet Portal –
Forum
19.10.1. Conferences and Forum management
1
2
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
TIA-PRO1 On the and
/ Training leftSupport
side,
you will find the so-called
Page 12 conference tree. It allows you to navigate
Siemens through
AG © 2015 the
1
individual discussion areas.
The conference overview is the central discussion area of the Technical Forum. This is where the
2 community meets to discuss technical questions about Siemens Industry products.
In forum management, you will find your personal control center for the Technical Forum. It allows
3 you to manage your specific profile data and filters.
M O
o RU
u t inh
Co
a
P e reir
e g o
Dy

Conference filter
M O
R U
o
ou tinh
ra C
ei
o Per
eg
Dy
SITRAIN
Conference filter
Add conferences to your personal filter of preferred conferences.
This allows you to enable a notification that informs you when new topics are started in these
conferences.
In Quicklinks, the Technical Forum additionally offers an overview page that contains all topics of
your preferred conferences.
Managing profile
Profile management provides interesting information and functions:
• You get an overview of your activities in the Technical Forum.
M O
•
RU
You can view your rank, any special permissions and your ranking progress.
• n ho
You can store a signature and a personal description for your profile in the forum.
t i
• You have direct access to the quick links
C otouget an overview of all topics you have contributed
to.
r e ira
o Pe
yeing the Technical Forum who posts entries that are particularly interesting?
User filter
Have you found aDuser
Then add this user to your list of "preferred users".
This allows you to enable a notification that informs you when the user has posted a new entry.
In Quicklinks, the Technical Forum additionally offers an overview page that contains all topics of
your preferred users.


Interaction
19.10.2. in theinconference
Interactions the Forum view
Creating a new topic in

a conference
M O
RU
o
Status: Topic from ou tinh Rating of
solved conference overview
ra C the topic
ei
o Per
eg
Dy
SITRAIN
MO
o RU
u t inh
C o
a
P e reir
e g o
Dy

Interaction in the forum
Topic from
conference overview
Creating a new entry

for the topic
M O
RU
o
ou tinh
Reacting to an
existing entry
ra C
e i
Per
y go for the
eFeedback
D individual entry
SITRAIN
Creating a new entry
Do you want to create or format a new entry? The entry editor provides all the necessary
functions.
• You can upload and publish in the forum a file with "Add attachment".
• You would like to check before the publication how your entry will actually look? A preview is
available for this purpose.
• You would like to look at the topic again to which you create an entry? Please, you used the
link over the input area (right mouse button > open in a new tab or window)
M O
Posting / replying to an entry
o RU
u t inh
Do you want to participate in an existing discussion with your own entry? Click on "Reply" and
o
post your personal entry to support other users in answering the question.
C
a
reir
• Use the "Reply" link to go to the entry editor and create a reply without quoting the entry.
• P e
If you want to quote the entry, possibly only excerpts of it, use the "Quote" link. The content of
e g o
the quoted entry is then displayed accordingly in the entry editor.
D y
Rating an entry / saying thank you
Do you find an entry particularly interesting? Use the available functions and rate the entry or say
thank you to provide personal feedback. Ratings and thank yours are the rewards our community
members get for the support they provide. When you rate an author or entry, this will be added to
the already existing ratings. The average value of all ratings is displayed.
Aside from feedback to the author of the entry, you also draw other readers' attention to
particularly valuable entries and helpful authors.

19.11. Task and Checkpoint
Task: Software compatibility
Goal
Find out which current version of virus scanners is compatible with your engineering software.
Use all information sources available:
• Readme files in the installation folder
• The compatibility tool of the Industry Online Support
• Entries in the Product support M O
• RU
Entries in the Forum o
• Create a Support Request.
ou tinh
Checkpoint ra C
Checkpoint
ei
o Per
eg
Dy Let‘s think about this:
• Name some reasons for
registration in MySupport.
• What do you think is the best way
to have always the latest version
of the required manuals for your
job with you?
MO
o RU
u t inh
C o
a
P e reir
SITRAIN
TIA-PRO1 / Training and Support
e g o Page 17 Siemens AG © 2015
Dy

M O
RU
o
ou tinh
ra C
e i
o Per
eg
Dy
MO
o RU
u t inh
Co
a
Pe reir
e g o
Dy
Siemens AG
Digital Factory
SITRAIN – Digital Industry Academy
P.O. Box 48 48
90026 Nuremberg, Germany
siemens.com/sitrain

Propriedade Intelectual

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Propriedade Intelectual

Enviado por

Direitos autorais:

Formatos disponíveis

PROPRIEDADE INTELECTUAL

2 Basics of Industrial Ethernet

PROFINET IRT & Isochronous

Location: 16 Open User Communication – OUC

This document was produced for training purposes. 17 OPC UA

SITRAIN course offer on the internet:www.siemens.com/sitrain

Version: V15.01.00 (for TIA Portal V15.1)

IK-TIAPN – Communication in the SIMATIC World

Communication in the SIMATIC World

At the end of the chapter the participant will ...

... get an idea of communication in automation

... be familiar with the different communication media

IK-TIAPN – Communication in the SIMATIC World

Control Level / Cell Level

IK-TIAPN – Communication in the SIMATIC World

PROFINET (IEC 61158/61784)

AS-Interface (IEC62026/EN 50295)

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IO-Controller PN/PN-Coupler IO-Controller

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

SITRAIN © Siemens AG 2018 IK-TIAPN

IK-TIAPN – Communication in the SIMATIC World

IK-TIAPN – Communication in the SIMATIC World

2.27.3. Ethernet SWITCH Basics 3 ................................................................................................. 2-44

IK-TIAPN – Basics of Industrial Ethernet

Basics of Industrial Ethernet

At the end of the chapter the participant will ...

... be familiar with the history of Ethernet

... understand the difference between Ethernet and Industrial Ethernet

y eg…o know the function of a Switch and how it works

IK-TIAPN – Basics of Industrial Ethernet

2.1. In the war

IK-TIAPN – Basics of Industrial Ethernet

IK-TIAPN – Basics of Industrial Ethernet

IK-TIAPN – Basics of Industrial Ethernet

2.3. Horizontal Levels

Field Level / Production Level

IK-TIAPN – Basics of Industrial Ethernet

◼ PROFINET is the innovation of PROFIBUS

◼ The Ethernet technology provides very high

D yeg and line topologies)

◼ A large number of suppliers / manufacturers,

Industrial Ethernet – Designed for Industry

IK-TIAPN – Basics of Industrial Ethernet

Advantages of Ethernet in the Industrial

Uniform network structure

The advantages of Internet technology

IK-TIAPN – Basics of Industrial Ethernet

Industrial Ethernet Office Ethernet

Data ▪Small data packets ▪Large data packets

chemical load o Pe ▪Very little mechanical or chemical load

IK-TIAPN – Basics of Industrial Ethernet