ProSoft Technology MVI56E-MNETC, MVI56E-MNETCXT User Manual

Download

MVI56E-MNETC/MNETCXT

ControlLogix Platform

Modbus TCP/IP Client Enhanced Communication Module - Client/Server

September 20, 2018

USER MANUAL

Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions, comments, compliments or complaints about our products, documentation, or support, please write or call us.

How to Contact Us

ProSoft Technology, Inc.

+1 (661) 716-5100 +1 (661) 716-5101 (Fax)

www.prosoft-technology.com

support@prosoft-technology.com

MVI56E-MNETC/MNETCXT User Manual

September 20, 2018

ProSoft Technology®, is a registered copyright of ProSoft Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products and services of, their respective owners.

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 our website:

www.prosoft-technology.com

Content Disclaimer

This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. 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. ProSoft Technology makes no warranty or representation as to its accuracy and assumes no liability for and reserves the right to correct such inaccuracies or errors at any time without notice. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.

No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of ProSoft Technology. All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components. When devices are used for applications with technical safety requirements, the relevant instructions must be followed. Failure to use ProSoft Technology software or approved software with our hardware products may result in injury, harm, or improper operating results. Failure to observe this information can result in injury or equipment damage.

Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability. North America: +1 (661) 716-5100

Asia Pacific: +603.7724.2080 Europe, Middle East, Africa: +33 (0) 5.3436.87.20 Latin America: +1.281.298.9109

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.

Warning – Cancer and Reproductive Harm – www.P65Warnings.ca.gov

Important Safety Information

North America Warnings

A This Equipment is Suitable For Use in Class I, Division 2, Groups A, B, C, D or Non-Hazardous Locations Only. B Warning – Explosion Hazard – Substitution of Any Components May Impair Suitability for Class I, Division 2. C Warning – Explosion Hazard – Do Not Disconnect Equipment Unless Power Has Been Switched Off Or The

Area is Known To Be Non-Hazardous.

D The subject devices are powered by a Switch Model Power Supply (SMPS) that has regulated output voltage of

5 VDC.

ATEX/IECEx Warnings and Conditions of Safe Usage:

Power, Input, and Output (I/O) wiring must be in accordance with the authority having jurisdiction.

A Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or wiring modules. B Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is

known to be non-hazardous.

C These products are intended to be mounted in an ATEX/IECEx Certified, tool-secured, IP54 enclosure. The

devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances of more than 40%. This device must be used only with ATEX certified backplanes.

D Before operating the reset switch, be sure the area is known to be non-hazardous. E If the equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment

may be impaired.

Agency Approvals & Certifications

Please visit our website: www.prosoft-technology.com

<Ex> II 3 G Ex nA IIC T4 Gc 0°C <= Ta <= 60°C

-25°C <= Ta <= 70°C (XT models only) II – Equipment intended for above ground use (not for use in mines). 3 – Category 3 equipment, investigated for normal operation only. G – Equipment protected against explosive gasses.

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. The battery itself should last for the life of the module. However, if left in an unpowered state for 14 to 21 days, the battery may become fully discharged and require recharging by being placed in a powered-up ControlLogix chassis. The time required to fully recharge the battery may be as long as 24 hours.

Once it is fully charged, the battery provides backup power for the CMOS setup and the real-time clock for approximately 21 days. Before you remove a module from its power source, ensure that the battery within the module is fully charged (the BATT LED on the front of the module goes OFF when the battery is fully charged). If the battery is allowed to become fully discharged, the module will revert to the default BIOS and clock settings.

Note: The battery is not user-replaceable or serviceable.

Electrical Ratings:

Backplane current load: 800mA @ 5 VDC; 3mA @ 24 VDC

Markings:

DC Voltage symbol

Caution symbol

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Contents Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Contents

Your Feedback Please ........................................................................................................................ 2

How to Contact Us .............................................................................................................................. 2

Content Disclaimer .............................................................................................................................. 2

Important Safety Information ............................................................................................................... 3

Battery Life Advisory ........................................................................................................................... 4

1 Start Here 9

1.1 System Requirements ............................................................................................. 10

1.2 Setting Jumpers ...................................................................................................... 11

1.3 Installing the Module in the Rack ............................................................................ 12

1.4 Creating a New RSLogix 5000 Project .................................................................... 13

1.4.1 Before You Import the Add-On Instruction .............................................................. 14

1.4.2 Creating the Module ................................................................................................ 15

1.4.3 Importing the Add-On Instruction ............................................................................ 18

1.4.4 Adding Multiple Modules (Optional) ........................................................................ 21

1.5 Connecting Your PC to the ControlLogix Processor ............................................... 27

1.6 Downloading the Sample Program to the Processor .............................................. 28

2 MVI56E-MNETC/MNETCXT Configuration 29

2.1 Using ProSoft Configuration Builder Software ........................................................ 29

2.1.1 Installing ProSoft Configuration Builder .................................................................. 29

2.1.2 Upgrading from MVI56-MNETC in ProSoft Configuration Builder .......................... 30

2.1.3 Setting Up the Project ............................................................................................. 30

2.1.4 Setting Module Parameters ..................................................................................... 33

2.1.5 Module ..................................................................................................................... 34

2.1.6 MNET Servers ......................................................................................................... 39

2.1.7 MNET Client x ......................................................................................................... 42

2.1.8 MNET Client x Commands ...................................................................................... 44

2.1.9 Static ARP Table ..................................................................................................... 51

2.1.10 Ethernet Configuration ............................................................................................ 53

2.2 Connecting Your PC to the Module ......................................................................... 54

2.2.1 Using CIPconnect to Connect to the Module .......................................................... 54

2.2.2 Using RSWho to Connect to the Module ................................................................ 64

2.2.3 Connecting Your PC to the Module's Ethernet Port ................................................ 65

2.3 Downloading the Project to the Module .................................................................. 68

3 Using Controller Tags 71

3.1 Controller Tags ........................................................................................................ 71

3.1.1 MVI56E-MNETC Controller Tags ............................................................................ 72

3.2 User-Defined Data Types (UDTs) ........................................................................... 73

3.2.1 MVI56E-MNETC User-Defined Data Types ............................................................ 73

3.3 Controller Tag Overview.......................................................................................... 74

3.3.1 MNETC.DATA ......................................................................................................... 74

3.3.2 MNETC.CONTROL ................................................................................................. 77

3.3.3 MNETC.STATUS .................................................................................................... 78

3.3.4 MNETC.UTIL ........................................................................................................... 78

ProSoft Technology, Inc. Page 5 of 172 September 20, 2018

Contents MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

4 Diagnostics and Troubleshooting 81

4.1 Ethernet LED Indicators .......................................................................................... 81

4.1.1 Scrolling LED Status Indicators .............................................................................. 82

4.1.2 Non-Scrolling LED Status Indicators ...................................................................... 83

4.2 Clearing a Fault Condition ...................................................................................... 83

4.3 Troubleshooting the LEDs ...................................................................................... 84

4.4 Using the Diagnostics Menu in ProSoft Configuration Builder ............................... 85

4.4.1 The Diagnostics Menu ............................................................................................ 88

4.4.2 Monitoring Module Information ............................................................................... 89

4.4.3 Monitoring Backplane Information .......................................................................... 90

4.4.4 Monitoring Database Information............................................................................ 90

4.4.5 Monitoring MNETC Server Information .................................................................. 91

4.4.6 Monitoring MNET Client Information....................................................................... 92

4.5 Reading Status Data from the Module ................................................................... 92

4.5.1 Status Data Definition ............................................................................................. 93

4.5.2 Configuration Error Word ........................................................................................ 96

4.5.3 Client Command Errors .......................................................................................... 96

4.6 Connecting to the Module's Web Page .................................................................. 98

5 Reference 101

5.1 Product Specifications .......................................................................................... 101

5.1.1 General Specifications .......................................................................................... 101

5.1.2 Functional Specifications ...................................................................................... 102

5.1.3 Hardware Specifications ....................................................................................... 102

5.2 Functional Overview ............................................................................................. 103

5.2.1 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

5.3 Ethernet Cable Specifications ............................................................................... 134

5.3.1 Ethernet Cable Configuration ............................................................................... 134

5.3.2 Ethernet Performance ........................................................................................... 134

5.4 Modbus Protocol Specification ............................................................................. 135

5.4.1 About the Modbus Protocol .................................................................................. 135

5.4.2 Read Coil Status (Function Code 01) ................................................................... 136

5.4.3 Read Input Status (Function Code 02) ................................................................. 137

5.4.4 Read Holding Registers (Function Code 03) ........................................................ 138

5.4.5 Read Input Registers (Function Code 04) ............................................................ 139

5.4.6 Force Single Coil (Function Code 05) .................................................................. 140

5.4.7 Preset Single Register (Function Code 06) .......................................................... 141

5.4.8 Read Exception Status (Function Code 07) ......................................................... 142

5.4.9 Diagnostics (Function Code 08) ........................................................................... 142

5.4.10 Force Multiple Coils (Function Code 15) .............................................................. 144

5.4.11 Preset Multiple Registers (Function Code 16) ...................................................... 145

5.4.12 Modbus Exception Responses ............................................................................. 145

5.5 Using the Optional Add-On Instruction ................................................................. 148

5.5.1 Before You Begin .................................................................................................. 148

5.5.2 Overview ............................................................................................................... 148

5.5.3 Importing the Optional Add-On Instruction ........................................................... 150

5.5.4 Reading the Ethernet Settings from the Module................................................... 154

5.5.5 Writing the Ethernet Settings to the Module ......................................................... 156

Page 6 of 172 ProSoft Technology, Inc. September 20, 2018

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

5.6 Adding the Module to an Existing Project ............................................................. 159

5.7 Using the Sample Program ................................................................................... 162

5.7.1 Opening the Sample Program in RSLogix ............................................................ 162

5.7.2 Choosing the Controller Type ............................................................................... 164

5.7.3 Selecting the Slot Number for the Module ............................................................ 165

5.7.4 Downloading the Sample Program to the Processor ............................................ 166

5.7.5 Adding the Sample Ladder to an Existing Application .......................................... 166

6 Support, Service & Warranty 167

6.1 Contacting Technical Support ............................................................................... 167

6.2 Warranty Information ............................................................................................. 169

Index 170

ProSoft Technology, Inc. Page 7 of 172 September 20, 2018

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

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here

In This Chapter

 System Requirements ........................................................................... 10

 Setting Jumpers .................................................................................... 10

 Installing the Module in the Rack ........................................................... 12

 Creating a New RSLogix 5000 Project .................................................. 13

 Connecting Your PC to the ControlLogix Processor .............................. 27

 Downloading the Sample Program to the Processor ............................. 28

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1 Start Here

