MVI56E-MCM / MCMXT ControlLogix Platform Modbus Communication Module

Transcription

1 MVI56E-MCM / MCMXT ControlLogix Platform SETUP GUIDE

2 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 (661) (661) (Fax) Copyright 2011 ProSoft Technology, Inc., all rights reserved. MVI56E-MCM / MCMXT 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:

3 Important Safety Information - MVI56E-MCM/XT 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. C Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is known 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 jurisdiction A B C Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or wiring modules. Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is known to be non-hazardous. 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. DO NOT OPEN WHEN ENERGIZED. Markings Agency Approvals and Certifications Agency RoHS Applicable Standards ATEX EN July 2006 EN October 2005 CSA CE IEC61010 EMC-EN :2006 EN :2007 CSA CB Safety CA/10533/CSA IEC Ed. 2 CB ( ) culus GOST-R EN61010 Lloyds Lloyds Register Test Specification Number 1, E ME06

4 Label Markings <Ex> II 3 G Ex na T5 0 C <= Ta <= 60 C -25 C <= Ta <= 70 C (XT models only) II Equipment intended for above ground use (not for use in mines). 3 Category 3 equipment, investigated for normal operation only. G Equipment protected against explosive gasses. <culus> E Class I, DIV 2, groups A,B,C,D T5 for all models 0 C to +60 C -25 C to +70 C (XT models only) 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: The battery is not user-replaceable or serviceable.

5 Contents Contents Your Feedback Please... 2 How to Contact Us... 2 ProSoft Technology Product Documentation... 2 Important Safety Information - MVI56E-MCM/XT... 3 Battery Life Advisory Scope What's New? Learning Objectives ProSoft Technology Documentation Prerequisites Before You Begin System Requirements Required Items Sample Files The Sample Application About the MODBUS Protocol General Overview Required Steps Architecture Memory Map Setting Module Jumpers Installing the Module in the Rack Using ProSoft Configuration Builder Software Setting Up the Project Connecting Your PC to the Module's Ethernet Port Setting Up a Permanent IP Address Importing the Sample Add-On Instruction Creating a New RSLogix 5000 Project Creating the Module Import the Ladder Rung Connecting Your PC to the ControlLogix Processor Downloading the Sample Program to the Processor Setting up the Read and Write Database Areas Configuring Modbus Port 1 (P1) Configuring the Modbus Master Read Command Configuring the Modbus Master Write Command Rebooting the Module to Transfer New Parameter Values Configuring the Quantum Processor as a Modbus Slave Connecting the MVI56E-MCM Module to the Quantum Processor ProSoft Technology, Inc. Page 5 of 78

6 Contents 4.11 Verifying Communication Viewing Exchanged Data Checking Module Status through ControlLogix Controller Tags Scrolling LED Status Indicators Non-Scrolling LED Status Indicators Building on Success Frequently Asked Questions What are the differences between the MVI56 and the MVI56E modules? What does the "E" stand for? Is the MVI56E product a direct replacement to my existing MVI56 product? How is the MVI56E-MCM configured? What is ProSoft Configuration Builder (PCB)? What is ProSoft Discovery Service (PDS)? What is the purpose of the MVI56E-MCM Ethernet Config (E1) Port? How do I change the module s IP address? Does the MVI56E-MCM module require processor logic? What is the purpose of the Optional MVI56E-MCM Add-On Instruction? How do I monitor MVI56E-MCM operation? Are there any other ways to monitor module diagnostics besides being connected to the module s network (subnet)? Glossary of Terms 73 Index 77 Page 6 of 78 ProSoft Technology, Inc.

7 Scope 1 Scope In This Chapter What's New?... 8 Learning Objectives... 9 ProSoft Technology Documentation Prerequisites 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-MCM / MCMXT. ProSoft Technology, Inc. Page 7 of 78

8 Scope 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 to benefit from an array of new features designed to improve interoperability and enhance ease of use. ProSoft Configuration Builder (PCB): Microsoft Windows -based utility software for diagnostics. Connect through the module's Ethernet port or use CIPconnect to access troubleshooting features and functions. ProSoft Discovery Service (PDS): New Windows-based utility software to find and display a list of MVI56E modules on the network and to temporarily change a module's IP address to be able to connect with a module's web page. CIPconnect-enabled: Allows PC-to-module diagnostics from the Ethernet network through a ControlLogix 1756-ENxT EtherNet/IP module. Personality Card: An industrial-grade compact flash memory card storing the 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 and network communication status. XT series for Extreme Environments: The MVI56E-MCMXT is part of the new XT series, designed to work at extreme temperatures and in harsh or caustic environments. XT series modules operate over a wider temperature range than the standard MVI56E series. The XT series also comes with conformal coating to protect module components from corrosive environmental elements. Page 8 of 78 ProSoft Technology, Inc.

