Allen-Bradley 160-DN2 User Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Control Unit
  5. 160-DN2
  6. User manual

Allen-Bradley 160-DN2 User Manual

Devicenet communication module
Hide thumbs
Table of Contents

Advertisement

Quick Links

DeviceNet™
Communication
Module
Catalog Number 160-DN2
Firmware 3.xxx
User Manual

Advertisement

Table of Contents
loading

Related Manuals for Allen-Bradley 160-DN2

Summary of Contents for Allen-Bradley 160-DN2

  • Page 1 DeviceNet™ Communication Module Catalog Number 160-DN2 Firmware 3.xxx User Manual...
  • Page 2 DeviceNet is a trademark of the Open DeviceNet Vendor Association. SSC is a registered trademark of Rockwell Automation, Inc. Allen-Bradley, ControlLogix, PLC-5, and SLC are trademarks of Rockwell Automation, Inc. RSLinx, RSLogix, and RSNetWorx for DeviceNet are trademarks of Rockwell Software.
  • Page 3 Compliance section. Chapter 5 Added EDS file search screen and removed obsolete Table 6 (EDS files for Bulletin 160 using a 160-DN2 version 3.000 or later). Chapter 6 Replaced DeviceNet Manager software references and screens with those of RSNetWorx for DeviceNet. Added I/O and explicit messaging information and ladder logic examples for ControlLogix, PLC-5, and SLC controllers.
  • Page 4 DeviceNet network. Ability to Create Electronic Data Sheets Configuration tools, such as DeviceNet Manager, can create an Electronic Data Sheet (EDS file) for the 160 SSC drive and 160-DN2 module. Added Parameter Object This object describes the parameters in the 160 SSC drive and 160-DN2 module.

  • Page 5: Table Of Contents

    DeviceNet Compatibility ......... . . P-4 Replacing a 160-DN1 with a 160-DN2 ....... . P-4 Rockwell Automation Support.
  • Page 6 Chapter 6 Using 160-DN2 with Needed Tools ........... 6-2 Setting Device MAC ID’s.
  • Page 7 Table of Contents Chapter 7 Troubleshooting Understanding the COMM LED ........7-2 Understanding the FAULT LED .
  • Page 8 Table of Contents Publication 0160-5.18 - June 2003...

  • Page 9: Preface

    DeviceNet master. Product References In this manual we refer to the: • Bulletin 160-DN2 DeviceNet Communication Module as Communication Module and Module. • Bulletin 160 SSC Variable Frequency AC Drive as the Drive. Conventions...

  • Page 10: Related Documentation

    DeviceNet system. If the network is not installed according to this document, unexpected operation and intermittent failures can occur. Documentation can be obtained online at http://www.ab.com/manuals. Manual Organization This 160-DN2 Module user manual contains the following sections: Chapter Title Contents Preface...

  • Page 11: Safety Precautions

    Using This Manual Safety Precautions Please read the following safety precautions carefully: ATTENTION: Risk of injury or death exists. The drive contains high voltage capacitors which take time to discharge after removal of mains supply. Before installing or removing the DeviceNet Communication Module, make sure to isolate the mains supply from line inputs [L1, L2, L3 (R, S, T)].

  • Page 12: Devicenet Compatibility

    Using This Manual DeviceNet Compatibility The 160-DN2 Communication Module is intended for use only with Bulletin 160 SSC Series A, Bulletin 160 SSC Series B, and Bulletin 160 SSC Series C (FRN 7.03 and later) devices. Bulletin 160 SSC (Series C) devices must use a 160-DN2 Communication Module to connect to a DeviceNet network.

  • Page 13: Module Description

    Chapter Product Overview This chapter contains the following information: • physical layout of the module • location of configuration switches • DeviceNet overview and components Module Description The Bulletin 160 SSC DeviceNet Communication Module is an optional interface device designed to provide a direct, digital link between DeviceNet devices and the Bulletin 160 SSC drive.

  • Page 14: Dip Switches

    Product Overview DIP Switches Figure 1.2 Module Rear View The Communication Module has one eight position DIP switch for setting the DeviceNet Node Address and Baud Rate. DIP switches are located on the rear of the module and are only accessible when the module is removed from the Bulletin 160 SSC drive.

  • Page 15: Introduction

    Chapter Quick Start for Experienced Users Introduction This chapter can help you start using the Bulletin 160 DeviceNet Communication module. If you have previously installed or configured a DeviceNet network and are familiar with Rockwell Automation DeviceNet modules and drives, this information can help reduce installation and startup time.

  • Page 16: Procedures

    Check the contents of the shipping box. — Unpack the shipping box, making sure that it contains: • Bulletin 160 DeviceNet module (Catalog Number 160-DN2) • 10-pin linear plug with probe holes and jack screws • DeviceNet Communication Module 160-DN2 User Manual If the contents are incomplete, call your local Allen-Bradley representative for assistance.

  • Page 17: Required Tools And Equipment

    Required Tools and Equipment Before installing and configuring the 160-DN2 Communication Module, make sure that the contents of the shipping box include: • Bulletin 160-DN2 module (Catalog Number 160-DN2) • 10 pin linear Plug (Part Number 1787-PLUG10R) •...

  • Page 18: Emc Directive 89/336/Eec Compliance

    DeviceNet communication cable enters the control cabinet. Low Voltage Directive 73/23/EEC The 160-DN2 Communication Module complies with Low Voltage Directive 73/23/EEC when conforming to these installation Compliance requirements: •...
  • Page 19 Installation and Wiring is 220 ohms and 0.50 microfarads. Select the voltage rating for the normal AC voltages. A typical surge suppressor that can be used for most transient EMI problems is Electrocube part number RG1676-16 (rated 480V ac). Surge suppressors are usually most effective when connected at the inductive loads.

  • Page 20: Common Mode Noise

    Installation and Wiring Common Mode Noise To greatly reduce high frequency common mode noise current coupled to ground in high capacitance connections, connect a common mode choke at the drive end of the motor cable. The common mode choke reduces the rise time of the high frequency noise by a factor of 10-20, and the amplitude by a factor of 5.

  • Page 21: Removing Program Keypad Module Or Ready/Fault Panel

    Installation and Wiring Removing Program Keypad Module Before installing the Communication Module, it may be necessary to remove a previously installed module such as a Program Keypad or Ready/Fault Panel Module or Ready/Fault Indicating panel. ATTENTION: Risk of injury or death exists. The drive contains high voltage capacitors which take time to discharge after removal of mains supply.

  • Page 22: Setting The Devicenet Node Address

    Installation and Wiring Setting the DeviceNet Node DIP switches 6 through 1 set the module’s node address using binary addressing. The factory default setting is DeviceNet address 63. Address Figure 3.6 Setting the Node Address DeviceNet Address 000000 - 111111 (0 to 63) ON = 1 OFF = 0 To set the DeviceNet node address:...

  • Page 23: Setting The Baud Rate

    Installation and Wiring Setting the Baud Rate Dip switches 7 and 8 set the baud rate at which the Communication Module communicates on the network. The factory default setting for baud rate is 125 kbps. Figure 3.7 Setting the Baud Rate Use DIP Switch 8 and 7 for setting the DeviceNet Baud Rate.

  • Page 24: Installing The Communication Module

    Installation and Wiring Installing the Communication After setting the DIP switches, secure the Communication Module to the drive by following these steps: Module 1. Insert the module, ensuring that the pins on the back of the module line up with the drive’s expansion port. 2.

  • Page 25: Wiring The Devicenet Connector

    Installation and Wiring Wiring the DeviceNet Connector Follow these recommendations for communications wiring: • See DeviceNet Cable System Planning and Installation Manual, Publication DN-6.7.2, for planning and installing DeviceNet networks. • Keep communication wiring away from high noise sources such as motor cables.

  • Page 26: Connecting The Devicenet Drop Line To The Module

    3-10 Installation and Wiring Connecting the DeviceNet Drop To connect your module DeviceNet drop line: Line to the Module 1. Turn off the network power supply. ATTENTION: Do not wire the Communication Module with the network power supply on. Wiring the module with the network power supply on may short your network or disrupt communication.

  • Page 27: Modes Of Operation

    DeviceNet address as the 160-DN2 module. If the power-up or reset is successful, the 160-DN2 module enters the Run mode and the COMM LED flashes green or turns solid green. Publication 0160-5.18 - June 2003...

  • Page 28: Run Mode

    • Accepts messages from the master on the DeviceNet network. • Monitors DeviceNet incoming power. If an error is detected, the 160-DN2 module will enter the Error mode (see heading below for more information). Error Mode If the 160-DN2 module detects an error, the COMM LED is affected.

  • Page 29: Devicenet Parameter Descriptions

    Scanner, for instructions to select an appropriate EDS file.) An EDS file defines all the parameters in the Bulletin 160 drive and the 160-DN2 module, and creates a public interface to the drive on the DeviceNet network. Configuration tools such as RSNetWorx for DeviceNet use EDS files to present you with parameters that enable you to configure the 160 SSC drive via DeviceNet by changing values associated with individual parameters.

  • Page 30: Bulletin 160 Ssc Interface

    This parameter set contains all of the parameters described in the Bulletin 160 SSC User Manual, plus a few extra parameters to configure the operation of the 160-DN2 module on the DeviceNet network. Locating EDS Files on the Internet Bulletin 160 SSC drives are available in Analog Signal Follower and Preset Speed models.

  • Page 31: Bulletin 160 Ssc Interface Parameters

    Page 6-23, for more information. DeviceNet Parameters Use the following parameters to configure and monitor the DeviceNet Network Interface. These parameters are unique to drives equipped with the 160-DN2 DeviceNet Communication Module. Object Mapping Parameter Min./Max. Factory Name and Description...
  • Page 32 70 = Basic Speed Control Input 71 = Extended Speed Control Input 102 = Custom Parameter Based Assembly 104 = Allen-Bradley Drive Assembly 105 = Allen-Bradley Drive Assembly with Parameters Important: See Appendix B, pages B-26 B-28 for the formats of the input assembly.
  • Page 33 0 to 88 This read/write parameter is used when P108 - [Input Assembly] is set to 102 Custom Parameter Based Assembly, or 105 Allen-Bradley Drive Assembly with Parameters. It defines the third word in an assembly built from Bulletin 160 parameters.

  • Page 34: Drive Display Parameters (Read Only)

    Faulted Reverse Latched A-B Internal Use Only Frequency Reference [Drive Type] 0xB3-1-10 Used by Allen-Bradley field service personnel. Numeric Value [Firmware Version] 0xB3-1-11 Version of drive firmware used. Numeric Value ➀ [Input Status] 0xB3-1-12 Open (0) Closed (1) state of Drive’s discrete inputs.
  • Page 35 DeviceNet Parameter Descriptions Drive Display Parameters (Read Only) (Continued) Object Mapping Parameter Parameter Name (Class-Instance- Description Units Number Attribute) [Preset Status] 0xB3-1-15 Open (0) and closed (1) state of TB3 inputs SW1, SW2, and SW3. Binary Number Bit 3 Bit 2 Bit 1 Bit 0 Unused [Analog Input] 0xB3-1-16...

  • Page 36: Drive Program Parameters

    DeviceNet Parameter Descriptions Drive Program Parameters Below is a brief description of the Bulletin 160 SSC Interface Program Group parameters. Refer to the Bulletin 160 SSC User Manual for more detailed information on these parameters. Object Mapping Parameter Parameter Name (Class-Instance- Description Units...
  • Page 37 Number Attribute) [Clear Fault] 0xB3-1-54 Setting to 1 performs a fault reset. Numeric Value [Probe Address] 0xB3-1-55 Used by Allen-Bradley service personnel. Numeric Value [Reset Functions] 0xB3-1-56 Sets all parameters to their factory default. Numeric Value [Program Lock] 0xB3-1-57 Locks all program group parameters.
  • Page 38 5-10 DeviceNet Parameter Descriptions Drive Program Parameters (Continued) Object Mapping Parameter Parameter Name (Class-Instance- Description Units Number Attribute) [Stall Disable] 0xB3-1-80 Amount of time that the drive must be in a stall condition Numeric Value before it causes a stall fault. ATTENTION: Risk of equipment damage exists.

  • Page 39: Using 160-Dn2 With Devicenet Scanner

    “Masters” on a DeviceNet Network for the I/O communication with a 160-DN2 module. Scanners periodically send I/O messages to a 160-DN2 module at a set frequency, and the module responds to these I/O messages by sending status messages back to the scanner.

  • Page 40: Needed Tools

    Using 160-DN2 with DeviceNet Scanner Needed Tools The following tools are needed to set up the 160-DN2 module on a DeviceNet network and operate with a scanner: • RSLinx Software (version 2.3x or higher) • RSNetWorx for DeviceNet (version 3.xxx of higher) •...

  • Page 41: Creating An Eds File

    Using RSNetWorx for DeviceNet Creating an EDS File (Continued) If the 160-DN2 communication module and Bulletin 160 SSC drive appear as an unrecognized device, create an EDS file for it. 1. Right-click the “Unrecognized Device” icon, and select Register Device in the menu. The EDS Wizard (Figure 6.2) appears.

  • Page 42: Accessing And Editing Parameters

    Using RSNetWorx for DeviceNet Accessing and Editing Parameters (Continued) Parameters in the drive and 160-DN2 module can be edited with RSNetWorx for DeviceNet. 1. After creating an EDS file, right-click on the icon for the Bulletin 160 SSC drive and 160-DN2 module and select Properties. The Bulletin 160 Drive dialog box appears.

  • Page 43: Selecting Input And Output Assemblies For I/O Messaging

    “bind attributes of multiple objects to allow data to or from each Assemblies for I/O Messaging object to be sent over a single connection.” The 160-DN2 module uses Assembly Objects to send data to and from a Scanner over an I/O connection.

  • Page 44: Changing The Output Assembly

    Using 160-DN2 with DeviceNet Scanner Selecting Input and Output An example screen (Figure 6.4) shows Output Assembly 103 and Input Assembly 104 selected. The following steps were used: Assemblies for I/O Messaging (Continued) Changing the Output Assembly 1. In the Current Value column, double-click on the value for Parameter 107 - [Output Assembly].

  • Page 45: Enabling Network Control

    Using 160-DN2 with DeviceNet Scanner Enabling Network Control The 160-DN2 module must be configured to accept commands from the network. To do this, configure the drive “Input Mode” parameter (Figure 6.5). Configuring Drive Input Mode 1. In the Current Value column, click on the value for Parameter 46 - [Input Mode] and select “Network Control”...

  • Page 46: Modifying Drive Reset Functions

    Using 160-DN2 with DeviceNet Scanner Enabling Network Control For the new input mode to take effect, modify the drive “Reset Functions” parameter (Figure 6.6). (Continued) Modifying Drive Reset Functions 1. In the Current Value column, click on the value for P56 - [Reset Functions] and select “Reset Input Mode”...

  • Page 47: Configuring The 160 To Accept Speed Commands From The Network

    Using 160-DN2 with DeviceNet Scanner Configuring the 160 to Accept The 160-DN2 module must be configured to accept its speed commands from the network. To do this, change the drive “Frequency Speed Commands from the Select” parameter (Figure 6.7). Network 1.

  • Page 48: Configuring The Scanner

    6-10 Using 160-DN2 with DeviceNet Scanner Configuring the Scanner The scanner must be configured to communicate with the 160-DN2 module and connected Bulletin 160-SSC drive. Example Network After the module is configured, the connected drive and module become a single node on the network. This section provides a step-by-...

  • Page 49: Setting Up The Scan List

    Using 160-DN2 with DeviceNet Scanner 6-11 Configuring the Scanner Setting Up the Scan List (Continued) 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.
  • Page 50 6-12 Using 160-DN2 with DeviceNet Scanner Configuring the Scanner Figure 6.10 Scanlist Page in the Scanner Module Dialog Box (Continued) 7. In the “Scanlist,” select the drive, and then click Edit I/O Param- eters. The Edit I/O Parameters dialog box (Figure 6.11) appears.

  • Page 51: Mapping The Drive Data In The Scanner

    Using 160-DN2 with DeviceNet Scanner 6-13 Configuring the Scanner 9. Type the number of bytes that are required for your I/O in the Input Size and Output Size boxes. (Continued) Refer to Appendix B, pages B-23 B-28 for all Bulletin 160 Assemblies.
  • Page 52 6-14 Using 160-DN2 with DeviceNet Scanner Configuring the Scanner Figure 6.12 Input Page on the Scanner Module Dialog Box (Continued) If you selected the Automap on Add box in the Scanlist tab (Figure 6.10), RSNetWorx has already mapped the I/O. If it is not mapped, click Automap to map it.
  • Page 53 Using 160-DN2 with DeviceNet Scanner 6-15 Configuring the Scanner Mapping the Output I/O (Continued) 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 6.9). Figure 6.13...

  • Page 54: Saving The Configuration

    Save to save the scanner configuration to a file. Using I/O Messaging This section discusses how to use I/O messaging after you have configured the 160-DN2 module and scanner. Example Ladder Logic Programs These example ladder logic programs (Figure 6.14,...

  • Page 55: Controllogix Example

    Using 160-DN2 with DeviceNet Scanner 6-17 Using I/O Messaging (Continued) ControlLogix Example Table 6.C 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...
  • Page 56 6-18 Using 160-DN2 with DeviceNet Scanner Using I/O Messaging (Continued) Figure 6.14 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 57: Plc-5 Example

    Using 160-DN2 with DeviceNet Scanner 6-19 Using I/O Messaging (Continued) PLC-5 Example Table 6.D Control File for Block Transfer EN ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM BT20:0 00 0 BT20:1 00 0 Figure 6.15 Example PLC-5 Ladder Logic Program The scanner gathers drive status data via the DeviceNet network.
  • Page 58 6-20 Using 160-DN2 with DeviceNet Scanner Using I/O Messaging (Continued) Figure 6.15 Example PLC-5 Ladder Logic Program (Continued) Operator Input Bulletin 160 Drive Stop STOP Command Bit Command Bit I:000 N10:1 0006 Operator Input Bulletin 160 Drive Jog Command Bit...

  • Page 59: Slc Example

    Using 160-DN2 with DeviceNet Scanner 6-21 Using I/O Messaging (Continued) SLC Example Figure 6.16 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.
  • Page 60 6-22 Using 160-DN2 with DeviceNet Scanner Using I/O Messaging (Continued) Figure 6.16 Example SLC Ladder Logic Program (Continued) Bulletin 160 Operator Input CLEAR FAULTS Drive Clear Faults 0007 Command Bit Command Bit N10:0 I:2.0 1746-I*16 Bulletin 160 REFERENCE Command Word...

  • Page 61: Using Explicit Messaging

    6-23 Using Explicit Messaging This section provides information and examples that explain how to use Explicit Messaging to monitor and configure the 160-DN2 module and connected Bulletin 160-SSC drive. ATTENTION: Hazard of injury or equipment damage exists. The examples in this publication are intended solely for purposes of example.
  • Page 62 6-24 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging Figure 6.17 ControlLogix Message Format in RSLogix 5000 (Continued) ➊ ➋ ➐ ➑ ➌ ➍ ➒ ➎ ➏ ➓ Page 6-25 for a description of the data required for each box (1 – 7).
  • Page 63 • Name of the DeviceNet scanner. • Communication port on the front of the 1756-DNB scanner. Always 2. • Node address of the 160-DN2 module. This is set with switches or parameters in the module. Tip: Click Browse to find the path or type in the name of a module that you previously mapped.
  • Page 64 6-26 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging Explicit Messages for a PLC-5 or SLC Controller (Continued) Transaction blocks in PLC-5 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.
  • Page 65 Using 160-DN2 with DeviceNet Scanner 6-27 Using Explicit Messaging PLC-5 / SLC Explicit Message Requests (Continued) Word Description Command (Least Significant Byte) The Command is a code that instructs the scanner how to administer the request during each download. 00 = Ignore transaction block (empty)
  • Page 66 6-28 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging PLC-5 / SLC Explicit Message Responses (Continued) 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...

  • Page 67: Executing Explicit Messages

    Using 160-DN2 with DeviceNet Scanner 6-29 Using Explicit Messaging Executing Explicit Messages (Continued) There are five basic events in the Explicit Messaging process. The details of each step will vary depending on the controller (ControlLogix, PLC-5, or SLC). Refer to the documentation for your controller.
  • Page 68 6-30 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging ControlLogix Example (Continued) Data Format for a Read and Write Parameter The data in this example is for a Bulletin 160-SSC drive at MAC ID For a description of the content in each box, refer to the “Formatting...
  • Page 69 Using 160-DN2 with DeviceNet Scanner 6-31 Using Explicit Messaging Figure 6.22 ParameterWriteMessage Screen (Continued) Setting Description Refer to . . . Message Type CIP Generic Must be CIP Generic 6-25 Service Type Set Attribute Single Defines Service Code as text message...
  • Page 70 6-32 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging (Continued) Table 6.E Tags for ControlLogix Example Explicit Messaging Program Tag Names Tag Names Type Type for Read Messages for Write Messages StartParameterRead BOOL StartParameterWrite BOOL Output_Current ParameterWriteMessage MESSAGE ParameterReadMessage MESSAGE Accel_Time_1 Figure 6.23...
  • Page 71 Using 160-DN2 with DeviceNet Scanner 6-33 Using Explicit Messaging PLC-5 Example (Continued) Data Format for a Read and Write Parameter The data in this example is for a Bulletin 160-SSC drive at MAC ID For a description of the content of the data file, refer to the “Formatting Explicit...
  • Page 72 6-34 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging Figure 6.24 PLC-5 Example Explicit Messaging Ladder Logic Program (Continued) 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 73 Using 160-DN2 with DeviceNet Scanner 6-35 Using Explicit Messaging SLC Example (Continued) Data Format for a Read and Write Parameter The data in this example is for a Bulletin 160-SSC drive at MAC ID For a description of the content of the data file, refer to the “Formatting Explicit...
  • Page 74 6-36 Using 160-DN2 with DeviceNet Scanner Using Explicit Messaging Important: To originate a scanner transaction, use a copy operation to M0:[slot number]:224. Then, use a copy operation to read (Continued) M1:1.224 for the result. If more than one message is enabled, use the TXID to determine which message you are reading.

  • Page 75: Troubleshooting

    Chapter Troubleshooting This chapter provides information for troubleshooting potential problems with the 160-DN2 DeviceNet Communication Module and network. Figure 7.1 Module Front View READY LED - Green when drive is powered up. CONFORMANCE TESTED CONFORMANCE TESTED FAULT LED - Red when drive is faulted Off when drive not faulted.

  • Page 76: Understanding The Comm Led

    Understanding the COMM LED The COMM LED provides status information on 160-DN2 module operations. The table below shows how to use the LED to detect and correct common operation problems.

  • Page 77: Understanding The Fault Led

    Troubleshooting Understanding the FAULT LED When the FAULT LED is Red, a drive fault is present. To view the fault code, you must either view P7 - [Present Fault] or read the value of Class 0x29 (Control Supervisor Object) Instance 1 Attribute 13 (Fault Code).
  • Page 78 No DeviceNet Power 24 volt network power is not detected. Check DeviceNet connector at module. Also, check the network’s power supply. DeviceNet Module DeviceNet 160-DN2 module EEPROM has invalid data. Reset to factory defaults P56 - [Reset Functions]. EEPROM Fault DeviceNet Lost Polled I/O connection timed out.
  • Page 79 6310 EEPROM Fault EEPROM has invalid data. Reset EEPROM. 6311 DeviceNet Module DevicNet 160-DN2 module EEPROM has invalid data. Reset to factory defaults using P56 - [Reset Defaults]. EEPROM Fault 7121 Motor Stalled Motor has stalled. Motor load is excessive.
  • Page 80 Troubleshooting Notes: Publication 0160-5.18 - June 2003...

  • Page 81: Specifications

    Appendix Specifications Electrical Network Supply Voltage 11 to 25V dc ➀ Node Current Consumption 40 mA maximum Power Consumption 1W maximum Environmental Ambient Temperature Operating 0 to 50° C (32 to 122° F) Storage -40 to 85° C (-40 to 185° F) Relative Humidity 0 to 95% non-condensing 1.0 G operational...
  • Page 82 Specifications Notes: Publication 0160-5.18 - June 2003...

  • Page 83: Devicenet Information

    Appendix DeviceNet Information The DeviceNet 160-DN2 module enables a Bulletin 160 SSC drive to operate as a slave device on a DeviceNet network. The module supports Explicit Messages and Polled or Change of State/Cyclic I/O Messages of the predefined master/slave connection set. A scanner must be used to properly route messages to a slave device.

  • Page 84: Object Classes

    DeviceNet Information Object Classes The 160-DN2 module supports these object classes: Class Object Refer to . . . 0x01 Identity 0x03 DeviceNet 0x04 Assembly B-23 0x05 Connection 0x0F Parameter 0x10 Parameter Group B-11 0x28 Motor Data B-12 0x29 Control Supervisor...

  • Page 85: Class Code 0X01 - Identity Object

    DeviceNet Information Class Code 0x01 — Class Attributes Identity Object Attribute ID Access Rule Name Data Type Value Revision UINT Max Instances UINT Max ID Class UINT Max ID Instance UINT Number of Instances: 2 Instance 1 Attributes: Drive Instance Attribute ID Access Rule Name...
  • Page 86 DeviceNet Information Class Code 0x01— Identity Object (Continued) Instance 2 Attributes: DeviceNet Instance Attribute ID Access ID Name Data Type Value Vendor UINT Product Type UINT 105 = Subassembly Product Code UINT Revision Structure of Major USINT Minor USINT 0 = Not Owned Status WORD 1 = Owned by Master...

  • Page 87: Class Code 0X03 - Devicenet Object

    DeviceNet Information Class Code 0x03 — DeviceNet Object Class Attributes: None Supported Number of Instances: 1 Instance 1 Attributes Attribute ID Access Rule Name Data Type Value Get/Set Node Address USINT 0 to 63 Get/Set Data Rate USINT 0 to 2 0 = Hold in error state on BOI error Get/Set BOOL...

  • Page 88: Class Code 0X05 - Connection Object

    DeviceNet Information Class Code 0x05 — Connection Object Class Attributes: None Supported Number of Instances: 3 Instance 1 Attributes: Explicit Message Instance Attribute ID Access Rule Name Data Type Value 0 = Nonexistant 1 = Configuring State USINT 3 = Established 4 = Timed out 5 = Deferred delete Instance Type...
  • Page 89 DeviceNet Information Class Code 0x05 — Connection Object (Continued) Instance 2 Attributes: Polled I/O Message Connection Attribute ID Access Rule Name Data Type Value 0 = Nonexistant 1 = Configuring State USINT 3 = Established 4 = Timed out Instance Type USINT 1 = I/O Message Transport Class Trigger...
  • Page 90 DeviceNet Information Class Code 0x05 — Connection Object (Continued) Instance 4 Attributes: Change of State/Cyclic Instance Attribute ID Access Rule Name Data Type Value 0 = Nonexistant 1 = Configuring State USINT 3 = Established 4 = Timed out Instance Type USINT 1 = I/O Message Transport Class Trigger...

  • Page 91: Class Code 0X0F - Parameter Object

    DeviceNet Information Class Code 0x0F — Class Attributes Parameter Object Attribute ID Access Rule Name Data Type Value Revision UINT Max Instance UINT Parameter Class Descriptor WORD 0x0B Configuration Assembly Instance UINT Native Language USINT 0 = English Number of Instances: 118 Instance 1 through 118 Attributes Attribute ID Access Rule...
  • Page 92 B-10 DeviceNet Information Class Code 0x0F — Parameter Object (Continued) Instance 1 through 118 Attributes (Continued) Attribute ID Access Rule Name Data Type Value ➀ Divisor Link UINT ➀ Base Link UINT ➀ Offset Link UINT ➀ Decimal Precision USINT ➀...

  • Page 93: Class Code 0X10 - Parameter Group Object

    DeviceNet Information B-11 Class Code 0x10 — Class Attributes Parameter Group Object Attribute ID Access Rule Name Data Type Value Revision UINT Max Instance UINT Native Language USINT 0 = English Number of Instances: 3 Instance 1 through 3 Attributes Attribute ID Access Rule Name...

  • Page 94: Class Code 0X28 - Motor Data Object

    B-12 DeviceNet Information Class Code 0x28 — Motor Data Object Class Attributes: None Supported Number of Instances: 1 Instance 1 Attributes Access Attribute ID Name Data Type Min/Max Units Default Description Rule 115% of Rated Stator Current Get/Set Rated Current UINT 0 to 100.00 0.01 Amps...

  • Page 95: Class Code 0X29 - Control Supervisor Object

    DeviceNet Information B-13 Class Code 0x29 — Control Supervisor Object Class Attributes: None Supported Number of Instances: 1 Instance 1 Attributes Access Attribute ID Name Data Type Min/Max Default Description Rule Get/Set RunFwd BOOL 0 to 1 See page B-15. Get/Set RunRev BOOL...

  • Page 96: State Transition Diagram

    B-14 DeviceNet Information Class Code 0x29 — Common Services Control Supervisor Object (Continued) Implemented for: Service Service Code Name Class Instance 0x0E Get_Attribute_Single 0x10 Set_Attribute_Single State Transition Diagram The following State Transition Diagram provides a graphical description of the states and state transitions that are described for attribute 6 on page B-13.

  • Page 97: Run/Stop Event Matrix

    DeviceNet Information B-15 Class Code 0x29 — Run/Stop Event Matrix Control Supervisor Object Attribute 5, NetCtrl is used to request that Run/Stop events be (Continued) controlled from the network. However, before Run/Stop control is accomplished from the network, these things must occur: •...

  • Page 98: Class Code 0X2A - Ac Drive Object

    B-16 DeviceNet Information Class Code 0x2A — AC Drive Object Class Attributes: None Supported Number of Instances: 1 Instance 1 Attributes Attribute Access Data Name Min/Max Units Default Description Rule Type AtReference BOOL 0 to 1 Set to 1 when SpeedActual is equal to SpeedRef. 1 = Drive uses SpeedRef (attribute 8) as its speed reference.

  • Page 99: Class Code 0X2B - Acknowledge Handler Object

    DeviceNet Information B-17 Class Code 0x2B — Acknowledge Handler Object Class Attributes: None Supported Number of Instances: 1 Instance 1 Attributes Attribute ID Access Rule Name Data Type Min/Max Default Get/Set Acknowledge Timer UINT 1 to 65,535 16 ms Get/Set Retry Limit USINT 0 to 255...

  • Page 100: Class Code 0Xb3 — 160 Parameter Table Object

    Temperature of the drive heatsink. [Drive Status] WORD Binary Number Status of drive in binary coded format. [Drive Type] USINT Numeric Value Used by Allen-Bradley field service personnel. [Control Version] UINT Numeric Value version of drive firmware used. [Input Status] WORD Binary Number Open (0) Closed (1) state of drive’s discrete inputs.
  • Page 101 [Clear Fault] BOOL Numeric Value Setting to 1 performs a fault reset. Get/Set [Probe Address] UINT Numeric Value Used by Allen-Bradley service personnel. Get/Set [Reset Functions] USINT Numeric Value Sets all parameters to their factory default. Get/Set [Program Lock] BOOL Numeric Value Locks all program group parameters.
  • Page 102 B-20 DeviceNet Information Class Code 0xB3 — 160 Parameter Table Object (Continued) Access Data Attribute ID Parameter Name Units Description Rule Type Get/Set [Zero Offset] Numeric Value Add or subtracts an offset to the analog input. Get/Set [DN Preset Cmd] USINT Numeric Value Network preset command.
  • Page 103 DeviceNet Information B-21 Class Code 0xB3 — Common Services 160 Parameter Table Object (Continued) Implemented for: Service Service Code Name Class Instance 0x0E Get_Attribute_Single 0x10 Set_Attribute_Single Publication 0160-5.18 - June 2003...

  • Page 104: Class Code 0Xb4 - Dn Interface Object

    DeviceNet DIP BYTE 0 to 255 Current DIP switch settings on the 160-DN2 module. Switches ➀ If set to a “9,” P9 - [Drive Status] (of the SSC Interface Profile) goes in the low byte of the assembly field, and P12 - [Input Status] (of the SSC Interface Profile) goes in the high byte of the assembly field.

  • Page 105: Class Code 0X04 - Assembly Objects

    DeviceNet Information B-23 Class Code 0x04 — Assembly Objects Class Attributes: None Supported Number of Instances: 19 Instance 1 to 105 Attributes: I/O Instances Access Attribute ID Name Data Type Min/Max Default Description Rule Data See instance data format for individual I/O assemblies on pages B-24 through B-28.

  • Page 106: Instance Data Format: Output Assemblies

    B-24 DeviceNet Information Class Code 0x04 — Instance Data Format: Output Assemblies Assembly Objects (Continued) Instance 1 Data Format (Basic Contactor Output Assembly) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Instance 2 Data Format (Basic Overload Output Assembly) Byte Bit 7...
  • Page 107 (DN Preset Cmd contains these three bits) (acts like TB2-4 (acts like TB2-2 (acts like TB2-1 or SW3) or SW2) or SW1) Instance 103 Allen-Bradley Drive Output Assembly This output assembly mirrors the 1305/1336 IO format. Byte Bit 7 Bit 6 Bit 5 Bit 4...

  • Page 108: Instance Data Format: Input Assemblies

    B-26 DeviceNet Information Class Code 0x04 — Instance Data Format: Input Assemblies Assembly Objects (Continued) Instance 50 Data Format (Basic Overload/Contactor Input Assembly) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Faulted Instance 51 Data Format (Extended Overload/Contactor Input Assembly) Byte...
  • Page 109 Value of parameter pointed to by Parameter Number 111 (High Byte) Value of parameter pointed to by Parameter Number 112 (Low Byte) Value of parameter pointed to by Parameter Number 112 (High Byte) Instance 104: Allen-Bradley Input Assembly This input assembly mirrors the Bulletin 1305 I/O Format. Byte...
  • Page 110 Instance Data Format: Input Assemblies (Continued) Assembly Objects (Continued) Instance 105: Allen-Bradley Drive Input Assembly with Parameters 160 SSC parameter values are used to form the Output_Data structure for this assembly. Parameters 111 and 112 contain numbers of the display parameter values that form this assembly.

  • Page 111: Configuration Assembly Data Formats

    DeviceNet Information B-29 Class Code 0x04 — Configuration Assembly Data Formats Assembly Objects (Continued) Instance 191 Data Format (Fixed Configuration Assembly – All Preset Speed Models) Parameter Parameter Config Num. Description Size Config Num. Description Size Number Number Input Mode Accel Time 1 Decel Time 1 Output Configuration...

  • Page 112: Publication 0160-5.18 - June

    B-30 DeviceNet Information Class Code 0x04 — Configuration Assembly Data Formats (Continued) Assembly Objects (Continued) Instance 193 Data Format (Fixed Configuration Assembly – DeviceNet Module) Config Num. Parameter Number Description Size None Reserved Motor Base RPM DN Fault Mode Output Assembly Input Assembly NV MAC ID NV Baud...

  • Page 113: Index

    Index Electronic Data Sheets, see EDS files baud rate (data rate) equipment required, 3-1 factory default, 3-7 error mode, 4-2 settings, 3-7 Explicit Messages example for ControlLogix, 6-30 example for PLC-5, 6-33 example for SLC, 6-35 Change of State (COS) data exchange using ControlLogix, 6-23 configuring scanner for, 6-12 using PLC-5, 6-26...
  • Page 114 Index removing Read/Fault panel, 3-5 LEDs, see COMM LED, FAULT LED or READY LED required equipment, 3-1 run mode, 4-2 modes of operation error mode, 4-2 scanner power-up reset mode, 4-1 configuring for Polled, COS or Cyclic, 6-12 run mode, 4-2 mapping the drive data, 6-13 modifying drive reset functions, 6-8 setting up the scan list, 6-11...
  • Page 116 Publication 0160-5.18 – June, 2003 P/N 193557-P02 Supersedes 0160-5.18 – March, 1999 Copyright © 2003 Rockwell Automation, Inc. All rights reserved. Printed in USA.

Table of Contents