ProSoft Technology MVI56E-MNETC - Manual (Page 106)

Guide to the MVI56E-MNETC User Manual MVI56E-MNETC ♦ ControlLogix Platform
User Manual Modbus TCP/IP Client Enhanced Communication Module
Page 106 of 183 ProSoft Technology, Inc.
February 3, 2013
4.3.3 Client Command Errors
There are several different ways to view Client Command Errors.
 In the MNETC.STATUS.CmdErrorList controller tag array
 On the Client status data screens in the ProSoft Configuration Builder
Diagnostics
 At a module database location specified by the configuration's MNET Client x
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
0 Command 0 Error
1 Command 1 Error
2 Command 2 Error
3 Command 3 Error
… ….
… …
15 Command 15 Error
16 Command 16 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 Last 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