9 Scope 1.2 Learning Objectives When you have completed all the steps in this, you will have learned how to Use the sample application (page 17) Install the MVI56E-MCM setup and diagnostic software Install the MVI56E-MCM module Import the Add-On Instruction to the processor (page 54) Configure the Modbus Master using the sample Add-On Instruction Configure the Modbus Slave (page 61) Verify the MVI56E-MCM module communication status (page 63) ProSoft Technology, Inc. Page 9 of 78

10 Scope 1.3 ProSoft Technology Documentation ProSoft Technology provides the following documentation (manuals) with your MVI56E-MCM. Documentation, tools, and product support Web Site Support: Visit the ProSoft Technology web site at to download additional documentation, tools, and application information. Technical Support: Send your support questions to Telephone Support: Please call ProSoft Technology Technical Support at: (Country Code 1+) Support is available 24 hours a day, 7 days a week. ProSoft Technology telephone support is free and unlimited. Page 10 of 78 ProSoft Technology, Inc.

11 Scope 1.4 Prerequisites To get the most benefit from this, you should have the following skills: Rockwell Automation RSLogix 5000 software: launch the program, configure, and transfer the Add-On Instruction (or ladder logic) Sample Application 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 the documentation for the devices connected to the network Ethernet networking: connect the MVI56E-MCM module to an Ethernet network using a valid IP address and subnet mask Hardware installation and wiring: install the module and safely connect Modbus Master/Slave and ControlLogix devices to a power source and to the MVI56E-MCM module s serial ports ProSoft Technology, Inc. Page 11 of 78

12 Scope Page 12 of 78 ProSoft Technology, Inc.

13 Before You Begin 2 Before You Begin In This Chapter System Requirements Required Items Sample Files ProSoft Technology, Inc. Page 13 of 78

14 Before You Begin 2.1 System Requirements The MVI56E-MCM 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-MCM 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 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 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 recommended) CD-ROM drive Note: The Hardware and Operating System requirements in this list are the minimum recommended to install and run software provided by ProSoft Technology. Other third party applications may have different minimum requirements. Refer to the documentation for any third party applications for system requirements. Note: You can install the module in a local or remote rack. For remote rack installation, the module requires EtherNet/IP or ControlNet communication with the processor. Page 14 of 78 ProSoft Technology, Inc.

15 Before You Begin 2.2 Required Items This uses a sample application that shows you how to establish communication between the MVI56E-MCM module (Master Port) and a Modbus Slave device. The sample application requires the following equipment. Item MVI56E-MCM Description 1756-L63 ControlLogix processor 1756-A7/B 1756-PA72/B CPU434 12A CPS XBP01000 Ethernet cable Serial cable ControlLogix rack ControlLogix rack power supply Quantum processor (Modbus device) Quantum power supply Quantum rack Ethernet cable to connect MVI56E-MCM module to Ethernet network for diagnostics (supplied with the module) Serial cable to connect MVI56E-MCM module to Modbus serial network ProSoft Technology, Inc. Page 15 of 78

16 Before You Begin 2.3 Sample Files Note: This 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-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 file contains all elements required for the MVI56E-MCM module to function. User-defined Data Types (UDTs) Add-On Instruction (AOI) Ladder rung with AOI Controller tags Item MVI56(E)MCM_AddOn_Rung_v2_2.L5X Description Sample rung import file containing Add-On Instruction Copy the file from the ProSoft Solutions CD-ROM, or download them from Save it to a convenient location in your PC, such as Desktop or My Documents. Page 16 of 78 ProSoft Technology, Inc.

17 The Sample Application 3 The Sample Application In This Chapter About the MODBUS Protocol General Overview Architecture Memory Map ProSoft Technology, Inc. Page 17 of 78

18 The Sample Application 3.1 About the MODBUS Protocol MODBUS is a widely-used protocol originally developed by Modicon in 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 Master and Slave devices on a network. Later enhancements to the protocol allow communication over other types of networks. MODBUS is a Master/Slave protocol. The Master establishes a connection to the remote Slave. When the connection is established, the Master sends the MODBUS commands to the Slave. The MVI56E-MCM module can work as a Master and as a Slave. The MVI56E-MCM module also works as an input/output module between itself and the Rockwell Automation backplane and processor. The module uses an internal database to pass data and commands between the processor and Master and Slave devices on MODBUS networks. Page 18 of 78 ProSoft Technology, Inc.

