ProSoft Technology MVI56E-MNETC User manual

MVI56E-MNETC
ControlLogix Platform
Modbus TCP/IP Multi Client
Enhanced Communication Module
April 18, 2011
SETUP GUIDE

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
[phone]
[phone] (Fax)
www.prosoft-technology.com
[e-mail]
Copyright © 2011 ProSoft Technology, Inc., all rights reserved.
MVI56E-MNETC Setup Guide
April 18, 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

Important Safety Information
North America Warnings
A Warning - Explosion Hazard - Substitution of components may impair suitability for Class I, Division 2.
B 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.
C Suitable for use in Class I, Division 2 Groups A, B, C, and D, T5 Hazardous Locations or Non-Hazardous
Locations.
ATEX 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 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 DO NOT OPEN WHEN ENERGIZED.
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
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 EN61010
ATEX EN60079-0
EN60079-15
243333 E183151 ME06
<cULus>
E183151
Class I Division 2 Groups A, B, C, and D
Temp Code T5
0°C to +60°C
Atex
Class I Division 2 Groups A, B, C, and D
Temp Code T5
0°C <= Ta <= 60°C
Battery Life Advisory
Note: Modules manufactured after April 1
st
, 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: he battery is not user-replaceable or serviceable.

MVI56E-MNE C ♦ ControlLogix Platform Contents
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 5 of 72
April 18, 2011
Contents
Your Feedback Please........................................................................................................................ 2
How to Contact Us .............................................................................................................................. 2
ProSoft Technology
®
Product Documentation .................................................................................... 2
Important Safety Information............................................................................................................... 3
Battery Life Advisory ........................................................................................................................... 4
1 Scope 7
1.1 What's New? ............................................................................................................. 8
1.2 Learning Objectives................................................................................................... 9
1.3 ProSoft Technology Documentation .......................................................................10
1.4 Prerequisites ...........................................................................................................11
2 Before You Begin 13
2.1 System Requirements ............................................................................................. 14
2.2 Required Items ........................................................................................................15
2.3 Sample Files............................................................................................................16
3 The Sample Application 17
3.1 About the MODBUS TCP/IP Protocol .....................................................................18
3.2 General Overview....................................................................................................19
3.2.1 Required Steps........................................................................................................19
3.3 Architecture .............................................................................................................20
3.4 Memory Map ...........................................................................................................21
4 Procedures 23
4.1 Setting Jumpers ......................................................................................................24
4.2 Installing the Module in the Rack ............................................................................25
4.3 Creating a New RSLogix 5000 Project....................................................................27
4.3.1 Creating the Module ................................................................................................28
4.3.2 Importing the Add-On Instruction ............................................................................30
4.4 Connecting Your PC to the ControlLogix Processor...............................................33
4.5 Downloading the Sample Program to the Processor ..............................................34
4.6 Using ProSoft Configuration Builder Software ........................................................35
4.6.1 Installing ProSoft Configuration Builder ..................................................................35
4.6.2 Setting Up the Project .............................................................................................36
4.6.3 Uploading the Sample Configuration from the Module ...........................................38
4.6.4 Enabling the MNET Client 0 Commands ................................................................40
4.7 Connecting Your PC to the Module.........................................................................43
4.7.1 Setting Up a Temporary IP Address .......................................................................43
4.8 Downloading the Project to the Module ..................................................................47
4.8.1 Using CIPconnect to Connect to the Module ..........................................................49
4.8.2 Using RSWho to Connect to the Module ................................................................51
4.9 Configuring the NOE Ethernet adapter for Modbus TCP/IP (Server) .....................53
4.10 Connecting the MVI56E-MNETC Module to the Modbus TCP/IP Server ...............54

