PLX82-EIP-PNC ♦ Communication Gateway
Diagnostics and Troubleshooting
EtherNet/IP™ Server to PROFINET Controller
User Manual
ProSoft Technology, Inc.
Page 105 of 154
July 24, 2018
0xC02E040C
The RPC request was canceled
0xC02E040D
The state of RPC server is invalid for this request
0xC02E040E
The activity has already been initialized
0xC02E040F
The RPC server received in invalid (unexpected) response packet
0xC02E0501
The handle to the RPC server instance is invalid
0xC02E0502
The status of the RPC server is invalid
0xC02E0503
The handle of the RPC Object instance is invalid
0xC02E0600
One of the parameters "uiMaxReg" or "uiMaxReq" is invalid
0xC02E0601
The maximum number of parallel RPC client instances has been reached
0xC02E0602
Creating TLR timer for RPC client instance failed
0xC02E0604
The state of endpoint mapper is invalid for this request
0xC02E0605
The handle to the RPC client instance is invalid
0xC02E0606
The maximum amount of outstanding RPC requests for this RPC client instance has
been reached
0xC02e0607
RPC client instances can only connect to an I/O device if there are no outstanding RPC
requests. Currently, at lease one RPC request is outstanding
0xC02E0608
The RPC client instance you tried to use is going to deregister right now. Aborting your
request!
0xC02E0609
Invalid RPC client instance element "ptElem". Internal RPC error
0xC02E060A
The LONG timeout TLR timer for an outstanding RPC request hit. Used internally by
RPC only
0xC02E060B
Invalid sequence number in RPC message receive by RPC client instance
0xC02E060C
Canceling a running request timeout out. This RPC client is no longer usable
0xC02E060D
The RPC client did not have a packet to return
0xC02E060E
The RPC client received a request with an unexpected flag value.
0xC02E060F
The request was aborted because the RPC client was unbound
0xC02E0610
The maximum resend number was reached by the activity.
Summary of Contents for PLX82-EIP-PNC
Page 4: ......