Configuration (see
figure under Config‐
uration)
③ System redundancy
(1 subnet)
④ System redundancy
(2 subnets in a line struc‐
ture)
⑤ System redundancy
+ Media redundancy
(2 subnets in a ring struc‐
ture)
Subnet configura‐
tion
The PROFINET IO sys‐
tem begins and ends at
an IO controller.
An interface module is connected to each of the two
IO controllers.
The PROFINET IO systems can be created in a sub‐
net.
Media redundancy
Possible
Yes: The subnet ring is
closed by the MRP con‐
nection to the same CPU.
Configuring in HW
Config
If a PROFINET IO system is created at each PN-IO connection of the CPU, a
newly inserted interface module is automatically connected to both PROFINET
IO systems of the CPU.
Node name The nodes on the fieldbus (PROFINET IO) must be assigned unique names.
Network connec‐
tions (example):
● Network1:
CPU (0) X5 port 1 +
CPU (1) X5 port 1
● Network1:
CPU (0) X5 port 1
● Network2:
CPU (1) X5 port 1
● Network1:
CPU (0) X5 port 1 +
CPU (0) X5 port 2
● Network2:
CPU (1) X5 port 1 +
CPU (1) X5 port 2
Activating system redundancy type R1 for distributed I/O
The system redundancy type R1 for distributed I/O can be activated through a license key. This
license key must be transferred onto the SEC of the CPU. You can perform the activation
without swapping the SEC.
You can activate system redundancy type R1 for distributed I/O as the upgrade of the system
expansion card of a CPU 410-5H.
You can find information on this in the documentation
Process Control System PCS 7, Service
Support and Diagnostics.
Response to failure
The following applies when a CPU or PROFINET cable fails:
The IO devices continue to be available in the PROFINET IO system.
Maintenance and service
One of the following functions is possible in runtime:
● Connecting and removing IO devices
● Replacing PROFINET cables
● Replacing a CPU
Plant planning
4.8 Redundancy and changes during operation
ET 200SP HA Distributed I/O system
46 System Manual, 08/2019, A5E39261167-AD
To Next Page
Loading...