19 The Sample Application 3.2 General Overview This shows you how to configure the MVI56E-MCM module and establish communication with a Modbus device (a Quantum processor, for this example). 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 Comm 1). The MVI56E-MCM will be configured to send two Master commands to the Modbus Slave 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, you will have enough information to set up your own application Required Steps This 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 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 Areas a 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) ProSoft Technology, Inc. Page 19 of 78

20 The Sample Application 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-MCM module acting as a Modbus Master A Quantum processor acting as a Modbus Slave An Ethernet network connecting the PC with the MVI56E-MCM, either directly or through an Ethernet hub or switch. An RS-232 serial cable connecting the MVI56E-MCM Modbus Master Port 1 to 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. Page 20 of 78 ProSoft Technology, Inc.

21 The Sample Application 3.4 Memory Map The memory map consists of the starting addresses for Read Data and Write Data areas in the MVI56E-MCM module and in the Quantum processor. The sample application reads and writes 10 words between the Modbus Master and the Modbus Slave. The following table describes the memory map for data transfer between the MVI56E-MCM module and the Quantum processor. Function MVI56E-MCM Database Start Address (Master) Quantum Memory Start Address (Slave) Read Write Word Count ProSoft Technology, Inc. Page 21 of 78

22 The Sample Application Page 22 of 78 ProSoft Technology, Inc.

23 4 In This Chapter Setting Module Jumpers Installing the Module in the Rack Using ProSoft Configuration Builder Software Importing the Sample Add-On Instruction Connecting Your PC to the ControlLogix Processor Downloading the Sample Program to the Processor Setting up the Read and Write Database Areas Rebooting the Module to Transfer New Parameter Values Configuring the Quantum Processor as a Modbus Slave Connecting the MVI56E-MCM Module to the Quantum Processor Verifying Communication ProSoft Technology, Inc. Page 23 of 78

24 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 to the target device using the supplied null-modem cable (RS-232). Set the PRT1 jumper for RS The Setup Jumper acts as "write protection" for the module s flash memory. In "write protected" mode, the Setup pins are not connected, and the module s firmware cannot be overwritten. The module is shipped with the Setup pins jumpered, so that you can update the module s firmware if necessary. 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 only one 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 to the module. Page 24 of 78 ProSoft Technology, Inc.

25 4.2 Installing the Module in the Rack If you have not already installed and configured your ControlLogix processor and power supply, please do so before installing the MVI56E-MCM module. Refer to your Rockwell Automation product documentation for installation instructions. Warning: You must follow all safety instructions when installing this or any other electronic devices. Failure to follow safety procedures could result in damage to hardware or data, or even serious injury or death to personnel. Refer to the documentation for each device you plan to connect to verify that suitable safety procedures are in place before installing or servicing the device. After you have checked the placement of the jumpers, insert the MVI56E-MCM into the ControlLogix chassis. Use the same technique recommended by Rockwell Automation to remove and install ControlLogix modules. You can install or remove ControlLogix system components while chassis power is applied and the system is operating. However, please note the following warning. Warning: When you insert or remove the module while backplane power is on, an electrical arc can occur. An electrical arc can cause personal injury or property damage by sending an erroneous signal to your system s actuators. This can cause unintended machine motion or loss of process control. Electrical arcs may also cause an explosion when they happen in a hazardous environment. Verify that power is removed or the area is non-hazardous before proceeding. Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector. Worn contacts may create electrical resistance that can affect module operation. ProSoft Technology, Inc. Page 25 of 78

26 1 Align the module with the top and bottom guides, and then slide it into the rack until the module is firmly against the backplane connector. 2 With a firm, steady push, snap the module into place. 3 Check that the holding clips on the top and bottom of the module are securely in the locking holes of the rack. 4 Make a note of the slot location. You must identify the slot in which the module is installed in order for the sample program to work correctly. Slot numbers are identified on the green circuit board (backplane) of the ControlLogix rack. 5 Turn power ON. Note: If you insert the module improperly, the system may stop working or may behave unpredictably. Note: When using the MVI56EMCMXT, you must use the 1756-A5XT or 1756-A7LXT chassis. In these chassis, modules are spaced further apart than in standard ControlLogix chassis. Blank spacers are inserted between active modules. Page 26 of 78 ProSoft Technology, Inc.

