315-4PN33

n For the communication between IO controller and IO device the
ways for the communication are to be defined before. For the
clear specification of the communication ways, these are estab-
lished during the start-up by the IO controller, based on the project
data. Here the configuration takes place by a hardware configura-
tion.
n As soon as the project data were transmitted, the IO controller
switches to system start-up.
n In this state the IO controller may be accessed and its CPU may
be configured via Ethernet by the IO controller by means of the IP
address.
n The PROFINET IO controller is configured by a hardware configu-
ration. After the transmission of the project into the IO controller
with connected IO devices, the IO controller has the whole infor-
mation for the addressing of and the data exchange with the IO
devices.
n During the system start-up of the IO controller the IO devices are
supplied with their configured IP address by means of the DCP
protocol. After PowerON due to the project data the system start-
up of the IO controller is initialized and it runs off independently.
During the system start-up the IO controller establishes a clear
communication relation (CR) and an application relation (AR) to
an IO-Device. Here the cyclic IO data, the acyclic R/W services
and the expected modules/sub modules are specified.
n If the IO controller has received valid project engineering data, a
system start-up with the IO devices is initialized and this is indi-
cated by flashing BF LED. The BF LED is on with configured
PROFINET IO device and bus cable is missing.
n If at least one IO device is not in cyclic data exchange during
start-up, the BF LED blinks.
n If all IO devices are in cyclic data exchange, the BF LED gets off.
This state does not depend on the state of the operating mode
switch of the CPU. After a successful system start-up the system
is ready for communication.
After PowerON respectively a receipt of a new hardware configuration
the configuration data are automatically transferred to the IO con-
troller. Dependent on the CPU state the following behaviour is shown
by the IO controller:
n Behaviour at CPU STOP
–
In the STOP state of the CPU an output telegram is further
cyclically sent but this is designated as "not valid" and the
output data are set to 0.
– The IO controller further receives the input data of the IO
devices and transfers them cyclically to the input area of the
CPU.
n Behaviour at CPU RUN
– The IO controller cyclically reads the output data from the CPU
and transfers these as telegram to the connected IO devices.
– The IO controller receives the input data of the IO devices and
transfers them cyclically to the input area of the CPU.
Online with bus param-
eters without project
IO device configuration
CPU state influences
the IO process data
VIPA System 300SDeployment Ethernet communication - PROFINET
Commissioning and start-up behaviour
HB140 | CPU | 315-4PN33 | GB | 14-43 142