Contents MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 6 of 72 ProSoft Technology, Inc.
April 18, 2011
4.11 Verifying Communication........................................................................................ 55
4.11.1 Viewing Exchanged Data........................................................................................ 55
4.11.2 Checking Module Status through ControlLogix Controller Tags ............................ 58
4.11.3 LED Status Indicators ............................................................................................. 59
5 Building on Success 61
5.1 Frequently Asked Questions................................................................................... 62
5.1.1 What are the differences between the MVI56 and the MVI56E modules? What
does the "E" stand for?................................................................................................................ 62
5.1.2 What is the difference between the MVI56E-MNET(R) and the MVI56E-
MNETC(R)? 63
5.1.3 Is the MVI56E product a direct replacement to my existing MVI56 product?......... 63
5.1.4 How is the MVI56E-MNETC configured? ............................................................... 63
5.1.5 What is ProSoft Configuration Builder (PCB)? ....................................................... 63
5.1.6 What is the purpose of the MVI56E-MNETC Ethernet (E1) Port?.......................... 63
5.1.7 How do I change the module’s IP address? ........................................................... 64
5.1.8 What is the purpose of the Optional MVI56E-MNETC Add-On Instruction? .......... 64
5.1.9 What is ProSoft Discovery Service (PDS)? ............................................................ 64
5.1.10 Does the MVI56E-MNETC module require processor logic? ................................. 64
5.1.11 How do I monitor MVI56E-MNETC operation?....................................................... 65
5.1.12 Are there any other ways to monitor module diagnostics besides being connected
to the module’s network (subnet)? .............................................................................................. 65
Glossary of Terms 67
Index 71

MVI56E-MNE C ♦ ControlLogix Platform Scope
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 7 of 72
April 18, 2011
1 Scope
In This Chapter
What's New? ...........................................................................................8
Learning Objectives.................................................................................9
ProSoft Technology Documentation...................................................... 10
Prerequisites ......................................................................................... 11
This document acts as a tutorial, providing step-by-step instructions on how to
read and write bi-directional data from one network device to another network
device using the MVI56E-MNETC.

Scope MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 8 of 72 ProSoft Technology, Inc.
April 18, 2011
1.1 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.
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.

MVI56E-MNE C ♦ ControlLogix Platform Scope
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 9 of 72
April 18, 2011
1.2 Learning Objectives
When you have completed all the steps in this Setup Guide, you will have
learned how to
Understand how the sample application works (page 17)
Install the MVI56E-MNETC configuration software
Install the MVI56E-MNETC module
Import the Add-On Instruction to the processor (page 34)
Configure the Modbus TCP/IP Client (page 40)
Verify the MVI56E-MNETC module communication status (page 55)

Scope MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 10 of 72 ProSoft Technology, Inc.
April 18, 2011
1.3 ProSoft Technology Documentation
ProSoft Technology provides the following documentation (manuals) with your
MVI56E-MNETC.
Documentation, tools, and product support
Web Site Support: Visit the ProSoft Technology web site at
www.prosoft-technology.com to download additional documentation, tools,
and application information.
Email Technical Support: Send your support questions to Support@prosoft-
technology.com.
Telephone Support: Please call ProSoft Technology Technical Support at:
(Country Code 1+) 661-716-5100. Support is available 24 hours a day, 7
days a week. ProSoft Technology telephone support is free and unlimited.

MVI56E-MNE C ♦ ControlLogix Platform Scope
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 11 of 72
April 18, 2011
1.4 Prerequisites
To get the most benefit from this setup guide, you should have the following
skills:
Rockwell Automation
®
RSLogix™ 5000 software: launch the program,
configure and transfer the Add-On Instruction to the processor
Microsoft Windows: install and launch programs, execute menu commands,
navigate dialog boxes and enter data.
Ethernet networking: connect the MVI56E-MNETC module to an Ethernet
network using a valid IP address and subnet mask
Hardware installation and wiring: install the module and safely connect
Modbus TCP/IP Client and ControlLogix devices to a power source and to the
MVI56E-MNETC module’s Ethernet port

Scope MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 12 of 72 ProSoft Technology, Inc.
April 18, 2011

MVI56E-MNE C ♦ ControlLogix Platform Before You Begin
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 13 of 72
April 18, 2011
2 Before You Begin
In This Chapter
System Requirements ........................................................................... 14
Required Items ...................................................................................... 15
Sample Files.......................................................................................... 16

Before You Begin MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 14 of 72 ProSoft Technology, Inc.
April 18, 2011
2.1 System Requirements
The MVI56E-MNETC 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-MNETC 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: he Hardware and Operating System requirements in this list are the minimum
recommended to install and run software provided by ProSoft echnology
®
. 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.

MVI56E-MNE C ♦ ControlLogix Platform Before You Begin
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 15 of 72
April 18, 2011
2.2 Required Items
This Setup Guide uses a sample application that shows you how to establish
communication between the MVI56E-MNETC module (Modbus TCP/IP Client)
and a Modbus TCP/IP Server device. The sample application requires the
following equipment.
Item Description
MVI56E-MNETC Modbus TCP/IP Multi Client Enhanced Communication Module
1756-L63 ControlLogix processor
1756-A7/B 1 ControlLogix rack
1756-PA72/B 1 ControlLogix rack power supply
CPU434 12A Quantum processor (Modbus device)
CPS 114 20 Quantum power supply
140XBP01000 Quantum rack
140NOE77111 NOE Card
Ethernet cable Ethernet cable to connect MVI56E-MNETC module to Ethernet network
for Modbus TCP/IP communication and diagnostics (supplied with the
module)

