DeviceNet Adapter 22-COMM-D FRN 1.
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. “Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls” (Publication SGI-1.1 available from your local Rockwell Automation Sales Office or online at http://www.ab.com/ manuals/gi) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Summary of Changes This is the first release of the DeviceNet adapter FRN 1.xxx.
S-ii Summary of Changes
Table of Contents Preface About This Manual Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1 Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . P-2 Rockwell Automation Support. . . . . . . . . . . . . . . . . . . . . . . . P-2 Chapter 1 Getting Started Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Table of Contents Chapter 5 Using I/O Messaging About I/O Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding the I/O Image. . . . . . . . . . . . . . . . . . . . . . . . . Using Logic Command/Status . . . . . . . . . . . . . . . . . . . . . . . . Using Reference/Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . Example Ladder Logic Programs . . . . . . . . . . . . . . . . . . . . . ControlLogix Example. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Appendix B iii Adapter Parameters About Parameter Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Appendix C DeviceNet Objects Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 Connection Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4 Register Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Table of Contents
Preface About This Manual Topic Related Documentation Conventions Used in this Manual Rockwell Automation Support Page P-1 P-2 P-2 Related Documentation For: DeviceNet™ Cables and Components DeviceNet Network Installation DeviceNet Networks DriveExplorer™ DriveTools 2000™ HIM Logix 5550 PowerFlex™ 4 Drive PowerFlex™ 40 Drive RSLinx™ RSLogix™ 5 RSLogix 500 RSLogix 5000 RSNetWorx™ for DeviceNet SLC 500™ and 1747-SDN PLC-5™ and 1771-SDN Refer to: DeviceNet Product Overview Publication DN-2.
P-2 About This Manual Conventions Used in this Manual The following conventions are used throughout this manual: • Parameter names are shown in the following format Parameter xx - [*]. The xx represents the parameter number. The * represents the parameter name. For example Parameter 01 - [Mode]. • 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.
Chapter 1 Getting Started The 22-COMM-D DeviceNet adapter is a communication option intended for installation into a PowerFlex 40 drive. It can also be used with other Allen-Bradley products that support an internal DSI adapter. The Multi-Drive feature (Chapter 7) also provides a means for PowerFlex 4 drives and other DSI Hosts to connect to DeviceNet.
1-2 Getting Started Features The DeviceNet adapter features the following: • The adapter is mounted in the PowerFlex 40 drive. It receives the required power from the drive and from the DeviceNet network. • Switches let you set a node address and network data rate before applying power to the PowerFlex drive. Alternately, you can disable the switches and use parameters to configure these functions. • A jumper lets you select between Single or Multi-Drive mode of operation.
Getting Started Compatible Products The DeviceNet adapter is compatible with Allen-Bradley PowerFlex drives and other products that support an internal DSI adapter. At the time of publication, compatible products include: • PowerFlex 40 drives The Multi-Drive feature (Chapter 7) also provides a means for PowerFlex 4 drives and other DSI Hosts to connect to DeviceNet.
1-4 Getting Started Safety Precautions Please read the following safety precautions carefully: ! ! ! ! ! ! ATTENTION: Risk of injury or death exists. The PowerFlex drive may contain high voltages that can cause injury or death. Remove all power from the PowerFlex drive, and then verify power has been removed before installing or removing an adapter. ATTENTION: Risk of injury or equipment damage exists.
Getting Started 1-5 Quick Start This section is designed to help experienced users start using the DeviceNet adapter. If you are unsure how to complete a step, refer to the referenced chapter. Step 1 Review the safety precautions for the adapter. 2 Verify that the PowerFlex drive is properly installed. 3 Commission the adapter. Set a unique node address and the appropriate data rate using the switches on the adapter. If desired, you can disable the switches and use parameter settings instead.
1-6 Getting Started Modes of Operation The adapter uses three status indicators to report its operating status. They can be viewed through the drive cover. See Figure 1.2. Figure 1.2 Status Indicators (location on drive may vary) ➊ ➋ ➌ ➊ ➋ ➌ ➍ Item Status Indicator ➊ PORT Status(1) Description Green Normal Operation. The adapter is properly connected and is communicating with the drive. The adapter is in the process of establishing a connection to the drive.
Chapter 2 Installing the Adapter Chapter 2 provides instructions for installing the adapter in a PowerFlex 40 drive. Topic Preparing for an Installation Commissioning the Adapter Connecting the Adapter to the Network Connecting the Adapter to the Drive Applying Power Page 2-1 2-1 2-4 2-5 2-7 Preparing for an Installation Before installing the DeviceNet adapter: • • Read the DeviceNet Product Overview Manual, Publication DN-2.
2-2 Installing the Adapter 1. Set the adapter node address and data rate switches (see Figure 2.1, Figure 2.2, and Figure 2.3). Figure 2.
Installing the Adapter 2-3 Figure 2.
2-4 Installing the Adapter Connecting the Adapter to the Network ! ATTENTION: Risk of injury or death exists. The PowerFlex drive may contain high voltages that can cause injury or death. Remove all power from the PowerFlex drive, and then verify power has been removed before installing or removing an adapter. 1. Remove power from the drive. 2. Use static control precautions. 3. Remove the drive cover. 4. Connect a DeviceNet cable to the network, and route it through the bottom of the PowerFlex drive.
Installing the Adapter 2-5 Connecting the Adapter to the Drive 1. Remove power from the drive. 2. Use static control precautions. 3. Mount the adapter on the cover, using the screw on the adapter to secure it in place. Important: Tighten the screw in the lower left hole to ground the adapter (see Figure 2.6). 4. Connect the Internal Interface cable to the DSI port on the drive and then to the mating DSI connector on the adapter. Figure 2.
2-6 Installing the Adapter Figure 2.
Installing the Adapter 2-7 Applying Power ! ATTENTION: Risk of equipment damage, injury, or death exists. 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. 1. Reinstall the cover on the drive. The status indicators can be viewed on the front of the drive after power has been applied. 2.
2-8 Notes: Installing the Adapter
Chapter 3 Configuring the Adapter Chapter 3 provides instructions and information for setting the parameters in the adapter.
3-2 Configuring the Adapter Using the PowerFlex 4-Class HIM The PowerFlex 4-Class HIM (Human Interface Module) can be used to access parameters in the adapter (see basic steps shown below). It is recommended that you read through the steps for your HIM before performing the sequence. For additional HIM information, refer to your HIM Quick Reference card. Using the HIM Step 1. Power up the drive. Then plug the HIM into the drive. The Parameters menu for the drive will be displayed.
Configuring the Adapter 3-3 Using RSNetWorx for DeviceNet RSNetWorx for DeviceNet is a Rockwell Software application that can be used to set up DeviceNet networks and configure connected devices. To set up RSLinx for RSNetWorx for DeviceNet To use RSNetWorx for DeviceNet, you must first set up a driver in RSLinx. The driver provides a communications link between the computer and DeviceNet network. Step 1.
3-4 Configuring the Adapter To go 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 if RSNetWorx for DeviceNet does not have an EDS file for it. Step 1. After setting up a driver in RSLinx, start RSNetWorx for DeviceNet. 2. Select Network > Online. If the Browse for Network dialog box appears, RSLinx has multiple drivers configured. Select your DeviceNet network, and click OK. A prompt appears. 3.
Configuring the Adapter 3-5 To create an EDS file If the adapter and drive appear as an unrecognized device, create an EDS file for it. Step 1. Right-click the “Unrecognized Device” icon, and select Register Device in the menu. The EDS Wizard (Figure 3.3) 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.
3-6 Configuring the Adapter To access and edit parameters Parameters in the drive and adapter can be edited with RSNetWorx. The adapter parameters are appended to the list of drive parameters. Step 1. After creating an EDS file, right-click on the icon for the PowerFlex drive and adapter and select Properties. The PowerFlex Drive dialog box appears. 2. Click the Parameters tab (Figure 3.4). If an EDS Editor message appears, click Upload to load the parameter values in the drive to the computer.
Configuring the Adapter 3-7 Setting the Node Address The value of Parameter 02 - [DN Addr Cfg] determines the node address if all of the adapter DIP switches are in the CLOSED position (all 0’s). 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 (ADR). 1. Set the value of Parameter 02 - [DN Addr Cfg] to a unique node address. Figure 3.
3-8 Configuring the Adapter 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 adapter. If the Mode Jumper is set to the Single mode position, only one drive is represented by the adapter and Parameter 15 - [DSI I/O Cfg] 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 adapter. 1. Set the value in Parameter 15 - [DSI I/O Cfg]: Figure 3.
Configuring the Adapter 3-9 Cyclic and Polled data exchanges are configured in the scanner, so you only need to set the I/O configuration in the adapter. COS data exchange must be configured in both the adapter and the scanner. You need to set the I/O configuration and COS parameters in the adapter. To use COS (Change of State) data exchange 1. Set the bits in the Logic Status word that should be checked for changes in Parameter 12 - [COS Status Mask].
3-10 Configuring the Adapter 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 Parameter 07 - [Comm Flt Action] and a different response to an idle scanner using Parameter 08 - [Idle Flt Action]. ! ATTENTION: Risk of injury or equipment damage exists.
Configuring the Adapter 3-11 To set the fault configuration parameters If you set Parameter 07 - [Comm Flt Action] or 08 - [Idle Flt Action] to the “Send Flt Cfg,” the values in the following parameters are sent to the drive after a communications fault and/or idle fault occurs. You must set these parameters to values required by your application. Parameter 10 11 Name Flt Cfg Logic Flt Cfg Ref Description A 16-bit value sent to the drive for Logic Command.
3-12 Configuring the Adapter Viewing the Adapter Configuration The following parameters provide information about how the adapter is configured. You can view these parameters at any time. Number 01 Name Mode 03 DN Addr Actual 05 DN Rate Actual 09 DN Active Config 16 DSI I/O Actual Description The mode in which the adapter is set (0 = Single drive operation, or 2 = Multi-Drive operation). The node address used by the adapter.
Chapter 4 Configuring the Scanner Chapter 4 provides instructions on how to configure a scanner to communicate with the adapter and connected PowerFlex drive. Topic Example Network Setting Up the Scan List Page 4-1 4-2 Topic Mapping the Drive Data in the Scanner Saving the Configuration Page 4-5 4-7 Example Network After the adapter is configured, the connected drive and adapter will be a single node on the network.
4-2 Configuring the Scanner 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. 1. Go online with RSNetWorx for DeviceNet. Refer to the Using RSNetWorx for DeviceNet section in Chapter 3. The devices on the network are displayed in the configuration view. Figure 4.2 Configuration View (Graph) 2. Right-click the DeviceNet scanner (node 00 in Figure 4.2) and select Properties.
Configuring the Scanner 4-3 6. Under Available Devices, select the drive, and then click > (Right Arrow) to add it to the scanlist. Figure 4.3 Scanlist Page in the Scanner Module Dialog Box 7. Under Scanlist, select the drive, and then click Edit I/O Parameters. The Edit I/O Parameters dialog box (Figure 4.4) appears.
4-4 Configuring the Scanner Figure 4.4 Edit I/O Parameters Dialog Box 8. Select the type(s) of data exchange (Polled, Change of State, and /or Cyclic). In our example, we selected Polled. 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 adapter. This information can be found in Parameter 16 - [DSI I/O Actual] in the adapter. Table 4.A shows common configuration Input/Output sizes.
Configuring the Scanner 4-5 11. Click OK. If you changed any settings, a Scanner Applet asks if it is OK to unmap the I/O. Click Yes to continue. The Edit I/O Parameters dialog box closes and then the Scanner Module dialog box (Figure 4.3) re-appears. You will map the I/O in the next section in this chapter. 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.
4-6 Configuring the Scanner If you selected the Automap on Add box in the Scanlist page (Figure 4.3), RSNetWorx has already mapped the I/O. If it is not mapped, click Automap to map it. If you need to change the mapping, click Advanced and change the settings. 2. In the Memory box, select a location in scanner memory. Scanner 1747-SDN 1756-DNB 1771-SDN Memory Locations Discrete or M-File Assembly Data Block Xfer 62 – 57 In our example, we are using a 1747-SDN and selected Discrete. 3.
Configuring the Scanner 4-7 If you selected the Automap on Add box in the Scanlist page (Figure 4.3), RSNetWorx has already mapped the I/O. If it is not mapped, click Automap to map it. If you need to change the mapping, click Advanced and change the settings. 2. In the Memory box, select a location in scanner memory. Scanner 1747-SDN 1756-DNB 1771-SDN Memory Locations Discrete or M-File Assembly Data Block Xfer 62 – 57 In our example, we are using a 1747-SDN and selected Discrete. 3.
4-8 Configuring the Scanner
Chapter 5 Using I/O Messaging Chapter 5 provides information and examples that explain how to use I/O Messaging to control a PowerFlex 40 drive. Topic About I/O Messaging Understanding the I/O Image Using Logic Command/Status Using Reference/Feedback ! Page 5-1 5-2 5-2 5-3 Topic Example Ladder Logic Programs ControlLogix Example PLC-5 Example SLC Example Page 5-3 5-4 5-7 5-9 ATTENTION: Hazard of injury or equipment damage exists.
5-2 Using I/O Messaging 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 adapter. Input I/O is status data that is produced by the adapter 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 adapter and Parameter 15 - [DSI I/O Cfg].
Using I/O Messaging 5-3 Using Reference/Feedback When enabled, Reference/Feedback begins at word 1 in the I/O image. The Reference (16 bits) is produced by the controller and consumed by the adapter. The Feedback (16 bits) is produced by the adapter and consumed by the controller. Size 16-bit Valid Values -32768 to 32767 In I/O Image Word 1 Example Figure 5.1 Example Ladder Logic Programs These example ladder logic programs (Figure 5.3 – Figure 5.6) work with PowerFlex 40 drives.
5-4 Using I/O Messaging Logic Command/Status Words These examples use the Logic Command word and Logic Status word for PowerFlex 40 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 DSI product. Refer to the documentation for your drive. ControlLogix Example Figure 5.
Using I/O Messaging Figure 5.3 Example ControlLogix Ladder Logic Program ControlLogix example program with a PowerFlex 40 at node address 1. This rung enables the scanner (changes the scanner to RUN mode). Local:3:O.CommandRegister.Run 0 1 scanner,, and moves it to This section retrieves the Logic Status and Feedbackk data from the sc 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].
5-6 Using I/O Messaging Figure 5.3 Example ControlLogix Ladder Logic Program (Continued) 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 For the explicit message portion of this ladder example program, see Figure 6.6.
Using I/O Messaging 5-7 PLC-5 Example Figure 5.4 Control File for Block Transfers EN ST DN ER CO EW NR TO RW RLEN DLEN FILE BT20:0 0 0 0 0 0 0 0 0 0 62 0 9 BT20:1 0 0 0 0 0 0 0 0 0 62 0 10 ELEM R G 0 00 0 0 00 0 Figure 5.5 Example PLC-5 Ladder Logic Program PLC-5 example program with a PowerFlex 40 at DeviceNet node address 1. The DeviceNet scanner gathers the drive status data via the network.
5-8 Using I/O Messaging Figure 5.5 Example PLC-5 Ladder Logic Program (Continued) 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 = PowerFlex 40 (node 1) Logic Command N10:2 = PowerFlex 40 (node 1) Reference Note that the Reference for the PowerFlex 40 is set in Hz and not in engineering units like other PowerFlex drives. For example, "300" equates to 30.0 Hz (the decimal point is always implied).
Using I/O Messaging SLC Example Figure 5.6 Example SLC Ladder Logic Program SLC 5/03 example program with a PowerFlex 40 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 PowerFlex 40. The B3:0 bits would be controlled elsewhere in the user program.
5-10 Using I/O Messaging Figure 5.6 Example SLC Ladder Logic Program (Continued) 0006 0007 Node 1 Forward Command B3:0 Node 1 Logic Command REVERSE O:1 4 21 1747-SDN This rung controls the Reference for the PowerFlex 40. N7:0 would be controlled elsewhere in the user program. Note that the Reference for the PowerFlex 40 is set in Hz and not in engineering units like other PowerFlex drives. For example, "300" equates to 30.0 Hz (the decimal point is always implied).
Using I/O Messaging 5-11 Figure 5.6 Example SLC Ladder Logic Program (Continued) Node 1 Logic Status FAULTED I:1 0011 23 1747-SDN Node 1 Logic Status AT REFERENCE I:1 0012 0013 Node 1 FAULTED B3:1 24 1747-SDN 7 Node 1 AT REFERENCE B3:1 8 This rung displays the Feedback word for the PowerFlex 40. N7:1 would be used elsewhere in the user program. Note that the Feedback for the PowerFlex 40 is set in Hz and not in engineering units like other PowerFlex drives. For example, "300" equates to 30.
5-12 Using I/O Messaging
Chapter 6 Using Explicit Messaging Chapter 6 provides information and examples that explain how to use Explicit Messaging to monitor and configure the adapter installed and connected to the PowerFlex 40 drive. Topic About Explicit Messaging Formatting Explicit Messages Running Explicit Messages ! ! Page 6-1 6-2 6-7 Topic ControlLogix Example PLC-5 Example SLC Example Page 6-8 6-11 6-13 ATTENTION: Hazard of injury or equipment damage exists.
6-2 Using Explicit Messaging Formatting Explicit Messages 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 6.1. Figure 6.
Using Explicit Messaging 6-3 The following table identifies the number of Explicit Messages that can be executed at a time. Scanner Messages at One Time 1756-DNB 5 Refer To Figure 6.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.
6-4 Using Explicit Messaging 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 6.2 or Figure 6.3. Figure 6.
Using Explicit Messaging 6-5 The following table identifies the number of transaction blocks within a scanner that are reserved for Explicit Messaging. Scanner Number of Transaction Blocks 1747-SDN 10 1771-SDN 10 Words in Each Refer To Transaction Block 32 Figure 6.3 32 (two blocks can Figure 6.
6-6 Using Explicit Messaging PLC / SLC Explicit Message Responses Word 0 1 2 3 – 31 Description Status (Least Significant Byte) One of the following status codes is provided during each upload: 00 = Ignore transaction block (empty) 01 = Transaction completed successfully 02 = Transaction in progress (not ready) 03 = Slave not in scan list 04 = Slave offline 05 = DeviceNet port disabled or offline 06 = Transaction TXID unknown 08 = Invalid command code 09 = Scanner out of buffers 10 = Other client/serv
Using Explicit Messaging 6-7 Running Explicit Messages There are five basic events in the Explicit Messaging process. 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 an response message for all Explicit Messages, whether you are reading or writing data. Figure 6.
6-8 Using Explicit Messaging ControlLogix Example Data Format for a Read and Write Parameter The data in this example is for a PowerFlex drive at node address 1. Refer to Formatting Explicit Messages in this chapter for a description of the content in each box. Configuration Service Code Object Type Object ID Object Attribute Example Value e (hex) f (hex) 39 (dec) 1 (hex) Description Get_Attribute_Single Parameter Object Parameter Address Parameter Value Refer to . . .
Using Explicit Messaging Configuration Service Code Object Type Object ID Object Attribute Example Value 10 (hex) f (hex) 39 (dec) 1 (hex) Description Set_Attribute_Single Parameter Object Parameter Address Parameter Value Refer to . . . C-10 C-8 C-9 Figure 6.
6-10 Using Explicit Messaging Figure 6.6 Example ControlLogix Ladder Logic Program Explicit Messaging Example PerformParameterRead 16 PerformParameterWrite 17 MSG Type - CIP Generic Message Control ParameterRDMessage ... MSG Type - CIP Generic Message Control ParameterWRMessage ... EN DN ER EN DN ER (End) For the I/O message portion of this ladder example program, see Figure 5.3.
Using Explicit Messaging 6-11 PLC-5 Example Data Format for a Read and Write Parameter The data in this example is for a PowerFlex drive at node address 1. Refer to Formatting Explicit Messages in this chapter for a description of the content of the data file.
6-12 Using Explicit Messaging Ladder Logic Program Figure 6.7 Example PLC-5 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.
Using Explicit Messaging 6-13 SLC Example Data Format for a Read and Write Parameter The data in this example is for a PowerFlex drive at node address 1. Refer to Formatting Explicit Messages in this chapter for a description of the content of the data file.
6-14 Using Explicit Messaging Response Data for Write to Drive Parameter 101 Address N9:50 N9:51 N9:52 Value (hex) 0101 0000 9001 Description TXID = 01, Status = 01 (successful transaction) Port = 00, Size = 00 bytes Service = 90 (successful) Address = 01 (Node Address) Refer to . . . 6-6 6-6 6-6 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.
Using Explicit Messaging 6-15 Figure 6.8 Example SLC Ladder Logic Program 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. B3:2 COP Copy File Source #N9:10 0 Dest #M0:1.224 Length 32 B3:2 U 0 0015 When I:1.0/15 is ON (response to the explicit message is available), the response message is copied into N9:50.
6-16 Notes: Using Explicit Messaging
Chapter 7 Using Multi-Drive Mode Chapter 7 provides information and a ControlLogix ladder example to explain how to use Multi-Drive mode. ! Topic Single Mode vs. Multi-Drive Mode Page 7-1 System Wiring Understanding the I/O Image 7-3 7-4 Configuring the RS-485 Network 7-5 Topic Multi-Drive Ladder Logic Program Example ControlLogix Example Multi-Drive Mode Explicit Messaging Additional Information Page 7-6 7-7 7-20 7-22 ATTENTION: Hazard of injury or equipment damage exists.
7-2 Using Multi-Drive Mode Figure 7.2 Multi-Drive Mode Example for Network up to 5 drives per node DeviceNet Up to 4 PowerFlex 4's or 40's PowerFlex 40 22-COMM-D 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 Benefits of Multi-Drive mode include: • Lower hardware costs. Only one 22-COMM-D adapter is needed for up to five drives.
Using Multi-Drive Mode 7-3 • Automatic Device Replacement (ADR) cannot be used with any of the drives. • The RSNetWorx Parameter editor cannot be used. • Since the RS-485 ports are used for daisy-chaining the drives, there is no connection for a peripheral device such as a HIM. The AK-U0-RJ45-SC1 DSI Splitter cable cannot be used to add a second connection for a peripheral device.
7-4 Using Multi-Drive Mode 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 adapter. Input I/O is status data that is produced by the adapter 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 adapter and Parameter 15 - [DSI I/O Cfg].
Using Multi-Drive Mode 7-5 Configuring the RS-485 Network The following parameters must be set in the daisy-chained drives: Parameter P36 - [Start Source] P38 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr] A107 - [Comm Format] Value 5 (“RS485 [DSI] Port”) 5 (“RS485 [DSI] Port”) 4 (“19.2K”) 1-247 (must be unique) 0 (“RTU 8-N-1”) Note that the RS-485 network is fixed at 19.2K baud, 8 data bits, no parity, and 1 stop bit.
7-6 Using Multi-Drive Mode Multi-Drive Ladder Logic Program Example The example ladder logic program demonstrates using Multi-Drive mode with five drives. See Figure 7.2 for a system layout diagram. Function of the Example Program The example program provided is for the ControlLogix, but other controllers can also be used. The following actions can be performed: • View status information from the drives such as Ready, Fault, At Speed, and Feedback.
Using Multi-Drive Mode 7-7 Drive Settings for the Example Program Parameter P36 - [Start Source] P38 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr](1) A105 - [Comm Loss Action] A106 - [Comm Loss Time] A107 - [Comm Format] (1) Value Drive 0 Drive 1 Drive 2 Drive 3 Drive 4 5 5 5 5 5 5 5 5 5 5 4 4 4 4 4 1 2 3 4 5 0 0 0 0 0 5 5 5 5 5 0 0 0 0 0 The settings for these parameters must match the respective parameter settings in the adapter (Parameter 17 - [Drive 0 Address] through Parameter
7-8 Using Multi-Drive Mode Tag Name Perform Parameter Write 0 Parameter WR Value 0 Parameter WR Message 0 Type BOOL INT MESSAGE Description Initiates the parameter value Write value to the parameter Set_Attribute_Single (Write) The same type of Tags are also used for Drive 1 through Drive 4. Main Routine The Main Routine tells the 1756-DNB scanner to run, reads the network Input Image from the scanner, calls the various drive control subroutines, and writes the network Output Image to the scanner.
Using Multi-Drive Mode Figure 7.6 Main Routine ControlLogix MultiDrive example program with a PowerFlex 40 at node address 1. Four PowerFlex 4/40's are daisy-chained to the main PowerFlex 40 via their RJ45 ports (RS-485). In this mode, up to FIVE PowerFlex 4/40's can exist on ONE DeviceNet node. This rung enables the scanner (changes the scanner to RUN mode). Local:3:O.CommandRegister.
7-10 Using Multi-Drive Mode Figure 7.6 Main Routine (Continued) This section writes the output image to the scanner.
Using Multi-Drive Mode Figure 7.7 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].
7-12 Using Multi-Drive Mode Figure 7.7 Drive 0 Control Routine (Continued) 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 13 MSG Type - CIP Generic Message Control ParameterRDMessage0 ... EN DN ER PerformParameterWrite0 14 MSG Type - CIP Generic Message Control ParameterWRMessage0 ...
Using Multi-Drive Mode Figure 7.8 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].
7-14 Using Multi-Drive Mode Figure 7.8 Drive 1 Control Routine (Continued) 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 13 MSG Type - CIP Generic Message Control ParameterRDMessage1 ... EN DN ER PerformParameterWrite1 14 MSG Type - CIP Generic Message Control ParameterWRMessage1 ...
Using Multi-Drive Mode Figure 7.9 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].
7-16 Using Multi-Drive Mode Figure 7.9 Drive 2 Control Routine (Continued) 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 13 MSG Type - CIP Generic Message Control ParameterRDMessage2 ... EN DN ER PerformParameterWrite2 14 MSG Type - CIP Generic Message Control ParameterWRMessage2 ...
Using Multi-Drive Mode Figure 7.10 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].
7-18 Using Multi-Drive Mode Figure 7.10 Drive 3 Control Routine (Continued) 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 13 MSG Type - CIP Generic Message Control ParameterRDMessage3 ... EN DN ER PerformParameterWrite3 14 MSG Type - CIP Generic Message Control ParameterWRMessage3 ...
Using Multi-Drive Mode Figure 7.11 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].
7-20 Using Multi-Drive Mode Figure 7.11 Drive 4 Control Routine (Continued) 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 13 MSG Type - CIP Generic Message Control ParameterRDMessage4 ... EN DN ER PerformParameterRead4 14 MSG Type - CIP Generic Message Control ParameterWRMessage4 ...
Using Multi-Drive Mode 7-21 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 7.12 and the write is shown in Figure 7.13. Figure 7.12 Parameter Read Message Configuration Figure 7.
7-22 Using Multi-Drive Mode The Class Code is “ f ” for the Parameter Object and the Instance Attribute is “1” to select retrieving the parameter value. See Appendix C, Parameter Object for more information. The Instance value is “17447” to access Parameter 39 - [Accel Time 1].
Chapter 8 Troubleshooting Chapter 8 contains troubleshooting information. Topic Locating the Status Indicators Page 8-1 PORT Status Indicator 8-2 MOD Status Indicator Net A Status Indicator 8-3 8-4 Topic Module Diagnostic Items in Single Drive Mode Module Diagnostic Items in Multi-Drive Mode Viewing and Clearing Events Page 8-4 8-5 8-6 Locating the Status Indicators The DeviceNet adapter has three status indicators. They can be viewed on the adapter or through the drive cover. See Figure 8.1.
8-2 Troubleshooting PORT Status Indicator Status Off Cause Corrective Action The adapter is not powered or • Securely connect the adapter to the drive is not connected properly to using the ribbon cable. the drive. • Apply power to the drive. Flashing The adapter is not receiving • Clear any drive faults. Red communication from the drive, • Verify that cables are securely connected. connected drive is faulted, or • Cycle power to the drive. a drive is missing in Multi-Drive mode.
Troubleshooting 8-3 MOD Status Indicator Status Off Cause The adapter is not powered. Corrective Action • Securely connect the adapter to the drive using the ribbon cable. • Apply power to the drive. Flashing The adapter has failed the • Clear faults in the drive. Red firmware test, connected drive • Cycle power to the drive. is faulted, or a drive is missing • If cycling power does not correct the in Multi-Drive mode. problem, the parameter settings may have been corrupted.
8-4 Troubleshooting Net A Status Indicator Status Off Cause Corrective Actions The adapter and/or • Securely connect the adapter to the drive network is not powered or using the Internal Interface cable and to the adapter is not connected network using a DeviceNet cable. properly to the network. • Correctly connect the DeviceNet cable to the DeviceNet plug. • Apply power to the drive and network. Flashing A DeviceNet I/O • Place the scanner in RUN mode, or apply Red connection has timed out.
Troubleshooting Module Diagnostic Items in Multi-Drive Mode The following diagnostic items can be accessed using DriveExplorer (version 3.01 or higher). No.
8-6 Troubleshooting Viewing and Clearing Events The adapter maintains an event queue that reports the history of its actions. You can view the event queue using DriveExplorer (3.01) software. Figure 8.
Troubleshooting 8-7 Events Many events in the Event queue occur under normal operation. If you encounter unexpected communications problems, the events may help you or Allen-Bradley personnel troubleshoot the problem. The following events may appear in the event queue: Code 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Event No Event Host Sent Reset EEPROM Sum Flt Reserved Control Disabled Control Enabled Description Text displayed in an empty event queue entry.
8-8 Notes: Troubleshooting
Appendix A Specifications This chapter present the specifications for the adapter. Topic Communications Electrical Mechanical Page A-1 A-1 A-1 Topic Environmental Regulatory Compliance Page A-2 A-2 Communications Network Protocol Data Rates Drive Protocol DeviceNet 125K, 250K, 500K, Autobaud DSI Electrical Consumption Drive Network 150 mA at 5V supplied through the drive 60 mA at 24V supplied through DeviceNet Use the 60 mA value to size the network current draw from the power supply.
A-2 Specifications Environmental Temperature Operating Storage Relative Humidity -10 to +50 °C (14 to 149 °F) -40 to +85 °C (-40 to +185 °F) -5 to 95% non-condensing Regulatory Compliance Certification UL cUL CE Specification UL508C CAN / CSA C22.2 No.
Appendix B Adapter Parameters Appendix B provides information about the DeviceNet adapter parameters. Topic Page About Parameter Numbers B-1 Parameter List B-1 About Parameter Numbers The parameters in the adapter are numbered consecutively. However, depending on which configuration tool you use, they may have different numbers. Configuration Tool • DriveExplorer • DriveTools 2000 • HIM • Explicit Messaging • RSNetWorx for DeviceNet Numbering Scheme The adapter parameters begin with parameter 1.
B-2 Adapter Parameters Parameter No. Name and Description 04 [DN Rate Cfg] Sets the DeviceNet data rate after a reset or power cycle. Details Default: Values: This setting is used when all of the adapter DIP switches are in the CLOSED position (all 0’s). 05 06 Type: Reset Required: [DN Rate Act] Default: Displays DeviceNet data rate currently being used Values: by the adapter. [Reset Module] No action if set to “Ready.” Resets the adapter if set to “Reset Module.
Adapter Parameters Parameter No. Name and Description 09 [DN Act Cfg] Displays the source from which the adapter node address and data rate are taken. This will either be switches or parameters in EEPROM. It is determined by the settings of the switches on the adapter. 10 [Flt Cfg Logic] Sets the Logic Command data that is sent to the drive if any of the following is true: • Parameter 07 - [Comm Flt Action] is set to Send Flt Cfg and communications are disrupted.
B-4 Adapter Parameters Parameter No. Name and Description Details 15 [DSI I/O Cfg] Default: Sets the configuration of the Drives that are active Values: in the Multi-Drive mode. Identifies the connections that would be attempted on a reset or power cycle. 16 [DSI I/O Act] Displays the Drives that are active in the Multi-Drive mode.
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 example ladder logic programs, refer to Chapter 6, Using Explicit Messaging. Object Identity Object Connection Object Register Object Parameter Object Parameter Group Object PCCC Object Class Code Hex. Dec.
C-2 DeviceNet Objects Identity Object Class Code Hexadecimal 0x01 Decimal 1 Instances (Single-Drive Mode) The number of instances is fixed at three and is as shown below: Instance 0 1 2 3 Description Class Host drive 22-COMM-D 22-SCM-232 or 22-HIM-* (when present) Instances (Multi-Drive Mode) The number of instances is fixed at one and is as shown below: Instance 0 1 Description Class 22-COMM-D Class Attributes Attribute ID 1 2 Access Name Rule Get Revision Get Max Instance Data Type Description
DeviceNet Objects Identity Object (Continued) Instance Attributes Attribute ID 1 2 3 Access Rule Get Get Get Name Data Type Description Vendor ID Device Type Product Code UINT UINT UINT 1 = Allen-Bradley 4 Get Revision 5 Get Status Struct of USINT USINT WORD 6 7 Get Get Serial Number Product Name UDINT SHORT_ STRING Unique number identifying the product name and rating Product Revision: Major Minor Bit 0 = Owned Bit 2 = Configured Bit 10 = Recoverable fault Bit 11 = Unrecoverable fault U
C-4 DeviceNet Objects Connection Object Class Code Hexadecimal Decimal 0x05 5 Instances Instance 1 2 4 6 – 10 Description Master-Slave Explicit Message Connection Polled I/O Connection Change of State/Cyclic Connection Explicit Message Connection Instance Attributes Refer to the DeviceNet Specification for more information.
DeviceNet Objects C-5 Connection Object (Continued) Instance Attributes (Continued) Refer to the DeviceNet Specification for more information.
C-6 DeviceNet Objects Register Object Class Code Hexadecimal Decimal 0x07 7 Instances The number of instances is fixed at thirteen and is as shown below: Instance 0 1 2 3 4 5 6 7 8 9 10 11 12 13 (1) Description Class Command and reference for all drives (read/write) Status and feedback for all drives (read-only) Command and reference for Drive 0 (read/write) Status and feedback for Drive 0 (read-only) Command and reference for Drive 1 (read/write) Status and feedback for Drive 1 (read-only) Command and
DeviceNet Objects C-7 Register Object (Continued) Class Attributes Not supported. Instance Attributes Attribute Access Rule Name ID 1 Get Bad Flag Data Type Description BOOL 2 Get BOOL 3 4 Get Size Conditional(1) Data If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data.
C-8 DeviceNet Objects Parameter Object Class Code Hexadecimal Decimal 0x0F 15 Instances (Single-Drive Mode) The number of instances is as shown below: Instance 0 1 " n n+1 " n + 21 Description Class Drive Parameter 1 " Drive Parameter n Adapter Parameter 1 " Adapter Parameter 21 Instances (Multi-Drive Mode) The number of instances is fixed at 21 and is as shown below: Instance 0 1 " 21 Description Class Adapter Parameter 1 " Adapter Parameter 21 Class Attributes Attribute ID 1 2 8 Access Rule Get Ge
DeviceNet Objects C-9 Parameter Object (Continued) Instance Attributes Attribute Access Name Data Type Description ID Rule (1) (3) 1 Parameter Value (2) 2 Get Link Path Size USINT 0 = No link specified n = Link specified (4) 3 Get Link Path 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 C3 = INT C7 = UINT D2 = WORD (16-bit) (3) 6 Get Data Size
C-10 DeviceNet Objects Parameter Object (Continued) Services Service Code 0x01 0x05 0x0E 0x10 0x4B Implemented for: Class No Yes Yes No No Service Name Instance Yes No Yes Yes Yes Get_Attribute_All Reset Get_Attribute_Single Set_Attribute_Single Get_Enum_String
DeviceNet Objects C-11 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 adapter parameters is appended to the list of groups in the drive.
C-12 DeviceNet Objects Parameter Group Object (Continued) Instance Attributes Attribute Access Name ID Rule 1 Get Group Name String 2 Get 3 Get 4 Get " n Get (1) Data Description Type SHORT_ Group name STRING Number of Members UINT Number of parameters in group. in Group (1) 1st Parameter UINT Number in Group (1) 2nd Parameter UINT Number in Group " (1) n Parameter UINT Number in Group Value varies based on group instance.
DeviceNet Objects C-13 PCCC Object Class Code Hexadecimal Decimal 0x67 103 Instances Not supported Class Attributes Not supported. Instance Attributes Not supported.
C-14 DeviceNet Objects PCCC Object (Continued) Message Structure for Execute_PCCC Request Name Data Type Length USINT Description Length of requestor ID Vendor UINT Vendor number of requestor Serial UDINT ASA serial Number number of requestor Other Product Identifier of user, Specific task, etc. on the requestor CMD USINT Command byte STS USINT 0 TNSW UINT Transport word FNC USINT Function code. Not used for all CMD’s.
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 adapter. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation.
D-2 Logic Command/Status Words PowerFlex 4 and PowerFlex 40 Drives 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 Active Command Direction Actual Direction Accel Decel Alarm Fault At Speed Main Freq Operation Command Parameters Digital Input 1 Status Digital Input 2 Status Digital Input 3 Status Digital Input 4 Status Description 0 = Not Ready 1 = Ready 0 = Not Active 1 = Active 0 = Reverse 1 = Forward 0 = Reverse 1 = Forward 0 = Not Accel
Glossary A Adapter Devices such as drives, controllers, and computers usually require an adapter to provide a communication interface between them and a network such as DeviceNet. An adapter reads data on the network and transmits it to the connected device. It also reads data in the device and transmits it to the network. The 20-COMM-D DeviceNet adapter is an adapter that connects, PowerFlex drives to a DeviceNet network.
Glossary-2 Controller A controller, also called programmable logic controller, is a solid-state control system that has a user-programmable memory for storage of instructions to implement specific functions such as I/O control, logic, timing, counting, report generation, communication, arithmetic, and data file manipulation. A controller consists of a central processor, input/ output interface, and memory. See also Scanner.
Glossary-3 DeviceNet Network A DeviceNet network uses a producer/consumer Controller Area Network (CAN) to connect devices (for example, controllers, drives, and motor starters). Both I/O and explicit messages can be transmitted over the network. A DeviceNet network can support a maximum of 64 devices. Each device is assigned a unique node address and transmits data on the network at the same data rate. A cable is used to connect devices on the network. It contains both the signal and power wires.
Glossary-4 DriveTools Software A software suite designed for Microsoft Windows 95, Windows 98, and Windows NT (4.0 or greater) operating systems. This software suite provides a family of tools that you can use to program, monitor, control, troubleshoot, and maintain Allen Bradley products. DriveTools 2000 (version 1.xx) can be used with PowerFlex drives. Information about DriveTools can be accessed at http://www.ab.com/drives.
Glossary-5 Flash Update The process of updating firmware in the adapter. The adapter can be flash updated using the X-Modem protocol and a 1203-SSS Smart Self-powered Serial converter (firmware 3.xx). H Heartbeat Rate The heartbeat rate is used in Change of State (COS) data exchange. It is associated with producing data once every EPR (Expected Packet Rate) duration. There may be four heartbeats before a time-out happens.
Glossary-6 N Node Address A DeviceNet network can have as many as 64 devices connected to it. Each device on the network must have a unique node address between 0 and 63. Node address 63 is the default used by uncommissioned devices. Node addresses are sometimes called “MAC IDs.” NVS (Non-Volatile Storage) NVS is the permanent memory of a device. Devices such as the adapter and drive store parameters and other information in NVS so that they are not lost when the device loses power.
Glossary-7 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-8 U UCMM (UnConnected Message Manager) UCMM provides a method to create connections between DeviceNet devices. Z Zero Data When communications are disrupted (for example, a cable is disconnected), the adapter and drive can respond with zero data. Zero data results in the drive receiving zero as values for command data. If the drive was running and using the Reference from the adapter, it will stay running but at zero Reference.
Index Numerics bus off, G-1 10-pin linear plug, 2-4 5-pin linear plug, 2-4 A adapter adding to the scan list, 4-2 applying power, 2-7 commissioning, 2-1 compatible products, 1-3 components, 1-1 definition, G-1 features, 1-2 grounding, 2-5 illustration, 1-1 installing, 2-1 to 2-7 mapping I/O in the scanner, 4-5 mounting, 2-5 to 2-6 parameters, B-1 to B-4 resetting, 3-11 Single/Multi-Drive mode of operation, 2-3 specifications, A-1 tools to configure, 3-1 troubleshooting, 8-1 viewing the active configurati
Index-2 COS, refer to Change of State COS/Cyc Interval parameter, B-3 Cyclic configuring a scanner for, 4-4 configuring an adapter for, 3-8 definition, G-2 D data exchange Change of State (COS), G-1 Cyclic, G-2 Polled, G-6 data rate definition, G-2 setting with a parameter, 3-7 setting with the switches, 2-2 DeviceNet 10-pin linear plug, 2-4 5-pin linear plug, 2-4 cable, 2-4 connector on adapter, 1-1 definition, G-3 example network, 4-1 objects, C-1 DeviceNet adapter, refer to adapter dimensions, A-1 DN Ac
Index-3 F fault action configuring an adapter, 3-10 definition, G-4 fault configuration configuring an adapter for, 3-10 definition, G-4 faulted node recovery definition, G-4 supported feature, 1-2 faults, refer to events features, 1-2 firmware release, soc-i, P-2 flash update, G-5 Flt Cfg Logic parameter, B-3 Flt Cfg Ref parameter, B-3 formatting Explicit Messages, 6-2 G going online with RSNetWorx, 3-4 grounding the adapter, 2-5 H heartbeat rate definition, G-5 setting in the scanner, 4-4 HIM (Human In
Index-4 mechanical dimensions, A-1 P messages, refer to Explicit Messages Parameter Group object, C-11 MOD status indicator locating, 8-1 troubleshooting with, 8-3 Parameter object, C-8 modes of operation, 1-6 mounting the adapter, 2-5 to 2-6 Multi-Drive mode additional information, 7-22 Explicit messaging, 7-20 ladder logic program example, 7-6 setting with the jumper, 2-3 system wiring, 7-3 using, 7-1 versus Single mode, 7-1 N NET A status indicator locating, 8-1 troubleshooting with, 8-4 NET B sta
Index-5 R reference/feedback definition, G-7 in I/O image, 5-2, 7-4 using, 5-3 Register object, C-6 regulatory compliance, A-1 related documentation, P-1 Reset Module parameter, B-2 ribbon cable, refer to Internal Interface cable RSLinx, P-2, 3-3 RSNetWorx for DeviceNet creating EDS files with, 3-5 definition, G-7 editing parameters with, 3-6 going online, 3-4 saving a network configuration, 4-7 setting up RSLinx for, 3-3 using to map I/O, 4-5 using to set up a scan list, 4-2 web site, G-7 SLC example pro
Index-6
www.rockwellautomation.com Corporate Headquarters Rockwell Automation, 777 East Wisconsin Avenue, Suite 1400, Milwaukee, WI, 53202-5302 USA, Tel: (1) 414.212.5200, Fax: (1) 414.212.5201 Headquarters for Allen-Bradley Products, Rockwell Software Products and Global Manufacturing Solutions Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.
