mvi56e mcmmcmxt setup guide

7/27/2019 Mvi56e Mcmmcmxt Setup Guide

http://slidepdf.com/reader/full/mvi56e-mcmmcmxt-setup-guide 1/78

MVI56E-MCM /

MCMXTControlLogix PlatformModbus Communication Module

November 29, 2010

SETUP GUIDE



Your Feedback PleaseWe 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 UsProSoft Technology 5201 Truxtun Ave., 3rd FloorBakersfield, CA 93309+1 (661) 716-5100+1 (661) 716-5101 (Fax)[email protected]

Copyright © 2010 ProSoft Technology, Inc., all rights reserved.

MVI56E-MCM / MCMXT Setup Guide

November 29, 2010

ProSoft Technology ® , ProLinx ® , inRAx ® , ProTalk ® , and RadioLinx ® are Registered Trademarks of ProSoftTechnology, Inc. All other brand or product names are or may be trademarks of, and are used to identify productsand services of, their respective owners.

ProSoft Technology ® Product DocumentationIn 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.comPrinted documentation is available for purchase. Contact ProSoft Technology for pricing and availability.North America: +1.661.716.5100

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



Important Safety Information - MVI56E-MCM/XT

North America WarningsA 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.

C Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area isknown to be nonhazardous.D Suitable for use in Class I, Division 2 Groups A, B, C, and D, 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 jurisdictionA 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 usedonly with ATEX certified backplanes.DO NOT OPEN WHEN ENERGIZED.

Markings

Agency Approvals and CertificationsAgency Applicable Standards

RoHS

ATEX EN60079-0 July 2006EN60079-15 October 2005

CSA IEC61010

CE EMC-EN61326-1:2006EN61000-6-4:2007

CSA CB Safety CA/10533/CSA IEC 61010-1 Ed. 2CB 243333-2056722 (2090408)

cULus

GOST-R EN61010

Lloyds Lloyds Register Test Specification Number 1,2002

243333 E183151 ME06



Label Markings

<Ex>II 3 GEx nA T50°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>E183151Class I, DIV 2, groups A,B,C,DT5 for all models0°C to +60°C-25°C to +70°C (XT models only)

Battery Life AdvisoryThe module uses a rechargeable Lithium Vanadium Pentoxide battery to back up the real-time clock and CMOSsettings. The battery itself should last for the life of the module. However, if left in an unpowered state for 14 to 21days, the battery may become fully discharged and require recharging by being placed in a powered-up ControlLogixchassis. 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 forapproximately 21 days. Before you remove a module from its power source, ensure that the battery within the moduleis fully charged (the BATT LED on the front of the module goes OFF when the battery is fully charged). If the batteryis 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.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform ContentsModbus Communication Module Setup Guide

ProSoft Technology, Inc. of 78November 29, 2010

ContentsYour Feedback Please ........................................................................................................................ 2 How to Contact Us .............................................................................................................................. 2 ProSoft Technology ® Product Documentation .................................................................................... 2 Important Safety Information - MVI56E-MCM/XT ............................................................................... 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 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 Module Jumpers.......................................................................................... 24 4.2 Installing the Module in the Rack ............................................................................ 25 4.3 Using ProSoft Configuration Builder Software ........................................................ 27

4.3.1 Setting Up the Project ............................................................................................. 28 4.3.2 Connecting Your PC to the Module's Ethernet Port ................ ................. ............... 29 4.3.3 Setting Up a Permanent IP Address ....................................................................... 33

4.4 Importing the Sample Add-On Instruction ............................................................... 45 4.4.1 Creating a New RSLogix 5000 Project .................. .................. ................. ............... 45 4.4.2 Creating the Module ................................................................................................ 46 4.4.3 Import the Ladder Rung .......................................................................................... 49

4.5 Connecting Your PC to the ControlLogix Processor .................. ................. ............ 53

4.6

Downloading the Sample Program to the Processor .............................................. 54

4.7 Setting up the Read and Write Database Areas ..................................................... 55 4.7.1 Configuring Modbus Port 1 (P1) .............................................................................. 56 4.7.2 Configuring the Modbus Master Read Command ................ .................. ................. 58 4.7.3 Configuring the Modbus Master Write Command ................................................... 59

4.8 Rebooting the Module to Transfer New Parameter Values .................................... 60 4.9 Configuring the Quantum Processor as a Modbus Slave ................ ................. ...... 61 4.10 Connecting the MVI56E-MCM Module to the Quantum Processor ........................ 62



Contents MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module

of 78 ProSoft Technology, Inc.November 29, 2010

4.11 Verifying Communication ........................................................................................ 63 4.11.1 Viewing Exchanged Data ........................................................................................ 63 4.11.2 Checking Module Status through ControlLogix Controller Tags ............................ 66 4.11.3 Scrolling LED Status Indicators .............................................................................. 67 4.11.4 Non-Scrolling LED Status Indicators ...................................................................... 68

5 Building on Success 69

5.1 Frequently Asked Questions ................................................................................... 70 5.1.1 What are the differences between the MVI56 and the MVI56E modules? Whatdoes the "E" stand for? .................. ................. .................. .................. .................. ................. ...... 70 5.1.2 Is the MVI56E product a direct replacement to my existing MVI56 product? ......... 70 5.1.3 How is the MVI56E-MCM configured? ................................................................... 70 5.1.4 What is ProSoft Configuration Builder (PCB)? ....................................................... 71 5.1.5 What is ProSoft Discovery Service (PDS)? ............................................................ 71 5.1.6 What is the purpose of the MVI56E-MCM Ethernet Config (E1) Port? .................. 71 5.1.7 How do I change the module’s IP address? ........................................................... 71 5.1.8 Does the MVI56E-MCM module require processor logic? ..................................... 71 5.1.9 What is the purpose of the Optional MVI56E-MCM Add-On Instruction? .............. 72 5.1.10 How do I monitor MVI56E-MCM operation? ........................................................... 72 5.1.11 Are there any other ways to monitor module diagnostics besides being connectedto the module’s network (subnet)? .............................................................................................. 72

Glossary of Terms 73

Index 77



MVI56E-MCM / MCMXT ♦ ControlLogix Platform ScopModbus Communication Module Setup Guide


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 toread and write bi-directional data from one network device to another networkdevice using the MVI56E-MCM / MCMXT.



Scope MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


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 andupgrade to benefit from an array of new features designed to improveinteroperability and enhance ease of use. ProSoft Configuration Builder (PCB): Microsoft Windows ® -based utility

software for diagnostics. Connect through the module's Ethernet port or useCIPconnect ® to access troubleshooting features and functions.

ProSoft Discovery Service (PDS): New Windows-based utility software tofind and display a list of MVI56E modules on the network and to temporarilychange a module's IP address to be able to connect with a module's webpage.

CIPconnect-enabled: Allows PC-to-module diagnostics from the Ethernetnetwork through a ControlLogix ® 1756-ENxT EtherNet/IP™ module.

Personality Card: An industrial-grade compact flash memory card storingthe module’s Ethernet settings, allowing quick and easy replacement.

LED Scrolling Diagnostic Display: 4-character, alphanumeric display,providing English messages for status and alarm data, and for processor andnetwork communication status.

XT series for Extreme Environments: The MVI56E-MCMXT is part of thenew XT series, designed to work at extreme temperatures and in harsh orcaustic environments. XT series modules operate over a wider temperaturerange than the standard MVI56E series. The XT series also comes withconformal coating to protect module components from corrosiveenvironmental elements.





