3.
Open the properties dialog by double-clicking
‘PN-I-Device’
and enter at
‘device
name’
the previously noted name of the VIPA I-Device.
The configured name must match the name of the PROFINET IO
controller ‘PN-IO’ of the I-Device CPU, which you have noted
before!
Chap. 7.4.3 ‘Configuration as I-Device’ page 188
4.
Configure an input area of the same size for each output area of the I-Device in the
IO controller and vice versa. Here also no gaps may arise. In particular, make sure
that the order of the transfer areas matches that of the I-Device configuration. The
following transfer units are available:
n
Input: 1, 8, 16, 32, 64, 128, 256, 512 byte per slot
n
Output: 1, 8, 16, 32, 64, 128, 256, 512 byte per slot
5.
Save and transfer your project to the CPU.
ð
Your VIPA PROFINET controller is now connected as an I-Device to the higher-
level PROFINET IO controller.
I-Device with S7 routing
S7 routing is not possible with the procedure above. S7 routing is only
possible if the I-Device and the higher-level I/O controller are configured
in the same network. The device names must not be identical. By using
identical names and extending the name of the I-Device with "-x", this is
detected internally and used appropriately for S7 routing.
7.4.5 Error behavior and interrupts
The system shows the following error behavior ...
n
... at gaps in the
‘slot’
configuration:
–
If the configuration of the I-Device contains gaps in the
‘slot’
configuration (i.e.
there are free
‘slots’
before used
‘slots’
), the configuration is rejected and
0xEA64 is returned as a configuration error in the diagnostic buffer.
–
If the configuration of the higher-level IO controller contains gaps in the
‘slot’
con-
figuration (i.e. there are free
‘slots’
before used
‘slots’
), the connection is rejected
with the PN IO Status
ErrorCode1
= 0x40 and
ErrorCode2
= 0x04
(AR_OUT_OF_RESOURCE).
n
... at modules, which differ from the configured:
–
A
ModuleDiffBlock
is generated and the wrong modules are not served.
Error behavior
VIPA System MICRO
Deployment PG/OP communication - PROFINET
Deployment as PROFINET I-Device > Error behavior and interrupts
HB400 | CPU | M13-CCF0000 | en | 18-50
190