ProSoft Technology 5201-MNET-ASCII - Manual (Page 53)

MNET ♦ ProLinx Gateway Diagnostics and Troubleshooting
Modbus TCP/IP Interface Module Driver Manual
ProSoft Technology, Inc. Page 53 of 78
September 1, 2010
3.3.5 MNET Client Command List Error Data
Each command in the command list for the MNET Client has a reserved word
value for a status/error code. This error data list can be read using the
Debug/Config Port and can be placed in the gateway’s internal database.
The first word in the register location defined contains the status/error code for
the first command in the Client Command List. Each successive word in the
Command Error List is associated with the next command in the Client
Command List. Therefore, the number of valid error values is dependent upon
the number of commands defined. The structure of the data area is displayed
below:
Internal Database Address Description
6010 Command #0 Error Status
6011 Command #1 Error Status
6012 Command #2 Error Status
6013 Command #3 Error Status
6014 Command #4 Error Status
.
.
.
6107 Command #97 Error Status
6108 Command #98 Error Status
6109 Command #99 Error Status
Note that the values in the Command List Error Status tables are initialized to
zero (0) at power-up, cold boot and during warm boot. Refer to the next section
containing Error Codes to interpret the status/error codes present in the data
area.
Standard Modbus Protocol 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
MNET Client Specific Errors
Code Description
-33 Failed to connect to server specified in command
-36 MNET command response timeout
-37 TCP/IP connection ended before session finished