27 4.3 Using ProSoft Configuration Builder Software ProSoft Configuration Builder (PCB) provides a quick and easy way to manage gateway configuration files customized to meet your application needs. PCB is not only a powerful solution for new configuration files, but also allows you to import information from previously installed (known working) configurations to new projects. The ProSoft Discovery Service (PDS) is available as a stand-alone application, or as part of ProSoft Configuration Builder. ProSoft Discovery Service shows you all the MVI56E modules available on your local area network. Note: The MVI56E-MCM module receives its protocol and backplane configuration information from the Ladder Logic. Use ProSoft Configuration Builder to configure the module s Ethernet settings. To install ProSoft Configuration Builder from the CD-ROM 1 Insert the ProSoft Solutions CD-ROM into the CD drive of your PC. Wait for the startup screen to appear. 2 On the startup screen, click INSTALL PROSOFT CONFIGURATION BUILDER. This action starts the installation wizard for ProSoft Configuration Builder. 3 Click NEXT on each page of the installation wizard. Click FINISH on the last page of the wizard. ProSoft Technology, Inc. Page 27 of 78

28 4.3.1 Setting Up the Project To begin, start PROSOFT CONFIGURATION BUILDER (PCB). If you have used other Windows configuration tools before, you will find the screen layout familiar. PCB s window consists of a tree view on the left, and an information pane and a configuration pane on the right side of the window. When you first start PCB, the tree view consists of folders for Default Project and Default Location, with a Default Module in the Default Location folder. The following illustration shows the PCB window with a new project. Your first task is to add the MVI56E-MCM module to the project. 1 Use the mouse to select DEFAULT MODULE in the tree view, and then click the right mouse button to open a shortcut menu. Page 28 of 78 ProSoft Technology, Inc.

29 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 save your settings and return to the ProSoft Configuration Builder window Connecting Your PC to the Module's Ethernet Port ith the module securely mounted, connect one end of the Ethernet cable to the CONFIG (E1) Port, and the other end to an Ethernet hub or switch accessible from the same network as your PC. Or, you can connect directly from the Ethernet Port on your PC to the CONFIG (E1) Port on the module. ProSoft Technology, Inc. Page 29 of 78

30 Setting Up a Temporary IP Address Important: ProSoft Configuration Builder locates MVI56E-MCM modules through UDP broadcast messages. These messages may be blocked by routers or layer 3 switches. In that case, ProSoft Discovery Service will be unable to locate the modules. To use ProSoft Configuration Builder, arrange the Ethernet connection so that there is no router/ layer 3 switch between the computer and the module OR reconfigure the router/ layer 3 switch to allow routing of the UDP broadcast messages. 1 In the tree view in ProSoft Configuration Builder, select the MVI56E-MCM module. 2 Click the right mouse button to open a shortcut menu. On the shortcut menu, choose DIAGNOSTICS. Page 30 of 78 ProSoft Technology, Inc.

31 3 In the Diagnostics window, click the SET UP CONNECTION button. 4 In the Connection Setup dialog box, click the BROWSE DEVICE(S) button to open the ProSoft Discovery Service. Select the module, then right-click and choose ASSIGN TEMPORARY IP. 5 The module s default IP address is usually 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). ProSoft Technology, Inc. Page 31 of 78

32 6 Close the ProSoft Discovery Service window. Enter the temporary IP in the Ethernet address field of the Connection Setup dialog box, then click the TEST CONNECTION button to verify that the module is accessible with the current settings. 7 If the Test Connection is successful, click CONNECT. The Diagnostics menu will display in the Diagnostics window. Page 32 of 78 ProSoft Technology, Inc.

33 4.3.3 Setting Up a Permanent IP Address Note: For alternative methods of connecting to the module with your PC, refer to Using CIPconnect to 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. The module s default IP address is 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 enter the MVI56E-MCM module s permanent IP Address (MY_IP), SUBNET MASK (NETMASK) and DEFAULT GATEWAY (GATEWAY). ProSoft Technology, Inc. Page 33 of 78

34 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 Ethernet address field contains the temporary IP address you assigned previously. ProSoft Configuration Builder will use this temporary IP address to connect to the module. Click TEST CONNECTION to verify that the temporary IP address is correct. 7 If the connection succeeds, click DOWNLOAD to transfer the Ethernet configuration to the module. If the Test Connection procedure fails, you will an error message. To correct the error, follow these steps. 1 Click OK to dismiss the error message. Page 34 of 78 ProSoft Technology, Inc.

