ProSoft MVI56E-MCMR User Manual
  1. Manuals
  2. Brands
  3. ProSoft Manuals
  4. Control Unit
  5. MVI56E-MCMR
  6. User manual

ProSoft MVI56E-MCMR User Manual

Controllogix platform modbus communication module with reduced data block
Hide thumbs Also See for MVI56E-MCMR:
Table of Contents

Advertisement

Quick Links

Download this manual
MVI56E-MCMR
ControlLogix Platform
Modbus Communication Module with
Reduced Data Block
July 12, 2019
USER MANUAL

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MVI56E-MCMR and is the answer not in the manual?

Questions and answers

Related Manuals for ProSoft MVI56E-MCMR

Summary of Contents for ProSoft MVI56E-MCMR

  • Page 1 MVI56E-MCMR ControlLogix Platform Modbus Communication Module with Reduced Data Block July 12, 2019 USER MANUAL...

  • Page 2: Your Feedback Please

    ® ProSoft Technology Product Documentation In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments. User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided at: www.prosoft-technology.com For professional users in the European Union If you wish to discard electrical and electronic equipment (EEE), please contact your dealer or supplier for further information.

  • Page 3: Mvi (Multi Vendor Interface) Modules

    0°C <= Ta <= 60°C II – Equipment intended for above ground use (not for use in mines). 3 – Category 3 equipment, investigated for normal operation only. G – Equipment protected against explosive gasses. Agency Approvals and Certifications Please visit our website: www.prosoft-technology.com...

  • Page 4: Battery Life Advisory

    Battery Life Advisory Note: Modules manufactured after April 1 , 2011 do not contain a battery. For modules manufactured before that date the following applies: The module uses a rechargeable Lithium Vanadium Pentoxide battery to back up the real-time clock and CMOS settings.

  • Page 5: Table Of Contents

    Configuring the MVI56E-MCMR Module Installing ProSoft Configuration Builder ..............45 Using ProSoft Configuration Builder Software ............46 2.2.1 Upgrading from MVI56-MCMR in ProSoft Configuration Builder ......46 2.2.2 Setting Up the Project ..................... 48 2.2.3 Setting Module Parameters ..................50 Configuration as a Modbus Master .................
  • Page 6 Ethernet LED Indicators ..................122 5.1.1 Scrolling LED Status Indicators ................122 5.1.2 Non-Scrolling LED Status Indicators ..............123 Using the Diagnostics Menu in ProSoft Configuration Builder ......124 Connect to the Module’s Web Page ..............127 5.2.1 5.2.2 The Diagnostics Menu ..................128 5.2.3...
  • Page 7 RS-422 ........................173 6.4.6 RS-485 Application Port(s) ..................173 6.4.7 DB9 to RJ45 Adaptor (Cable 14) ................174 MVI56E-MCMR Status Data Definition ..............175 Modbus Protocol Specification ................177 6.6.1 Commands Supported by the Module ..............177 6.6.2 Read Coil Status (Function Code 01) ..............178 6.6.3...
  • Page 8 MVI56E-MCMR ♦ ControlLogix Platform Modbus Communication Module with Reduced Data Block User Manual ProSoft Technology, Inc. Page 8 of 223...

  • Page 9: Start Here

    MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Start Here In This Chapter  What's New? ..................10  System Requirements ................11  Deployment Checklist ................12  Package Contents ................. 14 ...

  • Page 10: What's New

     ProSoft Discovery Service (PDS): Utility software to find and display a list of MVI56E modules on the network and to temporarily change an IP address to connect with a module's web page.

  • Page 11: System Requirements

    (firmware version 10 or higher), with compatible power supply, and one free slot in the rack for the MVI56E-MCMR module. The module requires 800 mA of available 5 Vdc power and 3 mA of available 24 VDC power. ...

  • Page 12: Deployment Checklist

    ____________ For a Modbus Slave, how many words or bits of data do you need to send to the Master device? The MVI56E-MCMR module can send data to a Modbus Master as 0x coil data, 1x input coil data, 3x input registers, and 4x holding registers. The...
  • Page 13 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual ____________ Parity? ____________ Stop bits? Required for both Master and Slave configurations. ____________ Wiring type to use (RS232, 422 or 485). Configured by jumper settings.

  • Page 14: Package Contents

    Modbus Communication Module with Reduced Data Block Package Contents The following components are included with your MVI56E-MCMR module, and are all required for installation and configuration. Important: Before beginning the installation, please verify that all of the following items are present.

  • Page 15: Setting Jumpers

    Setup pins are not connected, and the module’s firmware cannot be overwritten. The module is shipped with the Setup jumper OFF. Do not jumper the Setup pins together unless you are directed to do so by ProSoft Technical Support (or you want to update the module firmware).

  • Page 16: Installing The Module In The Rack

    After you have checked the placement of the jumpers, insert the MVI56E-MCMR into the ControlLogix chassis. Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules.
  • Page 17 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Align the module with the top and bottom guides, and then slide it into the rack until the module is firmly against the backplane connector.

  • Page 18: Importing The Sample Add-On Instruction

    Using the Sample Program (page 201). Before You Begin Two Add-On Instructions are provided for the MVI56E-MCMR module. The first is required for setting up the module; the second is optional. Copy the files from www.prosoft-technology.com. Save them to a convenient location in your PC, such as Desktop or My Documents.

  • Page 19: Creating A New Rslogix 5000 Project

    MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Creating a New RSLogix 5000 Project Open the F menu, and then choose N Select your ControlLogix controller model. Select the R of the controller.

  • Page 20: Creating The Remote Network

    1.8.1 Creating the Remote Network Note: If you are installing the MVI56E-MCMR module in a remote rack, follow these steps. If you are installing the module in a local rack, follow the steps in Creating the Module - Local Rack (page 25).
  • Page 21 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Name the ENBT/A module, then set the IP Address and Slot location in the local rack with the ControlLogix processor. Click OK. Next, select the 1756-ENBT module that you just created in the Controller Organization pane and click the right mouse button to open a shortcut menu.

  • Page 22: Creating The Module In A Remote Rack

    1.8.2 Creating the Module in a Remote Rack Note: To continue installing the MVI56E-MCMR module in a remote rack, follow these steps. If you are installing the module in a local rack, follow the steps in Creating the Module - Local Rack (page 25).
  • Page 23 Modbus Serial protocol communications. Comm Format Select D -INT (*Very Important*) Slot Enter the slot number in the rack where the MVI56E-MCMR module is to be installed. Input Assembly Instance Input Size Output Assembly Instance Output Size...
  • Page 24 On the C tab, set the RPI value for your project. Fifty (50) ONNECTION milliseconds is usually a good starting value. The MVI56E-MCMR module is now visible in the I/O C section ONFIGURATION Page 24 of 223 ProSoft Technology, Inc.

  • Page 25: Creating The Module In A Local Rack

    1.8.3 Creating the Module in a Local Rack Note: If you are installing the MVI56E-MCMR module in a local rack, follow these steps. If you are installing the module in a remote rack, follow the steps in Creating the Module - Remote Rack (page 20).
  • Page 26 Modbus Serial protocol communications. Comm Format Select D -INT (*Very Important*) Slot Enter the slot number in the rack where the MVI56E-MCMR module is to be installed. Input Assembly Instance Input Size Output Assembly Instance Output Size...
  • Page 27 On the C tab, set the RPI value for your project. Five (5) ONNECTION milliseconds is usually a good starting value. Click OK to confirm. The MVI56E-MCMR module is now visible in the I/O C section ONFIGURATION ProSoft Technology, Inc.

  • Page 28: Importing The Ladder Rung

    Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 1.8.4 Importing the Ladder Rung In the C window, expand the T folder and ONTROLLER RGANIZATION ASKS subfolder until you reach the M folder. ROGRAM...
  • Page 29 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual This action opens the I dialog box, showing the MPORT ONFIGURATION controller tags that will be created. Locate the Remote_ENBT:x:I Tag, where x is the slot number of the module within the local rack.
  • Page 30 Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Click OK to confirm the import. RSLogix will indicate that the import is in progress: When the import is completed, the new rung with the Add-On Instruction will be visible as shown in the following illustration.
  • Page 31 Modbus Communication Module with Reduced Data Block User Manual Adding Multiple Modules (Optional) Important: If your application requires more than one MVI56E-MCMR module in the same project, follow the steps below. In the I/O C folder, click the right mouse button to open a...
  • Page 32 Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Click OK to confirm. The new module is now visible: Expand the T folder, and then expand the M folder. ASKS On the M folder, click the right mouse button to open a shortcut ROGRAM menu.
  • Page 33 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Select the MVI56(E)MCMR_A 1_4.L5X file, and then click MPORT 10 This action opens the I window, which shows the tags MPORT ONFIGURATION that will be imported.
  • Page 34 Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 11 Associate the I/O connection variables to the correct module. The default values are Remote_ENBT:15:I and Remote_ENBT:15:I so these require change. Page 34 of 223...
  • Page 35 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual 12 Change the default tags MCMR and AOI56MCMR to avoid conflict with existing tags. In this procedure, you will append the string "_2" to all tags to be imported as shown in the following illustration.
  • Page 36 Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Configuring the Path for Message Blocks If you used the recommended name for the module (MCMR) to import the first Add-On Instruction, the MSG paths will be associated correctly with the module.

  • Page 37: Adjusting The Input And Output Array Sizes

    The size of each area you configure must match the Add-On instruction controller tag array sizes for the R arrays. RITE The MVI56E-MCMR sample program is configured for 600 registers of and 600 registers of W , which is sufficient for most RITE applications.
  • Page 38 Important: When you change the ReadData and WriteData array sizes in RSLogix, you must also change the Read Register Count and Write Register Count values in ProSoft Configuration Builder (page 53). In ProSoft Configuration Builder, navigate to the B...
  • Page 39 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Save and download the sample program to the processor. To modify the W array, follow the steps in this topic, but substitute RITE for ReadData throughout. Also, make sure that the R RITE arrays do not overlap in the module memory.

  • Page 40: Connecting Your Pc To The Controllogix Processor

    Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Connecting Your PC to the ControlLogix Processor There are several ways to establish communication between your PC and the ControlLogix processor. The following steps show how to establish communication through the serial interface.

  • Page 41: Downloading The Sample Program To The Processor

    MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual 1.10 Downloading the Sample Program to the Processor Note: The key switch on the front of the ControlLogix processor must be in the REM or PROG position.

  • Page 42: Configuring The Rslinx Driver For The Pc Com Port

    Start Here MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 1.10.1 Configuring the RSLinx Driver for the PC COM Port If RSLogix is unable to establish communication with the processor, follow these steps. Open RSLinx.
  • Page 43 MVI56E-MCMR ♦ ControlLogix Platform Start Here Modbus Communication Module with Reduced Data Block User Manual Click to select the driver, and then click C . This action opens the ONFIGURE Configure RS-232 DF1 Devices dialog box. Click the A button. RSLinx will attempt to configure your ONFIGURE serial port to work with the selected driver.
  • Page 44 MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Page 44 of 223 ProSoft Technology, Inc.

  • Page 45: Configuring The Mvi56E-Mcmr Module

    PCB_4.1.0.4.0206. Open a browser window and navigate to http://www.prosoft-technology.com/pcb. Click the download link for ProSoft Configuration Builder, and save the file to your Windows desktop. After the download completes, double-click on the PCB installation file, and follow the instructions that appear on the screen.

  • Page 46: Using Prosoft Configuration Builder Software

    Important: For this procedure, you need to have ProSoft Configuration Builder version 2.2.2 or later installed on your PC. You can download the latest version from www.prosoft-technology.com.
  • Page 47 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual In ProSoft Configuration Builder's tree view, click the icon and right- MODULE click to open a shortcut menu. On the shortcut menu, select C MVI56E-MCMR.

  • Page 48: Setting Up The Project

    Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 2.2.2 Setting Up the Project To begin, start P (PCB). ONFIGURATION UILDER If you have used other Windows configuration tools before, you will find the screen layout familiar.
  • Page 49 Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Your first task is to add the MVI56E-MCMR module to the project. Use the mouse to select D in the tree view, and then click the EFAULT ODULE right mouse button to open a shortcut menu.

  • Page 50: Setting Module Parameters

    2.2.3 Setting Module Parameters Notice that the contents of the information pane and the configuration pane changed when you added the MVI56E-MCMR module to the project. At this time, you may wish to rename the Default Project and Default Location folders in the tree view.
  • Page 51 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Creating Optional Comment Entries Click the [+] to the left of the icon to expand the module comments. Double-click the icon. The Edit - Module Comment dialog box appears.

  • Page 52: Configuration As A Modbus Master

    When the slave responds, or when a timeout has occurred, the Modbus Master will then execute the next command in the list. The following ProSoft Configuration Builder sections contain the Modbus Master configuration. You must configure all three sections.

  • Page 53: Backplane Configuration

    ACKPLANE ONFIGURATION for read and write data within the MVI56E-MCMR module. You will use these data read and write locations in the Internal Address tag within each Master Command (page 57). The following illustration shows the values from the sample program.

  • Page 54: Port Configuration

    Modbus Master device. Port 1 and Port 2 each have their own set of configuration parameters. Note: Any changes made within the configuration file must be downloaded to the MVI56E-MCMR module from ProSoft Configuration Builder. In ProSoft Configuration Builder, expand the MVI56E-MCMR node, and then expand the MCM P 1 node.
  • Page 55 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual The following parameters are displayed when the Type parameter is set to ASTER – M The following table describes the parameters in the E...
  • Page 56 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Parameter Description Float Flag or N Enables or disables use of floating data type Float Start 0 to 32767 Register offset in message for floats...

  • Page 57: Master Command Configuration

    User Manual 2.3.4 Master Command Configuration This topic describes the communications with the Master port and slave devices that are connected to that port. In ProSoft Configuration Builder, expand the MVI56E-MCMR node, and then double-click the M icon. ODBUS OMMANDS...
  • Page 58 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Parameter Description Internal Address 0 to 4999 for Register-level commands 0 to 65535 for Bit-level commands Determines the starting address in the module’s 5000-register database that will be affected by the command.
  • Page 59 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Parameter Description ModBus Function 1, 2, 3, 4, 5, 6, 15, and 16 (when viewed in the .CFG text file) The Modbus Function Code determines what kind of command to send to the slave device.
  • Page 60 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Parameter Description MB Address in Device Specifies the starting Modbus bit or register address where data will begin being read from or written to the slave device. With Modbus, to read an address of 40001, what will actually be transmitted out port is Function Code 03 (one byte) with an address of 00 00 (two bytes).

  • Page 61: Other Modbus Addressing Schemes

    MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual 2.3.5 Other Modbus Addressing Schemes While the above information will handle most devices, some device manufacturers show their Modbus addressing differently. The two most common schemes are six-digit addressing (400101, 301000, and so on) and some devices show their addressing already as an offset address (the address that actually goes out on the Modbus communication line).

  • Page 62: Master Command Examples

    Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block If our device listed above shows its addressing as follows: Then: To read "Switch_Input_Status", you would use Function Code 4 and use a MB Address in Device of 512.
  • Page 63 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Parameter Description Enable = YES The module will send the command every time it goes through the command list. Internal Address = 1000 Begins placing the data read from the slave device into the module at address 1000.
  • Page 64 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Parameter Description Enable = 1 The module will send the command every time it goes through the command list. Internal Address = 1010 Places the data read from the slave device into the module at address 1010.
  • Page 65 16320. Internal Address 16320 of the module memory will be copied into the tag MCMR.DATA.R [20] because 16320 represents a bit address within the memory of the MVI56E-MCMR module (16320 / 16 = register 1020). Reg Count = 160 Reads 160 consecutive bits from the Slave device.
  • Page 66 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Read Input Status 1x (Modbus Function Code 2) Use this command to read Input Coils from a slave device. These are single bit addresses within a Modbus slave device.
  • Page 67 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Preset (Write) Single Coil 0x (Modbus Function Code 5) Used to write a Coil of a slave device, these are single-bit addresses within a Modbus slave device.
  • Page 68 Description Enable = 2 The module will send the command to the slave device only when the data associated within the Internal Address of the MVI56E-MCMR module memory has changed. Internal Address = 320 Writes the data in bit 320 of the module memory to the slave device.
  • Page 69 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Preset (Write) Single Register 4x (Modbus Function Code 6) Used to write to Modbus Holding Registers 4x, this function code will write a single register to the slave device.
  • Page 70 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Preset (Write) Multiple Registers 4x (Modbus Function Code 16) Used to write to Modbus Holding Registers 4x, this function code will write multiple registers to the slave device. The Enable code can be set to a value of 1 for a continuous write, or a value of 2 to write the data to the slave device only when the data associated with the Internal Address field has changed.

  • Page 71: Floating-Point Data Handling (Modbus Master)

    MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual 2.3.7 Floating-Point Data Handling (Modbus Master) In many applications, it is necessary to read or write floating-point data to the slave device. The sample program only provides an INT array for the ReadData and Write Data array (16-bit signed integer value).
  • Page 72 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Along with the Function Code 3, MB Address in Device 256 will read Modbus address 40257 of the slave device. The above command will read 40257 and 40258 of the Modbus Slave #1 and place that data in MCMR.DATA.R...
  • Page 73 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Read Multiple Floating-Point Registers The following table is an example to read Multiple Floating-Point values and device addresses. The table shows 7 consecutive floating-point values (14 Modbus addresses).
  • Page 74 ControlLogix processor, into the MCMR.DATA.W array used RITE by the MVI56E-MCMR module. Below is an example. The length of this COP statement must now be 14. This will COP as many of the MCM_F values required to occupy the MCMR.DATA.W...
  • Page 75 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Read Floats with Single Modbus Register Address (Enron/Daniel Float) Some Modbus slave devices use a single Modbus address to store 32 bits of data.
  • Page 76 Therefore, a count of 1 will send 4 bytes of data, instead of the normal 2 bytes of data to a non Enron/Daniel floating-point register. First, copy the floating-point data from the ControlLogix processor into the MCMR.DATA.W array used by the MVI56E-MCMR module. Below RITE is an example. Page 76 of 223...
  • Page 77 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual The length of this COP statement must now be 14. This will COP as many of the MCM_F values required to occupy the LOAT MCMR.DATA.W...

  • Page 78: Configuration As A Modbus Slave

    This section specifies which of the MVI56E-MCMR module's 5000 registers of memory to send from the ControlLogix processor to the MVI56E-MCMR module (WriteData) and which registers to send from the MVI56E-MCMR module to the ControlLogix processor (ReadData). Page 78 of 223...
  • Page 79 ControlLogix processor in the ReadData tags. Read Register Count Sets how many registers of data the MVI56E-MCMR module will send to the ControlLogix processor. This value should also be a multiple of Write Register Start...
  • Page 80 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Modbus Memory Map Based on the configuration described above, below is the default Modbus address for the module. Each register within the module can be accessed as a 0x bit address, 1x bit address, 3x register address, or 4x register address.
  • Page 81 Bit Input Offset Defines the starting address within the module for 1x Modbus addressing. A value of 0 sets 10001 to 10016 as address 0 in the MVI56E-MCMR module. Word Input Offset Defines the starting address within the module memory for 3x registers.
  • Page 82 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block MVI Address Tag Address 10001 to 10016 WriteData[0] 10017 to 10032 WriteData[1] 10145 to 10160 WriteData[9] 10161 to 10176 30001 WriteData[10] 10177 to 10192...

  • Page 83: Slave Configuration

    MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual 2.4.3 Slave Configuration Value Description 1 = enable port, 0 = disable port Enabled Type 1 = Modbus Slave Port Protocol 0 = Modbus RTU mode, 1 = Modbus ASCII mode Baud Rate Sets the baud rate for the port.

  • Page 84: Floating-Point Data Handling (Modbus Slave)

    2.4.4 Floating-Point Data Handling (Modbus Slave) In most applications, the use of floating-point data requires no special handling. Copy the data to and from the MVI56E-MCMR module with a tag configured as a data type REAL in the ControlLogix processor.
  • Page 85 (does not require 2 Modbus addresses for 1 float value). A Master device requiring this type of addressing, would require that for every count of 1, the MVI56E-MCMR module responds to the request message with 4 bytes (one 32-bit REAL) value.
  • Page 86 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Here is a sample configuration for the module. With the above configuration, this would be the addressing for the module. Module Address Modbus Address...

  • Page 87: Ethernet Configuration

    MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Ethernet Configuration Use this procedure to configure the Ethernet settings for your module. You must assign an IP address, subnet mask and gateway address. After you complete this step, you can connect to the module with an Ethernet cable.

  • Page 88: Connecting Your Pc To The Module's Ethernet Port

    2.6.1 Setting Up a Temporary IP Address Important: ProSoft Configuration Builder locates MVI56E-MCMR modules through UDP broadcast messages. These messages may be blocked by routers or layer 3 switches. In that case, ProSoft Discovery Service will be unable to locate the modules.
  • Page 89 In the Diagnostics window, click the S button. ONNECTION In the Connection Setup dialog box, click the B ) button to ROWSE EVICE open the ProSoft Discovery Service. Select the module, then right-click and choose A SSIGN EMPORARY ProSoft Technology, Inc. Page 89 of 223...
  • Page 90 IP address, see Ethernet Configuration (page 87). Close the ProSoft Discovery Service window. Enter the temporary IP in the Ethernet address field of the Connection Setup dialog box, then click the button to verify that the module is accessible with the ONNECTION current settings.
  • Page 91 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual If the Test Connection is successful, click C . The Diagnostics menu ONNECT will display in the Diagnostics window. ProSoft Technology, Inc. Page 91 of 223...

  • Page 92: Downloading The Project To The Module

    In order for the module to use the settings you configured, you must download (copy) the updated Project file from your PC to the module. In the tree view in ProSoft Configuration Builder, click once to select the MVI56E-MCMR module.
  • Page 93 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual If the Test Connection procedure fails, you will see an error message. To correct the error, follow these steps. Click OK to dismiss the error message.

  • Page 94: Using Cipconnect To Connect To The Module

     The IP addresses and slot numbers of any 1756-ENBT modules in the path  The slot number of the MVI56E-MCMR in the destination ControlLogix chassis (the last ENBTx and chassis in the path). To use CIPconnect, follow these steps.
  • Page 95 CIPconnect Path Editor dialog box. The CIPconnect Path Editor allows you to define the path between the PC and the MVI56E-MCMR module. The first connection from the PC is always a 1756- ENBT (Ethernet/IP) module. ProSoft Technology, Inc.
  • Page 96 Modbus Communication Module with Reduced Data Block Each row corresponds to a physical rack in the CIP path.  If the MVI56E-MCMR module is located in the same rack as the first 1756- ENBT module, select R . 1 and configure the associated parameters.
  • Page 97 Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Example 1: Local Rack Application For this example, the MVI56E-MCMR module is located in the same rack as the 1756-ENBT that is connected to the PC. Rack 1 Slot...
  • Page 98 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Configure the path as shown in the following illustration, and click CIP P to build the path in text format. ONSTRUCT Click OK to close the CIPconnect Path Editor and return to the Download dialog box.
  • Page 99 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Click T to verify that the physical path is available. The ONNECTION following message should be displayed upon success. Click OK to close the Test Connection pop-up and then click D OWNLOAD download the configuration files to the module through the path.
  • Page 100 MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Example 2: Remote Rack Application For this example, the MVI56E-MCMR module is located in a remote rack accessible through ControlNet, as shown in the following illustration. Rack 1 Slot...
  • Page 101 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual In the Download dialog box, click CIP P Configure the path as shown in the following illustration and click C ONSTRUCT CIP P to build the path in text format.
  • Page 102 Configuring the MVI56E-MCMR Module MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Check the new path in the Download dialog box. Click T to verify that the physical path is available. The ONNECTION following message should be displayed upon success.
  • Page 103 MVI56E-MCMR ♦ ControlLogix Platform Configuring the MVI56E-MCMR Module Modbus Communication Module with Reduced Data Block User Manual Click D to download the configuration files to the module through OWNLOAD the path. ProSoft Technology, Inc. Page 103 of 223...

  • Page 104: Using Rswho To Connect To The Module

    For information on setting up the ENBT module, see Using CIPconnect to Connect to the Module (page 94). In the tree view in ProSoft Configuration Builder, right-click the MVI56E- MCMR module. From the shortcut menu, choose D...

  • Page 105: Verify Communication

    In This Chapter  Verify Master Communications ............106  Verify Slave Communications .............. 113 There are several ways to verify that the MVI56E-MCMR module is communicating with the processor and with the Modbus network.  View the LED Status Indicators ...

  • Page 106: Verify Master Communications

    User Manual Modbus Communication Module with Reduced Data Block Verify Master Communications Within the MVI56E-MCMR module, there are several ways to verify that the Modbus Master commands are working correctly. The most common, and detailed method of checking the communications is using the M parameter.
  • Page 107 MVI56E-MCMR ♦ ControlLogix Platform Verify Communication Modbus Communication Module with Reduced Data Block User Manual Offset Content Description Port 2 Command List This field contains the number of requests made from this Requests port to Slave devices on the network.

  • Page 108: Command Error Codes

    Verify Communication MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 3.1.2 Command Error Codes The MVI56E-MCMR module will return an individual error code for every command configured within the M section. The location ODBUS ORT X...
  • Page 109 MVI56E-MCMR ♦ ControlLogix Platform Verify Communication Modbus Communication Module with Reduced Data Block User Manual Based on these values shown above, a good place for the M ODBUS ORT X is address 1500, as shown. OMMAND RROR OINTER With the C...
  • Page 110 Slave device, or the range of the data you are writing does not match the valid range for that device. Refer to the documentation for your Slave device, or contact ProSoft Technical Support for more help with these types of error codes.
  • Page 111 Incorrect function code in response Invalid CRC/LRC value in response "Module Communication Errors" are generated by the MVI56E-MCMR module, and indicate communication errors with the Slave device. Error Code -11 indicates that the module is transmitting a message on the communications wire.

  • Page 112: Mcm Status Data

    Read Data (MCMR.M TART MCMR.M 3.1.3 MCM Status Data Status information can also be obtained from the MVI56E-MCMR module by checking the MCMR.STATUS.P location. Below is a sample. If your system is working correctly, you will see C...

  • Page 113: Verify Slave Communications

    MVI56E-MCMR ♦ ControlLogix Platform Verify Communication Modbus Communication Module with Reduced Data Block User Manual Verify Slave Communications For verifying the communications to the module as a Slave, you can monitor the STATUS tags under the P section. Below is an example.

  • Page 114: Status Data Definition As A Slave

    Verify Communication MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 3.2.1 Status Data Definition as a Slave This section contains a description of the members present in the MCMR.STATUS object. This data is transferred from the module to the processor as part of each read block using the module’s Input Image.

  • Page 115: Ladder Logic

     MVI56E-MCMR User Defined Data Types .......... 116 Ladder logic is required for application of the MVI56E-MCMR module. Tasks that must be handled by the ladder logic are module data transfer, special block handling, and status data receipt. Additionally, a power-up handler may be needed to handle the initialization of the module’s data and to clear any...

  • Page 116: Mvi56E-Mcmr User Defined Data Types

    If additional data transfer is required. 4.1.1 Module Status Data and Variables (MCMRModuleDef) All status and variable data related to the MVI56E-MCMR is stored in a user defined data type. An instance of the data type is required before the module can be used.
  • Page 117 Triggers Status reading. Within the MCMRSTATUS objects are objects containing the status information for each application port. Refer to MVI56E-MCMR Status Data Definition (page 175) for a complete listing of the data stored in this object. This data is acquired from the module using Message instructions (MSGs).
  • Page 118 Ladder Logic MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block MCMRBlockStats The MCMRB object stores the block transfer statistics for the LOCK TATS MVI56E-MCMR module. Name Data Type Description Read Total number of read block transfers...
  • Page 119 MVI56E-MCMR ♦ ControlLogix Platform Ladder Logic Modbus Communication Module with Reduced Data Block User Manual MCMREventCmd When the command bit (MCMR.CONTROL.E ) is set in the VENT RIGGER example ladder logic, the module will build a block 9901 with the command contained in the first command of the MCMR.CONTROL.E...
  • Page 120 MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Page 120 of 223 ProSoft Technology, Inc.

  • Page 121: Diagnostics And Troubleshooting

    LED status indicators on the front of the module provide information on the module’s status.  Status data contained in the module can be viewed in ProSoft Configuration Builder through the Ethernet port.  Status data values are transferred from the module to the processor.

  • Page 122: Ethernet Led Indicators

    Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Ethernet LED Indicators The Ethernet LEDs indicate the module's Ethernet port status as follows: State Description Data Ethernet connected at 10Mbps duplex speed AMBER Solid...

  • Page 123: Non-Scrolling Led Status Indicators

    The battery voltage is low or battery is not present. Allow battery to charge by keeping module plugged into rack for 24 hours. If ERR LED still does not go off, contact ProSoft Technology, as the battery is not a user-serviceable item.

  • Page 124: Using The Diagnostics Menu In Prosoft Configuration Builder

    Modbus Communication Module with Reduced Data Block Using the Diagnostics Menu in ProSoft Configuration Builder Tip: You can have a ProSoft Configuration Builder Diagnostics window open for more than one module at a time. To connect to the module’s Configuration/Debug Ethernet port: In ProSoft Configuration Builder, select the module, and then click the right mouse button to open a shortcut menu.
  • Page 125 MVI56E-MCMR ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus Communication Module with Reduced Data Block User Manual In the Diagnostics window, click the S button to browse for ONNECTION the module’s IP address. In the Connection Setup dialog box, click the T...
  • Page 126 (using the grey cable) or directly between your computer and the module (using the red cable). If you are still not able to establish a connection, contact ProSoft Technology for assistance. Page 126 of 223...

  • Page 127: Connect To The Module's Web Page

    5.2.1 Connect to the Module’s Web Page The module's internal web server provides access to module status, diagnostics, and firmware updates. In ProSoft Discovery Service, select the module to configure, and then click the right mouse button to open a shortcut menu. ’...

  • Page 128: The Diagnostics Menu

    Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 5.2.2 The Diagnostics Menu The Diagnostics menu for this module is arranged as a tree structure, with the Main Menu at the top of the tree, and one or more sub-menus for each menu command.

  • Page 129: Monitoring Database Information

    The status values on this menu correspond with members of the Status Data Definition. 5.2.4 Monitoring Database Information Use the DATABASE menu to view the contents of the MVI56E-MCMR module’s internal database. You can view data in the following formats:...

  • Page 130: Monitoring General Information

    5.2.6 Monitoring Modbus Port Information Use the Modbus Port 1 and Modbus Port 2 menus to view the information for each of the MVI56E-MCMR module’s Modbus application ports. Port Configuration Use the Port Configuration menu to view configuration settings for Modbus Port 1 and Modbus Port 2.

  • Page 131: Data Analyzer

    MVI56E-MCMR ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus Communication Module with Reduced Data Block User Manual Master Command Status Use the Master Command Status menu to view Master command status for Modbus Port 1 and Modbus Port 2. A zero indicates no error.
  • Page 132 Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Select the Communication Port to Analyze You can view incoming and outgoing data for one application port at a time. Choose the application port to analyze.
  • Page 133 (normally Drive C). Now you have everything that shows up on the Diagnostics screen being logged to a file called PCB-Log.txt. You can email this file to ProSoft Technical Support for help with issues on the communications network.
  • Page 134 Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block To begin the display of the communications data, start the Data Analyzer. When the Data Analyzer is running, you should see something like this.

  • Page 135: Reading Status Data From The Module

    User Manual 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 MVI56E-MCMR Status Data Definition (page 175).

  • Page 136: Communication Error Codes

    Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Communication Error Codes During module configuration download, the OK and APP LEDs will cycle through various states. If the OK LED remains RED and the APP LED remains OFF or RED for a long period of time, look at the configuration error words in the configuration request block.
  • Page 137 Note: If the APP, BP ACT and OK LEDs blink at a rate of every one-second, this indicates a serious problem with the module. Call ProSoft Technology Support to arrange for repairs. ProSoft Technology, Inc. Page 137 of 223...

  • Page 138: Clearing A Fault Condition

    Verify correct configuration data is being transferred to the module from the ControlLogix controller. If the module's OK LED does not turn GREEN, verify that the module is inserted completely into the rack. If this does not cure the problem, contact ProSoft Technology Technical Support. Page 138 of 223...

  • Page 139: Troubleshooting

    This indicates a problem with backplane communications. A problem flashes could exist between the processor and any installed I/O module, not just the MVI56E-MCMR. Verify that all modules in the rack are correctly configured in the ladder logic. Module Errors...
  • Page 140 Diagnostics and Troubleshooting MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Page 140 of 223 ProSoft Technology, Inc.

  • Page 141: Reference

    Specifications ..................143  Functional Overview ................146  Cable Connections ................169  MVI56E-MCMR Status Data Definition ..........175  Modbus Protocol Specification ............177  Using the Optional Add-On Instruction Rung Import ......190  Using the Sample Program - RSLogix 5000 Version 15 and earlier ..201 ProSoft Technology, Inc.

  • Page 142: About The Modbus Protocol

    Modbus is a Master/Slave protocol. The Master establishes a connection to the remote Slave. When the connection is established, the Master sends the Modbus commands to the Slave. The MVI56E-MCMR module can work as a Master and as a Slave.

  • Page 143: Specifications

    4-character, scrolling LED display of status and diagnostic data in plain English  ProSoft Discovery Service (PDS) software finds the module on the network and assigns a temporary IP address to facilitate module access  Personality Module (non-volatile CF card) to store network configuration allowing quick in-the-field product replacement by transferring the CF card ProSoft Technology, Inc.

  • Page 144: Hardware Specifications

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.2.2 Hardware Specifications Specification Description Backplane Current Load 800 mA @ 5 VDC 3 mA @ 24 VDC Operating Temperature 0°C to 60°C (32°F to 140°F) Storage Temperature -40°C to 85°C (-40°F to 185°F)

  • Page 145: General Specifications - Modbus Master/Slave

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.2.3 General Specifications - Modbus Master/Slave Communication Baud Rate: 110 to 115K baud parameters Stop Bits: 1 or 2 Data Size: 7 or 8 bits Parity: None, Even, Odd...

  • Page 146: Functional Overview

    Modbus Communication Module with Reduced Data Block Functional Overview 6.3.1 Processor/Module Data Transfers The MVI56E-MCMR module communicates directly over the ControlLogix backplane or across any supported 1756 network bridge (the most common being 1756-CNBx Control Net Bridge and 1756-ENxT EtherNet/IP Bridge). Data...
  • Page 147 User Manual The following illustration shows the data transfer method used to move data between the ControlLogix processor, the MVI56E-MCMR module, and the serial network. This applies only for the scheduled I/O data. As shown in the diagram, all data transferred between the module and the processor over the backplane is through the Input and Output Images.
  • Page 148 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Using Data Blocks Each block transferred between the module and the processor contains block identification codes that define the content or function of the block of data transferred.

  • Page 149: Normal Data Transfer Blocks

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.3.2 Normal Data Transfer Blocks Normal data transfer includes the transferring of data received by, or to be transmitted to, the Modbus drivers and the status data. This data is transferred through read (Input Image) and write (Output Image) blocks.

  • Page 150: Special Function Blocks

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Write Block Write Blocks transfer data from the ControlLogix processor's MCMR.DATA.W controller tag array to the module. The following table RITE describes the structure of the Output Image used to transfer this data.
  • Page 151 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Module Status Block (9250) The General Module Status block contains some basic information about the module itself and diagnostic counters to help monitor activity on each port and across the ControlLogix backplane.
  • Page 152 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Word Offset Content Description Port 1 Requests This field contains the total number of messages sent from the port when it is a Master and the total number or messages received when it is a Slave.
  • Page 153 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Word Offset Content Description Parse Block Count This field contains the total number of Output Image blocks received from the processor that were considered valid by the module firmware (successfully parsed or understood).
  • Page 154 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Event Command Blocks (9901, 9911) The Event Command special function is applicable only when the module's port is configured as a Modbus Master. Event Commands are best used to send commands based on special process conditions, such as emergency shutdowns or device-specific resets.
  • Page 155 Refer to Master Command Configuration (page 57) for a detailed definition of the fields contained in this block. They are the same as those used in constructing the commands in ProSoft Configuration Builder (PCB) in the M ODBUS or M lists.
  • Page 156 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Status Data will be returned to the processor by using a "Get Attribute Single" service type MSG instruction. If you follow the provided sample ladder logic or...
  • Page 157 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Block Response from Module to Processor Word Offset Definitions 9901 or 9911 Event Command ID number 0 = Fail-command not added to the command queue, 1 = Success-command added to the command queue.
  • Page 158 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Command Control will not enable commands for normal, repeated polling if they are not already enabled in the Command List. But Command Control may be used to force commands that are enabled for normal polling to the top of the Command Queue so that they will be executed out of their normal polling sequence, as well as being executed in the normal polling order.
  • Page 159 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The Send Command Control message uses the following parameters in the MSG configuration: Status Data can be returned to the processor using a "Get Attribute Single"...
  • Page 160 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Block Response from Module to Processor Word Offset Definitions 9902 or 9912 Command Control ID Number 0 = Fail-No Special Commands were added to the Command Queue >0 = Success - Indicates the number of command control successfully...
  • Page 161 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Command Error List Blocks (9950, 9951) The Get Command Error List special function is applicable only when the module's port is configured as a Modbus Master. Use block identification codes 9950 for Port 1 or 9951for Port 2 anytime you want to request the Command Error List for the 100 user-configurable commands that may be sent by that port.
  • Page 162 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Block Response from Module to Processor Word Offset Data Field(s) Description Number of This field contains the number of commands to report Commands to in the response message. The value is always 100.
  • Page 163 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Block Response from Module to Processor Word Offset Data Field(s) Description Number of Slaves This field always receives a value of 248 (-8 as a to report signed SINT, 16#F8).
  • Page 164 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Warm Boot Block (9998) The Warm Boot special function is used to restart the module application from within processor logic. This allows the module to be restarted without removing it from the chassis or removing power from the chassis.
  • Page 165 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Cold Boot Block (9999) The Cold Boot special function is used to restart the module application from within processor logic. This allows the module to be restarted without removing it from the chassis or removing power from the chassis.

  • Page 166: Master Driver

    Modbus Communication Module with Reduced Data Block 6.3.4 Master Driver In the Master mode, the MVI56E-MCMR module is responsible for issuing read or write commands to Slave devices on the Modbus network. These commands are user configured in the module via the Master Command List received from the ControlLogix processor or issued directly from the ControlLogix processor (event command control).
  • Page 167 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Master Command List In order to function in the Master Mode, you must define the module’s Master Command List. This list contains up to 100 individual entries, with each entry containing the information required to construct a valid command.

  • Page 168: Slave Driver

    Modbus Communication Module with Reduced Data Block 6.3.5 Slave Driver The Slave Driver Mode allows the MVI56E-MCMR module to respond to data read and write commands issued by a remote Master on the Modbus network. The following flow chart and associated table describe the flow of data into and out of the module.

  • Page 169: Cable Connections

    Modbus Communication Module with Reduced Data Block User Manual Cable Connections The application ports on the MVI56E-MCMR module support RS-232, RS-422, and RS-485 interfaces. Please inspect the module to ensure that the jumpers are set correctly to correspond with the type of interface you are using.

  • Page 170: Ethernet Cable Configuration

    2 Rx- 6 Tx- 6 Rx- 6.4.3 Ethernet Performance Ethernet performance on the MVI56E-MCMR module can affect the operation of the MCMR application ports in the following ways.  Accessing the web interface (refreshing the page, downloading files, and so on) may affect MCMR performance ...

  • Page 171: Application Port(S)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.4.4 RS-232 Application Port(s) When the RS-232 interface is selected, the use of hardware handshaking (control and monitoring of modem signal lines) is user definable. If no hardware handshaking will be used, here are the cable pinouts to connect to the port.
  • Page 172 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block RS-232: Null Modem Connection (Hardware Handshaking) This type of connection is used when the device connected to the module requires hardware handshaking (control and monitoring of modem signal lines).

  • Page 173: Application Port(S)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.4.5 RS-422 The RS-422 interface requires a single four or five wire cable. The Common connection is optional, depending on the RS-422 network devices used. The cable required for this interface is shown below: 6.4.6 RS-485 Application Port(s)

  • Page 174: Db9 To Rj45 Adaptor (Cable 14)

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Note: Terminating resistors are generally not required on the RS-485 network, unless you are experiencing communication problems that can be attributed to signal echoes or reflections. In these cases, installing a 120-ohm terminating resistor between pins 1 and 8 on the module connector end of the RS-485 line may improve communication quality.

  • Page 175: Mvi56E-Mcmr Status Data Definition

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual MVI56E-MCMR Status Data Definition This section contains a description of the members present in the MCMR.STATUS object. This data is transferred from the module to the processor in a message block.
  • Page 176 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Offset Content Description Command Block This field contains the total number of command blocks received Count from the processor. Error Block Count This field contains the total number of block errors recognized by the module.

  • Page 177: Modbus Protocol Specification

    User Manual Modbus Protocol Specification The following pages give additional reference information regarding the Modbus protocol commands supported by the MVI56E-MCMR. 6.6.1 Commands Supported by the Module The format of each command in the list depends on the MODBUS Function Code being executed.

  • Page 178: Read Coil Status (Function Code 01)

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.6.2 Read Coil Status (Function Code 01) Query This function allows the user to obtain the ON/OFF status of logic coils used to control discrete outputs from the addressed Slave only. Broadcast mode is not supported with this function code.

  • Page 179: Read Input Status (Function Code 02)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.6.3 Read Input Status (Function Code 02) Query This function allows the user to obtain the ON/OFF status of discrete inputs in the addressed Slave PC Broadcast mode is not supported with this function code. In...

  • Page 180: Read Holding Registers (Function Code 03)

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.6.4 Read Holding Registers (Function Code 03) Query Read Holding Registers (03) allows the user to obtain the binary contents of holding registers 4xxxx in the addressed Slave. The registers can store the numerical values of associated timers and counters which can be driven to external devices.

  • Page 181: Read Input Registers (Function Code 04)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.6.5 Read Input Registers (Function Code 04) Query Function code 04 obtains the contents of the controller's input registers at addresses 3xxxx. These locations receive their values from devices connected to...

  • Page 182: Force Single Coil (Function Code 05)

    Error Check Field The forcing of a coil via MODBUS function 5 will be accomplished regardless of whether the addressed coil is disabled or not (In ProSoft products, the coil is only affected if the necessary ladder logic is implemented).

  • Page 183: Preset Single Register (Function Code 06)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Coils that are reprogrammed in the controller logic program are not automatically cleared upon power up. Thus, if such a coil is set ON by function Code 5 and (even months later), an output is connected to that coil, the output will be "hot".

  • Page 184: Diagnostics (Function Code 08)

    Sub-function Codes Supported Only Sub-function 00 is supported by the MVI56E-MCMR module. 00 Return Query Data The data passed in the request data field is to be returned (looped back) in the response.

  • Page 185: Force Multiple Coils (Function Code 15)

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The data fields in responses to other kinds of queries could contain error counts or other data requested by the sub-function code. 6.6.9 Force Multiple Coils (Function Code 15)

  • Page 186: Preset Multiple Registers (Function Code 16)

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Response The normal response will be an echo of the Slave address, function code, starting address, and quantity of coils forced. Func Hi Addr Lo Addr...

  • Page 187: Modbus Exception Responses

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.6.11 Modbus Exception Responses When a Modbus Master sends a request to a Slave device, it expects a normal response. One of four possible events can occur from the Master's query: ...
  • Page 188 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block If the output address is non-existent in the server device, the server will return the exception response with the exception code shown (02). This specifies an illegal data address for the Slave.
  • Page 189 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Modbus Exception Codes Code Name Meaning Illegal Function The function code received in the query is not an allowable action for the Slave. This may be because the function code is only applicable to newer devices, and was not implemented in the unit selected.

  • Page 190: Using The Optional Add-On Instruction Rung Import

    Allows the processor to read or write the module IP address, netmask and gateway values. Note: This is an optional feature. You can perform the same task through PCB (ProSoft Configuration Builder). Even if your PC is in a different network group you can still access the module through PCB by setting a temporary IP address.

  • Page 191: Installing The Rung Import With Optional Add-On Instruction

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.7.3 Installing the Rung Import with Optional Add-On Instruction Right-click on an empty rung in the MainRoutine of your existing ladder logic and choose I MPORT Navigate to the folder where you saved MVI56(E)MCMR_Optional_AddOn_Rung_vXXX.L5X and select the file.
  • Page 192 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block In the I window, click OK. MPORT ONFIGURATION Page 192 of 223 ProSoft Technology, Inc.
  • Page 193 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The Optional Add-On instruction will be now visible in the ladder logic. Observe that the procedure has also imported data types and controller tags associated to the Optional Add-On instruction.
  • Page 194 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block You will notice that new tags have been imported: four MESSAGE tags, MVI56EMCMRC and MVI56EMCMRE tags. LOCK THERNET In the Optional Add-On instruction, click the [...] button next to each MSG tag...
  • Page 195 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Select the module to configure the message path. ProSoft Technology, Inc. Page 195 of 223...

  • Page 196: Reading The Ethernet Settings From The Module

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.7.4 Reading the Ethernet Settings from the Module Expand the MVI56MCMRE controller tag and move a value of 1 to THERNET MVI56MCMRE THERNET The bit will be automatically reset and the current Ethernet settings will be copied to MVI56MCMRE controller tag as follows.

  • Page 197: Writing The Ethernet Settings To The Module

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.7.5 Writing the Ethernet Settings to the Module Expand the MVI56EMCMRE controller tag. THERNET Set the new Ethernet configuration in MVI56EMCMRE THERNET ONFIG Move a value of 1 to MVI56MCMRE...
  • Page 198 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block To check the status of the message, refer to the W MSG tag. RITE THERNET Page 198 of 223 ProSoft Technology, Inc.

  • Page 199: Reading The Clock Value From The Module

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.7.6 Reading the Clock Value from the Module Expand the MVI56MCMRC controller tag and move a value of 1 to LOCK MVI56MCMRC LOCK The bit will be automatically reset and the current clock value will be copied to MVI56MCMRC controller tag as follows.

  • Page 200: Writing The Clock Value To The Module

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.7.7 Writing the Clock Value to the Module Expand the MVI56MCMRC controller tag. LOCK Set the new Clock value in MVI56MCMRC LOCK ONFIG Move a value of 1 to MVI56MCMRC...

  • Page 201: Using The Sample Program - Rslogix 5000 Version 15 And Earlier

    Diagnostics and Troubleshooting (page 120, page 128). 6.8.2 Add the Module to the Project Important: The following steps describe how to install and configure the MVI56E-MCMR module with RSLogix 5000 version 15 or older. If you are using RSLogix 5000 version 16, please refer to Sample Add-On Instruction Import Procedure.
  • Page 202 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block This action opens the S dialog box. ELECT ODULE Select 1756-M 1756 M ) from the list, and then click ODULE ENERIC ODULE OK. This action opens the N dialog box.
  • Page 203 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual Click OK to save your module settings. This action opens the M ODULE dialog box. ROPERTIES In the C tab, the Requested Packet Interval (RPI) value represents...

  • Page 204: Copying The User Defined Data Types

    Note: Data types prefixed with an underscore [_] are used in optional routines, and need not be copied unless your application requires them. Refer to MVI56E-MCMR User Defined Data Types for a description of the usage for each data type.

  • Page 205: Add The Ladder Logic

    MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual 6.8.5 Add the Ladder Logic If you are creating your own ladder logic, copy the rungs shown in the following illustration from the sample program to your application.

  • Page 206: Ladder Logic - Rslogix Version 15 And Lower

    Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block 6.8.6 Ladder Logic - RSLogix Version 15 and Lower MSG_BLKS The MSG_BLKS routine passes data between the module and the ControlLogix processor using MSG instructions. Data transferred using these blocks is of low- priority and completely under control of the ladder logic.
  • Page 207 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual After the block is read from the module, the data received should be copied to the module’s status controller tag area. The following illustration shows the ladder logic to accomplish this task.
  • Page 208 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block The next rung passes a block 9901 from the processor to the module: Page 208 of 223 ProSoft Technology, Inc.
  • Page 209 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The following illustrations show the format of the MSG block. The format of the MSG block for this rung is as shown in the previous illustration except it used the MCMRCmds[0] for the source and destination tags.
  • Page 210 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block The next rung performs the functions of a 9902 block: Page 210 of 223 ProSoft Technology, Inc.
  • Page 211 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The following illustrations show the format of the MSG block. ProSoft Technology, Inc. Page 211 of 223...
  • Page 212 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block The next rung requests a set of command list errors: Page 212 of 223 ProSoft Technology, Inc.
  • Page 213 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The following illustration shows the format of the MSG block. ProSoft Technology, Inc. Page 213 of 223...
  • Page 214 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block The data contained in the CmdErrData controller tag determines the set of errors returned. Page 214 of 223 ProSoft Technology, Inc.
  • Page 215 MVI56E-MCMR ♦ ControlLogix Platform Reference Modbus Communication Module with Reduced Data Block User Manual The following illustration shows the format of the MSG block. ProSoft Technology, Inc. Page 215 of 223...
  • Page 216 Reference MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Page 216 of 223 ProSoft Technology, Inc.

  • Page 217: Support, Service & Warranty

    Details about the serial, Ethernet or fieldbus devices interfaced to the module, if any. Note: For technical support calls within the United States, ProSoft’s 24/7 after-hours phone support is available for urgent plant-down issues. Detailed contact information for all our worldwide locations is available on the following page.
  • Page 218 Support, Service & Warranty MVI56E-MCMR ♦ ControlLogix Platform User Manual Modbus Communication Module with Reduced Data Block Asia Pacific Europe / Middle East / Africa Regional Office Regional Office Phone: +60.3.2247.1898 Phone: +33.(0)5.34.36.87.20 asiapc@prosoft-technology.com europe@prosoft-technology.com Languages spoken: Bahasa, Chinese, English,...

  • Page 219: Warranty Information

    Languages spoken: Spanish, English REGIONAL TECH SUPPORT support.la@prosoft-technology.com Warranty Information For complete details regarding ProSoft Technology’s TERMS & CONDITIONS OF SALE, WARRANTY, SUPPORT, SERVICE AND RETURN MATERIAL AUTHORIZATION INSTRUCTIONS, go to www.prosoft-technology.com/legal Documentation is subject to change without notice.
  • Page 220 MVI56E-MCMR ♦ ControlLogix Platform Modbus Communication Module with Reduced Data Block User Manual ProSoft Technology, Inc. Page 220 of 223...
  • Page 221 General Specifications - Modbus Master/Slave • 145 Configuring Module Parameters • 50 Configuring the Data Analyzer • 131 Configuring the MVI56E-MCMR Module • 45 Configuring the Path for Message Blocks • 36 Hardware Specifications • 144 Configuring the RSLinx Driver for the PC COM Port •...
  • Page 222 Monitoring Modbus Port Information • 130, 135 Null Modem Connection (Hardware Handshaking) MVI (Multi Vendor Interface) Modules • 3 • 172 MVI56E-MCMR Status Data Definition • 117, 131, 135, Null Modem Connection (No Hardware Handshaking) • 172 MVI56E-MCMR User Defined Data Types • 116, 149, RS-232 Application Port(s) •...
  • Page 223 Using CIPconnect® to Connect to the Module • 92, 94, 104, 125, 170 Using Data Blocks • 148 Using ProSoft Configuration Builder Software • 46 Using RSWho to Connect to the Module • 92, 104 Using the Diagnostics Menu in ProSoft Configuration Builder •...

Table of Contents