ProSoft Technology MVI56E-MNET/MNETXT - Manual (Page 105)

MVI56E-MNET / MNETXT ♦ ControlLogix Platform Diagnostics and Troubleshooting
Modbus TCP/IP Interface Module User Manual
ProSoft Technology, Inc. Page 105 of 181
April 23, 2014
4.3.3 Client Command Errors
There are several different ways to view Client Command Errors.
 In the MNET.STATUS.ClientStats.CurErr and
MNET.STATUS.ClientStats.LastErr controller tags
 On the Client status data screens in the ProSoft Configuration Builder
Diagnostics
 At a module database location specified by the configuration's MNET Client 0
Command Error Pointer, if the Command Error Pointer is enabled. This
means that the first register refers to command 1 and so on.
Word Offset Description
1 Command 1 Error
2 Command 2 Error
3 Command 3 Error
… ….
… …
For every command that has an error, the module automatically sets the poll
delay parameter to 30 seconds. This instructs the module to wait 30 seconds
until it attempts to issue the command again.
As the commands in the Client Command List are polled and executed, an error
value is maintained in the module for each command. This error list can be
transferred to the processor.
Standard Modbus Exception Code Errors
Code Description
1 Illegal function
2 Illegal data address
3 Illegal data value
4 Failure in associated device
5 Acknowledge
6 Busy; message was rejected
Module Communication Error Codes
Code Description
-2 Timeout while transmitting message
-11 Timeout waiting for response after request (same as -36)
253 Incorrect slave/server address in response
254 Incorrect function code in response
255 Invalid CRC/LRC value in response