PLX82-EIP-PNC ♦ Communication Gateway
Diagnostics and Troubleshooting
EtherNet/IP™ Server to PROFINET Controller
User Manual
ProSoft Technology, Inc.
Page 103 of 154
July 24, 2018
9.2.3 PROFINET Device Errors
Error Code
Description
D13 to D31
Unused, set to zero
D12
Inactive module present
D11
Module DiffBlock present
D10
Packet too small
D9
Diagnosis buffer overwritten
D8
Diagnosis buffer overflow
D7
Diagnosis - disappeared
D6
Diagnosis data present for I/O device
D5
IO - Device deactivated
D4
IO - Device parameter fault
D3
IO - Device invalid response
D2
IO - Device configuration fault
D1
IO - Device not ready
D0
IO - Device does not exist
9.2.4 Acyclic Read/Write Communication Status
Status Code
Description
0x00000000
Status OK
0xC00A0012
Insufficient memory for this request
0xC00A0014
This request cannot be served in current CMCTL state
0xC00A0018
Error while sending a packet to another task
0xC00A0040
The CMCTL protocol-machine restored from index invalid
0xC00A0041
The index of CMCTL protocol machine is invalid
0xC00C0030
Too many outstanding RPC-requests for this I/O device
0xC00C0031
Error while sending internal message to another task
0xC00C0032
The handle used for I/O device is wrong
0xC00C0051
The current bus state is OFF and no frames can be sent
0xC02E0100
Generic RPC error code. See Acyclic Read/Write PNIO Remote Procedure Call Status code
for details.
0xC02E0200
Error while sending internal message to another task
0xC02E0201
Creating a TLR-Timer-packet in RPC task failed due to insufficient memory
0xC02E0605
The handle to RPC-client instance is invalid
0xC02E0606
The maximum amount of outstanding RPC-Requests for this RPC-Clients instance is
reached
0xC02E0607
RPC-client instances can only to connect to an IO-Device if there are no outstanding RPC
Requests. There is currently at least one RPC-Request outstanding
0xC02B0024
The message ID of the request is incorrect; out of sequence
Summary of Contents for PLX82-EIP-PNC
Page 4: ......