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

ProSoft MVI56E-MNETCR User Manual

Modbus tcp/ip multi-client enhanced communications module for remote chassis
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
MVI56E-MNETCR
Modbus TCP/IP Multi-Client
Enhanced Communications Module
for Remote Chassis
July 12, 2019
USER MANUAL

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for ProSoft MVI56E-MNETCR

Summary of Contents for ProSoft MVI56E-MNETCR

  • Page 1 MVI56E-MNETCR Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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: Important Safety Information

    All phase conductor sizes must be at least 1.3 mm (squared) and all earth ground conductors must be at least 4mm (squared). Agency Approvals and Certifications Please visit our website: www.prosoft-technology.com Label Markings <cULus> E183151 Class I Division 2 Groups A, B, C, and D Temp Code T5 0°C to +60°C...

  • Page 5: Table Of Contents

    Configuring the MVI56E-MNETCR Module Installing ProSoft Configuration Builder ..............39 Using ProSoft Configuration Builder Software ............39 2.2.1 Upgrading from MVI56-MNETCR in ProSoft Configuration Builder ......40 2.2.2 Setting Up the Project ..................... 41 2.2.3 Setting Module Parameters ..................43 2.2.4...
  • Page 6 Non-Scrolling LED Status Indicators ..............87 4.1.4 Clearing a Fault Condition ..................88 4.1.5 Troubleshooting ...................... 88 Using the Diagnostics Menu in ProSoft Configuration Builder ....... 89 4.2.1 Connecting to the Module's Web Page ..............92 4.2.2 The Diagnostics Menu .................... 93 4.2.3...
  • Page 7 MVI56E-MNETCR ♦ ControlLogix Platform Contents Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 5.6.5 Writing the Ethernet Settings to the Module............143 5.6.6 Reading the Clock Value from the Module ............145 5.6.7 Writing the Clock Value to the Module ..............146 Adding the Module to an Existing Project .............
  • Page 8 Contents MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Page 8 of 161 ProSoft Technology, Inc.

  • Page 9: Start Here

    MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Start Here In This Chapter  What's New? ..................10  System Requirements ................11  Package Contents ................. 12  Setting Jumpers ..................13 ...

  • 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

    Rockwell Automation ControlLogix processor (firmware version 10 or higher), with compatible power supply, and one free slot in the rack for the MVI56E-MNETCR module. The module requires 800 mA of available 5 Vdc power  Rockwell Automation RSLogix 5000 programming software...

  • Page 12: Package Contents

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Package Contents The following components are included with your MVI56E-MNETCR 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 13: Setting Jumpers

    "write protected" mode, the Setup pins are not connected, and the module’s firmware cannot be overwritten. Do not jumper the Setup pins together unless you are directed to do so by ProSoft Technical Support. The following illustration shows the MVI56E-MNETCR jumper configuration.

  • Page 14: Installing The Module In The Rack

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Installing the Module in the Rack If you have not already installed and configured your ControlLogix processor and power supply, please do so before installing the MVI56E-MNETCR module. Refer to your Rockwell Automation product documentation for installation instructions.
  • Page 15 MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual With a firm, steady push, snap the module into place. Check that the holding clips on the top and bottom of the module are securely in the locking holes of the rack.

  • Page 16: Importing The Sample Add-On Instruction

    Using the Sample Program (page 150). Before You Begin Two Add-On Instructions are provided for the MVI56E-MNETCR 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 17: Creating A New Rslogix 5000 Project

    MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Creating a New RSLogix 5000 Project Open the F menu, and then choose N Select your ControlLogix controller model. Select R EVISION Enter a name for your controller, such as My_Controller.

  • Page 18: Creating The Remote Network

    1.7.1 Creating the Remote Network Note: If you are installing the MVI56E-MNETCR 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 22).
  • Page 19 MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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 20: Creating The Module - Remote Rack

    1.7.2 Creating the Module - Remote Rack Note: To continue installing the MVI56E-MNETCR module in a remote rack, follow the next steps. If you are installing the module in a local rack, follow the steps in Creating the Module - Local Rack (page 22).
  • Page 21 ODULE FOR EMOTE HASSIS Select D -INT (Very Important) Comm Format Slot Enter the slot number in the rack where the MVI56E-MNETCR module will be installed. Input Assembly Instance Input Size Output Assembly Instance Output Size Configuration Assembly Instance 4 Configuration Size On the Connection tab, set the RPI value for your project.

  • Page 22: Creating The Module - Local Rack

    1.7.3 Creating the Module - Local Rack Note: If you are installing the MVI56E-MNETCR 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 18).
  • Page 23 ODULE FOR EMOTE HASSIS Select D -INT (Very Important) Comm Format Slot Enter the slot number in the rack where the MVI56E-MNETCR module is to be installed. Input Assembly Instance Input Size Output Assembly Instance Output Size Configuration Assembly Instance 4 Configuration Size ProSoft Technology, Inc.
  • Page 24 On the Connection tab, set the RPI value for your project. Five (5) milliseconds is usually a good starting value. Click OK to confirm. The MVI56E-MNETCR module is now visible in the I/O Configuration pane. Page 24 of 161 ProSoft Technology, Inc.

  • Page 25: Importing The Add-On Instruction

    MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 1.7.4 Importing the Add-On Instruction Important: If your processor uses RSLogix 5000 version 15 or earlier, see Using the Sample Program (page 150).
  • Page 26 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Navigate to the location on your PC where you saved (page 16) the Add-On Instruction (for example, My Documents or Desktop). Select the MVI56EMNETCR_A 1_4.L5X file.
  • Page 27 MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual If you are installing the module in a Remote Rack, open the dropdown menus for the Input and Output tags, and select the MNETCR module in the remote rack.
  • Page 28 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis When the import is complete, you will see the new Add-On Instruction rung in the ladder. The procedure has also imported new user-defined data types, controller tags and the Add-On instructions for your project.
  • Page 29 Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Adding Multiple Modules (Optional) Important: If your application requires more than one MVI56E-MNETCR module in the same project, follow the steps below. In the I/O C folder, click the right mouse button to open a...
  • Page 30 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Fill the module properties as follows: Parameter Value Enter a module identification string. Example: MNETCR_2 Name Enter a description for the module. Example: M...
  • Page 31 MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Select an empty rung in the routine, and then click the right mouse button to open a shortcut menu. On the shortcut menu, choose I...
  • Page 32 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis This action opens the Import Configuration window, which shows the tags that will be imported. Page 32 of 161 ProSoft Technology, Inc.
  • Page 33 MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 10 Associate the I/O connection variables to the correct module. The default values are RemoteENBT_Slot6:1:I and RemoteENBT_Slot6:1:O, so these require change. ProSoft Technology, Inc.
  • Page 34 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 11 Change the default tags MNETCR and AOI56MNETCR to avoid conflict with existing tags. In this procedure, you will append the string "_2" as shown in the following illustration.
  • Page 35 Adjusting the Input and Output Array Sizes Note: It is unnecessary to manually edit the ReadData and WriteData user-defined data types in the ladder logic, as these are automatically updated to match the changed array sizes from ProSoft Configuration Builder.
  • Page 36 Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis To modify the WriteData array, follow the above steps, substituting WriteData for ReadData. Save and download the configuration to the module (page 61) and reboot.

  • Page 37: Connecting Your Pc To The Controllogix Processor

    MVI56E-MNETCR ♦ ControlLogix Platform Start Here Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 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 38: Downloading The Sample Program To The Processor

    Start Here MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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 39: Configuring The Mvi56E-Mnetcr Module

    (known working) configurations to new projects. Note: During startup and initialization, the MVI56E-MNETCR module receives its protocol and backplane configuration information from the installed Personality Module (Compact Flash). Use ProSoft Configuration Builder to configure module settings and to download changes to the Personality Module.

  • Page 40: Upgrading From Mvi56-Mnetcr In Prosoft Configuration Builder

    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 41: Setting Up The Project

    MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 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 42 MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Your first task is to add the MVI56E-MNETCR module to the project. Use the mouse to select D in the tree view, and then click the...

  • Page 43: 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-MNETCR module to the project. At this time, you may wish to rename the Default Project and Default Location folders in the tree view.

  • Page 44: Module

    Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 2.2.4 Module This section of the configuration describes the database setup and module-level parameters. Backplane Error/Status Pointer 1 to 4955 This parameter sets the address in the internal database where the backplane error/status data will be placed.
  • Page 45 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Write Register Start 0 to 4999 The Write Register Start parameter specifies the start of the Write Data area in module memory. Data in this area will be transferred in from the processor.

  • Page 46: Mnet Client X

    Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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.
  • Page 47 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Minimum Command Delay 0 to 65535 milliseconds This parameter specifies the number of milliseconds to wait between the initial issuances of a command. This parameter can be used to delay all commands sent to servers to avoid "flooding"...
  • Page 48 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis This parameter is used only if the Float Flag is set to Y . For example, if a value of 7000 is entered, all commands sent with addresses of 47001 (or 407001) and above will be considered as floating-point data commands and 32 bits of data will be sent or received for each count of one in the command.

  • Page 49: Mnet Client X Commands

    The function codes used for each command are those specified in the Modbus protocol. Each command list record has the same format. The first part of the record contains the information relating to the MVI56E-MNETCR communication module, and the second part contains information required to interface to the Modbus TCP/IP server device.
  • Page 50 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Command Entry Formats The following table shows the structure of the configuration data necessary for each of the supported commands. Enable...
  • Page 51 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Enable (0) or Y This field defines whether or not the command is to be executed. Value Description The command is disabled and will not be executed in the normal polling sequence.
  • Page 52 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis  Functions 5 and 6 ignore this field as they apply only to a single data point.  For functions 1, 2, and 15, this parameter sets the number of bits (inputs or coils) to be transferred by the command.
  • Page 53 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Use this parameter to specify the slave address of a remote Modbus Serial device through a Modbus Ethernet to Serial converter.
  • Page 54 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Modbus Function 1, 2, 3, 4, 5, 6, 15, or 16 This parameter specifies the Modbus Function Code to be executed by the command.

  • Page 55: Static Arp Table

    MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Note: If the documentation for a particular Modbus server device lists data addresses in hexadecimal (base16) notation, you will need to convert the hexadecimal value to a decimal value to enter in this parameter.

  • Page 56: Ethernet Configuration

    Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 2.2.8 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 57: Connecting Your Pc To The Module

    ProSoft Discovery Service will be unable to locate the modules. To use ProSoft Configuration Builder, arrange the Ethernet connection so that there is no router/ layer 3 switch between the computer and the module OR reconfigure the router/ layer 3 switch to allow routing of the UDP broadcast messages.
  • Page 58 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Click the right mouse button to open a shortcut menu. On the shortcut menu, choose D IAGNOSTICS In the Diagnostics window, click the S button.
  • Page 59 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 The module’s default IP address is 192.168.0.250. Choose an unused IP within your subnet, and then click OK.
  • Page 60 User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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 61: 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-MNETCR module.
  • Page 62 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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 63: Using Cipconnect To Connect To The Module

    Ethernet using Rockwell Automation’s 1756-ENBT EtherNet/IP ® module. This allows you to configure the MVI56E-MNETCR module and network, upload and download files, and view network and module diagnostics from a PC. RSLinx is not required when you use CIPconnect. All you need are: ...
  • Page 64 1756-ENBT (Ethernet/IP) module. Each row corresponds to a physical rack in the CIP path.  If the MVI56E-MNETCR module is located in the same rack as the first 1756- ENBT module, select R . 1 and configure the associated parameters.
  • Page 65 ONSTRUCT Click OK to confirm the configured path. Example 1: Local Rack Application For this example, the MVI56E-MNETCR module is located in the same rack as the 1756-ENBT that is connected to the PC. MVI56E Module 1756-ENBT...
  • Page 66 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis In the Download dialog box, click CIP P Configure the path as shown in the following illustration, and click CIP P to build the path in text format.
  • Page 67 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 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 68 Click OK to close the Test Connection pop-up and then click D OWNLOAD download the configuration files to the module through the path. Example 2: Remote Rack Application For this example, the MVI56E-MNETCR module is located in a remote rack accessible through ControlNet, as shown in the following illustration. 1756-CNB 1756-ENBT...
  • Page 69 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Rack 1 Slot Module Network Address ControlLogix Processor 1756-CNB Node = 1 1756-ENBT IP=192.168.0.100 Rack 2 Slot Module Network Address 1756-CNB...
  • Page 70 Configuring the MVI56E-MNETCR Module MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Configure the path as shown in the following illustration and click C ONSTRUCT CIP P to build the path in text format.
  • Page 71 MVI56E-MNETCR ♦ ControlLogix Platform Configuring the MVI56E-MNETCR Module Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Click T to verify that the physical path is available. The ONNECTION following message should be displayed upon success. Click D...

  • Page 72: Using Rswho To Connect To The Module

    For information on setting up the ENBT module, see Using CIPconnect to Connect to the Module (page 63). In the tree view in ProSoft Configuration Builder, right-click the MVI56E- MNETCR module. From the shortcut menu, choose D...
  • Page 73 Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Click RSW to display modules on the network. The MVI56E-MNETCR module will automatically be identified on the network. Select the module, and then click OK. In the Download dialog box, click D OWNLOAD ProSoft Technology, Inc.
  • Page 74 MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Page 74 of 161 ProSoft Technology, Inc.

  • Page 75: Ladder Logic

    MVI56E-MNETCR ♦ ControlLogix Platform Ladder Logic Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Ladder Logic In This Chapter  Controller Tags ..................76  User-Defined Data Types (UDTs) ............77  Using Controller Tags ................78 ...

  • Page 76: Controller Tags

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Controller Tags Data related to the MVI56E-MNETCR is stored in the ladder logic in variables called controller tags. Individual controller tags can be grouped into collections of controller tags called controller tag structures. A controller tag structure can contain any combination of: ...

  • Page 77: User-Defined Data Types (Udts)

    MVI56E-MNETCR ♦ ControlLogix Platform Ladder Logic Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Notice that the Data Type column displays the data types used to declare each controller tag, controller tag array or controller tag structure. Individual controller tags are declared with basic data types, such as INT and BOOL.

  • Page 78: Using Controller Tags

    Ladder Logic MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis For example, if you expand MNETCR.DATA, you will see that it contains two UDTs, ReadData and WriteData. Both of these are 600-element integer arrays by default.

  • Page 79: Controller Tag Overview

    3.4.1 MNETCR.DATA The controller tags in MNETCR.DATA hold data to be transferred between the processor and the MVI56E-MNETCR module. This read and write data is transferred between the processor and the module as "pages," or blocks, of data up to 40 words long.
  • Page 80 The ReadData array is related to the contents of the Read Data area of the module's internal database. To view the actual registers in the module's internal database, access the database display from ProSoft Configuration Builder's Diagnostics menu. For more information, see the section on PCB Diagnostics (page 93).
  • Page 81 The WriteData array is related to the contents of the Write Data area of the module's internal database. To view the actual registers in the module's internal database, access the database display from ProSoft Configuration Builder's Diagnostics menu. For more information, see the section on PCB Diagnostics (page 93).

  • Page 82: Mnetcr.control

    Ladder Logic MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 3.4.2 MNETCR.CONTROL This controller tag structure is used to request special tasks from the module. For more information, see Special Function Blocks (page 110).

  • Page 83: Mnetcr.util

    Ladder Logic Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 3.4.4 MNETCR.UTIL This controller tag structure stores the variables required for the data transfer between the processor and the MVI56E-MNETCR module. Controller Tag Data Type Description LastRead...
  • Page 84 Ladder Logic MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Page 84 of 161 ProSoft Technology, Inc.

  • Page 85: 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 86: Led Status Indicators

    Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis LED Status Indicators 4.1.1 Scrolling LED Status Indicators The scrolling LED display indicates the module's operating status as follows: Initialization Messages Code...

  • Page 87: Ethernet Led 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 88: 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. 4.1.5 Troubleshooting Use the following troubleshooting steps if you encounter problems when the module is powered up.

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

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 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 90 Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis In the Connection Setup dialog box, click the T button to ONNECTION verify that the module is accessible with the current settings.
  • Page 91 (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. ProSoft Technology, Inc.

  • Page 92: Connecting To The Module's Web Page

    The module's internal web server provides access to general product information, firmware download link, and links to ProSoft Technology's Web site. In ProSoft Discovery Service, select the module, and then click the right mouse button to open a shortcut menu.

  • Page 93: The Diagnostics Menu

    Main menu. 4.2.3 Monitoring Module Information Use the MODULE menu to view configuration and hardware information for the MVI56E-MNETCR module’s backplane and Ethernet application port. Version Use the Version menu to view module hardware and firmware information.

  • Page 94: Monitoring Backplane Information

    The status values on this menu correspond with members of the Status Data Definition (page 97). 4.2.5 Monitoring Database Information Use the DATABASE menu to view the contents of the MVI56E-MNETCR module’s internal database. You can view data in the following formats: Page 94 of 161 ProSoft Technology, Inc.

  • Page 95: Monitoring Mnet Client Information

    Config Use the Configuration menu to view configuration settings for MNET Client x. The information on this menu corresponds with the configuration information in the MNET Client x settings in ProSoft Configuration Builder. ProSoft Technology, Inc. Page 95 of 161...
  • Page 96 Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Status Use the Status menu to view status for MNET Client x. During normal operation, the number of requests and responses should increment, while the number of errors should not change.

  • Page 97: Reading Status Data From The Module

    In the ladder logic's MNETCR.STATUS controller tag structure. The MVI56E-MNETCR module returns status data in the input image that can be used to determine the module’s operating status. This data is transferred from the module to the ControlLogix processor continuously as part of the normal data transfer block sequence (page 108).
  • Page 98 Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Controller Tag Data Type Description PassCnt This value is incremented each time a complete program cycle occurs in the module. BlockStats.Read Total number of read blocks transferred from the module to the processor BlockStats.Write...

  • Page 99: Configuration Error Word

    There are several different ways to view Client Command Errors.  In the MNETCR.STATUS.CmdErrorList controller tag array  On the Client status data screens in the ProSoft Configuration Builder Diagnostics  At a module database location specified by the configuration's MNET Client x Command Error Pointer, if the Command Error Pointer is enabled.
  • Page 100 Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Word Offset Description Command 0 Error Command 1 Error Command 2 Error Command 3 Error … …. … … Command 15 Error...
  • Page 101 MVI56E-MNETCR ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Command List Entry Errors Code Description Too few parameters Invalid enable code Internal address > maximum address Invalid node address (<0 or >255)
  • Page 102 Diagnostics and Troubleshooting MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Page 102 of 161 ProSoft Technology, Inc.

  • Page 103: Reference

    In This Chapter  Product Specifications ................. 104  Backplane Data Transfer ..............106  Data Flow between MVI56E-MNETCR, Processor, and Network ..120  Ethernet Cable Specifications ............. 123  Modbus Protocol Specification ............125  Using the Optional Add-On Instruction Rung Import ......137 ...

  • Page 104: Product Specifications

    CF card Modbus TCP/IP Client (Master) The MVI56E-MNETCR is a Client-only module that will operate on a local or remote rack. This module was created to improve performance when controlling multiple servers on a Modbus TCP/IP network.

  • Page 105: Functional Specifications

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual  ControlLogix processor can be programmed to use special functions to control the activity on the Client by actively selecting commands to execute from the command list (Command Control) or by issuing commands directly from the ladder logic (Event Commands) 5.1.2 Functional Specifications...

  • Page 106: Backplane Data Transfer

    The module's firmware program extracts the data and places it in the module's internal database. The output image is set to 42 words. The following illustration shows the data transfer method used to move data between the ControlLogix processor, the MVI56E-MNETCR module and the Modbus TCP/IP Network. Page 106 of 161...
  • Page 107 4999 Data contained in this database is transferred in blocks, or pages, using the input and output images. ControlLogix ladder logic and the MVI56E-MNETCR module's program work together to coordinate these block transfers. Up to 40 words of data can be transferred from the module to the processor (read block - input image) or from the processor to the module (write block - output image) in each block transfer.

  • Page 108: Normal Data Transfer Blocks

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.2.1 Normal Data Transfer Blocks Normal data transfer includes the paging of user data between the processor's data areas and the module’s internal database (registers 0 to 4999), as well as the paging of status data.
  • Page 109 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Write Block These blocks of data transfer information from the ControlLogix processor to the module. The following table describes the structure of the output image.

  • Page 110: Special Function Blocks

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.2.2 Special Function Blocks Special function blocks are optional blocks used to request special tasks from the module. Initialize Output Data Blocks (1000 to 1124) Use the Initialize Output Data parameter in the configuration to bring the module to a known state after a restart operation.
  • Page 111 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Event Command Blocks (2000 to 2029) Note: Event Commands are not needed for normal Modbus command list polling operations and are needed only occasionally for special circumstances.
  • Page 112 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Word Offset Description Swap Code - The parameter specifies the swap type for the data. This function is only valid for function codes 3 and 4.
  • Page 113 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Controller Tag Data Type Description EventCmd.IP3 Enter the fourth digit of the destination server's IP address Enter the TCP Service Port number (0-65535). Enter EventCmd.ServPort...
  • Page 114 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Word Offset Client Status Not used Not used Not used Not used Configuration Error Word Current Error Last Error Status information transferred in the Client Status block can be viewed in the MNETCR.STATUS controller tag in the ladder logic.
  • Page 115 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Like Event Command blocks, Command Control blocks place commands into the module’s command priority queue. Unlike Event Command blocks, which contain all the values needed for one command, Command Control is used with commands already defined in the MNET Client x Command List.
  • Page 116 MNET CmdControl.CmdIndex INT[16] ROW NUMBER Client x Command List in Prosoft Configuration Builder minus 1. This is a 16-element array. Each element holds one Command Index. Set this tag to 1 to trigger the execution of a Command...
  • Page 117 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Reset Module Status Block (9971) This block allows the processor to reset all status values available from the module to the processor or through the PCB diagnostics menu. This block is...
  • Page 118 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Word Offset Description Length First digit of dotted IP address Second digit of dotted IP address Third digit of dotted IP address Last digit of dotted IP address...
  • Page 119 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Block Request from Processor to Module Word Offset Description Length 9998 1 to 41 Spare The module does not send a response block for this command.

  • Page 120: Data Flow Between Mvi56E-Mnetcr, Processor, And Network

    Data Flow between MVI56E-MNETCR, Processor, and Network The following topics describe the flow of data between the two pieces of hardware (processor and MVI56E-MNETCR module) and other nodes on the Modbus TCP/IP network. The module contains up to 30 Clients, which can generate either MBAP (Modbus API for network communications) or MNET requests dependent on the service port selected in the command.

  • Page 121: Client Driver

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 5.3.1 Client Driver In the Client driver, the MVI56E-MNETCR module issues read or write commands to servers on the Modbus TCP/IP network using up to 30 simulated Clients. The commands originate either from the module's user-configured Client x Command List for each Client, or directly from the processor as Event Commands.

  • Page 122: Client Command List

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis When configured, the Client driver begins transmitting read and/or write commands to servers on the network. The data for write commands is obtained from the module's internal database.

  • Page 123: Ethernet Cable Specifications

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Ethernet Cable Specifications The recommended cable is Category 5 or better. A Category 5 cable has four twisted pairs of wires, which are color-coded and cannot be swapped. The module uses only two of the four pairs.

  • Page 124: Ethernet Performance

    User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.4.2 Ethernet Performance Ethernet performance on the MVI56E-MNETCR module can affect the operation of the MNETCR application ports in the following ways.  Accessing the web interface (refreshing the page, downloading files, and so on) may affect MNETCR performance ...

  • Page 125: Modbus Protocol Specification

    Nevertheless, the efficiency, scalability, and low cost of a MODBUS/TCP network make this an ideal solution for industrial applications. The MVI56E-MNETCR module acts as an input/output module between devices on a MODBUS/TCP network and the Rockwell Automation backplane. The module uses an internal database to pass data and commands between the processor and the server devices on the MODBUS/TCP network.

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

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Func Data Start Pt Hi Data Start Pt Lo Data # Of Pts Ho Data # Of Pts Lo Error Check Field Response An example response to Read Coil Status is as shown in Figure C2. The data is packed one bit for each coil.

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

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Func Data Start Pt Hi Data Start Pt Lo Data #of Pts Hi Data #of Pts Lo Error Check Field Response An example response to Read Input Status is as shown in Figure C4. The data is packed one bit for each input.

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

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Adr Func Data Start Reg Hi Data Start Reg Lo Data #of Regs Hi Data #of Regs Lo Error Check Field Response The addressed server responds with its address and the function code, followed by the information field.

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

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Response The addressed server responds with its address and the function code followed by the information field. The information field contains 1 byte describing the quantity of data bytes to be returned.

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

    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 131: Diagnostics (Function Code 08)

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

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

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Request Response Field Name (Hex) Field Name (Hex) Function Function Sub-function Hi Sub-function Hi Sub-function Lo Sub-function Lo Data Hi Data Hi Data Lo...

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

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Note: Functions 5, 6, 15, and 16 are the only messages (other than Loopback Diagnostic Test) that will be recognized as valid for broadcast.

  • Page 134: Modbus Exception Responses

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Response The normal response to a function 16 query is to echo the address, function code, starting address and number of registers to be loaded.
  • Page 135 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Request Response Starting Address Hi Exception Code Starting Address Lo Quantity of Outputs Hi Quantity of Outputs Lo In this example, the Client addresses a request to server device. The function code (01) is for a Read Output Status operation.
  • Page 136 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Code Name Meaning Memory Parity Error Specialized use in conjunction with function codes 20 and 21 and reference type 6, to indicate that the extended file area failed to pass a consistency check.

  • Page 137: 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 138: Installing The Rung Import With Utility Add-On Instruction

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.6.3 Installing the Rung Import with Utility Add-On Instruction Right-click on an empty rung in the main routine of your existing ladder logic and choose I...
  • Page 139 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Navigate to the folder where you saved MVI56EMNETCR_Optional_Rung_v1_0.L5X and select the file. In the I window, click OK. MPORT ONFIGURATION ProSoft Technology, Inc. Page 139 of 161...
  • Page 140 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis The Add-On Instruction will now be visible in the ladder logic. Observe that the procedure has also imported data types and controller tags associated to the Add-On Instruction.
  • Page 141 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual You will notice that new tags have been imported: four MESSAGE tags, MVI56MNETCCLOCK and MVI56MNETCETHERNET tags. In the Add-On Instruction, click the [...] button next to each MSG tag to open...

  • Page 142: Reading The Ethernet Settings From The Module

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Select the module to configure the message path. 5.6.4 Reading the Ethernet Settings from the Module Expand the MVI56EMNETCRETHERNET controller tag and move a value of 1 to MVI56EMNETCRETHERNET.R...

  • Page 143: Writing The Ethernet Settings To The Module

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual The bit will be automatically reset and the current Ethernet settings will be copied to MVI56EMNETCRETHERNET controller tag as follows. To check the status of the message, refer to the READETHERNETMSG tag.
  • Page 144 Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis Move a value of 1 to MVI56EMNETCRETHERNET.W RITE After the message is executed, the MVI56EMNETCRETHERNET.W RITE resets to 0. To check the status of the message, refer to the WRITEETHERNETMSG tag.

  • Page 145: Reading The Clock Value From The Module

    MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual 5.6.6 Reading the Clock Value from the Module Expand the MVI56EMNETCRCLOCK controller tag and move a value of 1 to MVI56EMNETCRCLOCK.R The bit will be automatically reset and the current clock value will be copied to MVI56EMNETCRCLOCK.C...

  • Page 146: Writing The Clock Value To The Module

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.6.7 Writing the Clock Value to the Module Expand the MVI56EMNETCRCLOCK controller tag. Set the new Clock value in MVI56EMNETCRCLOCK.C ONFIG Move a value of 1 to MVI56EMNETCRCLOCK.W RITE The bit will be automatically reset to 0.

  • Page 147: Adding The Module To An Existing Project

    Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Adding the Module to an Existing Project Add the MVI56E-MNETCR module to the project. Select the I/O folder in the Controller Organization window, and then click ONFIGURATION the right mouse button to open a shortcut menu. On the shortcut menu,...
  • Page 148 ODULE FOR EMOTE HASSIS Select D -INT (Very Important) Comm Format Slot Enter the slot number in the rack where the MVI56E-MNETCR module will be installed. Input Assembly Instance Input Size Output Assembly Instance Output Size Configuration Assembly Instance 4 Configuration Size Enter the Name, Description and Slot options for your application.
  • Page 149 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Edit the Module Properties. Select the Requested Packet Interval value for scanning the I/O on the module. This value represents the minimum frequency that the module will handle scheduled events. This value should not be set to less than 1 millisecond.

  • Page 150: Using The Sample Program

    Download the manuals and sample program from the ProSoft Technology web site You can always download the latest version of the sample ladder logic and user manuals for the MVI56E-MNETCR module from the ProSoft Technology website, at www.prosoft-technology.com/support/downloads (http://www.prosoft-...
  • Page 151 MVI56E-MNETCR ♦ ControlLogix Platform Reference Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual When RSLogix has established communication with the processor, the Connected To Go Online dialog box will open. In the Connected To Go Online dialog box, click the G tab.

  • Page 152: Choosing The Controller Type

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.8.2 Choosing the Controller Type The sample application is for a 1756-L63 ControlLogix 5563 Controller. If you are using a different model of the ControlLogix processor, you must configure the sample program to use the correct processor model.

  • Page 153: Selecting The Slot Number For The Module

    RSLogix will automatically apply the slot number change to all tags, variables and ladder logic rungs that use the MVI56E-MNETCR slot number for computation. ProSoft Technology, Inc.

  • Page 154: Downloading The Sample Program To The Processor

    Reference MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 5.8.4 Downloading the Sample Program to the Processor To download the sample program from RSLogix 5000 to the ControlLogix processor Note: The key switch on the front of the ControlLogix module must be in the REM position.

  • Page 155: 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 156 Support, Service & Warranty MVI56E-MNETCR ♦ ControlLogix Platform User Manual Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis 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 157: 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 158 MVI56E-MNETCR ♦ ControlLogix Platform Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual ProSoft Technology, Inc. Page 158 of 161...

  • Page 159: Index

    Important Safety Information • 3 Configuring Module Parameters • 43 Importing the Add-On Instruction • 25 Configuring the MVI56E-MNETCR Module • 39 Importing the Sample Add-On Instruction • 16, 26 Connecting to the Module's Web Page • 92 Initialize Output Data • 45 Connecting Your PC to the ControlLogix Processor •...
  • Page 160 Package Contents • 12 Using Controller Tags • 78 Pinouts • 105, 123 Using ProSoft Configuration Builder Software • 39 Poll Interval • 51 Using RSWho to Connect to the Module • 61, 72 Preset Multiple Registers (Function Code 16) • 133 Using the Diagnostics Menu in ProSoft Configuration Preset Single Register (Function Code 06) •...
  • Page 161 MVI56E-MNETCR ♦ ControlLogix Platform Index Modbus TCP/IP Multi-Client Enhanced Communications Module for Remote Chassis User Manual Your Feedback Please • 2 ProSoft Technology, Inc. Page 161 of 161...

Table of Contents