EtherNet/IP Communications Module

Transcription

1 EtherNet/IP Communications Module M/N RECOMM-ENET Firmware Version 2.xxx Firmware Version 3.xxx Instruction Manual D

2 The information in this manual is subject to change without notice. Throughout this manual, the following notes are used to alert you to safety considerations:! ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Important: Identifies information that is critical for successful application and understanding of the product. ATTENTION: The drive may contain high voltages that can cause injury or death. Remove all power from the drive, and then verify power has been removed before installing or removing an! EtherNet/IP module. Failure to observe these precautions could result in severe bodily injury or loss of life. ATTENTION: Only qualified electrical personnel familiar with drive and power products and the associated machinery should plan or implement the installation, start up, configuration, and subsequent maintenance of the product using an EtherNet/IP module. Read and understand this manual in its entirety before proceeding. Failure to observe these precautions could result bodily injury and/or damage to equipment. ATTENTION: DPI host products must not be directly connected together via RECBL-xxx cables. Unpredictable behavior due to timing and other internal procedures can result if two or more devices are connected in this manner. Failure to observe this precaution could result bodily injury and/or damage to equipment. ATTENTION: If the EtherNet/IP module is transmitting control I/O to the drive, the drive may fault when you reset the module. Determine how your drive will respond before resetting an module. Failure to observe this precaution could result bodily injury and/or damage to equipment. ATTENTION: Parameters Comm Flt Action (21), Idle Flt Action (22), and Peer Flt Action (41) let you determine the action of the module and connected drive if communications are disrupted. By default, these parameters fault the drive. You can set these parameters so that the drive continues to run. Precautions should be taken to ensure that the settings of these parameters do not create a hazard of injury or equipment damage.when commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected cable or a faulted controller). Failure to observe this precaution could result bodily injury and/or damage to equipment. ATTENTION: When a system is configured for the first time, there may be unintended or incorrect machine motion. Disconnect the motor from the machine or process during initial system testing. Failure to observe this precaution could result bodily injury and/or damage to equipment. Windows and Microsoft are trademarks of Microsoft Corporation. Ethernet is a trademark of Digital Equipment Corporation, Intel Corporation, and Xerox Corporation. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation. Reliance, SP600, GV6000, LiquiFlo 2.0, VS Utilities, DPI, RSLogix, ControlLogix, and SLC are trademarks of Rockwell Automation Rockwell Automation. All rights reserved.

3 CONTENTS Chapter 1 Chapter 2 Chapter 3 Chapter 4 Introduction 1.1 Module Features Compatible Products Related Documentation Getting Assistance from Reliance Electric Getting Started 2.1 Required Equipment Installation Checklist Installing the EtherNet/IP Module 3.1 Preparing for an Installation Setting the Web Pages Switch (Version 3.xxx) Connecting the Module to the Drive Connecting the Module to the Network Applying Power Commissioning the Module Configuring the EtherNet/IP Module 4.1 Configuration Tools Using the LCD OIM to Configure the Module SP600 and LiquiFlo GV Using BOOTP to Set the IP Address, Subnet Mask, and Gateway Address Using Parameters to Set the IP Address, Subnet Mask, and Gateway Address Setting the Data Rate Setting the I/O Configuration Setting the Reference Adjustment Selecting a Master-Slave or Peer-to-Peer Hierarchy Configuring the Module for a Master-Slave Hierarchy Configuring the Module to Transmit Peer-to-Peer Data Configuring the Module to Receive Peer-to-Peer Data Setting a Fault Action Setting the Fault Configuration Parameters Contents I

4 4.10 Setting Web Access Control Resetting the Module Viewing the Module Configuration Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Configuring the Scanner or Bridge 5.1 Configuring a Simple Network: An Example Adding a Bridge or Scanner to the I/O Configuration Adding the Module and Drive to the I/O Configuration Saving the Configuration Using I/O Messaging 6.1 About I/O Messaging Understanding the I/O Image Using Logic Command/Status Using Reference/Feedback Using Datalinks Bit Parameters using 16-Bit Datalinks Sample Ladder Logic Program Function of the Sample Program RSLogix 5000 Configuration Logic Command/Status Words Sample ControlLogix Ladder Logic Program Sample Datalink Data Using Explicit Messaging 7.1 About Explicit Messaging Formatting Explicit Messages Performing Explicit Messages About the Explicit Message Examples Get Attribute Single Message Example Set Attribute Single Message Example Get Attributes Scattered Message Example Set Attributes Scattered Message Example Troubleshooting the Module and Network 8.1 Understanding the Status Indicators DRIVE Status Indicator MS Status Indicator NET A Status Indicator NET B Status Indicator Module Diagnostic Items Viewing and Clearing Events Viewing the Module s Web Pages 9.1 Accessing the Module s Main Web Pages II EtherNet/IP Communications Module

5 9.1.1 Information on Module Home Page Process Display Pop-Up Windows TCP/IP Configuration Web Page Configure Notification Web Page To configure notification DPI Device Information Pages Contents III

6 IV EtherNet/IP Communications Module

7 List of Figures Figure 2.1 Components of the EtherNet/IP Module Figure 3.1 Setting Web Pages Switch Figure 3.2 DPI Ports and Internal Interface Cables Figure 3.3 Mounting the Module Figure 3.4 Connecting the Ethernet Cable to the Network Figure 4.1 Accessing the Module Parameters using the LCD OIM (SP600, LiquiFlo) Figure 4.2 Acessing the Module Parameters using the LCD OIM (GV6000) Figure 4.3 BOOTP Server Window Figure 4.4 New Entry Dialog Box Figure 4.5 BOOTP Server Window with an Module in the Relation List Figure 4.6 Sample BOOTP Screen on an LCD OIM Figure 4.7 Sample IP Address Screen on an LCD OIM Figure 4.8 Sample Subnet Mask Screen on an LCD OIM Figure 4.9 Sample Gateway Screen on an LCD OIM Figure 4.10 Ethernet Data Rate Screen on an LCD OIM Figure 4.11 I/O Configuration Screen on an LCD OIM Figure 4.12 Reference Adjust Screen on an LCD OIM Figure 4.13 Master-Slave Input Screen on an LCD OIM Figure 4.14 Master-Slave Output Screen on an LCD OIM Figure 4.15 Peer Out Enable Screen on an LCD OIM Figure 4.16 Peer A Output Screen on an LCD OIM Figure 4.17 Peer B Output Screen on an LCD OIM Figure 4.18 Peer Out Time and Peer Out Skip Screens on an LCD OIM Figure 4.19 Peer Input Enable Screen on an LCD OIM Figure 4.20 Peer Input Address 1 Screen on an LCD OIM Figure 4.21 Peer A Input Screen on an LCD OIM Figure 4.22 Peer B Input Screen on an LCD OIM Figure 4.23 Peer Logic Command Mask Screen on an LCD OIM Figure 4.24 Peer Input Timeout Screen on an LCD OIM Figure 4.25 Peer Fault Action Screen on an LCD OIM Figure 4.26 Comm Flt Action Screen and Idle Flt Action Screen on an LCD OIM Figure 4.27 Example Web Access Control Screen on an LCD OIM Figure 4.28 Example Web Access Control Screen on an LCD OIM Figure 4.29 Reset Screen on an LCD OIM Figure 5.1 Sample EtherNet/IP Network Figure 5.2 RSLogix 5000 Window Figure 5.3 Select Module Type Dialog Box Figure 5.4 Module Properties Dialog Box - Page Figure 5.5 RSLogix 5000: I/O Configuration Folder Contents V

8 Figure 5.6 Right Clicking the Scanner Figure 5.7 Select Module Type Dialog Box Figure 5.8 Module Properties Dialog Box - Page Figure 5.9 Module Properties Dialog Box - Page Figure 5.10 RSLogix Data Types and I/O Configuration Folders Figure 5.11 Download Dialog Box Figure 6.1 ControlLogix I/O Image with All I/O Enabled (Example 1) Figure 6.2 ControlLogix I/O Image (Example 2) Figure 6.3 Controller Tags for the Sample ControlLogix Ladder Logic Program Figure 6.4 Output Image for the Sample ControlLogix Ladder Logic Program Figure 6.5 Input Image for the Sample ControlLogix Ladder Logic Program Figure 6.6 Program Tags for Sample ControlLogix Ladder Logic Program Figure 6.7 Sample ControlLogix Ladder Logic Program for I/O Messaging Figure 6.8 Sample ControlLogix Ladder Logic Program for I/O Messaging (Continued) Figure 6.9 Sample Datalink Data for the Sample Ladder Logic Program Figure 7.1 ControlLogix Message Format in RSLogix Figure 7.2 Explicit Message Process Figure 7.3 Controller Tags for Explicit Messages Figure 7.4 Message Format for a Get Attribute Single Message Figure 7.5 Get Attribute Single Message Example Figure 7.6 Example of Destination Data from a Get Attribute Single Message Figure 7.7 Message Format for a Set Attribute Single Message Figure 7.8 Set Attribute Single Message Example Figure 7.9 Example of Source Data from Set Attribute Single Message. 7-9 Figure 7.10 Message Format for a Get Attributes Scattered Message Figure 7.11 Example of Get Attributes Scattered Message Figure 7.12 Data Structure for Get Scattered Attributes Messages Figure 7.13 Source Data Example Figure 7.14 Destination Data Example Figure 7.15 Message Format for a Set Attributes Scattered Message Figure 7.16 Set Attributes Scattered Message Example Figure 7.17 Data Structures for Set Attributes Scattered Message Figure 7.18 Source Data Example Figure 7.19 Destination Data Example Figure 8.1 Viewing and Clearing Events Using an LCD OIM on a SP600 or LiquiFlo 2.0 Drive Figure 8.2 Viewing and Clearing Events Using an LCD OIM on a GV6000 Drive VI EtherNet/IP Communications Module

9 Figure 9.1 Main Web Page for the Module Figure 9.2 Process Display Pop-up Window Figure 9.3 TCP/IP Configuration Web Page Figure 9.4 Configuration of Notification Web Page Figure 9.5 Selected Fault Configuration Page Figure 9.6 Example of Message Ssent by Module Figure 9.7 Example of Port 0 (SP600 Drive) Module Information Page Figure 9.8 Example of Port 0 (SP600 Drive) Diagnostic Information Page Figure 9.9 Example of Port 0 (SP600 Drive) Fault Queue Page Figure 9.10 Example of Port 5 (RECOMM-ENET Module) Event Queue Page Contents VII

10 VIII EtherNet/IP Communications Module

11 List of Tables Table 2.1 Equipment Shipped with the EtherNet/IP Module Table 2.2 User-Supplied Items Required for Installation Table 4.1 Configuration Tools Table 4.2 Editing the New Entry Dialog Box Table 4.3 Selections for Drive Response to Communication Fault Table 4.4 Fault Configuration Parameters Table 4.5 Module Configuration Parameters Table 5.1 Module Properties Fields Table 5.2 Edit Module Properties Table 5.3 Edit Connection Parameters Table 5.4 SP600 and LiquiFlo 2.0 (16-Bit Reference/Feedback and Datalinks) Table 5.5 GV Bit Reference/Feedback and 32-bit Datalinks) Table 6.1 Parameter Settings for the Sample Program Table 7.1 Settings for Message Format Table 7.2 Key Settings for Data Format Table 7.3 Key Settings for Message Format Table 7.4 Message Format Settings Table 8.1 Status Indicators (Location on Drive May Vary) Table 8.2 DRIVE Status Indicator: State Definitions Table 8.3 MS Status Indicator: State Definitions Table 8.4 NET A Status Indicator: State Definitions Table 8.5 NET B Status Indicator: State Definitions Table 8.6 Module Diagnostic Items Table 8.7 Event Codes and Descriptions Contents IX

12 X EtherNet/IP Communications Module

13 CHAPTER 1 Introduction This manual provides information about the EtherNet/IP Communications module (RECOMM-ENET) and using it with DPI AC drives, such as SP600 and GV6000 drives. It is intended for qualified electrical personnel familiar with installing, programming, and maintaining AC drives and networks. The module is mounted in the drive and receives its required power from the drive. It can be used with other products that implement DPI, which is a peripheral communication interface. Refer to the documentation for your product for specific information about how it works with this module. 1.1 Module Features The EtherNet/IP Communications module features the following: Status indicators that report the status of the drive communications, module, and network. They are visible both when the cover is opened and when it is closed. I/O, including Logic Command/Reference and up to four pairs of Datalinks that may be configured for your application using associated parameters. A number of tools to configure the module and connected drive. These tools include the LCD OIM and VS Utilities software. In addition, you can use a BOOTP server to configure the network features on the module (for example, the IP address). User-defined fault actions that determine how the module and the drive respond to communication disruptions on the network. Explicit messages are supported. Master-Slave or Peer-to-Peer hierarchies can be set up so that the module and the connected drive can transmit data to and from either a scanner or another drive on the network. Each module has a web page that displays information about the module, the connected drive, and other DPI devices connected to the drive. The module can be configured to send messages to desired addresses when selected drive faults occur and/or are cleared, and/or when the module takes a communication or idle fault action. Introduction 1-1

14 1.2 Compatible Products DPI (Drive Peripheral Interface) is a second generation peripheral communication interface. The EtherNet/IP module is compatible with Reliance Electric drive products that support DPI. AT the time of publication, compatible products include: SP600 6SP Series AC Drives SP600 6SB Series AC Drives GV6000 AC Drives LiquiFlo 2.0 AC Drives 1.3 Related Documentation Refer to the following related publications as necessary for more information. All of the publications are available from D SP600 AC Drive User Manual (6SP Series) D SP600 AC Drive User Manual (6SB Series) D GV6000 AC Drive User Manual D VS Utilities Getting Results Manual Online help installed with the software D LiquiFlo 2.0 AC Drive User Manual ENET-IN EtherNet/IP Planning and Installation Manual ENET-AP EtherNet/IP Performance and Application Guide 1756-UM ControlLogix Ethernet Bridge Module User Manual 1756-UM ControlLogix Ethernet Communications Module User Manual 9399-WAB32GR RSLinx Getting Results with RSLinx 9399-RLD300GR RSLogix 5000 Getting Results Guide 1-2 EtherNet/IP Communications Module

