ProSoft Technology MVI56E-MNETCR User Manual
Page 50

Configuring the MVI56E-MNETCR Module
MVI56E-MNETCR ♦ ControlLogix Platform
User Manual
Modbus TCP/IP Multi Client Enhanced Communications Module for Remote Chassis
Page 50 of 159
ProSoft Technology, Inc.
June 14, 2011
2.1.3 Module
This section of the configuration describes the database setup and module level
parameters. This section provides the module with a unique name, identifies the
method of failure for the communications for the module if the processor is not in
RUN mode, and describes how to initialize the module upon startup.
Error/Status Pointer
-1 to 4955
Starting register location in virtual Modbus database for the error/status table. If a
value of -1 is entered, the error/status data will not be placed in the database. All
other valid values determine the starting location of the data. This data area
includes the module version information and all error/status data.
Read Register Start
0 to 4999
The Read Register Start parameter specifies the start of the Read Data area in
module memory. Data in this area will be transferred from the module to the
processor.
Note: Total user database memory space is limited to the first 5000 registers of module memory,
addresses 0 through 4999. Therefore, the practical limit for this parameter is 4999 minus the value
entered for Read Register Count, so that the Read Data Area does not try to extend above address
4999. Read Data and Write Data Areas must be configured to occupy separate address ranges in
module memory and should not be allowed to overlap.
Read Register Count
0 to 5000
The Read Register Count parameter specifies the size of the Read Data area of
module memory and the number of registers to transfer from this area to the
processor, up to a maximum of 5000 words.
Note: Total Read Register Count and Write Register Count cannot exceed 5000 total registers.
Read Data and Write Data Areas must be configured to occupy separate address ranges in
module memory and should not be allowed to overlap.