Modbus Plus, SY/MAX, and Ethernet TCP/IP Error Codes

Form of the Function Error Code

Function error codes for Modbus Plus and SY/MAX Ethernet transactions appear as Mmss, where:

M is the high code
m is the low code
ss is a subcode

Modbus Plus and SY/MAX Ethernet Network Errors

Hexadecimal error codes for Modbus Plus and SY/MAX Ethernet:

Hex. Error Code	Description
1001	Abort by user
2001	An operation type that is not supported has been specified in the control block
2002	One or more control block parameters were modified while the MSTR element was active (this only applies to operations which require several cycles for completion). Control block parameters my only be modified in inactive MSTR components.
2003	Invalid value in the length field of the control block
2004	Invalid value in the offset field of the control block
2005	Invalid value in the length and offset fields of the control block
2006	Unauthorized data field on slave
2007	Unauthorized network field on slave
2008	Unauthorized network routing path on slave
2009	Routing path equivalent to their own address
200A	Attempt to get more global data words than available
200C	Bad pattern for change address request
200D	Bad address for change address request
200E	The control block is not assigned, or parts of the control block are located outside of the %MW (4x) range.
30ss	Exceptional response by Modbus slave
4001	Inconsistent response by Modbus slave
5001	Inconsistent response by the network
6mss	Routing path error The subfield m shows where the error occurred (a 0 value means local node, 2 means 2nd device in route, etc).

TCP/IP Ethernet Network Errors

Hexadecimal error codes for TCP/IP Ethernet:

Hex. Error Code	Meaning
5004	Interrupted system call
5005	I/O error
5006	No such address
5009	Socket descriptor is invalid
500C	Not enough memory
500D	Permission denied
5011	Entry exists
5016	Argument is invalid
5017	Internal table has run out of space
5020	Connection is broken
5028	Destination address required
5029	Protocol wrong type for socket
502A	Protocol not available
502B	Protocol not supported
502C	Socket type not supported
502D	Operation not supported on a socket
502E	Protocol family not supported
502F	Address family not supported
5030	Address already in use
5031	Cannot assign requested address
5032	Socket operation on a non-socket
5033	Network is unreachable
5034	Network dropped connection on reset
5035	Network caused connection abort
5036	Connection reset by peer
5037	No buffer space available
5038	Socket already connected
5039	Socket not connected
503A	Cannot send after socket shutdown
503B	Too many references, cannot splice
503C	Connection timed out (see note below)
503D	Connection refused
503E	Network down
503F	Text file busy
5040	Too many levels of links
5041	No route to host
5042	Block device required
5043	Host is down
5044	Operation now in progress
5045	Operation already in progress
5046	Operation would block
5047	Function not implemented
5048	Hardware length is invalid
5049	Route specified cannot be found
504A	Collision in select call: these conditions have already been selected by another task
504B	Task ID is invalid
5050	No network resource
5051	Length error
5052	Addressing error
5053	Application error
5054	Client in bad state for request
5055	No remote resource -- may indicate no path to remote device (see note below)
5056	Non-operational TCP connection
5057	Incoherent configuration

NOTE:

Error code 5055 can occur before a 503C error.
No remote device takes precedence over a timeout.

ss Hexadecimal Value in 30ss Error Code

ss hexadecimal value in 30ss error code:

ss Hex. Value	Description
01	Slave does not support requested operation
02	Non-existing slave registers were requested
03	An unauthorized data value was requested
05	Slave has accepted a lengthy program command
06	Function cannot currently be carried out: lengthy command running
07	Slave has rejected lengthy program command

ss Hexadecimal Value in 6mss Error Code

NOTE: Subfield m in error code 6mss is an Index in the routing information that shows where an error has been detected (a 0 value indicates the local node, 2 means the second device in the route, etc.).

The ss subfield in error code 6mss is as follows:

ss Hex. Value	Description
01	No response reception
02	Access to program denied
03	Node out of service and unable to communicate
04	Unusual response received
05	Router-node data path busy
06	Slave out of order
07	Wrong destination address
08	Unauthorized node type in routing path
10	Slave has rejected the command
20	Slave has lost an activated transaction
40	Unexpected master output path received
80	Unexpected response received
F001	Wrong destination node was specified for the MSTR operation