35 2 On the DOWNLOAD dialog box, click BROWSE DEVICES to open PROSOFT DISCOVERY SERVICe. 3 Select the module, and then click the right mouse button to open a shortcut menu. On the shortcut menu, choose SELECT FOR PCB. 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-ENBT EtherNet/IP module. This allows you to configure the MVI56E-MCM network settings and view module diagnostics from a PC. RSLinx is not required when you use CIPconnect. All you need are: The IP addresses and slot numbers of any 1756-ENBT modules in the path The slot number of the MVI56E-MCM in the destination ControlLogix chassis (the last ENBTx and chassis in the path). To use CIPconnect, follow these steps. ProSoft Technology, Inc. Page 35 of 78

36 1 In the Select Port dropdown list, choose 1756-ENBT. The default path appears in the text box, as shown in the following illustration. 2 Click CIP PATH EDIT to open the CIPconnect Path Editor dialog box. The CIPconnect Path Editor allows you to define the path between the PC and the MVI56E-MCM module. The first connection from the PC is always a 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 ENBT module, select RACK NO. 1 and configure the associated parameters. Page 36 of 78 ProSoft Technology, Inc.

37 If the MVI56E-MCM is available in a remote rack (accessible through ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button). Parameter Source Module Description Source module type. This field is automatically selected depending on the destination module of the last rack (1756- CNB or 1756-ENBT). Source Module IP Address IP address of the source module (only applicable for ENBT) Source Module Node Address Node address of the source module (only applicable for CNB) Destination Module Destination Module Slot Number Select the destination module associated to the source module in the rack. The connection between the source and destination modules is performed through the backplane. The slot number where the destination MVI56E module is located. To use the CIPconnect Path Editor, follow these steps. 1 Configure the path between the 1756-ENBT connected to your PC and the MVI56E-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 PATH to build the path in text format 3 Click OK to confirm the configured path. The following examples should provide a better understanding on how to set up the path for your network. Example 1: Local Rack Application For this example, the MVI56E-MCM module is located in the same rack as the 1756-ENBT that is connected to the PC. ProSoft Technology, Inc. Page 37 of 78

38 Rack 1 Slot Module Network Address 0 ControlLogix Processor - 1 Any - 2 MVI56E-MCM ENBT IP= In the Download dialog box, click CIP PATH EDIT. 2 Configure the path as shown in the following illustration, and click CONSTRUCT CIP PATH to build the path in text format. Click OK to close the CIPconnect Path Editor and return to the Download dialog box. Page 38 of 78 ProSoft Technology, Inc.

39 3 Check the new path in the Download dialog box. 4 Click TEST CONNECTION to verify that the physical path is available. The following message should be displayed upon success. ProSoft Technology, Inc. Page 39 of 78

40 5 Click OK to close the Test Connection pop-up and then click DOWNLOAD to download the configuration files to the module through the path. Example 2: Remote Rack Application For this example, the MVI56E-MCM module is located in a remote rack accessible through ControlNet, as shown in the following illustration. Rack 1 Slot Module Network Address 0 ControlLogix Processor CNB Node = ENBT IP= Any - Page 40 of 78 ProSoft Technology, Inc.

41 Rack 2 Slot Module Network Address 0 Any - 1 Any - 2 Any - 3 Any - 4 Any CNB Node = 2 6 MVI56E-MCM - 1 In the Download dialog box, click CIP PATH EDIT. 2 Configure the path as shown in the following illustration and click CONSTRUCT CIP PATH to build the path in text format. Click OK to close the CIPconnect Path Editor and return to the Download dialog box. ProSoft Technology, Inc. Page 41 of 78

42 3 Check the new path in the Download dialog box. 4 Click TEST CONNECTION to verify that the physical path is available. The following message should be displayed upon success. Page 42 of 78 ProSoft Technology, Inc.

43 5 Click DOWNLOAD to download the configuration files to the module through the path. ProSoft Technology, Inc. Page 43 of 78

