ProSoft Technology MVI56E-MCMR - Manual (Page 137)

MVI56E-MCMR ♦ ControlLogix Platform Diagnostics and Troubleshooting
Modbus Communication Module with Reduced Data Block User Manual
ProSoft Technology, Inc. Page 137 of 225
May 13, 2014
5.3 Reading Status Data from the Module
The MVI56E-MCMR module returns a 33-word Status Data block that can be
used to determine the module’s operating status. This data is transferred to the
ControlLogix processor with an MSG instruction. For a complete listing of the
status data object, refer to MVI56
E-MCMR Status Data Definition (page 177).
5.3.1 Required Hardware
You can view configuration information, perform maintenance, and send (upload)
or receive (download) configuration files through the module’s Ethernet port.
ProSoft Technology recommends the following minimum hardware to connect
your computer to the module:

80486 based processor (Pentium preferred)
 1 megabyte of memory
 Use the included Ethernet cable to connect the module to an Ethernet hub or
a 10/100 Base-T Ethernet switch, or directly to the Ethernet port on your PC.
5.3.2 Viewing the Error Status Table
Command execution status and error codes for each individual command are
stored in a Master Command Status/Error List, held in the module’s internal
memory. There are several ways to view this data.

View Command Status, Slave Status and Port Status in the Diagnostics
dialog box in ProSoft Configuration Builder (page 132).
 Configure the Command Error Pointer parameter (<CmdErrPtr>) to copy the
status/error values into the User Database area of module memory.
 Copy this table to a section of the ReadData area, where you can view it in
the <R
EAD D ATA A RRAY > tag array in the ControlLogix controller tag database.
You can use these values for communications status monitoring and
alarming.
o C OMMAND E RROR P OINTER = "MCMR.CONFIG.P ORTX .C MD E RR P TR "
o <R EAD D ATA A RRAY > = "MCMR.DATA.R EAD D ATA [ X ]"
These variables would hold the literal tag names in the sample program or
Add-On Instruction. Use these variables to accommodate future ladder or tag
changes while maintaining backward compatibility.