Reference
MVI56-MNETCR ♦ ControlLogix Platform
User Manual
Modbus TCP/IP Multi Client Communication Module for Remote Chassis
Page 100 of 127
ProSoft Technology, Inc.
February 14, 2011
5.3.2 Client Command List
In order for the Client to function, the module's Client Command List must be
defined in the
MNET Client x Commands
section of the configuration. This list
contains up to 16 individual entries, with each entry containing the information
required to construct a valid command. This includes the following:
Command enable mode: (
0
) disabled or (
1
) continuous
IP address and service port to connect to on the remote server
Slave Node Address
Command Type - Read or Write up to 100 words per command
Database Source and Destination Register Address - Determines where data
will be placed and/or obtained
Count - Select the number of words to be transferred - 1 to 100
Poll Delay - 1/10
th
seconds
5.3.3 Client Command Errors
You can use the Client Command Error Pointer, which is separately configured
for each Client, to reference the offset register where all command error codes
will be stored. This means that the first register refers to command 1 and so on.
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 list is read in from the configuration file and as the commands are
processed, an error value is maintained in the module for each command. This
error list can be transferred to the processor. The errors generated by the module
are displayed in the following table.
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
