Standard modbus protocol errors, Module communication error codes, Mnet client specific errors – ProSoft Technology MVI71-MNET User Manual
Page 87: Command list entry errors

Reference MVI71-MNET
♦ PLC Platform
User Manual
Modbus TCP/IP Interface Module
ProSoft Technology, Inc.
Page 87 of 109
June 23, 2009
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, Rejected Message
Module Communication Error Codes
Code Description
-1
CTS modem control line not set before transmit
-2
Timeout while transmitting message
-11
Timeout waiting for response after request
253
Incorrect slave address in response
254
Incorrect function code in response
255
Invalid CRC/LRC value in response
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
Command List Entry Errors
Code Description
-40 Too
few
parameters
-41
Invalid enable code
-42
Internal address > maximum address
-43
Invalid node address (<0 or >255)
-44
Count parameter set to 0
-45
Invalid function code
-46
Invalid swap code
-47
ARP could not resolve MAC from IP (bad IP address, not part of a network, invalid
parameter to ARP routine).
-48
Error during ARP operation: the response to the ARP request did not arrive to the
module after a user-adjustable ARP Timeout.
Note: When the client gets error -47 or -48, it uses the adjustable ARP Timeout parameter in the
configuration file to set an amount of time to wait before trying again to connect to this non-existent
server. This feature allows the client to continue sending commands and polling other existing
servers, while waiting for the non-existent server to appear on the network.