MD65 EtherNet/IP Communications Module M/N MDCOMM-ENET Instruction Manual D2-3529
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.
CONTENTS 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.
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 ...................................... 6-5 6.
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..................... 10-6 10.2.3 TCP/IP Configuration Page ..............................
IV EtherNet/IP Communications Module
List of Figures Figure 2.1 – Components of the EtherNet/IP Module ................................. 2-1 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 ........................
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 – Message Format for a Get Attribute Single Message .............
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.
VIII EtherNet/IP Communications Module
CHAPTER 1 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. It can be used with other products that implement MDI, which is a peripheral communication interface.
1.2 Related Documentation Refer to the following related publications as necessary for more information. All of the publications are available from http://www.theautomationbookstore.com or http://www.reliance.com. 1.3 • • • D2-3529 MD65 Ethernet Manual D2-3519 MD65 User Manual D2-3488 VS Utilities Getting Results Manual Online help installed with the software • • ENET-IN001... EtherNet/IP Planning and Installation Manual ENET-AP001...
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 LED’s are on bottom side of module board. ➀ ➁ ➃ ➂ ➀ Status Indicators Four LEDs to indicate the status of the connected drive, module, and network. ➁ MDI Connector A 20-pin, single-row shrouded male header.
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 15.24 cm (6 in) Internal Interface cable One EtherNet/IP Communications Module User Manual (D2-3529) To install and configure the EtherNet/IP module, you must supply the items listed in table 2.2. Table 2.
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 ❒ 1 Review the safety precautions for the module. ❒ 2 Verify that the drive is properly installed. MD65 AC Drive User Manual ❒ 3 Action Install the module. Verify that the drive and the network are not powered.
✔ Step Action ❒ 7 Create a ladder logic program. Use a programming tool to create a ladder logic program that enables you to do the following: 2-4 Refer to: • Control the module and connected drive using I/O • Monitor or configure the drive using Explicit messages.
CHAPTER 3 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... • Verify that you have all required equipment. Refer to chapter 2, Getting Started, for a list of equipment. ! Important: 3.
Step 1. Set the Operating Mode Switch (SWI) for Single or MultiDrive operation (see figure 3.1 and setting descriptions below). For complete details on Multi-Drive operation, see chapter 8. WEB PAGES SWITCH OPERATING MODE SWITCH Multi-Drive Operation Position 1 Single-Drive Operation Position Enable Web Position 2 Disable Web Position Figure 3.1 – Setting Single/Multi-Drive Operation and Web Page Enable Switches Table 3.
Table 3.2 – Setting 2 Descriptions SW2 Settings Description Down position (DN = Closed = 0) Disables the module web pages. Up position (UP = Open = 1) Enables the module web pages (default 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 power from the drive, and then verify power has been discharged before installing or removing a module.
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 – MDI Ports and Internal Interface Cables .
3.4 Connecting the Module to the Network ! Step 1. 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. Remove power from the drive. Step 2. Use static control precautions. Step 3. Remove the drive cover. Step 4. Connect an Ethernet cable to the EtherNet/IP network.
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. ! 3.6 Step 1. Install the required special cover on the drive. The status indicators can be viewed on the front of the drive after power has been applied. Step 2. Apply power to the drive.
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.
4.2 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. Table 4.2– Using the LCD OIM or CopyCat Keypad Step Key(s) 1. Power up the drive. Plug the OIM or CopyCat Keypad into the drive. The Parameters menu for the drive will be displayed. 2.
Table 4.2– Using the LCD OIM or CopyCat Keypad Step Key(s) 4. Press Enter to select the Ethernet/IP module. The Parameters menu for the module will be displayed. 5. Press Enter to access the parameters. Edit the module parameters using the same techniques that you use to edit parameters. 4.
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. Edit the fields shown in table 4.3 in the New Entry Dialog box: Table 4.3 – Editing the New Entry Dialog Box In this field: A unique IP address for the module. Subnet Mask1 A subnet mask for the module’s network.
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. 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.
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 2 (BOOTP) to Disabled as shown in figure 4.4.
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. This parameter must be set to Disabled to configure the subnet mask using parameters. Step 2.
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. Step 1. Set the value of parameter 15 (EN Rate Cfg) to the data rate at which your network is operating.
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 MultiDrive Mode, refer to chapter 8. 4.7 Step 2. If a drive is enabled, configure the parameters in the drive to accept the Logic Command and Reference from the module. For example, set parameter 36 (Start Source) and parameter 38 (Speed Reference) in an MD65 drive to “Comm Port.” Step 3. Reset the module.
Table 4.4 – Selections for Drive Response to Communication Fault Value Action 0 Fault (default) Description The drive is faulted and stopped (Default). 1 Stop 2 Zero Data The drive is stopped, but not faulted. 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 after a communications disruption.
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. Determine how your drive will respond before resetting a connected module.
4.8 Viewing the Module Configuration The parameters in table 4.6 provide information about how the module is configured. You can view these parameters at any time. Table 4.6 – Module Configuration Parameters Number 1 Name Mode Description The mode in which the module is set: Values 0 = Single drive operation 1 = Multi-Drive operation 16 EN Rate Act.
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. By default, settings are not protected. To protect an e-mail configuration, set the value of Email Cfg Bit 0 to “0” (Disabled).
4-14 EtherNet/IP Communications Module
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 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. This chapter provides the steps that are needed to configure a simple network like the network in figure 5.1.
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 5000. The RSLogix 5000 window appears as shown in figure 5.2. RE_DF1-2\1 Figure 5.2 – RSLogix 5000 Window Step 2. 5-2 In the Control Organizer pane, right-click the I/O Configuration folder and select New Module (figure 5.2).
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. Reliance Electric Figure 5.4 – Module Properties Dialog Box - Page 1 Step 5.
Table 5.1 – Module Properties Fields Field Name Slot Revision IP Address Electronic Keying Step 6. 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.
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.
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. 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.
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. The additional 2 words for the inputs are for ENBT overhead. Table 5.
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 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.
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. MD65_Demo RE_DF1-2\1 Figure 5.
5-10 EtherNet/IP Communications Module
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 MD65 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.
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: • Configuration of the Operating Mode Switch (SW1) on the module and parameter 22 (MDI I/O Cfg).
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. 6.4 Using Reference/Feedback When enabled, the Reference/Feedback begins at word 1 in the I/O image. The Reference (16 bits) is produced by the controller and consumed by the module. The Feedback (16 bits) is produced by the module and consumed by the controller. Size 16-bit Valid Values1 In I/O Image 0.
6.6 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. MD65_Demo: C RE:ETHERNET_... MD65_Demo: I RE:ETHERNET_... MD65_Demo: O RE:ETHERNET_... Figure 6.
Program Tags In addition to the Controller tags that are automatically created, you need to create the Program tags shown in figure 6.4 for this sample program. MD65 ACTIVE MD65 AT SPEED MD65 FAULT MD65 FORWARD MD65 READY MD65 REVERSE MD65 FEEDBACK Figure 6.4 – Program Tags for Sample ControlLogix Ladder Logic Program 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.
6.8 Sample ControlLogix Ladder Logic Program 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/ MDCOMMENET EtherNet/IP module. The I/O image is as follows: INPUT (4 INT words) OUTPUT (2 INT words) MD65-Demo:I.Data[0] = ENBT Overhead MD65-Demo:I.Data[0] = MD65 Logic Command MD65-Demo:I.Data[1] = ENBT Overhead MD65-Demo:I.Data[1] = MD65 Reference MD65-Demo:I.Data[2] = MD65 Logic Status MD65-Demo:I.
6 This rung displays the Feedback word from the MD65.. Note that it is set in Hz and not in engineering units. For example, "300" equates to 30.0 Hz (the decimal point is always implied). MD65 Feedback MOV Move Source MD65_Demo:I.Data[3] 500 Dest Feedback 500 Logic Command bit control rungs are provided for display purposes only. The MD65_Demo: 0.Data[0].x bits could be used directly elsewhere in the ladder program. MD65 Demo Logic Command STOP Stop_Command MD65_Demo:O.Data[0].
6-8 EtherNet/IP Communications Module
CHAPTER 7 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. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
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.
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.
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 Message Response ➌ ➋ ➊ Format the required data and set up the ladder logic program to send an Explicit Message request to the scanner or bridge module (download).
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. Also, to format and execute these message examples, you need the Controller tags displayed in figure 7.3. MD65_Demo: C RE:ETHERNET_...
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 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 Service Type1 Service Code1 Class Instance Attribute Destination Value Get Attribute Single e (Hex.) f (Hex.) 39 (Dec.
Ladder Logic Rung Example Get Attribute Single Message Example Explicit Messaging Exampl Example 13 Reading a single parameter (Get Attribute Single command) PerformParameterRead Type - CIP Generic Message Control MSG ParameterReadMessage ... EN DN ER 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.
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: Table 7.2 – Key Settings for Data Format Configuration Service Type1 Service Code1 Class Instance Attribute Source Element Source Length Value Set Attribute Single 10 (Hex.
Ladder Logic Rung Example Explicit Messaging Example Writing a single parameter (Set Attribute Single command) PerformParameterWrite Type - CIP Generic 14 Message Control MSG ParameterWriteMessage ... EN DN ER Figure 7.8 – Set Attribute Single Message Example Example Source Data 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.
7-10 EtherNet/IP Communications Module
CHAPTER 8 Using Multi-Drive Mode Chapter 8 provides information and a ControlLogix Ladder example to explain how to use Multi-Drive mode. ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
EtherNet/IP up to 5 drives per node Up to 4 MD65 or MD60 Drives MD65 MDCOMM-ENET AK-U0-RJ45-TB2P Connector with Terminating Resistor RS-485 AK-U0-RJ45-TB2P AK-U0-RJ45-TB2P Connector with Terminating Resistor Figure 8.2 – Multi-Drive Mode Example for Network Benefits of Multi-Drive mode include: • Lower hardware costs. Only one MDCOMM-ENET module is needed for up to five drives. The MD60 can also be used for the daisy-chained drives instead of MD65 drives. • Reduces the network node count.
Table 8.1 – Throughput Time for Logic Command/Reference • 8.2 Drive Additional Throughput Time versus Single Mode MD65 with MDCOMM-ENET 0 ms MD65 with MDCOMM-ENET plus 1 drive +24 ms MD65 with MDCOMM-ENET plus 2 drives +48 ms MD65 with MDCOMM-ENET plus 3 drives +72 ms MD65 with MDCOMM-ENET plus 4 drives +96 ms Since the RS-485 ports are used for daisy-chaining the drives, there is no connection for a peripheral device such as an OIM.
The wiring diagram for using AK-U0-RJ45-TB2P terminal block connectors is shown in figure 8.4. To MD65 with MDCOMM-ENET To Drive #2 To Drive #3 To Drive #4 To Drive #5 120 ¼ Watt Resistor 120 ¼ 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. 8.3 Understanding the I/O Image The terms input and output are defined from the scanner’s point of view.
Figure 8.5 illustrates the Multi-Drive I/O image with 16-bit words.
8.4 Configuring the RS-485 Network Table 8.2 shows the parameters that must be set in the daisychained 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) 1-247 (must be unique) A107 (Comm Format) 0 (“RTU 8-N-1”) Note: The RS-485 network is fixed at 19.2K baud, 8 data bits, no parity, and 1 stop bit.
Important: 8.5 MDCOMM-ENET parameters can be set using MDI peripheral (OIM) ONLY when the Operating Mode Switch is in the Single 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.
8.5.3 Drive Settings for the Example Program Table 8.5 shows the drive settings for the example program. Table 8.
Table 8.7 describes the tags used for Drive 0. Table 8.
8.6.1 Main Routine The Main Routine reads the network Input Image from the scanner, calls the various drive control subroutines, and writes the network Output Image to the scanner. See figure 8.6. 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/ MDCOMMENET EtherNet/IP module. The I/O image is as follows: INPUT (4 INT words) OUTPUT (2 INT words) MD65-Demo:I.Data[0] = ENBT Overhead MD65-Demo:I.
This rung writes the output image to the scanner.
8.6.2.1 Drive 0 Control Routine 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 Drive0StatusActive DriveInputImage[0].3 Drive0StatusForward DriveInputImage[0].7 Drive0StatusFaulted DriveInputImage[0].
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 MSG Type - CIP Generic Message Control ParameterRDMessage0 ... 13 EN DN ER PerformParameterWrite0 MSG Type - CIP Generic Message Control ParameterWRMessage0 ... 14 EN DN ER RET 15 Return (End) Figure 8.
8.6.2.2 Drive 1 Control Routine 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 Drive1StatusActive DriveInputImage[2].3 Drive1StatusForward DriveInputImage[2].7 Drive1StatusFaulted DriveInputImage[2].
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 MSG Type - CIP Generic Message Control ParameterRDMessage1 ... 13 EN DN ER PerformParameterWrite1 MSG Type - CIP Generic Message Control ParameterWRMessage1 ... 14 EN DN ER RET 15 Return (End) Figure 8.
8.6.2.3 Drive 2 Control Routine 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 Drive2StatusActive DriveInputImage[4].3 Drive2StatusForward DriveInputImage[4].7 Drive2StatusFaulted DriveInputImage[4].
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 MSG Type - CIP Generic Message Control ParameterRDMessage2 ... 13 EN DN ER PerformParameterWrite2 MSG Type - CIP Generic Message Control ParameterWRMessage2 ... 14 EN DN ER RET 15 Return (End) Figure 8.
8.6.2.4 Drive 3 Control Routine 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 Drive3StatusActive DriveInputImage[6].3 Drive3StatusForward DriveInputImage[6].7 Drive3StatusFaulted DriveInputImage[6].
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 MSG Type - CIP Generic Message Control ParameterRDMessage3 ... 13 EN DN ER PerformParameterWrite3 MSG Type - CIP Generic Message Control ParameterWRMessage3 ... 14 EN DN ER RET 15 Return (End) Figure 8.
8.6.2.5 Drive 4 Control Routine 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 Drive4StatusActive DriveInputImage[8].3 Drive4StatusForward DriveInputImage[8].7 Drive4StatusFaulted DriveInputImage[8].
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 MSG Type - CIP Generic Message Control ParameterRDMessage4 ... 13 EN DN ER PerformParameterRead4 MSG Type - CIP Generic Message Control ParameterWRMessage4 ... 14 EN DN ER RET 15 Return (End) Figure 8.11 – Drive 4 Control Routine (Continued) 8.
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.
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).
8.8 8-24 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 powered down, communications with the four daisy-chained drives (Drive 1 to Drive 4) are disrupted and the drives will take their corresponding Comm Loss Actions.
CHAPTER 9 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.) DRIVE MS Bottom side of adapter board Number Status Indicator Description Refer to... ➊ DRIVE MDI Connection Status Section 9.1.1 ➋ MS Module Status Section 9.1.
9.1.1 DRIVE Status Indicator Table 9.1 – DRIVE Status Indicator: State Definitions Status Off Cause The module is not powered or is not connected properly to the drive. Flashing In Single mode, the Red module is not receiving communication from the drive. In Multi-Drive mode, the module is not receiving communication from the drive, or the drive is not a Reliance Electric drive. Solid Red • Securely connect the module to the drive using the Internal Interface (ribbon) cable.
9.1.2 MS Status Indicator Table 9.2 – MS Status Indicator: State Definitions Status Off Cause The module is not powered or properly connected to the drive. Flashing The module has Red failed the firmware test. Solid Red The module has failed the hardware test. Flashing The module is Green operational but is not transferring I/O data. Solid Green The module is operational and transferring I/O data.
9.1.3 NET A Status Indicator Table 9.3 – NET A Status Indicator: State Definitions Status Off Corrective Action • Securely connect the module to the drive using the Internal Interface (ribbon) 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.
9.1.4 NET B Status Indicator Table 9.4 – NET B Status Indicator: State Definitions Status Off 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 network. 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.
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) No. Name Description 1 Reserved 2 Logic Cmd Logic Command being transmitted to the drive by the module.
Table 9.5 – Module Diagnostic Items (Continued)(Single Drive Mode) No. 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.
Table 9.5 – Module Diagnostic Items (Continued)(Single Drive Mode) No. Name 48 EN Rx Errors Description 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 9.3 A count of the number of transmit errors reported by the EtherNet MAC. Module Diagnostic Items in MultiDrive Mode Table 9.6 lists diagnostic items that can be accessed using VS Utilities software or the LCD OIM.
Table 9.6 – Module Diagnostic Items (Continued)(Multi-Drive Mode) No. 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. 17 Drv 3 Logic Sts Logic Status being received from drive 3 by the module. 18 Drv 3 Feedback Feedback being received from drive 3 by the module.
Table 9.6 – Module Diagnostic Items (Continued)(Multi-Drive Mode) No. 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.
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. However, if you encounter communication problems, the events can help you or Rockwell Automation personnel troubleshoot the problem. Table 9.
Table 9.7 – Event Codes and Descriptions Code Event 10 Slave Detected 11 Slave Removed 12 Slave Logon 13 Slave Timeout 14 15 Slave Brand Flt Host 0 Logon 16 Host 1 Logon 17 Host 2 Logon 18 Host 3 Logon 19 Host 4 Logon 20 21 22 23 24 25 26 27 28 29 30-39 Host 0 Timeout Host 1 Timeout Host 2 Timeout Host 3 Timeout Host 4 Timeout Host 0 Brand Flt Host 1 Brand Flt Host 2 Brand Flt Host 3 Brand Flt Host 4 Brand Flt Reserved Description The module detected that the slave has been connected.
Table 9.7 – Event Codes and Descriptions Code Event 46 EN Comm Flt Description The module has performed the “Comm Flt” action specified by the user. 47 EN Idle Flt The module has performed the “Idle Flt” action specified by the user. 48 PCCC IO Open The module has begun receiving PCCC Control messages (the PCCC Control Timeout was previously set to non-zero value). 49 PCCC IO Close The device sending PCCC Control messages to the module has set the PCCC Control Timeout to a value of 0.
9-14 EtherNet/IP Communications Module
CHAPTER 10 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. 10.1 Accessing the Module’s Main Web Page After configuring the module, you can view its web pages.
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.
10.1.1 Title Bar on Module Web Pages The title bar appears on all module web pages, including its Home 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. Rockwell Automation logo (at far right) The logo is also a link. Click it to view the Rockwell Automation web Home Page.
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. These differences are highlighted in table 10.2. Table 10.2 – Navigation Menu Link/Folder Description Home Link Click this link to view the module’s Home Page.
Table 10.2 – Navigation Menu Link/Folder Port 0 - X folders (X = total connected hosts) Description Click a respective Port folder to expand and view its device’s “Module Information” link., “Module diagnostics” link, and “Fault queue” link, which 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.
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.
Information Description Product Text Description of host. Status Status of host. Commanded direction Rotation direction of host. Rotation direction Rotation direction of host. Process status Line 1 Line 2 Line 3 - Desired parameters of host and its dynamic value 1 (For all lines) 1. The parameter whose value is shown on this line can be set by using the Configure Process Display web 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.
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” (Disabled).
Step 3. Type the following information in the respective box: Information Description “IP address of...” Type in the address of the mail server that will be used to deliver the e-mail messages. “E-mail addresses to notify...” Type in addresses to where you want e-mail messages to be sent. Multiple addresses can be used, but they must be separated by commas (comma delimited). “Subject of e-mail message...” Type in the desired subject text for the email message. Step 4. Click Save Changes.
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” field for a host.) By default, this configuration is not protected.
Important:It is recommended that Web Features (parameter 30) Proc Dsp Cfg Bit 1 value be set to “0” (Disabled) after configuration. Otherwise the configuration can be changed anytime the web page is accessed with a browser. 10.2.6 MDI Device Information Pages MDI device information pages show a device’s module information, diagnostic information, and fault queue.
Viewing the Module’s Web Pages 10-13
10-14 EtherNet/IP Communications Module
APPENDIX A Technical Specifications Communications Network Protocol Data Rates EtherNet/IP 10/100 Mbps Half/Full Duplex Drive Protocol Data Rates MDI 19.2 kbps Electrical Consumption Drive Network 350 mA at 5 VDC supplied by the host (for example, the drive) None Mechanical Dimensions Height Length Width 19 mm (0.75 in) 86 mm (3.39 in) 78.5 mm (3.
Regulatory Compliance UL UL508C cUL CAN / CSA C22.2 No. 14-M91 CE 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.
APPENDIX B 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. Type: Read Only or Read/Write Reset Required: Module must be reset before parameter value is recognized.
01 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. 02 BOOTP Range: 0 = Disabled 1 = Enabled Default: 1 = Enabled Type: Read/Write Reset Required: Yes Configures the module to use BOOTP so that you can set its IP address, subnet mask, and gateway address with a BOOTP server.
07 08 09 10 Subnet Cfg 1 Subnet Cfg 2 Subnet Cfg 3 Subnet Cfg 4 Range: 0 to 255 Default: 0 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 (BOOTP) must be set to Disabled.
15 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. 16 EN Rate Act Range: 0 = No Link 1 = 10 Mbps Full 2 = 10 Mbps Half 3 = 100 Mbps Full 4 = 100 Mbps Half Default: 0 = No Link Type: Read Only Reset Required: N/A Displays the actual network data rate and duplex mode used by the module.
17 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.” Resets the module if it is set to “Reset Module.” Restores the module to factory default settings if it is set to “Set Defaults.” It will be reset to “0 = Ready” after the command has been performed.
19 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. This setting is effective only if the I/O that controls the drive is transmitted through the module. ! 20 ATTENTION: Idle Flt Action (19) lets you determine the action of the module and connected drive if the controller is idle.
21 Flt Cfg Ref Range: 0 to 65535 Default: 0 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. • Idle Flt Action (19) is set to Send Flt Cfg and the scanner is put into Program mode.
23 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. 7 6 5 4 3 2 1 0 x x x 0 0 0 0 0 0 = Drive 0 Active 1 = Drive 1 Active 2 = Drive 2 Active 3 = Drive 3 Active 4 = Drive 4 Active 5 = Not Used 6 = Not Used 7 = Not Used .
29 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. 30 Web Features Range: 0 = Disabled 1 = Enabled Default: xxxx xx11 Type: Read Write Reset Required: N/A Sets the access to the Web interface and Web-configurable features.
B-10 EtherNet/IP Communications Module
APPENDIX C 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 Identity Object Hex. Dec.
Data Type Description SINT 8-bit signed integer USINT 8-bit unsigned integer INT 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] STRING[n] SHORT_STRING Array of n bits Array of n characters 1-byte length indicator + that many characters STRUCT Structure name only - no size in addition to elements CONTAINER 32-bit parameter value - sign extended if necessary TCHAR 8 or 16-bi
Class Attributes Attribute ID Access Rule 1 Get Revision UINT 1 2 Get Max Instance UINT Total number of instances 6 Get Max ID Number UINT of Class Attributes 7 7 Get Max ID Number UINT of Instance Attributes 100 Name Data Type Description Instance Attributes Attribute Access ID Rule Name Data Type Description 1 Get Vendor ID UINT 5 = Reliance Electric 2 Get Device Type UINT 127 3 Get Product Code UINT Number identifying product name and rating 4 Get Revision: Maj
C.
C.
Instance 23 Input/ Output Description Logic Command for Drive 1 Out Size (in bits) 16 24 Feedback for Drive 1 In 16 25 Reference for Drive 1 Out 16 26 Feedback for Drive 1 In 16 27 Logic Command Status for Drive 2 Out 16 28 Logic Status for Drive 2 In 16 29 Reference for Drive 2 Out 16 30 Feedback for Drive 2 In 16 31 Logic Command Status for Drive 3 Out 16 32 Logic Status for Drive 3 In 16 33 Reference for Drive 3 Out 16 34 Feedback for Drive 3 In 16 35 Log
Instance Attributes Attribute ID Access Rule 1 Get Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data. 0 = good 1 = bad 2 Get Direction BOOL Direction of data transfer 0 = Input (Drive to EtherNet/IP 1 = Output (EtherNet/IP to drive) 3 Get 4 1 Conditional Data Type Name 1 Description Size UINT Size of register data in bits Data ARRAY of BITS Data to be transferred The access rule of Set is optional if attribute 2, Direction = 1.
C.4 Parameter Object Class Code Hexadecimal Decimal 0x0F 15 Instances (Single-Drive Mode) The number of instances is as shown below. Instance Description 0 Class 1 Drive Parameter 1 n Drive Parameter n1 n+1 Module Parameter 1 n+m Module Parameter m2 1 2 n represents the number of parameters in the drive. m represents the number of parameters in the module. Instances (Multi-Drive Mode) The number of instances is as shown below.
In addition, the parameters for the other MDI devices can be accessed using the instance-offset encoding shown in the table below: Instances (Dec.
Instance Attributes Attribute Access ID Rule Name Parameter Value Data Type Description 1 1 2 Get Link Path Size USINT 0 = No link specified n = The size of Attribute in 3 bytes 3 Get Link Path 4 4 Get Descriptor WORD 0 = False, 1 = True Bit 1 = Supports ENUMs Bit 2 = Supports scaling Bit 3 = Supports scaling links Bit 4 = Read only Bit 5 = Monitor Bit 6 = Extended precision scaling 5 Get Data Type USINT 0xC2 = SINT (8 bits) 0xC3 = INT (16 bits) 0xC4 = DINT (32 bits) 0xC6 = USINT (8 b
Attribute Access ID Rule Name Data Type Description 19 Get Base Link UINT 3 20 Get Offset Link UINT 3 21 Get Decimal Precision USINT 3 1 Access rule is defined in bit 4 of instance attribute 4. 0 = Get/Set, 1 = Get. Specified in descriptor, data type, and data size. 3 Value varies based on parameter instance. 4 Refer to the EtherNet/IP specification for a description of the link path.
C.5 Parameter Group Object Class Code Hexadecimal Decimal 0x10 16 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. Number Description 0 Class Attributes 1 Drive Group 1 Attributes n Drive Group n Attributes1 n+1 Module Group Attributes 1 n represents the number of parameter groups in the drive.
Instance Attributes 1 Attribute ID Access Rule 1 Get Group Name String SHORT_ STRING Group name 2 Get Number of Members in Group UINT Number of parameters in group. 3 Get 1st Parameter UINT Number in Group 1 4 Get 2nd Parameter UINT Number in Group 1 n Get UINT 1 Name Data Type Description Value varies based on group instance.
C.6 PCCC Object Class Code Hexadecimal Decimal 0x67 103 Instances Supports Instance 1. Class Attributes Not supported. Instance Attributes Not supported.
Message Structure for Execute_DH+ Request Name Data Type Response Description Data Type Name Description DLink UINT Destination Link ID DLink UINT Destination Link ID DSta USINT Destination Station Number DSta USINT Destination Station Number DUser USINT Destination “User” number DUser UDINT Destination “User” number SLink UINT Source Link ID SLink Product Specific Source Link ID SSta USINT Source Station number SSta USINT Source Station number SUser USINT Source User n
N-Files MDI Port Assignments MDI Port No. N-File N40 Bits N40:0 N40:1 … N40:2 N40:3 N40:4 N40:5 N40:6 Single-Drive Mode Multi-Drive Mode 0 The drive Drive 0 1 The module Drive 1 2 The slave Drive 2 3 Not supported Drive 3 4 Not supported Drive 4 5 Not supported The module Description This N-file lets you use Emulated Block Transfer messages to read and write many types of MDI messages.
N42 N42:3 N42:7 N42:8 This N-file lets you read and write some values configuring the port 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. Module Port Number (read only): MDI port on the drive to which the module is connected. Peer Modules (read only): Bit field of devices having MDI Peer capabilities.
N-File N10 - N18 Description This N-file lets you read and write parameter values in the drive and the module.
C.7 MDI Device Object Class Code Hexadecimal Decimal 0x92 146 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.
Attribute ID Access Rule Data Type Description 5 Set User Definable Text STRING[16] Text identifying the device with a user-supplied name. 6 Get Status Text STRING[12] Text describing the status of the device. 7 Get Configuration Code BYTE Identification of variations. 8 Get Configuration Text STRING[16] Text identifying a variation of a family device. 9 Get Brand Code WORD 0x0002 = Reliance 11 Get NVS Checksum WORD Checksum of the non-volatile storage in a device.
Instance Attributes Attribute Access ID Rule Name Data Type Description 3 Get Component Name STRING[32] Name of the component 4 Get Component Firmware Revision STRUCT of BYTE BYTE Major Revision Minor Revision BYTE 5 Get Component Hardware Change Number 8 Get Component Serial DWORD Number Value between 0x00 and 0xFFFFFFFF Services Implemented for: Service Code Class Instance Service Name 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single EtherNet I/P Object
C.8 MDI Parameter Object Class Code Hexadecimal Decimal 0x93 147 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.
Attribute Access ID Rule Name Data Type Description 7 Get Class Revision WORD 2 = MDI 8 Get First Parameter Processing Error WORD The first parameter that has been written with a value outside of its range. A “0” indicates no errors. 9 Set Link Command BYTE 0 = No operation 1 = Clear all parameter links (This does not clear links to function blocks.
Attribute Access ID Rule 13 Get Name MDI Read Basic Data Type Description STRUCT of BOOL[32] Descriptor CONTAINER CONTAINER CONTAINER CONTAINER STRING[16] STRING[4] Parameter value Minimum value Maximum value Default value Parameter name Units (e.g.
Bit Name Description 6 Not Recallable 0 = Recallable from NVS 1 = Not Recallable from NVS 7 ENUM 0 = No ENUM text 1 = ENUM text 8 Writable 0 = Read only 1 = Read/write 9 Not Writable When Enabled 0 = Writable when enabled (e.g.
Formulas for Converting Display Value = ((Internal Value + Offset) x Multiplier x Base) / (Divisor x 10 Decimal Places) Internal Value = ((Display Value x Divisor x 10 Decimal Place) / (Multiplier x Base)) - Offset Common Services Implemented for: Service Code Class Instance 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single Service Name Object Specific Services Service Code 1 Service Name 0x32 Get_Attributes_Scattered1 0x34 Set_Attributes_Scattered1 The instance and at
C.9 MDI Fault Object Class Code Hexadecimal Decimal 0x97 151 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. Instances (Dec.
Attribute Access ID Rule Name Data Type Description 6 Get Number of Recorded Faults WORD Number of faults/events in the queue. A “0” indicates the fault queue is empty.
C.10 MDI Diagnostic Object Class Code Hexadecimal 0x99 Decimal 153 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.
Instance Attributes Attribute Access ID Rule Name 0 Get Full/All Info 1 Get/Set Value Data Type STRUCT of BOOL[32] CONTAINER1 CONTAINER CONTAINER CONTAINER WORD WORD STRING[4] UINT UINT UINT INT DWORD STRING[16] Various Description Descriptor Value Minimum value Maximum value Default value Pad Word Pad Word Units (e.g.
C.11 TCP/IP Interface Object Class Code Hexadecimal 0xF5 Decimal 245 Instances The module supports one instance of the TCP/IP Interface object.
Attribute Access ID Rule Name Data Type 4 Get Physical Link STRUCT of Object UINT Padded EPATH 5 Get Interface STRUCT of Configuration UDINT UDINT UDINT UDINT UDINT STRING 6 Get Host Name STRING Description Path size Path Module’s IP address Module’s subnet mask Module’s gateway address Primary name server Secondary name server Default domain name Host name when using DHCP Services Service Code 0x0E 0x10 C-32 Implemented for: Class Instance Yes Yes No Yes Service Name Get_Attribute_Single Set_Attribut
C.12 Ethernet Link Object Class Code Hexadecimal 0xF6 Decimal 246 Instances The module supports one instance of the TCP/IP Interface object.
Attribute Access ID Rule Name 5 Get Media Counters Data Type Description STRUCT RX = Received, TX = Transmitted of 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 UDINT TX Frames delayed first attempt by busy medium UDINT Collisions detected later than 512 bit-times in trans.
APPENDIX D Logic Command/ Status Words Appendix D provides the definitions of the Logic Command/Logic Status words that are used for some products that can be connected to the 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.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command x x x Reference Select x 1 Description 000 = No Command 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 111 = Present Freq 3 Not Used A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition will start the drive.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 x Status Description Digital Input 3 Status1 x Digital Input 4 Status1 1 This status is available for only MD65 drive with firmware version 2.xx (or higher).
D-4 EtherNet/IP Communications Module
GLOSSARY 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. BOOTP can make it easier to administer an Ethernet network. A free version of Rockwell Software’s BOOTP Server can be accessed at: http://www.reliance.com/prodserv/standriv/stdhome.htm.
EtherNet/IP network - An open producer-consumer communication network based on the Ethernet standard (IEEE 802.3), TCP/IP, UDP/IP, and CIP. Designed for industrial communications, both I/O and explicit messages can be transmitted over the network. Each device is assigned a unique IP address and transmits data on the network. The number of devices that an EtherNet/IP network can support depends on the class of IP address. For example, a network with a Class C IP address can have 254 nodes.
hold last - 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. I/O messaging - Time-critical data such as a Logic Command and Reference.
Logic Command/Logic Status - The Logic Command is used to control the MD65 drive (e.g., start, stop, direction). It consists of one 16-bit word of input to the module from the network. The definitions of the bits in this word depend on the drive. The Logic Status is used to monitor the MD65 drive (for example, operating state, motor direction). It consists of one 16-bit word of output from the module to the network. The definitions of the bits in this word depend on the drive.
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. It is a 32-bit Windows application that runs on Windows 95, Windows 98, and Windows NT.
UDP (User Datagram Protocol) - EtherNet/IP uses this protocol to transfer I/O packets using IP. UDP provides a simple, but fast capability to send I/O messaging packets between devices. This protocol ensures that modules transmit the most recent data because it does not use acknowledgements or retries. 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.
INDEX A E assembly object, C-4 assistance, technical, 1-2 EN Rate Act (16), B-4 EN Rate Cfg (15), B-4 equipment required for installation, 2-2 Ethernet connector, 2-1 Ethernet link object, C-33 events codes and descriptions, 8-11 viewing and clearing, 8-11 example Explicit Messages, 7-5 Get Attribute Single message, 7-6 ladder logic program, 6-3 to 6-7 network configuration, 5-1 to 5-9 Set Attribute Single message, 7-8 Explicit Message examples, 7-5 explicit messaging, using, 7-1 B BOOTP (2), B-2 BOOTP
I/O messaging, 6-1 to 6-7 identity object, C-2 Idle Flt Action (19), B-6 installation checklist, 2-3 required equipment, 2-2 installing the module, 3-1 to 3-6 Internal Interface cables, 3-4 IP Addr Cfg 1 (3), B-2 IP Addr Cfg 2 (4), B-2 IP Addr Cfg 3 (5), B-2 IP Addr Cfg 4 (6), B-2 IP address setting using BOOTP, 4-3 setting using parameters, 4-6 L ladder logic program, sample, 6-3 to 6-7 LCD OIM see OIM LEDs, status, 8-1 Logic Command/Status words, D-1 to D-3 Logic Command/Status, using, 6-2 M manuals, re
from, 1-2 Reset Module (17), B-5 resetting the module, 4-11 Rockwell Automation, getting assistance from, 1-2 RSLogix 5000 configuration, 6-4 parameters, 4-7 T TCP/IP interface object, C-31 technical assistance, 1-2 troubleshooting, 8-1 to 8-13 S scanner, configuring, 5-1 to 5-9 Set Attribute Single message example, 7-8 Setting Operating Mode and Web Pages Switches, 3-1 specifications, A-1 status indicators, 8-1 Subnet Cfg 1 (7), B-3 Subnet Cfg 2 (8), B-3 Subnet Cfg 3 (9), B-3 Subnet Cfg 4 (10), B-3 subn
Index-4 EtherNet/IP Communications Module
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.