To get the most benefit from this User Manual, you should have the following skills:

 Rockwell Automation® RSLogix™ software: launch the program, configure

ladder logic, and transfer the ladder logic to the processor

 Microsoft Windows®: install and launch programs, execute menu

commands, navigate dialog boxes, and enter data

 Hardware installation and wiring: install the module, and safely connect

Modbus TCP/IP and ControlLogix devices to a power source and to the MVI56E-MNETC/MNETCXT module’s application port(s)

ProSoft Technology, Inc. Page 9 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

1.1 System Requirements

The MVI56E-MNETC/MNETCXT module requires the following minimum hardware and software components:

 Rockwell Automation ControlLogix® processor (firmware version 10 or higher)

with compatible limited voltage power supply and one free slot in the rack for the MVI56E-MNETC/MNETCXT module. The module requires 800mA of available 5 VDC and 3 mA of available 24 VDC power.

 Rockwell Automation RSLogix 5000 programming software

o Version 16 or higher required for Add-On Instruction o Version 15 or lower must use Sample Ladder, available from

www.prosoft-technology.com

 Rockwell Automation RSLinx® communication software version 2.51 or higher  ProSoft Configuration Builder (PCB) (included)  Pentium® II 450 MHz minimum. Pentium III 733 MHz (or better)

recommended

 Supported operating systems:

o Microsoft Windows o Microsoft Windows XP Professional with Service Pack 1 or 2 o Microsoft Windows 7 Professional (32-or 64-bit) o Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3 o Microsoft Windows Server 2003

 128 Mbytes of RAM minimum, 256 Mbytes of RAM recommended  100 Mbytes of free hard disk space (or more based on application

requirements)

 256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color

1024  768 recommended)

Vista

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 applications may have different minimum requirements. Refer to the documentation for any third party applications for system requirements.

Note: You can install the module in a local or remote rack. For remote rack installation, the module requires EtherNet/IP or ControlNet communication with the processor.

Page 10 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1.2 Setting Jumpers

The Setup Jumper acts as "write protection" for the module’s firmware. In "write protected" mode, the Setup pins are not connected, and the module’s firmware

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

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. That way, you can update the module’s firmware without requiring physical access to

the module.

Security considerations:

Leaving the Setup pin jumpered leaves the module open to unexpected firmware updates.

You should consider segmenting the data flow for security reasons. Per IEC 62443-1-1, you should align with IEC 62443 and implement segmentation of the control system. Relevant capabilities are firewalls, unidirectional communication, DMZ. Oil and Gas customers should also see DNVGL-RPG108 for guidance on partitioning.

You should practice security by design, per IEC 62443-4-1, including layers of security and detection. The module relies on overall network security design, as it is only one component of what should be a defined zone or subnet.

ProSoft Technology, Inc. Page 11 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

1.3 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. Failure to follow safety procedures could result in damage to hardware or data, or even serious injury or death to personnel. Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device.

After you have checked the placement of the jumpers, insert the MVI56EMNETC/MNETCXT into the ControlLogix chassis. Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules.

Warning: When you insert or remove the module while backplane power is on, an electrical arc can occur. An electrical arc can cause personal injury or property damage by sending an erroneous signal to the system’s actuators. This can cause unintended machine motion or loss of process control. Electrical arcs may also cause an explosion when they happen in a hazardous environment. Verify that power is removed or the area is non-hazardous before proceeding.

Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation.

1 Align the module with the top and bottom guides, and then slide it into the

rack until the module is firmly against the backplane connector.

2 With a firm, steady push, snap the module into place. 3 Check that the holding clips on the top and bottom of the module are securely

in the locking holes of the rack.

Page 12 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4 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.

5 Turn power ON.

Note: If you insert the module improperly, the system may stop working or may behave unpredictably.

Note: When using the XT version (if applicable), you must use the 1756-A5XT or 1756-A7LXT chassis to uphold the XT specifications. In these chassis, modules are spaced further apart than in standard ControlLogix chassis. Blank spacers are inserted between active modules.

1.4 Creating a New RSLogix 5000 Project

1 Open the FILE menu, and then choose NEW.

2 Select your ControlLogix controller model. 3 Select the REVISION of your controller. Depending on the revision, there may

be some small differences in the appearance of dialog boxes from the ones shown.

4 Enter a name for your controller, such as My_Controller. 5 Select your ControlLogix chassis type. 6 Select SLOT 0 for the controller. 7 Click OK.

ProSoft Technology, Inc. Page 13 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

File Name

Description

MVI56EMNETC_AddOn_Rung_v1_x.L5X. A newer version may be available at:

www.prosoft-technology.com

L5X file containing Add-On Instruction, user defined data types, controller tags and ladder logic required to configure the MVI56E-MNETC/MNETCXT module

MVI56EMNETC_Optional_AddOn_Rung_v1_x.L5X. A newer version may be available at:

www.prosoft-technology.com

Optional L5X file containing additional AddOn Instruction with logic for changing Ethernet configuration and clock settings.

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

1.4.1 Before You Import the Add-On Instruction

Note: This section only applies if your processor is using RSLogix 5000 version 16 or higher. If you have an earlier version, please see Using the Sample Program (page 162).

Two Add-On Instructions are provided for the MVI56E-MNETC/MNETCXT module. The first is required for setting up the module; the second is optional.

Download the files from www.prosoft-technology.com. Save them to a convenient location in your PC, such as Desktop or My Documents.

About the Optional Add-On Instruction

The Optional Add-On Instruction performs the following tasks:  Read/Write Ethernet Configuration

Allows the processor to read or write the module IP address, subnet mask, and network gateway IP address.

 Read/Write Module Clock Value

Allows the processor to read and write the module clock settings. The module's free-running clock also stores the last time that the Ethernet configuration was changed or the last time the module was restarted or rebooted. The date and time of the last change or restart is displayed on the scrolling LED during module power-up/start-up sequence.

For more information, see Using the Optional Add-On Instruction (page 148).

Note: You can also set the date and time from the module's web page. See Connecting to the 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. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1.4.2 Creating the Module

1 Add the MVI56E-MNETC/MNETCXT module to the project.

In the CONTROLLER ORGANIZATION window, select I/O CONFIGURATION and click the right mouse button to open a shortcut menu. On the shortcut menu, choose NEW MODULE...

This action opens the SELECT MODULE dialog box. Enter generic in the text box and select the GENERIC 1756 MODULE. If you're using a controller revision of 16 or less, expand OTHER in the SELECT MODULE dialog box, and then select the GENERIC 1756 MODULE.

ProSoft Technology, Inc. Page 15 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Parameter

Value

NAME

Enter a module identification string. Example: MNETC

DESCRIPTION

Enter a description for the module. Example: Modbus TCP/IP Client Enhanced Communication Module - Client/Server

COMM FORMAT

Select DATA-INT

SLOT

Enter the slot number in the rack where the MVI56EMNETC/MNETCXT module is located

INPUT ASSEMBLY INSTANCE

INPUT SIZE

250

OUTPUT ASSEMBLY INSTANCE

OUTPUT SIZE

248

CONFIGURATION ASSEMBLY INSTANCE

CONFIGURATION SIZE

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

2 Click CREATE. This action opens the NEW MODULE dialog box.

3 In the NEW MODULE dialog box, enter the following values.

Important: You must select the COMM FORMAT as DATA - INT in the dialog box, otherwise the module will not communicate over the backplane of the ControlLogix rack.

4 Click OK to continue.

Page 16 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

5 Edit the Module Properties. Select the REQUESTED PACKET INTERVAL value

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. The default value is 5 milliseconds. Values between 1 and 10 milliseconds should work with most applications.

6 Click OK to save the module and close the dialog box. Notice that the module

now appears in the CONTROLLER ORGANIZATION window.

ProSoft Technology, Inc. Page 17 of 172 September 20, 2018

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

1 In the CONTROLLER ORGANIZATION window, expand the TASKS folder and

subfolders until you reach the MAINPROGRAM folder.

2 In the MAINPROGRAM folder, double-click to open the MAINROUTINE ladder. 3 Select an empty rung in the routine, and then click the right mouse button to

open a shortcut menu. On the shortcut menu, choose IMPORT RUNGS…

Page 18 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4 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 IMPORT CONFIGURATION dialog box. Click TAGS under MAINROUTINE to show the controller tags that will be created. Note that if you are using a controller revision number of 16 or less, the IMPORT CONFIGURATION dialog box does not show the IMPORT CONTENT tree.

ProSoft Technology, Inc. Page 19 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

5 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 the text in the FINAL NAME column (NAME column for controller revision 16 or less). For example, if your module is located in slot 3, change Local:1:I in the above picture to Local:3:I. Do the same for Local:1:O. If your module is located in Slot 1 of the local rack, this step is not required.

6 Click OK to confirm the import.

When the import is completed, the new rung with the Add-On Instruction appears as shown in the following illustration.

The procedure also imports the new User Defined Data Types, Controller Tags, and the Add-On instruction for your project.

7 Save the application and then download the sample ladder logic to the

processor.

Page 20 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here 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.

1 In the I/O CONFIGURATION folder, click the right mouse button to open a

shortcut menu, and then choose NEW MODULE.

2 Select 1756-MODULE. If you're using a controller revision of 16 or less,

expand OTHER in the SELECT MODULE dialog box, and then select the 1756- MODULE.

ProSoft Technology, Inc. Page 21 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Parameter

Value

NAME

Enter a module identification string. Example: MNETC_2.

DESCRIPTION

Enter a description for the module. Example: ProSoft Modbus TCP/IP Enhanced Communication Module.

COMM FORMAT

Select DATA-INT.

SLOT

Enter the slot number in the rack where the MVI56EMNETC/MNETCXT module is located.

INPUT ASSEMBLY INSTANCE

INPUT SIZE

250

OUTPUT ASSEMBLY INSTANCE

OUTPUT SIZE

248

CONFIGURATION ASSEMBLY INSTANCE

CONFIGURATION SIZE

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

3 Fill the module properties as follows:

4 Click OK to confirm. The new module is now visible:

5 Expand the TASKS folder, and then expand the MAINTASK folder. 6 In the MAINPROGRAM folder, double-click to open the MAINROUTINE ladder.

Page 22 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

7 Select an empty rung in the routine, and then click the right mouse button to

open a shortcut menu. On the shortcut menu, choose IMPORT RUNGS…

8 Select the .L5X file, and then click IMPORT.

ProSoft Technology, Inc. Page 23 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

9 This action opens the IMPORT CONFIGURATION window. Click TAGS under

