ProSoft Technology MVI56E-MNET/MNETXT - Manual (Page 44)

Configuring the MVI56E-MNET Module MVI56E-MNET / MNETXT ♦ ControlLogix Platform
User Manual Modbus TCP/IP Interface Module
Page 44 of 181 ProSoft Technology, Inc.
April 23, 2014
Pass-Through Mode
0, 1, 2 or 3
This parameter specifies the pass-through mode for write messages received by
the MNET and MBAP server ports.
 If the parameter is set to 0, all write mes
sages will be placed in the module’s
virtual database.
 If a value of 1 is entered, write messages received will be sent to the
processor as unformatted messages.
 If a value of 2 is entered, write messages received will be sent to the
processor as formatted messages.
 If a value of 3 is entered, write messages received will be sent to the
processor with the bytes swapped in a formatted message.
Duplex/Speed Code
0, 1, 2, 3 or 4
This parameter allows you to cause the module to use a specific duplex and
speed setting.
 Value = 1: Half duplex, 10 MB speed
 Value = 2: Full duplex, 10 MB speed
 Value = 3: Half duplex, 100 MB speed
 Value = 4: Full duplex, 100 MB speed
 Value = 0: Auto-negotiate
Auto-negotiate is the default value for backward compatibility. This feature is not
implemented in older software revisions.
2.2.5 MNET Client x
This section defines general configuration for the MNET Client (Master).
Client Error/Status Pointer
1 to 4990
This parameter sets the address in the internal database where the Client
error/status data will be placed. If you want the error/status data to be moved to
the processor and placed into the ReadData array, the value entered should be a
module memory address in the Read Data area. If the value is set to -1, the
error/status data will not be stored in the module's internal database and will not
be transferred to the processor's ReadData array.
Enabling the Error/Status Pointer is optional. The error/status data is routinely
returned as part of the input image, which is continually being transferred from
the module to the processor. For more information, see Normal Data Transfer
Blocks (page 113).