Rockwell Automation Allen-Bradley 22-COMM-D User Manual
  1. Manuals
  2. Brands
  3. Rockwell Automation Manuals
  4. Adapter
  5. Allen-Bradley 22-COMM-D
  6. User manual

Rockwell Automation Allen-Bradley 22-COMM-D User Manual

Powerflex devicenet adapter.
Hide thumbs
Table of Contents

Advertisement

Quick Links

DeviceNet
Adapter
22-COMM-D
FRN 1.xxx
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Allen-Bradley 22-COMM-D and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Rockwell Automation Allen-Bradley 22-COMM-D

Summary of Contents for Rockwell Automation Allen-Bradley 22-COMM-D

  • Page 1 DeviceNet Adapter 22-COMM-D FRN 1.xxx User Manual...

  • Page 2: Important User Information

    In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
  • Page 3 Summary of Changes This is the first release of the DeviceNet adapter FRN 1.xxx.
  • Page 4 S-ii Summary of Changes...

  • Page 5: Table Of Contents

    Conventions Used in this Manual ..... P-2 Rockwell Automation Support......P-2...
  • Page 6 Table of Contents Chapter 5 Using I/O Messaging About I/O Messaging ....... 5-1 Understanding the I/O Image.
  • Page 7 Table of Contents Appendix B Adapter Parameters About Parameter Numbers......B-1 Parameter List ........B-1 Appendix C DeviceNet Objects Identity Object .
  • Page 8 Table of Contents...

  • Page 9: Preface

    Preface About This Manual Topic Page Related Documentation Conventions Used in this Manual P-2 Rockwell Automation Support Related Documentation For: Refer to: Publication DeviceNet™ Cables DeviceNet Product Overview DN-2.5 and Components DeviceNet Network DeviceNet Cable System Planning and Installation DN-6.7.2...

  • Page 10: Conventions Used In This Manual

    Contact your local Rockwell Automation, Inc. representative for sales and order support, product technical training, warranty support, and support service agreements. Technical Product Assistance If you need to contact Rockwell Automation, Inc. for technical assistance, please review the information in Chapter Troubleshooting first.

  • Page 11: Getting Started

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

  • Page 12: Features

    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.

  • Page 13: Compatible Products

    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.

  • Page 14: Safety Precautions

    There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.

  • Page 15: Quick Start

    Getting Started 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 Refer to Review the safety precautions for the adapter. Throughout This Manual Verify that the PowerFlex drive is properly installed.

  • Page 16: Modes Of Operation

    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) ➊ ➋ ➌ ➊ ➋...

  • Page 17: Preparing For An Installation

    Chapter Installing the Adapter Chapter 2 provides instructions for installing the adapter in a PowerFlex 40 drive. Topic Page Preparing for an Installation Commissioning the Adapter Connecting the Adapter to the Network Connecting the Adapter to the Drive Applying Power Preparing for an Installation Before installing the DeviceNet adapter: •...
  • Page 18 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.1 Setting Node Address/Data Rate Switches and Single/Multi-Drive Operation Jumper Single Drive Multi-Drive Operation Operation NODE RATE 3 4 5 6 7 3 4 5 6 7 UP = OPEN = 1 Switches Description...
  • Page 19 Installing the Adapter Figure 2.2 Node Address Switch Settings (UP = OPEN = 1) (Continued) Switch Setting Node Switch Setting Node SW 1 SW 2 SW 3 SW 4 SW 5 SW 6 Address SW 1 SW 2 SW 3 SW 4 SW 5 SW 6 Address Figure 2.3 Data Rate Switch Settings (UP = OPEN = 1) Switch Setting Data...

  • Page 20: Connecting The Adapter To The Network

    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.

  • Page 21: Connecting The Adapter To The Drive

    Installing the Adapter 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).
  • Page 22 Installing the Adapter Figure 2.6 Mounting the Adapter Adapter Mounted on Back of Cover PowerFlex 40 Drive B and C Frames (cover removed)

  • Page 23: Applying Power

    Installing the Adapter 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.
  • Page 24 Installing the Adapter Notes:...

  • Page 25: Configuring The Adapter

    Chapter Configuring the Adapter Chapter 3 provides instructions and information for setting the parameters in the adapter. Topic Page Topic Page Configuration Tools Setting the I/O Configuration Using the PowerFlex 4-Class HIM 3-2 Selecting COS, Cyclic, or Polled I/O 3-8 Using RSNetWorx for DeviceNet Setting a Fault Action 3-10...

  • Page 26: Using The Powerflex 4-Class Him

    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.

  • Page 27: Using Rsnetworx For Devicenet

    Configuring the Adapter 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.
  • Page 28 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 Icons 1.
  • Page 29 Configuring the Adapter To create an EDS file If the adapter and drive appear as an unrecognized device, create an EDS file for it. Step Icons 1. Right-click the “Unrecognized Device” icon, and select Register Device in the menu. The EDS Wizard (Figure 3.3) appears.
  • Page 30 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 Icons 1. After creating an EDS file, right-click on the icon for the PowerFlex drive and adapter and select Properties.

  • Page 31: Setting The Node Address

    Configuring the Adapter 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.

  • Page 32: Setting The I/O Configuration

    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.
  • Page 33 Configuring the Adapter 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.

  • Page 34: Setting A Fault Action

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

  • Page 35: Resetting The Adapter

    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.

  • Page 36: Viewing The Adapter Configuration

    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 Name Description Mode The mode in which the adapter is set (0 = Single drive operation, or 2 = Multi-Drive operation). DN Addr The node address used by the adapter.

  • Page 37: Configuring The Scanner

    Chapter Configuring the Scanner Chapter 4 provides instructions on how to configure a scanner to communicate with the adapter and connected PowerFlex drive. Topic Page Topic Page Example Network Mapping the Drive Data in the Scanner Setting Up the Scan List Saving the Configuration Example Network After the adapter is configured, the connected drive and adapter will be a...

  • Page 38: Setting Up The Scan List

    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...
  • Page 39 Configuring the Scanner 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.
  • Page 40 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.

  • Page 41: Mapping The Drive Data In The Scanner

    Configuring the Scanner 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 (Figure 4.3) re-appears.
  • Page 42 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.

  • Page 43: Saving The Configuration

    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.
  • Page 44 Configuring the Scanner...

  • Page 45: About I/O Messaging

    There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.

  • Page 46: Understanding The I/O Image

    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.

  • Page 47: Using Reference/Feedback

    Using I/O Messaging 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.

  • Page 48: Controllogix Example

    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 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.
  • Page 49 Using I/O Messaging Figure 5.3 Example ControlLogix Ladder Logic Program ControlLogix example program with a PowerFlex 40 at node address 1. ControlLogix example program with a PowerFlex 40 at node address 1. This rung enables the scanner (changes the scanner to RUN mode). This rung enables the scanner (changes the scanner to RUN mode).
  • Page 50 Using I/O Messaging Figure 5.3 Example ControlLogix Ladder Logic Program (Continued) DriveCommandForward DriveOutputImage[0].4 DriveCommandForward DriveOutputImage[0].5 Copy File Source DriveReference Dest DriveOutputImage[1] Length Copy File Source DriveOutputImage[0] Dest Local:3:O.Data[0] Length For the explicit message portion of this ladder example program, see Figure 6.6.

  • Page 51: Plc-5 Example

    Using I/O Messaging PLC-5 Example Figure 5.4 Control File for Block Transfers EN ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM R BT20:0 0 00 0 BT20:1 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.
  • Page 52 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.

  • Page 53: Slc Example

    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 0000 1747-SDN This section of rungs control the Logic Command bits for the PowerFlex 40.
  • Page 54 5-10 Using I/O Messaging Figure 5.6 Example SLC Ladder Logic Program (Continued) Node 1 Node 1 Forward Logic Command Command REVERSE B3:0 0006 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.
  • Page 55 Using I/O Messaging 5-11 Figure 5.6 Example SLC Ladder Logic Program (Continued) Node 1 Logic Status Node 1 FAULTED FAULTED B3:1 0011 1747-SDN Node 1 Logic Status Node 1 AT REFERENCE AT REFERENCE B3:1 0012 1747-SDN This rung displays the Feedback word for the PowerFlex 40. N7:1 would be used elsewhere in the user program.
  • Page 56 5-12 Using I/O Messaging...

  • Page 57: Using Explicit Messaging

    There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.

  • Page 58: Formatting Explicit Messages

    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.
  • Page 59 Using Explicit Messaging The following table identifies the number of Explicit Messages that can be executed at a time. Scanner Messages at Refer To One Time 1756-DNB 5 Figure 6.1 ControlLogix Message Requests and Responses Box Description ➊ Message Type The message type must be CIP Generic.
  • Page 60 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 Figure...
  • Page 61 Using Explicit Messaging The following table identifies the number of transaction blocks within a scanner that are reserved for Explicit Messaging. Scanner Number of Words in Each Refer To Transaction Blocks Transaction Block 1747-SDN 10 Figure 6.3 1771-SDN 10 32 (two blocks can Figure 6.2 be moved at once) PLC / SLC Explicit Message Requests...
  • Page 62 Using Explicit Messaging PLC / SLC Explicit Message Responses Word 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...

  • Page 63: Running Explicit Messages

    Using Explicit Messaging 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.

  • Page 64: Controllogix Example

    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 Example Value Description Refer to .
  • Page 65 Using Explicit Messaging Configuration Example Value Description Refer to . . . Service Code 10 (hex) Set_Attribute_Single C-10 Object Type f (hex) Parameter Object Object ID 39 (dec) Parameter Address Object Attribute 1 (hex) Parameter Value Figure 6.5 Tags for the Example Explicit Messaging Program Tag Names Tag Names for Read Message...
  • Page 66 6-10 Using Explicit Messaging Figure 6.6 Example ControlLogix Ladder Logic Program Explicit Messaging Example Explicit Messaging Example PerformParameterRead Type - CIP Generic Message Control ParameterRDMessage ... PerformParameterWrite Type - CIP Generic Message Control ParameterWRMessage ... (End) For the I/O message portion of this ladder example program, see Figure 5.3.

  • Page 67: Plc-5 Example

    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.
  • Page 68 6-12 Using Explicit Messaging Ladder Logic Program Figure 6.7 Example PLC-5 Ladder Logic Program Explicit Messaging Example 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.

  • Page 69: Slc Example

    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.
  • Page 70 6-14 Using Explicit Messaging Response Data for Write to Drive Parameter 101 Address Value (hex) Description Refer to . . . N9:50 0101 TXID = 01, Status = 01 (successful transaction) N9:51 0000 Port = 00, Size = 00 bytes N9:52 9001 Service = 90 (successful)
  • Page 71 Using Explicit Messaging 6-15 Figure 6.8 Example SLC Ladder Logic Program Explicit Messaging Example 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.
  • Page 72 6-16 Using Explicit Messaging Notes:...

  • Page 73: Using Multi-Drive Mode

    There are many variables and requirements with any application. Rockwell Automation, Inc. does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
  • Page 74 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 AK-U0-RJ45-TB2P RS-485 AK-U0-RJ45-TB2P Connector w/3rd Party Terminating Resistor Benefits of Multi-Drive mode include: •...

  • Page 75: System Wiring

    Using Multi-Drive Mode • 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.

  • Page 76: Understanding The I/O Image

    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.

  • Page 77: Configuring The Rs-485 Network

    Using Multi-Drive Mode Configuring the RS-485 Network The following parameters must be set in the daisy-chained drives: Parameter Value P36 - [Start Source] 5 (“RS485 [DSI] Port”) P38 - [Speed Reference] 5 (“RS485 [DSI] Port”) A103 - [Comm Data Rate] 4 (“19.2K”) A104 - [Comm Node Addr] 1-247 (must be unique)

  • Page 78: Multi-Drive Ladder Logic Program Example

    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.

  • Page 79: Controllogix Example

    Using Multi-Drive Mode Drive Settings for the Example Program Value Parameter Drive 0 Drive 1 Drive 2 Drive 3 Drive 4 P36 - [Start Source] P38 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr] A105 - [Comm Loss Action] A106 - [Comm Loss Time] A107 - [Comm Format] The settings for these parameters must match the respective parameter...
  • Page 80 Using Multi-Drive Mode Tag Name Type Description Perform Parameter Write 0 BOOL Initiates the parameter value Parameter WR Value 0 Write value to the parameter Parameter WR Message 0 MESSAGE 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,...
  • Page 81 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.
  • Page 82 7-10 Using Multi-Drive Mode Figure 7.6 Main Routine (Continued) This section writes the output image to the scanner. The output image is as follows: This section writes the output image to the scanner. The output image is as follows: DriveOutputImage[0] and DriveOutputImage[1] = Drive 0 Logic Command and Reference DriveOutputImage[0] and DriveOutputImage[1] = Drive 0 Logic Command and Reference DriveOutputImage[2] and DriveOutputImage[3] = Drive 1 Logic Command and Reference DriveOutputImage[2] and DriveOutputImage[3] = Drive 1 Logic Command and Reference...
  • Page 83 Using Multi-Drive Mode 7-11 Figure 7.7 Drive 0 Control Routine Drive 0 Control Subroutine Drive 0 Control Subroutine This section takes the data from the input area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[0].0 Drive0StatusReady DriveInputImage[0].1...
  • Page 84 7-12 Using Multi-Drive Mode Figure 7.7 Drive 0 Control Routine (Continued) Explicit Messaging Example Explicit Messaging Example Drive 0 parameters are accessed by adding 17408 decimal (4400 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 17447 (17408 + 39) is used.
  • Page 85 Using Multi-Drive Mode 7-13 Figure 7.8 Drive 1 Control Routine Drive 1 Control Subroutine Drive 1 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[2].0 Drive1StatusReady DriveInputImage[2].1...
  • Page 86 7-14 Using Multi-Drive Mode Figure 7.8 Drive 1 Control Routine (Continued) Explicit Messaging Example Explicit Messaging Example Drive 1 parameters are accessed by adding 18432 decimal (4800 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 18471 (18432 + 39) is used.
  • Page 87 Using Multi-Drive Mode 7-15 Figure 7.9 Drive 2 Control Routine Drive 2 Control Subroutine Drive 2 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[4].0 Drive2StatusReady DriveInputImage[4].1...
  • Page 88 7-16 Using Multi-Drive Mode Figure 7.9 Drive 2 Control Routine (Continued) Explicit Messaging Example Explicit Messaging Example Drive 2 parameters are accessed by adding 19456 decimal (4C00 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 19495 (19456 + 39) is used.
  • Page 89 Using Multi-Drive Mode 7-17 Figure 7.10 Drive 3 Control Routine Drive 3 Control Subroutine Drive 3 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[6].0 Drive3StatusReady DriveInputImage[6].1...
  • Page 90 7-18 Using Multi-Drive Mode Figure 7.10 Drive 3 Control Routine (Continued) Explicit Messaging Example Explicit Messaging Example Drive 3 parameters are accessed by adding 20480 decimal (5000 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 20519 (20480 + 39) is used.
  • Page 91 Using Multi-Drive Mode 7-19 Figure 7.11 Drive 4 Control Routine Drive 4 Control Subroutine Drive 4 Control Subroutine This section takes the data from the input image area and moves it to specific tags (Logic Status bits and Feedback) for use elsewhere in the ladder program. DriveInputImage[8].0 Drive4StatusReady DriveInputImage[8].1...

  • Page 92: Multi-Drive Mode Explicit Messaging

    7-20 Using Multi-Drive Mode Figure 7.11 Drive 4 Control Routine (Continued) Explicit Messaging Example Explicit Messaging Example Drive 4 parameters are accessed by adding 21504 decimal (5400 hex) to the desired parameter number. For example, to access Parameter 39 an Instance of 21543 (21504 + 39) is used.
  • Page 93 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...

  • Page 94: Additional Information

    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 Parameter Object for more information. The Instance value is “17447” to access Parameter 39 - [Accel Time 1].

  • Page 95: Troubleshooting

    Chapter Troubleshooting Chapter 8 contains troubleshooting information. Topic Page Topic Page Locating the Status Indicators Module Diagnostic Items in Single Drive Mode PORT Status Indicator Module Diagnostic Items in Multi-Drive Mode MOD Status Indicator Viewing and Clearing Events Net A Status Indicator Locating the Status Indicators The DeviceNet adapter has three status indicators.

  • Page 96: Port Status Indicator

    Troubleshooting PORT Status Indicator Status Cause Corrective Action • Securely connect the adapter to the drive The adapter is not powered or is not connected properly to using the ribbon cable. the drive. • Apply power to the drive. • Clear any drive faults. Flashing The adapter is not receiving communication from the drive,...

  • Page 97: Mod Status Indicator

    Troubleshooting MOD Status Indicator Status Cause Corrective Action • Securely connect the adapter to the drive The adapter is not powered. using the ribbon cable. • Apply power to the drive. • Clear faults in the drive. Flashing The adapter has failed the firmware test, connected drive •...

  • Page 98: Net A Status Indicator

    Troubleshooting Net A Status Indicator Status Cause Corrective Actions • Securely connect the adapter to the drive The adapter and/or 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.

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

    Troubleshooting Module Diagnostic Items in Multi-Drive Mode The following diagnostic items can be accessed using DriveExplorer (version 3.01 or higher). No. Name Description Field Flash Cnt The number of flash updates made to the adapter after shipping. Adapter Events The number of events in the event queue. Drv 0 Reference Reference being transmitted from the adapter to DSI drive 0.

  • Page 100: Viewing And Clearing Events

    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.2 DriveExplorer Event View/Clear Screen...
  • Page 101 Troubleshooting 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 Event Description No Event Text displayed in an empty event queue entry.
  • Page 102 Troubleshooting Notes:...

  • Page 103: Specifications

    Appendix Specifications This chapter present the specifications for the adapter. Topic Page Topic Page Communications Environmental Electrical Regulatory Compliance A-2 Mechanical Communications Network Protocol DeviceNet Data Rates 125K, 250K, 500K, Autobaud Drive Protocol Electrical Consumption Drive 150 mA at 5V supplied through the drive Network 60 mA at 24V supplied through DeviceNet Use the 60 mA value to size the network current draw...

  • Page 104: Environmental

    Specifications Environmental Temperature Operating -10 to +50 °C (14 to 149 °F) Storage -40 to +85 °C (-40 to +185 °F) Relative Humidity -5 to 95% non-condensing Regulatory Compliance Certification Specification UL508C CAN / CSA C22.2 No. 14-M91 EN50178 and EN61800-3...

  • Page 105: About Parameter Numbers

    Appendix Adapter Parameters Appendix B provides information about the DeviceNet adapter parameters. Topic Page About Parameter Numbers B-1 Parameter List About Parameter Numbers The parameters in the adapter are numbered consecutively. However, depending on which configuration tool you use, they may have different numbers.
  • Page 106 Adapter Parameters Parameter No. Name and Description Details [DN Rate Cfg] Default: 3 = Autobaud Sets the DeviceNet data rate after a reset or Values: 0 = 125 kbps power cycle. 1 = 250 kbps 2 = 500 kbps This setting is used when all of the adapter DIP 3 = Autobaud switches are in the CLOSED position (all 0’s).
  • Page 107 Adapter Parameters Parameter No. Name and Description Details [DN Act Cfg] Default: 0 = Switches Displays the source from which the adapter node Values: 0 = Switches address and data rate are taken. This will either be 1 = EEPROM switches or parameters in EEPROM.
  • Page 108 Adapter Parameters Parameter No. Name and Description Details [DSI I/O Cfg] Default: 0001 Sets the configuration of the Drives that are active Values: 0 = Drive 0 in the Multi-Drive mode. Identifies the connections 1 = Drives 0-1 that would be attempted on a reset or power cycle. 2 = Drives 0-2 3 = Drives 0-3 4 = Drives 0-4...

  • Page 109: Devicenet Objects

    Appendix 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 Using Explicit Messaging. Object Class Code Page Hex.

  • Page 110: Identity Object

    DeviceNet Objects Identity Object Class Code Hexadecimal Decimal 0x01 Instances (Single-Drive Mode) The number of instances is fixed at three and is as shown below: Instance 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 Description Class...
  • Page 111 DeviceNet Objects Identity Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Vendor ID UINT 1 = Allen-Bradley Device Type UINT Product Code UINT Unique number identifying the product name and rating Revision Struct of Product Revision: USINT Major USINT Minor...

  • Page 112: Connection Object

    DeviceNet Objects Connection Object Class Code Hexadecimal Decimal 0x05 Instances Instance Description Master-Slave Explicit Message Connection Polled I/O Connection Change of State/Cyclic Connection 6 – 10 Explicit Message Connection Instance Attributes Refer to the DeviceNet Specification for more information. Attribute Access Name Data Type...
  • Page 113 DeviceNet Objects Connection Object (Continued) Instance Attributes (Continued) Refer to the DeviceNet Specification for more information. Attribute Access Name Data Type Description Rule Produced Path UINT Number of bytes of data in the Length produced connection path Produced ARRAY of Byte stream which defines Connection Path UINT...

  • Page 114: Register Object

    DeviceNet Objects Register Object Class Code Hexadecimal Decimal 0x07 Instances The number of instances is fixed at thirteen and is as shown below: Instance 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)
  • Page 115 DeviceNet Objects Register Object (Continued) Class Attributes Not supported. Instance Attributes Attribute Access Rule Name Data Type Description Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data. 0 = good 1 = bad Direction BOOL Direction of data transfer...

  • Page 116: Parameter Object

    DeviceNet Objects Parameter Object Class Code Hexadecimal Decimal 0x0F Instances (Single-Drive Mode) The number of instances is as shown below: Instance Description Class Drive Parameter 1 " " Drive Parameter n n + 1 Adapter Parameter 1 " " n + 21 Adapter Parameter 21 Instances (Multi-Drive Mode) The number of instances is fixed at 21 and is as shown below:...
  • Page 117 DeviceNet Objects Parameter Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Parameter Value Link Path Size USINT 0 = No link specified n = Link specified Link Path Descriptor WORD 0 = False, 1 = True Bit 1 = Supports ENUMs Bit 2 = Supports scaling Bit 3 = Supports scaling links Bit 4 = Read only...
  • Page 118 C-10 DeviceNet Objects Parameter Object (Continued) Services Service Code Implemented for: Service Name Class Instance 0x01 Get_Attribute_All 0x05 Reset 0x0E Get_Attribute_Single 0x10 Set_Attribute_Single 0x4B Get_Enum_String...

  • Page 119: Parameter Group Object

    DeviceNet Objects C-11 Parameter Group Object Class Code Hexadecimal Decimal 0x10 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.
  • Page 120 C-12 DeviceNet Objects Parameter Group Object (Continued) Instance Attributes Attribute Access Name Data Description Rule Type Group Name String SHORT_ Group name STRING Number of Members UINT Number of parameters in group. in Group 1st Parameter UINT Number in Group 2nd Parameter UINT Number in Group...

  • Page 121: Pccc Object

    DeviceNet Objects C-13 PCCC Object Class Code Hexadecimal Decimal 0x67 Instances Not supported Class Attributes Not supported. Instance Attributes Not supported. Services Service Code Implemented for: Service Name Class Instance 0x4B Execute_PCCC 0x4D Execute_Local_PCCC...
  • Page 122 C-14 DeviceNet Objects PCCC Object (Continued) Message Structure for Execute_PCCC Request Response Name Data Description Name Data Description Type Type Length USINT Length of Length USINT Length of requestor ID requestor ID Vendor UINT Vendor number Vendor UINT Vendor number of requestor of requestor Serial UDINT ASA serial...

  • Page 123: Logic Command/Status Words

    Appendix 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. PowerFlex 4 and PowerFlex 40 Drives Logic Command Word Logic Bits...
  • Page 124 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 Description x Ready 0 = Not Ready 1 = Ready Active 0 = Not Active 1 = Active...

  • Page 125: Glossary

    Glossary 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.
  • Page 126 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.
  • Page 127 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.
  • Page 128 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.
  • Page 129 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). 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.
  • Page 130 Glossary-6 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.”...
  • Page 131 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.
  • Page 132 Glossary-8 UCMM (UnConnected Message Manager) UCMM provides a method to create connections between DeviceNet devices. 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.

  • Page 133: Index

    Index Numerics bus off, G-1 10-pin linear plug, 2-4 5-pin linear plug, 2-4 cables DeviceNet, 2-4 DSI Internal Interface, 2-5 adapter catalog number, 1-1 adding to the scan list, 4-2 Change of State (COS) applying power, 2-7 configuring a scanner for, 4-4 commissioning, 2-1 configuring an adapter for, 3-8 compatible products, 1-3...
  • Page 134 Index-2 COS, refer to Change of State DriveTools accessing parameters with, 3-1 COS/Cyc Interval parameter, B-3 definition, G-4 Cyclic supported feature, 1-2 configuring a scanner for, 4-4 Drv 0 - 4 Addr parameters, B-4 configuring an adapter for, 3-8 definition, G-2 connector on adapter, 1-1 data rate, 3-12 definition, G-3...
  • Page 135 Index-3 fault action configuring an adapter, 3-10 about, 5-1 definition, G-4 configuring an adapter for, 3-8 configuring scanner for, 4-4 fault configuration definition, G-5 configuring an adapter for, 3-10 examples, 5-3, 7-6 definition, G-4 image, 5-2, 7-4 faulted node recovery input, 4-5 definition, G-4 mapping in the scanner, 4-5...
  • Page 136 Index-4 mechanical dimensions, A-1 messages, refer to Explicit Messages Parameter Group object, C-11 MOD status indicator Parameter object, C-8 locating, 8-1 parameters troubleshooting with, 8-3 accessing, 3-1 modes of operation, 1-6 active configuration, 3-12 mounting the adapter, 2-5 to 2-6 convention, P-2 editing with RSNetWorx, 3-6 Multi-Drive mode...
  • Page 137 Index-5 example program for Explicit reference/feedback Messages, 6-13 definition, G-7 example program for I/O, 5-9 in I/O image, 5-2, 7-4 formatting Explicit Messages, 6-4 using, 5-3 specifications Register object, C-6 adapter, A-1 regulatory compliance, A-1 DeviceNet, G-3 related documentation, P-1 status indicators Reset Module parameter, B-2 definition, G-7...
  • Page 138 Index-6...
  • Page 140 Publication 22COMM-UM003A-EN-P – January, 2003 P/N 308269-P01 Copyright 2003 Rockwell International Corporation. All rights reserved. Printed in USA.

Table of Contents