MAINROUTINE to show the tags that will be imported.

10 Associate the I/O connection variables to the correct module. The default

values are Local:1:I and Local:1:O so you may have to edit the FINAL NAME field to change the values. You can also click the drop-down arrow to select the correct name.

Page 24 of 172 ProSoft Technology, Inc. September 20, 2018

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.

ProSoft Technology, Inc. Page 25 of 172 September 20, 2018

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. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Start Here Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1.5 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.

Note: It is not mandatory that you use the processor's serial interface. You may access the processor through any network interface is available on your system. Refer to your Rockwell Automation documentation for information on other connection methods.

1 Connect the right-angle connector end of the cable to your controller at the

communications port.

2 Connect the straight connector end of the cable to the serial port on your

computer.

ProSoft Technology, Inc. Page 27 of 172 September 20, 2018

Start Here MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

1.6 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.

1 If you are not already online with the processor, in RSLogix 5000 open the

Communications menu, and then choose DOWNLOAD. RSLogix 5000 will establish communication with the processor. You do not have to download through the processor's serial port, as shown here. You may download through any available network connection.

2 When communication is established, RSLogix 5000 will open a confirmation

dialog box. Click the DOWNLOAD button to transfer the sample program to the processor.

3 RSLogix 5000 will compile the program and transfer it to the processor. This

process may take a few minutes.

4 When the download is complete, RSLogix 5000 will open another

confirmation dialog box. If the key switch is in the REM position, click OK to switch the processor from PROGRAM mode to RUN mode.

Note: If you receive an error message during these steps, refer to your RSLogix documentation to interpret and correct the error.

Page 28 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration

In This Chapter

 Using ProSoft Configuration Builder Software ....................................... 29

 Connecting Your PC to the Module ....................................................... 54

 Downloading the Project to the Module ................................................. 68

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

2 MVI56E-MNETC/MNETCXT Configuration

2.1 Using ProSoft Configuration Builder Software

