ProSoft Technology PLX82-EIP-PNC User Manual page 105

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