Before You Begin MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 16 of 72 ProSoft Technology, Inc.
April 18, 2011
2.3 Sample Files
Note: his procedure requires RSLogix 5000 version 16 (or later), which supports Add-On
Instructions. For RSLogix version 15 (or older) applications, please refer to the MVI56E-MNETC
User Manual for information on how to use the sample ladder logic.
The sample MVI56EMNETC_AddOn_Rung_v1_5.L5X Add-On Instruction file
contains all elements required for the MVI56E-MNETC module to function.
User-defined Data Types (UDTs)
Add-On Instruction (AOI)
Ladder rung with AOI
Controller tags
Item Description
MVI56EMNE C_AddOn_Rung_v1_5.L5X Sample rung import file containing Add-On
Instruction
Copy the file from the ProSoft Solutions CD-ROM, or download them from
www.prosoft-technology.com. Save it to a convenient location in your PC, such
as Desktop or My Documents.

MVI56E-MNE C ♦ ControlLogix Platform he Sample Application
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 17 of 72
April 18, 2011
3 The Sample Application
In This Chapter
About the MODBUS TCP/IP Protocol.................................................... 18
General Overview.................................................................................. 19
Architecture ........................................................................................... 20
Memory Map ......................................................................................... 21

he Sample Application MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 18 of 72 ProSoft Technology, Inc.
April 18, 2011
3.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-MNETC 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-MNETC 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.

MVI56E-MNE C ♦ ControlLogix Platform he Sample Application
Modbus CP/IP Multi Client Enhanced Communication Module Setup Guide
ProSoft Technology, Inc. Page 19 of 72
April 18, 2011
3.2 General Overview
This Setup Guide shows you how to configure the MVI56E-MNETC module and
establish communication with a Modbus TCP/IP device (a Quantum processor
with a NOE Ethernet adapter, for this example).
The MVI56E-MNETC Ethernet application port will be configured as a Modbus
TCP/IP (MNET) Client device. The NOE Ethernet adapter will operate as a
Modbus TCP/IP Server device, passing data to the Quantum processor. The
MVI56E-MNETC will be configured to send two MNET Client commands to the
Modbus TCP/IP Server device:
Write 10 words (Modbus Function 16 - Preset [Write] Multiple Registers
Read 10 words (Modbus Function 3 -Read Holding Registers
When you finish the steps in this Setup Guide, you will have enough information
to set up your own application.
3.2.1 Required Steps
This Setup Guide will take you through the following steps:
1 Install the ProSoft Module in the rack
2 Use the Add-On Instruction to Configure the Module (page 27)
3 Connect your PC to the Processor (page 33)
4 Download the Sample Program to the Processor (page 34)
5 Set up the Sample Application (page 38)
a Configure the Modbus TCP/IP Client
b Configure the Modbus TCP/IP Client Read Command
c Configure the Modbus TCP/IP Client Write Command (page 41, page 42)
6 Transfer the configuration to the module (page 47)
7 Set up the NOE Modbus TCP/IP Server (page 53)
8 Verify Communication (page 55)

he Sample Application MVI56E-MNE C ♦ ControlLogix Platform
Setup Guide Modbus CP/IP Multi Client Enhanced Communication Module
Page 20 of 72 ProSoft Technology, Inc.
April 18, 2011
3.3 Architecture
The sample application uses the following hardware and connections.
A Personal Computer running a supported version of Microsoft Windows, with
a web browser, RSLogix 5000, ProSoft Discovery Service and an Ethernet
port
A ControlLogix processor with MVI56E-MNETC module acting as a Modbus
TCP/IP Client
A Quantum processor with a NOE Ethernet adapter acting as a Modbus
TCP/IP Server
An Ethernet network connecting the PC with the MVI56E-MNETC, either
directly, or through an Ethernet hub or switch.
An Ethernet cable connecting the MVI56E-MNETC Modbus TCP/IP Client to
the Modbus TCP/IP Server.
The following illustration shows the sample application.
Note: he illustration does not show the required Ethernet connection for processor programming.