1. Manuals
  2. Brands
  3. Reliance electric Manuals
  4. Control Unit
  5. MD65
  6. Instruction manual

Reliance electric MD65 Instruction Manual

Ethernet/ip communications module
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
MD65 EtherNet/IP
Communications Module
M/N MDCOMM-ENET
Instruction Manual
D2-3529

Advertisement

Table of Contents
loading

Related Manuals for Reliance electric MD65

Summary of Contents for Reliance electric MD65

  • Page 1 MD65 EtherNet/IP Communications Module M/N MDCOMM-ENET Instruction Manual D2-3529...
  • Page 2 Ethernet is a trademark of Digital Equipment Corporation, Intel Corporation, and Xerox Corporation. property of their respective companies. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation. Reliance, MD65, VS Utilities, DPI, RSLogix, ControlLogix, and SLC are trademarks of Rockwell Automation. ©2004 Rockwell Automation. All rights reserved.

  • Page 3: Table Of Contents

    ONTENTS Chapter 1 Introduction 1.1 Module Features............1-1 1.2 Related Documentation ..........1-2 1.3 Getting Assistance from Reliance Electric..... 1-2 Chapter 2 Getting Started 2.1 Required Equipment ............2-2 2.2 Installation Checklist ............2-3 Chapter 3 Installing the EtherNet/IP Module 3.1 Preparing for an Installation...........
  • Page 4 6.3 Using Logic Command/Status ........6-2 6.4 Using Reference/Feedback ........... 6-3 6.5 Sample Ladder Logic Program ........6-3 6.5.1 Function of the Sample Program ......6-3 6.5.2 Module Setting for the Sample Program....6-3 6.6 RSLogix 5000 Configuration .......... 6-4 6.7 Logic Command/Status Words ........
  • Page 5 Chapter 10 Viewing the Module’s Web Pages 10.1 Accessing the Module’s Main Web Page ....10-1 10.1.1 Title Bar on Module Web Pages......10-3 10.1.2 Navigation Menu on Module Web Pages ..10-4 10.2 Web Pages ..............10-6 10.2.1 Information on Module Home Page....10-6 10.2.2 Process Display Pop-up Windows.....
  • Page 6 EtherNet/IP Communications Module...
  • Page 7 Figure 3.1 – Setting Single/Multi-Drive Operation and Web Page Enable Switches ................3-2 Figure 3.2 – View of the switches on an Installed MD65 Drive....3-3 Figure 3.3 – MDI Ports and Internal Interface Cables......... 3-4 Figure 3.4 – Mounting and Grounding the Module ........3-4 Figure 3.5 –...
  • Page 8 Figure 6.5 – Sample ControlLogix Ladder Logic Program for I/O Messaging (Continued)................6-7 Figure 7.1 – ControlLogix Message Format in RSLogix 5000 ....7-2 Figure 7.2 – Explicit Message Process ............7-4 Figure 7.3 – Controller Tags for Explicit Messages ........7-5 Figure 7.4 –...
  • Page 9 List of Tables Table 2.1 – Equipment Shipped with the EtherNet/IP Module....2-2 Table 2.2 – User-Supplied Items Required for Installation ......2-2 Table 3.1 – Setting 1 Descriptions ..............3-2 Table 3.2 – Setting 2 Descriptions ..............3-3 Table 4.1 – Configuration Tools..............4-1 Table 4.2–...
  • Page 10 VIII EtherNet/IP Communications Module...

  • Page 11: Chapter 1 Introduction

    Introduction This manual provides information about the EtherNet/IP Communications module (MDCOMM-ENET) and using it with MDI AC drives, such as MD65 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.

  • Page 12: Related Documentation

    1.3 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 1-864-284-5350. Before calling, please review the troubleshooting section of this manual and check the Reliance drives website for additional information.

  • Page 13: Chapter 2 Getting Started

    HAPTER 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 LED’s are on bottom side of module board. Status Indicators Four LEDs to indicate the status of the connected drive, module, and network.

  • Page 14: Required Equipment

    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 • MD65 LCD OIM • VS Utilities • BOOTP Server (version 2.1 or higher) for network setup only...

  • Page 15: Installation Checklist

    Refer to: Review the safety precautions for the Throughout module. this manual Verify that the drive is properly installed. MD65 AC Drive User Manual Install the module. Chapter 3, Installing the Verify that the drive and the network are not EtherNet/IP powered.
  • Page 16 Step Action Refer to: Create a ladder logic program. Chapter 6, Use a programming tool to create a ladder Using I/O logic program that enables you to do the Messaging following: Chapter 7, • Control the module and connected drive Using Explicit using I/O Messaging...

  • Page 17: Chapter 3 Installing The Ethernet/Ip Module

    HAPTER Installing the EtherNet/IP Module Chapter 3 provides instructions for installing the module on an MD65 drive. 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-IN001...

  • Page 18: Figure 3.1 - Setting Single/Multi-Drive Operation And Web Page Enable Switches

    Step 1. Set the Operating Mode Switch (SWI) for Single or Multi- Drive operation (see figure 3.1 and setting descriptions below). For complete details on Multi-Drive operation, see chapter 8. WEB PAGES OPERATING SWITCH MODE SWITCH Multi-Drive Enable Web Operation Position Position Single-Drive...

  • Page 19: Connecting The Module To The Drive

    Enables the module web pages (default (UP = Open = 1) setting). Figure 3.2 – View of the switches on an Installed MD65 Drive 3.3 Connecting the Module to the Drive ATTENTION: The MD65 drive may contain high voltages that can cause injury or death. Remove...

  • Page 20: Figure 3.3 - Mdi Ports And Internal Interface Cables

    EtherNet/IP Adapter – — ˜ MD65 Drive (C Frame shown with cover removed) Back of Required Special Drive Cover (ordered separately): Part No. 6MD-COMMCVRB for B-frame 6MD-COMMCVRC for C-frame MDI Connector 15.24 cm (6 in.) Internal Interface cable EtherNet Cable Figure 3.3 –...

  • Page 21: Connecting The Module To The Network

    3.4 Connecting the Module to the Network ATTENTION: The MD65 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.

  • Page 22: Applying Power

    3.5 Applying Power 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. Step 1.

  • Page 23: Chapter 4 Configuring The Ethernet/Ip Module

    HAPTER 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.

  • Page 24: Using The Lcd Oim Or Copycat Keypad To Configure The Module

    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 MD65 AC Drive User Manual (D2-3519) for more information.

  • Page 25: Using Bootp To Set The Ip Address, Subnet Mask, And Gateway Address

    Table 4.2– Using the LCD OIM or CopyCat Keypad Step Key(s) Example Screens 4. Press Enter to select Parameters the Ethernet/IP Linear List module. The Changed Params Parameters menu for the module will be displayed. DIAG PARAM DSEL 5. Press Enter to access Mode the parameters.

  • Page 26: Figure 4.1 - Bootp Server Window

    Figure 4.1 – 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.2. Figure 4.2 – New Entry Dialog Box Step 4.

  • Page 27: Figure 4.3 - Bootp Server Window With A Module In The Relation List

    Step 5. Click OK to apply the settings. The module appears in the Relation List with the new settings as shown in figure 4.3. Figure 4.3 – BOOTP Server Window with a Module in the Relation List Step 6. To assign this configuration to the module permanently, click Disable BOOTP.

  • Page 28: Using Parameters To Set The Ip Address, Subnet Mask, And Gateway Address

    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.

  • Page 29: Figure 4.6 Sample Subnet Mask Screen On An Lcd Oim

    Step 3. Reset the module. Refer to Resetting the Module in section 4.7.2. 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 2 (BOOTP) is set to Disabled.

  • Page 30: Setting The Data Rate

    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 15 (EN Rate Cfg) determines the Ethernet data rate and duplex setting that the module will use to communicate.

  • Page 31: Setting A Fault Action

    Drive 0 is the MD65 with the MDCOMM-ENET module installed. Drive 1 through 4 are MD65 and/or MD60 drives that multi-drop to the RJ45 (RS-485) port on Drive 0. For more information on Multi- Drive Mode, refer to chapter 8.

  • Page 32: Setting The Fault Configuration Parameters

    Table 4.4 – Selections for Drive Response to Communication Fault Value Action Description Fault (default) The drive is faulted and stopped (Default). Stop The drive is stopped, but not faulted. Zero Data The drive is sent 0 for output data after a communications disruption.

  • Page 33: Resetting The Module

    4.7.2 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 17 (Reset Module). ATTENTION: If the module is transmitting control I/O to the drive, the drive may fault when you reset the module.

  • Page 34: Viewing The Module Configuration

    By accessing the IP address set for the module using a web browser, you can view the module’s web pages for information about the module, the MD65 drive to which it is connected, and other MDI devices connected to the drive such as OIMs, serial modules, or other daisy-chained drives (when module is in Multi- Drive mode).

  • Page 35: To Enable The Module Web

    4.9.1 To Enable the Module Web Pages Set the Web Pages Switch (SW2) to the “Enable Web” (up) position. Refer to figure 3.1 and table 3.2 Important:For a change to the switch setting to take effect, the module must be reset. Bit 0 of parameter 30 (Web Features) is used to protect the configured settings for e-mail notification.
  • Page 36 4-14 EtherNet/IP Communications Module...

  • Page 37: Chapter 5 Configuring The Scanner Or Bridge

    Configuring the Scanner or Bridge Chapter 5 provides instructions on how to configure a ControlLogix bridge to communicate with the module and connected MD65 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.

  • Page 38: Adding A Bridge Or Scanner To The I/O Configuration

    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.

  • Page 39: Figure 5.3 - Select Module Type Dialog Box

    1756-ENBT/A option is selected. Step 4. Click OK. The Module Properties dialog box (figure 5.4) appears. Reliance Electric 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.

  • Page 40: Adding The Module And Drive To The I/O Configuration

    Table 5.1 – Module Properties Fields Field Enter This Information Name A name to identify the scanner or bridge. Slot The slot of the EtherNet/IP scanner or bridge in the rack. Revision 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).

  • Page 41: Figure 5.6 - Right Clicking The Scanner

    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 MDCOMM-ENET module (figure 5.7), and then click OK. The Module Properties dialog box (figure 5.8) appears.

  • Page 42: Figure 5.8 - Module Properties Dialog Box

    Reliance Electric MD65_Demo 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.

  • Page 43: Figure 5.9 - Module Properties Dialog Box

    In our example, we typed 4 in the Input Size and Output Size boxes because the Operating Mode Switch on the module is set to “Single” (default) and parameter 22 (MDI I/O Cfg) is set to “Drive 0” (only one drive being connected). Logic Command/Reference uses 2 words and Logic Status/Feedback uses 2 words.

  • Page 44: Figure 5.10 - Rslogix 5000 - Data Types And I/O Configuration Folders

    Step 7. Click Finish>>. The new node (“MD65_Demo” 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 double- click on the Module-Defined folder, you will see that module-defined data types and tags have been automatically created.

  • Page 45: Saving The Configuration

    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.
  • Page 46 5-10 EtherNet/IP Communications Module...

  • Page 47: Chapter 6 Using I/O Messaging

    On EtherNet/IP networks, I/O messaging is used to transfer the data that controls the MD65 drive and sets its Reference. I/O can also be used to transfer data to and from Datalinks in MD65 drives. The module provides many options for configuring and using I/O, including configuring the size of I/O by selecting the number of attached drives (Single or Multi-Drive mode).

  • Page 48: Understanding The I/O Image

    Figure 6.1 – Single Drive Example of I/O Image Single mode is the typical configuration, where one node consists of a MD65 drive with a MDCOMM-ENET. For Multi-Drive mode, where one node can consist of up to 5 drives, refer to chapter 8.

  • Page 49: Using Reference/Feedback

    Word 1 Figure 6.1 0.0 to 400.0 Hz (MD65) 1. The Reference for a MD65 or MD60 is set in Hz. and not in engineering units. For example, “300” equates to 30.0 Hz (the decimal point is always implied). 6.5 Sample Ladder Logic Program The sample ladder logic program works with a ControlLogix controller and an MD65 drive.

  • Page 50: Rslogix 5000 Configuration

    16-bit words of data (see figure 6.3). RE:ETHERNET_... MD65_Demo: C MD65_Demo: I RE:ETHERNET_... MD65_Demo: I.Data MD65_Demo: I.Data[0] MD65_Demo: I.Data[1] MD65_Demo: I.Data[2] MD65 Logic Status MD65_Demo: I.Data[3] MD65 Feedback RE:ETHERNET_... MD65_Demo: 0 MD65_Demo: 0.Data MD65 Logic Command MD65_Demo: 0.Data[0] MD65_Demo: 0.Data[1] MD65 Demo Reference Figure 6.3 –...

  • Page 51: Logic Command/Status Words

    6.7 Logic Command/Status Words This example uses the Logic Command word and Logic Status word for MD65 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 MDI product. Refer to the documentation for your product.

  • Page 52: Sample Controllogix Ladder Logic Program

    ControlLogix to ControlLogix to MD65 on EtherNet/IP Demo The ControlLogix system consists of a 1756-ENBT in slot 5 communicating over Ethernet with a MD65 drive/ MDCOMM- The ControlLogix system consists of a 1756-ENBT in slot 5 communicating over Ethernet with ENET EtherNet/IP module.

  • Page 53: Figure 6.5 - Sample Controllogix Ladder Logic Program For I/O Messaging (Continued)

    MD65 Demo Logic Command REVERSE Forward_Command MD65_Demo:O.Data[0].5 This rung provides the Reference word to This rung provides the Reference word to the MD65. Note that it is set in Hz and not in engineering units. MD65 Demo Reference Move Source Reference Dest MD65_Demo:O.Data[1]...
  • Page 54 EtherNet/IP Communications Module...

  • Page 55: Chapter 7 Using Explicit Messaging

    HAPTER Using Explicit Messaging Chapter 7 provides information and examples that explain how to use Explicit Messaging to configure and monitor an MD65 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.

  • Page 56: Formatting Explicit Messages

    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 .
  • Page 57 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.

  • Page 58: Performing Explicit Messages

    7.3 Performing Explicit Messages Important: 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. Set up and send Parameter Message Complete Parameter Message Retrieve Parameter...

  • Page 59: About The Explicit Message Examples

    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 Message Formats When formatting a message example, refer to Formatting Explicit Messages in this chapter for an explanation of the content of each box.

  • Page 60: Get Attribute Single Message Example

    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 MD65 drive. Message Format Example MD65_Demo MD65_Demo Figure 7.4 – Message Format for a Get Attribute Single Message Table 7.1 identifies key settings for the message format:...

  • Page 61: Figure 7.5 - Get Attribute Single Message Example

    Destination Data Example In this example, the Get Attribute Single message reads parameter 39 (Accel Time 1) in the MD65 drive and returns its value to the destination tag named ParameterReadValue. Figure 7.6 – Example of Destination Data from a Get Attribute Single Message The acceleration time is 10.0 seconds.

  • Page 62: Set Attribute Single Message Example

    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 MD65 drive. Message Format Example MD65_Demo Figure 7.7 – Message Format for a Set Attribute Single Message Table 7.2 identifies key settings for the data format:...

  • Page 63: Figure 7.8 - Set Attribute Single Message Example

    In this example, the Set Attribute Single message writes 100, the value in the source tag named ParameterWriteValue, to parameter 39 (Accel Time 1) in the MD65 drive. Figure 7.9 – Example of Source Data from Set Attribute Single Message 10.0 seconds is written to the parameter.
  • Page 64 7-10 EtherNet/IP Communications Module...

  • Page 65: Chapter 8 Using Multi-Drive Mode

    Multi-Drive mode is an alternative to the typical network installation, where a single EtherNet/IP node can consist of one to five drives (see figure 8.2). The first drive must be a MD65 with a MDCOMM- ENET module. The remaining drives can be MD65 or MD60 drives that are daisy-chained over RS-485 with the first drive.

  • Page 66: Figure 8.2 - Multi-Drive Mode Example For Network

    The trade-offs of Multi-Drive mode include: • If the MD65 drive with the MDCOMM-ENET module is powered down, then communications with the daisy-chained drives is disrupted and the drives will take the appropriate communications loss action set in each drive.

  • Page 67: System Wiring

    The AK-U0-RJ45-SCI MDI Splitter Cable cannot be used to add a connection for a peripheral device. 8.2 System Wiring To daisy-chain the drives of the MD65 with the MDCOMM-ENET module (Drive 0), the AK-U0-RJ45-TB2P terminal block connector (Figure 8.3) can be used for easy installation.

  • Page 68: Understanding The I/O Image

    The wiring diagram for using AK-U0-RJ45-TB2P terminal block connectors is shown in figure 8.4. MD65 with MDCOMM-ENET Drive #2 Drive #3 Drive #4 Drive #5 ¼ Watt Resistor ¼ Watt Resistor Figure 8.4 – Multi-Drive Mode Example for Network The AK-U0-RJ45-TB2P comes with five (5) terminal block connectors and two (2) terminating resistors.

  • Page 69: Figure 8.5 - Multi-Drive Mode Example For Network

    Figure 8.5 illustrates the Multi-Drive I/O image with 16-bit words. EtherNet/IP Controller Scanner Adapter Word and I/O 0 Logic Command MD65 Drive 0 1 Reference 2 Logic Command MD65 Drive 1 3 Reference Output 4 Logic Command Image MD65 Drive 2...

  • Page 70: Configuring The Rs-485 Network

    8.4 Configuring the RS-485 Network Table 8.2 shows the parameters that must be set in the daisy- chained drives. Table 8.2 – Parameters for daisy-chained drives Parameter Value P36 (Start Source) 5 (Comm Port) P38 (Speed Reference) 5 (Comm Port) A103 (Comm Data Rate) 4 (“19.2K”) A104 (Comm Node Addr)

  • Page 71: Example Multi-Drive Ladder Logic Program

    Important: MDCOMM-ENET parameters can be set using MDI peripheral (OIM) ONLY when the Operating Mode Switch is in the Single 8.5 Example Multi-Drive Ladder Logic Program The ladder logic program example demonstrates using Multi-Drive mode with five drives. See figure 8.2 for a system layout diagram. 8.5.1 Function of Example Program The example program provided is for the ControlLogix, but other controllers can also be used.

  • Page 72: Drive Settings For The Example Program

    8.5.3 Drive Settings for the Example Program Table 8.5 shows the drive settings for the example program. Table 8.5 – Module Parameter Settings Drive Drive Drive Drive Drive Parameter P36 (Start Source) P38 (Speed Reference) A103 (Comm Data Rate) A104 (Comm Node Addr) A105 (Comm Loss Action) A106 (Comm Loss Time) A107 (Comm Format)

  • Page 73: Table 8.7 - Common Tags For Controllogix Example

    Table 8.7 describes the tags used for Drive 0. Table 8.7 – Common Tags for ControlLogix Example Tag Name Type Description Drive 0 Command Stop BOOL Logic Command bit 0 (STOP) Drive 0 Command Start BOOL Logic Command bit 1 (START) Drive 0 Command Jog BOOL...

  • Page 74: Main Routine

    ControlLogix to ControlLogix to MD65 on EtherNet/IP Demo The ControlLogix system consists of a 1756-ENBT in slot 5 communicating over Ethernet with a MD65 drive/ MDCOMM- The ControlLogix system consists of a 1756-ENBT in slot 5 communicating over Ethernet with ENET EtherNet/IP module.

  • Page 75: Drive 0 - Drive 4 Control Routines

    This rung writes the output image to the scanner. The output image is as follows: This rung writes the output image to the scanner. The output image is as follows: DriveOutputImage[0] and DriveOutputImage[1] = Drive 0 Logic Command and Reference DriveOutputImage[0] and DriveOutputImage[1] = Drive 0 Logic Command and Reference DriveOutputImage[2] and DriveOutputImage[3] = Drive 1 Logic Command and Reference DriveOutputImage[2] and DriveOutputImage[3] = Drive 1 Logic Command and Reference...

  • Page 76: Drive 0 Control Routine

    8.6.2.1 Drive 0 Control Routine Drive 0 Control Subroutine Drive 0 Control Subroutine This section takes the data from the input area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[0].0 Drive0StatusReady DriveInputImage[0].1...

  • Page 77: Figure 8.7 - Drive 0 Control Routine (Continued)

    Explicit Messaging Example Explicit Messaging Example Drive 0 parameters are accessed by adding 17408 decimal (4400 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 17447 (17408 + 39) is used. PerformParameterRead0 Type - CIP Generic Message Control ParameterRDMessage0 ...

  • Page 78: Drive 1 Control Routine

    8.6.2.2 Drive 1 Control Routine Drive 1 Control Subroutine Drive 1 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[2].0 Drive1StatusReady DriveInputImage[2].1...

  • Page 79: Figure 8.8 - Drive 1 Control Routine (Continued)

    Explicit Messaging Example Explicit Messaging Example Drive 1 parameters are accessed by adding 18432 decimal (4800 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 18471 (18432 + 39) is used. PerformParameterRead1 Type - CIP Generic Message Control ParameterRDMessage1 ...

  • Page 80: Drive 2 Control Routine

    8.6.2.3 Drive 2 Control Routine Drive 2 Control Subroutine Drive 2 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[4].0 Drive2StatusReady DriveInputImage[4].1...
  • Page 81 Explicit Messaging Example Explicit Messaging Example Drive 2 parameters are accessed by adding 19456 decimal (4C00 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 19495 (19456 + 39) is used. PerformParameterRead2 Type - CIP Generic Message Control ParameterRDMessage2 ...

  • Page 82: Drive 3 Control Routine

    8.6.2.4 Drive 3 Control Routine Drive 3 Control Subroutine Drive 3 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[6].0 Drive3StatusReady DriveInputImage[6].1...

  • Page 83: Figure 8.10 - Drive 3 Control Routine (Continued)

    Explicit Messaging Example Explicit Messaging Example Drive 3 parameters are accessed by adding 20480 decimal (5000 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 20519 (20480 + 39) is used. PerformParameterRead3 Type - CIP Generic Message Control ParameterRDMessage3 ...

  • Page 84: Drive 4 Control Routine

    8.6.2.5 Drive 4 Control Routine Drive 4 Control Subroutine Drive 4 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[8].0 Drive4StatusReady DriveInputImage[8].1...

  • Page 85: Multi-Drive Mode Explicit Messaging

    Explicit Messaging Example Explicit Messaging Example Drive 4 parameters are accessed by adding 21504 decimal (5400 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 21543 (21504 + 39) is used. PerformParameterWrite4 Type - CIP Generic Message Control ParameterRDMessage4 ...

  • Page 86: Drive 0 Explicit Message Example

    For example, to access parameter P39 (Accel Time 1) in each of the drives, the following instance would be used: Drive 0 Instance = 17447 (17408 + 39) Drive 1 Instance = 18471 (18432 + 39) Drive 2 Instance = 19495 (19456 + 39) Drive 3 Instance = 20519 (20480 + 39) Drive 4 Instance = 21543 (21504 + 39) 8.7.1 Drive 0 Explicit Message Example...

  • Page 87: Figure 8.13 - Parameter Write Message Configuration

    Figure 8.13 – Parameter Write Message Configuration The Class Code is “f” for the Parameter Object and the Instance Attribute is “1” to select retrieving the parameter value. (See Appendix C for more information.) The Instance value is “17441” to access parameter 39 (Accel Time 1).

  • Page 88: Additional Information

    8.8 Additional Information • When the MD65 with the MDCOMM-ENET module (Drive 0) is powered up, all configured daisy-chained drives must be present before an I/O connection is allowed on EtherNet/IP (i.e. before the drives can be controlled). • If the MD65 with the MDCOMM-ENET module (Drive 0) is...

  • Page 89: Chapter 9 Troubleshooting The Module And Network

    HAPTER Troubleshooting the Module and Network Chapter 9 contains information for troubleshooting the EtherNet/IP module and the network. 9.1 Understanding the Status Indicators The module has four status indicators. They can be viewed on the module or through the drive cover. (See figure 9.1.) –...

  • Page 90: Drive Status Indicator

    • communication from Cycle power to the drive. the drive, or the drive is • Use Reliance Electric MD65 not a Reliance Electric and MD 60 AC Drives. drive. Solid The drive has refused Important: Cycle power to the...

  • Page 91: Ms Status Indicator

    Table 9.2 – MS Status Indicator: State Definitions Status Cause Corrective Action • The module is not Securely connect the module powered or properly to the MD65 drive using the connected to the Internal Interface cable. drive. • Apply power to the drive and network. •...

  • Page 92: Net A Status Indicator

    9.1.3 NET A Status Indicator Table 9.3 – NET A Status Indicator: State Definitions Status Cause Corrective Action • The module and/or Securely connect the module to network is not the drive using the Internal powered, the Interface (ribbon) cable and to module is not the network using an Ethernet connected properly...

  • Page 93: Net B Status Indicator

    9.1.4 NET B Status Indicator Table 9.4 – NET B Status Indicator: State Definitions Status Cause Corrective Action The module is not If Net A is off: powered or is not • Securely connect the module to transmitting on the the drive using the Internal EtherNet/IP Interface cable and to the...

  • Page 94: Module Diagnostic Items In Single Drive Mode

    9.2 Module Diagnostic Items in Single Drive Mode Table 9.5 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 9.5 – Module Diagnostic Items (Single Drive Mode) Name Description 1 Reserved...
  • Page 95 Table 9.5 – Module Diagnostic Items (Continued)(Single Drive Mode) Name Description 34 IP Addr Act 1 The most significant byte in the module’s current IP address, or 0 if the modules does not currently have an IP address. 35 IP Addr Act 2 The second most significant byte in the module’s current IP address, or 0 if the modules does not currently have an IP address.

  • Page 96: Module Diagnostic Items In Multi-Drive Mode

    Table 9.5 – Module Diagnostic Items (Continued)(Single Drive Mode) Name Description 48 EN Rx Errors A count of the number of errors receive by the EtherNet MAC. 49 EN Packets Sent A count of the number of transmitted packets reported by the EtherNet MAC. 50 EN Tx Errors A count of the number of transmit errors reported by the EtherNet MAC.
  • Page 97 Table 9.6 – Module Diagnostic Items (Continued)(Multi-Drive Mode) Name Description 14 Drv 2 Feedback Feedback being received from drive 2 by the module. 15 Drv 3 Logic Cmd Logic Command being transmitted to drive 3 by the module. 16 Drv 3 Reference Reference being transmitted to drive 3 by the module.
  • Page 98 Table 9.6 – Module Diagnostic Items (Continued)(Multi-Drive Mode) Name Description 35 IP Addr Act 2 The second most significant byte in the module’s current IP address, or 0 if the modules does not currently have an IP address. 36 IP Addr Act 3 The second least significant byte in the module’s current IP address, or 0 if the modules does not currently have an IP address.

  • Page 99: Viewing And Clearing Events

    9.4 Viewing and Clearing Events The module maintains an event queue that reports the history of its actions. You can view the event queue using V*S Utilities software (3.01). To View and Clear Events MDCOMM-ENET Figure 9.2 – V*S Utilities Event View/Clear Screen Events Many events in the event queue occur under normal operation.
  • Page 100 Table 9.7 – Event Codes and Descriptions Code Event Description Slave Detected The module detected that the slave has been connected. Slave Removed The module detected that the slave has been disconnected. Slave Logon The module has established communications with the drive. Slave Timeout The module has lost communications with the drive.
  • Page 101 Table 9.7 – Event Codes and Descriptions Code Event Description EN Comm Flt The module has performed the “Comm Flt” action specified by the user. EN Idle Flt The module has performed the “Idle Flt” action specified by the user. PCCC IO Open The module has begun receiving PCCC Control messages (the PCCC Control Timeout was...
  • Page 102 9-14 EtherNet/IP Communications Module...

  • Page 103: Chapter 10 Viewing The Module's Web

    Viewing the Module’s Web Pages Chapter 10 provides instructions on how to monitor the module and connected MD65 MDI drive using the module’s web interface. Future enhancements may result in web pages that look different than the examples shown in this chapter.
  • Page 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).

  • Page 105: Title Bar On Module Web

    Page. It consists of three elements. Table 10.1 – MS Status Indicator: State Definitions Item Description Reliance Electric logo (at The logo is also a link. Click it to view the far left) Reliance.com web Home Page. Module Title (middle) Shows the module type and title.

  • Page 106: Navigation Menu On Module Web

    10.1.2 Navigation Menu on Module Web Pages The navigation menu appears on the left side of all module web pages, including the Home Page. The navigation menu consists of links and link folders which can be expanded or minimized. Slight difference occur in the navigation menu when the module is operated in Single mode versus Multi-Drive mode.
  • Page 107 (X = total connected diagnostics” link, and “Fault queue” link, which hosts) will take you to related information pages. Online User Manuals link Click this link to view Reliance Electric’s web page with documentation for drives and other devices. Software tools Web site Click this link to view Reliance Electric’s web...

  • Page 108: Web

    10.2 Web Pages 10.2.1 Information on Module Home Page The module Home Page displays the following information for the module and host: Table 10.3 – Module Home Page Information Item Description • Module Revision Information • IP Address • Ethernet Address (MAC) •...
  • Page 109 Information Description Product Text Description of host. Status Status of host. Commanded Rotation direction of host. direction Rotation direction Rotation direction of host. Process status Line 1 - Desired parameters of host and Line 2 - its dynamic value (For all lines) Line 3 - 1.

  • Page 110: Tcp/Ip Configuration Page

    10.2.3 TCP/IP Configuration Page The TCP/IP Configuration web page provides details about the module’s EtherNet/IP settings and network activities. Information Description IP Address IP address of the module Subnet Mask Subnet mask for the module’s network Gateway Address Address for the gateway device on the module’s network BOOTP Whether BOOTP is being used to configure...

  • Page 111: Configure E-Mail Notification Web Page

    10.2.4 Configure E-mail Notification Web Page The Configure E-mail Notification web page contains selections and data fields for configuring the module to automatically send e-mail messages to desired addresses when selected types of events occur. By default, this configuration is not protected. After configuration, the settings can be protected by setting Web Features (parameter 30) E-mail Cfg Bit 0 value to “0”...

  • Page 112: 2Stopping E-Mail Messages

    Subject: Notice from example drive Seq C - The MDI host "MD65 4C 1P 1:0V .50HP" at 10.91.97.59. Please do not reply to this message, as the module cannot process replies. The MDI host has logged the following fault (trip):...

  • Page 113: Configure Process Display Web Page

    10.2.5 Configure Process Display Web Page The Configure Process Display web page enables you to set a host’s parameters whose values you want shown in “Process status” fields on the Home page and the Process Display pop-up window. (When the module is operated in Multi-Drive mode, the Home Page does not show a “Process status”...

  • Page 114: Mdi Device Information

    Information Description Product Text Text identifying the device Vendor ID 1 = Reliance Electric Device Type Product Code Code for the product name and its rating Revision Firmware revision used by the device Serial Number Serial number of the device...
  • Page 115 10-13 Viewing the Module’s Web Pages...
  • Page 116 10-14 EtherNet/IP Communications Module...

  • Page 117: Appendix A Technical Specifications

    PPENDIX Technical Specifications Communications Network Protocol EtherNet/IP Data Rates 10/100 Mbps Half/Full Duplex Drive Protocol Data Rates 19.2 kbps Electrical Consumption Drive 350 mA at 5 VDC supplied by the host (for example, the drive) Network None Mechanical Dimensions Height 19 mm (0.75 in) Length 86 mm (3.39 in)
  • Page 118 Regulatory Compliance UL508C CAN / CSA C22.2 No. 14-M91 EN50178 and EN61800-3 CTick AS/NZS 2064, Group 1, Class A Note: This is a product of category C2 according to IEC61800-3. In a domestic environment this product may cause radio interference in which case supplementary mitigation measures may be required.

  • Page 119: Appendix B Module Parameters

    PPENDIX Module Parameters The following information is provided for each EtherNet/IP module parameter along with its description: Parameter Number: Unique number assigned to each parameter. Parameter Name: Unique name assigned to each parameter. Range: Predefined parameter limits or selections. Default: Factory default setting.
  • Page 120 Mode Range: 0 = Single Drive 1 = Multiple Drive Default: 0 = Single Drive Type: Read Only Reset Required: N/A Display the Single or Multi-Drive operating mode selected with the Operating Mode Switch (SW1) on the module. BOOTP Range: 0 = Disabled 1 = Enabled Default:...
  • Page 121 Subnet Cfg 1 Subnet Cfg 2 Subnet Cfg 3 Subnet Cfg 4 Range: 0 to 255 Default: Type: Read/Write Reset Required: Yes Sets the bytes of the subnet mask. 255 . 255 . 255 . 255 Subnet Cfg 1 Subnet Cfg 2 Subnet Cfg 3 Subnet Cfg 4 To set the subnet mask using these parameters, parameter 02...
  • Page 122 EN Rate Cfg Range: 0 = Autodetect 1 = 10 Mbps Full 2 = 10 Mbps Half 3 = 100 Mbps Full 4 = 100 Mbps Half Default: 0 = Autodetect Type: Read/Write Reset Required: Yes Configures the network data rate and duplex mode at which the module communicates.
  • Page 123 Reset Module Range: 0 = Ready (No action) 1 = Reset Module 2 = Set Defaults (Restores module to factory-default settings) Default: 0 = Ready Type: Read/Write Reset Required: No This parameter is a command. No action is taken if it is set to “Ready.”...
  • Page 124 Idle Flt Action Range: 0 = Fault 1 = Stop 2 = Zero Data 3 = Hold Last 4 = Send Flt Cfg Default: 0 = Fault Type: Read/Write Reset Required: No Sets the action that the module and the drive will take if the module detects that Ethernet communications have been disrupted.
  • Page 125 Flt Cfg Ref Range: 0 to 65535 Default: Type: Read/Write Reset Required: No Sets the Reference data that is sent to the drive if any of the following is true: • Comm Flt Action (18) is set to Send Flt Cfg and communications are disrupted.
  • Page 126 MDI I/O Act Range: 0 = Drive Active 1 = Drive Inactive Default: xxx0 0000 Type: Read Only Reset Required: N/A Displays the Drives that are active in the Multi-Drive mode. 0 = Drive 0 Active 1 = Drive 1 Active 2 = Drive 2 Active 3 = Drive 3 Active 4 = Drive 4 Active...
  • Page 127 Web Enable Range: 0 = Disabled 1 = Enabled Default: 0 = Disabled Type: Read Only Reset Required: N/A Displays the setting of the Web Pages Switch (SW2) on the module when the module was last reset. Web Features Range: 0 = Disabled 1 = Enabled Default:...
  • Page 128 B-10 EtherNet/IP Communications Module...
  • Page 129 PPENDIX EtherNet I/P Objects Appendix C presents information about the EtherNet/IP objects that can be accessed using Explicit Messages. For information on the format of Explicit Messages and sample ladder logic programs, refer to Chapter 9, Using Explicit Messaging. Class Code Object Hex.
  • Page 130 Data Type Description SINT 8-bit signed integer USINT 8-bit unsigned integer 16-bit signed integer UINT 16-bit unsigned integer DINT 32-bit signed integer UDINT 32-bit unsigned integer BOOL 8-bit value -- low bit is true or false BOOL[n] Array of n bits STRING[n] Array of n characters SHORT_STRING...
  • Page 131 UINT of Instance Attributes Instance Attributes Attribute Access Rule Name Data Type Description Vendor ID UINT 5 = Reliance Electric Device Type UINT Product Code UINT Number identifying product name and rating Revision: STRUCT of: Major USINT Value varies Minor...
  • Page 132 C.2 Assembly Object Class Code Hexadecimal Decimal 0x04 Instances Instance Description All I/O data being read from the MDI device (read-only) All I/O data written to the MDI device (read/write) Class Attributes Attribute Access Rule Name Data Type Description Revision UINT Max Instance UINT...
  • Page 133 C.3 Register Object Class Code Hexadecimal Decimal 0x07 Instances Input/ Size Instance Description Output (in bits) Logic Command and Reference for all Varies drives Logic Status and Feedback for all drives Varies Logic Command and Reference for drive 0 Out Logic Status and Feedback for drive 0 Logic Command and Reference for drive 1 Out Logic Status and Feedback for drive 1...
  • Page 134 Input/ Size Instance Description Output (in bits) Logic Command for Drive 1 Feedback for Drive 1 Reference for Drive 1 Feedback for Drive 1 Logic Command Status for Drive 2 Logic Status for Drive 2 Reference for Drive 2 Feedback for Drive 2 Logic Command Status for Drive 3 Logic Status for Drive 3 Reference for Drive 3...
  • Page 135 Instance Attributes Attribute Data Access Rule Name Type Description Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data. 0 = good 1 = bad Direction BOOL Direction of data transfer 0 = Input (Drive to EtherNet/IP 1 = Output (EtherNet/IP to drive) Size UINT...
  • Page 136 C.4 Parameter Object Class Code Hexadecimal Decimal 0x0F Instances (Single-Drive Mode) The number of instances is as shown below. Instance Description Class Drive Parameter 1 Drive Parameter n n + 1 Module Parameter 1 n + m Module Parameter m n represents the number of parameters in the drive.
  • Page 137 In addition, the parameters for the other MDI devices can be accessed using the instance-offset encoding shown in the table below: Instances (Dec.) Single-Drive Mode Multi-Drive Mode 16384 - 17407 Instances 0 - 1023 in the Instances 0 - 1023 in the module module 17408 - 18431 Instances 0 - 1023 in the...
  • Page 138 Instance Attributes Attribute Access Rule Name Data Type Description Parameter Value Link Path Size USINT 0 = No link specified n = The size of Attribute in 3 bytes Link Path Descriptor WORD 0 = False, 1 = True Bit 1 = Supports ENUMs Bit 2 = Supports scaling Bit 3 = Supports scaling links Bit 4 = Read only...
  • Page 139 Attribute Access Rule Name Data Type Description Base Link UINT Offset Link UINT Decimal USINT Precision Access rule is defined in bit 4 of instance attribute 4. 0 = Get/Set, 1 = Get. Specified in descriptor, data type, and data size. Value varies based on parameter instance.
  • Page 140 C.5 Parameter Group Object Class Code Hexadecimal Decimal 0x10 Instances The number of instances depends on the number of groups in the device. A group of module parameters is appended to the list of groups in the device. The total number of groups can be read in Instance 0, Attribute 2.
  • Page 141 Instance Attributes Attribute Access Rule Name Data Type Description Group Name SHORT_ Group name String STRING Number of UINT Number of parameters in group. Members in Group 1st Parameter UINT Number in Group 2nd Parameter UINT Number in Group UINT Value varies based on group instance.
  • Page 142 C.6 PCCC Object Class Code Hexadecimal Decimal 0x67 Instances Supports Instance 1. Class Attributes Not supported. Instance Attributes Not supported. Services Implemented for: Service Code Class Instance Service Name 0x4B Execute_PCCC 0x4C Execute_DH+ Message Structure for Execute_PCCC Request Response Data Data Name Type...
  • Page 143 Message Structure for Execute_DH+ Request Response Data Data Name Type Description Name Type Description DLink UINT Destination Link ID DLink UINT Destination Link ID DSta USINT Destination Station DSta USINT Destination Station Number Number DUser USINT Destination “User” DUser UDINT Destination “User”...

  • Page 144: Message

    N-Files MDI Port Assignments MDI Port No. Single-Drive Mode Multi-Drive Mode The drive Drive 0 The module Drive 1 The slave Drive 2 Not supported Drive 3 Not supported Drive 4 Not supported The module N-File Description This N-file lets you use Emulated Block Transfer messages to read and write many types of MDI messages.
  • Page 145 This N-file lets you read and write some values configuring the port N42:3 Time-out (read/write): Time (in seconds) allowed between messages to the N41 or N44 file. If the module does not receive a message in the specified time, it performs the fault action configured in its Comm Flt Action parameter.
  • Page 146 N-File Description N10 - N18 This N-file lets you read and write parameter values in the drive and the module. Single-Drive Mode Multi-Drive Mode N10:0 Number of parameters in the drive Number of parameters in Drive 0 N10:1 - 999 Drive parameters 1 - 999 Drive 0 parameters 1 - 999 N11:0 - 999...
  • Page 147 C.7 MDI Device Object Class Code Hexadecimal Decimal 0x92 Instances The number of instances depends on the number of components in the device. The total number of components can be read in Instance 0, Attribute 4. Instances (Hex) (Dec) Device Example Description 0x0000-0x3FFF 0-16383...
  • Page 148 Attribute Access Rule Name Data Type Description User Definable STRING[16] Text identifying the device with a Text user-supplied name. Status Text STRING[12] Text describing the status of the device. Configuration BYTE Identification of variations. Code Configuration STRING[16] Text identifying a variation of a Text family device.
  • Page 149 Instance Attributes Attribute Access Rule Name Data Type Description Component STRING[32] Name of the component Name Component STRUCT of Firmware BYTE Major Revision Revision BYTE Minor Revision Component BYTE Hardware Change Number Component Serial DWORD Value between 0x00 and Number 0xFFFFFFFF Services Implemented for:...
  • Page 150 C.8 MDI Parameter Object Class Code Hexadecimal Decimal 0x93 Instances The number of instances depends on the number of parameters in the device. The total number of parameters can be read in Instance 0, Attribute 0. Instances (Dec.) Single-Drive Mode Multi-Drive Mode 0 - 16383 Instances 0 - 16383 in the drive...
  • Page 151 Attribute Access Rule Name Data Type Description Class WORD 2 = MDI Revision First WORD The first parameter that has been written Parameter with a value outside of its range. A “0” Processing indicates no errors. Error Link BYTE 0 = No operation Command 1 = Clear all parameter links (This does not clear links to function blocks.)
  • Page 152 Attribute Access Rule Name Data Type Description MDI Read STRUCT of Basic BOOL[32] Descriptor CONTAINER Parameter value CONTAINER Minimum value CONTAINER Maximum value CONTAINER Default value STRING[16] Parameter name STRING[4] Units (e.g., Amp, Hz) STRING[16] Parameter name Parameter Name STRING[16] Customer-supplied parameter name Parameter Alias...
  • Page 153 Name Description Not Recallable 0 = Recallable from NVS 1 = Not Recallable from NVS ENUM 0 = No ENUM text 1 = ENUM text Writable 0 = Read only 1 = Read/write Not Writable When 0 = Writable when enabled (e.g., drive running) Enabled 1 = Not writable when enabled 10 Instance...
  • Page 154 Formulas for Converting Decimal Places Display Value = ((Internal Value + Offset) x Multiplier x Base) / (Divisor x 10 Decimal Place) (Multiplier x Base)) Internal Value = Display Value x Divisor x 10 Offset Common Services Implemented for: Service Code Class Instance...
  • Page 155 Class Code Hexadecimal Decimal 0x97 Products such as MD65 drives use this object for faults. Modules use this object for events. Instances The number of instances depends on the maximum number of faults or events supported in the queue. The maximum number of faults/events can be read in Instance 0, Attribute 2.
  • Page 156 Attribute Access Rule Name Data Type Description Number of WORD Number of faults/events in the Recorded Faults queue. A “0” indicates the fault queue is empty. Fault Parameter WORD Reserved Reference Instance Attributes Attribute Access Rule Name Data Type Description Full/All STRUCT of WORD Fault code...
  • Page 157 C.10 MDI Diagnostic Object Class Code Hexadecimal Decimal 0x99 Instances The number of instances depends on the maximum number of diagnostic items in the device. The total number of diagnostic items can be read in Instance 0, Attribute 2. Instances (Dec.) Single-Drive Mode Multi-Drive Mode 0 - 16383...
  • Page 158 Instance Attributes Attribute Access Rule Name Data Type Description Full/All Info STRUCT of BOOL[32] Descriptor Value CONTAINER Minimum value CONTAINER Maximum value CONTAINER Default value CONTAINER Pad Word WORD Pad Word WORD Units (e.g., amp, Hz) STRING[4] UINT Multiplier UINT Divisor UINT Base...
  • Page 159 C.11 TCP/IP Interface Object Class Code Hexadecimal Decimal 0xF5 Instances The module supports one instance of the TCP/IP Interface object. Number Description Class Attributes Object Attributes Class Attributes Access Attribute ID Rule Name Data Type Description Revision UINT The revision of this object Instance Attributes Attribute Access...
  • Page 160 Attribute Access Rule Name Data Type Description Physical Link STRUCT of Object UINT Path size Padded Path EPATH Interface STRUCT of Configuration UDINT Module’s IP address UDINT Module’s subnet mask UDINT Module’s gateway address UDINT Primary name server UDINT Secondary name server STRING Default domain name Host Name...
  • Page 161 C.12 Ethernet Link Object Class Code Hexadecimal Decimal 0xF6 Instances The module supports one instance of the TCP/IP Interface object. Number Description Class Attributes Object Attributes Class Attributes Attribute Access Rule Name Data Type Description Revision UINT The revision of this object Instance Attributes) Attribute Access...
  • Page 162 Attribute Access Rule Name Data Type Description Media STRUCT RX = Received, TX = Transmitted Counters UDINT RX frames not having integral number of octets long UDINT RX frames not passing FCS check UDINT TX frames having one collision UDINT TX frames having multiple collisions UDINT Number of times of SQE test error message...
  • Page 163 EtherNet/IP module. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation. D.1 MD60 and MD65 Drives Logic Command Word Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command...
  • Page 164 Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command Description Reference 000 = No Command Select 001 = Freq Source = Select 010 = Freq Source = Int. Freq 011 = Freq Source = Comm 100 = Present Freq 0 101 = Present Freq 1 110 = Present Freq 2...
  • Page 165 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status Description Digital Input 3 Status Digital Input 4 Status This status is available for only MD65 drive with firmware version 2.xx (or higher). Logic Command/Status Words...
  • Page 166 EtherNet/IP Communications Module...
  • Page 167 LOSSARY BOOTP (Bootstrap Protocol) - Enables the module to configure itself dynamically at boot time if the network has a BOOTP server. The BOOTP server assigns the module a preconfigured IP address, a subnet mask, and a gateway address; therefore, you do not have to configure these using the parameters in the module.
  • Page 168 - When communications are disrupted (for example, a cable is disconnected), the module and MD65 drive can respond with a user-defined fault configuration. The user sets the data that is sent to the drive in the fault configuration parameters (parameters 20 (Flt Cfg Logic) through 21 (Flt Cfg Ref).
  • Page 169 - When communications are disrupted (for example, a cable is disconnected), the module and MD65 drive can respond by holding last. Hold last results in the drive receiving the last data received via the EtherNet/IP connection before the disruption. If the drive was running and using the reference from the module, it will continue to run at the same reference.
  • Page 170 MDI product - A device that uses the MDI communications interface to communicate with one or more peripheral devices. For example, a motor drive such as a MD65 drive is a MDI product. In this manual, a MDI product is also referred to as “product” or “host.”...
  • Page 171 RSLogix - A tool for configuring and monitoring controllers to communicate with connected devices. It is a 32-bit application that runs on various Windows operating systems. Information about RSLogix software can be found a: http:///www.software.rockwell.com/rslogix. RSNetWorx for EtherNet/IP - RSNetWorx for EtherNet/IP software is a tool for configuring and monitoring EtherNet/IP networks and connected devices.
  • Page 172 VS Utilities software - A software tool for monitoring and configuring Reliance Electric products and modules. VS Utilities can be used to configure the EtherNet/IP module and MD65 drives. zero data - When communications are disrupted (for example, a cable is disconnected), the module and drive can respond with zero data.
  • Page 173 NDEX assembly object EN Rate Act (16) assistance, technical EN Rate Cfg (15) equipment required for installation Ethernet connector Ethernet link object C-33 events BOOTP (2) codes and descriptions 8-11 BOOTP (Bootstrap Protocol) viewing and clearing 8-11 configuring the module using example disabling Explicit Messages...
  • Page 174 4-12 publications, related diagnostic items dimensions features installing reference adjustment, setting mounting 3-10 3-11 3-12 Reference/Feedback, using 3-13 3-14 3-15 3-16 register object 3-17 3-18 3-19 3-20 regulatory compliance 3-21 Reliance Electric, getting assistance Index-2 EtherNet/IP Communications Module...
  • Page 175 from parameters Reset Module (17) resetting the module 4-11 Rockwell Automation, getting assistance from TCP/IP interface object C-31 RSLogix 5000 configuration technical assistance troubleshooting 8-13 scanner, configuring Set Attribute Single message UDP (User Datagram Protocol) example Setting Operating Mode and Web Pages Switches specifications VS Utilities software...
  • Page 176 Index-4 EtherNet/IP Communications Module...
  • Page 180 U.S. Drives Technical Support Tel: (1) 262.512.8176, Fax: (1) 262.512.2222, Email: support@drives.ra.rockwell.com, Online: www.ab.com/support/abdrives Publication D2-3529- April 2004 Copyright © 2004 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.

Table of Contents