mvi56e-mnetr - ProSoft Technology

MVI56E-MNETR
ControlLogix Platform
Modbus TCP/IP Interface Module with
Reduced Data Block
June 14, 2011
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
5201 Truxtun Ave., 3rd Floor
Bakersfield, CA 93309
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
www.prosoft-technology.com
support@prosoft-technology.com
Copyright © 2011 ProSoft Technology, Inc., all rights reserved.
MVI56E-MNETR User Manual
June 14, 2011
®
®
®
®
®
ProSoft Technology , ProLinx , inRAx , ProTalk , and RadioLinx are Registered Trademarks 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.
ProSoft Technology® Product Documentation
In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments.
User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD-ROM,
and are available at no charge from our web site: www.prosoft-technology.com
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.
Important Safety Information
North America Warnings
A
B
C
D
Warning - Explosion Hazard - Substitution of components may impair suitability for Class I, Division 2.
Warning - Explosion Hazard - When in Hazardous Locations, turn off power before replacing or rewiring
modules.
Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is
known to be nonhazardous.
Suitable for use in Class I, Division 2 Groups A, B, C, and D, Hazardous Locations or Non-Hazardous Locations.
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.
Electrical Ratings
Backplane Current Load: 800 mA @ 5 Vdc; 3 mA @ 24 Vdc
Operating Temperature: 0°C to 60°C (32°F to 140°F)
Storage Temperature: -40°C to 85°C (-40°F to 185°F)
Shock: 30 g operational; 50 g non-operational; Vibration: 5 g from 10 Hz to 150 Hz
Relative Humidity 5% to 95% (without condensation)
All phase conductor sizes must be at least 1.3 mm (squared) and all earth ground conductors must be at least
4mm (squared).
Markings
Agency
Applicable Standards
RoHS
ATEX
EN60079-0 July 2006
EN60079-15 October 2005
CSA
IEC61010
CE
EMC-EN61326-1:2006
EN61000-6-4:2007
CSA CB Safety
CA/10533/CSA IEC 61010-1 Ed. 2
CB 243333-2056722 (2090408)
cULus
GOST-R
Test 2.4
243333
E183151
ME06
<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. <cULus>
E183151
Class I, DIV 2, groups A,B,C,D
T5 for all models
0°C to +60°C
-25°C to +70°C (XT models only)
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Contents
User Manual
Contents
Your Feedback Please ........................................................................................................................ 2
How to Contact Us .............................................................................................................................. 2
®
ProSoft Technology Product Documentation .................................................................................... 2
Battery Life Advisory ........................................................................................................................... 3
Important Safety Information - MVI56E Modules ................................................................................ 3
Guide to the MVI56E-MNETR User Manual
1
Start Here
1.1
1.2
1.3
1.4
1.5
1.6
1.6.1
1.7
1.8
1.8.1
1.9
1.10
1.11
1.11.1
1.11.2
1.11.3
1.11.4
1.11.5
1.11.6
2
11
What's New? ........................................................................................................... 12
System Requirements ............................................................................................. 13
Package Contents ................................................................................................... 14
Setting Jumpers ...................................................................................................... 15
Installing the Module in the Rack ............................................................................ 16
Installing the Configuration Tools ............................................................................ 17
Installing ProSoft Configuration Builder .................................................................. 17
Connecting Your PC to the Module ......................................................................... 18
Setting Temporary IP Address ................................................................................ 19
Using CIPconnect to Connect to the Module .......................................................... 24
Connecting to the Module's Web Page ................................................................... 26
Uploading the Add-On Instruction from the Module ................................................ 27
Creating a New RSLogix 5000 Project.................................................................... 27
Create the Remote Network .................................................................................... 28
Create the Module - Remote Rack .......................................................................... 30
Create the Module - Local Rack .............................................................................. 33
Import Add-On Instruction ....................................................................................... 36
Connecting Your PC to the ControlLogix Processor ............................................... 47
Downloading the Sample Program to the Processor .............................................. 48
Configuring the MVI56E-MNETR Module
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.2
2.3
2.3.1
2.3.2
ProSoft Technology, Inc.
June 14, 2011
9
49
Using ProSoft Configuration Builder Software ........................................................ 50
Setting Up the Project ............................................................................................. 51
Renaming PCB Objects .......................................................................................... 53
Module ..................................................................................................................... 54
MNET Client x ......................................................................................................... 56
MNET Client x Commands ...................................................................................... 58
MNET Servers ......................................................................................................... 65
Static ARP Table ..................................................................................................... 67
Ethernet Configuration ............................................................................................ 68
Downloading the Project to the Module .................................................................. 69
®
Using CIPconnect to Connect to the Module ........................................................ 71
Example 1: Local Rack Application ......................................................................... 73
Example 2: Remote Rack Application ..................................................................... 76
Page 5 of 175
Contents
User Manual
3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ladder Logic
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.2
4
MNETRMODULEDEF ............................................................................................ 80
MNETRDATA.......................................................................................................... 81
MNETRSTATUS ..................................................................................................... 82
MNETRCONTROL ................................................................................................. 84
MNETRUTIL ........................................................................................................... 87
Modbus Message Data ........................................................................................... 89
Diagnostics and Troubleshooting
4.1
4.2
4.2.1
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.4
4.4.1
4.5
4.6
4.6.1
4.6.2
4.6.3
4.6.4
4.7
4.7.1
4.7.2
4.8
4.8.1
4.8.2
4.8.3
4.9
4.10
4.11
5
Reference
5.1
5.1.1
5.1.2
5.1.3
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.3
5.3.1
5.3.2
5.4
Page 6 of 175
79
91
Reading Status Data from the Module ................................................................... 92
The Diagnostics Menu ............................................................................................ 93
Using the Diagnostics Menu in ProSoft Configuration Builder ............................... 93
Monitoring Module Information ............................................................................... 97
Version .................................................................................................................... 97
Config ...................................................................................................................... 97
NIC Status ............................................................................................................... 97
Static ARP............................................................................................................... 97
Monitoring Backplane Information .......................................................................... 97
Backplane Status .................................................................................................... 98
Monitoring Database Information............................................................................ 99
Monitoring MNET Client Information..................................................................... 100
Command List ....................................................................................................... 100
Command Status .................................................................................................. 100
Config .................................................................................................................... 100
Status .................................................................................................................... 100
Monitoring MNET Server Information ................................................................... 101
Config .................................................................................................................... 101
Status .................................................................................................................... 101
LED Status Indicators ........................................................................................... 102
Scrolling LED Status Indicators ............................................................................ 102
Ethernet LED Indicators ........................................................................................ 103
Non-Scrolling LED Status Indicators .................................................................... 104
Client Configuration Error Word............................................................................ 105
Clearing a Fault Condition .................................................................................... 106
Troubleshooting .................................................................................................... 107
109
Product Specifications .......................................................................................... 110
General Specifications .......................................................................................... 110
Functional Specifications ...................................................................................... 111
Hardware Specifications ....................................................................................... 111
Functional Overview ............................................................................................. 112
About the MODBUS TCP/IP Protocol ................................................................... 112
Module Power Up ................................................................................................. 112
Backplane Data Transfer ...................................................................................... 113
Data Flow between MVI56E-MNETR Module and ControlLogix Processor......... 125
Ethernet Cable Specifications............................................................................... 130
Ethernet Cable Configuration ............................................................................... 130
Ethernet Performance........................................................................................... 130
Status Data Definition ........................................................................................... 131
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.5
5.5.1
5.5.2
5.5.3
5.5.4
5.5.5
5.5.6
5.5.7
5.5.8
5.5.9
5.5.10
5.5.11
5.6
5.6.1
5.6.2
5.6.3
5.6.4
5.6.5
5.6.6
5.6.7
5.7
5.8
5.8.1
5.8.2
5.8.3
5.8.4
6
Contents
User Manual
Modbus Protocol Specification .............................................................................. 132
Commands Supported by the Module ................................................................... 132
Read Coil Status (Function Code 01) ................................................................... 133
Read Input Status (Function Code 02).................................................................. 134
Read Holding Registers (Function Code 03) ........................................................ 135
Read Input Registers (Function Code 04)............................................................. 136
Force Single Coil (Function Code 05) ................................................................... 137
Preset Single Register (Function Code 06)........................................................... 138
Diagnostics (Function Code 08) ............................................................................ 139
Force Multiple Coils (Function Code 15) ............................................................... 141
Preset Multiple Registers (Function Code 16) ...................................................... 142
Modbus Exception Responses .............................................................................. 143
Using the Optional Add-On Instruction Rung Import ............................................. 146
Before You Begin .................................................................................................. 146
Overview................................................................................................................ 146
Installing the Rung Import with Optional Add-On Instruction ................................ 147
Reading the Ethernet Settings from the Module ................................................... 150
Writing the Ethernet Settings to the Module.......................................................... 152
Reading the Clock Value from the Module............................................................ 153
Writing the Clock Value to the Module .................................................................. 154
Adding the Module to an Existing Project ............................................................. 155
Using the Sample Program ................................................................................... 158
Opening the Sample Program in RSLogix ............................................................ 158
Choosing the Controller Type ............................................................................... 160
Selecting the Slot Number for the Module ............................................................ 161
Downloading the Sample Program to the Processor ............................................ 162
Support, Service & Warranty
163
Contacting Technical Support ......................................................................................................... 163
6.1
Return Material Authorization (RMA) Policies and Conditions.............................. 165
6.1.1
Returning Any Product .......................................................................................... 165
6.1.2
Returning Units Under Warranty ........................................................................... 165
6.1.3
Returning Units Out of Warranty ........................................................................... 166
6.2
LIMITED WARRANTY........................................................................................... 166
6.2.1
What Is Covered By This Warranty ....................................................................... 167
6.2.2
What Is Not Covered By This Warranty ................................................................ 167
6.2.3
Disclaimer Regarding High Risk Activities ............................................................ 168
6.2.4
Intellectual Property Indemnity .............................................................................. 168
6.2.5
Disclaimer of all Other Warranties ........................................................................ 169
6.2.6
Limitation of Remedies ** ...................................................................................... 170
6.2.7
Time Limit for Bringing Suit ................................................................................... 170
6.2.8
No Other Warranties ............................................................................................. 170
6.2.9
Allocation of Risks ................................................................................................. 170
6.2.10
Controlling Law and Severability ........................................................................... 171
Index
ProSoft Technology, Inc.
June 14, 2011
173
Page 7 of 175
Contents
User Manual
Page 8 of 175
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Guide to the MVI56E-MNETR User Manual
User Manual
Guide to the MVI56E-MNETR User Manual
Function
Section to Read
Details
Introduction
(Must Do)
→
Start Here (page 11) This section introduces the customer to the
module. Included are: package contents,
system requirements, hardware installation, and
basic configuration.
Diagnostic and
Troubleshooting
→
Diagnostics and
Troubleshooting
(page 91)
This section describes Diagnostic and
Troubleshooting procedures.
Reference
→
Reference (page
109)
These sections contain general references
associated with this product, Specifications, and
the Functional Overview.
Product Specifications
Product
Specifications (page
110)
Functional Overview
Functional Overview
(page 112)
Support, Service, and
Warranty
→
Support, Service
and Warranty (page
163)
Index
This section contains Support, Service and
Warranty information.
Index of chapters.
Index
ProSoft Technology, Inc.
June 14, 2011
Page 9 of 175
Guide to the MVI56E-MNETR User Manual
User Manual
Page 10 of 175
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1
Start Here
User Manual
Start Here
In This Chapter
What's New? ......................................................................................... 12
System Requirements ........................................................................... 13
Package Contents ................................................................................. 14
Setting Jumpers .................................................................................... 15
Installing the Module in the Rack........................................................... 16
Installing the Configuration Tools .......................................................... 17
Connecting Your PC to the Module ....................................................... 18
Setting Temporary IP Address .............................................................. 19
Connecting to the Module's Web Page ................................................. 26
Uploading the Add-On Instruction from the Module............................... 27
Creating a New RSLogix 5000 Project .................................................. 27
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-MNETR module’s application port(s)
ProSoft Technology, Inc.
June 14, 2011
Page 11 of 175
Start Here
User Manual
1.1
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
What's New?
MVI56E products are backward compatible with existing MVI56 products,
ladder logic, and module configuration files already in use. Easily swap and
upgrade products while benefiting from an array of new features designed to
improve interoperability and enhance ease of use.
Web Server: The built-in web server and web page allow access to manuals
and other tools previously provided only on a product CD-ROM or from the
ProSoft Technology® web site.
ProSoft Configuration Builder (PCB): New Windows software for
diagnostics, connecting via the module's Ethernet port or CIPconnect®, to
upload/download module configuration information and access
troubleshooting features and functions.
ProSoft Discovery Service (PDS): Utility software to find and display a list
of MVI56E modules on the network and to temporarily change an IP address
to connect with a module's web page.
CIPconnect-enabled: Allows PC-to-module configuration and diagnostics
from the Ethernet network through a ControlLogix 1756-ENBT EtherNet/IP™
module.
Personality Module: An industrial compact flash memory card storing the
module’s complete configuration and Ethernet settings, allowing quick and
easy replacement.
LED Scrolling Diagnostic Display: 4-character, alphanumeric display,
providing standard English messages for status and alarm data, and for
processor and network communication status.
Page 12 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.2
Start Here
User Manual
System Requirements
The MVI56E-MNETR module requires the following minimum hardware and
software components:
Rockwell Automation ControlLogix® processor (firmware version 10 or
higher), with compatible power supply, and one free slot in the rack for the
MVI56E-MNETR module. The module requires 800 mA of available 5 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)
ProSoft Discovery Service (PDS) (included in PCB)
Pentium® II 450 MHz minimum. Pentium III 733 MHz (or better)
recommended
Supported operating systems:
®
o Microsoft Windows Vista
o Microsoft Windows XP Professional with Service Pack 1 or 2
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)
CD-ROM drive
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.
ProSoft Technology, Inc.
June 14, 2011
Page 13 of 175
Start Here
User Manual
1.3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Package Contents
The following components are included with your MVI56E-MNETR module, and
are all required for installation and configuration.
Important: Before beginning the installation, please verify that all of the following items are
present.
Qty.
Part Name
Part Number
Part Description
1
MVI56E-MNETR
Module
MVI56E-MNETR
Modbus TCP/IP Interface Module with
Reduced Data Block
1
Cable
RL-CBL025
5-foot Ethernet Straight-Through Cable
(Gray)
1
ProSoft Solutions CD
CD-013
Contains configuration tools for the
MVI56E-MNETR module
1
Insert
MVI56E-MNETR Quick Start Guide
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
Page 14 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.4
Start Here
User Manual
Setting Jumpers
The Setup Jumper acts as "write protection" for the module’s flash memory. In
"write protected" mode, the Setup pins are not connected, and the module’s
firmware cannot be overwritten. Do not jumper the Setup pins together unless
you are directed to do so by ProSoft Technical Support.
The following illustration shows the MVI56E-MNETR jumper configuration.
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.
ProSoft Technology, Inc.
June 14, 2011
Page 15 of 175
Start Here
User Manual
1.5
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Installing the Module in the Rack
If you have not already installed and configured your ControlLogix processor and
power supply, please do so before installing the MVI56E-MNETR 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 MVI56EMNETR into the ControlLogix chassis. Use the same technique recommended by
Rockwell Automation to remove and install ControlLogix modules.
You can install or remove ControlLogix system components while chassis power
is applied and the system is operating. However, please note the following
warning.
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 your 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
3
With a firm, steady push, snap the module into place.
Check that the holding clips on the top and bottom of the module are securely
in the locking holes of the rack.
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.
Turn power ON.
4
5
Page 16 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.6
Start Here
User Manual
Installing the Configuration Tools
1.6.1 Installing ProSoft Configuration Builder
To install ProSoft Configuration Builder from the CD-ROM
1
Insert the ProSoft Solutions CD-ROM into the CD drive of your PC. Wait for
the startup screen to appear.
2
On the startup screen, click INSTALL PROSOFT CONFIGURATION BUILDER. This
action starts the installation wizard for ProSoft Configuration Builder.
Click NEXT on each page of the installation wizard. Click FINISH on the last
page of the wizard.
3
ProSoft Technology, Inc.
June 14, 2011
Page 17 of 175
Start Here
User Manual
1.7
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Connecting Your PC to the Module
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).
Page 18 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.8
Start Here
User Manual
Setting Temporary IP Address
Important: ProSoft Configuration Builder locates MVI56E-MNETR 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
Click the START button, and then navigate to PROGRAMS / PROSOFT
TECHNOLOGY.
2
Click to start PROSOFT CONFIGURATION BUILDER.
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.
3
Use the mouse to select DEFAULT MODULE in the tree view, and then click the
right mouse button to open a shortcut menu.
ProSoft Technology, Inc.
June 14, 2011
Page 19 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4
On the shortcut menu, select CHOOSE MODULE TYPE. This action opens the
Choose Module Type dialog box.
5
In the Product Line Filter area of the dialog box, select MVI56E. In the
SELECT MODULE TYPE dropdown list, select MVI56E-MNETR, and then click
OK to save your settings and return to the ProSoft Configuration Builder
window.
Right-click the module icon.
6
Page 20 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
7
Start Here
User Manual
On the shortcut menu, choose DIAGNOSTICS.
This action opens the Diagnostics dialog box.
ProSoft Technology, Inc.
June 14, 2011
Page 21 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
If there is no response from the module,
1
Click the SET UP CONNECTION button to browse for the module’s IP address.
2
On the Connection Setup dialog box, click the TEST CONNECTION button to
verify if the module is accessible with the current settings.
3
If PCB is still unable to connect to the module, click the BROWSE DEVICE(S)
button to open the ProSoft Discovery Service.
Page 22 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
4
Select the module, then right-click and choose ASSIGN TEMPORARY IP.
5
The module’s default IP address is 192.168.0.250.
6
Choose an unused IP within your subnet, and then click OK.
ProSoft Technology, Inc.
June 14, 2011
Page 23 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.8.1 Using CIPconnect to Connect to the Module
You can use CIPconnect® to connect a PC to the MVI56E-MNETR module over
Ethernet using Rockwell Automation’s 1756-ENBT EtherNet/IP® module. This
allows you to configure the MVI56E-MNETR 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-MNETR in the destination ControlLogix
chassis (the last ENBT/CNBx and chassis in the path).
To use CIPconnect, follow these steps.
1 In the Select Connection Type dropdown list, choose 1756-ENBT. The
default path appears in the text box, as shown in the following illustration.
Page 24 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
Start Here
User Manual
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-MNETR module. The first connection from the PC is always a 1756ENBT (Ethernet/IP) module.
Each row corresponds to a physical rack in the CIP path.
If the MVI56E-MNETR module is located in the same rack as the first 1756ENBT module, select RACK NO. 1 and configure the associated parameters.
If the MVI56E-MNETR is available in a remote rack (accessible through
ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).
Parameter
Source Module
Source Module IP Address
Source Module Node Address
Destination Module
Destination Module Slot Number
Description
Source module type. This field is automatically selected
depending on the destination module of the last rack
(1756-CNB or 1756-ENBT).
IP address of the source module (only applicable for
1756-ENBT)
Node address of the source module (only applicable for
1756-CNB)
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.
The slot number where the destination MVI56E module is
located.
To use the CIPconnect Path Editor, follow these steps.
1 Configure the path between the 1756-ENBT connected to your PC and the
MVI56E-MNETR 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.
ProSoft Technology, Inc.
June 14, 2011
Page 25 of 175
Start Here
User Manual
1.9
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Connecting to the Module's Web Page
1
2
In ProSoft Discovery Service, select the module to configure, and then click
the right mouse button to open a shortcut menu.
On the shortcut menu, choose VIEW MODULE’S WEBPAGE.
The web page contains the product documentation and sample programs.
Important: The temporary IP address is only valid until the next time the module is initialized.
Please refer to Setting Temporary IP Address (page 19) in the MVI56E-MNETR User Manual for
information on how to set the module’s permanent IP address.
Page 26 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.10
Start Here
User Manual
Uploading the Add-On Instruction from the Module
Configuration and control information for the MVI56E-MNETR module is provided
as an Add-On Instruction for RSLogix 5000, version 16 or higher.
Two Add-On Instructions are provided:
The Rung Import with Sample Program Add-On Instruction:
MVI56EMNETR_AddOn_Rung_v1_3.L5X
Includes the user-defined data types, data objects and ladder logic required
to configure the MVI56E-MNETR module.
The Rung Import with Utility Add-On Instruction (Optional):
MVI56EMNETR_Optional_Rung_v1_0.L5X
If your processor uses an earlier version of RSLogix 5000, see Using the Sample Program (page
158).
1.11
Creating a New RSLogix 5000 Project
1
Open the FILE menu, and then choose NEW.
ProSoft Technology, Inc.
June 14, 2011
Page 27 of 175
Start Here
User Manual
2
3
4
5
6
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Select your ControlLogix controller model.
Select REVISION 16.
Enter a name for your controller, such as My_Controller.
Select your ControlLogix chassis type.
Select SLOT 0 for the controller.
Note: If you are installing the MVI56E-MNETR module in a remote rack, follow these next few
steps. If you are installing the module in a local rack, follow the steps in Create the Module - Local
Rack (page 33).
1.11.1 Create the Remote Network
1
Right-click I/O CONFIGURATION and choose NEW MODULE…
Page 28 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
Start Here
User Manual
Expand the COMMUNICATIONS module selections and then select the Ethernet
Bridge module that matches your hardware. This example uses a 1756ENBT/A module.
Note: If you are prompted to "Select Major Revision", choose the lower of the available revision
numbers.
3
Name the ENBT/A module, then set the IP Address and slot location in the
local rack with the ControlLogix processor.
4
Click OK.
ProSoft Technology, Inc.
June 14, 2011
Page 29 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5
Next, select the 1756-ENBT module that you just created in the Controller
Organization pane and click the right mouse button to open a shortcut menu.
On the shortcut menu, choose NEW MODULE.
6
Repeat steps 2 and 3 to add the second EtherNet/IP module to the remote
rack.
1.11.2 Create the Module - Remote Rack
1
Next, select the remote 1756 BACKPLANE node in the Controller Organization
pane underneath the remote rack EtherNet/IP module you just created and
click the right mouse button to open a shortcut menu. On the shortcut menu,
choose NEW MODULE.
Page 30 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
This action opens the SELECT MODULE dialog box.
2
Select the 1756-MODULE (GENERIC 1756 MODULE) from the list and click OK.
This action opens the NEW MODULE dialog box.
ProSoft Technology, Inc.
June 14, 2011
Page 31 of 175
Start Here
User Manual
3
4
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Set the Module Properties values as follows:
Parameter
Value
Name
Enter a module identification string. The recommended value is
MNETR.
Description
Enter a description for the module. Example: Modbus TCP/IP
Interface Module with Reduced Data Block.
Comm Format
Select DATA-INT (Very Important)
Slot
Enter the slot number in the rack where the MVI56E-MNETR
module will be installed.
Input Assembly Instance
1
Input Size
42
Output Assembly Instance
2
Output Size
42
Configuration Assembly Instance 4
Configuration Size
5
0
On the CONNECTION tab, set the RPI value for your project. Fifty (50)
milliseconds is usually a good starting value.
Page 32 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
The MVI56E-MNETR module is now visible in the I/O CONFIGURATION section
Note: If you are installing the MVI56E-MNETR module in a local rack, follow these next few steps.
If you are installing the module in a remote rack, follow the steps in Create the Module - Remote
Rack (page 28).
1.11.3 Create the Module - Local Rack
1
Add the MVI56E-MNETR 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.
ProSoft Technology, Inc.
June 14, 2011
Page 33 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
Select the 1756-MODULE (GENERIC 1756 MODULE) from the list and click OK.
This action opens the NEW MODULE dialog box.
3
Set the Module Properties values as follows:
Parameter
Value
Name
Enter a module identification string. The recommended value is
MNETR.
Description
Enter a description for the module. Example: Modbus TCP/IP
Interface Module with Reduced Data Block.
Comm Format
Select DATA-INT (Very Important)
Slot
Enter the slot number in the rack where the MVI56E-MNETR
module is to be installed.
Input Assembly Instance
1
Input Size
42
Output Assembly Instance
2
Output Size
42
Configuration Assembly Instance 4
Configuration Size
Page 34 of 175
0
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4
Start Here
User Manual
On the CONNECTION tab, set the RPI value for your project. Five (5)
milliseconds is usually a good starting value. Click OK to confirm.
The MVI56E-MNETR module is now visible in the I/O CONFIGURATION section
ProSoft Technology, Inc.
June 14, 2011
Page 35 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.11.4 Import Add-On Instruction
1
2
3
4
In the CONTROLLER ORGANIZATION window, expand the TASKS folder and
subfolder until you reach the MAINPROGRAM folder.
In the MAINPROGRAM folder, double-click to open the MAINROUTINE ladder.
Select an empty rung in the new routine, and then click the right mouse
button to open a shortcut menu. On the shortcut menu, choose IMPORT
RUNG…
Navigate to the location on your PC where you saved (page 27) the Add-On
Instruction (for example, "My Documents" or "Desktop"). Select the
MVI56EMNETR_ADDON_RUNG_V1_3.L5X file
Page 36 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
This action opens the IMPORT CONFIGURATION dialog box, showing the
controller tags that will be created.
o If you are installing the module in a Remote Rack, open the dropdown
menus for the Input and Output tags, and select the MNETR module in
the remote rack.
5
Click OK to confirm the import. RSLogix will indicate that the import is in
progress:
ProSoft Technology, Inc.
June 14, 2011
Page 37 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
When the import is complete, you will see the new Add-On Instruction rung in
the ladder.
The procedure has also imported new User Defined Data Types, data objects
and the Add-On instruction for your project.
6
Save the application and then download the sample ladder logic into the
processor.
Page 38 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
Adding Multiple Modules (Optional)
Important: If your application requires more than one MVI56-MNETR module into 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
This action opens the New Module dialog box.
ProSoft Technology, Inc.
June 14, 2011
Page 39 of 175
Start Here
User Manual
3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Fill in the module properties as follows:
Parameter
Value
Name
Enter a module identification string. Example: MNETR_2
Description
Enter a description for the module. Example: Modbus TCP/IP
Interface Module with Reduced Data Block
Comm Format
Select DATA-INT
Slot
Enter the slot number in the rack where the MVI56E-MNETR module
is located.
Input Assembly Instance
1
Input Size
42
Output Assembly Instance
2
Output Size
42
Configuration Assembly
Instance
4
Configuration Size
0
4
Click OK to confirm. The new module is now visible:
5
6
Expand the Tasks folder, and then expand the MainTask folder.
On the MainProgram folder, click the right mouse button to open a shortcut
menu. On the shortcut menu, choose NEW ROUTINE.
In the New Routine dialog box, enter the name and description of your
routine, and then click OK.
7
Page 40 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
8
Select an empty rung in the new routine, and then click the right mouse
button to open a shortcut menu. On the shortcut menu, choose "IMPORT
RUNG…".
9
Select the file MVI56(E)MNETR_AddOn_Rung_<Version#>.L5X
ProSoft Technology, Inc.
June 14, 2011
Page 41 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
This action opens the IMPORT CONFIGURATION dialog box, showing the
controller tags that will be created.
10 Associate the I/O connection variables to the correct module. The default
values are Local:1:I and Local:1:O so these require change.
Page 42 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
Change the default tags MNETR and AOI56MNETR to avoid conflict with
existing tags. This procedure will append the string "_2" as follows:
Or, in a Remote Rack application…
ProSoft Technology, Inc.
June 14, 2011
Page 43 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
11 Click OK to confirm.
Page 44 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
Or, in a Remote Rack application…
ProSoft Technology, Inc.
June 14, 2011
Page 45 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Adjusting the Input and Output Array Sizes (Optional)
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.
The MVI56E-MNETR Add-On Instruction rung is configured for 600 registers of
Read Data and 600 registers of Write Data, which is sufficient for most
applications. However, you can configure the sizes of these data areas to meet
the needs of your application.
1 In ProSoft Configuration Builder, expand the Module icon in the tree view and
double-click MODULE to open an Edit window. Change the READ REGISTER
COUNT to contain the number of words for your Read Data area.
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.
To modify the WriteData array, follow the above steps, substituting WriteData
for ReadData. Also, 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 Read Register Start
parameter must be set to a value of 2000 or greater in ProSoft Configuration
Builder.
3 Save and download the sample configuration to the module (page 69)
It is unnecessary to manually edit the ReadData and WriteData user-defined data
types in the ladder logic, as these are automatically updated to match the
changed array sizes in ProSoft Configuration Builder.
2
Page 46 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Start Here
User Manual
1.11.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. It is not mandatory that you use the
processor's serial interface. You may access the processor through whatever
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.
June 14, 2011
Page 47 of 175
Start Here
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
1.11.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
2
3
4
If you are not already online with the processor, 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.
When communication is established, RSLogix 5000 will open a confirmation
dialog box. Click the DOWNLOAD button to transfer the sample program to the
processor.
RSLogix 5000 will compile the program and transfer it to the processor. This
process may take a few minutes.
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 48 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
Configuring the MVI56E-MNETR Module
User Manual
Configuring the MVI56E-MNETR Module
In This Chapter
Using ProSoft Configuration Builder Software ....................................... 50
Downloading the Project to the Module ................................................. 69
Using CIPconnect to Connect to the Module ....................................... 71
ProSoft Technology, Inc.
June 14, 2011
®
Page 49 of 175
Configuring the MVI56E-MNETR Module
User Manual
2.1
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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-MNETR module receives its protocol and
backplane configuration information from the installed Personality Module (Compact Flash). Use
ProSoft Configuration Builder to configure module settings and to download changes to the
Personality Module.
Page 50 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
2.1.1 Setting Up the Project
To begin, start PROSOFT CONFIGURATION BUILDER (PCB).
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-MNETR module to the project.
1 Use the mouse to select DEFAULT MODULE in the tree view, and then click the
right mouse button to open a shortcut menu.
ProSoft Technology, Inc.
June 14, 2011
Page 51 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
On the shortcut menu, select CHOOSE MODULE TYPE. This action opens the
Choose Module Type dialog box.
3
In the Product Line Filter area of the dialog box, select MVI56E. In the
SELECT MODULE TYPE dropdown list, select MVI56E-MNETR, and then click
OK to save your settings and return to the ProSoft Configuration Builder
window.
Page 52 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
2.1.2 Renaming PCB Objects
Notice that the contents of the information pane and the configuration pane
changed when you added the module to the project.
At this time, you may wish to rename the Default Project and Default Location
folders in the tree view.
1 Select the object, and then click the right mouse button to open a shortcut
menu. From the shortcut menu, 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 on the [+] sign next to the module icon to expand module information.
2
Click on the [+] sign next to any
configuration options.
3
4
Double-click any
icon to open an Edit dialog box.
To edit a parameter, select the parameter in the left pane and make your
changes in the right pane.
Click OK to save your changes.
5
icon to view module information and
Printing a Configuration File
1 Select the module icon, and then click the right mouse button to open a
shortcut menu.
2 On the shortcut menu, choose VIEW CONFIGURATION. This action opens the
View Configuration window.
3 In the View Configuration window, open the FILE menu, and choose PRINT.
This action opens the Print dialog box.
4 In the Print dialog box, choose the printer to use from the drop-down list,
select printing options, and then click OK.
ProSoft Technology, Inc.
June 14, 2011
Page 53 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2.1.3 Module
This section of the configuration describes the database setup and module level
parameters. This section provides the module with a unique name, identifies the
method of failure for the communications for the module if the processor is not in
RUN mode, and describes how to initialize the module upon startup.
Error/Status Pointer
-1 to 4955
Starting register location in virtual Modbus database for the error/status table. If a
value of -1 is entered, the error/status data will not be placed in the database. All
other valid values determine the starting location of the data. This data area
includes the module version information and all error/status data.
Read Register Start
0 to 4999
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.
Note: Total user database memory space is limited to the first 5000 registers of module memory,
addresses 0 through 4999. Therefore, the practical limit for this parameter is 4999 minus the value
entered for Read Register Count, so that the Read Data Area does not try to extend above address
4999. Read Data and Write Data Areas must be configured to occupy separate address ranges in
module memory and should not be allowed to overlap.
Read Register Count
0 to 5000
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 5000 words.
Note: Total Read Register Count and Write Register Count cannot exceed 5000 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.
Page 54 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Write Register Start
0 to 4999
The Write Register Start parameter specifies the start of the Write Data area in
module memory. Data in this area will be transferred in from the processor.
Note: Total user database memory space is limited to the first 5000 registers of module memory,
addresses 0 through 4999. Therefore, the practical limit for this parameter is 4999 minus the value
entered for Write Register Count, so that the Write Data Area does not try to extend above address
4999. 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 Count
0 to 5000
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 5000 words.
Note: Total Read Register Count and Write Register Count cannot exceed 5000 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.
Failure Flag Count
0 through 65535
This parameter specifies the number of successive transfer errors that must
occur before halting communication on the application port(s). If the parameter is
set to 0, the application port(s) will continue to operate under all conditions. If the
value is set larger than 0 (1 to 65535), communications will cease if the specified
number of failures occur.
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.
ProSoft Technology, Inc.
June 14, 2011
Page 55 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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.
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.4 MNET Client x
This section defines general configuration for the MNET Client (Master).
Error/Status Pointer
-1 to 4990
Starting register location in virtual database for the error/status table for this
Client. If a value of -1 is entered, the error/status data will not be placed in the
database. All other valid values determine the starting location of the data.
Command Error Pointer
-1 to 4999
This parameter sets the address in the internal database where the Command
Error List data will be placed so that it may be moved to the processor and
placed into the ReadData array. Therefore, 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.
Page 56 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Minimum Command Delay
0 to 65535 milliseconds
This parameter specifies the number of milliseconds to wait between the initial
issuances of a command. This parameter can be used to delay all commands
sent to Servers to avoid "flooding" 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 upon the type of communication network used, and the expected
response time of the slowest device on the network.
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 Server driver will respond to Function Code 3, 6, and
16 commands (read and write Holding Registers) from a remote Client when it is
moving 32-bit floating-point data.
If the remote Client 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 Server 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 Client for write commands. Example: Count = 10,
Server driver will send 20 16-bit registers for 10 total 32-bit floating-point values.
If, however, the remote Client 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 Float Start and Float Offset parameters to
appropriate values whenever the Float Flag parameter is set to YES.
Float Start
F0 to 65535
This parameter defines the first register of floating-point data. All requests with
register values greater than or equal to this value will be considered floating-point
data requests. This parameter is only used if the Float Flag is enabled. For
example, if a value of 7000 is entered, all requests for registers 7000 and above
will be considered as floating-point data.
ProSoft Technology, Inc.
June 14, 2011
Page 57 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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 Float Flag 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.
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.
2.1.5 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-MNETR communication
module, and the second part contains information required to interface to the
Modbus TCP/IP server device.
Page 58 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Command List Overview
In order to interface the MVI56E-MNETR 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 100 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.
Write commands have a special feature, as they can be set to execute only if the
data in the write command changes. If the register data values in the command
have not changed since the command was last issued, the command will not be
executed.
If the data in the command has changed since the command was last issued, the
command will be executed. Use of this feature can lighten the load on the
network. To implement this feature, set the enable code for the command to
CONDITIONAL (2).
ProSoft Technology, Inc.
June 14, 2011
Page 59 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Command Entry Formats
The following table shows the structure of the configuration data necessary for
each of the supported commands.
1
2
3
Enable Internal Poll Interval
Code Address Time
4
5
6
7
Count
Swap IP Address Serv
Code
Port
8
9
10
Slave
Node
Function Code
Device Modbus
Address
Code
Register 1/10th Seconds Bit
(bit)
Count
0
IP Address
Port # Address
Read Coil (0x)
Register
Code
Register 1/10th Seconds Bit
(bit)
Count
0
IP Address
Port # Address
Read Input (1x)
Register
Code
Register 1/10th Seconds Word
Count
Code
IP Address
Port # Address
Read Holding
Registers (4x)
Register
Code
Register 1/10th Seconds Word
Count
0
IP Address
Port # Address
Read Input Registers Register
(3x)
Code
1 bit
1/10th Seconds Bit
Count
0
IP Address
Port # Address
Force (Write) Single
Coil (0x)
Code
1 bit
1/10th Seconds Word
Count
0
IP Address
Port # Address
Preset (Write) Single Register
Register (4x)
Code
Register 1/10th Seconds Bit
(bit)
Count
0
IP Address
Port # Address
Force (Write)
Multiple Coil (0x)
Code
Register 1/10th Seconds Word
Count
0
IP Address
Port # Address
Preset (Write)
Register
Multiple Register (4x)
Register
Register
The first part of the record is the module information, which relates to the MVI56E
module and the second part contains information required to interface to the
server device.
Command list example:
Page 60 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Enable
NO (0), YES (1), or CONDITIONAL (2)
This field defines whether the command is to be executed and under what
conditions.
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. If the Poll Interval time is set to a nonzero value, the
command will be executed when the interval timer expires.
CONDITIONAL (2) The command will execute only if the internal data associated with the
command changes. This value is valid only for write commands.
Internal Address
0 to 4999 (for word-level addressing)
or
0 to 65535 (for bit-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 bitlevel address.
For Modbus functions 3, 4, 6, and 16, this parameter is interpreted as a wordor register-level address.
Poll Interval
0 to 65535
This parameter specifies the minimum interval to execute continuous commands
(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.
ProSoft Technology, Inc.
June 14, 2011
Page 61 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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.
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.
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)
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.
Page 62 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Service Port
502 or other supported ports on 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). If a
server implementation supports another service port, enter the value here.
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.
Note: Use the Node IP Address parameter (page 62) to address commands to a remote Modbus
TCP/IP device.
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, 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.
Modbus Function Code
Description
1
Read Coil Status
2
Read Input Status
3
Read Holding Registers
4
Read Input Registers
5
Force (Write) Single Coil
6
Preset (Write) Single Register
15
Force Multiple Coils
16
Preset Multiple Registers
ProSoft Technology, Inc.
June 14, 2011
Page 63 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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).
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 35 alphanumeric characters
Page 64 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
2.1.6 MNET Servers
This section contains database offset information used by the servers when
accessed by external Clients. These offsets can be utilized to segment the
database by data type.
Float Flag
YES or NO
This flag specifies how the Server driver will respond to Function Code 3, 6, and
16 commands (read and write Holding Registers) from a remote Client when it is
moving 32-bit floating-point data.
If the remote Client 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 Server 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 Client for write commands. Example: Count = 10,
Server driver will send 20 16-bit registers for 10 total 32-bit floating-point values.
If, however, the remote Client 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 Float Start and Float Offset parameters to
appropriate values whenever the Float Flag parameter is set to YES.
ProSoft Technology, Inc.
June 14, 2011
Page 65 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Float Start
F0 to 65535
This parameter defines the first register of floating-point data. All requests with
register values greater than or equal to this value will be considered floating-point
data requests. This parameter is only used if the Float Flag is enabled. For
example, if a value of 7000 is entered, all requests for registers 7000 and above
will be considered as floating-point data.
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 Float Flag 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.
Output Offset
0 to 4999
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 4999
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 4999
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.
Page 66 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
Word Input Offset
0 to 4999
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.
2.1.7 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 MVI56EMNETR 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.
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.
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 occur.
ProSoft Technology, Inc.
June 14, 2011
Page 67 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
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.
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 occur.
2.1.8 Ethernet Configuration
Use this procedure to configure the Ethernet settings for your module. You must
assign an IP address, subnet mask and gateway address. After you complete
this step, you can connect to the module with an Ethernet cable.
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).
When you are finished editing, click OK to save your changes and return to
the ProSoft Configuration Builder window.
4
Page 68 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2.2
Configuring the MVI56E-MNETR Module
User Manual
Downloading the Project to the Module
In order for the module to use the settings you configured, you must download
(copy) the updated Project file from your PC to the module.
1 In the tree view in ProSoft Configuration Builder, click once to select the
MVI56E-MNETR module.
2 Open the PROJECT menu, and then choose MODULE / DOWNLOAD.
This action opens the Download dialog box. Notice that the Ethernet address
field contains the temporary IP address you assigned in the previous step.
ProSoft Configuration Builder will use this temporary IP address to connect to
the module.
Click TEST CONNECTION to verify that the temporary IP address is correct.
If the connection succeeds, click DOWNLOAD to transfer the Ethernet
configuration to the module.
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.
3
ProSoft Technology, Inc.
June 14, 2011
Page 69 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
On the Download dialog box, click BROWSE DEVICES to open ProSoft
Discovery Service.
3
Select the module, and then click the right mouse button to open a shortcut
menu. On the shortcut menu, choose SELECT FOR PCB.
Close ProSoft Discovery Service.
Click DOWNLOAD to transfer the configuration to the module.
4
5
Page 70 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2.3
Configuring the MVI56E-MNETR Module
User Manual
Using CIPconnect® to Connect to the Module
You can use CIPconnect® to connect a PC to the ProSoft Technology MVI56EMNETR module over Ethernet using Rockwell Automation’s 1756-ENBT
EtherNet/IP® module. This allows you to configure the MVI56E-MNETR network
settings and view 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 slot number of the MVI56E-MNETR in the destination ControlLogix
chassis (the last ENBTx and chassis in the path).
To use CIPconnect, follow these steps.
1 In the Select Port dropdown list, choose 1756-ENBT. The default path
appears in the text box, as shown in the following illustration.
2
Click CIP PATH EDIT to open the CIPconnect Path Editor dialog box.
ProSoft Technology, Inc.
June 14, 2011
Page 71 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
The CIPconnect Path Editor allows you to define the path between the PC and
the MVI56E-MNETR module. The first connection from the PC is always a 1756ENBT (Ethernet/IP) module.
Each row corresponds to a physical rack in the CIP path.
If the MVI56E-MNETR module is located in the same rack as the first 1756ENBT module, select RACK NO. 1 and configure the associated parameters.
If the MVI56E-MNETR is available in a remote rack (accessible through
ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).
Parameter
Description
Source Module
Source module type. This field is automatically selected
depending on the destination module of the last rack (1756CNB or 1756-ENBT).
Source Module IP Address
IP address of the source module (only applicable for 1756ENBT)
Source Module Node Address
Node address of the source module (only applicable for 1756CNB)
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 MVI56E module is
located.
To use the CIPconnect Path Editor, follow these steps.
1 Configure the path between the 1756-ENBT connected to your PC and the
MVI56E-MNETR 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.
The following examples should provide a better understanding on how to set up
the path for your network.
Page 72 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
2.3.1 Example 1: Local Rack Application
For this example, the MVI56E-MNETR module is located in the same rack as the
1756-ENBT that is connected to the PC.
Rack 1
Slot
Module
Network Address
0
ControlLogix Processor
-
1
Any
-
2
MVI56E-MNETR
-
3
1756-ENBT
IP=192.168.0.100
1
In the Download dialog box, click CIP PATH EDIT.
ProSoft Technology, Inc.
June 14, 2011
Page 73 of 175
Configuring the MVI56E-MNETR Module
User Manual
2
3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configure the path as shown in the following illustration, and click
CONSTRUCT CIP PATH to build the path in text format.
Click OK to close the CIPconnect Path Editor and return to the Download
dialog box.
Check the new path in the Download dialog box.
Page 74 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
4
Click TEST CONNECTION to verify that the physical path is available. The
following message should be displayed upon success.
5
Click OK to close the Test Connection pop-up and then click DOWNLOAD to
download the configuration files to the module through the path.
ProSoft Technology, Inc.
June 14, 2011
Page 75 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2.3.2 Example 2: Remote Rack Application
For this example, the MVI56E-MNETR module is located in a remote rack
accessible through ControlNet, as shown in the following illustration.
Rack 1
Slot
Module
Network Address
0
ControlLogix Processor
-
1
1756-CNB
Node = 1
2
1756-ENBT
IP=192.168.0.100
3
Any
-
Slot
Module
Network Address
0
Any
-
1
Any
-
2
Any
-
3
Any
-
4
Any
-
5
1756-CNB
Node = 2
6
MVI56E-MNETR
-
Rack 2
Page 76 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Configuring the MVI56E-MNETR Module
User Manual
1
In the Download dialog box, click CIP PATH EDIT.
2
Configure the path as shown in the following illustration and click CONSTRUCT
CIP PATH to build the path in text format.
Click OK to close the CIPconnect Path Editor and return to the Download
dialog box.
ProSoft Technology, Inc.
June 14, 2011
Page 77 of 175
Configuring the MVI56E-MNETR Module
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
3
Check the new path in the Download dialog box.
4
Click TEST CONNECTION to verify that the physical path is available. The
following message should be displayed upon success.
5
Click DOWNLOAD to download the configuration files to the module through
the path.
Page 78 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
3
Ladder Logic
User Manual
Ladder Logic
In This Chapter
MNETRMODULEDEF ........................................................................... 80
Modbus Message Data.......................................................................... 89
Ladder logic is required for managing communication between the MVI56EMNETR module and the processor. The ladder logic handles tasks such as:
Module backplane data transfer
Special block handling
Status data receipt
Additionally, a power-up handler may be needed to initialize the module’s
database and may clear some processor fault conditions.
The sample Import Rung with 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 Import Rung with Add-On
Instruction will work without modification.
ProSoft Technology, Inc.
June 14, 2011
Page 79 of 175
Ladder Logic
User Manual
3.1
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
MNETRMODULEDEF
All data related to the MVI56E-MNETR is stored in a user defined data type. An
instance of the data type is required before the module can be used. This is done
by declaring a variable of the data type in the CONTROLLER TAGS EDIT TAGS
dialog box.
The following table describes the structure of the object.
Name
Data Type
DATA
MNETRDATA (page These objects hold data to be transferred
81)
between the processor and the MVI56EMNETR module
Description
STATUS
MNETRSTATUS
(page 82)
This object views the status of the module.
CONTROL
MNETRCONTROL
(page 84)
This object contains the data structure required
for the processor to request special tasks from
the module
UTIL
MNETRUTIL (page
87)
This data object stores the variables required
for the data transfer between the processor
and the module.
This object contains objects that define the configuration, user data, status and
command control data related to the module. Each of these object types is
discussed in the following topics of the document.
Page 80 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ladder Logic
User Manual
3.1.1 MNETRDATA
This object holds data to be transferred between the processor and the MVI56EMNETR module. The user data is the read and write data transferred between
the processor and the module as "pages" of data up to 40 words long.
Name
Data Type
Description
ReadData
INT[600]
Data read from module
WriteData
INT[600]
Data to write to module
The read data (READDATA) is an array set to match the value entered in the
Read Register Count parameter of the MNET.CFG file. For ease of use, this
array should be dimensioned as an even increment of 40 words. This data is
paged up to 50 words at a time from the module to the processor. The ReadData
task places the data received into the proper position in the read data array. Use
this data for status and control in the ladder logic of the processor.
The write data (WRITEDATA) is an array set to match the value entered in the
Write Register Count parameter of the MNET.CFG file. For ease of use, this
array should be dimensioned as even increments of 40 words. This data is paged
up to 40 words at a time from the processor to the module. The WriteData task
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.
ProSoft Technology, Inc.
June 14, 2011
Page 81 of 175
Ladder Logic
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
3.1.2 MNETRSTATUS
This object views the status of the module. The MNETRSTATUS object shown
below is updated each time a read block is received by the processor. Use this
data to monitor the state of the module at a "real-time rate".
The following table describes the structure of this object.
Name
Data Type
Description
PassCnt
INT
Program cycle counter
ProductVersion
INT
Shows the module software version
ProductCode
INT[2]
This identifies the module product code
BlockStats
MNETRBLOCKSTATS
(page 82)
Status information for the data transfer
operations between the processor and the
module
Reserved1
INT
Reserved for future use
Reserved2
INT
Reserved for future use
MNETReq
INT
The number of MNET (Port 2000) requests
received
MNETResp
INT
The number of MNET (Port 2000) responses
sent
MBAPReq
INT
The number of MBAP (Port 502) requests
received
MBAPResp
INT
The number of MBAP (Port 502) responses
sent
ClientStatus
MNETRCLIENTSTATS Client Status Data
(page 83)
MNETRBLOCKSTATS
This status object contains a structure that includes the status information for the
data transfer operations between the processor and the module
(MNETRBLOCKSTATS). The following table describes the structure of this
object.
Name
Data Type
Description
Read
INT
Total number of read block transfers
Write
INT
Total number of write block transfers
Parse
INT
Total number of blocks parsed
Event
INT
Total number of event blocks received
Cmd
INT
Total number of command blocks received
Err
INT
Total number of block transfer errors
Page 82 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ladder Logic
User Manual
MNETRCLIENTSTATS
The status object contains a structure for the MNET Client Status
(MNETRCLIENTSTATS). The following table describes the structure of this
object.
Name
Data Type
Description
CmdReq
INT
Total number of command list requests sent
CmdResp
INT
Total number of command list responses
received
CmdErr
INT
Total number of command list errors
Requests
INT
Total number of requests for port
Responses
INT
Total number of responses for port
ErrSent
INT
Total number of errors sent
ErrRec
INT
Total number of errors received
CfgErrWord
INT
Configuration Error Word
CurErr
INT
Current Error code
LastErr
INT
Last recorded error code
Refer to MVI56E-MNETR Status Data Definition for a complete listing of the data
stored in the status object.
ProSoft Technology, Inc.
June 14, 2011
Page 83 of 175
Ladder Logic
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
3.1.3 MNETRCONTROL
Contains the data structure required for the processor to request special tasks
from the module. The command control task allows the processor to dynamically
enable commands configured in the port command list. The event command task
allows the processor to dynamically build any commands to be sent by the MNET
Client to a remote Server.
The following table describes the structure of this object.
Name
Data Type
Description
BootTimer
TIMER
Timer to clear warmboot and coldboot
WarmBoot
BOOL
Triggers a Cold Boot Command
ColdBoot
BOOL
Triggers a Warm Boot Command
EventCmdTrigger
BOOL
Triggers the Event Command.
EventCmd
MNETREVENTCMD (page This object contains the attributes to define a
84)
Master command. An array of these objects is
used for each port.
CmdControl
MNETRCMDCONTROL
(page 85)
Controls the execution of the commands listed
in the configuration under the [MNET Client 0
Commands] section.
PassThru
MNETRPASSTHRU (page
86)
Transfers a remote Client’s commands
through the MNETR Module straight into the
Processor’s Controller tags.
IPAddress
MNETIPADDRESS (page
86)
Getting and Setting IP address to and from
Module
MNETREVENTCMD
The MNETREVENTCMD structure holds the information required for an event
command. An array of this object should be defined and should hold the event
command set to be employed in the application. The following table describes
the structure of this object.
Name
IP0
IP1
IP2
IP3
ServPort
Data Type
INT
INT
INT
INT
INT
Node
DBAddress
Count
Swap
Function
Address
Result
INT
INT
INT
INT
INT
INT
INT
Page 84 of 175
Description
First digit of IP address
Second digit of IP address
Third digit of IP address
Last digit of IP address
TCP Service Port number (0-65535), 502 for
MBAP, 2000 for MNET
Modbus slave node address (0 to 247)
Module internal database for message
Register or data point count
Swap code for functions 3 and 4
Modbus function code for message
Address to interface with in device
Shows the result of the event that was sent
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ladder Logic
User Manual
MNETRCMDCONTROL
When the command bit
(MNETR.CONTROL.CMDCONTROL.CMDCONTROLTRIGGER) is set in the example
ladder logic, the module will build a block 9901 with the number of commands set
through: MNETR.CONTROL.CMDCONTROL.NUMBEROFCOMMANDS[0].
The command indexes will be set through the controller tags starting from
MNETR.CONTROL.CMDCONTROL.CMDINDEX[0] to
MNETR.CONTROL.CMDCONTROL.CMDINDEX[5]
For example, in order to enable commands 0, 2 and 5 the following values would
be set:
MNETR.CONTROL.CMDCONTROL.CMDINDEX[0] = 3
MNETR.CONTROL.CMDCONTROL.CMDINDEX[1] = 0
MNETR.CONTROL.CMDCONTROL.CMDINDEX[2] = 2
MNETR.CONTROL.CMDCONTROL.CMDINDEX[3] = 5
The module will receive this block and build and send the command to the
specified control device using a MSG block.
The following table describes the data for the command element in
MNETRCmdControl.
Name
Data Type
Description
CmdIndex
INT[6]
The position of the initial command to execute
from the Client command list.
NumberOfCommands
INT
The number of commands to execute from the
Client command list
CommandsAddedtoQueue
INT
Number of commands added to queue
CmdControlTrigger
BOOL
Trigger Command Control. User application
will activate this trigger.
ProSoft Technology, Inc.
June 14, 2011
Page 85 of 175
Ladder Logic
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
MNETRPASSTHRU
During pass-through operation, write messages received at the MVI56E-MNETR
server write messages through to the processor. It is the responsibility of the
ladder logic to process the message received using this feature. Two data
objects are required for this mode: a variable to hold the length of the message
and a buffer to hold the message.
This information is passed from the module to the processor using a block
identification code of 9996 if the unformatted pass-through mode (code 1) is
selected as the pass through mode in the configuration file. Word one of this
block contains the length of the message and the message starts at word 3.
Other controller tags are required to store the controlled values contained in
these messages. The Modbus protocol supports control of binary output (coils functions 5 and 15) and registers (functions 6 and 16).
Additionally, formatted message blocks can be sent from the module to the
processor when the pass-through option is selected using the format selection
(codes 2 or 3 in the MNET.CFG file). These blocks require less decoding than
the unformatted blocks. Refer to the user manual for a full discussion on utilizing
the pass-through option in an application.
The following table describes the structure of this object.
Name
Data Type
Description
MBControl1
CONTROL
Modbus pass thru message control
MBControl2
CONTROL
Modbus pass thru message control
MBMsg
SINT[500]
Message array
MBScratch
INT[3]
Temporary used ints
MBOffsetBit
INT
Offset bit in the message
MBOffset
INT
Start offset in the message
MBMsgLen
INT
The length of the Modbus message in bytes
mbdouble
DINT
Modbus double int tag
MBCoil
MNETRCOILARRA
Y (page 86)
Conversion from Bool to INT data types
Name
Data Type
Description
Boolean
BOOL[416]
Conversion from Bool to INT data types
MNETRCOILARRAY
MNETRIPADDRESS
Data structure to get and set the IP address of the module.
Name
Data Type
Description
IPGetTrigger
BOOL
Gets IP address
IPReceived
INT[4]
IP address received
IPSetTrigger
BOOL
Sets IP address
IPRequested
INT[4]
IP address set
Page 86 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ladder Logic
User Manual
3.1.4 MNETRUTIL
This data object stores the variables required for the data transfer between the
processor and the MVI56E-MNETR module.
Caution: These variables are for internal ladder usage only. Do not use these variables in your
own application, otherwise unpredictable results could occur.
he following table describes the structure of this object.
Name
LastRead
LastWrite
BlockIndex
ReadDataSizeGet
WriteDataSizeGet
ReadDataBlkCount
Data Type
INT
INT
INT
INT
INT
INT
WriteDataBlkCount
INT
RBTSremainder
INT
WBTSremainder
INT
IPsetPending
IPgetPending
InitOutputData
BOOL
BOOL
MNETRINITOUTDATA
(page 88)
Description
Index of last read block
Index of last write block
Computed block offset for data table
Gets ReadData Array Length.
Gets WriteData Array Length.
Holds the value of the Block Counts of the Read
Data Array. Array Size is divided by 40.
Holds the value of the Block Counts of the Write
Data Array. Array Size is divided by 40.
Holds remainder calculation value from the read
array.
Holds remainder calculation value from the write
array.
Allows Setting module IP address
Allows Getting module IP address
This is to initialize output data
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 Block
Index tag is an intermediate variable used during the block calculation.
ProSoft Technology, Inc.
June 14, 2011
Page 87 of 175
Ladder Logic
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
MNETRINITOUTDATA
Used to bring the Module into a known state after a restart operation.
Name
Data Type
Description
TriggerInitOut
BOOL
Trigger Output Data Initialization.
InitializeOutputData
INT
RetInitOutData
TriggerInitOutPending
INT[200]
BOOL
RetInitOutDataBlkID
INT
InitOutBlkIDLim
INT
Quantity of Blocks(200 words of "ReadData")
for the module to read from the PLC. [0 to 24]
means a qty of 1 to 25
Returned Initialization output data
Set after the ladder has sent an event cmd to
the module and is waiting for the status to be
returned
Returned Block ID for Returned Initialize
Output Data command.
Block Index Limit for ReadData size of the
array
Page 88 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
3.2
Ladder Logic
User Manual
Modbus Message Data
During pass-through operation, write messages received at the MVI56E-MNETR
server write messages through to the processor. It is the responsibility of the
ladder logic to process the message received using this feature. Two data
objects are required for this mode: a variable to hold the length of the message
and a buffer to hold the message.
This information is passed from the module to the processor using a block
identification code of 9996 if the unformatted pass-through mode (code 1) is
selected as the pass through mode in the configuration file. Word one of this
block contains the length of the message and the message starts at word 3.
Other controller tags are required to store the controlled values contained in
these messages. The Modbus protocol supports control of binary output (coils functions 5 and 15) and registers (functions 6 and 16).
Additionally, formatted message blocks can be sent from the module to the
processor when the pass-through option is selected using the format selection
(codes 2 or 3 in the MNET.CFG file). These blocks require less decoding than
the unformatted blocks. Refer to Pass-Through Control Blocks (page 122) for a
full discussion on utilizing the pass-through option in an application.
ProSoft Technology, Inc.
June 14, 2011
Page 89 of 175
Ladder Logic
User Manual
Page 90 of 175
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4
Diagnostics and Troubleshooting
User Manual
Diagnostics and Troubleshooting
In This Chapter
Reading Status Data from the Module .................................................. 92
The Diagnostics Menu ........................................................................... 93
Monitoring Module Information .............................................................. 97
Monitoring Backplane Information ......................................................... 97
Monitoring Database Information .......................................................... 99
Monitoring MNET Client Information ................................................... 100
Monitoring MNET Server Information .................................................. 101
LED Status Indicators .......................................................................... 102
Client Configuration Error Word .......................................................... 105
Clearing a Fault Condition ................................................................... 106
Troubleshooting................................................................................... 107
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.
ProSoft Technology, Inc.
June 14, 2011
Page 91 of 175
Diagnostics and Troubleshooting
User Manual
4.1
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reading Status Data from the Module
The MVI56E-MNETR module returns a Status Data block that can be used to
determine the module’s operating status. This data is located in the module’s
database at a location specified by the Error Status Pointer configuration
parameter. This data is transferred to the ControlLogix processor continuously.
The Configuration/Debug port provides the following functionality:
Full view of the module’s configuration data
View of the module’s status data
Complete display of the module’s internal database (registers 0 to 4999)
Version Information
Control over the module (warm boot, cold boot, transfer configuration)
Facility to upload and download the module’s configuration file
Page 92 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.2
Diagnostics and Troubleshooting
User Manual
The Diagnostics Menu
The Diagnostics menu, available through the Ethernet configuration port for this
module, is arranged as a tree structure, with the Main menu at the top of the tree,
and one or more submenus for each menu command. The first menu you see
when you connect to the module is the Main menu.
4.2.1 Using the Diagnostics Menu in ProSoft Configuration Builder
To connect to the module’s Configuration/Debug Ethernet port:
1 In ProSoft Configuration Builder, select the module, and then click the right
mouse button to open a shortcut menu.
ProSoft Technology, Inc.
June 14, 2011
Page 93 of 175
Diagnostics and Troubleshooting
User Manual
2
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
On the shortcut menu, choose DIAGNOSTICS.
This action opens the Diagnostics dialog box.
If there is no response from the module,
1
Click the SET UP CONNECTION button to browse for the module’s IP address.
Page 94 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
2
Diagnostics and Troubleshooting
User Manual
In the Connection Setup dialog box, click the TEST CONNECTION button to
verify if the module is accessible with the current settings.
You can also use CIPconnect® to connect to the module through a 1756ENBT card.
Refer to Using CIPconnect to Connect to the Module (page 71, page 24) for
information on how to construct a CIP path.
ProSoft Technology, Inc.
June 14, 2011
Page 95 of 175
Diagnostics and Troubleshooting
User Manual
3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
If PCB is still unable to connect to the module, click the BROWSE DEVICE(S)
button to open the ProSoft Discovery Service. Select the module, then right
click and choose SELECT FOR PCB.
Close ProSoft Discovery Service, and click the CONNECT button again.
4 If all of 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.
Page 96 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.3
Diagnostics and Troubleshooting
User Manual
Monitoring Module Information
Use the MODULE menu to view configuration and hardware information for the
MVI56E-MNETR module’s backplane and Ethernet application port.
4.3.1 Version
Use the VERSION menu to view module hardware and firmware information.
The values on this menu correspond with the contents of the module’s
Miscellaneous Status registers.
4.3.2 Config
Use the Configuration menu to view backplane configuration settings for the
MVI56E-MNETR module.
The information on this menu corresponds with the configuration information in
the Module settings in ProSoft Configuration Builder.
4.3.3 NIC Status
Use the NIC Status (Network Interface Card) menu to view configuration and
status information for the MVI56E-MNETR module's Ethernet application port.
The information on this menu is useful for troubleshooting Ethernet network
connectivity problems.
4.3.4 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 67) defines a list of static IP addresses that the
module will use when an ARP is required.
4.4
Monitoring Backplane Information
Use the BACKPLANE menu to view the backplane status information for the
MVI56E-MNETR module.
ProSoft Technology, Inc.
June 14, 2011
Page 97 of 175
Diagnostics and Troubleshooting
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.4.1 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 the members of the MVI56EMNETR Status object (page 131).
Page 98 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.5
Diagnostics and Troubleshooting
User Manual
Monitoring Database Information
Use the DATABASE menu to view the contents of the MVI56E-MNETR module’s
internal database. The data locations on this menu corresponds with the
MVI56E-MNETR Database Definition
You can view data in the following formats:
ASCII
Decimal
Float
Hexadecimal
Use the scroll bar on the right edge of the window to view each page (100 words)
of data.
ProSoft Technology, Inc.
June 14, 2011
Page 99 of 175
Diagnostics and Troubleshooting
User Manual
4.6
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Monitoring MNET Client Information
Use the MNET CLIENT menu to view the configuration and status information for
the MNET Client(s).
4.6.1 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 settings in 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.
4.6.2 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. Refer to Client Command Errors (page 128)
for an explanation of each value.
4.6.3 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.
4.6.4 Status
Use the Status menu to view status for MNET Client x. During normal operation,
the number of requests and responses should increment, while the number of
errors should not change.
Page 100 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.7
Diagnostics and Troubleshooting
User Manual
Monitoring MNET Server Information
Use the MNET SERVER menu to view the configuration and status information
for the MNET server.
4.7.1 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 (page 65).
4.7.2 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.
June 14, 2011
Page 101 of 175
Diagnostics and Troubleshooting
User Manual
4.8
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
LED Status Indicators
4.8.1 Scrolling LED Status Indicators
The scrolling LED display indicates the module's operating status as follows:
Initialization Messages
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 Advanced
Add-On Instruction.
C0 (Client): CmdCnt: X MinDly :
X CmdOffs: X RespTmout : X
Retries : X ErrOffs : X
ARPTmout : X ErrDelay : X
FltFlag : X FltSt : X FltOffs : X
SVR (server) : BIOffs: X WIOffs :
X OutOffs : X HoldOffs : X
FltFlag : X FltSt : X FltSt : X
CommTmout : X
After power up and every reconfiguration, the module will
display the configuration of the application port(s). The
information consists of:
Client
CmdCnt : number of commands configured for the Client
MinDly : Minimum Command Delay parameter
CmdOffs : Command Error Pointer parameter
RespTmout : Response Timeout parameter
Retries : Retry Count parameter
ErrOffs : Error/Status Offset parameter
ARPTmout : ARP Timeout parameter
ErrDelay: Command Error Delay parameter
FltFlag: Float Flag parameter
Flt St : Float Start parameter
FltOffs : Float Offset parameter
Server
BIOffs: Bit Input Offset parameter
WIOffs : Word Input Offset parameter
OutOffs : Output offset parameter
HoldOffs : Holding Register offset parameter
FltFlag: Float Flag parameter
FltSt : Float Start parameter
FltOffs : Float Offset parameter
Page 102 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Diagnostics and Troubleshooting
User Manual
Operati on Messag es
After the initialization step, the following message pattern will be repeated.
<Backplane Status> <IP Address> <Backplane Status> <Port Status>
Code
Message
<Backplane Status>
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".
<IP Address>
Module IP address
<C0>
OK: Port is communicating without error
Communication Errors: port is having communication errors.
Refer to Diagnostics and Troubleshooting (page 91) for further
information about the error.
4.8.2 Ethernet LED Indicators
The Ethernet LEDs indicate the module's Ethernet port status as follows:
LED
State
Description
Data
OFF
Ethernet connected at 10Mbps duplex speed
AMBER Solid
Ethernet connected at 100Mbps duplex speed
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.
Link
ProSoft Technology, Inc.
June 14, 2011
Page 103 of 175
Diagnostics and Troubleshooting
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.8.3 Non-Scrolling LED Status Indicators
The non-scrolling LEDs indicate the module’s operating status as follows:
LED Label
Color
Status
Indication
APP
Red or
Green
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-MNETR 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.
OK
ERR
Page 104 of 175
Red or
Green
Not Used
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.9
Diagnostics and Troubleshooting
User Manual
Client Configuration Error Word
If a configuration error is found for the Client, the Client Configuration Error Word
will have a value other than zero. The Configuration Error Word is a controller tag
in MNET.STATUS.ClientStats in the ladder logic.
The bits in the Configuration Error Word have the following definitions:
Bit
Description
Value
0
0x0001
1
0x0002
2
0x0004
3
0x0008
4
Invalid retry count parameter
0x0010
5
The float flag parameter is not valid.
0x0020
6
The float start parameter is not valid.
0x0040
7
The float offset parameter is not valid.
0x0080
8
The ARP Timeout is not in range (ARP Timeout parameter 0 or 0x0100
greater than 60000 milliseconds) and will default to 5000
milliseconds.
9
The Command Error Delay is > 300 and will default to 300.
0x0200
10
0x0400
11
0x0800
12
0x1000
13
0x2000
14
0x4000
15
0x8000
Correct any invalid data in the configuration for proper module operation. When
the configuration contains a valid parameter set, all the bits in the configuration
word will be clear. This does not indicate that the configuration is valid for the
user application. Make sure each parameter is set correctly for the specific
application.
ProSoft Technology, Inc.
June 14, 2011
Page 105 of 175
Diagnostics and Troubleshooting
User Manual
4.10
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Clearing a Fault Condition
Typically, if the OK LED on the front of the module turns RED for more than ten
seconds, a hardware problem has been detected in the module 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 that the card 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.
Page 106 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
4.11
Diagnostics and Troubleshooting
User Manual
Troubleshooting
Use the following troubleshooting steps if you encounter problems when the
module is powered up. If these steps do not resolve your problem, please contact
ProSoft Technology Technical Support.
Processor Errors
Problem Description
Steps to take
Processor Fault
Verify that the module is plugged into the slot that has been configured
for the module in the I/O Configuration of RSLogix.
Verify that 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-MNETR. Verify that all modules in the rack are correctly
configured in the ladder logic.
Module Errors
Problem Description
Steps to take
MVI56E modules with
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
Configuration/Debug 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
re-insert the card in the rack, and then restore power to the rack.
ProSoft Technology, Inc.
June 14, 2011
Page 107 of 175
Diagnostics and Troubleshooting
User Manual
Page 108 of 175
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5
Reference
User Manual
Reference
In This Chapter
Product Specifications ......................................................................... 110
Functional Overview ............................................................................ 112
Ethernet Cable Specifications ............................................................. 130
Status Data Definition .......................................................................... 131
Modbus Protocol Specification ............................................................ 132
Using the Optional Add-On Instruction Rung Import ........................... 146
Adding the Module to an Existing Project ............................................ 155
Using the Sample Program ................................................................. 158
ProSoft Technology, Inc.
June 14, 2011
Page 109 of 175
Reference
User Manual
5.1
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Product Specifications
The Modbus TCP/IP Client/Server Enhanced Communication Module with
Reduced Data Block allows Rockwell Automation® ControlLogix® processors to
interface easily with Modbus TCP/IP-compatible devices, such as Modicon
Programmable Automation Controllers (PACs) and a wide variety of Modbus
TCP/IP-compatible instruments and devices.
The MVI56E-MNETR uses a reduced Input/Output (I/O) data image block size for
transferring data between itself and a ControlLogix processor. This makes it ideal
for remote rack applications using ControlNet™ or EtherNet/IP™ process
networks. The module also works well for applications that require redundant
ControlLogix processors.
MVI56E-MNETR enhancements include local and remote configuration and
diagnostics through the module’s Ethernet port, CIPconnect® technology for
bridging though Rockwell Automation ControlNet and EtherNet/IP networks, and
an on-board web server for access to module documentation and sample
program files.
5.1.1 General Specifications
Reduced I/O image size designed specifically to optimize remote
rack implementations
Backward compatible with previous MVI56-MNETR versions
Single-slot 1756 ControlLogix backplane compatible
10/100 Mbps auto crossover detection Ethernet configuration and application
port
User-definable module data memory mapping of up to 5000 16-bit registers
CIPconnect-enabled network configuration and diagnostics monitoring using
ControlLogix 1756-ENxT and 1756-CNB modules and EtherNet/IP passthrough communication
ProSoft Configuration Builder (PCB) software supported, a Windows-based
graphical user interface providing simple product and network configuration
Sample ladder logic and Add-On Instructions (AOI) are used for data transfer
between module and processor
Internal web server provides access to product documentation, module
status, diagnostics, and firmware updates
4-character, alpha-numeric, scrolling LED display of status and diagnostics
data in plain English – no cryptic error or alarm codes to decipher
ProSoft Discovery Service (PDS) software used to locate the module on the
network and assign temporary IP address
Personality Module - a non-volatile, industrial-grade Compact Flash (CF) card
used to store network and module configuration, allowing quick in-the-field
product replacement by transferring the CF card
Page 110 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.1.2 Functional Specifications
The MVI56E-MNETR transfers data in small I/O blocks than the MVI56EMNET, which makes it ideal for installations in remote racks or where
bandwidth is limited.
Works well with redundant ControlLogix Programmable Automation
Controllers (PACs) using ControlNet.
Module appears to the ControlLogix processor as an input/output (I/O)
module
40-word scheduled I/O image blocks used for data transfers require
significantly less bandwidth than the MVI56E-MNET
Retrieving module status and executing special functions (command control,
event commands, etc.) are supported in ladder logic by special block transfer
codes
5.1.3 Hardware Specifications
Specification
Description
Backplane Current Load
800 mA @ 5 Vdc
3 mA @ 24 Vdc
Operating Temperature
0°C to 60°C (32°F to 140°F)
Storage Temperature
-40°C to 85°C (-40°F to 185°F)
Shock
30 g operational
50 g non-operational
Vibration: 5 g from 10 to 150 Hz
Relative Humidity
5% to 95% (without condensation)
LED Indicators
Battery Status (ERR)
Application Status (APP)
Module Status (OK)
4-Character, Scrolling, AlphaNumeric LED Display
Shows Module, Version, IP, Application Port
Setting, Port Status, and Error Information
Debug/Configuration/Application Ethernet port (E1)
Ethernet Port
10/100 Base-T, RJ45 Connector, for CAT5 cable
Link and Activity LED indicators
Auto-crossover cable detection
Shipped with Unit
5-foot Ethernet straight-through cable
ProSoft Technology, Inc.
June 14, 2011
Page 111 of 175
Reference
User Manual
5.2
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Functional Overview
5.2.1 About the MODBUS TCP/IP Protocol
MODBUS is a widely used protocol originally developed by Modicon in 1978.
Since that time, the protocol has been adopted as a standard throughout the
automation industry.
The original MODBUS specification uses a serial connection to communicate
commands and data between Client and server devices on a network. Later
enhancements to the protocol allow communication over Ethernet networks using
TCP/IP as a "wrapper" for the MODBUS protocol. This protocol is known as
MODBUS TCP/IP.
MODBUS TCP/IP is a Client/server protocol. The Client establishes a connection
to the remote server. When the connection is established, the Client sends the
MODBUS TCP/IP commands to the server. The MVI56E-MNETR module works
both as a Client and as a server.
Aside from the benefits of Ethernet versus serial communications (including
performance, distance, and flexibility) for industrial networks, the MODBUS
TCP/IP protocol allows for remote administration and control of devices over a
TCP/IP network. The efficiency, scalability, and low cost of a MODBUS TCP/IP
network make this an ideal solution for industrial applications.
The MVI56E-MNETR module acts as an input/output module between devices
on a MODBUS TCP/IP network and the Rockwell Automation backplane. The
module uses an internal database to pass data and commands between the
processor and the Client and server devices on the MODBUS TCP/IP network.
5.2.2 Module Power Up
On power up the module begins performing the following logical functions:
1 Initialize hardware components
o Initialize ControlLogix backplane driver
o Test and Clear all RAM
o Read configuration for module from MNET.CFG file on Compact Flash
Disk
2 Initialize Module Register space
3 Enable Server Drivers
4 Enable Client Driver
When the module has received the configuration, the module will begin
communicating with other nodes on the network, depending on the configuration.
Page 112 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.2.3 Backplane Data Transfer
The MVI56E-MNETR module communicates directly over the ControlLogix
backplane. Data is paged between the module and the ControlLogix processor
across the backplane using the module's input and output images. The update
frequency of the images is determined by the scheduled scan rate defined by the
user for the module and the communication load on the module. Typical updates
are in the range of 1 to 10 milliseconds.
This bi-directional transference of data is accomplished by the module filling in
data in the module's input image to send to the processor. Data in the input
image is placed in the Controller Tags in the processor by the ladder logic. The
input image for the module is set to 42 words. This data is transferred in the
scheduled I/O timeslot.
The processor inserts data to the module's output image to transfer to the
module. The module's program extracts the data and places it in the module's
internal database. The output image for the module is set to 42 words. This data
is transferred in the scheduled I/O timeslot.
The following illustration shows the data transfer method used to move data
between the ControlLogix processor, the MVI56E-MNETR module and the
Modbus TCP/IP Network.
All data transferred between the module and the processor over the backplane is
through the input and output images. Ladder logic must be written in the
ControlLogix processor to interface the input and output image data with data
defined in the Controller Tags. All data used by the module is stored in its internal
database. This database is defined as a virtual Modbus data table with
addresses from 0 (40001 Modbus) to 4999 (45000 Modbus). The following
illustration shows the layout of the database:
ProSoft Technology, Inc.
June 14, 2011
Page 113 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Module’s Internal Database Structure
5000 registers for user data
0
Register Data
4999
Data contained in this database is paged through the input and output images by
coordination of the ControlLogix ladder logic and the MVI56E-MNETR module's
program. Up to 40 words of data can be transferred from the module to the
processor at a time. Up to 40 words of data can be transferred from the
processor to the module. Each image has a defined structure depending on the
data content and the function of the data transfer. The module uses the following
block numbers:
Block Range
-1
0
1 to 125
1000 to 1124
2000
5001 to 5006
9956
9957
9958
9959
9960
9961
9970
9996
9998
9999
Descriptions
Status block
Status block
Read or write data
Output Initialization Blocks
Event Command Block
Command Control
Formatted pass-through block from function 6 or 16 with word data.
Formatted pass-through block from function 6 or 16 with floating-point data.
Formatted pass-through block from function 5.
Formatted pass-through block from function 15.
Formatted pass-through block from function 22.
Formatted pass-through block from function 23.
Function 99 indication block.
Unformatted Pass-through block with raw Modbus message.
Warm-boot control block
Cold-boot control block
These block identification codes can be broken down into a few groups: Normal
data transfer blocks (-1 to 125), Initialization blocks (1000 to 1124), Command
control blocks (2000, 5001 to 5006, 9998 and 9999) and pass-through function
blocks (9956 to 9961, 9970 and 9996).
Normal Data Transfer Blocks
Normal data transfer includes the paging of user data from the module’s internal
database (registers 0 to 4999), as well as paging of status data. These data are
transferred through read (input image) and write (output image) blocks.
The following topics describe the function and structure of each block.
Page 114 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
Status Read Data Block
This block is automatically copied from the module and contains status
information about the module.
Offset
0
1
2 to 7
8 to 9
10 to 11
12 to 13
14 to 23
24 to 25
26
27 to 40
41
Description
Write Block ID
Program Scan Counter
Block Transfer Status
Reserved Server Status
MNET Server Status
MBAP Server Status
MNET Client Status
Product Name
Product Version
Reserved
Read Block ID (-1 or 0)
Length
1
1
6
2
2
2
10
2
1
14
1
Client Status Data
Word Offset
3
4
5
6
7
8
9
10
11
12
Client Status
Total number of command list requests
Total number of command list responses
Total number of command list errors
Total number of requests of slave
Total number of responses
Total number of errors sent
Total number of errors received
Configuration Error Word
Current Error
Last Error
Block Request from Processor to Module
These blocks of data transfer information from the ControlLogix processor to the
module. The following table describes the structure of the output image.
Offset
Description
Length
0
Write Block ID
1
1 to 40
Write Data
40
41
Spare
1
The Write Block ID is an index value used to determine the location in the
module’s database where the data will be placed. Each transfer can move up to
40 words (block offsets 1 to 40) of data.
ProSoft Technology, Inc.
June 14, 2011
Page 115 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Block Response from Module to Processor
These blocks of data transfer information from the module to the ControlLogix
processor. The following table describes the structure of the input image.
Offset
Description
Length
0
Write Block ID
1
1 to 40
Read Data
40
41
Read Block ID
1
The Read Block ID is an index value used to determine the location of where the
data will be placed in the ControlLogix processor controller tag array of module
read data. Each transfer can move up to 40 words (block offsets 1 to 40) of data.
In addition to moving user data, the block also contains status data for the
module.
The Write Block ID associated with the block requests data from the ControlLogix
processor. Under normal program operation, the module sequentially sends read
blocks and requests write blocks.
For example, if the application uses three read and two write blocks, the
sequence will be as follows:
R1W1→R2W2→R3W1→R1W2→R2W1→R3W2→R1W1→
This sequence will continue until interrupted by other write block numbers sent by
the controller or by a command request from a node on the Modbus network or
operator control through the module’s Configuration/Debug port.
Initialize Output Data
When the module performs a restart operation, it will request blocks of output
data from the processor to initialize the module’s output data (Read Data Area).
Use the Initialize Output Data parameter in the configuration file to bring the
module to a known state after a restart operation. The following table describes
the structure of the request block.
Offset
Description
Length
0
1000 to 1124
1
1 to 40
Spare
40
41
1000 to 1124
1
Page 116 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
The block number in word 20 of the block determines the data set of up to 40
output words to transfer from the processor. Ladder logic in the processor must
recognize these blocks and place the correct information in the output image to
be returned to the module. The following table describes the structure of the
response block.
Offset
Description
Length
0
1000 to 1124
1
1 to 40
Output Data to preset in module.
40
41
Spare
1
Special Function Blocks
Special function blocks are optional blocks used to request special tasks from the
module.
Note: Event Commands and Command Control are not needed for normal Modbus command list
polling operations and are needed only occasionally for special circumstances.
Important: Each command defined in the command list is controlled by the ladder logic. The Write
Command Bits parameter must be set in ladder logic to allow the command to be sent out on the
Modbus TCP/IP network.
ProSoft Technology, Inc.
June 14, 2011
Page 117 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Event Command Block (2000)
Event command control blocks send Modbus TCP/IP commands directly from the
ladder logic to one of the clients on the module. The following table describes the
format of these blocks.
Offset
Description
Length
0
2000
1
1 to 4
IP Address
4
5
Service Port
1
6
Slave Address
1
7
Internal DB Address
1
8
Point Count
1
9
Swap Code
1
10
Modbus Function Code
1
11
Device Database Address
1
12 to 41
Spare
30
Use the parameters passed with the block to construct the command. The IP
Address for the node to reach on the network is entered in four registers (1 to 4).
Each digit of the IP address is entered in the appropriate register.
For example, to interface with node 192.168.0.100, enter the values 192, 168, 0
and 100 in registers 1 to 4. The Service Port field selects the TCP service port
on the server to connect. If the parameter is set to 502, a standard MBAP
message will be generated. All other service port values will generate a Modbus
command message encapsulated in a TCP/IP packet.
The Internal DB Address parameter specifies the module’s database location to
associate with the command. The Point Count parameter defines the number of
points or registers for the command. The Swap Code is used with Modbus
functions 3 and 4 requests to change the word or byte order. The Modbus
Function Code has one of the following values 1, 2, 3, 4, 5, 6, 15 or 16. The
Device Database Address is the Modbus register or point in the remote slave
device to be associated with the command.
When the module receives the block, it will process it and place it in the
command queue. The following table describes the format of this block.
Word
Description
0
This word contains the block 2000 identification code to indicate that this
block contains a command to execute by the Client Driver.
1 to 4
These words contain the IP address for the server the message is intended.
Each digit (0 to 255) of the IP address is placed in one of the four registers.
For example, to reach IP address 192.168.0.100, enter the following values in
words 1 to 4 →192, 168, 0 and 100. The module will construct the normal
dotted IP address from the values entered. The values entered will be anded
with the mask 0x00ff to insure the values are in the range of 0 to 255.
Page 118 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
Word
Description
5
This word contains the TCP service port the message will be interfaced. For
example, to interface with a MBAP device, the word should contain a value of
502. To interface with a MNET device, a value of 2000 should be utilized. Any
value from 0 to 65535 is permitted. A value of 502 will cause a MBAP
formatted message to be generated. All other values will generate an
encapsulated Modbus message.
6
This word contains the Modbus node address for the message. This field
should have a value from 0 to 41.
7
This word contains the internal Modbus address in the module to use with the
command. This word can contain a value from 0 to 4999.
8
This word contains the count parameter that determines the number of digital
points or registers to associate with the command.
9
The parameter specifies the swap type for the data. This function is only valid
for function codes 3 and 4.
10
This word contains the Modbus function code for the command.
11
This word contains the Modbus address in the slave device to be associated
with the command.
12 to 41
Spare
The module will respond to each command block with a read block. The following
table describes the format of this block.
Offset
Description
Length
0
Write Block ID
1
1
0=Fail, 1=Success
1
2 to 40
Spare
39
41
2000
1
Word two of the block can be used by the ladder logic to determine if the
command was added to the command queue of the module. The command will
only fail if the command queue for the port is full (100 commands for each
queue).
ProSoft Technology, Inc.
June 14, 2011
Page 119 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Command Control Blocks (5001 to 5006)
Command control blocks place commands in the command list into the command
queue. The client has a command queue of up to 100 commands. The module
services commands in the queue before the user defined command list. This
gives high priority to commands in the queue. Commands placed in the queue
through this mechanism must be defined in the module's command list. Under
normal command list execution, the module will only execute commands with the
Enable parameter set to one or two. If the value is set to zero, the command is
skipped. Commands may be placed in the command queue with an Enable
parameter set to zero using this feature. These commands can then be executed
using the command control blocks.
One to six commands can be placed in the command queue with a single
request. The following table describes the format for this block.
Offset
Description
Length
0
5001 to 5006
1
1
Command index
1
2
Command index
1
3
Command index
1
4
Command index
1
5
Command index
1
6
Command index
1
7 to 41
Spare
35
The last digit in the block code defines the number of commands to process in
the block. For example, a block code of 5003 contains 3 command indexes that
are to be placed in the command queue. The Command index parameters in the
block have a range of 0 to 99 and correspond to the module's command list
entries.
The module responds to a command control block with a block containing the
number of commands added to the command queue for the port. The following
table describes the format for this block.
Offset
Description
Length
0
Write Block ID
1
1
Number of commands added to command queue
1
2 to 40
Spare
39
41
5001 to 5006
1
Page 120 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
Block 9990: Set Module IP Address
IP Set Request (Write Block)
Offset
Description
Length
0
9990
1
1
First digit of dotted IP address
1
2
Second digit of dotted IP address
1
3
Third digit of dotted IP address
1
4
Last digit of dotted IP address
1
5 to 41
Reserved
36
IP Set Response (Read Block)
Offset
Description
Length
0
0
1
1
Write Block ID
1
2
First digit of dotted IP address
1
3
Second digit of dotted IP address
1
4
Third digit of dotted IP address
1
5
Last digit of dotted IP address
1
6 to 41
Spare data area
35
Block 9991: Get Module IP Address
IP Get Request (Write Block)
Offset
Description
Length
0
9991
1
1 to 41
Spare data area
40
IP Get Response (Read Block)
Offset
Description
Length
0
0
1
1
Write Block ID
1
2
First digit of dotted IP address
1
3
Second digit of dotted IP address
1
4
Third digit of dotted IP address
1
5
Last digit of dotted IP address
1
6 to 41
Spare data area
35
ProSoft Technology, Inc.
June 14, 2011
Page 121 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Warm Boot Block (9998)
This block is sent from the ControlLogix processor to the module (output image)
when the module is required to perform a warm-boot (software reset) operation.
The following table describes the format of the control block.
Offset
Description
Length
0
9998
1
1 to 41
Spare
41
Cold Boot Block (9999)
This block is sent from the ControlLogix processor to the module (output image)
when the module is required to perform the cold boot (hardware reset) operation.
This block is sent to the module when a hardware problem is detected by the
ladder logic that requires a hardware reset. The following table describes the
format of the control block.
Offset
Description
Length
0
9999
1
1 to 41
Spare
41
Pass-Through Control Blocks
If the module is set for pass-through operation by placing a value of 1 to 3 in the
configuration file parameter Pass-Through Mode, the module will send special
blocks to the module when a write request is received from a client. Any Modbus
function 5, 6, 15 or 16 commands will be passed from the server to the processor
using this block identification numbers 9956 to 9961, 9970 and 9996. Ladder
logic must handle the receipt of these blocks and to place the enclosed data into
the proper controller tags in the module.
There are two basic modes of operation when the pass-through feature is
utilized: Unformatted (code 1) and Formatted (code 2 or 3). The unformatted
mode will pass the message received on the server directly to the processor
without any processing. The following table describes the format of the read
block.
Unformatted
Unformatted Pass-Through Command (Read Block)
Offset
Description
Length
0
9996
1
1
Number of bytes in Modbus msg
1
2
Reserved (always 0)
1
3 to 40
Modbus message received
38
41
9996
1
Page 122 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
The ladder logic should copy and parse the received message and control the
processor as expected by the master device. The processor must respond to the
pass-through control block with a write block. The following table describes the
format of the write block.
Unformatted Pass-Through Command (Write Block)
Offset
Description
Length
0
9996
1
1 to 41
Spare
41
This informs the module that the command has been processed and can be
cleared from the pass-through queue.
In formatted pass-through mode, the module processes the received write
request and generates a special block dependent on the function received. There
are two modes of operation when the formatted pass-through mode is selected. If
code 2 is utilized (no swap), the data received in the message is presented in the
order received by the module. If code 3 is utilized (swap mode), the bytes in the
data area of the message will be swapped. This selection is applied to all
received write requests. The block identification code used with the request
depends on the Modbus function requested. Block 9956 passes word type data
for functions 6 and 16. Block 9957 passes a floating-point message for functions
6 and 16. Block 9958 is utilized when Modbus function 5 data is received. Block
9959 is employed when function 15 is recognized. Block 9960 is used for
function 22 and Block 9961 is used for function 23 requests. Block 9970 is
utilized for function 99. The following tables describe the format for the read
blocks.
Formatted
Formatted Pass-Through Command Blocks (Read Block)
Offset
Description
Length
0
9956, 9957, 9958, 9960 or 9961
1
1
Number of word registers in Modbus data set
1
2
Starting address for Modbus data set
1
3 to 40
Modbus data set
38
41
9956, 9957, 9958, 9960 or 9961
1
ProSoft Technology, Inc.
June 14, 2011
Page 123 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Formatted Pass-Through Command Blocks (Read Block)
Offset
Description
Length
0
9959
1
1
Number of word registers in Modbus data set
1
2
Starting word address for Modbus data set
1
3 to 21
Modbus data set
19
22 to 40
Bit mask for the data set. Each bit to be considered with the
data set will have a value of 1 in the mask. Bits to ignore in
the data set will have a value of 0 in the mask.
19
41
9959
1
Formatted Pass-Through Command Blocks (Read Block)
Offset
Description
Length
0
9970
1
1
1
1
2
0
1
3 to 40
Spare data area
38
41
9996
1
The ladder logic should copy and parse the received message and control the
processor as expected by the master device. The processor must respond to the
formatted pass-through control blocks with a write block. The following tables
describe the format of the write blocks.
Formatted Pass-Through Response (Write Block)
Offset
Description
Length
0
9956, 9957, 9958, 9960 or 9961
1
1 to 41
Spare data area
41
Formatted Pass-Through Response (Write Block)
Offset
Description
Length
0
9959
1
1 to 41
Spare data area
41
Formatted Pass-Through Response (Write Block)
Offset
Description
Length
0
9970
1
1 to 41
Spare data area
41
Page 124 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.2.4 Data Flow between MVI56E-MNETR Module and ControlLogix
Processor
The following topics describe the flow of data between the two pieces of
hardware (ControlLogix processor and MVI56E-MNETR module) and other
nodes on the Modbus TCP/IP network under the module’s different operating
modes. The module has both server and Client capability. The servers accept
TCP/IP connections on service ports 502 (MBAP) (10 server connections) and
2000 (MNET) (10 server connections). The Client can generate either MBAP or
MNET requests dependent on the service port selected in the command.
The following topics discuss the operation of the server and Client drivers.
Server Driver
The Server Driver allows the MVI56E-MNETR module to respond to data read
and write commands issued by clients on the Modbus TCP/IP network. The
following illustration and associated table describe the flow of data into and out of
the module.
ProSoft Technology, Inc.
June 14, 2011
Page 125 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
The server driver receives the configuration information from the
configuration file on the Compact Flash Disk, and the module initializes the
servers.
2 A Client device, such as a Modicon PLC or an HMI application, issues a read
or write command to the module’s node address. The server driver qualifies
the message before accepting it into the module.
3 When the module accepts the command, the data is immediately transferred
to or from the internal database in the module. If the command is a read
command, the data is read out of the database and a response message is
built. If the command is a write command, the data is written directly into the
database and a response message is built. If the pass-through feature is
utilized, the write message is transferred directly to the processor and is not
written to the module’s database.
4 When the data processing has been completed in Step 3, the response is
issued to the originating Client node.
5 Counters are available in the Status Block that permit the ladder logic
program to determine the level of activity of the Server Driver.
After the server socket is open, it must receive messages within a one minute
period, or else it will close the socket. After closing, the socket will be reused.
An exception to this normal mode is when the pass-through mode is
implemented. In this mode, all write requests will be passed directly to the
processor and will not be placed in the database. This permits direct, remote
control of the processor without the intermediate database. This mode is
especially useful for Master devices that do not send both states of control. For
example, a SCADA system may only send an on command to a digital control
point and never send the clear state. The SCADA system expects the local logic
to reset the control bit. Pass-through must be used to simulate this mode. The
following illustration describes the data flow for a slave port with pass-through
enabled:
1
Page 126 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
Client Driver
In the Client driver, the MVI56E-MNETR module issues read or write commands
to servers on the Modbus TCP/IP network. These commands are user configured
in the module via the Client Command List received from the module's
configuration or issued directly from the ControlLogix processor (Event
Command). Command status is returned to the processor for each individual
command in the command list status block. The location of this status block in
the module's internal database is user-defined. The following flowchart describes
the flow of data into and out of the module.
1
2
The Client driver obtains configuration data when the module restarts. This
includes the timeout parameters and the Command List. These values are
used by the driver to determine the type of commands to be issued to the
other nodes on the Modbus TCP/IP network.
When configured, the Client driver begins transmitting read and/or write
commands to the other nodes on the network. The data for write commands
is obtained from the module's internal database.
ProSoft Technology, Inc.
June 14, 2011
Page 127 of 175
Reference
User Manual
3
4
5
6
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Presuming successful processing by the node specified in the command, a
response message is received into the Client driver for processing.
Data received from the node on the network is passed into the module's
internal database, assuming a read command.
Status information can be requested by the processor and returned in a
Status block.
Special functions, such as Event Commands and Command Control options,
can be generated by the processor and sent to the Client driver for action.
Client Command List
In order for the Client to function, the module's Client Command List must be
defined. This list contains up to 100 individual entries, with each entry containing
the information required to construct a valid command. This includes the
following:
Command enable mode
o (0) disabled
o (1) continuous
o (2) conditional
IP address and service port to connect to on the remote server
Slave Node Address
Command Type - Read or Write up to 100 words per command
Database Source and Destination Register Address - Determines where data
will be placed and/or obtained
Count - Select the number of words to be transferred - 1 to 100
Poll Delay - 1/10th seconds
Client Command Errors
You can use the MNET Client 0 Command Error Pointer in the configuration to
set the database offset register where all command error codes will be stored.
This means that the first register refers to command 1 and so on.
Offset
Description
1
Command 1 Error
2
Command 2 Error
3
Command 3 Error
…
….
…
…
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 list is read in from the configuration file and as the commands are
processed, an error value is maintained in the module for each command. This
error list can be transferred to the processor. The errors generated by the module
are displayed in the following table.
Page 128 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
Standard Modbus Exception Code Errors
Code
1
2
3
4
5
6
Description
Illegal function
Illegal data address
Illegal data value
Failure in associated device
Acknowledge
Busy; message was rejected
Module Communication Error Codes
Code
-2
-11
253
254
255
Description
Timeout while transmitting message
Timeout waiting for response after request
Incorrect slave/server address in response
Incorrect function code in response
Invalid CRC/LRC value in response
MNET Client Specific Errors
Code
-33
-36
-37
Description
Failed to connect to server specified in command
MNET command response timeout
TCP/IP connection ended before session finished
Command List Entry Errors
Code
-40
Description
Too few parameters
-41
-42
-43
-44
-45
-46
-47
Invalid enable code
Internal address > maximum address
Invalid node address (<0 or >255)
Count parameter set to 0
Invalid function code
Invalid swap code
ARP could not resolve MAC from IP (bad IP address, not part of a
network, invalid parameter to ARP routine).
Error during ARP operation: the response to the ARP request did
not arrive to the module after a user-adjustable ARP Timeout.
-48
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.
ProSoft Technology, Inc.
June 14, 2011
Page 129 of 175
Reference
User Manual
5.3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Ethernet Cable Specifications
The recommended cable is Category 5 or better. A Category 5 cable has four
twisted pairs of wires, which are color-coded and cannot be swapped. The
module uses only two of the four pairs.
The Ethernet port on the module is Auto-Sensing. You can use either a standard
Ethernet straight-through cable or a crossover cable when connecting the
module to an Ethernet hub, a 10/100 Base-T Ethernet switch, or directly to a PC.
The module will detect the cable type and use the appropriate pins to send and
receive Ethernet signals.
Ethernet cabling is like U.S. telephone cables, except that it has eight
conductors. Some hubs have one input that can accept either a straight-through
or crossover cable, depending on a switch position. In this case, you must ensure
that the switch position and cable type agree.
Refer to Ethernet cable configuration (page 130) for a diagram of how to
configure Ethernet cable.
5.3.1 Ethernet Cable Configuration
Note: The standard connector view shown is color-coded for a straight-through cable.
Crossover cable
Straight- through cable
RJ-45 PIN
RJ-45 PIN
RJ-45 PIN
RJ-45 PIN
1 Rx+
3 Tx+
1 Rx+
1 Tx+
2 Rx-
6 Tx-
2 Rx-
2 Tx-
3 Tx+
1 Rx+
3 Tx+
3 Rx+
6 Tx-
2 Rx-
6 Tx-
6 Rx-
5.3.2 Ethernet Performance
Ethernet performance on the MVI56E-MNETR module can affect the operation of
the MNETR application ports in the following ways.
Accessing the web interface (refreshing the page, downloading files, and so
on) may affect MNETR performance
High Ethernet traffic may impact MNETR performance (consider CIPconnect
(page 71, page 24) for these applications and disconnect the module
Ethernet port from the network).
Page 130 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.4
Reference
User Manual
Status Data Definition
This section contains a description of the members present in the
MNETR.STATUS object. This data is transferred from the module to the
processor as part of each read block.
Content
Pass Count
Product Version
Product Code
Read Block Count
Write Block Count
Parse Block Count
Command Event Block
Count
Command Block Count
Error Block Count
Reserved1
Reserved2
MNet Request Count
MNet Response Count
MBAP Request Count
MBAP Response Count
Client Cmd Request
Client Cmd Response
Client Cmd Error
Client Request Count
Client Response Count
Client Error Sent Count
Client Error Received Count
Client Cfg Error Word
Client Current Error Code
Client Last Error Code
ProSoft Technology, Inc.
June 14, 2011
Description
This value is incremented each time a complete program cycle
occurs in the module.
Shows the module software version.
Identifies the module product code.
This field contains the total number of read blocks transferred from
the module to the processor.
This field contains the total number of write blocks transferred from
the processor to the module.
This field contains the total number of blocks successfully parsed
that were received from the processor.
This field contains the total number of command event blocks
received from the processor.
This field contains the total number of command blocks received
from the processor.
This field contains the total number of block errors recognized by
the module.
Not used
Not used
This counter increments each time a MNet (port 2000) request is
received.
This counter is incremented each time a MNet (port 2000)
response message is sent.
This counter increments each time a MBAP (port 502) request is
received.
This counter is incremented each time a MBAP (port 502) response
message is sent.
This value is incremented each time a command request is issued.
This value is incremented each time a command response is
received.
This value is incremented each time an error message is received
from a remote unit or a local error is generated for a command.
This value is incremented each time a request message is issued.
This value is incremented each time a response message is
received.
This value is incremented each time an error is sent from the client.
This value is incremented each time an error is received from a
remote unit.
This word contains a bit map that defines configuration errors in the
configuration file for the client.
This value corresponds to the current error code for the client.
This value corresponds to the last error code recorded for the
client.
Page 131 of 175
Reference
User Manual
5.5
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Modbus Protocol Specification
The following pages give additional reference information regarding the Modbus
protocol commands supported by the MVI56E-MNETR.
5.5.1 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.
Function Code
Definition
Supported in Client
Supported in Server
1
Read Coil Status
X
X
2
Read Input Status
X
X
3
Read Holding Registers
X
X
4
Read Input Registers
X
X
5
Set Single Coil
X
X
6
Single Register Write
X
7
Read Exception Status
X
8
Diagnostics
X
15
Multiple Coil Write
X
X
16
Multiple Register Write
X
X
22
Mask Write 4X
X
23
Read/Write
X
X
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.
Page 132 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.5.2 Read Coil Status (Function Code 01)
Query
This function allows the user to obtain the ON/OFF status of logic coils used to
control discrete outputs from the addressed Server only. Broadcast mode is not
supported with this function code. In addition to the Server address and function
fields, the message requires that the information field contain the initial coil
address to be read (Starting Address) and the number of locations that will be
interrogated to obtain status data.
The addressing allows up to 2000 coils to be obtained at each request; however,
the specific Server device may have restrictions that lower the maximum
quantity. The coils are numbered from zero; (coil number 1 = zero, coil number 2
= one, coil number 3 = two, and so on).
The following table is a sample read output status request to read coils 0020 to
0056 from Server device number 11.
Adr
Func
Data Start Pt Hi
Data Start Pt Lo
Data # Of Pts Ho Data # Of Pts Lo
Error Check Field
11
01
00
13
00
CRC
25
Response
An example response to Read Coil Status is as shown in Figure C2. The data is
packed one bit for each coil. The response includes the Server address, function
code, quantity of data characters, the data characters, and error checking. Data
will be packed with one bit for each coil (1 = ON, 0 = OFF). The low order bit of
the first character contains the addressed coil, and the remainder follow. For coil
quantities that are not even multiples of eight, the last characters will be filled in
with zeros at high order end. The quantity of data characters is always specified
as quantity of RTU characters, that is, the number is the same whether RTU or
ASCII is used.
Because the Server interface device is serviced at the end of a controller's scan,
data will reflect coil status at the end of the scan. Some Servers will limit the
quantity of coils provided each scan; thus, for large coil quantities, multiple PC
transactions must be made using coil status from sequential scans.
Adr Func
Byte
Count
Data Coil
Status 20 to
27
Data Coil
Status 28 to
35
Data Coil
Status 36 to
43
Data Coil
Status 44 to
51
Data Coil
Status 52 to
56
Error
Check
Field
11
05
CD
6B
B2
OE
1B
CRC
01
ProSoft Technology, Inc.
June 14, 2011
Page 133 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
The status of coils 20 to 27 is shown as CD(HEX) = 1100 1101 (Binary). Reading
left to right, this shows that coils 27, 26, 23, 22, and 20 are all on. The other coil
data bytes are decoded similarly. Due to the quantity of coil statuses requested,
the last data field, which is shown 1B (HEX) = 0001 1011 (Binary), contains the
status of only 5 coils (52 to 56) instead of 8 coils. The 3 left most bits are
provided as zeros to fill the 8-bit format.
5.5.3 Read Input Status (Function Code 02)
Query
This function allows the user to obtain the ON/OFF status of discrete inputs in the
addressed Server PC Broadcast mode is not supported with this function code.
In addition to the Server address and function fields, the message requires that
the information field contain the initial input address to be read (Starting Address)
and the number of locations that will be interrogated to obtain status data.
The addressing allows up to 2000 inputs to be obtained at each request;
however, the specific Server device may have restrictions that lower the
maximum quantity. The inputs are numbered form zero; (input 10001 = zero,
input 10002 = one, input 10003 = two, and so on, for a 584).
The following table is a sample read input status request to read inputs 10197 to
10218 from Server number 11.
Adr
Func
Data Start Pt Hi
Data Start Pt Lo
Data #of Pts Hi
Data #of Pts Lo
Error Check Field
11
02
00
C4
00
16
CRC
Response
An example response to Read Input Status is as shown in Figure C4. The data is
packed one bit for each input. The response includes the Server address,
function code, quantity of data characters, the data characters, and error
checking. Data will be packed with one bit for each input (1=ON, 0=OFF). The
lower order bit of the first character contains the addressed input, and the
remainder follow. For input quantities that are not even multiples of eight, the last
characters will be filled in with zeros at high order end. The quantity of data
characters is always specified as a quantity of RTU characters, that is, the
number is the same whether RTU or ASCII is used.
Because the Server interface device is serviced at the end of a controller's scan,
data will reflect input status at the end of the scan. Some Servers will limit the
quantity of inputs provided each scan; thus, for large coil quantities, multiple PC
transactions must be made using coil status for sequential scans.
Adr
Func
Byte
Count
Data Discrete Input
10197 to 10204
Data Discrete Input
10205 to 10212
Data Discrete Input
10213 to 10218
Error Check Field
11
02
03
AC
DB
35
CRC
Page 134 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
The status of inputs 10197 to 10204 is shown as AC (HEX) = 10101 1100
(binary). Reading left to right, this show that inputs 10204, 10202, and 10199 are
all on. The other input data bytes are decoded similar.
Due to the quantity of input statuses requested, the last data field which is shown
as 35 HEX = 0011 0101 (binary) contains the status of only 6 inputs (10213 to
102180) instead of 8 inputs. The two left-most bits are provided as zeros to fill
the 8-bit format.
5.5.4 Read Holding Registers (Function Code 03)
Query
Read Holding Registers (03) allows the user to obtain the binary contents of
holding registers 4xxxx in the addressed Server. The registers can store the
numerical values of associated timers and counters which can be driven to
external devices. The addressing allows up to 125 registers to obtained at each
request; however, the specific Server device may have restriction that lower this
maximum quantity. The registers are numbered form zero (40001 = zero, 40002
= one, and so on). The broadcast mode is not allowed.
The example below reads registers 40108 through 40110 from Server 584
number 11.
Adr Func
Data Start Reg Hi
Data Start Reg Lo
Data #of Regs Hi Data #of Regs Lo
Error Check Field
11
00
6B
00
CRC
03
03
Response
The addressed Server responds with its address and the function code, followed
by the information field. The information field contains 1 byte describing the
quantity of data bytes to be returned. The contents of the registers requested
(DATA) are two bytes each, with the binary content right justified within each pair
of characters. The first byte includes the high order bits and the second, the low
order bits.
Because the Server interface device is normally serviced at the end of the
controller's scan, the data will reflect the register content at the end of the scan.
Some Servers will limit the quantity of register content provided each scan; thus
for large register quantities, multiple transmissions will be made using register
content from sequential scans.
In the example below, the registers 40108 to 40110 have the decimal contents
555, 0, and 100 respectively.
Adr
Func
ByteCnt
Hi Data
Lo Data
Hi Data
Lo Data
Hi Data
Lo Data
Error Check Field
11
03
06
02
2B
00
00
00
64
CRC
ProSoft Technology, Inc.
June 14, 2011
Page 135 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.5.5 Read Input Registers (Function Code 04)
Query
Function code 04 obtains the contents of the controller's input registers at
addresses 3xxxx. These locations receive their values from devices connected to
the I/O structure and can only be referenced, not altered from within the
controller, The addressing allows up to 125 registers to be obtained at each
request; however, the specific Server device may have restrictions that lower this
maximum quantity. The registers are numbered for zero (30001 = zero, 30002 =
one, and so on). Broadcast mode is not allowed.
The example below requests the contents of register 3009 in Server number 11.
Adr Func Data Start Reg Hi Data Start Reg Lo
Data #of Regs Hi
Data #of Regs Lo
Error Check Field
11
00
01
CRC
04
00
08
Response
The addressed Server responds with its address and the function code followed
by the information field. The information field contains 1 byte describing the
quantity of data bytes to be returned. The contents of the registers requested
(DATA) are 2 bytes each, with the binary content right justified within each pair of
characters. The first byte includes the high order bits and the second, the low
order bits.
Because the Server interface is normally serviced at the end of the controller's
scan, the data will reflect the register content at the end of the scan. Each PC will
limit the quantity of register contents provided each scan; thus for large register
quantities, multiple PC scans will be required, and the data provided will be form
sequential scans.
In the example below the register 3009 contains the decimal value 0.
Adr
Func
Byte Count
Data Input Reg Hi
Data Input Reg Lo
Error Check Field
11
04
02
00
00
E9
Page 136 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.5.6 Force Single Coil (Function Code 05)
Query
This message forces a single coil either ON or OFF. Any coil that exists within
the controller can be forced to either state (ON or OFF). However, because the
controller is actively scanning, unless the coil is disabled, the controller can also
alter the state of the coil. Coils are numbered from zero (coil 0001 = zero, coil
0002 = one, and so on). The data value 65,280 (FF00 HEX) will set the coil ON
and the value zero will turn it OFF; all other values are illegal and will not affect
that coil.
The use of Server address 00 (Broadcast Mode) will force all attached Servers to
modify the desired coil.
Note: Functions 5, 6, 15, and 16 are the only messages that will be recognized as valid for
broadcast.
The example below is a request to Server number 11 to turn ON coil 0173.
Adr
Func
Data Coil # Hi
Data Coil # Lo
Data On/off Ind
Data
Error Check Field
11
05
00
AC
FF
00
CRC
Response
The normal response to the Command Request is to re-transmit the message as
received after the coil state has been altered.
Adr
Func
Data Coil # Hi
Data Coil # Lo
Data On/ Off
Data
Error Check Field
11
05
00
AC
FF
00
CRC
The forcing of a coil via MODBUS function 5 will be accomplished regardless of
whether the addressed coil is disabled or not (In ProSoft products, the coil is only
affected if the necessary ladder logic is implemented).
Note: The Modbus protocol does not include standard functions for testing or changing the
DISABLE state of discrete inputs or outputs. Where applicable, this may be accomplished via
device specific Program commands (In ProSoft products, this is only accomplished through ladder
logic programming).
Coils that are reprogrammed in the controller logic program are not automatically
cleared upon power up. Thus, if such a coil is set ON by function Code 5 and
(even months later), an output is connected to that coil, the output will be "hot".
ProSoft Technology, Inc.
June 14, 2011
Page 137 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.5.7 Preset Single Register (Function Code 06)
Query
Function (06) allows the user to modify the contents of a holding register. Any
holding register that exists within the controller can have its contents changed by
this message. However, because the controller is actively scanning, it also can
alter the content of any holding register at any time. The values are provided in
binary up to the maximum capacity of the controller unused high order bits must
be set to zero. When used with Server address zero (Broadcast mode) all Server
controllers will load the specified register with the contents specified.
Note Functions 5, 6, 15, and 16 are the only messages that will be recognized as valid for
broadcast.
Adr
Func
Data Start Reg
Hi
Data Start Reg
Lo
Data #of Regs Hi Data #of Regs Lo
Error Check Field
11
06
00
01
00
CRC
03
Response
The response to a preset single register request is to re-transmit the query
message after the register has been altered.
Adr
Func
Data Reg Hi
Data Reg Lo
Data Input Reg Hi
Data Input Reg Lo
Error Check Field
11
06
00
01
00
03
CRC
Page 138 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.5.8 Diagnostics (Function Code 08)
MODBUS function code 08 provides a series of tests for checking the
communication system between a Client device and a server, or for checking
various internal error conditions within a server.
The function uses a two-byte sub-function code field in the query to define the
type of test to be performed. The server echoes both the function code and subfunction code in a normal response. Some of the diagnostics cause data to be
returned from the remote device in the data field of a normal response.
In general, issuing a diagnostic function to a remote device does not affect the
running of the user program in the remote device. Device memory bit and
register data addresses are not accessed by the diagnostics. However, certain
functions can optionally reset error counters in some remote devices.
A server device can, however, be forced into 'Listen Only Mode' in which it will
monitor the messages on the communications system but not respond to them.
This can affect the outcome of your application program if it depends upon any
further exchange of data with the remote device. Generally, the mode is forced to
remove a malfunctioning remote device from the communications system.
Sub-function codes supported
Only Sub-function 00 is supported by the MVI56E-MNETR module.
00 Return Query Data
The data passed in the request data field is to be returned (looped back) in the
response. The entire response message should be identical to the request.
Sub-function
Data Field (Request)
Data Field (Response)
00 00
Any
Echo Request Data
Example and state diagram
Here is an example of a request to remote device to Return Query Data. This
uses a sub-function code of zero (00 00 hex in the two-byte field). The data to be
returned is sent in the two-byte data field (A5 37 hex).
Request
Response
Field Name
(Hex)
Field Name
(Hex)
Function
08
Function
08
Sub-function Hi
00
Sub-function Hi
00
Sub-function Lo
00
Sub-function Lo
00
Data Hi
A5
Data Hi
A5
Data Lo
37
Data Lo
27
ProSoft Technology, Inc.
June 14, 2011
Page 139 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
The data fields in responses to other kinds of queries could contain error counts
or other data requested by the sub-function code.
Page 140 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.5.9 Force Multiple Coils (Function Code 15)
Query
This message forces each coil in a consecutive block of coils to a desired ON or
OFF state. Any coil that exists within the controller can be forced to either state
(ON or OFF). However, because the controller is actively scanning, unless the
coils are disabled, the controller can also alter the state of the coil. Coils are
numbered from zero (coil 00001 = zero, coil 00002 = one, and so on). The
desired status of each coil is packed in the data field, one bit for each coil (1=
ON, 0= OFF). The use of Server address 0 (Broadcast Mode) will force all
attached Servers to modify the desired coils.
Note: Functions 5, 6, 15, and 16 are the only messages (other than Loopback Diagnostic Test) that
will be recognized as valid for broadcast.
The following example forces 10 coils starting at address 20 (13 HEX). The two
data fields, CD =1100 and 00 = 0000 000, indicate that coils 27, 26, 23, 22, and
20 are to be forced on.
Adr
Func
Hi Add
Lo
Add
Quantity
Byte
Cnt
Data Coil Status Data Coil Status
20 to 27
28 to 29
Error Check
Field
11
0F
00
13
00
0A
02
00
CD
CRC
Response
The normal response will be an echo of the Server address, function code,
starting address, and quantity of coils forced.
Adr
Func
Hi Addr
Lo Addr
Quantity
Error Check Field
11
0F
00
13
00
0A
CRC
The writing of coils via Modbus function 15 will be accomplished regardless of
whether the addressed coils are disabled or not.
Coils that are unprogrammed in the controller logic program are not automatically
cleared upon power up. Thus, if such a coil is set ON by function code 15 and
(even months later) an output is connected to that coil, the output will be hot.
ProSoft Technology, Inc.
June 14, 2011
Page 141 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.5.10 Preset Multiple Registers (Function Code 16)
Query
Holding registers existing within the controller can have their contents changed
by this message (a maximum of 60 registers). However, because the controller is
actively scanning, it also can alter the content of any holding register at any time.
The values are provided in binary up to the maximum capacity of the controller
(16-bit for the 184/384 and 584); unused high order bits must be set to zero.
Note: Function codes 5, 6, 15, and 16 are the only messages that will be recognized as valid for
broadcast.
Adr
Func
Hi
Add
Lo Add
Quantity
11
10
00
87
00
02
Byte
Cnt
Hi
Data
Lo
Data
Hi
Data
Lo Data Error Check
Field
04
00
0A
01
02
CRC
Response
The normal response to a function 16 query is to echo the address, function
code, starting address and number of registers to be loaded.
Adr
Func
Hi Addr
Lo Addr
Quantity
11
10
00
87
00
Page 142 of 175
Error Check Field
02
56
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.5.11 Modbus Exception Responses
When a Modbus Client sends a request to a Server device, it expects a normal
response. One of four possible events can occur from the Client's query:
If the server device receives the request without a communication error, and
can handle the query normally, it returns a normal response.
If the server does not receive the request due to a communication error, no
response is returned. The Client program will eventually process a timeout
condition for the request.
If the server receives the request, but detects a communication error (parity,
LRC, CRC, ...), no response is returned. The Client program will eventually
process a timeout condition for the request.
If the server receives the request without a communication error, but cannot
handle it (for example, if the request is to read a non-existent output or
register), the server will return an exception response informing the Client of
the nature of the error.
The exception response message has two fields that differentiate it from a
normal response:
Function Code Field: In a normal response, the server echoes the function
code of the original request in the function code field of the response. All function
codes have a most-significant bit (MSB) of 0 (their values are all below 80
hexadecimal). In an exception response, the server sets the MSB of the function
code to 1. This makes the function code value in an exception response exactly
80 hexadecimal higher than the value would be for a normal response.
With the function code's MSB set, the Client's application program can recognize
the exception response and can examine the data field for the exception code.
Data Field: In a normal response, the server may return data or statistics in the
data field (any information that was requested in the request). In an exception
response, the server returns an exception code in the data field. This defines the
server condition that caused the exception.
The following table shows an example of a Client request and server exception
response.
Request
Field Name
Function
Starting Address Hi
Starting Address Lo
Quantity of Outputs Hi
Quantity of Outputs Lo
(Hex)
01
04
A1
00
01
Response
Field Name
Function
Exception Code
(Hex)
81
02
In this example, the Client addresses a request to server device. The function
code (01) is for a Read Output Status operation. It requests the status of the
output at address 1245 (04A1 hex). Note that only that one output is to be read,
as specified by the number of outputs field (0001).
ProSoft Technology, Inc.
June 14, 2011
Page 143 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
If the output address is non-existent in the server device, the server will return
the exception response with the exception code shown (02). This specifies an
illegal data address for the Server.
Modbus Exception Codes
Code
01
02
03
04
05
06
08
0a
Page 144 of 175
Name
Illegal Function
Meaning
The function code received in the query is not an allowable
action for the Server. This may be because the function
code is only applicable to newer devices, and was not
implemented in the unit selected. It could also indicate that
the Server is in the wrong state to process a request of this
type, for example because it is unconfigured and is being
asked to return register values.
Illegal Data Address
The data address received in the query is not an allowable
address for the Server. More specifically, the combination
of reference number and transfer length is invalid. For a
controller with 100 registers, a request with offset 96 and
length 4 would succeed; a request with offset 96 and length
5 will generate exception 02.
Illegal Data Value
A value contained in the query data field is not an allowable
value for Server. This indicates a fault in the structure of
the remainder of a complex request, such as that the
implied length is incorrect. It specifically does not mean that
a data item submitted for storage in a register has a value
outside the expectation of the application program,
because the Modbus protocol is unaware of the
significance of any particular value of any particular
register.
Slave Device Failure
An unrecoverable error occurred while the Server was
attempting to perform the requested action.
Acknowledge
Specialized use in conjunction with programming
commands. The Server has accepted the request and is
processing it, but a long duration of time will be required to
do so. This response is returned to prevent a timeout error
from occurring in the Client. The Client can next issue a
poll program complete message to determine if processing
is completed.
Slave Device Busy
Specialized use in conjunction with programming
commands. The Server is engaged in processing a longduration program command. The Client should retransmit
the message later when the Server is free.
Memory Parity Error
Specialized use in conjunction with function codes 20 and
21 and reference type 6, to indicate that the extended file
area failed to pass a consistency check. The Server
attempted to read record file, but detected a parity error in
the memory. The Client can retry the request, but service
may be required on the Server device.
Gateway Path Unavailable Specialized use in conjunction with gateways, indicates
that the gateway was unable to allocate an internal
communication path from the input port to the output port
for processing the request. Usually means that the gateway
is misconfigured or overloaded.
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Code
0b
Name
Gateway Target Device
Failed To Respond
ProSoft Technology, Inc.
June 14, 2011
Reference
User Manual
Meaning
Specialized use in conjunction with gateways, indicates
that no response was obtained from the target device.
Usually means that the device is not present on the
network.
Page 145 of 175
Reference
User Manual
5.6
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Using the Optional Add-On Instruction Rung Import
5.6.1 Before You Begin
Make sure that you have installed RSLogix 5000 version 16 (or later)
Download the Optional Add-On file
MVI56EMNETR_Optional_Rung_v1_0.L5X from the module's web page and
copy it to a folder in your PC
5.6.2 Overview
The Optional Add-On Instruction Rung Import contains optional logic for MVI56EMNETR applications to perform the following tasks.
Read/Write Ethernet Configuration
Allows the processor to read or write the module IP address, netmask and
gateway values.
Note: This is an optional feature. You can perform the same task through PCB (ProSoft
Configuration Builder). Even if your PC is in a different network group you can still access the
module through PCB by setting a temporary IP address.
Read/Write Module Clock Value
Allows the processor to read and write the module clock settings. The module
clock stores the last time that the Ethernet configuration was changed. The
date and time of the last Ethernet configuration change is displayed in the
scrolling LED during module power up.
Important: The Optional Add-On Instruction only supports the two features listed above. You must
use the sample ladder logic for all other features including backplane transfer of Modbus TCP/IP
data.
Page 146 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.6.3 Installing the Rung Import with Optional Add-On Instruction
1
Right-click on an empty rung in the main routine of your existing ladder logic
and choose IMPORT RUNG…
2
Navigate to the folder where you saved
MVI56(E)MNETR_Optional_AddOn_Rung_<version #>.L5X and select the
file.
ProSoft Technology, Inc.
June 14, 2011
Page 147 of 175
Reference
User Manual
3
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
In the IMPORT CONFIGURATION window, click OK.
The Add-On Instruction will be now visible in the ladder logic. Observe that
the procedure has also imported data types and controller tags associated to
the Add-On Instruction.
Page 148 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
You will notice that new tags have been imported: four MESSAGE tags,
MVI56MNETRCLOCK and MVI56MNETRETHERNET tags.
4
5
In the Add-On Instruction, click the [...] button next to each MSG tag to open
the MESSAGE CONFIGURATION TAG.
Click the COMMUNICATION tab and click the BROWSE button as follows.
ProSoft Technology, Inc.
June 14, 2011
Page 149 of 175
Reference
User Manual
6
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Select the module to configure the message path.
5.6.4 Reading the Ethernet Settings from the Module
Expand the MVI56MNETRETHERNET controller tag and move a value of 1 to
MVI56MNETRETHERNET.READ.
Page 150 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
The bit will be automatically reset and the current Ethernet settings will be copied
to MVI56MNETRETHERNET controller tag as follows.
To check the status of the message, refer to the READETHERNETMSG tag.
ProSoft Technology, Inc.
June 14, 2011
Page 151 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.6.5 Writing the Ethernet Settings to the Module
Expand the MVI56EMNETRETHERNET controller tag.
Set the new Ethernet configuration in MVI56EMNETRETHERNET.CONFIG
Move a value of 1 to MVI56MNETRETHERNET.WRITE
After the message is executed, the MVI56MNETRETHERNET.WRITE bit resets to
0.
To check the status of the message, refer to the WRITEETHERNETMSG tag.
Page 152 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.6.6 Reading the Clock Value from the Module
Expand the MVI56MNETRCLOCK controller tag and move a value of 1 to
MVI56MNETRCLOCK.READ
The bit will be automatically reset and the current clock value will be copied to
MVI56MNETRCLOCK.CONFIG controller tag as follows.
To check the status of the message, refer to the READCLOCKMSG tag.
ProSoft Technology, Inc.
June 14, 2011
Page 153 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.6.7 Writing the Clock Value to the Module
Expand the MVI56MNETRCLOCK controller tag.
Set the new Clock value in MVI56MNETRCLOCK.CONFIG
Move a value of 1 to MVI56MNETRCLOCK.WRITE
The bit will be automatically reset to 0.
To check the status of the message, refer to the WRITECLOCKMSG tag.
Page 154 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.7
Reference
User Manual
Adding the Module to an Existing Project
1
Add the MVI56E-MNETR module to the project. Select the I/O
CONFIGURATION folder in the CONTROLLER ORGANIZATION window, and then
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:
ProSoft Technology, Inc.
June 14, 2011
Page 155 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Select the 1756-MODULE (Generic 1756 Module) from the list and click OK.
This action opens the NEW MODULE dialog box.
Parameter
Value
Name
Enter a module identification string. The recommended value
is MNETR.
Description
Enter a description for the module. Example: Modbus TCP/IP
Interface Module with Reduced Data Block.
Comm Format
Select DATA-INT (Very Important)
Slot
Enter the slot number in the rack where the MVI56E-MNETR
module will be installed.
Input Assembly Instance
1
Input Size
42
Output Assembly Instance
2
Output Size
42
Configuration Assembly
Instance
4
Configuration Size
0
Enter the Name, Description and Slot options for your application. 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.
Click OK to continue.
Page 156 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
2
Edit the Module Properties. Select the REQUESTED PACKET INTERVAL value
for scanning the I/O on the module. This value represents the minimum
frequency that the module will handle scheduled events. This value should
not be set to less than 1 millisecond. The default value is 5 milliseconds.
Values between 1 and 10 milliseconds should work with most applications.
3
Save the module. Click OK to dismiss the dialog box. The CONTROLLER
ORGANIZATION window now displays the module's presence.
4
5
6
7
Copy the Controller Tags from the sample program.
Copy the User Defined Data Types from the sample program.
Copy the Ladder Rungs from the sample program.
Save and Download (page 48, page 162) the new application to the controller
and place the processor in run mode.
ProSoft Technology, Inc.
June 14, 2011
Page 157 of 175
Reference
User Manual
5.8
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Using the Sample Program
If your processor uses RSLogix 5000 version 15 or earlier, you will not be able to
use the Add-On Instruction for your module. Follow the steps below to obtain and
use a sample program for your application.
5.8.1 Opening the Sample Program in RSLogix
The sample program for your MVI56E-MNETR module includes custom tags,
data types and ladder logic for data I/O, status and command control. For most
applications, you can run the sample program without modification, or, for
advanced applications, you can incorporate the sample program into your
existing application.
Download the manuals and sample program from the ProSoft Technology web site
You can always download the latest version of the sample ladder logic and user
manuals for the MVI56E-MNETR module from the ProSoft Technology website,
at www.prosoft-technology.com/support/downloads (http://www.prosofttechnology.com/support/downloads)
From that link, navigate to the download page for your module and choose the
sample program to download for your version of RSLogix 5000 and your
processor.
To determine the firmware version of your processor
Important: The RSLinx service must be installed and running on your computer in order for
RSLogix to communicate with the processor. Refer to your RSLinx and RSLogix documentation for
help configuring and troubleshooting these applications.
1
2
3
Connect an RS-232 serial cable from the COM (serial) port on your PC to the
communication port on the front of the processor.
Start RSLogix 5000 and close any existing project that may be loaded.
Open the COMMUNICATIONS menu and choose GO ONLINE. RSLogix will
establish communication with the processor. This may take a few moments.
Page 158 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
4
When RSLogix has established communication with the processor, the
Connected To Go Online dialog box will open.
5
In the Connected To Go Online dialog box, click the GENERAL tab. This tab
shows information about the processor, including the Revision (firmware)
version. In the following illustration, the firmware version is 11.32
6
Select the sample ladder logic file for your firmware version.
To open the sample program
On the Connected to Go Online dialog box, click the SELECT FILE button.
Choose the sample program file that matches your firmware version, and
then click the SELECT button.
3 RSLogix will load the sample program.
The next step is to configure the correct controller type and slot number for your
application.
1
2
ProSoft Technology, Inc.
June 14, 2011
Page 159 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.8.2 Choosing the Controller Type
The sample application is for a 1756-L63 ControlLogix 5563 Controller. If you are
using a different model of the ControlLogix processor, you must configure the
sample program to use the correct processor model.
1 In the Controller Organization list, select the folder for the controller and then
click the right mouse button to open a shortcut menu.
2 On the shortcut menu, choose PROPERTIES. This action opens the Controller
Properties dialog box.
3
Click the CHANGE TYPE or CHANGE CONTROLLER button. This action opens
the Change Controller dialog box.
4
5
6
Open the TYPE dropdown list, and then select your ControlLogix controller.
Select the correct firmware revision for your controller, if necessary.
Click OK to save your changes and return to the previous window.
Page 160 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Reference
User Manual
5.8.3 Selecting the Slot Number for the Module
The sample application is for a module installed in Slot 1 in a ControlLogix rack.
The ladder logic uses the slot number to identify the module. If you are installing
the module in a different slot, you must update the ladder logic so that program
tags and variables are correct, and do not conflict with other modules in the rack.
To change the slot number
1
2
In the Controller Organization list, select the module, and then click the right
mouse button to open a shortcut menu.
On the shortcut menu, choose PROPERTIES. This action opens the Module
Properties dialog box.
In the SLOT field, use the up and down arrows on the right side of the field to
select the slot number where the module will reside in the rack, and then click
OK.
RSLogix will automatically apply the slot number change to all tags, variables
and ladder logic rungs that use the MVI56E-MNETR slot number for
computation.
3
ProSoft Technology, Inc.
June 14, 2011
Page 161 of 175
Reference
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
5.8.4 Downloading the Sample Program to the Processor
To download the sample program from RSLogix 5000 to the ControlLogix
processor
Note: The key switch on the front of the ControlLogix module must be in the REM position.
1
2
3
4
If you are not already online to the processor, open the COMMUNICATIONS
menu, and then choose DOWNLOAD. RSLogix will establish communication
with the processor.
When communication is established, RSLogix will open a confirmation dialog
box. Click the DOWNLOAD button to transfer the sample program to the
processor.
RSLogix will compile the program and transfer it to the processor. This
process may take a few minutes.
When the download is complete, RSLogix will open another confirmation
dialog box. 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 162 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
6
Support, Service & Warranty
User Manual
Support, Service & Warranty
In This Chapter
Contacting Technical Support ............................................................. 163
Return Material Authorization (RMA) Policies and Conditions............. 165
LIMITED WARRANTY ......................................................................... 166
Contacting Technical Support
ProSoft Technology, Inc. (ProSoft) is committed to providing the most efficient
and effective support possible. Before calling, please gather the following
information to assist in expediting this process:
1 Product Version Number
2 System architecture
3 Network details
If the issue is hardware related, we will also need information regarding:
1 Module configuration and associated ladder files, if any
2 Module operation and any unusual behavior
3 Configuration/Debug status information
4 LED patterns
5 Details about the serial, Ethernet or fieldbus devices interfaced to the module,
if any.
Note: For technical support calls within the United States, ProSoft’s 24/7 after-hours phone
support is available for urgent plant-down issues. Detailed contact information for all our
worldwide locations is available on the following page.
ProSoft Technology, Inc.
June 14, 2011
Page 163 of 175
Support, Service & Warranty
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Internet
Web Site: www.prosoft-technology.com/support
E-mail address: support@prosoft-technology.com
Asia Pacific
(location in Malaysia)
Tel: +603.7724.2080, E-mail: asiapc@prosoft-technology.com
Languages spoken include: Chinese, English
Asia Pacific
(location in China)
Tel: +86.21.5187.7337 x888, E-mail: asiapc@prosoft-technology.com
Languages spoken include: Chinese, English
Europe
(location in Toulouse,
France)
Tel: +33 (0) 5.34.36.87.20,
E-mail: support.EMEA@prosoft-technology.com
Languages spoken include: French, English
Europe
(location in Dubai, UAE)
Tel: +971-4-214-6911,
E-mail: mea@prosoft-technology.com
Languages spoken include: English, Hindi
North America
(location in California)
Tel: +1.661.716.5100,
E-mail: support@prosoft-technology.com
Languages spoken include: English, Spanish
Latin America
(Oficina Regional)
Tel: +1-281-2989109,
E-Mail: latinam@prosoft-technology.com
Languages spoken include: Spanish, English
Latin America
Tel: +52-222-3-99-6565,
(location in Puebla, Mexico) E-mail: soporte@prosoft-technology.com
Languages spoken include: Spanish
Brasil
(location in Sao Paulo)
Tel: +55-11-5083-3776,
E-mail: brasil@prosoft-technology.com
Languages spoken include: Portuguese, English
For complete details regarding ProSoft Technology’s TERMS & CONDITIONS OF SALE,
WARRANTY, SUPPORT, SERVICE AND RETURN MATERIAL AUTHORIZATION
INSTRUCTIONS please see the documents on the Product DVD or go to
www.prosoft-technology/legal
Documentation is subject to change without notice.
Page 164 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
6.1
Support, Service & Warranty
User Manual
Return Material Authorization (RMA) Policies and Conditions
The following Return Material Authorization (RMA) Policies and Conditions
(collectively, "RMA Policies") apply to any returned product. These RMA Policies
are subject to change by ProSoft Technology, Inc., without notice. For warranty
information, see Limited Warranty (page 166). In the event of any inconsistency
between the RMA Policies and the Warranty, the Warranty shall govern.
6.1.1 Returning Any Product
a) In order to return a Product for repair, exchange, or otherwise, the
Customer must obtain a Return Material Authorization (RMA) number
from ProSoft Technology and comply with ProSoft Technology shipping
instructions.
b) In the event that the Customer experiences a problem with the Product for
any reason, Customer should contact ProSoft Technical Support at one of
the telephone numbers listed above (page 163). A Technical Support
Engineer will request that you perform several tests in an attempt to
isolate the problem. If after completing these tests, the Product is found to
be the source of the problem, we will issue an RMA.
c) All returned Products must be shipped freight prepaid, in the original
shipping container or equivalent, to the location specified by ProSoft
Technology, and be accompanied by proof of purchase and receipt date.
The RMA number is to be prominently marked on the outside of the
shipping box. Customer agrees to insure the Product or assume the risk
of loss or damage in transit. Products shipped to ProSoft Technology
using a shipment method other than that specified by ProSoft Technology,
or shipped without an RMA number will be returned to the Customer,
freight collect. Contact ProSoft Technical Support for further information.
d) A 10% restocking fee applies to all warranty credit returns, whereby a
Customer has an application change, ordered too many, does not need,
etc. Returns for credit require that all accessory parts included in the
original box (i.e.; antennas, cables) be returned. Failure to return these
items will result in a deduction from the total credit due for each missing
item.
6.1.2 Returning Units Under Warranty
A Technical Support Engineer must approve the return of Product under ProSoft
Technology’s Warranty:
a) A replacement module will be shipped and invoiced. A purchase order will
be required.
b) Credit for a product under warranty will be issued upon receipt of
authorized product by ProSoft Technology at designated location
referenced on the Return Material Authorization
i. If a defect is found and is determined to be customer generated, or if
the defect is otherwise not covered by ProSoft Technology s warranty,
there will be no credit given. Customer will be contacted and can
request module be returned at their expense;
ProSoft Technology, Inc.
June 14, 2011
Page 165 of 175
Support, Service & Warranty
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ii. If defect is customer generated and is repairable, customer can
authorize ProSoft Technology to repair the unit by providing a
purchase order for 30% of the current list price plus freight charges,
duties and taxes as applicable.
6.1.3 Returning Units Out of Warranty
a) Customer sends unit in for evaluation to location specified by ProSoft
Technology, freight prepaid.
b) If no defect is found, Customer will be charged the equivalent of $100
USD, plus freight charges, duties and taxes as applicable. A new
purchase order will be required.
c) If unit is repaired, charge to Customer will be 30% of current list price
(USD) plus freight charges, duties and taxes as applicable. A new
purchase order will be required or authorization to use the purchase order
submitted for evaluation fee.
The following is a list of non-repairable units:
o 3150 - All
o 3750
o 3600 - All
o 3700
o 3170 - All
o 3250
o 1560 - Can be repaired, only if defect is the power supply
o 1550 - Can be repaired, only if defect is the power supply
o 3350
o 3300
o 1500 - All
6.2
LIMITED WARRANTY
This Limited Warranty ("Warranty") governs all sales of hardware, software, and
other products (collectively, "Product") manufactured and/or offered for sale by
ProSoft Technology, Incorporated (ProSoft), and all related services provided by
ProSoft, including maintenance, repair, warranty exchange, and service
programs (collectively, "Services"). By purchasing or using the Product or
Services, the individual or entity purchasing or using the Product or Services
("Customer") agrees to all of the terms and provisions (collectively, the "Terms")
of this Limited Warranty. All sales of software or other intellectual property are, in
addition, subject to any license agreement accompanying such software or other
intellectual property.
Page 166 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Support, Service & Warranty
User Manual
6.2.1 What Is Covered By This Warranty
a) Warranty On New Products: ProSoft warrants, to the original purchaser,
that the Product that is the subject of the sale will (1) conform to and
perform in accordance with published specifications prepared, approved
and issued by ProSoft, and (2) will be free from defects in material or
workmanship; provided these warranties only cover Product that is sold as
new. This Warranty expires three (3) years from the date of shipment for
Product purchased on or after January 1st, 2008, or one (1) year from the
date of shipment for Product purchased before January 1st, 2008 (the
"Warranty Period"). If the Customer discovers within the Warranty Period
a failure of the Product to conform to specifications, or a defect in material
or workmanship of the Product, the Customer must promptly notify
ProSoft by fax, email or telephone. In no event may that notification be
received by ProSoft later than 39 months from date of original shipment.
Within a reasonable time after notification, ProSoft will correct any failure
of the Product to conform to specifications or any defect in material or
workmanship of the Product, with either new or remanufactured
replacement parts. ProSoft reserves the right, and at its sole discretion,
may replace unrepairable units with new or remanufactured equipment.
All replacement units will be covered under warranty for the 3 year period
commencing from the date of original equipment purchase, not the date of
shipment of the replacement unit. Such repair, including both parts and
labor, will be performed at ProSoft’s expense. All warranty service will be
performed at service centers designated by ProSoft.
b) Warranty On Services: Materials and labor performed by ProSoft to repair
a verified malfunction or defect are warranteed in the terms specified
above for new Product, provided said warranty will be for the period
remaining on the original new equipment warranty or, if the original
warranty is no longer in effect, for a period of 90 days from the date of
repair.
6.2.2 What Is Not Covered By This Warranty
a) ProSoft makes no representation or warranty, expressed or implied, that
the operation of software purchased from ProSoft will be uninterrupted or
error free or that the functions contained in the software will meet or
satisfy the purchaser’s intended use or requirements; the Customer
assumes complete responsibility for decisions made or actions taken
based on information obtained using ProSoft software.
ProSoft Technology, Inc.
June 14, 2011
Page 167 of 175
Support, Service & Warranty
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
b) This Warranty does not cover the failure of the Product to perform
specified functions, or any other non-conformance, defects, losses or
damages caused by or attributable to any of the following: (i) shipping; (ii)
improper installation or other failure of Customer to adhere to ProSoft’s
specifications or instructions; (iii) unauthorized repair or maintenance; (iv)
attachments, equipment, options, parts, software, or user-created
programming (including, but not limited to, programs developed with any
IEC 61131-3, "C" or any variant of "C" programming languages) not
furnished by ProSoft; (v) use of the Product for purposes other than those
for which it was designed; (vi) any other abuse, misapplication, neglect or
misuse by the Customer; (vii) accident, improper testing or causes
external to the Product such as, but not limited to, exposure to extremes
of temperature or humidity, power failure or power surges; or (viii)
disasters such as fire, flood, earthquake, wind and lightning.
c) The information in this Agreement is subject to change without notice.
ProSoft shall not be liable for technical or editorial errors or omissions
made herein; nor for incidental or consequential damages resulting from
the furnishing, performance or use of this material. The user guide
included with your original product purchase from ProSoft contains
information protected by copyright. No part of the guide may be duplicated
or reproduced in any form without prior written consent from ProSoft.
6.2.3 Disclaimer Regarding High Risk Activities
Product manufactured or supplied by ProSoft is not fault tolerant and is not
designed, manufactured or intended for use in hazardous environments requiring
fail-safe performance including and without limitation: the operation of nuclear
facilities, aircraft navigation of communication systems, air traffic control, direct
life support machines or weapons systems in which the failure of the product
could lead directly or indirectly to death, personal injury or severe physical or
environmental damage (collectively, "high risk activities"). ProSoft specifically
disclaims any express or implied warranty of fitness for high risk activities.
6.2.4 Intellectual Property Indemnity
Buyer shall indemnify and hold harmless ProSoft and its employees from and
against all liabilities, losses, claims, costs and expenses (including attorney’s
fees and expenses) related to any claim, investigation, litigation or proceeding
(whether or not ProSoft is a party) which arises or is alleged to arise from Buyer’s
acts or omissions under these Terms or in any way with respect to the Products.
Without limiting the foregoing, Buyer (at its own expense) shall indemnify and
hold harmless ProSoft and defend or settle any action brought against such
Companies to the extent based on a claim that any Product made to Buyer
specifications infringed intellectual property rights of another party. ProSoft
makes no warranty that the product is or will be delivered free of any person’s
claiming of patent, trademark, or similar infringement. The Buyer assumes all
risks (including the risk of suit) that the product or any use of the product will
infringe existing or subsequently issued patents, trademarks, or copyrights.
Page 168 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Support, Service & Warranty
User Manual
a) Any documentation included with Product purchased from ProSoft is
protected by copyright and may not be duplicated or reproduced in any
form without prior written consent from ProSoft.
b) ProSoft’s technical specifications and documentation that are included
with the Product are subject to editing and modification without notice.
c) Transfer of title shall not operate to convey to Customer any right to make,
or have made, any Product supplied by ProSoft.
d) Customer is granted no right or license to use any software or other
intellectual property in any manner or for any purpose not expressly
permitted by any license agreement accompanying such software or other
intellectual property.
e) Customer agrees that it shall not, and shall not authorize others to, copy
software provided by ProSoft (except as expressly permitted in any
license agreement accompanying such software); transfer software to a
third party separately from the Product; modify, alter, translate, decode,
decompile, disassemble, reverse-engineer or otherwise attempt to derive
the source code of the software or create derivative works based on the
software; export the software or underlying technology in contravention of
applicable US and international export laws and regulations; or use the
software other than as authorized in connection with use of Product.
f) Additional Restrictions Relating To Software And Other Intellectual
Property
In addition to compliance with the Terms of this Warranty, Customers
purchasing software or other intellectual property shall comply with any
license agreement accompanying such software or other intellectual
property. Failure to do so may void this Warranty with respect to such
software and/or other intellectual property.
6.2.5 Disclaimer of all Other Warranties
The Warranty set forth in What Is Covered By This Warranty (page 167) are in
lieu of all other warranties, express or implied, including but not limited to the
implied warranties of merchantability and fitness for a particular purpose.
ProSoft Technology, Inc.
June 14, 2011
Page 169 of 175
Support, Service & Warranty
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
6.2.6 Limitation of Remedies **
In no event will ProSoft or its Dealer be liable for any special, incidental or
consequential damages based on breach of warranty, breach of contract,
negligence, strict tort or any other legal theory. Damages that ProSoft or its
Dealer will not be responsible for include, but are not limited to: Loss of profits;
loss of savings or revenue; loss of use of the product or any associated
equipment; loss of data; cost of capital; cost of any substitute equipment,
facilities, or services; downtime; the claims of third parties including, customers of
the Purchaser; and, injury to property.
** Some areas do not allow time limitations on an implied warranty, or allow the exclusion or
limitation of incidental or consequential damages. In such areas, the above limitations may not
apply. This Warranty gives you specific legal rights, and you may also have other rights which vary
from place to place.
6.2.7 Time Limit for Bringing Suit
Any action for breach of warranty must be commenced within 39 months
following shipment of the Product.
6.2.8 No Other Warranties
Unless modified in writing and signed by both parties, this Warranty is
understood to be the complete and exclusive agreement between the parties,
suspending all oral or written prior agreements and all other communications
between the parties relating to the subject matter of this Warranty, including
statements made by salesperson. No employee of ProSoft or any other party is
authorized to make any warranty in addition to those made in this Warranty. The
Customer is warned, therefore, to check this Warranty carefully to see that it
correctly reflects those terms that are important to the Customer.
6.2.9 Allocation of Risks
This Warranty allocates the risk of product failure between ProSoft and the
Customer. This allocation is recognized by both parties and is reflected in the
price of the goods. The Customer acknowledges that it has read this Warranty,
understands it, and is bound by its Terms.
Page 170 of 175
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Support, Service & Warranty
User Manual
6.2.10 Controlling Law and Severability
This Warranty shall be governed by and construed in accordance with the laws of
the United States and the domestic laws of the State of California, without
reference to its conflicts of law provisions. If for any reason a court of competent
jurisdiction finds any provisions of this Warranty, or a portion thereof, to be
unenforceable, that provision shall be enforced to the maximum extent
permissible and the remainder of this Warranty shall remain in full force and
effect. Any cause of action with respect to the Product or Services must be
instituted in a court of competent jurisdiction in the State of California.
ProSoft Technology, Inc.
June 14, 2011
Page 171 of 175
Support, Service & Warranty
User Manual
Page 172 of 175
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Contacting Technical Support • 163, 165
Controlling Law and Severability • 171
Create the Module - Local Rack • 28, 33
Create the Module - Remote Rack • 30
Create the Remote Network • 28, 33
Creating a New RSLogix 5000 Project • 27
Index
0
00 Return Query Data • 139
A
About the MODBUS TCP/IP Protocol • 112
Adding Multiple Modules (Optional) • 39
Adding the Module to an Existing Project • 155
Adjusting the Input and Output Array Sizes (Optional) •
46
Allocation of Risks • 170
ARP Timeout • 58
B
Backplane Data Transfer • 113
Backplane Status • 98
Battery Life Advisory • 3
Before You Begin • 146
Bit Input Offset • 66
Block 9990
Set Module IP Address • 121
Block 9991
Get Module IP Address • 121
Block Request from Processor to Module • 115
Block Response from Module to Processor • 116
C
Choosing the Controller Type • 160
Clearing a Fault Condition • 106
Client Command Errors • 100, 128
Client Command List • 128
Client Configuration Error Word • 105
Client Driver • 127
Client Status Data • 115
Cold Boot Block (9999) • 122
Command Control Blocks (5001 to 5006) • 120
Command Entry Formats • 60
Command Error Delay • 58
Command Error Pointer • 56
Command List • 100
Command List Entry Errors • 129
Command List Overview • 59
Command Status • 100
Commands Supported by the Module • 132
Comment • 64
Config • 97, 100, 101
Configuring Module Parameters • 53
Configuring the MVI56E-MNETR Module • 49
Connecting to the Module's Web Page • 26
Connecting Your PC to the ControlLogix Processor •
47
Connecting Your PC to the Module • 18
ProSoft Technology, Inc.
June 14, 2011
Index
User Manual
D
Data Flow between MVI56E-MNETR Module and
ControlLogix Processor • 125
Diagnostics (Function Code 08) • 139
Diagnostics and Troubleshooting • 9, 91, 103
Disclaimer of all Other Warranties • 169
Disclaimer Regarding High Risk Activities • 168
Downloading the Project to the Module • 69
Downloading the Sample Program to the Processor •
48, 157, 162
Duplex/Speed Code • 56
E
Enable • 61
Error/Status Pointer • 54, 56
Ethernet Cable Configuration • 130
Ethernet Cable Specifications • 130
Ethernet Configuration • 68
Ethernet LED Indicators • 103
Ethernet Performance • 130
Event Command Block (2000) • 118
Example 1
Local Rack Application • 73
Example 2
Remote Rack Application • 76
Example and state diagram • 139
F
Failure Flag Count • 55
Float Flag • 57, 65
Float Offset • 58, 66
Float Start • 57, 66
Force Multiple Coils (Function Code 15) • 141
Force Single Coil (Function Code 05) • 137
Formatted • 123
Functional Overview • 9, 112
Functional Specifications • 111
G
General Specifications • 110
Guide to the MVI56E-MNETR User Manual • 9
H
Hardware MAC Address • 68
Hardware Specifications • 111
Holding Register Offset • 66
How to Contact Us • 2
I
Import Add-On Instruction • 36
Page 173 of 175
Index
User Manual
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Important Safety Information - MVI56E Modules • 3
Initialize Output Data • 55, 116
Installing ProSoft Configuration Builder • 17
Installing the Configuration Tools • 17
Installing the Module in the Rack • 16
Installing the Rung Import with Optional Add-On
Instruction • 147
Intellectual Property Indemnity • 168
Internal Address • 61
IP Address • 67
L
Ladder Logic • 79
LED Status Indicators • 102
Limitation of Remedies ** • 170
LIMITED WARRANTY • 165, 166
M
MB Address in Device • 64
Minimum Command Delay • 57
MNET Client Specific Errors • 129
MNET Client x • 56
MNET Client x Commands • 58
MNET Servers • 65, 101
MNETRBLOCKSTATS • 82
MNETRCLIENTSTATS • 82, 83
MNETRCMDCONTROL • 84, 85
MNETRCOILARRAY • 86
MNETRCONTROL • 80, 84
MNETRDATA • 80, 81
MNETREVENTCMD • 84
MNETRINITOUTDATA • 87, 88
MNETRIPADDRESS • 84, 86
MNETRMODULEDEF • 80
MNETRPASSTHRU • 84, 86
MNETRSTATUS • 80, 82
MNETRUTIL • 80, 87
Modbus Exception Codes • 144
Modbus Exception Responses • 143
Modbus Function • 63
Modbus Message Data • 89
Modbus Protocol Specification • 132
Module • 54
Module Communication Error Codes • 129
Module Power Up • 112
Monitoring Backplane Information • 97
Monitoring Database Information • 99
Monitoring MNET Client Information • 100
Monitoring MNET Server Information • 101
Monitoring Module Information • 97
N
NIC Status • 97
No Other Warranties • 170
Node IP Address • 62, 63
Non-Scrolling LED Status Indicators • 104
Normal Data Transfer Blocks • 114
Page 174 of 175
O
Opening the Sample Program in RSLogix • 158
Output Offset • 66
Overview • 146
P
Package Contents • 14
Pass-Through Control Blocks • 89, 122
Pass-Through Mode • 56
Pinouts • 110, 111, 130
Poll Interval • 61
Preset Multiple Registers (Function Code 16) • 142
Preset Single Register (Function Code 06) • 138
Printing a Configuration File • 53
Product Specifications • 9, 110
ProSoft Technology® Product Documentation • 2
R
Read Coil Status (Function Code 01) • 133
Read Holding Registers (Function Code 03) • 135
Read Input Registers (Function Code 04) • 136
Read Input Status (Function Code 02) • 134
Read Register Count • 54
Read Register Start • 54
Reading Status Data from the Module • 92
Reading the Clock Value from the Module • 153
Reading the Ethernet Settings from the Module • 150
Reference • 9, 109
Reg Count • 62
Renaming PCB Objects • 53
Response Timeout • 57
Retry Count • 57
Return Material Authorization (RMA) Policies and
Conditions • 165
Returning Any Product • 165
Returning Units Out of Warranty • 166
Returning Units Under Warranty • 165
S
Scrolling LED Status Indicators • 102
Selecting the Slot Number for the Module • 161
Server Driver • 125
Service Port • 63
Setting Jumpers • 15
Setting Temporary IP Address • 19, 26
Setting Up the Project • 51
Slave Address • 63
Special Function Blocks • 117
Standard Modbus Exception Code Errors • 129
Start Here • 9, 11
Static ARP • 97
Static ARP Table • 67, 97
Status • 100, 101
Status Data Definition • 98, 131
Status Read Data Block • 115
Sub-function codes supported • 139
Support, Service & Warranty • 9, 163
Swap Code • 62
ProSoft Technology, Inc.
June 14, 2011
MVI56E-MNETR ♦ ControlLogix Platform
Modbus TCP/IP Interface Module with Reduced Data Block
Index
User Manual
System Requirements • 13
T
The Diagnostics Menu • 93
Time Limit for Bringing Suit • 170
Troubleshooting • 107
U
Unformatted • 122
Uploading the Add-On Instruction from the Module •
27, 36
Using CIPconnect to Connect to the Module • 24, 95,
130
Using CIPconnect® to Connect to the Module • 71, 95,
130
Using ProSoft Configuration Builder Software • 50
Using the Diagnostics Menu in ProSoft Configuration
Builder • 93
Using the Optional Add-On Instruction Rung Import •
146
Using the Sample Program • 27, 158
V
Version • 97
W
Warm Boot Block (9998) • 122
What Is Covered By This Warranty • 167, 169
What Is Not Covered By This Warranty • 167
What's New? • 12
Word Input Offset • 67
Write Register Count • 55
Write Register Start • 55
Writing the Clock Value to the Module • 154
Writing the Ethernet Settings to the Module • 152
Y
Your Feedback Please • 2
ProSoft Technology, Inc.
June 14, 2011
Page 175 of 175