ProSoft Technology MVI56E-MNETCR User Manual
Page 104

Reference
MVI56E-MNETCR ♦ ControlLogix Platform
User Manual
Modbus TCP/IP Multi Client Enhanced Communications Module for Remote Chassis
Page 104 of 159
ProSoft Technology, Inc.
June 14, 2011
Word
Description
5
This word contains the TCP service port the message will be interfaced. For
example, to interface with a MBAP device, the word should contain a value of
502. To interface with a MNET device, a value of 2000 should be utilized. Any
value from 0 to 65535 is permitted. A value of 502 will cause a MBAP
formatted message to be generated. All other values will generate an
encapsulated Modbus message.
6
This word contains the Modbus node address for the message. This field
should have a value from 0 to 41.
7
This word contains the internal Modbus address in the module to use with the
command. This word can contain a value from 0 to 4999.
8
This word contains the count parameter that determines the number of digital
points or registers to associate with the command.
9
The parameter specifies the swap type for the data. This function is only valid
for function codes 3 and 4.
10
This word contains the Modbus function code for the command.
11
This word contains the Modbus address in the slave device to be associated
with the command.
12 to 41
Spare
The module will respond to each command block with a read block. The following
table describes the format of this block.
Offset
Description
Length
0
Write Block ID
1
1
0=Fail, 1=Success
1
2 to 40
Spare
39
41
2000 to 2029
1
Word two of the block can be used by the ladder logic to determine if the
command was added to the command queue of the module. The command will
only fail if the command queue for the port is full (16 commands for each queue).