E1...E4 d1 d2 d3 d4 Identi-
fier
000...06
3
AC500
display
<− Display in
Class Comp Dev Mod Ch Err PS501
PLC
browser
Byte 4
Bit 6...7
- Byte 1 Byte 2 Byte 3 Byte 4
Bit 0...5
PNIO
diag-
nosis
block
Class Inter-
face
Device Module Channel Error
identi-
fier
Error message Remedy
1
)
2
)
3
)
CANopen Channel error
4
)
4 - 31 31 12...75 12 Reception SW
FIFO (CAN2.0A)
overrun (Buffer
number 1...64)
5
)
Check
modules
and
parame-
terization
4 - 31 31 112...175 12 Reception SW
FIFO (CAN2.0B)
overrun (Buffer
number 1...64)
5
)
Check
modules
and
parame-
terization
Remarks:
1
)
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.
2
)
With "Device" the following allocation applies: ADR = Hardware address
(e.g. of the CI506-PNIO)
3
)
With "Module" the following allocation applies dependent of the master:
31 = Module itself
4
)
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.
5
)
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
1.7.6.5.9 State LEDs
The LEDs are located at the front of module. There are 4 different groups:
Communication Interface Modules (S500) > PROFINET
2019/04/17 3ADR010121, 13, en_US 1097