PLX3x Series ♦ Multi-Protocol Gateways EIP Protocol
User Manual
ProSoft Technology, Inc. Page 73 of 215
January 25, 2018
5.3.3 EIP Error Codes
The gateway stores error codes returned from the command list process in the
command list error memory region. A word is allocated for each command in the
memory area. The error codes are formatted in the word as follows: The least-
significant byte of the word contains the extended status code and the most-
significant byte contains the status code.
Use the error codes returned for each command in the list to determine the
success or failure of the command. If the command fails, use the error code to
determine the cause of failure.
Warning: The gateway-specific error codes (not EtherNet/IP/PCCC compliant) are returned from
the gateway and never returned from an attached EtherNet/IP/PCCC slave device. These are error
codes that are part of the EtherNet/IP/PCCC protocol or are extended codes unique to the PLX3x
gateway. The most common errors for the EtherNet/IP/PCCC protocol are shown below.
Local STS Error Codes
DST node is out of buffer space
Cannot guarantee delivery (Link Layer)
Duplicate token holder detected
Local port is disconnected
Application layer timed out waiting for response
Remote STS Error Codes
Illegal command or format
Host has a problem and will not communicate
Remote node host is missing, disconnected or shut down
Host could not complete function due to hardware fault
Addressing problem or memory protect rungs
Function not allowed due to command protection selection
Processor is in Program mode
Compatibility mode file missing or communication zone problem
Remote node cannot buffer command
Wait ACK (1775-KA buffer full)
Remote node problem due to download