44 Using RSWho to Connect to the Module You need to have RSLinx installed on your PC to use this feature. You also need an ENBT module set up in the rack. For information on setting up the ENBT module, see Using CIPconnect to Connect to the Module (page 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 RSWHO to display modules on the network. The MVI56E-MCM module will 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 in the following sections of this. Page 44 of 78 ProSoft Technology, Inc.

45 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 you have an earlier version, please see Using the Sample Program. Before You Begin Two Add-On Instructions are provided for the MVI56E-MCM module. The first is required for setting up the module; the second is optional. Copy the files from the ProSoft Solutions CD-ROM, or download them from Save them to a convenient location in your PC, such as Desktop or My Documents. File Name MVI56(E)MCM_AddOn_Rung_v2_2.L5X MVI56(E)MCM_Optional_AddOn_Rung_v1_0.L5X Description L5X file containing Add-On Instruction, user defined data types, controller tags and ladder logic required to configure the MVI56E-MCM module Optional L5X file containing additional Add-On Instruction with logic for changing Ethernet configuration and clock settings Creating a New RSLogix 5000 Project 1 Open the FILE menu, and then choose NEW. 2 Select your ControlLogix controller model. 3 Select REVISION Enter a name for your controller, such as My_Controller. 5 Select your ControlLogix chassis type. ProSoft Technology, Inc. Page 45 of 78

46 6 Select SLOT 0 for the controller Creating the Module 1 Add the MVI56E-MCM module to the project. In the CONTROLLER ORGANIZATION window, select I/O CONFIGURATION and click the right mouse button to open a shortcut menu. On the shortcut menu, choose NEW MODULE... Page 46 of 78 ProSoft Technology, Inc.

47 This action opens the SELECT MODULE dialog box. 2 Select the 1756-MODULE (GENERIC 1756 MODULE) from the list and click OK. This action opens the NEW MODULE dialog box. ProSoft Technology, Inc. Page 47 of 78

48 3 In the NEW MODULE dialog box, enter the following values. Parameter NAME DESCRIPTION COMM FORMAT SLOT INPUT ASSEMBLY INSTANCE 1 Value MCM INPUT SIZE 250 OUTPUT ASSEMBLY INSTANCE 2 OUTPUT SIZE 248 CONFIGURATION ASSEMBLY INSTANCE 4 CONFIGURATION SIZE 0 Enter a description for the module. Example: Modbus Communication Module Select DATA-INT Enter the slot number in the rack where the MVI56E-MCM module is located Important: You must select the COMM FORMAT as DATA - INT in the dialog box, otherwise the module will not communicate over the backplane of the ControlLogix rack. 4 Click OK to continue. 5 Edit the Module Properties. Select the REQUESTED PACKET INTERVAl value for scanning the I/O on the module. This value represents the minimum frequency at which the module will handle scheduled events. This value should not be set to less than 1 millisecond. The default value is 5 milliseconds. Values between 1 and 10 milliseconds should work with most applications. 6 Save the module Page 48 of 78 ProSoft Technology, Inc.

49 Click OK to close the dialog box. Notice that the module now appears in the CONTROLLER ORGANIZATION window Import the Ladder Rung 1 In the CONTROLLER ORGANIZATION window, expand the TASKS folder and subfolders until you reach the MAINPROGRAM folder. 2 In the MAINPROGRAM folder, double-click to open the MAINROUTINE ladder. ProSoft Technology, Inc. Page 49 of 78

50 3 Select an empty rung in the routine, and then click the right mouse button to open a shortcut menu. On the shortcut menu, choose IMPORT RUNG 4 Navigate to the location on your PC where you saved (page 45) the Add-On Instruction (for example, My Documents or Desktop). Select the MVI56(E)MCM_ADDON_RUNG_V2_2.L5X file Page 50 of 78 ProSoft Technology, Inc.

51 This action opens the IMPORT CONFIGURATION dialog box, showing the controller tags that will be created. 5 If you are using the module in a different slot (or remote rack), select the correct connection input and output variables that define the path to the module. If your module is located in Slot 1 of the local rack, this step is not required. 6 Click OK to confirm the import. RSLogix will indicate that the import is in progress: ProSoft Technology, Inc. Page 51 of 78

52 When the import is completed, the new rung with the Add-On Instruction will be visible as shown in the following illustration. The procedure has also imported new User Defined Data Types, Controller Tags, and the Add-On instruction for your project. 7 Save the application and then download the sample ladder logic into the processor. Page 52 of 78 ProSoft Technology, Inc.

53 4.5 Connecting Your PC to the ControlLogix Processor There are several ways to establish communication between your PC and the ControlLogix processor. The following steps show how to establish communication through the serial interface. It is not mandatory that you use the processor's serial interface. You may access the processor through whatever network interface is available on your system. Refer to your Rockwell Automation documentation for information on other connection methods. 1 Connect the right-angle connector end of the cable to your controller at the communications port. 2 Connect the straight connector end of the cable to the serial port on your computer. ProSoft Technology, Inc. Page 53 of 78

54 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 establish communication with the processor. You do not have to download through the processor's serial port, as shown here. You may download through any available network connection. 2 When communication is established, RSLogix 5000 will open a confirmation dialog box. Click the DOWNLOAD button to transfer the sample program to the processor. 3 RSLogix 5000 will compile the program and transfer it to the processor. This process may take a few minutes. 4 When the download is complete, RSLogix 5000 will open another confirmation dialog box. If the key switch is in the REM position, click OK to switch the processor from PROGRAM mode to RUN mode. Note: If you receive an error message during these steps, refer to your RSLogix documentation to interpret and correct the error. Page 54 of 78 ProSoft Technology, Inc.

55 4.7 Setting up the Read and Write Database Areas The next part of this tutorial is to configure the MVI56E-MCM database read and write areas to define how data will be transferred between the processor and the MVI56E-MCM module. Write Area Read Area Description Database area transferred from processor to the module Database area transferred from module to the processor Start Register Database Address Parameter MCM.CONFIG.ModDef. WriteStartReg MCM.CONFIG.ModDef. ReadStartReg Register Count Database Parameter MCM.CONFIG.ModDef. WriteRegCnt MCM.CONFIG.ModDef. ReadRegCnt Data Controller Tag Array Name MCM.DATA.WriteData MCM.DATA.ReadData The Write Data and Read Data areas are configured through the following controller tags. The settings in the sample application above correspond with the following memory diagram. ProSoft Technology, Inc. Page 55 of 78

56 4.7.1 Configuring Modbus Port 1 (P1) The sample application uses the following configuration settings for Modbus Port 1 (Master) on the MVI56E-MCM module. Parameter Modbus Protocol Value RTU Baud Rate Parity Data Bits 8 Stop Bits 1 None The MODBUS PORT X configuration parameters are used when the module is configured as a Modbus Master device. Port 1 and Port 2 each have their own set of parameters to configure. Page 56 of 78 ProSoft Technology, Inc.

57 In RSLogix 5000, expand the MCM.CONFIG.MODDEF controller tag, and navigate to MCM.CONFIG.PORT1. Any parameters not mentioned in this section are not used or not essential when the module is configured as a Modbus Master. The following table describes the relevant parameters in the MCM.CONFIG.MODDEF.PORT1 tag array. Parameter Enabled Type Protocol Description 1 = ENABLE PORT, 0 = disable port 0=MASTER, 1=Slave, 2=Slave: pass-through, 3=Slave: formatted passthrough/data swapped, 4=Slave: form. Pass-through 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 (for 115,200 baud) Parity 0 = None, 1 = Odd, 2 = Even DataBits Modbus RTU mode = 8 Modbus ASCII mode = 8 or 7 StopBits Valid values are 1 or 2. UseCts RespTO RetryCount MinCmdDelay CmdErrPtr No or Yes This 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 hardware handshaking. Set to Yes if the devices connected to the port require hardware handshaking (most modern devices do not) If you set this parameter to Yes, be sure to pay attention to the pinout and wiring requirements to be sure the hardware handshaking signal lines are properly connected; otherwise communication will fail. 0 to milliseconds response timeout for command Note: 1000 = 1000 milliseconds (1 second) before it will either reissue the command, if RETRYCOUNT > 0, or, if the RetryCount =0 or has already been met, then it will move on to the next command in the list. Number of times to retry a failed request before moving to the next command on the list milliseconds The amount of delay in milliseconds to be inserted after receiving a slave response or encountering a response timeout before retrying the command or sending the next command on the list. Use this parameter to slow down overall polling speed and spread out commands on networks with slaves that require additional gaps between messages. Internal DB location to place command error list Note: Set Master Command Errors location. Each command will reserve one word for the command error code for that command. See Verify Communication. CMDERRPTR value should be within the range of the READDATA array. See Backplane Configuration. ProSoft Technology, Inc. Page 57 of 78

58 4.7.2 Configuring the Modbus Master Read Command The Modbus Read Command reads 10 words of data from the Quantum processor (Modbus Slave) and transfers it to the MVI56E-MCM module's internal database. The following table describes the relationship between memory addresses in the Modbus Master (MVI56E-MCM) and the Modbus Slave (Quantum processor). MVI56E-MCM Database Address Quantum Memory Address In the sample program, the Modbus Read Command is present, but disabled. To enable the command, change the 0 (zero) to 1 (one) in the MCM.CONFIG.PORT1MASTERCMD[0].ENABLE tag. Be sure the tag MCM.CONFIG.PORT1MASTERCMD[0].DEVADDRESS, is set to 800, 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 = , 801 = , 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) Page 58 of 78 ProSoft Technology, Inc.

59 4.7.3 Configuring the Modbus Master Write Command The Modbus Write Command will write data from the MVI56E-MCM module to the Quantum processor as follows. MVI56E-MCM Database Address Quantum Memory Address In the sample program, a Modbus Write Command is present, but disabled. To enable this command, change the 0 (zero) to 1 (one) in the MCM.CONFIG.PORT1MASTERCMD[1].ENABLE tag. Be sure the tag, MCM.CONFIG.PORT1MASTERCMD[1].NODE, is set to 400 as shown in the following illustration. Notes: FUNC 16 represents Modbus Function Code 16, the command code to Preset (Write) Holding Registers The DEVADDRESS parameter is 0-based so 400 = , 401 = , 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) ProSoft Technology, Inc. Page 59 of 78

