Functions
5.3 Shared device
PROFINET with STEP 7
Function Manual, 05/2021, A5E03444486-AL
151
Principle
Access to the submodules of the shared device is then divided up among the individual
IO controllers. Each submodule of the shared device is assigned exclusively to one IO
controller.
Requirement
•
STEP 7 V12 Service Pack 1 or higher
•
IO device supports the shared device function, e.g. interface module IM 155-5 PN ST
•
IO controller supports the shared device function, for example CPU 1516-3 PN/DP as of
firmware version 1.1 or CPU 1215 DC/DC/DC as of firmware version 4.1
Explanatory notes:
•
A CPU that is configured as an I-device can be used as a shared device. For this purpose,
you create a GSD file for the I-device in STEP 7 via "GSD export". You then import the GSD
file into a different project and assign the I-device to the IO controller there. The CPU has
to support the GSD export, for example CPU 1215C DC/DC/DC as of firmware version 4.1.
The maximum number of IO controllers that you can assign to a CPU configured as a
shared I-device is given in the technical specifications in the CPU manuals.
Configuring the access
The IO device must be present in several projects so that the modules or submodules of an IO
device can be assigned to different IO controllers. A separate project is required for each IO
controller.
You use the "Shared device" parameter of the interface module to determine the modules or
submodules to which the IO controller has access:
•
If the local IO controller has access to the configured module, select the name of the IO
controller from the list.
•
If the IO controller from a different project and not the local IO controller is to have access
to the configured module, select the entry "---".
The configuration is consistent regarding access if each module or submodule in exactly one
project is assigned to an IO controller.
Module or submodule is assigned to another IO controller
The paragraph below describes the consequences of the "---" setting of the "Shared device"
parameter from the point of view of the local IO controller.
In this case, the local IO controller does not have access to the module configured in this way.
Specifically, this means:
•
No data exchange with the module or submodule
•
No reception of alarms or diagnostics, which means no display of the diagnostics status in
the online view
•
No parameter assignment of the module or submodule
Summary of Contents for SIMATIC ET 200AL
Page 2: ......
Page 143: ......
Page 218: ......
Page 250: ......
Page 296: ......
Page 337: ......
Page 365: ......
Page 392: ......
Page 419: ......
Page 451: ......
Page 483: ......
Page 597: ......
Page 648: ......
Page 702: ......
Page 739: ......
Page 781: ......
Page 804: ......
Page 828: ......
Page 853: ......
Page 880: ......
Page 906: ......
Page 996: ...Diagnostics ...
Page 1121: ......
Page 1565: ......