Table of Contents
Advertisement
E1...E4
Class
Byte 4
Bit 6...7
Class
CANopen Channel error
4
4
Remarks:
1
)
2
)
3
)
4
)
5
)
1.7.6.5.9
State LEDs
The LEDs are located at the front of module. There are 4 different groups:
2019/04/17
d1
d2
d3
Comp
Dev
Mod
-
Byte 1
Byte 2
Inter-
Device
Module
face
1
2
3
)
)
)
4
)
-
31
31
-
31
31
In AC500 the following interface identifier applies:
"-" = Diagnosis via bus-specific Function Blocks; 0...4 or 10 = Position of
the Communication Module;14 = I/O bus; 31 = Module itself
The identifier is not contained in the CI506-PNIO diagnosis block.
With "Device" the following allocation applies: ADR = Hardware address
(e.g. of the CI506-PNIO)
With "Module" the following allocation applies dependent of the master:
31 = Module itself
All CANopen master and slave diagnostics are not available as PRO-
FINET alarms; instead they can be read via PROFINET acyclic service.
In AC500 PLC these are available in form of Function Blocks.
CAN2A Buffers 1...64 are mapped to the channel values 12...75, so the
correlation value 11 has to be subtracted from the channel value to get
the correct buffer number.
CAN2B Buffers 1...64 are mapped to the channel values 112...175, so the
correlation value 111 has to be subtracted from the channel value to get
the correct buffer number
3ADR010121, 13, en_US
Communication Interface Modules (S500) > PROFINET
d4
Identi-
AC500
fier
display
000...06
3
Ch
Err
PS501
PLC
browser
Byte 3
Byte 4
PNIO
diag-
Bit 0...5
nosis
block
Channel Error
Error message
identi-
fier
12...75
12
Reception SW
FIFO (CAN2.0A)
overrun (Buffer
number 1...64)
112...175 12
Reception SW
FIFO (CAN2.0B)
overrun (Buffer
number 1...64)
Device Specifications
<− Display in
Remedy
Check
modules
and
parame-
5
)
terization
Check
modules
and
parame-
5
)
terization
1097
Advertisement
Chapters
Table of Contents
