Allen-Bradley PowerFlex 20-COMM-D User Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Adapter
  5. PowerFlex 20-COMM-D
  6. User manual

Allen-Bradley PowerFlex 20-COMM-D User Manual

Devicenet adapter
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DeviceNet
Adapter
20-COMM-D
FRN 1.xxx
User Manual

Advertisement

Table of Contents
loading

Related Manuals for Allen-Bradley PowerFlex 20-COMM-D

Summary of Contents for Allen-Bradley PowerFlex 20-COMM-D

  • Page 1 DeviceNet Adapter 20-COMM-D FRN 1.xxx User Manual...
  • Page 2 In no event will the Allen-Bradley Company be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes.

  • Page 3: Table Of Contents

    Table of Contents Preface About This Manual Related Documentation ......P-1 Conventions Used in this Manual ..... P-2 Rockwell Automation Support.
  • Page 4 Table of Contents Chapter 5 Using I/O Messaging About I/O Messaging ....... 5-1 Understanding the I/O Image .
  • Page 5 Table of Contents Appendix C DeviceNet Objects Identity Object ........C-2 Connection Object .
  • Page 6 Table of Contents Notes:...

  • Page 7: 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 Installation Manual DeviceNet...

  • Page 8: Conventions Used In This Manual

    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 xxx - [*]. The xxx represents the parameter number. The * represents the parameter name. For example Parameter 01 - [DPI Port]. •...

  • Page 9: Getting Started

    Chapter Getting Started The 20-COMM-D DeviceNet adapter is an embedded communication option for any one drive in the PowerFlex family. It can also be used with other Allen-Bradley products implementing DPI™, a functional enhancement to SCANport™. Topic Page Topic Page...

  • Page 10: Features

    Getting Started Features The DeviceNet adapter features the following: • The adapter is mounted in the PowerFlex 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 11: Compatible Products

    Getting Started Compatible Products The DeviceNet adapter is compatible with Allen-Bradley PowerFlex drives and other products that support DPI. DPI is a second generation peripheral communication interface. It is a functional enhancement to SCANport. At the time of publication, compatible products include: •...

  • Page 12: Safety Precautions

    Getting Started Safety Precautions Please read the following safety precautions carefully ATTENTION: Risk of injury or equipment damage exists. Only personnel familiar with drive and power products and the associated machinery should plan or implement the installation, start-up, configuration, and subsequent maintenance of the product using a DeviceNet adapter.

  • Page 13: 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 14: Modes Of Operation

    Getting Started Modes of Operation The adapter uses three status indicators to report its operating status. They can be viewed on the adapter or through the drive cover. See Figure 1.2. Figure 1.2 Status Indicators (location on drive may vary) –...

  • Page 15: Installing The Adapter

    Chapter Installing the Adapter Chapter 2 provides instructions for installing the adapter on a PowerFlex 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 16 Installing the Adapter 1. Set the node address switches. Figure 2.1 Setting the Node Address Ones Tens Digit Digit Setting Description 0-63 Node address used by the adapter if switches are enabled. The default switch setting is 63. Node address 63 is also the default address used by all uncommissioned devices.

  • Page 17: 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 power from the drive, and then verify power has been discharged before installing or removing an adapter.

  • Page 18: Connecting The Adapter To The Drive

    Installing the Adapter Connecting the Adapter to the Drive 1. Remove power from the drive and network. 2. Use static control precautions. 3. Connect the Internal Interface cable to the DPI port on the drive and then to DPI connector on the adapter. Figure 2.4 DPI Ports and Internal Interface Cables –...
  • Page 19 Installing the Adapter 4. Mount the adapter on the drive, using the four captive screws to secure it in place and ground it to the drive. Important: On a PowerFlex 700 drive, tighten the screw in the lower left hole to ground the adapter. On a PowerFlex 70 drive, tighten the screw in the lower right hole to ground the adapter.

  • Page 20: 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 21: 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 Selecting Master-Slave or Peer-to-Peer 3-8 Using the PowerFlex HIM Selecting COS, Cyclic, or Polled I/O 3-14 Using RSNetWorx for DeviceNet 3-3 Setting a Fault Action 3-16 Setting the Node Address...

  • Page 22: Using The Powerflex Him

    Configuring the Adapter Using the PowerFlex HIM If your drive has either an LED or LCD HIM (Human Interface Module), access parameters in the adapter as shown below. It is recommended that you read through the steps for your HIM before performing the sequence.

  • Page 23: 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 24 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 (node 63 in Figure 3.2) if RSNetWorx for DeviceNet does not have an EDS file for it. Step Icons 1.
  • Page 25 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 26 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. In Figure 3.4, for example, the drive has 387 parameters, so parameter 388 is the first adapter parameter.

  • Page 27: Setting The Node Address

    Configuring the Adapter Setting the Node Address If the adapter Data Rate switch is set to “PGM,” the value of Parameter 03 - [DN Addr Cfg] determines the node address. We recommend that you do not use node address 63 because all new devices use it as the default address.

  • Page 28: Setting The I/O Configuration

    Configuring the Adapter Setting the I/O Configuration The I/O configuration determines the type of data sent to the drive. Logic Command/Status, Reference/Feedback, and Datalinks may be enabled or disabled. A “1” enables the I/O. A “0” disables it. 1. Set the bits in Parameter 13 - [DPI I/O Config]: Figure 3.7 I/O Configuration Screen on an LCD HIM Description Port 5 Device...
  • Page 29 Configuring the Adapter To set a Master-Slave hierarchy 1. Enable the desired I/O in Parameter 13 - [DPI I/O Config]. Refer to Figure 3.7. 2. Set the bits in the Parameter 25 - [M-S Input]. This parameter determines the data transmitted from the scanner to the drive. A “1” enables the I/O.
  • Page 30 3-10 Configuring the Adapter To set an adapter to transmit Peer-to-Peer data 1. Verify that Parameter 41 - [Peer Out Enable] is set to Off. This parameter must be set to Off while you configure some of the peer output parameters. Figure 3.10 Peer Out Enable Screen on an LCD HIM Value Setting Port 5 Device...
  • Page 31 Configuring the Adapter 3-11 4. Set Parameters 42 - [Peer Out Time] and 43 - [Peer Out Skip] to establish the minimum and maximum intervals between Peer messages. The minimum interval is set in Parameter 42 - [Peer Out Time]. The maximum interval is the value of Parameter 42 - [Peer Out Time] multiplied by the value of Parameter 43 - [Peer Out Skip].
  • Page 32 3-12 Configuring the Adapter 3. Select the destination of the data that is input to the drive in Parameter 30 - [Peer A Input]. Figure 3.16 Peer A Input Screen on an LCD HIM Value Description Port 5 Device Off (Default) 20-COMM-D Logic Command/Reference Parameter #: 30...
  • Page 33 Configuring the Adapter 3-13 6. If you are receiving a Reference, set the scale in Parameter 33 - [Peer Ref Adjust]. It can be scaled between 0.00 and 199.99%. ATTENTION: To guard against equipment damage and/or personal injury, note that changes to Parameter 33 - [Peer Ref Adjust] take effect immediately.

  • Page 34: Selecting Cos, Cyclic, Or Polled I/O

    3-14 Configuring the Adapter 8. Parameter 34 - [Peer Flt Action] sets the action that the adapter will take if it times out. ATTENTION: Risk of injury or equipment damage exists. Parameter 34 - [Peer Flt Action] lets you determine the action of the adapter and connected drive if communications are disrupted.
  • Page 35 Configuring the Adapter 3-15 To use COS (Change of State) data exchange 1. Set bit 0 (the Logic Command/Reference bit) in Parameter 13 - [DPI I/O Config] to 1 (enabled) and bit 0 (the Logic Status/ Feedback bit) in Parameter 26 - [M-S Output] to 1 (enabled). Changes to bits in the Logic Status or Feedback trigger messages in COS data exchange.

  • Page 36: Setting A Fault Action

    3-16 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 10 - [Comm Flt Action] and a different response to an idle scanner using Parameter 11 - [Idle Flt Action].

  • Page 37: Resetting The Adapter

    Configuring the Adapter 3-17 To set the fault configuration parameters If you set Parameter 10 - [Comm Flt Action], 11 - [Idle Flt Action], or 34 - [Peer 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.

  • Page 38: Viewing The Adapter Configuration

    3-18 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 DPI Port The port on the drive to which the adapter is connected. Usually, it is port 5.

  • Page 39: 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 40: 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 41 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.
  • Page 42 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 Rx Size and Tx Size boxes.

  • Page 43: Mapping The Drive Data In The Scanner

    Configuring the Scanner Table 4.A Host Products using 16-bit Reference/Feedback & Datalinks Datalinks (16-bit) Logic Command/ Reference/ Size Size Status Feedback (16-bit) ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔...
  • Page 44 Configuring the Scanner Mapping the Input I/O 1. In the Scanner Module dialog box, click the Input tab. (If necessary, right-click the scanner in the configuration view (Figure 4.2) to display this dialog box.) Figure 4.5 Input Page on the Scanner Module Dialog Box If you selected the Automap on Add box in the Scanlist page (Figure 4.3), RSNetWorx has already mapped the I/O.
  • Page 45 Configuring the Scanner Mapping the Output I/O 1. In the Scanner Module dialog box, click the Output tab. To display this dialog box, right-click the scanner in the configuration view (Figure 4.2). Figure 4.6 Output Page on the Scanner Module Dialog Box If you selected the Automap on Add box in the Scanlist page (Figure 4.3), RSNetWorx has already mapped the I/O.

  • Page 46: Saving The Configuration

    Configuring the Scanner Saving the Configuration After configuring a scanner, you must download it to the scanner. You should also save it to a file on your computer. 1. In the Scanner Module dialog box (Figure 4.6), click Apply to save the configuration to the scanner.

  • Page 47: About I/O Messaging

    Chapter Using I/O Messaging Chapter 5 provides information and examples that explain how to use I/O Messaging to control a PowerFlex drive. Topic Page Topic Page About I/O Messaging Example Ladder Logic Programs 5-6 Understanding the I/O Image ControlLogix Example Using Logic Command/Status PLC-5 Example Using Reference/Feedback...

  • Page 48: 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 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 49 Using I/O Messaging An image that uses 32-bit words for Reference and Datalinks would change the I/O image in Figure 5.1 as follows: Word Word Logic Command/Status 8 - 11 Datalink B Pad Word 12 - 15 Datalink C 2 - 3 Reference/Feedback 16 - 19 Datalink D...

  • Page 50: Using Logic Command/Status

    Using I/O Messaging Using Logic Command/Status When enabled, the Logic Command/Status word is always word 0 in the I/O image. The Logic Command is a 16-bit word of control produced by the scanner and consumed by the adapter. The Logic Status is a 16-bit word of status produced by the adapter and consumed by the scanner.
  • Page 51 Using I/O Messaging 32-Bit Parameters using 16-Bit Datalinks To read (and/or write) a 32-bit parameter using 16-bit Datalinks, typically both Datalinks (A,B,C,D) are set to the 32-bit parameter. For example, to read Parameter 09 - [Elapsed MWh], both Datalink A1 and A2 are set to “9.”...

  • Page 52: Example Ladder Logic Programs

    Using I/O Messaging Example Ladder Logic Programs These example ladder logic programs (Figure 5.4 – Figure 5.7) work with PowerFlex 70 or PowerFlex 700 drives. Functions of the Example Programs The example programs use an operator station wired to an I/O module in Slot 0, Module Group 0, Rack 0.

  • Page 53: Controllogix Example

    Using I/O Messaging ControlLogix Example Figure 5.3 Tags for the Example Program Tag Name Type Tag Name Type Local:1:I DINT[] DriveFeedback Local:1:O DINT[] DriveInputImage INT[2] DriveCommandClearFault BOOL DriveOutputImage INT[2] DriveCommandJog BOOL DriveReference DriveCommandStart BOOL DriveStatusFaulted BOOL DriveCommandStop BOOL DriveStatusRunning BOOL Figure 5.4 Example ControlLogix Ladder Logic Program This rung enables the DeviceNet scanner.
  • Page 54 Using I/O Messaging Figure 5.4 Example ControlLogix Ladder Logic Program (Continued) DriveCommandClearFault DriveOutputImage[0].3 This rung transfers the reference tag to the drive’s output image. Copy File Source DriveReference Dest DriveOutputImage[1] Length This rung copies the output image into the 32-bit DeviceNet scanner output structure.

  • Page 55: Plc-5 Example

    Using I/O Messaging PLC-5 Example Figure 5.5 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.6 Example PLC-5 Ladder Logic Program The scanner gathers drive status data via the DeviceNet network.
  • Page 56 5-10 Using I/O Messaging Figure 5.6 Example PLC-5 Ladder Logic Program (Continued) Operator Input PowerFlex 70 Drive Stop STOP Command Bit Command Bit I:000 N10:1 0006 Operator Input PowerFlex 70 Drive Jog Command Bit Command Bit I:000 N10:1 0007 PowerFlex 70 Operator Input CLEAR FAULT Drive Clear Faults...

  • Page 57: Slc Example

    Using I/O Messaging 5-11 SLC Example Figure 5.7 Example SLC Ladder Logic Program The scanner gathers drive status data via the DeviceNet network. The M-File is copied into the N9 data file in the SLC to move the drive status information to a convenient location. CO P 0000 Copy File...
  • Page 58 5-12 Using I/O Messaging Figure 5.7 Example SLC Ladder Logic Program (Continued) PowerFlex 70 Operator Input CLEAR FAULTS Drive Clear Faults 0007 Command Bit Command Bit N10:0 I:2.0 1746-I*16 PowerFlex 70 REFERENCE Command Word 0008 Move Source N21:0 0< Dest N10:1 0<...

  • Page 59: Using Explicit Messaging

    Chapter Using Explicit Messaging Chapter 6 provides information and examples that explain how to use Explicit Messaging to monitor and configure the adapter and connected PowerFlex drive. Topic Page Topic Page About Explicit Messaging ControlLogix Example Formatting Explicit Messages PLC-5 Example 6-10 Running Explicit Messages SLC Example...

  • Page 60: 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 61 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 Description – Message Type The message type must be CIP Generic. —...
  • Page 62 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 63 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 64 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 65: 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 66: 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 Value Description...
  • Page 67 Using Explicit Messaging Configuration Value Description Refer to . . . Service Code 10 (hex) Set_Attribute_Single C-10 Object Type f (hex) Parameter Object Object ID 101 (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 68: Plc-5 Example

    6-10 Using Explicit Messaging 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. Request Data for Read of Drive Parameter 101 Address Value (hex) Description Refer to .
  • Page 69 Using Explicit Messaging 6-11 Ladder Logic Program Figure 6.7 Example PLC-5 Ladder Logic Program When I:000/17 is set to true, a one-time Block Transfer Write sends data to the scanner. The Move instruction then initializes the first word of the data file that is used by the Block Transfer Read instruction in the next rung.

  • Page 70: Slc Example

    6-12 Using Explicit Messaging 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. Request Data for Read of Drive Parameter 101 Address Value (hex) Description Refer to .
  • Page 71 Using Explicit Messaging 6-13 Program Important: To originate a scanner transaction, use a copy operation to M0:[slot number]:224. Then, use a copy operation to read M1:1.224 for the result. If more than one message is enabled, use the TXID to determine which message you are reading.
  • Page 72 6-14 Using Explicit Messaging Notes:...

  • Page 73: Troubleshooting

    Chapter Troubleshooting Chapter 7 contains troubleshooting information. Topic Page Topic Page Locating the Status Indicators Net A Status Indicator PORT Status Indicator Module Diagnostic Items MOD Status Indicator Viewing and Clearing Events Locating the Status Indicators The DeviceNet adapter has three status indicators. They can be viewed on the adapter or through the drive cover.

  • Page 74: Port Status Indicator

    • Orange The adapter is connected to a Connect the adapter to a product that product that does not support supports Allen-Bradley DPI Allen-Bradley DPI communications (for example, PowerFlex communications. drives). • Flashing The adapter is establishing an No Action.

  • Page 75: Mod Status Indicator

    Troubleshooting MOD Status Indicator Status Cause Corrective Action • The adapter is not Securely connect the adapter to the drive powered. using the ribbon cable. • Apply power to the drive. • Flashing The adapter has failed the Verify that node address switch setting is firmware test or the node between 0 and 63.

  • Page 76: Net A Status Indicator

    Troubleshooting Net A Status Indicator Status 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. •...

  • Page 77: Module Diagnostic Items

    Troubleshooting Module Diagnostic Items The following diagnostic items can be accessed using DriveExplorer (version 2.01 or higher). No. Name Description Common Logic Current value of the Common Logic Command being transmitted to the host by this peripheral. Prod Logic Cmd Current value of the Product Specific Logic Command being transmitted to the host by this peripheral.

  • Page 78: Viewing And Clearing Events

    Troubleshooting No. Name Description DN Image Size Size of I/O image on DeviceNet Network. Data Rate SW Current value of data rate switch. Node Address Current value of node address switches. Viewing and Clearing Events The adapter maintains an event queue that reports the history of its actions.
  • Page 79 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...
  • Page 80 Troubleshooting Code Event Description Bad I/O A DeviceNet I/O fragment was received out of sequence. Fragment Possible line noise problem. Idle I/O The DeviceNet scanner was placed in program mode. Message Peer I/O The adapter has not received Peer I/O from another device on Timeout the network within the specified time-out interval.

  • Page 81: Communications

    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, PGM The PGM (Program) setting on the switch is used to set the data rate using the adapter parameter.

  • Page 82: 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 508C and CUL EN61800-3...

  • Page 83: Adapter Parameters

    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 84 Adapter Parameters Parameter No. Name and Description Details [DN Addr Actual] Default: DeviceNet node address actually used by the Minimum: adapter. Maximum: Type: Read Only [DN Rate Cfg] Default: 3 = Autobaud DeviceNet data rate if the data rate switch is set to Values: 0 = 125 kbps “PGM”...

  • Page 85: Cmd/Ref

    Adapter Parameters Parameter No. Name and Description Details [Idle Flt Action] Default: 0 = Fault Sets the action that the adapter and drive take if Values: 0 = Fault the adapter detects that scanner is idle because 1 = Stop the controller was switched to program mode.

  • Page 86: Master-Slave Input

    Adapter Parameters Parameter No. Name and Description Details [Flt Cfg Logic] Default: 0000 0000 0000 0000 Sets the Logic Command data that is sent to the Minimum: 0000 0000 0000 0000 drive if any of the following is true: Maximum: 1111 1111 1111 1111 •...
  • Page 87 Adapter Parameters Parameter No. Name and Description Details [M-S Output] Default: xxx0 0001 Master-Slave output data. This data is produced Bit Values: 0 = I/O disabled by the adapter and consumed by the scanner. 1 = I/O enabled Type: Read/Write Reset Required: Bit Definitions 0 = Status/Fdbk...
  • Page 88 Adapter Parameters Parameter No. Name and Description Details [Peer Cmd Mask] Default: 0000 0000 0000 0000 Mask that is used for the Logic Command word Minimum: 0 = Ignore bit when it is received through peer input. If the mask 1 = Use bit bit is 0 (Off), the command bit is ignored and not Type:...
  • Page 89 Adapter Parameters Parameter No. Name and Description Details [Peer Inp Status] Default: 0 = Off Status of the consumed peer input connection. Values: 0 = Off 1 = Waiting 2 = Running 3 = Faulted Type: Read Only [Peer A Output] Default: 0 = Off [Peer B Output]...
  • Page 90 Adapter Parameters Notes:...
  • Page 91 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 92: Devicenet Objects

    Max Instance UINT Total number of instances Instance Attributes Attribute Access Name Data Type Description Rule Vendor ID UINT 1 = Allen-Bradley Device Type UINT Product Code UINT Number identifying product name and rating Revision: STRUCT of Major USINT Value varies...
  • Page 93 DeviceNet Objects Identity Object (Continued) Services Service Code Implemented for: Service Name Class Instance 0x05 Reset 0x0E Get_Attribute_Single 0x11 Find_Next_Obj_Instance...

  • Page 94: 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...
  • Page 95 DeviceNet Objects Connection Object (Continued) Instance Attributes (Continued) Refer to the DeviceNet Specification for more information. Attribute Access Name Data Description Rule Type Get/Set Watchdog USINT 0 = Transition to timed out Action 1 = Auto delete 2 = Auto reset Produced Path UINT Number of bytes of data in the produced...

  • Page 96: Register Object

    DeviceNet Objects Register Object Class Code Hexadecimal Decimal 0x07 Instances Instance Description All polled data being read from the DPI device (read-only) All polled data written to the DPI device (read/write) Logic Status and Feedback data (read-only) Logic Command and Reference data (read/write) Datalink A (input data from device to scanner) (read only) Datalink A (output data from scanner to device) (read/write) Datalink B (input data from device to scanner) (read only)
  • Page 97 DeviceNet Objects Register Object (Continued) 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 0 = Producer Register 1 = Consumer Register...

  • Page 98: Parameter Object

    DeviceNet Objects Parameter Object Class Code Hexadecimal Decimal 0x0F Instances The number of instances depends on the number of parameters in the DPI drive. The adapter parameters are appended to the list of drive parameters. The total number of parameters can be read in Instance 0, Attribute 2 Instance Description...
  • Page 99 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 100 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 0x15 Restore_Request 0x16 Save_Request 0x4B Get_Enum_String...

  • Page 101: Parameter Group Object

    DeviceNet Objects C-11 Parameter Group Object Class Code Hexadecimal Decimal 0x10 Instances The number of instances depends on the number of groups in the device. A group of adapter parameters is appended to the list of groups in the device. The total number of groups can be read in Instance 0, Attribute 2. Number Description Class Attributes...
  • Page 102 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 Number UINT in Group 2nd Parameter UINT Number in Group...

  • Page 103: 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 104 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 105: Dpi Device Object

    DeviceNet Objects C-15 DPI Device Object Class Code Hexadecimal Decimal 0x92 Instances The number of instances depends on the number of components in the device. The total number of components can be read in Instance 0, Attribute 4. Number Description Class Attributes (Drive) Drive Component 1 Drive Component 2...
  • Page 106 BYTE Identification of variations. Code Configuration Text STRING[16] Text identifying a variation of a family device. Brand Code WORD 0x0001 = Allen-Bradley NVS Checksum WORD Checksum of the Non-Volatile Storage in a device. Class Revision WORD 2 = DPI Character Set...
  • Page 107 DeviceNet Objects C-17 DPI Device Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Component STRING[32] Name of the component Name Component STRUCT of Firmware BYTE Major Revision Revision BYTE Minor Revision Component BYTE 0 = Not Available Hardware Change Number First Flash Object...

  • Page 108: Dpi Parameter Object

    C-18 DeviceNet Objects DPI Parameter Object Class Code Hexadecimal Decimal 0x93 Instances The number of instances depends on the number of parameters in the device. The total number of parameters can be read in Instance 0, Attribute 0. Number Description Class Attributes (Drive) Drive Parameter 1 Attributes Drive Parameter 2 Attributes...
  • Page 109 DeviceNet Objects C-19 DPI Parameter Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule DPI Online Read STRUCT of Full BOOL[32] Descriptor (Refer to pages C-20 – C-21) CONTAINER Parameter value CONTAINER Minimum value CONTAINER Maximum value CONTAINER Default value WORD Next parameter...
  • Page 110 C-20 DeviceNet Objects DPI Parameter Object (Continued) Descriptor Attributes Name Description Data Type (Bit 1) Right bit is least significant bit (0). 000 = BYTE used as an array of Boolean 001 = WORD used as an array of Boolean 010 = BYTE (8-bit integer) Data Type (Bit 2) 011 = WORD (16-bit integer)
  • Page 111 DeviceNet Objects C-21 DPI Parameter Object (Continued) Descriptor Attributes Name Description Parameter Exists Reserved Not Used Reserved Formula Links Reserved Access Level (Bit 1) Reserved Access Level (BIt 2) Reserved Access Level (Bit 3) Reserved Writable ENUM Reserved Not a Link Source 0 = Parameter can be a source for a link 1 = Parameter cannot be a source for a link Enhanced Bit ENUM...
  • Page 112 C-22 DeviceNet Objects DPI Parameter Object (Continued) Format for Get_Attributes_Scattered Service The structure shown below can get up to eight parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated parameter value field actually contains an error code.
  • Page 113 DeviceNet Objects C-23 DPI Parameter Object (Continued) The PLC data in this example is for a Get_Attributes_Scattered of PowerFlex 70 parameters; 1 - [Output Freq], 3 - [Output Current] and 6 - [Output Voltage] from a device at node address 1. Request Data for Get_Attributes_Scattered Address Value (hex) Description Refer to .
  • Page 114 C-24 DeviceNet Objects DPI Parameter Object (Continued) Format for Set_Attributes_Scattered Service The structure shown below can get up to eight parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated pad word field contains an error code. Request Response Word 0...
  • Page 115 DeviceNet Objects C-25 DPI Parameter Object (Continued) The PLC data in this example is for a Set_Attributes_Scattered of PowerFlex 70 parameters; 140 - [Accel Time 1], 142 - [Decel Time 1] and 100 - [Jog Speed] to a device at node address 1. Request Data for Set_Attributes_Scattered Address Value (hex) Description Refer to .

  • Page 116: Dpi Fault Object

    C-26 DeviceNet Objects DPI Fault Object Class Code Hexadecimal Decimal 0x97 Products such as PowerFlex drives use this object for faults. Adapters use this object for events. Instances The number of instances depends on the maximum number of faults or events supported in the queue.
  • Page 117 DeviceNet Objects C-27 DPI Fault Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Full/All STRUCT of Information WORD Fault code STRUCT of Fault source BYTE DPI port BYTE DPI Device Object STRING[16] Fault text STRUCT of Fault time stamp LWORD Timer value (0 = Timer not supported) BOOL[16]...

  • Page 118: Dpi Alarm Object

    C-28 DeviceNet Objects DPI Alarm Object Class Code Hexadecimal Decimal 0x98 Products such as PowerFlex drives use this object for alarms or warnings. Adapters do not support this object. Instances The number of instances depends on the maximum number of alarms supported by the queue.
  • Page 119 DeviceNet Objects C-29 DPI Alarm Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Full/All STRUCT of Information WORD Alarm code STRUCT of Alarm source BYTE DPI port BYTE DPI Device Object STRING[16] Alarm text STRUCT of Alarm time stamp LWORD Timer value (0 = Timer not supported) BOOL[16]...

  • Page 120: Dpi Time Object

    C-30 DeviceNet Objects DPI Time Object Class Code Hexadecimal Decimal 0x9B Instances The number of instances depends on the number of timers in the device. Instance 1 is always reserved for a real time clock although a device may not support it. The total number of timers can be read in Instance 0, Attribute 2.
  • Page 121 DeviceNet Objects C-31 DPI Time Object (Continued) Instance Attributes Attribute Access Name Data Type Description Rule Read Full STRUCT of STRING[16] Name of the timer LWORD or Elapsed time in milliseconds unless timer STRUCT is a real time clock (See attribute 2) BOOL[16] See Attribute 3 Timer Text...
  • Page 122 C-32 DeviceNet Objects Notes:...

  • 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 70 and PowerFlex 700 Drives Logic Command Word Logic Bits...
  • Page 124 Logic Command/Status Words PowerFlex 70 and PowerFlex 700 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: M-S Input Parameter Configurations

    Appendix Master-Slave I/O Configuration Appendix E lists possible configurations for the M-S Input/Output parameters and the possible data size allocation associated with each value depending on the method of data transfer. Topic Page M-S Input Parameter Configurations M-S Output Parameter Configurations M-S Input Parameter Configurations Parameter 25 - [M-S Input] has the following five configurable bits.
  • Page 126 Master-Slave I/O Configuration Table E.A Host Products using 16-bit Reference/Feedback & Datalinks Allocation (Number of Bytes) Data Size sent from the Controller to the Adapter Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic 00000 xxxx0 00001 xxxx0...
  • Page 127 Master-Slave I/O Configuration Allocation (Number of Bytes) Data Size sent from the Controller to the Adapter Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic 01011 xxxx1 12 & 0 12 & 0 01100 xxxx1 8 &...

  • Page 128: Master-Slave I/O Configuration

    Master-Slave I/O Configuration Table E.B Host Products using 32-bit Reference/Feedback & Datalinks Allocation (Number of Bytes) Data Size sent from the Controller to the Adapter Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic 00000 xxxx0 00001 xxxx0...

  • Page 129: M-S Output Parameter Configurations

    Master-Slave I/O Configuration Allocation (Number of Bytes) Data Size sent from the Controller to the Adapter Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic 01011 xxxx1 24 & 0 24 & 0 01100 xxxx1 16 &...
  • Page 130 Master-Slave I/O Configuration Table E.C Host Products using 16-bit Reference/Feedback & Datalinks Allocation (Number of Bytes) Data Size sent from the Adapter to the Controller Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic xxxxx 00000 xxxxx 00010...
  • Page 131 Master-Slave I/O Configuration Table E.D Host Products using 32-bit Reference/Feedback & Datalinks Allocation (Number of Bytes) Data Size sent from the Adapter to the Controller Input Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic xxxxx 00000 xxxxx 00010...
  • Page 132 Master-Slave I/O Configuration Notes:...

  • Page 133: 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 134 Glossary-2 Classes A class is defined by the DeviceNet specification as “a set of objects that all represent the same kind of system component. A class is a generalization of an object. All objects in a class are identical in form and behavior, but may contain different attribute values.”...
  • Page 135 DriveExplorer Software DriveExplorer software is a tool for monitoring and configuring Allen-Bradley products and adapters. It can be run on computers running Microsoft Windows 95, Windows 98, Windows NT (version 4.0 or greater), and Windows CE (version 2.0 or greater) operating systems.
  • Page 136 RSNetWorx for DeviceNet to describe products so that you can easily commission them on a network. EDS files describe a product device type, revision, and configurable parameters. EDS files for many Allen-Bradley products can be found at http://www.ab.com/networks/ eds. Explicit Messaging Explicit Messages are used to configure, monitor, and diagnose devices...
  • Page 137 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 138 Glossary-6 Master-Slave Hierarchy An adapter configured for a master-slave hierarchy exchanges data with the master device. Usually, a network has one scanner which is the master device, and all other devices (for example, drives connected to DeviceNet adapters) are slave devices. On a network with multiple scanners (called a multimaster hierarchy), each slave device must have a scanner specified as its master.
  • Page 139 Logic Status of the connected PowerFlex drive. PowerFlex Drives The Allen-Bradley PowerFlex family of drives include the PowerFlex 70 and PowerFlex 700. These drives can be used for applications ranging from 0.37 kW (0.5 HP) to 3,000 kW (4,000 HP). All PowerFlex drives implement DPI, allowing them to use the 20COMM-D DeviceNet adapter.
  • Page 140 Type 0/Type 1/Type 2 Control When transmitting I/O, the adapter can use different types of messages for control. The Type 0, Type 1, and Type 2 events help Allen-Bradley personnel identify the type of messages that an adapter is using.

  • Page 141: Index

    Index Numerics 10-pin linear plug, 2-3 cables DeviceNet, 2-3 5-pin linear plug, 2-3 DPI Internal Interface, 2-4 catalog number, 1-1 Change of State (COS) adapter configuring a scanner for, 4-4 adding to the scan list, 4-2 configuring an adapter for, 3-14 applying power, 2-6 definition, G-1 commissioning, 2-1...
  • Page 142 Index-2 Cyclic configuring a scanner for, 4-4 connector on adapter, 1-1 configuring an adapter for, 3-14 data rate, 3-18 definition, G-2 definition, G-3 Internal Interface cable, 2-4 peripheral, G-3 products, G-3 data exchange DPI Alarm object, C-28 Change of State (COS), G-1 DPI Data Rate parameter, B-1 Cyclic, G-2 DPI Device object, C-15...
  • Page 143 Index-3 events clearing, 7-6 heartbeat rate list of, 7-7 definition, G-5 viewing, 7-6 setting in the scanner, 4-4 examples HIM (Human Interface Module) about I/O examples, 5-6 accessing parameters with, 3-1 datalinks, 5-5 definition, G-5 Explicit Messages LCD model, 3-2 about, 6-1 LED model, 3-2 ControlLogix format, 6-2...
  • Page 144 Index-4 LCD HIM, 3-2 NET A status indicator locating, 7-1 LED HIM, 3-2 NET B status indicator LEDs, refer to status indicators locating, 7-1 logic command/status not used, 7-1 bit definitions, D-1 node address definition, G-5 definition, G-6 in I/O image, 5-2 setting with a parameter, 3-7 using, 5-4 setting with switches, 2-2...
  • Page 145 Index-5 Peer B Output parameter, B-7 producer/consumer network, G-7 Peer Cmd Mask parameter, B-6 products, see SCANport or DPI products Peer Flt Action parameter, B-6 programmable logic controller, refer Peer Inp Enable parameter, B-6 to controller Peer Inp Status parameter, B-7 Peer Inp Timeout parameter, B-6 Peer Node to Inp parameter, B-6 quick start, 1-5...
  • Page 146 Index-6 scanner adding devices to a scan list, 4-2 zero data configuring for COS, Cyclic, or configuring an adapter for, 3-16 Polled, 4-4 definition, G-8 definition, G-7 in Master-Slave hierarchy, 3-8 mapping I/O, 4-5 example program for Explicit Messages, 6-12 example program for I/O, 5-11 formatting Explicit Messages, 6-4 specifications...
  • Page 147 Allen-Bradley, DPI, DriveExplorer, DriveTools 2000, DriveTools32, PLC-5, PowerFlex, SCANport, and SLC are trademarks of Rockwell Automation. DeviceNet is a trademark of the Open DeviceNet Vendor Association. RSLinx, RSLogix, and RSNetWorx are trademarks of Rockwell Software. Windows, Windows CE, Windows NT, and Microsoft are either...
  • Page 149 Reach us now at www.rockwellautomation.com Wherever you need us, Rockwell Automation brings together leading brands in industrial automation including Allen-Bradley controls, Reliance Electric power transmission products, Dodge mechanical power transmission components, and Rockwell Software. Rockwell Automation's unique, flexible approach to helping customers achieve a competitive advantage is supported by thousands of authorized partners, distributors and system integrators around the world.

Table of Contents