Description The Entry ID 49311792 gives you an overview of the PROFINET IO controllers and IO devices of SIMOTION and SINAMICS that support the PROFINET functions above.
Isochronous real-time communication (IRT) Synchronized transmission procedure for cyclic exchange of IRT data between PROFINET devices. There is a bandwidth reserved for the IRT data in the transmitter clock. The reserved bandwidth guarantees that the IRT data can be transmitted at reserved, clock-synchronized intervals even when the network is otherwise heavily loaded (with TCP/IP communication or additional real-time communication, for example).
Prioritized startup Prioritized startup is the PROFINET functionality for accelerating the startup of an IO device in a PROFINET IO system with RT and IRT communication.
The function cuts the time needed by the appropriately configured IO devices to get back into the cyclic user data communication in the cases below:
After return of power supply
After station return
After IO device enabling
Medium redundancy protocol (MRP) Medium redundancy is a function for ensuring that availability of networks and plants. Redundant transmission paths (ring topology) ensure that when one transmission path fails an alternative path is made available.
PROFIenergy Function for saving power in the process, during idle times, for example, through temporary switch-off of the encoder and load supply in the potential group via standard PROFIenergy commands.
More information about PROFIenergy is available in the manuals ready for downloading in the Entry IDs below.
Shared device IO device that makes its data available to multiple IO controllers.
I device Using the I device function you can use an IO controller also as IO device and thus establish a separate lower-level PROFINET IO subnetwork.
An I device can also be used as a shared device.
Clock-synchronized mode for process data Process data, transmission cycle via PROFINET IO and user program are synchronized with each other to achieve the highest deterministics. The input and output data of distributed IOs in the plant is captured and output simultaneously. The equidistant PROFINET IO cycle is the clock for this.
Which communication services supported by the CPUs with integrated PROFINET interface and by the WinAC RTX via Industrial Ethernet?
Description Software Redundancy (SWR) is a software package for configuring fault-tolerant controllers with standard components. The controller part consists of standard CPUs of the S7-300 and S7-400 series. The redundancy link for synchronizing the redundant CPUs is achieved with standard communication mechanisms like CPs or via an MPI interface. Connection to I/O devices is via two redundant PROFIBUS DP segments to the ET-200M stations with redundant IM 153-2 interface modules. You can also implement Software Redundancy on WinAC RTX as from version 2008.
More information is available in the function manual "Software Redundancy for SIMATIC S7" in Entry ID 1137637.
The following table lists modules that support software redundancy. The lowercase letter x is a wildcard character in the order numbers.
The ET 200M stations must always be configured with active bus modules (6ES7195-7HB00-0XA0 or 6ES7195-7HC00-0XA0), even if the "Hot swapping of I/O modules" function is not possible with S7-300 CPUs.
What are the requirements for using the S7 routing function and which modules can you implement?
Description From STEP 7 V5.0 SP3 HF3 onwards you can reach ST stations online over and beyond subnet limits with the PG/PC, in order, for example, to load user programs or a hardware configuration or in order to execute test and diagnostic functions. You can connect a PG/PC at any place within the network and connect online to any stations which are reached through gateways.
The gateway from a subnet to one or more other subnets is in a SIMATIC station that has interfaces to the subnets concerned.
At least STEP 7 V5.0 SP3 HF3 is installed on the PG/PC for configuration and use of the S7 routing function.
An interface (Industrial Ethernet or PROFIBUS PC CP) is installed in the PG/PC to establish a connection to the gateway. You can use PROFIBUS PC CPs 55xx and 56xx. You can use any NDIS-compatible Ethernet network card (3COM, CP1613, for example) as Industrial Ethernet interface in the PG/PC.
The associated communications modules of the station support the S7 routing function.
The network configuration does not go across project boundaries.
Both the modules and the PG or PC are loaded with the configuration information that contains the latest "knowledge" about the complete network configuration of the project. Technical background All the modules associated with the gateway must receive information about which subnets can be reached over which routes (= routing information).
Note The lists below have been updated with the modules of the hardware catalog of STEP 7 V5.4 SP2. This means that older modules which support the S7 routing function are listed in the tables, but are not necessarily included in the hardware catalog of the latest versions of STEP 7.
SIMATIC S7-CPUs The list below gives an overview of the SIMATIC S7 CPUs that support the S7 Routing function.
Description: IO devices that support the "Replace device without interchangeable medium" function can be replaced without the need for an interchangeable medium (Micro Memory Card, for example) with saved device name being slotted.
The replacement IO device no longer receives the device name from the interchangeable medium, but from the IO controller.
For this, the IO controller and the neighboring PROFINET devices of the replaced IO device must also support the "Replace device without interchangeable medium" function.
The IO controller uses the topology configured in STEP 7 to assign the device name and the neighbor relationships of the IO devices.
The IO controllers below support the "Replace device without interchangeable medium" function:
Configuration Notes: With the extended PROFINET diagnostics it is possible to have functions like the diagnostics and parameterization of integrated Ethernet interfaces (e.g. fiber-optic diagnostics and topology configuration). The PROFINET IO-Devices that support extended PROFINET diagnostics are configured in the Hardware Configuration in STEP 7. They are available in the hardware catalog and have additional ports e.g. interface modules as subslots in Slot 0.
Example: ET200S with and without PROFINET diagnostics
The following IO-Controllers support the extended PROFINET-Diagnostics:
SIMATIC NET PC-Software
SOFTNET PROFINET IO
Embedded and PC-based Automation
WinAC RTX 2008
CPU 414-3 PN/DP
CPU 416-3 PN/DP
CPU 416F-3 PN/DP
CPU 315-2 PN/DP
CPU 317-2 PN/DP
CPU 319-3 PN/DP
CPU 319F-3 PN/DP
Industrial Ethernet CPs
IM151-8 PN/DP CPU
IM151-8F PN/DP CPU
The following IO-Devices can use the extended PROFINET-Diagnostics:
The PROFINET IO devices that support the extended PROFINET diagnostics can only be operated on PROFINET IO controllers that likewise support the extended PROFINET diagnostics.
There is a migration GSDML file for some of the PROFINET IO devices listed above for operating the PROFINET IO device on a PROFINET IO controller that does not support the extended PROFINET diagnostics.
Example: PN/PN coupler
Note: The following applications provide a detailed description, including sample program, of the diagnostics options available in a PROFINET IO system.
"Diagnostic Methods for PROFINET Network Components (PROFINET IO, SNMP, WBM)" in Entry ID: 21566216
"PROFINET IO – Diagnostics Processing in the User Program"
in Entry ID: 24000238
Which SIMATIC S7 modules support the "Direct Data Exchange" function (internode communication)?
Configuration Notes: The following table gives you an overview of the SIMATIC S7 modules that support the "Direct Data Exchange" function (internode communication) as I slave or DP master in the receive and send area.
IM151-7 CPU FO
S7-400 IM modules
IM 467 FO
WinAC RTX 2005 from SP2
x1) The "Direct Data Exchange" function is supported in Send mode from V3.0 and from in Receive mode from V1.1.
When implementing interface modules, support of the "Direct Data Exchange" (internode communication) function depends on the CPU used and not on the interface module itself.