ProSoft Configuration Builder (PCB) provides a quick and easy way to manage module configuration files customized to meet your application needs. PCB is not only a powerful solution for new configuration files, but also allows you to import information from previously installed (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.

2.1.1 Installing ProSoft Configuration Builder

Use the ProSoft Configuration Builder (PCB) software to configure the module. You can find the latest version of the ProSoft Configuration Builder (PCB) on our web site: www.prosoft-technology.com. The installation filename contains the PCB version number. For example, PCB_4.3.4.5.0238.EXE.

If you are installing PCB from the ProSoft website:

1 Open a browser window and navigate to www.prosoft-technology.com. 2 Perform a search for 'pcb' in the Search bar. Click on the ProSoft

Configuration Builder search result.

3 On the PCB page, click the download link for ProSoft Configuration Builder,

and save the file to your Windows desktop.

4 After the download completes, double-click the file to install. If you are using

Windows 7, right-click the PCB installation file and then choose RUN AS

ADMINISTRATOR. Follow the instructions that appear on the screen.

5 If you want to find additional software specific to your MVI56E-

MNETC/MNETCXT, enter the model number into the ProSoft website search box and press the ENTER key.

ProSoft Technology, Inc. Page 29 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual 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 MVI56MNETC 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.

ProSoft Configuration Builder version 2.2.2 or later has an upgrade option that easily performs this conversion, while preserving all your configuration settings and any name you may have given your module.

Important: For this procedure, ProSoft Configuration Builder version 2.2.2 or later must be installed on your PC. You can download the latest version from www.prosoft-technology.com.

1 In ProSoft Configuration Builder's tree view, click the MODULE icon and right-

click to open a shortcut menu.

2 On the shortcut menu, select CHANGE MODULE TYPE TO MVI56E-MNETC.

2.1.3 Setting Up the Project

To begin, start PROSOFT CONFIGURATION BUILDER (PCB).

Page 30 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

If you have used other Windows configuration tools before, you will find the screen layout familiar. PCB’s window consists of a tree view on the left, and an information pane and a configuration pane on the right side of the window. When you first start PCB, the tree view consists of folders for Default Project and 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 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

1 Right-click DEFAULT MODULE in the tree view and then choose CHOOSE

MODULE TYPE. This opens the Choose Module Type dialog box.

2 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 32 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

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.

Renaming an Object

1 Right-click the object and then choose RENAME. 2 Type the name to assign to the object. 3 Click away from the object to save the new name.

Configuring Module Parameters

1 Click the [+] sign next to the module icon to expand module information. 2 Click the [+] sign next to any icon to view module information and

configuration options.

3 Double-click any icon to open an Edit dialog box. 4 To edit a parameter, select the parameter in the left pane and make your

changes in the right pane.

5 Click OK to save your changes.

ProSoft Technology, Inc. Page 33 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Printing a Configuration File

1 In the main PCB window, right-click the MVI56E-MNETC/MNETCXT MODULE

icon and then choose VIEW CONFIGURATION.

2 In the View Configuration dialog box, click the FILE menu and then click

PRINT.

3 In the Print dialog box, choose the printer to use from the drop-down list,

select the printing options, and then click OK.

2.1.5 Module

This section of the configuration describes the database setup and module-level parameters.

Adjust the Input and Output Array Sizes (Optional)

Tip: If you have not installed ProSoft Configuration Builder, see Installing ProSoft Configuration Builder (page 29).

The module internal database is divided into two user-configurable areas:

 Read Data  Write Data.

The Read Data area is moved from the module to the processor, while the Write Data area is moved from the processor to the module. You can configure the start register and size of each area. The size of each area you configure must match the Add-On instruction controller tag array sizes for the READDATA and WRITEDATA arrays.

The MVI56E-MNETC/MNETCXT sample program is configured for 600 registers of READDATA and 600 registers of WRITEDATA, which is sufficient for most application. This topic describes how to configure user data for applications requiring more than 600 registers of ReadData and WriteData. In this example, we will expand both the Read and Write Data sizes to 1000.

Important: Because the module pages data in blocks of 200 registers at a time, you must configure your user data in multiples of 200 registers.

Caution: When you change the array size, RSLogix may reset the MNETC tag values to zero. To avoid data loss, be sure to save your settings before continuing.

Page 34 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1 In the CONTROLLER ORGANIZATION window, expand the DATA TYPES and

USER-DEFINED folders, and then double-click MNETCDATA. This action

opens an edit window for the MNETCDATA data type.

2 In the edit window, change the value of the READDATA array from INT[600] to

INT[1000] as shown, and then click APPLY.

Note: If RSLogix resets your data values, refer to the backup copy of your program to re-enter your configuration parameters.

3 Next, navigate to CONTROLLER TAGS and double click to open an edit

window. Click the MONITOR TAGS tab at the bottom of the edit window. You execute the rest of the steps in ProSoft Configuration Builder.

4 Start ProSoft Configuration Builder. 5 Double-click the MVI56E-MNETC icon to expand the menu for the module in

PCB.

6 Click the [+] icon next to the MODULE icon to expand the Module menu.

ProSoft Technology, Inc. Page 35 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

7 Double-click the MODULE icon to open up the Edit - Module dialog box.

8 Click READ REGISTER COUNT and change the value from 600 to 1000. 9 Click OK to close the dialog box. 10 Save and Downloading the Project to the Module (page 68) and reboot.

To modify the WRITEDATA array, follow the above steps, but substitute:

 WRITEDATA for ReadData in RSLogix.  WRITE REGISTER COUNT for Read Register Count in PCB.

Note: make sure that the READDATA and WRITEDATA arrays do not overlap in the module memory. For example, if your application requires 2000 words of WriteData starting at register 0, then your WRITE REGISTER START in PCB must be set to a value of 2000 or greater.

Backplane Error/Status Pointer

-1 to 9955

This parameter sets the address in the internal database where the backplane error/status data will be placed. If you want the error/status data to be moved to the processor and placed into the ReadData array, the value entered should be a module memory address in the Read Data area. If the value is set to -1, the error/status data will not be stored in the module's internal database and will not be transferred to the processor's ReadData array.

Enabling the Error/Status Pointer is optional. The error/status data is routinely returned as part of the input image, which is continually being transferred from the module to the processor. For more information, see Normal Data Transfer Blocks (page 106).

Page 36 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Read Register Start

0 to 9999 The Read Register Start parameter specifies the start of the Read Data area in

module memory. Data in this area will be transferred from the module to the processor.

The total user database memory space is limited to the first 10,000 registers of module memory, addresses 0 through 9999. Therefore, the practical limit for this parameter is 9999 minus the value entered for Read Register Count, so that the Read Data Area does not try to extend above address 9999. Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap.

Note: To take advantage of the new features described above, your MVI56EMNETC/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.

Read Register Count

0 to 10000 The Read Register Count parameter specifies the size of the Read Data area of

module memory and the number of registers to transfer from this area to the processor, up to a maximum of 10,000 words.

Note: Total Read Register Count and Write Register Count cannot exceed 10,000 total registers. Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap.

Write Register Start

0 to 9999 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.

Note: Total user database memory space is limited to the first 10,000 registers of module memory, addresses 0 through 9999. Therefore, the practical limit for this parameter is 9999 minus the value entered for Write Register Count, so that the Write Data Area does not try to extend above address

9999. Read Data and Write Data Areas must be configured to occupy separate address ranges in module memory and should not be allowed to overlap.

ProSoft Technology, Inc. Page 37 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Write Register Count

0 to 10000 The Write Register Count parameter specifies the size of the Write Data area of

module memory and the number of registers to transfer from the processor to this memory area, up to a maximum value of 10,000 words.

Failure Flag Count

If this value is greater than zero the protocol communication will be interrupted once a backplane failure is detected, or communication with the processor fails. A value of zero will disable this feature.

Initialize Output Data

0 = No, 1 = Yes This parameter is used to determine if the output data for the module should be

initialized with values from the processor. If the value is set to 0, the output data will be initialized to 0. If the value is set to 1, the data will be initialized with data from the processor. Use of this option requires associated ladder logic to pass the data from the processor to the module.

Pass-Through Mode

0, 1, 2 or 3 This parameter specifies the pass-through mode for write messages received by

the MNET and MBAP server ports.  If the parameter is set to 0, all write messages will be placed in the module’s

virtual database.

 If a value of 1 is entered, write messages received will be sent to the

processor as unformatted messages.

 If a value of 2 is entered, write messages received will be sent to the

processor as formatted messages.

 If a value of 3 is entered, write messages received will be sent to the

processor with the bytes swapped in a formatted message.

Page 38 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

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.

 Value = 1: Half duplex, 10 MB speed  Value = 2: Full duplex, 10 MB speed  Value = 3: Half duplex, 100 MB speed  Value = 4: Full duplex, 100 MB speed  Value = 0: Auto-negotiate

Auto-negotiate is the default value for backward compatibility. This feature is not implemented in older software revisions.

2.1.6 MNET Servers

This section contains database offset information used by the server when accessed by external Clients. These offsets can be utilized to segment the database by data type.

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 AddOn Instruction needs to be version 1.8 or higher. Earlier versions have no server capabilities and support only up to 5000 user database registers.

ProSoft Technology, Inc. Page 39 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Enron-Daniels

YES or NO 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.

If the remote master expects to receive or will send one complete 32-bit floatingpoint value for each count of one (1), then set this parameter to YES. When set to YES, the Slave driver will return values from two consecutive 16-bit internal memory registers (32 total bits) for each count in the read command, or receive 32-bits per count from the master for write commands. Example: Count = 10, Slave driver will send 20 16-bit registers for 10 total 32-bit floating-point values.

If, however, the remote master sends a count of two (2) for each 32-bit floatingpoint value it expects to receive or send, or, if you do not plan to use floatingpoint data in your application, then set this parameter to NO, which is the default setting.

You will also need to set the Enron-Daniels Float Start and Enron-Daniels Float Offset parameters to appropriate values whenever the Enron-Daniels parameter is set to YES.

Float Start

0 TO 65535 Whenever the Enron-Daniels parameter is set to YES, this parameter determines

the lowest Modbus Address, received in commands from a remote master, to consider as requests to read or write floating-point data. All commands with address values greater than or equal to this value will be considered floatingpoint data requests. All commands with address values less than this value will be considered normal 16-bit register data requests.

This parameter is used only if the Enron-Daniels parameter is set to YES. For example, if a value of 7000 is entered, all commands received with addresses of 47001 (or 407001) and above will be considered as requests for floating-point data and 32-bits of data will be returned for each count of one in the command.

You will also need to set the Enron-Daniels Float Offset parameter to an appropriate value whenever the Enron-Daniels parameter is set to YES.

Enron-Daniels Float Offset

0 to 9999 This parameter defines the start register for floating-point data in the internal

database. This parameter is used only if the Enron-Daniels parameter is enabled. For example, if the Float Offset value is set to 3000 and the float start parameter is set to 7000, data requests for register 7000 will use the internal Modbus register 3000.

Page 40 of 172 ProSoft Technology, Inc. September 20, 2018

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. For example, if the Output Offset value is set to 3000, data requests for Modbus Coil Register address 00001 will use the internal database register 3000, bit 0. If the Output Offset value is set to 3000, data requests for Modbus Coil register address 00016 will use the internal database register 3000, bit 15. Function codes affected are 1, 5, and 15.

Bit Input Offset

0 to 9999 This parameter defines the start register for Modbus command data in the

internal database. This parameter is enabled when a value greater than 0 is set. For example, if the Bit Input Offset value is set to 3000, data requests for Modbus Input Register address 10001 will use the internal database register 3000, bit 0. If the Bit Input Offset is set to 3000, data requests for Modbus Coil register address 10016 will use the internal database register 3000, bit 15. Function code 2 is affected.

Holding Register 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. For example, if the Holding Register Offset value is set to 4000, data requests for Modbus Word register 40001 will use the internal database register 4000. Function codes affected are 3, 6, 16, & 23.

Word Input Offset

0 to 9999 This parameter defines the start register for Modbus Command data in the

internal database. This parameter is enabled when a value greater than 0 is set. For example, if the Word Input Offset value is set to 4000, data requests for Modbus Word register address 30001 will use the internal database register

4000. Function code 4 is affected.

Connection Timeout

0 to 1200 seconds Thhe number of seconds the server will wait to receive new data. If the server

does not receive any new data during this time, it will close the connection.

Error/Status Pointer

-1 to 9980 seconds This is the database offset for MBAP and MNET server status data.

ProSoft Technology, Inc. Page 41 of 172 September 20, 2018

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. If you want the error/status data to be moved to the processor and placed into the ReadData array, the value entered should be a module memory address in the Read Data area. If the value is set to -1, the error/status data will not be stored in the module's internal database and will not be transferred to the processor's ReadData array.

Enabling the Error/Status Pointer is optional. Alternatively, the error/status data for a specific Client can be requested by the processor and returned in a special Client Status block. For more information, see Client Status Blocks (3000 to

3029) (page 114).

Command Error Pointer

-1 to 9984

This parameter sets the address in the internal database where the Command Error List data will be placed. If you want the Command Error List data to be moved to the processor and placed into the ReadData array, the value entered should be a module memory address in the Read Data area. If the value is set to

-1, the Command Error List data will not be stored in the module's internal

database and will not be transferred to the processor's ReadData array. Enabling the Command Error Pointer is optional. Alternatively, the Command

Error List data for a specific Client can be requested by the processor and returned in a special Client Status block. For more information, see Client Status Blocks (3000 to 3029) (page 114).

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" commands on the network. This parameter does not affect retries of a command as they will be issued when failure is recognized.

Response Timeout

0 to 65535 milliseconds This is the time in milliseconds that a Client will wait before re-transmitting a

command if no response is received from the addressed server. The value to use depends on the type of communication network used, and the expected response time of the slowest device on the network.

Page 42 of 172 ProSoft Technology, Inc. September 20, 2018

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

YES or NO This flag specifies how the Client driver will issue Function Code 3, 6, and 16

commands (read and write Holding Registers) to a remote server when it is moving 32-bit floating-point data.

If the remote server expects to receive or will send one complete 32-bit floatingpoint value for each count of one (1), then set this parameter to YES. When set to YES, the Client driver will send values from two consecutive 16-bit internal memory registers (32 total bits) for each count in a write command, or receive 32 bits per count from the server for read commands. Example: Count = 10, Client driver will send 20 16-bit registers for 10 total 32-bit floating-point values.

If, however, the remote server expects to use a count of two (2) for each 32-bit floating-point value it sends or receives, or if you do not plan to use floating-point data in your application, then set this parameter to NO, which is the default setting.

You will also need to set the Enron-Daniels Float Start and Enron-Daniels Float Offset parameters to appropriate values whenever the Enron-Daniels parameter is set to YES.

Enron-Daniels Float Start

0 to 65535 Whenever the Enron-Daniels parameter is set to YES, this parameter determines

the lowest Modbus Address, used in commands to a remote server, to consider as commands to read or write floating-point data. All commands with address values greater than or equal to this value will be considered floating-point data commands. All commands with address values less than this value will be considered normal 16-bit register data commands.

This parameter is used only if the Enron-Daniels is set to YES. 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.

You will also need to set the Enron-Daniels Float Offset parameter to an appropriate value whenever the Enron-Daniels parameter is set to YES.

ProSoft Technology, Inc. Page 43 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Enron-Daniels Float Offset

0 to 9999 This parameter defines the start register for floating-point data in the internal

database. This parameter is used only if the Enron-Daniels is enabled. For example, if the Enron-Daniels Float Offset value is set to 3000 and the Enron- Daniels Float Start parameter is set to 7000, data requests for register 7000 will use the internal Modbus register 3000.

ARP Timeout

1 to 60 This parameter specifies the number of seconds to wait for an ARP reply after a

request is issued.

Command Error Delay

0 to 300 This parameter specifies the number of 100 millisecond intervals to turn off a

command in the error list after an error is recognized for the command. If this parameter is set to 0, there will be no delay.

MBAP Port Override

YES or NO If this parameter is set to YES, all messages generated by the Client driver will be

MBAP format messages to all Service Port values. If this parameter is set to NO (default value), or is omitted from the configuration

file, all messages sent to Service Port 502 will be MBAP format messages, and all other Service Ports values will use the encapsulated Modbus message format (MNET).

Each Client is configured independently in the configuration file. This parameter applies to firmware version 1.05 and above. For downward

compatibility, you may omit this parameter from the Client's configuration.

2.1.8 MNET Client x Commands

The MNET Client x Commands section of the configuration sets the Modbus TCP/IP Client command list. This command list polls Modbus TCP/IP server devices attached to the Modbus TCP/IP Client port. The module supports numerous commands. This permits the module to interface with a wide variety of Modbus TCP/IP protocol devices.

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 44 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration

Function Code

Definition

Supported in Client

Supported in Server

Read Coil Status

Read Input Status

X X 3

Read Holding Registers

Read Input Registers

X X 5

Force (Write) Single Coil

Preset (Write) Single Register

Read Exception Status

Diagnostics

X 15

Force (Write) Multiple Coils

Preset (Write) Multiple Registers

X X 22

Mask Write 4X

Read/Write

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 be addressed, the function to be performed (read or write), the data area in the device to interface with, and the registers in the internal database to be associated with the device data. The Client command list supports up to 16 commands.

The command list is processed from top (command #1) to bottom. A poll interval parameter is associated with each command to specify a minimum delay time in tenths of a second between the issuances of a command. If the user specifies a value of 10 for the parameter, the command will be executed no more frequently than every 1 second.

NOTE: If you are using only Event Commands or issuing commands from the Command List using Command Control from ladder logic, it is likely that the module will not leave any inactive TCP/IP socket connections open for more than 60-seconds. To maintain an open socket connection, your configuration or application must be designed so that at least one command is issued to each server connection at less than 60-second intervals. The 60-second connection timeout is not userconfigurable and was put in place to prevent long delays between commands.

Commands Supported by the Module

The format of each command in the list depends on the Modbus Function Code being executed.

The following table lists the functions supported by the module.

ProSoft Technology, Inc. Page 45 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

1 2 3 4 5 6 7 8 9

Enable Code

Internal Address

Poll Interval Time

Count

Swap Code

IP Address

Serv Port

Slave Node

Function Code

Device Modbus Address

Code

1/10th Seconds

Bit Count

IP Address

Port #

Address

Read Coil (0x)

Code

1/10th Seconds

Bit Count

IP Address

Port #

Address

Read Input (1x)

Code

1/10th Seconds

Word Count

Code

IP Address

Port #

Address

Read Holding Registers (4x)

Code

1/10th Seconds

Word Count

IP Address

Port #

Address

Read Input Registers (3x)

Code

1 bit

1/10th Seconds

Bit Count

IP Address

Port #

Address

Force (Write) Single Coil (0x)

Code

1 bit

1/10th Seconds

Word Count

IP Address

Port #

Address

Preset (Write) Single Register (4x)

Code

1/10th Seconds

Bit Count

IP Address

Port #

Address

Force (Write) Multiple Coil (0x)

Code

1/10th Seconds

Word Count

IP Address

Port #

Address

Preset (Write) Multiple Register (4x)

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Each command list record has the same general format. The first part of the record contains the information relating to the communication module and the second part contains information required to interface to the Modbus TCP/IP server device.

Command Entry Formats

The following table shows the structure of the configuration data necessary for each of the supported commands.

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. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration

Value

Description

NO (0)

The command is disabled and will not be executed in the normal polling sequence.

YES (1)

The command is executed each scan of the command list if the Poll Interval Time is set to zero (0). If the Poll Interval time is set, the command will be executed when the interval timer expires.

CONDITIONAL (2)

For function codes 5, 15, 6, or 16; data will be sent to the target device only when the data to be written has been changed. This applies only to write commands.

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Command list example:

Enable

NO (0) or YES (1) This field defines whether or not the command is to be executed.

Important: The commands must also be enabled in the ladder logic in order for them to be executed. The MNETC.CONTROL.CmdControl.WriteCmdBits[x] controller tag array holds 16- command bit arrays for each Client. If a bit for a specific command is set to zero (0) in the WriteCmdBits[x] controller tag, the command will not be executed, regardless of its enabled or disabled state in the configuration. For more information, see Command Control Blocks (page

121).

ProSoft Technology, Inc. Page 47 of 172 September 20, 2018

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) or 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. The database address is interpreted as a bit address or a 16-bit word (register) address, depending on the Modbus Function Code used in the command.

 For Modbus functions 1, 2, 5, and 15, this parameter is interpreted as a bit-

level address.

 For Modbus functions 3, 4, 6, and 16, this parameter is interpreted as a word-

level or register-level address.

Poll Interval

0 to 65535 This parameter specifies the minimum interval between issuances of a command

during continuous command execution (Enable code of 1). The parameter is entered in tenths of a second. Therefore, if a value of 100 is entered for a command, the command executes no more frequently than every 10 seconds.

Reg Count

Regs: 1 to 125 Coils: 1 to 800 This parameter specifies the number of 16-bit registers or binary bits to be

transferred by the command.

 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.

 For functions 3, 4, and 16, this parameter sets the number of registers to be

transferred by the command.

Page 48 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration

Swap Code

Description

NONE

No change is made in the byte ordering (1234 = 1234)

SWAP WORDS

The words are swapped (1234=3412)

SWAP WORDS & BYTES

The words are swapped, then the bytes in each word are swapped (1234=4321)

SWAP BYTES

The bytes in each word are swapped (1234=2143)

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Swap Code

NONE SWAP WORDS SWAP WORDS & BYTES SWAP BYTES

This parameter defines if and how the order of bytes in data received or sent is to be rearranged. This option exists to allow for the fact that different manufacturers store and transmit multi-byte data in different combinations. This parameter is helpful when dealing with floating-point or other multi-byte values, as there is no one standard method of storing these data types. The parameter can be set to rearrange the byte order of data received or sent into an order more useful or convenient for other applications. The following table defines the valid Swap Code values and the effect they have on the byte-order of the data.

These swap operations affect 4-byte (or 2-word) groups of data. Therefore, data swapping using these Swap Codes should be done only when using an even number of words, such as when 32-bit integer or floating-point data is involved.

Node IP Address

xxx.xxx.xxx.xxx The IP address of the device being addressed by the command.

Service Port

502 or other port numbers supported on a server

Use a value of 502 when addressing Modbus TCP/IP servers that are compatible with the Schneider Electric MBAP specifications (this will be most devices). All other service port values will generate a Modbus command message encapsulated in a TCP/IP packet.

Slave Address

0 - Broadcast to all nodes 1 to 255

Use this parameter to specify the slave address of a remote Modbus Serial device through a Modbus Ethernet to Serial converter.

ProSoft Technology, Inc. Page 49 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Modbus Function Code

Description

Read Coil Status

Read Input Status

Read Holding Registers

Read Input Registers

Force (Write) Single Coil

Preset (Write) Single Register

Read Exception Status

Force Multiple Coils

Preset Multiple Registers

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.

If the value is set to zero, the command will be a broadcast message on the network. The Modbus protocol permits broadcast commands for write operations. Do not use node address 0 for read operations.

Modbus Function

1, 2, 3, 4, 5, 6, 7, 15, or 16 This parameter specifies the Modbus Function Code to be executed by the

command. These function codes are defined in the Modbus protocol. The following table lists the purpose of each function supported by the module. More information on the protocol is available from www.modbus.org.

MB Address in Device

This parameter specifies the starting Modbus register or bit address in the server to be used by the command. Refer to the documentation of each Modbus server device for the register and bit address assignments valid for that device.

The Modbus Function Code determines whether the address will be a registerlevel or bit-level OFFSET address into a given data type range. The offset will be the target data address in the server minus the base address for that data type. Base addresses for the different data types are:

 00001 or 000001 (0x0001) for bit-level Coil data (Function Codes 1, 5, and

15).

 10001 or 100001 (1x0001) for bit-level Input Status data (Function Code 2)  30001 or 300001 (3x0001) for Input Register data (Function Code 4)  40001 or 400001 (4x0001) for Holding Register data (Function Codes 3, 6,

and 16).

Page 50 of 172 ProSoft Technology, Inc. September 20, 2018

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).

 For Coil address 00115, specify 114

