Commissioning And Start-Up Behavior - YASKAWA VIPA System MICRO Manual

Table of Contents

Advertisement

Deployment PG/OP communication - PROFINET

Commissioning and start-up behavior

7.8 Commissioning and start-up behavior
Start-up on delivery state
Online with bus parame-
ters without project
IO device configuration
CPU state influences the
IO process data
196
In the delivery state the CPU is overall reset. After power ON the PROFINET part has no
configuration the PROFINET has no configuration. The PROFINET part is passive and
can be found by the device search.
n
For the communication between IO controller and IO device the ways for the commu-
nication are to be defined before. For the clear specification of the communication
ways, these are established during the start-up by the IO controller, based on the
project data. Here the configuration takes place by a hardware configuration.
n
As soon as the project data were transmitted, the IO controller performs a new
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 configuration. After the
transmission of the project into the IO controller, 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 and after trans-
mitting a new hardware configuration, due to the project data the system start-up of
the IO controller is initialized and it runs automatically. During the system start-up the
IO controller establishes a clear communication relation (CR) and an application rela-
tion (AR) to an IO device. Here the cyclic IO data, the acyclic R/W services and the
expected modules/sub modules are specified.
n
The PROFINET IO controller does not have any physical LEDs to show the status.
The status information are stored as virtual LED states. During runtime, you can
determine their status using the SSL partial lists xy19h or xy74h.
nostics status indication via SSLs' page 199
The BF3 LED is on when a PROFINET IO device is configured as "linked" but o
bus cable is connected.
If the IO controller has received a valid configuration with at least one IO device,
the BS2-LED gets on.
With Ethernet interface parameters, which are unsuitable for PROFINET opera-
tion, the BS2-LED flashes at 1Hz.
If the IP address of the IO controller can not be used because e.g. it is duplicated,
the BS2-LED flashes at 0.5Hz.
If at least one IO device is not in cyclic data exchange after the start-up, the BF3
LED blinks.
If all IO devices are in cyclic data exchange, the BF3 LED gets off. After a suc-
cessful 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 controller. Dependent on the CPU state the
following behavior is shown by the IO controller:
n
Behavior at CPU STOP
In the STOP state of the CPU an output telegram is further cyclically sent, but the
contained data are marked as "invalid" and as output data zeros are transmitted.
The IO controller further receives the input data of the IO devices and transfers
them cyclically to the input area of the CPU.
n
Behavior at CPU RUN
The IO controller cyclically reads the output data from the CPU and transfers
these as telegram to the configured IO devices.
The IO controller receives the input data of the IO devices and transfers them
cyclically to the input area of the CPU.
VIPA System MICRO
Ä Chap. 7.9.5 'Diag-
HB400 | CPU | M13-CCF0000 | en | 18-50

Advertisement

Table of Contents
loading

Table of Contents