60 4.8 Rebooting the Module to Transfer New Parameter Values The changes you made in the sample program do not take effect until you reboot the module. 1 Locate the MCM.CONTROL.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 begin exchanging data with the processor. Page 60 of 78 ProSoft Technology, Inc.

61 4.9 Configuring the Quantum Processor as a Modbus Slave The next part of this tutorial is to configure the remote Modbus Slave. For this example, 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 configure the Quantum processor with Schneider Electric's Concept programming software (version 2.6 or higher). Parameter Node Address 1 Modbus Protocol Value RTU Baud Rate Parity Data Bits 8 Stop Bits 1 None The following illustration shows the MODBUS PORT SETTINGS dialog box in Concept version 2.6. ProSoft Technology, Inc. Page 61 of 78

62 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 and the supplied null modem cable to Port 1 on the MVI56E-MCM module, and Modbus Comm1 on the Quantum processor. The following illustration shows the serial connection between the MVI56E-MCM module and the Quantum processor. Page 62 of 78 ProSoft Technology, Inc.

63 4.11 Verifying Communication There are several ways to verify that the MVI56E-MCM module is communicating with 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 Viewing Exchanged Data The following illustration describes the source and destination for the data exchanged by the two Modbus Master Commands. ProSoft Technology, Inc. Page 63 of 78