(00115 - 00001 = 114)

 For register read or write commands (FC 3, 6, or 16) 4X range, for 40001,

specify a value of 0 (40001 - 40001 = 0).

 For 01101, 11101, 31101 or 41101, specify a value of 1100.

(01101 - 00001 = 1100) (11101 -10001 = 1100) (31101 - 30001 = 1100) (41101 - 40001 = 1100)

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. In such cases, it is not usually necessary to subtract 1 from the converted decimal number, as this addressing scheme typically uses the exact offset address expressed as a hexadecimal number.

Comment

0 to 32 alphanumeric characters

2.1.9 Static ARP Table

The Static ARP Table defines a list of static IP addresses that the module will use when an ARP (Address Resolution Protocol) is required. The module will accept up to 40 static IP/MAC address data sets.

Use the Static ARP table to reduce the amount of network traffic by specifying IP addresses and their associated MAC (hardware) addresses that the MVI56EMNETC/MNETCXT module will be communicating with regularly.

Important: If the device in the field is changed, this table must be updated to contain the new MAC address for the device and downloaded to the module. If the MAC is not changed, no communications with the module will be provided.

ProSoft Technology, Inc. Page 51 of 172 September 20, 2018

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.

Hardware MAC Address

Hex value This table contains a list of static MAC 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 52 of 172 ProSoft Technology, Inc. September 20, 2018

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.

1 Determine the network settings for your module, with the help of your network

administrator if necessary. You will need the following information:

o IP address (fixed IP required) _____ . _____ . _____ . _____ o Subnet mask _____ . _____ . _____ . _____ o Gateway address _____ . _____ . _____ . _____

Note: The gateway address is optional, and is not required for networks that do not use a default gateway.

2 Double-click the ETHERNET CONFIGURATION icon. This action opens the Edit

dialog box.

3 Edit the values for my_ip, netmask (subnet mask) and gateway (default

gateway).

4 When you are finished editing, click OK to save your changes and return to

the ProSoft Configuration Builder window.

ProSoft Technology, Inc. Page 53 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

2.2 Connecting Your PC to the Module

2.2.1 Using CIPconnect to Connect to the Module

You can use CIPconnect® to connect a PC to the MVI56E-MNETC/MNETCXT module over 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:

 The IP addresses and slot numbers of any 1756-ENBT modules in the path  The ControlNet node numbers and slot numbers of any 1756-CNBx

ControlNet Bridge modules in the path

 The slot number of the MVI56E-MNETC/MNETCXT in the destination

ControlLogix chassis (the last ENBT/CNBx and chassis in the path).

To use CIPconnect, follow these steps.

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT icon and then choose DIAGNOSTICS.

2 In the Diagnostics window, click the SET UP CONNECTION button.

Page 54 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

3 In the Select Connection Type dropdown list, choose 1756-ENBT. The

default path appears in the text box, as shown in the following illustration.

4 Click CIP PATH EDIT to open the 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.

ProSoft Technology, Inc. Page 55 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Parameter

Description

Source Module

Source module type. This field is automatically selected depending on the destination module of the last rack (1756-CNB or 1756-ENBT).

Source Module IP Address

IP address of the source module (only applicable for 1756-ENBT)

Source Module Node Address

Node address of the source module (only applicable for 1756-CNB)

Destination Module

Select the destination module associated to the source module in the rack. The connection between the source and destination modules is performed through the backplane.

Destination Module Slot Number

The slot number where the destination MVI56EMNETC/MNETCXT module is located.

Ethernet

Rack 1

MVI56E Module 1756-ENBT

0 1 2

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 RACK NO. 1 and configure the associated parameters.

 If the MVI56E-MNETC/MNETCXT is available in a remote rack (accessible

through ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).

To use the CIPconnect Path Editor, follow these steps. 1 Configure the path between the 1756-ENBT connected to your PC and the

MVI56E-MNETC/MNETCXT module.

o If the module is located in a remote rack, add more racks to configure the

full path.

o The path can only contain ControlNet or Ethernet/IP networks. o The maximum number of supported racks is six.

2 Click CONSTRUCT CIP PATH to build the path in text format. 3 Click OK to confirm the configured path.

Example 1: Local Rack Application

For this example, the MVI56E-MNETC/MNETCXT module is located in the same rack as the 1756-ENBT that is connected to the PC.

Page 56 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration

Slot

Module

Network Address

ControlLogix Processor

- 1 Any

MVI56E-MNETC/MNETCXT

- 3 1756-ENBT

IP=192.168.0.100

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Rack 1

1 In ProSoft Configuration Builder, right-click the MVI56E-MNETC/MNETCXT

icon and then choose DIAGNOSTICS.

2 In the Diagnostics window, click the SET UP CONNECTION button.

ProSoft Technology, Inc. Page 57 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

3 In the Select Connection Type dropdown list, choose 1756-ENBT. The

default path appears in the text box, as shown in the following illustration.

4 Configure the path as shown in the following illustration, and click

CONSTRUCT CIP PATH to build the path in text format.

5 Click OK to close the CIPconnect Path Editor and return to the Connection

Setup dialog box.

Page 58 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

6 Check the new path in the Connection Setup dialog box.

7 Click TEST CONNECTION to verify that the physical path is available. The

following message should be displayed upon success.

8 Click OK to close the Test Connection pop-up and then click CONNECT to

close the Connection Set up dialog box. The Diagnostics menu is now connected through CIPconnect.

ProSoft Technology, Inc. Page 59 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Ethernet

Rack 1

0 1 2 3

ControlNet