1.2 Learning Objectives

When you have completed all the steps in this Setup Guide, you will havelearned how to

Use the sample application (page 17)

Install the MVI56E-MCM setup and diagnostic softwareInstall the MVI56E-MCM moduleImport the Add-On Instruction to the processor (page 54)Configure the Modbus Master using the sample Add-On InstructionConfigure the Modbus Slave (page 61)Verify the MVI56E-MCM module communication status (page 63)





1.3 ProSoft Technology Documentation

ProSoft Technology provides the following documentation (manuals) with yourMVI56E-MCM.Documentation, tools, and product support

Web Site Support: Visit the ProSoft Technology web site atwww.prosoft-technology.com to download additional documentation, tools,and application information.

Email Technical Support: Send your support questions to [email protected].

Telephone Support: Please call ProSoft Technology Technical Support at:(Country Code 1+) 661-716-5100. Support is available 24 hours a day, 7days a week. ProSoft Technology telephone support is free and unlimited.





1.4 Prerequisites

To get the most benefit from this Setup Guide , you should have the followingskills: Rockwell Automation ® RSLogix™ 5000 software: launch the program,

configure, and transfer the Add-On Instruction (or ladder logic) SampleApplication program to the processor Microsoft Windows ® : install and launch programs, execute menu

commands, navigate dialog boxes and enter data. Serial data communication: correctly configure data communication

parameters such as baud rate, parity, data bits, and so on, using thedocumentation for the devices connected to the network

Ethernet networking: connect the MVI56E-MCM module to an Ethernetnetwork using a valid IP address and subnet mask

Hardware installation and wiring : install the module and safely connectModbus Master/Slave and ControlLogix devices to a power source and to theMVI56E-MCM module’s serial ports



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Before You BeModbus Communication Module Setup Guide


2 Before You Begin

In This Chapter

System Requirements ........................................................................... 14

Required Items ...................................................................................... 15

Sample Files .......................................................................................... 16



Before You Begin MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


2.1 System Requirements

The MVI56E-MCM module requires the following minimum hardware andsoftware components:

Rockwell Automation ControlLogix ® processor (firmware version 10 or

higher), with compatible power supply, and one free slot in the rack for theMVI56E-MCM module. The module requires 800 mA of available 5 VdcpowerRockwell Automation RSLogix 5000 programming softwareo Version 16 or higher required for Add-On Instructiono Version 15 or lower must use Sample Ladder, available from

www.prosoft-technology.comRockwell Automation RSLinx ® communication software version 2.51 or higherProSoft 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 ® Vistao Microsoft Windows XP Professional with Service Pack 1 or 2o Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3o Microsoft Windows Server 2003128 Mbytes of RAM minimum, 256 Mbytes of RAM recommended100 Mbytes of free hard disk space (or more based on applicationrequirements)256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color1024 × 768 recommended)CD-ROM drive

Note: The Hardware and Operating System requirements in this list are the minimumrecommended to install and run software provided by ProSoft Technology®. Other third partyapplications may have different minimum requirements. Refer to the documentation for any thirdparty applications for system requirements.Note: You can install the module in a local or remote rack. For remote rack installation, the modulerequires EtherNet/IP or ControlNet communication with the processor.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Before You BeModbus Communication Module Setup Guide


2.2 Required Items

This Setup Guide uses a sample application that shows you how to establishcommunication between the MVI56E-MCM module (Master Port) and a ModbusSlave device. The sample application requires the following equipment.

Item DescriptionMVI56E-MCM Modbus Communication Module

1756-L63 ControlLogix processor

1756-A7/B ControlLogix rack

1756-PA72/B ControlLogix rack power supply

CPU434 12A Quantum processor (Modbus device)

CPS 114 20 Quantum power supply

140XBP01000 Quantum rack

Ethernet cable Ethernet cable to connect MVI56E-MCM module to Ethernet networkfor diagnostics (supplied with the module)

Serial cable Serial cable to connect MVI56E-MCM module to Modbus serial

network



Before You Begin MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


2.3 Sample Files

Note: This procedure requires RSLogix 5000 version 16 (or later), which supports Add-OnInstructions. For RSLogix version 15 (or older) applications, please refer to theMVI56E-MCM User Manual for information on how to use the sample ladder logic.

The sample MVI56(E)MCM_AddOn_Rung_v2_2.L5X Add-On Instruction filecontains all elements required for the MVI56E-MCM module to function.

User-defined Data Types (UDTs)Add-On Instruction (AOI)Ladder rung with AOIController tags

Item Description

MVI56(E)MCM_AddOn_Rung_v2_2.L5X Sample rung import file containing Add-OnInstruction

Copy the file from the ProSoft Solutions CD-ROM , or download them fromwww.prosoft-technology.com. Save it to a convenient location in your PC, suchas Desktop or My Documents .



MVI56E-MCM / MCMXT ♦ ControlLogix Platform The Sample ApplicatModbus Communication Module Setup Guide


3 The Sample Application

In This Chapter

About the MODBUS Protocol ................................................................ 18

General Overview ........... .......... ........... .......... ........... .......... ........... ........ 19

Architecture ........................................................................................... 20

Memory Map ......................................................................................... 21



The Sample Application MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


3.1 About the MODBUS 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 theautomation industry.

The original MODBUS specification uses a serial connection to communicatecommands and data between Master and Slave devices on a network. Laterenhancements to the protocol allow communication over other types of networks.MODBUS is a Master/Slave protocol. The Master establishes a connection to theremote Slave. When the connection is established, the Master sends theMODBUS commands to the Slave. The MVI56E-MCM module can work as aMaster and as a Slave.The MVI56E-MCM module also works as an input/output module between itselfand the Rockwell Automation backplane and processor. The module uses aninternal database to pass data and commands between the processor andMaster and Slave devices on MODBUS networks.





3.2 General Overview

This Setup Guide shows you how to configure the MVI56E-MCM module andestablish communication with a Modbus device (a Quantum processor, for thisexample).

The MVI56E-MCM Port 1 (P1) will be configured as a Modbus Master device.The Quantum processor will operate as a Modbus Slave device (Modbus Comm1). The MVI56E-MCM will be configured to send two Master commands to theModbus Slave device:

