DeviceNet Communications Module M/N MDCOMM-DNET Instruction Manual D2-3520
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 DeviceNet Module Features .......................................... 1-1 1.2 Related Documentation ................................................. 1-2 1.3 Conventions Used in This Manual ................................. 1-3 1.4 Getting Assistance from Reliance Electric..................... 1-3 Chapter 2 Getting Started 2.1 DeviceNet Module Components .................................... 2-1 2.2 Required Equipment .....................................................
5.3.2 Mapping the Output I/O ....................................... 5-6 5.4 Saving the Configuration................................................ 5-7 Chapter 6 Using I/O Messaging 6.1 About I/O Messaging ..................................................... 6-1 6.2 Understanding the I/O Image......................................... 6-2 6.3 Using Logic Command/Status ....................................... 6-3 6.4 Using Reference/Feedback ........................................... 6-3 6.
Appendix C DeviceNet Objects ................................................................C-1 Appendix D Logic Command/Status Words .............................................D-1 Glossary .................................................................................. Glossary-1 Index .......................................................................................
IV DeviceNet Communications Module
List of Figures Figure 2.1 – Components of the DeviceNet Module ................................... 2-1 Figure 3.1 – Setting the Node Address/ Data Switches and Single-/Multi-Drive Operation Jumper..................................... 3-2 Figure 3.2 – Connecting a 5-Pin Linear Plug to the Cable.......................... 3-5 Figure 3.3 – MDI Ports and Internal Interface Cables................................. 3-6 Figure 3.4 – Mounting the Module ..............................................................
Figure 7.8 – Sample PLC-5 Ladder Logic Program .................................. 7-12 Figure 7.9 – Sample SLC Ladder Logic Program ..................................... 7-14 Figure 8.1 – Example of a Single-Drive Mode Network .............................. 8-1 Figure 8.2 – Example of a Multi-Drive Mode Network................................. 8-2 Figure 8.3 – AK-U0-RJ45-TB2P Terminal Block Connector ....................... 8-3 Figure 8.4 – AK-U0-RJ45-TB2P Connector Wiring Diagram ......................
List of Tables Table 2.2 – Equipment Shipped with the DeviceNet Module...................... 2-2 Table 2.3 – Required User-Supplied Equipment ........................................ 2-2 Table 3.1 – Node Address Switch Settings (UP = OPEN = 1).................... 3-3 Table 3.2 – Data Rate Switch Settings (UP = OPEN = 1) .......................... 3-3 Table 3.3 – Jumper Settings for Single- or Multi-Drive Operation .............. 3-4 Table 4.1 – Configuration Tools............................................
Table 9.1 – DRIVE Status Indicator: State Definitions ................................9-2 Table 9.2 – MS Status Indicator: State Definitions......................................9-3 Table 9.3 – NET A Status Indicator: State Definitions ................................9-4 Table 9.4 – Diagnostic Items Accessed Using VS Utilities in Single-Drive Mode....................................................................9-5 Table 9.5 – Diagnostic Items Accessed Using VS Utilities in Multi-Drive Mode ..............
CHAPTER 1 Introduction This manual provides information about the DeviceNet module (MDCOMM-DNET) and using it with MD65 drives. The module is mounted in the MD65 drive and receives its required power from the drive and from the DeviceNet network. This manual is intended for qualified electrical personnel familiar with installing, programming, and maintaining AC drives and DeviceNet networks. 1.
1.2 • User-defined fault actions that determine how the module and MD65 drive respond to communication disruptions on the network and controllers in idle mode. • Faulted node recovery is supported. You can configure a device even when it is faulted on the network if you have a configuration tool that uses faulted node recovery and have properly set module node address switches and data rate switches. Related Documentation Refer to the following related publications as necessary for more information.
1.3 • 1747-6.5.2 DeviceNet Scanner Module Configuration Manual • 1747-5.14 DeviceNet Scanner Module Installation Instructions • 1771-6.5.118 DeviceNet Scanner Module Configuration Manual Conventions Used in This Manual The following conventions are used throughout this manual: 1.4 • Menu commands are shown in bold type face and follow the format Menu > Command. For example, if you read “Select File > Open,” you should click the File menu and then click the Open command.
1-4 DeviceNet Communications Module
CHAPTER 2 Getting Started This chapter provides: • A description of the DeviceNet 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 2.1 DeviceNet Module Components ➊ ➎ ➋ ➍ ➌ Status Indicators Three LEDs that indicate the status of the connected drive, module, and network. Refer to chapter 9, Troubleshooting. MDI Connector A 20-pin, single-row shrouded male header.
2.2 Required Equipment Table 2.2 lists the equipment shipped with the DeviceNet module. When you unpack the module, verify that the package includes all of these items. Table 2.2 – Equipment Shipped with the DeviceNet Module Item Description DeviceNet module 15.24 cm (6 in) Internal Interface cable Five-pin linear DeviceNet plug (connected to the DeviceNet connector on the module) Grounding wrist strap DeviceNet Module User Manual (D2-3520) Table 2.
2.3 Installation Checklist This section is designed to help experienced users start using the DeviceNet module. If you are unsure how to complete a step, refer to the referenced chapter. Step Action Refer to ❒ 1 Review the safety precautions for the module. Throughout this manual ❒ 2 Verify that the MD65 drive is properly installed. MD65 AC Drive User Manual ❒ 3 Commission the module. Set a unique node address and the appropriate data rate using the switches on the module.
Step Action Refer to ❒ 7 Apply power to the DeviceNet master and other devices on the network. Verify that the master and network are installed and functioning in accordance with DeviceNet standards, and then apply power to them. DeviceNet Cable System Planning and Installation Manual ❒ 8 Configure the scanner to communicate with the module. Use a network tool such as RSNetWorx for DeviceNet to configure the scanner on the network.
CHAPTER 3 Installing the DeviceNet Module Chapter 3 provides instructions for installing the DeviceNet module in an MD65 drive. 3.1 Preparing for an Installation Before installing the DeviceNet module: • Read the DeviceNet Product Overview Manual, Publication DN-2.5, and the DeviceNet Cable System Planning and Installation Manual, Publication DN-6.7.2. These manuals will provide information on selecting cables, setting up a network, and network basics. • Verify that you have all required equipment.
Important: If all switches are in the CLOSED position (all 0s), then the Node Address and Data Rate are determined by parameter settings in DN Addr Cfg (02) and DN Rate Cfg (04).
Table 3.
Table 3.3 – Jumper Settings for Single- or Multi-Drive Operation Jumper Setting Right position or jumper missing Description Sets the module for Single-Drive mode (default setting) using a single drive connection. Important: In this mode, connections to multiple drives must be removed since all powered and connected hosts will respond to any message sent by the module. Left position Sets the module for Multi-Drive operation mode using up to 5 different drives.
Red White Bare Blue Black 5 4 3 2 1 Terminal Color Signal Function 5 Red V+ Power Supply 4 White CAN_H Signal High 3 Bare SHIELD Shield 2 Blue CAN_L Signal Low 1 Black V– Common Figure 3.2 – Connecting a 5-Pin Linear Plug to the Cable Step 6. Insert the DeviceNet cable plug into the mating module receptacle and secure it with the two screws. (See figure 3.3, item 3.) Verify that the colors of the wires match up with the color codes on the receptacle. 3.
MDCOMM-DNET DeviceNet Module ➊ ➋ MD65 Drive B and C Frames (cover removed) ➌ Back of Cover 6MD-COMMCVRB 6MD-COMMCVRC MDI connector 15.24 cm (6 in) Internal Interface cable DeviceNet cable Figure 3.
DeviceNet Module Mounted on Back of Cover MD65 Drive B and C Frames (cover removed) Figure 3.4 – Mounting the Module 3.5 Applying Power ! ATTENTION: Unpredictable operation may occur if you fail to verify that parameter settings and switch settings are 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 or loss of life. Step 1.
Step 3. Apply power to the drive. The module receives its power from the connected drive and network. When you apply power to the product and network for the first time, the status indicators should be green after an initialization. If the status indicators are red, there is a problem. Refer to chapter 9, Troubleshooting the DeviceNet Module and Network. Step 4.
CHAPTER 4 Configuring the DeviceNet Module Chapter 4 provides instructions and information for setting the parameters in the DeviceNet module. For a list of parameters, refer to Appendix B, DeviceNet Module Parameters. For definitions of terms in this chapter, refer to the Glossary. 4.1 Configuration Tools The DeviceNet module stores parameters and other information in its own non-volatile memory. Therefore, you must access the module to view and edit its parameters. Table 4.
4.2 Using the LCD OIM to Configure the Module Use the procedure in figure 4.1 to access the parameters on the DeviceNet module using the LCD OIM (M/N MD4LCD-PNL, MD4ALCD, or MD1CC). If you are unfamiliar with the operation of the LCD OIM, refer to the OIM Quick Reference (D2-3508) for more information. Device Select MDI Devices DIAG PARAM DSEL MDI Devices MD65 MDCOMM-DNET MEM SEL Parameters Linear List Changed Params DIAG PARAM DSEL MEM SEL Figure 4.
Table 4.2 – Procedure for Setting Up RSLinx for RSNetworx for DeviceNet Step Action 1. Start RSLinx, and select Communications > Configure Drivers to display the Configure Drivers dialog box. See figure 4.2. 2. In the Available Driver Types box, select DeviceNet Drivers, and then click Add New. The DeviceNet Driver Selection dialog box appears. 3. In the Available DeviceNet Drivers list, select the module connected to your computer, and then click Select. A Driver Configuration dialog box appears.
4.3.2 Going Online with RSNetWorx for DeviceNet You can view the devices on a DeviceNet network by going online. A device may appear as an unrecognized device (node 63 in figure 4.3) if RSNetWorx for DeviceNet does not have an Electronic Data Sheet (EDS) file for it. See table 4.3 for the procedure to view devices. Table 4.3 – Viewing Devices on the DeviceNet Network using RSNetWorx Step Action Icon 1. After setting up a driver in RSLinx, start RSNetWorx for DeviceNet. 2. Select Network > Online.
4.3.3 Creating an Electronic Data Sheet (EDS) File If the module and drive appear as an unrecognized device, create an EDS file for it using the procedure in table 4.4. Table 4.4 – Procedure for Creating an EDS File Step Action 1. Right-click the “Unrecognized Device” icon, and select Register Device in the menu. The EDS Wizard (figure 4.4) appears. 2. Click Next to display the next step. 3. Select Upload EDS, and then click Next. 4. Type a description (if desired), and then click Next. 5.
4.3.4 Accessing and Editing Parameters Parameters in the drive and module can be edited with RSNetWorx using the procedure in table 4.5. The module parameters are appended to the list of drive parameters. Table 4.5 – Procedure to Access and Edit Parameters Using RSNetWorx Step Action 1. After creating an EDS file, right-click on the icon for the MD65 drive and module and select Properties. The MD65 Drive dialog box appears. 2. Click the Parameters tab (figure 4.5).
4.4 Setting the Node Address The value of DN Addr Cfg (2) determines the node address if all of the module DIP switches are in the CLOSED position (all 0s). We recommend that you do not use node address 63 because all new devices use it as the default address. Address 63 is also used for Automatic Device Recovery. Step 1. Set the value of DN Addr Cfg (3) to a unique node address. See figure 4.6. DN Addr Cfg Default = 63 Parameter: # 002 63 VALUE LIMITS SEL Figure 4.
4.6 Setting the I/O Configuration The I/O configuration determines the number of drives that will be represented on the network as one node by the module. If the Mode Jumper is set to the Single-Mode position, only one drive is represented by the module, and DSI I/O Cfg (15) has no effect. If the Mode Jumper is set to the Multi-Drive position, up to five drives can be represented as one node by the module. Step 1. Set the value in DSI I/O Cfg (15).
Cyclic and polled data exchanges are configured in the scanner, so you only need to set the I/O configuration in the module. COS data exchange must be configured in both the module and the scanner. You need to set the I/O configuration and COS parameters in the module. 4.7.1 Using COS (Change of State) Data Exchange Step 1. Set the bits in the Logic Status word that should be checked for changes in COS Status Mask (12).
4.8 Setting a Fault Action By default, when communications are disrupted (for example, a cable is disconnected) or the scanner is idle, the drive responds by faulting if it is using I/O from the network. You can configure a different response to communication disruptions using Comm Flt Action (7) and a different response to an idle scanner using Idle Flt Action (8).
Comm Flt Action Idle Flt Action Parameter: Fault VALUE 007 # Parameter: 0 LIMITS Fault SEL VALUE 008 # LIMITS 0 SEL Figure 4.11 – Fault Action Screens on an LCD OIM Changes to these parameters take effect immediately. A reset is not required. If Multi-Drive mode is used, the same fault action is used by the module for all of the drives it controls (Drive 0 - Drive 4). 4.8.
4.9 Resetting the Module Changes to switch settings on 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 Reset Module (6). 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.10 Viewing the Module Configuration The parameters in table 4.8 provide information about how the module is configured. You can view these parameters at any time. Table 4.8 – Module Configuration Parameters Number Name 01 Mode 03 Description The mode in which the module is set (0 = Single drive operation, or 1 = Multi-Drive operation). DN Addr The node address used by the module. This Actual will be one of the following values: • The address set by the module DIP switches 1 through 6.
4-14 DeviceNet Communications Module
CHAPTER 5 Configuring the Scanner A scanner is a separate module of a multi-module controller or a built-in component of a single-module controller that provides communication with a module connected to a network. Chapter 5 provides instructions on how to configure a scanner to communicate with the DeviceNet module and the 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.
5.2 Setting Up the Scan List For the scanner to communicate with a drive, the scanner must be configured and the drive’s node number must be added to its scan list. Step 1. Go online with RSNetWorx for DeviceNet. Refer to section 4.3.2. The devices on the network are displayed in the configuration view as shown in figure 5.2. MD65 Drive Figure 5.2 – Configuration View (Graph Tab) Step 2. Right-click the DeviceNet scanner (node 00 in figure 5.2 and select Properties.
. 01, MD65 Figure 5.3 – Scanlist Page in the Scanner Module Dialog Box Step 7. Under Scanlist, select the drive, and then click Edit I/O Parameters. The Edit I/O Parameters dialog box (figure 5.4) appears. Figure 5.
Step 8. Select the type(s) of data exchange (Polled, Change of State, and/or Cyclic). In our example, we selected Polled. Step 9. Type the number of bytes that are required for your I/O in the Input Size and Output Size boxes. The size will depend on the I/O that you enabled in the module. This information can be found in DSI I/O Actual (16) in the module. Table 5.1 shows common configuration Input/ Output sizes.
5.3 Mapping the Drive Data in the Scanner Data from I/O messages must be mapped in the scanner. This mapping determines where a ladder logic program can find data that is passed over the network. You must map both the Input I/O and the Output I/O. 5.3.1 Mapping the Input I/O Step 1. In the Scanner Module dialog box, click the Input tab. See figure 5.5. (If necessary, right-click the scanner in the configuration view (figure 5.2) to display this dialog box.
Table 5.3 – Scanner Module Memory Locations Scanner Memory Locations 1747-SDN Discrete or M-File 1756-DNB Assembly Data 1771-SDN Block Xfer 62 – 57 In our example, we are using a 1747-SDN and selected Discrete. Step 3. In the Start Word box, select the word in memory at which the data should start. In our example, we selected 1. Logic Status and Speed Feedback information will be found in I:1.1 and I:1.2, respectively. 5.3.2 Mapping the Output I/O Step 1.
Step 2. In the Memory box, select a location in scanner memory from table 5.4. Table 5.4 – Scanner Module Memory Locations Scanner Memory Locations 1747-SDN Discrete or M-File 1756-DNB Assembly Data 1771-SDN Block Xfer 62 – 57 In our example, we are using a 1747-SDN scanner and selected Discrete. Step 3. In the Start Word box, select the word in memory at which the data should start. In our example, we selected 1. Logic Command and Speed Reference data should be written to O:1.1 and O:1.
5-8 DeviceNet Communications Module
CHAPTER 6 Using I/O Messaging Chapter 6 provides information and examples that explain how to use I/O Messaging to control an MD65 drive. ! 6.1 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.
6.2 Understanding the I/O Image The DeviceNet specification requires that the terms input and output be defined from scanner’s point of view. Output I/O is data that is output from the scanner and consumed by the DeviceNet 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 configuration of the Mode Jumper (J2) on the module and DSI I/O Config (15). The image table always uses consecutive words starting at word 0.
6.3 Using Logic Command/Status When enabled, the Logic Command/Status word is always word 0 in the I/O image. The Logic Command is a 16-bit word of control produced by the scanner and consumed by the module. The Logic Status is a 16-bit word of status produced by the module and consumed by the scanner. This manual contains the bit definitions for compatible products available at the time of publication in Appendix D, Logic Command/Status Words. For other products, refer to the corresponding documentation.
Logic Command/Status Words These examples use 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 drive. 6.5.1 Sample ControlLogix Ladder Logic Program Table 6.
Sample ControlLogix program with an MD65 drive at node address 1. This rung enables the scanner (changes the scanner to RUN mode). Local:3:O.CommandRegister.Run 0 1 This section retrieves the Logic Status and Feedback data from the scanner and moves it to specifc tags for use elsewhere in the ladder program. COP Copy File Source Local:3:I.Data[0] Dest DriveInputImage[0] Length 2 DriveInputImage[0].0 DriveStatusReady DriveInputImage[0].1 DriveStatusActive DriveInputImage[0].
DriveCommandForward DriveOutputImage[0].4 DriveCommandForward / DriveOutputImage[0].5 12 13 14 15 COP Copy File Source DriveReference Dest DriveOutputImage[1] Length 1 COP Copy File Source DriveOutputImage[0] Dest Local:3:O.Data[0] Length 1 Figure 6.3 – Sample ControlLogix Ladder Logic Program (continued) For the explicit message portion of this sample ladder program, see figure 7.7.
6.5.2 Sample PLC-5 Ladder Logic Program Table 6.2 – Control File for Block Transfers BT20:0 BT20:1 EN 0 0 ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM R G S 0 0 0 0 0 0 0 0 62 0 9 0 00 0 0 0 0 0 0 0 0 0 0 62 0 10 0 00 0 0 Sample PLC-5 program with an MD65 drive at DeviceNet node address 1. The DeviceNet scanner gathers the drive status data via the network.
The BTR in this rung moves the drive control data to the scanner from the N10: data file in the PLC, where: N10:0 = Scanner Control word N10:1 = MD65 (node 1) Logic Command N10:2 = MD65 (node 1) Reference Note that the Reference for the MD65 drive is set in Hz and not in engineering units. For example, "300" equates to 30.0 Hz (the decimal point is always implied). The scanner then sends the data to the drive over the network.
6.5.3 Sample SLC Ladder Logic Program SLC 5/03 example program with an MD65 at DeviceNet node address 1. This rung enables the scanner (changes the scanner to RUN mode). 1747-SDN Scanner Enable bit O:1 0000 0 1747-SDN This section of rungs control the Logic Command bits for the MD65 drive. The B3:0 bits would be controlled elsewhere in the user program.
Node 1 Forward Command B3:0 Node 1 Logic Command REVERSE O:1 4 21 1747-SDN 0006 0007 This rung controls the Reference for the MD65 drive. N7:0 would be controlled elsewhere in the user program. Note that the Reference for the MD65 drive is set in Hz and not in engineering units. For example, "300" equates to 30.0 Hz (the decimal point is always implied). Node 1 REFERENCE (Hz) MOV Move Source N7:0 300 < Dest O:1.2 300 < This section of rungs displays the Logic Status bits for the MD65 drive.
Node 1 Logic Status FAULTED I:1 Node 1 FAULTED B3:1 0011 23 1747-SDN Node 1 Logic Status AT REFERENCE I:1 7 Node 1 AT REFERENCE B3:1 0012 24 1747-SDN 0013 8 This rung displays the Feedback word for the MD65 drive. N7:1 would be used elsewhere in the user program. Note that the Feedback for the MD65 drive is set in Hz and not in engineering units. For example, "300" equates to 30.0 Hz (the decimal point is always implied). Node 1 FEEDBACK (Hz) MOV Move Source I:1.2 300 < Dest N7:1 300 < Figure 6.
6-12 DeviceNet Communications Module
CHAPTER 7 Using Explicit Messaging Chapter 7 provides information and examples that explain how to use Explicit Messaging to monitor and configure the module and the connected MD65 drive. ! 7.1 ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application.
7.2 Formatting Explicit Messages for a ControlLogix Controller ControlLogix scanners accommodate both downloading Explicit Message Requests and uploading Explicit Message Responses. The scanner module can accommodate one request or response for each transaction block. Each transaction block must be formatted as shown in figure 7.1. Refer to table 7.1 for a description of the data that is required in each box (items 1–9). Figure 7.
Table 7.1 – ControlLogix Message Requests and Responses Box Description Message Type The message type must be CIP Generic. Service Type/Service Code The service type/code is the requested DeviceNet service. Available services depend on the class and instance that you are using. Refer to Appendix C, DeviceNet Objects. Class The object type is a DeviceNet class. Refer to Appendix C, DeviceNet Objects, for available classes. Instance The object ID is an instance of a DeviceNet class.
7.3 Formatting Explicit Messages for a PLC or SLC Controller Transaction blocks in PLC and SLC scanners accommodate both downloading Explicit Message Requests and uploading Explicit Message Responses. The scanner module can accommodate one request or response for each transaction block. Each transaction block must be formatted as shown in figure 7.2 or figure 7.3.
Table 7.2 identifies the number of transaction blocks within a scanner that are reserved for Explicit Messaging. Table 7.2 – Number of Transaction Blocks Reserved for Explicit Messaging No. of Transaction Blocks Scanner 1747-SDN 10 1771-SDN 10 Words in Each Transaction Block 32 32 (two blocks can be moved at once) Refer To Figure 7.3 Figure 7.2 Table 7.
Table 7.
7.4 Running Explicit Messages There are five basic events in the Explicit Messaging process as shown in figure 7.4. The details of each step will vary depending on the controller (ControlLogix, PLC, or SLC). Refer to the documentation for your controller. Important: There must be a request message and a response message for all Explicit Messages, whether you are reading or writing data.
7.5 ControlLogix Example Data Format for a Read and Write Parameter The data in this example is for an MD65 drive at node address 1. Refer to section 7.2 for a description of the content in each box. Configuration Service Code Object Type Object ID Object Attribute Value e (hex) f (hex) 39 (dec) 1 (hex) Description Get_Attribute_Single Parameter Object Parameter Address Parameter Value Refer to . . . Page C-10 Page C-8 Page C-9 Figure 7.
Configuration Service Code Object Type Object ID Object Attribute Value 10 (hex) f (hex) 39 (dec) 1 (hex) Description Get_Attribute_Single Parameter Object Parameter Address Parameter Value Refer to . . . Page C-10 Page C-8 Page C-9 Figure 7.6 – Data Format for a Read and Write Parameter (2 of 2) Table 7.
Ex plic it M e ssaging Ex am ple PerformParameterRead 16 MS G Type - CIP Generic Message Control PerformParameterWrite 17 ParameterRDMessage ... EN DN ER ... EN DN ER MS G Type - CIP Generic Message Control ParameterWRMessage (End) Figure 7.7 – Sample ControlLogix Ladder Logic Program For the I/O message portion of this sample ladder program, see figure 6.3.
7.6 PLC-5 Example Data Format for a Read and Write Parameter The data in this example is for an MD65 drive at node address 1. Refer to section 7.2 for a description of the content of the data file. Table 7.6 – Request Data for Read of Drive Parameter 39 Address Value (hex) N11:0 Description Refer to ... 0101 TXID = 01, Command = 01 (execute) Section 7.3 N11:1 0006 Port = 00, Size = 06 bytes Section 7.
Ladder Logic Program Explicit Messaging Example 0003 When B3:0/0 is set to ON, a one-time BTW sends the explicit message data (starts at N11:0) to the scanner. The MOV instruction then initializes the first word of the data file that is used by the BTR instruction in the next rung.
7.7 SLC Example Data Format for a Read and Write Parameter The data in this example is for an MD65 drive at node address 1. Refer to section 7.2 for a description of the content of the data file. Table 7.10 – Request Data for Read of Drive Parameter 101 Address Value (hex) N9:10 Description Refer to ... 0101 TXID = 01, Command = 01 (execute) Section 7.3 N9:11 0006 Port = 00, Size = 06 bytes Section 7.
Ladder Logic Program Important: To originate a scanner transaction, use a copy operation to M0:[slot number]:224. Then, use a copy operation to read M1:1.224 for the result. If more than one message is enabled, use the TXID to determine which message you are reading. Explicit Messaging Example 0014 When B3:2/0 is set ON, this rung will copy the 32 words of Explicit Message from the buffer at N9:10 to the M0 File Explicit Message buffer. The scanner will send the message out over DeviceNet.
CHAPTER 8 Using Multi-Drive Mode Chapter 8 provides information and a ControlLogix ladder example to explain how to use Multi-Drive mode. ! 8.1 ATTENTION: Hazard of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
up to 5 drives per node DeviceNet Up to 4 MD65 or MD60 Drives MD65 Drive MDCOMM-DNET AK-U0-RJ45-TB2P Connector w/3rd Party Terminating Resistor RS-485 AK-U0-RJ45-TB2P AK-U0-RJ45-TB2P Connector w/3rd Party Terminating Resistor Figure 8.2 – Example of a Multi-Drive Mode Network Benefits of Multi-Drive mode include: • Lower hardware costs. Only one MDCOMM-DNET module is needed for up to five drives. MD60 drives can also be used for the daisy-chained drives instead of MD65 drives.
: Table 8.1 – Additional Throughput Time for Logic Command/Reference Drive MD65 w/MDCOMM-DNET MD65 w/MDCOMM-DNET plus 1 drive MD65 w/MDCOMM-DNET plus 2 drives MD65 w/MDCOMM-DNET plus 3 drives MD65 w/MDCOMM-DNET plus 4 drives Additional Throughput Time versus Single-Drive Mode 0 ms +24 ms +48 ms +72 ms +96 ms • Automatic Device Replacement (ADR) cannot be used with any of the drives. • The RSNetWorx Parameter editor cannot be used.
MD65 Drive with MDCOMM-DNET Drive #2 Drive #3 Drive #4 Drive #5 120 Ω ¼ Watt Resistor 120 Ω ¼ Watt Resistor Figure 8.4 – AK-U0-RJ45-TB2P Connector Wiring Diagram 8.3 Understanding the I/O Image The DeviceNet specification requires that the terms input and output be defined from the scanner’s point of view. Therefore, Output I/O is data that is output from the scanner and consumed by the DeviceNet module. Input I/O is status data that is produced by the module and consumed as input by the scanner.
MDI DeviceNet Controller Scanner Output Image (Write) Input Image (Read) Module Word and I/O 0 Logic Command 1 Reference MD65 Drive 0 2 Logic Command 3 Reference MD65 Drive 1 4 Logic Command 5 Reference MD65 Drive 2 6 Logic Command 7 Reference MD65 Drive 3 8 Logic Command 9 Reference MD65 Drive 4 0 Logic Status 1 Feedback MD65 Drive 0 2 Logic Status 3 Feedback MD65 Drive 1 4 Logic Status 5 Feedback 6 Logic Status 7 Feedback 8 Logic Status 9 Feedback Message Handler MD65 Drive 2 MD65 Dri
Important: Comm Loss Action (A105) and Comm Loss Time (A106) in the daisy-chained drives are not used in Multi-Drive mode. If the RS-485 cable is disconnected or broken, the disconnected drive(s) will fault. On the DeviceNet side, Comm Flt Action (7) and Idle Flt Action (8) in the MDCOMM-DNET module determine the action taken for ALL of the drives on the Multi-Drive node.
Module Settings for the Example Program • The Mode Jumper on the module is set to the Multi-Drive operation position. See section 3.2, Commissioning the Module. • All DIP switches on the module are set to CLOSED (all 0s). See section 3.2, Commissioning the Module. The actual node address will be set via a software parameter.
8.6 ControlLogix Example The following common Tags are used: Tag Name Local : 3 : I Local : 3 : O Local : 3 : 5 Drive Input Image Drive Output Image Type AB: 1756_D... AB: 1756_D... AB: 1756_D...
ControlLogix MultiDrive example program with an MD65 drive at node address 1. Four MD65/MD60 drives are daisy-chained to the main MD65 drive via their RJ45 ports (RS-485). In this mode, up to FIVE MD65/MD60 drives can exist on ONE DeviceNet node. This rung enables the scanner (changes the scanner to RUN mode). Local:3:O.CommandRegister.
This section writes the output image to the scanner.
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 0 1 2 3 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 MS G 13 Type - CIP Generic Message Control ParameterRDMessage0 ... EN DN ER ... EN DN ER PerformParameterWrite0 MS G 14 Type - CIP Generic Message Control ParameterWRMessage0 RET 15 Return (End) Figure 8.
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 0 1 2 3 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 MS G 13 Type - CIP Generic Message Control ParameterRDMessage1 ... EN DN ER ... EN DN ER PerformParameterWrite1 MS G 14 Type - CIP Generic Message Control ParameterWRMessage1 RET 15 Return (End) Figure 8.
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 0 1 2 3 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 MS G 13 Type - CIP Generic Message Control ParameterRDMessage2 ... EN DN ER ... EN DN ER PerformParameterWrite2 MS G 14 Type - CIP Generic Message Control ParameterWRMessage2 RET 15 Return (End) Figure 8.
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 0 1 2 3 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 MS G 13 Type - CIP Generic Message Control ParameterRDMessage3 ... EN DN ER ... EN DN ER PerformParameterWrite3 MS G 14 Type - CIP Generic Message Control ParameterWRMessage3 RET 15 Return (End) Figure 8.
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 0 1 2 3 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 MS G 13 Type - CIP Generic Message Control ParameterRDMessage4 ... EN DN ER ... EN DN ER PerformParameterRead4 MS G 14 Type - CIP Generic Message Control ParameterWRMessage4 RET 15 Return (End) Figure 8.17 – Drive 4 Control Routine (Continued) 8.
Drive 0 Explicit Message Example The Explicit message examples in the ControlLogix example program perform a read (Get_Attribute_Single) and a write (Set_Attribute_Single) to parameter 39 (Accel Time 1). The configuration for the read is shown in figure 8.18 and the write is shown in figure 8.19. Figure 8.18 – Parameter Read Message Configuration Figure 8.
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 “17447” to access parameter 39 (Accel Time 1). The Explicit messages for Drive 1 to Drive 4 are identical except for the Instance values: • 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.
CHAPTER 9 Troubleshooting the DeviceNet Module and Network Chapter 9 contains information for troubleshooting the DeviceNet module and network. 9.1 Understanding the Status Indicators The DeviceNet module has three status indicators. They can be viewed on the module or through the drive cover. See figure 9.1. ➊ ➋ ➌ ➊ ➋ ➌ ➍ DRIVE MS Number Status Indicator DRIVE MS NET A NET B Description MDI Connection Status Module Status DeviceNet Status Not Used for DeviceNet Refer to... 9.1.1 9.1.2 9.1.
9.1.1 DRIVE Status Indicator Table 9.1 – DRIVE Status Indicator: State Definitions Status Cause Off The module is not powered or is not connected properly to the drive. Flashing The module is not Red receiving communication from the drive, connected drive is faulted, or a drive is missing in Multi-Drive mode. Solid The drive has refused an Red I/O connection from the module. Flashing Green Solid Green Orange 9-2 Another MDI peripheral is using the same MDI port as the module.
9.1.2 MS Status Indicator Table 9.2 – MS Status Indicator: State Definitions Status Cause Off The module is not powered. Flashing Red The module has failed the firmware test, connected drive is faulted, or a drive is missing in Multi-Drive mode. Solid Red The module has failed the hardware test. Flashing Green The module is 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 Cause Corrective Actions Off The module and/or • Securely connect the module to the drive network is not powered using the Internal Interface cable and to or module is not the network using a DeviceNet cable. connected properly to • Correctly connect the DeviceNet cable to the network. the DeviceNet plug. • Apply power to the drive and network.
9.2 Module Diagnostic Items in Single- Drive Mode The diagnostic items shown in table 9.4 can be accessed using VS Utilities (version 3.01 or higher). Table 9.4 – Diagnostic Items Accessed Using VS Utilities in Single-Drive Mode No. 1 2 3 4 5 6 7 Name Field Flash Cnt Module Events Reference Logic Cmd Logic Sts Feedback DN Rx Errors 8 DN Tx Errors 9 10 Data Rate SW Node Address SW 9.3 Description The number of flash updates made to the module after shipping. The number of events in the event queue.
Table 9.5 – Diagnostic Items Accessed Using VS Utilities in Multi-Drive Mode (Continued) No. 14 15 16 17 18 19 20 21 22 23 Name Drv 2 Feedback Drv 3 Reference Drv 3 Logic Cmd Drv 3 Logic Sts Drv 3 Feedback Drv 4 Reference Drv 4 Logic Cmd Drv 4 Logic Sts Drv 4 Feedback DN Rx Errors 24 DN Tx Errors 25 26 Data Rate SW Node Address SW 9.4 Description Feedback from MDI drive 2 being received by the module. Reference being transmitted from the module to MDI drive 3.
Events Many events in the event queue occur under normal operation. If you encounter unexpected communications problems, the events may help you or Rockwell Automation personnel troubleshoot the problem. Table 9.6 lists events that may appear in the event queue: Table 9.6 – Event Codes and Descriptions Code Event Description 0 No Event Text displayed in an empty event queue entry. 1 Host Sent Reset The MDI product issued this because it was reset.
Table 9.6 – Event Codes and Descriptions (Continued) Code Event 24 Slave Timeout 25 26 27 9-8 Description An explicit message to a Slave has timed out waiting for a response. Slave Detected An MDI slave was detected on the /slave I/O line. Slave Removed An MDI slave was removed from the /slave I/O line. Language CRC Bad The language flash segment is corrupt.
APPENDIX A Technical Specifications Communications Network Protocol Data Rates Drive Protocol DeviceNet 125K, 250K, 500K, Autobaud MDI Electrical Consumption Drive Network 150 mA at +5 V supplied through the drive 60 mA at +24 V supplied through DeviceNet Use the 60 mA value to size the network current draw from the power supply. Mechanical Dimensions Height Length Width 19 mm (0.75 in) 86 mm (3.33 in) 78.5 mm (3.
A-2 DeviceNet Communications Module
APPENDIX B DeviceNet Module Parameters The following information is provided for each DeviceNet 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.
1 Mode Range: 0 = Single Drive 1 = Multiple Drive Default: 0 = Single Drive Type: Read Only Reset Required: N/A Displays the Single- or Multi-Drive operating mode selected with jumper on the module. 2 DN Addr Cfg Range: 0 to 63 Default: 63 Type: Read/Write Reset Required: Yes Sets the node address used by the drive after a reset or power cycle. This setting is used when all of the module DIP switches are in the CLOSED position (all 0s).
5 DN Rate Act Range: 0 = 125 kpbs 1 = 250 kbps 2 = 500 kbps 3 = Autobaud Default: 0 = 125 kbps Type: Read Only Reset Required: N/A Displays the DeviceNet data rate currently being used by the module. 6 Reset Module Range: 0 = Ready (No action) 1 = Reset Module 2 = Set Defaults (Restores module to factory-default settings) Default: 0 = Read Type: Read/Write Reset Required: No This parameter is a command. It will be reset to 0 = Ready after the command has been performed.
7 Comm 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 Action that the module and drive take if the module detects that DeviceNet communications have been disrupted. This setting is effective only if I/O that controls the drive is transmitted though the module. ! B-4 ATTENTION: Comm Flt Action (7) lets you determine the action of the module and connected drive if communications are disrupted.
8 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 take if the module detects that the scanner is idle because the controller was switched to program mode. This setting is effective only if the I/O that controls the drive is transmitted through the module.
10 Flt Cfg Logic Range: 0 to 65535 Default: 0 Type: Read/Write Reset Required: No Sets the Logic Command data that is sent to the drive if any of the following is true: • Comm Flt Action (7) is set to Send Flt Cfg and communications are disrupted. • Idle Flt Action (8) is set to Send Flt Cfg and the scanner is put into Program or Test mode. The bit definitions will depend on the product to which the module is connected.
12 COS Status Mask Range: 0 to 65535 Default: 0 Type: Read/Write Reset Required: No Sets the mask of the 16-bit Logic Status word. Unless they are masked out, the bits in the Logic Status word are checked for changes when the module is allocated using COS (change of state). If a bit changes, it is reported as a change in the change of state operation. If the mask bit is 0 (Off), the bit is ignored. If the mask bit is 1 (On), the bit is checked.
15 DSI I/O Cfg Range: 0 = Drive 0 1 = Drives 0-1 2 = Drives 0-2 3 = Drives 0-3 4 = Drives 0-4 Default: 0001 Type: Read/Write Reset Required: Yes Sets the configuration of the drives that are active in the Multi-Drive mode. Identifies the connections that would be attempted on a reset or power cycle.
APPENDIX C DeviceNet Objects Appendix C presents information about the DeviceNet objects that can be accessed using Explicit Messages. For information on the format of Explicit Messages and sample ladder logic programs, refer to Chapter 7, Using Explicit Messaging. Class Code Hex. Dec. Refer to Section Identity Object 0x01 1 C.1 Connection Object 0x05 5 C.2 Register Object 0x07 7 C.3 Parameter Object 0x0F 15 C.4 Parameter Group Object 0x10 16 C.5 PCCC Object 0x67 103 C.
C.
Attribute Access ID Rule Name Data Type Description STRUCT of USINT USINT Product Revision: Major Minor Status WORD Bit 0 = Owned Bit 2 = Configured Bit 10 = Recoverable fault Bit 11 = Unrecoverable fault Get Serial Number UDINT Unique 32-bit number Get Product Name SHORT_ STRING 4 Get Revision: 5 Get 6 7 Product name and rating Services Implemented for: Service Code Class Instance 0x01 Yes Yes Get_Attributes_All 0x05 Yes No Reset 0x0E Yes Yes Get_Attribute_Single 0x10
C.2 Connection Object Class Code Hexadecimal Decimal 0x05 5 Instances Instance 1 Description Master-Slave Explicit Message Connection 2 Polled I/O Connection 4 Change of State/Cyclic Connection 6 – 10 Explicit Message Connection Instance Attributes Refer to the DeviceNet specification for more information.
Attribute ID Access Rule 12 Get/Set 13 Name Data Type Description Watchdog Action USINT 0 = Transition to timed out 1 = Auto delete 2 = Auto reset Get Produced Path Length UINT Number of bytes of data in the produced connection path 14 Get Produced Connection Path ARRAY of UINT Byte stream which defines Application objects whose data is to be produced by this Connection object 15 Get Consumed Path Length UINT Number of bytes of data in the consumed connection path 16 Get Consumed
C.
Class Attributes Not supported. 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 = Producer Register 1 = Consumer Register 3 Get Size UINT Size of register data in bits ARRAY of BITS Data to be transferred 4 Conditional Data 1 1 Data Type Name Description 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 shown below.
Attribute Access ID Rule 10 Get Data Type Name Native Language USINT Description 0 = English 1 = French 2 = Spanish 3 = Italian 4 = German 5 = Japanese 6 = Portuguese 7 = Mandarin Chinese 8 = Russian 9 = Dutch Instance Attributes Attribute Access ID Rule Data Type Name 1 2 Get Link Path Size USINT 0 = No link specified n = Link specified 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 = Rea
Attribute Access ID Rule Data Type Name Description 13 Get Scaling Multiplier UINT 3 14 Get Scaling Divisor UINT 3 15 Get Scaling Base UINT 3 16 Get Scaling Offset UINT 3 17 Get Multiplier Link UINT 3 18 Get Divisor Link UINT 3 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.
C.5 Parameter Group Object Class Code Hexadecimal Decimal 0x10 16 Instances (Single-Drive Mode) The number of instances depends on the number of groups in the drive. A group of module parameters is appended to the list of groups in the drive.
Class Attributes Attribute Access ID Rule C-12 Name Data Type Description 1 Get Parameter group version UINT 1 2 Get Max Instance UINT Total number of groups 8 Get Native Language USINT 0 = English 1 = French 2 = Spanish (Mexican) 3 = Italian 4 = German 5 = Japanese 6 = Portuguese 7 = Mandarin Chinese 8 = Russian 9 = Dutch DeviceNet Communications Module
Instance Attributes Attribute Access ID Rule Data Type Description 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 n Parameter UINT Number in Group … … 1 Name 1 Value varies based on group instance.
C.6 PCCC Object Class Code Hexadecimal Decimal 0x67 103 Instances Not supported. Class Attributes Not supported. Instance Attributes Not supported.
Message Structure for Execute_PCCC Request Name Data Type Description Response Name Data Type Description Length USINT Length of requestor ID Length USINT Length of requestor ID Vendor UINT Vendor number of requestor Vendor UINT Vendor number of requestor Serial Number UDINT ASA serial number of requestor Serial Number UDINT ASA serial number of requestor Other Product Specific Identifier of user, Other task, etc., on the requestor Product Specific Identifier of user, task, etc.
C-16 DeviceNet Communications Module
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 DeviceNet 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 Description x x x Reference Select 000 = No Command 001 = Freq Source = Select 010 = Freq Source = Int. Freq 011 = Freq Source = Comm 100 = Preset Freq 1 101 = Preset Freq 2 110 = Preset Freq 3 111 = Preset Freq 4 x MOP Decrement 0 = Not Decrement 1 = Decrement * A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition will start the drive.
Logic Status Word Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status x Ready x x x x x x x x x x x x x x x Logic Command/Status Words Description 0 = Not Ready 1 = Ready Active 0 = Not Active 1 = Active Command 0 = Reverse Direction 1 = Forward Actual Direction 0 = Reverse 1 = Forward Accel 0 = Not Accelerating 1 = Accelerating Decel 0 = Not Decelerating 1 = Decelerating Alarm 0 = No Alarm 1 = Alarm Fault 0 = No Fault 1 = Fault At Speed 0 = Not At Reference 1 = At Reference Main Freq 0 = Not Controll
D-4 DeviceNet Communications Module
GLOSSARY Automatic Device Replacement (ADR) - A means for replacing a malfunctioning device with a new unit and having the device configuration data set automatically. The DeviceNet scanner is set up for ADR using RSNetWorx. The scanner uploads and stores a device’s configuration. Upon replacing a malfunctioning device with a new unit (node 63), the scanner automatically downloads the configuration data and sets the node address.
Cable Thick Trunk Line Thin Trunk Line Maximum Drop Length Cumulative Drop Length 125 K 500 m (1,640 ft) 100 m (328 ft) 6 m (20 ft) 156 m (512 ft) Maximum Cable Length 250 K 500 K 250 m (820 ft) 100 m (328 ft) 100 m (328 ft) 100 m (328 ft) 6 m (20 ft) 6 m (20 ft) 78 m (256 ft) 39 m (128 ft) DeviceNet network - A DeviceNet network uses a producer/ consumer Controller Area Network (CAN) to connect devices (for example, controllers, drives, and motor starters).
faulted node recovery - DeviceNet feature lets you change a configuration of a device that is faulted on the network. For example, if you add a device to a network and it does not have a unique address, it will fault. If you have a configuration tool that supports faulted node recovery and your adapter is using parameters to set its node address and data rate, you can change the node address. Flash update - The process of updating firmware in the module.
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 an MD65 drive is an MDI product. In this manual, an MDI product is also referred to as “product” or “host.” module - Devices such as drives, controllers, and computers usually require a module to provide a communication interface between them and a network such as DeviceNet. A module reads data on the network and transmits it to the connected device.
producer/consumer network - On producer/consumer networks, packets are identified by content rather than an explicit destination. If a node needs the packet, it will accept the identifier and consume the packet. The source therefore sends a packet once and all the nodes consume the same packet if they need it. Data is produced once, regardless of the number of consumers.
Glossary-6 DeviceNet Communications Module
INDEX A assistance, technical, 1-3 C change of state (COS) data exchange configuring a module for, 4-8 configuring a scanner for, 5-3 checklist, installation, 2-3 Comm Flt Action (7), B-4 commissioning the module, 3-1 communications specifications, A-1 configuration tools, 4-1 configuring the module, 4-1 to 4-13 connecting the module to the drive, 3-5 connecting the module to the network, 3-4 connection object, C-4 connector DeviceNet, 2-1 MDI, 2-1 controller ControlLogix, 6-4, 7-8 PLC, 6-7, 7-11 running E
H hold last, configuring a module for, 4-10 I I/O configuring a module for, 4-8 configuring scanner for, 5-3 image, 6-2 input, 5-5 mapping in the scanner, 5-5 messaging, 6-1 output, 5-6 identity object, C-2 Idle Flt Action (8), B-5 indicators, status, 9-1 installation checklist, 2-3 commissioning the module, 3-1 preparing for, 3-1 connecting to network, 3-4 connecting to the drive, 3-5 diagnostic items, 9-5 features, 1-1 installation, 3-1 to 3-8 mapping I/O in the scanner, 5-5 parameters, B-1 to B-8 reset
power consumption, A-1 preparing for an installation, 3-1 protocol, A-1 publications, related, 1-2 R Reference/Feedback in I/O image, 6-2 reference/feedback using, 6-3 register object, C-6 regulatory compliance, A-1 Reliance Electric, getting assistance from, 1-3 Reset Module (6), B-3 resetting a module, 4-12 RSLinx, 4-2 RSNetWorx for DeviceNet creating EDS files with, 4-5 editing parameters with, 4-6 going online, 4-4 saving a network configuration, 5-7 setting up RSLinx for, 4-2 using to map I/O, 5-5 usi
Index-4 DeviceNet 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-3520-June 2003 Copyright © 2003 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