15 1.4 Getting Assistance from Reliance Electric If you have any questions or problems with the products described in this instruction manual, contact your local Reliance Electric sales office. For technical assistance, call Before calling, please review the troubleshooting section of this manual and check the Reliance drives website for additional information. When you call this number, you will be asked for the drive model number and this instruction manual number. Introduction 1-3

16 1-4 EtherNet/IP Communications Module

17 CHAPTER 2 Getting Started This chapter provides: A description of the EtherNet/IP module s components A list of parts shipped with the module A list of user-supplied parts required for installing the module An installation checklist ➊ ➋ ➌ ➍ Not provided on firmware version 2.xxx or earlier ➀ Status Indicators Four LEDs to indicate the status of the connected drive, module, and network. Refer to chapter 6 for more information about the LEDs. ➁ DPI Connector A 20-pin, single-row shrouded male header. An Internal Interface cable connects to this connector and one on the drive. ➂ 4 Ethernet Connector Web Page Switch (SW2) An RJ-45 connector the Ethernet cable. The connector is CAT-5 compliant to ensure reliable data transfer on 100Base-TX Ethernet connections. Enables or disables the module web pages. Refer to Chapter 3, Setting the Web Pages Switch (Firmware 3.xxx only). SW1 is unused. Figure 2.1 Components of the EtherNet/IP Module Getting Started 2-1

18 2.1 Required Equipment Table 2.1 lists the equipment shipped with the EtherNet/IP module. When you unpack the module, verify that the package includes all of these items. Table 2.1 Equipment Shipped with the EtherNet/IP Module Item Description One EtherNet/IP Communications module One 2.54 cm (1 in) and one cm (6 in) Internal Interface cable (only one of these cables is needed to connect the module to the drive) One EtherNet/IP Communications module User Manual (D2-3510) To install and configure the EtherNet/IP module, you must supply the items listed in table 2.2. Table 2.2 User-Supplied Items Required for Installation Item Description Small flathead or Phillips screwdriver Ethernet cable (Refer to the EtherNet/IP Media Planning and Installation Manual, publication ENET-IN001..., for details.) Configuration tool, such as SP600 LCD OIM, GV6000 LCD OIM, or LiquiFlo 2.0 LCD OIM VS Utilities BOOTP Server (version 2.1 or higher) for network setup only Controller configuration software (for example: RSLogix 5, RSLogix 500, RSLogix 5000 software) PC connection to the EtherNet/IP network. 2-2 EtherNet/IP Communcations Module

19 2.2 Installation Checklist This section is designed to help experienced users start using the EtherNet/IP module. If you are unsure how to complete a step, refer to the referenced chapter. Step Action Refer to: 1 Review the safety precautions for the module. Throughout this manual 2 Verify that the drive is properly installed. Drive User Manual 3 Install the module. Verify that the drive and the network are not powered. Then, connect the module to the network using an Ethernet cable and to the drive using the Internal Interface cable. Use the captive screws to secure and ground the module to the drive. 4 Apply power to the module. Apply power to the network and to the drive. The module receives power from the drive and network. The status indicators should be green. If they flash red, there is a problem. Refer to chapter 8 for more information on the status indicators. 5 Configure the module for your application. Set the parameters for the following features as required by your application: IP address, subnet mask, and gateway address Data rate I/O configuration Master-slave or peer-to-peer hierarchy Fault actions 6 Configure the scanner or bridge to communicate with the module. Use a software tool, such as RSLogix, to configure the master on the EtherNet/IP network to recognize the module and the drive. Chapter 3, Installing the EtherNet/IP module Chapter 3, Installing the EtherNet/IP module Chapter 4, Configuring the EtherNet/IP module Chapter 5, Configuring the Scanner or Bridge Getting Started 2-3

20 Step Action Refer to: 7 Create a ladder logic program. Use a programming tool to create a ladder logic program that enables you to do the following: Control the module and connected drive using I/O Monitor or configure the drive using Explicit messages. Chapter 6, Using I/O Messaging Chapter 7, Using Explicit Messaging 2-4 EtherNet/IP Communcations Module