64 Checking Write Data The following steps show you how to verify that the WriteData Command is working. 1 In RSLogix, navigate to the processor controller tags MCM.DATA.WRITEDATA[0] through MCM.DATA.WRITEDATA[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 the MVI56E-MCM, and then to the Quantum processor, where you will be able to see the data in Concept. 3 In Concept, navigate to the REFERENCE DATA EDITOR to monitor the processor memory addresses from through The data should match the data you sent from RSLogix Page 64 of 78 ProSoft Technology, Inc.

65 Checking Read Data The following steps show you how to verify that the ReadData Command is working. 1 In Concept, navigate to the REFERENCE DATA EDITOR, and enter the following values in processor memory addresses from through as shown in the following illustration. This action populates the memory addresses in the Quantum processor that the MVI56E-MCM will attempt to retrieve with the ReadData Command. 2 In RSLogix 5000, the values in MCM.DATA.READDATA[0] through [9] should match the data you entered in Concept. Tip: Repeat these tests, using different values each time, to verify that the same data appears in the proper place in each processor. ProSoft Technology, Inc. Page 65 of 78

66 Checking Module Status through ControlLogix Controller Tags You can view network status through the ControlLogix controller tags that are updated 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 at the address you used for MCM.CONFIG.PORTX.CMDERRPTR parameter, minus the value of the MCM.CONFIG.MODDEF.READSTARTREG tag. In this case, the CmdErrPtr was set to 1500 and the ReadStartReg to This means that ( = 500); so READDATA[500] and READDATA[501] will tell you the individual status of each of the two commands issued by the module. To verify that the Modbus Slave is communicating with a Modbus Master, view the contents of the MCM.STATUS.PRTXERRS tag for total commands issued, responses received, errors, and so on. The following controller tags should continuously increment indicating that Port 1 is continuously sending commands and receiving responses: MCM.STATUS.PRT1ERRS.CMDREQ MCM.STATUS.PRT1ERRS.CMDRESP MCM.STATUS.PRT1ERRS.REQUESTS MCM.STATUS.PRT1ERRS.RESPONSES If the error counters continuously increment, the LASTERROR controller tag value shows the command index which caused the latest failure. You can refer to the command error pointer feature to read the command error codes as previously discussed. Page 66 of 78 ProSoft Technology, Inc.