1 2 3 4 5

Rack 2

1756-ENBT

1756-CNB

MVI56E Module

Slot

Module

Network Address

ControlLogix Processor

- 1 1756-CNB

Node = 1

1756-ENBT

IP=192.168.0.100

Any

Slot

Module

Network Address

Any

Any - 2

Any

Any - 4

Any

1756-CNB

Node = 2

MVI56E-MNETC/MNETCXT

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.

Rack 1

Rack 2

Page 60 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

1 In ProSoft Configuration Builder, right-click the MVI56E-MNETC/MNETCXT

icon and then choose DIAGNOSTICS.

2 In the Diagnostics window, click the SET UP CONNECTION button.

ProSoft Technology, Inc. Page 61 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

3 In the Select Connection Type dropdown list, choose 1756-ENBT. The

default path appears in the text box, as shown in the following illustration.

4 Configure the path as shown in the following illustration, and click

CONSTRUCT CIP PATH to build the path in text format.

5 Click OK to close the CIPconnect Path Editor and return to the Connection

Setup dialog box.

Page 62 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

6 Check the new path in the Connection Setup dialog box.

7 Click TEST CONNECTION to verify that the physical path is available. The

following message should be displayed upon success.

8 Click OK to close the Test Connection pop-up and then click CONNECT to

close the Connection Set up dialog box. The Diagnostics menu is now connected through CIPconnect.

ProSoft Technology, Inc. Page 63 of 172 September 20, 2018

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. For information on setting up the ENBT module, see Using CIPconnect to Connect to the Module (page 54).

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT module. 2 From the shortcut menu, choose DOWNLOAD FROM PC TO DEVICE. 3 In the Download dialog box, choose 1756 ENBT from the Select Connection

Type dropdown box.

4 Click RSWHO to display modules on the network. The MVI56E-

MNETC/MNETCXT module will automatically be identified on the network.

5 Select the module, and then click OK.

Page 64 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

2.2.3 Connecting Your PC to the Module's Ethernet Port

With the module securely mounted, connect one end of the Ethernet cable to the Config (E1) Port, and the other end to an Ethernet hub or switch accessible from the same network as your PC. You can also connect directly from the Ethernet Port on your PC to the Config (E1) Port on the module by using an Ethernet crossover cable (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.

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.

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT icon to open a shortcut menu.

2 On the shortcut menu, choose DIAGNOSTICS.

ProSoft Technology, Inc. Page 65 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

3 In the Diagnostics window, click the SET UP CONNECTION button.

4 In the Connection Setup dialog box, click the BROWSE DEVICE(S) button to

open the ProSoft Discovery Service. Select the module, then right-click and

choose ASSIGN TEMPORARY IP.

5 The module’s default IP address is 192.168.0.250. Choose an unused IP

within your subnet, and then click OK.

Important: The temporary IP address is only valid until the next time the module is initialized. For

information on how to set the module’s permanent IP address, see Ethernet Configuration (page

53).

Page 66 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform MVI56E-MNETC/MNETCXT Configuration Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

6 Close the ProSoft Discovery Service window. Enter the temporary IP in the

Ethernet address field of the Connection Setup dialog box, then click the TEST CONNECTION button to verify that the module is accessible with the current settings.

7 If the Test Connection is successful, click CONNECT. The Diagnostics menu

will display in the Diagnostics window.

ProSoft Technology, Inc. Page 67 of 172 September 20, 2018

MVI56E-MNETC/MNETCXT Configuration MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

2.3 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).

In order for the module to use the settings you configured, you must download the updated Project file from your PC to the module.

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT icon and then choose DOWNLOAD FROM PC TO DEVICE.

This opens the Download dialog box.

2 In the Download dialog box, choose the connection type in the Select

Connection Type dropdown box:

o Choose ETHERNET if you are connecting to the module through the

Ethernet cable.

o Choose 1756 ENBT if you are connecting to the module through

CIPconnect or RSWho. See Connecting Your PC to the Module (page 54) for more information.

Note: If you connected to the module using an Ethernet cable and set a

temporary IP address, the Ethernet address field contains that temporary IP

address. ProSoft Configuration Builder uses this temporary IP address to

connect to the module.

3 Click TEST CONNECTION to verify that the IP address allows access to the

module. 4 If the connection succeeds, click DOWNLOAD to transfer the Ethernet

configuration to the module.

Page 68 of 172 ProSoft Technology, Inc. September 20, 2018

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.

1 Click OK to dismiss the error message. 2 In the Download dialog box, click BROWSE DEVICE(S) to open ProSoft

Discovery Service.

3 Right-click the module and then choose SELECT FOR PCB. 4 Close ProSoft Discovery Service. 5 Click DOWNLOAD to transfer the configuration to the module.

ProSoft Technology, Inc. Page 69 of 172 September 20, 2018

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

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags

In This Chapter

 Controller Tags ...................................................................................... 71

 User-Defined Data Types (UDTs) ......................................................... 73

 Controller Tag Overview ........................................................................ 74

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

3 Using Controller Tags

Controller tags are a feature of the RSLogix software and are part of the MVI56EMNETC/MNETCXT Add-On Instruction. Refer to the section Adding the Module to RSLogix (page 29, page 13) for information on importing the Add-On Instruction into RSLogix.

3.1 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:

 View the read and write data being transferred between the module and the

processor.

 View status data for the module.  Set up and trigger special functions.  Initiate module restarts (Warm Boot or Cold Boot).

Individual controller tags can be grouped into collections of controller tags called controller tag structures. A controller tag structure can contain any combination of:

 Individual controller tags  Controller tag arrays  Lower-level controller tag structures

The controller tags are included in the MVI56E-MNETC/MNETCXT Add-On Instruction ladder logic. After you import the Add-On Instruction, you can find the controller tags in the Controller Tags subfolder, located in the Controller folder in the Controller Organizer pane of the main RSLogix 5000 window. This controller tag structure is arranged as a tree structure. Individual controller tags are found at the lowest level of the tree structure. Each individual controller tag is defined to hold data of a specific type, such as integer or floating-point data.

The Add-On Instruction also includes user-defined data types (UDTs). UDTs are collections of data types and declares the data types for the controller tag structures.

ProSoft Technology, Inc. Page 71 of 172 September 20, 2018

Using Controller Tags MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform 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.

3.1.1 MVI56E-MNETC Controller Tags

The main controller tag structure, MNETC, is broken down into four lower-level controller tag structures.

The four lower-level controller tag structures contain other controller tags and controller tag structures. Click the [+] sign next to any controller tag structure to expand it and view the next level in the structure.

For example, if you expand the MNETC.DATA controller tag structure, you will see that it contains two controller tag arrays, MNETC.DATA.ReadData and MNETC.DATA.WriteData, which are 600-element integer arrays by default.

Each controller tag in the Add-On Instruction is commented in the Description column.

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. Controller tag arrays are declared with arrays of basic data types. Controller tag structures are declared with user-defined data types (UDTs).

Page 72 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

3.2 User-Defined Data Types (UDTs)

User-defined data types (UDTs) allow you to organize collections of data types into groupings. You can use these groupings, or data type structures, to declare the data types for controller tag structures. Another advantage of defining a UDT is that you may reuse it in other controller tag structures that use the same data types.

The Add-On Instruction for the MVI56E-MNETC/MNETCXT module has predefined UDTs. You can find them in the User-Defined subfolder, located in the Data Types folder in the Controller Organizer pane of the main RSLogix window. 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. There are four UDTs one level below MNETCMODULEDEF. These lower-level UDTs were used to create the MNETC.DATA, MNETC.CONTROL, MNETC.STATUS, and MNETC.UTIL controller tag structures.

Click the [+] signs to expand the UDT structures and view lower-level UDTs.

ProSoft Technology, Inc. Page 73 of 172 September 20, 2018

Using Controller Tags MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Controller Tag

Description

MNETC.DATA

MNET input and output data transferred between the processor and the module

MNETC.CONTROL

Governs the data movement between the PLC rack and the module

MNETC.STATUS

Status information

MNETC.UTIL

Block statistics and generic tags used for internal ladder processing (DO NOT MODIFY)

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

For example, if you expand MNETC.DATA, you will see that it contains two UDTs, ReadData and WriteData. Both of these are 600-element integer arrays by default.

Notice that these UDTs are the data types used to declare the MNETC.DATA.ReadData and MNETC.DATA.WriteData controller tag arrays.

Each UDT is commented in the Description column.

3.3 Controller Tag Overview

This and the following sections describe the MNETC controller tags in detail.

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.

The data types for the MNETC.DATA.ReadData and MNETC.DATA.WriteData controller tag arrays are integer arrays containing variable numbers of elements.

Page 74 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags

Controller Tag

Data Type

Description

ReadData

INT[x]

Data read from module. Array size is equal to the size set in the configuration.

WriteData

INT[x]

Data to write to module. Array size is equal to the size set in the configuration.

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

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.

For ease of use, this array should be dimensioned as a multiple of 200 words. This data is paged up to 200 words at a time from the module to the processor. The ladder logic places the data received into the proper position in the ReadData array. This data is used for status and control in the processor ladder logic.

ProSoft Technology, Inc. Page 75 of 172 September 20, 2018

Using Controller Tags MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

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 The Diagnostics Menu (page 88).

MNETC.DATA.WriteData The WriteData controller tag array should accommodate the value entered in the

For ease of use, this array should be dimensioned as a multiple of 200 words. This data is paged up to 200 words at a time from the processor to the module. The ladder logic places the write data into the output image for transfer to the module. This data is passed from the processor to the module for status and control information for use in other nodes on the network.

Page 76 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags

Controller Tag

Data Type

Description

BootTimer

TIMER

Timer used to clear both cold and warm boot requests

ColdBoot

BOOL

Hardware reset of the module

WarmBoot

BOOL

Configuration data reset in the module

ResetStatus

BOOL

Reset status values

CmdID

INT

Command ID from 1 to 16

CmdControl

MNETCCMDCONTROL

Holds Command Control statistics

CmdControlPending

BOOL

Halts rung until module is ready

CmdControlTrigger

BOOL

Command Control Trigger

IPAddress

MNETCIPADDRESS

Getting and setting IP address to and from module

EventCmd

MNETCEVENTCMD

Holds Event Command configuration

EventSeqCmd

MNETCEVENTCMD_SE Q

Event sequence commands

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. For more information, see the section on PCB The Diagnostics Menu (page 88).

3.3.2 MNETC.CONTROL

This controller tag structure is used to request special tasks from the module. For more information, see Special Function Blocks (page 110).

ProSoft Technology, Inc. Page 77 of 172 September 20, 2018