21 CHAPTER 3 Installing the EtherNet/IP Module Chapter 3 provides instructions for installing the module on Reliance Electric drives. 3.1 Preparing for an Installation Before installing the module: Read the EtherNet/IP Performance and Application Guide, publication ENET-AP001..., and EtherNet/IP Media Planning and Installation Manual, publication ENET-IN Verify that you have all required equipment. Refer to chapter 2, Getting Started, for a list of equipment.! Important: ATTENTION: The EtherNet/IP module contains ESD- (Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures. Static control precautions are required when handling the module. Failure to observe these precautions could result in damage to equipment. To guard against device malfunction, you must wear a grounding wrist strap when installing the EtherNet/IP module. 3.2 Setting the Web Pages Switch (Version 3.xxx) To use the module web pages, the Web Pages Switch (not provided on version 2.xxx and earlier modules) must be set to its Enable Web position. Important: A new setting is recognized only when power is applied to the module, or the module is reset. If you change a setting, cycle power or reset the module. Installing the EtherNet/IP Module 3-1

22 ! ATTENTION: The EtherNet/IP module contains ESD- (Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures. Static control precautions are required when handling the module. Failure to observe these precautions could result in damage to equipment. Set the Web Pages Switch (SW2) to enable or disable the module web pages (see figure 3.1 and setting descriptions below). By default, the module web pages are disabled. For complete details on module web pages, see Chapter 9, View the module s Web Pages. UNUSED SWITCH WEB PAGES SWITCH O N 1 2 Enable Web Position Disable Web Position SW2 Setting Down (OFF) position Up (ON) position Description Disables the module web pages (default setting). Enables the module web pages. Figure 3.1 Setting Web Pages Switch 3.3 Connecting the Module to the Drive! Step 1. Step 2. ATTENTION: The Reliance Electric drive may contain high voltages that can cause injury or death. Remove power from the drive, and then verify power has been discharged before installing or removing an module. Failure to observe this precaution could result in severe bodily injury or loss of life. Remove power from the drive. Use static control precautions. 3-2 EtherNet/IP Communications Module

23 Step 3. Connect the Internal Interface cable to the DPI port on the drive and then to the DPI connector on the module. See figure 3.2. ➀ ➁ ➂ EtherNet/IP module SP600 Drive (6SP Series) ➃ GV6000 or SP600 6SB Series Drive ➀ ➁ ➂ ➃ cm (6 in) Internal Interface cable DPI Connector EtherNet Cable 2.54 cm (1 in) Internal Interface cable Figure 3.2 DPI Ports and Internal Interface Cables Step 4. For SP600 6SP Series drives, fold the Internal Interface cable behind the module and mount the module on the drive using the four captive screws. See figure 3.3. Installing the EtherNet/IP Module 3-3

24 For GV6000 and SP600 6SB series drives, mount the module on the drive using the four captive screws to secure and ground it to the drive. Important: All screws must be tightened since the module is grounded through a screw. The recommended tightening torque is 0.9 N-m (8 in-lb). Module SP600 6SP Series Drive Internal Interface cable folded behind the module and in front of the drive. GV6000 or SP600 6SB Series Drive Figure 3.3 Mounting the Module 3-4 EtherNet/IP Communications Module

25 3.4 Connecting the Module to the Network! Step 1. Step 2. Step 3. ATTENTION: The Reliance Electric drive may contain high voltages that can cause injury or death. Remove power from the drive, and then verify power has been discharged before installing or removing a module. Failure to observe this precaution could result in severe bodily injury or loss of life. Remove power from the drive. Use static control precautions. Connect an Ethernet cable to the EtherNet/IP network. Refer to figure 3.4. Router (Optional) ControlLogix with EtherNet/IP Bridge SP600 Drive with RECOMM-ENET GV6000 Drive with RECOMM-ENET Figure 3.4 Connecting the Ethernet Cable to the Network Step 4. Route the Ethernet cable through the bottom of the drive and connect it to the module. Step 5. Connect the cable to the module (refer to figure 3.2). Installing the EtherNet/IP Module 3-5

26 3.5 Applying Power Step 1. Step 2.! ATTENTION: Unpredictable operation may occur if parameter settings are not compatible with your application. Verify that settings are compatible with your application before applying power to the drive. Failure to observe these precautions could result in severe bodily injury of loss of life. Close the door or reinstall the cover on the drive. The status indicators can be viewed on the front of the drive after power has been applied. Apply power to the drive. The module receives its power from the connected drive. When you apply power to the product for the first time, the status indicators should be green or off after an initialization. If the status indicators are red, refer to chapter 8, Troubleshooting the module and Network. 3.6 Commissioning the Module To commission the module, you must set a unique IP address. (Refer to the Glossary for details about IP addresses.) After installing the module and applying power, you can set the IP address by using a BOOTP server or by setting parameters. By default, the module is configured so that you must set the IP address using a BOOTP server. To set the IP address using parameters, you must disable the BOOTP feature. Refer to chapter 4, Configuring the module, for details. Important: New settings for some parameters (for example, IP Addr Cfg 1 through IP Addr Cfg 4) are recognized only when power is applied to the module or it is reset. After you change parameter settings, cycle power or reset the module. 3-6 EtherNet/IP Communications Module

27 CHAPTER 4 Configuring the EtherNet/IP Module Chapter 4 provides instructions and information for setting the parameters in the module. For a complete list of parameters, refer to Appendix B, EtherNet/IP Module Parameters. For definitions of terms in this chapter, refer to the Glossary. 4.1 Configuration Tools The module stores parameters and other information in its own nonvolatile memory. Therefore, you must access the module to view and edit its parameters. Table 4.1 lists the tools that can be used to access the module parameters. Table 4.1 Configuration Tools Tool Refer to: VS Utilities Software VS Utilities online help LCD OIM Section 4.2 BOOTP Server Section 4.3 Configuring the EtherNet/IP Module 4-1

28 4.2 Using the LCD OIM to Configure the Module SP600 and LiquiFlo 2.0 Use the procedure in figure 4.1 to access the parameters on the EtherNet/IP module using the LCD OIM. If you are unfamiliar with the operation of the LCD OIM, refer to the Reliance Electric Drive User Manual for more information. >> Stopped Auto P0: SP600 Main Menu >> Stopped Auto P0: SP600 Device: Port 0 SP600 RECOMM-ENET >> Auto Stopped P5: RECOMM-ENET Main Menu Device Select Monitor Lang Parameters Use to highlight Device Select icon Use to select RECOMM-ENET. Edit the EtherNet/IP parameters using the same techniques as for drive parameters. Figure 4.1 Accessing the Module Parameters using the LCD OIM (SP600, LiquiFlo) 4-2 EtherNet/IP Communications Module

29 4.2.2 GV6000 Use the procedure in figure 4.2 to access the parameters on the EtherNet/IP module using the LCD OIM. If you are unfamiliar with the operation of the LCD OIM, refer to the Reliance Electric Drive User Manual for more information. Figure 4.2 Acessing the Module Parameters using the LCD OIM (GV6000) 4.3 Using BOOTP to Set the IP Address, Subnet Mask, and Gateway Address By default, the module is configured so that you can set its IP address, subnet mask, and gateway address by using a BOOTP utility. You can select from a variety of BOOTP utilities. These instructions use Rockwell s BOOTP Server (version 2.1), a standalone program that incorporates the functionality of standard BOOTP utilities with a graphical interface. It is available from Refer to the Readme file and online Help for detailed directions and information. Note: If desired, you can disable BOOTP and configure the IP address, subnet mask, and gateway address by setting parameters. For details, refer to section 4.4. To configure the module using BOOTP Server, use the following procedure: Step 1. On the label of the module, locate and note the hardware address of the module. Configuring the EtherNet/IP Module 4-3

30 Step 2. On a computer connected to the EtherNet/IP network, start the BOOTP software. The BOOTP Server window appears as shown in figure 4.3. Devices on the network issuing BOOTP requests appear in the BOOTP Request History list. Figure 4.3 BOOTP Server Window Step 3. In the BOOTP Request History list, double-click the hardware address (Ethernet MAC address) of the module. The New Entry dialog box is displayed as shown in figure 4.4. Figure 4.4 New Entry Dialog Box Step 4. Edit the fields shown in table 4.2 in the New Entry Dialog box: 4-4 EtherNet/IP Communications Module

31 Table 4.2 Editing the New Entry Dialog Box In this field: IP Address 1 Subnet Mask 1 Gateway 1 Enter this information: A unique IP address for the module. A subnet mask for the module s network. The IP address of the gateway device on the module s network. 1 For definitions, refer to the Glossary. Step 5. Click OK to apply the settings. The module appears in the Relation List with the new settings as shown in figure 4.5. Figure 4.5 BOOTP Server Window with an Module in the Relation List Step 6. Step 7. To assign this configuration to the module permanently, click Disable BOOTP. When power is cycled on the module, it will use the configuration you assigned it and will not issue new BOOTP requests. Note: To enable BOOTP for a module that has had BOOTP disabled: a. Select the module in the Relation List b. Click Enable BOOTP. c. Reset the module. To save the Relation List, select File > Save. Configuring the EtherNet/IP Module 4-5

32 4.4 Using Parameters to Set the IP Address, Subnet Mask, and Gateway Address By default, the module is configured so that you set its IP address, subnet mask, and gateway address using a BOOTP server. If you want to set these features using the module s parameters instead, you must disable BOOTP and then set the appropriate parameters in the module. To disable the BOOTP feature: Step 1. Set the value of module parameter 3 (BOOTP) to Disabled as shown in figure 4.6. Port 5 Device RECOMM-ENET Parameter #: 03 BOOTP 0 Disabled Value Setting 0 Disabled 1 Enabled (Default) Figure 4.6 Sample BOOTP Screen on an LCD OIM Step 2. Reset the module. Refer to Resetting the Module in section After disabling the BOOTP feature, you can then configure the IP address, subnet mask, and gateway using the module s parameters. To set an IP address using parameters: Step 1. Verify that module parameter 3 (BOOTP) is set to Disabled. This parameter must be set to Disabled to configure the IP address using parameters. Step 2. Set the value of module parameters 4 through 7 (IP Addr Cfg 1 through IP Addr Cfg 4) to a unique IP address. Port 5 Device RECOMM-ENET Parameter #: 04 IP Addr Cfg <> 255 Default = [IP Addr Cfg 1] [IP Addr Cfg 2] [IP Addr Cfg 3] [IP Addr Cfg 4] Figure 4.7 Sample IP Address Screen on an LCD OIM 4-6 EtherNet/IP Communications Module

33 Step 3. Reset the module. Refer to Resetting the Module in section The Net A status indicator will be solid green or flashing green if the IP address is correctly configured. To set a subnet mask using parameters: Step 1. Verify that module parameter 3 (BOOTP) is set to Disabled. This parameter must be set to Disabled to configure the subnet mask using parameters. Step 2. Set the value of module parameters 8 through 11 (Subnet Cfg 1 through Subnet Cfg 4) to the desired value for the subnet mask as shown in figure 4.8. Port 5 Device RECOMM-ENET Parameter #: 08 Subnet Cfg <> 255 Default = [Subnet Cfg 1] [Subnet Cfg 2] [Subnet Cfg 3] [Subnet Cfg 4] Figure 4.8 Sample Subnet Mask Screen on an LCD OIM Step 3. Reset the module. Refer to Resetting the Module in section To set a gateway address for the module using parameters Step 1. Verify that module parameter 3 (BOOTP) is set to Disabled. This parameter must be set to Disabled to configure the gateway address using parameters. Step 2. Set the value of module parameters 12 through 15 (Gateway Cfg 1 through Gateway Cfg 4) to the IP address of the gateway device as shown in figure 4.9. Port 5 Device RECOMM-ENET Parameter #: 12 Gateway Cfg <> 255 Default = [Gateway Cfg 1] [Gateway Cfg 2] [Gateway Cfg 3] [Gateway Cfg 4] Step 3. Figure 4.9 Sample Gateway Screen on an LCD OIM Reset the module. Refer to Resetting the Module in section Configuring the EtherNet/IP Module 4-7

34 4.5 Setting the Data Rate By default, the module is set to autodetect, so it automatically detects the data rate and duplex setting used on the network. If you need to set a specific data rate and duplex setting, the value of module parameter 16 (EN Rate Cfg) determines the Ethernet data rate and duplex setting that the module will use to communicate. For definitions of data rate and duplex, refer to the Glossary. Step 1. Set the value of parameter 16 (EN Rate Cfg) to the data rate at which your network is operating as shown in figure Port 5 Device RECOMM-ENET Parameter #: 16 EN Rate Cfg 0 Autodetect Value Data Rate 0 Autodetect (default) 1 10 Mbps Full 2 10 Mbps Half Mbps Full Mbps Half Figure 4.10 Ethernet Data Rate Screen on an LCD OIM Important:Auto detection of baud rate and duplex works properly only if the device (usually a switch) on the other end of the cable is also set to auto detect the baud rate/duplex. If one device has the baud rate/duplex hard coded, the other device must be hard-coded to the same settings. Step 2. Reset the module. Refer to Resetting the Module in section Setting the I/O Configuration The I/O configuration determines the data that is sent to and from the drive. Logic Command/Status, Reference/Feedback and Datalinks may be enabled or disabled. Step 1. Set the bits in module parameter 23 (DPI I/O CFG) as shown in figure A 1 enables the I/O. A 0 disables the I/O. Bit 0 is the right-most bit. In figure 4.11, it is highlighted and equals EtherNet/IP Communications Module

35 Port 5 Device RECOMM-ENET Parameter #: 23 DPI I/O Config xxxxxxxxxxx Cmd/Ref b00 Bit Description 0 Logic Command/Reference (Default) 1 Datalink A 2 Datalink B 3 Datalink C 4 Datalink D 5-15 Not Used Step 2. Step 3. Step 4. Figure 4.11 I/O Configuration Screen on an LCD OIM If Logic Command/Reference is enabled, configure the parameters in the drive to accept the Logic Command and Reference from the module. For example, set Speed Ref A Sel (90) in the drive to Network so that the drive uses the Reference from the module. Also, verify that drive parameter Logic Source Sel (89) is configured to receive the desired logic from the module. Refer to the drive documentation for details. If you enabled one or more Datalinks, configure parameters in the drive to determine the source and destination of data in the Datalink(s). For example, configure the Datalinks in the drive by setting parameters 300 through 317 (Data In A1 through Data Out D2). Also, ensure that the EtherNet/IP module is the only module using the enabled Datalink(s). Reset the module. Refer to section 4.11, Resetting the Module. The module is ready to receive I/O. You must now configure the module to receive I/O from a master or peer device. Refer to section 4.8, Selecting a Master-Slave or Peer-to-Peer Hierarchy. If you select a Master-Slave hierarchy, you must also configure the master to communicate with the module. Refer to chapter 5, Configuring the Scanner or Bridge. Configuring the EtherNet/IP Module 4-9

36 4.7 Setting the Reference Adjustment A reference adjustment is a percent scaling factor for the reference from the network and can be set from 0 to 200%. This allows the drive s reference to either match the network reference (=100%), scale below the network reference (<100%), or scale above the network reference (>100%).! ATTENTION: Changes to module parameter 37 (Ref Adjust) take effect immediately. A drive receiving its Reference from the module will receive the newly scaled Reference, resulting in a change of speed. Failure to observe this precaution could result in bodily injury or damage to equipment. If the module is receiving a reference, adjust the scale in module parameter 37 (Ref Adjust). It can be scaled between 0.00 and %. Refer to figure Port 5 Device RECOMM-ENET Parameter #: 37 Ref Adjust % 0.00 <> Default = % Figure 4.12 Reference Adjust Screen on an LCD OIM The adjustment takes effect as soon as it is entered. 4.8 Selecting a Master-Slave or Peer-to- Peer Hierarchy A hierarchy determines the type of device with which the module exchanges data. In a Master-Slave hierarchy, a module exchanges data with a master, such as a scanner or bridge. In a Peer-to-Peer hierarchy, a module exchanges data with one or more EtherNet/IP modules connected to devices that have compatible logic command/status words. For both master-slave and peer-to-peer hierarchies, the devices exchanging data must be on the same IP subnet. See IP Addresses in the Glossary for more information about IP subnets EtherNet/IP Communications Module

37 4.8.1 Configuring the Module for a Master-Slave Hierarchy To select a Master-Slave hierarchy: Step 1. Enable the desired I/O in module parameter 23 (DPI I/O Cfg). Refer to figure Step 2. Set the bits in module parameter 35 (M-S Input). This parameter determines the data received from the master by the drive. A 1 enables the I/O. A 0 disables the I/O. Bit 0 is the right-most bit. In 4.13, it is highlighted and equals 1. Port 5 Device RECOMM-ENET Parameter #: 35 M-S Input xxxx xxxx xxx Cmd/Ref b00 Bit Description 0 Logic Command/Reference (Default) 1 Datalink A Input 2 Datalink B Input 3 Datalink C Input 4 Datalink D Input 5-15 Not Used Figure 4.13 Master-Slave Input Screen on an LCD OIM Step 3. Set the bits in module parameter 36 (M-S Output). This parameter determines the data transmitted from the drive to the scanner. A 1 enables the I/O. A 0 disables the I/O. Bit 0 is the right-most bit. In figure 4.14, it is highlighted and equals 1.. Port 5 Device RECOMM-ENET Parameter #: 36 M-S Output xxxxxxxxxxx Status/Fdbk b00 Bit Description 0 Status/Feedback (Default) 1 Datalink A Output 2 Datalink B Output 3 Datalink C Output 4 Datalink D Output 5-15 Not Used Figure 4.14 Master-Slave Output Screen on an LCD OIM Step 4. Reset the module. Refer to Resetting the Module in section The module is ready to receive I/O from the master (i.e., scanner). You must now configure the scanner to recognize and transmit I/O to the module. Refer to chapter 5, Configuring the Scanner or Bridge. Configuring the EtherNet/IP Module 4-11

38 4.8.2 Configuring the Module to Transmit Peer-to- Peer Data To configure an module to transmit Peer-to-Peer data: Step 1. Verify that module parameter 51 (Peer Out Enable) is set to Off (see figure 4.15). This parameter must be Off while you configure peer output parameters. Port 5 Device RECOMM-ENET Parameter #: 51 Peer Out Enable 0 Off Value Setting 0 Off (Default) 1 On Figure 4.15 Peer Out Enable Screen on an LCD OIM Step 2. Select the source of the data to output to the network in module parameter 49 (Peer A Output). See figure Port 5 Device RECOMM-ENET Parameter #: 49 Peer A Output 1 Cmd/Ref Value Description 0 Off (Default) 1 Logic Command/Reference 2-5 Datalink A, B, C, or D Input 6-9 Datalink A, B, C, or D Output Figure 4.16 Peer A Output Screen on an LCD OIM Step 3. If desired, select an additional source of the data to output to the network in module parameter 50 (Peer B Output) as shown in figure Port 5 Device RECOMM-ENET Parameter #: 50 Peer B Output 2 DL A Input Value Description 0 Off (Default) 1 Logic Command/Reference 2-5 Datalink A, B, C, or D Input 6-9 Datalink A, B, C, or D Output Figure 4.17 Peer B Output Screen on an LCD OIM Step 4. Set module parameters 52 (Peer Out Time) and 53 (Peer Out Skip) to establish the minimum and maximum intervals between Peer messages. Because the module 4-12 EtherNet/IP Communications Module

39 transmits Peer messages when a change-of-state condition occurs, minimum and maximum intervals are required. The minimum interval ensures that the module does not transmit messages on the network too often, thus minimizing network traffic. It is set in module parameter 52 (Peer Out Time). The maximum interval ensures that the module transmits messages often enough so that the receiving module(s) can receive recent data and verify that communications are working or, if communications are not working, can timeout. The maximum interval is the value of module parameter 52 (Peer Out Time) multiplied by the value of module parameter 53 (Peer Out Skip). In the example in figure 4.18, the minimum interval is set to 2.00 seconds, and the maximum interval is set to 4.00 seconds (2.00 x 2). Port 5 Device RECOMM-ENET Parameter #: 52 Peer Out Time 2.00 Secs. 0 <> Default = Secs Port 5 Device RECOMM-ENET Parameter #: 53 Peer Out Skip 2 1 <>16 Default = 1 Figure 4.18 Peer Out Time and Peer Out Skip Screens on an LCD OIM Step 5. Set module parameter 51 (Peer Out Enable) to On. The module will transmit the data selected in module parameters 49 (Peer A Output) and 50 (Peer B Output) to the network. Another module must be configured to receive the peer I/O data Configuring the Module to Receive Peer-to- Peer Data To configure the module to receive Peer-to-Peer data: Step 1. Verify that module parameter 47 (Peer Inp Enable) is set to Off (see figure 4.19). This parameter must be set to Off while you configure the peer input parameters. Configuring the EtherNet/IP Module 4-13

40 Port 5 Device RECOMM-ENET Parameter #: 47 Peer Inp Enable 0 Off Value Setting 0 Off (Default) 1 On Figure 4.19 Peer Input Enable Screen on an LCD OIM Step 2. In module parameters 42 through 45 (Peer Inp Addr 1 through Peer Inp Addr 4), set the IP address of the node from which you want to receive data. See figure Valid nodes must have EtherNet/IP modules connected to drives with compatible logic command/status words. Port 5 Device RECOMM-ENET Parameter #: 42 Peer Inp Addr <> 255 IP Address of Node Transmitting Peer I/O Default = [Peer Inp Addr 1] [Peer Inp Addr 2] [Peer Inp Addr 3] [Peer Inp Addr 4] Figure 4.20 Peer Input Address 1 Screen on an LCD OIM Step 3. Select the destination of the data that is input to the drive as Peer A in module parameter 38 (Peer A Input). See figure Port 5 Device RECOMM-ENET Parameter #: 38 Peer A Input 1 Cmd/Ref Value Description 0 Off (Default) 1 Logic Command/Reference 2-5 Datalink A, B, C, or D Input Figure 4.21 Peer A Input Screen on an LCD OIM If you select a Reference or Datalink as an input, note the following: If a drive that uses a 32-bit Reference and 32-bit Datalinks receives a 16-bit Reference or Datalink, it uses the data in its most significant word, and its least significant word is zero EtherNet/IP Communications Module

41 Step 4. If a drive that uses a 16-bit Reference and 16-bit Datalinks receives a 32-bit Reference or Datalink, it uses the data in the most significant word of the 32-bit Reference or Datalink and ignores the data in the least significant word. If desired, select the destination of the data to input to the drive as Peer B in module parameter 39 (Peer B Input). See figure Port 5 Device RECOMM-ENET Parameter #: 39 Peer B Input 2 DL A Input Value Description 0 Off (Default) 1 Logic Command/Reference 2-5 Datalink A, B, C, or D Input Figure 4.22 Peer B Input Screen on an LCD OIM Step 5. If the module receives a Logic Command, set the bits in module Peer Cmd Mask (40) that the drive should use. See figure The bit definitions for the Logic Command word will depend on the drive to which the module is connected. Refer to Appendix D or drive documentation. Port 5 Device RECOMM-ENET Parameter #: 40 Peer Cmd Mask Bit 0 B00 Value Description 0 Ignore this command bit. (Default) 1 Use this command bit. Figure 4.23 Peer Logic Command Mask Screen on an LCD OIM If the module receives a Logic Command from both a Master device and a Peer device, each command bit must have only one source. The source of command bits set to 0 will be the Master device. The source of command bits set to 1 will be the Peer device. Step 6. Set module Peer Inp Timeout (46) to the maximum amount of time the module will wait for a message before timing out. See figure Important:This value must be greater than the product of Peer Out Time (52) multiplied by Peer Out Skip (53) in the module from which you are receiving I/O. Configuring the EtherNet/IP Module 4-15

42 For example, if the value of Peer Out Time (52) is 2.00 and the value of Peer Out Skip (53) is 2 (see figure 4.18), then parameter 46 (Peer Inp Timeout) needs to have a value greater than 4.00, such as 5.00 (see figure 4.24). Port 5 Device RECOMM-ENET Parameter #: 46 Peer Inp Timeout 5.00 Secs <> Default = Secs Figure 4.24 Peer Input Timeout Screen on an LCD OIM Step 7.! Set the action in parameter 41 (Peer Flt Action) that the module will take if it times out. Figure 4.25 shows the Peer Flt Action Screen on an LCD OIM. Refer to section 4.9 for more information about setting fault actions. ATTENTION: Peer Flt Action (41) lets you determine the action of the module and connected drive if the module times out. By default, this parameter faults the drive if you have configured the module for peerto-peer communication. You can set this parameter so that the drive continues to run. Precautions should be taken to ensure that the setting of this parameter does not create a hazard of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations. Failure to observe this precaution could result in bodily injury and/or damage to equipment. Port 5 Device RECOMM-ENET Parameter #: 41 Peer Flt Action 0 Fault Value Description 0 Fault (Default) 1 Stop 2 Zero Data 3 Hold Last 4 Send Flt Cfg Figure 4.25 Peer Fault Action Screen on an LCD OIM Step 8. Step 9. Set module parameter 47 (Peer Inp Enable) to On. Reset the module. Refer to section 4.11, Resetting the module. The module is now configured to receive Peer I/O from the specified node. Ensure that the specified node is configured to transmit Peer I/O EtherNet/IP Communications Module

43 4.9 Setting a Fault Action There are three user-configurable fault action parameters: Comm Flt Action (21) and Idle Flt Action (22) determine the action of the module and the connected drive if communications are disrupted. By default, these parameters fault the drive if it is using I/ O from the network and communications are disrupted (for example, a cable is disconnected) or the master is idle. Peer Flt Action (41) determines the action of the module and the connected drive if the module times out. By default, this parameter faults the drive if the module has been configured for peer-to-peer communications and the module times out. Table 4.3 lists the response selections for these parameters. Changes to these parameters take effect immediately. A reset is not required. See figure 4.26 for sample LCD OIM Comm Flt Action and Idle Flt Action screens. See figure 4.25 for a sample LCD OIM Peer Flt Action Screen.! ATTENTION: Comm Flt Action (21) and Idle Fault Action (22) let you determine the action of the module and connected drive if communications are disrupted or the controller is idle. By default, these parameters fault the drive. You can set the parameters so that the drive continues to run. Precautions should be taken to ensure that the setting of these parameters does not create a risk of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (e.g., a disconnected cable or faulted controller). Failure to observe this precaution could result in bodily injury and/or damage to equipment. Configuring the EtherNet/IP Module 4-17

44 ! ATTENTION: Parameter 41 (Peer Flt Action) lets you determine the action of the module and connected drive if the module times out. By default, this parameter faults the drive if you have configured the module for peer-to-peer communication. You can set this parameter so that the drive continues to run. Precautions should be taken to ensure that the setting of this parameter does not create a hazard of injury or equipment damage. When commissioning the drive, verify that your system responds correctly to various situations (for example, a disconnected cable). Failure to observe this precaution could result in bodily injury and/or damage to equipment. Table 4.3 Selections for Drive Response to Communication Fault Value Action Description 0 Fault (default) The drive is faulted and stopped (Default). 1 Stop The drive is stopped, but not faulted. 2 Zero Data The drive is sent 0 for output data after a communications disruption. This does not command a stop. 3 Hold Last The drive continues in its present state. 4 Send Flt Cfg The drive is sent the data that you set in the fault configuration parameters, Flt Cfg Logic (25) through Flt Cfg D2 In (34). Port 5 Device RECOMM-ENET Parameter #: 21 Comm Flt Action 0 Fault Port 5 Device RECOMM-ENET Parameter #: 22 Idle Flt Action 0 Fault Figure 4.26 Comm Flt Action Screen and Idle Flt Action Screen on an LCD OIM 4-18 EtherNet/IP Communications Module

45 4.9.1 Setting the Fault Configuration Parameters If you set parameter 21 (Comm Flt Action), 22 (Idle Flt Action), or 14 (Peer Flt Action) to Send Flt Cfg, the values in the parameters shown in table 4.4 are sent to the drive after a communications fault occurs. You must set these parameters to values required by your application. Table 4.4 Fault Configuration Parameters Parameter Number Name Description 25 Flt Cfg Logic A 16-bit value sent to the drive for Logic Command. 26 Flt Cfg Ref A 32-bit value (0 to ) sent to Flt Cfg x1 In Flt Cfg x2 In the drive as a Reference or Datalink. Important: If the drive uses a 16-bit Reference or 16-bit Datalinks, the most significant word of the value must be set to zero (0) or a fault will occur. Changes to these parameters take effect immediately. A reset is not required Setting Web Access Control By accessing the IP address set for the adapter using a web browser, you can view the module s web pages for information about the module, the Reliance Electric drive to which it is connected, and other DPI devices connected to the drive such as OIMs or serial adapters. Additionally, the module can be configured to automatically send messages to desired addresses when selected drive faults occur and/or are cleared, and/or when the module takes a communication or idle fault action. For more details on the modules s web pages, refer to Chapter 9, Viewing the Module s Web Pages. Important:Firmware 2.xxx (and earlier) module web pages are accessed differently than 3.xxx web pages. Enabling/ disabling configuration is also different. Configuring the EtherNet/IP Module 4-19

46 Firmware 2.xxx (and earlier) By default, the firmware 2.xxx (and earlier) module web pages are enabled. To disable the module web pages, use Access Control (54) to set the Web Enable Bit 0 value to 0 (Disabled). You can also protect the configured settings for messaging using Access Control (54). To do this, the value of Config Bit 1 must be 0 (Disabled default). messaging will remain active regardless of whether or not its settings are protected unless messaging was never configured. Port 5 Device RECOMM-ENET Parameter #: 54 Access Control xxxxxxxxxxxxxx0 1 Web Enable b00 Bit Description 0 Web Enable (Default = 1 = enabled) 1 Config (Default = 0 = disabled) 2-31 Not Used Figure 4.27 Example Web Access Control Screen on an LCD OIM Changes to this parameter take effect immediately. A reset is not required. Firmware 3.xxx (and later) By default, the firmware 3.xxx (and later) module web pages are disabled. Refer to Figure 3.1 and set the Web Pages Switch (SW2) to the Enabled Web (UP) position. Important:For a change to the switch setting to take effect, the module must be reset. Bit 0 of Web Features (56) is used to protect the configured settings for notification. By default, settings are not protected and the user can make changes. To protect an configuration, set the value of Cfg Bit 0 to 0 (Disabled). You can unprotect the configuration by changing Bit 0 back to 1 (enabled). notification will always remain active regardless of whether or not its settings are protected unless notification was never configured. Bit 0 is the right-most bit. In figure 4.28 it is highlighted and equals EtherNet/IP Communications Module

47 Port 5 Device RECOMM-ENET Parameter #: 56 Web Features xxxxxxxxxxxxxxx 1 Cfg b00 Bit Description 0 Cfg (Default = 1 = enabled) 1-7 Not Used Figure 4.28 Example Web Access Control Screen on an LCD OIM Changes to this parameter take effect immediately. A reset is not required Resetting the Module Changes to some module parameters require that you reset the module before the new settings take effect. You can reset the module by cycling power to the drive or by using module parameter Reset Module (20).! ATTENTION: If the module is transmitting control I/O to the drive, the drive may fault when you reset the module. Determine how your drive will respond before resetting a connected module. Failure to observe this precaution could result in bodily injury or damage to equipment. Set Reset Module (20) to Reset Module. See figure Port 5 Device RECOMM-ENET Parameter #: 20 Reset Module 1 Reset Module Value Description 0 Ready (default) 1 Reset Module 2 Set Defaults Figure 4.29 Reset Screen on an LCD OIM When you enter 1 (Reset Module), the module will be immediately reset. When you enter 2 (Set Defaults), the module will set all module parameters to their factory-default settings. The module should be reset after performing a Set Defaults. The value of this parameter will be restored to 0 (Ready) after the module is reset or after resetting the defaults. Configuring the EtherNet/IP Module 4-21

48 4.12 Viewing the Module Configuration The parameters in table 4.5 provide information about how the module is configured. You can view these parameters at any time. Table 4.5 Module Configuration Parameters No Name and Description Details 17 EN Rate Act The actual network data rate. Values Type: 18 Ref / Fdbk Size Values: Size of the Reference/Feedback. The drive determines the size of the Reference/Feedback. Type: 19 Datalink Size Values: Size of each Datalink word. The drive determines the size of Datalinks. Type: 24 DPI I/O Act Bit Values: I/O that the module is actively transmitting. The value of this parameter will usually be equal to the Type: value of parameter 23 (DPI I/O Config). Bit Bit Definitions Default x x x = Cmd/Ref 1 = Datalink A 2 = Datalink B 3 = Datalink C 4 = Datalink D 5 = Not Used 6 = Not Used 7 = Not Used 48 Peer Inp Status Values: Status of the consumed peer input connection. Type: 0 = No Link 1 = 10 Mbps Full 2 = 10 Mbps Half 3 = 100 Mbps Full 4 = 100 Mbps Half Read Only 0 = 16-bit 1 = 32-bit Read Only 0 = 16-bit 1 = 32-bit Read Only 0 = I/O disabled 1 = I/O enabled Read Only 0 = Off 1 = Waiting 2 = Running 3 = Faulted Read Only Configuring the EtherNet/IP Module 4-22

49 PWR STS CHAPTER 5 Configuring the Scanner or Bridge Chapter 5 provides instructions on how to configure a ControlLogix bridge to communicate with the module and connected drive. 5.1 Configuring a Simple Network: An Example After the module is configured, the connected drive and module will be a single node on the network. This chapter provides the steps that are needed to configure a simple network like the network in figure 5.1. In our example, we will configure a 1756-ENBT (series A) bridge to communicate with a drive using Logic Command/Status, Reference/ Feedback, and four 16-bit datalinks over the network. IP Address ControlLogix Controller with 1756-ENBT Bridge IP Address SP600 Drive with EtherNet/IP Module Ethernet Switch Computer with Ethernet Connection Figure 5.1 Sample EtherNet/IP Network Configuring the Scanner or Bridge 5-1

50 5.2 Adding a Bridge or Scanner to the I/O Configuration To establish communications over an EtherNet/IP network, you must first add the controller and its scanner or bridge to the I/O configuration. This example uses RSLogix software to do this. Step 1. Start RSLogix The RSLogix 5000 window appears as shown in figure 5.2. Example_RECOMM_ENET Controller Example_RECOMM_ENET Figure 5.2 RSLogix 5000 Window Step 2. In the Control Organizer pane, right-click the I/O Configuration folder and select New Module (figure 5.2). The Select Module Type dialog box (figure 5.3) appears. 5-2 EtherNet/IP Communications Module

51 Figure 5.3 Select Module Type Dialog Box Step 3. In the list, select the EtherNet/IP scanner or bridge used by your controller and then select the major revision of its firmware in the Major Revision box. In this example (figure 5.3), we use a 1756-ENBT EtherNet/IP Bridge (Series A), so the 1756-ENBT/A option is selected. Step 4. Click OK. The Module Properties dialog box (figure 5.4) appears. Figure 5.4 Module Properties Dialog Box - Page 1 Step 5. Edit the fields listed in table 5.1 in the Module Properties Dialog Box. Configuring the Scanner or Bridge 5-3

52 Table 5.1 Module Properties Fields Field Name Slot Revision IP Address Electronic Keying Enter This Information A name to identify the scanner or bridge. The slot of the EtherNet/IP scanner or bridge in the rack. The minor revision of the firmware in the scanner. (You already set the major revision in the Select Module Type dialog box (figure 5.3). The IP address of the EtherNet/IP scanner or bridge. Compatible Module. This setting for Electronic Keying ensures the physical module is consistent with the software configuration before the controller and scanner or bridge make a connection. Therefore, ensure that you have set the correct revision in this dialog box. Refer to the online Help if the controller and scanner have problems making a connection and you want to change this setting. Step 6. Click Finish>>. The scanner or bridge is now configured for the EtherNet/IP network. It appears in the I/O Configuration folder. In our example, a 1756-ENBT bridge appears under the I/O Configuration folder (figure 5.5). Figure 5.5 RSLogix 5000: I/O Configuration Folder 5.3 Adding the Module and Drive to the I/O Configuration To transmit data between the scanner or bridge and the module, you must add the RECOMM-ENET module as a child device of the scanner or bridge. Step 1. In the Control Organizer pane, right-click on the scanner or bridge and select New Module (figure 5.6). In our example, we right-click on the 1756-ENBT/A bridge. 5-4 EtherNet/IP Communications Module

53 Figure 5.6 Right Clicking the Scanner The Select Module Type dialog box (figure 5.7) appears. Figure 5.7 Select Module Type Dialog Box Step 2. Select module type ETHERNET-MODULE (Generic Ethernet Module) to configure a RECOMM-ENET module (figure 5.7), and then click OK. The Module Properties dialog box (figure 5.8) appears. Configuring the Scanner or Bridge 5-5

54 SP600 Figure 5.8 Module Properties Dialog Box - Page 1 Step 3. Edit the fields listed in table 5.2. Table 5.2 Edit Module Properties Field Enter This Information Name A name to identify the module and drive. Comm. Format Data - INT. This setting formats the data in 16-bit words. IP Address The IP address of the module. Step 4. Under Connection Parameters, edit the fields listed in table 5.3. Table 5.3 Edit Connection Parameters Field Input Output Configuration Assembly Instance Column 1 (This value is required.) 2 (This value is required.) 6 (This value is required.) Size Column The value will vary based on your application (setting of parameters 23 (I/O Config) and 36 (M-S Output) and the size (16- or 32- bit) of the Reference/Feedback and Datalinks in the drive. Refer to tables 5.4 and 5.5. The value will vary based on your application (setting of Parameters 23 - [I/O Config] and 35 - [M-S Input]) and the size (16- or 32-bit) of the Reference/Feedback and Datalinks in the drive. Refer to tables 5.4 and (This value is required.) 5-6 EtherNet/IP Communications Module

55 Tables 5.4 and 5.5 define the number of 16-bit words that you need for input and output depending on your configuration. Table 5.4 SP600 and LiquiFlo 2.0 (16-Bit Reference/Feedback and Datalinks) Input Size Output Size Logic Command/ Status Reference/ Feedback (16-bit) Datalinks (16-bit) A B C D Table 5.5 GV Bit Reference/Feedback and 32-bit Datalinks) Input Size Output Size Logic Command/ Status Reference/ Feedback (16-bit) Datalinks (32-bit) A B C D Note: For instructions on configuring the I/O for the module (I/O Config (23)) and the Master-Slave Hierarchy (M-S Input (35) and M- S Output (36)), refer to chapter 4, Configuring the Module. Step 5. Click Next > to display the next page as shown in figure 5.9. Figure 5.9 Module Properties Dialog Box - Page 2 Configuring the Scanner or Bridge 5-7

56 Step 6. Step 7. In the Requested Packet Interval (RPI) field, set the value to 5.0 milliseconds or greater. This value determines the maximum interval that a controller should use to move data to or from the module. To conserve bandwidth, use higher values for communicating with low priority devices. Click Finish>>. The new node ( SP600 in this example) now appears under the scanner or bridge ( 1756-ENBT in this example) in the I/O Configuration folder. If you double-click the Data Types folder and then doubleclick on the Module-Defined folder, you will see that module-defined data types and tags have been automatically created. After you save and download the configuration, these tags allow you to access the Input and Output data of the module via the controller s ladder logic. SP600 Figure 5.10 RSLogix Data Types and I/O Configuration Folders 5-8 EtherNet/IP Communications Module

57 5.4 Saving the Configuration After adding the scanner or bridge and the module to the I/O configuration, you must download the configuration to the controller. You should also save the configuration to a file on your computer. Step 1. Select Communications > Download. The Download dialog box (figure 5.11) appears. Example_RECOMM_ENET Figure 5.11 Download Dialog Box Note: If a message box reports that RSLogix is unable to go online, select Communications > Who Active to try to find your controller in the Who Active dialog box. If it does not appear, you need to add or configure the EtherNet/IP driver in RSLinx. Refer to the RSLinx online help. Step 2. Step 3. Click Download to download the configuration to the controller. When the download is completed successfully, RSLogix enters online mode and the I/O OK box in the upper-left part of the screen is green. Select File > Save. If this is the first time that you saved the project, the Save As dialog box appears. Navigate to a folder, type a file name, and click Save to save the configuration to a file on your computer. Configuring the Scanner or Bridge 5-9

58 5-10 EtherNet/IP Communications Module

59 CHAPTER 6 Using I/O Messaging Chapter 6 provides information and examples that explain how to use a ControlLogix controller to send I/O Messaging to control, configure, and monitor an SP600, GV6000 or LiquiFlo 2.0 drive.! ATTENTION: Risk of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication. Important: At the time of publication, only ControlLogix controllers are able to transmit I/O data over an EtherNet/IP network. PLC-5 and SLC controllers cannot transmit EtherNet/IP I/O data. However, these controllers can perform control using explicit messaging to the Register object and PCCC N41 and N42 files. 6.1 About I/O Messaging On EtherNet/IP networks, I/O messaging is used to transfer the data that controls the Reliance Electric drive and sets its reference. I/O can also be used to transfer data to and from Datalinks in Reliance Electric drives. The module provides the following options for configuring and using I/O: The size of I/O can be configured by enabling or disabling the Logic Command/Reference and Datalinks. A Master-Slave hierarchy or a Peer-to-Peer hierarchy can be set up. Using I/O Messaging 6-1

60 Chapter 4, Configuring the Module, and chapter 5, Configuring the Scanner or Bridge, discuss how to configure the module and scanner or bridge on the network for these options. The Glossary defines the different options. This chapter discusses how to use I/O after you have configured the module and scanner or bridge. 6.2 Understanding the I/O Image The terms input and output are defined from the scanner s point of view. Therefore, Output I/O is data that is output from the scanner and consumed by the EtherNet/IP module. Input I/O is status data that is produced by the module and consumed as input by the scanner. The I/O image table will vary based on the following: Size (either 16-bit or 32-bit) of the Reference/Feedback words and Datalink words used by the drive. Configuration of I/O (DPI I/O Config (23)). If all I/O is not enabled, the image table is truncated. The image table always uses consecutive words starting at word EtherNet/IP Communications Module

61 Figure 6.1 illustrates an example of an I/O image with 16-bit words. EtherNet/IP Scanner DPI Controller Output Image (Write) Module Word and I/O 0 Logic Command 1 Reference 2 Datalink In A1 3 Datalink In A2 4 Datalink In B1 5 Datalink In B2 6 Datalink In C1 7 Datalink In C2 8 Datalink In D1 9 Datalink In D2 Reliance Electric Drive Logic Command Reference Data In A1 Data In A2 Data In B1 Data In B2 Data In C1 Data In C2 Data In D1 Data In D2 Input Image (Read) Message Handler 0 Pad Word (1) 1 Pad Word (1) 2 Logic Status 3 Feedback 4 Datalink Out A1 5 Datalink Out A2 6 Datalink Out B1 7 Datalink Out B2 8 Datalink Out C1 9 Datalink Out C2 10 Datalink Out D1 11 Datalink Out D2 Message Buffer Logic Status Feedback Data Out A1 Data Out A2 Data Out B1 Data Out B2 Data Out C1 Data Out C2 Data Out D1 Data Out D2 Message Handler 1 Required by ControlLogix. May or may not be required by other controllers. Figure 6.1 ControlLogix I/O Image with All I/O Enabled (Example 1) In figure 6.1, the configuration illustrates using 10 words of output and 12 words of input (the module adds two pad words at the beginning of the input). Depending on your application needs, this may vary. Using I/O Messaging 6-3

62 For example, an image that uses 32-bit words for Reference and four Datalinks would change the I/O image in figure 6.1 as follows: Word Output I/O Word Input I/O 0 Logic Command/Status 0-1 Pad Word 1 Pad Word 2 Logic Command/Status 2-3 Reference/Feedback 3 Pad Word 4-7 Datalink A1/A2 4-5 Reference/Feedback 8-11 Datalink B1/B2 6-9 Datalink A1/A Datalink C1/C Datalink B1/B Datalink D1/D Datalink C1/C Datalink D1/D2 An image that uses a 16-bit Reference and 32-bit Datalinks would change the I/O image in figure 6.1 as follows: Word Output I/O Word Input I/O 0 Logic Command/Status 0-1 Pad Word 1 Pad Word 2 Logic Command/Status 2 Reference/Feedback 3 Pad Word 3 Pad Word 4-5 Reference/Feedback 4-7 Datalink A1/A2 6-9 Datalink A1/A Datalink B1/B Datalink B1/B Datalink C1/C Datalink C1/C Datalink D1/D Datalink D1/D2 As another example, figure 6.2 illustrates an I/O image that does not use all of the I/O data. Only the Logic Command/Reference and Datalink B are enabled. In this example, the reference is a 32-bit word, and Datalinks are 16-bit words. 6-4 EtherNet/IP Communications Module

63 EtherNet/IP Scanner Module Word and I/O DPI Controller Output Image (Write) 0 Logic Command 1 Pad Word 2 Reference (LSW) (2) 3 Reference (MSW) (2) 4 Datalink In B1 5 Datalink In B2 Reliance Electric Drive Logic Command Reference Data In A1 Data In A2 Data In B1 Data In B2 Data In C1 Data In C2 Data In D1 Data In D2 Input Image (Read) Message Handler 0 Pad Word (1) 1 Pad Word (1) 2 Logic Status 3 Pad Word 4 Feedback (LSW) 5 Feedback (MSW) 6 Datalink Out B1 7 Datalink Out B2 Message Buffer Logic Status Feedback Data Out A1 Data Out A2 Data Out B1 Data Out B2 Data Out C1 Data Out C2 Data Out D1 Data Out D2 Message Handler 1 Required by ControlLogix. May or may not be required by other controllers. 2 LSW is Least Significant Word (Bits 15-0). MSW is Most Significant Word (Bits 31-16). Figure 6.2 ControlLogix I/O Image (Example 2) 6.3 Using Logic Command/Status When enabled, the Logic Command/Status word is always word 0 in the output image and word 2 in the input image. The Logic Command is a 16-bit word of control produced by the scanner and consumed by the module. The Logic Status is a 16-bit word of status produced by the module and consumed by the scanner. This manual contains the bit definitions for compatible products available at the time of publication in Appendix D, Logic Command/ Status Words. For other products, refer to their documentation. Using I/O Messaging 6-5

64 6.4 Using Reference/Feedback When enabled, Reference/Feedback begins at word 1 (16-bit) or word 2 (32-bit) in the I/O image. The reference (16 bits or 32 bits) is produced by the controller and consumed by the adapter. The feedback (16 bits or 32 bits) is produced by the adapter and consumed by the controller. The size of the Reference/Feedback is determined by the drive and displayed in Ref/Fdbk Size (18) in the adapter. Size Valid Values In I/O Image 16-bit to Word 1 32-bit to Word 2 and Word 3 The Reference value is a scaled value; it is not an engineering value. For example, in Reliance Electric drives, the Reference is scaled based on the value of Maximum Freq (55) where 32,767 equals the Maximum frequency value, and 0 equals 0 Hz. Note that the commanded maximum speed can never exceed the value of Maximum Speed (82). The below table shows example references and their results on a drive that has its Maximum Freq (55) set to 130 Hz and Maximum Speed (82) set to 60 Hz. Reference Value Scale Percent Value Output Speed Feedback Value % 130 Hz 60 Hz % 65 Hz 60 Hz % 32.5 Hz 32.5 Hz % 0 Hz 0 Hz 0 1. A value of is equivalent to the Parameter 55 frequency value. The effects of values greater than depend on whether the DPI product uses a bipolar or unipolar direction mode. Refer to the documentation for your DPI product. 2. The drive runs at 60 Hz instead of 130 Hz or 65 Hz because Parameter 82 - [Maximum Speed] sets 60 Hz as the maximum speed. 3. The Feedback value is also scaled based on the value of Parameter 55 - [Maximum Freq], For example, 60/130 = 0.46 so x 0.46 = For Reference/Feedback details about other DPI Hosts, refer to their respective User Manuals. 6-6 EtherNet/IP Communications Module

65 6.5 Using Datalinks A Datalink is a mechanism used by Reliance Electric drives to transfer data to and from the controller. Datalinks allow a parameter value to be changed without using an Explicit Message. When enabled, each Datalink consumes either two 16-bit or 32-bit words in both the input and output image depending on its size. The size of Datalinks (16-bit words or 32-bit words) is determined by the drive and displayed in Datalink Size (19) in the module. Rules for Using Datalinks Each set of Datalink parameters in a Reliance Electric drive can be used by only one module. If more than one module is connected to a single drive, multiple modules must not try to use the same Datalink. Parameter settings in the drive determine the data passed through the Datalink mechanism. Refer to the documentation for your drive. When you use a Datalink to change a value, the value is not written to the Non-Volatile Storage (NVS). The value is stored in volatile memory and lost when the drive loses power. Thus, use Datalinks when you need to change a value of a parameter frequently. Using I/O Messaging 6-7

66 Bit Parameters using 16-Bit Datalinks To read (and/or write) a 32-bit parameter using 16-bit Datalinks, typically both Datalinks of a pair (x1 and x2) are set to the same 32- bit parameter. For example, to read Elapsed MWh (9) in an SP600 drive, both Datalink A1 and A2 are set to 9. Datalink A1 will contain the least significant word (LSW) and Datalink A2 the most significant word (MSW). In this example, the parameter 9 value of 5.8 MWh is read as a 58 in Datalink A1. Datalink Most/Least Significant Word Parameter Data (decimal) A1 LSW 9 58 A2 MSW 9 0 Regardless of the Datalink combination, x1 will always contain the LSW and x2 will always contain the MSW. In the following examples Power Up Marker (242) contains a value of hours. Datalink Most/Least Significant Word Parameter Data (decimal) A1 LSW A2 - Not Used Datalink Most/Least Significant Word Parameter Data (decimal) A1 - Not Used A2 MSW Datalink Most/Least Significant Word Parameter Data (decimal) A2 MSW B1 LSW bit data is stored in binary as follows: MSW 2 31 through 2 16 LSW 2 15 through 2 0 Example: Power Up Marker (242) = hours MSW = 13 decimal = 1101 binary = = LSW = = EtherNet/IP Communications Module

67 6.6 Sample Ladder Logic Program The sample ladder logic program works with a ControlLogix controller and an SP600 drive Function of the Sample Program With this program, you can perform the following actions: Obtain Logic Status information from the drive. Use the Logic Command to control the drive (for example, start). Send a Reference to the drive and receive Feedback from the drive. Transmit Datalink data to and from the drive. Table 6.1 Parameter Settings for the Sample Program Device Parameter Name Value Description SP600 Drive RECOMM- ENET Module 90 Speed Ref A Sel 22 DPI Port 5 (RECOMM-ENET) 300 Data In A1 140 Points to Par (Accel Time 1) 301 Data In A2 142 Points to Par (Decel Time 1) 302 Data In B1 100 Points to Par (Jog Speed) 303 Data In B2 155 Points to Par (Stop Mode A) 304 Data In C1 101 Points to Par (Preset Speed 1) 305 Data In C2 102 Points to Par (Preset Speed 2) 306 Data In D1 103 Points to Par (Preset Speed 3) 307 Data In D2 104 Points to Par (Preset Speed 4) 310 Data Out A1 140 Points to Par (Accel Time 1) 311 Data Out A2 142 Points to Par (Decel Time 1) 312 Data Out B1 100 Points to Par (Jog Speed) 313 Data Out B2 155 Points to Par (Stop Mode A) 314 Data Out C1 101 Points to Par (Preset Speed 1) 315 Data Out C2 102 Points to Par (Preset Speed 2) 316 Data Out D1 103 Points to Par (Preset Speed 3) 317 Data Out D2 104 Points to Par (Preset Speed 4) IP Addr Cfg IP Address for the module 23 DPI I/O Cfg xxx Enables Cmd/Ref, Datalinks A-D 35 M-S Input xxx Configures the I/O Data to be transferred from the controller on the network to the drive. 36 M-S Output xxx Configures the I/O Data to be transferred from the drive to the controller on the network. Using I/O Messaging 6-9

68 6.7 RSLogix 5000 Configuration Controller Tags When you add the module and drive to the I/O configuration (refer to chapter 5), RSLogix 5000 software automatically creates controller tags for them. In this example program, the following controller tags are used. SP600:C SP600:I SP600:O Figure 6.3 Controller Tags for the Sample ControlLogix Ladder Logic Program You can expand the Output and Input tags to reveal the output and input configuration. The Output tag for this sample program requires ten 16-bit words of data (see figure 6.4). The Input tag for this example requires twelve 16-bit words of data (see figure 6.5). SP600:C SP600:I SP600:O SP600:O.Data SP600:O.Data[0] SP600:O.Data[1] SP600:O.Data[2] SP600:O.Data[3] SP600:O.Data[4] SP600:O.Data[5] SP600:O.Data[6] SP600:O.Data[7] SP600:O.Data[8] SP600:O.Data[9] SP600 Output Image Ta... SP600 Logic Command SP600 Reference SP600 Datalink A1 In SP600 Datalink A2 In SP600 Datalink B1 In SP600 Datalink B2 In SP600 Datalink C1 In SP600 Datalink C2 In SP600 Datalink D1 In SP600 Datalink D2 In Figure 6.4 Output Image for the Sample ControlLogix Ladder Logic Program 6-10 EtherNet/IP Communications Module

69 SP600:C SP600:I SP600:I.Data SP600:I.Data[0] SP600:I.Data[1] SP600:I.Data[2] SP600:I.Data[3] SP600:I.Data[4] SP600:I.Data[5] SP600:I.Data[6] SP600:I.Data[7] SP600:I.Data[8] SP600:I.Data[9] SP600:I.Data[10] SP600:I.Data[11] SP600 Input Image Table System Overhead System Overhead SP600 Logic Status SP600 Feedback SP600 Datalink A1 Out SP600 Datalink A2 Out SP600 Datalink B1 Out SP600 Datalink B2 Out SP600 Datalink C1 Out SP600 Datalink C2 Out SP600 Datalink D1 Out SP600 Datalink D2 Out Figure 6.5 Input Image for the Sample ControlLogix Ladder Logic Program Program Tags In addition to the Controller tags that are automatically created, you need to create the Program tags shown in figure 6.6 for this sample program. SP600 Speed Feedback SP600 Speed Reference Figure 6.6 Program Tags for Sample ControlLogix Ladder Logic Program 6.8 Logic Command/Status Words This example uses the Logic Command word and Logic Status word for SP600 drives. Refer to Appendix D, Logic Command/ Status Words, to view these. The definition of the bits in these words may vary if you are using a different DPI product. Refer to the documentation for your product. Using I/O Messaging 6-11

70 6.9 Sample ControlLogix Ladder Logic Program S600 Logic Status Word bit 01 (ACTIVE) SP600:I.Data[2].1 SP600 Logic Status Word bit 07 (FAULT) SP600:I.Data[2].7 DriveCommandStop DriveCommandStart DriveCommandJog DriveCommandClearFault DriveStatusRunning DriveStatusFaulted SP600 Speed Feedback Copy File Source COP SP600:I.Data[3] Dest DriveFeedback Length 1 SP600 Logic Command bit 00 (STOP) SP600:O.Data[0].0 SP600 Logic Command bit 01 (START) SP600:O.Data[0].1 SP600 Logic Command bit 02 (JOG) SP600:O.Data[0].2 SP600 Logic Command bit 03 (CLEAR FAULTS) SP600:O.Data[0].3 Transfer Speed Reference data to the SP600 drive. SP600 Reference 7 Copy File Source COP DriveReference Dest SP600:O.Data[1] Length 1 Read Datalink A-D data from the SP600 drive (Data Out A1 - Data Out D2). SP600 Datalink A1 Out COP 8 Copy File Source SP600:I.Data[4] Dest DatalinkDataFromDrive[0] Length 8 Figure 6.7 Sample ControlLogix Ladder Logic Program for I/O Messaging 6-12 EtherNet/IP Communications Module

71 Write Datalink A-D data to the SP600 drive (Data In A1 - Data In D2). SP600 Datalink A1 In 9 Copy File Source COP DatalinkDataToDrive[0] Dest SP600:O.Data[2] Length 8 (End) Figure 6.8 Sample ControlLogix Ladder Logic Program for I/O Messaging (Continued) 6.10 Sample Datalink Data The following figure shows the Datalink data used in the sample program. SP600 Datalink A1 Out SP600 Datalink A2 Out SP600 Datalink B1 Out SP600 Datalink B2 Out SP600 Datalink C1 Out SP600 Datalink C2 Out SP600 Datalink D1 Out SP600 Datalink D2 Out SP600 Datalink A1 In SP600 Datalink A2 In SP600 Datalink B1 In SP600 Datalink B2 In SP600 Datalink C1 In SP600 Datalink C2 In SP600 Datalink D1 In SP600 Datalink D2 In Figure 6.9 Sample Datalink Data for the Sample Ladder Logic Program Using I/O Messaging 6-13

72 6-14 EtherNet/IP Communications Module

73 CHAPTER 7 Using Explicit Messaging Chapter 7 provides information and examples that explain how to use Explicit Messaging to configure and monitor a Reliance Electric drive and an EtherNet/IP module.! ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication. Failure to observe this precaution could result in bodily injury and/or damage to equipment. ATTENTION: If Explicit Messages are programmed to write parameter data to Non-Volatile Storage (NVS) frequently, the NVS will quickly exceed its life cycle and cause the drive to malfunction. Do not create a program that frequently uses Explicit Messages to write parameter data to NVS. Datalinks do not write to NVS and should be used for frequently changed parameters. Failure to observe this precaution could result in bodily injury and/or damage to equipment. Refer to chapter 6 for information about the I/O Image, using Logic Command/Status, Reference/Feedback, and Datalinks. 7.1 About Explicit Messaging Explicit Messaging is used to transfer data that does not require continuous updates. With Explicit Messaging, you can configure and monitor a slave device s parameters on the EtherNet/IP network. Using Explicit Messaging 7-1

74 7.2 Formatting Explicit Messages Explicit Messages for the ControlLogix Controller ControlLogix scanners and bridges accommodate both downloading Explicit Message Requests and uploading Explicit Message Responses. The scanner or bridge module can accommodate one request or response for each transaction block. Each transaction block must be formatted as shown in figure 7.1. ➓ ➊ ➋ ➌ ➎ ➍ ➏ ➐ ➑ ➒ Box ➊ ➋ ➌ Description Message Type The message type is usually CIP Generic. Service Type The service type indicates the service (for example, Get Attribute Single or Set Attribute Single) that you want to perform. Available services depend on the class and instance that you are using. Refer to Appendix C EtherNet/IP Objects. Service Code The service code is the code for the requested EtherNet/IP service. This value changes based on the Service Type that has been selected. In most cases, this is a read-only box. If you select Custom in the Service Type box, then you need to specify a service code in this box (for example, 4B for a Get Attributes Scattered service or 4C for a Set Attributes Scattered service). Figure 7.1 ControlLogix Message Format in RSLogix EtherNet/IP Communications Module

75 Box ➍ ➎ ➏ ➐ ➑ ➒ ➓ Description Class The class is an EtherNet/IP class. Refer to Appendix C, EtherNet/IP Objects, for available classes. Instance The instance is an instance (or object) of an EtherNet/IP class. Refer to Appendix C, EtherNet/IP Objects, for available instances for each class. Attribute The attribute is a class or instance attribute. Refer to Appendix C, Ethernet/IP Objects, for available attributes for each class or instance. Source Element This box contains the name of the tag for any service data to be sent from the scanner or bridge to the module and drive. Source Length This box contains the number of bytes of service data to be sent in the message. Destination This box contains the name of the tag that will receive service response data from the module and drive. Path The path is the route that the message will follow. Note: Click Browse to find the path or type in the name of a module that you previously mapped. Name The name for the message. Figure 7.1 ControlLogix Message Format in RSLogix 5000 (Continued) Note: To display the Message Configuration dialog box in RSLogix 5000, add a message instruction (MSG), create a new tag for the message (properties: Base tag type, MESSAGE data type, controller scope), and click the Configure button. 7.3 Performing Explicit Messages There are five basic events in the Explicit Messaging process defined below. The details of each step will vary depending on the controller. Refer to the documentation for your controller. Important: There must be a request message and a response message for all Explicit Messages, whether you are reading or writing data. Using Explicit Messaging 7-3

76 ➎ Complete Explicit Message ➍ Retrieve Explicit Message Response ➊ Set up and send Explicit Message ➋ ➌ ➊ ➋ ➌ ➍ ➎ Format the required data and set up the ladder logic program to send an Explicit Message request to the scanner or bridge module (download). The scanner or bridge module transmits the Explicit Message Request to the slave device over the EtherNet/IP network. The slave device transmits the Explicit Message Response back to the master. The controller retrieves the Explicit Message Response. It may be required to repeat steps 1-3, depending on the amount of data. The Explicit Message is complete. Figure 7.2 Explicit Message Process Note: The scanner module may be integrated with the controller (for example, ControlLogix). 7-4 EtherNet/IP Communications Module

77 7.4 About the Explicit Message Examples These examples show how to format and execute the following types of Explicit Messages using a ControlLogix controller: Get Attribute Single Set Attribute Single Get Attributes Scattered Set Attributes Scattered Message Formats When formatting a message example, refer to Formatting Explicit Messages in this chapter for an explanation of the content of each box. Also, to format and execute these message examples, you need the Controller tags displayed in figure 7.3. SP600:C SP600:I SP600:O Ladder Logic Rungs Figure 7.3 Controller Tags for Explicit Messages The ladder logic rungs for the examples in this chapter can be appended after rung 9 in the ladder logic program (figure 6.7) in chapter 6, Using I/O Messaging. Source and Destination Data The values in the examples that appear in this chapter for the source and destination data may vary in your application. Using Explicit Messaging 7-5

78 7.4.1 Get Attribute Single Message Example A Get Attribute Single message reads a single attribute value. In this example, we read the value of a parameter in an SP600 drive. Message Format Example SP600 Figure 7.4 Message Format for a Get Attribute Single Message Table 7.1 identifies key settings for the message format: Table 7.1 Settings for Message Format Configuration Value Description Page Service Type 1 Service Code 1 Class Instance Attribute Destination Get Attribute Single e (Hex.) 93 (Hex.) 1 (Dec.) 9 (Hex.) GetAttributeSingleData Read Parameter data Code for Get_Attribute_Single DPI Parameter Object Parameter 1 (Output Freq) Parameter Value Controller tag for response data C-24 C-10 C-20 C-20 C The default setting for Service Type is Custom, which enables you to enter a Service Code that is not available from the Service Type pulldown menu. When you select a Service Type other than Custom from the pulldown menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (inaccessible). 7-6 EtherNet/IP Communications Module

79 Ladder Logic Rung Example Get Attribute Single Message Example 10 PerformGetAttributeSingle Get Attribute Single Service MSG Type - CIP Generic Message Control GetAttributeSingle... EN DN ER Figure 7.5 Get Attribute Single Message Example Destination Data Example In this example, the Get Attribute Single message reads Output Freq (1) in the drive and returns its value to the destination tag named GetAttributeSingleData. Figure 7.6 Example of Destination Data from a Get Attribute Single Message The output frequency is 32.5 Hz. Using Explicit Messaging 7-7

80 7.4.2 Set Attribute Single Message Example A Set Attribute Single message writes a value for a single attribute. In this example, we write the value of a parameter in an SP600 drive. Message Format Example SP600 Figure 7.7 Message Format for a Set Attribute Single Message Table 7.2 identifies key settings for the data format: Table 7.2 Key Settings for Data Format Configuration Value Description Page Service Type 1 Service Code 1 Class Instance Attribute Source Element Source Length Set Attribute Single 10 (Hex.) 93 (Hex.) 107 (Dec.) 9 (Hex.) SetAttributeSingleData 2 bytes Write parameter data Code for Set_Attribute_Single DPI Parameter Object Parameter 107 (Preset Speed 7) Parameter Value Controller tag for write data One 16-bit word of data is sent C-24 C-10 C-20 C-20 C The default setting for Service Type is Custom, which enables you to enter a Service Code that is not available from the Service Type pulldown menu. When you select a Service Type other than Custom from the pulldown menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (inaccessible). 7-8 EtherNet/IP Communications Module

81 Ladder Logic Rung Example 11 PerformSetAttributeSingle Set Attribute Single Service MSG Type - CIP Generic Message Control SetAttributeSingle... EN DN ER Figure 7.8 Set Attribute Single Message Example Example Source Data In this example, the Set Attribute Single message writes 599, the value in the source tag named SetAttributeSingleData, to Preset Speed 7 (107) in the drive. Figure 7.9 Example of Source Data from Set Attribute Single Message 59.9 Hz is written to the parameter. Using Explicit Messaging 7-9

82 7.4.3 Get Attributes Scattered Message Example A Get Attributes Scattered message reads the values of multiple attributes. In this example, we read the values of various parameters in an SP600 drive. Message Format Example SP600 Figure 7.10 Message Format for a Get Attributes Scattered Message The following table identifies key settings for the message format: Table 7.3 Key Settings for Message Format Configuration Value Description Page Service Type 1 Service Code 1 Class Instance Attribute Source Element Source Length Destination Custom 4B 93 (Hex.) 0 (Dec.) 0 (Hex.) GetScatteredRequestData 30 Bytes GetScatteredResponseData Required for scattered messages Code for Get Attributes Scattered DPI Parameter Object Required for scattered messages Required for scattered messages Controller tag for request data Fifteen 16-bit words of data Controller tag for response data C-24 C The default setting for Service Type is Custom, which enables you to enter a Service Code that is not available from the Service Type pulldown menu. When you select a Service Type other than Custom from the pulldown menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (inaccessible) EtherNet/IP Communications Module

83 Ladder Logic Rung Example 12 PerformGetAttributesScattered Get Attributes Scattered Service MSG Type - CIP Generic Message Control GetAttributesScattered... EN DN ER Figure 7.11 Example of Get Attributes Scattered Message Explanation of Source and Destination Data The data structures in figure 7.13 uses 16-bit words and can get up to twenty-two parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated parameter value field contains an error code. Request (Source Data) Response (Destination Data) Word 0 Parameter Number Word 0 Parameter Number 1 Pad Word 1 Parameter Value LSW 2 Pad Word 2 Parameter Value MSW 3 Parameter Number 3 Parameter Number 4 Pad Word 4 Parameter Value LSW 5 Pad Word 5 Parameter Value MSW 6 Parameter Number 6 Parameter Number 7 Pad Word 7 Parameter Value LSW 8 Pad Word 8 Parameter Value MSW 9 Parameter Number 9 Parameter Number 10 Pad Word 10 Parameter Value LSW 11 Pad Word 11 Parameter Value MSW 12 Parameter Number 12 Parameter Number 13 Pad Word 13 Parameter Value LSW 14 Pad Word 14 Parameter Value MSW 15 Parameter Number 15 Parameter Number 16 Pad Word 16 Parameter Value LSW 17 Pad Word 17 Parameter Value MSW Parameter Number 63 Parameter Number 64 Pad Word 64 Parameter Value LSW 65 Pad Word 65 Parameter Value MSW Figure 7.12 Data Structure for Get Scattered Attributes Messages Using Explicit Messaging 7-11

84 Source Data Example In this example, we use the data structure in figure 7.13 in the source tag named GetScatteredRequestData to read the following five parameters: Output Freq (1) Output Current (3) Output Voltage (6) DC Bus Voltage (12) Analog In1 Value (17) Figure 7.13 Source Data Example 7-12 EtherNet/IP Communications Module

85 Destination Data Example The Get Attributes Scattered message reads the multiple parameters and returns their values to the destination tag (GetScatteredResponseData). Figure 7.14 Destination Data Example In this example, the parameters have the following values: Drive Parameter Output Freq (1) Output Current (3) Output Voltage (6) DC Bus Voltage (12) Analog In2 Value (17) 32.5 Hz 0.1 Amp VAC VDC ma Value Using Explicit Messaging 7-13

86 7.4.4 Set Attributes Scattered Message Example A Set Attributes Scattered message writes values to multiple attributes. In this example, we write the values of various parameters in an SP600 drive. Example Message Format SP600 Figure 7.15 Message Format for a Set Attributes Scattered Message The following table identifies key settings for the message format: Table 7.4 Message Format Settings Configuration Value Description Page Service Type 1 Service Code 1 Class Instance Attribute Source Element Source Length Destination Custom 4C 93 (Hex.) 0 (Dec.) 0 (Hex.) SetScatteredRequestData 30 Bytes SetScatteredResponseData Required for scattered messages Code for Get Attributes Scattered DPI Parameter Object Required for scattered messages Required for scattered messages Controller tag for request data Fifteen 16-bit words of data Controller tag for response data C-24 C The default setting for Service Type is Custom, which enables you to enter a Service Code that is not available from the Service Type pulldown menu. When you select a Service Type other than Custom from the pulldown menu, an appropriate Hex. value is automatically assigned to the Service Code box which grays out (inaccessible) EtherNet/IP Communications Module

87 Ladder Logic Rung Example 13 PerformSetAttributesScattered Set Attributes Scattered Service MSG Type - CIP Generic Message Control SetAttributesScattered... EN DN ER Figure 7.16 Set Attributes Scattered Message Example Explanation of Source and Destination Data The data structures in figure 7.17 use 16-bit words and can set up to twenty-two parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated pad word field contains an error code. Request (Source Data) Response (Destination Data) Word 0 Parameter Number Word 0 Parameter Number 1 Parameter Value LSW 1 Pad Word or Error Code 2 Parameter Value MSW 2 Pad Word 3 Parameter Number 3 Parameter Number 4 Parameter Value LSW 4 Pad Word or Error Code 5 Parameter Value MSW 5 Pad Word 6 Parameter Number 6 Parameter Number 7 Parameter Value LSW 7 Pad Word or Error Code 8 Parameter Value MSW 8 Pad Word 9 Parameter Number 9 Parameter Number 10 Parameter Value LSW 10 Pad Word or Error Code 11 Parameter Value MSW 11 Pad Word 12 Parameter Number 12 Parameter Number 13 Parameter Value LSW 13 Pad Word or Error Code 14 Parameter Value MSW 14 Pad Word 15 Parameter Number 15 Parameter Number 16 Parameter Value LSW 16 Pad Word or Error Code 17 Parameter Value MSW 17 Pad Word Parameter Number 63 Parameter Number 64 Parameter Value LSW 64 Pad Word 65 Parameter Value MSW 65 Pad Word Figure 7.17 Data Structures for Set Attributes Scattered Message Using Explicit Messaging 7-15

88 Source Data Example In this example, we use the data structure in figure 7.18 in the source tag (SetScatteredRequestData) to write new values for these parameters: Drive Parameter Accel Time 2 (141) Decel Time 2 (143) Preset Speed 5 (105) Preset Speed 6 (106) Preset Speed 7 (107) 11.1 sec 22.2 sec 33.3 Hz 44.4 Hz 55.5 Hz Value Figure 7.18 Source Data Example 7-16 EtherNet/IP Communications Module

89 Example Destination Data The results of the message appear in the destination tag named SetScatteredResponseData. Values of 0 indicate no errors occurred. Figure 7.19 Destination Data Example Using Explicit Messaging 7-17

90 7-18 EtherNet/IP Communications Module

91 CHAPTER 8 Troubleshooting the Module and Network Chapter 8 contains information for troubleshooting the EtherNet/IP module and the network. 8.1 Understanding the Status Indicators The module has four status indicators. They can be viewed on the module or through the drive cover. ➊ ➋ ➌ ➍ ➊ ➋ ➌ ➍ Number Status Indicator Description Refer to... ➊ DRIVE DPI Connection Status Section ➋ MS Module Status Section ➌ NET A EtherNet/IP Section Connection Status ➍ NET B EtherNet/IP Transmit Status Section Table 8.1 Status Indicators (Location on Drive May Vary) Troubleshooting the Module and Network 8-1

92 8.1.1 DRIVE Status Indicator Table 8.2 DRIVE Status Indicator: State Definitions Status Cause Corrective Action Off The module is not powered or is not connected properly to the drive. Securely connect the module to the drive using the ribbon cable. Flashing Red Solid Red Orange Flashing Green Solid Green The module is not receiving a ping message from the drive. The drive has refused an I/O connection from the module. Another DPI peripheral is using the same DPI port as the module. The module is connected to a product that does not support Reliance Electric DPI communications. The module is establishing an I/O connection to the drive. The module is properly connected and is communicating with the drive. Apply power to the drive. Verify that cables are securely connected. Cycle power to the drive. Important: Cycle power to the product after making any of the following corrections: Verify that all DPI cables are securely connected and not damaged. Replace cables if necessary. Verify that the DPI Host supports Datalinks. Configure the module and DPI Host to use a Datalink that is not already being used by another peripheral. Connect the module to a product that supports Reliance Electric DPI communications (for example, SP600, LiquiFlo 2.0 or GV6000 drives). No action. Normal behavior if no DPI I/O is enabled. No action. 8-2 EtherNet/IP Communications Module

93 8.1.2 MS Status Indicator Table 8.3 MS Status Indicator: State Definitions Status Cause Corrective Action Off The module is not powered. Flashing Red Solid Red Flashing Green Solid Green The module has failed the firmware test. The module is being flash upgraded. The module has failed the hardware test. The module is operational but is not transferring I/O data. The module is operational and transferring I/O data. Securely connect the module to the drive using the Internal Interface cable. Apply power to the drive and network. Clear faults in the module. Cycle power to the drive. If cycling power does not correct the problem, the parameter settings may have been corrupted. Reset defaults and reconfigure the module. If resetting defaults does not correct the problem, flash the module with the latest firmware release. Cycle power to the drive. Replace the module. Place the scanner in RUN mode. Program the controller to recognize and transmit I/O to the module. Configure the module for the program in the controller. Normal behavior if no DPI I/O is enabled. No action. Troubleshooting the Module and Network 8-3

94 8.1.3 NET A Status Indicator Table 8.4 NET A Status Indicator: State Definitions Status Cause Corrective Action Off The module and/or network is not powered, the module is not connected properly to the network, or the module needs an IP address. Solid Red Flashing Red Flashing Red/ Green Flashing Green Solid Green The module failed duplicated IP address detection test. An EtherNet/IP connection has timed out. The module is performing a self test. The module is properly connected but is not communicating with any devices on the network. The module is properly connected and communicating with the network. Securely connect the module to the drive using the Internal Interface cable and to the network using an Ethernet cable. Correctly connect the Ethernet cable to the Ethernet connector. Set a unique IP address using a BOOTP server or disabling BOOTP and using parameters. Apply power to the drive and network. Configure the module to use a unique IP address and cycle power. Place the scanner in RUN mode, or apply power to the peer device that will send I/O. Check the amount of traffic on the network. No action is required. Place the controller in RUN, or apply power to the peer device that will send I/O. Program a controller or peer device to recognize and transmit I/O or make a messaging connection to the module. Configure the module for the program in the controller or the I/O from the peer device. No action required. 8-4 EtherNet/IP Communications Module

95 8.1.4 NET B Status Indicator Table 8.5 NET B Status Indicator: State Definitions Status Cause Corrective Action Off The module is not powered or is not transmitting on the EtherNet/IP network. Flashing Green The module is transmitting on the EtherNet/IP network. If Net A is off: Securely connect the module to the drive using the Internal Interface cable and to the network using an Ethernet cable. Correctly connect the Ethernet cable to the Ethernet connector. Set a unique IP address using a BOOTP server or by disabling BOOTP and using parameters. If Net A is solid Red: Configure the module to use a unique IP address and cycle power. If Net A is flashing red/green or red: Check the IP address in the module and scanner. Ping the module. Normal condition if the module is idle. No action required. Troubleshooting the Module and Network 8-5

96 8.2 Module Diagnostic Items Table 8.6 lists diagnostic items that can be accessed using VS Utilities software or the LCD OIM. Diagnostic items can help you or Rockwell Automation personnel troubleshoot communication problems. Table 8.6 Module Diagnostic Items No. Event Description 1 Common Logic Cmd The current value of the Common Logic Command being transmitted to the host. 2 Prod Logic Cmd The current value of the Product-Specific Logic Command being transmitted to the host. 3 Reference The current value of the Product-Specific Reference being transmitted to the host. 4 Common Logic Sts The current value of the Common Logic Status being received from the host. 5 Prod Logic Sts The current value of the Product-Specific Status being received from the host. 6 Feedback The current value of the Product-Specific Feedback being received from the host Datalink A1 In Datalink A2 In Datalink B1 In Datalink B2 In Datalink C1 In Datalink C2 In Datalink D1 In Datalink D2 In Datalink A1 Out Datalink A2 Out Datalink B1 Out Datalink B2 Out Datalink C1 Out Datalink C2 Out Datalink D1 Out Datalink D2 Out The current value of the specified Datalink being transmitted to the host. (Value of 0 if datalink is not used). The current value of the specified Datalink being received from the host. 23 DPI Rx Errors The current value of the DPI Receive error counter. 24 DPI Rx Err Max The maximum value (since reset) of the DPI Receive error counter. 25 DPI Tx Errors The current value of the DPI Transmit error counter. 26 DPI Tx Err Max The maximum value (since reset) of the DPI Transmit error counter. 8-6 EtherNet/IP Communications Module

97 27 Boot Flash Count The number of times the Boot flash segment has been updated. 28 App Flash Count The number of times the Application flash segment has been updated in the field. 29 M-S Input Size The size of data transferred from the network to the drive. 30 M-S Output Size The size of data transferred from the drive to the network HW Addr 1 HW Addr 2 HW Addr 3 HW Addr 4 HW Addr 5 HW Addr 6 IP Addr Act 1 IP Addr Act 2 IP Addr Act 3 IP Addr Act 4 Table 8.6 Module Diagnostic Items (Continued) No. Event Description The decimal value of each byte in the module s Ethernet hardware address. 255 : 255 : 255 : 255 : 255 : 255 [HW Addr 1] [HW Addr 2] [HW Addr 3] [HW Addr 4] HW Addr 5] [HW Addr 6] The value of each byte in the module s current IP address. A value of 0 appears if the module does not currently have an IP address Subnet Act 1 Subnet Act 2 Subnet Act 3 Subnet Act 4 [IP Addr Act 1] [IP Addr Act 2] [IP Addr Act 3] [IP Addr Act 4] The value of each byte in the module s current subnet mask. A value of 0 appears if the module does not currently have a subnet mask [Subnet Act 1] [Subnet Act 2] [Subnet Act 3] [Subnet Act 4] Troubleshooting the Module and Network 8-7

98 Gateway Act 1 Gateway Act 2 Gateway Act 3 Gateway Act 4 Table 8.6 Module Diagnostic Items (Continued) No. Event Description The value of each byte in the module s current gateway address. A value of 0 appears if the module does not currently have a gateway address [Gateway Act 1] [Gateway Act 2] [Gateway Act 3] [Gateway Act 4] 49 EN Rx Overruns The number of receive buffer overruns reported by the Ethernet hardware. 50 EN Rx Packets The number of Ethernet packets that the module has received. 51 EN Rx Errors The number of receive errors reported by the Ethernet hardware. 52 EN Tx Packets The number of Ethernet packets that the module has sent. 53 EN Tx Errors The number of transmit errors reported by the Ethernet hardware. 54 Last TCP Reset Last reason that the module reset or rejected a TCP/IP connection. 55 Missed IO Pkts Number of incoming I/O connection packets that the module did not receive. 56 OPT Status Operating status of optional I/O board (in External Comms Kit). 57 OPT RX Errors Number of optional I/O board receive errors. 58 OPT FW Version Firmware version of optional I/O board (in External Comms Kit). 8-8 EtherNet/IP Communications Module

99 8.3 Viewing and Clearing Events The module maintains an event queue that reports the history of its actions. You can view the event queue using an LCD OIM or VS Utilities software. To View and Clear Events Using an LCD OIM Use the procedure shown in figures 8.2 and 8.3 to access the event queue using the LCD OIM. Note that you must have the RECOMM- ENET module as the selected device to access the event queue. >> Stopped Auto P5: RECOMM-ENET Main Menu Diagnostics Monitor Lang Highlight Diagnostics icon Diagnostics: View Event Queue Device Version OIM Version Highlight item EvtQ# 1 : E#xxxxx 500kbps Clrqu Press F2 key to clear event queue Figure 8.1 Viewing and Clearing Events Using an LCD OIM on a SP600 or LiquiFlo 2.0 Drive P5 Parameters Groups Linear List Changed Params STARTUP PARAM DIAG SEL SEL P5 Diagnostics Events Device Select Device Name Device Version Device Items STARTUP PARAM DIAG SEL P5 Events View Event Queue Clear Events Clear Event Queue Use the SEL key to select the DIAG tab and then the Up/Down arrow keys to highlight "Events". Press the ENTER key and then the Up/Down arrow keys to highlight "View Event Queue". Press the ENTER key to view the list of events in the event queue. Use the UP/DOWN arrow keys to highlight the event of interest and then the ENTER key to see details about that event. P5 View Event Queue E01:EN Link Up E02:Control Enabled E03:Type 0 Login 500kbps E05:Normal Startup P5 Event Queue 1 EvtQ# 1 E# 37 EN Link Up Accum: 4:27: Figure 8.2 Viewing and Clearing Events Using an LCD OIM on a GV6000 Drive Troubleshooting the Module and Network 8-9

100 Events Many events in the event queue occur under normal operation. However, if you encounter communication problems, the events can help you or Rockwell Automation personnel troubleshoot the problem. Table 8.7 lists events that may appear in the event queue. Table 8.7 Event Codes and Descriptions Code Event Description 1 No Event Empty event queue entry. 2 DPI Bus Off Flt A bus-off condition was detected on DPI. This event may be caused by loose or broken cables or by noise. 3 Ping Time Flt A ping message was not received on DPI within the specified time. 4 Port ID Flt The module is not connected to a correct port on a DPI product. 5 Port Change Flt The DPI port changed. 6 Host Sent Reset The DPI product issued this because it was reset. 7 EEPROM Sum Flt The EEPROM in the module is corrupt kbps The module and DPI product are communicating at 125 kbps kbps The module and DPI product are communicating at 500 kbps. 10 Bad Host Flt The module was connected to an incompatible product. 11 Dup. Port Flt Another peripheral with the same port number is already in use. 12 Type 0 Login The module has logged in for type 0 control. 13 Type 0 Time Flt The module has not received a type 0 status message within the specified time. 14 DL Login The module has logged into a Datalink. 15 DL Reject Flt The host rejected an attempt to log in to a Datalink because the Datalink is not supported or is used by another peripheral. 16 DL Time Flt The module has not received a Datalink message within the specified time. 17 Reserved Not used. 18 Control Disabled The module has sent a Soft Control Disable command to the DPI product. 19 Control Enabled The module has sent a Soft Control Enable command to the DPI product. 20 Message Timeout A Client-Server message sent by the peripheral was not completed. Troubleshooting the Module and Network 8-10

101 Table 8.7 Event Codes and Descriptions Code Event Description 21 Flt Cfg Error Flt Cfg for the Reference or Datalinks is set to a value greater than and the host requires a 16-bit value. 22 App Updated New application firmware detected. 23 EN Comm Flt The module detected a communications fault on the network. 24 EN Sent Reset The module received a fault from the network. 25 EN Close Fit An I/O connection from the network to the module was closed. 26 EN Idle Flt The module is receiving idle packets from the network. 27 EN Open An I/O connection from the network to the module has been opened. 28 EN Timeout Flt An I/O connection from the network to the module has timed out. 29 PCCC IO Close The device sending PCCC Control messages to the module has sent the PCCC Control Timeout to a value of zero. 30 PCCC IO Open The module has begun receiving PCCC Control messages. 31 PCCC IO Time Flt The module has not received a PCCC Control Message for longer than the PCCC Control Timeout. 32 Watchdog T/O Flt The software detects a failure. 33 EEPROM Init A blank EEPROM map revision detected. 34 Normal Startup The module completes a normal start up. 35 Manual Reset The module was reset by changing parameter 20 (Reset Module). 36 EN Link Down The Ethernet link was removed from the module. 37 EN Link Up An Ethernet link is available for the module. 38 BOOTP Response The module received a response to its BOOTP request. 39 Dup IP Addr The module uses the same IP address as another device on the network. 40 Peer IO Open The module received the first Peer I/O image. 41 Peer IO Time Flt The module has not received a Peer I/O message for longer than the Peer I/O Timeout. 42 Failed The module encountered an error attempting to send a requested message. Troubleshooting the Module and Network 8-11

102 Table 8.7 Event Codes and Descriptions Code Event Description 43 Msg Ctrl Open The timeout attribute in either the CIP Register or Assembly object was written with a nonzero value, allowing control messages to be sent to the module. 44 Msg Ctrl Close The timeout attribute in either the CIP Register or Assembly object was written with a zero value, disallowing control messages to be sent to the module. 45 Msg Ctrl Timeout The timeout attribute in either the CIP Register or Assembly object elapsed between accesses of those objects. 46 OPT Open The module began exchanging I/O data with the I/O option. 47 OPT Close The module forced a fault condition on the I/O option. 48 OPT Timeout Communication between the module and I/O option was disrupted EtherNet/IP Communications Module

103 CHAPTER 9 Viewing the Module s Web Pages Chapter 9 provides instructions on how to monitor the module and connected drive using the web interface. Future enhancements may result in web pages that look different than the examples shown in this chapter. 9.1 Accessing the Module s Main Web Pages After configuring the module, you can view its web pages. These pages present information about the module, the drive to which it is connected, and the other DPI devices (for example, OIMs or serial modules) connected to the drive. Note: Firmware 2.xxx (and earlier) module web pages are accessed differently than firmware 3.xxx (and later). Firmware 2.xxx (and earlier) module By default the module web pages are enabled. To disable the web pages, use Bit 0 of Access Control (54). Firmware 3.xxx (and later) module By default the module web pages are disabled. To enable the web pages, set the Web Pages Switch to its Enable Web position and reset the module. Web Enable (55) can be used to display the setting (enabled or disabled) of this switch. The module can be configured to automatically send messages to desired addresses when selected drive faults occur and/or are cleared, and/or when the module takes a communication or idle fault action. For firmware 2.xxx (and earlier) modules, Bit 1 of Access Control (54) can be used to protect the configured settings for the messaging feature. For firmware 3.xxx (and later)modules, Bit 0 of Web Features (56) can be used to protect the configured settings. Viewing the Module s Web Pages 9-1

104 To view the module s web pages: Step 1. On a computer with access to the EtherNet/IP network on which the module is installed, start a web browser (for example, Microsoft Internet Explorer (version 5.0 or greater) or Netscape Navigator (version 4.6 or greater) software. The computer can access the web pages if it is connected to the same network as the module or if it is connected to a network with access to the module s network via a gateway device (for example, a router). Step 2. In the Address (Explorer) or Location (Navigator) box, type then type the IP address of the module, and finally press ENTER. The main page for the module appears as shown in figure 9.1. Important:Clicking the browser s Refresh button always re-displays the Home page even while viewing another module we page. Figure 9.1 Main Web Page for the Module 9-2 EtherNet/IP Communications Module

105 Title Bar on Adapter Web Pages The title bar appears on all module web pages, including its Home Page. It consists of three elements: Item Reliance Electric logo (at far left) Module Title (middle) Rockwell Automation logo (at far right) Description This logo is also a link. Click it to view the reliance.com web Home Page. Shows the module type or user-configurable title. This logo is also a link. Click it to view the Rockwell Automation web Home Page. Navigation Menu on Adapter Web Pages The navigation menu appears on the left side of all module web pages, including its Home page. The navigation menu consists of links and link folders which can be expanded or minimized. The following table shows all of the navigation menu s links and link folders: Link/Folder Description Home link Click this link to view the module s Home Page. Process Display link Click this link to view the Host s Process Display pop-up window. TCP/IP Click this link to view the module s TCP/IP configuration link Configuration web page showing information about the TCP/IP configuration, such as the module s IP address and the number of packets being sent. Configure notification link Browse DPI devices folder Port x folders Online user manuals link Click this link to view the module s Configure Notification web page to configure the module to send automatic messages. notification can accommodate specific needs such as when only selected faults occur. Click this folder to expand and view the Port folders for all present DPI devices, including the drive, adapter, and other DPI devices connected to the drive such as an OIM. Click a respective Port folder to expand and view its device s various links which take you to related information pages. Click this link to view Reliance Electric s web page with documentation for drives and other devices. Viewing the Module s Web Pages 9-3

106 Link/Folder Software tools Web site link Launch my V*S Utilities software link technical support link Description Click this link to view Reliance Electric s web page with information about software tools such as V*S Utilities. Click this link to launch the V*S Utilities software already installed on your PC. Click this link to view a new message window to send a message to Reliance Electric s Technical Support Team Information on Module Home Page The module Home Page displays the following information for the module and host: Item Module Information Host X Information Description Revision IP Address Ethernet Address (MAC) Serial Number Status I/O Connection Status Revision Status Commanded Direction Rotation Direction Process Status 9-4 EtherNet/IP Communications Module

107 9.2 Process Display Pop-Up Windows The Process Display pop-up window dynamically shows a host s information. To view this window, click the Process Display link in the navigation window. Information Product Text Status Commanded Direction Rotation Direction Process Status Figure 9.2 Process Display Pop-up Window Description Description of Host Status of Host Commanded direction of Host Rotation direction of Host Line 1 - desired parameter of host and its dyanmic value 1 Line 2 - desired parameter of host and its dyanmic value 2 Line 3 - desired parameter of host and its dyanmic value 2 1. The parameter whose value is shown on this line is the feedback value selected using a drive parameter. For details, see the drive User Manual. 2. The parameter whose value is shown on this line can be set using the OIM. For details, see the drive User Manual. Viewing the Module s Web Pages 9-5

108 9.3 TCP/IP Configuration Web Page The TCP/IP Configuration web page provides details about the module s Ethernet settings and network activities. Figure 9.3 TCP/IP Configuration Web Page Information IP Address Subnet Mask Gateway Address BOOTP Ethernet Address (MAC) Ethernet Received Packets Ethernet Receive Errors Ethernet Receive Overruns Description IP address of module Subnet mask for the module s network Address for the gateway device on the module s network Whether BOOTP is being used to configure the module s network information. Hardware address for the module Number of packets that the module has received Number of receive errors reported by the hardware Number of receive buffer overruns reported by the hardware 9-6 EtherNet/IP Communications Module

109 Information Ethernet Transmitted Packets Ethernet Transmit Errors EtherNet/IP Missed I/ O Packets Description Number of packets tha the module has sent Number of transmit errors reported by the hardware Number of I/O connection packets that the module did not receive 9.4 Configure Notification Web Page The Configure Notification web page contains selections and data fields for configuring the module to automatically send messages to desired addresses when selected types of events occur. configuration for Series A modules is enabled and disabled differently than Series B modules. Firmware 2.xxx (and earlier) modules By default, settings are protected and the user needs to enable configuration by setting the Access Control (54) Config Bit 1 value to 1 (Enabled). After configuration, the settings can be protected by setting the Access Control (54) Config Bit 1 value to 0 (Disabled). Firmware 3.xxx (and later) modules By default, settings are not protected. After configuration, the settings can be protected by setting the Web Features (56) Cfg Bit 0 value to 0 (Disabled). To change a protected configuration, it must first be unprotected by setting the Cfg Bit 0 value back to 1 (Enabled) Viewing the Module s Web Pages 9-7

110 For more information, see section 4.10, Setting Web Access Control. Figure 9.4 Configuration of Notification Web Page To configure notification Step 1. Click the desired Send an message when... check boxes you want to occur that will send notification. If you only want notification when selected faults/alarms occur: Click the respective fault and/or alarm radio buttons. Click the selected faults link and/or selected alarms link. Viewing the Module s Web Pages 9-8

111 Step 2. Information IP address of... addresses to notify... Subject of message... Figure 9.5 Selected Fault Configuration Page Click the desired fault/alarm check boxes, and click Save Changes. Click the Back to Configuration Page link. Type the following information in their respective boxes: Description Type in the address of the mail server that will be used to deliver the messages. Type in addresses to where you want messages to be sent. Multiple addresses can be used, but they must be separated by commas (comma delimited). Type in the desired subject text for the message. Step 3. Click Save changes. Viewing the Module s Web Pages 9-9

112 Important:For firmware 2.xxx (and earlier) modules, it is recommended that Access Control (54) Config Bit 1 value be set to 0 (Disabled) after Notification has been configured. Otherwise the configuration can be changed anytime the web page is accessed with a browser.forfirmware 3.xxx (and later) modules, it is recommended that Web Features (56) E- mail Cfg Bit 0 value be set to 0 (Disabled) after Notification has been configured. Otherwise the configuration can be changed anytime the web page is accessed with a browser. An example of an message automatically sent by the adapter in response to selected events is shown below. Figure 9.6 Example of Message Ssent by Module Note: To stop messages, do one of the following: Delete all addresses from the Configure Notification web page. Uncheck all of the Send an message when... boxes. For firmware 2.xxx (and earlier) modules, disabling the adapter web pages by using Access Control (54) to set the Web Enable Bit 0 value to 0 (Disabled) will NOT stop the module from sending e- mail messages. For firmware 3.xxx (and later) modules, setting the Web Pages Switch to the Disable Web position will NOT stop the module from sending messages. Viewing the Module s Web Pages 9-10

113 9.5 DPI Device Information Pages DPI device information pages show a device s module information, diagnostic information, and fault queue. Figure 9.7 Example of Port 0 (SP600 Drive) Module Information Page Information Description Product Text Text identifying the device Vendor ID 1 = Reliance Electric Device Type 123 Product Code Code for the product name and its rating Revision Firmware revision used by the device Serial Number Serial number of the device Status Operating status of the device (for example, faulted) Viewing the Module s Web Pages 9-11

114 Figure 9.8 Example of Port 0 (SP600 Drive) Diagnostic Information Page Figure 9.9 Example of Port 0 (SP600 Drive) Fault Queue Page Viewing the Module s Web Pages 9-12

115 Figure 9.10 Example of Port 5 (RECOMM-ENET Module) Event Queue Page Viewing the Module s Web Pages 9-13