MVI56E-MCM ♦ ControlLogix Platform Reference
Modbus Communication Module User Manual
ProSoft Technology, Inc. Page 179 of 209
The following table shows an example of a Master request and server exception
response.
In this example, the Master addresses a request to server device. The function
code (01) is for a Read Output Status operation. It requests the status of the
output at address 1245 (04A1 hex). Note that only that one output is to be read,
as specified by the number of outputs field (0001).
If the output address is non-existent in the server device, the server will return
the exception response with the exception code shown (02). This specifies an
illegal data address for the Slave.
Modbus Exception Codes
The function code received in the query is not an allowable
action for the Slave. 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 Slave 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.
The data address received in the query is not an allowable
address for the Slave. 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.
A value contained in the query data field is not an allowable
value for Slave. This indicates a fault in the structure of the
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, because the
Modbus protocol is unaware of the significance of any
particular value of any particular register.
An unrecoverable error occurred while the Slave was
attempting to perform the requested action.