What are the different error codes that can be returned by the Modbus Protocol? | Schneider Electric Egypt and North East Africa

Search FAQs

What are the different error codes that can be returned by the Modbus Protocol?

Issue:
The Magelis HMI is showing an error "The PLC equipment has returned error code 0AH". What does this mean?

Product Line:
Vijeo Designer (all versions), Magelis series, XBTGT, HMIGTO, HMIGTU, HMISTO, HMISTU, HMIGK, iPC

Resolution:
When a Magelis HMI is communicating to a Modbus device over Modbus TCP/IP or Modbus RTU, there are serveral different error codes that the PLC may return in the event of an exception. Please see the table below for a description of each possible error code.

The exception codes as explained in the Modbus specification are:

Exception Code	Name	Meaning
01 (01 hex)	Illegal Function	The function code received in the query is not an allowable action for the server. This may be because the function code is only applicable to newer devices, and was not implemented in the unit selected. It could also indicate that the server is in the wrong state to process a request of this type, for example because it is unconfigured and is being asked to return register values. If a Poll Program Complete command was issued, this code indicates that no program function preceded it.
02 (02 hex)	Illegal Data Address	The data address received in the query is not an allowable address for the server. More specifically, the combination of reference number and transfer length is invalid. For a controller with 100 registers, a request with offset 96 and length 4 would succeed, a request with offset 96 and length 5 will generate exception 02.
03 (03 hex)	Illegal Data Value	A value contained in the query data field is not an allowable value for the server. This indicates a fault in the structure of remainder of a complex request, such as that the implied length is incorrect. It specifically does NOT mean that a data item submitted for storage in a register has a value outside the expectation of the application program, since the MODBUS protocol is unaware of the significance of any particular value of any particular register.
04 (04 hex)	Slave Device Failure	An unrecoverable error occurred while the server was attempting to perform the requested action.
05 (05 hex)	Acknowledge	Specialized use in conjunction with programming commands. The server has accepted the request and is processing it, but a long duration of time will be required to do so. This response is returned to prevent a timeout error from occurring in the client. The client can next issue a Poll Program Complete message to determine if processing is completed.
06 (06 hex)	Slave Device Busy	Specialized use in conjunction with programming commands. The server is engaged in processing a long-duration program command. The client should retransmit the message later when the server is free..
07 (07 hex)	Negative Acknowledge	The server cannot perform the program function received in the query. This code is returned for an unsuccessful programming request using function code 13 or 14 decimal. The client should request diagnostic or error information from the server.
08 (08 hex)	Memory Parity Error	Specialized use in conjunction with function codes 20 and 21 and reference type 6, to indicate that the extended file area failed to pass a consistency check. The server attempted to read extended memory or record file, but detected a parity error in memory. The client can retry the request, but service may be required on the server device.
10 (0A hex)	Gateway Path Unavailable	Specialized use in conjunction with gateways, indicates that the gateway was unable to allocate an internal communication path from the input port to the output port for processing the request. Usually means the gateway is misconfigured or overloaded.
11 (0B hex)	Gateway Target Device Failed to Respond	Specialized use in conjunction with gateways, indicates that no response was obtained from the target device. Usually means that the device is not present on the network.