Using Controller Tags MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Name

Data Type

Description

PassCnt

INT

Program cycle counter

ProductVersion

INT

This is used to pass the product version to the processor

ProductCode

INT[2]

This is used to pass the product code to the processor

BlockStats

MNETCBLOCKSTATS

Block transfer statistics

CmdBits

INT[30]

Command bits array to be used for 30 Clients

ClientStatsTrigger

BOOL

Get Client status

ClientID

INT

Client ID to get status from

ClientStatus

MNETCCLIENTSTATS[30 ]

Client status data CmdErrorList

INT[16]

Command Error List

EventSeqCmdPending

MNETCCMDCLIENTSEQ _PENDING

Number of sequence events pending in the module

EventSeqCmd

MNETCEVENTCMD_SE QSTAT

Event sequence event commands pending

EventSeqReady

DINT

Status data (bit=1 data ready, bit=0 no event data)

ServerStatus

MNETCSERVERS

Server status data

ServerStatsTrigger

BOOL

Trigger the Server Status block request

Name

Data Type

Description

LastRead

INT

Index of last read block

LastWrite

INT

Index of last write block

BlockIndex

INT

Computed block offset for data table

StatusIndex

INT

Computed block offset for status data

ReadDataSizeGet

INT

Gets ReadData array length

WriteDataSizeGet

INT

Gets WriteData array length

ReadDataBlkCount

INT

Holds the value of the block counts of the ReadData array

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

3.3.3 MNETC.STATUS

This controller tag structure contains module and Client status data. For a more complete description of the MNETC.STATUS controller tag structure, refer to the Status Data Definition (page 93).

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.

Page 78 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Using Controller Tags

Name

Data Type

Description

WriteDataBlkCount

INT

Holds the value of the block counts of the WriteData array

RBTSremainder

INT

Holds remainder calculation value from the read array

WBTSremainder

INT

Holds remainder calculation value from the write array

PassThru

MNETCPASSTHRU

Modbus pass-through commands

IPsetPending

BOOL

Allows setting module IP address

IPgetPending

BOOL

Allows getting module IP address

InitOutputData

MNETCINITOUTDATA

Used to bring the module into a known state after a restart operation

FaultCode

INT

Fault Code value

CheckInitialization

BOOL

Check initialization trigger

StatusSeqIndex

INT

Computed block offset for status data

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

The LastRead tag stores the latest Read Block ID received from the module. The LastWrite tag stores the latest Write Block ID to be sent to the module. The BlockIndex tag is an intermediate variable used during the block calculation.

ProSoft Technology, Inc. Page 79 of 172 September 20, 2018

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

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting

In This Chapter

 Ethernet LED Indicators ........................................................................ 81

 Clearing a Fault Condition ..................................................................... 83

 Troubleshooting the LEDs ..................................................................... 84

 Using the Diagnostics Menu in ProSoft Configuration Builder ............... 85

 Reading Status Data from the Module .................................................. 92

 Connecting to the Module's Web Page ................................................. 98

LED

State

Description

Data

OFF

Ethernet connected at 10Mbps duplex speed

AMBER Solid

Ethernet connected at 100Mbps duplex speed

Link

OFF

No physical network connection is detected. No Ethernet communication is possible. Check wiring and cables.

GREEN Solid or Blinking

Physical network connection detected. This LED must be ON solid for Ethernet communication to be possible.

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4 Diagnostics and Troubleshooting

The module provides information on diagnostics and troubleshooting in the following forms:

 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.

4.1 Ethernet LED Indicators

The Ethernet LEDs indicate the module's Ethernet port status as follows:

ProSoft Technology, Inc. Page 81 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Code

Message

Boot / DDOK

Module is initializing

Ladd

Module is waiting for required module configuration data from ladder logic to configure the application port(s)

Waiting for Processor Connection

Module did not connect to processor during initialization

 Sample ladder logic or AOI is not loaded on processor  Module is located in a different slot than the one

configured in the ladder logic/AOI

 Processor is not in RUN or REM RUN mode

Last config: <date>

Indicates the last date when the module changed its IP address. You can update the module date and time through the module’s web page, or with the Optional MVI56E Add-On Instruction.

After power up and every reconfiguration, the module will display the configuration of the application port(s). The information consists of:

Client

 C0 C2 C3 C4 ….. C29

Code

Message

OK: Module is communicating with processor ERR: Module is unable to communicate with processor. For

this scenario, the <Port Status> message above is replaced with "Processor faulted or is in program mode".

Module IP address

<C0>

OK: Port is communicating without error Communication Errors: port is having communication errors.

Refer to Diagnostics and Troubleshooting (page 80) for further information about the error.

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

Operation Messages

After the initialization step, the following message pattern will be repeated.

Page 82 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting

LED Label

Status

Indication

APP

OFF

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.

RED

The most common cause is that the module has detected a communication error during operation of an application port.

The following conditions may also cause a RED LED:

 The firmware is initializing during startup  The firmware detects an on-board hardware problem during startup  Failure of application port hardware during startup  The module is shutting down  The module is rebooting due to a ColdBoot or WarmBoot request

from the ladder logic or Debug Menu

OFF

The module is not receiving adequate power or is not securely plugged into the rack.

GREEN

The module is operating normally.

RED

The module has detected an internal error or is being initialized. If the LED remains RED for over 10 seconds, the module is not working. Remove it from the rack and re-insert it to restart its internal program.

ERR

RED

Not used.

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4.1.2 Non-Scrolling LED Status Indicators

The non-scrolling LEDs indicate the module’s operating status as follows:

4.2 Clearing a Fault Condition

Typically, if the OK LED on the front of the module remains RED for more than ten seconds, a hardware problem has been detected or the program has exited.

To clear the condition, follow these steps:

1 Turn off power to the rack. 2 Remove the card from the rack. 3 Verify that all jumpers are set correctly. 4 If the module requires a Compact Flash card, verify it is installed correctly. 5 Re-insert the card in the rack and turn the power back on. 6 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.

ProSoft Technology, Inc. Page 83 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Problem Description

Steps to take

Processor Fault

Verify the module is securely plugged into the slot that has been configured for the module in the I/O Configuration of RSLogix.

Verify the slot location in the rack has been configured correctly in the ladder logic.

Processor I/O LED flashes

This indicates a problem with backplane communications. A problem could 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.

Problem Description

Steps to take

Module Scrolling LED display: <Backplane Status> condition reads ERR

This indicates that backplane transfer operations are failing. Connect to the module’s Configuration/Debug port to check this.

To establish backplane communications, verify the following items:

 The processor is in RUN or REM RUN mode.  The backplane driver is loaded in the module.  The module is configured for read and write data block transfer.  The ladder logic handles all read and write block situations.  The module is properly configured in the processor I/O configuration

and ladder logic.

OK LED remains RED

The program has halted or a critical error has occurred. Connect to the communication port to see if the module is running. If the program has halted, turn off power to the rack, remove the card from the rack and reinsert the card in the rack, and then restore power to the rack.

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

4.3 Troubleshooting the LEDs

Use the following troubleshooting steps if problems occur when the module is powered up. If these steps do not resolve the problem, please contact ProSoft Technology Technical Support.

Processor Errors

Module Errors

Page 84 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4.4 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, refer to Connecting Your PC to the ControlLogix Processor (page 27).

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT icon to open a shortcut menu.

2 On the shortcut menu, choose DIAGNOSTICS.

3 In the Diagnostics window, click the SET UP CONNECTION button to browse for

the module’s IP address.

ProSoft Technology, Inc. Page 85 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

4 In the Connection Setup dialog box, click the TEST CONNECTION button to

verify that the module is accessible with the current settings.

You can also use CIPconnect® to connect to the module through a 1756-

ENBT card. Refer to Using CIPconnect to Connect to the Module (page 54)

for information on how to construct a CIP path.

5 If the Test Connection is successful, click CONNECT.

Page 86 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

If PCB is unable to connect to the module: 1 Click the BROWSE DEVICE(S) button to open the ProSoft Discovery Service.

Select the module, then right-click and choose SELECT FOR PCB.

2 Close ProSoft Discovery Service, and click the CONNECT button again. 3 If these troubleshooting steps fail, verify that the Ethernet cable is connected

properly between your computer and the module, either through a hub or switch (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 87 of 172 September 20, 2018

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. The first menu you see when you connect to the module is the Main menu.

Page 88 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting 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.

The information on this menu corresponds with the configuration information in the Module settings in ProSoft Configuration Builder.

NIC Status

Use the NIC Status (Network Interface Card) menu to view configuration and status information for the MVI56E-MNETC/MNETCXT module's Ethernet application port.

The information on this menu is useful for troubleshooting Ethernet network connectivity problems.

Static ARP

Use the Static ARP menu to view the list of IP and MAC addresses that are configured not to receive ARP (Address Resolution Protocol) messages from the module.

The Static ARP Table (page 51) defines a list of static IP addresses that the module will use when an ARP is required.

ProSoft Technology, Inc. Page 89 of 172 September 20, 2018

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

 Number of retries  Backplane status  Fail count  Number of words read  Number of words written  Number of words parsed  Error count  Event count  Command count

During normal operation, the read, write, and parsing values should increment continuously, while the error value should not increment.

The status values on this menu correspond with members of the Status Data Definition. See Status Data in Read Block (page 107).

4.4.4 Monitoring Database Information

Use the DATABASE menu to view the contents of the MVI56EMNETC/MNETCXT module’s internal database.

You can view data in the following formats:

ASCII

Decimal

Page 90 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

Float

Hexadecimal

Use the scroll bar on the right edge of the window to view each page (100 words) of data.

4.4.5 Monitoring MNETC Server Information

Use the MNETC SERVER menu to view the configuration and status information for the MNETC server.

Config

Use the Configuration menu to view configuration settings for MNET servers connected to the MNET Client.

The information on this menu corresponds with the configuration information in the MNET Servers settings in ProSoft Configuration Builder MNET Servers (page

39) dialog box. See MNET Servers (page 39).

Status

Use the Status menu to view the status of each MNET server connected to the MNET Client 0. During normal operation, the number of requests and responses should increment, while the number of errors should not change.

ProSoft Technology, Inc. Page 91 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

4.4.6 Monitoring MNET Client Information

Use the MNET CLIENT x menu to view the configuration and status information for the MNET Client(s).

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.

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.

Command List

Use the Command List menu to view the command list settings for MNET Client x. The information on this menu corresponds with the MNET Client x Commands settings in ProSoft Configuration Builder.

Use the scroll bar on the right edge of the window to view each MNET Client command.

Command Status

Use the Command Status menu to view MNET Client x Command status. A zero indicates no error. A non-zero value indicates an error. For an explanation of each value, see Client

Command Errors (page 96).

4.5 Reading Status Data from the Module

Module status information is useful for troubleshooting and can be accessed in several different ways.

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). You can view this data in the MNETC.STATUS controller tag structure in the ladder logic.