Write 10 words (Modbus Function 16 - Preset [Write] Multiple RegistersRead 10 words (Modbus Function 3 -Read Holding Registers

When you finish the steps in this Setup Guide, you will have enough informationto 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 rack2 Use the Add-On Instruction to Configure the Module (page 45)3 Connect your PC to the Processor (page 53)4 Download the Sample Program to the Processor (page 54)

5 Set up the Read and Write Database Areasa Configure Modbus Port 1 (P1) (page 56)b Configure the Modbus Master Read Command (page 58, page 59)c Configure the Modbus Master Write Command (page 59)

6 Reboot the module (page 60)7 Set up the Quantum Processor Modbus Slave Port (page 61)8 Verify Communication (page 63)





3.3 Architecture

The sample application uses the following hardware and connections.A Personal Computer running a supported version of Microsoft Windows, witha web browser, RSLogix 5000, ProSoft Discovery Service and an Ethernet

portA ControlLogix processor with MVI56E-MCM module acting as a ModbusMasterA Quantum processor acting as a Modbus SlaveAn Ethernet network connecting the PC with the MVI56E-MCM, either directlyor through an Ethernet hub or switch.An RS-232 serial cable connecting the MVI56E-MCM Modbus Master Port 1to the Quantum processor Modbus Slave Port.

The following illustration shows the sample application.

Note: The illustration does not show the required Ethernet connection for processor programming.





3.4 Memory Map

The memory map consists of the starting addresses for Read Data and WriteData areas in the MVI56E-MCM module and in the Quantum processor. Thesample application reads and writes 10 words between the Modbus Master andthe Modbus Slave.The following table describes the memory map for data transfer between theMVI56E-MCM module and the Quantum processor.Function MVI56E-MCM Database

Start Address (Master)Quantum Memory StartAddress (Slave)

Word Count

Read 1000 400801 10

Write 0 400401 10



MVI56E-MCM / MCMXT ♦ ControlLogix Platform ProcedurModbus Communication Module Setup Guide


4 Procedures

In This Chapter

Setting Module Jumpers ........................................................................ 24

Installing the Module in the Rack ........... .......... ........... .......... ........... ...... 25

Using ProSoft Configuration Builder Software ....................................... 27

Importing the Sample Add-On Instruction.............................................. 45

Connecting Your PC to the ControlLogix Processor .......... .......... .......... 53

Downloading the Sample Program to the Processor .......... ........... ........ 54

Setting up the Read and Write Database Areas .................................... 55

Rebooting the Module to Transfer New Parameter Values ................... 60Configuring the Quantum Processor as a Modbus Slave .......... ........... . 61

Connecting the MVI56E-MCM Module to the Quantum Processor ....... 62

Verifying Communication....................................................................... 63



Procedures MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


4.1 Setting Module Jumpers

There are three jumpers located at the bottom of the module. The first two jumpers (PRT1 and PRT2) set the serial communication mode: RS-232, RS-422,or RS-485.

The following illustration shows the MVI56E-MCM jumper configuration.

1 The sample application will connect the MVI56E-MCM application port P1 tothe target device using the supplied null-modem cable (RS-232). Set thePRT1 jumper for RS-232.

2 The Setup Jumper acts as "write protection" for the module’s flash memory.In "write protected" mode, the Setup pins are not connected, and themodule’s firmware cannot be overwritten. The module is shipped with theSetup pins jumpered, so that you can update the module’s firmware ifnecessary. As you will not be updating the firmware for this procedure,remove the setup jumper and store it in a safe place (for example, on onlyone of the pins).

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 tothe module.





4.2 Installing the Module in the Rack

If you have not already installed and configured your ControlLogix processor andpower supply, please do so before installing the MVI56E-MCM module. Refer toyour Rockwell Automation product documentation for installation instructions.

Warning: You must follow all safety instructions when installing this or any other electronicdevices. Failure to follow safety procedures could result in damage to hardware or data, or evenserious injury or death to personnel. Refer to the documentation for each device you plan toconnect to verify that suitable safety procedures are in place before installing or servicing thedevice.

After you have checked the placement of the jumpers, insert the MVI56E-MCMinto the ControlLogix chassis. Use the same technique recommended byRockwell Automation to remove and install ControlLogix modules.

You can install or remove ControlLogix system components while chassis poweris applied and the system is operating. However, please note the followingwarning.

Warning: When you insert or remove the module while backplane power is on, an electrical arccan occur. An electrical arc can cause personal injury or property damage by sending anerroneous 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 hazardousenvironment. 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 matingconnector. 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 therack until the module is firmly against the backplane connector.

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

in the locking holes of the rack.4 Make a note of the slot location. You must identify the slot in which the

module is installed in order for the sample program to work correctly. Slotnumbers are identified on the green circuit board (backplane) of theControlLogix rack.

5 Turn power ON.

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

Note: When using the MVI56EMCMXT, you must use the 1756-A5XT or 1756-A7LXT chassis. Inthese chassis, modules are spaced further apart than in standard ControlLogix chassis. Blankspacers are inserted between active modules.





4.3 Using ProSoft Configuration Builder Software

ProSoft Configuration Builder (PCB) provides a quick and easy way to managegateway configuration files customized to meet your application needs. PCB isnot only a powerful solution for new configuration files, but also allows you toimport information from previously installed (known working) configurations tonew projects.

The ProSoft Discovery Service (PDS) is available as a stand-alone application,or as part of ProSoft Configuration Builder. ProSoft Discovery Service shows youall the MVI56E modules available on your local area network.

Note: The MVI56E-MCM module receives its protocol and backplane configuration informationfrom the Ladder Logic. Use ProSoft Configuration Builder to configure the module’s Ethernetsettings.

To install ProSoft Configuration Builder from the CD-ROM

1 Insert the ProSoft Solutions CD-ROM into the CD drive of your PC. Wait forthe startup screen to appear.

2 On the startup screen, click INSTALL P RO S OFT CONFIGURATION BUILDER . Thisaction starts the installation wizard for ProSoft Configuration Builder.

3 Click NEXT on each page of the installation wizard. Click FINISH on the lastpage of the wizard.





4.3.1 Setting Up the Project To begin, start P RO S OFT CONFIGURATION BUILDER (PCB).

If you have used other Windows configuration tools before, you will find thescreen layout familiar. PCB ’s window consists of a tree view on the left, and aninformation pane and a configuration pane on the right side of the window. Whenyou first start PCB , the tree view consists of folders for Default Project andDefault Location , with a Default Module in the Default Location folder. Thefollowing illustration shows the PCB window with a new project.

Your first task is to add the MVI56E-MCM module to the project.

1 Use the mouse to select DEFAULT MODULE in the tree view, and then click theright mouse button to open a shortcut menu.





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-MCM, and then click OK to saveyour settings and return to the ProSoft Configuration Builder window.

4.3.2 Connecting Your PC to the Module's Ethernet Port

ith the module securely mounted, connect one end of the Ethernet cable to theCONFIG (E1) Port, and the other end to an Ethernet hub or switch accessible fromthe same network as your PC. Or, you can connect directly from the EthernetPort on your PC to the CONFIG (E1) Port on the module.





Setting Up a Temporary IP Address

Important: ProSoft Configuration Builder locates MVI56E-MCM modules through UDP broadcastmessages. These messages may be blocked by routers or layer 3 switches. In that case,ProSoft

Discovery Servicewill 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 toallow routing of the UDP broadcast messages.

1 In the tree view in ProSoft Configuration Builder , select the MVI56E-MCM module.

2 Click the right mouse button to open a shortcut menu. On the shortcut menu,choose DIAGNOSTICS .





3 In the Diagnostics window, click the S ET UP CONNECTION button.

4 In the Connection Setup dialog box, click the BROWSE DEVICE (S ) button toopen the ProSoft Discovery Service . Select the module, then right-click andchoose ASSIGN TEMPORARY IP.

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

IP within your subnet, and then click OK.

Important: The temporary IP address is only valid until the next time the module is initialized. For information on how to set the module’s permanent IP address, see Setting Up a Permanent IP

Address (page 33).





6 Close the ProSoft Discovery Service window. Enter the temporary IP in theEthernet address field of the Connection Setup dialog box, then click theTEST CONNECTION button to verify that the module is accessible with thecurrent settings.

7 If the Test Connection is successful, click CONNECT . The Diagnostics menuwill display in the Diagnostics window.





4.3.3 Setting Up a Permanent IP Address

Note: For alternative methods of connecting to the module with your PC, refer to Using CIPconnectto Connect to the Module (page 35) or Using RSWho to Connect to the Module (page 44).

These steps show you how to set a permanent IP address on the module. Themodule’s default IP address is 192.168.0.250.1 Start ProSoft Configuration Builder.2 Select the MVI56E-MCM icon, and then click the [+] symbol to expand the

MVI56E-MCM tree.3 Select ETHERNET CONFIGURATION , and then click the right mouse button to

open a shortcut menu.4 On the shortcut menu, select CONFIGURE .

This action opens the EDIT-WATTCP dialog box. Use this dialog box to enterthe MVI56E-MCM module’s permanent IP Address (MY _ IP), S UBNET MASK(NETMASK ) and DEFAULT GATEWAY (GATEWAY ).





5 Click OK to save the updated Ethernet configuration.6 Next, select the MVI56E-MCM icon, and then click the right mouse button to

open a shortcut menu. On the shortcut menu, choose DOWNLOAD FROM PC TO DEVICE .

This action opens the DOWNLOAD dialog box. Notice that the Ethernetaddress field contains the temporary IP address you assigned previously.ProSoft Configuration Builder will use this temporary IP address to connect tothe module.

Click TEST CONNECTION to verify that the temporary IP address is correct.

7 If the connection succeeds, click DOWNLOAD to transfer the Ethernetconfiguration to the module.

If the Test Connection procedure fails, you will an error message. To correct theerror, follow these steps.1 Click OK to dismiss the error message.





2 On the DOWNLOAD dialog box, click BROWSE DEVICES to open P RO S OFTDISCOVERY S ERVIC e.

3 Select the module, and then click the right mouse button to open a shortcutmenu. On the shortcut menu, choose S ELECT FOR PCB .

4 Close Prosoft Discovery Service.5 Click DOWNLOAD to transfer the Ethernet configuration to the module.

Using CIPconnect ® to Connect to the Module You can use CIPconnect ® to connect a PC to the ProSoft Technology MVI56E-MCM module over Ethernet using Rockwell Automation’s 1756-ENBTEtherNet/IP ® module. This allows you to configure the MVI56E-MCM networksettings and view module diagnostics from a PC. RSLinx is not required whenyou use CIPconnect. All you need are:

The IP addresses and slot numbers of any 1756-ENBT modules in the pathThe slot number of the MVI56E-MCM 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 pathappears in the text box, as shown in the following illustration.

2 Click CIP P ATH EDIT to open the CIPconnect Path Editor dialog box.

The CIPconnect Path Editor allows you to define the path between the PC andthe MVI56E-MCM module. The first connection from the PC is always a 1756-ENBT (Ethernet/IP) module.Each row corresponds to a physical rack in the CIP path.

If the MVI56E-MCM module is located in the same rack as the first 1756-ENBT module, select RACK NO. 1 and configure the associated parameters.





If the MVI56E-MCM is available in a remote rack (accessible throughControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).

Parameter Description

Source Module Source module type. This field is automatically selecteddepending on the destination module of the last rack (1756-

CNB or 1756-ENBT).Source Module IP Address IP address of the source module (only applicable for 1756-

ENBT)

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

Destination Module Select the destination module associated to the source modulein the rack. The connection between the source and destinationmodules is performed through the backplane.

Destination Module Slot Number The slot number where the destination MVI56E module islocated.

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

MVI56E-MCM 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 P ATH to build the path in text format3 Click OK to confirm the configured path.The following examples should provide a better understanding on how to set upthe path for your network.

Example 1: Local Rack Application

For this example, the MVI56E-MCM module is located in the same rack as the1756-ENBT that is connected to the PC.





Rack 1Slot Module Network Address

0 ControlLogix Processor -

1 Any -

2 MVI56E-MCM -3 1756-ENBT IP=192.168.0.100

1 In the Download dialog box, click CIP P ATH EDIT.

2 Configure the path as shown in the following illustration, and clickCONSTRUCT CIP P ATH to build the path in text format.

Click OK to close the CIPconnect Path Editor and return to the Download dialog box.





3 Check the new path in the Download dialog box.

4 Click TEST CONNECTION to verify that the physical path is available. Thefollowing message should be displayed upon success.





5 Click OK to close the Test Connection pop-up and then click DOWNLOAD todownload the configuration files to the module through the path.

Example 2: Remote Rack ApplicationFor this example, the MVI56E-MCM module is located in a remote rackaccessible through ControlNet, as shown in the following illustration.


0 ControlLogix Processor -

1 1756-CNB Node = 1

2 1756-ENBT IP=192.168.0.100

3 Any -






0 Any -

1 Any -

2 Any -

3 Any -

4 Any -

5 1756-CNB Node = 2

6 MVI56E-MCM -

1 In the Download dialog box, click CIP P ATH EDIT.

2 Configure the path as shown in the following illustration and click CONSTRUCT

CIP P ATH to build the path in text format.

Click OK to close the CIPconnect Path Editor and return to the Download dialog box.





3 Check the new path in the Download dialog box.

4 Click TEST CONNECTION to verify that the physical path is available. Thefollowing message should be displayed upon success.





5 Click DOWNLOAD to download the configuration files to the module throughthe path.





Using RSWho to Connect to the Module

You need to have RSLinx installed on your PC to use this feature. You also need an ENBT moduleset up in the rack. For information on setting up the ENBT module, see Using CIPconnect to

Connect to the Module (page 35).

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

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

Type dropdown box.

4 Click RSW HO to display modules on the network. The MVI56E-MCM modulewill automatically be identified on the network.

5 Select the module, and then click OK.

6 In the Download dialog box, click DOWNLOAD .You will need the User Manual and the Add-On Software to complete the steps inthe following sections of this Setup Guide.





4.4 Importing the Sample Add-On Instruction

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

Before You BeginTwo Add-On Instructions are provided for the MVI56E-MCM module. The first isrequired for setting up the module; the second is optional.Copy the files from the ProSoft Solutions CD-ROM , or download them fromwww.prosoft-technology.com. Save them to a convenient location in your PC,such as Desktop or My Documents .

File Name Description

MVI56(E)MCM_AddOn_Rung_v2_2.L5X L5X file containing Add-On Instruction, user defineddata types, controller tags and ladder logic requiredto configure the MVI56E-MCM module

MVI56(E)MCM_Optional_AddOn_Rung_v1_0.L5X

Optional L5X file containing additional Add-OnInstruction with logic for changing Ethernetconfiguration and clock settings.

4.4.1 Creating a New RSLogix 5000 Project 1 Open the FILE menu, and then choose NEW .

2 Select your ControlLogix controller model.3 Select REVISION 16 .4 Enter a name for your controller, such as My_Controller .5 Select your ControlLogix chassis type.





6 Select S LOT 0 for the controller.

4.4.2 Creating the Module

1 Add the MVI56E-MCM module to the project.In the CONTROLLER ORGANIZATION window, select I/O CONFIGURATION andclick the right mouse button to open a shortcut menu. On the shortcut menu,choose NEW MODULE ...





This action opens the S ELECT MODULE dialog box.

2 Select the 1756-M ODULE (GENERIC 1756 MODULE ) from the list and click OK. This action opens the NEW MODULE dialog box.





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

NAME MCM

DESCRIPTION Enter a description for the module. Example: ModbusCommunication Module

COMM FORMAT Select DATA -INT

S LOT Enter the slot number in the rack where the MVI56E-MCMmodule is located

INPUT ASSEMBLY INSTANCE 1

INPUT S IZE 250

OUTPUT ASSEMBLY INSTANCE 2

OUTPUT S IZE 248

CONFIGURATION ASSEMBLY INSTANCE 4

CONFIGURATION S IZE 0

Important: You must select theCOMMFORMATas DATA - INTin the dialog box, otherwise themodule will not communicate over the backplane of the ControlLogix rack.

4 Click OK to continue.5 Edit the Module Properties.

Select the REQUESTED P ACKET INTERVA l value for scanning the I/O on themodule. This value represents the minimum frequency at which the modulewill handle scheduled events. This value should not be set to less than 1millisecond. The default value is 5 milliseconds. Values between 1 and 10milliseconds should work with most applications.

6 Save the module





Click OK to close the dialog box. Notice that the module now appears in theCONTROLLER ORGANIZATION window.

4.4.3 Import the Ladder Rung 1 In the CONTROLLER ORGANIZATION window, expand the TASKS folder and

subfolders until you reach the MAINP ROGRAM folder.2 In the MAINP ROGRAM folder, double-click to open the MAINROUTINE ladder.





3 Select an empty rung in the routine, and then click the right mouse button toopen a shortcut menu. On the shortcut menu, choose IMPORT RUNG…

4 Navigate to the location on your PC where you saved (page 45) the Add-OnInstruction (for example, My Documents or Desktop ). Select theMVI56(E)MCM_A DDON _R UNG _ V2_2.L5X file





This action opens the IMPORT CONFIGURATION dialog box, showing thecontroller tags that will be created.

5 If you are using the module in a different slot (or remote rack), select thecorrect connection input and output variables that define the path to themodule. If your module is located in Slot 1 of the local rack, this step is notrequired.

6 Click OK to confirm the import. RSLogix will indicate that the import is inprogress:





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

The procedure has also imported new User Defined Data Types, ControllerTags, and the Add-On instruction for your project.

7 Save the application and then download the sample ladder logic into theprocessor.





4.5 Connecting Your PC to the ControlLogix Processor

There are several ways to establish communication between your PC and theControlLogix processor. The following steps show how to establishcommunication through the serial interface. It is not mandatory that you use theprocessor's serial interface. You may access the processor through whatevernetwork interface is available on your system. Refer to your Rockwell Automationdocumentation 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 yourcomputer.





4.6 Downloading the Sample Program to the Processor

Note: The key switch on the front of the ControlLogix processor must be in the REM or PROG position.

1 If you are not already online with the processor, open the Communications menu, and then choose DOWNLOAD . RSLogix 5000 will establishcommunication with the processor. You do not have to download through theprocessor's serial port, as shown here. You may download through anyavailable network connection.

2 When communication is established, RSLogix 5000 will open a confirmationdialog box. Click the DOWNLOAD button to transfer the sample program to theprocessor.

3 RSLogix 5000 will compile the program and transfer it to the processor. Thisprocess may take a few minutes.

4 When the download is complete, RSLogix 5000 will open anotherconfirmation 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 tointerpret and correct the error.





4.7 Setting up the Read and Write Database Areas

The next part of this tutorial is to configure the MVI56E-MCM database read andwrite areas to define how data will be transferred between the processor and theMVI56E-MCM module.

Description Start Register Database AddressParameter

Register CountDatabase Parameter Data Controller TagArray Name

Write Area Database area transferredfrom processor to themodule

MCM.CONFIG.ModDef.WriteStartReg

MCM.CONFIG.ModDef.WriteRegCnt

MCM.DATA.WriteData

Read Area Database area transferredfrom module to theprocessor

MCM.CONFIG.ModDef.ReadStartReg

MCM.CONFIG.ModDef.ReadRegCnt

MCM.DATA.ReadData

The Write Data and Read Data areas are configured through the followingcontroller tags.

The settings in the sample application above correspond with the followingmemory diagram.





4.7.1 Configuring Modbus Port 1 (P1)

The sample application uses the following configuration settings for Modbus Port1 (Master) on the MVI56E-MCM module.Parameter Value

Modbus Protocol RTUBaud Rate 19200

Parity None

Data Bits 8

Stop Bits 1

The MODBUS P ORT X configuration parameters are used when the module isconfigured as a Modbus Master device. Port 1 and Port 2 each have their ownset of parameters to configure.





In RSLogix 5000, expand the MCM.CONFIG.M ODDEF controller tag, andnavigate to MCM.CONFIG.P ORT 1. Any parameters not mentioned in this section are not used or not essential whenthe module is configured as a Modbus Master.The following table describes the relevant parameters in theMCM.CONFIG.M ODDEF .P ORT 1 tag array.Parameter Description

Enabled 1 = ENABLE PORT , 0 = disable port

Type 0=MASTER , 1=Slave, 2=Slave: pass-through, 3=Slave: formatted pass-through/data swapped, 4=Slave: form. Pass-through

Protocol 0 = Modbus RTU mode, 1 = Modbus ASCII mode

Baudrate Sets the baud rate for the port. Valid values for this field are 110, 150,300, 600, 1200, 4800, 9600, 19200, 384 or 3840 (for 38,400 baud),576 or 5760 (for 57,600 baud) and 115,1152, or 11520 (for 115,200baud)

Parity 0 = None, 1 = Odd, 2 = Even

DataBits Modbus RTU mode = 8 Modbus ASCII mode = 8 or 7StopBits Valid values are 1 or 2.

UseCts No or YesThis parameter is used to enable or disable hardware handshaking.The default setting is No hardware handshaking, CTS Line not used.Set to No if the connected devices do not need hardwarehandshaking. Set to Yes if the devices connected to the port requirehardware handshaking (most modern devices do not) If you set thisparameter to Yes , be sure to pay attention to the pinout and wiringrequirements to be sure the hardware handshaking signal lines areproperly connected; otherwise communication will fail.

RespTO 0 to 65535 milliseconds response timeout for commandNote: 1000 = 1000 milliseconds (1 second) before it will either reissue

the command, if RETRY COUNT > 0, or, if the RetryCount =0 or hasalready been met, then it will move on to the next command in the list.

RetryCount Number of times to retry a failed request before moving to the nextcommand on the list.

MinCmdDelay 0-65535 millisecondsThe amount of delay in milliseconds to be inserted after receiving aslave response or encountering a response timeout before retrying thecommand or sending the next command on the list. Use thisparameter to slow down overall polling speed and spread outcommands on networks with slaves that require additional gapsbetween messages.

CmdErrPtr Internal DB location to place command error listNote: Set Master Command Errors location. Each command will

reserve one word for the command error code for that command. SeeVerify Communication. CMDERR P TR value should be within the rangeof the READDATA array. See Backplane Configuration.





4.7.2 Configuring the Modbus Master Read Command

The Modbus Read Command reads 10 words of data from the Quantumprocessor (Modbus Slave) and transfers it to the MVI56E-MCM module's internaldatabase. The following table describes the relationship between memoryaddresses in the Modbus Master (MVI56E-MCM) and the Modbus Slave(Quantum processor).MVI56E-MCM Database Address Quantum Memory Address

1000 400801

1001 400802

1002 400803

1003 400804

1004 400805

1005 400806

1006 400807

1007 400808

1008 4008091009 400810

In the sample program, the Modbus Read Command is present, but disabled. Toenable the command, change the 0 (zero) to 1 (one) in theMCM.CONFIG.P ORT 1MASTER CMD[0].E NABLE tag.Be sure the tag MCM.CONFIG.P ORT 1MASTER CMD[0].D EVADDRESS , is set to800, as shown in the following illustration.

Notes: Func 3 represents Modbus Function Code 3, the command code to Read Holding Registers The DevAddress parameter is 0-based so 800 = 400801, 801 = 400802, and so on. The Enable code must be set to 1 to enable the command (0 = disable) The destination Slave node address must be set as 1 (Node parameter)





4.7.3 Configuring the Modbus Master Write Command

The Modbus Write Command will write data from the MVI56E-MCM module tothe Quantum processor as follows.MVI56E-MCM Database Address Quantum Memory Address

0 4004011 400402

2 400403

3 400404

4 400405

5 400406

6 400407

7 400408

8 400409

9 400411

In the sample program, a Modbus Write Command is present, but disabled. Toenable this command, change the 0 (zero) to 1 (one) in theMCM.CONFIG.P ORT 1MASTER CMD[1].E NABLE tag.Be sure the tag, MCM.CONFIG.P ORT 1MASTER CMD[1].N ODE , is set to 400 asshown in the following illustration.

Notes: FUNC16 represents Modbus Function Code 16, the command code to Preset (Write) Holding

Registers The DEVADDRESSparameter is 0-based so 400 = 400401, 401 = 400402, and so on. The ENABLEcode must be set to 1 to enable the command (0 = disable). The destination Slave node address must be set as 1 (NODEparameter)





4.8 Rebooting the Module to Transfer New Parameter Values

The changes you made in the sample program do not take effect until you rebootthe module.1 Locate the MCM.C ONTROL .WARMBOOT controller tag.

2 Enter a value of 1 into this controller tag.

3 Verify that the tag value is automatically reset to zero (0) after a short delay.

The module is now configured with the new parameters, and will beginexchanging data with the processor.





4.9 Configuring the Quantum Processor as a Modbus Slave

The next part of this tutorial is to configure the remote Modbus Slave. For thisexample, the Modbus Slave will be a Quantum processor.The communication port settings for the Modbus Slave must match the Port 1

settings for the Modbus Master. Use the values in the following table to configurethe Quantum processor with Schneider Electric's Concept programming software(version 2.6 or higher).Parameter Value

Node Address 1

Modbus Protocol RTU

Baud Rate 19200

Parity None

Data Bits 8

Stop Bits 1

The following illustration shows the MODBUS P ORT S ETTINGS dialog box inConcept version 2.6.





4.10 Connecting the MVI56E-MCM Module to the Quantum Processor

The final part of this tutorial is to connect the supplied RJ45 to DB9 adaptor andthe supplied null modem cable to Port 1 on the MVI56E-MCM module, andModbus Comm1 on the Quantum processor.

The following illustration shows the serial connection between the MVI56E-MCMmodule and the Quantum processor.





4.11 Verifying Communication

There are several ways to verify that the MVI56E-MCM module is communicatingwith the processor and with the Modbus Master/Slave network. You can:

View Exchanged Data (page 63)

View the Module Status in the RSLogix 5000 Controller Tags (page 66)View the LED Status Indicators

4.11.1 Viewing Exchanged Data

The following illustration describes the source and destination for the dataexchanged by the two Modbus Master Commands.





Checking Write Data The following steps show you how to verify that the WriteData Command isworking.1 In RSLogix, navigate to the processor controller tags

MCM.DATA.W RITEDATA [0] through MCM.DATA.W RITEDATA [9] .2 For words [0] through [9], enter the numbers shown in the following

illustration.

This action sends the values you entered to the Modbus Master Port on theMVI56E-MCM, and then to the Quantum processor, where you will be able tosee the data in Concept.

3 In Concept, navigate to the REFERENCE DATA EDITOR to monitor theprocessor memory addresses from 400401 through 400410. The data shouldmatch the data you sent from RSLogix 5000.





Checking Read Data The following steps show you how to verify that the ReadData Command isworking.1 In Concept, navigate to the REFERENCE DATA EDITOR , and enter the following

values in processor memory addresses from 400801 through 400810 asshown in the following illustration.

This action populates the memory addresses in the Quantum processor thatthe MVI56E-MCM will attempt to retrieve with the ReadData Command.

2 In RSLogix 5000, the values in MCM.DATA.R EAD DATA [0] through [9] shouldmatch the data you entered in Concept.

Tip: Repeat these tests, using different values each time, to verify that the same data appears inthe proper place in each processor.





4.11.2 Checking Module Status through ControlLogix Controller Tags

You can view network status through the ControlLogix controller tags that areupdated through the MVI56E-MCM sample ladder.

To verify that the Modbus Master is communicating with one or more Modbus

Slaves, view the contents of the two ReadData array elements beginning atthe address you used for MCM.CONFIG.P ORT X.CMDERR P TR parameter,minus the value of the MCM.CONFIG.M ODDEF .READS TART REG tag. In thiscase, the CmdErrPtr was set to 1500 and the ReadStartReg to 1000. Thismeans that (1500 – 1000 = 500); so READDATA [500] and READDATA [501] willtell you the individual status of each of the two commands issued by themodule.To verify that the Modbus Slave is communicating with a Modbus Master,view the contents of the MCM.STATUS.P RT XERRS tag for total commandsissued, responses received, errors, and so on.

The following controller tags should continuously increment indicating that Port 1is continuously sending commands and receiving responses: MCM.STATUS.P RT 1E RRS .CMDREQ MCM.STATUS.P RT 1E RRS .CMDRESP MCM.STATUS.P RT 1E RRS .REQUESTS MCM.STATUS.P RT 1E RRS .RESPONSES

If the error counters continuously increment, the LAST ERROR controller tag valueshows the command index which caused the latest failure. You can refer to thecommand error pointer feature to read the command error codes as previouslydiscussed.





4.11.3 Scrolling LED Status Indicators

The scrolling LED display indicates the module’s operating status as follows:

Initialization Messages

Code MessageBoot / DDOK Module is initializing

Ladd Module is waiting for required module configuration data fromladder logic to configure the Modbus ports

Waiting for Processor Connection Module did not connect to processor during initializationSample ladder logic or AOI is not loaded on processorModule is located in a different slot than the oneconfigured in the ladder logic/AOIProcessor is not in RUN or REM RUN mode

Last config: <date> Indicates the last date when the module changed its IPaddress. You can update the module date and time throughthe module’s web page, or with the MVI56E Optional Add-OnInstruction.

Config P1/P2 <Modbus mode><Port type> <Baud> <Parity><Data bits> <Stop Bits> <RSInterface> <ID (Slave)> <Cmds:(Master)>

After power up and every reconfiguration, the module willdisplay the configuration of both ports. The informationconsists of:

Modbus mode: RTU/ASCIIPort type: Master/SlaveBaud: 115200 / 57600 / 38400 / 19200 / 9600/ 4800 / 2400 / 1200 / 600 / 300Parity: None / Even / OddData bits: 7 / 8Stop bits: 1 / 2RS Interface: RS-232 / RS-422 / RS-485ID: Slave Modbus Address

Cmds: Configured Modbus Master Commands

Operation MessagesAfter 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 processorERR: Module is unable to communicate with processor. Forthis scenario, the <Port Status> message above is replacedwith "Processor faulted or is in program mode".

<IP Address> Module IP address

<Port Status> OK: Port is communicating without errorMaster/Slave Communication Errors: port is havingcommunication errors. Refer to PCB diagnostics for furtherinformation about the error.





4.11.4 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 configurationdownload.

GREEN The MVI56E-MCM is working normally.

RED The most common cause is that the module has detected acommunication error during operation of an application port.The following conditions may also cause a RED LED:

The firmware is initializing during startupThe firmware detects an on-board hardware problemduring startupFailure of application port hardware during startupThe module is shutting downThe module is rebooting due to a ColdBoot or WarmBootrequest from the ladder logic or Debug Menu

OK Red orGreen

OFF The module is not receiving adequate power or is not securelyplugged into the rack.

GREEN The module is operating normally.

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

ERR Red OFF The battery voltage is OK and functioning.

ON The battery voltage is low or battery is not present. Allowbattery to charge by keeping module plugged into rack for 24hours. If ERR LED still does not go off, contact ProSoftTechnology, as the battery is not a user-serviceable item.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Building on SuccModbus Communication Module Setup Guide


5 Building on Success

In This Chapter

Frequently Asked Questions ................................................................. 70

Now that you have successfully installed, configured, and verified operation ofthe MVI56E-MCM module, you should have a better understanding of how tomake it work for your specific application. The following resources are availableto help you build on your success.

For more information about the MVI56E-MCM module, including detailedhardware and software configuration, troubleshooting, and applicationinformation, refer to the MVI56E-MCM User Manual. For technical support and warranty information for your MVI56E-MCMmodule, refer to Support, Service, and Warranty in the MVI56E-MCM User Manual .For more information on ProSoft Technology products and services, pleasevisit www.prosoft-technology.com.



Building on Success MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


5.1 Frequently Asked Questions

5.1.1 What are the differences between the MVI56 and the MVI56E modules? What does the "E" stand for?

The "E" stands for E nhanced with E thernet communication capabilities. The newenhancements are: PCB: MVI56E-MCM products now use PCB (ProSoft Configuration Builder)

software; a Windows-based configuration utility providing a new graphic userinterface for module diagnostics with screen navigation, improvinginteroperability with the module.

Seamless Migration: MVI56E products are backward compatible withexisting ladder logic and module configuration files, allowing for a smooth"plug and play" transition when replacing the earlier version MVI56-MCMproduct.

Personality Memory Module: The module incorporates a non-volatilecompact flash (CF) memory card for storing the module’s network

configuration data (or personality). This feature allows quick replacement offaulted modules and restoration of systems by a simple exchange of thePersonality Memory Module, with absolutely no other PC or configurationrequirements.

Ethernet Configuration Port: Allows for remote module connectivity.Replaces serial communication and becomes the primary configuration port,as well as providing a web server interface.

LED Display: The 4-character, scrolling, alphanumeric LED display providesadditional detailed plain English diagnostic and error information, backplanecommunication, and network conditions for the module, .

Discovery Service: Allows PCB configuration software (or separate utility) tofind and display products located on the network using key product attributes

such as name, serial number, and IP address. The user will be able tochange IP address, upload/download, and enter into diagnostics from the list. CIPconnect ® enabled: Allows end-users to connect from remote locations to

local- and remote-chassis-installed MVI56E modules from anywhere on aRockwell Automation ® EtherNet/IP™ or ControlNet™ process network, up tosix remote links away.

5.1.2 Is the MVI56E product a direct replacement to my existing MVI56 product?

Yes

5.1.3 How is the MVI56E-MCM configured? The module is configured with ladder logic controller tags. A warm boot operationis required to transfer all parameters from the processor to the module.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Building on SuccModbus Communication Module Setup Guide


5.1.4 What is ProSoft Configuration Builder (PCB)?

ProSoft Configuration Builder (PCB) provides a quick and easy way to managemodule diagnostics and troubleshooting operations. Built-in module diagnosticsmenus and the serial port data stream analyzer can be accessed using PCBthrough the module's high-speed Ethernet configuration port (E1) or thoughRockwell Automation 1756-ENxT or 1756-CNBx communications interfacesusing CIPconnect ® .

5.1.5 What is ProSoft Discovery Service (PDS)?

ProSoft Discovery Service (PDS) is Windows-based software that connects tothe Ethernet port of the module for the following purposes:

Automatic module discovery on the Ethernet networkSet a temporary IP address for the module for easy commissioningAllow PCB to select the module for monitoring and IP address reconfiguration

The ProSoft Discovery Service software is supplied as a stand-alone utility, as

well as being integrated into PCB.

5.1.6 What is the purpose of the MVI56E-MCM Ethernet Config (E1) Port?

The MVI56E-MCM Ethernet Port (E1) allows a remote PC to set the module’s IPaddress, as well as monitor module operation using ProSoft ConfigurationBuilder (PCB) diagnostics.You can also set the IP address with ladder logic. Refer to the MVI56E-MCM User Manual for more information on this option.

5.1.7 How do I change the module’s IP address?

1 Use ProSoft Discovery Service to temporarily change a MVI56E module'sconfiguration port IP address.

2 Use ProSoft Configuration Builder to edit and download the Ethernetconfiguration to the module.

3 Use the Optional Add-On Instruction (AOI). The AOI file is available on theProSoft Solutions CD-ROM , or can be downloaded fromwww.prosoft-technology.com.

5.1.8 Does the MVI56E-MCM module require processor logic?

Yes, ladder logic is required for data transfer between the MVI56E module andthe ControlLogix ® processor.

For RSLogix™ 5000 version 16 applications (or later), the included Add-OnInstruction encapsulates the entire ladder logic into one single instruction.For RSLogix 5000 version 15 and older, sample ladder logic is available fromthe ProSoft Technology ® website at www.prosoft-technology.com.



Building on Success MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


5.1.9 What is the purpose of the Optional MVI56E-MCM Add-On Instruction?

The Optional Add-On Instruction (AOI) allows the processor to perform thefollowing tasks:

1 Set the MVI56E Ethernet settings2 Read the MVI56E Ethernet settings3 Set MVI56E date/time information4 Read the MVI56E date/time informationItems 1 and 2 can also be performed through ProSoft Configuration Builder(PCB) for permanent IP address changes or through ProSoft Discovery Servicefor temporary changes. Items 3 and 4 can also be performed through themodule's built-in web page.The Optional AOI is needed only for specific applications where Ethernet orCIPconnect access from a programmer's personal computer (PC) to the moduleis not possible.

5.1.10 How do I monitor MVI56E-MCM operation? Module operation can be monitored either through the processor controller tagsor through the ProSoft Configuration Builder diagnostic window. Available statusinformation includes number of messages sent, number of messages received,number of errors, and error codes.

5.1.11 Are there any other ways to monitor module diagnostics besides being connected to the module’s network (subnet)?

PCB can monitor the module via ControlLogix backplanes and process networksusing CIPconnect. The PC running PCB can use its Ethernet port to connect to

any 1756-ENxT EtherNet/IP™ interface module which is on the same Ethernetsubnet. Through this connection, PCB can use CIPconnect to route through theControlLogix backplane to other 1756-ENxT or 1756-CNBx modules, for up tofive more route links, to reach an MVI56E module in a chassis connected onEtherNet/IP or ControlNet™ process networks.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Glossary of TermModbus Communication Module Setup Guide


Glossary of Terms

AASCIIAmerican Standard Code for Information Interchange. A communication mode inwhich each eight-bit byte in a message contains one ASCII character code.ASCII characters (or hexadecimal characters) are sometimes used as a key toencrypt data and ensure its secure transmission.

B

Baud RateThe speed of communication between devices on the network. All devices mustcommunicate at the same rate.

C

ClientA client is a software program, or the device on which that program runs, thatmakes requests for information from a software program, or the device on whichthat program runs, in a client-server relationship.A Client on an Ethernet network is equivalent to a Master on a serial network.

D

DCEData communications equipment. A modem, for example.

Default GatewayThe IP address of a network router where data is sent if the destination IPaddress is outside the local subnet. The gateway is the device that routes thetraffic from the local area network to other networks such as the Internet.

DTEData terminal equipment. A computer or terminal, for example.

E

ESD

Electrostatic Discharge. Can cause internal circuit damage to the coprocessor.EthernetA set of network cabling and network access (CSMA/CD) protocol standards forbus topology computer networks invented by Xerox but now controlled by the802.3 subcommittee of the IEEE.



Glossary of Terms MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


F

FirmwareSoftware for embedded computers.

Full-DuplexA communications circuit or system designed to simultaneously transmit andreceive two different streams of data. Telephones are an example of a full-duplexcommunication system. Both parties on a telephone conversation can talk andlisten at the same time. If both talk at the same time, their two signals are notcorrupted.

H

Half-DuplexA communications circuit or system designed to transmit and receive data, butnot both simultaneously. CB or walkie-talkie radios are an example of a half-duplex communication system. Either parties on a radio conversation may talk or

listen; but both cannot talk at the same time without corrupting each other'ssignal. If one operator is "talking", the other must be "listening" to havesuccessful communication.

I

IP AddressA 32-bit identification number for each node on an Internet Protocol network.These addresses are represented as four sets of 8-bit numbers (numbers from 0to 255), separated by periods ("dots").Networks using the TCP/IP Protocol route messages based on the IP address ofthe destination. Each number can be 0 to 255. For example, 192.168.0.100 could

be an IP address. Each node on the network must have a unique IP address.L

LEDLight-emitting diode.

M

MAC IDA hexadecimal number that uniquely identifies an Ethernet device.

Master A Master is a device that makes requests for information from a softwareprogram, or the device on which that program runs, in a Master-Slaverelationship.A Client on an Ethernet network is equivalent to a Master on a Serial network.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform Glossary of TermModbus Communication Module Setup Guide


N

NetworkA series of stations or nodes connected by some type of communication medium.A network may consist of a single link or multiple links.

NodeAn address or software location on the network.

P

Peer-to-Peer A network relationship between devices where each device can send commandsas a master or client, and respond to commands as a slave or server.

Power SupplyDevice that supplies electrical power to the I/O chassis containing the processor,coprocessor, or other modules.

ProtocolThe language or packaging of information that is transmitted between nodes on anetwork.

R

RS-232Recommended Standard 232; the standard for serial binary signals betweenDTE and DCE devices.

S

Serial Data/Serial Data TransmissionData that is transferred one bit at a time. Serial data transmission involveschanging a carrier signal line between two possible states to indicate a binary 0or binary 1 value. Successive data bits are rapidly transmitted one after the otherwith a fixed time allowed for each bit. Data bits are usually grouped into"packets", which contain a specific amount of data bits, along with extra bitsincluded to provide error-checking capability.

Server A Server is a software program, or the device on which that program runs, thatprovides a specific kind of service to a Client software program, or the device onwhich that program runs, on an Ethernet network.

A Server on an Ethernet network is equivalent to a Slave on a Serial network.



Glossary of Terms MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module


SimplexA communications circuit or system designed to either transmit data or receivedata, but not both. Broadcast television is an example of simplex communicationsystem. A television station sends a TV signal but cannot receive responsesback from the television sets to which it is transmitting. The TV sets can receivethe signal from the TV station but cannot transmit back to the station.

SlaveA Slave is a software program, or the device on which that program runs, whichprovides a specific kind of service to a Master software program, or the device onwhich that program runs, on a serial network.A Slave on a Serial network is equivalent to a Server on an Ethernet network.

Subnet MaskA mask used to determine what subnet an IP address belongs to. An IP addresshas two components: the network address, and the host (node or device)address. For example, consider the IP address 150.215.017.009. Assuming thisis part of a Class B network (with a subnet mask of 255.255.0.0), the first twonumbers (150.215) represent the Class B network address, and the second twonumbers (017.009) identify a particular host on this network.



MVI56E-MCM / MCMXT ♦ ControlLogix Platform IndModbus Communication Module Setup Guide


Index

A About the MODBUS Protocol • 18Architecture • 20Are there any other ways to monitor module

diagnostics besides being connected to themodule’s network (subnet)? • 72

ASCII • 73

B

Battery Life Advisory • 4Baud Rate • 73Before You Begin • 13Building on Success • 69

C Checking Module Status through ControlLogix

Controller Tags • 63, 66Checking Read Data • 65Checking Write Data • 64Client • 73Configuring Modbus Port 1 (P1) • 19, 56Configuring the Modbus Master Read Command • 19,

58Configuring the Modbus Master Write Command • 19,

59Configuring the Quantum Processor as a Modbus

Slave • 9, 19, 61Connecting the MVI56E-MCM Module to the Quantum

Processor • 62Connecting Your PC to the ControlLogix Processor •19, 53

Connecting Your PC to the Module's Ethernet Port • 29Creating a New RSLogix 5000 Project • 19, 45Creating the Module • 46

D

DCE • 73Default Gateway • 73Does the MVI56E-MCM module require processor

logic? • 71Downloading the Sample Program to the Processor •

9, 19, 54DTE • 73

E

ESD • 73Ethernet • 73Example 1

Local Rack Application • 37Example 2

Remote Rack Application • 40

F

Firmware • 74Frequently Asked Questions • 70Full-Duplex • 74

G

General Overview • 19

H

Half-Duplex • 74How do I change the module’s IP address? • 71How do I monitor MVI56E-MCM operation? • 72How is the MVI56E-MCM configured? • 70How to Contact Us • 2

I

Import the Ladder Rung • 49Important Safety Information - MVI56E-MCM/XT • 3Importing the Sample Add-On Instruction • 45, 50

Installing the Module in the Rack • 25IP Address • 74Is the MVI56E product a direct replacement to my

existing MVI56 product? • 70

L

Learning Objectives • 9LED • 74

M

MAC ID • 74Master • 74Memory Map • 21

N

Network • 75Node • 75Non-Scrolling LED Status Indicators • 68

P

Peer-to-Peer • 75Power Supply • 75Prerequisites • 11Procedures • 23ProSoft Technology Documentation • 10ProSoft Technology® Product Documentation • 2Protocol • 75

R

Rebooting the Module to Transfer New Parameter Values • 19, 60

Required Items • 15Required Steps • 19RS-232 • 75



Index MVI56E-MCM / MCMXT ♦ ControlLogix PlatformSetup Guide Modbus Communication Module

S

Sample Files • 16Scope • 7Scrolling LED Status Indicators • 67Serial Data/Serial Data Transmission • 75Server • 75Setting Module Jumpers • 24Setting Up a Permanent IP Address • 31, 33Setting Up a Temporary IP Address • 30Setting Up the Project • 28Setting up the Read and Write Database Areas • 55Simplex • 76Slave • 76Subnet Mask • 76System Requirements • 14

T

The Sample Application • 9, 17

U

Using CIPconnect® to Connect to the Module • 33, 35,44

Using ProSoft Configuration Builder Software • 27Using RSWho to Connect to the Module • 33, 44

V

Verifying Communication • 9, 19, 63Viewing Exchanged Data • 63

W

What are the differences between the MVI56 and theMVI56E modules? What does the • 70

What is ProSoft Configuration Builder (PCB)? • 71What is ProSoft Discovery Service (PDS)? • 71What is the purpose of the MVI56E-MCM Ethernet

Config (E1) Port? • 71What is the purpose of the Optional MVI56E-MCM

Add-On Instruction? • 72What's New? • 8

Y

Your Feedback Please • 2