ProSoft Technology MVI56E-MNETC User Manual
  1. Manuals
  2. Brands
  3. ProSoft Technology Manuals
  4. Server
  5. MVI56E-MNETC
  6. User manual

ProSoft Technology MVI56E-MNETC User Manual

Controllogix platform, modbus tcp/ip client enhanced, communication module - client/server
Hide thumbs Also See for MVI56E-MNETC:
Table of Contents

Advertisement

Quick Links

Download this manual
MVI56E-MNETC/MNETCXT
ControlLogix Platform
Modbus TCP/IP Client Enhanced
Communication Module - Client/Server
September 20, 2018
USER MANUAL

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for ProSoft Technology MVI56E-MNETC

Summary of Contents for ProSoft Technology MVI56E-MNETC

  • Page 1 MVI56E-MNETC/MNETCXT ControlLogix Platform Modbus TCP/IP Client Enhanced Communication Module - Client/Server September 20, 2018 USER MANUAL...

  • Page 2: Your Feedback Please

    Neither ProSoft Technology nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. Information in this document including illustrations, specifications and dimensions may contain technical inaccuracies or typographical errors.

  • Page 3: Important Safety Information

    Important Safety Information North America Warnings This Equipment is Suitable For Use in Class I, Division 2, Groups A, B, C, D or Non-Hazardous Locations Only. Warning – Explosion Hazard – Substitution of Any Components May Impair Suitability for Class I, Division 2. Warning –...

  • Page 4: Battery Life Advisory

    Battery Life Advisory Note: Modules manufactured after April 1st, 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

    Downloading the Project to the Module ..............68 Using Controller Tags Controller Tags ......................71 3.1.1 MVI56E-MNETC Controller Tags ................72 User-Defined Data Types (UDTs) ................73 3.2.1 MVI56E-MNETC User-Defined Data Types ............73 Controller Tag Overview..................74 3.3.1 MNETC.DATA ......................74 3.3.2 MNETC.CONTROL ....................77 3.3.3 MNETC.STATUS ....................
  • Page 6 Backplane Data Transfer ..................103 5.2.2 Normal Data Transfer Blocks ................106 5.2.3 Special Function Blocks ..................110 5.2.4 Data Flow between MVI56E-MNETC/MNETCXT Module and Processor ... 129 Ethernet Cable Specifications ................134 5.3.1 Ethernet Cable Configuration ................134 5.3.2 Ethernet Performance ................... 134 Modbus Protocol Specification ................
  • Page 7 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Contents Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 5.5.6 Reading the Clock Value from the Module ............157 5.5.7 Writing the Clock Value to the Module ..............158 Adding the Module to an Existing Project ............. 159 Using the Sample Program ...................
  • Page 8 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual ProSoft Technology, Inc. Page 8 of 172 September 20, 2018...

  • Page 9: Start Here

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Start Here In This Chapter  System Requirements ................10  Setting Jumpers ..................10  Installing the Module in the Rack ............12 ...

  • Page 10: System Requirements

    256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color 1024  768 recommended) Note: The Hardware and Operating System requirements in this list are the minimum recommended to install and run software provided by ProSoft Technology . Other third party ®...

  • Page 11: Setting Jumpers

    Setup pins together unless you are directed to do so by ProSoft Technical Support (or you want to update the module firmware). The following illustration shows the MVI56E-MNETC/MNETCXT jumper configuration with the Setup Jumper OFF. Note: If you are installing the module in a remote rack, you may prefer to leave the Setup pins jumpered.

  • Page 12: Installing The Module In The Rack

    Installing the Module in the Rack Make sure your ControlLogix processor and power supply are installed and configured, before installing the MVI56E-MNETC/MNETCXT module. Refer to your Rockwell Automation product documentation for installation instructions. Warning: You must follow all safety instructions when installing this or any other electronic devices.

  • Page 13: Creating A New Rslogix 5000 Project

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Make a note of the slot location. You must identify the slot in which the module is installed in order for the sample program to work correctly. Slot numbers are identified on the green circuit board (backplane) of the ControlLogix rack.

  • Page 14: Before You Import The Add-On Instruction

    Module's Web Page (page 98). Important: The Optional Add-On Instruction supports only the two features listed above. You must use the regular MVI56E-MNETC/MNETCXT Add-On Instruction for all other features including backplane transfer and Modbus data communication. Page 14 of 172 ProSoft Technology, Inc.

  • Page 15: Creating The Module

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 1.4.2 Creating the Module Add the MVI56E-MNETC/MNETCXT module to the project. In the C window, select I/O C ONTROLLER RGANIZATION ONFIGURATION click the right mouse button to open a shortcut menu. On the shortcut menu,...
  • Page 16 Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Click C . This action opens the N dialog box. REATE ODULE In the N dialog box, enter the following values. ODULE Parameter Value Enter a module identification string.
  • Page 17 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Edit the Module Properties. Select the R value EQUESTED ACKET NTERVAL for scanning the I/O on the module. This value represents the minimum frequency at which the module will handle scheduled events. This value should not be set to less than 1 millisecond.

  • Page 18: Importing The Add-On Instruction

    Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 1.4.3 Importing the Add-On Instruction In the C window, expand the T folder and ONTROLLER RGANIZATION ASKS subfolders until you reach the M folder.
  • Page 19 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Navigate to the location on your PC where you saved the Add-On Instruction (for example, My Documents or Desktop). Select the .L5X file. This action opens the I dialog box.

  • Page 20: September

    Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server If you are using the module in a different slot (or remote rack), edit the connection input and output variables that define the path to the module. Edit...

  • Page 21: Adding Multiple Modules (Optional)

    Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 1.4.4 Adding Multiple Modules (Optional) Important: If your application requires more than one MVI56E-MNETC/MNETCXT module in the same project, follow the steps below. In the I/O C folder, click the right mouse button to open a...
  • Page 22 Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Fill the module properties as follows: Parameter Value Enter a module identification string. Example: MNETC_2. Enter a description for the module. Example: ProSoft Modbus ESCRIPTION TCP/IP Enhanced Communication Module.
  • Page 23 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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 24 Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server This action opens the I window. Click T under MPORT ONFIGURATION to show the tags that will be imported. OUTINE 10 Associate the I/O connection variables to the correct module. The default...
  • Page 25 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 11 Change the default tags MNETC and AOI56MNETC to avoid conflict with existing tags. In this step, append the string "_2", as shown in the following illustration.
  • Page 26 Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 12 Click OK to confirm. The setup procedure is now complete. Save the project and download the application to your ControlLogix processor. Page 26 of 172 ProSoft Technology, Inc.

  • Page 27: Connecting Your Pc To The Controllogix Processor

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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 28: Downloading The Sample Program To The Processor

    Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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 29: Mvi56E-Mnetc/Mnetcxt Configuration

    (known working) configurations to new projects. Note: During startup and initialization, the MVI56E-MNETC/MNETCXT 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 30: Upgrading From Mvi56-Mnetc In Prosoft Configuration Builder

    Modbus TCP/IP Client Enhanced Communication Module - Client/Server 2.1.2 Upgrading from MVI56-MNETC in ProSoft Configuration Builder MVI56E-MNETC/MNETCXT modules are fully backward-compatible with MVI56- MNETC modules. However, you will need to convert your MVI56-MNETC configuration in ProSoft Configuration Builder to a form that your new MVI56E- MNETC/MNETCXT module will accept when you download it.
  • Page 31 Default Location, with a Default Module in the Default Location folder. The following illustration shows the PCB window with a new project. Your first task is to add the MVI56E-MNETC/MNETCXT module to the project. ProSoft Technology, Inc. Page 31 of 172...
  • Page 32 . This opens the Choose Module Type dialog box. ODULE In the Product Line Filter area of the dialog box, select MVI56E. In the Select Module Type dropdown list, select MVI56E-MNETC/MNETCXT, and then click OK to save your settings and return to the ProSoft Configuration Builder window.

  • Page 33: Setting Module Parameters

    2.1.4 Setting Module Parameters Notice that the contents of the information pane and the configuration pane changed when you added the MVI56E-MNETC/MNETCXT module to the project. At this time, you may wish to rename the Default Project and Default Location folders in the tree view.

  • Page 34: Module

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Printing a Configuration File In the main PCB window, right-click the MVI56E-MNETC/MNETCXT M ODULE icon and then choose V ONFIGURATION In the View Configuration dialog box, click the F...
  • Page 35 ONITOR You execute the rest of the steps in ProSoft Configuration Builder. Start ProSoft Configuration Builder. Double-click the MVI56E-MNETC icon to expand the menu for the module in PCB. Click the [+] icon next to the icon to expand the Module menu.
  • Page 36 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Double-click the icon to open up the Edit - Module dialog box. ODULE Click R and change the value from 600 to 1000. EGISTER OUNT Click OK to close the dialog box.
  • Page 37 Note: To take advantage of the new features described above, your MVI56E- MNETC/MNETCXT module needs to have firmware version 3.01 or higher, and your MVI56E-MNETC/MNETCXT Add-On Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.
  • Page 38 Note: To take advantage of the new features described above, your MVI56E- MNETC/MNETCXT module needs to have firmware version 3.01 or higher, and your MVI56E-MNETC/MNETCXT Add-On Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.

  • Page 39: Mnet Servers

    Note: To take advantage of the new features described above, your MVI56E-MNETC/MNETCXT module needs to have firmware version 3.01 or higher, and your MVI56E-MNETC/MNETCXT Add- On Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.
  • Page 40 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Enron-Daniels or N This flag specifies how the Slave driver will respond to Function Code 3, 6, and 16 commands (read and write Holding Registers) from a remote master when it is moving 32-bit floating-point data.
  • Page 41 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Output Offset 0 to 9999 This parameter defines the start register for the Modbus command data in the internal database. This parameter is enabled when a value greater than 0 is set.

  • Page 42: Mnet Client X

    MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 2.1.7 MNET Client x This section defines general configuration for the MNET Client (Master). Client Error/Status Pointer -1 to 9990 This parameter sets the address in the internal database where the Client error/status data will be placed.
  • Page 43 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Retry Count 0 to 10 This parameter specifies the number of times a command will be retried if it fails. Float Flag or N...

  • Page 44: 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-MNETC/MNETCXT communication module, and the second part contains information required to interface to the Modbus TCP/IP server device.
  • Page 45 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Command List Overview In order to interface the module with Modbus TCP/IP server devices, you must construct a command list. The commands in the list specify the server device to...
  • Page 46 Register Count Multiple Register (4x) The first part of the record is the module information, which relates to the MVI56E-MNETC/MNETCXT, and the second part contains information required to interface to the server device. Page 46 of 172 ProSoft Technology, Inc.
  • Page 47 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Command list example: 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 48 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Internal Address 0 to 65535 (for bit-level addressing) 0 to 9999 (for word-level addressing) This field specifies the database address in the module's internal database to use as the destination for data brought in by a read command or as the source for data to be sent out by a write command.
  • Page 49 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Swap Code ORDS & B ORDS YTES YTES This parameter defines if and how the order of bytes in data received or sent is to be rearranged.
  • Page 50 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Note: Use the Node IP Address parameter to address commands to a remote Modbus TCP/IP device. See Node IP Address (page 49). Note: Most Modbus devices accept an address in the range of only 1 to 247, so check with the slave device manufacturer to see if a particular slave can use addresses 248 to 255.

  • Page 51: Static Arp Table

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Address calculation examples:  For bit-level Coil commands (FC 1, 5, or 15) to read or write a Coil 0X address 00001, specify a value of 0 (00001 - 00001 = 0).
  • Page 52 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server IP Address Dotted notation This table contains a list of static IP addresses that the module will use when an ARP is required. The module will accept up to 40 static IP/MAC address data sets.

  • Page 53: Ethernet Configuration

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 2.1.10 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 54: Connecting Your Pc To The Module

    Ethernet using Rockwell Automation’s 1756-ENBT EtherNet/IP ® module. This allows you to configure the MVI56E-MNETC/MNETCXT 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 55 CIPconnect Path Editor dialog box. The CIPconnect Path Editor allows you to define the path between the PC and the MVI56E-MNETC/MNETCXT module. The first connection from the PC is always a 1756-ENBT (Ethernet/IP) module. Each row corresponds to a physical rack in the CIP path.
  • Page 56 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server  If the MVI56E-MNETC/MNETCXT module is located in the same rack as the first 1756-ENBT module, select R . 1 and configure the associated parameters. ...
  • Page 57 Rack 1 Slot Module Network Address ControlLogix Processor MVI56E-MNETC/MNETCXT 1756-ENBT IP=192.168.0.100 In ProSoft Configuration Builder, right-click the MVI56E-MNETC/MNETCXT icon and then choose D IAGNOSTICS In the Diagnostics window, click the S button. ONNECTION ProSoft Technology, Inc. Page 57 of 172...
  • Page 58 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server In the Select Connection Type dropdown list, choose 1756-ENBT. The default path appears in the text box, as shown in the following illustration. Configure the path as shown in the following illustration, and click CIP P to build the path in text format.
  • Page 59 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Check the new path in the Connection Setup dialog box. Click T to verify that the physical path is available. The ONNECTION following message should be displayed upon success.
  • Page 60 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Example 2: Remote Rack Application For this example, the MVI56E-MNETC/MNETCXT module is located in a remote rack accessible through ControlNet, as shown in the following illustration. 1756-ENBT 1756-CNB...
  • Page 61 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual In ProSoft Configuration Builder, right-click the MVI56E-MNETC/MNETCXT icon and then choose D IAGNOSTICS In the Diagnostics window, click the S button. ONNECTION ProSoft Technology, Inc.
  • Page 62 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server In the Select Connection Type dropdown list, choose 1756-ENBT. The default path appears in the text box, as shown in the following illustration. Configure the path as shown in the following illustration, and click CIP P to build the path in text format.
  • Page 63 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Check the new path in the Connection Setup dialog box. Click T to verify that the physical path is available. The ONNECTION following message should be displayed upon success.

  • Page 64: Using Rswho To Connect To The Module

    MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 2.2.2 Using RSWho to Connect to the Module You need to have RSLinx installed on your PC to use this feature. You also need an ENBT module set up in the rack.

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

    (not included). Setting Up a Temporary IP Address Important: ProSoft Configuration Builder locates MVI56E-MNETC/MNETCXT 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 66 MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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...
  • Page 67 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Close the ProSoft Discovery Service window. Enter the temporary IP in the Ethernet address field of the Connection Setup dialog box, then click the...

  • Page 68: Downloading The Project To The Module

    MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Downloading the Project to the Module Note: For alternative methods of connecting to the module with your PC, see Connecting Your PC to the Module (page 54).
  • Page 69 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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 70 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Page 70 of 172 ProSoft Technology, Inc. September 20, 2018...

  • Page 71: Using Controller Tags

    RSLogix (page 29, page 13) for information on importing the Add-On Instruction into RSLogix. Controller Tags Data related to the MVI56E-MNETC/MNETCXT is stored in the ladder logic in variables called controller tags. You use controller tags to manage communication between the MVI56E-MNETC/MNETCXT module and the ControlLogix processor: ...

  • Page 72: Mvi56E-Mnetc Controller Tags

    User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server The MVI56E-MNETC/MNETCXT Add-On Instruction is extensively commented to provide information on the purpose and function of each user-defined data type and controller tag. For most applications, the Add-On Instruction works without needing any modification.

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

    Like the controller tags, the UDTs are organized in a multiple-level tree structure. 3.2.1 MVI56E-MNETC User-Defined Data Types Eleven different UDTs are defined for the MVI56E-MNETC Add-On Instruction. The main UDT, MNETCMODULEDEF, contains all the data types for the module and was used to create the main controller tag structure, MNETC.

  • Page 74: Controller Tag Overview

    3.3.1 MNETC.DATA The controller tags in MNETC.DATA hold data to be transferred between the processor and the MVI56E-MNETC/MNETCXT module. This read and write data is transferred between the processor and module as "pages," or blocks, of data up to 200 words long.
  • Page 75 MNETC.DATA.ReadData The ReadData controller tag array should accommodate the value entered in the Read Register Count (page 37) parameter of the MVI56E-MNETC/MNETCXT configuration file in Prosoft Configuration Builder. The default length of this array is 600. If more than 600 registers are needed, please see Adjust the Input and Output Array Sizes.
  • Page 76 MNETC.DATA.WriteData The WriteData controller tag array should accommodate the value entered in the Read Register Count (page 37) parameter of the MVI56E-MNETC/MNETCXT configuration file in Prosoft Configuration Builder. The default length of this array is 600. If more than 600 registers are needed, please see Adjust the Input and Output Array Sizes.

  • Page 77: Mnetc.control

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 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.

  • Page 78: Mnetc.status

    Server status data ServerStatsTrigger BOOL Trigger the Server Status block request 3.3.4 MNETC.UTIL This controller tag structure stores the variables required for the data transfer between the processor and the MVI56E-MNETC/MNETCXT module. Name Data Type Description LastRead Index of last read block...
  • Page 79 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Name Data Type Description WriteDataBlkCount Holds the value of the block counts of the WriteData array RBTSremainder Holds remainder calculation value from the...
  • Page 80 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Page 80 of 172 ProSoft Technology, Inc. September 20, 2018...

  • Page 81: Diagnostics And Troubleshooting

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Diagnostics and Troubleshooting In This Chapter  Ethernet LED Indicators ................ 81  Clearing a Fault Condition ..............83  Troubleshooting the LEDs ..............84 ...

  • Page 82: Scrolling Led Status Indicators

    Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 4.1.1 Scrolling LED Status Indicators The scrolling LED display indicates the module's operating status as follows: Initialization Messages Code Message Boot / DDOK...

  • Page 83: Non-Scrolling Led Status Indicators

    The module is not receiving adequate power or is not securely plugged into the rack. May also be OFF during configuration download. GREEN The MVI56E-MNETC/MNETCXT is working normally. The most common cause is that the module has detected a communication error during operation of an application port.

  • Page 84: Troubleshooting The Leds

    Processor I/O LED This indicates a problem with backplane communications. A problem could flashes exist between the processor and any installed I/O module, not just the MVI56E-MNETC/MNETCXT. Verify all modules in the rack are configured correctly. Module Errors Problem Description...

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

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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.
  • Page 86 Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server In the Connection Setup dialog box, click the T button to ONNECTION verify that the module is accessible with the current settings. ®...
  • Page 87 (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 88: The Diagnostics Menu

    Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 4.4.1 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 89: Monitoring Module Information

    Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 4.4.2 Monitoring Module Information Use the MODULE menu to view configuration and hardware information for the MVI56E-MNETC/MNETCXT module’s backplane and Ethernet application port. Version Use the Version menu to view module hardware and firmware information. Config Use the Configuration menu to view backplane configuration settings for the MVI56E-MNETC/MNETCXT module.

  • Page 90: Monitoring Backplane Information

    Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 4.4.3 Monitoring Backplane Information Use the BACKPLANE menu to view the backplane status information for the MVI56E-MNETC/MNETCXT module. Backplane Status Use the Status menu to view current backplane status, including ...

  • Page 91: Monitoring Mnetc Server Information

    Note: To take advantage of the new features described above, your MVI56E- MNETC/MNETCXT module needs to have firmware version 3.01 or higher, and your MVI56E-MNETC/MNETCXT Add-On Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.

  • Page 92: Monitoring Mnet Client Information

    In the ladder logic's MNETC.STATUS controller tag structure. The MVI56E-MNETC/MNETCXT 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 Blocks (page 106).

  • Page 93: Status Data Definition

    Note: To take advantage of the new features described above, your MVI56E- MNETC/MNETCXT module needs to have firmware version 3.01 or higher, and your MVI56E-MNETC/MNETCXT Add-On Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.
  • Page 94 Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Controller Tag Data Type Description PassCnt This value is incremented each time a complete program cycle occurs in the module. ProductVersion Product version...
  • Page 95 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Controller Tag Data Type Description EventSeqCmd.Trigger BOOL Set the value of this tag to 1 to trigger the Event Sequence Command block request.

  • Page 96: Configuration Error Word

    Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 4.5.2 Configuration Error Word The Configuration Error Word contains Client configuration error indications, in a bit-mapped format. Specific bits in the module's Configuration Error Word are turned on (set to 1) to indicate various configuration errors.
  • Page 97 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Word Offset Description Command 0 Error Command 1 Error Command 2 Error Command 3 Error … …. … … Command 15 Error Command 16 Error For every command that has an error, the module automatically sets the poll delay parameter to 30 seconds.

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

    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 the tree view in ProSoft Configuration Builder, right-click the MVI56E- MNETC/MNETCXT icon and then choose D...
  • Page 99 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual In ProSoft Discovery Service, right-click the MVI56E-MNETC/MNETCXT icon ’ and then choose V IEW MODULE S WEBPAGE This displays the module webpage. ProSoft Technology, Inc.
  • Page 100 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Page 100 of 172 ProSoft Technology, Inc. September 20, 2018...

  • Page 101: Reference

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Reference In This Chapter  Product Specifications ................. 101  Functional Overview ................103  Ethernet Cable Specifications ............. 134  Modbus Protocol Specification ............135 ...

  • Page 102: Functional Specifications

    CF card Modbus TCP/IP Specifications ProSoft Technology’s Modbus TCP/IP implementation (MNET) includes both Client (Master) and server (slave) capabilities. Modbus TCP/IP Server (Slave) ...

  • Page 103: Functional Overview

    Auto-crossover cable detection Functional Overview 5.2.1 Backplane Data Transfer The MVI56E-MNETC/MNETCXT module communicates directly over the ControlLogix backplane. Data is paged between the module and the ControlLogix processor across the backplane using the module's input and output images. The update frequency of the images is determined by the scheduled scan rate defined by the user for the module and the communication load on the module.
  • Page 104 Modbus TCP/IP Client Enhanced Communication Module - Client/Server The following illustration shows the data transfer method used to move data between the ControlLogix processor, the MVI56E-MNETC/MNETCXT module and the Modbus TCP/IP Network. All data transferred between the module and the processor over the backplane is through the input and output images.
  • Page 105 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Data contained in this database is transferred in blocks, or pages, using the input and output images. ControlLogix ladder logic and the MVI56E- MNETC/MNETCXT module's program work together to coordinate these block transfers.

  • Page 106: Normal Data Transfer Blocks

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Block ID Range Descriptions 9999 Cold-boot block These block identification codes can be broken down into two groups: Normal data transfer blocks  Read and Write blocks (-1 to 50) Special function blocks ...
  • Page 107 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual The Read Block ID is an index value used to determine where the 200 words of data from module memory will be placed in the ReadData[x] controller tag array of the ControlLogix processor.
  • Page 108 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Status information transferred in the Read block can be viewed in the MNETC.STATUS controller tag in the ladder logic. For more information, see the Status Data Definition (page 93).
  • Page 109 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual The following illustrations show the effect of changing the value of the Select Priority Read Block register (Write Block offset 247). In the following histogram curve, the Select Priority Read Block is equal to 0.

  • Page 110: Special Function Blocks

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Select Priority Read Block = 0 After the ladder logic changes the value of Local:1:O.Data[247] from 5 to 0, then the Local:1:I.Data[249] value is updated as before, by returning all blocks 1 through 10 in a repeating sequence.
  • Page 111 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Block Request from Module to Processor Word Offset Description Length Reserved 1000 to 1049 2 to 248 Spare 1000 to 1049 Ladder logic subtracts 1000 from the value contained in word 249 to determine a block index.
  • Page 112 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Block Request from Processor to Module Word Offset Description Length 2000 to 2029 (last digits indicate which Client to utilize) 1 to 4 IP Address...
  • Page 113 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Word Offset Description This word contains the next read request block identification code. This word contains the result of the event request. If a value of one is present, the command was issued.
  • Page 114 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Client Status Blocks (3000 to 3029) Client status data for a specific Client can be requested and returned in a special Client Status block. The status data contained in the Client Status block is different from the status data contained in the normal data transfer blocks.
  • Page 115 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Controller Tags To issue a Client Status block request, enter the appropriate values in the following members of the MNETC.STATUS controller tag in the ladder logic.
  • Page 116 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Server Status Data Word Offset Server Status Total number of MNET command list requests Total number of MNET command list responses Total number of MNET command list errors sent...
  • Page 117 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual The routine polling process is temporarily interrupted. The commands in the command priority queue are executed until the queue is empty. Then the module goes back to where it left off on the MNET Client x Command List and continues routine polling.
  • Page 118 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server  The Modbus Function Code has one of the following values 1, 2, 3, 4, 5, 6, 7, 15 or 16.  The Device Database Address is the Modbus register or point in the remote server device to be associated with the command.
  • Page 119 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Event Sequence Command Error Report (4100 to 4129) This block displays the result of each command sent to the Client. The request includes the Client identification and the command sequence number. The response is the event count and error code for each event.
  • Page 120 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Event Sequence Command Count Status (4200) This block displays the command queue status data for all clients. The response is the priority command queue count and the Event Sequence Command status queue count.
  • Page 121 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Command Control Blocks Note: Command Control is not needed for normal Modbus command list polling operations and is needed only occasionally for special circumstances. During routine operation, the module continuously cycles through the user-...
  • Page 122 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Word Offset Description Length Command Index 2 Command Index 3 Command Index 4 Command Index 5 Command Index 6 Command Index 7 Command Index 8...
  • Page 123 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Controller Tags The MNETC.CONTROL controller tag array holds all the values needed to create one Command Control block, have it sent to the module, and control the processing of the returned response block.
  • Page 124 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server The Modbus protocol supports control of binary output (coils - functions 5 and 15) and registers (functions 6 and 16). Any Modbus function 5, 6, 15 or 16 commands will be passed from the server to the processor using the block identification numbers 9956 to 9961, 9970 and 9996.
  • Page 125 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Pass-Through Block 9959 from Module to Processor Word Offset Description Length 9959 Number of word registers in Modbus data set Starting word address for Modbus data set...
  • Page 126 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Unformatted Pass-Through Block (9996) When the unformatted pass-through mode (code 1) is selected, information is passed from the module to the processor with a block identification code of 9996.
  • Page 127 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Block Response from Module to Processor Word Offset Description Length Write Block ID First digit of dotted IP address Second digit of dotted IP address...
  • Page 128 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Reset Module Status Block (9997) 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 129: Data Flow Between Mvi56E-Mnetc/Mnetcxt Module And Processor

    Processor The following topics describe the flow of data between the two pieces of hardware (processor and MVI56E-MNETC/MNETCXT 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 130 Modbus TCP/IP Client Enhanced Communication Module - Client/Server Server Driver The server driver allows the MVI56E-MNETC/MNETCXT module to respond to data read and write commands issued by Clients on the Modbus TCP/IP network. The following illustration describes the flow of data into and out of the module.
  • Page 131 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the server driver. An exception to normal processing is when the pass-through mode is implemented.
  • Page 132 Modbus TCP/IP Client Enhanced Communication Module - Client/Server Client Driver In the Client driver, the MVI56E-MNETC/MNETCXT 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 133 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 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 134: Ethernet Cable Specifications

    1 Rx+ 3 Tx+ 3 Rx+ 6 Tx- 2 Rx- 6 Tx- 6 Rx- 5.3.2 Ethernet Performance Ethernet performance in the MVI56E-MNETC/MNETCXT module can be affected in the following way: Page 134 of 172 ProSoft Technology, Inc. September 20, 2018...

  • Page 135: Modbus Protocol Specification

    Nevertheless, the efficiency, scalability, and low cost of a Modbus TCP/IP network make this an ideal solution for industrial applications. The MVI56E-MNETC/MNETCXT Module module acts as an input/output module between devices on a Modbus TCP/IP network and the Rockwell Automation backplane and processor.

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

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 5.4.2 Read Coil Status (Function Code 01) Query This function allows you to obtain the ON/OFF status of logic coils (Modbus 0x range) used to control discrete outputs from the addressed server only.

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

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual The status of coils 20 to 27 is shown as CD (HEX) = 1100 1101 (Binary). Reading from left to right, this shows that coils 27, 26, 23, 22, and 20 are all on.

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

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Node Func Byte Data Discrete Data Discrete Data Discrete Error Check Address Code Count Input 10197 to Input 10205 to Input 10213 to Field 10204...

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

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Because the server interface device is normally serviced at the end of the controller's scan, the data reflect the register content at the end of the scan.

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

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Because the server interface is normally serviced at the end of the controller's scan, the data reflect the register content at the end of the scan. Each PC limits the quantity of register contents provided each scan;...

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

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Node Function Data Coil Bit Data Coil Bit Data On/Off Data Error Check Address Code High Field (2 bytes) The forcing of a coil via Modbus function 5 happens regardless of whether the addressed coil is disabled or not (In ProSoft products, the coil is only affected if you implement the necessary ladder logic).

  • Page 142: Read Exception Status (Function Code 07)

    Generally, the mode is forced to remove a malfunctioning remote device from the communications system. Sub-function Codes Supported Only Sub-function 00 is supported by the MVI56E-MNETC/MNETCXT Module module. 00 Return Query Data The data passed in the request data field is to be returned (looped back) in the response.
  • Page 143 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Sub-function Data Field (Request) Data Field (Response) 00 00 Echo Request Data Example and State Diagram Here is an example of a request to remote device to Return Query Data. This uses a sub-function code of zero (00 00 hex in the two-byte field).

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

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 5.4.10 Force Multiple Coils (Function Code 15) Query This function forces each coil (Modbus 0x range) in a consecutive block of coils to a desired ON or OFF state. Any coil that exists within the controller can be forced to either state (ON or OFF).

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

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Coils that are not programmed in the controller logic program are not automatically cleared upon power up. Thus, if such a coil is set ON by function code 15 and (even months later) an output is connected to that coil, the output is hot.
  • Page 146 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server  If the server receives the request, but detects a communication error (parity, LRC, CRC, ...), no response is returned. The master program will eventually process a timeout condition for the request.
  • Page 147 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Modbus Exception Codes Code Name Meaning Illegal Function The function code received in the query is not an allowable action for the server. This may be because the function code is only applicable to newer devices, and was not implemented in the unit selected.

  • Page 148: Using The Optional Add-On Instruction

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Using the Optional Add-On Instruction 5.5.1 Before You Begin Make sure that you have installed RSLogix 5000 version 16 (or later). Download the files from www.prosoft-technology.com. Save them to a convenient location in your PC, such as Desktop or My Documents.
  • Page 149 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 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 150: Importing The Optional Add-On Instruction

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 5.5.3 Importing the Optional Add-On Instruction Right-click an empty rung in the main routine of your existing ladder logic and choose I MPORT Page 150 of 172 ProSoft Technology, Inc.
  • Page 151 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Navigate to the folder where you saved MVI56EMNETC_Optional_AddOn_Rung_v1_0.L5X and select the file. In the Import Configuration window, click OK. ProSoft Technology, Inc. Page 151 of 172...
  • Page 152 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server The Add-On Instruction is now visible in the ladder logic. Observe that the procedure has also imported data types and controller tags associated with the Add-On Instruction.
  • Page 153 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual You will notice that new tags have been imported: MVI56MNETCEthernet, MVI56MNETCClock, and four MESSAGE tags. In the Add-On Instruction, click the [...] button next to any MSG tag to open the Message Configuration dialog box.

  • Page 154: Reading The Ethernet Settings From The Module

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Select the module to configure the message path. 5.5.4 Reading the Ethernet Settings from the Module Expand the MVI56EMNETCETHERNET controller tag and move a value of 1 to MVI56EMNETCETHERNET.Read.
  • Page 155 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual The bit will be automatically reset and the current Ethernet settings will be copied to MVI56EMNETCETHERNET controller tag as follows. To check the status of the message, refer to the ReadEthernetMSG tag.

  • Page 156: Writing The Ethernet Settings To The Module

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 5.5.5 Writing the Ethernet Settings to the Module Expand the MVI56EMNETCETHERNET controller tag. Set the new Ethernet configuration in MVI56EMNETCETHERNET.Config: Move a value of 1 to MVI56EMNETCETHERNET.Write.

  • Page 157: Reading The Clock Value From The Module

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual To check the status of the message, refer to the WriteEthernetMSG tag. 5.5.6 Reading the Clock Value from the Module Expand the MVI56EMNETCCLOCK controller tag and move a value of 1 to MVI56EMNETCCLOCK.Read...

  • Page 158: Writing The Clock Value To The Module

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server To check the status of the message, refer to the ReadClockMSG tag. 5.5.7 Writing the Clock Value to the Module Expand the MVI56EMNETCCLOCK controller tag.

  • Page 159: Adding The Module To An Existing Project

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual To check the status of the message, refer to the WriteClockMSG tag. Adding the Module to an Existing Project Select the I/O Configuration folder in the Controller Organization window of RSLogix 5000, and then click the right mouse button to open a shortcut menu.
  • Page 160 Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server This action opens the Select Module dialog box .Enter in the text GENERIC box and select the GENERIC 1756 MODULE. If you're using an earlier version of RSLogix, expand OTHER in the Select Module dialog box, and then select the GENERIC 1756 MODULE.
  • Page 161 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual 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 162: Using The Sample Program

    5.7.1 Opening the Sample Program in RSLogix The sample program for your MVI56E-MNETC/MNETCXT module includes custom tags, data types and ladder logic for data I/O, status and command control. For most applications, you can run the sample program without modification, or, for advanced applications, you can incorporate the sample program into your existing application.
  • Page 163 MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Reference Modbus TCP/IP Client Enhanced Communication Module - Client/Server 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 164: Choosing The Controller Type

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server To open the sample program On the Connected to Go Online dialog box, click the S button. ELECT Choose the sample program file that matches your firmware version, and then click the S button.

  • Page 165: 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-MNETC/MNETCXT slot number for computation. ProSoft Technology, Inc.

  • Page 166: Downloading The Sample Program To The Processor

    Reference MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server 5.7.4 Downloading the Sample Program to the Processor Note: The key switch on the front of the ControlLogix module must be in the REM position.

  • Page 167: Support, Service & Warranty

    Contacting Technical Support ............. 167  Warranty Information ................169 Contacting Technical Support ProSoft Technology, Inc. is committed to providing the most efficient and effective support possible. Before calling, please gather the following information to assist in expediting this process: Product Version Number...
  • Page 168 Support, Service & Warranty MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Asia Pacific Europe / Middle East / Africa Regional Office Regional Office Phone: +60.3.7941.2888 Phone: +33.(0)5.34.36.87.20 asiapc@prosoft-technology.com europe@prosoft-technology.com Languages spoken: Bahasa, Chinese, English,...

  • Page 169: Warranty Information

    Phone: +54.911.4565.8119 scone@prosoft-technology.com Languages spoken: Spanish, English Warranty Information For complete details regarding ProSoft Technology’s TERMS & CONDITIONS OF SALE, WARRANTY, SUPPORT, SERVICE AND RETURN MATERIAL AUTHORIZATION INSTRUCTIONS, please see the documents at: www.prosoft-technology/legal Documentation is subject to change without notice.

  • Page 170: Index

    MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Support, Service & Warranty Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual Contacting Technical Support • 167 Content Disclaimer • 2 Controller Tag Overview • 74 Controller Tags • 71 Index Creating a New RSLogix 5000 Project • 13, 71 Creating the Module •...

  • Page 171: Prosoft Technology, Inc

    Preset Single Register (Function Code 06) • 141 Printing a Configuration File • 34 Product Specifications • 101 Important Safety Information - MVI56E-MNETC • 3 Importing the Add-On Instruction • 18 Importing the Optional Add-On Instruction • 150 Initialize Output Data • 38 Read Block •...

  • Page 172: Prosoft Technology, Inc

    Support, Service & Warranty MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server Upgrading from MVI56-MNETC in ProSoft Configuration Builder • 30 User-Defined Data Types (UDTs) • 73 Using CIPconnect to Connect to the Module • 54, 64, Using Controller Tags •...

This manual is also suitable for:

Mvi56e-mnetcxt

Table of Contents

Save PDF