Client status data can also be requested and returned in a special Client Status Blocks (3000 to 3029) (page 114), outside of the normal data transfer block sequence. The status data contained in the Client Status block is different from the status data in the normal data transfer blocks. It can also be viewed in the MNETC.STATUS controller tag structure.

Page 92 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

For more information about status data in MNETC.STATUS, see the Status Data Definition (page 93).

In ProSoft Configuration Builder's Diagnostics screens.

For more information, see the section on The Diagnostics Menu (page 88).

In database locations specified by Error/Status Pointers (optional).

If optional Error/Status Pointers are enabled, status data can also be found in the

Read Data area of the module’s database at the locations specified by the

pointer configuration parameters. For more information, see Backplane Error/Status Pointer (page 36), Client Error/Status Pointer (page 42) and Command Error Pointer (page 42).

4.5.1 Status Data Definition

This section contains a description of the controller tags in the MNETC.STATUS controller tag structure, which contains module and Client status data.

 The first ten controller tags contain status data routinely transferred from the

module to the processor in the Normal Data Transfer Blocks (page 106).

 The next controller tags are used to request and receive Client status data via

the Client Status Blocks (3000 to 3029) (page 114).

 The next controller tags are the Event Command Blocks with Sequence

Number (4000 to 4029, 4100 to 4129, 4200) (page 116).

 The remaining controller tags are used to request and receive server status

data via the Server Client Status Blocks (3000 to 3029) (page 114).

Note: In order to access up-to-date status data from these remaining controller tags, you must ensure that a Client Status block or Server Status block was recently received from the module. Client Status blocks and Server Status blocks are not routinely sent from the module; they are returned on a once-per-request basis as a response to a Client Status block request or Server Status block request from the processor.

ProSoft Technology, Inc. Page 93 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Controller Tag

Data Type

Description

PassCnt

INT

This value is incremented each time a complete program cycle occurs in the module.

ProductVersion

INT

Product version

ProductCode

INT[2]

Product code

BlockStats.Read

INT

Total number of read blocks transferred from the module to the processor

BlockStats.Write

INT

Total number of write blocks transferred from the processor to the module

BlockStats.Parse

INT

Total number of blocks successfully parsed that were received from the processor

BlockStats.Event

INT

Total number of Event Command blocks received from the processor

BlockStats.Cmd

INT

Total number of Command Control blocks received from the processor

BlockStats.Err

INT

Total number of block errors recognized by the module

CmdBits[x]

INT

Displays enabled or disabled status of all 16 commands in the Client x Command List for each Client

ClientStatsTrigger

BOOL

Initiates request for Client Status block from module when set to 1

ClientID

INT

Specifies Client (0 to 29) to request status data from

ClientStatus[x].CmdReq

INT

Total number of command list requests sent from Client

ClientStatus[x].CmdResp

INT

Total number of command list responses received by Client

ClientStatus[x].CmdErr

INT

This value is incremented each time an error message is received from a remote unit or a local error is generated for a command.

ClientStatus[x].Requests

INT

Not used

ClientStatus[x].Responses

INT

Not used

ClientStatus[x].ErrSent

INT

Not used

ClientStatus[x].ErrRec

INT

Not used

ClientStatus[x].CfgErrWord

INT

Configuration Error Word - This word contains a bitmap that indicates general module configuration errors.

ClientStatus[x].CurErr

INT

Most recent error code recorded for the Client

ClientStatus[x].LastErr

INT

Previous most recent error code recorded for the Client

CmdErrorList[x]

INT

Command error code for each command (0-15) on the specified Client's command list

EventSeqCmdPending.Trigg er

BOOL

Set to 1 to trigger the command queue status data request.

EventSeqCmdPending.Clien t[x]_QueueCount

SINT

Number of Event sequence commands for which status has not yet been retrieved

EventSeqCmdPending.Clien t[x]_WaitingMsgs

SINT

Total number of commands waiting in the command queue

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

Page 94 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting

Controller Tag

Data Type

Description

EventSeqCmd.Trigger

BOOL

Set the value of this tag to 1 to trigger the Event Sequence Command block request.

EventSeqCmd.ClientID

INT

Specifies Client (0 to 29) to request status data from.

EventSeqCmd.Client[x].Cou nt

INT

Number of Event Sequence Commands executed by the specified Client for which status has not yet been retrieved

EventSeqCmd.Client[x].Cmd [x].Sequence

INT

Sequence number for each Event Sequence command

EventSeqCmd.Client[x].Cmd [x].Error

INT

Error code for each Event Sequence command: 0=success, 1=failure

EventSeqReady

DINT

One bit for each Client, indicating which Clients have Event Sequence commands with unretrieved status data: 0=no status data available, 1=status data available for retrieval

ServerStatusTrigger

BOOL

Set to 1 to trigger the Server Status block request.

ServerStatus.MNET.Reques ts

INT

This counter increments each time an MNet (port

2000) request is received.

ServerStatus.MNET.Respon ses

INT

This counter increments each time an MNet (port

2000) response message is sent.

ServerStatus.MNET.ErrSent

INT

This counter increments each time an MNet (port

2000) sends an exception response to Client. Example: Client sent illegal Modbus Data location address.

ServerStatus.MNET.ErrRec

INT

This counter increments each time an MNet (port

2000) receives a bad command. Example: Client sent illegal function command.

ServerStatus.MBAP.Reques ts

INT

This counter increments each time an MBAP (port

502) request is received.

ServerStatus.MBAP.Respon ses

INT

This counter increments each time an MBAP (port

502) response message is sent.

ServerStatus.MBAP.ErrSent

INT

This counter increments each time an MBAP (port

502) sends an exception response to Client. Example: Client sent illegal Modbus Data location address.

ServerStatus.MBAP.ErrRec

INT

This counter increments each time an MBAP (port

502) receives a bad command. Example: Client sent illegal function command.

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

ProSoft Technology, Inc. Page 95 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Bit

Description

Hex Value

Reserved - not currently used

0001h

Reserved - not currently used

0002h

Reserved - not currently used

0004h

Reserved - not currently used

0008h

Invalid retry count parameter

0010h

The float flag parameter is not valid.

0020h

The float start parameter is not valid.

0040h

The float offset parameter is not valid.

0080h

The ARP Timeout is not in range (ARP Timeout parameter 0 or greater than 60000 milliseconds) and will default to 5000 milliseconds.

0100h 9

The Command Error Delay is > 300 and will default to 300.

0200h

Reserved - not currently used

0400h

Reserved - not currently used

0800h

Reserved - not currently used

1000h

Reserved - not currently used

2000h

Reserved - not currently used

4000h

Reserved - not currently used

8000h

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. The Configuration Error Word appears in the MNETC.STATUS.ClientStatus[x] controller tag array.

Bits set to 1 in the Configuration Error Word indicate the following errors.

Combinations of errors will result in more than one bit being set in the error word. Correct any invalid data in the configuration for proper module operation. A value of zero (0) in this word indicates all bits are clear, which means that all module configuration parameters contain valid values. However, this does not mean that the configuration is valid for the user application. Make sure each parameter is set correctly for the intended application.

4.5.3 Client Command Errors

There are several different ways to view Client Command Errors.

 In the MNETC.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. This

means that the first register refers to command 1 and so on.

Page 96 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting

Word Offset

Description

Command 0 Error

Command 1 Error

Command 2 Error

Command 3 Error

…

….

… … 15

Command 15 Error

Command 16 Error

Code

Description

Illegal function

Illegal data address

Illegal data value

Failure in associated device

Acknowledge

Busy; message was rejected

Code

Description

-2

Timeout while transmitting message

-11

Timeout waiting for response after request (same as -36)

253

Incorrect slave/server address in response

254

Incorrect function code in response

255

Invalid CRC/LRC value in response

Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

For every command that has an error, the module automatically sets the poll delay parameter to 30 seconds. This instructs the module to wait 30 seconds until it attempts to issue the command again.

As the commands in the Client Command Last are polled and executed, an error value is maintained in the module for each command. This error list can be transferred to the processor.

Standard Modbus Exception Code Errors

Module Communication Error Codes

ProSoft Technology, Inc. Page 97 of 172 September 20, 2018

Diagnostics and Troubleshooting MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform

Code

Description

-33

Failed to connect to server specified in command

-35

Invalid length of response message

-36

MNET command response timeout

-37

TCP/IP connection ended before session finished

Code

Description

-40

Too few parameters

-41

Invalid enable code

-42

Internal address > maximum address

-43

Invalid node address (<0 or >255)

-44

Count parameter set to 0

-45

Invalid function code

-46

Invalid swap code

-47

Could not establish a connection. ARP could not resolve MAC from IP (Bad IP address, not part of network, invalid parameter to ARP routine).

-48

Error during ARP operation: the response to the ARP request did not arrive to the module after a 5 second timeout.

User Manual Modbus TCP/IP Client Enhanced Communication Module - Client/Server

MNET Client Specific Errors

Command List Entry Errors

Note: When the Client gets error -47 or -48, it uses the adjustable ARP Timeout parameter in the configuration file to set an amount of time to wait before trying again to connect to this non-existent server. This feature allows the Client to continue sending commands and polling other existing servers, while waiting for the non-existent server to appear on the network.

4.6 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.

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

MNETC/MNETCXT icon and then choose DOWNLOAD FROM PC TO DEVICE. 2 In the Download dialog box, choose the connection type in the Select

Connection Type dropdown box:

o Choose ETHERNET if you are connecting to the module through the

Ethernet cable.

o Choose 1756 ENBT if you are connecting to the module through

CIPconnect or RSWho. See Connecting Your PC to the Module (page 54) for more information.

3 In the Download files from PC to module dialog box, click BROWSE DEVICE(S).

Page 98 of 172 ProSoft Technology, Inc. September 20, 2018

MVI56E-MNETC/MNETCXT ♦ ControlLogix Platform Diagnostics and Troubleshooting Modbus TCP/IP Client Enhanced Communication Module - Client/Server User Manual

4 In ProSoft Discovery Service, right-click the MVI56E-MNETC/MNETCXT icon

and then choose VIEW MODULE’S WEBPAGE.

This displays the module webpage.

ProSoft Technology, Inc. Page 99 of 172 September 20, 2018

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

ProSoft Technology MVI56E-MNETC, MVI56E-MNETCXT User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual